diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/hardware.pot | 458 | ||||
| -rw-r--r-- | po/pot/install-methods.pot | 360 | ||||
| -rw-r--r-- | po/pot/installation-howto.pot | 30 | ||||
| -rw-r--r-- | po/pot/partitioning.pot | 150 | ||||
| -rw-r--r-- | po/pot/preparing.pot | 4 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 6 | ||||
| -rw-r--r-- | po/pot/random-bits.pot | 28 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 798 |
8 files changed, 903 insertions, 931 deletions
diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index e5a7b747e..1bd77cd52 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2008-09-01 00:10+0000\n" +"POT-Creation-Date: 2008-09-28 00:09+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" @@ -543,7 +543,7 @@ msgid "This is the first official release of &debian; for the &arch-title; archi msgstr "" #. Tag: title -#: hardware.xml:241 hardware.xml:700 hardware.xml:736 hardware.xml:840 hardware.xml:859 hardware.xml:945 hardware.xml:987 hardware.xml:1061 hardware.xml:1133 +#: hardware.xml:241 hardware.xml:700 hardware.xml:736 hardware.xml:840 hardware.xml:859 hardware.xml:944 hardware.xml:986 hardware.xml:1060 hardware.xml:1132 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" @@ -1665,7 +1665,7 @@ msgid "Complete information concerning supported peripherals can be found at <ul msgstr "" #. Tag: title -#: hardware.xml:709 hardware.xml:868 hardware.xml:1034 +#: hardware.xml:709 hardware.xml:868 hardware.xml:1033 #, no-c-format msgid "<title>CPU</title>" msgstr "" @@ -1787,1337 +1787,1337 @@ msgstr "" #. Tag: para #: hardware.xml:922 #, 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). Essentially all personal computers sold in recent years use one of these." +msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, PCIe, 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:946 +#: hardware.xml:945 #, 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:953 +#: hardware.xml:952 #, 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:961 +#: hardware.xml:960 #, 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:988 +#: hardware.xml:987 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run Debian on MIPS if you don't have the hardware. </para></listitem> <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:1035 +#: hardware.xml:1034 #, 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:1045 +#: hardware.xml:1044 #, 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:1062 +#: hardware.xml:1061 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run Debian on MIPS if you don't have the hardware. </para></listitem> <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:1103 +#: hardware.xml:1102 #, no-c-format msgid "CPU/Machine types" msgstr "" #. Tag: para -#: hardware.xml:1105 +#: hardware.xml:1104 #, no-c-format msgid "All MIPS based Cobalt machines are supported." msgstr "" #. Tag: para -#: hardware.xml:1109 +#: hardware.xml:1108 #, 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:1119 +#: hardware.xml:1118 #, no-c-format msgid "Supported console options" msgstr "" #. Tag: para -#: hardware.xml:1120 +#: hardware.xml:1119 #, no-c-format msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps." msgstr "" #. Tag: para -#: hardware.xml:1134 +#: hardware.xml:1133 #, 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:1141 #, 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:1149 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:1152 +#: hardware.xml:1151 #, 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:1158 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:1160 +#: hardware.xml:1159 #, 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:1169 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:1171 +#: hardware.xml:1170 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:1175 +#: hardware.xml:1174 #, 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:1180 #, 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:1185 #, 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:1194 #, no-c-format msgid "<term>prep</term>" msgstr "" #. Tag: para -#: hardware.xml:1196 +#: hardware.xml:1195 #, no-c-format msgid "This kernel flavour supports the PReP subarchitecture." msgstr "" #. Tag: term -#: hardware.xml:1204 +#: hardware.xml:1203 #, no-c-format msgid "apus" msgstr "" #. Tag: para -#: hardware.xml:1205 +#: hardware.xml:1204 #, 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:1217 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:1220 +#: hardware.xml:1219 #, 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:1226 #, 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:1234 #, 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:1242 #, 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:1258 hardware.xml:1393 hardware.xml:1437 hardware.xml:1466 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:1260 +#: hardware.xml:1259 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:1266 +#: hardware.xml:1265 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:1267 +#: hardware.xml:1266 #, 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:1267 hardware.xml:1270 hardware.xml:1273 hardware.xml:1276 hardware.xml:1279 hardware.xml:1282 hardware.xml:1285 hardware.xml:1288 hardware.xml:1291 hardware.xml:1294 hardware.xml:1297 hardware.xml:1300 hardware.xml:1303 hardware.xml:1306 hardware.xml:1309 hardware.xml:1312 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:1270 +#: hardware.xml:1269 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:1273 +#: hardware.xml:1272 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:1276 +#: hardware.xml:1275 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:1279 +#: hardware.xml:1278 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:1282 +#: hardware.xml:1281 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:1285 +#: hardware.xml:1284 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:1288 +#: hardware.xml:1287 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:1291 +#: hardware.xml:1290 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:1294 +#: hardware.xml:1293 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:1297 +#: hardware.xml:1296 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:1300 +#: hardware.xml:1299 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:1303 +#: hardware.xml:1302 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:1306 +#: hardware.xml:1305 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:1309 +#: hardware.xml:1308 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:1312 +#: hardware.xml:1311 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:1315 +#: hardware.xml:1314 #, 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:1315 hardware.xml:1318 hardware.xml:1321 hardware.xml:1324 hardware.xml:1327 hardware.xml:1330 hardware.xml:1333 hardware.xml:1336 hardware.xml:1339 hardware.xml:1342 hardware.xml:1345 hardware.xml:1348 hardware.xml:1354 hardware.xml:1357 hardware.xml:1363 hardware.xml:1369 hardware.xml:1375 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:1318 +#: hardware.xml:1317 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:1321 +#: hardware.xml:1320 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:1324 +#: hardware.xml:1323 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:1327 +#: hardware.xml:1326 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:1330 +#: hardware.xml:1329 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:1333 +#: hardware.xml:1332 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:1336 +#: hardware.xml:1335 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:1339 +#: hardware.xml:1338 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:1342 +#: hardware.xml:1341 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:1345 +#: hardware.xml:1344 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:1348 +#: hardware.xml:1347 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:1353 +#: hardware.xml:1352 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:1354 +#: hardware.xml:1353 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:1357 +#: hardware.xml:1356 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:1362 +#: hardware.xml:1361 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:1363 +#: hardware.xml:1362 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:1368 +#: hardware.xml:1367 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1369 +#: hardware.xml:1368 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:1374 hardware.xml:1400 +#: hardware.xml:1373 hardware.xml:1399 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:1375 +#: hardware.xml:1374 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:1384 +#: hardware.xml:1383 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1401 +#: hardware.xml:1400 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:1403 +#: hardware.xml:1402 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:1405 +#: hardware.xml:1404 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:1407 +#: hardware.xml:1406 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:1409 +#: hardware.xml:1408 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:1413 hardware.xml:1444 +#: hardware.xml:1412 hardware.xml:1443 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:1414 +#: hardware.xml:1413 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:1416 +#: hardware.xml:1415 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:1418 +#: hardware.xml:1417 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:1420 +#: hardware.xml:1419 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:1428 +#: hardware.xml:1427 #, no-c-format msgid "CHRP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1445 +#: hardware.xml:1444 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:1448 +#: hardware.xml:1447 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:1449 +#: hardware.xml:1448 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: title -#: hardware.xml:1457 +#: hardware.xml:1456 #, no-c-format msgid "APUS subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1473 +#: hardware.xml:1472 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:1474 +#: hardware.xml:1473 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:1482 +#: hardware.xml:1481 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:1484 +#: hardware.xml:1483 #, 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:1520 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:1523 +#: hardware.xml:1522 #, 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:1531 #, 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:1539 #, 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:1555 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "" #. Tag: para -#: hardware.xml:1557 +#: hardware.xml:1556 #, 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://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: title -#: hardware.xml:1579 +#: hardware.xml:1578 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para -#: hardware.xml:1580 +#: hardware.xml:1579 #, no-c-format msgid "Sparc-based hardware is divided into a number of different subarchitectures, identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u or sun4v. The following list describes what machines they include and what level of support may be expected for each of them." msgstr "" #. Tag: term -#: hardware.xml:1591 +#: hardware.xml:1590 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "" #. Tag: para -#: hardware.xml:1593 +#: hardware.xml:1592 #, no-c-format msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1600 +#: hardware.xml:1599 #, no-c-format msgid "The last Debian release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases." msgstr "" #. Tag: term -#: hardware.xml:1610 +#: hardware.xml:1609 #, no-c-format msgid "<term>sun4u</term>" msgstr "" #. Tag: para -#: hardware.xml:1612 +#: hardware.xml:1611 #, no-c-format msgid "This subarchitecture includes all 64-bit machines (sparc64) based on the UltraSparc processor and its clones. Most of the machines are well supported, even though for some you may experience problems booting from CD due to firmware or bootloader bugs (this problem may be worked around by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP configurations respectively." msgstr "" #. Tag: term -#: hardware.xml:1625 +#: hardware.xml:1624 #, no-c-format msgid "<term>sun4v</term>" msgstr "" #. Tag: para -#: hardware.xml:1627 +#: hardware.xml:1626 #, no-c-format msgid "This is the newest addition to the Sparc family, which includes machines based on the Niagara multi-core CPUs. At the moment such CPUs are only available in T1000 and T2000 servers by Sun, and are well supported. Use the sparc64-smp kernel." msgstr "" #. Tag: para -#: hardware.xml:1638 +#: hardware.xml:1637 #, no-c-format msgid "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel." msgstr "" #. Tag: title -#: hardware.xml:1647 +#: hardware.xml:1646 #, no-c-format msgid "Graphics Card Support" msgstr "" #. Tag: para -#: hardware.xml:1648 +#: hardware.xml:1647 #, 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:1656 +#: hardware.xml:1655 #, 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:1665 +#: hardware.xml:1664 #, no-c-format msgid "The X.Org X 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:1674 +#: hardware.xml:1673 #, no-c-format msgid "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:1681 +#: hardware.xml:1680 #, no-c-format msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card." msgstr "" #. Tag: para -#: hardware.xml:1691 +#: hardware.xml:1690 #, no-c-format msgid "It is not uncommon for a Sparc machine to have two graphics cards in a default configuration. In such a case there is a possibility that the Linux kernel will not direct its output to the card initially used by the firmware. The lack of output on the graphical console may then be mistaken for a hang (usually the last message seen on console is 'Booting Linux...'). One possible solution is to physically remove one of the video cards; another option is to disable one of the cards using a kernel boot parameter. Also, if graphical output is not required or desired, serial console may be used as an alternative. On some systems use of serial console can be activated automatically by disconnecting the keyboard before booting the system." msgstr "" #. Tag: title -#: hardware.xml:1708 +#: hardware.xml:1707 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1709 +#: hardware.xml:1708 #, 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:1720 hardware.xml:1742 hardware.xml:1762 hardware.xml:1785 +#: hardware.xml:1719 hardware.xml:1741 hardware.xml:1761 hardware.xml:1784 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1721 +#: hardware.xml:1720 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image 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:1729 +#: hardware.xml:1728 #, 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:1744 +#: hardware.xml:1743 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image 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:1753 +#: hardware.xml:1752 #, 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:1763 +#: hardware.xml:1762 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. However, the standard Debian &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1772 +#: hardware.xml:1771 #, 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:1786 +#: hardware.xml:1785 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture, and is supported by a precompiled Debian kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1796 +#: hardware.xml:1795 #, 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." msgstr "" #. Tag: para -#: hardware.xml:1802 +#: hardware.xml:1801 #, no-c-format msgid "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:1819 +#: hardware.xml:1818 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:1821 +#: hardware.xml:1820 #, no-c-format msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used to install Debian. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section." msgstr "" #. Tag: title -#: hardware.xml:1832 +#: hardware.xml:1831 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:1833 +#: hardware.xml:1832 #, 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:1839 +#: hardware.xml:1838 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:1846 +#: hardware.xml:1845 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:1848 +#: hardware.xml:1847 #, 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:1855 +#: hardware.xml:1854 #, 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:1867 +#: hardware.xml:1866 #, 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." +msgid "SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux." msgstr "" #. Tag: para -#: hardware.xml:1877 +#: hardware.xml:1872 #, 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:1882 +#: hardware.xml:1877 #, 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:1891 +#: hardware.xml:1886 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines." msgstr "" #. Tag: para -#: hardware.xml:1895 +#: hardware.xml:1890 #, no-c-format msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card." msgstr "" #. Tag: title -#: hardware.xml:1913 +#: hardware.xml:1908 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:1915 +#: hardware.xml:1910 #, 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:1921 +#: hardware.xml:1916 #, 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:1926 +#: hardware.xml:1921 #, 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:1934 +#: hardware.xml:1929 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:1936 +#: hardware.xml:1931 #, 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:1948 +#: hardware.xml:1943 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:1950 +#: hardware.xml:1945 #, no-c-format msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP." msgstr "" #. Tag: para -#: hardware.xml:1960 +#: hardware.xml:1955 #, no-c-format msgid "You can also <emphasis>boot</emphasis> the installation system over the network. <phrase arch=\"mips\">This is the preferred installation technique for &arch-title;.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1966 +#: hardware.xml:1961 #, no-c-format msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." msgstr "" #. Tag: title -#: hardware.xml:1974 +#: hardware.xml:1969 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:1976 +#: hardware.xml:1971 #, no-c-format msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." msgstr "" #. Tag: title -#: hardware.xml:1988 +#: hardware.xml:1983 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:1990 +#: hardware.xml:1985 #, 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:2000 +#: hardware.xml:1995 #, 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." +msgid "Generally, the Debian installation system includes support for floppies, IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." msgstr "" #. Tag: para -#: hardware.xml:2007 +#: hardware.xml:2002 #, 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." +msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or PATA — are supported. SATA and SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." msgstr "" #. Tag: para -#: hardware.xml:2017 +#: hardware.xml:2010 #, 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:2027 +#: hardware.xml:2020 #, 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:2060 +#: hardware.xml:2053 #, 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:2069 +#: hardware.xml:2062 #, 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:2075 +#: hardware.xml:2068 #, 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:2081 +#: hardware.xml:2074 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:2086 +#: hardware.xml:2079 #, 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:2103 +#: hardware.xml:2096 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:2104 +#: hardware.xml:2097 #, 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:2110 +#: hardware.xml:2103 #, no-c-format msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>)." msgstr "" #. Tag: para -#: hardware.xml:2116 +#: hardware.xml:2109 #, 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:2122 +#: hardware.xml:2115 #, 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:2128 +#: hardware.xml:2121 #, 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:2134 +#: hardware.xml:2127 #, 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:2144 +#: hardware.xml:2137 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" #. Tag: para -#: hardware.xml:2146 +#: hardware.xml:2139 #, 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:2154 +#: hardware.xml:2147 #, 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:2159 +#: hardware.xml:2152 #, 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:2167 +#: hardware.xml:2160 #, 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:2178 +#: hardware.xml:2171 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:2179 +#: hardware.xml:2172 #, 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:2186 +#: hardware.xml:2179 #, 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:2197 +#: hardware.xml:2190 #, 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:2209 +#: hardware.xml:2202 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:2210 +#: hardware.xml:2203 #, 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:2223 +#: hardware.xml:2216 #, no-c-format msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes it being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" #. Tag: para -#: hardware.xml:2244 +#: hardware.xml:2237 #, 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:2261 +#: hardware.xml:2254 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:2263 +#: hardware.xml:2256 #, no-c-format msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>." msgstr "" #. Tag: para -#: hardware.xml:2270 +#: hardware.xml:2263 #, no-c-format msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users." msgstr "" #. Tag: para -#: hardware.xml:2287 +#: hardware.xml:2280 #, 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:2296 +#: hardware.xml:2289 #, 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:2304 +#: hardware.xml:2297 #, 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:2314 +#: hardware.xml:2307 #, no-c-format msgid "FIXME: is this still true?" msgstr "" #. Tag: title -#: hardware.xml:2325 +#: hardware.xml:2318 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:2326 +#: hardware.xml:2319 #, no-c-format msgid "Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase> <phrase arch=\"m68k\">Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:2338 +#: hardware.xml:2331 #, no-c-format msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:" msgstr "" #. Tag: para -#: hardware.xml:2344 +#: hardware.xml:2337 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:2349 +#: hardware.xml:2342 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:2354 +#: hardware.xml:2347 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:2359 +#: hardware.xml:2352 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:2364 +#: hardware.xml:2357 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:2371 +#: hardware.xml:2364 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:2376 +#: hardware.xml:2369 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:2381 +#: hardware.xml:2374 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:2386 +#: hardware.xml:2379 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:2395 +#: hardware.xml:2388 #, no-c-format msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided. The major exception is the IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a proprietary microcode for the operation of its built-in Ethernet device. Unofficial images for Linksys NSLU2 with this proprietary microcode can be obtained from the <ulink url=\"&url-slug-firmware;\">Slug-Firmware site</ulink>." msgstr "" #. Tag: para -#: hardware.xml:2405 +#: hardware.xml:2398 #, no-c-format msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;. Using ISDN during the installation is not supported." msgstr "" #. Tag: title -#: hardware.xml:2414 +#: hardware.xml:2407 #, no-c-format msgid "Drivers Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:2415 +#: hardware.xml:2408 #, no-c-format msgid "The installation system currently does not support retrieving firmware. This means that any network cards that use a driver that requires firmware to be loaded, is not supported by default." msgstr "" #. Tag: para -#: hardware.xml:2421 +#: hardware.xml:2414 #, no-c-format msgid "If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually. Note that the firmware may be packaged separately from the driver and may not be available in the <quote>main</quote> section of the &debian; archive." msgstr "" #. Tag: para -#: hardware.xml:2432 +#: hardware.xml:2425 #, no-c-format msgid "If the driver itself <emphasis>is</emphasis> supported, you may also be able to use the NIC during installation by copying the firmware from some medium to <filename>/usr/lib/hotplug/firmware</filename>. Don't forget to also copy the firmware to that location for the installed system before the reboot at the end of the installation." msgstr "" #. Tag: title -#: hardware.xml:2444 +#: hardware.xml:2437 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:2445 +#: hardware.xml:2438 #, no-c-format msgid "Wireless NICs are in general supported as well, with one big proviso. A lot of wireless adapters require drivers that are either non-free or have not been accepted into the official Linux kernel. These NICs can generally be made to work under &debian;, but are not supported during the installation." msgstr "" #. Tag: para -#: hardware.xml:2452 +#: hardware.xml:2445 #, no-c-format msgid "If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Use the same procedure as described above for NICs that require firmware." msgstr "" #. Tag: para -#: hardware.xml:2458 +#: hardware.xml:2451 #, no-c-format msgid "In some cases the driver you need may not be available as a Debian package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>" msgstr "" #. Tag: title -#: hardware.xml:2472 +#: hardware.xml:2465 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:2473 +#: hardware.xml:2466 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:2480 +#: hardware.xml:2473 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:2482 +#: hardware.xml:2475 #, no-c-format msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly." msgstr "" #. Tag: para -#: hardware.xml:2492 +#: hardware.xml:2485 #, no-c-format msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>." msgstr "" #. Tag: para -#: hardware.xml:2500 +#: hardware.xml:2493 #, no-c-format msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted." msgstr "" #. Tag: title -#: hardware.xml:2513 +#: hardware.xml:2506 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:2515 +#: hardware.xml:2508 #, no-c-format msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." msgstr "" diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot index 73ee52bc6..83d15464f 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: 2008-09-05 00:09+0000\n" +"POT-Creation-Date: 2008-09-28 00:09+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" @@ -65,227 +65,227 @@ msgstr "" #. Tag: para #: install-methods.xml:90 #, no-c-format -msgid "When downloading files from a Debian mirror, be sure to download the files in <emphasis>binary</emphasis> mode, not text or automatic mode." +msgid "When downloading files from a Debian mirror using FTP, be sure to download the files in <emphasis>binary</emphasis> mode, not text or automatic mode." msgstr "" #. Tag: title -#: install-methods.xml:99 +#: install-methods.xml:98 #, no-c-format msgid "Where to Find Installation Images" msgstr "" #. Tag: para -#: install-methods.xml:101 +#: install-methods.xml:100 #, no-c-format msgid "The installation images are located on each Debian mirror in the directory <ulink url=\"&url-debian-installer;images\">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> — the <ulink url=\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> lists each image and its purpose." msgstr "" #. Tag: title -#: install-methods.xml:113 +#: install-methods.xml:112 #, no-c-format msgid "Alpha Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:114 +#: install-methods.xml:113 #, no-c-format msgid "If you choose to boot from ARC console firmware using <command>MILO</command>, you will also need to prepare a disk containing <command>MILO</command> and <command>LINLOAD.EXE</command> from the provided disk images. See <xref linkend=\"alpha-firmware\"/> for more information on Alpha firmware and boot loaders. The floppy images can be found in the <filename>MILO</filename> directory as <filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>." msgstr "" #. Tag: para -#: install-methods.xml:125 +#: install-methods.xml:124 #, no-c-format msgid "Unfortunately, these <command>MILO</command> images could not be tested and might not work for all subarchitectures. If you find it doesn't work for you, try copying the appropriate <command>MILO</command> binary onto the floppy (<ulink url=\"&disturlftp;main/disks-alpha/current/MILO/\"></ulink>). Note that those <command>MILO</command>s don't support ext2 <quote>sparse superblocks</quote>, so you can't use them to load kernels from newly generated ext2 file systems. As a workaround, you can put your kernel onto the FAT partition next to the <command>MILO</command>." msgstr "" #. Tag: para -#: install-methods.xml:137 +#: install-methods.xml:136 #, no-c-format msgid "<command>MILO</command> binaries are platform-specific. See <xref linkend=\"alpha-cpus\"/> to determine the appropriate <command>MILO</command> image for your Alpha platform." msgstr "" #. Tag: title -#: install-methods.xml:152 +#: install-methods.xml:151 #, no-c-format msgid "Netwinder Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:153 +#: install-methods.xml:152 #, no-c-format msgid "The easiest way to boot a Netwinder is over the network, using the supplied TFTP image &netwinder-boot-img;." msgstr "" #. Tag: title -#: install-methods.xml:162 +#: install-methods.xml:161 #, no-c-format msgid "CATS Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:163 +#: install-methods.xml:162 #, no-c-format msgid "CATS can be booted either via the network or from CD-ROM. The kernel and initrd can be obtained from &cats-boot-img;." msgstr "" #. Tag: title -#: install-methods.xml:172 +#: install-methods.xml:171 #, no-c-format msgid "NSLU2 Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:173 +#: install-methods.xml:172 #, no-c-format msgid "A firmware image is provided for the Linksys NSLU2 which will automatically boot <classname>debian-installer</classname>. This image can be uploaded via the Linksys web frontend or with upslug2. This firmware image can be obtained from &nslu2-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:185 +#: install-methods.xml:184 #, no-c-format msgid "Thecus N2100 Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:186 +#: install-methods.xml:185 #, no-c-format msgid "A firmware image is provided for the Thecus N2100 which will automatically boot <classname>debian-installer</classname>. This image can be installed using the Thecus firmware upgrade process. This firmware image can be obtained from &n2100-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:197 +#: install-methods.xml:196 #, no-c-format msgid "GLAN Tank Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:198 +#: install-methods.xml:197 #, no-c-format msgid "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install Debian. These images can be obtained from &glantank-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:208 +#: install-methods.xml:207 #, no-c-format msgid "Kurobox Pro Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:209 +#: install-methods.xml:208 #, no-c-format msgid "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install Debian. These images can be obtained from &kuroboxpro-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:219 +#: install-methods.xml:218 #, no-c-format msgid "HP mv2120 Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:220 +#: install-methods.xml:219 #, no-c-format msgid "A firmware image is provided for the HP mv2120 which will automatically boot <classname>debian-installer</classname>. This image can be installed with uphpmvault on Linux and other systems and with the HP Media Vault Firmware Recovery Utility on Windows. The firmware image can be obtained from &mv2120-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:232 +#: install-methods.xml:231 #, no-c-format msgid "QNAP Turbo Station Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:233 +#: install-methods.xml:232 #, no-c-format msgid "The QNAP Turbo Station (TS-109, TS-209 and TS-409) requires a kernel and ramdisk which can be obtained from &qnap-firmware-img;. A script is provided to write these images to flash." msgstr "" #. Tag: title -#: install-methods.xml:279 +#: install-methods.xml:278 #, no-c-format msgid "Choosing a Kernel" msgstr "" #. Tag: para -#: install-methods.xml:281 +#: install-methods.xml:280 #, no-c-format msgid "Some m68k subarchs have a choice of kernels to install. In general we recommend trying the most recent version first. If your subarch or machine needs to use a 2.2.x kernel, make sure you choose one of the images that supports 2.2.x kernels (see the <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink>)." msgstr "" #. Tag: para -#: install-methods.xml:290 +#: install-methods.xml:289 #, no-c-format msgid "All of the m68k images for use with 2.2.x kernels, require the kernel parameter &ramdisksize;." msgstr "" #. Tag: title -#: install-methods.xml:308 +#: install-methods.xml:307 #, no-c-format msgid "Creating an IPL tape" msgstr "" #. Tag: para -#: install-methods.xml:310 +#: install-methods.xml:309 #, no-c-format msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>." msgstr "" #. Tag: title -#: install-methods.xml:334 +#: install-methods.xml:333 #, no-c-format msgid "Creating Floppies from Disk Images" msgstr "" #. Tag: para -#: install-methods.xml:335 +#: install-methods.xml:334 #, no-c-format msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means." msgstr "" #. Tag: para -#: install-methods.xml:340 +#: install-methods.xml:339 #, no-c-format msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives." msgstr "" #. Tag: para -#: install-methods.xml:345 +#: install-methods.xml:344 #, no-c-format msgid "Booting the installer from floppy disk is not supported on Amigas or 68k Macs." msgstr "" #. Tag: para -#: install-methods.xml:350 +#: install-methods.xml:349 #, no-c-format msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy." msgstr "" #. Tag: para -#: install-methods.xml:361 +#: install-methods.xml:360 #, no-c-format msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms." msgstr "" #. Tag: para -#: install-methods.xml:367 +#: install-methods.xml:366 #, no-c-format msgid "Before you can create the floppies, you will first need to download them from one of the Debian mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>" msgstr "" #. Tag: para -#: install-methods.xml:375 +#: install-methods.xml:374 #, no-c-format msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally." msgstr "" #. Tag: title -#: install-methods.xml:383 +#: install-methods.xml:382 #, no-c-format msgid "Writing Disk Images From a Linux or Unix System" msgstr "" #. Tag: para -#: install-methods.xml:384 +#: install-methods.xml:383 #, no-c-format msgid "" "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n" @@ -294,253 +294,253 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:405 +#: install-methods.xml:404 #, no-c-format msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>" msgstr "" #. Tag: para -#: install-methods.xml:426 +#: install-methods.xml:425 #, no-c-format msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it." msgstr "" #. Tag: title -#: install-methods.xml:444 +#: install-methods.xml:443 #, no-c-format msgid "Writing Disk Images From DOS, Windows, or OS/2" msgstr "" #. Tag: para -#: install-methods.xml:446 +#: install-methods.xml:445 #, no-c-format msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies." msgstr "" #. Tag: para -#: install-methods.xml:451 +#: install-methods.xml:450 #, no-c-format msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work." msgstr "" #. Tag: para -#: install-methods.xml:459 +#: install-methods.xml:458 #, no-c-format msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory." msgstr "" #. Tag: para -#: install-methods.xml:465 +#: install-methods.xml:464 #, no-c-format msgid "These tools can be found on the Official Debian CD-ROMs under the <filename>/tools</filename> directory." msgstr "" #. Tag: title -#: install-methods.xml:478 +#: install-methods.xml:477 #, no-c-format msgid "Writing Disk Images on Atari Systems" msgstr "" #. Tag: para -#: install-methods.xml:479 +#: install-methods.xml:478 #, no-c-format msgid "You'll find the &rawwrite.ttp; program in the same directory as the floppy disk images. Start the program by double clicking on the program icon, and type in the name of the floppy image file you want written to the floppy at the TOS program command line dialog box." msgstr "" #. Tag: title -#: install-methods.xml:490 +#: install-methods.xml:489 #, no-c-format msgid "Writing Disk Images on Macintosh Systems" msgstr "" #. Tag: para -#: install-methods.xml:491 +#: install-methods.xml:490 #, no-c-format msgid "Since the current release does not yet support booting from floppies to start the installation, there would be no point in doing this on Macintosh Systems. However, these files are needed for the installation of the operating system and modules, later in the process." msgstr "" #. Tag: title -#: install-methods.xml:507 +#: install-methods.xml:506 #, no-c-format msgid "Writing Disk Images From MacOS" msgstr "" #. Tag: para -#: install-methods.xml:508 +#: install-methods.xml:507 #, no-c-format msgid "An AppleScript, <application>Make Debian Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it." msgstr "" #. Tag: para -#: install-methods.xml:519 +#: install-methods.xml:518 #, no-c-format msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities." msgstr "" #. Tag: title -#: install-methods.xml:530 +#: install-methods.xml:529 #, no-c-format msgid "Writing Disk Images with <command>Disk Copy</command>" msgstr "" #. Tag: para -#: install-methods.xml:531 +#: install-methods.xml:530 #, no-c-format msgid "If you are creating the floppy image from files which were originally on the official &debian; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a Debian mirror." msgstr "" #. Tag: para -#: install-methods.xml:540 +#: install-methods.xml:539 #, no-c-format msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file." msgstr "" #. Tag: para -#: install-methods.xml:547 +#: install-methods.xml:546 #, no-c-format msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields." msgstr "" #. Tag: para -#: install-methods.xml:554 +#: install-methods.xml:553 #, no-c-format msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted." msgstr "" #. Tag: para -#: install-methods.xml:563 +#: install-methods.xml:562 #, no-c-format msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>." msgstr "" #. Tag: para -#: install-methods.xml:570 +#: install-methods.xml:569 #, no-c-format msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy." msgstr "" #. Tag: title -#: install-methods.xml:585 +#: install-methods.xml:584 #, no-c-format msgid "Writing Disk Images with <command>suntar</command>" msgstr "" #. Tag: para -#: install-methods.xml:589 +#: install-methods.xml:588 #, no-c-format msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu." msgstr "" #. Tag: para -#: install-methods.xml:597 +#: install-methods.xml:596 #, no-c-format msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)." msgstr "" #. Tag: para -#: install-methods.xml:603 +#: install-methods.xml:602 #, no-c-format msgid "Select the <filename>root.bin</filename> file in the file-opening dialog." msgstr "" #. Tag: para -#: install-methods.xml:608 +#: install-methods.xml:607 #, no-c-format msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another." msgstr "" #. Tag: para -#: install-methods.xml:616 +#: install-methods.xml:615 #, no-c-format msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it." msgstr "" #. Tag: title -#: install-methods.xml:635 +#: install-methods.xml:634 #, no-c-format msgid "Preparing Files for USB Memory Stick Booting" msgstr "" #. Tag: para -#: install-methods.xml:637 +#: install-methods.xml:636 #, no-c-format msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. You should ensure that the usb-storage kernel module is loaded (<userinput>modprobe usb-storage</userinput>) and try to find out which SCSI device the USB stick has been mapped to (in this example <filename>/dev/sda</filename> is used). To write to your stick, you may have to turn off its write protection switch." msgstr "" #. Tag: para -#: install-methods.xml:647 +#: install-methods.xml:646 #, no-c-format msgid "Note that the USB stick should be at least 256 MB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)." msgstr "" #. Tag: title -#: install-methods.xml:655 +#: install-methods.xml:654 #, no-c-format msgid "Copying the files — the easy way" msgstr "" #. Tag: para -#: install-methods.xml:656 +#: install-methods.xml:655 #, no-c-format msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) as well as <command>SYSLINUX</command> and its configuration file. You only have to extract it directly to your USB stick:" msgstr "" #. Tag: screen -#: install-methods.xml:663 +#: install-methods.xml:662 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sda</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:665 +#: install-methods.xml:664 #, no-c-format msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) as well as <command>yaboot</command> and its configuration file. Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:" msgstr "" #. Tag: screen -#: install-methods.xml:674 +#: install-methods.xml:673 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sda2</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:677 +#: install-methods.xml:676 #, no-c-format msgid "Using this method will destroy anything already on the device. Make sure that you use the correct device name for your USB stick." msgstr "" #. Tag: para -#: install-methods.xml:683 +#: install-methods.xml:682 #, no-c-format msgid "After that, mount the USB memory stick (<userinput>mount <replaceable arch=\"x86\">/dev/sda</replaceable> <replaceable arch=\"powerpc\">/dev/sda2</replaceable> /mnt</userinput>), which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a Debian netinst or businesscard ISO image to it (see <xref linkend=\"usb-add-iso\"/>). Unmount the stick (<userinput>umount /mnt</userinput>) and you are done." msgstr "" #. Tag: title -#: install-methods.xml:699 +#: install-methods.xml:698 #, no-c-format msgid "Copying the files — the flexible way" msgstr "" #. Tag: para -#: install-methods.xml:700 +#: install-methods.xml:699 #, no-c-format msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick." msgstr "" #. Tag: title -#: install-methods.xml:712 install-methods.xml:801 +#: install-methods.xml:711 install-methods.xml:800 #, no-c-format msgid "USB stick partitioning on &arch-title;" msgstr "" #. Tag: para -#: install-methods.xml:713 +#: install-methods.xml:712 #, no-c-format msgid "We will show how to setup the memory stick to use the first partition, instead of the entire device." msgstr "" #. Tag: para -#: install-methods.xml:718 +#: install-methods.xml:717 #, no-c-format msgid "" "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition, and then create the filesystem using: <informalexample><screen>\n" @@ -549,13 +549,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:732 +#: install-methods.xml:731 #, no-c-format msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <command>LILO</command>) should work, it's convenient to use <command>SYSLINUX</command>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para -#: install-methods.xml:742 +#: install-methods.xml:741 #, no-c-format msgid "" "To put <command>SYSLINUX</command> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n" @@ -564,19 +564,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:755 +#: install-methods.xml:754 #, no-c-format msgid "Mount the partition (<userinput>mount /dev/sda1 /mnt</userinput>) and copy the following files from the Debian archives to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> <listitem><para> <filename>syslinux.cfg</filename> (SYSLINUX configuration file) </para></listitem> <listitem><para> Optional kernel modules </para></listitem> </itemizedlist> If you want to rename the files, please note that <command>SYSLINUX</command> can only process DOS (8.3) file names." msgstr "" #. Tag: para -#: install-methods.xml:786 +#: install-methods.xml:785 #, no-c-format msgid "The <filename>syslinux.cfg</filename> configuration file should contain the following two lines:" msgstr "" #. Tag: screen -#: install-methods.xml:791 +#: install-methods.xml:790 #, no-c-format msgid "" "default vmlinuz\n" @@ -584,7 +584,7 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:802 +#: install-methods.xml:801 #, no-c-format msgid "" "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/sda</userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n" @@ -593,13 +593,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:818 +#: install-methods.xml:817 #, no-c-format msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para -#: install-methods.xml:827 +#: install-methods.xml:826 #, no-c-format msgid "" "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n" @@ -612,43 +612,43 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:843 +#: install-methods.xml:842 #, no-c-format msgid "Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and copy the following files from the Debian archives to the stick:" msgstr "" #. Tag: para -#: install-methods.xml:849 +#: install-methods.xml:848 #, no-c-format msgid "<filename>vmlinux</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:854 +#: install-methods.xml:853 #, no-c-format msgid "<filename>initrd.gz</filename> (initial ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:859 +#: install-methods.xml:858 #, no-c-format msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" msgstr "" #. Tag: para -#: install-methods.xml:864 +#: install-methods.xml:863 #, no-c-format msgid "<filename>boot.msg</filename> (optional boot message)" msgstr "" #. Tag: para -#: install-methods.xml:869 +#: install-methods.xml:868 #, no-c-format msgid "Optional kernel modules" msgstr "" #. Tag: para -#: install-methods.xml:876 +#: install-methods.xml:875 #, no-c-format msgid "" "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n" @@ -666,283 +666,283 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:893 +#: install-methods.xml:892 #, no-c-format msgid "Adding an ISO image" msgstr "" #. Tag: para -#: install-methods.xml:894 +#: install-methods.xml:893 #, no-c-format msgid "The installer will look for a Debian ISO image on the stick as its source for additional data needed for the installation. So your next step is to copy a Debian ISO image (businesscard, netinst or even a full CD image) onto your stick (be sure to select one that fits). The file name of the image must end in <filename>.iso</filename>." msgstr "" #. Tag: para -#: install-methods.xml:902 +#: install-methods.xml:901 #, no-c-format msgid "If you want to install over the network, without using an ISO image, you will of course skip the previous step. Moreover you will have to use the initial ramdisk from the <filename>netboot</filename> directory instead of the one from <filename>hd-media</filename>, because <filename>hd-media/initrd.gz</filename> does not have network support." msgstr "" #. Tag: para -#: install-methods.xml:911 +#: install-methods.xml:910 #, no-c-format msgid "When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>) and activate its write protection switch." msgstr "" #. Tag: title -#: install-methods.xml:921 +#: install-methods.xml:920 #, no-c-format msgid "Booting the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:922 +#: install-methods.xml:921 #, no-c-format msgid "If your system refuses to boot from the memory stick, the stick may contain an invalid master boot record (MBR). To fix this, use the <command>install-mbr</command> command from the package <classname>mbr</classname>:" msgstr "" #. Tag: screen -#: install-methods.xml:929 +#: install-methods.xml:928 #, no-c-format msgid "# install-mbr /dev/<replaceable>sda</replaceable>" msgstr "" #. Tag: title -#: install-methods.xml:940 +#: install-methods.xml:939 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "" #. Tag: para -#: install-methods.xml:941 +#: install-methods.xml:940 #, no-c-format msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS." msgstr "" #. Tag: para -#: install-methods.xml:947 +#: install-methods.xml:946 #, no-c-format msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks." msgstr "" #. Tag: para -#: install-methods.xml:954 +#: install-methods.xml:953 #, no-c-format msgid "The installer cannot boot from files on an NTFS file system." msgstr "" #. Tag: para -#: install-methods.xml:958 +#: install-methods.xml:957 #, no-c-format msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download." msgstr "" #. Tag: para -#: install-methods.xml:969 +#: install-methods.xml:968 #, no-c-format msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model." msgstr "" #. Tag: title -#: install-methods.xml:978 +#: install-methods.xml:977 #, no-c-format msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: install-methods.xml:980 +#: install-methods.xml:979 #, no-c-format msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>." msgstr "" #. Tag: para -#: install-methods.xml:986 +#: install-methods.xml:985 #, no-c-format msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel." msgstr "" #. Tag: para -#: install-methods.xml:992 +#: install-methods.xml:991 #, no-c-format msgid "Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>." msgstr "" #. Tag: para -#: install-methods.xml:999 +#: install-methods.xml:998 #, no-c-format msgid "<filename>vmlinuz</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:1004 +#: install-methods.xml:1003 #, no-c-format msgid "<filename>initrd.gz</filename> (ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:1011 +#: install-methods.xml:1010 #, no-c-format msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1021 +#: install-methods.xml:1020 #, no-c-format msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1022 +#: install-methods.xml:1021 #, no-c-format msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your Debian installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model." msgstr "" #. Tag: para -#: install-methods.xml:1035 +#: install-methods.xml:1034 #, no-c-format msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on Debian http/ftp mirrors and official Debian CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder." msgstr "" #. Tag: title -#: install-methods.xml:1055 +#: install-methods.xml:1054 #, no-c-format msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1056 +#: install-methods.xml:1055 #, no-c-format msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs." msgstr "" #. Tag: para -#: install-methods.xml:1067 +#: install-methods.xml:1066 #, no-c-format msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the Debian archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)." msgstr "" #. Tag: filename -#: install-methods.xml:1077 install-methods.xml:1434 +#: install-methods.xml:1076 install-methods.xml:1433 #, no-c-format msgid "vmlinux" msgstr "" #. Tag: filename -#: install-methods.xml:1082 install-methods.xml:1439 +#: install-methods.xml:1081 install-methods.xml:1438 #, no-c-format msgid "initrd.gz" msgstr "" #. Tag: filename -#: install-methods.xml:1087 install-methods.xml:1444 +#: install-methods.xml:1086 install-methods.xml:1443 #, no-c-format msgid "yaboot" msgstr "" #. Tag: filename -#: install-methods.xml:1092 install-methods.xml:1449 +#: install-methods.xml:1091 install-methods.xml:1448 #, no-c-format msgid "yaboot.conf" msgstr "" #. Tag: para -#: install-methods.xml:1097 +#: install-methods.xml:1096 #, no-c-format msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer." msgstr "" #. Tag: para -#: install-methods.xml:1105 +#: install-methods.xml:1104 #, no-c-format msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1118 +#: install-methods.xml:1117 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "" #. Tag: para -#: install-methods.xml:1119 +#: install-methods.xml:1118 #, no-c-format msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine." msgstr "" #. Tag: para -#: install-methods.xml:1127 +#: install-methods.xml:1126 #, no-c-format msgid "You need to setup a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>." msgstr "" #. Tag: para -#: install-methods.xml:1134 +#: install-methods.xml:1133 #, no-c-format msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> <phrase arch=\"m68k\">Yet another alternative exists on VMEbus systems: the IP address can be manually configured in boot ROM.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP." msgstr "" #. Tag: para -#: install-methods.xml:1151 +#: install-methods.xml:1150 #, no-c-format msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP." msgstr "" #. Tag: para -#: install-methods.xml:1157 +#: install-methods.xml:1156 #, no-c-format msgid "Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM console will <emphasis>not</emphasis> use RARP to obtain its IP address, and therefore you must use BOOTP for net booting your Alpha<footnote> <para> Alpha systems can also be net-booted using the DECNet MOP (Maintenance Operations Protocol), but this is not covered here. Presumably, your local OpenVMS operator will be happy to assist you should you have some burning need to use MOP to boot Linux on your Alpha. </para> </footnote>. You can also enter the IP configuration for network interfaces directly in the SRM console." msgstr "" #. Tag: para -#: install-methods.xml:1174 +#: install-methods.xml:1173 #, no-c-format msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in Debian." msgstr "" #. Tag: para -#: install-methods.xml:1179 +#: install-methods.xml:1178 #, no-c-format msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux." msgstr "" #. Tag: para -#: install-methods.xml:1187 +#: install-methods.xml:1186 #, no-c-format msgid "To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> support. On a &debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</classname> packages qualify; we recommend <classname>tftpd-hpa</classname>." msgstr "" #. Tag: title -#: install-methods.xml:1205 +#: install-methods.xml:1204 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para -#: install-methods.xml:1206 +#: install-methods.xml:1205 #, no-c-format 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:1218 +#: install-methods.xml:1217 #, no-c-format 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:1240 +#: install-methods.xml:1239 #, no-c-format msgid "Setting up a BOOTP server" msgstr "" #. Tag: para -#: install-methods.xml:1241 +#: install-methods.xml:1240 #, 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>dhcp3-server</classname> packages respectively." msgstr "" #. Tag: para -#: install-methods.xml:1249 +#: install-methods.xml:1248 #, 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" @@ -959,25 +959,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1282 +#: install-methods.xml:1281 #, 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\"/>. In that case, 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/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1303 +#: install-methods.xml:1302 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1304 +#: install-methods.xml:1303 #, no-c-format msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):" msgstr "" #. Tag: screen -#: install-methods.xml:1311 +#: install-methods.xml:1310 #, no-c-format msgid "" "option domain-name \"example.com\";\n" @@ -1002,25 +1002,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1313 +#: install-methods.xml:1312 #, 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:1323 +#: install-methods.xml:1322 #, no-c-format msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1331 +#: install-methods.xml:1330 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1332 +#: install-methods.xml:1331 #, 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" @@ -1055,13 +1055,13 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1348 +#: install-methods.xml:1347 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1349 +#: install-methods.xml:1348 #, 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" @@ -1070,19 +1070,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1361 +#: install-methods.xml:1360 #, no-c-format msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/var/lib/tftpboot</filename>. You may have to adjust the configuration examples in this section accordingly." msgstr "" #. Tag: para -#: install-methods.xml:1371 +#: install-methods.xml:1370 #, no-c-format msgid "Look in <filename>/etc/inetd.conf</filename> and remember the directory which is used as the argument of <command>in.tftpd</command><footnote> <para> All <command>in.tftpd</command> alternatives available in Debian should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors. </para> </footnote>; you'll need that below. 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:1391 +#: install-methods.xml:1390 #, 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" @@ -1093,61 +1093,61 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1413 +#: install-methods.xml:1412 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1414 +#: install-methods.xml:1413 #, 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. You may 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:1423 +#: install-methods.xml:1422 #, 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. You will need to download the following files from the <filename>netboot/</filename> directory:" msgstr "" #. Tag: filename -#: install-methods.xml:1454 +#: install-methods.xml:1453 #, no-c-format msgid "boot.msg" msgstr "" #. Tag: para -#: install-methods.xml:1459 +#: install-methods.xml:1458 #, 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:1467 +#: install-methods.xml:1466 #, 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:1479 +#: install-methods.xml:1478 #, no-c-format msgid "Alpha TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1480 +#: install-methods.xml:1479 #, 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:1495 +#: install-methods.xml:1494 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1496 +#: install-methods.xml:1495 #, 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" @@ -1156,85 +1156,85 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1512 +#: install-methods.xml:1511 #, no-c-format msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested." msgstr "" #. Tag: para -#: install-methods.xml:1519 +#: install-methods.xml:1518 #, 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:1530 +#: install-methods.xml:1529 #, no-c-format msgid "BVM/Motorola TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1531 +#: install-methods.xml:1530 #, 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:1536 +#: install-methods.xml:1535 #, 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:1548 +#: install-methods.xml:1547 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1549 +#: install-methods.xml:1548 #, 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:1561 +#: install-methods.xml:1560 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1562 +#: install-methods.xml:1561 #, 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:1667 +#: install-methods.xml:1666 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1668 +#: install-methods.xml:1667 #, 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:1681 +#: install-methods.xml:1680 #, no-c-format msgid "Automatic Installation Using the Debian Installer" msgstr "" #. Tag: para -#: install-methods.xml:1682 +#: install-methods.xml:1681 #, 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:1689 +#: install-methods.xml:1688 #, 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/installation-howto.pot b/po/pot/installation-howto.pot index 6965a68ce..219f609f6 100644 --- a/po/pot/installation-howto.pot +++ b/po/pot/installation-howto.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: 2007-12-31 01:09+0000\n" +"POT-Creation-Date: 2008-09-28 00:09+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" @@ -227,7 +227,7 @@ msgstr "" #. Tag: para #: installation-howto.xml:248 #, no-c-format -msgid "Now it is time to partition your disks. First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive (guided partitioning). This is recommended for new users or anyone in a hurry. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu." +msgid "Now it is time to partition your disks. First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive (see <xref linkend=\"partman-auto\"/>). This is recommended for new users or anyone in a hurry. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu." msgstr "" #. Tag: para @@ -239,71 +239,71 @@ msgstr "" #. Tag: para #: installation-howto.xml:263 #, no-c-format -msgid "On the next screen you will see your partition table, how the partitions will be formatted, and where they will be mounted. Select a partition to modify or delete it. If you did automatic partitioning, you should just be able to choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to use what it set up. Remember to assign at least one partition for swap space and to mount a partition on <filename>/</filename>. <xref linkend=\"partitioning\"/> has more information about partitioning." +msgid "On the next screen you will see your partition table, how the partitions will be formatted, and where they will be mounted. Select a partition to modify or delete it. If you did automatic partitioning, you should just be able to choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to use what it set up. Remember to assign at least one partition for swap space and to mount a partition on <filename>/</filename>. For more detailed information on how to use the partitioner, please refer to <xref linkend=\"di-partition\"/>; the appendix <xref linkend=\"partitioning\"/> has more general information about partitioning." msgstr "" #. Tag: para -#: installation-howto.xml:273 +#: installation-howto.xml:276 #, no-c-format msgid "Now &d-i; formats your partitions and starts to install the base system, which can take a while. That is followed by installing a kernel." msgstr "" #. Tag: para -#: installation-howto.xml:278 +#: installation-howto.xml:281 #, no-c-format msgid "The base system that was installed earlier is a working, but very minimal installation. To make the system more functional the next step allows you to install additional packages by selecting tasks. Before packages can be installed <classname>apt</classname> needs to be configured as that defines from where the packages will be retrieved. The <quote>Standard system</quote> task will be selected by default and should normally be installed. Select the <quote>Desktop environment</quote> task if you would like to have a graphical desktop after the installation. See <xref linkend=\"pkgsel\"/> for additional information about this step." msgstr "" #. Tag: para -#: installation-howto.xml:290 +#: installation-howto.xml:293 #, no-c-format -msgid "Partitioning is followed by setting up user accounts. By default you will need to provide a password for the <quote>root</quote> (administrator) account and information necessary to create one regular user account." +msgid "Installation of the base system is followed by setting up user accounts. By default you will need to provide a password for the <quote>root</quote> (administrator) account and information necessary to create one regular user account." msgstr "" #. Tag: para -#: installation-howto.xml:296 +#: installation-howto.xml:300 #, no-c-format msgid "The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. <phrase arch=\"x86\">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase>" msgstr "" #. Tag: para -#: installation-howto.xml:306 +#: installation-howto.xml:310 #, no-c-format msgid "&d-i; will now tell you that the installation has finished. Remove the cdrom or other boot media and hit &enterkey; to reboot your machine. It should boot up into the newly installed system and allow you to log in. This is explained in <xref linkend=\"boot-new\"/>." msgstr "" #. Tag: para -#: installation-howto.xml:313 +#: installation-howto.xml:317 #, no-c-format msgid "If you need more information on the install process, see <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: title -#: installation-howto.xml:322 +#: installation-howto.xml:326 #, no-c-format msgid "Send us an installation report" msgstr "" #. Tag: para -#: installation-howto.xml:323 +#: installation-howto.xml:327 #, no-c-format msgid "If you successfully managed an installation with &d-i;, please take time to provide us with a report. The simplest way to do so is to install the reportbug package (<command>aptitude install reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run <command>reportbug installation-reports</command>." msgstr "" #. Tag: para -#: installation-howto.xml:333 +#: installation-howto.xml:337 #, no-c-format msgid "If you did not complete the install, you probably found a bug in debian-installer. To improve the installer it is necessary that we know about them, so please take the time to report them. You can use an installation report to report problems; if the install completely fails, see <xref linkend=\"problem-report\"/>." msgstr "" #. Tag: title -#: installation-howto.xml:345 +#: installation-howto.xml:349 #, no-c-format msgid "And finally…" msgstr "" #. Tag: para -#: installation-howto.xml:346 +#: installation-howto.xml:350 #, no-c-format msgid "We hope that your Debian installation is pleasant and that you find Debian useful. You might want to read <xref linkend=\"post-install\"/>." msgstr "" diff --git a/po/pot/partitioning.pot b/po/pot/partitioning.pot index f740f293d..b791cbef9 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: 2007-08-06 18:17+0000\n" +"POT-Creation-Date: 2008-09-28 00:09+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" @@ -437,329 +437,317 @@ msgstr "" #. Tag: para #: partitioning.xml:372 #, no-c-format -msgid "The first XT disk is named <filename>/dev/xda</filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:377 -#, no-c-format -msgid "The second XT disk is named <filename>/dev/xdb</filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:382 -#, no-c-format msgid "The first ACSI device is named <filename>/dev/ada</filename>, the second is named <filename>/dev/adb</filename>." msgstr "" #. Tag: para -#: partitioning.xml:391 +#: partitioning.xml:381 #, no-c-format msgid "The first DASD device is named <filename>/dev/dasda</filename>." msgstr "" #. Tag: para -#: partitioning.xml:397 +#: partitioning.xml:387 #, no-c-format msgid "The second DASD device is named <filename>/dev/dasdb</filename>, and so on." msgstr "" #. Tag: para -#: partitioning.xml:405 +#: partitioning.xml:395 #, no-c-format msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>sda1</filename> and <filename>sda2</filename> represent the first and second partitions of the first SCSI disk drive in your system." msgstr "" #. Tag: para -#: partitioning.xml:412 +#: partitioning.xml:402 #, no-c-format msgid "Here is a real-life example. Let's assume you have a system with 2 SCSI disks, one at SCSI address 2 and the other at SCSI address 4. The first disk (at address 2) is then named <filename>sda</filename>, and the second <filename>sdb</filename>. If the <filename>sda</filename> drive has 3 partitions on it, these will be named <filename>sda1</filename>, <filename>sda2</filename>, and <filename>sda3</filename>. The same applies to the <filename>sdb</filename> disk and its partitions." msgstr "" #. Tag: para -#: partitioning.xml:423 +#: partitioning.xml:413 #, no-c-format msgid "Note that if you have two SCSI host bus adapters (i.e., controllers), the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities." msgstr "" #. Tag: para -#: partitioning.xml:430 +#: partitioning.xml:420 #, no-c-format msgid "Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are numbered starting at 5, so the first logical partition on that same drive is <filename>/dev/hda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. This applies to SCSI disks as well as IDE disks." msgstr "" #. Tag: para -#: partitioning.xml:441 +#: partitioning.xml:431 #, no-c-format msgid "VMEbus systems using the TEAC FC-1 SCSI floppy drive will see it as normal SCSI disk. To make identification of the drive simpler the installation software will create a symbolic link to the appropriate device and name it <filename>/dev/sfd0</filename>." msgstr "" #. Tag: para -#: partitioning.xml:448 +#: partitioning.xml:438 #, no-c-format msgid "Sun disk partitions allow for 8 separate partitions (or slices). The third partition is usually (and is preferred to have) the <quote>Whole Disk</quote> partition. This partition references all of the sectors of the disk, and is used by the boot loader (either SILO, or Sun's)." msgstr "" #. Tag: para -#: partitioning.xml:455 +#: partitioning.xml:445 #, no-c-format msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> represent the first and second partitions of the first DASD device in your system." msgstr "" #. Tag: title -#: partitioning.xml:470 +#: partitioning.xml:460 #, no-c-format msgid "Debian Partitioning Programs" msgstr "" #. Tag: para -#: partitioning.xml:471 +#: partitioning.xml:461 #, no-c-format msgid "Several varieties of partitioning programs have been adapted by Debian developers to work on various types of hard disks and computer architectures. Following is a list of the program(s) applicable for your architecture." msgstr "" #. Tag: command -#: partitioning.xml:483 +#: partitioning.xml:473 #, no-c-format msgid "partman" msgstr "" #. Tag: para -#: partitioning.xml:484 +#: partitioning.xml:474 #, no-c-format msgid "Recommended partitioning tool in Debian. This Swiss army knife can also resize partitions, create filesystems <phrase arch=\"x86\"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints." msgstr "" #. Tag: command -#: partitioning.xml:495 +#: partitioning.xml:485 #, no-c-format msgid "fdisk" msgstr "" #. Tag: para -#: partitioning.xml:496 +#: partitioning.xml:486 #, no-c-format msgid "The original Linux disk partitioner, good for gurus." msgstr "" #. Tag: para -#: partitioning.xml:500 +#: partitioning.xml:490 #, no-c-format msgid "Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that <command>fdisk</command> represents them (or not) can make the device names differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</ulink>." msgstr "" #. Tag: command -#: partitioning.xml:512 +#: partitioning.xml:502 #, no-c-format msgid "cfdisk" msgstr "" #. Tag: para -#: partitioning.xml:513 +#: partitioning.xml:503 #, no-c-format msgid "A simple-to-use, full-screen disk partitioner for the rest of us." msgstr "" #. Tag: para -#: partitioning.xml:517 +#: partitioning.xml:507 #, no-c-format msgid "Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result." msgstr "" #. Tag: command -#: partitioning.xml:526 +#: partitioning.xml:516 #, no-c-format msgid "atari-fdisk" msgstr "" #. Tag: para -#: partitioning.xml:527 +#: partitioning.xml:517 #, no-c-format msgid "Atari-aware version of <command>fdisk</command>." msgstr "" #. Tag: command -#: partitioning.xml:535 +#: partitioning.xml:525 #, no-c-format msgid "amiga-fdisk" msgstr "" #. Tag: para -#: partitioning.xml:536 +#: partitioning.xml:526 #, no-c-format msgid "Amiga-aware version of <command>fdisk</command>." msgstr "" #. Tag: command -#: partitioning.xml:544 +#: partitioning.xml:534 #, no-c-format msgid "mac-fdisk" msgstr "" #. Tag: para -#: partitioning.xml:545 +#: partitioning.xml:535 #, no-c-format msgid "Mac-aware version of <command>fdisk</command>." msgstr "" #. Tag: command -#: partitioning.xml:553 +#: partitioning.xml:543 #, no-c-format msgid "pmac-fdisk" msgstr "" #. Tag: para -#: partitioning.xml:554 +#: partitioning.xml:544 #, no-c-format msgid "PowerMac-aware version of <command>fdisk</command>, also used by BVM and Motorola VMEbus systems." msgstr "" #. Tag: command -#: partitioning.xml:563 +#: partitioning.xml:553 #, no-c-format msgid "fdasd" msgstr "" #. Tag: para -#: partitioning.xml:564 +#: partitioning.xml:554 #, no-c-format msgid "&arch-title; version of <command>fdisk</command>; Please read the fdasd manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and Installation Commands</ulink> for details." msgstr "" #. Tag: para -#: partitioning.xml:575 +#: partitioning.xml:565 #, no-c-format msgid "One of these programs will be run by default when you select <guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible to use a different partitioning tool from the command line on VT2, but this is not recommended." msgstr "" #. Tag: para -#: partitioning.xml:582 +#: partitioning.xml:572 #, no-c-format msgid "Remember to mark your boot partition as <quote>Bootable</quote>." msgstr "" #. Tag: para -#: partitioning.xml:585 +#: partitioning.xml:575 #, no-c-format msgid "One key point when partitioning for Mac type disks is that the swap partition is identified by its name; it must be named <quote>swap</quote>. All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you should take if you are sharing your disk with MacOS." msgstr "" #. Tag: title -#: partitioning.xml:601 partitioning.xml:662 partitioning.xml:686 partitioning.xml:783 partitioning.xml:897 partitioning.xml:974 +#: partitioning.xml:591 partitioning.xml:652 partitioning.xml:676 partitioning.xml:773 partitioning.xml:887 partitioning.xml:964 #, no-c-format msgid "Partitioning for &arch-title;" msgstr "" #. Tag: para -#: partitioning.xml:602 +#: partitioning.xml:592 #, no-c-format msgid "Booting Debian from the SRM console (the only disk boot method supported by &releasename;) requires you to have a BSD disk label, not a DOS partition table, on your boot disk. (Remember, the SRM boot block is incompatible with MS-DOS partition tables — see <xref linkend=\"alpha-firmware\"/>.) As a result, <command>partman</command> creates BSD disk labels when running on &architecture;, but if your disk has an existing DOS partition table the existing partitions will need to be deleted before <command>partman</command> can convert it to use a disk label." msgstr "" #. Tag: para -#: partitioning.xml:613 +#: partitioning.xml:603 #, no-c-format msgid "If you have chosen to use <command>fdisk</command> to partition your disk, and the disk that you have selected for partitioning does not already contain a BSD disk label, you must use the <quote>b</quote> command to enter disk label mode." msgstr "" #. Tag: para -#: partitioning.xml:620 +#: partitioning.xml:610 #, 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), 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:632 +#: partitioning.xml:622 #, 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:644 +#: partitioning.xml:634 #, 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:663 +#: partitioning.xml:653 #, 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:687 +#: partitioning.xml:677 #, 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>Manual</guimenuitem> and then simply select an existing partition and change its size." msgstr "" #. Tag: para -#: partitioning.xml:697 +#: partitioning.xml:687 #, 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:708 +#: partitioning.xml:698 #, 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:719 +#: partitioning.xml:709 #, 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:729 +#: partitioning.xml:719 #, 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:737 +#: partitioning.xml:727 #, 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:751 +#: partitioning.xml:741 #, 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:763 +#: partitioning.xml:753 #, 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:784 +#: partitioning.xml:774 #, 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:796 +#: partitioning.xml:786 #, no-c-format msgid "EFI Recognized Formats" msgstr "" #. Tag: para -#: partitioning.xml:797 +#: partitioning.xml:787 #, no-c-format msgid "The IA-64 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 IA-64 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:809 +#: partitioning.xml:799 #, 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:817 +#: partitioning.xml:807 #, 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" @@ -774,97 +762,97 @@ msgid "" msgstr "" #. Tag: title -#: partitioning.xml:842 +#: partitioning.xml:832 #, no-c-format msgid "Boot Loader Partition Requirements" msgstr "" #. Tag: para -#: partitioning.xml:843 +#: partitioning.xml:833 #, no-c-format msgid "ELILO, the IA-64 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:852 +#: partitioning.xml:842 #, 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:867 +#: partitioning.xml:857 #, 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:875 +#: partitioning.xml:865 #, no-c-format msgid "EFI Diagnostic Partitions" msgstr "" #. Tag: para -#: partitioning.xml:876 +#: partitioning.xml:866 #, 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:898 +#: partitioning.xml:888 #, 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:915 +#: partitioning.xml:905 #, no-c-format msgid "Partitioning Newer PowerMacs" msgstr "" #. Tag: para -#: partitioning.xml:916 +#: partitioning.xml:906 #, 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 have at least 819200 bytes 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:929 +#: partitioning.xml:919 #, 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:936 +#: partitioning.xml:926 #, 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:946 +#: partitioning.xml:936 #, 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:958 +#: partitioning.xml:948 #, 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:975 +#: partitioning.xml:965 #, 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:983 +#: partitioning.xml:973 #, 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:994 +#: partitioning.xml:984 #, 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/preparing.pot b/po/pot/preparing.pot index db94c2d6e..d40431dd2 100644 --- a/po/pot/preparing.pot +++ b/po/pot/preparing.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2008-07-14 00:09+0000\n" +"POT-Creation-Date: 2008-09-28 00:09+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" @@ -425,7 +425,7 @@ msgstr "" #. Tag: entry #: preparing.xml:457 #, no-c-format -msgid "Whether IDE or SCSI (most computers are IDE)." +msgid "Whether IDE (also known as PATA), SATA or SCSI." msgstr "" #. Tag: entry diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot index 5548831af..aca02e3fd 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: 2008-09-26 00:09+0000\n" +"POT-Creation-Date: 2008-09-28 00:09+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" @@ -718,7 +718,7 @@ msgstr "" #. Tag: para #: preseed.xml:693 #, no-c-format -msgid "Keyboard configuration consists of selecting a keyboard architecture and a keymap. In most cases the correct keyboard architecture is selected by default, so there's normally no need to preseed it. The keymap must be valid for the selected keyboard architecture." +msgid "Keyboard configuration consists of selecting a keyboard architecture and a keymap. In most cases the correct keyboard architecture is selected by default, so there's normally no need to preseed it. The keymap must be known to the &d-i; for the selected keyboard architecture." msgstr "" #. Tag: screen @@ -939,6 +939,8 @@ msgid "" "# contains an old LVM configuration, the user will normally receive a\n" "# warning. This can be preseeded away...\n" "d-i partman-lvm/device_remove_lvm boolean true\n" + "# The same applies to pre-existing software RAID array:\n" + "d-i parman-md/device_remove_md boolean true\n" "# And the same goes for the confirmation to write the lvm partitions.\n" "d-i partman-lvm/confirm boolean true\n" "\n" diff --git a/po/pot/random-bits.pot b/po/pot/random-bits.pot index 126fdded5..32ceb8089 100644 --- a/po/pot/random-bits.pot +++ b/po/pot/random-bits.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2008-09-07 00:09+0000\n" +"POT-Creation-Date: 2008-09-28 00:09+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" @@ -1504,36 +1504,12 @@ msgstr "" #. Tag: para #: random-bits.xml:1256 #, no-c-format -msgid "Information on some screens is not yet nicely formatted into columns as it should be. This is most visible during partitioning." +msgid "Information on some screens is not yet nicely formatted into columns as it should be." msgstr "" #. Tag: para #: random-bits.xml:1262 #, no-c-format -msgid "Typing some characters may not work and in some cases the wrong character may be printed. For example, \"composing\" a character by typing an accent and then the letter over/under which the accent should appear does not work." -msgstr "" - -#. Tag: para -#: random-bits.xml:1269 -#, no-c-format msgid "Support for touchpads is not yet optimal." msgstr "" -#. Tag: para -#: random-bits.xml:1274 -#, no-c-format -msgid "Starting a shell from the graphical frontend is currently not supported. This means that relevant options to do that (which are available when you use the textual frontend), will not be shown in the main menu of the installation system and in the menu for the rescue mode. You will instead have to switch (as described above) to the shells that are available on virtual consoles VT2 and VT3." -msgstr "" - -#. Tag: para -#: random-bits.xml:1283 -#, no-c-format -msgid "After booting the installer in rescue mode, it may be useful to start a shell in the root partition of an already installed system. This is possible (after you have selected the partition to be mounted as the root partition) by switching to VT2 or VT3 and entering the following command:" -msgstr "" - -#. Tag: screen -#: random-bits.xml:1290 -#, no-c-format -msgid "# chroot /target" -msgstr "" - diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index 6adfabf8a..e4ec37ae4 100644 --- a/po/pot/using-d-i.pot +++ b/po/pot/using-d-i.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2008-09-26 00:09+0000\n" +"POT-Creation-Date: 2008-09-28 00:09+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" @@ -65,635 +65,647 @@ msgstr "" #. Tag: para #: using-d-i.xml:59 #, no-c-format -msgid "The normal installer display is character-based (as opposed to the now more familiar graphical interface). The mouse is not operational in this environment. Here are the keys you can use to navigate within the various dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move <quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> <keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move <quote>backward</quote> between displayed buttons and selections. The <keycap>up</keycap> and <keycap>down</keycap> arrow select different items within a scrollable list, and also scroll the list itself. In addition, in long lists, you can type a letter to cause the list to scroll directly to the section with items starting with the letter you typed and use <keycap>Pg-Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The <keycap>space bar</keycap> selects an item such as a checkbox. Use &enterkey; to activate choices." +msgid "For this architecture the &d-i; supports two different user interfaces: a character-based one and a graphical one. The character-based interface is used by default unless you selected the <quote>Graphical install</quote> option in the initial boot menu. For more information about the graphical installer, please refer to <xref linkend=\"graphical\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:77 +#: using-d-i.xml:67 +#, no-c-format +msgid "For this architecture the installer uses a character-based user interface. A graphical user interface is currently not available." +msgstr "" + +#. Tag: para +#: using-d-i.xml:72 +#, no-c-format +msgid "In the character-based environment the use of a mouse is not supported. Here are the keys you can use to navigate within the various dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move <quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> <keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move <quote>backward</quote> between displayed buttons and selections. The <keycap>up</keycap> and <keycap>down</keycap> arrow select different items within a scrollable list, and also scroll the list itself. In addition, in long lists, you can type a letter to cause the list to scroll directly to the section with items starting with the letter you typed and use <keycap>Pg-Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The <keycap>space bar</keycap> selects an item such as a checkbox. Use &enterkey; to activate choices." +msgstr "" + +#. Tag: para +#: using-d-i.xml:89 #, no-c-format msgid "S/390 does not support virtual consoles. You may open a second and third ssh session to view the logs described below." msgstr "" #. Tag: para -#: using-d-i.xml:82 +#: using-d-i.xml:94 #, no-c-format msgid "Error messages and logs are redirected to the fourth console. You can access this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing the <keycap>F4</keycap> function key); get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>." msgstr "" #. Tag: para -#: using-d-i.xml:92 +#: using-d-i.xml:104 #, no-c-format msgid "These messages can also be found in <filename>/var/log/syslog</filename>. After installation, this log is copied to <filename>/var/log/installer/syslog</filename> on your new system. Other installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system." msgstr "" #. Tag: title -#: using-d-i.xml:106 +#: using-d-i.xml:118 #, no-c-format msgid "Components Introduction" msgstr "" #. Tag: para -#: using-d-i.xml:107 +#: using-d-i.xml:119 #, no-c-format msgid "Here is a list of installer components with a brief description of each component's purpose. Details you might need to know about using a particular component are in <xref linkend=\"module-details\"/>." msgstr "" #. Tag: term -#: using-d-i.xml:118 +#: using-d-i.xml:130 #, no-c-format msgid "main-menu" msgstr "" #. Tag: para -#: using-d-i.xml:118 +#: using-d-i.xml:130 #, no-c-format msgid "Shows the list of components to the user during installer operation, and starts a component when it is selected. Main-menu's questions are set to priority medium, so if your priority is set to high or critical (high is the default), you will not see the menu. On the other hand, if there is an error which requires your intervention, the question priority may be downgraded temporarily to allow you to resolve the problem, and in that case the menu may appear." msgstr "" #. Tag: para -#: using-d-i.xml:128 +#: using-d-i.xml:140 #, no-c-format msgid "You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly to back all the way out of the currently running component." msgstr "" #. Tag: term -#: using-d-i.xml:137 +#: using-d-i.xml:149 #, no-c-format msgid "localechooser" msgstr "" #. Tag: para -#: using-d-i.xml:137 +#: using-d-i.xml:149 #, no-c-format msgid "Allows the user to select localization options for the installation and the installed system: language, country and locales. The installer will display messages in the selected language, unless the translation for that language is not complete in which case some messages may be shown in English." msgstr "" #. Tag: term -#: using-d-i.xml:149 +#: using-d-i.xml:161 #, no-c-format msgid "kbd-chooser" msgstr "" #. Tag: para -#: using-d-i.xml:149 +#: using-d-i.xml:161 #, no-c-format msgid "Shows a list of keyboards, from which the user chooses the model which matches his own." msgstr "" #. Tag: term -#: using-d-i.xml:158 +#: using-d-i.xml:170 #, no-c-format msgid "hw-detect" msgstr "" #. Tag: para -#: using-d-i.xml:158 +#: using-d-i.xml:170 #, no-c-format msgid "Automatically detects most of the system's hardware, including network cards, disk drives, and PCMCIA." msgstr "" #. Tag: term -#: using-d-i.xml:167 +#: using-d-i.xml:179 #, no-c-format msgid "cdrom-detect" msgstr "" #. Tag: para -#: using-d-i.xml:167 +#: using-d-i.xml:179 #, no-c-format msgid "Looks for and mounts a Debian installation CD." msgstr "" #. Tag: term -#: using-d-i.xml:175 +#: using-d-i.xml:187 #, no-c-format msgid "netcfg" msgstr "" #. Tag: para -#: using-d-i.xml:175 +#: using-d-i.xml:187 #, no-c-format msgid "Configures the computer's network connections so it can communicate over the internet." msgstr "" #. Tag: term -#: using-d-i.xml:184 +#: using-d-i.xml:196 #, no-c-format msgid "iso-scan" msgstr "" #. Tag: para -#: using-d-i.xml:184 +#: using-d-i.xml:196 #, no-c-format msgid "Looks for ISO file systems, which may be on a CD-ROM or on the hard drive." msgstr "" #. Tag: term -#: using-d-i.xml:193 +#: using-d-i.xml:205 #, no-c-format msgid "choose-mirror" msgstr "" #. Tag: para -#: using-d-i.xml:193 +#: using-d-i.xml:205 #, no-c-format msgid "Presents a list of Debian archive mirrors. The user may choose the source of his installation packages." msgstr "" #. Tag: term -#: using-d-i.xml:202 +#: using-d-i.xml:214 #, no-c-format msgid "cdrom-checker" msgstr "" #. Tag: para -#: using-d-i.xml:202 +#: using-d-i.xml:214 #, no-c-format msgid "Checks integrity of a CD-ROM. This way, the user may assure him/herself that the installation CD-ROM was not corrupted." msgstr "" #. Tag: term -#: using-d-i.xml:211 +#: using-d-i.xml:223 #, no-c-format msgid "lowmem" msgstr "" #. Tag: para -#: using-d-i.xml:211 +#: using-d-i.xml:223 #, no-c-format msgid "Lowmem tries to detect systems with low memory and then does various tricks to remove unnecessary parts of &d-i; from the memory (at the cost of some features)." msgstr "" #. Tag: term -#: using-d-i.xml:221 +#: using-d-i.xml:233 #, no-c-format msgid "anna" msgstr "" #. Tag: para -#: using-d-i.xml:221 +#: using-d-i.xml:233 #, no-c-format msgid "Anna's Not Nearly APT. Installs packages which have been retrieved from the chosen mirror or CD." msgstr "" #. Tag: term -#: using-d-i.xml:230 +#: using-d-i.xml:242 #, no-c-format msgid "clock-setup" msgstr "" #. Tag: para -#: using-d-i.xml:230 +#: using-d-i.xml:242 #, no-c-format msgid "Updates the system clock and determines whether the clock is set to UTC or not." msgstr "" #. Tag: term -#: using-d-i.xml:239 +#: using-d-i.xml:251 #, no-c-format msgid "tzsetup" msgstr "" #. Tag: para -#: using-d-i.xml:239 +#: using-d-i.xml:251 #, no-c-format msgid "Selects the time zone, based on the location selected earlier." msgstr "" #. Tag: term -#: using-d-i.xml:247 +#: using-d-i.xml:259 #, no-c-format msgid "partman" msgstr "" #. Tag: para -#: using-d-i.xml:247 +#: using-d-i.xml:259 #, no-c-format msgid "Allows the user to partition disks attached to the system, create file systems on the selected partitions, and attach them to the mountpoints. Included are also interesting features like a fully automatic mode or LVM support. This is the preferred partitioning tool in Debian." msgstr "" #. Tag: term -#: using-d-i.xml:259 +#: using-d-i.xml:271 #, no-c-format msgid "partitioner" msgstr "" #. Tag: para -#: using-d-i.xml:259 +#: using-d-i.xml:271 #, no-c-format msgid "Allows the user to partition disks attached to the system. A partitioning program appropriate to your computer's architecture is chosen." msgstr "" #. Tag: term -#: using-d-i.xml:269 +#: using-d-i.xml:281 #, no-c-format msgid "partconf" msgstr "" #. Tag: para -#: using-d-i.xml:269 +#: using-d-i.xml:281 #, no-c-format msgid "Displays a list of partitions, and creates file systems on the selected partitions according to user instructions." msgstr "" #. Tag: term -#: using-d-i.xml:278 +#: using-d-i.xml:290 #, no-c-format msgid "lvmcfg" msgstr "" #. Tag: para -#: using-d-i.xml:278 +#: using-d-i.xml:290 #, no-c-format msgid "Helps the user with the configuration of the <firstterm>LVM</firstterm> (Logical Volume Manager)." msgstr "" #. Tag: term -#: using-d-i.xml:287 +#: using-d-i.xml:299 #, no-c-format msgid "mdcfg" msgstr "" #. Tag: para -#: using-d-i.xml:287 +#: using-d-i.xml:299 #, no-c-format msgid "Allows the user to setup Software <firstterm>RAID</firstterm> (Redundant Array of Inexpensive Disks). This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards." msgstr "" #. Tag: term -#: using-d-i.xml:298 +#: using-d-i.xml:310 #, no-c-format msgid "base-installer" msgstr "" #. Tag: para -#: using-d-i.xml:298 +#: using-d-i.xml:310 #, no-c-format msgid "Installs the most basic set of packages which would allow the computer to operate under Linux when rebooted." msgstr "" #. Tag: term -#: using-d-i.xml:307 +#: using-d-i.xml:319 #, no-c-format msgid "user-setup" msgstr "" #. Tag: para -#: using-d-i.xml:307 +#: using-d-i.xml:319 #, no-c-format msgid "Sets up the root password, and adds a non-root user." msgstr "" #. Tag: term -#: using-d-i.xml:315 +#: using-d-i.xml:327 #, no-c-format msgid "apt-setup" msgstr "" #. Tag: para -#: using-d-i.xml:315 +#: using-d-i.xml:327 #, no-c-format msgid "Configures apt, mostly automatically, based on what media the installer is running from." msgstr "" #. Tag: term -#: using-d-i.xml:324 +#: using-d-i.xml:336 #, no-c-format msgid "pkgsel" msgstr "" #. Tag: para -#: using-d-i.xml:324 +#: using-d-i.xml:336 #, no-c-format msgid "Uses <classname>tasksel</classname> to select and install additional software." msgstr "" #. Tag: term -#: using-d-i.xml:332 +#: using-d-i.xml:344 #, no-c-format msgid "os-prober" msgstr "" #. Tag: para -#: using-d-i.xml:332 +#: using-d-i.xml:344 #, no-c-format msgid "Detects currently installed operating systems on the computer and passes this information to the bootloader-installer, which may offer you an ability to add discovered operating systems to the bootloader's start menu. This way the user could easily choose at the boot time which operating system to start." msgstr "" #. Tag: term -#: using-d-i.xml:344 +#: using-d-i.xml:356 #, no-c-format msgid "bootloader-installer" msgstr "" #. Tag: para -#: using-d-i.xml:344 +#: using-d-i.xml:356 #, no-c-format msgid "The various bootloader installers each install a boot loader program on the hard disk, which is necessary for the computer to start up using Linux without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots." msgstr "" #. Tag: term -#: using-d-i.xml:355 +#: using-d-i.xml:367 #, no-c-format msgid "shell" msgstr "" #. Tag: para -#: using-d-i.xml:355 +#: using-d-i.xml:367 #, no-c-format msgid "Allows the user to execute a shell from the menu, or in the second console." msgstr "" #. Tag: term -#: using-d-i.xml:364 +#: using-d-i.xml:376 #, no-c-format msgid "save-logs" msgstr "" #. Tag: para -#: using-d-i.xml:364 +#: using-d-i.xml:376 #, no-c-format msgid "Provides a way for the user to record information on a floppy disk, network, hard disk, or other media when trouble is encountered, in order to accurately report installer software problems to Debian developers later." msgstr "" #. Tag: title -#: using-d-i.xml:382 +#: using-d-i.xml:394 #, no-c-format msgid "Using Individual Components" msgstr "" #. Tag: para -#: using-d-i.xml:383 +#: using-d-i.xml:395 #, no-c-format msgid "In this section we will describe each installer component in detail. The components have been grouped into stages that should be recognizable for users. They are presented in the order they appear during the install. Note that not all modules will be used for every installation; which modules are actually used depends on the installation method you use and on your hardware." msgstr "" #. Tag: title -#: using-d-i.xml:395 +#: using-d-i.xml:407 #, no-c-format msgid "Setting up Debian Installer and Hardware Configuration" msgstr "" #. Tag: para -#: using-d-i.xml:396 +#: using-d-i.xml:408 #, no-c-format msgid "Let's assume the Debian Installer has booted and you are facing its first screen. At this time, the capabilities of &d-i; are still quite limited. It doesn't know much about your hardware, preferred language, or even the task it should perform. Don't worry. Because &d-i; is quite clever, it can automatically probe your hardware, locate the rest of its components and upgrade itself to a capable installation system. However, you still need to help &d-i; with some information it can't determine automatically (like selecting your preferred language, keyboard layout or desired network mirror)." msgstr "" #. Tag: para -#: using-d-i.xml:409 +#: using-d-i.xml:421 #, no-c-format msgid "You will notice that &d-i; performs <firstterm>hardware detection</firstterm> several times during this stage. The first time is targeted specifically at the hardware needed to load installer components (e.g. your CD-ROM or network card). As not all drivers may be available during this first run, hardware detection needs to be repeated later in the process." msgstr "" #. Tag: title -#: using-d-i.xml:424 +#: using-d-i.xml:436 #, no-c-format msgid "Check available memory / low memory mode" msgstr "" #. Tag: para -#: using-d-i.xml:426 +#: using-d-i.xml:438 #, no-c-format msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian; on your system." msgstr "" #. Tag: para -#: using-d-i.xml:433 +#: using-d-i.xml:445 #, no-c-format msgid "The first measure taken to reduce memory consumption by the installer is to disable translations, which means that the installation can only be done in English. Of course, you can still localize the installed system after the installation has completed." msgstr "" #. Tag: para -#: using-d-i.xml:440 +#: using-d-i.xml:452 #, no-c-format msgid "If that is not sufficient, the installer will further reduce memory consumption by loading only those components essential to complete a basic installation. This reduces the functionality of the installation system. You will be given the opportunity to load additional components manually, but you should be aware that each component you select will use additional memory and thus may cause the installation to fail." msgstr "" #. Tag: para -#: using-d-i.xml:449 +#: using-d-i.xml:461 #, no-c-format msgid "If the installer runs in low memory mode, it is recommended to create a relatively large swap partition (64–128MB). The swap partition will be used as virtual memory and thus increases the amount of memory available to the system. The installer will activate the swap partition as early as possible in the installation process. Note that heavy use of swap will reduce performance of your system and may lead to high disk activity." msgstr "" #. Tag: para -#: using-d-i.xml:459 +#: using-d-i.xml:471 #, no-c-format msgid "Despite these measures, it is still possible that your system freezes, that unexpected errors occur or that processes are killed by the kernel because the system runs out of memory (which will result in <quote>Out of memory</quote> messages on VT4 and in the syslog)." msgstr "" #. Tag: para -#: using-d-i.xml:466 +#: using-d-i.xml:478 #, no-c-format msgid "For example, it has been reported that creating a big ext3 file system fails in low memory mode when there is insufficient swap space. If a larger swap doesn't help, try creating the file system as ext2 (which is an essential component of the installer) instead. It is possible to change an ext2 partition to ext3 after the installation." msgstr "" #. Tag: para -#: using-d-i.xml:474 +#: using-d-i.xml:486 #, no-c-format msgid "It is possible to force the installer to use a higher lowmem level than the one based on available memory by using the boot parameter <quote>lowmem</quote> as described in <xref linkend=\"installer-args\"/>." msgstr "" #. Tag: title -#: using-d-i.xml:489 +#: using-d-i.xml:501 #, no-c-format msgid "Selecting Localization Options" msgstr "" #. Tag: para -#: using-d-i.xml:491 +#: using-d-i.xml:503 #, no-c-format msgid "In most cases the first questions you will be asked concern the selection of localization options to be used both for the installation and for the installed system. The localization options consist of language, country and locales." msgstr "" #. Tag: para -#: using-d-i.xml:498 +#: using-d-i.xml:510 #, no-c-format msgid "The language you choose will be used for the rest of the installation process, provided a translation of the different dialogs is available. If no valid translation is available for the selected language, the installer will default to English." msgstr "" #. Tag: para -#: using-d-i.xml:505 +#: using-d-i.xml:517 #, no-c-format msgid "The selected country will be used later in the installation process to pick the default timezone and a Debian mirror appropriate for your geographic location. Language and country together will be used to set the default locale for your system and to help select your keyboard." msgstr "" #. Tag: para -#: using-d-i.xml:512 +#: using-d-i.xml:524 #, no-c-format msgid "You will first be asked to select your preferred language. The language names are listed in both English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names. At the top of the list is an extra option that allows you to select the <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed." msgstr "" #. Tag: para -#: using-d-i.xml:524 +#: using-d-i.xml:536 #, no-c-format msgid "If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will be shown a list of only those countries. To select a country that is not in that list, choose <guimenuitem>Other</guimenuitem> (the last option). You will then be presented with a list of continents; selecting a continent will lead to a list of relevant countries on that continent." msgstr "" #. Tag: para -#: using-d-i.xml:542 +#: using-d-i.xml:554 #, no-c-format msgid "If the language has only one country associated with it, that country will be selected automatically. In that case it is only possible to select a different country by first lowering the debconf priority to medium, followed by revisiting the language selection option in the main menu of the installer." msgstr "" #. Tag: para -#: using-d-i.xml:550 +#: using-d-i.xml:562 #, no-c-format msgid "A default locale will be selected based on the selected language and country. If you are installing at medium or low priority, you will have the option of selecting a different default locale and of selecting additional locales to be generated for the installed system." msgstr "" #. Tag: title -#: using-d-i.xml:565 +#: using-d-i.xml:577 #, no-c-format msgid "Choosing a Keyboard" msgstr "" #. Tag: para -#: using-d-i.xml:567 +#: using-d-i.xml:579 #, no-c-format msgid "Keyboards are often tailored to the characters used in a language. Select a layout that conforms to the keyboard you are using, or select something close if the keyboard layout you want isn't represented. Once the system installation is complete, you'll be able to select a keyboard layout from a wider range of choices (run <command>kbdconfig</command> as root after you have completed the installation)." msgstr "" #. Tag: para -#: using-d-i.xml:577 +#: using-d-i.xml:589 #, no-c-format msgid "Move the highlight to the keyboard selection you desire and press &enterkey;. Use the arrow keys to move the highlight — they are in the same place in all national language keyboard layouts, so they are independent of the keyboard configuration. An 'extended' keyboard is one with <keycap>F1</keycap> through <keycap>F10</keycap> keys along the top row." msgstr "" #. Tag: para -#: using-d-i.xml:586 +#: using-d-i.xml:598 #, no-c-format msgid "There are two keyboard layouts for US keyboards; the qwerty/mac-usb-us (Apple USB) layout will place the Alt function on the <keycap>Command/Apple</keycap> key (in the keyboard position next to the <keycap>space</keycap> key similar to <keycap>Alt</keycap> on PC keyboards), while the qwerty/us (Standard) layout will place the Alt function on the <keycap>Option</keycap> key (engraved with 'alt' on most Mac keyboards). In other respects the two layouts are similar." msgstr "" #. Tag: title -#: using-d-i.xml:616 +#: using-d-i.xml:628 #, no-c-format msgid "Looking for the Debian Installer ISO Image" msgstr "" #. Tag: para -#: using-d-i.xml:617 +#: using-d-i.xml:629 #, no-c-format msgid "When installing via the <emphasis>hd-media</emphasis> method, there will be a moment where you need to find and mount the Debian Installer iso image in order to get the rest of the installation files. The component <command>iso-scan</command> does exactly this." msgstr "" #. Tag: para -#: using-d-i.xml:624 +#: using-d-i.xml:636 #, no-c-format msgid "At first, <command>iso-scan</command> automatically mounts all block devices (e.g. partitions) which have some known filesystem on them and sequentially searches for filenames ending with <filename>.iso</filename> (or <filename>.ISO</filename> for that matter). Beware that the first attempt scans only files in the root directory and in the first level of subdirectories (i.e. it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, <filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not <filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). After an iso image has been found, <command>iso-scan</command> checks its content to determine if the image is a valid Debian iso image or not. In the former case we are done, in the latter <command>iso-scan</command> seeks for another image." msgstr "" #. Tag: para -#: using-d-i.xml:641 +#: using-d-i.xml:653 #, no-c-format msgid "In case the previous attempt to find an installer iso image fails, <command>iso-scan</command> will ask you whether you would like to perform a more thorough search. This pass doesn't just look into the topmost directories, but really traverses whole filesystem." msgstr "" #. Tag: para -#: using-d-i.xml:648 +#: using-d-i.xml:660 #, no-c-format msgid "If <command>iso-scan</command> does not discover your installer iso image, reboot back to your original operating system and check if the image is named correctly (ending in <filename>.iso</filename>), if it is placed on a filesystem recognizable by &d-i;, and if it is not corrupted (verify the checksum). Experienced Unix users could do this without rebooting on the second console." msgstr "" #. Tag: title -#: using-d-i.xml:669 +#: using-d-i.xml:681 #, no-c-format msgid "Configuring the Network" msgstr "" #. Tag: para -#: using-d-i.xml:671 +#: using-d-i.xml:683 #, no-c-format msgid "As you enter this step, if the system detects that you have more than one network device, you'll be asked to choose which device will be your <emphasis>primary</emphasis> network interface, i.e. the one which you want to use for installation. The other interfaces won't be configured at this time. You may configure additional interfaces after installation is complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> man page." msgstr "" #. Tag: para -#: using-d-i.xml:682 +#: using-d-i.xml:694 #, no-c-format msgid "By default, &d-i; tries to configure your computer's network automatically via DHCP. If the DHCP probe succeeds, you are done. If the probe fails, it may be caused by many factors ranging from unplugged network cable, to a misconfigured DHCP setup. Or maybe you don't have a DHCP server in your local network at all. For further explanation, check the error messages on the fourth console. In any case, you will be asked if you want to retry, or if you want to perform a manual setup. DHCP servers are sometimes really slow in their responses, so if you are sure everything is in place, try again." msgstr "" #. Tag: para -#: using-d-i.xml:694 +#: using-d-i.xml:706 #, no-c-format msgid "The manual network setup in turn asks you a number of questions about your network, notably <computeroutput>IP address</computeroutput>, <computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</computeroutput>, <computeroutput>Name server addresses</computeroutput>, and a <computeroutput>Hostname</computeroutput>. Moreover, if you have a wireless network interface, you will be asked to provide your <computeroutput>Wireless ESSID</computeroutput> and a <computeroutput>WEP key</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:708 +#: using-d-i.xml:720 #, no-c-format msgid "Some technical details you might, or might not, find handy: the program assumes the network IP address is the bitwise-AND of your system's IP address and your netmask. The default broadcast address is calculated as the bitwise OR of your system's IP address with the bitwise negation of the netmask. It will also guess your gateway. If you can't find any of these answers, use the offered defaults — if necessary, you can change them by editing <filename>/etc/network/interfaces</filename> once the system has been installed." msgstr "" #. Tag: title -#: using-d-i.xml:753 +#: using-d-i.xml:765 #, no-c-format msgid "Configuring the Clock" msgstr "" #. Tag: para -#: using-d-i.xml:755 +#: using-d-i.xml:767 #, no-c-format msgid "The installer will first attempt to connect to a time server on the Internet (using the <firstterm>NTP</firstterm> protocol) in order to correctly set the system time. If this does not succeed, the installer will assume the time and date obtained from the system clock when the installation system was booted are correct. It is not possible to manually set the system time during the installation process." msgstr "" #. Tag: para -#: using-d-i.xml:773 +#: using-d-i.xml:785 #, no-c-format msgid "Depending on the location selected earlier in the installation process, you may be shown a list of timezones relevant for that location. If your location has only one time zone, you will not be asked anything and the system will assume that time zone." msgstr "" #. Tag: para -#: using-d-i.xml:780 +#: using-d-i.xml:792 #, no-c-format msgid "If for some reason you wish to set a time zone for the installed system that does <emphasis>not</emphasis> match the selected location, there are two options." msgstr "" #. Tag: para -#: using-d-i.xml:791 +#: using-d-i.xml:803 #, no-c-format msgid "The simplest option is to just select a different timezone after the installation has been completed and you've booted into the new system. The command to do this is:" msgstr "" #. Tag: screen -#: using-d-i.xml:797 +#: using-d-i.xml:809 #, no-c-format msgid "# dpkg-reconfigure tzdata" msgstr "" #. Tag: para -#: using-d-i.xml:803 +#: using-d-i.xml:815 #, no-c-format msgid "Alternatively, the time zone can be set at the very start of the installation by passing the parameter <userinput>time/zone=<replaceable>value</replaceable></userinput> when you boot the installation system. The value should of course be a valid time zone, for example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>." msgstr "" #. Tag: para -#: using-d-i.xml:817 +#: using-d-i.xml:829 #, no-c-format msgid "For automated installations the time zone can also be set using preseeding." msgstr "" #. Tag: title -#: using-d-i.xml:830 +#: using-d-i.xml:842 #, no-c-format msgid "Partitioning and Mount Point Selection" msgstr "" #. Tag: para -#: using-d-i.xml:831 +#: using-d-i.xml:843 #, no-c-format msgid "At this time, after hardware detection has been executed a final time, &d-i; should be at its full strength, customized for the user's needs and ready to do some real work. As the title of this section indicates, the main task of the next few components lies in partitioning your disks, creating filesystems, assigning mountpoints and optionally configuring closely related options like RAID, LVM or encrypted devices." msgstr "" #. Tag: para -#: using-d-i.xml:852 +#: using-d-i.xml:864 #, no-c-format msgid "If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:858 +#: using-d-i.xml:870 #, no-c-format msgid "" "If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to <quote>zero</quote> the first few sectors of the drive: <informalexample><screen>\n" @@ -702,163 +714,163 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:871 +#: using-d-i.xml:883 #, no-c-format msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu." msgstr "" #. Tag: title -#: using-d-i.xml:881 +#: using-d-i.xml:893 #, no-c-format msgid "Guided Partitioning" msgstr "" #. Tag: para -#: using-d-i.xml:882 +#: using-d-i.xml:894 #, no-c-format msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>." msgstr "" #. Tag: para -#: using-d-i.xml:897 +#: using-d-i.xml:909 #, no-c-format msgid "The option to use (encrypted) LVM may not be available on all architectures." msgstr "" #. Tag: para -#: using-d-i.xml:902 +#: using-d-i.xml:914 #, no-c-format msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data." msgstr "" #. Tag: para -#: using-d-i.xml:911 +#: using-d-i.xml:923 #, no-c-format msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk." msgstr "" #. Tag: para -#: using-d-i.xml:920 +#: using-d-i.xml:932 #, no-c-format msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk." msgstr "" #. Tag: para -#: using-d-i.xml:930 +#: using-d-i.xml:942 #, no-c-format msgid "If you choose guided partitioning (either classic or using (encrypted) LVM) for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them." msgstr "" #. Tag: para -#: using-d-i.xml:939 +#: using-d-i.xml:951 #, no-c-format msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible." msgstr "" #. Tag: para -#: using-d-i.xml:947 +#: using-d-i.xml:959 #, no-c-format msgid "Next, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail." msgstr "" #. Tag: entry -#: using-d-i.xml:963 +#: using-d-i.xml:975 #, no-c-format msgid "Partitioning scheme" msgstr "" #. Tag: entry -#: using-d-i.xml:964 +#: using-d-i.xml:976 #, no-c-format msgid "Minimum space" msgstr "" #. Tag: entry -#: using-d-i.xml:965 +#: using-d-i.xml:977 #, no-c-format msgid "Created partitions" msgstr "" #. Tag: entry -#: using-d-i.xml:971 +#: using-d-i.xml:983 #, no-c-format msgid "All files in one partition" msgstr "" #. Tag: entry -#: using-d-i.xml:972 +#: using-d-i.xml:984 #, no-c-format msgid "600MB" msgstr "" #. Tag: entry -#: using-d-i.xml:973 +#: using-d-i.xml:985 #, no-c-format msgid "<filename>/</filename>, swap" msgstr "" #. Tag: entry -#: using-d-i.xml:975 +#: using-d-i.xml:987 #, no-c-format msgid "Separate /home partition" msgstr "" #. Tag: entry -#: using-d-i.xml:976 +#: using-d-i.xml:988 #, no-c-format msgid "500MB" msgstr "" #. Tag: entry -#: using-d-i.xml:977 +#: using-d-i.xml:989 #, no-c-format msgid "<filename>/</filename>, <filename>/home</filename>, swap" msgstr "" #. Tag: entry -#: using-d-i.xml:981 +#: using-d-i.xml:993 #, no-c-format msgid "Separate /home, /usr, /var and /tmp partitions" msgstr "" #. Tag: entry -#: using-d-i.xml:982 +#: using-d-i.xml:994 #, no-c-format msgid "<entry>1GB</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:983 +#: using-d-i.xml:995 #, no-c-format msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap" msgstr "" #. Tag: para -#: using-d-i.xml:992 +#: using-d-i.xml:1004 #, no-c-format msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, including the swap partition, will be created inside the LVM partition." msgstr "" #. Tag: para -#: using-d-i.xml:998 +#: using-d-i.xml:1010 #, no-c-format msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition." msgstr "" #. Tag: para -#: using-d-i.xml:1006 +#: using-d-i.xml:1018 #, no-c-format msgid "If you choose guided partitioning for your Alpha system, an additional, unformatted partition will be allocated at the beginning of your disk to reserve this space for the aboot boot loader." msgstr "" #. Tag: para -#: using-d-i.xml:1012 +#: using-d-i.xml:1024 #, no-c-format msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted." msgstr "" #. Tag: para -#: using-d-i.xml:1018 +#: using-d-i.xml:1030 #, no-c-format msgid "" "The list of partitions might look like this: <informalexample><screen>\n" @@ -881,601 +893,601 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:1031 +#: using-d-i.xml:1043 #, no-c-format msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning." msgstr "" #. Tag: title -#: using-d-i.xml:1045 +#: using-d-i.xml:1057 #, no-c-format msgid "Manual Partitioning" msgstr "" #. Tag: para -#: using-d-i.xml:1046 +#: using-d-i.xml:1058 #, no-c-format msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually setup your partition table and the usage of partitions by your new Debian system will be covered in the remainder of this section." msgstr "" #. Tag: para -#: using-d-i.xml:1054 +#: using-d-i.xml:1066 #, no-c-format msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk." msgstr "" #. Tag: para -#: using-d-i.xml:1062 +#: using-d-i.xml:1074 #, no-c-format msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap, software RAID, LVM, an encrypted file system, or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem for this partition, including options to use the partition for swap, software RAID, LVM, or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen." msgstr "" #. Tag: para -#: using-d-i.xml:1084 +#: using-d-i.xml:1096 #, no-c-format msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen as is used when creating a new partition, so you can change the same settings. One thing that may not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition." msgstr "" #. Tag: para -#: using-d-i.xml:1095 +#: using-d-i.xml:1107 #, no-c-format msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue." msgstr "" #. Tag: para -#: using-d-i.xml:1103 +#: using-d-i.xml:1115 #, no-c-format msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one." msgstr "" #. Tag: para -#: using-d-i.xml:1109 +#: using-d-i.xml:1121 #, no-c-format msgid "Capabilities of <command>partman</command> can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)." msgstr "" #. Tag: para -#: using-d-i.xml:1117 +#: using-d-i.xml:1129 #, no-c-format msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested." msgstr "" #. Tag: title -#: using-d-i.xml:1145 +#: using-d-i.xml:1157 #, no-c-format msgid "Configuring Multidisk Devices (Software RAID)" msgstr "" #. Tag: para -#: using-d-i.xml:1146 +#: using-d-i.xml:1158 #, no-c-format msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct MD device even from partitions residing on single physical drive, but that won't bring you anything useful. </para></footnote> in your computer, you can use <command>mdcfg</command> to setup your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)." msgstr "" #. Tag: para -#: using-d-i.xml:1160 +#: using-d-i.xml:1172 #, no-c-format msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)." msgstr "" #. Tag: para -#: using-d-i.xml:1168 +#: using-d-i.xml:1180 #, no-c-format msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar to RAID5 except that it uses two parity devices instead of one. </para><para> A RAID6 array can survive up to two disk failures. </para></listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It creates <replaceable>n</replaceable> copies of incoming data and distributes them across the partitions so that none of the copies of the same data are on the same device. The default value of <replaceable>n</replaceable> is 2, but it can be set to something else in expert mode. The number of partitions used must be at least <replaceable>n</replaceable>. RAID10 has different layouts for distributing the copies. The default is near copies. Near copies have all of the copies at about the same offset on all of the disks. Far copies have the copies at different offsets on the disks. Offset copies copy the stripe, not the individual copies. </para><para> RAID10 can be used to achieve reliability and redundancy without the drawback of having to calculate parity. </para></listitem> </varlistentry> </variablelist> To sum it up:" msgstr "" #. Tag: entry -#: using-d-i.xml:1282 +#: using-d-i.xml:1294 #, no-c-format msgid "Type" msgstr "" #. Tag: entry -#: using-d-i.xml:1283 +#: using-d-i.xml:1295 #, no-c-format msgid "Minimum Devices" msgstr "" #. Tag: entry -#: using-d-i.xml:1284 +#: using-d-i.xml:1296 #, no-c-format msgid "Spare Device" msgstr "" #. Tag: entry -#: using-d-i.xml:1285 +#: using-d-i.xml:1297 #, no-c-format msgid "Survives disk failure?" msgstr "" #. Tag: entry -#: using-d-i.xml:1286 +#: using-d-i.xml:1298 #, no-c-format msgid "Available Space" msgstr "" #. Tag: entry -#: using-d-i.xml:1292 +#: using-d-i.xml:1304 #, no-c-format msgid "RAID0" msgstr "" #. Tag: entry -#: using-d-i.xml:1293 using-d-i.xml:1301 using-d-i.xml:1331 +#: using-d-i.xml:1305 using-d-i.xml:1313 using-d-i.xml:1343 #, no-c-format msgid "<entry>2</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1294 using-d-i.xml:1295 +#: using-d-i.xml:1306 using-d-i.xml:1307 #, no-c-format msgid "<entry>no</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1296 +#: using-d-i.xml:1308 #, no-c-format msgid "Size of the smallest partition multiplied by number of devices in RAID" msgstr "" #. Tag: entry -#: using-d-i.xml:1300 +#: using-d-i.xml:1312 #, no-c-format msgid "RAID1" msgstr "" #. Tag: entry -#: using-d-i.xml:1302 using-d-i.xml:1310 using-d-i.xml:1321 using-d-i.xml:1332 +#: using-d-i.xml:1314 using-d-i.xml:1322 using-d-i.xml:1333 using-d-i.xml:1344 #, no-c-format msgid "optional" msgstr "" #. Tag: entry -#: using-d-i.xml:1303 using-d-i.xml:1311 using-d-i.xml:1322 using-d-i.xml:1333 +#: using-d-i.xml:1315 using-d-i.xml:1323 using-d-i.xml:1334 using-d-i.xml:1345 #, no-c-format msgid "<entry>yes</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1304 +#: using-d-i.xml:1316 #, no-c-format msgid "Size of the smallest partition in RAID" msgstr "" #. Tag: entry -#: using-d-i.xml:1308 +#: using-d-i.xml:1320 #, no-c-format msgid "RAID5" msgstr "" #. Tag: entry -#: using-d-i.xml:1309 +#: using-d-i.xml:1321 #, no-c-format msgid "<entry>3</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1312 +#: using-d-i.xml:1324 #, no-c-format msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)" msgstr "" #. Tag: entry -#: using-d-i.xml:1319 +#: using-d-i.xml:1331 #, no-c-format msgid "RAID6" msgstr "" #. Tag: entry -#: using-d-i.xml:1320 +#: using-d-i.xml:1332 #, no-c-format msgid "<entry>4</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1323 +#: using-d-i.xml:1335 #, no-c-format msgid "Size of the smallest partition multiplied by (number of devices in RAID minus two)" msgstr "" #. Tag: entry -#: using-d-i.xml:1330 +#: using-d-i.xml:1342 #, no-c-format msgid "RAID10" msgstr "" #. Tag: entry -#: using-d-i.xml:1334 +#: using-d-i.xml:1346 #, no-c-format msgid "Total of all partitions divided by the number of chunk copies (defaults to two)" msgstr "" #. Tag: para -#: using-d-i.xml:1341 +#: using-d-i.xml:1353 #, no-c-format msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>." msgstr "" #. Tag: para -#: using-d-i.xml:1346 +#: using-d-i.xml:1358 #, no-c-format msgid "To create a MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)" msgstr "" #. Tag: para -#: using-d-i.xml:1355 +#: using-d-i.xml:1367 #, no-c-format msgid "Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for <filename>/boot</filename> when using RAID for the root (<filename>/</filename>) file system. Most boot loaders <phrase arch=\"x86\">(including lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</filename> can be an option." msgstr "" #. Tag: para -#: using-d-i.xml:1367 +#: using-d-i.xml:1379 #, no-c-format msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) file system. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell." msgstr "" #. Tag: para -#: using-d-i.xml:1376 +#: using-d-i.xml:1388 #, no-c-format msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected." msgstr "" #. Tag: para -#: using-d-i.xml:1389 +#: using-d-i.xml:1401 #, no-c-format msgid "RAID0 is simple — you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD." msgstr "" #. Tag: para -#: using-d-i.xml:1396 +#: using-d-i.xml:1408 #, no-c-format msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided few seconds ago. Don't worry. If you make a mistake and select different number of partitions, the &d-i; won't let you continue until you correct the issue." msgstr "" #. Tag: para -#: using-d-i.xml:1408 +#: using-d-i.xml:1420 #, no-c-format msgid "RAID5 has a similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions." msgstr "" #. Tag: para -#: using-d-i.xml:1414 +#: using-d-i.xml:1426 #, no-c-format -msgid "RAID6 also has a similar setup procedure as RAID1 except thatat least <emphasis>four</emphasis> active partitions are required." +msgid "RAID6 also has a similar setup procedure as RAID1 except that at least <emphasis>four</emphasis> active partitions are required." msgstr "" #. Tag: para -#: using-d-i.xml:1420 +#: using-d-i.xml:1432 #, no-c-format msgid "RAID10 again has a similar setup procedure as RAID1 except in expert mode. In expert mode, &d-i; will ask you for the layout. The layout has two parts. The first part is the layout type. It is either <literal>n</literal> (for near copies), <literal>f</literal> (for far copies), or <literal>o</literal> (for offset copies). The second part is the number of copies to make of the data. There must be at least that many active devices so that all of the copies can be distributed onto different disks." msgstr "" #. Tag: para -#: using-d-i.xml:1434 +#: using-d-i.xml:1446 #, no-c-format msgid "It is perfectly possible to have several types of MD at once. For example, if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine the first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)." msgstr "" #. Tag: para -#: using-d-i.xml:1443 +#: using-d-i.xml:1455 #, no-c-format msgid "After you setup MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints." msgstr "" #. Tag: title -#: using-d-i.xml:1458 +#: using-d-i.xml:1470 #, no-c-format msgid "Configuring the Logical Volume Manager (LVM)" msgstr "" #. Tag: para -#: using-d-i.xml:1459 +#: using-d-i.xml:1471 #, no-c-format msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation with moving stuff around, symlinking, etc." msgstr "" #. Tag: para -#: using-d-i.xml:1467 +#: using-d-i.xml:1479 #, no-c-format msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disk (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks." msgstr "" #. Tag: para -#: using-d-i.xml:1477 +#: using-d-i.xml:1489 #, no-c-format msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk to the computer, join it with your existing volume group and then resize the logical volume which holds your <filename>/home</filename> filesystem and voila — your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>." msgstr "" #. Tag: para -#: using-d-i.xml:1488 +#: using-d-i.xml:1500 #, no-c-format msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>." msgstr "" #. Tag: para -#: using-d-i.xml:1497 +#: using-d-i.xml:1509 #, no-c-format msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:" msgstr "" #. Tag: para -#: using-d-i.xml:1508 +#: using-d-i.xml:1520 #, no-c-format msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1513 +#: using-d-i.xml:1525 #, no-c-format msgid "Create volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1516 +#: using-d-i.xml:1528 #, no-c-format msgid "Create logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1519 +#: using-d-i.xml:1531 #, no-c-format msgid "Delete volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1522 +#: using-d-i.xml:1534 #, no-c-format msgid "Delete logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1525 +#: using-d-i.xml:1537 #, no-c-format msgid "Extend volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1528 +#: using-d-i.xml:1540 #, no-c-format msgid "Reduce volume group" msgstr "" #. Tag: para -#: using-d-i.xml:1530 +#: using-d-i.xml:1542 #, no-c-format msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen" msgstr "" #. Tag: para -#: using-d-i.xml:1536 +#: using-d-i.xml:1548 #, no-c-format msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it." msgstr "" #. Tag: para -#: using-d-i.xml:1541 +#: using-d-i.xml:1553 #, no-c-format msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)." msgstr "" #. Tag: title -#: using-d-i.xml:1555 +#: using-d-i.xml:1567 #, no-c-format msgid "Configuring Encrypted Volumes" msgstr "" #. Tag: para -#: using-d-i.xml:1556 +#: using-d-i.xml:1568 #, no-c-format msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters." msgstr "" #. Tag: para -#: using-d-i.xml:1568 +#: using-d-i.xml:1580 #, no-c-format msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition." msgstr "" #. Tag: para -#: using-d-i.xml:1583 +#: using-d-i.xml:1595 #, no-c-format msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length." msgstr "" #. Tag: para -#: using-d-i.xml:1590 +#: using-d-i.xml:1602 #, no-c-format msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition." msgstr "" #. Tag: para -#: using-d-i.xml:1601 +#: using-d-i.xml:1613 #, no-c-format msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default." msgstr "" #. Tag: para -#: using-d-i.xml:1613 +#: using-d-i.xml:1625 #, no-c-format msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind." msgstr "" #. Tag: term -#: using-d-i.xml:1623 +#: using-d-i.xml:1635 #, no-c-format msgid "Encryption: <userinput>aes</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1625 +#: using-d-i.xml:1637 #, no-c-format msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century." msgstr "" #. Tag: term -#: using-d-i.xml:1643 +#: using-d-i.xml:1655 #, no-c-format msgid "Key size: <userinput>256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1645 +#: using-d-i.xml:1657 #, no-c-format msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher." msgstr "" #. Tag: term -#: using-d-i.xml:1657 +#: using-d-i.xml:1669 #, no-c-format msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1659 +#: using-d-i.xml:1671 #, no-c-format msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data." msgstr "" #. Tag: para -#: using-d-i.xml:1669 +#: using-d-i.xml:1681 #, no-c-format msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms." msgstr "" #. Tag: term -#: using-d-i.xml:1681 +#: using-d-i.xml:1693 #, no-c-format msgid "Encryption key: <userinput>Passphrase</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1683 +#: using-d-i.xml:1695 #, no-c-format msgid "Here you can choose the type of the encryption key for this partition." msgstr "" #. Tag: term -#: using-d-i.xml:1689 +#: using-d-i.xml:1701 #, no-c-format msgid "Passphrase" msgstr "" #. Tag: para -#: using-d-i.xml:1690 +#: using-d-i.xml:1702 #, no-c-format msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process." msgstr "" #. Tag: term -#: using-d-i.xml:1705 using-d-i.xml:1798 +#: using-d-i.xml:1717 using-d-i.xml:1810 #, no-c-format msgid "Random key" msgstr "" #. Tag: para -#: using-d-i.xml:1706 +#: using-d-i.xml:1718 #, no-c-format msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)" msgstr "" #. Tag: para -#: using-d-i.xml:1715 +#: using-d-i.xml:1727 #, no-c-format msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition." msgstr "" #. Tag: term -#: using-d-i.xml:1734 using-d-i.xml:1811 +#: using-d-i.xml:1746 using-d-i.xml:1823 #, no-c-format msgid "Erase data: <userinput>yes</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1736 +#: using-d-i.xml:1748 #, no-c-format msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>." msgstr "" #. Tag: para -#: using-d-i.xml:1756 +#: using-d-i.xml:1768 #, no-c-format msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:" msgstr "" #. Tag: term -#: using-d-i.xml:1765 +#: using-d-i.xml:1777 #, no-c-format msgid "Encryption: <userinput>AES256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1767 +#: using-d-i.xml:1779 #, no-c-format msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information." msgstr "" #. Tag: term -#: using-d-i.xml:1777 +#: using-d-i.xml:1789 #, no-c-format msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1779 +#: using-d-i.xml:1791 #, no-c-format msgid "Here you can select the type of the encryption key for this partition." msgstr "" #. Tag: term -#: using-d-i.xml:1785 +#: using-d-i.xml:1797 #, no-c-format msgid "Keyfile (GnuPG)" msgstr "" #. Tag: para -#: using-d-i.xml:1786 +#: using-d-i.xml:1798 #, no-c-format msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)." msgstr "" #. Tag: para -#: using-d-i.xml:1799 +#: using-d-i.xml:1811 #, no-c-format msgid "Please see the section on random keys above." msgstr "" #. Tag: para -#: using-d-i.xml:1813 +#: using-d-i.xml:1825 #, no-c-format msgid "Please see the the section on erasing data above." msgstr "" #. Tag: para -#: using-d-i.xml:1822 +#: using-d-i.xml:1834 #, no-c-format msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time." msgstr "" #. Tag: para -#: using-d-i.xml:1832 +#: using-d-i.xml:1844 #, no-c-format msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)." msgstr "" #. Tag: para -#: using-d-i.xml:1841 +#: using-d-i.xml:1853 #, no-c-format msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system." msgstr "" #. Tag: para -#: using-d-i.xml:1854 +#: using-d-i.xml:1866 #, no-c-format msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted." msgstr "" #. Tag: para -#: using-d-i.xml:1870 +#: using-d-i.xml:1882 #, no-c-format msgid "" "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n" @@ -1488,607 +1500,607 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:1883 +#: using-d-i.xml:1895 #, no-c-format msgid "One thing to note here are the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between ordinary boot process and boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:1893 +#: using-d-i.xml:1905 #, no-c-format msgid "Once you are satisfied with the partitioning scheme, continue with the installation." msgstr "" #. Tag: title -#: using-d-i.xml:1904 +#: using-d-i.xml:1916 #, no-c-format msgid "Installing the Base System" msgstr "" #. Tag: para -#: using-d-i.xml:1905 +#: using-d-i.xml:1917 #, no-c-format msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time." msgstr "" #. Tag: para -#: using-d-i.xml:1918 +#: using-d-i.xml:1930 #, no-c-format msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>." msgstr "" #. Tag: para -#: using-d-i.xml:1927 +#: using-d-i.xml:1939 #, no-c-format msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console." msgstr "" #. Tag: para -#: using-d-i.xml:1933 +#: using-d-i.xml:1945 #, no-c-format msgid "As part of the installation, a Linux kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels." msgstr "" #. Tag: title -#: using-d-i.xml:1945 +#: using-d-i.xml:1957 #, no-c-format msgid "Setting Up Users And Passwords" msgstr "" #. Tag: para -#: using-d-i.xml:1946 +#: using-d-i.xml:1958 #, no-c-format msgid "After the base system has been installed, the installer will allow you to set up the <quote>root</quote> account and/or an account for the first user. Other user accounts can be created after the installation has been completed." msgstr "" #. Tag: title -#: using-d-i.xml:1960 +#: using-d-i.xml:1972 #, no-c-format msgid "Set the Root Password" msgstr "" #. Tag: para -#: using-d-i.xml:1964 +#: using-d-i.xml:1976 #, no-c-format msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible." msgstr "" #. Tag: para -#: using-d-i.xml:1972 +#: using-d-i.xml:1984 #, no-c-format msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed." msgstr "" #. Tag: para -#: using-d-i.xml:1980 +#: using-d-i.xml:1992 #, no-c-format msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator." msgstr "" #. Tag: title -#: using-d-i.xml:1990 +#: using-d-i.xml:2002 #, no-c-format msgid "Create an Ordinary User" msgstr "" #. Tag: para -#: using-d-i.xml:1992 +#: using-d-i.xml:2004 #, no-c-format msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login." msgstr "" #. Tag: para -#: using-d-i.xml:2001 +#: using-d-i.xml:2013 #, no-c-format msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program — that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail — consider reading one if it is new to you." msgstr "" #. Tag: para -#: using-d-i.xml:2011 +#: using-d-i.xml:2023 #, no-c-format msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account." msgstr "" #. Tag: para -#: using-d-i.xml:2018 +#: using-d-i.xml:2030 #, no-c-format msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command." msgstr "" #. Tag: title -#: using-d-i.xml:2029 +#: using-d-i.xml:2041 #, no-c-format msgid "Installing Additional Software" msgstr "" #. Tag: para -#: using-d-i.xml:2030 +#: using-d-i.xml:2042 #, no-c-format msgid "At this point you have a usable but limited system. Most users will want to install additional software on the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network connection." msgstr "" #. Tag: title -#: using-d-i.xml:2045 +#: using-d-i.xml:2057 #, no-c-format msgid "Configuring apt" msgstr "" #. Tag: para -#: using-d-i.xml:2047 +#: using-d-i.xml:2059 #, no-c-format msgid "One of the tools used to install packages on a &debian; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management." msgstr "" #. Tag: para -#: using-d-i.xml:2071 +#: using-d-i.xml:2083 #, no-c-format msgid "<command>apt</command> must be configured so that it knows from where to retrieve packages. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>. You can examine and edit this file to your liking after the installation is complete." msgstr "" #. Tag: para -#: using-d-i.xml:2078 +#: using-d-i.xml:2090 #, no-c-format msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>volatile</quote> update service." msgstr "" #. Tag: para -#: using-d-i.xml:2087 +#: using-d-i.xml:2099 #, no-c-format msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or volatile update services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive." msgstr "" #. Tag: title -#: using-d-i.xml:2098 +#: using-d-i.xml:2110 #, no-c-format msgid "Installing from more than one CD or DVD" msgstr "" #. Tag: para -#: using-d-i.xml:2100 +#: using-d-i.xml:2112 #, no-c-format msgid "If you are installing from a CD or a DVD that is part of a larger set, the installer will ask if you want to scan additional CDs or DVDs. If you have additional CDs or DVDs available, you probably want to do this so the installer can use the packages included on them." msgstr "" #. Tag: para -#: using-d-i.xml:2107 +#: using-d-i.xml:2119 #, no-c-format msgid "If you do not have any additional CDs or DVDs, that is no problem: using them is not required. If you also do not use a network mirror (as explained in the next section), it can mean that not all packages belonging to the tasks you select in the next step of the installation can be installed." msgstr "" #. Tag: para -#: using-d-i.xml:2115 +#: using-d-i.xml:2127 #, no-c-format msgid "Packages are included on CDs (and DVDs) in the order of their popularity. This means that for most uses only the first CDs in a set are needed and that only very few people actually use any of the packages included on the last CDs in a set." msgstr "" #. Tag: para -#: using-d-i.xml:2122 +#: using-d-i.xml:2134 #, no-c-format msgid "It also means that buying or downloading and burning a full CD set is just a waste of money as you'll never use most of them. In most cases you are better off getting only the first 3 to 8 CDs and installing any additional packages you may need from the Internet by using a mirror. The same goes for DVD sets: the first DVD, or maybe the first two DVDs will cover most needs." msgstr "" #. Tag: para -#: using-d-i.xml:2131 +#: using-d-i.xml:2143 #, no-c-format msgid "A good rule of thumb is that for a regular desktop installation (using the GNOME desktop environment) only the first three CDs are needed. For the alternative desktop environments (KDE or Xfce), additional CDs are needed. The first DVD easily covers all three desktop environments." msgstr "" #. Tag: para -#: using-d-i.xml:2139 +#: using-d-i.xml:2151 #, no-c-format msgid "If you do scan multiple CDs or DVDs, the installer will prompt you to exchange them when it needs packages from another CD/DVD than the one currently in the drive. Note that only CDs or DVDs that belong to the same set should be scanned. The order in which they are scanned does not really matter, but scanning them in ascending order will reduce the chance of mistakes." msgstr "" #. Tag: title -#: using-d-i.xml:2152 +#: using-d-i.xml:2164 #, no-c-format msgid "Using a network mirror" msgstr "" #. Tag: para -#: using-d-i.xml:2154 +#: using-d-i.xml:2166 #, no-c-format msgid "One question that will be asked during most installs is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions." msgstr "" #. Tag: para -#: using-d-i.xml:2160 +#: using-d-i.xml:2172 #, no-c-format msgid "If you are <emphasis>not</emphasis> installing from a full CD or DVD or using a full CD/DVD image, you really should use a network mirror as otherwise you will end up with only a very minimal system. However, if you have a limited Internet connection it is best <emphasis>not</emphasis> to select the <literal>desktop</literal> task in the next step of the installation." msgstr "" #. Tag: para -#: using-d-i.xml:2169 +#: using-d-i.xml:2181 #, no-c-format msgid "If you are installing from a single full CD or using a full CD image, using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. If you have a limited Internet connection it may still be best to <emphasis>not</emphasis> select a network mirror here, but to finish the installation using only what's available on the CD and selectively install additional packages after the installation (i.e. after you have rebooted into the new system)." msgstr "" #. Tag: para -#: using-d-i.xml:2180 +#: using-d-i.xml:2192 #, no-c-format msgid "If you are installing from a DVD or using a DVD image, any packages needed during the installation should be present on the first DVD. The same is true if you have scanned multiple CDs as explained in the previous section. Use of a network mirror is optional." msgstr "" #. Tag: para -#: using-d-i.xml:2187 +#: using-d-i.xml:2199 #, no-c-format msgid "One advantage of adding a network mirror is that updates that have occurred since the CD/DVD set was created and have been included in a point release, will become available for installation, thus extending the life of your CD/DVD set without compromising the security or stability of the installed system." msgstr "" #. Tag: para -#: using-d-i.xml:2194 +#: using-d-i.xml:2206 #, no-c-format msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available from CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on" msgstr "" #. Tag: para -#: using-d-i.xml:2203 +#: using-d-i.xml:2215 #, no-c-format msgid "the tasks you select in the next step of the installation," msgstr "" #. Tag: para -#: using-d-i.xml:2208 +#: using-d-i.xml:2220 #, no-c-format msgid "which packages are needed for those tasks," msgstr "" #. Tag: para -#: using-d-i.xml:2213 +#: using-d-i.xml:2225 #, no-c-format msgid "which of those packages are present on the CDs or DVDs you have scanned, and" msgstr "" #. Tag: para -#: using-d-i.xml:2218 +#: using-d-i.xml:2230 #, no-c-format msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or volatile updates)." msgstr "" #. Tag: para -#: using-d-i.xml:2227 +#: using-d-i.xml:2239 #, no-c-format msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or volatile update available for them and those services have been configured." msgstr "" #. Tag: title -#: using-d-i.xml:2243 +#: using-d-i.xml:2255 #, no-c-format msgid "Selecting and Installing Software" msgstr "" #. Tag: para -#: using-d-i.xml:2245 +#: using-d-i.xml:2257 #, no-c-format msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks." msgstr "" #. Tag: para -#: using-d-i.xml:2254 +#: using-d-i.xml:2266 #, no-c-format msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks." msgstr "" #. Tag: para -#: using-d-i.xml:2281 +#: using-d-i.xml:2293 #, no-c-format msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can deselect them. You can even opt to install no tasks at all at this point." msgstr "" #. Tag: para -#: using-d-i.xml:2288 +#: using-d-i.xml:2300 #, no-c-format msgid "Unless you are using the special KDE or Xfce CDs, the <quote>Desktop environment</quote> task will install the GNOME desktop environment." msgstr "" #. Tag: para -#: using-d-i.xml:2295 +#: using-d-i.xml:2307 #, no-c-format msgid "It is not possible to interactively select a different desktop during the installation. However, it <emphasis>is</emphasis> possible to get &d-i; to install a KDE desktop environment instead of GNOME by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter <literal>desktop=kde</literal> at the boot prompt when starting the installer. Alternatively the more lightweight Xfce desktop environment can be selected by using <literal>desktop=xfce</literal>." msgstr "" #. Tag: para -#: using-d-i.xml:2305 +#: using-d-i.xml:2317 #, no-c-format msgid "Note that this will only work if the packages needed for KDE or Xfce are actually available. If you are installing using a single full CD image, they will need to be downloaded from a mirror as most needed packages are only included on later CDs; installing KDE or Xfce this way should work fine if you are using a DVD image or any other installation method." msgstr "" #. Tag: para -#: using-d-i.xml:2313 +#: using-d-i.xml:2325 #, no-c-format -msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache</classname>." +msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache2</classname>." msgstr "" #. Tag: para -#: using-d-i.xml:2325 +#: using-d-i.xml:2337 #, no-c-format msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the tasks you've selected." msgstr "" #. Tag: para -#: using-d-i.xml:2332 +#: using-d-i.xml:2344 #, no-c-format msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task." msgstr "" #. Tag: para -#: using-d-i.xml:2338 +#: using-d-i.xml:2350 #, no-c-format msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started." msgstr "" #. Tag: para -#: using-d-i.xml:2347 +#: using-d-i.xml:2359 #, no-c-format msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image." msgstr "" #. Tag: para -#: using-d-i.xml:2356 +#: using-d-i.xml:2368 #, no-c-format msgid "Each package you selected with <command>tasksel</command> is downloaded, unpacked and then installed in turn by the <command>apt-get</command> and <command>dpkg</command> programs. If a particular program needs more information from the user, it will prompt you during this process." msgstr "" #. Tag: title -#: using-d-i.xml:2369 +#: using-d-i.xml:2381 #, no-c-format msgid "Making Your System Bootable" msgstr "" #. Tag: para -#: using-d-i.xml:2371 +#: using-d-i.xml:2383 #, no-c-format msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>" msgstr "" #. Tag: title -#: using-d-i.xml:2386 +#: using-d-i.xml:2398 #, no-c-format msgid "Detecting other operating systems" msgstr "" #. Tag: para -#: using-d-i.xml:2388 +#: using-d-i.xml:2400 #, no-c-format msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to Debian." msgstr "" #. Tag: para -#: using-d-i.xml:2396 +#: using-d-i.xml:2408 #, no-c-format msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information." msgstr "" #. Tag: title -#: using-d-i.xml:2414 +#: using-d-i.xml:2426 #, no-c-format msgid "Install <command>aboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2415 +#: using-d-i.xml:2427 #, no-c-format msgid "If you have booted from SRM and you select this option, the installer will write <command>aboot</command> to the first sector of the disk on which you installed Debian. Be <emphasis>very</emphasis> careful — it is <emphasis>not</emphasis> possible to boot multiple operating systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a different operating system installed on the disk where you have installed Debian, you will have to boot GNU/Linux from a floppy instead." msgstr "" #. Tag: title -#: using-d-i.xml:2435 +#: using-d-i.xml:2447 #, no-c-format msgid "<command>palo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2436 +#: using-d-i.xml:2448 #, no-c-format msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions." msgstr "" #. Tag: para -#: using-d-i.xml:2445 +#: using-d-i.xml:2457 #, no-c-format msgid "hppa FIXME ( need more info )" msgstr "" #. Tag: title -#: using-d-i.xml:2457 +#: using-d-i.xml:2469 #, no-c-format msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2459 +#: using-d-i.xml:2471 #, no-c-format msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for new users and old hands alike." msgstr "" #. Tag: para -#: using-d-i.xml:2465 +#: using-d-i.xml:2477 #, no-c-format msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information." msgstr "" #. Tag: para -#: using-d-i.xml:2471 +#: using-d-i.xml:2483 #, no-c-format msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use." msgstr "" #. Tag: title -#: using-d-i.xml:2484 +#: using-d-i.xml:2496 #, no-c-format msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2486 +#: using-d-i.xml:2498 #, no-c-format msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>." msgstr "" #. Tag: para -#: using-d-i.xml:2496 +#: using-d-i.xml:2508 #, no-c-format msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation." msgstr "" #. Tag: para -#: using-d-i.xml:2504 +#: using-d-i.xml:2516 #, no-c-format msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:" msgstr "" #. Tag: term -#: using-d-i.xml:2511 +#: using-d-i.xml:2523 #, no-c-format msgid "Master Boot Record (MBR)" msgstr "" #. Tag: para -#: using-d-i.xml:2511 +#: using-d-i.xml:2523 #, no-c-format msgid "This way the <command>LILO</command> will take complete control of the boot process." msgstr "" #. Tag: term -#: using-d-i.xml:2518 +#: using-d-i.xml:2530 #, no-c-format msgid "new Debian partition" msgstr "" #. Tag: para -#: using-d-i.xml:2518 +#: using-d-i.xml:2530 #, no-c-format msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new Debian partition and it will serve as a secondary boot loader." msgstr "" #. Tag: term -#: using-d-i.xml:2527 +#: using-d-i.xml:2539 #, no-c-format msgid "Other choice" msgstr "" #. Tag: para -#: using-d-i.xml:2527 +#: using-d-i.xml:2539 #, no-c-format msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use traditional device names such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>." msgstr "" #. Tag: para -#: using-d-i.xml:2537 +#: using-d-i.xml:2549 #, no-c-format msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record — however, this means that you'll need to use some other way to get back into Debian!" msgstr "" #. Tag: title -#: using-d-i.xml:2553 +#: using-d-i.xml:2565 #, no-c-format msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2555 +#: using-d-i.xml:2567 #, no-c-format msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to do the actual work of loading and starting the Linux kernel." msgstr "" #. Tag: para -#: using-d-i.xml:2571 +#: using-d-i.xml:2583 #, no-c-format msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem." msgstr "" #. Tag: title -#: using-d-i.xml:2583 +#: using-d-i.xml:2595 #, no-c-format msgid "Choose the correct partition!" msgstr "" #. Tag: para -#: using-d-i.xml:2585 +#: using-d-i.xml:2597 #, no-c-format msgid "The criteria for selecting a partition is that it is FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!" msgstr "" #. Tag: title -#: using-d-i.xml:2600 +#: using-d-i.xml:2612 #, no-c-format msgid "EFI Partition Contents" msgstr "" #. Tag: para -#: using-d-i.xml:2602 +#: using-d-i.xml:2614 #, no-c-format msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured." msgstr "" #. Tag: filename -#: using-d-i.xml:2624 +#: using-d-i.xml:2636 #, no-c-format msgid "elilo.conf" msgstr "" #. Tag: para -#: using-d-i.xml:2625 +#: using-d-i.xml:2637 #, no-c-format msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition." msgstr "" #. Tag: filename -#: using-d-i.xml:2634 +#: using-d-i.xml:2646 #, no-c-format msgid "elilo.efi" msgstr "" #. Tag: para -#: using-d-i.xml:2635 +#: using-d-i.xml:2647 #, no-c-format msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>Debian GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu." msgstr "" #. Tag: filename -#: using-d-i.xml:2645 +#: using-d-i.xml:2657 #, no-c-format msgid "initrd.img" msgstr "" #. Tag: para -#: using-d-i.xml:2646 +#: using-d-i.xml:2658 #, no-c-format msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>." msgstr "" #. Tag: filename -#: using-d-i.xml:2658 +#: using-d-i.xml:2670 #, no-c-format msgid "readme.txt" msgstr "" #. Tag: para -#: using-d-i.xml:2659 +#: using-d-i.xml:2671 #, no-c-format msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run." msgstr "" #. Tag: filename -#: using-d-i.xml:2669 +#: using-d-i.xml:2681 #, no-c-format msgid "vmlinuz" msgstr "" #. Tag: para -#: using-d-i.xml:2670 +#: using-d-i.xml:2682 #, no-c-format msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>." msgstr "" #. Tag: title -#: using-d-i.xml:2690 +#: using-d-i.xml:2702 #, no-c-format msgid "<command>arcboot</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2691 +#: using-d-i.xml:2703 #, no-c-format msgid "" "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n" @@ -2101,289 +2113,289 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2710 +#: using-d-i.xml:2722 #, no-c-format msgid "scsi" msgstr "" #. Tag: para -#: using-d-i.xml:2711 +#: using-d-i.xml:2723 #, no-c-format msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2719 +#: using-d-i.xml:2731 #, no-c-format msgid "disk" msgstr "" #. Tag: para -#: using-d-i.xml:2720 +#: using-d-i.xml:2732 #, no-c-format msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2728 +#: using-d-i.xml:2740 #, no-c-format msgid "partnr" msgstr "" #. Tag: para -#: using-d-i.xml:2729 +#: using-d-i.xml:2741 #, no-c-format msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2737 +#: using-d-i.xml:2749 #, no-c-format msgid "config" msgstr "" #. Tag: para -#: using-d-i.xml:2738 +#: using-d-i.xml:2750 #, no-c-format msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: title -#: using-d-i.xml:2759 +#: using-d-i.xml:2771 #, no-c-format msgid "Install <command>Yaboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2760 +#: using-d-i.xml:2772 #, no-c-format msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian;." msgstr "" #. Tag: title -#: using-d-i.xml:2778 +#: using-d-i.xml:2790 #, no-c-format msgid "Install <command>Quik</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2779 +#: using-d-i.xml:2791 #, no-c-format msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones." msgstr "" #. Tag: title -#: using-d-i.xml:2795 +#: using-d-i.xml:2807 #, no-c-format msgid "<command>zipl</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2796 +#: using-d-i.xml:2808 #, no-c-format msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>." msgstr "" #. Tag: title -#: using-d-i.xml:2813 +#: using-d-i.xml:2825 #, no-c-format msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2815 +#: using-d-i.xml:2827 #, no-c-format msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install." msgstr "" #. Tag: title -#: using-d-i.xml:2840 +#: using-d-i.xml:2852 #, no-c-format msgid "Continue Without Boot Loader" msgstr "" #. Tag: para -#: using-d-i.xml:2842 +#: using-d-i.xml:2854 #, no-c-format msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader). <phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, and Amiga systems, where the original operating system must be maintained on the box and used to boot GNU/Linux.</phrase>" msgstr "" #. Tag: para -#: using-d-i.xml:2851 +#: using-d-i.xml:2863 #, no-c-format msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem." msgstr "" #. Tag: title -#: using-d-i.xml:2868 +#: using-d-i.xml:2880 #, no-c-format msgid "Finishing the Installation" msgstr "" #. Tag: para -#: using-d-i.xml:2869 +#: using-d-i.xml:2881 #, no-c-format msgid "This is the last step in the Debian installation process during which the installer will do any last minute tasks. It mostly consists of tidying up after the &d-i;." msgstr "" #. Tag: title -#: using-d-i.xml:2882 +#: using-d-i.xml:2894 #, no-c-format msgid "Setting the System Clock" msgstr "" #. Tag: para -#: using-d-i.xml:2884 +#: using-d-i.xml:2896 #, no-c-format msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed." msgstr "" #. Tag: para -#: using-d-i.xml:2891 +#: using-d-i.xml:2903 #, no-c-format msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"m68k;powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase> <phrase arch=\"x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase>" msgstr "" #. Tag: para -#: using-d-i.xml:2902 +#: using-d-i.xml:2914 #, no-c-format msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made." msgstr "" #. Tag: title -#: using-d-i.xml:2917 +#: using-d-i.xml:2929 #, no-c-format msgid "Reboot the System" msgstr "" #. Tag: para -#: using-d-i.xml:2919 +#: using-d-i.xml:2931 #, no-c-format msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2925 +#: using-d-i.xml:2937 #, no-c-format msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian; from the DASD which you selected for the root filesystem during the first steps of the installation." msgstr "" #. Tag: title -#: using-d-i.xml:2938 +#: using-d-i.xml:2950 #, no-c-format msgid "Miscellaneous" msgstr "" #. Tag: para -#: using-d-i.xml:2939 +#: using-d-i.xml:2951 #, no-c-format msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong." msgstr "" #. Tag: title -#: using-d-i.xml:2952 +#: using-d-i.xml:2964 #, no-c-format msgid "Saving the installation logs" msgstr "" #. Tag: para -#: using-d-i.xml:2954 +#: using-d-i.xml:2966 #, no-c-format msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2961 +#: using-d-i.xml:2973 #, no-c-format msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report." msgstr "" #. Tag: title -#: using-d-i.xml:2981 +#: using-d-i.xml:2993 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "" #. Tag: para -#: using-d-i.xml:2983 +#: using-d-i.xml:2995 #, no-c-format msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to installer itself." msgstr "" #. Tag: para -#: using-d-i.xml:3001 +#: using-d-i.xml:3013 #, no-c-format msgid "For the graphical installer see also <xref linkend=\"gtk-using\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:3005 +#: using-d-i.xml:3017 #, no-c-format msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer." msgstr "" #. Tag: para -#: using-d-i.xml:3013 +#: using-d-i.xml:3025 #, no-c-format msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history." msgstr "" #. Tag: para -#: using-d-i.xml:3022 +#: using-d-i.xml:3034 #, no-c-format msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory." msgstr "" #. Tag: para -#: using-d-i.xml:3029 +#: using-d-i.xml:3041 #, no-c-format msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging." msgstr "" #. Tag: para -#: using-d-i.xml:3035 +#: using-d-i.xml:3047 #, no-c-format msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell." msgstr "" #. Tag: title -#: using-d-i.xml:3050 +#: using-d-i.xml:3062 #, no-c-format msgid "Installation Over the Network" msgstr "" #. Tag: para -#: using-d-i.xml:3052 +#: using-d-i.xml:3064 #, no-c-format msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)" msgstr "" #. Tag: para -#: using-d-i.xml:3062 +#: using-d-i.xml:3074 #, no-c-format msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>." msgstr "" #. Tag: para -#: using-d-i.xml:3075 +#: using-d-i.xml:3087 #, no-c-format msgid "For installations on &arch-title;, this is the default method after setting up the network." msgstr "" #. Tag: para -#: using-d-i.xml:3080 +#: using-d-i.xml:3092 #, no-c-format msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the <quote>person who will continue the installation remotely</quote>." msgstr "" #. Tag: para -#: using-d-i.xml:3092 +#: using-d-i.xml:3104 #, no-c-format msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component." msgstr "" #. Tag: para -#: using-d-i.xml:3098 +#: using-d-i.xml:3110 #, no-c-format msgid "" "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n" @@ -2392,38 +2404,32 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:3115 +#: using-d-i.xml:3127 #, no-c-format msgid "The <command>ssh</command> server in the installer uses a default configuration that does not send keep-alive packets. In principle, a connection to the system being installed should be kept open indefinitely. However, in some situations — depending on your local network setup — the connection may be lost after some period of inactivity. One common case where this can happen is when there is some form of Network Address Translation (NAT) somewhere between the client and the system being installed. Depending on at which point of the installation the connection was lost, you may or may not be able to resume the installation after reconnecting." msgstr "" #. Tag: para -#: using-d-i.xml:3128 +#: using-d-i.xml:3140 #, no-c-format msgid "You may be able to avoid the connection being dropped by adding the option <userinput>-o ServerAliveInterval=<replaceable>value</replaceable></userinput> when starting the <command>ssh</command> connection, or by adding that option in your <command>ssh</command> configuration file. Note however that in some cases adding this option may also <emphasis>cause</emphasis> a connection to be dropped (for example if keep-alive packets are sent during a brief network outage, from which <command>ssh</command> would otherwise have recovered), so it should only be used when needed." msgstr "" #. Tag: para -#: using-d-i.xml:3141 +#: using-d-i.xml:3153 #, no-c-format msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename><footnote> <para> The following command will remove an existing entry for a host: <command>ssh-keygen -R <<replaceable>hostname</replaceable>|<replaceable>IP address</replaceable>></command>. </para> </footnote> and try again." msgstr "" #. Tag: para -#: using-d-i.xml:3157 +#: using-d-i.xml:3169 #, no-c-format msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells." msgstr "" #. Tag: para -#: using-d-i.xml:3167 +#: using-d-i.xml:3179 #, no-c-format msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system." msgstr "" -#. Tag: para -#: using-d-i.xml:3175 -#, no-c-format -msgid "Also, if you are running the SSH session from an X terminal, you should not resize the window as that will result in the connection being terminated." -msgstr "" - |