diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/bookinfo.pot | 22 | ||||
| -rw-r--r-- | po/pot/boot-installer.pot | 74 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 1058 | ||||
| -rw-r--r-- | po/pot/post-install.pot | 264 | ||||
| -rw-r--r-- | po/pot/preparing.pot | 6 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 611 |
6 files changed, 1153 insertions, 882 deletions
diff --git a/po/pot/bookinfo.pot b/po/pot/bookinfo.pot index fdcfd75c3..68be893ad 100644 --- a/po/pot/bookinfo.pot +++ b/po/pot/bookinfo.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-07-25 21:39+0000\n" +"POT-Creation-Date: 2006-12-29 10:24+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" @@ -29,29 +29,41 @@ msgstr "" #. Tag: para #: bookinfo.xml:17 #, no-c-format +msgid "Because the &arch-title; port is not a release architecture for &releasename;, there is no official version of this manual for &arch-title; for &releasename;. However, because the port is still active and there is hope that &arch-title; may be included again in future official releases, this development version of the Installation Guide is still available." +msgstr "" + +#. Tag: para +#: bookinfo.xml:25 +#, no-c-format +msgid "Because &arch-title; is not an official architecture, some of the information, and especially some links, in this manual may be incorrect. For additional information, please check the <ulink url=\"&url-ports;\">webpages</ulink> of the port or contact the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink>." +msgstr "" + +#. Tag: para +#: bookinfo.xml:36 +#, no-c-format msgid "This installation guide is based on an earlier manual written for the old Debian installation system (the <quote>boot-floppies</quote>), and has been updated to document the new Debian installer. However, for &architecture;, the manual has not been fully updated and fact checked for the new installer. There may remain parts of the manual that are incomplete or outdated or that still document the boot-floppies installer. A newer version of this manual, possibly better documenting this architecture, may be found on the Internet at the <ulink url=\"&url-d-i;\">&d-i; home page</ulink>. You may also be able to find additional translations there." msgstr "" #. Tag: para -#: bookinfo.xml:30 +#: bookinfo.xml:49 #, no-c-format msgid "Although this installation guide for &architecture; is mostly up-to-date, we plan to make some changes and reorganize parts of the manual after the official release of &releasename;. A newer version of this manual may be found on the Internet at the <ulink url=\"&url-d-i;\">&d-i; home page</ulink>. You may also be able to find additional translations there." msgstr "" #. Tag: para -#: bookinfo.xml:39 +#: bookinfo.xml:58 #, no-c-format msgid "Translators can use this paragraph to provide some information about the status of the translation, for example if the translation is still being worked on or if review is wanted (don't forget to mention where comments should be sent!). See build/lang-options/README on how to enable this paragraph. Its condition is \"translation-status\"." msgstr "" #. Tag: holder -#: bookinfo.xml:54 +#: bookinfo.xml:73 #, no-c-format msgid "the Debian Installer team" msgstr "" #. Tag: para -#: bookinfo.xml:58 +#: bookinfo.xml:77 #, no-c-format msgid "This manual is free software; you may redistribute it and/or modify it under the terms of the GNU General Public License. Please refer to the license in <xref linkend=\"appendix-gpl\"/>." msgstr "" diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 32c890d45..1ff1b0700 100644 --- a/po/pot/boot-installer.pot +++ b/po/pot/boot-installer.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-27 20:04+0000\n" +"POT-Creation-Date: 2006-12-29 10:24+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" @@ -2481,7 +2481,7 @@ msgid "If you have a large amount of memory installed in your machine, more than msgstr "" #. Tag: title -#: boot-installer.xml:3506 +#: boot-installer.xml:3506 boot-installer.xml:3591 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" @@ -2537,7 +2537,7 @@ msgstr "" #. Tag: title #: boot-installer.xml:3576 #, no-c-format -msgid "System Freeze while Loading the USB Modules" +msgid "System Freeze while Loading USB Modules" msgstr "" #. Tag: para @@ -2546,62 +2546,108 @@ msgstr "" msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter at the boot prompt, which will prevent the modules from being loaded." msgstr "" +#. Tag: para +#: boot-installer.xml:3592 +#, no-c-format +msgid "There are some common installation problems that are worth mentioning." +msgstr "" + #. Tag: title -#: boot-installer.xml:3591 +#: boot-installer.xml:3598 +#, no-c-format +msgid "Misdirected video output" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3599 +#, no-c-format +msgid "" + "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n" + "Remapping the kernel... done\n" + "Booting Linux...\n" + "</screen></informalexample> To work around this, you can either pull out one of the video cards, or disable the one not used during the OpenProm boot phase using a kernel parameter. For example, to disable an ATI card, you should boot the installer with <userinput>video=atyfb:off</userinput>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3613 +#, no-c-format +msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3624 +#, no-c-format +msgid "Failure to Boot or Kernel from CD-ROM" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3625 +#, no-c-format +msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3631 +#, no-c-format +msgid "We recommend to install such systems by netbooting the installer." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3640 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3593 +#: boot-installer.xml:3642 #, no-c-format msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable> </computeroutput>, or <computeroutput> <replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable> </computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable> </computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." msgstr "" #. Tag: title -#: boot-installer.xml:3618 +#: boot-installer.xml:3667 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3619 +#: boot-installer.xml:3668 #, no-c-format msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report you may want to attach this information to the bug report." msgstr "" #. Tag: para -#: boot-installer.xml:3630 +#: boot-installer.xml:3679 #, no-c-format msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system." msgstr "" #. Tag: title -#: boot-installer.xml:3641 +#: boot-installer.xml:3690 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3642 +#: boot-installer.xml:3691 #, no-c-format msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations." msgstr "" #. Tag: para -#: boot-installer.xml:3649 +#: boot-installer.xml:3698 #, no-c-format msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an E-Mail address that you do not mind being made public." msgstr "" #. Tag: para -#: boot-installer.xml:3655 +#: boot-installer.xml:3704 #, no-c-format -msgid "If you have a working Debian system, the easiest way to send an installation report is to install the installation-report and reportbug packages (<command>apt-get install installation-report reportbug</command>) and run the command <command>reportbug installation-report</command>." +msgid "If you have a working Debian system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-report</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3662 +#: boot-installer.xml:3714 #, no-c-format msgid "" "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n" diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index 72b28ff66..cf394da5b 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-26 01:54+0000\n" +"POT-Creation-Date: 2006-12-29 10:24+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" @@ -315,13 +315,13 @@ msgid "DECstation" msgstr "" #. Tag: entry -#: hardware.xml:136 hardware.xml:1104 hardware.xml:1119 hardware.xml:1129 +#: hardware.xml:136 hardware.xml:1107 hardware.xml:1122 hardware.xml:1132 #, no-c-format msgid "r4k-kn04" msgstr "" #. Tag: entry -#: hardware.xml:138 hardware.xml:1099 hardware.xml:1109 hardware.xml:1114 hardware.xml:1124 +#: hardware.xml:138 hardware.xml:1102 hardware.xml:1112 hardware.xml:1117 hardware.xml:1127 #, no-c-format msgid "r3k-kn02" msgstr "" @@ -459,9 +459,15 @@ msgid "sparc" msgstr "" #. Tag: entry +#: hardware.xml:183 +#, no-c-format +msgid "<entry>sun4m</entry>" +msgstr "" + +#. Tag: entry #: hardware.xml:184 #, no-c-format -msgid "sun4cdm" +msgid "sparc32" msgstr "" #. Tag: entry @@ -471,1477 +477,1489 @@ msgid "<entry>sun4u</entry>" msgstr "" #. Tag: entry -#: hardware.xml:190 +#: hardware.xml:187 +#, no-c-format +msgid "sparc64" +msgstr "" + +#. Tag: entry +#: hardware.xml:189 +#, no-c-format +msgid "<entry>sun4v</entry>" +msgstr "" + +#. Tag: entry +#: hardware.xml:193 #, no-c-format msgid "IBM S/390" msgstr "" #. Tag: entry -#: hardware.xml:191 +#: hardware.xml:194 #, no-c-format msgid "s390" msgstr "" #. Tag: entry -#: hardware.xml:192 +#: hardware.xml:195 #, no-c-format msgid "IPL from VM-reader and DASD" msgstr "" #. Tag: entry -#: hardware.xml:193 +#: hardware.xml:196 #, no-c-format msgid "generic" msgstr "" #. Tag: entry -#: hardware.xml:195 +#: hardware.xml:198 #, no-c-format msgid "IPL from tape" msgstr "" #. Tag: entry -#: hardware.xml:196 +#: hardware.xml:199 #, no-c-format msgid "tape" msgstr "" #. Tag: para -#: hardware.xml:201 +#: hardware.xml:204 #, no-c-format msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture. If you are looking for information on any of the other Debian-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">Debian-Ports</ulink> pages." msgstr "" #. Tag: para -#: hardware.xml:209 +#: hardware.xml:212 #, no-c-format msgid "This is the first official release of &debian; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well." msgstr "" #. Tag: title -#: hardware.xml:231 hardware.xml:690 hardware.xml:726 hardware.xml:819 hardware.xml:838 hardware.xml:924 hardware.xml:966 hardware.xml:1034 hardware.xml:1193 +#: hardware.xml:234 hardware.xml:693 hardware.xml:729 hardware.xml:822 hardware.xml:841 hardware.xml:927 hardware.xml:969 hardware.xml:1037 hardware.xml:1196 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para -#: hardware.xml:232 +#: hardware.xml:235 #, no-c-format msgid "Complete information regarding supported DEC Alphas can be found at <ulink url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this section is to describe the systems supported by the boot disks." msgstr "" #. Tag: para -#: hardware.xml:239 +#: hardware.xml:242 #, no-c-format msgid "Alpha machines are subdivided into different system types because there are a number of generations of motherboard and supporting chipsets. Different systems (<quote>sub-architectures</quote>) often have radically different engineering and capabilities. Therefore, the process of installing and, more to the point, booting, can vary from system to system." msgstr "" #. Tag: para -#: hardware.xml:247 +#: hardware.xml:250 #, no-c-format msgid "The following table lists the system types supported by the Debian installation system. The table also indicates the <emphasis>code name</emphasis> for these system types. You'll need to know this code name when you actually begin the installation process:" msgstr "" #. Tag: entry -#: hardware.xml:264 +#: hardware.xml:267 #, no-c-format msgid "Hardware Type" msgstr "" #. Tag: entry -#: hardware.xml:265 +#: hardware.xml:268 #, no-c-format msgid "Aliases" msgstr "" #. Tag: entry -#: hardware.xml:265 +#: hardware.xml:268 #, no-c-format msgid "MILO image" msgstr "" #. Tag: entry -#: hardware.xml:271 +#: hardware.xml:274 #, no-c-format msgid "ALCOR" msgstr "" #. Tag: entry -#: hardware.xml:272 +#: hardware.xml:275 #, no-c-format msgid "AlphaStation 500 5/266.300" msgstr "" #. Tag: entry -#: hardware.xml:273 +#: hardware.xml:276 #, no-c-format msgid "Maverick" msgstr "" #. Tag: entry -#: hardware.xml:274 hardware.xml:278 hardware.xml:282 +#: hardware.xml:277 hardware.xml:281 hardware.xml:285 #, no-c-format msgid "alcor" msgstr "" #. Tag: entry -#: hardware.xml:276 +#: hardware.xml:279 #, no-c-format msgid "AlphaStation 500 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:277 +#: hardware.xml:280 #, no-c-format msgid "Bret" msgstr "" #. Tag: entry -#: hardware.xml:280 +#: hardware.xml:283 #, no-c-format msgid "AlphaStation 600/266...300" msgstr "" #. Tag: entry -#: hardware.xml:281 +#: hardware.xml:284 #, no-c-format msgid "Alcor" msgstr "" #. Tag: entry -#: hardware.xml:284 +#: hardware.xml:287 #, no-c-format msgid "AlphaStation 600/300...433" msgstr "" #. Tag: entry -#: hardware.xml:285 +#: hardware.xml:288 #, no-c-format msgid "<entry>XLT</entry>" msgstr "" #. Tag: entry -#: hardware.xml:286 +#: hardware.xml:289 #, no-c-format msgid "<entry>xlt</entry>" msgstr "" #. Tag: entry -#: hardware.xml:290 +#: hardware.xml:293 #, no-c-format msgid "BOOK1" msgstr "" #. Tag: entry -#: hardware.xml:291 +#: hardware.xml:294 #, no-c-format msgid "AlphaBook1 (laptop)" msgstr "" #. Tag: entry -#: hardware.xml:292 +#: hardware.xml:295 #, no-c-format msgid "Alphabook1/Burns" msgstr "" #. Tag: entry -#: hardware.xml:293 +#: hardware.xml:296 #, no-c-format msgid "book1" msgstr "" #. Tag: entry -#: hardware.xml:297 +#: hardware.xml:300 #, no-c-format msgid "AVANTI" msgstr "" #. Tag: entry -#: hardware.xml:298 +#: hardware.xml:301 #, no-c-format msgid "AlphaStation 200 4/100...166" msgstr "" #. Tag: entry -#: hardware.xml:299 +#: hardware.xml:302 #, no-c-format msgid "Mustang" msgstr "" #. Tag: entry -#: hardware.xml:300 hardware.xml:304 hardware.xml:308 hardware.xml:312 hardware.xml:316 hardware.xml:320 hardware.xml:324 hardware.xml:328 +#: hardware.xml:303 hardware.xml:307 hardware.xml:311 hardware.xml:315 hardware.xml:319 hardware.xml:323 hardware.xml:327 hardware.xml:331 #, no-c-format msgid "avanti" msgstr "" #. Tag: entry -#: hardware.xml:302 +#: hardware.xml:305 #, no-c-format msgid "AlphaStation 200 4/233" msgstr "" #. Tag: entry -#: hardware.xml:303 +#: hardware.xml:306 #, no-c-format msgid "Mustang+" msgstr "" #. Tag: entry -#: hardware.xml:306 +#: hardware.xml:309 #, no-c-format msgid "AlphaStation 205 4/133...333" msgstr "" #. Tag: entry -#: hardware.xml:307 +#: hardware.xml:310 #, no-c-format msgid "<entry>LX3</entry>" msgstr "" #. Tag: entry -#: hardware.xml:310 +#: hardware.xml:313 #, no-c-format msgid "AlphaStation 250 4/300" msgstr "" #. Tag: entry -#: hardware.xml:311 +#: hardware.xml:314 #, no-c-format msgid "<entry>M3+</entry>" msgstr "" #. Tag: entry -#: hardware.xml:314 +#: hardware.xml:317 #, no-c-format msgid "AlphaStation 255 4/133...333" msgstr "" #. Tag: entry -#: hardware.xml:315 +#: hardware.xml:318 #, no-c-format msgid "LX3+" msgstr "" #. Tag: entry -#: hardware.xml:318 +#: hardware.xml:321 #, no-c-format msgid "AlphaStation 300 4/266" msgstr "" #. Tag: entry -#: hardware.xml:319 +#: hardware.xml:322 #, no-c-format msgid "Melmac" msgstr "" #. Tag: entry -#: hardware.xml:322 +#: hardware.xml:325 #, no-c-format msgid "AlphaStation 400 4/166" msgstr "" #. Tag: entry -#: hardware.xml:323 +#: hardware.xml:326 #, no-c-format msgid "Chinet" msgstr "" #. Tag: entry -#: hardware.xml:326 +#: hardware.xml:329 #, no-c-format msgid "AlphaStation 400 4/233...300" msgstr "" #. Tag: entry -#: hardware.xml:327 +#: hardware.xml:330 #, no-c-format msgid "Avanti" msgstr "" #. Tag: entry -#: hardware.xml:332 hardware.xml:345 hardware.xml:346 +#: hardware.xml:335 hardware.xml:348 hardware.xml:349 #, no-c-format msgid "EB164" msgstr "" #. Tag: entry -#: hardware.xml:333 +#: hardware.xml:336 #, no-c-format msgid "AlphaPC164" msgstr "" #. Tag: entry -#: hardware.xml:334 +#: hardware.xml:337 #, no-c-format msgid "PC164" msgstr "" #. Tag: entry -#: hardware.xml:335 +#: hardware.xml:338 #, no-c-format msgid "pc164" msgstr "" #. Tag: entry -#: hardware.xml:337 +#: hardware.xml:340 #, no-c-format msgid "AlphaPC164-LX" msgstr "" #. Tag: entry -#: hardware.xml:338 +#: hardware.xml:341 #, no-c-format msgid "LX164" msgstr "" #. Tag: entry -#: hardware.xml:339 +#: hardware.xml:342 #, no-c-format msgid "lx164" msgstr "" #. Tag: entry -#: hardware.xml:341 +#: hardware.xml:344 #, no-c-format msgid "AlphaPC164-SX" msgstr "" #. Tag: entry -#: hardware.xml:342 +#: hardware.xml:345 #, no-c-format msgid "SX164" msgstr "" #. Tag: entry -#: hardware.xml:343 +#: hardware.xml:346 #, no-c-format msgid "sx164" msgstr "" #. Tag: entry -#: hardware.xml:347 +#: hardware.xml:350 #, no-c-format msgid "eb164" msgstr "" #. Tag: entry -#: hardware.xml:351 hardware.xml:360 hardware.xml:361 +#: hardware.xml:354 hardware.xml:363 hardware.xml:364 #, no-c-format msgid "EB64+" msgstr "" #. Tag: entry -#: hardware.xml:352 +#: hardware.xml:355 #, no-c-format msgid "AlphaPC64" msgstr "" #. Tag: entry -#: hardware.xml:353 hardware.xml:357 +#: hardware.xml:356 hardware.xml:360 #, no-c-format msgid "Cabriolet" msgstr "" #. Tag: entry -#: hardware.xml:354 hardware.xml:358 +#: hardware.xml:357 hardware.xml:361 #, no-c-format msgid "cabriolet" msgstr "" #. Tag: entry -#: hardware.xml:356 +#: hardware.xml:359 #, no-c-format msgid "AlphaPCI64" msgstr "" #. Tag: entry -#: hardware.xml:362 +#: hardware.xml:365 #, no-c-format msgid "eb64p" msgstr "" #. Tag: entry -#: hardware.xml:366 hardware.xml:367 hardware.xml:368 +#: hardware.xml:369 hardware.xml:370 hardware.xml:371 #, no-c-format msgid "EB66" msgstr "" #. Tag: entry -#: hardware.xml:369 +#: hardware.xml:372 #, no-c-format msgid "eb66" msgstr "" #. Tag: entry -#: hardware.xml:371 hardware.xml:372 +#: hardware.xml:374 hardware.xml:375 #, no-c-format msgid "EB66+" msgstr "" #. Tag: entry -#: hardware.xml:373 +#: hardware.xml:376 #, no-c-format msgid "eb66p" msgstr "" #. Tag: entry -#: hardware.xml:377 +#: hardware.xml:380 #, no-c-format msgid "JENSEN" msgstr "" #. Tag: entry -#: hardware.xml:378 +#: hardware.xml:381 #, no-c-format msgid "DEC 2000 Model 300(S)" msgstr "" #. Tag: entry -#: hardware.xml:379 hardware.xml:387 +#: hardware.xml:382 hardware.xml:390 #, no-c-format msgid "Jensen" msgstr "" #. Tag: entry -#: 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 +#: hardware.xml:383 hardware.xml:387 hardware.xml:391 hardware.xml:452 hardware.xml:456 hardware.xml:474 hardware.xml:478 hardware.xml:482 hardware.xml:486 hardware.xml:490 hardware.xml:494 hardware.xml:498 hardware.xml:512 hardware.xml:516 hardware.xml:520 hardware.xml:524 hardware.xml:528 hardware.xml:562 hardware.xml:566 hardware.xml:570 hardware.xml:574 hardware.xml:588 hardware.xml:592 hardware.xml:596 hardware.xml:600 hardware.xml:607 hardware.xml:611 hardware.xml:615 hardware.xml:619 hardware.xml:623 hardware.xml:627 hardware.xml:631 hardware.xml:635 hardware.xml:639 hardware.xml:643 hardware.xml:647 hardware.xml:651 hardware.xml:655 hardware.xml:662 hardware.xml:666 #, no-c-format msgid "<entry>N/A</entry>" msgstr "" #. Tag: entry -#: hardware.xml:382 +#: hardware.xml:385 #, no-c-format msgid "DEC 2000 Model 500" msgstr "" #. Tag: entry -#: hardware.xml:383 +#: hardware.xml:386 #, no-c-format msgid "Culzen" msgstr "" #. Tag: entry -#: hardware.xml:386 +#: hardware.xml:389 #, no-c-format msgid "DECpc 150" msgstr "" #. Tag: entry -#: hardware.xml:392 +#: hardware.xml:395 #, no-c-format msgid "MIATA" msgstr "" #. Tag: entry -#: hardware.xml:393 +#: hardware.xml:396 #, no-c-format msgid "Personal WorkStation 433a" msgstr "" #. Tag: entry -#: hardware.xml:394 hardware.xml:398 hardware.xml:402 hardware.xml:406 hardware.xml:410 hardware.xml:414 hardware.xml:418 hardware.xml:422 +#: hardware.xml:397 hardware.xml:401 hardware.xml:405 hardware.xml:409 hardware.xml:413 hardware.xml:417 hardware.xml:421 hardware.xml:425 #, no-c-format msgid "Miata" msgstr "" #. Tag: entry -#: hardware.xml:395 hardware.xml:399 hardware.xml:403 hardware.xml:407 hardware.xml:411 hardware.xml:415 hardware.xml:419 hardware.xml:423 +#: hardware.xml:398 hardware.xml:402 hardware.xml:406 hardware.xml:410 hardware.xml:414 hardware.xml:418 hardware.xml:422 hardware.xml:426 #, no-c-format msgid "miata" msgstr "" #. Tag: entry -#: hardware.xml:397 +#: hardware.xml:400 #, no-c-format msgid "Personal WorkStation 433au" msgstr "" #. Tag: entry -#: hardware.xml:401 +#: hardware.xml:404 #, no-c-format msgid "Personal WorkStation 466au" msgstr "" #. Tag: entry -#: hardware.xml:405 +#: hardware.xml:408 #, no-c-format msgid "Personal WorkStation 500a" msgstr "" #. Tag: entry -#: hardware.xml:409 +#: hardware.xml:412 #, no-c-format msgid "Personal WorkStation 500au" msgstr "" #. Tag: entry -#: hardware.xml:413 +#: hardware.xml:416 #, no-c-format msgid "Personal WorkStation 550au" msgstr "" #. Tag: entry -#: hardware.xml:417 +#: hardware.xml:420 #, no-c-format msgid "Personal WorkStation 600a" msgstr "" #. Tag: entry -#: hardware.xml:421 +#: hardware.xml:424 #, no-c-format msgid "Personal WorkStation 600au" msgstr "" #. Tag: entry -#: hardware.xml:427 +#: hardware.xml:430 #, no-c-format msgid "MIKASA" msgstr "" #. Tag: entry -#: hardware.xml:428 +#: hardware.xml:431 #, no-c-format msgid "AlphaServer 1000 4/200" msgstr "" #. Tag: entry -#: hardware.xml:429 +#: hardware.xml:432 #, no-c-format msgid "Mikasa" msgstr "" #. Tag: entry -#: hardware.xml:430 hardware.xml:434 hardware.xml:438 hardware.xml:442 +#: hardware.xml:433 hardware.xml:437 hardware.xml:441 hardware.xml:445 #, no-c-format msgid "mikasa" msgstr "" #. Tag: entry -#: hardware.xml:432 +#: hardware.xml:435 #, no-c-format msgid "AlphaServer 1000 4/233..266" msgstr "" #. Tag: entry -#: hardware.xml:433 +#: hardware.xml:436 #, no-c-format msgid "Mikasa+" msgstr "" #. Tag: entry -#: hardware.xml:436 hardware.xml:440 +#: hardware.xml:439 hardware.xml:443 #, no-c-format msgid "AlphaServer 1000 5/300" msgstr "" #. Tag: entry -#: hardware.xml:437 +#: hardware.xml:440 #, no-c-format msgid "Mikasa-Pinnacle" msgstr "" #. Tag: entry -#: hardware.xml:441 +#: hardware.xml:444 #, no-c-format msgid "Mikasa-Primo" msgstr "" #. Tag: entry -#: hardware.xml:446 +#: hardware.xml:449 #, no-c-format msgid "NAUTILUS" msgstr "" #. Tag: entry -#: hardware.xml:447 +#: hardware.xml:450 #, no-c-format msgid "UP1000" msgstr "" #. Tag: entry -#: hardware.xml:448 +#: hardware.xml:451 #, no-c-format msgid "Nautilus" msgstr "" #. Tag: entry -#: hardware.xml:451 +#: hardware.xml:454 #, no-c-format msgid "UP1100" msgstr "" #. Tag: entry -#: hardware.xml:452 +#: hardware.xml:455 #, no-c-format msgid "Galaxy-Train/Nautilus Jr." msgstr "" #. Tag: entry -#: hardware.xml:457 +#: hardware.xml:460 #, no-c-format msgid "NONAME" msgstr "" #. Tag: entry -#: hardware.xml:458 +#: hardware.xml:461 #, no-c-format msgid "AXPpci33" msgstr "" #. Tag: entry -#: hardware.xml:459 +#: hardware.xml:462 #, no-c-format msgid "Noname" msgstr "" #. Tag: entry -#: hardware.xml:460 hardware.xml:464 +#: hardware.xml:463 hardware.xml:467 #, no-c-format msgid "noname" msgstr "" #. Tag: entry -#: hardware.xml:462 +#: hardware.xml:465 #, no-c-format msgid "<entry>UDB</entry>" msgstr "" #. Tag: entry -#: hardware.xml:463 +#: hardware.xml:466 #, no-c-format msgid "Multia" msgstr "" #. Tag: entry -#: hardware.xml:468 +#: hardware.xml:471 #, no-c-format msgid "NORITAKE" msgstr "" #. Tag: entry -#: hardware.xml:469 +#: hardware.xml:472 #, no-c-format msgid "AlphaServer 1000A 4/233...266" msgstr "" #. Tag: entry -#: hardware.xml:470 +#: hardware.xml:473 #, no-c-format msgid "Noritake" msgstr "" #. Tag: entry -#: hardware.xml:473 +#: hardware.xml:476 #, no-c-format msgid "AlphaServer 1000A 5/300" msgstr "" #. Tag: entry -#: hardware.xml:474 +#: hardware.xml:477 #, no-c-format msgid "Noritake-Pinnacle" msgstr "" #. Tag: entry -#: hardware.xml:477 +#: hardware.xml:480 #, no-c-format msgid "AlphaServer 1000A 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:478 +#: hardware.xml:481 #, no-c-format msgid "Noritake-Primo" msgstr "" #. Tag: entry -#: hardware.xml:481 +#: hardware.xml:484 #, no-c-format msgid "AlphaServer 800 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:482 hardware.xml:490 hardware.xml:494 +#: hardware.xml:485 hardware.xml:493 hardware.xml:497 #, no-c-format msgid "Corelle" msgstr "" #. Tag: entry -#: hardware.xml:485 +#: hardware.xml:488 #, no-c-format msgid "AlphaStation 600 A" msgstr "" #. Tag: entry -#: hardware.xml:486 +#: hardware.xml:489 #, no-c-format msgid "Alcor-Primo" msgstr "" #. Tag: entry -#: hardware.xml:489 +#: hardware.xml:492 #, no-c-format msgid "Digital Server 3300" msgstr "" #. Tag: entry -#: hardware.xml:493 +#: hardware.xml:496 #, no-c-format msgid "Digital Server 3300R" msgstr "" #. Tag: entry -#: hardware.xml:499 +#: hardware.xml:502 #, no-c-format msgid "PLATFORM 2000" msgstr "" #. Tag: entry -#: hardware.xml:500 hardware.xml:501 +#: hardware.xml:503 hardware.xml:504 #, no-c-format msgid "<entry>P2K</entry>" msgstr "" #. Tag: entry -#: hardware.xml:502 +#: hardware.xml:505 #, no-c-format msgid "<entry>p2k</entry>" msgstr "" #. Tag: entry -#: hardware.xml:506 +#: hardware.xml:509 #, no-c-format msgid "RAWHIDE" msgstr "" #. Tag: entry -#: hardware.xml:507 +#: hardware.xml:510 #, no-c-format msgid "AlphaServer 1200 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:508 hardware.xml:520 +#: hardware.xml:511 hardware.xml:523 #, no-c-format msgid "Tincup/DaVinci" msgstr "" #. Tag: entry -#: hardware.xml:511 +#: hardware.xml:514 #, no-c-format msgid "AlphaServer 4000 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:512 +#: hardware.xml:515 #, no-c-format msgid "Wrangler/Durango" msgstr "" #. Tag: entry -#: hardware.xml:515 +#: hardware.xml:518 #, no-c-format msgid "AlphaServer 4100 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:516 hardware.xml:524 +#: hardware.xml:519 hardware.xml:527 #, no-c-format msgid "Dodge" msgstr "" #. Tag: entry -#: hardware.xml:519 +#: hardware.xml:522 #, no-c-format msgid "Digital Server 5300" msgstr "" #. Tag: entry -#: hardware.xml:523 +#: hardware.xml:526 #, no-c-format msgid "Digital Server 7300" msgstr "" #. Tag: entry -#: hardware.xml:529 +#: hardware.xml:532 #, no-c-format msgid "RUFFIAN" msgstr "" #. Tag: entry -#: hardware.xml:530 +#: hardware.xml:533 #, no-c-format msgid "DeskStation AlphaPC164-UX" msgstr "" #. Tag: entry -#: hardware.xml:531 hardware.xml:535 hardware.xml:539 hardware.xml:543 hardware.xml:547 hardware.xml:551 +#: hardware.xml:534 hardware.xml:538 hardware.xml:542 hardware.xml:546 hardware.xml:550 hardware.xml:554 #, no-c-format msgid "Ruffian" msgstr "" #. Tag: entry -#: hardware.xml:532 hardware.xml:536 hardware.xml:540 hardware.xml:544 hardware.xml:548 hardware.xml:552 +#: hardware.xml:535 hardware.xml:539 hardware.xml:543 hardware.xml:547 hardware.xml:551 hardware.xml:555 #, no-c-format msgid "ruffian" msgstr "" #. Tag: entry -#: hardware.xml:534 +#: hardware.xml:537 #, no-c-format msgid "DeskStation RPL164-2" msgstr "" #. Tag: entry -#: hardware.xml:538 +#: hardware.xml:541 #, no-c-format msgid "DeskStation RPL164-4" msgstr "" #. Tag: entry -#: hardware.xml:542 +#: hardware.xml:545 #, no-c-format msgid "DeskStation RPX164-2" msgstr "" #. Tag: entry -#: hardware.xml:546 +#: hardware.xml:549 #, no-c-format msgid "DeskStation RPX164-4" msgstr "" #. Tag: entry -#: hardware.xml:550 +#: hardware.xml:553 #, no-c-format msgid "Samsung AlphaPC164-BX" msgstr "" #. Tag: entry -#: hardware.xml:556 +#: hardware.xml:559 #, no-c-format msgid "SABLE" msgstr "" #. Tag: entry -#: hardware.xml:557 +#: hardware.xml:560 #, no-c-format msgid "AlphaServer 2000 4/xxx" msgstr "" #. Tag: entry -#: hardware.xml:558 +#: hardware.xml:561 #, no-c-format msgid "Demi-Sable" msgstr "" #. Tag: entry -#: hardware.xml:561 +#: hardware.xml:564 #, no-c-format msgid "AlphaServer 2000 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:562 +#: hardware.xml:565 #, no-c-format msgid "Demi-Gamma-Sable" msgstr "" #. Tag: entry -#: hardware.xml:565 +#: hardware.xml:568 #, no-c-format msgid "AlphaServer 2100 4/xxx" msgstr "" #. Tag: entry -#: hardware.xml:566 +#: hardware.xml:569 #, no-c-format msgid "Sable" msgstr "" #. Tag: entry -#: hardware.xml:569 +#: hardware.xml:572 #, no-c-format msgid "AlphaServer 2100 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:570 +#: hardware.xml:573 #, no-c-format msgid "Gamma-Sable" msgstr "" #. Tag: entry -#: hardware.xml:575 +#: hardware.xml:578 #, no-c-format msgid "TAKARA" msgstr "" #. Tag: entry -#: hardware.xml:576 +#: hardware.xml:579 #, no-c-format msgid "21164 PICMG SBC" msgstr "" #. Tag: entry -#: hardware.xml:577 +#: hardware.xml:580 #, no-c-format msgid "Takara" msgstr "" #. Tag: entry -#: hardware.xml:578 +#: hardware.xml:581 #, no-c-format msgid "takara" msgstr "" #. Tag: entry -#: hardware.xml:582 +#: hardware.xml:585 #, no-c-format msgid "TITAN" msgstr "" #. Tag: entry -#: hardware.xml:583 +#: hardware.xml:586 #, no-c-format msgid "AlphaServer DS15" msgstr "" #. Tag: entry -#: hardware.xml:584 +#: hardware.xml:587 #, no-c-format msgid "HyperBrick2" msgstr "" #. Tag: entry -#: hardware.xml:587 +#: hardware.xml:590 #, no-c-format msgid "AlphaServer DS25" msgstr "" #. Tag: entry -#: hardware.xml:588 +#: hardware.xml:591 #, no-c-format msgid "Granite" msgstr "" #. Tag: entry -#: hardware.xml:591 +#: hardware.xml:594 #, no-c-format msgid "AlphaServer ES45" msgstr "" #. Tag: entry -#: hardware.xml:592 +#: hardware.xml:595 #, no-c-format msgid "Privateer" msgstr "" #. Tag: entry -#: hardware.xml:595 hardware.xml:634 hardware.xml:638 +#: hardware.xml:598 hardware.xml:637 hardware.xml:641 #, no-c-format msgid "UNKNOWN" msgstr "" #. Tag: entry -#: hardware.xml:596 +#: hardware.xml:599 #, no-c-format msgid "Yukon" msgstr "" #. Tag: entry -#: hardware.xml:601 +#: hardware.xml:604 #, no-c-format msgid "TSUNAMI" msgstr "" #. Tag: entry -#: hardware.xml:602 +#: hardware.xml:605 #, no-c-format msgid "AlphaServer DS10" msgstr "" #. Tag: entry -#: hardware.xml:603 hardware.xml:651 +#: hardware.xml:606 hardware.xml:654 #, no-c-format msgid "Webbrick" msgstr "" #. Tag: entry -#: hardware.xml:606 +#: hardware.xml:609 #, no-c-format msgid "AlphaServer DS10L" msgstr "" #. Tag: entry -#: hardware.xml:607 +#: hardware.xml:610 #, no-c-format msgid "Slate" msgstr "" #. Tag: entry -#: hardware.xml:610 +#: hardware.xml:613 #, no-c-format msgid "AlphaServer DS20" msgstr "" #. Tag: entry -#: hardware.xml:611 +#: hardware.xml:614 #, no-c-format msgid "Catamaran/Goldrush" msgstr "" #. Tag: entry -#: hardware.xml:614 +#: hardware.xml:617 #, no-c-format msgid "AlphaServer DS20E" msgstr "" #. Tag: entry -#: hardware.xml:615 +#: hardware.xml:618 #, no-c-format msgid "Goldrack" msgstr "" #. Tag: entry -#: hardware.xml:618 +#: hardware.xml:621 #, no-c-format msgid "AlphaServer DS20L" msgstr "" #. Tag: entry -#: hardware.xml:619 +#: hardware.xml:622 #, no-c-format msgid "Shark" msgstr "" #. Tag: entry -#: hardware.xml:622 +#: hardware.xml:625 #, no-c-format msgid "AlphaServer ES40" msgstr "" #. Tag: entry -#: hardware.xml:623 +#: hardware.xml:626 #, no-c-format msgid "Clipper" msgstr "" #. Tag: entry -#: hardware.xml:626 hardware.xml:627 +#: hardware.xml:629 hardware.xml:630 #, no-c-format msgid "DP264" msgstr "" #. Tag: entry -#: hardware.xml:630 +#: hardware.xml:633 #, no-c-format msgid "SMARTengine 21264 PCI/ISA SBC" msgstr "" #. Tag: entry -#: hardware.xml:631 +#: hardware.xml:634 #, no-c-format msgid "Eiger" msgstr "" #. Tag: entry -#: hardware.xml:635 +#: hardware.xml:638 #, no-c-format msgid "Warhol" msgstr "" #. Tag: entry -#: hardware.xml:639 +#: hardware.xml:642 #, no-c-format msgid "Windjammer" msgstr "" #. Tag: entry -#: hardware.xml:642 +#: hardware.xml:645 #, no-c-format msgid "UP2000" msgstr "" #. Tag: entry -#: hardware.xml:643 +#: hardware.xml:646 #, no-c-format msgid "Swordfish" msgstr "" #. Tag: entry -#: hardware.xml:646 +#: hardware.xml:649 #, no-c-format msgid "XP1000" msgstr "" #. Tag: entry -#: hardware.xml:647 +#: hardware.xml:650 #, no-c-format msgid "Monet/Brisbane" msgstr "" #. Tag: entry -#: hardware.xml:650 +#: hardware.xml:653 #, no-c-format msgid "XP900" msgstr "" #. Tag: entry -#: hardware.xml:656 +#: hardware.xml:659 #, no-c-format msgid "WILDFIRE" msgstr "" #. Tag: entry -#: hardware.xml:657 +#: hardware.xml:660 #, no-c-format msgid "AlphaServer GS160" msgstr "" #. Tag: entry -#: hardware.xml:658 hardware.xml:662 +#: hardware.xml:661 hardware.xml:665 #, no-c-format msgid "Wildfire" msgstr "" #. Tag: entry -#: hardware.xml:661 +#: hardware.xml:664 #, no-c-format msgid "AlphaServer GS320" msgstr "" #. Tag: entry -#: hardware.xml:667 hardware.xml:669 +#: hardware.xml:670 hardware.xml:672 #, no-c-format msgid "<entry>XL</entry>" msgstr "" #. Tag: entry -#: hardware.xml:668 +#: hardware.xml:671 #, no-c-format msgid "XL-233...266" msgstr "" #. Tag: entry -#: hardware.xml:670 +#: hardware.xml:673 #, no-c-format msgid "<entry>xl</entry>" msgstr "" #. Tag: para -#: hardware.xml:675 +#: hardware.xml:678 #, no-c-format msgid "It is believed that Debian &releasename; supports installing on all alpha sub-architectures with the exception of the ARC-only Ruffian and XL sub-architectures and the Titan subarchitecture, which requires a change to the kernel compile options." msgstr "" #. Tag: para -#: hardware.xml:691 hardware.xml:839 +#: hardware.xml:694 hardware.xml:842 #, no-c-format msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics." msgstr "" #. Tag: title -#: hardware.xml:699 hardware.xml:847 hardware.xml:1007 +#: hardware.xml:702 hardware.xml:850 hardware.xml:1010 #, no-c-format msgid "<title>CPU</title>" msgstr "" #. Tag: para -#: hardware.xml:700 +#: hardware.xml:703 #, no-c-format msgid "Both AMD64 and Intel EM64T processors are supported." msgstr "" #. Tag: para -#: hardware.xml:728 +#: hardware.xml:731 #, no-c-format msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard Debian distribution only supports installation on a number of the most common platforms. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU." msgstr "" #. Tag: para -#: hardware.xml:737 +#: hardware.xml:740 #, no-c-format msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems." msgstr "" #. Tag: para -#: hardware.xml:745 +#: hardware.xml:748 #, no-c-format msgid "The supported platforms are:" msgstr "" #. Tag: term -#: hardware.xml:752 +#: hardware.xml:755 #, no-c-format msgid "Netwinder" msgstr "" #. Tag: para -#: hardware.xml:753 +#: hardware.xml:756 #, no-c-format msgid "This is actually the name for the group of machines based upon the StrongARM 110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff)." msgstr "" #. Tag: term -#: hardware.xml:766 +#: hardware.xml:769 #, no-c-format msgid "IOP32x" msgstr "" #. Tag: para -#: hardware.xml:767 +#: hardware.xml:770 #, no-c-format msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. Debian currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. Debian explicitly supports two such devices: the GLAN Tank from IO-Data and the Thecus N2100." msgstr "" #. Tag: term -#: hardware.xml:779 +#: hardware.xml:782 #, no-c-format msgid "IXP4xx" msgstr "" #. Tag: para -#: hardware.xml:780 +#: hardware.xml:783 #, no-c-format msgid "The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected." msgstr "" #. Tag: term -#: hardware.xml:793 +#: hardware.xml:796 #, no-c-format msgid "<term>RiscPC</term>" msgstr "" #. Tag: para -#: hardware.xml:794 +#: hardware.xml:797 #, no-c-format msgid "This machine is the oldest supported hardware but support for it in our new installer is incomplete. It has RISC OS in ROM, Linux can be booted from that OS using linloader. The RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA video, parallel port, single serial port, PS/2 keyboard and proprietary mouse port. The proprietary module expansion bus allows for up to eight expansion cards to be fitted depending on configuration, several of these modules have Linux drivers." msgstr "" #. Tag: para -#: hardware.xml:820 +#: hardware.xml:823 #, no-c-format msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future." msgstr "" #. Tag: para -#: hardware.xml:848 +#: hardware.xml:851 #, no-c-format msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and new processors like the Athlon XP and Intel P4 Xeon." msgstr "" #. Tag: para -#: hardware.xml:856 +#: hardware.xml:859 #, no-c-format msgid "If your system has a 64-bit AMD64, Intel EM64T or Intel Core 2 Duo processor, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture." msgstr "" #. Tag: para -#: hardware.xml:863 +#: hardware.xml:866 #, no-c-format msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", Debian Sarge has <emphasis>dropped support</emphasis> for actual 80386 processors (and their clones), which were supported by earlier releases<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para> </footnote>." msgstr "" #. Tag: title -#: hardware.xml:900 +#: hardware.xml:903 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:901 +#: hardware.xml:904 #, no-c-format msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, the Microchannel Architecture (MCA, used in IBM's PS/2 line), or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these." msgstr "" #. Tag: para -#: hardware.xml:925 +#: hardware.xml:928 #, no-c-format msgid "Complete information concerning supported M68000 based (<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the basics." msgstr "" #. Tag: para -#: hardware.xml:932 +#: hardware.xml:935 #, no-c-format msgid "The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory Management Unit) and a FPU (floating-point unit). This includes the 68020 with an external 68851 PMMU, the 68030, and better, and excludes the <quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink> for complete details." msgstr "" #. Tag: para -#: hardware.xml:940 +#: hardware.xml:943 #, no-c-format msgid "There are four major supported <emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two systems to which Linux was ported; in keeping, they are also the two most well-supported Debian ports. The Macintosh line is supported incompletely, both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> for project status and supported hardware. The BVM and Motorola single board VMEbus computers are the most recent addition to the list of machines supported by Debian. Ports to other &architecture; architectures, such as the Sun3 architecture and NeXT black box, are underway but not yet supported by Debian." msgstr "" #. Tag: para -#: hardware.xml:967 +#: hardware.xml:970 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1008 +#: hardware.xml:1011 #, no-c-format msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the Debian installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported. The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." msgstr "" #. Tag: para -#: hardware.xml:1018 +#: hardware.xml:1021 #, no-c-format msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture." msgstr "" #. Tag: para -#: hardware.xml:1035 +#: hardware.xml:1038 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: title -#: hardware.xml:1075 +#: hardware.xml:1078 #, no-c-format msgid "CPU/Machine types" msgstr "" #. Tag: para -#: hardware.xml:1077 +#: hardware.xml:1080 #, no-c-format msgid "Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by the Debian installation system on little endian MIPS. The Debian installation system works on the following machines:" msgstr "" #. Tag: entry -#: hardware.xml:1089 +#: hardware.xml:1092 #, no-c-format msgid "System Type" msgstr "" #. Tag: entry -#: hardware.xml:1089 +#: hardware.xml:1092 #, no-c-format msgid "<entry>CPU</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1089 +#: hardware.xml:1092 #, no-c-format msgid "Code-name" msgstr "" #. Tag: entry -#: hardware.xml:1090 +#: hardware.xml:1093 #, no-c-format msgid "Debian subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1096 +#: hardware.xml:1099 #, no-c-format msgid "DECstation 5000/1xx" msgstr "" #. Tag: entry -#: hardware.xml:1097 hardware.xml:1107 hardware.xml:1112 hardware.xml:1122 +#: hardware.xml:1100 hardware.xml:1110 hardware.xml:1115 hardware.xml:1125 #, no-c-format msgid "R3000" msgstr "" #. Tag: entry -#: hardware.xml:1098 hardware.xml:1103 +#: hardware.xml:1101 hardware.xml:1106 #, no-c-format msgid "3MIN" msgstr "" #. Tag: entry -#: hardware.xml:1101 +#: hardware.xml:1104 #, no-c-format msgid "DECstation 5000/150" msgstr "" #. Tag: entry -#: hardware.xml:1102 hardware.xml:1127 +#: hardware.xml:1105 hardware.xml:1130 #, no-c-format msgid "R4000" msgstr "" #. Tag: entry -#: hardware.xml:1106 +#: hardware.xml:1109 #, no-c-format msgid "DECstation 5000/200" msgstr "" #. Tag: entry -#: hardware.xml:1108 +#: hardware.xml:1111 #, no-c-format msgid "3MAX" msgstr "" #. Tag: entry -#: hardware.xml:1111 +#: hardware.xml:1114 #, no-c-format msgid "DECstation 5000/240" msgstr "" #. Tag: entry -#: hardware.xml:1113 hardware.xml:1118 +#: hardware.xml:1116 hardware.xml:1121 #, no-c-format msgid "3MAX+" msgstr "" #. Tag: entry -#: hardware.xml:1116 +#: hardware.xml:1119 #, no-c-format msgid "DECstation 5000/260" msgstr "" #. Tag: entry -#: hardware.xml:1117 +#: hardware.xml:1120 #, no-c-format msgid "R4400" msgstr "" #. Tag: entry -#: hardware.xml:1121 +#: hardware.xml:1124 #, no-c-format msgid "Personal DECstation 5000/xx" msgstr "" #. Tag: entry -#: hardware.xml:1123 hardware.xml:1128 +#: hardware.xml:1126 hardware.xml:1131 #, no-c-format msgid "Maxine" msgstr "" #. Tag: entry -#: hardware.xml:1126 +#: hardware.xml:1129 #, no-c-format msgid "Personal DECstation 5000/50" msgstr "" #. Tag: para -#: hardware.xml:1133 +#: hardware.xml:1136 #, no-c-format msgid "All Cobalt machines are supported. In the past, only machines with a serial console were supported (that is, all machines except for the Qube 2700, aka Qube1). However, installations are now also possible through SSH." msgstr "" #. Tag: para -#: hardware.xml:1140 +#: hardware.xml:1143 #, no-c-format msgid "The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." msgstr "" #. Tag: title -#: hardware.xml:1150 +#: hardware.xml:1153 #, no-c-format msgid "Supported console options" msgstr "" #. Tag: para -#: hardware.xml:1151 +#: hardware.xml:1154 #, no-c-format msgid "A serial console is available on all supported DECstations (9600 bps, 8N1). To use the serial console, you have to boot the installer image with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter (with <replaceable>x</replaceable> being the number of the serial port you have your terminal connected to — usually <literal>2</literal>, but <literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available with the PMAG-BA and the PMAGB-B graphics options." msgstr "" #. Tag: para -#: hardware.xml:1162 +#: hardware.xml:1165 #, no-c-format msgid "" "If you have a Linux system to use as serial terminal, an easy way is to run <command>cu</command><footnote> <para> In Woody this command was part of the <classname>uucp</classname> package, but in later releases it is available as a separate package. </para> </footnote> on it. Example: <informalexample><screen>\n" @@ -1950,1280 +1968,1340 @@ msgid "" msgstr "" #. Tag: para -#: hardware.xml:1180 +#: hardware.xml:1183 #, no-c-format msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps." msgstr "" #. Tag: para -#: hardware.xml:1194 +#: hardware.xml:1197 #, no-c-format msgid "There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga Power-UP System), and CHRP machines. Each subarchitecture has its own boot methods. In addition, there are four different kernel flavours, supporting different CPU variants." msgstr "" #. Tag: para -#: hardware.xml:1202 +#: hardware.xml:1205 #, no-c-format msgid "Ports to other <emphasis>&architecture;</emphasis> architectures, such as the Be-Box and MBX architecture, are underway but not yet supported by Debian. We may have a 64-bit port in the future." msgstr "" #. Tag: title -#: hardware.xml:1210 +#: hardware.xml:1213 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:1212 +#: hardware.xml:1215 #, no-c-format msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:1219 +#: hardware.xml:1222 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:1220 +#: hardware.xml:1223 #, no-c-format msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors." msgstr "" #. Tag: term -#: hardware.xml:1230 +#: hardware.xml:1233 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:1231 +#: hardware.xml:1234 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:1235 +#: hardware.xml:1238 #, no-c-format msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270." msgstr "" #. Tag: para -#: hardware.xml:1241 +#: hardware.xml:1244 #, no-c-format msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690." msgstr "" #. Tag: para -#: hardware.xml:1246 +#: hardware.xml:1249 #, no-c-format msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour." msgstr "" #. Tag: term -#: hardware.xml:1255 +#: hardware.xml:1258 #, no-c-format msgid "<term>prep</term>" msgstr "" #. Tag: para -#: hardware.xml:1256 +#: hardware.xml:1259 #, no-c-format msgid "This kernel flavour supports the PReP subarchitecture." msgstr "" #. Tag: term -#: hardware.xml:1264 +#: hardware.xml:1267 #, no-c-format msgid "apus" msgstr "" #. Tag: para -#: hardware.xml:1265 +#: hardware.xml:1268 #, no-c-format msgid "This kernel flavour supports the Amiga Power-UP System, though it is currently disabled." msgstr "" #. Tag: title -#: hardware.xml:1278 +#: hardware.xml:1281 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:1280 +#: hardware.xml:1283 #, no-c-format msgid "Apple (and briefly a few other manufacturers — Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by Debian), OldWorld, and NewWorld." msgstr "" #. Tag: para -#: hardware.xml:1287 +#: hardware.xml:1290 #, no-c-format msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld." msgstr "" #. Tag: para -#: hardware.xml:1295 +#: hardware.xml:1298 #, no-c-format msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards." msgstr "" #. Tag: para -#: hardware.xml:1303 +#: hardware.xml:1306 #, no-c-format msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>." msgstr "" #. Tag: entry -#: hardware.xml:1319 hardware.xml:1454 hardware.xml:1498 hardware.xml:1527 +#: hardware.xml:1322 hardware.xml:1457 hardware.xml:1501 hardware.xml:1530 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:1320 +#: hardware.xml:1323 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:1326 +#: hardware.xml:1329 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:1327 +#: hardware.xml:1330 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:1328 hardware.xml:1331 hardware.xml:1334 hardware.xml:1337 hardware.xml:1340 hardware.xml:1343 hardware.xml:1346 hardware.xml:1349 hardware.xml:1352 hardware.xml:1355 hardware.xml:1358 hardware.xml:1361 hardware.xml:1364 hardware.xml:1367 hardware.xml:1370 hardware.xml:1373 +#: hardware.xml:1331 hardware.xml:1334 hardware.xml:1337 hardware.xml:1340 hardware.xml:1343 hardware.xml:1346 hardware.xml:1349 hardware.xml:1352 hardware.xml:1355 hardware.xml:1358 hardware.xml:1361 hardware.xml:1364 hardware.xml:1367 hardware.xml:1370 hardware.xml:1373 hardware.xml:1376 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:1330 +#: hardware.xml:1333 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:1333 +#: hardware.xml:1336 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:1336 +#: hardware.xml:1339 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:1339 +#: hardware.xml:1342 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:1342 +#: hardware.xml:1345 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:1345 +#: hardware.xml:1348 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:1348 +#: hardware.xml:1351 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:1351 +#: hardware.xml:1354 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:1354 +#: hardware.xml:1357 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:1357 +#: hardware.xml:1360 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:1360 +#: hardware.xml:1363 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:1363 +#: hardware.xml:1366 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:1366 +#: hardware.xml:1369 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:1369 +#: hardware.xml:1372 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:1372 +#: hardware.xml:1375 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:1375 +#: hardware.xml:1378 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:1376 hardware.xml:1379 hardware.xml:1382 hardware.xml:1385 hardware.xml:1388 hardware.xml:1391 hardware.xml:1394 hardware.xml:1397 hardware.xml:1400 hardware.xml:1403 hardware.xml:1406 hardware.xml:1409 hardware.xml:1415 hardware.xml:1418 hardware.xml:1424 hardware.xml:1430 hardware.xml:1436 +#: hardware.xml:1379 hardware.xml:1382 hardware.xml:1385 hardware.xml:1388 hardware.xml:1391 hardware.xml:1394 hardware.xml:1397 hardware.xml:1400 hardware.xml:1403 hardware.xml:1406 hardware.xml:1409 hardware.xml:1412 hardware.xml:1418 hardware.xml:1421 hardware.xml:1427 hardware.xml:1433 hardware.xml:1439 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:1378 +#: hardware.xml:1381 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:1381 +#: hardware.xml:1384 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:1384 +#: hardware.xml:1387 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:1387 +#: hardware.xml:1390 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:1390 +#: hardware.xml:1393 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:1393 +#: hardware.xml:1396 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:1396 +#: hardware.xml:1399 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:1399 +#: hardware.xml:1402 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:1402 +#: hardware.xml:1405 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:1405 +#: hardware.xml:1408 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:1408 +#: hardware.xml:1411 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:1413 +#: hardware.xml:1416 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:1414 +#: hardware.xml:1417 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:1417 +#: hardware.xml:1420 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:1422 +#: hardware.xml:1425 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:1423 +#: hardware.xml:1426 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:1428 +#: hardware.xml:1431 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1429 +#: hardware.xml:1432 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:1434 hardware.xml:1460 +#: hardware.xml:1437 hardware.xml:1463 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:1435 +#: hardware.xml:1438 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:1444 +#: hardware.xml:1447 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1461 +#: hardware.xml:1464 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:1463 +#: hardware.xml:1466 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:1465 +#: hardware.xml:1468 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:1467 +#: hardware.xml:1470 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:1469 +#: hardware.xml:1472 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:1473 hardware.xml:1504 +#: hardware.xml:1476 hardware.xml:1507 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:1474 +#: hardware.xml:1477 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:1476 +#: hardware.xml:1479 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:1478 +#: hardware.xml:1481 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:1480 +#: hardware.xml:1483 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:1488 +#: hardware.xml:1491 #, no-c-format msgid "CHRP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1505 +#: hardware.xml:1508 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:1508 +#: hardware.xml:1511 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:1509 +#: hardware.xml:1512 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: title -#: hardware.xml:1517 +#: hardware.xml:1520 #, no-c-format msgid "APUS subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1533 +#: hardware.xml:1536 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:1534 +#: hardware.xml:1537 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:1542 +#: hardware.xml:1545 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:1544 +#: hardware.xml:1547 #, no-c-format msgid "NuBus systems are not currently supported by Debian/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which Debian does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>." msgstr "" #. Tag: title -#: hardware.xml:1581 +#: hardware.xml:1584 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:1583 +#: hardware.xml:1586 #, no-c-format msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950." msgstr "" #. Tag: para -#: hardware.xml:1592 +#: hardware.xml:1595 #, no-c-format msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD." msgstr "" #. Tag: para -#: hardware.xml:1600 +#: hardware.xml:1603 #, no-c-format msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)." msgstr "" #. Tag: title -#: hardware.xml:1616 +#: hardware.xml:1619 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "" #. Tag: para -#: hardware.xml:1617 +#: hardware.xml:1620 #, no-c-format msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128.ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance." msgstr "" #. Tag: title -#: hardware.xml:1639 +#: hardware.xml:1642 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para -#: hardware.xml:1640 +#: hardware.xml:1643 #, no-c-format msgid "Sparc-based hardware is divided into a number of different subarchitectures, identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u or sun4v. The following list describes what machines they include and what level of support may be expected for each of them." msgstr "" #. Tag: term -#: hardware.xml:1651 +#: hardware.xml:1654 #, no-c-format msgid "sun4, sun4c, sun4d" msgstr "" #. Tag: para -#: hardware.xml:1653 +#: hardware.xml:1656 #, no-c-format msgid "These subarchitectures include some very old 32-bit machines, which are no longer supported. For a complete list please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>." msgstr "" #. Tag: term -#: hardware.xml:1664 +#: hardware.xml:1667 #, no-c-format -msgid "sun4m" +msgid "<term>sun4m</term>" msgstr "" #. Tag: para -#: hardware.xml:1666 +#: hardware.xml:1669 #, no-c-format msgid "sun4m is the only 32-bit subarchitecture (sparc32) that is currently supported. The most popular machines belonging to this class are Sparcstation 4, 5, 10 and 20." msgstr "" #. Tag: para -#: hardware.xml:1672 +#: hardware.xml:1675 #, no-c-format msgid "Note that symmetric multiprocessing (SMP) — the ability to run processes on multiple processors — is not supported on this hardware, due to stability problems with such configurations. The available uniprocessor (UP) sparc32 kernel will boot fine on multiprocessor machines, although it will activate and use only the first CPU." msgstr "" #. Tag: term -#: hardware.xml:1684 +#: hardware.xml:1687 #, no-c-format msgid "<term>sun4u</term>" msgstr "" #. Tag: para -#: hardware.xml:1686 +#: hardware.xml:1689 #, no-c-format msgid "This subarchitecture includes all 64-bit machines (sparc64) based on the UltraSparc processor and its clones. Most of the machines are well supported, even though for some you may experience problems booting from CD due to firmware or bootloader bugs (this problem may be worked around by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP configurations respectively." msgstr "" #. Tag: term -#: hardware.xml:1699 +#: hardware.xml:1702 #, no-c-format -msgid "sun4v" +msgid "<term>sun4v</term>" msgstr "" #. Tag: para -#: hardware.xml:1701 +#: hardware.xml:1704 #, no-c-format msgid "This is the newest addition to the Sparc family, which includes machines based on the Niagara multi-core CPUs. At the moment such CPUs are only available in T1000 and T2000 servers by Sun, and are well supported. Use the sparc64-smp kernel." msgstr "" #. Tag: para -#: hardware.xml:1712 +#: hardware.xml:1715 #, no-c-format msgid "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel." msgstr "" #. Tag: title -#: hardware.xml:1721 +#: hardware.xml:1724 #, no-c-format msgid "Graphics Card Support" msgstr "" #. Tag: para -#: hardware.xml:1722 +#: hardware.xml:1725 #, no-c-format msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document." msgstr "" #. Tag: para -#: hardware.xml:1730 +#: hardware.xml:1733 #, no-c-format msgid "Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian &release; ships with X.Org version &x11ver;." msgstr "" #. Tag: para -#: hardware.xml:1739 +#: hardware.xml:1742 #, no-c-format msgid "The X.Org X11 window system is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: para -#: hardware.xml:1748 +#: hardware.xml:1751 #, no-c-format msgid "The X.Org X11 window system is supported on some DECstation models. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: para -#: hardware.xml:1756 +#: hardware.xml:1759 #, no-c-format msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card." msgstr "" #. Tag: para -#: hardware.xml:1766 +#: hardware.xml:1769 #, no-c-format msgid "It is not uncommon for a Sparc machine to have two graphics cards in a default configuration. In such a case there is a possibility that the Linux kernel will not direct its output to the card initially used by the firmware. The lack of output on the graphical console may then be mistaken for a hang (usually the last message seen on console is 'Booting Linux...'). One possible solution is to physically remove one of the video cards; another option is to disable one of the cards using a kernel boot parameter. Also, if graphical output is not required or desired, serial console may be used as an alternative. On some systems use of serial console can be activated automatically by disconnecting the keyboard before booting the system." msgstr "" #. Tag: title -#: hardware.xml:1783 +#: hardware.xml:1786 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1784 +#: hardware.xml:1787 #, no-c-format msgid "Laptops are also supported. Laptops are often specialized or contain proprietary hardware. To see if your particular laptop works well with GNU/Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>" msgstr "" #. Tag: title -#: hardware.xml:1795 hardware.xml:1817 hardware.xml:1837 hardware.xml:1860 +#: hardware.xml:1798 hardware.xml:1820 hardware.xml:1840 hardware.xml:1863 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1796 +#: hardware.xml:1799 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with SMP support. This should not prevent installation, since the SMP kernel should boot on non-SMP systems; the kernel will simply cause a bit more overhead." msgstr "" #. Tag: para -#: hardware.xml:1804 +#: hardware.xml:1807 #, no-c-format msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" #. Tag: para -#: hardware.xml:1819 +#: hardware.xml:1822 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems." msgstr "" #. Tag: para -#: hardware.xml:1828 +#: hardware.xml:1831 #, no-c-format msgid "The 486 flavour of the Debian kernel image packages for &arch-title; is not compiled with SMP support." msgstr "" #. Tag: para -#: hardware.xml:1838 +#: hardware.xml:1841 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. However, the standard Debian &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1847 +#: hardware.xml:1850 #, no-c-format msgid "In order to take advantage of multiple processors, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" #. Tag: para -#: hardware.xml:1861 +#: hardware.xml:1864 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture, and is supported by a precompiled Debian kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1871 +#: hardware.xml:1874 #, no-c-format msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package." msgstr "" #. Tag: para -#: hardware.xml:1877 +#: hardware.xml:1880 #, no-c-format msgid "You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" #. Tag: title -#: hardware.xml:1894 +#: hardware.xml:1897 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:1896 +#: hardware.xml:1899 #, no-c-format msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used to install Debian. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section." msgstr "" #. Tag: title -#: hardware.xml:1907 +#: hardware.xml:1910 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:1908 +#: hardware.xml:1911 #, no-c-format msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive." msgstr "" #. Tag: para -#: hardware.xml:1914 +#: hardware.xml:1917 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:1921 +#: hardware.xml:1924 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:1923 +#: hardware.xml:1926 #, no-c-format msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI." msgstr "" #. Tag: para -#: hardware.xml:1930 +#: hardware.xml:1933 #, no-c-format msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>." msgstr "" #. Tag: para -#: hardware.xml:1942 +#: hardware.xml:1945 #, no-c-format msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the boot disks (such as Mitsumi and Matsushita drives). However, these models might require special boot parameters or other massaging to get them to work, and booting off these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux." msgstr "" #. Tag: para -#: hardware.xml:1952 +#: hardware.xml:1955 #, no-c-format msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" #. Tag: para -#: hardware.xml:1957 +#: hardware.xml:1960 #, no-c-format msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as the controller is supported by the SRM console. This rules out many add-on controller cards, but most integrated IDE and SCSI chips and controller cards that were provided by the manufacturer can be expected to work. To find out whether your device is supported from the SRM console, see the <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1966 +#: hardware.xml:1969 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-ROMs are also supported." msgstr "" #. Tag: para -#: hardware.xml:1971 +#: hardware.xml:1974 #, no-c-format msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card." msgstr "" #. Tag: para -#: hardware.xml:1986 +#: hardware.xml:1989 #, no-c-format msgid "On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position." msgstr "" #. Tag: para -#: hardware.xml:1995 +#: hardware.xml:1998 #, no-c-format msgid "CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal DECstation 5000/50)." msgstr "" #. Tag: para -#: hardware.xml:2004 +#: hardware.xml:2007 #, no-c-format msgid "To boot from CD, issue the command <userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware prompt, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot (3 on most DECstations) and <replaceable>id</replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" #. Tag: userinput -#: hardware.xml:2016 +#: hardware.xml:2019 #, no-c-format msgid "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=value1 param2=value2 ..." msgstr "" #. Tag: title -#: hardware.xml:2023 +#: hardware.xml:2026 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:2025 +#: hardware.xml:2028 #, no-c-format msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk." msgstr "" #. Tag: para -#: hardware.xml:2031 +#: hardware.xml:2034 #, no-c-format msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines." msgstr "" #. Tag: para -#: hardware.xml:2036 +#: hardware.xml:2039 #, no-c-format msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)." msgstr "" #. Tag: title -#: hardware.xml:2044 +#: hardware.xml:2047 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:2046 +#: hardware.xml:2049 #, no-c-format msgid "Many Debian boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives." msgstr "" #. Tag: title -#: hardware.xml:2058 +#: hardware.xml:2061 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:2060 +#: hardware.xml:2063 #, no-c-format msgid "You can also <emphasis>boot</emphasis> your system over the network. <phrase arch=\"mips\">This is the preferred installation technique for Mips.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:2066 +#: hardware.xml:2069 #, no-c-format msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." msgstr "" #. Tag: para -#: hardware.xml:2071 +#: hardware.xml:2074 #, no-c-format msgid "After the operating system kernel is installed, you can install the rest of your system via any sort of network connection (including PPP after installation of the base system), via FTP or HTTP." msgstr "" #. Tag: title -#: hardware.xml:2080 +#: hardware.xml:2083 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:2082 +#: hardware.xml:2085 #, no-c-format msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of the manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." msgstr "" #. Tag: title -#: hardware.xml:2094 +#: hardware.xml:2097 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:2096 +#: hardware.xml:2099 #, no-c-format msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware." msgstr "" #. Tag: para -#: hardware.xml:2106 +#: hardware.xml:2109 #, no-c-format msgid "Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." msgstr "" #. Tag: para -#: hardware.xml:2113 +#: hardware.xml:2116 #, no-c-format msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or ATA — are supported. Very old 8–bit hard disk controllers used in the IBM XT computer are supported only as a module. SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." msgstr "" #. Tag: para -#: hardware.xml:2123 +#: hardware.xml:2126 #, no-c-format msgid "Pretty much all storage systems supported by the Linux kernel are supported by the Debian installation system. Note that the current Linux kernel does not support floppies on the Macintosh at all, and the Debian installation system doesn't support floppies for Amigas. Also supported on the Atari is the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) file system. Amigas support the FAT file system, and HFS as a module." msgstr "" #. Tag: para -#: hardware.xml:2133 +#: hardware.xml:2136 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel." msgstr "" #. Tag: para -#: hardware.xml:2166 +#: hardware.xml:2169 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This includes both SCSI and IDE disks. Note, however, that on many systems, the SRM console is unable to boot from IDE drives, and the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;\"></ulink> for more information on booting the Jensen)" msgstr "" #. Tag: para -#: hardware.xml:2175 +#: hardware.xml:2178 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all." msgstr "" #. Tag: para -#: hardware.xml:2181 +#: hardware.xml:2184 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive." msgstr "" #. Tag: para -#: hardware.xml:2187 +#: hardware.xml:2190 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:2192 +#: hardware.xml:2195 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)." msgstr "" #. Tag: title -#: hardware.xml:2209 +#: hardware.xml:2212 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:2210 +#: hardware.xml:2213 #, no-c-format msgid "Linux supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system." msgstr "" #. Tag: para -#: hardware.xml:2216 +#: hardware.xml:2219 #, no-c-format msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)." msgstr "" #. Tag: para -#: hardware.xml:2222 +#: hardware.xml:2225 #, no-c-format msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux." msgstr "" #. Tag: para -#: hardware.xml:2228 +#: hardware.xml:2231 #, no-c-format msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP." msgstr "" #. Tag: para -#: hardware.xml:2234 +#: hardware.xml:2237 #, no-c-format msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots." msgstr "" #. Tag: para -#: hardware.xml:2240 +#: hardware.xml:2243 #, no-c-format msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." msgstr "" #. Tag: title -#: hardware.xml:2250 +#: hardware.xml:2253 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" #. Tag: para -#: hardware.xml:2252 +#: hardware.xml:2255 #, no-c-format msgid "There are several vendors, who ship systems with Debian or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux." msgstr "" #. Tag: para -#: hardware.xml:2260 +#: hardware.xml:2263 #, no-c-format msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all." msgstr "" #. Tag: para -#: hardware.xml:2265 +#: hardware.xml:2268 #, no-c-format msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that." msgstr "" #. Tag: para -#: hardware.xml:2273 +#: hardware.xml:2276 #, no-c-format msgid "Whether or not you are purchasing a system with Linux bundled, or even a used system, it is still important to check that your hardware is supported by the Linux kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a Linux system. Support Linux-friendly hardware vendors." msgstr "" #. Tag: title -#: hardware.xml:2284 +#: hardware.xml:2287 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:2285 +#: hardware.xml:2288 #, no-c-format msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the Linux source code." msgstr "" #. Tag: para -#: hardware.xml:2292 +#: hardware.xml:2295 #, no-c-format msgid "Another example is the proprietary hardware in the older Macintosh line. In fact, no specifications or documentation have ever been released for any Macintosh hardware, most notably the ADB controller (used by the mouse and keyboard), the floppy controller, and all acceleration and CLUT manipulation of the video hardware (though we do now support CLUT manipulation on nearly all internal video chips). In a nutshell, this explains why the Macintosh Linux port lags behind other Linux ports." msgstr "" #. Tag: para -#: hardware.xml:2303 +#: hardware.xml:2306 #, no-c-format msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under Linux. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market." msgstr "" #. Tag: title -#: hardware.xml:2315 +#: hardware.xml:2318 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:2316 +#: hardware.xml:2319 #, no-c-format msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence." msgstr "" #. Tag: para -#: hardware.xml:2329 +#: hardware.xml:2332 #, no-c-format msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes its being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" #. Tag: para -#: hardware.xml:2350 +#: hardware.xml:2353 #, no-c-format msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>." msgstr "" #. Tag: title -#: hardware.xml:2367 +#: hardware.xml:2370 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:2369 +#: hardware.xml:2372 #, no-c-format msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. For a minimal console-based system (all standard packages), 250MB is required. If you want to install a reasonable amount of software, including the X Window System, and some development programs and libraries, you'll need at least 400MB. For a more or less complete desktop system, you'll need a few gigabytes." msgstr "" #. Tag: para -#: hardware.xml:2378 +#: hardware.xml:2381 #, no-c-format msgid "On the Amiga the size of FastRAM is relevant towards the total memory requirements. Also, using Zorro cards with 16-bit RAM is not supported; you'll need 32-bit RAM. The <command>amiboot</command> program can be used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically." msgstr "" #. Tag: para -#: hardware.xml:2387 +#: hardware.xml:2390 #, no-c-format msgid "On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many users have reported problems running the kernel itself in Fast RAM, so the Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM." msgstr "" #. Tag: para -#: hardware.xml:2395 +#: hardware.xml:2398 #, no-c-format msgid "On the Macintosh, care should be taken on machines with RAM-based video (RBV). The RAM segment at physical address 0 is used as screen memory, making the default load position for the kernel unavailable. The alternate RAM segment used for kernel and RAMdisk must be at least 4 MB." msgstr "" #. Tag: emphasis -#: hardware.xml:2405 +#: hardware.xml:2408 #, no-c-format msgid "FIXME: is this still true?" msgstr "" #. Tag: title -#: hardware.xml:2416 +#: hardware.xml:2419 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:2418 +#: hardware.xml:2420 #, no-c-format -msgid "Most PCI and many older ISA network cards are supported. Some network interface cards are not supported by most Debian installation disks, such as AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider & Koch G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) network cards are not supported by the standard installation system, but see <ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) instructions. FDDI networks are also not supported by the installation disks, both cards and protocols." +msgid "Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase> <phrase arch=\"m68k\">Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:2437 +#: hardware.xml:2432 #, no-c-format -msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;." +msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:" msgstr "" #. Tag: para -#: hardware.xml:2445 +#: hardware.xml:2438 #, no-c-format -msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details." +msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:2454 +#: hardware.xml:2443 #, no-c-format -msgid "The following network interface cards (NICs) are supported from the bootable kernel directly:" +msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:2460 +#: hardware.xml:2448 #, no-c-format -msgid "Sun LANCE" +msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:2466 +#: hardware.xml:2453 #, no-c-format -msgid "Sun Happy Meal" +msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:2474 +#: hardware.xml:2458 #, no-c-format -msgid "The following network interface cards are supported as modules. They can be enabled once the drivers are installed during the setup. However, due to the magic of OpenPROM, you still should be able to boot from these devices:" +msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:2482 +#: hardware.xml:2465 #, no-c-format -msgid "Sun BigMAC" +msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:2488 +#: hardware.xml:2470 #, no-c-format -msgid "Sun QuadEthernet" +msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:2493 +#: hardware.xml:2475 #, no-c-format -msgid "MyriCOM Gigabit Ethernet" +msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:2500 hardware.xml:2506 hardware.xml:2512 hardware.xml:2518 hardware.xml:2524 +#: hardware.xml:2480 #, no-c-format -msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module." +msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:2530 +#: hardware.xml:2489 #, no-c-format -msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work." +msgid "The following network interface cards are supported directly by the installation images for Netwinder and CATS machines:" msgstr "" #. Tag: para -#: hardware.xml:2536 +#: hardware.xml:2495 #, no-c-format -msgid "Any network interface card (NIC) supported by the Linux kernel is also be supported by the boot disks. All network drivers are compiled as modules so you need to load one first during the initial network setup. The list of supported network devices is:" +msgid "PCI-based NE2000" msgstr "" #. Tag: para -#: hardware.xml:2544 +#: hardware.xml:2500 #, no-c-format -msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" +msgid "DECchip Tulip" msgstr "" #. Tag: para -#: hardware.xml:2549 +#: hardware.xml:2507 #, no-c-format -msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" +msgid "The following network interface cards are supported directly by the installation images for RiscPCs:" msgstr "" #. Tag: para -#: hardware.xml:2554 +#: hardware.xml:2513 #, no-c-format -msgid "Inter-User Communication Vehicle (IUCV) — available for VM guests only" +msgid "Ether1" msgstr "" #. Tag: para -#: hardware.xml:2559 +#: hardware.xml:2518 #, no-c-format -msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" +msgid "Ether3" msgstr "" #. Tag: para -#: hardware.xml:2568 +#: hardware.xml:2523 #, no-c-format -msgid "The following network interface cards are supported directly by the boot disks on Netwinder and CATS machines:" +msgid "EtherH" msgstr "" #. Tag: para -#: hardware.xml:2574 +#: hardware.xml:2530 #, no-c-format -msgid "PCI-based NE2000" +msgid "If your card is mentioned in the lists above, the complete installation can be carried out from the network with no need for CD-ROMs or floppy disks." msgstr "" #. Tag: para -#: hardware.xml:2580 +#: hardware.xml:2536 #, no-c-format -msgid "DECchip Tulip" +msgid "Any other network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module; this means that you will have to install the operating system kernel and modules using some other media." msgstr "" #. Tag: para -#: hardware.xml:2587 +#: hardware.xml:2543 +#, no-c-format +msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;. Using ISDN during the installation is not supported." +msgstr "" + +#. Tag: title +#: hardware.xml:2552 #, no-c-format -msgid "The following network interface cards are supported directly by the boot disks on RiscPCs:" +msgid "Drivers Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:2593 +#: hardware.xml:2553 #, no-c-format -msgid "Ether1" +msgid "The installation system currently does not support retrieving firmware. This means that any network cards that use a driver that requires firmware to be loaded, is not supported by default." msgstr "" #. Tag: para -#: hardware.xml:2598 +#: hardware.xml:2559 #, no-c-format -msgid "Ether3" +msgid "If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually. Note that the firmware may be packaged separately from the driver and may not be available in the <quote>main</quote> section of the &debian; archive." msgstr "" #. Tag: para -#: hardware.xml:2603 +#: hardware.xml:2570 #, no-c-format -msgid "EtherH" +msgid "If the driver itself <emphasis>is</emphasis> supported, you may also be able to use the NIC during installation by copying the firmware from some medium to <filename>/usr/lib/hotplug/firmware</filename>. Don't forget to also copy the firmware to that location for the installed system before the reboot at the end of the installation." +msgstr "" + +#. Tag: title +#: hardware.xml:2582 +#, no-c-format +msgid "Wireless Network Cards" msgstr "" #. Tag: para +#: hardware.xml:2583 +#, no-c-format +msgid "Wireless NICs are in general supported as well, with one big proviso. A lot of wireless adapters require drivers that are either non-free or have not been accepted into the official Linux kernel. These NICs can generally be made to work under &debian;, but are not supported during the installation." +msgstr "" + +#. Tag: para +#: hardware.xml:2590 +#, no-c-format +msgid "If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Use the same procedure as described above for NICs that require firmware." +msgstr "" + +#. Tag: para +#: hardware.xml:2596 +#, no-c-format +msgid "In some cases the driver you need may not be available as a Debian package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>" +msgstr "" + +#. Tag: title #: hardware.xml:2610 #, no-c-format -msgid "If your card is mentioned in the lists above, the complete installation can be carried out from the network with no need for CD-ROMs or floppy disks." +msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:2616 +#: hardware.xml:2611 #, no-c-format -msgid "Any other network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module; this means that you will have to install the operating system kernel and modules using some other media." +msgid "There are a couple of issues with specific network cards that are worth mentioning here." +msgstr "" + +#. Tag: title +#: hardware.xml:2618 +#, no-c-format +msgid "Conflict between tulip and dfme drivers" +msgstr "" + +#. Tag: para +#: hardware.xml:2620 +#, no-c-format +msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly." +msgstr "" + +#. Tag: para +#: hardware.xml:2630 +#, no-c-format +msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. During the installation the solution is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>." +msgstr "" + +#. Tag: title +#: hardware.xml:2645 +#, no-c-format +msgid "Sun B100 blade" +msgstr "" + +#. Tag: para +#: hardware.xml:2647 +#, no-c-format +msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." msgstr "" diff --git a/po/pot/post-install.pot b/po/pot/post-install.pot index 22576b136..2f8c495d0 100644 --- a/po/pot/post-install.pot +++ b/po/pot/post-install.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-27 04:04+0000\n" +"POT-Creation-Date: 2006-12-29 10:24+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" @@ -153,175 +153,379 @@ msgid "A general source of information on GNU/Linux is the <ulink url=\"http://w msgstr "" #. Tag: title -#: post-install.xml:237 +#: post-install.xml:238 +#, no-c-format +msgid "Setting Up Your System To Use E-Mail" +msgstr "" + +#. Tag: para +#: post-install.xml:239 +#, no-c-format +msgid "Today, email is an important part of many people's life. As there are many options as to how to set it up, and as having it set up correctly is important for some Debian utilities, we will try to cover the basics in this section." +msgstr "" + +#. Tag: para +#: post-install.xml:246 +#, no-c-format +msgid "There are three main functions that make up an e-mail system. First there is the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user actually uses to compose and read mails. Then there is the <firstterm>Mail Transfer Agent</firstterm> (MTA) that takes care of transferring messages from one computer to another. And last there is the <firstterm>Mail Delivery Agent</firstterm> (MDA) that takes care of delivering incoming mail to the user's inbox." +msgstr "" + +#. Tag: para +#: post-install.xml:256 +#, no-c-format +msgid "These three functions can be performed by separate programs, but they can also be combined in one or two programs. It is also possible to have different programs handle these functions for different types of mail." +msgstr "" + +#. Tag: para +#: post-install.xml:262 +#, no-c-format +msgid "On Linux and Unix systems <command>mutt</command> is historically a very popular MUA. Like most traditional Linux programs it is text based. It is often used in combination with <command>exim</command> or <command>sendmail</command> as MTA and <command>procmail</command> as MDA." +msgstr "" + +#. Tag: para +#: post-install.xml:269 +#, no-c-format +msgid "With the increasing popularity of graphical desktop systems, the use of graphical e-mail programs like GNOME's <command>evolution</command>, KDE's <command>kmail</command> or Mozilla's <command>thunderbird</command> (in Debian available as <command>icedove</command><footnote> <para> The reason that <command>thunderbird</command> has been renamed to <command>icedove</command> in Debian has to do with licencing issues. Details are outside the scope of this manual. </para> </footnote>) is becoming more popular. These programs combine the function of a MUA, MTA and MDA, but can — and often are — also be used in combination with the traditional Linux tools." +msgstr "" + +#. Tag: title +#: post-install.xml:289 +#, no-c-format +msgid "Default E-Mail Configuration" +msgstr "" + +#. Tag: para +#: post-install.xml:290 +#, no-c-format +msgid "Even if you are planning to use a graphical mail program, it is important that a traditional MTA/MDA is also installed and correctly set up on your Linux system. Reason is that various utilities running on the system<footnote> <para> Examples are: <command>cron</command>, <command>quota</command>, <command>logcheck</command>, <command>aide</command>, … </para> </footnote> can send important notices by e-mail to inform the system administrator of (potential) problems or changes." +msgstr "" + +#. Tag: para +#: post-install.xml:305 +#, no-c-format +msgid "For this reason the packages <classname>exim4</classname> and <classname>mutt</classname> will be installed by default (provided you did not unselect the <quote>standard</quote> task during the installation). <classname>exim4</classname> is a combination MTA/MDA that is relatively small but very flexible. By default it will be configured to only handle e-mail local to the system itself and e-mails addressed to the system administrator (root account) will be delivered to the regular user account created during the installation<footnote> <para> The forwarding of mail for root to the regular user account is configured in <filename>/etc/aliases</filename>. If no regular user account was created, the mail will of course be delivered to the root account itself. </para> </footnote>." +msgstr "" + +#. Tag: para +#: post-install.xml:324 +#, no-c-format +msgid "When system e-mails are delivered they are added to a file in <filename>/var/mail/<replaceable>account_name</replaceable></filename>. The e-mails can be read using <command>mutt</command>." +msgstr "" + +#. Tag: title +#: post-install.xml:334 +#, no-c-format +msgid "Sending E-Mails Outside The System" +msgstr "" + +#. Tag: para +#: post-install.xml:335 +#, no-c-format +msgid "As mentioned earlier, the installed Debian system is only set up to handle e-mail local to the system, not for sending mail to others nor for receiving mail from others." +msgstr "" + +#. Tag: para +#: post-install.xml:341 +#, no-c-format +msgid "If you would like <classname>exim4</classname> to handle external e-mail, please refer to the next subsection for the basic available configuration options. Make sure to test that mail can be sent and received correctly." +msgstr "" + +#. Tag: para +#: post-install.xml:347 +#, no-c-format +msgid "If you intend to use a graphical mail program and use a mail server of your Internet Service Provider (ISP) or your company, there is not really any need to configure <classname>exim4</classname> for handling external e-mail. Just configure your favorite graphical mail program to use the correct servers to send and receive e-mail (how is outside the scope of this manual)." +msgstr "" + +#. Tag: para +#: post-install.xml:356 +#, no-c-format +msgid "However, in that case you may need to configure individual utilities to correctly send e-mails. One such utility is <command>reportbug</command>, a program that facilitates submitting bug reports against Debian packages. By default it expects to be able to use <classname>exim4</classname> to submit bug reports." +msgstr "" + +#. Tag: para +#: post-install.xml:364 +#, no-c-format +msgid "To correctly set up <command>reportbug</command> to use an external mail server, please run the command <command>reportbug --configure</command> and answer <quote>no</quote> to the question if an MTA is available. You will then be asked for the SMTP server to be used for submitting bug reports." +msgstr "" + +#. Tag: title +#: post-install.xml:375 +#, no-c-format +msgid "Configuring the Exim4 Mail Transport Agent" +msgstr "" + +#. Tag: para +#: post-install.xml:376 +#, no-c-format +msgid "If you would like your system to also handle external e-mail, you will need to reconfigure the <classname>exim4</classname> package<footnote> <para> You can of course also remove <classname>exim4</classname> and replace it with an alternative MTA/MDA. </para> </footnote>:" +msgstr "" + +#. Tag: screen +#: post-install.xml:388 +#, no-c-format +msgid "# dpkg-reconfigure exim4-config" +msgstr "" + +#. Tag: para +#: post-install.xml:390 +#, no-c-format +msgid "After entering that command (as root), you will be asked if you want split the configuration into small files. If you are unsure, select the default option." +msgstr "" + +#. Tag: para +#: post-install.xml:396 +#, no-c-format +msgid "Next you will be presented with several common mail scenarios. Choose the one that most closely resembles your needs." +msgstr "" + +#. Tag: term +#: post-install.xml:405 +#, no-c-format +msgid "internet site" +msgstr "" + +#. Tag: para +#: post-install.xml:406 +#, no-c-format +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 "" + +#. Tag: term +#: post-install.xml:417 +#, no-c-format +msgid "mail sent by smarthost" +msgstr "" + +#. Tag: para +#: post-install.xml:418 +#, no-c-format +msgid "In this scenario your outgoing mail is forwarded to another machine, called a <quote>smarthost</quote>, which does the actual job for you. The 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." +msgstr "" + +#. Tag: para +#: post-install.xml:427 +#, no-c-format +msgid "In a lot of cases the smarthost will be your ISP's mail server, which makes this option very suitable for dial-up users. It can also be a company mail server, or even another system on your own network." +msgstr "" + +#. Tag: term +#: post-install.xml:437 +#, no-c-format +msgid "mail sent by smarthost; no local mail" +msgstr "" + +#. Tag: para +#: post-install.xml:438 +#, no-c-format +msgid "This option is basically the same as the previous one except that the system will not be set up to handle mail for a local e-mail domain. Mail on the system itself (e.g. for the system administrator) will still be handled." +msgstr "" + +#. Tag: term +#: post-install.xml:449 +#, no-c-format +msgid "local delivery only" +msgstr "" + +#. Tag: para +#: post-install.xml:450 +#, no-c-format +msgid "This is the option your system is configured for by default." +msgstr "" + +#. Tag: term +#: post-install.xml:458 +#, no-c-format +msgid "no configuration at this time" +msgstr "" + +#. Tag: para +#: post-install.xml:459 +#, no-c-format +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 "" + +#. Tag: para +#: post-install.xml:470 +#, no-c-format +msgid "If none of these scenarios suits your needs, or if you need a finer grained setup, you will need to edit configuration files under the <filename>/etc/exim4</filename> directory after the installation is complete. More information about <classname>exim4</classname> may be found under <filename>/usr/share/doc/exim4</filename>; the file <filename>README.Debian.gz</filename> has additional details about configuring <classname>exim4</classname>." +msgstr "" + +#. Tag: para +#: post-install.xml:480 +#, no-c-format +msgid "Note that sending mail directly to the Internet when you don't have an official domain name, can result in your mail being rejected because of anti-spam measures on receiving servers. Using your ISP's mail server is preferred. If you still do want to send out mail directly, you may want to use a different e-mail address than is generated by default. If you use <classname>exim4</classname> as your MTA, this is possible by adding an entry in <filename>/etc/email-addresses</filename>." +msgstr "" + +#. Tag: title +#: post-install.xml:498 #, no-c-format msgid "Compiling a New Kernel" msgstr "" #. Tag: para -#: post-install.xml:238 +#: post-install.xml:499 #, no-c-format msgid "Why would someone want to compile a new kernel? It is often not necessary since the default kernel shipped with Debian handles most configurations. Also, Debian often offers several alternative kernels. So you may want to check first if there is an alternative kernel image package that better corresponds to your hardware. However, it can be useful to compile a new kernel in order to:" msgstr "" #. Tag: para -#: post-install.xml:248 +#: post-install.xml:509 #, no-c-format msgid "handle special hardware needs, or hardware conflicts with the pre-supplied kernels" msgstr "" #. Tag: para -#: post-install.xml:254 +#: post-install.xml:515 #, no-c-format msgid "use options of the kernel which are not supported in the pre-supplied kernels (such as high memory support)" msgstr "" #. Tag: para -#: post-install.xml:260 +#: post-install.xml:521 #, no-c-format msgid "optimize the kernel by removing useless drivers to speed up boot time" msgstr "" #. Tag: para -#: post-install.xml:265 +#: post-install.xml:526 #, no-c-format msgid "create a monolithic instead of a modularized kernel" msgstr "" #. Tag: para -#: post-install.xml:270 +#: post-install.xml:531 #, no-c-format msgid "run an updated or development kernel" msgstr "" #. Tag: para -#: post-install.xml:275 +#: post-install.xml:536 #, no-c-format msgid "learn more about linux kernels" msgstr "" #. Tag: title -#: post-install.xml:284 +#: post-install.xml:545 #, no-c-format msgid "Kernel Image Management" msgstr "" #. Tag: para -#: post-install.xml:285 +#: post-install.xml:546 #, no-c-format msgid "Don't be afraid to try compiling the kernel. It's fun and profitable." msgstr "" #. Tag: para -#: post-install.xml:289 +#: post-install.xml:550 #, no-c-format msgid "To compile a kernel the Debian way, you need some packages: <classname>fakeroot</classname>, <classname>kernel-package</classname>, <classname>linux-source-2.6</classname> and a few others which are probably already installed (see <filename>/usr/share/doc/kernel-package/README.gz</filename> for the complete list)." msgstr "" #. Tag: para -#: post-install.xml:298 +#: post-install.xml:559 #, no-c-format msgid "This method will make a .deb of your kernel source, and, if you have non-standard modules, make a synchronized dependent .deb of those too. It's a better way to manage kernel images; <filename>/boot</filename> will hold the kernel, the System.map, and a log of the active config file for the build." msgstr "" #. Tag: para -#: post-install.xml:306 +#: post-install.xml:567 #, no-c-format msgid "Note that you don't <emphasis>have</emphasis> to compile your kernel the <quote>Debian way</quote>; but we find that using the packaging system to manage your kernel is actually safer and easier. In fact, you can get your kernel sources right from Linus instead of <classname>linux-source-2.6</classname>, yet still use the <classname>kernel-package</classname> compilation method." msgstr "" #. Tag: para -#: post-install.xml:315 +#: post-install.xml:576 #, no-c-format msgid "Note that you'll find complete documentation on using <classname>kernel-package</classname> under <filename>/usr/share/doc/kernel-package</filename>. This section just contains a brief tutorial." msgstr "" #. Tag: para -#: post-install.xml:322 +#: post-install.xml:583 #, no-c-format msgid "Hereafter, we'll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory<footnote> <para> There are other locations where you can extract kernel sources and build your custom kernel, but this is easiest as it does not require special permissions. </para> </footnote>. We'll also assume that your kernel version is &kernelversion;. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using <userinput>tar xjf /usr/src/linux-source-&kernelversion;.tar.bz2</userinput> and change to the directory <filename>linux-source-&kernelversion;</filename> that will have been created." msgstr "" #. Tag: para -#: post-install.xml:342 +#: post-install.xml:603 #, no-c-format msgid "Now, you can configure your kernel. Run <userinput>make xconfig</userinput> if X11 is installed, configured and being run; run <userinput>make menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</classname> installed). Take the time to read the online help and choose carefully. When in doubt, it is typically better to include the device driver (the software which manages hardware peripherals, such as Ethernet cards, SCSI controllers, and so on) you are unsure about. Be careful: other options, not related to a specific hardware, should be left at the default value if you do not understand them. Do not forget to select <quote>Kernel module loader</quote> in <quote>Loadable module support</quote> (it is not selected by default). If not included, your Debian installation will experience problems." msgstr "" #. Tag: para -#: post-install.xml:357 +#: post-install.xml:618 #, no-c-format msgid "Clean the source tree and reset the <classname>kernel-package</classname> parameters. To do that, do <userinput>make-kpkg clean</userinput>." msgstr "" #. Tag: para -#: post-install.xml:362 +#: post-install.xml:623 #, no-c-format msgid "Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image</userinput>. The version number of <quote>1.0</quote> can be changed at will; this is just a version number that you will use to track your kernel builds. Likewise, you can put any word you like in place of <quote>custom</quote> (e.g., a host name). Kernel compilation may take quite a while, depending on the power of your machine." msgstr "" #. Tag: para -#: post-install.xml:372 +#: post-install.xml:633 #, no-c-format msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <userinput>dpkg -i ../linux-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, you'll need to install that package as well." msgstr "" #. Tag: para -#: post-install.xml:392 +#: post-install.xml:653 #, no-c-format msgid "It is time to reboot the system: read carefully any warning that the above step may have produced, then <userinput>shutdown -r now</userinput>." msgstr "" #. Tag: para -#: post-install.xml:397 +#: post-install.xml:658 #, no-c-format msgid "For more information on Debian kernels and kernel compilation, see the <ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>." msgstr "" #. Tag: title -#: post-install.xml:413 +#: post-install.xml:674 #, no-c-format msgid "Recovering a Broken System" msgstr "" #. Tag: para -#: post-install.xml:414 +#: post-install.xml:675 #, no-c-format msgid "Sometimes, things go wrong, and the system you've carefully installed is no longer bootable. Perhaps the boot loader configuration broke while trying out a change, or perhaps a new kernel you installed won't boot, or perhaps cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</filename>. Regardless of the cause, you'll need to have a system to work from while you fix it, and rescue mode can be useful for this." msgstr "" #. Tag: para -#: post-install.xml:424 +#: post-install.xml:685 #, no-c-format msgid "To access rescue mode, type <userinput>rescue</userinput> at the <prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/enable=true</userinput> boot parameter. You'll be shown the first few screens of the installer, with a note in the corner of the display to indicate that this is rescue mode, not a full installation. Don't worry, your system is not about to be overwritten! Rescue mode simply takes advantage of the hardware detection facilities available in the installer to ensure that your disks, network devices, and so on are available to you while repairing your system." msgstr "" #. Tag: para -#: post-install.xml:439 +#: post-install.xml:700 #, no-c-format msgid "Instead of the partitioning tool, you should now be presented with a list of the partitions on your system, and asked to select one of them. Normally, you should select the partition containing the root file system that you need to repair. You may select partitions on RAID and LVM devices as well as those created directly on disks." msgstr "" #. Tag: para -#: post-install.xml:447 +#: post-install.xml:708 #, no-c-format msgid "If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. <phrase arch=\"x86\"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. </phrase>" msgstr "" #. Tag: para -#: post-install.xml:459 +#: post-install.xml:720 #, no-c-format msgid "If the installer cannot run a usable shell in the root file system you selected, perhaps because the file system is corrupt, then it will issue a warning and offer to give you a shell in the installer environment instead. You may not have as many tools available in this environment, but they will often be enough to repair your system anyway. The root file system you selected will be mounted on the <filename>/target</filename> directory." msgstr "" #. Tag: para -#: post-install.xml:468 +#: post-install.xml:729 #, no-c-format msgid "In either case, after you exit the shell, the system will reboot." msgstr "" #. Tag: para -#: post-install.xml:472 +#: post-install.xml:733 #, no-c-format msgid "Finally, note that repairing broken systems can be difficult, and this manual does not attempt to go into all the things that might have gone wrong or how to fix them. If you have problems, consult an expert." msgstr "" diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot index 9f0b9f47f..677802b3c 100644 --- a/po/pot/preparing.pot +++ b/po/pot/preparing.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-27 04:04+0000\n" +"POT-Creation-Date: 2006-12-29 10:24+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" @@ -1696,11 +1696,11 @@ msgstr "" #: preparing.xml:1890 #, no-c-format msgid "" - "Typically, with newer revisions, you can use OpenBoot devices such as <quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, <quote>disk</quote>, or <quote>disk2</quote>. These have the obvious meanings; the <quote>net</quote> device is for booting from the network. Additionally, the device name can specify a particular partition of a disk, such as <quote>disk2:a</quote> to boot disk2, first partition. Full OpenBoot device names have the form <informalexample> <screen>\n" + "Typically, with newer revisions, you can use OpenBoot devices such as <quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, <quote>disk</quote>, or <quote>disk2</quote>. These have the obvious meanings; the <quote>net</quote> device is for booting from the network. Additionally, the device name can specify a particular partition of a disk, such as <quote>disk2:a</quote> to boot disk2, first partition. Full OpenBoot device names have the form: <informalexample> <screen>\n" "<replaceable>driver-name</replaceable>@\n" "<replaceable>unit-address</replaceable>:\n" "<replaceable>device-arguments</replaceable>\n" - "</screen></informalexample>. In older revisions of OpenBoot, device naming is a bit different: the floppy device is called <quote>/fd</quote>, and SCSI disk devices are of the form <quote>sd(<replaceable>controller</replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in newer OpenBoot revisions is useful for viewing the currently configured devices. For full information, whatever your revision, see the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>." + "</screen></informalexample> In older revisions of OpenBoot, device naming is a bit different: the floppy device is called <quote>/fd</quote>, and SCSI disk devices are of the form <quote>sd(<replaceable>controller</replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in newer OpenBoot revisions is useful for viewing the currently configured devices. For full information, whatever your revision, see the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>." msgstr "" #. Tag: para diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index 2ae7ced4b..250a8da82 100644 --- a/po/pot/using-d-i.pot +++ b/po/pot/using-d-i.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-27 20:04+0000\n" +"POT-Creation-Date: 2006-12-29 10:24+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" @@ -657,157 +657,166 @@ msgid "Now it is time to partition your disks. If you are uncomfortable with par msgstr "" #. Tag: para -#: using-d-i.xml:777 +#: using-d-i.xml:778 +#, no-c-format +msgid "" + "If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to <quote>zero</quote> the first few sectors of the drive: <informalexample><screen>\n" + "# dd if=/dev/zero of=/dev/hd<replaceable>X</replaceable> bs=512 count=2; sync\n" + "</screen></informalexample> Note that this will make any existing data on that disk inaccessible." +msgstr "" + +#. Tag: para +#: using-d-i.xml:791 #, no-c-format msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu." msgstr "" #. Tag: para -#: using-d-i.xml:784 +#: using-d-i.xml:798 #, no-c-format msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>." msgstr "" #. Tag: para -#: using-d-i.xml:799 +#: using-d-i.xml:813 #, no-c-format msgid "The option to use (encrypted) LVM may not be available on all architectures." msgstr "" #. Tag: para -#: using-d-i.xml:804 +#: using-d-i.xml:818 #, no-c-format msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data." msgstr "" #. Tag: para -#: using-d-i.xml:813 +#: using-d-i.xml:827 #, no-c-format msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk." msgstr "" #. Tag: para -#: using-d-i.xml:822 +#: using-d-i.xml:836 #, no-c-format msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk." msgstr "" #. Tag: para -#: using-d-i.xml:832 +#: using-d-i.xml:846 #, no-c-format msgid "If you choose guided partitioning (either classic or using (encrypted) LVM) for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them." msgstr "" #. Tag: para -#: using-d-i.xml:841 +#: using-d-i.xml:855 #, no-c-format msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible." msgstr "" #. Tag: para -#: using-d-i.xml:849 +#: using-d-i.xml:863 #, no-c-format msgid "Next, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail." msgstr "" #. Tag: entry -#: using-d-i.xml:865 +#: using-d-i.xml:879 #, no-c-format msgid "Partitioning scheme" msgstr "" #. Tag: entry -#: using-d-i.xml:866 +#: using-d-i.xml:880 #, no-c-format msgid "Minimum space" msgstr "" #. Tag: entry -#: using-d-i.xml:867 +#: using-d-i.xml:881 #, no-c-format msgid "Created partitions" msgstr "" #. Tag: entry -#: using-d-i.xml:873 +#: using-d-i.xml:887 #, no-c-format msgid "All files in one partition" msgstr "" #. Tag: entry -#: using-d-i.xml:874 +#: using-d-i.xml:888 #, no-c-format msgid "600MB" msgstr "" #. Tag: entry -#: using-d-i.xml:875 +#: using-d-i.xml:889 #, no-c-format msgid "<filename>/</filename>, swap" msgstr "" #. Tag: entry -#: using-d-i.xml:877 +#: using-d-i.xml:891 #, no-c-format msgid "Separate /home partition" msgstr "" #. Tag: entry -#: using-d-i.xml:878 +#: using-d-i.xml:892 #, no-c-format msgid "500MB" msgstr "" #. Tag: entry -#: using-d-i.xml:879 +#: using-d-i.xml:893 #, no-c-format msgid "<filename>/</filename>, <filename>/home</filename>, swap" msgstr "" #. Tag: entry -#: using-d-i.xml:883 +#: using-d-i.xml:897 #, no-c-format msgid "Separate /home, /usr, /var and /tmp partitions" msgstr "" #. Tag: entry -#: using-d-i.xml:884 +#: using-d-i.xml:898 #, no-c-format msgid "<entry>1GB</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:885 +#: using-d-i.xml:899 #, no-c-format msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap" msgstr "" #. Tag: para -#: using-d-i.xml:894 +#: using-d-i.xml:908 #, no-c-format msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, except for the swap partition, will be created inside the LVM partition." msgstr "" #. Tag: para -#: using-d-i.xml:900 +#: using-d-i.xml:914 #, no-c-format msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition." msgstr "" #. Tag: para -#: using-d-i.xml:908 +#: using-d-i.xml:922 #, no-c-format msgid "If you choose guided partitioning for your Alpha system, an additional, unformatted partition will be allocated at the beginning of your disk to reserve this space for the aboot boot loader." msgstr "" #. Tag: para -#: using-d-i.xml:914 +#: using-d-i.xml:928 #, no-c-format msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted." msgstr "" #. Tag: para -#: using-d-i.xml:920 +#: using-d-i.xml:934 #, no-c-format msgid "" "The list of partitions might look like this: <informalexample><screen>\n" @@ -830,553 +839,553 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:933 +#: using-d-i.xml:947 #, no-c-format msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning." msgstr "" #. Tag: para -#: using-d-i.xml:943 +#: using-d-i.xml:957 #, no-c-format msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually setup your partition table and the usage of partitions by your new Debian system will be covered in the remainder of this section." msgstr "" #. Tag: para -#: using-d-i.xml:951 +#: using-d-i.xml:965 #, no-c-format msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk." msgstr "" #. Tag: para -#: using-d-i.xml:959 +#: using-d-i.xml:973 #, no-c-format msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap, software RAID, LVM, an encrypted file system, or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose different filesystem for this partition including options to use the partition for swap, software RAID, LVM, or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen." msgstr "" #. Tag: para -#: using-d-i.xml:981 +#: using-d-i.xml:995 #, no-c-format msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen like when creating a new partition, so you can change the same settings. One thing which might not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition." msgstr "" #. Tag: para -#: using-d-i.xml:992 +#: using-d-i.xml:1006 #, no-c-format msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue." msgstr "" #. Tag: para -#: using-d-i.xml:1000 +#: using-d-i.xml:1014 #, no-c-format msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one." msgstr "" #. Tag: para -#: using-d-i.xml:1006 +#: using-d-i.xml:1020 #, no-c-format msgid "Capabilities of <command>partman</command> can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)." msgstr "" #. Tag: para -#: using-d-i.xml:1014 +#: using-d-i.xml:1028 #, no-c-format msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested." msgstr "" #. Tag: title -#: using-d-i.xml:1042 +#: using-d-i.xml:1056 #, no-c-format msgid "Configuring Multidisk Device (Software RAID)" msgstr "" #. Tag: para -#: using-d-i.xml:1043 +#: using-d-i.xml:1057 #, no-c-format msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct MD device even from partitions residing on single physical drive, but that won't bring you anything useful. </para></footnote> in your computer, you can use <command>mdcfg</command> to setup your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)." msgstr "" #. Tag: para -#: using-d-i.xml:1057 +#: using-d-i.xml:1071 #, no-c-format msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)." msgstr "" #. Tag: para -#: using-d-i.xml:1065 +#: using-d-i.xml:1079 #, no-c-format msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> </variablelist> To sum it up:" msgstr "" #. Tag: entry -#: using-d-i.xml:1143 +#: using-d-i.xml:1157 #, no-c-format msgid "Type" msgstr "" #. Tag: entry -#: using-d-i.xml:1144 +#: using-d-i.xml:1158 #, no-c-format msgid "Minimum Devices" msgstr "" #. Tag: entry -#: using-d-i.xml:1145 +#: using-d-i.xml:1159 #, no-c-format msgid "Spare Device" msgstr "" #. Tag: entry -#: using-d-i.xml:1146 +#: using-d-i.xml:1160 #, no-c-format msgid "Survives disk failure?" msgstr "" #. Tag: entry -#: using-d-i.xml:1147 +#: using-d-i.xml:1161 #, no-c-format msgid "Available Space" msgstr "" #. Tag: entry -#: using-d-i.xml:1153 +#: using-d-i.xml:1167 #, no-c-format msgid "RAID0" msgstr "" #. Tag: entry -#: using-d-i.xml:1154 using-d-i.xml:1162 +#: using-d-i.xml:1168 using-d-i.xml:1176 #, no-c-format msgid "<entry>2</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1155 using-d-i.xml:1156 +#: using-d-i.xml:1169 using-d-i.xml:1170 #, no-c-format msgid "<entry>no</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1157 +#: using-d-i.xml:1171 #, no-c-format msgid "Size of the smallest partition multiplied by number of devices in RAID" msgstr "" #. Tag: entry -#: using-d-i.xml:1161 +#: using-d-i.xml:1175 #, no-c-format msgid "RAID1" msgstr "" #. Tag: entry -#: using-d-i.xml:1163 using-d-i.xml:1171 +#: using-d-i.xml:1177 using-d-i.xml:1185 #, no-c-format msgid "optional" msgstr "" #. Tag: entry -#: using-d-i.xml:1164 using-d-i.xml:1172 +#: using-d-i.xml:1178 using-d-i.xml:1186 #, no-c-format msgid "<entry>yes</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1165 +#: using-d-i.xml:1179 #, no-c-format msgid "Size of the smallest partition in RAID" msgstr "" #. Tag: entry -#: using-d-i.xml:1169 +#: using-d-i.xml:1183 #, no-c-format msgid "RAID5" msgstr "" #. Tag: entry -#: using-d-i.xml:1170 +#: using-d-i.xml:1184 #, no-c-format msgid "<entry>3</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1173 +#: using-d-i.xml:1187 #, no-c-format msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)" msgstr "" #. Tag: para -#: using-d-i.xml:1181 +#: using-d-i.xml:1195 #, no-c-format msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>." msgstr "" #. Tag: para -#: using-d-i.xml:1186 +#: using-d-i.xml:1200 #, no-c-format msgid "To create a MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)" msgstr "" #. Tag: para -#: using-d-i.xml:1195 +#: using-d-i.xml:1209 #, no-c-format msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) filesystem. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell." msgstr "" #. Tag: para -#: using-d-i.xml:1204 +#: using-d-i.xml:1218 #, no-c-format msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected." msgstr "" #. Tag: para -#: using-d-i.xml:1217 +#: using-d-i.xml:1231 #, no-c-format msgid "RAID0 is simple — you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD." msgstr "" #. Tag: para -#: using-d-i.xml:1224 +#: using-d-i.xml:1238 #, no-c-format msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided few seconds ago. Don't worry. If you make a mistake and select different number of partitions, the &d-i; won't let you continue until you correct the issue." msgstr "" #. Tag: para -#: using-d-i.xml:1236 +#: using-d-i.xml:1250 #, no-c-format msgid "RAID5 has similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions." msgstr "" #. Tag: para -#: using-d-i.xml:1244 +#: using-d-i.xml:1258 #, no-c-format msgid "It is perfectly possible to have several types of MD at once. For example if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)." msgstr "" #. Tag: para -#: using-d-i.xml:1253 +#: using-d-i.xml:1267 #, no-c-format msgid "After you setup MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints." msgstr "" #. Tag: title -#: using-d-i.xml:1268 +#: using-d-i.xml:1282 #, no-c-format msgid "Configuring the Logical Volume Manager (LVM)" msgstr "" #. Tag: para -#: using-d-i.xml:1269 +#: using-d-i.xml:1283 #, no-c-format msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation with moving stuff around, symlinking, etc." msgstr "" #. Tag: para -#: using-d-i.xml:1277 +#: using-d-i.xml:1291 #, no-c-format msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disk (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks." msgstr "" #. Tag: para -#: using-d-i.xml:1287 +#: using-d-i.xml:1301 #, no-c-format msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk to the computer, join it with your existing volume group and then resize the logical volume which holds your <filename>/home</filename> filesystem and voila — your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>." msgstr "" #. Tag: para -#: using-d-i.xml:1298 +#: using-d-i.xml:1312 #, no-c-format msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>." msgstr "" #. Tag: para -#: using-d-i.xml:1307 +#: using-d-i.xml:1321 #, no-c-format msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:" msgstr "" #. Tag: para -#: using-d-i.xml:1318 +#: using-d-i.xml:1332 #, no-c-format msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1323 +#: using-d-i.xml:1337 #, no-c-format msgid "Create volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1326 +#: using-d-i.xml:1340 #, no-c-format msgid "Create logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1329 +#: using-d-i.xml:1343 #, no-c-format msgid "Delete volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1332 +#: using-d-i.xml:1346 #, no-c-format msgid "Delete logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1335 +#: using-d-i.xml:1349 #, no-c-format msgid "Extend volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1338 +#: using-d-i.xml:1352 #, no-c-format msgid "Reduce volume group" msgstr "" #. Tag: para -#: using-d-i.xml:1340 +#: using-d-i.xml:1354 #, no-c-format msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen" msgstr "" #. Tag: para -#: using-d-i.xml:1346 +#: using-d-i.xml:1360 #, no-c-format msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it." msgstr "" #. Tag: para -#: using-d-i.xml:1351 +#: using-d-i.xml:1365 #, no-c-format msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)." msgstr "" #. Tag: title -#: using-d-i.xml:1365 +#: using-d-i.xml:1379 #, no-c-format msgid "Configuring Encrypted Volumes" msgstr "" #. Tag: para -#: using-d-i.xml:1366 +#: using-d-i.xml:1380 #, no-c-format msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters." msgstr "" #. Tag: para -#: using-d-i.xml:1378 +#: using-d-i.xml:1392 #, no-c-format msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition." msgstr "" #. Tag: para -#: using-d-i.xml:1393 +#: using-d-i.xml:1407 #, no-c-format msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length." msgstr "" #. Tag: para -#: using-d-i.xml:1400 +#: using-d-i.xml:1414 #, no-c-format msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition." msgstr "" #. Tag: para -#: using-d-i.xml:1411 +#: using-d-i.xml:1425 #, no-c-format msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default." msgstr "" #. Tag: para -#: using-d-i.xml:1423 +#: using-d-i.xml:1437 #, no-c-format msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind." msgstr "" #. Tag: term -#: using-d-i.xml:1433 +#: using-d-i.xml:1447 #, no-c-format msgid "Encryption: <userinput>aes</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1435 +#: using-d-i.xml:1449 #, no-c-format msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century." msgstr "" #. Tag: term -#: using-d-i.xml:1453 +#: using-d-i.xml:1467 #, no-c-format msgid "Key size: <userinput>256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1455 +#: using-d-i.xml:1469 #, no-c-format msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher." msgstr "" #. Tag: term -#: using-d-i.xml:1467 +#: using-d-i.xml:1481 #, no-c-format msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1469 +#: using-d-i.xml:1483 #, no-c-format msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data." msgstr "" #. Tag: para -#: using-d-i.xml:1479 +#: using-d-i.xml:1493 #, no-c-format msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms." msgstr "" #. Tag: term -#: using-d-i.xml:1491 +#: using-d-i.xml:1505 #, no-c-format msgid "Encryption key: <userinput>Passphrase</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1493 +#: using-d-i.xml:1507 #, no-c-format msgid "Here you can choose the type of the encryption key for this partition." msgstr "" #. Tag: term -#: using-d-i.xml:1499 +#: using-d-i.xml:1513 #, no-c-format msgid "Passphrase" msgstr "" #. Tag: para -#: using-d-i.xml:1500 +#: using-d-i.xml:1514 #, no-c-format msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process." msgstr "" #. Tag: term -#: using-d-i.xml:1515 using-d-i.xml:1608 +#: using-d-i.xml:1529 using-d-i.xml:1622 #, no-c-format msgid "Random key" msgstr "" #. Tag: para -#: using-d-i.xml:1516 +#: using-d-i.xml:1530 #, no-c-format msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)" msgstr "" #. Tag: para -#: using-d-i.xml:1525 +#: using-d-i.xml:1539 #, no-c-format msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition." msgstr "" #. Tag: term -#: using-d-i.xml:1544 using-d-i.xml:1621 +#: using-d-i.xml:1558 using-d-i.xml:1635 #, no-c-format msgid "Erase data: <userinput>yes</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1546 +#: using-d-i.xml:1560 #, no-c-format msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>." msgstr "" #. Tag: para -#: using-d-i.xml:1566 +#: using-d-i.xml:1580 #, no-c-format msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:" msgstr "" #. Tag: term -#: using-d-i.xml:1575 +#: using-d-i.xml:1589 #, no-c-format msgid "Encryption: <userinput>AES256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1577 +#: using-d-i.xml:1591 #, no-c-format msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information." msgstr "" #. Tag: term -#: using-d-i.xml:1587 +#: using-d-i.xml:1601 #, no-c-format msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1589 +#: using-d-i.xml:1603 #, no-c-format msgid "Here you can select the type of the encryption key for this partition." msgstr "" #. Tag: term -#: using-d-i.xml:1595 +#: using-d-i.xml:1609 #, no-c-format msgid "Keyfile (GnuPG)" msgstr "" #. Tag: para -#: using-d-i.xml:1596 +#: using-d-i.xml:1610 #, no-c-format msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)." msgstr "" #. Tag: para -#: using-d-i.xml:1609 +#: using-d-i.xml:1623 #, no-c-format msgid "Please see the the section on random keys above." msgstr "" #. Tag: para -#: using-d-i.xml:1623 +#: using-d-i.xml:1637 #, no-c-format msgid "Please see the the section on erasing data above." msgstr "" #. Tag: para -#: using-d-i.xml:1632 +#: using-d-i.xml:1646 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1639 +#: using-d-i.xml:1653 #, no-c-format msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time." msgstr "" #. Tag: para -#: using-d-i.xml:1650 +#: using-d-i.xml:1664 #, no-c-format msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)." msgstr "" #. Tag: para -#: using-d-i.xml:1659 +#: using-d-i.xml:1673 #, no-c-format msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system." msgstr "" #. Tag: para -#: using-d-i.xml:1672 +#: using-d-i.xml:1686 #, no-c-format msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted." msgstr "" #. Tag: para -#: using-d-i.xml:1688 +#: using-d-i.xml:1702 #, no-c-format msgid "" "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n" @@ -1389,583 +1398,505 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:1701 +#: using-d-i.xml:1715 #, no-c-format msgid "One thing to note here are the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between ordinary boot process and boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:1711 +#: using-d-i.xml:1725 #, no-c-format msgid "Once you are satisfied with the partitioning scheme, continue with the installation." msgstr "" #. Tag: title -#: using-d-i.xml:1722 +#: using-d-i.xml:1736 #, no-c-format msgid "Setting up the System" msgstr "" #. Tag: para -#: using-d-i.xml:1723 +#: using-d-i.xml:1737 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:1735 +#: using-d-i.xml:1749 #, no-c-format msgid "Configuring Your Time Zone" msgstr "" #. Tag: para -#: using-d-i.xml:1737 +#: using-d-i.xml:1751 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:1753 +#: using-d-i.xml:1767 #, no-c-format msgid "Configuring the Clock" msgstr "" #. Tag: para -#: using-d-i.xml:1755 +#: using-d-i.xml:1769 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1762 +#: using-d-i.xml:1776 #, no-c-format msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"m68k;powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> <phrase arch=\"x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase>" msgstr "" #. Tag: para -#: using-d-i.xml:1773 +#: using-d-i.xml:1787 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:1789 +#: using-d-i.xml:1803 #, no-c-format msgid "Setting Up Users And Passwords" msgstr "" #. Tag: title -#: using-d-i.xml:1792 +#: using-d-i.xml:1806 #, no-c-format msgid "Set the Root Password" msgstr "" #. Tag: para -#: using-d-i.xml:1794 +#: using-d-i.xml:1808 #, no-c-format msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible." msgstr "" #. Tag: para -#: using-d-i.xml:1802 +#: using-d-i.xml:1816 #, no-c-format msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed." msgstr "" #. Tag: para -#: using-d-i.xml:1810 +#: using-d-i.xml:1824 #, no-c-format msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator." msgstr "" #. Tag: title -#: using-d-i.xml:1820 +#: using-d-i.xml:1834 #, no-c-format msgid "Create an Ordinary User" msgstr "" #. Tag: para -#: using-d-i.xml:1822 +#: using-d-i.xml:1836 #, no-c-format msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login." msgstr "" #. Tag: para -#: using-d-i.xml:1829 +#: using-d-i.xml:1843 #, no-c-format msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program — that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail — consider reading one if it is new to you." msgstr "" #. Tag: para -#: using-d-i.xml:1839 +#: using-d-i.xml:1853 #, no-c-format msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account." msgstr "" #. Tag: para -#: using-d-i.xml:1846 +#: using-d-i.xml:1860 #, no-c-format msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command." msgstr "" #. Tag: title -#: using-d-i.xml:1858 +#: using-d-i.xml:1872 #, no-c-format msgid "Installing the Base System" msgstr "" #. Tag: para -#: using-d-i.xml:1859 +#: using-d-i.xml:1873 #, no-c-format msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time." msgstr "" #. Tag: para -#: using-d-i.xml:1872 +#: using-d-i.xml:1886 #, no-c-format msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>." msgstr "" #. Tag: para -#: using-d-i.xml:1881 +#: using-d-i.xml:1895 #, no-c-format msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console." msgstr "" #. Tag: para -#: using-d-i.xml:1887 +#: using-d-i.xml:1901 #, no-c-format msgid "As part of the installation, a Linux kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels." msgstr "" #. Tag: title -#: using-d-i.xml:1899 +#: using-d-i.xml:1913 #, no-c-format msgid "Installing Additional Software" msgstr "" #. Tag: para -#: using-d-i.xml:1900 +#: using-d-i.xml:1914 #, no-c-format msgid "After the base system is installed, you have a usable but limited system. Most users will want to install additional software to the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network." msgstr "" #. Tag: title -#: using-d-i.xml:1914 +#: using-d-i.xml:1928 #, no-c-format msgid "Configuring apt" msgstr "" #. Tag: para -#: using-d-i.xml:1916 +#: using-d-i.xml:1930 #, no-c-format msgid "One of the tools used to install packages on a &debian; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management." msgstr "" #. Tag: para -#: using-d-i.xml:1942 +#: using-d-i.xml:1956 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:1958 +#: using-d-i.xml:1972 #, no-c-format msgid "Selecting and Installing Software" msgstr "" #. Tag: para -#: using-d-i.xml:1960 +#: using-d-i.xml:1974 #, no-c-format msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks." msgstr "" #. Tag: para -#: using-d-i.xml:1969 +#: using-d-i.xml:1983 #, no-c-format msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks." msgstr "" #. Tag: para -#: using-d-i.xml:1994 +#: using-d-i.xml:2008 #, no-c-format msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can un-select the tasks. You can even opt to install no tasks at all at this point." msgstr "" #. Tag: para -#: using-d-i.xml:2001 +#: using-d-i.xml:2015 #, no-c-format msgid "The <quote>Desktop environment</quote> task will install the GNOME desktop environment. The options offered by the installer currently do not allow to select a different desktop environment such as for example KDE." msgstr "" #. Tag: para -#: using-d-i.xml:2007 +#: using-d-i.xml:2021 #, no-c-format msgid "It is possible to get the installer to install KDE by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding <literal>tasks=\"standard, kde-desktop\"</literal> at the boot prompt when starting the installer. However, this will only work if the packages needed for KDE are actually available. If you are installing using a full CD image, they will need to be downloaded from a mirror as KDE packages are not included on the first full CD; installing KDE this way should work fine if you are using a DVD image or any other installation method." msgstr "" #. Tag: para -#: using-d-i.xml:2018 +#: using-d-i.xml:2032 #, no-c-format msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL server: <classname>postgresql</classname>; Web server: <classname>apache</classname>." msgstr "" #. Tag: para -#: using-d-i.xml:2030 +#: using-d-i.xml:2044 #, no-c-format -msgid "Once you've selected your tasks, select <guibutton>Ok</guibutton>. At this point, <command>aptitude</command> will install the packages that are part of the tasks you've selected." +msgid "Once you've selected your tasks, select <guibutton>OK</guibutton>. At this point, <command>aptitude</command> will install the packages that are part of the tasks you've selected." msgstr "" #. Tag: para -#: using-d-i.xml:2037 +#: using-d-i.xml:2051 #, no-c-format msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task." msgstr "" #. Tag: para -#: using-d-i.xml:2046 +#: using-d-i.xml:2060 #, no-c-format msgid "Each package you selected with <command>tasksel</command> is downloaded, unpacked and then installed in turn by the <command>apt-get</command> and <command>dpkg</command> programs. If a particular program needs more information from the user, it will prompt you during this process." msgstr "" #. Tag: title -#: using-d-i.xml:2057 -#, no-c-format -msgid "Configuring Your Mail Transport Agent" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2059 -#, no-c-format -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 "" - -#. Tag: para -#: using-d-i.xml:2067 -#, no-c-format -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 "" - -#. Tag: para -#: using-d-i.xml:2075 -#, no-c-format -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 "" - -#. Tag: term -#: using-d-i.xml:2084 -#, no-c-format -msgid "internet site" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2085 -#, no-c-format -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 "" - -#. Tag: term -#: using-d-i.xml:2096 -#, no-c-format -msgid "mail sent by smarthost" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2097 -#, no-c-format -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 "" - -#. Tag: term -#: using-d-i.xml:2110 -#, no-c-format -msgid "local delivery only" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2111 -#, no-c-format -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 "" - -#. Tag: term -#: using-d-i.xml:2124 -#, no-c-format -msgid "no configuration at this time" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2125 -#, no-c-format -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 "" - -#. Tag: para -#: using-d-i.xml:2136 -#, no-c-format -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 "" - -#. Tag: title -#: using-d-i.xml:2150 +#: using-d-i.xml:2073 #, no-c-format msgid "Making Your System Bootable" msgstr "" #. Tag: para -#: using-d-i.xml:2152 +#: using-d-i.xml:2075 #, no-c-format msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>" msgstr "" #. Tag: title -#: using-d-i.xml:2167 +#: using-d-i.xml:2090 #, no-c-format msgid "Detecting other operating systems" msgstr "" #. Tag: para -#: using-d-i.xml:2169 +#: using-d-i.xml:2092 #, no-c-format msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to Debian." msgstr "" #. Tag: para -#: using-d-i.xml:2177 +#: using-d-i.xml:2100 #, no-c-format msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information." msgstr "" #. Tag: title -#: using-d-i.xml:2195 +#: using-d-i.xml:2118 #, no-c-format msgid "Install <command>aboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2196 +#: using-d-i.xml:2119 #, no-c-format msgid "If you have booted from SRM and you select this option, the installer will write <command>aboot</command> to the first sector of the disk on which you installed Debian. Be <emphasis>very</emphasis> careful — it is <emphasis>not</emphasis> possible to boot multiple operating systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a different operating system installed on the disk where you have installed Debian, you will have to boot GNU/Linux from a floppy instead." msgstr "" #. Tag: title -#: using-d-i.xml:2216 +#: using-d-i.xml:2139 #, no-c-format msgid "<command>palo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2217 +#: using-d-i.xml:2140 #, no-c-format msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions." msgstr "" #. Tag: para -#: using-d-i.xml:2226 +#: using-d-i.xml:2149 #, no-c-format msgid "hppa FIXME ( need more info )" msgstr "" #. Tag: title -#: using-d-i.xml:2238 +#: using-d-i.xml:2161 #, no-c-format msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2240 +#: using-d-i.xml:2163 #, no-c-format msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for newbies and old hands alike." msgstr "" #. Tag: para -#: using-d-i.xml:2246 +#: using-d-i.xml:2169 #, no-c-format msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information." msgstr "" #. Tag: para -#: using-d-i.xml:2252 +#: using-d-i.xml:2175 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2266 +#: using-d-i.xml:2189 #, no-c-format msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2268 +#: using-d-i.xml:2191 #, no-c-format msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>." msgstr "" #. Tag: para -#: using-d-i.xml:2278 +#: using-d-i.xml:2201 #, no-c-format msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation." msgstr "" #. Tag: para -#: using-d-i.xml:2286 +#: using-d-i.xml:2209 #, no-c-format msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:" msgstr "" #. Tag: term -#: using-d-i.xml:2293 +#: using-d-i.xml:2216 #, no-c-format msgid "Master Boot Record (MBR)" msgstr "" #. Tag: para -#: using-d-i.xml:2293 +#: using-d-i.xml:2216 #, no-c-format msgid "This way the <command>LILO</command> will take complete control of the boot process." msgstr "" #. Tag: term -#: using-d-i.xml:2300 +#: using-d-i.xml:2223 #, no-c-format msgid "new Debian partition" msgstr "" #. Tag: para -#: using-d-i.xml:2300 +#: using-d-i.xml:2223 #, no-c-format msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new Debian partition and it will serve as a secondary boot loader." msgstr "" #. Tag: term -#: using-d-i.xml:2309 +#: using-d-i.xml:2232 #, no-c-format msgid "Other choice" msgstr "" #. Tag: para -#: using-d-i.xml:2309 +#: using-d-i.xml:2232 #, no-c-format msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use 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 "" #. Tag: para -#: using-d-i.xml:2321 +#: using-d-i.xml:2244 #, no-c-format msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record — however, this means that you'll need to use some other way to get back into Debian!" msgstr "" #. Tag: title -#: using-d-i.xml:2337 +#: using-d-i.xml:2260 #, no-c-format msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2339 +#: using-d-i.xml:2262 #, no-c-format msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to do the actual work of loading and starting the Linux kernel." msgstr "" #. Tag: para -#: using-d-i.xml:2355 +#: using-d-i.xml:2278 #, no-c-format msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem." msgstr "" #. Tag: title -#: using-d-i.xml:2367 +#: using-d-i.xml:2290 #, no-c-format msgid "Choose the correct partition!" msgstr "" #. Tag: para -#: using-d-i.xml:2369 +#: using-d-i.xml:2292 #, no-c-format msgid "The criteria for selecting a partition is that it is FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!" msgstr "" #. Tag: title -#: using-d-i.xml:2384 +#: using-d-i.xml:2307 #, no-c-format msgid "EFI Partition Contents" msgstr "" #. Tag: para -#: using-d-i.xml:2386 +#: using-d-i.xml:2309 #, no-c-format msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured." msgstr "" #. Tag: filename -#: using-d-i.xml:2408 +#: using-d-i.xml:2331 #, no-c-format msgid "elilo.conf" msgstr "" #. Tag: para -#: using-d-i.xml:2409 +#: using-d-i.xml:2332 #, no-c-format msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition." msgstr "" #. Tag: filename -#: using-d-i.xml:2418 +#: using-d-i.xml:2341 #, no-c-format msgid "elilo.efi" msgstr "" #. Tag: para -#: using-d-i.xml:2419 +#: using-d-i.xml:2342 #, no-c-format msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>Debian GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu." msgstr "" #. Tag: filename -#: using-d-i.xml:2429 +#: using-d-i.xml:2352 #, no-c-format msgid "initrd.img" msgstr "" #. Tag: para -#: using-d-i.xml:2430 +#: using-d-i.xml:2353 #, no-c-format msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>." msgstr "" #. Tag: filename -#: using-d-i.xml:2442 +#: using-d-i.xml:2365 #, no-c-format msgid "readme.txt" msgstr "" #. Tag: para -#: using-d-i.xml:2443 +#: using-d-i.xml:2366 #, no-c-format msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run." msgstr "" #. Tag: filename -#: using-d-i.xml:2453 +#: using-d-i.xml:2376 #, no-c-format msgid "vmlinuz" msgstr "" #. Tag: para -#: using-d-i.xml:2454 +#: using-d-i.xml:2377 #, no-c-format msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>." msgstr "" #. Tag: title -#: using-d-i.xml:2474 +#: using-d-i.xml:2397 #, no-c-format msgid "<command>arcboot</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2475 +#: using-d-i.xml:2398 #, no-c-format msgid "" "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n" @@ -1978,61 +1909,61 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2494 +#: using-d-i.xml:2417 #, no-c-format msgid "scsi" msgstr "" #. Tag: para -#: using-d-i.xml:2495 +#: using-d-i.xml:2418 #, no-c-format msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2503 +#: using-d-i.xml:2426 #, no-c-format msgid "disk" msgstr "" #. Tag: para -#: using-d-i.xml:2504 +#: using-d-i.xml:2427 #, no-c-format msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2512 using-d-i.xml:2581 +#: using-d-i.xml:2435 using-d-i.xml:2504 #, no-c-format msgid "partnr" msgstr "" #. Tag: para -#: using-d-i.xml:2513 +#: using-d-i.xml:2436 #, no-c-format msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2521 +#: using-d-i.xml:2444 #, no-c-format msgid "config" msgstr "" #. Tag: para -#: using-d-i.xml:2522 +#: using-d-i.xml:2445 #, no-c-format msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: title -#: using-d-i.xml:2543 +#: using-d-i.xml:2466 #, no-c-format msgid "<command>delo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2544 +#: using-d-i.xml:2467 #, no-c-format msgid "" "The boot loader on DECstations is <command>DELO</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). DELO supports different configurations which are set up in <filename>/etc/delo.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After DELO has been installed, the system can be booted from hard disk by entering <informalexample><screen>\n" @@ -2041,265 +1972,265 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2563 +#: using-d-i.xml:2486 #, no-c-format msgid "<replaceable>#</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2564 +#: using-d-i.xml:2487 #, no-c-format msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2572 +#: using-d-i.xml:2495 #, no-c-format msgid "<replaceable>id</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2573 +#: using-d-i.xml:2496 #, no-c-format msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed" msgstr "" #. Tag: para -#: using-d-i.xml:2582 +#: using-d-i.xml:2505 #, no-c-format msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2590 +#: using-d-i.xml:2513 #, no-c-format msgid "name" msgstr "" #. Tag: para -#: using-d-i.xml:2591 +#: using-d-i.xml:2514 #, no-c-format msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: para -#: using-d-i.xml:2601 +#: using-d-i.xml:2524 #, no-c-format msgid "In case <filename>/etc/delo.conf</filename> is on the first partition on the disk and the default configuration shall be booted, it is sufficient to use" msgstr "" #. Tag: screen -#: using-d-i.xml:2607 +#: using-d-i.xml:2530 #, no-c-format msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>" msgstr "" #. Tag: title -#: using-d-i.xml:2617 +#: using-d-i.xml:2540 #, no-c-format msgid "Install <command>Yaboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2618 +#: using-d-i.xml:2541 #, no-c-format msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian;." msgstr "" #. Tag: title -#: using-d-i.xml:2636 +#: using-d-i.xml:2559 #, no-c-format msgid "Install <command>Quik</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2637 +#: using-d-i.xml:2560 #, no-c-format msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones." msgstr "" #. Tag: title -#: using-d-i.xml:2653 +#: using-d-i.xml:2576 #, no-c-format msgid "<command>zipl</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2654 +#: using-d-i.xml:2577 #, no-c-format msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>." msgstr "" #. Tag: title -#: using-d-i.xml:2671 +#: using-d-i.xml:2594 #, no-c-format msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2673 +#: using-d-i.xml:2596 #, no-c-format msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install." msgstr "" #. Tag: title -#: using-d-i.xml:2698 +#: using-d-i.xml:2621 #, no-c-format msgid "Continue Without Boot Loader" msgstr "" #. Tag: para -#: using-d-i.xml:2700 +#: using-d-i.xml:2623 #, no-c-format msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader). <phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, and Amiga systems, where the original operating system must be maintained on the box and used to boot GNU/Linux.</phrase>" msgstr "" #. Tag: para -#: using-d-i.xml:2709 +#: using-d-i.xml:2632 #, no-c-format msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem." msgstr "" #. Tag: title -#: using-d-i.xml:2726 +#: using-d-i.xml:2649 #, no-c-format msgid "Finishing the Installation" msgstr "" #. Tag: para -#: using-d-i.xml:2727 +#: using-d-i.xml:2650 #, no-c-format msgid "These are the last bits to do before rebooting to your new system. It mostly consists of tidying up after the &d-i;." msgstr "" #. Tag: title -#: using-d-i.xml:2739 +#: using-d-i.xml:2662 #, no-c-format msgid "Finish the Installation and Reboot" msgstr "" #. Tag: para -#: using-d-i.xml:2741 +#: using-d-i.xml:2664 #, no-c-format msgid "This is the last step in the initial Debian installation process. You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. The installer will do any last minute tasks, and then reboot into your new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2748 +#: using-d-i.xml:2671 #, no-c-format msgid "Select the <guimenuitem>Finish the installation</guimenuitem> menu item which will halt the system because rebooting is not supported on &arch-title; in this case. You then need to IPL GNU/Linux from the DASD which you selected for the root filesystem during the first steps of the installation." msgstr "" #. Tag: title -#: using-d-i.xml:2762 +#: using-d-i.xml:2685 #, no-c-format msgid "Miscellaneous" msgstr "" #. Tag: para -#: using-d-i.xml:2763 +#: using-d-i.xml:2686 #, no-c-format msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong." msgstr "" #. Tag: title -#: using-d-i.xml:2776 +#: using-d-i.xml:2699 #, no-c-format msgid "Saving the installation logs" msgstr "" #. Tag: para -#: using-d-i.xml:2778 +#: using-d-i.xml:2701 #, no-c-format msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2785 +#: using-d-i.xml:2708 #, no-c-format msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report." msgstr "" #. Tag: title -#: using-d-i.xml:2805 +#: using-d-i.xml:2728 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "" #. Tag: para -#: using-d-i.xml:2807 +#: using-d-i.xml:2730 #, no-c-format msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to installer itself." msgstr "" #. Tag: para -#: using-d-i.xml:2825 +#: using-d-i.xml:2748 #, no-c-format msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. To get back to the installer itself, type <userinput>exit</userinput> to close the shell." msgstr "" #. Tag: para -#: using-d-i.xml:2832 +#: using-d-i.xml:2755 #, no-c-format msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history." msgstr "" #. Tag: para -#: using-d-i.xml:2841 +#: using-d-i.xml:2764 #, no-c-format msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory." msgstr "" #. Tag: para -#: using-d-i.xml:2848 +#: using-d-i.xml:2771 #, no-c-format msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging." msgstr "" #. Tag: para -#: using-d-i.xml:2854 +#: using-d-i.xml:2777 #, no-c-format msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell." msgstr "" #. Tag: title -#: using-d-i.xml:2869 +#: using-d-i.xml:2792 #, no-c-format msgid "Installation Over the Network" msgstr "" #. Tag: para -#: using-d-i.xml:2871 +#: using-d-i.xml:2794 #, no-c-format msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)" msgstr "" #. Tag: para -#: using-d-i.xml:2881 +#: using-d-i.xml:2804 #, no-c-format msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>." msgstr "" #. Tag: para -#: using-d-i.xml:2894 +#: using-d-i.xml:2817 #, no-c-format msgid "For installations on &arch-title;, this is the default method after setting up the network." msgstr "" #. Tag: para -#: using-d-i.xml:2899 +#: using-d-i.xml:2822 #, no-c-format msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the <quote>person who will continue the installation remotely</quote>." msgstr "" #. Tag: para -#: using-d-i.xml:2911 +#: using-d-i.xml:2834 #, no-c-format msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component." msgstr "" #. Tag: para -#: using-d-i.xml:2917 +#: using-d-i.xml:2840 #, no-c-format msgid "" "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n" @@ -2308,25 +2239,25 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:2934 +#: using-d-i.xml:2857 #, no-c-format msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename> and try again." msgstr "" #. Tag: para -#: using-d-i.xml:2943 +#: using-d-i.xml:2866 #, no-c-format msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells." msgstr "" #. Tag: para -#: using-d-i.xml:2953 +#: using-d-i.xml:2876 #, no-c-format msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system." msgstr "" #. Tag: para -#: using-d-i.xml:2961 +#: using-d-i.xml:2884 #, no-c-format msgid "Also, if you are running the SSH session from an X terminal, you should not resize the window as that will result in the connection being terminated." msgstr "" |