diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/hardware.pot | 1042 | ||||
| -rw-r--r-- | po/pot/install-methods.pot | 374 |
2 files changed, 774 insertions, 642 deletions
diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index e835825aa..e5a7b747e 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2008-05-21 00:10+0000\n" +"POT-Creation-Date: 2008-09-01 00:10+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" @@ -119,7 +119,7 @@ msgstr "" #. Tag: entry #: hardware.xml:81 #, no-c-format -msgid "ARM and StrongARM" +msgid "<entry>ARM</entry>" msgstr "" #. Tag: entry @@ -165,2887 +165,2959 @@ msgid "ixp4xx" msgstr "" #. Tag: entry -#: hardware.xml:94 +#: hardware.xml:92 #, no-c-format -msgid "HP PA-RISC" +msgid "Marvell Orion" +msgstr "" + +#. Tag: entry +#: hardware.xml:93 +#, no-c-format +msgid "orion5x" msgstr "" #. Tag: entry #: hardware.xml:95 #, no-c-format -msgid "hppa" +msgid "<entry>Versatile</entry>" msgstr "" #. Tag: entry #: hardware.xml:96 #, no-c-format +msgid "versatile" +msgstr "" + +#. Tag: entry +#: hardware.xml:100 +#, no-c-format +msgid "HP PA-RISC" +msgstr "" + +#. Tag: entry +#: hardware.xml:101 +#, no-c-format +msgid "hppa" +msgstr "" + +#. Tag: entry +#: hardware.xml:102 +#, no-c-format msgid "PA-RISC 1.1" msgstr "" #. Tag: entry -#: hardware.xml:97 +#: hardware.xml:103 #, no-c-format msgid "<entry>32</entry>" msgstr "" #. Tag: entry -#: hardware.xml:99 +#: hardware.xml:105 #, no-c-format msgid "PA-RISC 2.0" msgstr "" #. Tag: entry -#: hardware.xml:100 +#: hardware.xml:106 #, no-c-format msgid "<entry>64</entry>" msgstr "" #. Tag: entry -#: hardware.xml:104 +#: hardware.xml:110 #, no-c-format msgid "Intel IA-64" msgstr "" #. Tag: entry -#: hardware.xml:105 +#: hardware.xml:111 #, no-c-format msgid "ia64" msgstr "" #. Tag: entry -#: hardware.xml:111 +#: hardware.xml:117 #, no-c-format msgid "MIPS (big endian)" msgstr "" #. Tag: entry -#: hardware.xml:112 +#: hardware.xml:118 #, no-c-format msgid "mips" msgstr "" #. Tag: entry -#: hardware.xml:113 +#: hardware.xml:119 #, no-c-format msgid "SGI IP22 (Indy/Indigo 2)" msgstr "" #. Tag: entry -#: hardware.xml:114 +#: hardware.xml:120 #, no-c-format msgid "r4k-ip22" msgstr "" #. Tag: entry -#: hardware.xml:116 +#: hardware.xml:122 #, no-c-format msgid "SGI IP32 (O2)" msgstr "" #. Tag: entry -#: hardware.xml:117 +#: hardware.xml:123 #, no-c-format msgid "r5k-ip32" msgstr "" #. Tag: entry -#: hardware.xml:119 hardware.xml:132 +#: hardware.xml:125 hardware.xml:144 +#, no-c-format +msgid "MIPS Malta (32 bit)" +msgstr "" + +#. Tag: entry +#: hardware.xml:126 hardware.xml:145 +#, no-c-format +msgid "4kc-malta" +msgstr "" + +#. Tag: entry +#: hardware.xml:128 hardware.xml:147 +#, no-c-format +msgid "MIPS Malta (64 bit)" +msgstr "" + +#. Tag: entry +#: hardware.xml:129 hardware.xml:148 +#, no-c-format +msgid "5kc-malta" +msgstr "" + +#. Tag: entry +#: hardware.xml:131 hardware.xml:150 #, no-c-format msgid "Broadcom BCM91250A (SWARM)" msgstr "" #. Tag: entry -#: hardware.xml:120 hardware.xml:133 +#: hardware.xml:132 hardware.xml:151 #, no-c-format msgid "sb1-bcm91250a" msgstr "" #. Tag: entry -#: hardware.xml:122 hardware.xml:135 +#: hardware.xml:134 hardware.xml:153 #, no-c-format msgid "Broadcom BCM91480B (BigSur)" msgstr "" #. Tag: entry -#: hardware.xml:123 hardware.xml:136 +#: hardware.xml:135 hardware.xml:154 #, no-c-format msgid "sb1a-bcm91480b" msgstr "" #. Tag: entry -#: hardware.xml:127 +#: hardware.xml:139 #, no-c-format msgid "MIPS (little endian)" msgstr "" #. Tag: entry -#: hardware.xml:128 +#: hardware.xml:140 #, no-c-format msgid "mipsel" msgstr "" #. Tag: entry -#: hardware.xml:129 +#: hardware.xml:141 #, no-c-format msgid "Cobalt" msgstr "" #. Tag: entry -#: hardware.xml:130 +#: hardware.xml:142 #, no-c-format msgid "cobalt" msgstr "" #. Tag: entry -#: hardware.xml:140 +#: hardware.xml:158 #, no-c-format msgid "Motorola 680x0" msgstr "" #. Tag: entry -#: hardware.xml:141 +#: hardware.xml:159 #, no-c-format msgid "m68k" msgstr "" #. Tag: entry -#: hardware.xml:142 +#: hardware.xml:160 #, no-c-format msgid "Atari" msgstr "" #. Tag: entry -#: hardware.xml:143 +#: hardware.xml:161 #, no-c-format msgid "atari" msgstr "" #. Tag: entry -#: hardware.xml:145 +#: hardware.xml:163 #, no-c-format msgid "Amiga" msgstr "" #. Tag: entry -#: hardware.xml:146 +#: hardware.xml:164 #, no-c-format msgid "amiga" msgstr "" #. Tag: entry -#: hardware.xml:148 +#: hardware.xml:166 #, no-c-format msgid "68k Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:149 +#: hardware.xml:167 #, no-c-format msgid "<entry>mac</entry>" msgstr "" #. Tag: entry -#: hardware.xml:151 +#: hardware.xml:169 #, no-c-format msgid "<entry>VME</entry>" msgstr "" #. Tag: entry -#: hardware.xml:152 +#: hardware.xml:170 #, no-c-format msgid "bvme6000" msgstr "" #. Tag: entry -#: hardware.xml:154 +#: hardware.xml:172 #, no-c-format msgid "mvme147" msgstr "" #. Tag: entry -#: hardware.xml:156 +#: hardware.xml:174 #, no-c-format msgid "mvme16x" msgstr "" #. Tag: entry -#: hardware.xml:160 +#: hardware.xml:178 #, no-c-format msgid "IBM/Motorola PowerPC" msgstr "" #. Tag: entry -#: hardware.xml:161 +#: hardware.xml:179 #, no-c-format msgid "<entry>powerpc</entry>" msgstr "" #. Tag: entry -#: hardware.xml:162 +#: hardware.xml:180 #, no-c-format msgid "CHRP" msgstr "" #. Tag: entry -#: hardware.xml:163 +#: hardware.xml:181 #, no-c-format msgid "chrp" msgstr "" #. Tag: entry -#: hardware.xml:165 +#: hardware.xml:183 #, no-c-format msgid "PowerMac" msgstr "" #. Tag: entry -#: hardware.xml:166 +#: hardware.xml:184 #, no-c-format msgid "pmac" msgstr "" #. Tag: entry -#: hardware.xml:168 +#: hardware.xml:186 #, no-c-format msgid "PReP" msgstr "" #. Tag: entry -#: hardware.xml:169 +#: hardware.xml:187 #, no-c-format msgid "<entry>prep</entry>" msgstr "" #. Tag: entry -#: hardware.xml:173 +#: hardware.xml:191 #, no-c-format msgid "Sun SPARC" msgstr "" #. Tag: entry -#: hardware.xml:174 +#: hardware.xml:192 #, no-c-format msgid "sparc" msgstr "" #. Tag: entry -#: hardware.xml:175 +#: hardware.xml:193 #, no-c-format msgid "<entry>sun4u</entry>" msgstr "" #. Tag: entry -#: hardware.xml:176 +#: hardware.xml:194 #, no-c-format msgid "sparc64" msgstr "" #. Tag: entry -#: hardware.xml:178 +#: hardware.xml:196 #, no-c-format msgid "<entry>sun4v</entry>" msgstr "" #. Tag: entry -#: hardware.xml:182 +#: hardware.xml:200 #, no-c-format msgid "IBM S/390" msgstr "" #. Tag: entry -#: hardware.xml:183 +#: hardware.xml:201 #, no-c-format msgid "s390" msgstr "" #. Tag: entry -#: hardware.xml:184 +#: hardware.xml:202 #, no-c-format msgid "IPL from VM-reader and DASD" msgstr "" #. Tag: entry -#: hardware.xml:185 +#: hardware.xml:203 #, no-c-format msgid "generic" msgstr "" #. Tag: entry -#: hardware.xml:187 +#: hardware.xml:205 #, no-c-format msgid "IPL from tape" msgstr "" #. Tag: entry -#: hardware.xml:188 +#: hardware.xml:206 #, no-c-format msgid "tape" msgstr "" #. Tag: para -#: hardware.xml:193 +#: hardware.xml:211 #, 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:201 +#: hardware.xml:219 #, 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:223 hardware.xml:682 hardware.xml:718 hardware.xml:796 hardware.xml:815 hardware.xml:901 hardware.xml:943 hardware.xml:1011 hardware.xml:1077 +#: hardware.xml:241 hardware.xml:700 hardware.xml:736 hardware.xml:840 hardware.xml:859 hardware.xml:945 hardware.xml:987 hardware.xml:1061 hardware.xml:1133 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para -#: hardware.xml:224 +#: hardware.xml:242 #, 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:231 +#: hardware.xml:249 #, 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:239 +#: hardware.xml:257 #, 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:256 +#: hardware.xml:274 #, no-c-format msgid "Hardware Type" msgstr "" #. Tag: entry -#: hardware.xml:257 +#: hardware.xml:275 #, no-c-format msgid "Aliases" msgstr "" #. Tag: entry -#: hardware.xml:257 +#: hardware.xml:275 #, no-c-format msgid "MILO image" msgstr "" #. Tag: entry -#: hardware.xml:263 +#: hardware.xml:281 #, no-c-format msgid "ALCOR" msgstr "" #. Tag: entry -#: hardware.xml:264 +#: hardware.xml:282 #, no-c-format msgid "AlphaStation 500 5/266.300" msgstr "" #. Tag: entry -#: hardware.xml:265 +#: hardware.xml:283 #, no-c-format msgid "Maverick" msgstr "" #. Tag: entry -#: hardware.xml:266 hardware.xml:270 hardware.xml:274 +#: hardware.xml:284 hardware.xml:288 hardware.xml:292 #, no-c-format msgid "alcor" msgstr "" #. Tag: entry -#: hardware.xml:268 +#: hardware.xml:286 #, no-c-format msgid "AlphaStation 500 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:269 +#: hardware.xml:287 #, no-c-format msgid "Bret" msgstr "" #. Tag: entry -#: hardware.xml:272 +#: hardware.xml:290 #, no-c-format msgid "AlphaStation 600/266...300" msgstr "" #. Tag: entry -#: hardware.xml:273 +#: hardware.xml:291 #, no-c-format msgid "Alcor" msgstr "" #. Tag: entry -#: hardware.xml:276 +#: hardware.xml:294 #, no-c-format msgid "AlphaStation 600/300...433" msgstr "" #. Tag: entry -#: hardware.xml:277 +#: hardware.xml:295 #, no-c-format msgid "<entry>XLT</entry>" msgstr "" #. Tag: entry -#: hardware.xml:278 +#: hardware.xml:296 #, no-c-format msgid "<entry>xlt</entry>" msgstr "" #. Tag: entry -#: hardware.xml:282 +#: hardware.xml:300 #, no-c-format msgid "BOOK1" msgstr "" #. Tag: entry -#: hardware.xml:283 +#: hardware.xml:301 #, no-c-format msgid "AlphaBook1 (laptop)" msgstr "" #. Tag: entry -#: hardware.xml:284 +#: hardware.xml:302 #, no-c-format msgid "Alphabook1/Burns" msgstr "" #. Tag: entry -#: hardware.xml:285 +#: hardware.xml:303 #, no-c-format msgid "book1" msgstr "" #. Tag: entry -#: hardware.xml:289 +#: hardware.xml:307 #, no-c-format msgid "AVANTI" msgstr "" #. Tag: entry -#: hardware.xml:290 +#: hardware.xml:308 #, no-c-format msgid "AlphaStation 200 4/100...166" msgstr "" #. Tag: entry -#: hardware.xml:291 +#: hardware.xml:309 #, no-c-format msgid "Mustang" msgstr "" #. Tag: entry -#: hardware.xml:292 hardware.xml:296 hardware.xml:300 hardware.xml:304 hardware.xml:308 hardware.xml:312 hardware.xml:316 hardware.xml:320 +#: hardware.xml:310 hardware.xml:314 hardware.xml:318 hardware.xml:322 hardware.xml:326 hardware.xml:330 hardware.xml:334 hardware.xml:338 #, no-c-format msgid "avanti" msgstr "" #. Tag: entry -#: hardware.xml:294 +#: hardware.xml:312 #, no-c-format msgid "AlphaStation 200 4/233" msgstr "" #. Tag: entry -#: hardware.xml:295 +#: hardware.xml:313 #, no-c-format msgid "Mustang+" msgstr "" #. Tag: entry -#: hardware.xml:298 +#: hardware.xml:316 #, no-c-format msgid "AlphaStation 205 4/133...333" msgstr "" #. Tag: entry -#: hardware.xml:299 +#: hardware.xml:317 #, no-c-format msgid "<entry>LX3</entry>" msgstr "" #. Tag: entry -#: hardware.xml:302 +#: hardware.xml:320 #, no-c-format msgid "AlphaStation 250 4/300" msgstr "" #. Tag: entry -#: hardware.xml:303 +#: hardware.xml:321 #, no-c-format msgid "<entry>M3+</entry>" msgstr "" #. Tag: entry -#: hardware.xml:306 +#: hardware.xml:324 #, no-c-format msgid "AlphaStation 255 4/133...333" msgstr "" #. Tag: entry -#: hardware.xml:307 +#: hardware.xml:325 #, no-c-format msgid "LX3+" msgstr "" #. Tag: entry -#: hardware.xml:310 +#: hardware.xml:328 #, no-c-format msgid "AlphaStation 300 4/266" msgstr "" #. Tag: entry -#: hardware.xml:311 +#: hardware.xml:329 #, no-c-format msgid "Melmac" msgstr "" #. Tag: entry -#: hardware.xml:314 +#: hardware.xml:332 #, no-c-format msgid "AlphaStation 400 4/166" msgstr "" #. Tag: entry -#: hardware.xml:315 +#: hardware.xml:333 #, no-c-format msgid "Chinet" msgstr "" #. Tag: entry -#: hardware.xml:318 +#: hardware.xml:336 #, no-c-format msgid "AlphaStation 400 4/233...300" msgstr "" #. Tag: entry -#: hardware.xml:319 +#: hardware.xml:337 #, no-c-format msgid "Avanti" msgstr "" #. Tag: entry -#: hardware.xml:324 hardware.xml:337 hardware.xml:338 +#: hardware.xml:342 hardware.xml:355 hardware.xml:356 #, no-c-format msgid "EB164" msgstr "" #. Tag: entry -#: hardware.xml:325 +#: hardware.xml:343 #, no-c-format msgid "AlphaPC164" msgstr "" #. Tag: entry -#: hardware.xml:326 +#: hardware.xml:344 #, no-c-format msgid "PC164" msgstr "" #. Tag: entry -#: hardware.xml:327 +#: hardware.xml:345 #, no-c-format msgid "pc164" msgstr "" #. Tag: entry -#: hardware.xml:329 +#: hardware.xml:347 #, no-c-format msgid "AlphaPC164-LX" msgstr "" #. Tag: entry -#: hardware.xml:330 +#: hardware.xml:348 #, no-c-format msgid "LX164" msgstr "" #. Tag: entry -#: hardware.xml:331 +#: hardware.xml:349 #, no-c-format msgid "lx164" msgstr "" #. Tag: entry -#: hardware.xml:333 +#: hardware.xml:351 #, no-c-format msgid "AlphaPC164-SX" msgstr "" #. Tag: entry -#: hardware.xml:334 +#: hardware.xml:352 #, no-c-format msgid "SX164" msgstr "" #. Tag: entry -#: hardware.xml:335 +#: hardware.xml:353 #, no-c-format msgid "sx164" msgstr "" #. Tag: entry -#: hardware.xml:339 +#: hardware.xml:357 #, no-c-format msgid "eb164" msgstr "" #. Tag: entry -#: hardware.xml:343 hardware.xml:352 hardware.xml:353 +#: hardware.xml:361 hardware.xml:370 hardware.xml:371 #, no-c-format msgid "EB64+" msgstr "" #. Tag: entry -#: hardware.xml:344 +#: hardware.xml:362 #, no-c-format msgid "AlphaPC64" msgstr "" #. Tag: entry -#: hardware.xml:345 hardware.xml:349 +#: hardware.xml:363 hardware.xml:367 #, no-c-format msgid "Cabriolet" msgstr "" #. Tag: entry -#: hardware.xml:346 hardware.xml:350 +#: hardware.xml:364 hardware.xml:368 #, no-c-format msgid "cabriolet" msgstr "" #. Tag: entry -#: hardware.xml:348 +#: hardware.xml:366 #, no-c-format msgid "AlphaPCI64" msgstr "" #. Tag: entry -#: hardware.xml:354 +#: hardware.xml:372 #, no-c-format msgid "eb64p" msgstr "" #. Tag: entry -#: hardware.xml:358 hardware.xml:359 hardware.xml:360 +#: hardware.xml:376 hardware.xml:377 hardware.xml:378 #, no-c-format msgid "EB66" msgstr "" #. Tag: entry -#: hardware.xml:361 +#: hardware.xml:379 #, no-c-format msgid "eb66" msgstr "" #. Tag: entry -#: hardware.xml:363 hardware.xml:364 +#: hardware.xml:381 hardware.xml:382 #, no-c-format msgid "EB66+" msgstr "" #. Tag: entry -#: hardware.xml:365 +#: hardware.xml:383 #, no-c-format msgid "eb66p" msgstr "" #. Tag: entry -#: hardware.xml:369 +#: hardware.xml:387 #, no-c-format msgid "JENSEN" msgstr "" #. Tag: entry -#: hardware.xml:370 +#: hardware.xml:388 #, no-c-format msgid "DEC 2000 Model 300(S)" msgstr "" #. Tag: entry -#: hardware.xml:371 hardware.xml:379 +#: hardware.xml:389 hardware.xml:397 #, no-c-format msgid "Jensen" msgstr "" #. Tag: entry -#: hardware.xml:372 hardware.xml:376 hardware.xml:380 hardware.xml:441 hardware.xml:445 hardware.xml:463 hardware.xml:467 hardware.xml:471 hardware.xml:475 hardware.xml:479 hardware.xml:483 hardware.xml:487 hardware.xml:501 hardware.xml:505 hardware.xml:509 hardware.xml:513 hardware.xml:517 hardware.xml:551 hardware.xml:555 hardware.xml:559 hardware.xml:563 hardware.xml:577 hardware.xml:581 hardware.xml:585 hardware.xml:589 hardware.xml:596 hardware.xml:600 hardware.xml:604 hardware.xml:608 hardware.xml:612 hardware.xml:616 hardware.xml:620 hardware.xml:624 hardware.xml:628 hardware.xml:632 hardware.xml:636 hardware.xml:640 hardware.xml:644 hardware.xml:651 hardware.xml:655 +#: hardware.xml:390 hardware.xml:394 hardware.xml:398 hardware.xml:459 hardware.xml:463 hardware.xml:481 hardware.xml:485 hardware.xml:489 hardware.xml:493 hardware.xml:497 hardware.xml:501 hardware.xml:505 hardware.xml:519 hardware.xml:523 hardware.xml:527 hardware.xml:531 hardware.xml:535 hardware.xml:569 hardware.xml:573 hardware.xml:577 hardware.xml:581 hardware.xml:595 hardware.xml:599 hardware.xml:603 hardware.xml:607 hardware.xml:614 hardware.xml:618 hardware.xml:622 hardware.xml:626 hardware.xml:630 hardware.xml:634 hardware.xml:638 hardware.xml:642 hardware.xml:646 hardware.xml:650 hardware.xml:654 hardware.xml:658 hardware.xml:662 hardware.xml:669 hardware.xml:673 #, no-c-format msgid "<entry>N/A</entry>" msgstr "" #. Tag: entry -#: hardware.xml:374 +#: hardware.xml:392 #, no-c-format msgid "DEC 2000 Model 500" msgstr "" #. Tag: entry -#: hardware.xml:375 +#: hardware.xml:393 #, no-c-format msgid "Culzen" msgstr "" #. Tag: entry -#: hardware.xml:378 +#: hardware.xml:396 #, no-c-format msgid "DECpc 150" msgstr "" #. Tag: entry -#: hardware.xml:384 +#: hardware.xml:402 #, no-c-format msgid "MIATA" msgstr "" #. Tag: entry -#: hardware.xml:385 +#: hardware.xml:403 #, no-c-format msgid "Personal WorkStation 433a" msgstr "" #. Tag: entry -#: hardware.xml:386 hardware.xml:390 hardware.xml:394 hardware.xml:398 hardware.xml:402 hardware.xml:406 hardware.xml:410 hardware.xml:414 +#: hardware.xml:404 hardware.xml:408 hardware.xml:412 hardware.xml:416 hardware.xml:420 hardware.xml:424 hardware.xml:428 hardware.xml:432 #, no-c-format msgid "Miata" msgstr "" #. Tag: entry -#: hardware.xml:387 hardware.xml:391 hardware.xml:395 hardware.xml:399 hardware.xml:403 hardware.xml:407 hardware.xml:411 hardware.xml:415 +#: hardware.xml:405 hardware.xml:409 hardware.xml:413 hardware.xml:417 hardware.xml:421 hardware.xml:425 hardware.xml:429 hardware.xml:433 #, no-c-format msgid "miata" msgstr "" #. Tag: entry -#: hardware.xml:389 +#: hardware.xml:407 #, no-c-format msgid "Personal WorkStation 433au" msgstr "" #. Tag: entry -#: hardware.xml:393 +#: hardware.xml:411 #, no-c-format msgid "Personal WorkStation 466au" msgstr "" #. Tag: entry -#: hardware.xml:397 +#: hardware.xml:415 #, no-c-format msgid "Personal WorkStation 500a" msgstr "" #. Tag: entry -#: hardware.xml:401 +#: hardware.xml:419 #, no-c-format msgid "Personal WorkStation 500au" msgstr "" #. Tag: entry -#: hardware.xml:405 +#: hardware.xml:423 #, no-c-format msgid "Personal WorkStation 550au" msgstr "" #. Tag: entry -#: hardware.xml:409 +#: hardware.xml:427 #, no-c-format msgid "Personal WorkStation 600a" msgstr "" #. Tag: entry -#: hardware.xml:413 +#: hardware.xml:431 #, no-c-format msgid "Personal WorkStation 600au" msgstr "" #. Tag: entry -#: hardware.xml:419 +#: hardware.xml:437 #, no-c-format msgid "MIKASA" msgstr "" #. Tag: entry -#: hardware.xml:420 +#: hardware.xml:438 #, no-c-format msgid "AlphaServer 1000 4/200" msgstr "" #. Tag: entry -#: hardware.xml:421 +#: hardware.xml:439 #, no-c-format msgid "Mikasa" msgstr "" #. Tag: entry -#: hardware.xml:422 hardware.xml:426 hardware.xml:430 hardware.xml:434 +#: hardware.xml:440 hardware.xml:444 hardware.xml:448 hardware.xml:452 #, no-c-format msgid "mikasa" msgstr "" #. Tag: entry -#: hardware.xml:424 +#: hardware.xml:442 #, no-c-format msgid "AlphaServer 1000 4/233..266" msgstr "" #. Tag: entry -#: hardware.xml:425 +#: hardware.xml:443 #, no-c-format msgid "Mikasa+" msgstr "" #. Tag: entry -#: hardware.xml:428 hardware.xml:432 +#: hardware.xml:446 hardware.xml:450 #, no-c-format msgid "AlphaServer 1000 5/300" msgstr "" #. Tag: entry -#: hardware.xml:429 +#: hardware.xml:447 #, no-c-format msgid "Mikasa-Pinnacle" msgstr "" #. Tag: entry -#: hardware.xml:433 +#: hardware.xml:451 #, no-c-format msgid "Mikasa-Primo" msgstr "" #. Tag: entry -#: hardware.xml:438 +#: hardware.xml:456 #, no-c-format msgid "NAUTILUS" msgstr "" #. Tag: entry -#: hardware.xml:439 +#: hardware.xml:457 #, no-c-format msgid "UP1000" msgstr "" #. Tag: entry -#: hardware.xml:440 +#: hardware.xml:458 #, no-c-format msgid "Nautilus" msgstr "" #. Tag: entry -#: hardware.xml:443 +#: hardware.xml:461 #, no-c-format msgid "UP1100" msgstr "" #. Tag: entry -#: hardware.xml:444 +#: hardware.xml:462 #, no-c-format msgid "Galaxy-Train/Nautilus Jr." msgstr "" #. Tag: entry -#: hardware.xml:449 +#: hardware.xml:467 #, no-c-format msgid "NONAME" msgstr "" #. Tag: entry -#: hardware.xml:450 +#: hardware.xml:468 #, no-c-format msgid "AXPpci33" msgstr "" #. Tag: entry -#: hardware.xml:451 +#: hardware.xml:469 #, no-c-format msgid "Noname" msgstr "" #. Tag: entry -#: hardware.xml:452 hardware.xml:456 +#: hardware.xml:470 hardware.xml:474 #, no-c-format msgid "noname" msgstr "" #. Tag: entry -#: hardware.xml:454 +#: hardware.xml:472 #, no-c-format msgid "<entry>UDB</entry>" msgstr "" #. Tag: entry -#: hardware.xml:455 +#: hardware.xml:473 #, no-c-format msgid "Multia" msgstr "" #. Tag: entry -#: hardware.xml:460 +#: hardware.xml:478 #, no-c-format msgid "NORITAKE" msgstr "" #. Tag: entry -#: hardware.xml:461 +#: hardware.xml:479 #, no-c-format msgid "AlphaServer 1000A 4/233...266" msgstr "" #. Tag: entry -#: hardware.xml:462 +#: hardware.xml:480 #, no-c-format msgid "Noritake" msgstr "" #. Tag: entry -#: hardware.xml:465 +#: hardware.xml:483 #, no-c-format msgid "AlphaServer 1000A 5/300" msgstr "" #. Tag: entry -#: hardware.xml:466 +#: hardware.xml:484 #, no-c-format msgid "Noritake-Pinnacle" msgstr "" #. Tag: entry -#: hardware.xml:469 +#: hardware.xml:487 #, no-c-format msgid "AlphaServer 1000A 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:470 +#: hardware.xml:488 #, no-c-format msgid "Noritake-Primo" msgstr "" #. Tag: entry -#: hardware.xml:473 +#: hardware.xml:491 #, no-c-format msgid "AlphaServer 800 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:474 hardware.xml:482 hardware.xml:486 +#: hardware.xml:492 hardware.xml:500 hardware.xml:504 #, no-c-format msgid "Corelle" msgstr "" #. Tag: entry -#: hardware.xml:477 +#: hardware.xml:495 #, no-c-format msgid "AlphaStation 600 A" msgstr "" #. Tag: entry -#: hardware.xml:478 +#: hardware.xml:496 #, no-c-format msgid "Alcor-Primo" msgstr "" #. Tag: entry -#: hardware.xml:481 +#: hardware.xml:499 #, no-c-format msgid "Digital Server 3300" msgstr "" #. Tag: entry -#: hardware.xml:485 +#: hardware.xml:503 #, no-c-format msgid "Digital Server 3300R" msgstr "" #. Tag: entry -#: hardware.xml:491 +#: hardware.xml:509 #, no-c-format msgid "PLATFORM 2000" msgstr "" #. Tag: entry -#: hardware.xml:492 hardware.xml:493 +#: hardware.xml:510 hardware.xml:511 #, no-c-format msgid "<entry>P2K</entry>" msgstr "" #. Tag: entry -#: hardware.xml:494 +#: hardware.xml:512 #, no-c-format msgid "<entry>p2k</entry>" msgstr "" #. Tag: entry -#: hardware.xml:498 +#: hardware.xml:516 #, no-c-format msgid "RAWHIDE" msgstr "" #. Tag: entry -#: hardware.xml:499 +#: hardware.xml:517 #, no-c-format msgid "AlphaServer 1200 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:500 hardware.xml:512 +#: hardware.xml:518 hardware.xml:530 #, no-c-format msgid "Tincup/DaVinci" msgstr "" #. Tag: entry -#: hardware.xml:503 +#: hardware.xml:521 #, no-c-format msgid "AlphaServer 4000 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:504 +#: hardware.xml:522 #, no-c-format msgid "Wrangler/Durango" msgstr "" #. Tag: entry -#: hardware.xml:507 +#: hardware.xml:525 #, no-c-format msgid "AlphaServer 4100 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:508 hardware.xml:516 +#: hardware.xml:526 hardware.xml:534 #, no-c-format msgid "Dodge" msgstr "" #. Tag: entry -#: hardware.xml:511 +#: hardware.xml:529 #, no-c-format msgid "Digital Server 5300" msgstr "" #. Tag: entry -#: hardware.xml:515 +#: hardware.xml:533 #, no-c-format msgid "Digital Server 7300" msgstr "" #. Tag: entry -#: hardware.xml:521 +#: hardware.xml:539 #, no-c-format msgid "RUFFIAN" msgstr "" #. Tag: entry -#: hardware.xml:522 +#: hardware.xml:540 #, no-c-format msgid "DeskStation AlphaPC164-UX" msgstr "" #. Tag: entry -#: hardware.xml:523 hardware.xml:527 hardware.xml:531 hardware.xml:535 hardware.xml:539 hardware.xml:543 +#: hardware.xml:541 hardware.xml:545 hardware.xml:549 hardware.xml:553 hardware.xml:557 hardware.xml:561 #, no-c-format msgid "Ruffian" msgstr "" #. Tag: entry -#: hardware.xml:524 hardware.xml:528 hardware.xml:532 hardware.xml:536 hardware.xml:540 hardware.xml:544 +#: hardware.xml:542 hardware.xml:546 hardware.xml:550 hardware.xml:554 hardware.xml:558 hardware.xml:562 #, no-c-format msgid "ruffian" msgstr "" #. Tag: entry -#: hardware.xml:526 +#: hardware.xml:544 #, no-c-format msgid "DeskStation RPL164-2" msgstr "" #. Tag: entry -#: hardware.xml:530 +#: hardware.xml:548 #, no-c-format msgid "DeskStation RPL164-4" msgstr "" #. Tag: entry -#: hardware.xml:534 +#: hardware.xml:552 #, no-c-format msgid "DeskStation RPX164-2" msgstr "" #. Tag: entry -#: hardware.xml:538 +#: hardware.xml:556 #, no-c-format msgid "DeskStation RPX164-4" msgstr "" #. Tag: entry -#: hardware.xml:542 +#: hardware.xml:560 #, no-c-format msgid "Samsung AlphaPC164-BX" msgstr "" #. Tag: entry -#: hardware.xml:548 +#: hardware.xml:566 #, no-c-format msgid "SABLE" msgstr "" #. Tag: entry -#: hardware.xml:549 +#: hardware.xml:567 #, no-c-format msgid "AlphaServer 2000 4/xxx" msgstr "" #. Tag: entry -#: hardware.xml:550 +#: hardware.xml:568 #, no-c-format msgid "Demi-Sable" msgstr "" #. Tag: entry -#: hardware.xml:553 +#: hardware.xml:571 #, no-c-format msgid "AlphaServer 2000 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:554 +#: hardware.xml:572 #, no-c-format msgid "Demi-Gamma-Sable" msgstr "" #. Tag: entry -#: hardware.xml:557 +#: hardware.xml:575 #, no-c-format msgid "AlphaServer 2100 4/xxx" msgstr "" #. Tag: entry -#: hardware.xml:558 +#: hardware.xml:576 #, no-c-format msgid "Sable" msgstr "" #. Tag: entry -#: hardware.xml:561 +#: hardware.xml:579 #, no-c-format msgid "AlphaServer 2100 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:562 +#: hardware.xml:580 #, no-c-format msgid "Gamma-Sable" msgstr "" #. Tag: entry -#: hardware.xml:567 +#: hardware.xml:585 #, no-c-format msgid "TAKARA" msgstr "" #. Tag: entry -#: hardware.xml:568 +#: hardware.xml:586 #, no-c-format msgid "21164 PICMG SBC" msgstr "" #. Tag: entry -#: hardware.xml:569 +#: hardware.xml:587 #, no-c-format msgid "Takara" msgstr "" #. Tag: entry -#: hardware.xml:570 +#: hardware.xml:588 #, no-c-format msgid "takara" msgstr "" #. Tag: entry -#: hardware.xml:574 +#: hardware.xml:592 #, no-c-format msgid "TITAN" msgstr "" #. Tag: entry -#: hardware.xml:575 +#: hardware.xml:593 #, no-c-format msgid "AlphaServer DS15" msgstr "" #. Tag: entry -#: hardware.xml:576 +#: hardware.xml:594 #, no-c-format msgid "HyperBrick2" msgstr "" #. Tag: entry -#: hardware.xml:579 +#: hardware.xml:597 #, no-c-format msgid "AlphaServer DS25" msgstr "" #. Tag: entry -#: hardware.xml:580 +#: hardware.xml:598 #, no-c-format msgid "Granite" msgstr "" #. Tag: entry -#: hardware.xml:583 +#: hardware.xml:601 #, no-c-format msgid "AlphaServer ES45" msgstr "" #. Tag: entry -#: hardware.xml:584 +#: hardware.xml:602 #, no-c-format msgid "Privateer" msgstr "" #. Tag: entry -#: hardware.xml:587 hardware.xml:626 hardware.xml:630 +#: hardware.xml:605 hardware.xml:644 hardware.xml:648 #, no-c-format msgid "UNKNOWN" msgstr "" #. Tag: entry -#: hardware.xml:588 +#: hardware.xml:606 #, no-c-format msgid "Yukon" msgstr "" #. Tag: entry -#: hardware.xml:593 +#: hardware.xml:611 #, no-c-format msgid "TSUNAMI" msgstr "" #. Tag: entry -#: hardware.xml:594 +#: hardware.xml:612 #, no-c-format msgid "AlphaServer DS10" msgstr "" #. Tag: entry -#: hardware.xml:595 hardware.xml:643 +#: hardware.xml:613 hardware.xml:661 #, no-c-format msgid "Webbrick" msgstr "" #. Tag: entry -#: hardware.xml:598 +#: hardware.xml:616 #, no-c-format msgid "AlphaServer DS10L" msgstr "" #. Tag: entry -#: hardware.xml:599 +#: hardware.xml:617 #, no-c-format msgid "Slate" msgstr "" #. Tag: entry -#: hardware.xml:602 +#: hardware.xml:620 #, no-c-format msgid "AlphaServer DS20" msgstr "" #. Tag: entry -#: hardware.xml:603 +#: hardware.xml:621 #, no-c-format msgid "Catamaran/Goldrush" msgstr "" #. Tag: entry -#: hardware.xml:606 +#: hardware.xml:624 #, no-c-format msgid "AlphaServer DS20E" msgstr "" #. Tag: entry -#: hardware.xml:607 +#: hardware.xml:625 #, no-c-format msgid "Goldrack" msgstr "" #. Tag: entry -#: hardware.xml:610 +#: hardware.xml:628 #, no-c-format msgid "AlphaServer DS20L" msgstr "" #. Tag: entry -#: hardware.xml:611 +#: hardware.xml:629 #, no-c-format msgid "Shark" msgstr "" #. Tag: entry -#: hardware.xml:614 +#: hardware.xml:632 #, no-c-format msgid "AlphaServer ES40" msgstr "" #. Tag: entry -#: hardware.xml:615 +#: hardware.xml:633 #, no-c-format msgid "Clipper" msgstr "" #. Tag: entry -#: hardware.xml:618 hardware.xml:619 +#: hardware.xml:636 hardware.xml:637 #, no-c-format msgid "DP264" msgstr "" #. Tag: entry -#: hardware.xml:622 +#: hardware.xml:640 #, no-c-format msgid "SMARTengine 21264 PCI/ISA SBC" msgstr "" #. Tag: entry -#: hardware.xml:623 +#: hardware.xml:641 #, no-c-format msgid "Eiger" msgstr "" #. Tag: entry -#: hardware.xml:627 +#: hardware.xml:645 #, no-c-format msgid "Warhol" msgstr "" #. Tag: entry -#: hardware.xml:631 +#: hardware.xml:649 #, no-c-format msgid "Windjammer" msgstr "" #. Tag: entry -#: hardware.xml:634 +#: hardware.xml:652 #, no-c-format msgid "UP2000" msgstr "" #. Tag: entry -#: hardware.xml:635 +#: hardware.xml:653 #, no-c-format msgid "Swordfish" msgstr "" #. Tag: entry -#: hardware.xml:638 +#: hardware.xml:656 #, no-c-format msgid "XP1000" msgstr "" #. Tag: entry -#: hardware.xml:639 +#: hardware.xml:657 #, no-c-format msgid "Monet/Brisbane" msgstr "" #. Tag: entry -#: hardware.xml:642 +#: hardware.xml:660 #, no-c-format msgid "XP900" msgstr "" #. Tag: entry -#: hardware.xml:648 +#: hardware.xml:666 #, no-c-format msgid "WILDFIRE" msgstr "" #. Tag: entry -#: hardware.xml:649 +#: hardware.xml:667 #, no-c-format msgid "AlphaServer GS160" msgstr "" #. Tag: entry -#: hardware.xml:650 hardware.xml:654 +#: hardware.xml:668 hardware.xml:672 #, no-c-format msgid "Wildfire" msgstr "" #. Tag: entry -#: hardware.xml:653 +#: hardware.xml:671 #, no-c-format msgid "AlphaServer GS320" msgstr "" #. Tag: entry -#: hardware.xml:659 hardware.xml:661 +#: hardware.xml:677 hardware.xml:679 #, no-c-format msgid "<entry>XL</entry>" msgstr "" #. Tag: entry -#: hardware.xml:660 +#: hardware.xml:678 #, no-c-format msgid "XL-233...266" msgstr "" #. Tag: entry -#: hardware.xml:662 +#: hardware.xml:680 #, no-c-format msgid "<entry>xl</entry>" msgstr "" #. Tag: para -#: hardware.xml:667 +#: hardware.xml:685 #, 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:683 hardware.xml:816 +#: hardware.xml:701 hardware.xml:860 #, 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:691 hardware.xml:824 hardware.xml:984 +#: hardware.xml:709 hardware.xml:868 hardware.xml:1034 #, no-c-format msgid "<title>CPU</title>" msgstr "" #. Tag: para -#: hardware.xml:692 +#: hardware.xml:710 #, no-c-format msgid "Both AMD64 and Intel EM64T processors are supported." msgstr "" #. Tag: para -#: hardware.xml:720 +#: hardware.xml:738 #, 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:729 +#: hardware.xml:747 #, 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:737 +#: hardware.xml:755 #, no-c-format msgid "The supported platforms are:" msgstr "" #. Tag: term -#: hardware.xml:744 +#: hardware.xml:762 #, no-c-format msgid "Netwinder" msgstr "" #. Tag: para -#: hardware.xml:745 +#: hardware.xml:763 #, 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:758 +#: hardware.xml:776 #, no-c-format msgid "IOP32x" msgstr "" #. Tag: para -#: hardware.xml:759 +#: hardware.xml:777 #, 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:772 +#: hardware.xml:790 #, no-c-format msgid "IXP4xx" msgstr "" #. Tag: para -#: hardware.xml:773 +#: hardware.xml:791 #, 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:805 +#, no-c-format +msgid "Orion5x" +msgstr "" + #. Tag: para -#: hardware.xml:797 +#: hardware.xml:806 +#, no-c-format +msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: <ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>, <ulink url=\"&url-arm-cyrius-qnap;\">QNAP Turbo Station</ulink> (TS-109, TS-209 and TS-409)." +msgstr "" + +#. Tag: term +#: hardware.xml:821 +#, no-c-format +msgid "<term>Versatile</term>" +msgstr "" + +#. Tag: para +#: hardware.xml:822 +#, no-c-format +msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run Debian on ARM if you don't have the hardware." +msgstr "" + +#. Tag: para +#: hardware.xml:841 #, 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:825 +#: hardware.xml:869 #, 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:833 +#: hardware.xml:877 #, 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:840 +#: hardware.xml:884 #, 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:877 +#: hardware.xml:921 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:878 +#: hardware.xml:922 #, no-c-format msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, the Microchannel Architecture (MCA, used in IBM's PS/2 line), or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these." msgstr "" #. Tag: para -#: hardware.xml:902 +#: hardware.xml:946 #, 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:909 +#: hardware.xml:953 #, 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:917 +#: hardware.xml:961 #, 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:944 +#: hardware.xml:988 #, 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>." +msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run Debian on MIPS if you don't have the hardware. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: para -#: hardware.xml:985 +#: hardware.xml:1035 #, 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:995 +#: hardware.xml:1045 #, 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:1012 +#: hardware.xml:1062 #, no-c-format -msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> 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>." +msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run Debian on MIPS if you don't have the hardware. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: title -#: hardware.xml:1047 +#: hardware.xml:1103 #, no-c-format msgid "CPU/Machine types" msgstr "" #. Tag: para -#: hardware.xml:1049 +#: hardware.xml:1105 #, no-c-format msgid "All MIPS based Cobalt machines are supported." msgstr "" #. Tag: para -#: hardware.xml:1053 +#: hardware.xml:1109 #, 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:1063 +#: hardware.xml:1119 #, no-c-format msgid "Supported console options" msgstr "" #. Tag: para -#: hardware.xml:1064 +#: hardware.xml:1120 #, no-c-format msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps." msgstr "" #. Tag: para -#: hardware.xml:1078 +#: hardware.xml:1134 #, 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:1086 +#: hardware.xml:1142 #, 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:1094 +#: hardware.xml:1150 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:1096 +#: hardware.xml:1152 #, no-c-format msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:1103 +#: hardware.xml:1159 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:1104 +#: hardware.xml:1160 #, 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:1114 +#: hardware.xml:1170 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:1115 +#: hardware.xml:1171 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:1119 +#: hardware.xml:1175 #, 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:1125 +#: hardware.xml:1181 #, 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:1130 +#: hardware.xml:1186 #, 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:1139 +#: hardware.xml:1195 #, no-c-format msgid "<term>prep</term>" msgstr "" #. Tag: para -#: hardware.xml:1140 +#: hardware.xml:1196 #, no-c-format msgid "This kernel flavour supports the PReP subarchitecture." msgstr "" #. Tag: term -#: hardware.xml:1148 +#: hardware.xml:1204 #, no-c-format msgid "apus" msgstr "" #. Tag: para -#: hardware.xml:1149 +#: hardware.xml:1205 #, no-c-format msgid "This kernel flavour supports the Amiga Power-UP System, though it is currently disabled." msgstr "" #. Tag: title -#: hardware.xml:1162 +#: hardware.xml:1218 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:1164 +#: hardware.xml:1220 #, 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:1171 +#: hardware.xml:1227 #, 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:1179 +#: hardware.xml:1235 #, 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:1187 +#: hardware.xml:1243 #, 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:1203 hardware.xml:1338 hardware.xml:1382 hardware.xml:1411 +#: hardware.xml:1259 hardware.xml:1394 hardware.xml:1438 hardware.xml:1467 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:1204 +#: hardware.xml:1260 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:1210 +#: hardware.xml:1266 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:1211 +#: hardware.xml:1267 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:1212 hardware.xml:1215 hardware.xml:1218 hardware.xml:1221 hardware.xml:1224 hardware.xml:1227 hardware.xml:1230 hardware.xml:1233 hardware.xml:1236 hardware.xml:1239 hardware.xml:1242 hardware.xml:1245 hardware.xml:1248 hardware.xml:1251 hardware.xml:1254 hardware.xml:1257 +#: hardware.xml:1268 hardware.xml:1271 hardware.xml:1274 hardware.xml:1277 hardware.xml:1280 hardware.xml:1283 hardware.xml:1286 hardware.xml:1289 hardware.xml:1292 hardware.xml:1295 hardware.xml:1298 hardware.xml:1301 hardware.xml:1304 hardware.xml:1307 hardware.xml:1310 hardware.xml:1313 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:1214 +#: hardware.xml:1270 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:1217 +#: hardware.xml:1273 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:1220 +#: hardware.xml:1276 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:1223 +#: hardware.xml:1279 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:1226 +#: hardware.xml:1282 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:1229 +#: hardware.xml:1285 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:1232 +#: hardware.xml:1288 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:1235 +#: hardware.xml:1291 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:1238 +#: hardware.xml:1294 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:1241 +#: hardware.xml:1297 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:1244 +#: hardware.xml:1300 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:1247 +#: hardware.xml:1303 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:1250 +#: hardware.xml:1306 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:1253 +#: hardware.xml:1309 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:1256 +#: hardware.xml:1312 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:1259 +#: hardware.xml:1315 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:1260 hardware.xml:1263 hardware.xml:1266 hardware.xml:1269 hardware.xml:1272 hardware.xml:1275 hardware.xml:1278 hardware.xml:1281 hardware.xml:1284 hardware.xml:1287 hardware.xml:1290 hardware.xml:1293 hardware.xml:1299 hardware.xml:1302 hardware.xml:1308 hardware.xml:1314 hardware.xml:1320 +#: hardware.xml:1316 hardware.xml:1319 hardware.xml:1322 hardware.xml:1325 hardware.xml:1328 hardware.xml:1331 hardware.xml:1334 hardware.xml:1337 hardware.xml:1340 hardware.xml:1343 hardware.xml:1346 hardware.xml:1349 hardware.xml:1355 hardware.xml:1358 hardware.xml:1364 hardware.xml:1370 hardware.xml:1376 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:1262 +#: hardware.xml:1318 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:1265 +#: hardware.xml:1321 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:1268 +#: hardware.xml:1324 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:1271 +#: hardware.xml:1327 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:1274 +#: hardware.xml:1330 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:1277 +#: hardware.xml:1333 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:1280 +#: hardware.xml:1336 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:1283 +#: hardware.xml:1339 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:1286 +#: hardware.xml:1342 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:1289 +#: hardware.xml:1345 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:1292 +#: hardware.xml:1348 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:1297 +#: hardware.xml:1353 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:1298 +#: hardware.xml:1354 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:1301 +#: hardware.xml:1357 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:1306 +#: hardware.xml:1362 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:1307 +#: hardware.xml:1363 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:1312 +#: hardware.xml:1368 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1313 +#: hardware.xml:1369 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:1318 hardware.xml:1344 +#: hardware.xml:1374 hardware.xml:1400 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:1319 +#: hardware.xml:1375 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:1328 +#: hardware.xml:1384 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1345 +#: hardware.xml:1401 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:1347 +#: hardware.xml:1403 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:1349 +#: hardware.xml:1405 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:1351 +#: hardware.xml:1407 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:1353 +#: hardware.xml:1409 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:1357 hardware.xml:1388 +#: hardware.xml:1413 hardware.xml:1444 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:1358 +#: hardware.xml:1414 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:1360 +#: hardware.xml:1416 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:1362 +#: hardware.xml:1418 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:1364 +#: hardware.xml:1420 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:1372 +#: hardware.xml:1428 #, no-c-format msgid "CHRP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1389 +#: hardware.xml:1445 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:1392 +#: hardware.xml:1448 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:1393 +#: hardware.xml:1449 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: title -#: hardware.xml:1401 +#: hardware.xml:1457 #, no-c-format msgid "APUS subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1417 +#: hardware.xml:1473 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:1418 +#: hardware.xml:1474 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:1426 +#: hardware.xml:1482 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:1428 +#: hardware.xml:1484 #, 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:1465 +#: hardware.xml:1521 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:1467 +#: hardware.xml:1523 #, 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:1476 +#: hardware.xml:1532 #, 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:1484 +#: hardware.xml:1540 #, 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:1500 +#: hardware.xml:1556 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "" #. Tag: para -#: hardware.xml:1501 +#: hardware.xml:1557 #, 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:1523 +#: hardware.xml:1579 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para -#: hardware.xml:1524 +#: hardware.xml:1580 #, 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:1535 +#: hardware.xml:1591 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "" #. Tag: para -#: hardware.xml:1537 +#: hardware.xml:1593 #, 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:1544 +#: hardware.xml:1600 #, 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:1554 +#: hardware.xml:1610 #, no-c-format msgid "<term>sun4u</term>" msgstr "" #. Tag: para -#: hardware.xml:1556 +#: hardware.xml:1612 #, 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:1569 +#: hardware.xml:1625 #, no-c-format msgid "<term>sun4v</term>" msgstr "" #. Tag: para -#: hardware.xml:1571 +#: hardware.xml:1627 #, 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:1582 +#: hardware.xml:1638 #, 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:1591 +#: hardware.xml:1647 #, no-c-format msgid "Graphics Card Support" msgstr "" #. Tag: para -#: hardware.xml:1592 +#: hardware.xml:1648 #, 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:1600 +#: hardware.xml:1656 #, 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:1609 +#: hardware.xml:1665 #, 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:1618 +#: hardware.xml:1674 #, no-c-format msgid "The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: para -#: hardware.xml:1625 +#: hardware.xml:1681 #, 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:1635 +#: hardware.xml:1691 #, 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:1652 +#: hardware.xml:1708 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1653 +#: hardware.xml:1709 #, 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:1664 hardware.xml:1686 hardware.xml:1706 hardware.xml:1729 +#: hardware.xml:1720 hardware.xml:1742 hardware.xml:1762 hardware.xml:1785 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1665 +#: hardware.xml:1721 #, 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:1673 +#: hardware.xml:1729 #, 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:1688 +#: hardware.xml:1744 #, 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:1697 +#: hardware.xml:1753 #, 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:1707 +#: hardware.xml:1763 #, 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:1716 +#: hardware.xml:1772 #, 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:1730 +#: hardware.xml:1786 #, 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:1740 +#: hardware.xml:1796 #, 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:1746 +#: hardware.xml:1802 #, 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:1763 +#: hardware.xml:1819 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:1765 +#: hardware.xml:1821 #, 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:1776 +#: hardware.xml:1832 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:1777 +#: hardware.xml:1833 #, 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:1783 +#: hardware.xml:1839 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:1790 +#: hardware.xml:1846 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:1792 +#: hardware.xml:1848 #, 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:1799 +#: hardware.xml:1855 #, 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:1811 +#: hardware.xml:1867 #, 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:1821 +#: hardware.xml:1877 #, 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:1826 +#: hardware.xml:1882 #, 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:1835 +#: hardware.xml:1891 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines." msgstr "" #. Tag: para -#: hardware.xml:1839 +#: hardware.xml:1895 #, no-c-format msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card." msgstr "" #. Tag: title -#: hardware.xml:1857 +#: hardware.xml:1913 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:1859 +#: hardware.xml:1915 #, 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:1865 +#: hardware.xml:1921 #, 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:1870 +#: hardware.xml:1926 #, 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:1878 +#: hardware.xml:1934 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:1880 +#: hardware.xml:1936 #, 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:1892 +#: hardware.xml:1948 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:1894 +#: hardware.xml:1950 #, 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:1904 +#: hardware.xml:1960 #, 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:1910 +#: hardware.xml:1966 #, 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:1918 +#: hardware.xml:1974 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:1920 +#: hardware.xml:1976 #, 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:1932 +#: hardware.xml:1988 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:1934 +#: hardware.xml:1990 #, 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:1944 +#: hardware.xml:2000 #, 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:1951 +#: hardware.xml:2007 #, 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:1961 +#: hardware.xml:2017 #, 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:1971 +#: hardware.xml:2027 #, 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:2004 +#: hardware.xml:2060 #, 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:2013 +#: hardware.xml:2069 #, 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:2019 +#: hardware.xml:2075 #, 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:2025 +#: hardware.xml:2081 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:2030 +#: hardware.xml:2086 #, 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:2047 +#: hardware.xml:2103 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:2048 +#: hardware.xml:2104 #, 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:2054 +#: hardware.xml:2110 #, 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:2060 +#: hardware.xml:2116 #, 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:2066 +#: hardware.xml:2122 #, 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:2072 +#: hardware.xml:2128 #, 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:2078 +#: hardware.xml:2134 #, 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:2088 +#: hardware.xml:2144 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" #. Tag: para -#: hardware.xml:2090 +#: hardware.xml:2146 #, 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:2098 +#: hardware.xml:2154 #, 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:2103 +#: hardware.xml:2159 #, 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:2111 +#: hardware.xml:2167 #, 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:2122 +#: hardware.xml:2178 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:2123 +#: hardware.xml:2179 #, 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:2130 +#: hardware.xml:2186 #, 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:2141 +#: hardware.xml:2197 #, 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:2153 +#: hardware.xml:2209 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:2154 +#: hardware.xml:2210 #, 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:2167 +#: hardware.xml:2223 #, 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:2188 +#: hardware.xml:2244 #, 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:2205 +#: hardware.xml:2261 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:2207 +#: hardware.xml:2263 #, no-c-format msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>." msgstr "" #. Tag: para -#: hardware.xml:2214 +#: hardware.xml:2270 #, no-c-format msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users." msgstr "" #. Tag: para -#: hardware.xml:2231 +#: hardware.xml:2287 #, 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:2240 +#: hardware.xml:2296 #, 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:2248 +#: hardware.xml:2304 #, 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:2258 +#: hardware.xml:2314 #, no-c-format msgid "FIXME: is this still true?" msgstr "" #. Tag: title -#: hardware.xml:2269 +#: hardware.xml:2325 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:2270 +#: hardware.xml:2326 #, 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:2282 +#: hardware.xml:2338 #, 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:2288 +#: hardware.xml:2344 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:2293 +#: hardware.xml:2349 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:2298 +#: hardware.xml:2354 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:2303 +#: hardware.xml:2359 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:2308 +#: hardware.xml:2364 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:2315 +#: hardware.xml:2371 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:2320 +#: hardware.xml:2376 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:2325 +#: hardware.xml:2381 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:2330 +#: hardware.xml:2386 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:2339 +#: hardware.xml:2395 #, 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:2349 +#: hardware.xml:2405 #, 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:2358 +#: hardware.xml:2414 #, no-c-format msgid "Drivers Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:2359 +#: hardware.xml:2415 #, 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:2365 +#: hardware.xml:2421 #, 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:2376 +#: hardware.xml:2432 #, 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:2388 +#: hardware.xml:2444 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:2389 +#: hardware.xml:2445 #, 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:2396 +#: hardware.xml:2452 #, 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:2402 +#: hardware.xml:2458 #, 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:2416 +#: hardware.xml:2472 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:2417 +#: hardware.xml:2473 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:2424 +#: hardware.xml:2480 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:2426 +#: hardware.xml:2482 #, 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:2436 +#: hardware.xml:2492 #, 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:2444 +#: hardware.xml:2500 #, 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:2457 +#: hardware.xml:2513 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:2459 +#: hardware.xml:2515 #, 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 70c6e3060..2c991ea89 100644 --- a/po/pot/install-methods.pot +++ b/po/pot/install-methods.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2008-07-04 00:09+0000\n" +"POT-Creation-Date: 2008-09-01 00:10+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" @@ -137,95 +137,155 @@ msgstr "" #. Tag: para #: 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;." +msgid "A firmware image is provided for the Linksys NSLU2 which will automatically boot <classname>debian-installer</classname>. This image can be uploaded via the Linksys web frontend or with upslug2. This firmware image can be obtained from &nslu2-firmware-img;." +msgstr "" + +#. Tag: title +#: install-methods.xml:185 +#, no-c-format +msgid "Thecus N2100 Installation Files" +msgstr "" + +#. Tag: para +#: install-methods.xml:186 +#, no-c-format +msgid "A firmware image is provided for the Thecus N2100 which will automatically boot <classname>debian-installer</classname>. This image can be installed using the Thecus firmware upgrade process. This firmware image can be obtained from &n2100-firmware-img;." +msgstr "" + +#. Tag: title +#: install-methods.xml:197 +#, no-c-format +msgid "GLAN Tank Installation Files" +msgstr "" + +#. Tag: para +#: install-methods.xml:198 +#, no-c-format +msgid "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk on with you intend to install Debian. These images can be obtained from &glantank-firmware-img;." +msgstr "" + +#. Tag: title +#: install-methods.xml:208 +#, no-c-format +msgid "Kurobox Pro Installation Files" +msgstr "" + +#. Tag: para +#: install-methods.xml:209 +#, no-c-format +msgid "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the disk on with you intend to install Debian. These images can be obtained from &kuroboxpro-firmware-img;." msgstr "" #. Tag: title #: install-methods.xml:219 #, no-c-format +msgid "HP mv2120 Installation Files" +msgstr "" + +#. Tag: para +#: install-methods.xml:220 +#, no-c-format +msgid "A firmware image is provided for the HP mv2120 which will automatically boot <classname>debian-installer</classname>. This image can be installed with uphpmvault on Linux and other systems and with the HP Media Vault Firmware Recovery Utility on Windows. The firmware image can be obtained from &mv2120-firmware-img;." +msgstr "" + +#. Tag: title +#: install-methods.xml:232 +#, no-c-format +msgid "QNAP Turbo Station Installation Files" +msgstr "" + +#. Tag: para +#: install-methods.xml:233 +#, no-c-format +msgid "The QNAP Turbo Station (TS-109, TS-209 and TS-409) requires a kernel and ramdisk which can be obtained from &qnap-firmware-img;. A script is provided to write these images to flash." +msgstr "" + +#. Tag: title +#: install-methods.xml:279 +#, no-c-format msgid "Choosing a Kernel" msgstr "" #. Tag: para -#: install-methods.xml:221 +#: install-methods.xml:281 #, 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:230 +#: install-methods.xml:290 #, 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:248 +#: install-methods.xml:308 #, no-c-format msgid "Creating an IPL tape" msgstr "" #. Tag: para -#: install-methods.xml:250 +#: install-methods.xml:310 #, 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:274 +#: install-methods.xml:334 #, no-c-format msgid "Creating Floppies from Disk Images" msgstr "" #. Tag: para -#: install-methods.xml:275 +#: install-methods.xml:335 #, 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:280 +#: install-methods.xml:340 #, no-c-format msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives." msgstr "" #. Tag: para -#: install-methods.xml:285 +#: install-methods.xml:345 #, no-c-format msgid "Booting the installer from floppy disk is not supported on Amigas or 68k Macs." msgstr "" #. Tag: para -#: install-methods.xml:290 +#: install-methods.xml:350 #, 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:301 +#: install-methods.xml:361 #, 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:307 +#: install-methods.xml:367 #, 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:315 +#: install-methods.xml:375 #, 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:323 +#: install-methods.xml:383 #, no-c-format msgid "Writing Disk Images From a Linux or Unix System" msgstr "" #. Tag: para -#: install-methods.xml:324 +#: install-methods.xml:384 #, 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" @@ -234,253 +294,253 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:345 +#: install-methods.xml:405 #, 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:366 +#: install-methods.xml:426 #, 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:384 +#: install-methods.xml:444 #, no-c-format msgid "Writing Disk Images From DOS, Windows, or OS/2" msgstr "" #. Tag: para -#: install-methods.xml:386 +#: install-methods.xml:446 #, 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:391 +#: install-methods.xml:451 #, 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:399 +#: install-methods.xml:459 #, 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:405 +#: install-methods.xml:465 #, 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:418 +#: install-methods.xml:478 #, no-c-format msgid "Writing Disk Images on Atari Systems" msgstr "" #. Tag: para -#: install-methods.xml:419 +#: install-methods.xml:479 #, 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:430 +#: install-methods.xml:490 #, no-c-format msgid "Writing Disk Images on Macintosh Systems" msgstr "" #. Tag: para -#: install-methods.xml:431 +#: install-methods.xml:491 #, 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:447 +#: install-methods.xml:507 #, no-c-format msgid "Writing Disk Images From MacOS" msgstr "" #. Tag: para -#: install-methods.xml:448 +#: install-methods.xml:508 #, 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:459 +#: install-methods.xml:519 #, 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:470 +#: install-methods.xml:530 #, no-c-format msgid "Writing Disk Images with <command>Disk Copy</command>" msgstr "" #. Tag: para -#: install-methods.xml:471 +#: install-methods.xml:531 #, 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:480 +#: install-methods.xml:540 #, 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:487 +#: install-methods.xml:547 #, 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:494 +#: install-methods.xml:554 #, 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:503 +#: install-methods.xml:563 #, 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:510 +#: install-methods.xml:570 #, 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:525 +#: install-methods.xml:585 #, no-c-format msgid "Writing Disk Images with <command>suntar</command>" msgstr "" #. Tag: para -#: install-methods.xml:529 +#: install-methods.xml:589 #, 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:537 +#: install-methods.xml:597 #, no-c-format msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)." msgstr "" #. Tag: para -#: install-methods.xml:543 +#: install-methods.xml:603 #, no-c-format msgid "Select the <filename>root.bin</filename> file in the file-opening dialog." msgstr "" #. Tag: para -#: install-methods.xml:548 +#: install-methods.xml:608 #, 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:556 +#: install-methods.xml:616 #, 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:575 +#: install-methods.xml:635 #, no-c-format msgid "Preparing Files for USB Memory Stick Booting" msgstr "" #. Tag: para -#: install-methods.xml:577 +#: install-methods.xml:637 #, 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:587 +#: install-methods.xml:647 #, 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:595 +#: install-methods.xml:655 #, no-c-format msgid "Copying the files — the easy way" msgstr "" #. Tag: para -#: install-methods.xml:596 +#: install-methods.xml:656 #, 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:603 +#: install-methods.xml:663 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sda</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:605 +#: install-methods.xml:665 #, 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:614 +#: install-methods.xml:674 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sda2</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:617 +#: install-methods.xml:677 #, 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:623 +#: install-methods.xml:683 #, 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:639 +#: install-methods.xml:699 #, no-c-format msgid "Copying the files — the flexible way" msgstr "" #. Tag: para -#: install-methods.xml:640 +#: install-methods.xml:700 #, 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:652 install-methods.xml:741 +#: install-methods.xml:712 install-methods.xml:801 #, no-c-format msgid "USB stick partitioning on &arch-title;" msgstr "" #. Tag: para -#: install-methods.xml:653 +#: install-methods.xml:713 #, 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:658 +#: install-methods.xml:718 #, 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" @@ -489,13 +549,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:672 +#: install-methods.xml:732 #, 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:682 +#: install-methods.xml:742 #, 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" @@ -504,19 +564,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:695 +#: install-methods.xml:755 #, 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:726 +#: install-methods.xml:786 #, no-c-format msgid "The <filename>syslinux.cfg</filename> configuration file should contain the following two lines:" msgstr "" #. Tag: screen -#: install-methods.xml:731 +#: install-methods.xml:791 #, no-c-format msgid "" "default vmlinuz\n" @@ -524,7 +584,7 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:742 +#: install-methods.xml:802 #, 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" @@ -533,13 +593,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:758 +#: install-methods.xml:818 #, 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:767 +#: install-methods.xml:827 #, 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" @@ -552,43 +612,43 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:783 +#: install-methods.xml:843 #, 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:789 +#: install-methods.xml:849 #, no-c-format msgid "<filename>vmlinux</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:794 +#: install-methods.xml:854 #, no-c-format msgid "<filename>initrd.gz</filename> (initial ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:799 +#: install-methods.xml:859 #, no-c-format msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" msgstr "" #. Tag: para -#: install-methods.xml:804 +#: install-methods.xml:864 #, no-c-format msgid "<filename>boot.msg</filename> (optional boot message)" msgstr "" #. Tag: para -#: install-methods.xml:809 +#: install-methods.xml:869 #, no-c-format msgid "Optional kernel modules" msgstr "" #. Tag: para -#: install-methods.xml:816 +#: install-methods.xml:876 #, no-c-format msgid "" "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n" @@ -606,283 +666,283 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:833 +#: install-methods.xml:893 #, no-c-format msgid "Adding an ISO image" msgstr "" #. Tag: para -#: install-methods.xml:834 +#: install-methods.xml:894 #, 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:842 +#: install-methods.xml:902 #, 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:851 +#: install-methods.xml:911 #, 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:861 +#: install-methods.xml:921 #, no-c-format msgid "Booting the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:862 +#: install-methods.xml:922 #, 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:869 +#: install-methods.xml:929 #, no-c-format msgid "# install-mbr /dev/<replaceable>sda</replaceable>" msgstr "" #. Tag: title -#: install-methods.xml:880 +#: install-methods.xml:940 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "" #. Tag: para -#: install-methods.xml:881 +#: install-methods.xml:941 #, 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:887 +#: install-methods.xml:947 #, 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:894 +#: install-methods.xml:954 #, no-c-format msgid "The installer cannot boot from files on an NTFS file system." msgstr "" #. Tag: para -#: install-methods.xml:898 +#: install-methods.xml:958 #, 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:909 +#: install-methods.xml:969 #, 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:918 +#: install-methods.xml:978 #, no-c-format msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: install-methods.xml:920 +#: install-methods.xml:980 #, 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:926 +#: install-methods.xml:986 #, 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:932 +#: install-methods.xml:992 #, 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:939 +#: install-methods.xml:999 #, no-c-format msgid "<filename>vmlinuz</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:944 +#: install-methods.xml:1004 #, no-c-format msgid "<filename>initrd.gz</filename> (ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:951 +#: install-methods.xml:1011 #, no-c-format msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>." msgstr "" #. Tag: title -#: install-methods.xml:961 +#: install-methods.xml:1021 #, no-c-format msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:962 +#: install-methods.xml:1022 #, 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:975 +#: install-methods.xml:1035 #, 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:995 +#: install-methods.xml:1055 #, no-c-format msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:996 +#: install-methods.xml:1056 #, 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:1007 +#: install-methods.xml:1067 #, 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:1017 install-methods.xml:1374 +#: install-methods.xml:1077 install-methods.xml:1434 #, no-c-format msgid "vmlinux" msgstr "" #. Tag: filename -#: install-methods.xml:1022 install-methods.xml:1379 +#: install-methods.xml:1082 install-methods.xml:1439 #, no-c-format msgid "initrd.gz" msgstr "" #. Tag: filename -#: install-methods.xml:1027 install-methods.xml:1384 +#: install-methods.xml:1087 install-methods.xml:1444 #, no-c-format msgid "yaboot" msgstr "" #. Tag: filename -#: install-methods.xml:1032 install-methods.xml:1389 +#: install-methods.xml:1092 install-methods.xml:1449 #, no-c-format msgid "yaboot.conf" msgstr "" #. Tag: para -#: install-methods.xml:1037 +#: install-methods.xml:1097 #, 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:1045 +#: install-methods.xml:1105 #, no-c-format msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1058 +#: install-methods.xml:1118 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "" #. Tag: para -#: install-methods.xml:1059 +#: install-methods.xml:1119 #, 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:1067 +#: install-methods.xml:1127 #, 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:1074 +#: install-methods.xml:1134 #, 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:1091 +#: install-methods.xml:1151 #, 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:1097 +#: install-methods.xml:1157 #, 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:1114 +#: install-methods.xml:1174 #, 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:1119 +#: install-methods.xml:1179 #, 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:1127 +#: install-methods.xml:1187 #, 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:1145 +#: install-methods.xml:1205 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para -#: install-methods.xml:1146 +#: install-methods.xml:1206 #, 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:1158 +#: install-methods.xml:1218 #, 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:1180 +#: install-methods.xml:1240 #, no-c-format msgid "Setting up a BOOTP server" msgstr "" #. Tag: para -#: install-methods.xml:1181 +#: install-methods.xml:1241 #, 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:1189 +#: install-methods.xml:1249 #, 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" @@ -899,25 +959,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1222 +#: install-methods.xml:1282 #, 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:1243 +#: install-methods.xml:1303 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1244 +#: install-methods.xml:1304 #, 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:1251 +#: install-methods.xml:1311 #, no-c-format msgid "" "option domain-name \"example.com\";\n" @@ -942,25 +1002,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1253 +#: install-methods.xml:1313 #, 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:1263 +#: install-methods.xml:1323 #, 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:1271 +#: install-methods.xml:1331 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1272 +#: install-methods.xml:1332 #, 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" @@ -995,13 +1055,13 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1288 +#: install-methods.xml:1348 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1289 +#: install-methods.xml:1349 #, 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" @@ -1010,19 +1070,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1301 +#: install-methods.xml:1361 #, 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:1311 +#: install-methods.xml:1371 #, no-c-format msgid "Look in <filename>/etc/inetd.conf</filename> and remember the directory which is used as the argument of <command>in.tftpd</command><footnote> <para> All <command>in.tftpd</command> alternatives available in Debian should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors. </para> </footnote>; you'll need that below. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>." msgstr "" #. Tag: para -#: install-methods.xml:1331 +#: install-methods.xml:1391 #, 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" @@ -1033,61 +1093,61 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1353 +#: install-methods.xml:1413 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1354 +#: install-methods.xml:1414 #, 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:1363 +#: install-methods.xml:1423 #, no-c-format msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the <filename>netboot/</filename> directory:" msgstr "" #. Tag: filename -#: install-methods.xml:1394 +#: install-methods.xml:1454 #, no-c-format msgid "boot.msg" msgstr "" #. Tag: para -#: install-methods.xml:1399 +#: install-methods.xml:1459 #, 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:1407 +#: install-methods.xml:1467 #, 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:1419 +#: install-methods.xml:1479 #, no-c-format msgid "Alpha TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1420 +#: install-methods.xml:1480 #, 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:1435 +#: install-methods.xml:1495 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1436 +#: install-methods.xml:1496 #, 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" @@ -1096,85 +1156,85 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1452 +#: install-methods.xml:1512 #, 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:1459 +#: install-methods.xml:1519 #, 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:1470 +#: install-methods.xml:1530 #, no-c-format msgid "BVM/Motorola TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1471 +#: install-methods.xml:1531 #, 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:1476 +#: install-methods.xml:1536 #, 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:1488 +#: install-methods.xml:1548 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1489 +#: install-methods.xml:1549 #, 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:1501 +#: install-methods.xml:1561 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1502 +#: install-methods.xml:1562 #, 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:1607 +#: install-methods.xml:1667 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1608 +#: install-methods.xml:1668 #, 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:1621 +#: install-methods.xml:1681 #, no-c-format msgid "Automatic Installation Using the Debian Installer" msgstr "" #. Tag: para -#: install-methods.xml:1622 +#: install-methods.xml:1682 #, 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:1629 +#: install-methods.xml:1689 #, no-c-format msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>." msgstr "" |