diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/hardware.pot | 1102 | ||||
| -rw-r--r-- | po/pot/install-methods.pot | 344 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 42 | ||||
| -rw-r--r-- | po/pot/random-bits.pot | 291 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 254 |
5 files changed, 1001 insertions, 1032 deletions
diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index af0865223..df56a726c 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: 2007-08-20 00:08+0000\n" +"POT-Creation-Date: 2007-10-22 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" @@ -117,49 +117,49 @@ msgid "alpha" msgstr "" #. Tag: entry -#: hardware.xml:81 hardware.xml:82 +#: hardware.xml:81 #, no-c-format msgid "ARM and StrongARM" msgstr "" #. Tag: entry -#: hardware.xml:83 hardware.xml:84 +#: hardware.xml:82 #, no-c-format msgid "<entry>arm</entry>" msgstr "" #. Tag: entry -#: hardware.xml:85 +#: hardware.xml:83 #, no-c-format msgid "Netwinder and CATS" msgstr "" #. Tag: entry -#: hardware.xml:86 +#: hardware.xml:84 #, no-c-format msgid "netwinder" msgstr "" #. Tag: entry -#: hardware.xml:88 +#: hardware.xml:86 #, no-c-format msgid "Intel IOP32x" msgstr "" #. Tag: entry -#: hardware.xml:89 +#: hardware.xml:87 #, no-c-format msgid "iop32x" msgstr "" #. Tag: entry -#: hardware.xml:91 +#: hardware.xml:89 #, no-c-format msgid "Intel IXP4xx" msgstr "" #. Tag: entry -#: hardware.xml:92 +#: hardware.xml:90 #, no-c-format msgid "ixp4xx" msgstr "" @@ -167,1799 +167,1763 @@ msgstr "" #. Tag: entry #: hardware.xml:94 #, no-c-format -msgid "<entry>RiscPC</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:95 -#, no-c-format -msgid "<entry>rpc</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:99 -#, no-c-format msgid "HP PA-RISC" msgstr "" #. Tag: entry -#: hardware.xml:100 +#: hardware.xml:95 #, no-c-format msgid "hppa" msgstr "" #. Tag: entry -#: hardware.xml:101 +#: hardware.xml:96 #, no-c-format msgid "PA-RISC 1.1" msgstr "" #. Tag: entry -#: hardware.xml:102 +#: hardware.xml:97 #, no-c-format msgid "<entry>32</entry>" msgstr "" #. Tag: entry -#: hardware.xml:104 +#: hardware.xml:99 #, no-c-format msgid "PA-RISC 2.0" msgstr "" #. Tag: entry -#: hardware.xml:105 +#: hardware.xml:100 #, no-c-format msgid "<entry>64</entry>" msgstr "" #. Tag: entry -#: hardware.xml:109 +#: hardware.xml:104 #, no-c-format msgid "Intel IA-64" msgstr "" #. Tag: entry -#: hardware.xml:110 +#: hardware.xml:105 #, no-c-format msgid "ia64" msgstr "" #. Tag: entry -#: hardware.xml:116 +#: hardware.xml:111 #, no-c-format msgid "MIPS (big endian)" msgstr "" #. Tag: entry -#: hardware.xml:117 +#: hardware.xml:112 #, no-c-format msgid "mips" msgstr "" #. Tag: entry -#: hardware.xml:118 +#: hardware.xml:113 #, no-c-format msgid "SGI IP22 (Indy/Indigo 2)" msgstr "" #. Tag: entry -#: hardware.xml:119 +#: hardware.xml:114 #, no-c-format msgid "r4k-ip22" msgstr "" #. Tag: entry -#: hardware.xml:121 +#: hardware.xml:116 #, no-c-format msgid "SGI IP32 (O2)" msgstr "" #. Tag: entry -#: hardware.xml:122 +#: hardware.xml:117 #, no-c-format msgid "r5k-ip32" msgstr "" #. Tag: entry -#: hardware.xml:124 hardware.xml:142 +#: hardware.xml:119 hardware.xml:137 #, no-c-format msgid "Broadcom BCM91250A (SWARM)" msgstr "" #. Tag: entry -#: hardware.xml:125 hardware.xml:143 +#: hardware.xml:120 hardware.xml:138 #, no-c-format msgid "sb1-bcm91250a" msgstr "" #. Tag: entry -#: hardware.xml:127 hardware.xml:145 +#: hardware.xml:122 hardware.xml:140 #, no-c-format msgid "Broadcom BCM91480B (BigSur)" msgstr "" #. Tag: entry -#: hardware.xml:128 hardware.xml:146 +#: hardware.xml:123 hardware.xml:141 #, no-c-format msgid "sb1a-bcm91480b" msgstr "" #. Tag: entry -#: hardware.xml:132 +#: hardware.xml:127 #, no-c-format msgid "MIPS (little endian)" msgstr "" #. Tag: entry -#: hardware.xml:133 +#: hardware.xml:128 #, no-c-format msgid "mipsel" msgstr "" #. Tag: entry -#: hardware.xml:134 +#: hardware.xml:129 #, no-c-format msgid "Cobalt" msgstr "" #. Tag: entry -#: hardware.xml:135 +#: hardware.xml:130 #, no-c-format msgid "cobalt" msgstr "" #. Tag: entry -#: hardware.xml:137 +#: hardware.xml:132 #, no-c-format msgid "DECstation" msgstr "" #. Tag: entry -#: hardware.xml:138 hardware.xml:1113 hardware.xml:1128 hardware.xml:1138 +#: hardware.xml:133 hardware.xml:1086 hardware.xml:1101 hardware.xml:1111 #, no-c-format msgid "r4k-kn04" msgstr "" #. Tag: entry -#: hardware.xml:140 hardware.xml:1108 hardware.xml:1118 hardware.xml:1123 hardware.xml:1133 +#: hardware.xml:135 hardware.xml:1081 hardware.xml:1091 hardware.xml:1096 hardware.xml:1106 #, no-c-format msgid "r3k-kn02" msgstr "" #. Tag: entry -#: hardware.xml:150 +#: hardware.xml:145 #, no-c-format msgid "Motorola 680x0" msgstr "" #. Tag: entry -#: hardware.xml:151 +#: hardware.xml:146 #, no-c-format msgid "m68k" msgstr "" #. Tag: entry -#: hardware.xml:152 +#: hardware.xml:147 #, no-c-format msgid "Atari" msgstr "" #. Tag: entry -#: hardware.xml:153 +#: hardware.xml:148 #, no-c-format msgid "atari" msgstr "" #. Tag: entry -#: hardware.xml:155 +#: hardware.xml:150 #, no-c-format msgid "Amiga" msgstr "" #. Tag: entry -#: hardware.xml:156 +#: hardware.xml:151 #, no-c-format msgid "amiga" msgstr "" #. Tag: entry -#: hardware.xml:158 +#: hardware.xml:153 #, no-c-format msgid "68k Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:159 +#: hardware.xml:154 #, no-c-format msgid "<entry>mac</entry>" msgstr "" #. Tag: entry -#: hardware.xml:161 +#: hardware.xml:156 #, no-c-format msgid "<entry>VME</entry>" msgstr "" #. Tag: entry -#: hardware.xml:162 +#: hardware.xml:157 #, no-c-format msgid "bvme6000" msgstr "" #. Tag: entry -#: hardware.xml:164 +#: hardware.xml:159 #, no-c-format msgid "mvme147" msgstr "" #. Tag: entry -#: hardware.xml:166 +#: hardware.xml:161 #, no-c-format msgid "mvme16x" msgstr "" #. Tag: entry -#: hardware.xml:170 +#: hardware.xml:165 #, no-c-format msgid "IBM/Motorola PowerPC" msgstr "" #. Tag: entry -#: hardware.xml:171 +#: hardware.xml:166 #, no-c-format msgid "<entry>powerpc</entry>" msgstr "" #. Tag: entry -#: hardware.xml:172 +#: hardware.xml:167 #, no-c-format msgid "CHRP" msgstr "" #. Tag: entry -#: hardware.xml:173 +#: hardware.xml:168 #, no-c-format msgid "chrp" msgstr "" #. Tag: entry -#: hardware.xml:175 +#: hardware.xml:170 #, no-c-format msgid "PowerMac" msgstr "" #. Tag: entry -#: hardware.xml:176 +#: hardware.xml:171 #, no-c-format msgid "pmac" msgstr "" #. Tag: entry -#: hardware.xml:178 +#: hardware.xml:173 #, no-c-format msgid "PReP" msgstr "" #. Tag: entry -#: hardware.xml:179 +#: hardware.xml:174 #, no-c-format msgid "<entry>prep</entry>" msgstr "" #. Tag: entry -#: hardware.xml:183 hardware.xml:188 +#: hardware.xml:178 #, no-c-format msgid "Sun SPARC" msgstr "" #. Tag: entry -#: hardware.xml:184 hardware.xml:189 +#: hardware.xml:179 #, no-c-format msgid "sparc" msgstr "" #. Tag: entry -#: hardware.xml:185 -#, no-c-format -msgid "<entry>sun4m</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:186 -#, no-c-format -msgid "sparc32" -msgstr "" - -#. Tag: entry -#: hardware.xml:190 +#: hardware.xml:180 #, no-c-format msgid "<entry>sun4u</entry>" msgstr "" #. Tag: entry -#: hardware.xml:191 +#: hardware.xml:181 #, no-c-format msgid "sparc64" msgstr "" #. Tag: entry -#: hardware.xml:193 +#: hardware.xml:183 #, no-c-format msgid "<entry>sun4v</entry>" msgstr "" #. Tag: entry -#: hardware.xml:197 +#: hardware.xml:187 #, no-c-format msgid "IBM S/390" msgstr "" #. Tag: entry -#: hardware.xml:198 +#: hardware.xml:188 #, no-c-format msgid "s390" msgstr "" #. Tag: entry -#: hardware.xml:199 +#: hardware.xml:189 #, no-c-format msgid "IPL from VM-reader and DASD" msgstr "" #. Tag: entry -#: hardware.xml:200 +#: hardware.xml:190 #, no-c-format msgid "generic" msgstr "" #. Tag: entry -#: hardware.xml:202 +#: hardware.xml:192 #, no-c-format msgid "IPL from tape" msgstr "" #. Tag: entry -#: hardware.xml:203 +#: hardware.xml:193 #, no-c-format msgid "tape" msgstr "" #. Tag: para -#: hardware.xml:208 +#: hardware.xml:198 #, no-c-format msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture. If you are looking for information on any of the other Debian-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">Debian-Ports</ulink> pages." msgstr "" #. Tag: para -#: hardware.xml:216 +#: hardware.xml:206 #, no-c-format msgid "This is the first official release of &debian; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well." msgstr "" #. Tag: title -#: hardware.xml:238 hardware.xml:697 hardware.xml:733 hardware.xml:828 hardware.xml:847 hardware.xml:933 hardware.xml:975 hardware.xml:1043 hardware.xml:1202 +#: hardware.xml:228 hardware.xml:687 hardware.xml:723 hardware.xml:801 hardware.xml:820 hardware.xml:906 hardware.xml:948 hardware.xml:1016 hardware.xml:1175 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para -#: hardware.xml:239 +#: hardware.xml:229 #, no-c-format msgid "Complete information regarding supported DEC Alphas can be found at <ulink url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this section is to describe the systems supported by the boot disks." msgstr "" #. Tag: para -#: hardware.xml:246 +#: hardware.xml:236 #, no-c-format msgid "Alpha machines are subdivided into different system types because there are a number of generations of motherboard and supporting chipsets. Different systems (<quote>sub-architectures</quote>) often have radically different engineering and capabilities. Therefore, the process of installing and, more to the point, booting, can vary from system to system." msgstr "" #. Tag: para -#: hardware.xml:254 +#: hardware.xml:244 #, no-c-format msgid "The following table lists the system types supported by the Debian installation system. The table also indicates the <emphasis>code name</emphasis> for these system types. You'll need to know this code name when you actually begin the installation process:" msgstr "" #. Tag: entry -#: hardware.xml:271 +#: hardware.xml:261 #, no-c-format msgid "Hardware Type" msgstr "" #. Tag: entry -#: hardware.xml:272 +#: hardware.xml:262 #, no-c-format msgid "Aliases" msgstr "" #. Tag: entry -#: hardware.xml:272 +#: hardware.xml:262 #, no-c-format msgid "MILO image" msgstr "" #. Tag: entry -#: hardware.xml:278 +#: hardware.xml:268 #, no-c-format msgid "ALCOR" msgstr "" #. Tag: entry -#: hardware.xml:279 +#: hardware.xml:269 #, no-c-format msgid "AlphaStation 500 5/266.300" msgstr "" #. Tag: entry -#: hardware.xml:280 +#: hardware.xml:270 #, no-c-format msgid "Maverick" msgstr "" #. Tag: entry -#: hardware.xml:281 hardware.xml:285 hardware.xml:289 +#: hardware.xml:271 hardware.xml:275 hardware.xml:279 #, no-c-format msgid "alcor" msgstr "" #. Tag: entry -#: hardware.xml:283 +#: hardware.xml:273 #, no-c-format msgid "AlphaStation 500 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:284 +#: hardware.xml:274 #, no-c-format msgid "Bret" msgstr "" #. Tag: entry -#: hardware.xml:287 +#: hardware.xml:277 #, no-c-format msgid "AlphaStation 600/266...300" msgstr "" #. Tag: entry -#: hardware.xml:288 +#: hardware.xml:278 #, no-c-format msgid "Alcor" msgstr "" #. Tag: entry -#: hardware.xml:291 +#: hardware.xml:281 #, no-c-format msgid "AlphaStation 600/300...433" msgstr "" #. Tag: entry -#: hardware.xml:292 +#: hardware.xml:282 #, no-c-format msgid "<entry>XLT</entry>" msgstr "" #. Tag: entry -#: hardware.xml:293 +#: hardware.xml:283 #, no-c-format msgid "<entry>xlt</entry>" msgstr "" #. Tag: entry -#: hardware.xml:297 +#: hardware.xml:287 #, no-c-format msgid "BOOK1" msgstr "" #. Tag: entry -#: hardware.xml:298 +#: hardware.xml:288 #, no-c-format msgid "AlphaBook1 (laptop)" msgstr "" #. Tag: entry -#: hardware.xml:299 +#: hardware.xml:289 #, no-c-format msgid "Alphabook1/Burns" msgstr "" #. Tag: entry -#: hardware.xml:300 +#: hardware.xml:290 #, no-c-format msgid "book1" msgstr "" #. Tag: entry -#: hardware.xml:304 +#: hardware.xml:294 #, no-c-format msgid "AVANTI" msgstr "" #. Tag: entry -#: hardware.xml:305 +#: hardware.xml:295 #, no-c-format msgid "AlphaStation 200 4/100...166" msgstr "" #. Tag: entry -#: hardware.xml:306 +#: hardware.xml:296 #, no-c-format msgid "Mustang" msgstr "" #. Tag: entry -#: hardware.xml:307 hardware.xml:311 hardware.xml:315 hardware.xml:319 hardware.xml:323 hardware.xml:327 hardware.xml:331 hardware.xml:335 +#: hardware.xml:297 hardware.xml:301 hardware.xml:305 hardware.xml:309 hardware.xml:313 hardware.xml:317 hardware.xml:321 hardware.xml:325 #, no-c-format msgid "avanti" msgstr "" #. Tag: entry -#: hardware.xml:309 +#: hardware.xml:299 #, no-c-format msgid "AlphaStation 200 4/233" msgstr "" #. Tag: entry -#: hardware.xml:310 +#: hardware.xml:300 #, no-c-format msgid "Mustang+" msgstr "" #. Tag: entry -#: hardware.xml:313 +#: hardware.xml:303 #, no-c-format msgid "AlphaStation 205 4/133...333" msgstr "" #. Tag: entry -#: hardware.xml:314 +#: hardware.xml:304 #, no-c-format msgid "<entry>LX3</entry>" msgstr "" #. Tag: entry -#: hardware.xml:317 +#: hardware.xml:307 #, no-c-format msgid "AlphaStation 250 4/300" msgstr "" #. Tag: entry -#: hardware.xml:318 +#: hardware.xml:308 #, no-c-format msgid "<entry>M3+</entry>" msgstr "" #. Tag: entry -#: hardware.xml:321 +#: hardware.xml:311 #, no-c-format msgid "AlphaStation 255 4/133...333" msgstr "" #. Tag: entry -#: hardware.xml:322 +#: hardware.xml:312 #, no-c-format msgid "LX3+" msgstr "" #. Tag: entry -#: hardware.xml:325 +#: hardware.xml:315 #, no-c-format msgid "AlphaStation 300 4/266" msgstr "" #. Tag: entry -#: hardware.xml:326 +#: hardware.xml:316 #, no-c-format msgid "Melmac" msgstr "" #. Tag: entry -#: hardware.xml:329 +#: hardware.xml:319 #, no-c-format msgid "AlphaStation 400 4/166" msgstr "" #. Tag: entry -#: hardware.xml:330 +#: hardware.xml:320 #, no-c-format msgid "Chinet" msgstr "" #. Tag: entry -#: hardware.xml:333 +#: hardware.xml:323 #, no-c-format msgid "AlphaStation 400 4/233...300" msgstr "" #. Tag: entry -#: hardware.xml:334 +#: hardware.xml:324 #, no-c-format msgid "Avanti" msgstr "" #. Tag: entry -#: hardware.xml:339 hardware.xml:352 hardware.xml:353 +#: hardware.xml:329 hardware.xml:342 hardware.xml:343 #, no-c-format msgid "EB164" msgstr "" #. Tag: entry -#: hardware.xml:340 +#: hardware.xml:330 #, no-c-format msgid "AlphaPC164" msgstr "" #. Tag: entry -#: hardware.xml:341 +#: hardware.xml:331 #, no-c-format msgid "PC164" msgstr "" #. Tag: entry -#: hardware.xml:342 +#: hardware.xml:332 #, no-c-format msgid "pc164" msgstr "" #. Tag: entry -#: hardware.xml:344 +#: hardware.xml:334 #, no-c-format msgid "AlphaPC164-LX" msgstr "" #. Tag: entry -#: hardware.xml:345 +#: hardware.xml:335 #, no-c-format msgid "LX164" msgstr "" #. Tag: entry -#: hardware.xml:346 +#: hardware.xml:336 #, no-c-format msgid "lx164" msgstr "" #. Tag: entry -#: hardware.xml:348 +#: hardware.xml:338 #, no-c-format msgid "AlphaPC164-SX" msgstr "" #. Tag: entry -#: hardware.xml:349 +#: hardware.xml:339 #, no-c-format msgid "SX164" msgstr "" #. Tag: entry -#: hardware.xml:350 +#: hardware.xml:340 #, no-c-format msgid "sx164" msgstr "" #. Tag: entry -#: hardware.xml:354 +#: hardware.xml:344 #, no-c-format msgid "eb164" msgstr "" #. Tag: entry -#: hardware.xml:358 hardware.xml:367 hardware.xml:368 +#: hardware.xml:348 hardware.xml:357 hardware.xml:358 #, no-c-format msgid "EB64+" msgstr "" #. Tag: entry -#: hardware.xml:359 +#: hardware.xml:349 #, no-c-format msgid "AlphaPC64" msgstr "" #. Tag: entry -#: hardware.xml:360 hardware.xml:364 +#: hardware.xml:350 hardware.xml:354 #, no-c-format msgid "Cabriolet" msgstr "" #. Tag: entry -#: hardware.xml:361 hardware.xml:365 +#: hardware.xml:351 hardware.xml:355 #, no-c-format msgid "cabriolet" msgstr "" #. Tag: entry -#: hardware.xml:363 +#: hardware.xml:353 #, no-c-format msgid "AlphaPCI64" msgstr "" #. Tag: entry -#: hardware.xml:369 +#: hardware.xml:359 #, no-c-format msgid "eb64p" msgstr "" #. Tag: entry -#: hardware.xml:373 hardware.xml:374 hardware.xml:375 +#: hardware.xml:363 hardware.xml:364 hardware.xml:365 #, no-c-format msgid "EB66" msgstr "" #. Tag: entry -#: hardware.xml:376 +#: hardware.xml:366 #, no-c-format msgid "eb66" msgstr "" #. Tag: entry -#: hardware.xml:378 hardware.xml:379 +#: hardware.xml:368 hardware.xml:369 #, no-c-format msgid "EB66+" msgstr "" #. Tag: entry -#: hardware.xml:380 +#: hardware.xml:370 #, no-c-format msgid "eb66p" msgstr "" #. Tag: entry -#: hardware.xml:384 +#: hardware.xml:374 #, no-c-format msgid "JENSEN" msgstr "" #. Tag: entry -#: hardware.xml:385 +#: hardware.xml:375 #, no-c-format msgid "DEC 2000 Model 300(S)" msgstr "" #. Tag: entry -#: hardware.xml:386 hardware.xml:394 +#: hardware.xml:376 hardware.xml:384 #, no-c-format msgid "Jensen" msgstr "" #. Tag: entry -#: hardware.xml:387 hardware.xml:391 hardware.xml:395 hardware.xml:456 hardware.xml:460 hardware.xml:478 hardware.xml:482 hardware.xml:486 hardware.xml:490 hardware.xml:494 hardware.xml:498 hardware.xml:502 hardware.xml:516 hardware.xml:520 hardware.xml:524 hardware.xml:528 hardware.xml:532 hardware.xml:566 hardware.xml:570 hardware.xml:574 hardware.xml:578 hardware.xml:592 hardware.xml:596 hardware.xml:600 hardware.xml:604 hardware.xml:611 hardware.xml:615 hardware.xml:619 hardware.xml:623 hardware.xml:627 hardware.xml:631 hardware.xml:635 hardware.xml:639 hardware.xml:643 hardware.xml:647 hardware.xml:651 hardware.xml:655 hardware.xml:659 hardware.xml:666 hardware.xml:670 +#: hardware.xml:377 hardware.xml:381 hardware.xml:385 hardware.xml:446 hardware.xml:450 hardware.xml:468 hardware.xml:472 hardware.xml:476 hardware.xml:480 hardware.xml:484 hardware.xml:488 hardware.xml:492 hardware.xml:506 hardware.xml:510 hardware.xml:514 hardware.xml:518 hardware.xml:522 hardware.xml:556 hardware.xml:560 hardware.xml:564 hardware.xml:568 hardware.xml:582 hardware.xml:586 hardware.xml:590 hardware.xml:594 hardware.xml:601 hardware.xml:605 hardware.xml:609 hardware.xml:613 hardware.xml:617 hardware.xml:621 hardware.xml:625 hardware.xml:629 hardware.xml:633 hardware.xml:637 hardware.xml:641 hardware.xml:645 hardware.xml:649 hardware.xml:656 hardware.xml:660 #, no-c-format msgid "<entry>N/A</entry>" msgstr "" #. Tag: entry -#: hardware.xml:389 +#: hardware.xml:379 #, no-c-format msgid "DEC 2000 Model 500" msgstr "" #. Tag: entry -#: hardware.xml:390 +#: hardware.xml:380 #, no-c-format msgid "Culzen" msgstr "" #. Tag: entry -#: hardware.xml:393 +#: hardware.xml:383 #, no-c-format msgid "DECpc 150" msgstr "" #. Tag: entry -#: hardware.xml:399 +#: hardware.xml:389 #, no-c-format msgid "MIATA" msgstr "" #. Tag: entry -#: hardware.xml:400 +#: hardware.xml:390 #, no-c-format msgid "Personal WorkStation 433a" msgstr "" #. Tag: entry -#: hardware.xml:401 hardware.xml:405 hardware.xml:409 hardware.xml:413 hardware.xml:417 hardware.xml:421 hardware.xml:425 hardware.xml:429 +#: hardware.xml:391 hardware.xml:395 hardware.xml:399 hardware.xml:403 hardware.xml:407 hardware.xml:411 hardware.xml:415 hardware.xml:419 #, no-c-format msgid "Miata" msgstr "" #. Tag: entry -#: hardware.xml:402 hardware.xml:406 hardware.xml:410 hardware.xml:414 hardware.xml:418 hardware.xml:422 hardware.xml:426 hardware.xml:430 +#: hardware.xml:392 hardware.xml:396 hardware.xml:400 hardware.xml:404 hardware.xml:408 hardware.xml:412 hardware.xml:416 hardware.xml:420 #, no-c-format msgid "miata" msgstr "" #. Tag: entry -#: hardware.xml:404 +#: hardware.xml:394 #, no-c-format msgid "Personal WorkStation 433au" msgstr "" #. Tag: entry -#: hardware.xml:408 +#: hardware.xml:398 #, no-c-format msgid "Personal WorkStation 466au" msgstr "" #. Tag: entry -#: hardware.xml:412 +#: hardware.xml:402 #, no-c-format msgid "Personal WorkStation 500a" msgstr "" #. Tag: entry -#: hardware.xml:416 +#: hardware.xml:406 #, no-c-format msgid "Personal WorkStation 500au" msgstr "" #. Tag: entry -#: hardware.xml:420 +#: hardware.xml:410 #, no-c-format msgid "Personal WorkStation 550au" msgstr "" #. Tag: entry -#: hardware.xml:424 +#: hardware.xml:414 #, no-c-format msgid "Personal WorkStation 600a" msgstr "" #. Tag: entry -#: hardware.xml:428 +#: hardware.xml:418 #, no-c-format msgid "Personal WorkStation 600au" msgstr "" #. Tag: entry -#: hardware.xml:434 +#: hardware.xml:424 #, no-c-format msgid "MIKASA" msgstr "" #. Tag: entry -#: hardware.xml:435 +#: hardware.xml:425 #, no-c-format msgid "AlphaServer 1000 4/200" msgstr "" #. Tag: entry -#: hardware.xml:436 +#: hardware.xml:426 #, no-c-format msgid "Mikasa" msgstr "" #. Tag: entry -#: hardware.xml:437 hardware.xml:441 hardware.xml:445 hardware.xml:449 +#: hardware.xml:427 hardware.xml:431 hardware.xml:435 hardware.xml:439 #, no-c-format msgid "mikasa" msgstr "" #. Tag: entry -#: hardware.xml:439 +#: hardware.xml:429 #, no-c-format msgid "AlphaServer 1000 4/233..266" msgstr "" #. Tag: entry -#: hardware.xml:440 +#: hardware.xml:430 #, no-c-format msgid "Mikasa+" msgstr "" #. Tag: entry -#: hardware.xml:443 hardware.xml:447 +#: hardware.xml:433 hardware.xml:437 #, no-c-format msgid "AlphaServer 1000 5/300" msgstr "" #. Tag: entry -#: hardware.xml:444 +#: hardware.xml:434 #, no-c-format msgid "Mikasa-Pinnacle" msgstr "" #. Tag: entry -#: hardware.xml:448 +#: hardware.xml:438 #, no-c-format msgid "Mikasa-Primo" msgstr "" #. Tag: entry -#: hardware.xml:453 +#: hardware.xml:443 #, no-c-format msgid "NAUTILUS" msgstr "" #. Tag: entry -#: hardware.xml:454 +#: hardware.xml:444 #, no-c-format msgid "UP1000" msgstr "" #. Tag: entry -#: hardware.xml:455 +#: hardware.xml:445 #, no-c-format msgid "Nautilus" msgstr "" #. Tag: entry -#: hardware.xml:458 +#: hardware.xml:448 #, no-c-format msgid "UP1100" msgstr "" #. Tag: entry -#: hardware.xml:459 +#: hardware.xml:449 #, no-c-format msgid "Galaxy-Train/Nautilus Jr." msgstr "" #. Tag: entry -#: hardware.xml:464 +#: hardware.xml:454 #, no-c-format msgid "NONAME" msgstr "" #. Tag: entry -#: hardware.xml:465 +#: hardware.xml:455 #, no-c-format msgid "AXPpci33" msgstr "" #. Tag: entry -#: hardware.xml:466 +#: hardware.xml:456 #, no-c-format msgid "Noname" msgstr "" #. Tag: entry -#: hardware.xml:467 hardware.xml:471 +#: hardware.xml:457 hardware.xml:461 #, no-c-format msgid "noname" msgstr "" #. Tag: entry -#: hardware.xml:469 +#: hardware.xml:459 #, no-c-format msgid "<entry>UDB</entry>" msgstr "" #. Tag: entry -#: hardware.xml:470 +#: hardware.xml:460 #, no-c-format msgid "Multia" msgstr "" #. Tag: entry -#: hardware.xml:475 +#: hardware.xml:465 #, no-c-format msgid "NORITAKE" msgstr "" #. Tag: entry -#: hardware.xml:476 +#: hardware.xml:466 #, no-c-format msgid "AlphaServer 1000A 4/233...266" msgstr "" #. Tag: entry -#: hardware.xml:477 +#: hardware.xml:467 #, no-c-format msgid "Noritake" msgstr "" #. Tag: entry -#: hardware.xml:480 +#: hardware.xml:470 #, no-c-format msgid "AlphaServer 1000A 5/300" msgstr "" #. Tag: entry -#: hardware.xml:481 +#: hardware.xml:471 #, no-c-format msgid "Noritake-Pinnacle" msgstr "" #. Tag: entry -#: hardware.xml:484 +#: hardware.xml:474 #, no-c-format msgid "AlphaServer 1000A 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:485 +#: hardware.xml:475 #, no-c-format msgid "Noritake-Primo" msgstr "" #. Tag: entry -#: hardware.xml:488 +#: hardware.xml:478 #, no-c-format msgid "AlphaServer 800 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:489 hardware.xml:497 hardware.xml:501 +#: hardware.xml:479 hardware.xml:487 hardware.xml:491 #, no-c-format msgid "Corelle" msgstr "" #. Tag: entry -#: hardware.xml:492 +#: hardware.xml:482 #, no-c-format msgid "AlphaStation 600 A" msgstr "" #. Tag: entry -#: hardware.xml:493 +#: hardware.xml:483 #, no-c-format msgid "Alcor-Primo" msgstr "" #. Tag: entry -#: hardware.xml:496 +#: hardware.xml:486 #, no-c-format msgid "Digital Server 3300" msgstr "" #. Tag: entry -#: hardware.xml:500 +#: hardware.xml:490 #, no-c-format msgid "Digital Server 3300R" msgstr "" #. Tag: entry -#: hardware.xml:506 +#: hardware.xml:496 #, no-c-format msgid "PLATFORM 2000" msgstr "" #. Tag: entry -#: hardware.xml:507 hardware.xml:508 +#: hardware.xml:497 hardware.xml:498 #, no-c-format msgid "<entry>P2K</entry>" msgstr "" #. Tag: entry -#: hardware.xml:509 +#: hardware.xml:499 #, no-c-format msgid "<entry>p2k</entry>" msgstr "" #. Tag: entry -#: hardware.xml:513 +#: hardware.xml:503 #, no-c-format msgid "RAWHIDE" msgstr "" #. Tag: entry -#: hardware.xml:514 +#: hardware.xml:504 #, no-c-format msgid "AlphaServer 1200 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:515 hardware.xml:527 +#: hardware.xml:505 hardware.xml:517 #, no-c-format msgid "Tincup/DaVinci" msgstr "" #. Tag: entry -#: hardware.xml:518 +#: hardware.xml:508 #, no-c-format msgid "AlphaServer 4000 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:519 +#: hardware.xml:509 #, no-c-format msgid "Wrangler/Durango" msgstr "" #. Tag: entry -#: hardware.xml:522 +#: hardware.xml:512 #, no-c-format msgid "AlphaServer 4100 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:523 hardware.xml:531 +#: hardware.xml:513 hardware.xml:521 #, no-c-format msgid "Dodge" msgstr "" #. Tag: entry -#: hardware.xml:526 +#: hardware.xml:516 #, no-c-format msgid "Digital Server 5300" msgstr "" #. Tag: entry -#: hardware.xml:530 +#: hardware.xml:520 #, no-c-format msgid "Digital Server 7300" msgstr "" #. Tag: entry -#: hardware.xml:536 +#: hardware.xml:526 #, no-c-format msgid "RUFFIAN" msgstr "" #. Tag: entry -#: hardware.xml:537 +#: hardware.xml:527 #, no-c-format msgid "DeskStation AlphaPC164-UX" msgstr "" #. Tag: entry -#: hardware.xml:538 hardware.xml:542 hardware.xml:546 hardware.xml:550 hardware.xml:554 hardware.xml:558 +#: hardware.xml:528 hardware.xml:532 hardware.xml:536 hardware.xml:540 hardware.xml:544 hardware.xml:548 #, no-c-format msgid "Ruffian" msgstr "" #. Tag: entry -#: hardware.xml:539 hardware.xml:543 hardware.xml:547 hardware.xml:551 hardware.xml:555 hardware.xml:559 +#: hardware.xml:529 hardware.xml:533 hardware.xml:537 hardware.xml:541 hardware.xml:545 hardware.xml:549 #, no-c-format msgid "ruffian" msgstr "" #. Tag: entry -#: hardware.xml:541 +#: hardware.xml:531 #, no-c-format msgid "DeskStation RPL164-2" msgstr "" #. Tag: entry -#: hardware.xml:545 +#: hardware.xml:535 #, no-c-format msgid "DeskStation RPL164-4" msgstr "" #. Tag: entry -#: hardware.xml:549 +#: hardware.xml:539 #, no-c-format msgid "DeskStation RPX164-2" msgstr "" #. Tag: entry -#: hardware.xml:553 +#: hardware.xml:543 #, no-c-format msgid "DeskStation RPX164-4" msgstr "" #. Tag: entry -#: hardware.xml:557 +#: hardware.xml:547 #, no-c-format msgid "Samsung AlphaPC164-BX" msgstr "" #. Tag: entry -#: hardware.xml:563 +#: hardware.xml:553 #, no-c-format msgid "SABLE" msgstr "" #. Tag: entry -#: hardware.xml:564 +#: hardware.xml:554 #, no-c-format msgid "AlphaServer 2000 4/xxx" msgstr "" #. Tag: entry -#: hardware.xml:565 +#: hardware.xml:555 #, no-c-format msgid "Demi-Sable" msgstr "" #. Tag: entry -#: hardware.xml:568 +#: hardware.xml:558 #, no-c-format msgid "AlphaServer 2000 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:569 +#: hardware.xml:559 #, no-c-format msgid "Demi-Gamma-Sable" msgstr "" #. Tag: entry -#: hardware.xml:572 +#: hardware.xml:562 #, no-c-format msgid "AlphaServer 2100 4/xxx" msgstr "" #. Tag: entry -#: hardware.xml:573 +#: hardware.xml:563 #, no-c-format msgid "Sable" msgstr "" #. Tag: entry -#: hardware.xml:576 +#: hardware.xml:566 #, no-c-format msgid "AlphaServer 2100 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:577 +#: hardware.xml:567 #, no-c-format msgid "Gamma-Sable" msgstr "" #. Tag: entry -#: hardware.xml:582 +#: hardware.xml:572 #, no-c-format msgid "TAKARA" msgstr "" #. Tag: entry -#: hardware.xml:583 +#: hardware.xml:573 #, no-c-format msgid "21164 PICMG SBC" msgstr "" #. Tag: entry -#: hardware.xml:584 +#: hardware.xml:574 #, no-c-format msgid "Takara" msgstr "" #. Tag: entry -#: hardware.xml:585 +#: hardware.xml:575 #, no-c-format msgid "takara" msgstr "" #. Tag: entry -#: hardware.xml:589 +#: hardware.xml:579 #, no-c-format msgid "TITAN" msgstr "" #. Tag: entry -#: hardware.xml:590 +#: hardware.xml:580 #, no-c-format msgid "AlphaServer DS15" msgstr "" #. Tag: entry -#: hardware.xml:591 +#: hardware.xml:581 #, no-c-format msgid "HyperBrick2" msgstr "" #. Tag: entry -#: hardware.xml:594 +#: hardware.xml:584 #, no-c-format msgid "AlphaServer DS25" msgstr "" #. Tag: entry -#: hardware.xml:595 +#: hardware.xml:585 #, no-c-format msgid "Granite" msgstr "" #. Tag: entry -#: hardware.xml:598 +#: hardware.xml:588 #, no-c-format msgid "AlphaServer ES45" msgstr "" #. Tag: entry -#: hardware.xml:599 +#: hardware.xml:589 #, no-c-format msgid "Privateer" msgstr "" #. Tag: entry -#: hardware.xml:602 hardware.xml:641 hardware.xml:645 +#: hardware.xml:592 hardware.xml:631 hardware.xml:635 #, no-c-format msgid "UNKNOWN" msgstr "" #. Tag: entry -#: hardware.xml:603 +#: hardware.xml:593 #, no-c-format msgid "Yukon" msgstr "" #. Tag: entry -#: hardware.xml:608 +#: hardware.xml:598 #, no-c-format msgid "TSUNAMI" msgstr "" #. Tag: entry -#: hardware.xml:609 +#: hardware.xml:599 #, no-c-format msgid "AlphaServer DS10" msgstr "" #. Tag: entry -#: hardware.xml:610 hardware.xml:658 +#: hardware.xml:600 hardware.xml:648 #, no-c-format msgid "Webbrick" msgstr "" #. Tag: entry -#: hardware.xml:613 +#: hardware.xml:603 #, no-c-format msgid "AlphaServer DS10L" msgstr "" #. Tag: entry -#: hardware.xml:614 +#: hardware.xml:604 #, no-c-format msgid "Slate" msgstr "" #. Tag: entry -#: hardware.xml:617 +#: hardware.xml:607 #, no-c-format msgid "AlphaServer DS20" msgstr "" #. Tag: entry -#: hardware.xml:618 +#: hardware.xml:608 #, no-c-format msgid "Catamaran/Goldrush" msgstr "" #. Tag: entry -#: hardware.xml:621 +#: hardware.xml:611 #, no-c-format msgid "AlphaServer DS20E" msgstr "" #. Tag: entry -#: hardware.xml:622 +#: hardware.xml:612 #, no-c-format msgid "Goldrack" msgstr "" #. Tag: entry -#: hardware.xml:625 +#: hardware.xml:615 #, no-c-format msgid "AlphaServer DS20L" msgstr "" #. Tag: entry -#: hardware.xml:626 +#: hardware.xml:616 #, no-c-format msgid "Shark" msgstr "" #. Tag: entry -#: hardware.xml:629 +#: hardware.xml:619 #, no-c-format msgid "AlphaServer ES40" msgstr "" #. Tag: entry -#: hardware.xml:630 +#: hardware.xml:620 #, no-c-format msgid "Clipper" msgstr "" #. Tag: entry -#: hardware.xml:633 hardware.xml:634 +#: hardware.xml:623 hardware.xml:624 #, no-c-format msgid "DP264" msgstr "" #. Tag: entry -#: hardware.xml:637 +#: hardware.xml:627 #, no-c-format msgid "SMARTengine 21264 PCI/ISA SBC" msgstr "" #. Tag: entry -#: hardware.xml:638 +#: hardware.xml:628 #, no-c-format msgid "Eiger" msgstr "" #. Tag: entry -#: hardware.xml:642 +#: hardware.xml:632 #, no-c-format msgid "Warhol" msgstr "" #. Tag: entry -#: hardware.xml:646 +#: hardware.xml:636 #, no-c-format msgid "Windjammer" msgstr "" #. Tag: entry -#: hardware.xml:649 +#: hardware.xml:639 #, no-c-format msgid "UP2000" msgstr "" #. Tag: entry -#: hardware.xml:650 +#: hardware.xml:640 #, no-c-format msgid "Swordfish" msgstr "" #. Tag: entry -#: hardware.xml:653 +#: hardware.xml:643 #, no-c-format msgid "XP1000" msgstr "" #. Tag: entry -#: hardware.xml:654 +#: hardware.xml:644 #, no-c-format msgid "Monet/Brisbane" msgstr "" #. Tag: entry -#: hardware.xml:657 +#: hardware.xml:647 #, no-c-format msgid "XP900" msgstr "" #. Tag: entry -#: hardware.xml:663 +#: hardware.xml:653 #, no-c-format msgid "WILDFIRE" msgstr "" #. Tag: entry -#: hardware.xml:664 +#: hardware.xml:654 #, no-c-format msgid "AlphaServer GS160" msgstr "" #. Tag: entry -#: hardware.xml:665 hardware.xml:669 +#: hardware.xml:655 hardware.xml:659 #, no-c-format msgid "Wildfire" msgstr "" #. Tag: entry -#: hardware.xml:668 +#: hardware.xml:658 #, no-c-format msgid "AlphaServer GS320" msgstr "" #. Tag: entry -#: hardware.xml:674 hardware.xml:676 +#: hardware.xml:664 hardware.xml:666 #, no-c-format msgid "<entry>XL</entry>" msgstr "" #. Tag: entry -#: hardware.xml:675 +#: hardware.xml:665 #, no-c-format msgid "XL-233...266" msgstr "" #. Tag: entry -#: hardware.xml:677 +#: hardware.xml:667 #, no-c-format msgid "<entry>xl</entry>" msgstr "" #. Tag: para -#: hardware.xml:682 +#: hardware.xml:672 #, no-c-format msgid "It is believed that Debian &releasename; supports installing on all alpha sub-architectures with the exception of the ARC-only Ruffian and XL sub-architectures and the Titan subarchitecture, which requires a change to the kernel compile options." msgstr "" #. Tag: para -#: hardware.xml:698 hardware.xml:848 +#: hardware.xml:688 hardware.xml:821 #, no-c-format msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics." msgstr "" #. Tag: title -#: hardware.xml:706 hardware.xml:856 hardware.xml:1016 +#: hardware.xml:696 hardware.xml:829 hardware.xml:989 #, no-c-format msgid "<title>CPU</title>" msgstr "" #. Tag: para -#: hardware.xml:707 +#: hardware.xml:697 #, no-c-format msgid "Both AMD64 and Intel EM64T processors are supported." msgstr "" #. Tag: para -#: hardware.xml:735 +#: hardware.xml:725 #, no-c-format msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard Debian distribution only supports installation on a number of the most common platforms. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU." msgstr "" #. Tag: para -#: hardware.xml:744 +#: hardware.xml:734 #, no-c-format msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems." msgstr "" #. Tag: para -#: hardware.xml:752 +#: hardware.xml:742 #, no-c-format msgid "The supported platforms are:" msgstr "" #. Tag: term -#: hardware.xml:759 +#: hardware.xml:749 #, no-c-format msgid "Netwinder" msgstr "" #. Tag: para -#: hardware.xml:760 +#: hardware.xml:750 #, no-c-format msgid "This is actually the name for the group of machines based upon the StrongARM 110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff)." msgstr "" #. Tag: term -#: hardware.xml:773 +#: hardware.xml:763 #, no-c-format msgid "IOP32x" msgstr "" #. Tag: para -#: hardware.xml:774 +#: hardware.xml:764 #, no-c-format msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. Debian currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. Debian explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>." msgstr "" #. Tag: term -#: hardware.xml:787 +#: hardware.xml:777 #, no-c-format msgid "IXP4xx" msgstr "" #. Tag: para -#: hardware.xml:788 +#: hardware.xml:778 #, no-c-format msgid "The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected. There is an external site with <ulink url=\"&url-arm-cyrius-nslu2;\">installation instructions</ulink>." msgstr "" -#. Tag: term -#: hardware.xml:802 -#, no-c-format -msgid "<term>RiscPC</term>" -msgstr "" - #. Tag: para -#: hardware.xml:803 -#, no-c-format -msgid "This machine is the oldest supported hardware but support for it in our new installer is incomplete. It has RISC OS in ROM, Linux can be booted from that OS using linloader. The RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA video, parallel port, single serial port, PS/2 keyboard and proprietary mouse port. The proprietary module expansion bus allows for up to eight expansion cards to be fitted depending on configuration, several of these modules have Linux drivers." -msgstr "" - -#. Tag: para -#: hardware.xml:829 +#: hardware.xml:802 #, no-c-format msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future." msgstr "" #. Tag: para -#: hardware.xml:857 +#: hardware.xml:830 #, no-c-format msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon." msgstr "" #. Tag: para -#: hardware.xml:865 +#: hardware.xml:838 #, no-c-format msgid "If your system has a 64-bit processor from the AMD64 or Intel EM64T families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture." msgstr "" #. Tag: para -#: hardware.xml:872 +#: hardware.xml:845 #, no-c-format msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of Debian<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para> </footnote>." msgstr "" #. Tag: title -#: hardware.xml:909 +#: hardware.xml:882 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:910 +#: hardware.xml:883 #, 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." msgstr "" #. Tag: para -#: hardware.xml:934 +#: hardware.xml:907 #, 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:941 +#: hardware.xml:914 #, 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:949 +#: hardware.xml:922 #, 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:976 +#: hardware.xml:949 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1017 +#: hardware.xml:990 #, 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:1027 +#: hardware.xml:1000 #, 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:1044 +#: hardware.xml:1017 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: title -#: hardware.xml:1084 +#: hardware.xml:1057 #, no-c-format msgid "CPU/Machine types" msgstr "" #. Tag: para -#: hardware.xml:1086 +#: hardware.xml:1059 #, no-c-format msgid "Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by the Debian installation system on little endian MIPS. The Debian installation system works on the following machines:" msgstr "" #. Tag: entry -#: hardware.xml:1098 +#: hardware.xml:1071 #, no-c-format msgid "System Type" msgstr "" #. Tag: entry -#: hardware.xml:1098 +#: hardware.xml:1071 #, no-c-format msgid "<entry>CPU</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1098 +#: hardware.xml:1071 #, no-c-format msgid "Code-name" msgstr "" #. Tag: entry -#: hardware.xml:1099 +#: hardware.xml:1072 #, no-c-format msgid "Debian subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1105 +#: hardware.xml:1078 #, no-c-format msgid "DECstation 5000/1xx" msgstr "" #. Tag: entry -#: hardware.xml:1106 hardware.xml:1116 hardware.xml:1121 hardware.xml:1131 +#: hardware.xml:1079 hardware.xml:1089 hardware.xml:1094 hardware.xml:1104 #, no-c-format msgid "R3000" msgstr "" #. Tag: entry -#: hardware.xml:1107 hardware.xml:1112 +#: hardware.xml:1080 hardware.xml:1085 #, no-c-format msgid "3MIN" msgstr "" #. Tag: entry -#: hardware.xml:1110 +#: hardware.xml:1083 #, no-c-format msgid "DECstation 5000/150" msgstr "" #. Tag: entry -#: hardware.xml:1111 hardware.xml:1136 +#: hardware.xml:1084 hardware.xml:1109 #, no-c-format msgid "R4000" msgstr "" #. Tag: entry -#: hardware.xml:1115 +#: hardware.xml:1088 #, no-c-format msgid "DECstation 5000/200" msgstr "" #. Tag: entry -#: hardware.xml:1117 +#: hardware.xml:1090 #, no-c-format msgid "3MAX" msgstr "" #. Tag: entry -#: hardware.xml:1120 +#: hardware.xml:1093 #, no-c-format msgid "DECstation 5000/240" msgstr "" #. Tag: entry -#: hardware.xml:1122 hardware.xml:1127 +#: hardware.xml:1095 hardware.xml:1100 #, no-c-format msgid "3MAX+" msgstr "" #. Tag: entry -#: hardware.xml:1125 +#: hardware.xml:1098 #, no-c-format msgid "DECstation 5000/260" msgstr "" #. Tag: entry -#: hardware.xml:1126 +#: hardware.xml:1099 #, no-c-format msgid "R4400" msgstr "" #. Tag: entry -#: hardware.xml:1130 +#: hardware.xml:1103 #, no-c-format msgid "Personal DECstation 5000/xx" msgstr "" #. Tag: entry -#: hardware.xml:1132 hardware.xml:1137 +#: hardware.xml:1105 hardware.xml:1110 #, no-c-format msgid "Maxine" msgstr "" #. Tag: entry -#: hardware.xml:1135 +#: hardware.xml:1108 #, no-c-format msgid "Personal DECstation 5000/50" msgstr "" #. Tag: para -#: hardware.xml:1142 +#: hardware.xml:1115 #, no-c-format msgid "All Cobalt machines are supported. In the past, only machines with a serial console were supported (that is, all machines except for the Qube 2700, aka Qube1). However, installations are now also possible through SSH." msgstr "" #. Tag: para -#: hardware.xml:1149 +#: hardware.xml:1122 #, 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:1159 +#: hardware.xml:1132 #, no-c-format msgid "Supported console options" msgstr "" #. Tag: para -#: hardware.xml:1160 +#: hardware.xml:1133 #, no-c-format msgid "A serial console is available on all supported DECstations (9600 bps, 8N1). To use the serial console, you have to boot the installer image with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter (with <replaceable>x</replaceable> being the number of the serial port you have your terminal connected to — usually <literal>2</literal>, but <literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available with the PMAG-BA and the PMAGB-B graphics options." msgstr "" #. Tag: para -#: hardware.xml:1171 +#: hardware.xml:1144 #, no-c-format msgid "" "If you have a Linux system to use as serial terminal, an easy way is to run <command>cu</command><footnote> <para> In Woody this command was part of the <classname>uucp</classname> package, but in later releases it is available as a separate package. </para> </footnote> on it. Example: <informalexample><screen>\n" @@ -1968,1321 +1932,1291 @@ msgid "" msgstr "" #. Tag: para -#: hardware.xml:1189 +#: hardware.xml:1162 #, no-c-format msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps." msgstr "" #. Tag: para -#: hardware.xml:1203 +#: hardware.xml:1176 #, 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:1211 +#: hardware.xml:1184 #, 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:1219 +#: hardware.xml:1192 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:1221 +#: hardware.xml:1194 #, no-c-format msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:1228 +#: hardware.xml:1201 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:1229 +#: hardware.xml:1202 #, 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:1239 +#: hardware.xml:1212 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:1240 +#: hardware.xml:1213 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:1244 +#: hardware.xml:1217 #, 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:1250 +#: hardware.xml:1223 #, 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:1255 +#: hardware.xml:1228 #, 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:1264 +#: hardware.xml:1237 #, no-c-format msgid "<term>prep</term>" msgstr "" #. Tag: para -#: hardware.xml:1265 +#: hardware.xml:1238 #, no-c-format msgid "This kernel flavour supports the PReP subarchitecture." msgstr "" #. Tag: term -#: hardware.xml:1273 +#: hardware.xml:1246 #, no-c-format msgid "apus" msgstr "" #. Tag: para -#: hardware.xml:1274 +#: hardware.xml:1247 #, no-c-format msgid "This kernel flavour supports the Amiga Power-UP System, though it is currently disabled." msgstr "" #. Tag: title -#: hardware.xml:1287 +#: hardware.xml:1260 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:1289 +#: hardware.xml:1262 #, 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:1296 +#: hardware.xml:1269 #, 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:1304 +#: hardware.xml:1277 #, 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:1312 +#: hardware.xml:1285 #, 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:1328 hardware.xml:1463 hardware.xml:1507 hardware.xml:1536 +#: hardware.xml:1301 hardware.xml:1436 hardware.xml:1480 hardware.xml:1509 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:1329 +#: hardware.xml:1302 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:1335 +#: hardware.xml:1308 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:1336 +#: hardware.xml:1309 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:1337 hardware.xml:1340 hardware.xml:1343 hardware.xml:1346 hardware.xml:1349 hardware.xml:1352 hardware.xml:1355 hardware.xml:1358 hardware.xml:1361 hardware.xml:1364 hardware.xml:1367 hardware.xml:1370 hardware.xml:1373 hardware.xml:1376 hardware.xml:1379 hardware.xml:1382 +#: hardware.xml:1310 hardware.xml:1313 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:1352 hardware.xml:1355 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:1339 +#: hardware.xml:1312 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:1342 +#: hardware.xml:1315 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:1345 +#: hardware.xml:1318 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:1348 +#: hardware.xml:1321 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:1351 +#: hardware.xml:1324 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:1354 +#: hardware.xml:1327 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:1357 +#: hardware.xml:1330 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:1360 +#: hardware.xml:1333 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:1363 +#: hardware.xml:1336 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:1366 +#: hardware.xml:1339 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:1369 +#: hardware.xml:1342 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:1372 +#: hardware.xml:1345 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:1375 +#: hardware.xml:1348 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:1378 +#: hardware.xml:1351 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:1381 +#: hardware.xml:1354 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:1384 +#: hardware.xml:1357 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:1385 hardware.xml:1388 hardware.xml:1391 hardware.xml:1394 hardware.xml:1397 hardware.xml:1400 hardware.xml:1403 hardware.xml:1406 hardware.xml:1409 hardware.xml:1412 hardware.xml:1415 hardware.xml:1418 hardware.xml:1424 hardware.xml:1427 hardware.xml:1433 hardware.xml:1439 hardware.xml:1445 +#: hardware.xml:1358 hardware.xml:1361 hardware.xml:1364 hardware.xml:1367 hardware.xml:1370 hardware.xml:1373 hardware.xml:1376 hardware.xml:1379 hardware.xml:1382 hardware.xml:1385 hardware.xml:1388 hardware.xml:1391 hardware.xml:1397 hardware.xml:1400 hardware.xml:1406 hardware.xml:1412 hardware.xml:1418 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:1387 +#: hardware.xml:1360 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:1390 +#: hardware.xml:1363 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:1393 +#: hardware.xml:1366 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:1396 +#: hardware.xml:1369 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:1399 +#: hardware.xml:1372 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:1402 +#: hardware.xml:1375 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:1405 +#: hardware.xml:1378 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:1408 +#: hardware.xml:1381 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:1411 +#: hardware.xml:1384 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:1414 +#: hardware.xml:1387 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:1417 +#: hardware.xml:1390 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:1422 +#: hardware.xml:1395 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:1423 +#: hardware.xml:1396 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:1426 +#: hardware.xml:1399 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:1431 +#: hardware.xml:1404 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:1432 +#: hardware.xml:1405 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:1437 +#: hardware.xml:1410 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1438 +#: hardware.xml:1411 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:1443 hardware.xml:1469 +#: hardware.xml:1416 hardware.xml:1442 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:1444 +#: hardware.xml:1417 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:1453 +#: hardware.xml:1426 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1470 +#: hardware.xml:1443 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:1472 +#: hardware.xml:1445 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:1474 +#: hardware.xml:1447 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:1476 +#: hardware.xml:1449 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:1478 +#: hardware.xml:1451 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:1482 hardware.xml:1513 +#: hardware.xml:1455 hardware.xml:1486 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:1483 +#: hardware.xml:1456 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:1485 +#: hardware.xml:1458 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:1487 +#: hardware.xml:1460 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:1489 +#: hardware.xml:1462 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:1497 +#: hardware.xml:1470 #, no-c-format msgid "CHRP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1514 +#: hardware.xml:1487 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:1517 +#: hardware.xml:1490 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:1518 +#: hardware.xml:1491 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: title -#: hardware.xml:1526 +#: hardware.xml:1499 #, no-c-format msgid "APUS subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1542 +#: hardware.xml:1515 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:1543 +#: hardware.xml:1516 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:1551 +#: hardware.xml:1524 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:1553 +#: hardware.xml:1526 #, 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:1590 +#: hardware.xml:1563 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:1592 +#: hardware.xml:1565 #, 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:1601 +#: hardware.xml:1574 #, 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:1609 +#: hardware.xml:1582 #, 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:1625 +#: hardware.xml:1598 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "" #. Tag: para -#: hardware.xml:1626 +#: hardware.xml:1599 #, 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:1648 +#: hardware.xml:1621 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para -#: hardware.xml:1649 +#: hardware.xml:1622 #, 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:1660 -#, no-c-format -msgid "sun4, sun4c, sun4d" -msgstr "" - -#. Tag: para -#: hardware.xml:1662 -#, no-c-format -msgid "These subarchitectures include some very old 32-bit machines, which are no longer supported. For a complete list please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>." -msgstr "" - -#. Tag: term -#: hardware.xml:1673 -#, no-c-format -msgid "<term>sun4m</term>" -msgstr "" - -#. Tag: para -#: hardware.xml:1675 -#, no-c-format -msgid "sun4m is the only 32-bit subarchitecture (sparc32) that is currently supported. The most popular machines belonging to this class are Sparcstation 4, 5, 10 and 20." -msgstr "" - -#. Tag: para -#: hardware.xml:1681 -#, no-c-format -msgid "Note that symmetric multiprocessing (SMP) — the ability to run processes on multiple processors — is not supported on this hardware, due to stability problems with such configurations. The available uniprocessor (UP) sparc32 kernel will boot fine on multiprocessor machines, although it will activate and use only the first CPU." -msgstr "" - -#. Tag: term -#: hardware.xml:1693 +#: hardware.xml:1633 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "" #. Tag: para -#: hardware.xml:1695 +#: hardware.xml:1635 #, 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:1702 +#: hardware.xml:1642 #, 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:1712 +#: hardware.xml:1652 #, no-c-format msgid "<term>sun4u</term>" msgstr "" #. Tag: para -#: hardware.xml:1714 +#: hardware.xml:1654 #, 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:1727 +#: hardware.xml:1667 #, no-c-format msgid "<term>sun4v</term>" msgstr "" #. Tag: para -#: hardware.xml:1729 +#: hardware.xml:1669 #, 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:1740 +#: hardware.xml:1680 #, 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:1749 +#: hardware.xml:1689 #, no-c-format msgid "Graphics Card Support" msgstr "" #. Tag: para -#: hardware.xml:1750 +#: hardware.xml:1690 #, 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:1758 +#: hardware.xml:1698 #, 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:1767 +#: hardware.xml:1707 #, 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:1776 +#: hardware.xml:1716 #, no-c-format msgid "The X.Org X Window System is supported on some DECstation models. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: para -#: hardware.xml:1784 +#: hardware.xml:1724 #, 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:1794 +#: hardware.xml:1734 #, 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:1811 +#: hardware.xml:1751 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1812 +#: hardware.xml:1752 #, 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:1823 hardware.xml:1845 hardware.xml:1865 hardware.xml:1888 +#: hardware.xml:1763 hardware.xml:1785 hardware.xml:1805 hardware.xml:1828 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1824 +#: hardware.xml:1764 #, 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:1832 +#: hardware.xml:1772 #, 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:1847 +#: hardware.xml:1787 #, 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:1856 +#: hardware.xml:1796 #, 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:1866 +#: hardware.xml:1806 #, 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:1875 +#: hardware.xml:1815 #, 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:1889 +#: hardware.xml:1829 #, 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:1899 +#: hardware.xml:1839 #, 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:1905 +#: hardware.xml:1845 #, 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:1922 +#: hardware.xml:1862 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:1924 +#: hardware.xml:1864 #, 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:1935 +#: hardware.xml:1875 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:1936 +#: hardware.xml:1876 #, 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:1942 +#: hardware.xml:1882 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:1949 +#: hardware.xml:1889 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:1951 +#: hardware.xml:1891 #, 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:1958 +#: hardware.xml:1898 #, 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:1970 +#: hardware.xml:1910 #, no-c-format msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the boot disks (such as Mitsumi and Matsushita drives). However, these models might require special boot parameters or other massaging to get them to work, and booting off these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux." msgstr "" #. Tag: para -#: hardware.xml:1980 +#: hardware.xml:1920 #, 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:1985 +#: hardware.xml:1925 #, 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:1994 +#: hardware.xml:1934 #, no-c-format -msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines. <phrase condition=\"etch\">On RiscPCs, SCSI CD-ROMs are also supported.</phrase>" +msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines." msgstr "" #. Tag: para -#: hardware.xml:1999 +#: hardware.xml:1938 #, no-c-format msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card." msgstr "" #. Tag: para -#: hardware.xml:2014 +#: hardware.xml:1953 #, no-c-format msgid "On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position." msgstr "" #. Tag: para -#: hardware.xml:2023 +#: hardware.xml:1962 #, no-c-format msgid "CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal DECstation 5000/50)." msgstr "" #. Tag: para -#: hardware.xml:2032 +#: hardware.xml:1971 #, no-c-format msgid "To boot from CD, issue the command <userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware prompt, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot (3 on most DECstations) and <replaceable>id</replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" #. Tag: userinput -#: hardware.xml:2044 +#: hardware.xml:1983 #, no-c-format msgid "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=value1 param2=value2 ..." msgstr "" #. Tag: title -#: hardware.xml:2051 +#: hardware.xml:1990 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:2053 +#: hardware.xml:1992 #, 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:2059 +#: hardware.xml:1998 #, 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:2064 +#: hardware.xml:2003 #, 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:2072 +#: hardware.xml:2011 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:2074 +#: hardware.xml:2013 #, 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:2086 +#: hardware.xml:2025 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:2088 +#: hardware.xml:2027 #, 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:2098 +#: hardware.xml:2037 #, 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:2104 +#: hardware.xml:2043 #, 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:2112 +#: hardware.xml:2051 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:2114 +#: hardware.xml:2053 #, 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:2126 +#: hardware.xml:2065 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:2128 +#: hardware.xml:2067 #, 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:2138 +#: hardware.xml:2077 #, no-c-format msgid "Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." msgstr "" #. Tag: para -#: hardware.xml:2145 +#: hardware.xml:2084 #, no-c-format msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or ATA — are supported. Very old 8–bit hard disk controllers used in the IBM XT computer are supported only as a module. SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." msgstr "" #. Tag: para -#: hardware.xml:2155 +#: hardware.xml:2094 #, 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:2165 +#: hardware.xml:2104 #, 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:2198 +#: hardware.xml:2137 #, 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:2207 +#: hardware.xml:2146 #, 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:2213 +#: hardware.xml:2152 #, 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:2219 +#: hardware.xml:2158 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:2224 +#: hardware.xml:2163 #, 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:2241 +#: hardware.xml:2180 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:2242 +#: hardware.xml:2181 #, 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:2248 +#: hardware.xml:2187 #, 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:2254 +#: hardware.xml:2193 #, 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:2260 +#: hardware.xml:2199 #, 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:2266 +#: hardware.xml:2205 #, 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:2272 +#: hardware.xml:2211 #, 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:2282 +#: hardware.xml:2221 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" #. Tag: para -#: hardware.xml:2284 +#: hardware.xml:2223 #, 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:2292 +#: hardware.xml:2231 #, 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:2297 +#: hardware.xml:2236 #, 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:2305 +#: hardware.xml:2244 #, 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:2316 +#: hardware.xml:2255 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:2317 +#: hardware.xml:2256 #, 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:2324 +#: hardware.xml:2263 #, 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:2335 +#: hardware.xml:2274 #, 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:2347 +#: hardware.xml:2286 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:2348 +#: hardware.xml:2287 #, 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:2361 +#: hardware.xml:2300 #, 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:2382 +#: hardware.xml:2321 #, 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:2399 +#: hardware.xml:2338 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:2401 +#: hardware.xml:2340 #, no-c-format msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. Note that these are really bare-minimum numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>." msgstr "" #. Tag: para -#: hardware.xml:2407 +#: hardware.xml:2346 #, 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:2416 +#: hardware.xml:2355 #, 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:2424 +#: hardware.xml:2363 #, 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:2434 +#: hardware.xml:2373 #, no-c-format msgid "FIXME: is this still true?" msgstr "" #. Tag: title -#: hardware.xml:2445 +#: hardware.xml:2384 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:2446 +#: hardware.xml:2385 #, 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:2458 +#: hardware.xml:2397 #, 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:2464 +#: hardware.xml:2403 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:2469 +#: hardware.xml:2408 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:2474 +#: hardware.xml:2413 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:2479 +#: hardware.xml:2418 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:2484 +#: hardware.xml:2423 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:2491 +#: hardware.xml:2430 #, no-c-format msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work." msgstr "" #. Tag: para -#: hardware.xml:2497 +#: hardware.xml:2436 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:2502 +#: hardware.xml:2441 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:2507 +#: hardware.xml:2446 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:2512 +#: hardware.xml:2451 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:2521 +#: hardware.xml:2460 #, 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:2531 +#: hardware.xml:2470 #, 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:2540 +#: hardware.xml:2479 #, no-c-format msgid "Drivers Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:2541 +#: hardware.xml:2480 #, 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:2547 +#: hardware.xml:2486 #, 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:2558 +#: hardware.xml:2497 #, 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:2570 +#: hardware.xml:2509 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:2571 +#: hardware.xml:2510 #, 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:2578 +#: hardware.xml:2517 #, 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:2584 +#: hardware.xml:2523 #, 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:2598 +#: hardware.xml:2537 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:2599 +#: hardware.xml:2538 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:2606 +#: hardware.xml:2545 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:2608 +#: hardware.xml:2547 #, 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:2618 +#: hardware.xml:2557 #, 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:2626 +#: hardware.xml:2565 #, 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:2639 +#: hardware.xml:2578 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:2641 +#: hardware.xml:2580 #, 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 7811fb121..0e61e1da0 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: 2007-02-28 20:57+0000\n" +"POT-Creation-Date: 2007-10-22 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" @@ -107,137 +107,125 @@ msgstr "" #. Tag: title #: install-methods.xml:152 #, no-c-format -msgid "RiscPC Installation Files" -msgstr "" - -#. Tag: para -#: install-methods.xml:153 -#, no-c-format -msgid "The RiscPC installer is booted initially from RISC OS. All the necessary files are provided in one Zip archive, &rpc-install-kit;. Download this file onto the RISC OS machine, copy the <filename>linloader.!Boot</filename> components into place, and run <filename>!dInstall</filename>." -msgstr "" - -#. Tag: title -#: install-methods.xml:165 -#, no-c-format msgid "Netwinder Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:166 +#: install-methods.xml:153 #, 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:175 +#: install-methods.xml:162 #, no-c-format msgid "CATS Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:176 +#: install-methods.xml:163 #, 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:185 +#: install-methods.xml:172 #, no-c-format msgid "NSLU2 Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:186 +#: install-methods.xml:173 #, no-c-format msgid "A firmware image is provided for the Linksys NSLU2 which will automatically boot <classname>debian-installer</classname>. This firmware image can be obtained from &nslu2-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:232 +#: install-methods.xml:219 #, no-c-format msgid "Choosing a Kernel" msgstr "" #. Tag: para -#: install-methods.xml:234 +#: install-methods.xml:221 #, 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:243 +#: install-methods.xml:230 #, 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:261 +#: install-methods.xml:248 #, no-c-format msgid "Creating an IPL tape" msgstr "" #. Tag: para -#: install-methods.xml:263 +#: install-methods.xml:250 #, 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:287 +#: install-methods.xml:274 #, no-c-format msgid "Creating Floppies from Disk Images" msgstr "" #. Tag: para -#: install-methods.xml:288 +#: install-methods.xml:275 #, 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:293 +#: install-methods.xml:280 #, no-c-format msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives." msgstr "" #. Tag: para -#: install-methods.xml:298 +#: install-methods.xml:285 #, no-c-format msgid "Booting the installer from floppy disk is not supported on Amigas or 68k Macs." msgstr "" #. Tag: para -#: install-methods.xml:303 +#: install-methods.xml:290 #, 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:314 +#: install-methods.xml:301 #, 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:320 +#: install-methods.xml:307 #, 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:328 +#: install-methods.xml:315 #, 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:336 +#: install-methods.xml:323 #, no-c-format msgid "Writing Disk Images From a Linux or Unix System" msgstr "" #. Tag: para -#: install-methods.xml:337 +#: install-methods.xml:324 #, 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" @@ -246,253 +234,253 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:358 +#: install-methods.xml:345 #, 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:379 +#: install-methods.xml:366 #, 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:397 +#: install-methods.xml:384 #, no-c-format msgid "Writing Disk Images From DOS, Windows, or OS/2" msgstr "" #. Tag: para -#: install-methods.xml:399 +#: install-methods.xml:386 #, 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:404 +#: install-methods.xml:391 #, 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:412 +#: install-methods.xml:399 #, 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:418 +#: install-methods.xml:405 #, 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:431 +#: install-methods.xml:418 #, no-c-format msgid "Writing Disk Images on Atari Systems" msgstr "" #. Tag: para -#: install-methods.xml:432 +#: install-methods.xml:419 #, 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:443 +#: install-methods.xml:430 #, no-c-format msgid "Writing Disk Images on Macintosh Systems" msgstr "" #. Tag: para -#: install-methods.xml:444 +#: install-methods.xml:431 #, 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:460 +#: install-methods.xml:447 #, no-c-format msgid "Writing Disk Images From MacOS" msgstr "" #. Tag: para -#: install-methods.xml:461 +#: install-methods.xml:448 #, 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:472 +#: install-methods.xml:459 #, 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:483 +#: install-methods.xml:470 #, no-c-format msgid "Writing Disk Images with <command>Disk Copy</command>" msgstr "" #. Tag: para -#: install-methods.xml:484 +#: install-methods.xml:471 #, 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:493 +#: install-methods.xml:480 #, 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:500 +#: install-methods.xml:487 #, 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:507 +#: install-methods.xml:494 #, 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:516 +#: install-methods.xml:503 #, 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:523 +#: install-methods.xml:510 #, 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:538 +#: install-methods.xml:525 #, no-c-format msgid "Writing Disk Images with <command>suntar</command>" msgstr "" #. Tag: para -#: install-methods.xml:542 +#: install-methods.xml:529 #, 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:550 +#: install-methods.xml:537 #, no-c-format msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)." msgstr "" #. Tag: para -#: install-methods.xml:556 +#: install-methods.xml:543 #, no-c-format msgid "Select the <filename>root.bin</filename> file in the file-opening dialog." msgstr "" #. Tag: para -#: install-methods.xml:561 +#: install-methods.xml:548 #, 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:569 +#: install-methods.xml:556 #, 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:588 +#: install-methods.xml:575 #, no-c-format msgid "Preparing Files for USB Memory Stick Booting" msgstr "" #. Tag: para -#: install-methods.xml:590 +#: install-methods.xml:577 #, 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:600 +#: install-methods.xml:587 #, 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:608 +#: install-methods.xml:595 #, no-c-format msgid "Copying the files — the easy way" msgstr "" #. Tag: para -#: install-methods.xml:609 +#: install-methods.xml:596 #, 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:616 +#: install-methods.xml:603 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sda</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:618 +#: install-methods.xml:605 #, 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:627 +#: install-methods.xml:614 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sda2</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:630 +#: install-methods.xml:617 #, 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:636 +#: install-methods.xml:623 #, 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:652 +#: install-methods.xml:639 #, no-c-format msgid "Copying the files — the flexible way" msgstr "" #. Tag: para -#: install-methods.xml:653 +#: install-methods.xml:640 #, 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:665 install-methods.xml:754 +#: install-methods.xml:652 install-methods.xml:741 #, no-c-format msgid "USB stick partitioning on &arch-title;" msgstr "" #. Tag: para -#: install-methods.xml:666 +#: install-methods.xml:653 #, 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:671 +#: install-methods.xml:658 #, 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" @@ -501,13 +489,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:685 +#: install-methods.xml:672 #, 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:695 +#: install-methods.xml:682 #, 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" @@ -516,19 +504,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:708 +#: install-methods.xml:695 #, 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:739 +#: install-methods.xml:726 #, no-c-format msgid "The <filename>syslinux.cfg</filename> configuration file should contain the following two lines:" msgstr "" #. Tag: screen -#: install-methods.xml:744 +#: install-methods.xml:731 #, no-c-format msgid "" "default vmlinuz\n" @@ -536,7 +524,7 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:755 +#: install-methods.xml:742 #, 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" @@ -545,13 +533,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:771 +#: install-methods.xml:758 #, 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:780 +#: install-methods.xml:767 #, 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" @@ -564,43 +552,43 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:796 +#: install-methods.xml:783 #, 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:802 +#: install-methods.xml:789 #, no-c-format msgid "<filename>vmlinux</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:807 +#: install-methods.xml:794 #, no-c-format msgid "<filename>initrd.gz</filename> (initial ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:812 +#: install-methods.xml:799 #, no-c-format msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" msgstr "" #. Tag: para -#: install-methods.xml:817 +#: install-methods.xml:804 #, no-c-format msgid "<filename>boot.msg</filename> (optional boot message)" msgstr "" #. Tag: para -#: install-methods.xml:822 +#: install-methods.xml:809 #, no-c-format msgid "Optional kernel modules" msgstr "" #. Tag: para -#: install-methods.xml:829 +#: install-methods.xml:816 #, no-c-format msgid "" "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n" @@ -618,283 +606,283 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:846 +#: install-methods.xml:833 #, no-c-format msgid "Adding an ISO image" msgstr "" #. Tag: para -#: install-methods.xml:847 +#: install-methods.xml:834 #, 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:855 +#: install-methods.xml:842 #, 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:864 +#: install-methods.xml:851 #, 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:874 +#: install-methods.xml:861 #, no-c-format msgid "Booting the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:875 +#: install-methods.xml:862 #, 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:882 +#: install-methods.xml:869 #, no-c-format msgid "# install-mbr /dev/<replaceable>sda</replaceable>" msgstr "" #. Tag: title -#: install-methods.xml:893 +#: install-methods.xml:880 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "" #. Tag: para -#: install-methods.xml:894 +#: install-methods.xml:881 #, 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:900 +#: install-methods.xml:887 #, 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:907 +#: install-methods.xml:894 #, no-c-format msgid "The installer cannot boot from files on an NTFS file system." msgstr "" #. Tag: para -#: install-methods.xml:911 +#: install-methods.xml:898 #, 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:922 +#: install-methods.xml:909 #, 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:931 +#: install-methods.xml:918 #, no-c-format msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: install-methods.xml:933 +#: install-methods.xml:920 #, 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:939 +#: install-methods.xml:926 #, 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:945 +#: install-methods.xml:932 #, 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:952 +#: install-methods.xml:939 #, no-c-format msgid "<filename>vmlinuz</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:957 +#: install-methods.xml:944 #, no-c-format msgid "<filename>initrd.gz</filename> (ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:964 +#: install-methods.xml:951 #, no-c-format msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>." msgstr "" #. Tag: title -#: install-methods.xml:974 +#: install-methods.xml:961 #, no-c-format msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:975 +#: install-methods.xml:962 #, 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:988 +#: install-methods.xml:975 #, 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:1008 +#: install-methods.xml:995 #, no-c-format msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1009 +#: install-methods.xml:996 #, 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:1020 +#: install-methods.xml:1007 #, 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:1030 +#: install-methods.xml:1017 #, no-c-format msgid "vmlinux" msgstr "" #. Tag: filename -#: install-methods.xml:1035 +#: install-methods.xml:1022 #, no-c-format msgid "initrd.gz" msgstr "" #. Tag: filename -#: install-methods.xml:1040 +#: install-methods.xml:1027 #, no-c-format msgid "yaboot" msgstr "" #. Tag: filename -#: install-methods.xml:1045 +#: install-methods.xml:1032 #, no-c-format msgid "yaboot.conf" msgstr "" #. Tag: para -#: install-methods.xml:1050 +#: install-methods.xml:1037 #, 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:1058 +#: install-methods.xml:1045 #, no-c-format msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1071 +#: install-methods.xml:1058 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "" #. Tag: para -#: install-methods.xml:1072 +#: install-methods.xml:1059 #, 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:1080 +#: install-methods.xml:1067 #, 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:1087 +#: install-methods.xml:1074 #, 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:1104 +#: install-methods.xml:1091 #, 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:1110 +#: install-methods.xml:1097 #, 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:1127 +#: install-methods.xml:1114 #, 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:1132 +#: install-methods.xml:1119 #, 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:1140 +#: install-methods.xml:1127 #, 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:1158 +#: install-methods.xml:1145 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para -#: install-methods.xml:1159 +#: install-methods.xml:1146 #, 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:1171 +#: install-methods.xml:1158 #, 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:1193 +#: install-methods.xml:1180 #, no-c-format msgid "Setting up a BOOTP server" msgstr "" #. Tag: para -#: install-methods.xml:1194 +#: install-methods.xml:1181 #, 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:1202 +#: install-methods.xml:1189 #, 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" @@ -911,25 +899,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1235 +#: install-methods.xml:1222 #, 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:1256 +#: install-methods.xml:1243 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1257 +#: install-methods.xml:1244 #, 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:1264 +#: install-methods.xml:1251 #, no-c-format msgid "" "option domain-name \"example.com\";\n" @@ -954,25 +942,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1266 +#: install-methods.xml:1253 #, 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:1276 +#: install-methods.xml:1263 #, 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:1284 +#: install-methods.xml:1271 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1285 +#: install-methods.xml:1272 #, 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" @@ -1007,13 +995,13 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1301 +#: install-methods.xml:1288 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1302 +#: install-methods.xml:1289 #, 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" @@ -1022,19 +1010,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1314 +#: install-methods.xml:1301 #, 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:1324 +#: install-methods.xml:1311 #, 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> The <userinput>-l</userinput> argument enables some versions of <command>in.tftpd</command> to log all requests to the system logs; this is useful for diagnosing boot errors. </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:1342 +#: install-methods.xml:1329 #, 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" @@ -1045,85 +1033,85 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1364 +#: install-methods.xml:1351 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1365 +#: install-methods.xml:1352 #, 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:1374 +#: install-methods.xml:1361 #, no-c-format msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP directory." msgstr "" #. Tag: para -#: install-methods.xml:1383 +#: install-methods.xml:1370 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: para -#: install-methods.xml:1391 +#: install-methods.xml:1378 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: title -#: install-methods.xml:1403 +#: install-methods.xml:1390 #, no-c-format msgid "DECstation TFTP Images" msgstr "" #. Tag: para -#: install-methods.xml:1404 +#: install-methods.xml:1391 #, no-c-format msgid "For DECstations, there are tftpimage files for each subarchitecture, which contain both kernel and installer in one file. The naming convention is <filename><replaceable>subarchitecture</replaceable>/netboot-boot.img</filename>. Copy the tftpimage file you would like to use to <userinput>/tftpboot/tftpboot.img</userinput> if you work with the example BOOTP/DHCP setups described above." msgstr "" #. Tag: para -#: install-methods.xml:1414 +#: install-methods.xml:1401 #, no-c-format msgid "The DECstation firmware boots by TFTP with the command <userinput>boot <replaceable>#</replaceable>/tftp</userinput>, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot. On most DECstations this is <quote>3</quote>. If the BOOTP/DHCP server does not supply the filename or you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" #. Tag: userinput -#: install-methods.xml:1426 +#: install-methods.xml:1413 #, no-c-format msgid "boot #/tftp/filename param1=value1 param2=value2 ..." msgstr "" #. Tag: para -#: install-methods.xml:1428 +#: install-methods.xml:1415 #, no-c-format msgid "Several DECstation firmware revisions show a problem with regard to net booting: the transfer starts, but after some time it stops with an <computeroutput>a.out err</computeroutput>. This can have several reasons: <orderedlist> <listitem><para> The firmware does not respond to ARP requests during a TFTP transfer. This leads to an ARP timeout and the transfer stops. The solution is to add the MAC address of the Ethernet card in the DECstation statically to the ARP table of the TFTP server. This is done by running <userinput>arp -s <replaceable>IP-address</replaceable> <replaceable>MAC-address</replaceable></userinput> as root on the machine acting as TFTP server. The MAC-address of the DECstation can be read out by entering <command>cnfg</command> at the DECstation firmware prompt. </para></listitem> <listitem><para> The firmware has a size limit on the files that can be booted by TFTP. </para></listitem> </orderedlist> There are also firmware revisions that cannot boot via TFTP at all. An overview about the different firmware revisions can be found at the NetBSD web pages: <ulink url=\"http://www.netbsd.org/Ports/pmax/board-list.html#proms\"></ulink>." msgstr "" #. Tag: title -#: install-methods.xml:1466 +#: install-methods.xml:1453 #, no-c-format msgid "Alpha TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1467 +#: install-methods.xml:1454 #, no-c-format msgid "On Alpha, you must specify the filename (as a relative path to the boot image directory) using the <userinput>-file</userinput> argument to the SRM <userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</userinput> environment variable. Alternatively, the filename can be given via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</userinput> directive). Unlike Open Firmware, there is <emphasis>no default filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a filename by either one of these methods." msgstr "" #. Tag: title -#: install-methods.xml:1482 +#: install-methods.xml:1469 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1483 +#: install-methods.xml:1470 #, no-c-format msgid "" "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n" @@ -1132,85 +1120,85 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1499 +#: install-methods.xml:1486 #, 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:1506 +#: install-methods.xml:1493 #, 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:1517 +#: install-methods.xml:1504 #, no-c-format msgid "BVM/Motorola TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1518 +#: install-methods.xml:1505 #, 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:1523 +#: install-methods.xml:1510 #, 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:1535 +#: install-methods.xml:1522 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1536 +#: install-methods.xml:1523 #, 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:1548 +#: install-methods.xml:1535 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1549 +#: install-methods.xml:1536 #, 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:1654 +#: install-methods.xml:1641 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1655 +#: install-methods.xml:1642 #, 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:1668 +#: install-methods.xml:1655 #, no-c-format msgid "Automatic Installation Using the Debian Installer" msgstr "" #. Tag: para -#: install-methods.xml:1669 +#: install-methods.xml:1656 #, 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:1676 +#: install-methods.xml:1663 #, 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/preseed.pot b/po/pot/preseed.pot index a75a25fd5..a5d2b690c 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: 2007-09-16 00:09+0000\n" +"POT-Creation-Date: 2007-10-22 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" @@ -837,9 +837,8 @@ msgstr "" #, no-c-format msgid "" "# If you select ftp, the mirror/country string does not need to be set.\n" - "#d-i mirror/protocol string ftp<phrase condition=\"etch\">\n" - "d-i mirror/country string enter information manually</phrase><phrase condition=\"lenny\">\n" - "d-i mirror/country string manual</phrase>\n" + "#d-i mirror/protocol string ftp\n" + "d-i mirror/country string manual\n" "d-i mirror/http/hostname string &archive-mirror;\n" "d-i mirror/http/directory string /debian\n" "d-i mirror/http/proxy string\n" @@ -877,17 +876,13 @@ msgid "" "#d-i partman-auto/init_automatically_partition \\\n" "# select Guided - use the largest continuous free space\n" "\n" - "<phrase condition=\"etch\"># Alternatively, you can specify a disk to partition. The device name\n" - "# can be given in either devfs or traditional non-devfs format.\n" - "# For example, to use the first disk:\n" - "d-i partman-auto/disk string /dev/discs/disc0/disc</phrase><phrase condition=\"lenny\">\n" "# Alternatively, you can specify a disk to partition. The device name must\n" "# be given in traditional non-devfs format.\n" "# For example, to use the first SCSI/SATA hard disk:\n" "d-i partman-auto/disk string /dev/sda\n" "# Note: If you want to use whatever disk is available, no matter\n" "# what its device name, comment the line above out. This will only work if\n" - "# the system only has one disk.</phrase>\n" + "# the system only has one disk.\n" "# In addition, you'll need to specify the method to use.\n" "# The presently available methods are: \"regular\", \"lvm\" and \"crypto\"\n" "d-i partman-auto/method string lvm\n" @@ -1031,13 +1026,12 @@ msgid "" "\n" "# You may set this to any valid setting for $TZ; see the contents of\n" "# /usr/share/zoneinfo/ for valid values.\n" - "d-i time/zone string US/Eastern<phrase condition=\"lenny\">\n" + "d-i time/zone string US/Eastern\n" "\n" "# Controls whether to use NTP to set the clock during the install\n" "d-i clock-setup/ntp boolean true\n" "# NTP server to use. The default is almost always fine here.\n" - "#d-i clock-setup/ntp-server ntp.example.com\n" - "</phrase>" + "#d-i clock-setup/ntp-server ntp.example.com" msgstr "" #. Tag: title @@ -1083,11 +1077,11 @@ msgid "" "# or encrypted using an MD5 hash.\n" "#d-i passwd/user-password-crypted password [MD5 hash]\n" "# Create the first user with the specified UID instead of the default.\n" - "#d-i passwd/user-uid string 1010<phrase condition=\"lenny\">\n" + "#d-i passwd/user-uid string 1010\n" "\n" "# The user account will be added to some standard initial groups. To\n" "# override that, use this.\n" - "#d-i passwd/user-default-groups string audio cdrom video</phrase>" + "#d-i passwd/user-default-groups string audio cdrom video" msgstr "" #. Tag: para @@ -1125,11 +1119,11 @@ msgstr "" #, no-c-format msgid "" "# Select the initramfs generator used to generate the initrd for 2.6 kernels.\n" - "#d-i base-installer/kernel/linux/initramfs-generators string yaird<phrase condition=\"lenny\">\n" + "#d-i base-installer/kernel/linux/initramfs-generators string yaird\n" "\n" "# The kernel image (meta) package to be installed; \"none\" can be used if no\n" "# kernel is to be installed.\n" - "#d-i base-installer/kernel/image linux-image-2.6-486</phrase>" + "#d-i base-installer/kernel/image linux-image-2.6-486" msgstr "" #. Tag: title @@ -1152,15 +1146,12 @@ msgid "" "#d-i apt-setup/non-free boolean true\n" "#d-i apt-setup/contrib boolean true\n" "# Uncomment this if you don't want to use a network mirror.\n" - "#d-i apt-setup/use_mirror boolean false<phrase condition=\"etch\">\n" - "# Uncomment this to avoid adding security sources, or\n" - "# add a hostname to use a different server than security.debian.org.\n" - "#d-i apt-setup/security_host string</phrase><phrase condition=\"lenny\">\n" + "#d-i apt-setup/use_mirror boolean false\n" "# Select which update services to use; define the mirrors to be used.\n" "# Values shown below are the normal defaults.\n" "#d-i apt-setup/services-select multi-select security, volatile\n" "#d-i apt-setup/security_host string security.debian.org\n" - "#d-i apt-setup/volatile_host string volatile.debian.org</phrase>\n" + "#d-i apt-setup/volatile_host string volatile.debian.org\n" "\n" "# Additional repositories, local[0-9] available\n" "#d-i apt-setup/local0/repository string \\\n" @@ -1273,11 +1264,10 @@ msgstr "" #: preseed.xml:961 #, no-c-format msgid "" - "#tasksel tasksel/first multiselect standard, web-server<phrase condition=\"lenny\">\n" + "#tasksel tasksel/first multiselect standard, web-server\n" "# If the desktop task is selected, install the kde and xfce desktops\n" "# instead of the default gnome desktop.\n" - "#tasksel tasksel/desktop multiselect kde, xfce</phrase><phrase condition=\"etch\">\n" - "#tasksel tasksel/first multiselect standard, kde-desktop</phrase>\n" + "#tasksel tasksel/desktop multiselect kde, xfce\n" "\n" "# Individual additional packages to install\n" "#d-i pkgsel/include string openssh-server build-essential\n" @@ -1301,10 +1291,10 @@ msgstr "" msgid "" "# Grub is the default boot loader (for x86). If you want lilo installed\n" "# instead, uncomment this:\n" - "#d-i grub-installer/skip boolean true<phrase condition=\"lenny\">\n" + "#d-i grub-installer/skip boolean true\n" "# To also skip installing lilo, and install no bootloader, uncomment this\n" "# too:\n" - "#d-i lilo-installer/skip boolean true</phrase>\n" + "#d-i lilo-installer/skip boolean true\n" "\n" "# This is fairly safe to set, it makes grub install automatically to the MBR\n" "# if no other operating system is detected on the machine.\n" diff --git a/po/pot/random-bits.pot b/po/pot/random-bits.pot index c19b0cfe8..5816ef3fa 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: 2007-07-09 16:44+0000\n" +"POT-Creation-Date: 2007-10-22 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" @@ -628,20 +628,26 @@ msgstr "" msgid "Once you've got the new Debian system configured to your preference, you can migrate your existing user data (if any) to it, and keep on rolling. This is therefore a <quote>zero downtime</quote> &debian; install. It's also a clever way for dealing with hardware that otherwise doesn't play friendly with various boot or installation media." msgstr "" +#. Tag: para +#: random-bits.xml:359 +#, no-c-format +msgid "As this is a mostly manual procedure, you should bear in mind that you will need to do a lot of basic configuration of the system yourself, which will also require more knowledge of Debian and of Linux in general than performing a regular installation. You cannot expect this procedure to result in a system that is identical to a system from a regular installation. You should also keep in mind that this procedure only gives the basic steps to set up a system. Additional installation and/or configuration steps may be needed." +msgstr "" + #. Tag: title -#: random-bits.xml:360 +#: random-bits.xml:373 #, no-c-format msgid "Getting Started" msgstr "" #. Tag: para -#: random-bits.xml:361 +#: random-bits.xml:374 #, no-c-format msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need around 350MB of space available for a console only install, or about 1GB if you plan to install X (more if you intend to install desktop environments like GNOME or KDE)." msgstr "" #. Tag: para -#: random-bits.xml:369 +#: random-bits.xml:382 #, no-c-format msgid "" "Next, create file systems on the partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n" @@ -650,7 +656,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:379 +#: random-bits.xml:392 #, no-c-format msgid "" "Initialize and activate swap (substitute the partition number for your intended Debian swap partition): <informalexample><screen>\n" @@ -661,7 +667,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:391 +#: random-bits.xml:404 #, no-c-format msgid "" "# mkdir /mnt/debinst\n" @@ -669,25 +675,25 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:394 +#: random-bits.xml:407 #, no-c-format msgid "If you want to have parts of the filesystem (e.g. /usr) mounted on separate partitions, you will need to create and mount these directories manually before proceding with the next stage." msgstr "" #. Tag: title -#: random-bits.xml:404 +#: random-bits.xml:417 #, no-c-format msgid "Install <command>debootstrap</command>" msgstr "" #. Tag: para -#: random-bits.xml:405 +#: random-bits.xml:418 #, no-c-format msgid "The utility used by the Debian installer, and recognized as the official way to install a Debian base system, is <command>debootstrap</command>. It uses <command>wget</command> and <command>ar</command>, but otherwise depends only on <classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> <para> These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>. </para> </footnote>. Install <command>wget</command> and <command>ar</command> if they aren't already on your current system, then download and install <command>debootstrap</command>." msgstr "" #. Tag: para -#: random-bits.xml:435 +#: random-bits.xml:448 #, no-c-format msgid "" "Or, you can use the following procedure to install it manually. Make a work folder for extracting the .deb into: <informalexample><screen>\n" @@ -697,7 +703,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:450 +#: random-bits.xml:463 #, no-c-format msgid "" "# ar -x debootstrap_0.X.X_all.deb\n" @@ -706,31 +712,31 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:456 +#: random-bits.xml:469 #, no-c-format msgid "Run <command>debootstrap</command>" msgstr "" #. Tag: para -#: random-bits.xml:457 +#: random-bits.xml:470 #, no-c-format msgid "<command>debootstrap</command> can download the needed files directly from the archive when you run it. You can substitute any Debian archive mirror for <userinput>&archive-mirror;/debian</userinput> in the command example below, preferably a mirror close to you network-wise. Mirrors are listed at <ulink url=\"http://www.debian.org/misc/README.mirrors\"></ulink>." msgstr "" #. Tag: para -#: random-bits.xml:466 +#: random-bits.xml:479 #, no-c-format msgid "If you have a &releasename; &debian; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>" msgstr "" #. Tag: para -#: random-bits.xml:472 +#: random-bits.xml:485 #, no-c-format msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>alpha</userinput>, <userinput>amd64</userinput>, <userinput>arm</userinput>, <userinput>hppa</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>m68k</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, or <userinput>sparc</userinput>." msgstr "" #. Tag: screen -#: random-bits.xml:490 +#: random-bits.xml:503 #, no-c-format msgid "" "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n" @@ -738,13 +744,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:496 +#: random-bits.xml:509 #, no-c-format msgid "Configure The Base System" msgstr "" #. Tag: para -#: random-bits.xml:497 +#: random-bits.xml:510 #, no-c-format msgid "" "Now you've got a real Debian system, though rather lean, on disk. <command>chroot</command> into it: <informalexample><screen>\n" @@ -753,19 +759,63 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:507 +#: random-bits.xml:520 #, no-c-format msgid "# export TERM=<replaceable>xterm-color</replaceable>" msgstr "" #. Tag: title -#: random-bits.xml:512 +#: random-bits.xml:525 +#, no-c-format +msgid "Create device files" +msgstr "" + +#. Tag: para +#: random-bits.xml:526 +#, no-c-format +msgid "At this point <filename>/dev/</filename> only contains very basic device files. For the next steps of the installation additional device files may be needed. There are different ways to go about this and which method you should use depends on the host system you are using for the installation, on whether you intend to use a modular kernel or not, and on whether you intend to use dynamic (e.g. using <classname>udev</classname>) or static device files for the new system." +msgstr "" + +#. Tag: para +#: random-bits.xml:536 +#, no-c-format +msgid "A few of the available options are:" +msgstr "" + +#. Tag: para +#: random-bits.xml:541 +#, no-c-format +msgid "create a default set of static device files using" +msgstr "" + +#. Tag: screen +#: random-bits.xml:544 +#, no-c-format +msgid "" + "# cd /dev\n" + "# MAKEDEV generic" +msgstr "" + +#. Tag: para +#: random-bits.xml:547 +#, no-c-format +msgid "manually create only specific device files using <command>MAKEDEV</command>" +msgstr "" + +#. Tag: para +#: random-bits.xml:552 +#, no-c-format +msgid "bind mount /dev from your host system on top of /dev in the target system; note that the postinst scripts of some packages may try to create device files, so this option should only be used with care" +msgstr "" + +#. Tag: title +#: random-bits.xml:565 #, no-c-format msgid "Mount Partitions" msgstr "" #. Tag: para -#: random-bits.xml:513 +#: random-bits.xml:566 #, no-c-format msgid "" "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n" @@ -799,37 +849,37 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:539 +#: random-bits.xml:592 #, no-c-format msgid "# mount -t proc proc /proc" msgstr "" #. Tag: para -#: random-bits.xml:541 +#: random-bits.xml:594 #, no-c-format msgid "The command <userinput>ls /proc</userinput> should now show a non-empty directory. Should this fail, you may be able to mount proc from outside the chroot:" msgstr "" #. Tag: screen -#: random-bits.xml:547 +#: random-bits.xml:600 #, no-c-format msgid "# mount -t proc proc /mnt/debinst/proc" msgstr "" #. Tag: title -#: random-bits.xml:553 +#: random-bits.xml:606 #, no-c-format msgid "Setting Timezone" msgstr "" #. Tag: para -#: random-bits.xml:554 +#: random-bits.xml:607 #, no-c-format msgid "An option in the file <filename>/etc/default/rcS</filename> determines whether the system will interpret the hardware clock as being set to UTC or local time. The following command allow you to set that and choose your timezone." msgstr "" #. Tag: screen -#: random-bits.xml:561 +#: random-bits.xml:614 #, no-c-format msgid "" "# editor /etc/default/rcS\n" @@ -837,13 +887,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:567 +#: random-bits.xml:620 #, no-c-format msgid "Configure Networking" msgstr "" #. Tag: para -#: random-bits.xml:568 +#: random-bits.xml:621 #, no-c-format msgid "" "To configure networking, edit <filename>/etc/network/interfaces</filename>, <filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> and <filename>/etc/hosts</filename>. <informalexample><screen>\n" @@ -896,13 +946,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:609 +#: random-bits.xml:662 #, no-c-format msgid "Configure Apt" msgstr "" #. Tag: para -#: random-bits.xml:610 +#: random-bits.xml:663 #, no-c-format msgid "" "Debootstrap will have created a very basic <filename>/etc/apt/sources.list</filename> that will allow installing additional packages. However, you may want to add some additional sources, for example for source packages and security updates: <informalexample><screen>\n" @@ -914,13 +964,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:626 +#: random-bits.xml:679 #, no-c-format msgid "Configure Locales and Keyboard" msgstr "" #. Tag: para -#: random-bits.xml:627 +#: random-bits.xml:680 #, no-c-format msgid "" "To configure your locale settings to use a language other than English, install the <classname>locales</classname> support package and configure it. Currently the use of UTF-8 locales is recommended. <informalexample><screen>\n" @@ -930,7 +980,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:637 +#: random-bits.xml:690 #, no-c-format msgid "" "# aptitude install console-data\n" @@ -938,37 +988,37 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:639 +#: random-bits.xml:692 #, no-c-format msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot." msgstr "" #. Tag: title -#: random-bits.xml:649 +#: random-bits.xml:702 #, no-c-format msgid "Install a Kernel" msgstr "" #. Tag: para -#: random-bits.xml:650 +#: random-bits.xml:703 #, no-c-format msgid "If you intend to boot this system, you probably want a Linux kernel and a boot loader. Identify available pre-packaged kernels with:" msgstr "" #. Tag: screen -#: random-bits.xml:655 +#: random-bits.xml:708 #, no-c-format msgid "# apt-cache search linux-image" msgstr "" #. Tag: para -#: random-bits.xml:657 +#: random-bits.xml:710 #, no-c-format msgid "If you intend to use a pre-packaged kernel, you may want to create the configuration file <filename>/etc/kernel-img.conf</filename> before you do so. Here's an example file:" msgstr "" #. Tag: screen -#: random-bits.xml:663 +#: random-bits.xml:716 #, no-c-format msgid "" "# Kernel image management overrides\n" @@ -982,13 +1032,13 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:665 +#: random-bits.xml:718 #, no-c-format msgid "For detailed information about this file and the various options, consult its man page which will be available after installing the <classname>kernel-package</classname> package. We recommend that you check that the values are appropriate for your system." msgstr "" #. Tag: para -#: random-bits.xml:672 +#: random-bits.xml:725 #, no-c-format msgid "" "Then install the kernel package of your choice using its package name. <informalexample><screen>\n" @@ -997,25 +1047,25 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:686 +#: random-bits.xml:739 #, no-c-format msgid "Set up the Boot Loader" msgstr "" #. Tag: para -#: random-bits.xml:687 +#: random-bits.xml:740 #, no-c-format msgid "To make your &debian; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your Debian chroot to do so." msgstr "" #. Tag: para -#: random-bits.xml:694 +#: random-bits.xml:747 #, no-c-format msgid "Check <userinput>info grub</userinput> or <userinput>man lilo.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing grub <filename>menu.lst</filename> or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call <command>lilo</command> (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)." msgstr "" #. Tag: para -#: random-bits.xml:706 +#: random-bits.xml:759 #, no-c-format msgid "" "Installing and setting up <classname>grub</classname> is as easy as: <informalexample><screen>\n" @@ -1026,13 +1076,19 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:716 +#: random-bits.xml:769 +#, no-c-format +msgid "Note that this assumes that a <filename>/dev/hda</filename> device file has been created. There are alternative methods to install <command>grub</command>, but those are outside the scope of this appendix." +msgstr "" + +#. Tag: para +#: random-bits.xml:775 #, no-c-format msgid "Here is a basic <filename>/etc/lilo.conf</filename> as an example:" msgstr "" #. Tag: screen -#: random-bits.xml:720 +#: random-bits.xml:779 #, no-c-format msgid "" "boot=/dev/<replaceable>hda6</replaceable>\n" @@ -1041,17 +1097,18 @@ msgid "" "delay=20\n" "lba32\n" "image=/vmlinuz\n" + "initrd=/initrd.img\n" "label=Debian" msgstr "" #. Tag: para -#: random-bits.xml:722 +#: random-bits.xml:781 #, no-c-format msgid "Depending on which bootloader you selected, you can now make some additional changes in <filename>/etc/kernel-img.conf</filename>." msgstr "" #. Tag: para -#: random-bits.xml:727 +#: random-bits.xml:786 #, no-c-format msgid "" "For the <classname>grub</classname> bootloader, you should set the <literal>do_bootloader</literal> option to <quote>no</quote>. And to automatically update your <filename>/boot/grub/menu.lst</filename> on installation or removal of Debian kernels, add the following lines: <informalexample><screen>\n" @@ -1061,13 +1118,13 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:739 +#: random-bits.xml:798 #, no-c-format msgid "Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing <filename>yaboot.conf</filename>. You could also copy it to the new system and edit it there. After you are done editing, call ybin (remember it will use <filename>yaboot.conf</filename> relative to the system you call it from)." msgstr "" #. Tag: para -#: random-bits.xml:749 +#: random-bits.xml:808 #, no-c-format msgid "" "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n" @@ -1083,13 +1140,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:762 +#: random-bits.xml:821 #, no-c-format msgid "Finishing touches" msgstr "" #. Tag: para -#: random-bits.xml:763 +#: random-bits.xml:822 #, no-c-format msgid "" "As mentioned earlier, the installed system will be very basic. If you would like to make the system a bit more mature, there is an easy method to install all packages with <quote>standard</quote> priority: <informalexample><screen>\n" @@ -1098,91 +1155,91 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:774 +#: random-bits.xml:833 #, no-c-format msgid "After the installation there will be a lot of downloaded packages in <filename>/var/cache/apt/archives/</filename>. You can free up some diskspace by running:" msgstr "" #. Tag: screen -#: random-bits.xml:780 +#: random-bits.xml:839 #, no-c-format msgid "# aptitude clean" msgstr "" #. Tag: title -#: random-bits.xml:791 +#: random-bits.xml:850 #, no-c-format msgid "Installing &debian; over Parallel Line IP (PLIP)" msgstr "" #. Tag: para -#: random-bits.xml:793 +#: random-bits.xml:852 #, no-c-format msgid "This section explains how to install &debian; on a computer without an Ethernet card, but with just a remote gateway computer attached via a Null-Modem cable (also called Null-Printer cable). The gateway computer should be connected to a network that has a Debian mirror on it (e.g. to the Internet)." msgstr "" #. Tag: para -#: random-bits.xml:801 +#: random-bits.xml:860 #, no-c-format msgid "In the example in this appendix we will set up a PLIP connection using a gateway connected to the Internet over a dial-up connection (ppp0). We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the target system and the source system respectively (these addresses should be unused within your network address space)." msgstr "" #. Tag: para -#: random-bits.xml:809 +#: random-bits.xml:868 #, no-c-format msgid "The PLIP connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)." msgstr "" #. Tag: para -#: random-bits.xml:814 +#: random-bits.xml:873 #, no-c-format msgid "Before you start, you will need to check the BIOS configuration (IO base address and IRQ) for the parallel ports of both the source and target systems. The most common values are <literal>io=0x378</literal>, <literal>irq=7</literal>." msgstr "" #. Tag: title -#: random-bits.xml:824 +#: random-bits.xml:883 #, no-c-format msgid "Requirements" msgstr "" #. Tag: para -#: random-bits.xml:827 +#: random-bits.xml:886 #, no-c-format msgid "A target computer, called <emphasis>target</emphasis>, where Debian will be installed." msgstr "" #. Tag: para -#: random-bits.xml:833 +#: random-bits.xml:892 #, no-c-format msgid "System installation media; see <xref linkend=\"installation-media\"/>." msgstr "" #. Tag: para -#: random-bits.xml:838 +#: random-bits.xml:897 #, no-c-format msgid "Another computer connected to the Internet, called <emphasis>source</emphasis>, that will function as the gateway." msgstr "" #. Tag: para -#: random-bits.xml:844 +#: random-bits.xml:903 #, no-c-format msgid "A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> for more information on this cable and instructions how to make your own." msgstr "" #. Tag: title -#: random-bits.xml:856 +#: random-bits.xml:915 #, no-c-format msgid "Setting up source" msgstr "" #. Tag: para -#: random-bits.xml:857 +#: random-bits.xml:916 #, no-c-format msgid "The following shell script is a simple example of how to configure the source computer as a gateway to the Internet using ppp0." msgstr "" #. Tag: screen -#: random-bits.xml:862 +#: random-bits.xml:921 #, no-c-format msgid "" "#!/bin/sh\n" @@ -1203,13 +1260,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:868 +#: random-bits.xml:927 #, no-c-format msgid "Installing target" msgstr "" #. Tag: para -#: random-bits.xml:869 +#: random-bits.xml:928 #, no-c-format msgid "" "Boot the installation media. The installation needs to be run in expert mode; enter <userinput>expert</userinput> at the boot prompt. If you need to set parameters for kernel modules, you also need to do this at the boot prompt. For example, to boot the installer and set values for the <quote>io</quote> and <quote>irq</quote> options for the parport_pc module, enter the following at the boot prompt: <informalexample><screen>\n" @@ -1218,97 +1275,97 @@ msgid "" msgstr "" #. Tag: guimenuitem -#: random-bits.xml:888 +#: random-bits.xml:947 #, no-c-format msgid "Load installer components from CD" msgstr "" #. Tag: para -#: random-bits.xml:890 +#: random-bits.xml:949 #, no-c-format msgid "Select the <userinput>plip-modules</userinput> option from the list; this will make the PLIP drivers available to the installation system." msgstr "" #. Tag: guimenuitem -#: random-bits.xml:898 +#: random-bits.xml:957 #, no-c-format msgid "Detect network hardware" msgstr "" #. Tag: para -#: random-bits.xml:903 +#: random-bits.xml:962 #, no-c-format msgid "If target <emphasis>does</emphasis> have a network card, a list of driver modules for detected cards will be shown. If you want to force &d-i; to use plip instead, you have to deselect all listed driver modules. Obviously, if target doesn't have a network card, the installer will not show this list." msgstr "" #. Tag: para -#: random-bits.xml:912 +#: random-bits.xml:971 #, no-c-format msgid "Because no network card was detected/selected earlier, the installer will ask you to select a network driver module from a list. Select the <userinput>plip</userinput> module." msgstr "" #. Tag: guimenuitem -#: random-bits.xml:924 +#: random-bits.xml:983 #, no-c-format msgid "Configure the network" msgstr "" #. Tag: para -#: random-bits.xml:927 +#: random-bits.xml:986 #, no-c-format msgid "Auto-configure network with DHCP: No" msgstr "" #. Tag: para -#: random-bits.xml:932 +#: random-bits.xml:991 #, no-c-format msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>" msgstr "" #. Tag: para -#: random-bits.xml:937 +#: random-bits.xml:996 #, no-c-format msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>" msgstr "" #. Tag: para -#: random-bits.xml:943 +#: random-bits.xml:1002 #, no-c-format msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)" msgstr "" #. Tag: title -#: random-bits.xml:962 +#: random-bits.xml:1021 #, no-c-format msgid "Installing &debian; using PPP over Ethernet (PPPoE)" msgstr "" #. Tag: para -#: random-bits.xml:964 +#: random-bits.xml:1023 #, no-c-format msgid "In some countries PPP over Ethernet (PPPoE) is a common protocol for broadband (ADSL or cable) connections to an Internet Service Provider. Setting up a network connection using PPPoE is not supported by default in the installer, but can be made to work very simply. This section explains how." msgstr "" #. Tag: para -#: random-bits.xml:972 +#: random-bits.xml:1031 #, no-c-format msgid "The PPPoE connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)." msgstr "" #. Tag: para -#: random-bits.xml:977 +#: random-bits.xml:1036 #, no-c-format msgid "To have the option of setting up and using PPPoE during the installation, you will need to install using one of the CD-ROM/DVD images that are available. It is not supported for other installation methods (e.g. netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)." msgstr "" #. Tag: para -#: random-bits.xml:984 +#: random-bits.xml:1043 #, no-c-format msgid "Installing over PPPoE is mostly the same as any other installation. The following steps explain the differences." msgstr "" #. Tag: para -#: random-bits.xml:992 +#: random-bits.xml:1051 #, no-c-format msgid "" "Boot the installer with <userinput>modules=ppp-udeb</userinput> as boot parameter. This means that at the boot prompt you should enter: <informalexample><screen>\n" @@ -1319,169 +1376,169 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:1007 +#: random-bits.xml:1066 #, no-c-format msgid "Follow the regular initial steps of the installation (language, country and keyboard selection; the loading of additional installer components<footnote> <para> The <classname>ppp-udeb</classname> component is loaded as one of the additional components in this step. If you want to install at medium or low priority (expert mode), you can also manually select the <classname>ppp-udeb</classname> instead of entering the <quote>modules</quote> parameter at the boot prompt. </para> </footnote>)." msgstr "" #. Tag: para -#: random-bits.xml:1026 +#: random-bits.xml:1085 #, no-c-format msgid "The next step is the detection of network hardware, in order to identify any Ethernet cards present in the system." msgstr "" #. Tag: para -#: random-bits.xml:1032 +#: random-bits.xml:1091 #, no-c-format msgid "After this the actual setup of PPPoE is started. The installer will probe all the detected Ethernet interfaces in an attempt to find a PPPoE concentrator (a type of server which handles PPPoE connections)." msgstr "" #. Tag: para -#: random-bits.xml:1038 +#: random-bits.xml:1097 #, no-c-format msgid "It is possible that the concentrator will not to be found at the first attempt. This can happen occasionally on slow or loaded networks or with faulty servers. In most cases a second attempt to detect the concentrator will be successful; to retry, select <guimenuitem>Configure and start a PPPoE connection</guimenuitem> from the main menu of the installer." msgstr "" #. Tag: para -#: random-bits.xml:1047 +#: random-bits.xml:1106 #, no-c-format msgid "After a concentrator is found, the user will be prompted to type the login information (the PPPoE username and password)." msgstr "" #. Tag: para -#: random-bits.xml:1053 +#: random-bits.xml:1112 #, no-c-format msgid "At this point the installer will use the provided information to establish the PPPoE connection. If the correct information was provided, the PPPoE connection should be configured and the installer should be able to use it to connect to the Internet and retrieve packages over it (if needed). If the login information is not correct or some error appears, the installer will stop, but the configuration can be attempted again by selecting the menu entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>." msgstr "" #. Tag: title -#: random-bits.xml:1073 +#: random-bits.xml:1132 #, no-c-format msgid "The Graphical Installer" msgstr "" #. Tag: para -#: random-bits.xml:1074 +#: random-bits.xml:1133 #, no-c-format msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the regular installer as it basically uses the same programs, but with a different frontend." msgstr "" #. Tag: para -#: random-bits.xml:1082 +#: random-bits.xml:1141 #, no-c-format msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the regular <quote>newt</quote> frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen." msgstr "" #. Tag: para -#: random-bits.xml:1091 +#: random-bits.xml:1150 #, no-c-format msgid "The graphical installer is available with all CD images and with the hd-media installation method. As the graphical installer uses a separate (much larger) initrd than the regular installer, it has to be booted using <userinput>installgui</userinput> instead of <userinput>install</userinput>. Analogous, the expert and rescue modes are booted using <userinput>expertgui</userinput> and <userinput>rescuegui</userinput> respectively." msgstr "" #. Tag: para -#: random-bits.xml:1101 +#: random-bits.xml:1160 #, no-c-format -msgid "It is also available as a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a Debian mirror as described in <xref linkend=\"downloading-files\"/>. Look for <phrase condition=\"etch\"><filename>gtk-miniiso</filename></phrase> <phrase condition=\"lenny\"><filename>netboot/gtk/mini.iso</filename></phrase>. </para> </footnote>, which is mainly useful for testing; in this case the image is booted just using <userinput>install</userinput>. There is no graphical installer image that can be netbooted." +msgid "It is also available as a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a Debian mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is mainly useful for testing; in this case the image is booted just using <userinput>install</userinput>. There is no graphical installer image that can be netbooted." msgstr "" #. Tag: para -#: random-bits.xml:1117 +#: random-bits.xml:1175 #, no-c-format -msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a Debian mirror as described in <xref linkend=\"downloading-files\"/>. Look for <phrase condition=\"etch\"><filename>gtk-miniiso</filename></phrase> <phrase condition=\"lenny\"><filename>netboot/gtk/mini.iso</filename></phrase>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems." +msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a Debian mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems." msgstr "" #. Tag: para -#: random-bits.xml:1132 +#: random-bits.xml:1189 #, no-c-format msgid "The graphical installer requires significantly more memory to run than the regular installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the regular <quote>newt</quote> frontend." msgstr "" #. Tag: para -#: random-bits.xml:1139 +#: random-bits.xml:1196 #, no-c-format msgid "You can add boot parameters when starting the graphical installer, just as with the regular installer. One of those parameters allows you to configure the mouse for left-handed use. See <xref linkend=\"boot-parms\"/> for valid parameters." msgstr "" #. Tag: title -#: random-bits.xml:1149 +#: random-bits.xml:1206 #, no-c-format msgid "Using the graphical installer" msgstr "" #. Tag: para -#: random-bits.xml:1150 +#: random-bits.xml:1207 #, no-c-format msgid "As already mentioned, the graphical installer basically works the same as the regular installer and thus the rest of this manual can be used to guide you through the installation process." msgstr "" #. Tag: para -#: random-bits.xml:1156 +#: random-bits.xml:1213 #, no-c-format msgid "If you prefer using the keyboard over the mouse, there are two things you need to know. To expand a collapsed list (used for example for the selection of countries within continents), you can use the <keycap>+</keycap> and <keycap>-</keycap> keys. For questions where more than one item can be selected (e.g. task selection), you first need to tab to the &BTN-CONT; button after making your selections; hitting enter will toggle a selection, not activate &BTN-CONT;." msgstr "" #. Tag: para -#: random-bits.xml:1166 +#: random-bits.xml:1223 #, no-c-format msgid "To switch to another console, you will also need to use the <keycap>Ctrl</keycap> key, just as with the X Window System. For example, to switch to VT1 you would use: <keycombo> <keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F1</keycap> </keycombo>." msgstr "" #. Tag: title -#: random-bits.xml:1177 +#: random-bits.xml:1234 #, no-c-format msgid "Known issues" msgstr "" #. Tag: para -#: random-bits.xml:1178 +#: random-bits.xml:1235 #, no-c-format msgid "Etch is the first release that includes the graphical installer and uses some relatively new technology. There are a few known issues that you may run into during the installation. We expect to be able to fix these issues for the next release of &debian;." msgstr "" #. Tag: para -#: random-bits.xml:1188 +#: random-bits.xml:1245 #, no-c-format msgid "Information on some screens is not nicely formatted into columns as it should be. The most obvious example is the first screen where you select your language. Another example is the main screen of partman." msgstr "" #. Tag: para -#: random-bits.xml:1195 +#: random-bits.xml:1252 #, 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:1202 +#: random-bits.xml:1259 #, no-c-format msgid "Support for touchpads is not yet optimal." msgstr "" #. Tag: para -#: random-bits.xml:1207 +#: random-bits.xml:1264 #, no-c-format msgid "You should not switch to a different console while the installer is busy; this may cause the frontend to crash. The frontend will be restarted automatically, but this may still cause problems with the installation. Switching to another console while the installer is waiting for input should work without causing any problems." msgstr "" #. Tag: para -#: random-bits.xml:1216 +#: random-bits.xml:1273 #, no-c-format msgid "Support for creating encrypted partitions is limited as it is not possible to generate a random encryption key. It is possible to set up an encrypted partition using a passphrase as encryption key." msgstr "" #. Tag: para -#: random-bits.xml:1223 +#: random-bits.xml:1280 #, 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:1232 +#: random-bits.xml:1289 #, 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:1239 +#: random-bits.xml:1296 #, no-c-format msgid "# chroot /target" msgstr "" diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index c53e4ef62..d3f557147 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: 2007-10-21 00:05+0000\n" +"POT-Creation-Date: 2007-10-22 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" @@ -1578,45 +1578,45 @@ msgid "One of the tools used to install packages on a &debian; system is a progr msgstr "" #. Tag: para -#: using-d-i.xml:1973 +#: using-d-i.xml:1971 #, 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:1980 +#: using-d-i.xml:1978 #, 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:1989 +#: using-d-i.xml:1987 #, 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:2000 +#: using-d-i.xml:1998 #, no-c-format msgid "Using a network mirror" msgstr "" #. Tag: para -#: using-d-i.xml:2002 +#: using-d-i.xml:2000 #, no-c-format msgid "One question that will be asked in most cases 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:2008 +#: using-d-i.xml:2006 #, 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:2017 +#: using-d-i.xml:2015 #, no-c-format -msgid "If you are installing from a full CD or using a CD image (not DVD), using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. The installer currently does not support using multiple CD or DVD images during the installation<footnote> Adding that option is planned. </footnote>. 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 install additional packages after the installation (i.e. after you have rebooted into the new system)." +msgid "If you are installing from a full CD or using a CD image (not DVD), using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. The installer currently does not support using multiple CD or DVD images during the installation<footnote> <para> Adding that option is planned. </para> </footnote>. 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 install additional packages after the installation (i.e. after you have rebooted into the new system)." msgstr "" #. Tag: para @@ -1628,353 +1628,353 @@ msgstr "" #. Tag: para #: using-d-i.xml:2043 #, no-c-format -msgid "To install additional packages after the installation you have two options: <orderedlist> <listitem><para> if you have additional CD/DVD images available (from same set as the installation CD/DVD you are using), you can add those to the <filename>sources.list</filename> using <command>apt-cdrom</command>; </para></listitem> <listitem><para> manually add a mirror to the <filename>sources.list</filename> using an editor. </para></listitem> </orderedlist> You can then use one of the package management front-ends to select and install additional packages<footnote> It is possible to add both additional CDs or DVDs <emphasis>and</emphasis> a network mirror in <filename>/etc/apt/sources.list</filename>. Also adding a network mirror has the advantage that it will make updates of packages in point releases of the distribution available for installation. </footnote>." +msgid "To install additional packages after the installation you have two options: <orderedlist> <listitem><para> if you have additional CD/DVD images available (from same set as the installation CD/DVD you are using), you can add those to the <filename>sources.list</filename> using <command>apt-cdrom</command>; </para></listitem> <listitem><para> manually add a mirror to the <filename>sources.list</filename> using an editor. </para></listitem> </orderedlist> You can then use one of the package management front-ends to select and install additional packages<footnote> <para> It is possible to add both additional CDs or DVDs <emphasis>and</emphasis> a network mirror in <filename>/etc/apt/sources.list</filename>. Also adding a network mirror has the advantage that it will make updates of packages in point releases of the distribution available for installation. </para> </footnote>." msgstr "" #. Tag: para -#: using-d-i.xml:2075 +#: using-d-i.xml:2077 #, 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 on the CD/DVD, the installer will alway use that. The amount of data that will be downloaded if you do select a mirror thus depends on a) the tasks you select in the next step of the installation, b) which packages are needed for those tasks, and c) which of those packages are present on the CD/DVD." msgstr "" #. Tag: para -#: using-d-i.xml:2085 +#: using-d-i.xml:2087 #, no-c-format msgid "Note 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:2100 +#: using-d-i.xml:2102 #, no-c-format msgid "Selecting and Installing Software" msgstr "" #. Tag: para -#: using-d-i.xml:2102 +#: using-d-i.xml:2104 #, 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:2111 +#: using-d-i.xml:2113 #, 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:2138 +#: using-d-i.xml:2140 #, 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 un-select the tasks. You can even opt to install no tasks at all at this point." msgstr "" #. Tag: para -#: using-d-i.xml:2145 +#: using-d-i.xml:2147 #, no-c-format msgid "The <quote>Desktop environment</quote> task will install the GNOME desktop environment. The options offered by the installer currently do not allow to select a different desktop environment such as for example KDE." msgstr "" #. Tag: para -#: using-d-i.xml:2153 +#: using-d-i.xml:2155 #, no-c-format msgid "It is possible to get the installer to install KDE by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding <literal>tasks=\"standard, kde-desktop\"</literal> at the boot prompt when starting the installer<footnote> <para> A more lightweight Xfce desktop environment can be selected by using <literal>xfce-desktop</literal> instead of <literal>kde-desktop</literal>. If you are installing on a laptop, you could also add <literal>laptop</literal> to the tasks to be installed. </para> </footnote>. However, this will only work if the packages needed for KDE are actually available. If you are installing using a full CD image, they will need to be downloaded from a mirror as KDE packages are not included on the first full CD; installing KDE this way should work fine if you are using a DVD image or any other installation method." msgstr "" #. Tag: para -#: using-d-i.xml:2173 +#: using-d-i.xml:2175 #, 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>." msgstr "" #. Tag: para -#: using-d-i.xml:2185 +#: using-d-i.xml:2187 #, 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:2192 +#: using-d-i.xml:2194 #, 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:2198 +#: using-d-i.xml:2200 #, 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:2207 +#: using-d-i.xml:2209 #, 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:2216 +#: using-d-i.xml:2218 #, 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:2229 +#: using-d-i.xml:2231 #, no-c-format msgid "Making Your System Bootable" msgstr "" #. Tag: para -#: using-d-i.xml:2231 +#: using-d-i.xml:2233 #, 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:2246 +#: using-d-i.xml:2248 #, no-c-format msgid "Detecting other operating systems" msgstr "" #. Tag: para -#: using-d-i.xml:2248 +#: using-d-i.xml:2250 #, 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:2256 +#: using-d-i.xml:2258 #, 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:2274 +#: using-d-i.xml:2276 #, no-c-format msgid "Install <command>aboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2275 +#: using-d-i.xml:2277 #, 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:2295 +#: using-d-i.xml:2297 #, no-c-format msgid "<command>palo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2296 +#: using-d-i.xml:2298 #, 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:2305 +#: using-d-i.xml:2307 #, no-c-format msgid "hppa FIXME ( need more info )" msgstr "" #. Tag: title -#: using-d-i.xml:2317 +#: using-d-i.xml:2319 #, no-c-format msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2319 +#: using-d-i.xml:2321 #, 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:2325 +#: using-d-i.xml:2327 #, 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:2331 +#: using-d-i.xml:2333 #, 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:2344 +#: using-d-i.xml:2346 #, no-c-format msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2346 +#: using-d-i.xml:2348 #, 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:2356 +#: using-d-i.xml:2358 #, 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:2364 +#: using-d-i.xml:2366 #, 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:2371 +#: using-d-i.xml:2373 #, no-c-format msgid "Master Boot Record (MBR)" msgstr "" #. Tag: para -#: using-d-i.xml:2371 +#: using-d-i.xml:2373 #, 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:2378 +#: using-d-i.xml:2380 #, no-c-format msgid "new Debian partition" msgstr "" #. Tag: para -#: using-d-i.xml:2378 +#: using-d-i.xml:2380 #, 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:2387 +#: using-d-i.xml:2389 #, no-c-format msgid "Other choice" msgstr "" #. Tag: para -#: using-d-i.xml:2387 +#: using-d-i.xml:2389 #, 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 <phrase condition=\"etch\">devfs style names, such as those that start with <filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and <filename>/dev/discs</filename>, as well as traditional names,</phrase> <phrase condition=\"lenny\">traditional device names</phrase> such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>." +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:2401 +#: using-d-i.xml:2399 #, 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:2417 +#: using-d-i.xml:2415 #, no-c-format msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2419 +#: using-d-i.xml:2417 #, 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:2435 +#: using-d-i.xml:2433 #, 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:2447 +#: using-d-i.xml:2445 #, no-c-format msgid "Choose the correct partition!" msgstr "" #. Tag: para -#: using-d-i.xml:2449 +#: using-d-i.xml:2447 #, 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:2464 +#: using-d-i.xml:2462 #, no-c-format msgid "EFI Partition Contents" msgstr "" #. Tag: para -#: using-d-i.xml:2466 +#: using-d-i.xml:2464 #, 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:2488 +#: using-d-i.xml:2486 #, no-c-format msgid "elilo.conf" msgstr "" #. Tag: para -#: using-d-i.xml:2489 +#: using-d-i.xml:2487 #, 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:2498 +#: using-d-i.xml:2496 #, no-c-format msgid "elilo.efi" msgstr "" #. Tag: para -#: using-d-i.xml:2499 +#: using-d-i.xml:2497 #, 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:2509 +#: using-d-i.xml:2507 #, no-c-format msgid "initrd.img" msgstr "" #. Tag: para -#: using-d-i.xml:2510 +#: using-d-i.xml:2508 #, 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:2522 +#: using-d-i.xml:2520 #, no-c-format msgid "readme.txt" msgstr "" #. Tag: para -#: using-d-i.xml:2523 +#: using-d-i.xml:2521 #, 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:2533 +#: using-d-i.xml:2531 #, no-c-format msgid "vmlinuz" msgstr "" #. Tag: para -#: using-d-i.xml:2534 +#: using-d-i.xml:2532 #, 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:2554 +#: using-d-i.xml:2552 #, no-c-format msgid "<command>arcboot</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2555 +#: using-d-i.xml:2553 #, 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" @@ -1987,61 +1987,61 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2574 +#: using-d-i.xml:2572 #, no-c-format msgid "scsi" msgstr "" #. Tag: para -#: using-d-i.xml:2575 +#: using-d-i.xml:2573 #, 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:2583 +#: using-d-i.xml:2581 #, no-c-format msgid "disk" msgstr "" #. Tag: para -#: using-d-i.xml:2584 +#: using-d-i.xml:2582 #, 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:2592 using-d-i.xml:2661 +#: using-d-i.xml:2590 using-d-i.xml:2659 #, no-c-format msgid "partnr" msgstr "" #. Tag: para -#: using-d-i.xml:2593 +#: using-d-i.xml:2591 #, 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:2601 +#: using-d-i.xml:2599 #, no-c-format msgid "config" msgstr "" #. Tag: para -#: using-d-i.xml:2602 +#: using-d-i.xml:2600 #, 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:2623 +#: using-d-i.xml:2621 #, no-c-format msgid "<command>delo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2624 +#: using-d-i.xml:2622 #, no-c-format msgid "" "The boot loader on DECstations is <command>DELO</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). DELO supports different configurations which are set up in <filename>/etc/delo.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After DELO has been installed, the system can be booted from hard disk by entering <informalexample><screen>\n" @@ -2050,265 +2050,265 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2643 +#: using-d-i.xml:2641 #, no-c-format msgid "<replaceable>#</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2644 +#: using-d-i.xml:2642 #, no-c-format msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2652 +#: using-d-i.xml:2650 #, no-c-format msgid "<replaceable>id</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2653 +#: using-d-i.xml:2651 #, no-c-format msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed" msgstr "" #. Tag: para -#: using-d-i.xml:2662 +#: using-d-i.xml:2660 #, no-c-format msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2670 +#: using-d-i.xml:2668 #, no-c-format msgid "name" msgstr "" #. Tag: para -#: using-d-i.xml:2671 +#: using-d-i.xml:2669 #, no-c-format msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: para -#: using-d-i.xml:2681 +#: using-d-i.xml:2679 #, no-c-format msgid "In case <filename>/etc/delo.conf</filename> is on the first partition on the disk and the default configuration shall be booted, it is sufficient to use" msgstr "" #. Tag: screen -#: using-d-i.xml:2687 +#: using-d-i.xml:2685 #, no-c-format msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>" msgstr "" #. Tag: title -#: using-d-i.xml:2697 +#: using-d-i.xml:2695 #, no-c-format msgid "Install <command>Yaboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2698 +#: using-d-i.xml:2696 #, 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:2716 +#: using-d-i.xml:2714 #, no-c-format msgid "Install <command>Quik</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2717 +#: using-d-i.xml:2715 #, 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:2733 +#: using-d-i.xml:2731 #, no-c-format msgid "<command>zipl</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2734 +#: using-d-i.xml:2732 #, 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:2751 +#: using-d-i.xml:2749 #, no-c-format msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2753 +#: using-d-i.xml:2751 #, 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:2778 +#: using-d-i.xml:2776 #, no-c-format msgid "Continue Without Boot Loader" msgstr "" #. Tag: para -#: using-d-i.xml:2780 +#: using-d-i.xml:2778 #, 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:2789 +#: using-d-i.xml:2787 #, 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:2806 +#: using-d-i.xml:2804 #, no-c-format msgid "Finishing the Installation" msgstr "" #. Tag: para -#: using-d-i.xml:2807 +#: using-d-i.xml:2805 #, no-c-format msgid "These are the last bits to do before rebooting to your new system. It mostly consists of tidying up after the &d-i;." msgstr "" #. Tag: title -#: using-d-i.xml:2819 +#: using-d-i.xml:2817 #, no-c-format msgid "Finish the Installation and Reboot" msgstr "" #. Tag: para -#: using-d-i.xml:2821 +#: using-d-i.xml:2819 #, no-c-format msgid "This is the last step in the initial Debian installation process. You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. The installer will do any last minute tasks, and then reboot into your new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2828 +#: using-d-i.xml:2826 #, no-c-format msgid "Select the <guimenuitem>Finish the installation</guimenuitem> menu item which will halt the system because rebooting is not supported on &arch-title; in this case. You then need to IPL GNU/Linux from the DASD which you selected for the root filesystem during the first steps of the installation." msgstr "" #. Tag: title -#: using-d-i.xml:2842 +#: using-d-i.xml:2840 #, no-c-format msgid "Miscellaneous" msgstr "" #. Tag: para -#: using-d-i.xml:2843 +#: using-d-i.xml:2841 #, 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:2856 +#: using-d-i.xml:2854 #, no-c-format msgid "Saving the installation logs" msgstr "" #. Tag: para -#: using-d-i.xml:2858 +#: using-d-i.xml:2856 #, 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:2865 +#: using-d-i.xml:2863 #, 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:2885 +#: using-d-i.xml:2883 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "" #. Tag: para -#: using-d-i.xml:2887 +#: using-d-i.xml:2885 #, 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:2905 +#: using-d-i.xml:2903 #, 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:2913 +#: using-d-i.xml:2911 #, 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:2922 +#: using-d-i.xml:2920 #, 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:2929 +#: using-d-i.xml:2927 #, 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:2935 +#: using-d-i.xml:2933 #, 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:2950 +#: using-d-i.xml:2948 #, no-c-format msgid "Installation Over the Network" msgstr "" #. Tag: para -#: using-d-i.xml:2952 +#: using-d-i.xml:2950 #, 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:2962 +#: using-d-i.xml:2960 #, 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:2975 +#: using-d-i.xml:2973 #, 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:2980 +#: using-d-i.xml:2978 #, 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:2992 +#: using-d-i.xml:2990 #, 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:2998 +#: using-d-i.xml:2996 #, 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" @@ -2317,25 +2317,25 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:3015 +#: using-d-i.xml:3013 #, 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> and try again." msgstr "" #. Tag: para -#: using-d-i.xml:3024 +#: using-d-i.xml:3022 #, 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:3034 +#: using-d-i.xml:3032 #, 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:3042 +#: using-d-i.xml:3040 #, 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 "" |