diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-new.pot | 120 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 982 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 559 |
3 files changed, 1015 insertions, 646 deletions
diff --git a/po/pot/boot-new.pot b/po/pot/boot-new.pot index 58380400f..5f6cc204d 100644 --- a/po/pot/boot-new.pot +++ b/po/pot/boot-new.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2006-02-07 15:07+0000\n" +"POT-Creation-Date: 2006-07-09 14:07+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" @@ -167,46 +167,150 @@ msgstr "" #: boot-new.xml:191 #, no-c-format #. Tag: title -msgid "Log In" +msgid "Mounting encrypted volumes" msgstr "" #: boot-new.xml:193 #, no-c-format #. Tag: para +msgid "If you created encrypted volumes during the installation and assigned them mount points, you will be asked to enter the passphrase for each of these volumes during the boot. The actual procedure differs slightly between dm-crypt and loop-AES." +msgstr "" + +#: boot-new.xml:203 +#, no-c-format +#. Tag: title +msgid "loop-AES" +msgstr "" + +#: boot-new.xml:205 +#, no-c-format +#. Tag: para +msgid "" + "For partitions encrypted via loop-AES you will be shown the following prompt during the boot: <informalexample><screen>\n" + "mount: going to use loop device /dev/loop<replaceable>X</replaceable>\n" + "Password:\n" + "</screen></informalexample> In the first line of the prompt, <replaceable>X</replaceable> is the number of the loop device. You are now probably wondering <emphasis>for which volume</emphasis> you are actually entering the passphrase. Does is relate to your <filename>/home</filename>? Or to <filename>/var</filename>? Of course, if you have just one encrypted volume, this is easy and you can just enter the passphrase you used when setting up this volume. If you set up more than one encrypted volume during the installation, the notes you wrote down as the last step in <xref linkend=\"partman-crypto\"/> come in handy. If you did not make a note of the mapping between <filename>loop<replaceable>X</replaceable></filename> and the mount points before, you can still find it in <filename>/etc/fstab</filename> of your new system." +msgstr "" + +#: boot-new.xml:226 +#, no-c-format +#. Tag: para +msgid "No characters (even asterisks) will be shown while entering the passphrase. Be careful, you have only <emphasis>one try</emphasis>. If you enter wrong passphrase, an error message will appear and the boot process will skip that volume and continue to mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting\"/> for further information." +msgstr "" + +#: boot-new.xml:235 +#, no-c-format +#. Tag: para +msgid "After entering all passphrases the boot should continue as usual." +msgstr "" + +#: boot-new.xml:243 +#, no-c-format +#. Tag: title +msgid "dm-crypt" +msgstr "" + +#: boot-new.xml:245 +#, no-c-format +#. Tag: para +msgid "TODO: write something once it works." +msgstr "" + +#: boot-new.xml:253 +#, no-c-format +#. Tag: title +msgid "Troubleshooting" +msgstr "" + +#: boot-new.xml:255 +#, no-c-format +#. Tag: para +msgid "If some of the encrypted volumes could not be mounted because a wrong passphrase was entered, you will have to mount them manually after the boot. There are several cases." +msgstr "" + +#: boot-new.xml:264 +#, no-c-format +#. Tag: para +msgid "The first case concerns the root partition. When it is not mounted correctly, the boot process will halt and you will have to reboot the computer to try again." +msgstr "" + +#: boot-new.xml:271 +#, no-c-format +#. Tag: para +msgid "" + "The easiest case is for encrypted volumes holding data like <filename>/home</filename> or <filename>/srv</filename>. You can simply mount them manually after the boot. For loop-AES this is one-step operation: <informalexample><screen>\n" + "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>\n" + "<prompt>Password:</prompt>\n" + "</screen></informalexample> where <replaceable>/mount_point</replaceable> should be replaced by the particular directory (e.g. <filename>/home</filename>). The only difference from an ordinary mount is that you will be asked to enter the passphrase for this volume." +msgstr "" + +#: boot-new.xml:285 +#, no-c-format +#. Tag: para +msgid "" + "For dm-crypt this is a bit trickier. First you need to register the volumes with <application>device mapper</application> by running: <informalexample><screen>\n" + "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n" + "</screen></informalexample> This will scan all volumes mentioned in <filename>/etc/crypttab</filename> and will create appropriate devices under the <filename>/dev</filename> directory after entering the correct passphrases. (Already registered volumes will be skipped, so you can repeat this command several times without worrying.) After successful registration you can simply mount the volumes the usual way:" +msgstr "" + +#: boot-new.xml:300 +#, no-c-format +#. Tag: screen +msgid "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>" +msgstr "" + +#: boot-new.xml:303 +#, no-c-format +#. Tag: para +msgid "" + "If the volumes holding noncritical system files could not be mounted (<filename>/usr</filename> or <filename>/var</filename>), the system should still boot and you should be able to mount the volumes manually like in the previous case. However, you will also need to (re)start any services usually running in your default runlevel because it is very likely that they were not started. The easiest way to achieve this is by switching to the first runlevel and back by entering <informalexample><screen>\n" + "<prompt>#</prompt> <userinput>init 1</userinput>\n" + "</screen></informalexample> at the shell prompt and pressing <keycombo> <keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the root password." +msgstr "" + +#: boot-new.xml:326 +#, no-c-format +#. Tag: title +msgid "Log In" +msgstr "" + +#: boot-new.xml:328 +#, no-c-format +#. Tag: para msgid "Once your system boots, you'll be presented with the login prompt. Log in using the personal login and password you selected during the installation process. Your system is now ready to use." msgstr "" -#: boot-new.xml:199 +#: boot-new.xml:334 #, no-c-format #. Tag: para msgid "If you are a new user, you may want to explore the documentation which is already installed on your system as you start to use it. There are currently several documentation systems, work is proceeding on integrating the different types of documentation. Here are a few starting points." msgstr "" -#: boot-new.xml:207 +#: boot-new.xml:342 #, no-c-format #. Tag: para msgid "Documentation accompanying programs you have installed is in <filename>/usr/share/doc/</filename>, under a subdirectory named after the program. For example, the APT User's Guide for using <command>apt</command> to install other programs on your system, is located in <filename>/usr/share/doc/apt/guide.html/index.html</filename>." msgstr "" -#: boot-new.xml:216 +#: boot-new.xml:351 #, no-c-format #. Tag: para msgid "In addition, there are some special folders within the <filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</emphasis> format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. After installing <command>dhelp</command> you will find a browse-able index of documentation in <filename>/usr/share/doc/HTML/index.html</filename>." msgstr "" -#: boot-new.xml:226 +#: boot-new.xml:361 #, no-c-format #. Tag: para msgid "One easy way to view these documents is to <userinput>cd /usr/share/doc/</userinput>, and type <userinput>lynx</userinput> followed by a space and a dot (the dot stands for the current directory)." msgstr "" -#: boot-new.xml:233 +#: boot-new.xml:368 #, no-c-format #. Tag: para msgid "You can also type <userinput>info <replaceable>command</replaceable></userinput> or <userinput>man <replaceable>command</replaceable></userinput> to see documentation on most commands available at the command prompt. Typing <userinput>help</userinput> will display help on shell commands. And typing a command followed by <userinput>--help</userinput> will usually display a short summary of the command's usage. If a command's results scroll past the top of the screen, type <userinput>| more</userinput> after the command to cause the results to pause before scrolling past the top of the screen. To see a list of all commands available which begin with a certain letter, type the letter and then two tabs." msgstr "" -#: boot-new.xml:248 +#: boot-new.xml:383 #, no-c-format #. Tag: para msgid "For a more complete introduction to Debian and GNU/Linux, see <filename>/usr/share/doc/debian-guide/html/noframes/index.html</filename>." diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index 28d10ea30..3f850a090 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2006-05-04 19:49+0000\n" +"POT-Creation-Date: 2006-07-09 14:07+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" @@ -263,7 +263,7 @@ msgstr "" #: hardware.xml:118 #, no-c-format #. Tag: entry -msgid "riscpc" +msgid "<entry>rpc</entry>" msgstr "" #: hardware.xml:122 @@ -311,7 +311,7 @@ msgstr "" #: hardware.xml:131 #, no-c-format #. Tag: entry -msgid "prep" +msgid "<entry>prep</entry>" msgstr "" #: hardware.xml:133 @@ -401,1528 +401,1522 @@ msgstr "" #: hardware.xml:160 #, no-c-format #. Tag: entry -msgid "r5k-ip22" -msgstr "" - -#: hardware.xml:162 -#, no-c-format -#. Tag: entry msgid "SGI IP32 (O2)" msgstr "" -#: hardware.xml:163 +#: hardware.xml:161 #, no-c-format #. Tag: entry msgid "r5k-ip32" msgstr "" -#: hardware.xml:165 hardware.xml:183 +#: hardware.xml:163 hardware.xml:181 #, no-c-format #. Tag: entry msgid "Broadcom BCM91250A (SWARM)" msgstr "" -#: hardware.xml:166 hardware.xml:184 +#: hardware.xml:164 hardware.xml:182 #, no-c-format #. Tag: entry msgid "sb1-bcm91250a" msgstr "" -#: hardware.xml:168 hardware.xml:186 +#: hardware.xml:166 hardware.xml:184 #, no-c-format #. Tag: entry msgid "Broadcom BCM91480B (BigSur)" msgstr "" -#: hardware.xml:169 hardware.xml:187 +#: hardware.xml:167 hardware.xml:185 #, no-c-format #. Tag: entry msgid "sb1a-bcm91480b" msgstr "" -#: hardware.xml:173 +#: hardware.xml:171 #, no-c-format #. Tag: entry msgid "MIPS (little endian)" msgstr "" -#: hardware.xml:174 +#: hardware.xml:172 #, no-c-format #. Tag: entry msgid "mipsel" msgstr "" -#: hardware.xml:175 +#: hardware.xml:173 #, no-c-format #. Tag: entry msgid "Cobalt" msgstr "" -#: hardware.xml:176 +#: hardware.xml:174 #, no-c-format #. Tag: entry msgid "cobalt" msgstr "" -#: hardware.xml:178 +#: hardware.xml:176 #, no-c-format #. Tag: entry msgid "DECstation" msgstr "" -#: hardware.xml:179 hardware.xml:1010 hardware.xml:1025 hardware.xml:1035 +#: hardware.xml:177 hardware.xml:1008 hardware.xml:1023 hardware.xml:1033 #, no-c-format #. Tag: entry msgid "r4k-kn04" msgstr "" -#: hardware.xml:181 hardware.xml:1005 hardware.xml:1015 hardware.xml:1020 hardware.xml:1030 +#: hardware.xml:179 hardware.xml:1003 hardware.xml:1013 hardware.xml:1018 hardware.xml:1028 #, no-c-format #. Tag: entry msgid "r3k-kn02" msgstr "" -#: hardware.xml:191 +#: hardware.xml:189 #, no-c-format #. Tag: entry msgid "IBM S/390" msgstr "" -#: hardware.xml:192 +#: hardware.xml:190 #, no-c-format #. Tag: entry msgid "s390" msgstr "" -#: hardware.xml:193 +#: hardware.xml:191 #, no-c-format #. Tag: entry msgid "IPL from VM-reader and DASD" msgstr "" -#: hardware.xml:194 +#: hardware.xml:192 #, no-c-format #. Tag: entry msgid "generic" msgstr "" -#: hardware.xml:196 +#: hardware.xml:194 #, no-c-format #. Tag: entry msgid "IPL from tape" msgstr "" -#: hardware.xml:197 +#: hardware.xml:195 #, no-c-format #. Tag: entry msgid "tape" msgstr "" -#: hardware.xml:202 +#: hardware.xml:200 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:210 +#: hardware.xml:208 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:233 hardware.xml:692 hardware.xml:768 hardware.xml:787 hardware.xml:830 hardware.xml:872 hardware.xml:940 hardware.xml:1099 hardware.xml:1505 +#: hardware.xml:231 hardware.xml:690 hardware.xml:766 hardware.xml:785 hardware.xml:828 hardware.xml:870 hardware.xml:938 hardware.xml:1097 hardware.xml:1543 #, no-c-format #. Tag: title msgid "CPU, Main Boards, and Video Support" msgstr "" -#: hardware.xml:234 +#: hardware.xml:232 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:241 +#: hardware.xml:239 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:249 +#: hardware.xml:247 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:266 +#: hardware.xml:264 #, no-c-format #. Tag: entry msgid "Hardware Type" msgstr "" -#: hardware.xml:267 +#: hardware.xml:265 #, no-c-format #. Tag: entry msgid "Aliases" msgstr "" -#: hardware.xml:267 +#: hardware.xml:265 #, no-c-format #. Tag: entry msgid "MILO image" msgstr "" -#: hardware.xml:273 +#: hardware.xml:271 #, no-c-format #. Tag: entry msgid "ALCOR" msgstr "" -#: hardware.xml:274 +#: hardware.xml:272 #, no-c-format #. Tag: entry msgid "AlphaStation 500 5/266.300" msgstr "" -#: hardware.xml:275 +#: hardware.xml:273 #, no-c-format #. Tag: entry msgid "Maverick" msgstr "" -#: hardware.xml:276 hardware.xml:280 hardware.xml:284 +#: hardware.xml:274 hardware.xml:278 hardware.xml:282 #, no-c-format #. Tag: entry msgid "alcor" msgstr "" -#: hardware.xml:278 +#: hardware.xml:276 #, no-c-format #. Tag: entry msgid "AlphaStation 500 5/333...500" msgstr "" -#: hardware.xml:279 +#: hardware.xml:277 #, no-c-format #. Tag: entry msgid "Bret" msgstr "" -#: hardware.xml:282 +#: hardware.xml:280 #, no-c-format #. Tag: entry msgid "AlphaStation 600/266...300" msgstr "" -#: hardware.xml:283 +#: hardware.xml:281 #, no-c-format #. Tag: entry msgid "Alcor" msgstr "" -#: hardware.xml:286 +#: hardware.xml:284 #, no-c-format #. Tag: entry msgid "AlphaStation 600/300...433" msgstr "" -#: hardware.xml:287 +#: hardware.xml:285 #, no-c-format #. Tag: entry msgid "<entry>XLT</entry>" msgstr "" -#: hardware.xml:288 +#: hardware.xml:286 #, no-c-format #. Tag: entry msgid "<entry>xlt</entry>" msgstr "" -#: hardware.xml:292 +#: hardware.xml:290 #, no-c-format #. Tag: entry msgid "BOOK1" msgstr "" -#: hardware.xml:293 +#: hardware.xml:291 #, no-c-format #. Tag: entry msgid "AlphaBook1 (laptop)" msgstr "" -#: hardware.xml:294 +#: hardware.xml:292 #, no-c-format #. Tag: entry msgid "Alphabook1/Burns" msgstr "" -#: hardware.xml:295 +#: hardware.xml:293 #, no-c-format #. Tag: entry msgid "book1" msgstr "" -#: hardware.xml:299 +#: hardware.xml:297 #, no-c-format #. Tag: entry msgid "AVANTI" msgstr "" -#: hardware.xml:300 +#: hardware.xml:298 #, no-c-format #. Tag: entry msgid "AlphaStation 200 4/100...166" msgstr "" -#: hardware.xml:301 +#: hardware.xml:299 #, no-c-format #. Tag: entry msgid "Mustang" msgstr "" -#: hardware.xml:302 hardware.xml:306 hardware.xml:310 hardware.xml:314 hardware.xml:318 hardware.xml:322 hardware.xml:326 hardware.xml:330 +#: hardware.xml:300 hardware.xml:304 hardware.xml:308 hardware.xml:312 hardware.xml:316 hardware.xml:320 hardware.xml:324 hardware.xml:328 #, no-c-format #. Tag: entry msgid "avanti" msgstr "" -#: hardware.xml:304 +#: hardware.xml:302 #, no-c-format #. Tag: entry msgid "AlphaStation 200 4/233" msgstr "" -#: hardware.xml:305 +#: hardware.xml:303 #, no-c-format #. Tag: entry msgid "Mustang+" msgstr "" -#: hardware.xml:308 +#: hardware.xml:306 #, no-c-format #. Tag: entry msgid "AlphaStation 205 4/133...333" msgstr "" -#: hardware.xml:309 +#: hardware.xml:307 #, no-c-format #. Tag: entry msgid "<entry>LX3</entry>" msgstr "" -#: hardware.xml:312 +#: hardware.xml:310 #, no-c-format #. Tag: entry msgid "AlphaStation 250 4/300" msgstr "" -#: hardware.xml:313 +#: hardware.xml:311 #, no-c-format #. Tag: entry msgid "<entry>M3+</entry>" msgstr "" -#: hardware.xml:316 +#: hardware.xml:314 #, no-c-format #. Tag: entry msgid "AlphaStation 255 4/133...333" msgstr "" -#: hardware.xml:317 +#: hardware.xml:315 #, no-c-format #. Tag: entry msgid "LX3+" msgstr "" -#: hardware.xml:320 +#: hardware.xml:318 #, no-c-format #. Tag: entry msgid "AlphaStation 300 4/266" msgstr "" -#: hardware.xml:321 +#: hardware.xml:319 #, no-c-format #. Tag: entry msgid "Melmac" msgstr "" -#: hardware.xml:324 +#: hardware.xml:322 #, no-c-format #. Tag: entry msgid "AlphaStation 400 4/166" msgstr "" -#: hardware.xml:325 +#: hardware.xml:323 #, no-c-format #. Tag: entry msgid "Chinet" msgstr "" -#: hardware.xml:328 +#: hardware.xml:326 #, no-c-format #. Tag: entry msgid "AlphaStation 400 4/233...300" msgstr "" -#: hardware.xml:329 +#: hardware.xml:327 #, no-c-format #. Tag: entry msgid "Avanti" msgstr "" -#: hardware.xml:334 hardware.xml:347 hardware.xml:348 +#: hardware.xml:332 hardware.xml:345 hardware.xml:346 #, no-c-format #. Tag: entry msgid "EB164" msgstr "" -#: hardware.xml:335 +#: hardware.xml:333 #, no-c-format #. Tag: entry msgid "AlphaPC164" msgstr "" -#: hardware.xml:336 +#: hardware.xml:334 #, no-c-format #. Tag: entry msgid "PC164" msgstr "" -#: hardware.xml:337 +#: hardware.xml:335 #, no-c-format #. Tag: entry msgid "pc164" msgstr "" -#: hardware.xml:339 +#: hardware.xml:337 #, no-c-format #. Tag: entry msgid "AlphaPC164-LX" msgstr "" -#: hardware.xml:340 +#: hardware.xml:338 #, no-c-format #. Tag: entry msgid "LX164" msgstr "" -#: hardware.xml:341 +#: hardware.xml:339 #, no-c-format #. Tag: entry msgid "lx164" msgstr "" -#: hardware.xml:343 +#: hardware.xml:341 #, no-c-format #. Tag: entry msgid "AlphaPC164-SX" msgstr "" -#: hardware.xml:344 +#: hardware.xml:342 #, no-c-format #. Tag: entry msgid "SX164" msgstr "" -#: hardware.xml:345 +#: hardware.xml:343 #, no-c-format #. Tag: entry msgid "sx164" msgstr "" -#: hardware.xml:349 +#: hardware.xml:347 #, no-c-format #. Tag: entry msgid "eb164" msgstr "" -#: hardware.xml:353 hardware.xml:362 hardware.xml:363 +#: hardware.xml:351 hardware.xml:360 hardware.xml:361 #, no-c-format #. Tag: entry msgid "EB64+" msgstr "" -#: hardware.xml:354 +#: hardware.xml:352 #, no-c-format #. Tag: entry msgid "AlphaPC64" msgstr "" -#: hardware.xml:355 hardware.xml:359 +#: hardware.xml:353 hardware.xml:357 #, no-c-format #. Tag: entry msgid "Cabriolet" msgstr "" -#: hardware.xml:356 hardware.xml:360 +#: hardware.xml:354 hardware.xml:358 #, no-c-format #. Tag: entry msgid "cabriolet" msgstr "" -#: hardware.xml:358 +#: hardware.xml:356 #, no-c-format #. Tag: entry msgid "AlphaPCI64" msgstr "" -#: hardware.xml:364 +#: hardware.xml:362 #, no-c-format #. Tag: entry msgid "eb64p" msgstr "" -#: hardware.xml:368 hardware.xml:369 hardware.xml:370 +#: hardware.xml:366 hardware.xml:367 hardware.xml:368 #, no-c-format #. Tag: entry msgid "EB66" msgstr "" -#: hardware.xml:371 +#: hardware.xml:369 #, no-c-format #. Tag: entry msgid "eb66" msgstr "" -#: hardware.xml:373 hardware.xml:374 +#: hardware.xml:371 hardware.xml:372 #, no-c-format #. Tag: entry msgid "EB66+" msgstr "" -#: hardware.xml:375 +#: hardware.xml:373 #, no-c-format #. Tag: entry msgid "eb66p" msgstr "" -#: hardware.xml:379 +#: hardware.xml:377 #, no-c-format #. Tag: entry msgid "JENSEN" msgstr "" -#: hardware.xml:380 +#: hardware.xml:378 #, no-c-format #. Tag: entry msgid "DEC 2000 Model 300(S)" msgstr "" -#: hardware.xml:381 hardware.xml:389 +#: hardware.xml:379 hardware.xml:387 #, no-c-format #. Tag: entry msgid "Jensen" msgstr "" -#: hardware.xml:382 hardware.xml:386 hardware.xml:390 hardware.xml:451 hardware.xml:455 hardware.xml:473 hardware.xml:477 hardware.xml:481 hardware.xml:485 hardware.xml:489 hardware.xml:493 hardware.xml:497 hardware.xml:511 hardware.xml:515 hardware.xml:519 hardware.xml:523 hardware.xml:527 hardware.xml:561 hardware.xml:565 hardware.xml:569 hardware.xml:573 hardware.xml:587 hardware.xml:591 hardware.xml:595 hardware.xml:599 hardware.xml:606 hardware.xml:610 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:661 hardware.xml:665 +#: hardware.xml:380 hardware.xml:384 hardware.xml:388 hardware.xml:449 hardware.xml:453 hardware.xml:471 hardware.xml:475 hardware.xml:479 hardware.xml:483 hardware.xml:487 hardware.xml:491 hardware.xml:495 hardware.xml:509 hardware.xml:513 hardware.xml:517 hardware.xml:521 hardware.xml:525 hardware.xml:559 hardware.xml:563 hardware.xml:567 hardware.xml:571 hardware.xml:585 hardware.xml:589 hardware.xml:593 hardware.xml:597 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:648 hardware.xml:652 hardware.xml:659 hardware.xml:663 #, no-c-format #. Tag: entry msgid "<entry>N/A</entry>" msgstr "" -#: hardware.xml:384 +#: hardware.xml:382 #, no-c-format #. Tag: entry msgid "DEC 2000 Model 500" msgstr "" -#: hardware.xml:385 +#: hardware.xml:383 #, no-c-format #. Tag: entry msgid "Culzen" msgstr "" -#: hardware.xml:388 +#: hardware.xml:386 #, no-c-format #. Tag: entry msgid "DECpc 150" msgstr "" -#: hardware.xml:394 +#: hardware.xml:392 #, no-c-format #. Tag: entry msgid "MIATA" msgstr "" -#: hardware.xml:395 +#: hardware.xml:393 #, no-c-format #. Tag: entry msgid "Personal WorkStation 433a" msgstr "" -#: hardware.xml:396 hardware.xml:400 hardware.xml:404 hardware.xml:408 hardware.xml:412 hardware.xml:416 hardware.xml:420 hardware.xml:424 +#: hardware.xml:394 hardware.xml:398 hardware.xml:402 hardware.xml:406 hardware.xml:410 hardware.xml:414 hardware.xml:418 hardware.xml:422 #, no-c-format #. Tag: entry msgid "Miata" msgstr "" -#: hardware.xml:397 hardware.xml:401 hardware.xml:405 hardware.xml:409 hardware.xml:413 hardware.xml:417 hardware.xml:421 hardware.xml:425 +#: hardware.xml:395 hardware.xml:399 hardware.xml:403 hardware.xml:407 hardware.xml:411 hardware.xml:415 hardware.xml:419 hardware.xml:423 #, no-c-format #. Tag: entry msgid "miata" msgstr "" -#: hardware.xml:399 +#: hardware.xml:397 #, no-c-format #. Tag: entry msgid "Personal WorkStation 433au" msgstr "" -#: hardware.xml:403 +#: hardware.xml:401 #, no-c-format #. Tag: entry msgid "Personal WorkStation 466au" msgstr "" -#: hardware.xml:407 +#: hardware.xml:405 #, no-c-format #. Tag: entry msgid "Personal WorkStation 500a" msgstr "" -#: hardware.xml:411 +#: hardware.xml:409 #, no-c-format #. Tag: entry msgid "Personal WorkStation 500au" msgstr "" -#: hardware.xml:415 +#: hardware.xml:413 #, no-c-format #. Tag: entry msgid "Personal WorkStation 550au" msgstr "" -#: hardware.xml:419 +#: hardware.xml:417 #, no-c-format #. Tag: entry msgid "Personal WorkStation 600a" msgstr "" -#: hardware.xml:423 +#: hardware.xml:421 #, no-c-format #. Tag: entry msgid "Personal WorkStation 600au" msgstr "" -#: hardware.xml:429 +#: hardware.xml:427 #, no-c-format #. Tag: entry msgid "MIKASA" msgstr "" -#: hardware.xml:430 +#: hardware.xml:428 #, no-c-format #. Tag: entry msgid "AlphaServer 1000 4/200" msgstr "" -#: hardware.xml:431 +#: hardware.xml:429 #, no-c-format #. Tag: entry msgid "Mikasa" msgstr "" -#: hardware.xml:432 hardware.xml:436 hardware.xml:440 hardware.xml:444 +#: hardware.xml:430 hardware.xml:434 hardware.xml:438 hardware.xml:442 #, no-c-format #. Tag: entry msgid "mikasa" msgstr "" -#: hardware.xml:434 +#: hardware.xml:432 #, no-c-format #. Tag: entry msgid "AlphaServer 1000 4/233..266" msgstr "" -#: hardware.xml:435 +#: hardware.xml:433 #, no-c-format #. Tag: entry msgid "Mikasa+" msgstr "" -#: hardware.xml:438 hardware.xml:442 +#: hardware.xml:436 hardware.xml:440 #, no-c-format #. Tag: entry msgid "AlphaServer 1000 5/300" msgstr "" -#: hardware.xml:439 +#: hardware.xml:437 #, no-c-format #. Tag: entry msgid "Mikasa-Pinnacle" msgstr "" -#: hardware.xml:443 +#: hardware.xml:441 #, no-c-format #. Tag: entry msgid "Mikasa-Primo" msgstr "" -#: hardware.xml:448 +#: hardware.xml:446 #, no-c-format #. Tag: entry msgid "NAUTILUS" msgstr "" -#: hardware.xml:449 +#: hardware.xml:447 #, no-c-format #. Tag: entry msgid "UP1000" msgstr "" -#: hardware.xml:450 +#: hardware.xml:448 #, no-c-format #. Tag: entry msgid "Nautilus" msgstr "" -#: hardware.xml:453 +#: hardware.xml:451 #, no-c-format #. Tag: entry msgid "UP1100" msgstr "" -#: hardware.xml:454 +#: hardware.xml:452 #, no-c-format #. Tag: entry msgid "Galaxy-Train/Nautilus Jr." msgstr "" -#: hardware.xml:459 +#: hardware.xml:457 #, no-c-format #. Tag: entry msgid "NONAME" msgstr "" -#: hardware.xml:460 +#: hardware.xml:458 #, no-c-format #. Tag: entry msgid "AXPpci33" msgstr "" -#: hardware.xml:461 +#: hardware.xml:459 #, no-c-format #. Tag: entry msgid "Noname" msgstr "" -#: hardware.xml:462 hardware.xml:466 +#: hardware.xml:460 hardware.xml:464 #, no-c-format #. Tag: entry msgid "noname" msgstr "" -#: hardware.xml:464 +#: hardware.xml:462 #, no-c-format #. Tag: entry msgid "<entry>UDB</entry>" msgstr "" -#: hardware.xml:465 +#: hardware.xml:463 #, no-c-format #. Tag: entry msgid "Multia" msgstr "" -#: hardware.xml:470 +#: hardware.xml:468 #, no-c-format #. Tag: entry msgid "NORITAKE" msgstr "" -#: hardware.xml:471 +#: hardware.xml:469 #, no-c-format #. Tag: entry msgid "AlphaServer 1000A 4/233...266" msgstr "" -#: hardware.xml:472 +#: hardware.xml:470 #, no-c-format #. Tag: entry msgid "Noritake" msgstr "" -#: hardware.xml:475 +#: hardware.xml:473 #, no-c-format #. Tag: entry msgid "AlphaServer 1000A 5/300" msgstr "" -#: hardware.xml:476 +#: hardware.xml:474 #, no-c-format #. Tag: entry msgid "Noritake-Pinnacle" msgstr "" -#: hardware.xml:479 +#: hardware.xml:477 #, no-c-format #. Tag: entry msgid "AlphaServer 1000A 5/333...500" msgstr "" -#: hardware.xml:480 +#: hardware.xml:478 #, no-c-format #. Tag: entry msgid "Noritake-Primo" msgstr "" -#: hardware.xml:483 +#: hardware.xml:481 #, no-c-format #. Tag: entry msgid "AlphaServer 800 5/333...500" msgstr "" -#: hardware.xml:484 hardware.xml:492 hardware.xml:496 +#: hardware.xml:482 hardware.xml:490 hardware.xml:494 #, no-c-format #. Tag: entry msgid "Corelle" msgstr "" -#: hardware.xml:487 +#: hardware.xml:485 #, no-c-format #. Tag: entry msgid "AlphaStation 600 A" msgstr "" -#: hardware.xml:488 +#: hardware.xml:486 #, no-c-format #. Tag: entry msgid "Alcor-Primo" msgstr "" -#: hardware.xml:491 +#: hardware.xml:489 #, no-c-format #. Tag: entry msgid "Digital Server 3300" msgstr "" -#: hardware.xml:495 +#: hardware.xml:493 #, no-c-format #. Tag: entry msgid "Digital Server 3300R" msgstr "" -#: hardware.xml:501 +#: hardware.xml:499 #, no-c-format #. Tag: entry msgid "PLATFORM 2000" msgstr "" -#: hardware.xml:502 hardware.xml:503 +#: hardware.xml:500 hardware.xml:501 #, no-c-format #. Tag: entry msgid "<entry>P2K</entry>" msgstr "" -#: hardware.xml:504 +#: hardware.xml:502 #, no-c-format #. Tag: entry msgid "<entry>p2k</entry>" msgstr "" -#: hardware.xml:508 +#: hardware.xml:506 #, no-c-format #. Tag: entry msgid "RAWHIDE" msgstr "" -#: hardware.xml:509 +#: hardware.xml:507 #, no-c-format #. Tag: entry msgid "AlphaServer 1200 5/xxx" msgstr "" -#: hardware.xml:510 hardware.xml:522 +#: hardware.xml:508 hardware.xml:520 #, no-c-format #. Tag: entry msgid "Tincup/DaVinci" msgstr "" -#: hardware.xml:513 +#: hardware.xml:511 #, no-c-format #. Tag: entry msgid "AlphaServer 4000 5/xxx" msgstr "" -#: hardware.xml:514 +#: hardware.xml:512 #, no-c-format #. Tag: entry msgid "Wrangler/Durango" msgstr "" -#: hardware.xml:517 +#: hardware.xml:515 #, no-c-format #. Tag: entry msgid "AlphaServer 4100 5/xxx" msgstr "" -#: hardware.xml:518 hardware.xml:526 +#: hardware.xml:516 hardware.xml:524 #, no-c-format #. Tag: entry msgid "Dodge" msgstr "" -#: hardware.xml:521 +#: hardware.xml:519 #, no-c-format #. Tag: entry msgid "Digital Server 5300" msgstr "" -#: hardware.xml:525 +#: hardware.xml:523 #, no-c-format #. Tag: entry msgid "Digital Server 7300" msgstr "" -#: hardware.xml:531 +#: hardware.xml:529 #, no-c-format #. Tag: entry msgid "RUFFIAN" msgstr "" -#: hardware.xml:532 +#: hardware.xml:530 #, no-c-format #. Tag: entry msgid "DeskStation AlphaPC164-UX" msgstr "" -#: hardware.xml:533 hardware.xml:537 hardware.xml:541 hardware.xml:545 hardware.xml:549 hardware.xml:553 +#: hardware.xml:531 hardware.xml:535 hardware.xml:539 hardware.xml:543 hardware.xml:547 hardware.xml:551 #, no-c-format #. Tag: entry msgid "Ruffian" msgstr "" -#: hardware.xml:534 hardware.xml:538 hardware.xml:542 hardware.xml:546 hardware.xml:550 hardware.xml:554 +#: hardware.xml:532 hardware.xml:536 hardware.xml:540 hardware.xml:544 hardware.xml:548 hardware.xml:552 #, no-c-format #. Tag: entry msgid "ruffian" msgstr "" -#: hardware.xml:536 +#: hardware.xml:534 #, no-c-format #. Tag: entry msgid "DeskStation RPL164-2" msgstr "" -#: hardware.xml:540 +#: hardware.xml:538 #, no-c-format #. Tag: entry msgid "DeskStation RPL164-4" msgstr "" -#: hardware.xml:544 +#: hardware.xml:542 #, no-c-format #. Tag: entry msgid "DeskStation RPX164-2" msgstr "" -#: hardware.xml:548 +#: hardware.xml:546 #, no-c-format #. Tag: entry msgid "DeskStation RPX164-4" msgstr "" -#: hardware.xml:552 +#: hardware.xml:550 #, no-c-format #. Tag: entry msgid "Samsung AlphaPC164-BX" msgstr "" -#: hardware.xml:558 +#: hardware.xml:556 #, no-c-format #. Tag: entry msgid "SABLE" msgstr "" -#: hardware.xml:559 +#: hardware.xml:557 #, no-c-format #. Tag: entry msgid "AlphaServer 2000 4/xxx" msgstr "" -#: hardware.xml:560 +#: hardware.xml:558 #, no-c-format #. Tag: entry msgid "Demi-Sable" msgstr "" -#: hardware.xml:563 +#: hardware.xml:561 #, no-c-format #. Tag: entry msgid "AlphaServer 2000 5/xxx" msgstr "" -#: hardware.xml:564 +#: hardware.xml:562 #, no-c-format #. Tag: entry msgid "Demi-Gamma-Sable" msgstr "" -#: hardware.xml:567 +#: hardware.xml:565 #, no-c-format #. Tag: entry msgid "AlphaServer 2100 4/xxx" msgstr "" -#: hardware.xml:568 +#: hardware.xml:566 #, no-c-format #. Tag: entry msgid "Sable" msgstr "" -#: hardware.xml:571 +#: hardware.xml:569 #, no-c-format #. Tag: entry msgid "AlphaServer 2100 5/xxx" msgstr "" -#: hardware.xml:572 +#: hardware.xml:570 #, no-c-format #. Tag: entry msgid "Gamma-Sable" msgstr "" -#: hardware.xml:577 +#: hardware.xml:575 #, no-c-format #. Tag: entry msgid "TAKARA" msgstr "" -#: hardware.xml:578 +#: hardware.xml:576 #, no-c-format #. Tag: entry msgid "21164 PICMG SBC" msgstr "" -#: hardware.xml:579 +#: hardware.xml:577 #, no-c-format #. Tag: entry msgid "Takara" msgstr "" -#: hardware.xml:580 +#: hardware.xml:578 #, no-c-format #. Tag: entry msgid "takara" msgstr "" -#: hardware.xml:584 +#: hardware.xml:582 #, no-c-format #. Tag: entry msgid "TITAN" msgstr "" -#: hardware.xml:585 +#: hardware.xml:583 #, no-c-format #. Tag: entry msgid "AlphaServer DS15" msgstr "" -#: hardware.xml:586 +#: hardware.xml:584 #, no-c-format #. Tag: entry msgid "HyperBrick2" msgstr "" -#: hardware.xml:589 +#: hardware.xml:587 #, no-c-format #. Tag: entry msgid "AlphaServer DS25" msgstr "" -#: hardware.xml:590 +#: hardware.xml:588 #, no-c-format #. Tag: entry msgid "Granite" msgstr "" -#: hardware.xml:593 +#: hardware.xml:591 #, no-c-format #. Tag: entry msgid "AlphaServer ES45" msgstr "" -#: hardware.xml:594 +#: hardware.xml:592 #, no-c-format #. Tag: entry msgid "Privateer" msgstr "" -#: hardware.xml:597 hardware.xml:636 hardware.xml:640 +#: hardware.xml:595 hardware.xml:634 hardware.xml:638 #, no-c-format #. Tag: entry msgid "UNKNOWN" msgstr "" -#: hardware.xml:598 +#: hardware.xml:596 #, no-c-format #. Tag: entry msgid "Yukon" msgstr "" -#: hardware.xml:603 +#: hardware.xml:601 #, no-c-format #. Tag: entry msgid "TSUNAMI" msgstr "" -#: hardware.xml:604 +#: hardware.xml:602 #, no-c-format #. Tag: entry msgid "AlphaServer DS10" msgstr "" -#: hardware.xml:605 hardware.xml:653 +#: hardware.xml:603 hardware.xml:651 #, no-c-format #. Tag: entry msgid "Webbrick" msgstr "" -#: hardware.xml:608 +#: hardware.xml:606 #, no-c-format #. Tag: entry msgid "AlphaServer DS10L" msgstr "" -#: hardware.xml:609 +#: hardware.xml:607 #, no-c-format #. Tag: entry msgid "Slate" msgstr "" -#: hardware.xml:612 +#: hardware.xml:610 #, no-c-format #. Tag: entry msgid "AlphaServer DS20" msgstr "" -#: hardware.xml:613 +#: hardware.xml:611 #, no-c-format #. Tag: entry msgid "Catamaran/Goldrush" msgstr "" -#: hardware.xml:616 +#: hardware.xml:614 #, no-c-format #. Tag: entry msgid "AlphaServer DS20E" msgstr "" -#: hardware.xml:617 +#: hardware.xml:615 #, no-c-format #. Tag: entry msgid "Goldrack" msgstr "" -#: hardware.xml:620 +#: hardware.xml:618 #, no-c-format #. Tag: entry msgid "AlphaServer DS20L" msgstr "" -#: hardware.xml:621 +#: hardware.xml:619 #, no-c-format #. Tag: entry msgid "Shark" msgstr "" -#: hardware.xml:624 +#: hardware.xml:622 #, no-c-format #. Tag: entry msgid "AlphaServer ES40" msgstr "" -#: hardware.xml:625 +#: hardware.xml:623 #, no-c-format #. Tag: entry msgid "Clipper" msgstr "" -#: hardware.xml:628 hardware.xml:629 +#: hardware.xml:626 hardware.xml:627 #, no-c-format #. Tag: entry msgid "DP264" msgstr "" -#: hardware.xml:632 +#: hardware.xml:630 #, no-c-format #. Tag: entry msgid "SMARTengine 21264 PCI/ISA SBC" msgstr "" -#: hardware.xml:633 +#: hardware.xml:631 #, no-c-format #. Tag: entry msgid "Eiger" msgstr "" -#: hardware.xml:637 +#: hardware.xml:635 #, no-c-format #. Tag: entry msgid "Warhol" msgstr "" -#: hardware.xml:641 +#: hardware.xml:639 #, no-c-format #. Tag: entry msgid "Windjammer" msgstr "" -#: hardware.xml:644 +#: hardware.xml:642 #, no-c-format #. Tag: entry msgid "UP2000" msgstr "" -#: hardware.xml:645 +#: hardware.xml:643 #, no-c-format #. Tag: entry msgid "Swordfish" msgstr "" -#: hardware.xml:648 +#: hardware.xml:646 #, no-c-format #. Tag: entry msgid "XP1000" msgstr "" -#: hardware.xml:649 +#: hardware.xml:647 #, no-c-format #. Tag: entry msgid "Monet/Brisbane" msgstr "" -#: hardware.xml:652 +#: hardware.xml:650 #, no-c-format #. Tag: entry msgid "XP900" msgstr "" -#: hardware.xml:658 +#: hardware.xml:656 #, no-c-format #. Tag: entry msgid "WILDFIRE" msgstr "" -#: hardware.xml:659 +#: hardware.xml:657 #, no-c-format #. Tag: entry msgid "AlphaServer GS160" msgstr "" -#: hardware.xml:660 hardware.xml:664 +#: hardware.xml:658 hardware.xml:662 #, no-c-format #. Tag: entry msgid "Wildfire" msgstr "" -#: hardware.xml:663 +#: hardware.xml:661 #, no-c-format #. Tag: entry msgid "AlphaServer GS320" msgstr "" -#: hardware.xml:669 hardware.xml:671 +#: hardware.xml:667 hardware.xml:669 #, no-c-format #. Tag: entry msgid "<entry>XL</entry>" msgstr "" -#: hardware.xml:670 +#: hardware.xml:668 #, no-c-format #. Tag: entry msgid "XL-233...266" msgstr "" -#: hardware.xml:672 +#: hardware.xml:670 #, no-c-format #. Tag: entry msgid "<entry>xl</entry>" msgstr "" -#: hardware.xml:677 +#: hardware.xml:675 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:694 +#: hardware.xml:692 #, no-c-format #. Tag: para 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 systems. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU including xscale." msgstr "" -#: hardware.xml:702 +#: hardware.xml:700 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:710 +#: hardware.xml:708 #, no-c-format #. Tag: para msgid "The supported systems are:" msgstr "" -#: hardware.xml:717 +#: hardware.xml:715 #, no-c-format #. Tag: term msgid "Netwinder" msgstr "" -#: hardware.xml:718 +#: hardware.xml:716 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:731 +#: hardware.xml:729 #, no-c-format #. Tag: term msgid "NSLU2" msgstr "" -#: hardware.xml:732 +#: hardware.xml:730 #, no-c-format #. Tag: para msgid "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." msgstr "" -#: hardware.xml:743 +#: hardware.xml:741 #, no-c-format #. Tag: term msgid "<term>RiscPC</term>" msgstr "" -#: hardware.xml:744 +#: hardware.xml:742 #, no-c-format #. Tag: para msgid "This machine is the oldest supported hardware: it was released in 1994. It has RISC OS in ROM, Linux can be booted from that OS using linloader. The RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA video, parallel port, single serial port, PS/2 keyboard and proprietary mouse port. The proprietary module expansion bus allows for up to eight expansion cards to be fitted depending on configuration, several of these modules have Linux drivers." msgstr "" -#: hardware.xml:769 +#: hardware.xml:767 #, no-c-format #. Tag: para msgid "The 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 "" -#: hardware.xml:788 +#: hardware.xml:786 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:796 hardware.xml:913 +#: hardware.xml:794 hardware.xml:911 #, no-c-format #. Tag: title msgid "<title>CPU</title>" msgstr "" -#: hardware.xml:797 +#: hardware.xml:795 #, no-c-format #. Tag: para msgid "Nearly all x86-based processors are supported; this includes AMD and VIA (former Cyrix) processors as well. Also the new processors like Athlon XP and Intel P4 Xeon are supported. However, Linux will <emphasis>not</emphasis> run on 286 or earlier processors." msgstr "" -#: hardware.xml:807 +#: hardware.xml:805 #, no-c-format #. Tag: title msgid "I/O Bus" msgstr "" -#: hardware.xml:808 +#: hardware.xml:806 #, no-c-format #. Tag: para 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)." msgstr "" -#: hardware.xml:831 +#: hardware.xml:829 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:838 +#: hardware.xml:836 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:846 +#: hardware.xml:844 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:873 +#: hardware.xml:871 #, no-c-format #. Tag: para msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" -#: hardware.xml:914 +#: hardware.xml:912 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:924 +#: hardware.xml:922 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:941 +#: hardware.xml:939 #, no-c-format #. Tag: para msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" -#: hardware.xml:981 +#: hardware.xml:979 #, no-c-format #. Tag: title msgid "CPU/Machine types" msgstr "" -#: hardware.xml:983 +#: hardware.xml:981 #, no-c-format #. Tag: para msgid "Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by the Debian installation system on little endian MIPS. The Debian installation system works on the following machines:" msgstr "" -#: hardware.xml:995 +#: hardware.xml:993 #, no-c-format #. Tag: entry msgid "System Type" msgstr "" -#: hardware.xml:995 +#: hardware.xml:993 #, no-c-format #. Tag: entry msgid "<entry>CPU</entry>" msgstr "" -#: hardware.xml:995 +#: hardware.xml:993 #, no-c-format #. Tag: entry msgid "Code-name" msgstr "" -#: hardware.xml:996 +#: hardware.xml:994 #, no-c-format #. Tag: entry msgid "Debian subarchitecture" msgstr "" -#: hardware.xml:1002 +#: hardware.xml:1000 #, no-c-format #. Tag: entry msgid "DECstation 5000/1xx" msgstr "" -#: hardware.xml:1003 hardware.xml:1013 hardware.xml:1018 hardware.xml:1028 +#: hardware.xml:1001 hardware.xml:1011 hardware.xml:1016 hardware.xml:1026 #, no-c-format #. Tag: entry msgid "R3000" msgstr "" -#: hardware.xml:1004 hardware.xml:1009 +#: hardware.xml:1002 hardware.xml:1007 #, no-c-format #. Tag: entry msgid "3MIN" msgstr "" -#: hardware.xml:1007 +#: hardware.xml:1005 #, no-c-format #. Tag: entry msgid "DECstation 5000/150" msgstr "" -#: hardware.xml:1008 hardware.xml:1033 +#: hardware.xml:1006 hardware.xml:1031 #, no-c-format #. Tag: entry msgid "R4000" msgstr "" -#: hardware.xml:1012 +#: hardware.xml:1010 #, no-c-format #. Tag: entry msgid "DECstation 5000/200" msgstr "" -#: hardware.xml:1014 +#: hardware.xml:1012 #, no-c-format #. Tag: entry msgid "3MAX" msgstr "" -#: hardware.xml:1017 +#: hardware.xml:1015 #, no-c-format #. Tag: entry msgid "DECstation 5000/240" msgstr "" -#: hardware.xml:1019 hardware.xml:1024 +#: hardware.xml:1017 hardware.xml:1022 #, no-c-format #. Tag: entry msgid "3MAX+" msgstr "" -#: hardware.xml:1022 +#: hardware.xml:1020 #, no-c-format #. Tag: entry msgid "DECstation 5000/260" msgstr "" -#: hardware.xml:1023 +#: hardware.xml:1021 #, no-c-format #. Tag: entry msgid "R4400" msgstr "" -#: hardware.xml:1027 +#: hardware.xml:1025 #, no-c-format #. Tag: entry msgid "Personal DECstation 5000/xx" msgstr "" -#: hardware.xml:1029 hardware.xml:1034 +#: hardware.xml:1027 hardware.xml:1032 #, no-c-format #. Tag: entry msgid "Maxine" msgstr "" -#: hardware.xml:1032 +#: hardware.xml:1030 #, no-c-format #. Tag: entry msgid "Personal DECstation 5000/50" msgstr "" -#: hardware.xml:1039 +#: hardware.xml:1037 #, no-c-format #. Tag: para msgid "All Cobalt machines are supported. In the past, only machines with a serial console were supported (that is, all machines except for the Qube 2700, aka Qube1). However, installations are now also possible through SSH." msgstr "" -#: hardware.xml:1046 +#: hardware.xml:1044 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1056 +#: hardware.xml:1054 #, no-c-format #. Tag: title msgid "Supported console options" msgstr "" -#: hardware.xml:1057 +#: hardware.xml:1055 #, no-c-format #. Tag: para msgid "A serial console is available on all supported DECstations (9600 bps, 8N1). To use the serial console, you have to boot the installer image with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter (with <replaceable>x</replaceable> being the number of the serial port you have your terminal connected to — usually <literal>2</literal>, but <literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available with the PMAG-BA and the PMAGB-B graphics options." msgstr "" -#: hardware.xml:1068 +#: hardware.xml:1066 #, no-c-format #. Tag: para msgid "" @@ -1931,1219 +1925,1243 @@ msgid "" "</screen></informalexample> where the option <literal>-l</literal> (line) sets the serial port to use and <literal>-s</literal> (speed) sets the speed for the connection (9600 bits per second)." msgstr "" -#: hardware.xml:1086 +#: hardware.xml:1084 #, no-c-format #. Tag: para msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps." msgstr "" -#: hardware.xml:1100 +#: hardware.xml:1098 #, no-c-format #. Tag: para -msgid "There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh), 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." +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 "" -#: hardware.xml:1108 +#: hardware.xml:1106 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1116 +#: hardware.xml:1114 #, no-c-format #. Tag: title msgid "Kernel Flavours" msgstr "" -#: hardware.xml:1118 +#: hardware.xml:1116 #, no-c-format #. Tag: para msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" -#: hardware.xml:1125 +#: hardware.xml:1123 #, no-c-format #. Tag: term msgid "<term>powerpc</term>" msgstr "" -#: hardware.xml:1126 +#: hardware.xml:1124 #, no-c-format #. Tag: para -msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple Power Macintosh systems up to and including the G4 use one of these processors." +msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors." msgstr "" -#: hardware.xml:1136 +#: hardware.xml:1134 #, no-c-format #. Tag: term -msgid "power3" +msgid "power64" msgstr "" -#: hardware.xml:1137 +#: hardware.xml:1135 #, no-c-format #. Tag: para -msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270." +msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" -#: hardware.xml:1147 +#: hardware.xml:1139 #, no-c-format -#. Tag: term -msgid "power4" +#. Tag: para +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 "" -#: hardware.xml:1148 +#: hardware.xml:1145 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1153 +#: hardware.xml:1150 #, no-c-format #. Tag: para -msgid "The Apple G5 is also based on the POWER4 architecture, and uses this kernel flavour." +msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour." msgstr "" -#: hardware.xml:1162 +#: hardware.xml:1159 #, no-c-format #. Tag: term -msgid "<term>apus</term>" +msgid "<term>prep</term>" msgstr "" -#: hardware.xml:1163 +#: hardware.xml:1160 #, no-c-format #. Tag: para -msgid "This kernel flavour supports the Amiga Power-UP System." +msgid "This kernel flavour supports the PReP subarchitecture." msgstr "" -#: hardware.xml:1175 +#: hardware.xml:1168 #, no-c-format -#. Tag: title -msgid "Power Macintosh (pmac) subarchitecture" +#. Tag: term +msgid "<term>apus</term>" msgstr "" -#: hardware.xml:1177 +#: hardware.xml:1169 #, no-c-format #. Tag: para -msgid "Apple (and briefly a few other manufacturers — Power Computing, for example) makes a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus, OldWorld PCI, and NewWorld." +msgid "This kernel flavour supports the Amiga Power-UP System, though it is currently disabled." msgstr "" -#: hardware.xml:1184 +#: hardware.xml:1182 #, no-c-format -#. Tag: para -msgid "Macintosh computers using the 680x0 series of processors are not in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> or have a 3-digit model number such as Centris 650 or Quadra 950. Apple's pre-iMac PowerPC model numbers have four digits." +#. Tag: title +msgid "Power Macintosh (pmac) subarchitecture" msgstr "" -#: hardware.xml:1191 +#: hardware.xml:1184 #, no-c-format #. Tag: para -msgid "NuBus systems are not currently supported by debian/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which Debian does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>" +msgid "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 "" -#: hardware.xml:1224 +#: hardware.xml:1191 #, no-c-format #. Tag: para -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. The beige colored G3 systems are also OldWorld." +msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld." msgstr "" -#: hardware.xml:1230 +#: hardware.xml:1199 #, no-c-format #. Tag: para -msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards." +msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards." msgstr "" -#: hardware.xml:1238 +#: hardware.xml:1207 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1254 hardware.xml:1389 hardware.xml:1433 hardware.xml:1462 +#: hardware.xml:1223 hardware.xml:1358 hardware.xml:1402 hardware.xml:1431 #, no-c-format #. Tag: entry msgid "Model Name/Number" msgstr "" -#: hardware.xml:1255 +#: hardware.xml:1224 #, no-c-format #. Tag: entry msgid "Generation" msgstr "" -#: hardware.xml:1261 +#: hardware.xml:1230 #, no-c-format #. Tag: entry msgid "Apple" msgstr "" -#: hardware.xml:1262 +#: hardware.xml:1231 #, no-c-format #. Tag: entry msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" -#: 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:1296 hardware.xml:1299 hardware.xml:1302 hardware.xml:1305 hardware.xml:1308 +#: hardware.xml:1232 hardware.xml:1235 hardware.xml:1238 hardware.xml:1241 hardware.xml:1244 hardware.xml:1247 hardware.xml:1250 hardware.xml:1253 hardware.xml:1256 hardware.xml:1259 hardware.xml:1262 hardware.xml:1265 hardware.xml:1268 hardware.xml:1271 hardware.xml:1274 hardware.xml:1277 #, no-c-format #. Tag: entry msgid "NewWorld" msgstr "" -#: hardware.xml:1265 +#: hardware.xml:1234 #, no-c-format #. Tag: entry msgid "iMac Summer 2000, Early 2001" msgstr "" -#: hardware.xml:1268 +#: hardware.xml:1237 #, no-c-format #. Tag: entry msgid "iMac G5" msgstr "" -#: hardware.xml:1271 +#: hardware.xml:1240 #, no-c-format #. Tag: entry msgid "iBook, iBook SE, iBook Dual USB" msgstr "" -#: hardware.xml:1274 +#: hardware.xml:1243 #, no-c-format #. Tag: entry msgid "iBook2" msgstr "" -#: hardware.xml:1277 +#: hardware.xml:1246 #, no-c-format #. Tag: entry msgid "iBook G4" msgstr "" -#: hardware.xml:1280 +#: hardware.xml:1249 #, no-c-format #. Tag: entry msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" -#: hardware.xml:1283 +#: hardware.xml:1252 #, no-c-format #. Tag: entry msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" -#: hardware.xml:1286 +#: hardware.xml:1255 #, no-c-format #. Tag: entry msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" -#: hardware.xml:1289 +#: hardware.xml:1258 #, no-c-format #. Tag: entry msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" -#: hardware.xml:1292 +#: hardware.xml:1261 #, no-c-format #. Tag: entry msgid "Power Macintosh G5" msgstr "" -#: hardware.xml:1295 +#: hardware.xml:1264 #, no-c-format #. Tag: entry msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" -#: hardware.xml:1298 +#: hardware.xml:1267 #, no-c-format #. Tag: entry msgid "PowerBook G3 Lombard (1999)" msgstr "" -#: hardware.xml:1301 +#: hardware.xml:1270 #, no-c-format #. Tag: entry msgid "PowerBook G4 Titanium" msgstr "" -#: hardware.xml:1304 +#: hardware.xml:1273 #, no-c-format #. Tag: entry msgid "PowerBook G4 Aluminum" msgstr "" -#: hardware.xml:1307 +#: hardware.xml:1276 #, no-c-format #. Tag: entry msgid "Xserve G5" msgstr "" -#: hardware.xml:1310 +#: hardware.xml:1279 #, no-c-format #. Tag: entry msgid "Performa 4400, 54xx, 5500" msgstr "" -#: hardware.xml:1311 hardware.xml:1314 hardware.xml:1317 hardware.xml:1320 hardware.xml:1323 hardware.xml:1326 hardware.xml:1329 hardware.xml:1332 hardware.xml:1335 hardware.xml:1338 hardware.xml:1341 hardware.xml:1344 hardware.xml:1350 hardware.xml:1353 hardware.xml:1359 hardware.xml:1365 hardware.xml:1371 +#: hardware.xml:1280 hardware.xml:1283 hardware.xml:1286 hardware.xml:1289 hardware.xml:1292 hardware.xml:1295 hardware.xml:1298 hardware.xml:1301 hardware.xml:1304 hardware.xml:1307 hardware.xml:1310 hardware.xml:1313 hardware.xml:1319 hardware.xml:1322 hardware.xml:1328 hardware.xml:1334 hardware.xml:1340 #, no-c-format #. Tag: entry msgid "OldWorld" msgstr "" -#: hardware.xml:1313 +#: hardware.xml:1282 #, no-c-format #. Tag: entry msgid "Performa 6360, 6400, 6500" msgstr "" -#: hardware.xml:1316 +#: hardware.xml:1285 #, no-c-format #. Tag: entry msgid "Power Macintosh 4400, 5400" msgstr "" -#: hardware.xml:1319 +#: hardware.xml:1288 #, no-c-format #. Tag: entry msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" -#: hardware.xml:1322 +#: hardware.xml:1291 #, no-c-format #. Tag: entry msgid "Power Macintosh 8200, 8500, 8600" msgstr "" -#: hardware.xml:1325 +#: hardware.xml:1294 #, no-c-format #. Tag: entry msgid "Power Macintosh 9500, 9600" msgstr "" -#: hardware.xml:1328 +#: hardware.xml:1297 #, no-c-format #. Tag: entry msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" -#: hardware.xml:1331 +#: hardware.xml:1300 #, no-c-format #. Tag: entry msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" -#: hardware.xml:1334 +#: hardware.xml:1303 #, no-c-format #. Tag: entry msgid "PowerBook 2400, 3400, 3500" msgstr "" -#: hardware.xml:1337 +#: hardware.xml:1306 #, no-c-format #. Tag: entry msgid "PowerBook G3 Wallstreet (1998)" msgstr "" -#: hardware.xml:1340 +#: hardware.xml:1309 #, no-c-format #. Tag: entry msgid "Twentieth Anniversary Macintosh" msgstr "" -#: hardware.xml:1343 +#: hardware.xml:1312 #, no-c-format #. Tag: entry msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" -#: hardware.xml:1348 +#: hardware.xml:1317 #, no-c-format #. Tag: entry msgid "Power Computing" msgstr "" -#: hardware.xml:1349 +#: hardware.xml:1318 #, no-c-format #. Tag: entry msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" -#: hardware.xml:1352 +#: hardware.xml:1321 #, no-c-format #. Tag: entry msgid "PowerCenter / Pro, PowerCurve" msgstr "" -#: hardware.xml:1357 +#: hardware.xml:1326 #, no-c-format #. Tag: entry msgid "UMAX" msgstr "" -#: hardware.xml:1358 +#: hardware.xml:1327 #, no-c-format #. Tag: entry msgid "C500, C600, J700, S900" msgstr "" -#: hardware.xml:1363 +#: hardware.xml:1332 #, no-c-format #. Tag: entry msgid "<entry>APS</entry>" msgstr "" -#: hardware.xml:1364 +#: hardware.xml:1333 #, no-c-format #. Tag: entry msgid "APS Tech M*Power 604e/2000" msgstr "" -#: hardware.xml:1369 hardware.xml:1395 +#: hardware.xml:1338 hardware.xml:1364 #, no-c-format #. Tag: entry msgid "Motorola" msgstr "" -#: hardware.xml:1370 +#: hardware.xml:1339 #, no-c-format #. Tag: entry msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" -#: hardware.xml:1379 +#: hardware.xml:1348 #, no-c-format #. Tag: title msgid "PReP subarchitecture" msgstr "" -#: hardware.xml:1396 +#: hardware.xml:1365 #, no-c-format #. Tag: entry msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" -#: hardware.xml:1398 +#: hardware.xml:1367 #, no-c-format #. Tag: entry msgid "MPC 7xx, 8xx" msgstr "" -#: hardware.xml:1400 +#: hardware.xml:1369 #, no-c-format #. Tag: entry msgid "MTX, MTX+" msgstr "" -#: hardware.xml:1402 +#: hardware.xml:1371 #, no-c-format #. Tag: entry msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" -#: hardware.xml:1404 +#: hardware.xml:1373 #, no-c-format #. Tag: entry msgid "MCP(N)750" msgstr "" -#: hardware.xml:1408 hardware.xml:1439 +#: hardware.xml:1377 hardware.xml:1408 #, no-c-format #. Tag: entry msgid "IBM RS/6000" msgstr "" -#: hardware.xml:1409 +#: hardware.xml:1378 #, no-c-format #. Tag: entry msgid "40P, 43P" msgstr "" -#: hardware.xml:1411 +#: hardware.xml:1380 #, no-c-format #. Tag: entry msgid "Power 830/850/860 (6070, 6050)" msgstr "" -#: hardware.xml:1413 +#: hardware.xml:1382 #, no-c-format #. Tag: entry msgid "6030, 7025, 7043" msgstr "" -#: hardware.xml:1415 +#: hardware.xml:1384 #, no-c-format #. Tag: entry msgid "p640" msgstr "" -#: hardware.xml:1423 +#: hardware.xml:1392 #, no-c-format #. Tag: title msgid "CHRP subarchitecture" msgstr "" -#: hardware.xml:1440 +#: hardware.xml:1409 #, no-c-format #. Tag: entry msgid "B50, 43P-150, 44P" msgstr "" -#: hardware.xml:1443 +#: hardware.xml:1412 #, no-c-format #. Tag: entry msgid "Genesi" msgstr "" -#: hardware.xml:1444 +#: hardware.xml:1413 #, no-c-format #. Tag: entry msgid "Pegasos I, Pegasos II" msgstr "" -#: hardware.xml:1452 +#: hardware.xml:1421 #, no-c-format #. Tag: title msgid "APUS subarchitecture" msgstr "" -#: hardware.xml:1468 +#: hardware.xml:1437 #, no-c-format #. Tag: entry msgid "Amiga Power-UP Systems (APUS)" msgstr "" -#: hardware.xml:1469 +#: hardware.xml:1438 #, no-c-format #. Tag: entry msgid "A1200, A3000, A4000" msgstr "" -#: hardware.xml:1482 +#: hardware.xml:1446 +#, no-c-format +#. Tag: title +msgid "Nubus PowerMac subarchitecture (unsupported)" +msgstr "" + +#: hardware.xml:1448 +#, no-c-format +#. Tag: para +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 "" + +#: hardware.xml:1485 +#, no-c-format +#. Tag: title +msgid "Non-PowerPC Macs" +msgstr "" + +#: hardware.xml:1487 +#, no-c-format +#. Tag: para +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. <para></para> 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. <para></para> 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 "" + +#: hardware.xml:1520 #, no-c-format #. Tag: title msgid "S/390 and zSeries machine types" msgstr "" -#: hardware.xml:1483 +#: hardware.xml:1521 #, no-c-format #. Tag: para msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/documentation-2.4.shtml\">technical details web page</ulink> at <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/index.shtml\">developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance." msgstr "" -#: hardware.xml:1506 +#: hardware.xml:1544 #, no-c-format #. Tag: para msgid "Currently the <emphasis>&architecture;</emphasis> port supports several types of Sparc systems. The most common identifiers for Sparc systems are sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not support very old sun4 hardware. However, the other systems are supported. Sun4d has been tested the least of these, so expect possible problems with regard to the kernel stability. Sun4c and Sun4m, the most common of the older Sparc hardware, includes such systems as SparcStation 1, 1+, IPC, IPX and the SparcStation LX, 5, 10, and 20, respectively. The UltraSPARC class systems fall under the sun4u identifier, and are supported using the sun4u set of install images. Some systems that fall under these supported identifiers are known to not be supported. Known unsupported systems are the AP1000 multicomputer and the Tadpole Sparcbook 1. See the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARCProcessors FAQ</ulink> for complete information." msgstr "" -#: hardware.xml:1526 +#: hardware.xml:1564 #, no-c-format #. Tag: title msgid "Memory Configuration" msgstr "" -#: hardware.xml:1527 +#: hardware.xml:1565 #, no-c-format #. Tag: para msgid "Some older Sun workstations, notably the Sun IPX and Sun IPC have memory banks located at fixed locations in physical memory. Thus if the banks are not filled gaps will exist in the physical memory space. The Linux installation requires a contiguous memory block into which to load the kernel and the initial RAMdisk. If this is not available a <quote>Data Access Exception</quote> will result." msgstr "" -#: hardware.xml:1536 +#: hardware.xml:1574 #, no-c-format #. Tag: para msgid "Thus you must configure the memory so that the lowest memory block is contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks are mapped in at 16Mb boundaries. In effect this means that you must have a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. In this case 4Mb is <emphasis>not</emphasis> sufficient." msgstr "" -#: hardware.xml:1544 +#: hardware.xml:1582 #, no-c-format #. Tag: para msgid "Example: In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS connectors]. You must therefore install the 16Mb SIMM in bank 0; it is then recommended to install the 4Mb SIMM in bank 2." msgstr "" -#: hardware.xml:1555 +#: hardware.xml:1593 #, no-c-format #. Tag: title msgid "Graphics Configuration" msgstr "" -#: hardware.xml:1556 +#: hardware.xml:1594 #, no-c-format #. Tag: para msgid "Especially in the case of older Sun workstations, it is very common for there to be an onboard framebuffer which has been superseded (for example the bwtwo on a sun IPC), and an SBUS card containing a later probably accelerated buffer is then plugged in to an SBUS slot. Under Solaris/SunOS this causes no problems because both cards are initialized." msgstr "" -#: hardware.xml:1565 +#: hardware.xml:1603 #, no-c-format #. Tag: para msgid "However with Linux this can cause a problem, in that the boot PROM monitor may display its output on this additional card; however the linux kernel boot messages may then be directed to the original on board framebuffer, leaving <emphasis>no</emphasis> error messages on the screen, with the machine apparently stuck loading the RAMdisk." msgstr "" -#: hardware.xml:1573 +#: hardware.xml:1611 #, no-c-format #. Tag: para msgid "To avoid this problem, connect the monitor (if required) to the video card in the lowest numbered SBUS slot (on motherboard card counts as below external slots). Alternatively it is possible to use a serial console." msgstr "" -#: hardware.xml:1585 +#: hardware.xml:1623 #, no-c-format #. Tag: title msgid "Graphics Card" msgstr "" -#: hardware.xml:1587 +#: hardware.xml:1625 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1595 +#: hardware.xml:1633 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1604 +#: hardware.xml:1642 #, no-c-format #. Tag: para msgid "The X.Org X11 window system is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" -#: hardware.xml:1613 +#: hardware.xml:1651 #, no-c-format #. Tag: para msgid "The X.Org X11 window system is supported on some DECstation models. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" -#: hardware.xml:1625 +#: hardware.xml:1663 #, no-c-format #. Tag: title msgid "Laptops" msgstr "" -#: hardware.xml:1626 +#: hardware.xml:1664 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1638 hardware.xml:1663 hardware.xml:1686 +#: hardware.xml:1676 hardware.xml:1701 hardware.xml:1724 #, no-c-format #. Tag: title msgid "Multiple Processors" msgstr "" -#: hardware.xml:1640 +#: hardware.xml:1678 #, no-c-format #. Tag: para msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with SMP support. This should not prevent installation, since the SMP kernel should boot on non-SMP systems; the kernel will simply cause a bit more overhead." msgstr "" -#: hardware.xml:1648 +#: hardware.xml:1686 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1664 +#: hardware.xml:1702 #, no-c-format #. Tag: para msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. However, the standard Debian &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" -#: hardware.xml:1673 +#: hardware.xml:1711 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1687 +#: hardware.xml:1725 #, no-c-format #. Tag: para msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture, and is supported by a precompiled Debian kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" -#: hardware.xml:1697 +#: hardware.xml:1735 #, no-c-format #. Tag: para msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package. You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" -#: hardware.xml:1718 +#: hardware.xml:1756 #, no-c-format #. Tag: title msgid "Installation Media" msgstr "" -#: hardware.xml:1720 +#: hardware.xml:1758 #, no-c-format #. Tag: para msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used to install Debian. There is a whole chapter devoted media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section." msgstr "" -#: hardware.xml:1731 +#: hardware.xml:1769 #, no-c-format #. Tag: title msgid "Floppies" msgstr "" -#: hardware.xml:1732 +#: hardware.xml:1770 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1738 +#: hardware.xml:1776 #, no-c-format #. Tag: para msgid "For CHRP, floppy support is currently broken." msgstr "" -#: hardware.xml:1745 +#: hardware.xml:1783 #, no-c-format #. Tag: title msgid "CD-ROM/DVD-ROM" msgstr "" -#: hardware.xml:1747 +#: hardware.xml:1785 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1754 +#: hardware.xml:1792 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1766 +#: hardware.xml:1804 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1776 +#: hardware.xml:1814 #, no-c-format #. Tag: para msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" -#: hardware.xml:1781 +#: hardware.xml:1819 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1790 +#: hardware.xml:1828 #, no-c-format #. Tag: para msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-ROMs are also supported." msgstr "" -#: hardware.xml:1795 +#: hardware.xml:1833 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1810 +#: hardware.xml:1848 #, no-c-format #. Tag: para msgid "On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position." msgstr "" -#: hardware.xml:1819 +#: hardware.xml:1857 #, no-c-format #. Tag: para msgid "CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal DECstation 5000/50)." msgstr "" -#: hardware.xml:1828 +#: hardware.xml:1866 #, no-c-format #. Tag: para msgid "To boot from CD, issue the command <userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware prompt, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot (3 on most DECstations) and <replaceable>id</replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" -#: hardware.xml:1840 +#: hardware.xml:1878 #, no-c-format #. Tag: userinput msgid "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=value1 param2=value2 ..." msgstr "" -#: hardware.xml:1847 +#: hardware.xml:1885 #, no-c-format #. Tag: title msgid "Hard Disk" msgstr "" -#: hardware.xml:1849 +#: hardware.xml:1887 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1855 +#: hardware.xml:1893 #, no-c-format #. Tag: para msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines." msgstr "" -#: hardware.xml:1860 +#: hardware.xml:1898 #, no-c-format #. Tag: para msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)." msgstr "" -#: hardware.xml:1868 +#: hardware.xml:1906 #, no-c-format #. Tag: title msgid "USB Memory Stick" msgstr "" -#: hardware.xml:1870 +#: hardware.xml:1908 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1882 +#: hardware.xml:1920 #, no-c-format #. Tag: title msgid "Network" msgstr "" -#: hardware.xml:1884 +#: hardware.xml:1922 #, no-c-format #. Tag: para msgid "You can also <emphasis>boot</emphasis> your system over the network. <phrase arch=\"mips\">This is the preferred installation technique for Mips.</phrase>" msgstr "" -#: hardware.xml:1890 +#: hardware.xml:1928 #, no-c-format #. Tag: para msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." msgstr "" -#: hardware.xml:1895 +#: hardware.xml:1933 #, no-c-format #. Tag: para msgid "After the operating system kernel is installed, you can install the rest of your system via any sort of network connection (including PPP after installation of the base system), via FTP or HTTP." msgstr "" -#: hardware.xml:1904 +#: hardware.xml:1942 #, no-c-format #. Tag: title msgid "Un*x or GNU system" msgstr "" -#: hardware.xml:1906 +#: hardware.xml:1944 #, no-c-format #. Tag: para msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of the manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." msgstr "" -#: hardware.xml:1918 +#: hardware.xml:1956 #, no-c-format #. Tag: title msgid "Supported Storage Systems" msgstr "" -#: hardware.xml:1920 +#: hardware.xml:1958 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1930 +#: hardware.xml:1968 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1937 +#: hardware.xml:1975 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1947 +#: hardware.xml:1985 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1957 +#: hardware.xml:1995 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1990 +#: hardware.xml:2028 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1999 +#: hardware.xml:2037 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2005 +#: hardware.xml:2043 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2011 +#: hardware.xml:2049 #, no-c-format #. Tag: para msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" -#: hardware.xml:2016 +#: hardware.xml:2054 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2033 +#: hardware.xml:2071 #, no-c-format #. Tag: title msgid "Peripherals and Other Hardware" msgstr "" -#: hardware.xml:2034 +#: hardware.xml:2072 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2040 +#: hardware.xml:2078 #, no-c-format #. Tag: para msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)." msgstr "" -#: hardware.xml:2046 +#: hardware.xml:2084 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2052 +#: hardware.xml:2090 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2058 +#: hardware.xml:2096 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2064 +#: hardware.xml:2102 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2074 +#: hardware.xml:2112 #, no-c-format #. Tag: title msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" -#: hardware.xml:2076 +#: hardware.xml:2114 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2084 +#: hardware.xml:2122 #, no-c-format #. Tag: para msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all." msgstr "" -#: hardware.xml:2089 +#: hardware.xml:2127 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2097 +#: hardware.xml:2135 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2108 +#: hardware.xml:2146 #, no-c-format #. Tag: title msgid "Avoid Proprietary or Closed Hardware" msgstr "" -#: hardware.xml:2109 +#: hardware.xml:2147 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2116 +#: hardware.xml:2154 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2127 +#: hardware.xml:2165 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2139 +#: hardware.xml:2177 #, no-c-format #. Tag: title msgid "Windows-specific Hardware" msgstr "" -#: hardware.xml:2140 +#: hardware.xml:2178 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2153 +#: hardware.xml:2191 #, no-c-format #. Tag: para msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes its being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" -#: hardware.xml:2174 +#: hardware.xml:2212 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2187 +#: hardware.xml:2225 #, no-c-format #. Tag: title msgid "Fake or <quote>Virtual</quote> Parity RAM" msgstr "" -#: hardware.xml:2188 +#: hardware.xml:2226 #, no-c-format #. Tag: para msgid "If you ask for Parity RAM in a computer store, you'll probably get <emphasis>virtual parity</emphasis> memory modules instead of <emphasis>true parity</emphasis> ones. Virtual parity SIMMs can often (but not always) be distinguished because they only have one more chip than an equivalent non-parity SIMM, and that one extra chip is smaller than all the others. Virtual-parity SIMMs work exactly like non-parity memory. They can't tell you when you have a single-bit RAM error the way true-parity SIMMs do in a motherboard that implements parity. Don't ever pay more for a virtual-parity SIMM than a non-parity one. Do expect to pay a little more for true-parity SIMMs, because you are actually buying one extra bit of memory for every 8 bits." msgstr "" -#: hardware.xml:2203 +#: hardware.xml:2241 #, no-c-format #. Tag: para msgid "If you want complete information on &arch-title; RAM issues, and what is the best RAM to buy, see the <ulink url=\"&url-pc-hw-faq;\">PC Hardware FAQ</ulink>." msgstr "" -#: hardware.xml:2209 +#: hardware.xml:2247 #, no-c-format #. Tag: para msgid "Most, if not all, Alpha systems require true-parity RAM." msgstr "" -#: hardware.xml:2224 +#: hardware.xml:2262 #, no-c-format #. Tag: title msgid "Memory and Disk Space Requirements" msgstr "" -#: hardware.xml:2226 +#: hardware.xml:2264 #, no-c-format #. Tag: para msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. For a minimal console-based system (all standard packages), 250MB is required. If you want to install a reasonable amount of software, including the X Window System, and some development programs and libraries, you'll need at least 400MB. For a more or less complete desktop system, you'll need a few gigabytes." msgstr "" -#: hardware.xml:2235 +#: hardware.xml:2273 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2244 +#: hardware.xml:2282 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2252 +#: hardware.xml:2290 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2262 +#: hardware.xml:2300 #, no-c-format #. Tag: emphasis msgid "FIXME: is this still true?" msgstr "" -#: hardware.xml:2273 +#: hardware.xml:2311 #, no-c-format #. Tag: title msgid "Network Connectivity Hardware" msgstr "" -#: hardware.xml:2275 +#: hardware.xml:2313 #, no-c-format #. Tag: para msgid "Most PCI and many older ISA network cards are supported. Some network interface cards are not supported by most Debian installation disks, such as AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider & Koch G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) network cards are not supported by the standard installation system, but see <ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) instructions. FDDI networks are also not supported by the installation disks, both cards and protocols." msgstr "" -#: hardware.xml:2294 +#: hardware.xml:2332 #, no-c-format #. Tag: para msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;." msgstr "" -#: hardware.xml:2302 +#: hardware.xml:2340 #, no-c-format #. Tag: para msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details." msgstr "" -#: hardware.xml:2311 +#: hardware.xml:2349 #, no-c-format #. Tag: para msgid "The following network interface cards (NICs) are supported from the bootable kernel directly:" msgstr "" -#: hardware.xml:2317 +#: hardware.xml:2355 #, no-c-format #. Tag: para msgid "Sun LANCE" msgstr "" -#: hardware.xml:2323 +#: hardware.xml:2361 #, no-c-format #. Tag: para msgid "Sun Happy Meal" msgstr "" -#: hardware.xml:2331 +#: hardware.xml:2369 #, no-c-format #. Tag: para msgid "The following network interface cards are supported as modules. They can be enabled once the drivers are installed during the setup. However, due to the magic of OpenPROM, you still should be able to boot from these devices:" msgstr "" -#: hardware.xml:2339 +#: hardware.xml:2377 #, no-c-format #. Tag: para msgid "Sun BigMAC" msgstr "" -#: hardware.xml:2345 +#: hardware.xml:2383 #, no-c-format #. Tag: para msgid "Sun QuadEthernet" msgstr "" -#: hardware.xml:2350 +#: hardware.xml:2388 #, no-c-format #. Tag: para msgid "MyriCOM Gigabit Ethernet" msgstr "" -#: hardware.xml:2357 hardware.xml:2363 hardware.xml:2369 hardware.xml:2375 hardware.xml:2381 +#: hardware.xml:2395 hardware.xml:2401 hardware.xml:2407 hardware.xml:2413 hardware.xml:2419 #, no-c-format #. Tag: para msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module." msgstr "" -#: hardware.xml:2387 +#: hardware.xml:2425 #, no-c-format #. Tag: para msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work." msgstr "" -#: hardware.xml:2393 +#: hardware.xml:2431 #, no-c-format #. Tag: para msgid "Any network interface card (NIC) supported by the Linux kernel is also be supported by the boot disks. All network drivers are compiled as modules so you need to load one first during the initial network setup. The list of supported network devices is:" msgstr "" -#: hardware.xml:2401 +#: hardware.xml:2439 #, no-c-format #. Tag: para msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" -#: hardware.xml:2406 +#: hardware.xml:2444 #, no-c-format #. Tag: para msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" -#: hardware.xml:2411 +#: hardware.xml:2449 #, no-c-format #. Tag: para msgid "Inter-User Communication Vehicle (IUCV) — available for VM guests only" msgstr "" -#: hardware.xml:2416 +#: hardware.xml:2454 #, no-c-format #. Tag: para msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" -#: hardware.xml:2425 +#: hardware.xml:2463 #, no-c-format #. Tag: para msgid "The following network interface cards are supported directly by the boot disks on Netwinder and CATS machines:" msgstr "" -#: hardware.xml:2431 +#: hardware.xml:2469 #, no-c-format #. Tag: para msgid "PCI-based NE2000" msgstr "" -#: hardware.xml:2437 +#: hardware.xml:2475 #, no-c-format #. Tag: para msgid "DECchip Tulip" msgstr "" -#: hardware.xml:2444 +#: hardware.xml:2482 #, no-c-format #. Tag: para msgid "The following network interface cards are supported directly by the boot disks on RiscPCs:" msgstr "" -#: hardware.xml:2450 +#: hardware.xml:2488 #, no-c-format #. Tag: para msgid "Ether1" msgstr "" -#: hardware.xml:2455 +#: hardware.xml:2493 #, no-c-format #. Tag: para msgid "Ether3" msgstr "" -#: hardware.xml:2460 +#: hardware.xml:2498 #, no-c-format #. Tag: para msgid "EtherH" msgstr "" -#: hardware.xml:2467 +#: hardware.xml:2505 #, no-c-format #. Tag: para msgid "If your card is mentioned in the lists above, the complete installation can be carried out from the network with no need for CD-ROMs or floppy disks." msgstr "" -#: hardware.xml:2473 +#: hardware.xml:2511 #, no-c-format #. Tag: para msgid "Any other network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module; this means that you will have to install the operating system kernel and modules using some other media." diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index 65a911ff1..1b1b0f9f6 100644 --- a/po/pot/using-d-i.pot +++ b/po/pot/using-d-i.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2006-06-24 19:23+0000\n" +"POT-Creation-Date: 2006-07-09 14:07+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" @@ -1012,598 +1012,845 @@ msgstr "" #: using-d-i.xml:1212 #, no-c-format #. Tag: para -msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected." +msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected." msgstr "" -#: using-d-i.xml:1223 +#: using-d-i.xml:1225 #, no-c-format #. Tag: para msgid "RAID0 is simple — you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD." msgstr "" -#: using-d-i.xml:1230 +#: using-d-i.xml:1232 #, no-c-format #. Tag: para msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided few seconds ago. Don't worry. If you make a mistake and select different number of partitions, the &d-i; won't let you continue until you correct the issue." msgstr "" -#: using-d-i.xml:1242 +#: using-d-i.xml:1244 #, no-c-format #. Tag: para msgid "RAID5 has similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions." msgstr "" -#: using-d-i.xml:1250 +#: using-d-i.xml:1252 #, no-c-format #. Tag: para msgid "It is perfectly possible to have several types of MD at once. For example if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine first partitions on all three disk into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)." msgstr "" -#: using-d-i.xml:1259 +#: using-d-i.xml:1261 #, no-c-format #. Tag: para msgid "After you setup MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints." msgstr "" -#: using-d-i.xml:1272 +#: using-d-i.xml:1276 +#, no-c-format +#. Tag: title +msgid "Configuring Encrypted Volumes" +msgstr "" + +#: using-d-i.xml:1277 +#, no-c-format +#. Tag: para +msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters." +msgstr "" + +#: using-d-i.xml:1289 +#, no-c-format +#. Tag: para +msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition." +msgstr "" + +#: using-d-i.xml:1304 +#, no-c-format +#. Tag: para +msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length." +msgstr "" + +#: using-d-i.xml:1311 +#, no-c-format +#. Tag: para +msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition setting</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition." +msgstr "" + +#: using-d-i.xml:1322 +#, no-c-format +#. Tag: para +msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default." +msgstr "" + +#: using-d-i.xml:1334 +#, no-c-format +#. Tag: para +msgid "First, let's have a look at available options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind." +msgstr "" + +#: using-d-i.xml:1344 +#, no-c-format +#. Tag: term +msgid "Encryption: <userinput>aes</userinput>" +msgstr "" + +#: using-d-i.xml:1346 +#, no-c-format +#. Tag: para +msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century." +msgstr "" + +#: using-d-i.xml:1364 +#, no-c-format +#. Tag: term +msgid "Key size: <userinput>256</userinput>" +msgstr "" + +#: using-d-i.xml:1366 +#, no-c-format +#. Tag: para +msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher." +msgstr "" + +#: using-d-i.xml:1378 +#, no-c-format +#. Tag: term +msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>" +msgstr "" + +#: using-d-i.xml:1380 +#, no-c-format +#. Tag: para +msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data." +msgstr "" + +#: using-d-i.xml:1390 +#, no-c-format +#. Tag: para +msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms." +msgstr "" + +#: using-d-i.xml:1402 +#, no-c-format +#. Tag: term +msgid "Encryption key: <userinput>Passphrase</userinput>" +msgstr "" + +#: using-d-i.xml:1404 +#, no-c-format +#. Tag: para +msgid "Here you can choose the type of the encryption key for this partition." +msgstr "" + +#: using-d-i.xml:1410 +#, no-c-format +#. Tag: term +msgid "Passphrase" +msgstr "" + +#: using-d-i.xml:1411 +#, no-c-format +#. Tag: para +msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process." +msgstr "" + +#: using-d-i.xml:1426 using-d-i.xml:1519 +#, no-c-format +#. Tag: term +msgid "Random key" +msgstr "" + +#: using-d-i.xml:1427 +#, no-c-format +#. Tag: para +msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)" +msgstr "" + +#: using-d-i.xml:1436 +#, no-c-format +#. Tag: para +msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition." +msgstr "" + +#: using-d-i.xml:1455 using-d-i.xml:1532 +#, no-c-format +#. Tag: term +msgid "Erase data: <userinput>yes</userinput>" +msgstr "" + +#: using-d-i.xml:1457 +#, no-c-format +#. Tag: para +msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>." +msgstr "" + +#: using-d-i.xml:1477 +#, no-c-format +#. Tag: para +msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:" +msgstr "" + +#: using-d-i.xml:1486 +#, no-c-format +#. Tag: term +msgid "Encryption: <userinput>AES256</userinput>" +msgstr "" + +#: using-d-i.xml:1488 +#, no-c-format +#. Tag: para +msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information." +msgstr "" + +#: using-d-i.xml:1498 +#, no-c-format +#. Tag: term +msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>" +msgstr "" + +#: using-d-i.xml:1500 +#, no-c-format +#. Tag: para +msgid "Here you can select the type of the encryption key for this partition." +msgstr "" + +#: using-d-i.xml:1506 +#, no-c-format +#. Tag: term +msgid "Keyfile (GnuPG)" +msgstr "" + +#: using-d-i.xml:1507 +#, no-c-format +#. Tag: para +msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)." +msgstr "" + +#: using-d-i.xml:1520 +#, no-c-format +#. Tag: para +msgid "Please see the the section on random keys above." +msgstr "" + +#: using-d-i.xml:1534 +#, no-c-format +#. Tag: para +msgid "Please see the the section on erasing data above." +msgstr "" + +#: using-d-i.xml:1543 +#, no-c-format +#. Tag: para +msgid "Please note that the <emphasis>graphical</emphasis> version of the installer still has some limitations when compared to the textual one. For cryptography it means you can set up only volumes using <emphasis>passphrases</emphasis> as the encryption keys." +msgstr "" + +#: using-d-i.xml:1550 +#, no-c-format +#. Tag: para +msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time." +msgstr "" + +#: using-d-i.xml:1561 +#, no-c-format +#. Tag: para +msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)." +msgstr "" + +#: using-d-i.xml:1570 +#, no-c-format +#. Tag: para +msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system." +msgstr "" + +#: using-d-i.xml:1583 +#, no-c-format +#. Tag: para +msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted." +msgstr "" + +#: using-d-i.xml:1599 +#, no-c-format +#. Tag: para +msgid "" + "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n" + "Encrypted volume (<replaceable>crypt0</replaceable>) - 115.1 GB Linux device-mapper\n" + " #1 115.1 GB F ext3\n" + "\n" + "Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile\n" + " #1 515.2 MB F ext3\n" + "</screen></informalexample> Now is the time to assign mount points to the volumes and optionally change the file system types if the defaults do not suit you." +msgstr "" + +#: using-d-i.xml:1612 +#, no-c-format +#. Tag: para +msgid "One thing to note here are the identifiers in parentheses (<replaceable>crypt0</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between ordinary boot process and boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>." +msgstr "" + +#: using-d-i.xml:1622 +#, no-c-format +#. Tag: para +msgid "Once you are satisfied with the partitioning scheme, continue with the installation." +msgstr "" + +#: using-d-i.xml:1633 #, no-c-format #. Tag: title msgid "Setting up the System" msgstr "" -#: using-d-i.xml:1273 +#: using-d-i.xml:1634 #, no-c-format #. Tag: para msgid "After partitioning the installer asks a few more questions that will be used to set up the system it is about to install." msgstr "" -#: using-d-i.xml:1285 +#: using-d-i.xml:1646 #, no-c-format #. Tag: title msgid "Configuring Your Time Zone" msgstr "" -#: using-d-i.xml:1287 +#: using-d-i.xml:1648 #, no-c-format #. Tag: para msgid "Depending on the location selected at the beginning of the installation process, you might be shown a list of timezones relevant for that location. If your location has only one time zone, you will not be asked anything and the system will assume that time zone." msgstr "" -#: using-d-i.xml:1303 +#: using-d-i.xml:1664 #, no-c-format #. Tag: title msgid "Configuring the Clock" msgstr "" -#: using-d-i.xml:1305 +#: using-d-i.xml:1666 #, no-c-format #. Tag: para msgid "The installer might ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed." msgstr "" -#: using-d-i.xml:1312 +#: using-d-i.xml:1673 #, no-c-format #. Tag: para msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"m68k;powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> <phrase arch=\"i386\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase>" msgstr "" -#: using-d-i.xml:1323 +#: using-d-i.xml:1684 #, no-c-format #. Tag: para msgid "Note that the installer does not currently allow you to actually set the time in the computer's clock. You can set the clock to the current time after you have installed, if it is incorrect or if it was previously not set to UTC." msgstr "" -#: using-d-i.xml:1339 +#: using-d-i.xml:1700 #, no-c-format #. Tag: title msgid "Setting Up Users And Passwords" msgstr "" -#: using-d-i.xml:1342 +#: using-d-i.xml:1703 #, no-c-format #. Tag: title msgid "Set the Root Password" msgstr "" -#: using-d-i.xml:1344 +#: using-d-i.xml:1705 #, no-c-format #. Tag: para msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible." msgstr "" -#: using-d-i.xml:1352 +#: using-d-i.xml:1713 #, no-c-format #. Tag: para msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed." msgstr "" -#: using-d-i.xml:1360 +#: using-d-i.xml:1721 #, no-c-format #. Tag: para msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator." msgstr "" -#: using-d-i.xml:1370 +#: using-d-i.xml:1731 #, no-c-format #. Tag: title msgid "Create an Ordinary User" msgstr "" -#: using-d-i.xml:1372 +#: using-d-i.xml:1733 #, no-c-format #. Tag: para msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login." msgstr "" -#: using-d-i.xml:1379 +#: using-d-i.xml:1740 #, no-c-format #. Tag: para msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program — that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail — consider reading one if it is new to you." msgstr "" -#: using-d-i.xml:1389 +#: using-d-i.xml:1750 #, no-c-format #. Tag: para msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account." msgstr "" -#: using-d-i.xml:1396 +#: using-d-i.xml:1757 #, no-c-format #. Tag: para msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command." msgstr "" -#: using-d-i.xml:1408 +#: using-d-i.xml:1769 #, no-c-format #. Tag: title msgid "Installing the Base System" msgstr "" -#: using-d-i.xml:1409 +#: using-d-i.xml:1770 #, no-c-format #. Tag: para msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time." msgstr "" -#: using-d-i.xml:1423 +#: using-d-i.xml:1784 #, no-c-format #. Tag: title msgid "Base System Installation" msgstr "" -#: using-d-i.xml:1425 +#: using-d-i.xml:1786 #, no-c-format #. Tag: para msgid "During the Base installation, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>." msgstr "" -#: using-d-i.xml:1435 +#: using-d-i.xml:1796 #, no-c-format #. Tag: para msgid "The unpack/setup messages generated by the base installation are saved in <filename>/var/log/syslog</filename> when the installation is performed over a serial console." msgstr "" -#: using-d-i.xml:1441 +#: using-d-i.xml:1802 #, no-c-format #. Tag: para msgid "As part of the installation, a Linux kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels." msgstr "" -#: using-d-i.xml:1454 +#: using-d-i.xml:1815 #, no-c-format #. Tag: title msgid "Installing Additional Software" msgstr "" -#: using-d-i.xml:1455 +#: using-d-i.xml:1816 #, no-c-format #. Tag: para msgid "After the base system is installed, you have a usable but limited system. Most users will want to add additional software to the system to tune it to their needs, and the installer lets you do so. This step can take even longer than installing the base system if you have a slow computer or network." msgstr "" -#: using-d-i.xml:1469 +#: using-d-i.xml:1830 #, no-c-format #. Tag: title msgid "Configuring apt" msgstr "" -#: using-d-i.xml:1471 +#: using-d-i.xml:1832 #, no-c-format #. Tag: para msgid "The main means that people use to install packages on their system is via a program called <command>apt-get</command>, from the <classname>apt</classname> package.<footnote> <para> Note that the actual program that installs packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool as it will invoke <command>dpkg</command> as appropriate and also because it knows to install other packages which are required for the package you're trying to install, as well as how to retrieve the package from your CD, the network, or wherever. </para> </footnote> Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command> are also in use and depend on <command>apt-get</command>. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface." msgstr "" -#: using-d-i.xml:1495 +#: using-d-i.xml:1856 #, no-c-format #. Tag: para msgid "<command>apt</command> must be configured so that it knows where to retrieve packages from. The installer largely takes care of this automatically based on what it knows about your installation medium. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>, and you can examine and edit it to your liking after the install is complete." msgstr "" -#: using-d-i.xml:1511 +#: using-d-i.xml:1872 #, no-c-format #. Tag: title msgid "Selecting and Installing Software" msgstr "" -#: using-d-i.xml:1513 +#: using-d-i.xml:1874 #, no-c-format #. Tag: para msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks." msgstr "" -#: using-d-i.xml:1522 +#: using-d-i.xml:1883 #, no-c-format #. Tag: para msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install (or remove) more packages, or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks." msgstr "" -#: using-d-i.xml:1547 +#: using-d-i.xml:1908 #, no-c-format #. Tag: para msgid "Once you've selected your tasks, select <guibutton>Ok</guibutton>. At this point, <command>aptitude</command> will install the packages you've selected." msgstr "" -#: using-d-i.xml:1554 +#: using-d-i.xml:1915 #, no-c-format #. Tag: para msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task." msgstr "" -#: using-d-i.xml:1561 +#: using-d-i.xml:1922 #, no-c-format #. Tag: para msgid "Note that some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can un-select the tasks. You can even opt to install no tasks at all at this point." msgstr "" -#: using-d-i.xml:1569 +#: using-d-i.xml:1930 #, no-c-format #. Tag: para msgid "Each package you selected with <command>tasksel</command> is downloaded, unpacked and then installed in turn by the <command>apt-get</command> and <command>dpkg</command> programs. If a particular program needs more information from the user, it will prompt you during this process." msgstr "" -#: using-d-i.xml:1578 +#: using-d-i.xml:1939 #, no-c-format #. Tag: title msgid "Configuring Your Mail Transport Agent" msgstr "" -#: using-d-i.xml:1580 +#: using-d-i.xml:1941 #, no-c-format #. Tag: para msgid "Today, email is a very important part of many people's life, so it's no surprise Debian lets you configure your mail system right as a part of the installation process. The standard mail transport agent in Debian is <command>exim4</command>, which is relatively small, flexible, and easy to learn." msgstr "" -#: using-d-i.xml:1588 +#: using-d-i.xml:1949 #, no-c-format #. Tag: para msgid "You may ask if this is needed even if your computer is not connected to any network. The short answer is: Yes. The longer explanation: Some system utilities (like <command>cron</command>, <command>quota</command>, <command>aide</command>, …) may send you important notices via email." msgstr "" -#: using-d-i.xml:1596 +#: using-d-i.xml:1957 #, no-c-format #. Tag: para msgid "So on the first screen you will be presented with several common mail scenarios. Choose the one that most closely resembles your needs:" msgstr "" -#: using-d-i.xml:1605 +#: using-d-i.xml:1966 #, no-c-format #. Tag: term msgid "internet site" msgstr "" -#: using-d-i.xml:1606 +#: using-d-i.xml:1967 #, no-c-format #. Tag: para msgid "Your system is connected to a network and your mail is sent and received directly using SMTP. On the following screens you will be asked a few basic questions, like your machine's mail name, or a list of domains for which you accept or relay mail." msgstr "" -#: using-d-i.xml:1617 +#: using-d-i.xml:1978 #, no-c-format #. Tag: term msgid "mail sent by smarthost" msgstr "" -#: using-d-i.xml:1618 +#: using-d-i.xml:1979 #, no-c-format #. Tag: para msgid "In this scenario is your outgoing mail forwarded to another machine, called a <quote>smarthost</quote>, which does the actual job for you. Smarthost also usually stores incoming mail addressed to your computer, so you don't need to be permanently online. That also means you have to download your mail from the smarthost via programs like fetchmail. This option is suitable for dial-up users." msgstr "" -#: using-d-i.xml:1631 +#: using-d-i.xml:1992 #, no-c-format #. Tag: term msgid "local delivery only" msgstr "" -#: using-d-i.xml:1632 +#: using-d-i.xml:1993 #, no-c-format #. Tag: para msgid "Your system is not on a network and mail is sent or received only between local users. Even if you don't plan to send any messages, this option is highly recommended, because some system utilities may send you various alerts from time to time (e.g. beloved <quote>Disk quota exceeded</quote>). This option is also convenient for new users, because it doesn't ask any further questions." msgstr "" -#: using-d-i.xml:1645 +#: using-d-i.xml:2006 #, no-c-format #. Tag: term msgid "no configuration at this time" msgstr "" -#: using-d-i.xml:1646 +#: using-d-i.xml:2007 #, no-c-format #. Tag: para msgid "Choose this if you are absolutely convinced you know what you are doing. This will leave you with an unconfigured mail system — until you configure it, you won't be able to send or receive any mail and you may miss some important messages from your system utilities." msgstr "" -#: using-d-i.xml:1657 +#: using-d-i.xml:2018 #, no-c-format #. Tag: para msgid "If none of these scenarios suits your needs, or if you need a finer setup, you will need to edit configuration files under the <filename>/etc/exim4</filename> directory after the installation is complete. More information about <command>exim4</command> may be found under <filename>/usr/share/doc/exim4</filename>." msgstr "" -#: using-d-i.xml:1672 +#: using-d-i.xml:2033 #, no-c-format #. Tag: title msgid "Making Your System Bootable" msgstr "" -#: using-d-i.xml:1674 +#: using-d-i.xml:2035 #, no-c-format #. Tag: para msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set the OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>" msgstr "" -#: using-d-i.xml:1682 +#: using-d-i.xml:2043 #, no-c-format #. Tag: para msgid "Note that multiple operating systems booting on a single machine is still something of a black art. This document does not even attempt to document the various boot managers, which vary by architecture and even by subarchitecture. You should see your boot manager's documentation for more information." msgstr "" -#: using-d-i.xml:1697 +#: using-d-i.xml:2058 #, no-c-format #. Tag: title msgid "Detecting other operating systems" msgstr "" -#: using-d-i.xml:1699 +#: using-d-i.xml:2060 #, no-c-format #. Tag: para msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to Debian." msgstr "" -#: using-d-i.xml:1707 +#: using-d-i.xml:2068 #, no-c-format #. Tag: para msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information." msgstr "" -#: using-d-i.xml:1725 +#: using-d-i.xml:2086 #, no-c-format #. Tag: title msgid "Install <command>aboot</command> on a Hard Disk" msgstr "" -#: using-d-i.xml:1726 +#: using-d-i.xml:2087 #, no-c-format #. Tag: para msgid "If you have booted from SRM, if you select this option, the installer will write <command>aboot</command> to the first sector of the disk on which you installed Debian. Be <emphasis>very</emphasis> careful — it is <emphasis>not</emphasis> possible to boot multiple operating systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a different operating system installed on the disk where you have installed Debian, you will have to boot GNU/Linux from a floppy instead." msgstr "" -#: using-d-i.xml:1746 +#: using-d-i.xml:2107 #, no-c-format #. Tag: title msgid "<command>palo</command>-installer" msgstr "" -#: using-d-i.xml:1747 +#: using-d-i.xml:2108 #, no-c-format #. Tag: para msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions." msgstr "" -#: using-d-i.xml:1756 +#: using-d-i.xml:2117 #, no-c-format #. Tag: para msgid "hppa FIXME ( need more info )" msgstr "" -#: using-d-i.xml:1768 +#: using-d-i.xml:2129 #, no-c-format #. Tag: title msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" msgstr "" -#: using-d-i.xml:1770 +#: using-d-i.xml:2131 #, no-c-format #. Tag: para msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for newbies and old hands alike." msgstr "" -#: using-d-i.xml:1776 +#: using-d-i.xml:2137 #, no-c-format #. Tag: para msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information." msgstr "" -#: using-d-i.xml:1782 +#: using-d-i.xml:2143 #, no-c-format #. Tag: para msgid "If you do not want to install grub at all, use the Back button to get to the main menu, and from there select whatever bootloader you would like to use." msgstr "" -#: using-d-i.xml:1796 +#: using-d-i.xml:2157 #, no-c-format #. Tag: title msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk" msgstr "" -#: using-d-i.xml:1798 +#: using-d-i.xml:2159 #, no-c-format #. Tag: para msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>." msgstr "" -#: using-d-i.xml:1808 +#: using-d-i.xml:2169 #, no-c-format #. Tag: para msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation." msgstr "" -#: using-d-i.xml:1816 +#: using-d-i.xml:2177 #, no-c-format #. Tag: para msgid "&d-i; presents you three choices where to install the <command>LILO</command> boot loader:" msgstr "" -#: using-d-i.xml:1823 +#: using-d-i.xml:2184 #, no-c-format #. Tag: term msgid "Master Boot Record (MBR)" msgstr "" -#: using-d-i.xml:1823 +#: using-d-i.xml:2184 #, no-c-format #. Tag: para msgid "This way the <command>LILO</command> will take complete control of the boot process." msgstr "" -#: using-d-i.xml:1830 +#: using-d-i.xml:2191 #, no-c-format #. Tag: term msgid "new Debian partition" msgstr "" -#: using-d-i.xml:1830 +#: using-d-i.xml:2191 #, no-c-format #. Tag: para msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new Debian partition and it will serve as a secondary boot loader." msgstr "" -#: using-d-i.xml:1839 +#: using-d-i.xml:2200 #, no-c-format #. Tag: term msgid "Other choice" msgstr "" -#: using-d-i.xml:1839 +#: using-d-i.xml:2200 #, no-c-format #. Tag: para msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use devfs style names, such as those that start with <filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and <filename>/dev/discs</filename>, as well as traditional names, such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>." msgstr "" -#: using-d-i.xml:1851 +#: using-d-i.xml:2212 #, no-c-format #. Tag: para msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record — however, this means that you'll need to use some other way to get back into Debian! For more information on this please read <xref linkend=\"reactivating-win\"/>." msgstr "" -#: using-d-i.xml:1868 +#: using-d-i.xml:2229 #, no-c-format #. Tag: title msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" msgstr "" -#: using-d-i.xml:1870 +#: using-d-i.xml:2231 #, no-c-format #. Tag: para msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies file into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to actually do the work of loading and starting the Linux kernel." msgstr "" -#: using-d-i.xml:1886 +#: using-d-i.xml:2247 #, no-c-format #. Tag: para msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem." msgstr "" -#: using-d-i.xml:1898 +#: using-d-i.xml:2259 #, no-c-format #. Tag: title msgid "Choose the correct partition!" msgstr "" -#: using-d-i.xml:1900 +#: using-d-i.xml:2261 #, no-c-format #. Tag: para msgid "The criteria for selecting a partition is that it is FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, the <command>elilo</command> may format the partition during the installation, erasing any previous contents!" msgstr "" -#: using-d-i.xml:1915 +#: using-d-i.xml:2276 #, no-c-format #. Tag: title msgid "EFI Partition Contents" msgstr "" -#: using-d-i.xml:1917 +#: using-d-i.xml:2278 #, no-c-format #. Tag: para msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured." msgstr "" -#: using-d-i.xml:1939 +#: using-d-i.xml:2300 #, no-c-format #. Tag: filename msgid "elilo.conf" msgstr "" -#: using-d-i.xml:1940 +#: using-d-i.xml:2301 #, no-c-format #. Tag: para msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition." msgstr "" -#: using-d-i.xml:1949 +#: using-d-i.xml:2310 #, no-c-format #. Tag: filename msgid "elilo.efi" msgstr "" -#: using-d-i.xml:1950 +#: using-d-i.xml:2311 #, no-c-format #. Tag: para msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>Debian GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu." msgstr "" -#: using-d-i.xml:1960 +#: using-d-i.xml:2321 #, no-c-format #. Tag: filename msgid "initrd.img" msgstr "" -#: using-d-i.xml:1961 +#: using-d-i.xml:2322 #, no-c-format #. Tag: para msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>." msgstr "" -#: using-d-i.xml:1973 +#: using-d-i.xml:2334 #, no-c-format #. Tag: filename msgid "readme.txt" msgstr "" -#: using-d-i.xml:1974 +#: using-d-i.xml:2335 #, no-c-format #. Tag: para msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run." msgstr "" -#: using-d-i.xml:1984 +#: using-d-i.xml:2345 #, no-c-format #. Tag: filename msgid "vmlinuz" msgstr "" -#: using-d-i.xml:1985 +#: using-d-i.xml:2346 #, no-c-format #. Tag: para msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>." msgstr "" -#: using-d-i.xml:2005 +#: using-d-i.xml:2366 #, no-c-format #. Tag: title msgid "<command>arcboot</command>-installer" msgstr "" -#: using-d-i.xml:2006 +#: using-d-i.xml:2367 #, no-c-format #. Tag: para msgid "" @@ -1616,61 +1863,61 @@ msgid "" "</screen></informalexample> on the firmware prompt, and then typing <command>boot</command>." msgstr "" -#: using-d-i.xml:2025 +#: using-d-i.xml:2386 #, no-c-format #. Tag: replaceable msgid "scsi" msgstr "" -#: using-d-i.xml:2026 +#: using-d-i.xml:2387 #, no-c-format #. Tag: para msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers" msgstr "" -#: using-d-i.xml:2034 +#: using-d-i.xml:2395 #, no-c-format #. Tag: replaceable msgid "disk" msgstr "" -#: using-d-i.xml:2035 +#: using-d-i.xml:2396 #, no-c-format #. Tag: para msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed" msgstr "" -#: using-d-i.xml:2043 using-d-i.xml:2112 +#: using-d-i.xml:2404 using-d-i.xml:2473 #, no-c-format #. Tag: replaceable msgid "partnr" msgstr "" -#: using-d-i.xml:2044 +#: using-d-i.xml:2405 #, no-c-format #. Tag: para msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides" msgstr "" -#: using-d-i.xml:2052 +#: using-d-i.xml:2413 #, no-c-format #. Tag: replaceable msgid "config" msgstr "" -#: using-d-i.xml:2053 +#: using-d-i.xml:2414 #, no-c-format #. Tag: para msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default." msgstr "" -#: using-d-i.xml:2074 +#: using-d-i.xml:2435 #, no-c-format #. Tag: title msgid "<command>delo</command>-installer" msgstr "" -#: using-d-i.xml:2075 +#: using-d-i.xml:2436 #, no-c-format #. Tag: para msgid "" @@ -1679,247 +1926,247 @@ msgid "" "</screen></informalexample> on the firmware prompt." msgstr "" -#: using-d-i.xml:2094 +#: using-d-i.xml:2455 #, no-c-format #. Tag: replaceable msgid "<replaceable>#</replaceable>" msgstr "" -#: using-d-i.xml:2095 +#: using-d-i.xml:2456 #, no-c-format #. Tag: para msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers" msgstr "" -#: using-d-i.xml:2103 +#: using-d-i.xml:2464 #, no-c-format #. Tag: replaceable msgid "<replaceable>id</replaceable>" msgstr "" -#: using-d-i.xml:2104 +#: using-d-i.xml:2465 #, no-c-format #. Tag: para msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed" msgstr "" -#: using-d-i.xml:2113 +#: using-d-i.xml:2474 #, no-c-format #. Tag: para msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides" msgstr "" -#: using-d-i.xml:2121 +#: using-d-i.xml:2482 #, no-c-format #. Tag: replaceable msgid "name" msgstr "" -#: using-d-i.xml:2122 +#: using-d-i.xml:2483 #, no-c-format #. Tag: para msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default." msgstr "" -#: using-d-i.xml:2132 +#: using-d-i.xml:2493 #, no-c-format #. Tag: para msgid "In case <filename>/etc/delo.conf</filename> is on the first partition on the disk and the default configuration shall be booted, it is sufficient to use" msgstr "" -#: using-d-i.xml:2138 +#: using-d-i.xml:2499 #, no-c-format #. Tag: screen msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>" msgstr "" -#: using-d-i.xml:2148 +#: using-d-i.xml:2509 #, no-c-format #. Tag: title msgid "Install <command>Yaboot</command> on a Hard Disk" msgstr "" -#: using-d-i.xml:2149 +#: using-d-i.xml:2510 #, no-c-format #. Tag: para msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian;." msgstr "" -#: using-d-i.xml:2167 +#: using-d-i.xml:2528 #, no-c-format #. Tag: title msgid "Install <command>Quik</command> on a Hard Disk" msgstr "" -#: using-d-i.xml:2168 +#: using-d-i.xml:2529 #, no-c-format #. Tag: para msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones." msgstr "" -#: using-d-i.xml:2184 +#: using-d-i.xml:2545 #, no-c-format #. Tag: title msgid "<command>zipl</command>-installer" msgstr "" -#: using-d-i.xml:2185 +#: using-d-i.xml:2546 #, no-c-format #. Tag: para msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>." msgstr "" -#: using-d-i.xml:2202 +#: using-d-i.xml:2563 #, no-c-format #. Tag: title msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" msgstr "" -#: using-d-i.xml:2204 +#: using-d-i.xml:2565 #, no-c-format #. Tag: para msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install." msgstr "" -#: using-d-i.xml:2229 +#: using-d-i.xml:2590 #, no-c-format #. Tag: title msgid "Continue Without Boot Loader" msgstr "" -#: using-d-i.xml:2231 +#: using-d-i.xml:2592 #, no-c-format #. Tag: para msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader). <phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, and Amiga systems, where the original operating system must be maintained on the box and used to boot GNU/Linux.</phrase>" msgstr "" -#: using-d-i.xml:2240 +#: using-d-i.xml:2601 #, no-c-format #. Tag: para msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem." msgstr "" -#: using-d-i.xml:2257 +#: using-d-i.xml:2618 #, no-c-format #. Tag: title msgid "Finishing the Installation" msgstr "" -#: using-d-i.xml:2258 +#: using-d-i.xml:2619 #, no-c-format #. Tag: para msgid "These are the last bits to do before rebooting to your new system. It mostly consists of tidying up after the &d-i;." msgstr "" -#: using-d-i.xml:2270 +#: using-d-i.xml:2631 #, no-c-format #. Tag: title msgid "Finish the Installation and Reboot" msgstr "" -#: using-d-i.xml:2272 +#: using-d-i.xml:2633 #, no-c-format #. Tag: para msgid "This is the last step in the initial Debian installation process. You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. The installer will do any last minute tasks, and then reboot into your new Debian system." msgstr "" -#: using-d-i.xml:2279 +#: using-d-i.xml:2640 #, no-c-format #. Tag: para msgid "Select the <guimenuitem>Finish the installation</guimenuitem> menu item which will halt the system because rebooting is not supported on &arch-title; in this case. You then need to IPL GNU/Linux from the DASD which you selected for the root filesystem during the first steps of the installation." msgstr "" -#: using-d-i.xml:2293 +#: using-d-i.xml:2654 #, no-c-format #. Tag: title msgid "Miscellaneous" msgstr "" -#: using-d-i.xml:2294 +#: using-d-i.xml:2655 #, no-c-format #. Tag: para msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong." msgstr "" -#: using-d-i.xml:2307 +#: using-d-i.xml:2668 #, no-c-format #. Tag: title msgid "Saving the installation logs" msgstr "" -#: using-d-i.xml:2309 +#: using-d-i.xml:2670 #, no-c-format #. Tag: para msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new Debian system." msgstr "" -#: using-d-i.xml:2316 +#: using-d-i.xml:2677 #, no-c-format #. Tag: para msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report." msgstr "" -#: using-d-i.xml:2336 +#: using-d-i.xml:2697 #, no-c-format #. Tag: title msgid "Using the Shell and Viewing the Logs" msgstr "" -#: using-d-i.xml:2339 +#: using-d-i.xml:2700 #, no-c-format #. Tag: para msgid "There is an <guimenuitem>Execute a Shell</guimenuitem> item on the menu. If the menu is not available when you need to use the shell, press <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap> </keycombo>) to switch to the second <emphasis>virtual console</emphasis>. That's the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap>, and the <keycap>F2</keycap> function key, at the same time. This is a separate window running a Bourne shell clone called <command>ash</command>." msgstr "" -#: using-d-i.xml:2351 +#: using-d-i.xml:2712 #, no-c-format #. Tag: para msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The text editor is <command>nano</command>. The shell has some nice features like autocompletion and history." msgstr "" -#: using-d-i.xml:2360 +#: using-d-i.xml:2721 #, no-c-format #. Tag: para msgid "Use the menus to perform any task that they are able to do — the shell and commands are only there in case something goes wrong. In particular, you should always use the menus, not the shell, to activate your swap partition, because the menu software can't detect that you've done this from the shell. Press <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to get back to menus, or type <command>exit</command> if you used a menu item to open the shell." msgstr "" -#: using-d-i.xml:2379 +#: using-d-i.xml:2740 #, no-c-format #. Tag: title msgid "Installation Over the Network" msgstr "" -#: using-d-i.xml:2381 +#: using-d-i.xml:2742 #, no-c-format #. Tag: para msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)" msgstr "" -#: using-d-i.xml:2391 +#: using-d-i.xml:2752 #, no-c-format #. Tag: para msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>." msgstr "" -#: using-d-i.xml:2404 +#: using-d-i.xml:2765 #, no-c-format #. Tag: para msgid "For installations on &arch-title;, this is the default method after setting up the network." msgstr "" -#: using-d-i.xml:2409 +#: using-d-i.xml:2770 #, no-c-format #. Tag: para msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the <quote>person who will continue the installation remotely</quote>." msgstr "" -#: using-d-i.xml:2421 +#: using-d-i.xml:2782 #, no-c-format #. Tag: para msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component." msgstr "" -#: using-d-i.xml:2427 +#: using-d-i.xml:2788 #, no-c-format #. Tag: para msgid "" @@ -1928,25 +2175,25 @@ msgid "" "</screen></informalexample> Where <replaceable>install_host</replaceable> is either the name or IP address of the computer being installed. Before the actual login the fingerprint of the remote system will be displayed and you will have to confirm that it is correct." msgstr "" -#: using-d-i.xml:2444 +#: using-d-i.xml:2805 #, no-c-format #. Tag: para msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename> and try again." msgstr "" -#: using-d-i.xml:2453 +#: using-d-i.xml:2814 #, no-c-format #. Tag: para msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells." msgstr "" -#: using-d-i.xml:2463 +#: using-d-i.xml:2824 #, no-c-format #. Tag: para msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system." msgstr "" -#: using-d-i.xml:2471 +#: using-d-i.xml:2832 #, no-c-format #. Tag: para msgid "Also, if you are running the SSH session from an X terminal, you should not resize the window as that will result in the connection being terminated." |