diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 1140 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 1698 | ||||
| -rw-r--r-- | po/pot/install-methods.pot | 348 | ||||
| -rw-r--r-- | po/pot/partitioning.pot | 92 | ||||
| -rw-r--r-- | po/pot/preparing.pot | 508 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 562 |
6 files changed, 1308 insertions, 3040 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 903b7fadc..e4ab1f53c 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: 2009-11-02 22:05+0000\n" +"POT-Creation-Date: 2009-11-02 22:19+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" @@ -39,563 +39,109 @@ msgid "For information on how to boot the graphical installer, see <xref linkend msgstr "" #. Tag: title -#: boot-installer.xml:38 -#, no-c-format -msgid "Alpha Console Firmware" -msgstr "" - -#. Tag: para -#: boot-installer.xml:39 -#, no-c-format -msgid "Console firmware is stored in a flash ROM and started when an Alpha system is powered up or reset. There are two different console specifications used on Alpha systems, and hence two classes of console firmware available:" -msgstr "" - -#. Tag: para -#: boot-installer.xml:49 -#, no-c-format -msgid "<emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem specification, which provides an operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems." -msgstr "" - -#. Tag: para -#: boot-installer.xml:56 -#, no-c-format -msgid "<emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the Advanced RISC Computing (ARC) specification, which provides an operating environment for Windows NT." -msgstr "" - -#. Tag: para -#: boot-installer.xml:65 -#, no-c-format -msgid "From the user's perspective, the most important difference between SRM and ARC is that the choice of console constrains the possible disk-partitioning scheme for the hard disk which you wish to boot off of." -msgstr "" - -#. Tag: para -#: boot-installer.xml:72 -#, no-c-format -msgid "ARC requires that you use an MS-DOS partition table (as created by <command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition tables are the <quote>native</quote> partition format when booting from ARC. In fact, since AlphaBIOS contains a disk partitioning utility, you may prefer to partition your disks from the firmware menus before installing Linux." -msgstr "" - -#. Tag: para -#: boot-installer.xml:81 -#, no-c-format -msgid "Conversely, SRM is <emphasis>incompatible</emphasis><footnote> <para> Specifically, the bootsector format required by the Console Subsystem Specification conflicts with the placement of the DOS partition table. </para> </footnote> with MS-DOS partition tables. Since Tru64 Unix uses the BSD disklabel format, this is the <quote>native</quote> partition format for SRM installations." -msgstr "" - -#. Tag: para -#: boot-installer.xml:94 -#, no-c-format -msgid "GNU/Linux is the only operating system on Alpha that can be booted from both console types, but &debian; &release; only supports booting on SRM-based systems. If you have an Alpha for which no version of SRM is available, if you will be dual-booting the system with Windows NT, or if your boot device requires ARC console support for BIOS initialization, you will not be able to use the &debian; &release; installer. You can still run &debian; &release; on such systems by using other install media; for instance, you can install Debian woody with MILO and upgrade." -msgstr "" - -#. Tag: para -#: boot-installer.xml:105 -#, no-c-format -msgid "Because <command>MILO</command> is not available for any of the Alpha systems currently in production (as of February 2000), and because it is no longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM firmware on your older Alpha, it is recommended that you use SRM when possible." -msgstr "" - -#. Tag: para -#: boot-installer.xml:113 -#, no-c-format -msgid "The following table summarizes available and supported system type/console combinations (see <xref linkend=\"alpha-cpus\"/> for the system type names). The word <quote>ARC</quote> below denotes any of the ARC-compliant consoles." -msgstr "" - -#. Tag: entry -#: boot-installer.xml:125 -#, no-c-format -msgid "System Type" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:126 -#, no-c-format -msgid "Console Type Supported" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:132 -#, no-c-format -msgid "alcor" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:133 boot-installer.xml:136 boot-installer.xml:142 boot-installer.xml:148 boot-installer.xml:151 boot-installer.xml:154 boot-installer.xml:157 boot-installer.xml:163 boot-installer.xml:166 boot-installer.xml:169 boot-installer.xml:178 boot-installer.xml:187 boot-installer.xml:202 boot-installer.xml:205 -#, no-c-format -msgid "ARC or SRM" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:135 -#, no-c-format -msgid "avanti" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:138 -#, no-c-format -msgid "book1" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:139 boot-installer.xml:145 boot-installer.xml:160 boot-installer.xml:172 boot-installer.xml:181 boot-installer.xml:184 boot-installer.xml:190 boot-installer.xml:196 boot-installer.xml:199 -#, no-c-format -msgid "SRM only" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:141 -#, no-c-format -msgid "cabriolet" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:144 -#, no-c-format -msgid "dp264" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:147 -#, no-c-format -msgid "eb164" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:150 -#, no-c-format -msgid "eb64p" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:153 -#, no-c-format -msgid "eb66" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:156 -#, no-c-format -msgid "eb66p" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:159 -#, no-c-format -msgid "jensen" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:162 -#, no-c-format -msgid "lx164" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:165 -#, no-c-format -msgid "miata" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:168 -#, no-c-format -msgid "mikasa" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:171 -#, no-c-format -msgid "mikasa-p" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:174 -#, no-c-format -msgid "nautilus" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:175 -#, no-c-format -msgid "ARC (see motherboard manual) or SRM" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:177 -#, no-c-format -msgid "noname" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:180 -#, no-c-format -msgid "noritake" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:183 -#, no-c-format -msgid "noritake-p" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:186 -#, no-c-format -msgid "pc164" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:189 -#, no-c-format -msgid "rawhide" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:192 -#, no-c-format -msgid "ruffian" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:193 boot-installer.xml:208 boot-installer.xml:211 -#, no-c-format -msgid "ARC only" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:195 -#, no-c-format -msgid "sable" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:198 -#, no-c-format -msgid "sable-g" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:201 -#, no-c-format -msgid "sx164" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:204 -#, no-c-format -msgid "takara" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:207 -#, no-c-format -msgid "<entry>xl</entry>" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:210 -#, no-c-format -msgid "<entry>xlt</entry>" -msgstr "" - -#. Tag: para -#: boot-installer.xml:218 -#, no-c-format -msgid "Generally, none of these consoles can boot Linux directly, so the assistance of an intermediary bootloader is required. For the SRM console, <command>aboot</command>, a small, platform-independent bootloader, is used. See the (unfortunately outdated) <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</command>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:227 -#, no-c-format -msgid "The following paragraphs are from the woody install manual, and are included here for reference; they may be useful to someone at a later date when Debian supports MILO-based installs again." -msgstr "" - -#. Tag: para -#: boot-installer.xml:233 -#, no-c-format -msgid "Generally, none of these consoles can boot Linux directly, so the assistance of an intermediary bootloader is required. There are two mainstream Linux loaders: <command>MILO</command> and <command>aboot</command>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:239 -#, no-c-format -msgid "<command>MILO</command> is itself a console, which replaces ARC or SRM in memory. <command>MILO</command> can be booted from both ARC and SRM and is the only way to bootstrap Linux from the ARC console. <command>MILO</command> is platform-specific (a different <command>MILO</command> is needed for each system type) and exist only for those systems, for which ARC support is shown in the table above. See also the (unfortunately outdated) <ulink url=\"&url-milo-howto;\">MILO HOWTO</ulink>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:249 -#, no-c-format -msgid "<command>aboot</command> is a small, platform-independent bootloader, which runs from SRM only. See the (also unfortunately outdated) <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</command>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:256 -#, no-c-format -msgid "" - "Thus, three scenarios are generally possible, depending on the system's console firmware and whether or not <command>MILO</command> is available: <informalexample><screen>\n" - "SRM -> aboot\n" - "SRM -> MILO\n" - "ARC -> MILO\n" - "</screen></informalexample> Because <command>MILO</command> is not available for any of the Alpha systems currently in production (as of February 2000), and because it is no longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM firmware on your older Alpha, it is recommended that you use SRM and <command>aboot</command> on new installations of GNU/Linux, unless you wish to dual-boot with Windows NT." -msgstr "" - -#. Tag: para -#: boot-installer.xml:271 -#, no-c-format -msgid "The majority of AlphaServers and all current server and workstation products contain both SRM and AlphaBIOS in their firmware. For <quote>half-flash</quote> machines such as the various evaluation boards, it is possible to switch from one version to another by reflashing the firmware. Also, once SRM is installed, it is possible to run ARC/AlphaBIOS from a floppy disk (using the <command>arc</command> command). For the reasons mentioned above, we recommend switching to SRM before installing &debian;." -msgstr "" - -#. Tag: para -#: boot-installer.xml:282 -#, no-c-format -msgid "As on other architectures, you should install the newest available revision of the firmware<footnote> <para> Except on Jensen, where Linux is not supported on firmware versions newer than 1.7 — see <ulink url=\"&url-jensen-howto;\"></ulink> for more information. </para> </footnote> before installing &debian;. For Alpha, firmware updates can be obtained from <ulink url=\"&url-alpha-firmware;\">Alpha Firmware Updates</ulink>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:301 boot-installer.xml:1062 boot-installer.xml:1589 boot-installer.xml:1730 boot-installer.xml:1784 boot-installer.xml:2092 boot-installer.xml:2201 -#, no-c-format -msgid "Booting with TFTP" -msgstr "" - -#. Tag: para -#: boot-installer.xml:302 -#, no-c-format -msgid "" - "In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput> prefix, and will be listed in the output of the <userinput>show dev</userinput> command, like this (edited slightly): <informalexample><screen>\n" - ">>> show dev\n" - "ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65\n" - "ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54\n" - "ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0\n" - "</screen></informalexample> You first need to set the boot protocol: <informalexample><screen>\n" - ">>> set ewa0_protocols bootp\n" - "</screen></informalexample> Then check the medium type is correct: <informalexample><screen>\n" - ">>> set ewa0_mode <replaceable>mode</replaceable>\n" - "</screen></informalexample> You can get a listing of valid modes with <userinput>>>>set ewa0_mode</userinput>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:320 -#, no-c-format -msgid "" - "Then, to boot from the first Ethernet interface, you would type: <informalexample><screen>\n" - ">>> boot ewa0 -flags \"\"\n" - "</screen></informalexample> This will boot using the default kernel parameters as included in the netboot image." -msgstr "" - -#. Tag: para -#: boot-installer.xml:329 -#, no-c-format -msgid "If you wish to use a serial console, you <emphasis>must</emphasis> pass the <userinput>console=</userinput> parameter to the kernel. This can be done using the <userinput>-flags</userinput> argument to the SRM <userinput>boot</userinput> command. The serial ports are named the same as their corresponding files in <userinput>/dev</userinput>. Also, when specifying additional kernel parameters, you must repeat certain default options that are needed by the &d-i; images. For example, to boot from <userinput>ewa0</userinput> and use a console on the first serial port, you would type:" -msgstr "" - -#. Tag: screen -#: boot-installer.xml:341 -#, no-c-format -msgid ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0"" -msgstr "" - -#. Tag: title -#: boot-installer.xml:346 -#, no-c-format -msgid "Booting from CD-ROM with the SRM Console" -msgstr "" - -#. Tag: para -#: boot-installer.xml:347 -#, no-c-format -msgid "" - "The &debian; install CDs include several preconfigured boot options for VGA and serial consoles. Type <informalexample><screen>\n" - ">>> boot xxxx -flags 0\n" - "</screen></informalexample> to boot using VGA console, where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation. To use serial console on the first serial device, type <informalexample><screen>\n" - ">>> boot xxxx -flags 1\n" - "</screen></informalexample> and for console on the second serial port, type" -msgstr "" - -#. Tag: screen -#: boot-installer.xml:362 -#, no-c-format -msgid ">>> boot xxxx -flags 2" -msgstr "" - -#. Tag: title -#: boot-installer.xml:368 -#, no-c-format -msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" -msgstr "" - -#. Tag: para -#: boot-installer.xml:369 -#, no-c-format -msgid "To boot a CD-ROM from the ARC console, find your sub-architecture code name (see <xref linkend=\"alpha-cpus\"/>), then enter <filename>\\milo\\linload.exe</filename> as the boot loader and <filename>\\milo\\<replaceable>subarch</replaceable></filename> (where <replaceable>subarch</replaceable> is the proper subarchitecture name) as the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: You need to use <filename>\\milo\\ldmilo.exe</filename> as boot loader." -msgstr "" - -#. Tag: title -#: boot-installer.xml:385 -#, no-c-format -msgid "Booting from Floppies with the SRM Console" -msgstr "" - -#. Tag: para -#: boot-installer.xml:386 -#, no-c-format -msgid "" - "At the SRM prompt (<prompt>>>></prompt>), issue the following command: <informalexample><screen>\n" - ">>> boot dva0 -flags 0\n" - "</screen></informalexample> possibly replacing <filename>dva0</filename> with the actual device name. Usually, <filename>dva0</filename> is the floppy; type <informalexample><screen>\n" - ">>> show dev\n" - "</screen></informalexample> to see the list of devices (e.g., if you want to boot from a CD). Note that if you are booting via MILO, <command>-flags</command> argument is ignored, so you can just type <command>boot dva0</command>. If everything works OK, you will eventually see the Linux kernel boot." -msgstr "" - -#. Tag: para -#: boot-installer.xml:403 -#, no-c-format -msgid "" - "If you want to specify kernel parameters when booting via <command>aboot</command>, use the following command: <informalexample><screen>\n" - ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 load_ramdisk=1 arguments\"\n" - "</screen></informalexample> (typed on one line), substituting, if necessary, the actual SRM boot device name for <filename>dva0</filename>, the Linux boot device name for <filename>fd0</filename>, and the desired kernel parameters for <filename>arguments</filename>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:415 -#, no-c-format -msgid "If you want to specify kernel parameters when booting via <command>MILO</command>, you will have to interrupt bootstrap once you get into MILO. See <xref linkend=\"booting-from-milo\"/>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:425 -#, no-c-format -msgid "Booting from Floppies with the ARC or AlphaBIOS Console" -msgstr "" - -#. Tag: para -#: boot-installer.xml:427 -#, no-c-format -msgid "In the OS Selection menu, set <command>linload.exe</command> as the boot loader, and <command>milo</command> as the OS Path. Bootstrap using the newly created entry." -msgstr "" - -#. Tag: title -#: boot-installer.xml:436 -#, no-c-format -msgid "Booting with MILO" -msgstr "" - -#. Tag: para -#: boot-installer.xml:437 -#, no-c-format -msgid "MILO contained on the bootstrap media is configured to proceed straight to Linux automatically. Should you wish to intervene, all you need is to press space during MILO countdown." -msgstr "" - -#. Tag: para -#: boot-installer.xml:443 -#, no-c-format -msgid "" - "If you want to specify all the bits explicitly (for example, to supply additional parameters), you can use a command like this: <informalexample><screen>\n" - "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->\n" - "</screen></informalexample> If you are booting from something other than a floppy, substitute <filename>fd0</filename> in the above example with the appropriate device name in Linux notation. The <command>help</command> command would give you a brief MILO command reference." -msgstr "" - -#. Tag: title -#: boot-installer.xml:462 +#: boot-installer.xml:37 #, no-c-format msgid "Booting from TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:468 boot-installer.xml:1068 boot-installer.xml:1607 boot-installer.xml:2098 boot-installer.xml:2207 +#: boot-installer.xml:43 boot-installer.xml:643 boot-installer.xml:1182 boot-installer.xml:1673 boot-installer.xml:1782 #, no-c-format msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)." msgstr "" #. Tag: para -#: boot-installer.xml:473 boot-installer.xml:1073 boot-installer.xml:1612 boot-installer.xml:2103 boot-installer.xml:2212 +#: boot-installer.xml:48 boot-installer.xml:648 boot-installer.xml:1187 boot-installer.xml:1678 boot-installer.xml:1787 #, no-c-format msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server." msgstr "" #. Tag: para -#: boot-installer.xml:478 boot-installer.xml:1078 boot-installer.xml:1617 boot-installer.xml:2108 boot-installer.xml:2217 +#: boot-installer.xml:53 boot-installer.xml:653 boot-installer.xml:1192 boot-installer.xml:1683 boot-installer.xml:1792 #, no-c-format msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:489 +#: boot-installer.xml:64 #, no-c-format msgid "Booting from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:495 boot-installer.xml:758 boot-installer.xml:1226 boot-installer.xml:1884 boot-installer.xml:2246 +#: boot-installer.xml:70 boot-installer.xml:333 boot-installer.xml:801 boot-installer.xml:1459 boot-installer.xml:1821 #, no-c-format msgid "The easiest route for most people will be to use a set of Debian CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply <phrase arch=\"x86\"> configure your system for booting off a CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert your CD, reboot, and proceed to the next chapter." msgstr "" #. Tag: para -#: boot-installer.xml:506 boot-installer.xml:769 boot-installer.xml:1237 boot-installer.xml:1895 boot-installer.xml:2257 +#: boot-installer.xml:81 boot-installer.xml:344 boot-installer.xml:812 boot-installer.xml:1470 boot-installer.xml:1832 #, no-c-format msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you." msgstr "" #. Tag: para -#: boot-installer.xml:514 boot-installer.xml:777 boot-installer.xml:1245 boot-installer.xml:1903 boot-installer.xml:2265 +#: boot-installer.xml:89 boot-installer.xml:352 boot-installer.xml:820 boot-installer.xml:1478 boot-installer.xml:1840 #, no-c-format msgid "Even if you cannot boot from CD-ROM, you can probably install the Debian system components and any packages you want from CD-ROM. Simply boot using a different media, such as floppies. When it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive." msgstr "" #. Tag: para -#: boot-installer.xml:522 boot-installer.xml:785 boot-installer.xml:1253 boot-installer.xml:1911 boot-installer.xml:2273 +#: boot-installer.xml:97 boot-installer.xml:360 boot-installer.xml:828 boot-installer.xml:1486 boot-installer.xml:1848 #, no-c-format msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:532 +#: boot-installer.xml:107 #, no-c-format msgid "Booting from Firmware" msgstr "" #. Tag: para -#: boot-installer.xml:538 +#: boot-installer.xml:113 #, no-c-format msgid "There is an increasing number of consumer devices that directly boot from a flash chip on the device. The installer can be written to flash so it will automatically start when you reboot your machines." msgstr "" #. Tag: para -#: boot-installer.xml:544 +#: boot-installer.xml:119 #, no-c-format msgid "In many cases, changing the firmware of an embedded device voids your warranty. Sometimes you are also not able to recover your device if there are problems during the flashing process. Therefore, please take care and follow the steps precisely." msgstr "" #. Tag: title -#: boot-installer.xml:555 +#: boot-installer.xml:130 #, no-c-format msgid "Booting the NSLU2" msgstr "" #. Tag: para -#: boot-installer.xml:556 +#: boot-installer.xml:131 #, no-c-format msgid "There are three ways how to put the installer firmware into flash:" msgstr "" #. Tag: title -#: boot-installer.xml:562 +#: boot-installer.xml:137 #, no-c-format msgid "Using the NSLU2 web interface" msgstr "" #. Tag: para -#: boot-installer.xml:563 +#: boot-installer.xml:138 #, no-c-format msgid "Go to the administration section and choose the menu item <literal>Upgrade</literal>. You can then browse your disk for the installer image you have previously downloaded. Then press the <literal>Start Upgrade</literal> button, confirm, wait for a few minutes and confirm again. The system will then boot straight into the installer." msgstr "" #. Tag: title -#: boot-installer.xml:574 +#: boot-installer.xml:149 #, no-c-format msgid "Via the network using Linux/Unix" msgstr "" #. Tag: para -#: boot-installer.xml:575 +#: boot-installer.xml:150 #, no-c-format msgid "" "You can use <command>upslug2</command> from any Linux or Unix machine to upgrade the machine via the network. This software is packaged for Debian. First, you have to put your NSLU2 in upgrade mode: <orderedlist> <listitem><para> Disconnect any disks and/or devices from the USB ports. </para></listitem> <listitem><para> Power off the NSLU2 </para></listitem> <listitem><para> Press and hold the reset button (accessible through the small hole on the back just above the power input). </para></listitem> <listitem><para> Press and release the power button to power on the NSLU2. </para></listitem> <listitem><para> Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset button. </para></listitem> <listitem><para> The NSLU2 ready/status LED will flash alternately red/green (there is a 1 second delay before the first green). The NSLU2 is now in upgrade mode. </para></listitem> </orderedlist> See the <ulink url=\"http://www.nslu2-linux.org/wiki/OpenSlug/UsingTheBinary\">NSLU2-Linux pages</ulink> if you have problems with this. Once your NSLU2 is in upgrade mode, you can flash the new image: <informalexample><screen>\n" @@ -604,55 +150,55 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:636 +#: boot-installer.xml:211 #, no-c-format msgid "Via the network using Windows" msgstr "" #. Tag: para -#: boot-installer.xml:637 +#: boot-installer.xml:212 #, no-c-format msgid "There is <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmware/all_router_utility.zip\">a tool</ulink> for Windows to upgrade the firmware via the network." msgstr "" #. Tag: title -#: boot-installer.xml:648 +#: boot-installer.xml:223 #, no-c-format msgid "Booting the SS4000-E" msgstr "" #. Tag: para -#: boot-installer.xml:649 +#: boot-installer.xml:224 #, no-c-format msgid "Due to limitations in the SS4000-E firmware, it unfortunately is not possible to boot the installer without the use of a serial port at this time. To boot the installer, you will need a serial nullmodem cable; a computer with a serial port<footnote id=\"arm-s4ke-port\"> <para> A USB serial converter will also work. </para> </footnote>; and a ribbon cable with a male DB9 connector at one end, and a 10-pin .1\" IDC header at the other<footnote id=\"arm-s4k-rib\"> <para> This cable is often found in older desktop machines with builtin 9-pin serial ports. </para> </footnote>." msgstr "" #. Tag: para -#: boot-installer.xml:670 +#: boot-installer.xml:245 #, no-c-format msgid "To boot the SS4000-E, first load the Debian-provided firmware image (ss4000e.pkg) through the SS4000-E's web interface (go to <quote>administration</quote>, then to <quote>firmware</quote>, and upload the image). Next, use your serial nullmodem cable and the ribbon cable to connect to the serial port of the SS4000-E, and reboot the machine. You need to use a serial terminal application to communicate with the machine; a good option on a Debian GNU/Linux is to use the <command>cu</command> program, in the package of the same name. Assuming the serial port on your computer is to be found on <filename>/dev/ttyS0</filename>, use the following command line:" msgstr "" #. Tag: screen -#: boot-installer.xml:686 +#: boot-installer.xml:261 #, no-c-format msgid "cu -lttyS0 -s115200" msgstr "" #. Tag: para -#: boot-installer.xml:688 +#: boot-installer.xml:263 #, no-c-format msgid "If using Windows, you may want to consider using the program <classname>hyperterminal</classname>. Use a baud rate of 115200, 8 bits word length, no stop bits, and one parity bit." msgstr "" #. Tag: para -#: boot-installer.xml:694 +#: boot-installer.xml:269 #, no-c-format msgid "When the machine boots, you will see the following line of output:" msgstr "" #. Tag: screen -#: boot-installer.xml:700 +#: boot-installer.xml:275 #, no-c-format msgid "" "No network interfaces found\n" @@ -662,25 +208,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:702 +#: boot-installer.xml:277 #, no-c-format msgid "At this point, hit Control-C to interrupt the boot loader<footnote id=\"arm-s4ke-sec\"> <para> Note that you have only one second to do so; if you miss this window, just powercycle the machine and try again. </para> </footnote>. This will give you the RedBoot prompt. Enter the following command:" msgstr "" #. Tag: screen -#: boot-installer.xml:717 +#: boot-installer.xml:292 #, no-c-format msgid "fconfig boot_script_data" msgstr "" #. Tag: para -#: boot-installer.xml:719 +#: boot-installer.xml:294 #, no-c-format msgid "RedBoot is now waiting for you to enter the boot script. Make sure to <emphasis>exactly</emphasis> enter the following script:" msgstr "" #. Tag: screen -#: boot-installer.xml:726 +#: boot-installer.xml:301 #, no-c-format msgid "" "fis load ramdisk.gz\n" @@ -689,79 +235,79 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:728 +#: boot-installer.xml:303 #, no-c-format msgid "Finish the script with an empty line, and enter <quote>y</quote> at the prompt to update the non-volatile configuration. Finally, use <quote>reset</quote> to restart the system, and allow it to boot normally. The installer should now come up as normal. You can either install Debian through the serial port, or use an SSH client to connect through SSH." msgstr "" #. Tag: para -#: boot-installer.xml:736 +#: boot-installer.xml:311 #, no-c-format msgid "Note that it is not necessary to update the boot script after the installation. The system will be configured to take the root device from system configuration, rather than from the kernel command line. It will not do any harm to do so anyway, however." msgstr "" #. Tag: title -#: boot-installer.xml:752 boot-installer.xml:1220 boot-installer.xml:1878 boot-installer.xml:2240 +#: boot-installer.xml:327 boot-installer.xml:795 boot-installer.xml:1453 boot-installer.xml:1815 #, no-c-format msgid "Booting from a CD-ROM" msgstr "" #. Tag: title -#: boot-installer.xml:859 +#: boot-installer.xml:434 #, no-c-format msgid "Booting from Windows" msgstr "" #. Tag: para -#: boot-installer.xml:860 +#: boot-installer.xml:435 #, no-c-format msgid "To start the installer from Windows, you must first obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:866 +#: boot-installer.xml:441 #, no-c-format msgid "If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing <command>setup.exe</command>." msgstr "" #. Tag: para -#: boot-installer.xml:874 +#: boot-installer.xml:449 #, no-c-format msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to start the &debian; installer." msgstr "" #. Tag: title -#: boot-installer.xml:914 +#: boot-installer.xml:489 #, no-c-format msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: boot-installer.xml:917 +#: boot-installer.xml:492 #, no-c-format msgid "To boot the installer from hard disk, you must first download and place the needed files as described in <xref linkend=\"boot-drive-files\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:922 +#: boot-installer.xml:497 #, no-c-format msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/&architecture;/initrd.gz</filename> file and its corresponding kernel <filename>netboot/debian-installer/&architecture;/linux</filename>. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care." msgstr "" #. Tag: para -#: boot-installer.xml:932 +#: boot-installer.xml:507 #, no-c-format msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD/DVD image, without needing the network." msgstr "" #. Tag: para -#: boot-installer.xml:941 +#: boot-installer.xml:516 #, no-c-format msgid "For <command>LILO</command>, you will need to configure two essential things in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to load the <filename>initrd.gz</filename> installer at boot time; </para></listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is a <filename>/etc/lilo.conf</filename> example:" msgstr "" #. Tag: screen -#: boot-installer.xml:962 +#: boot-installer.xml:537 #, no-c-format msgid "" "image=/boot/newinstall/vmlinuz\n" @@ -770,19 +316,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:962 +#: boot-installer.xml:537 #, no-c-format msgid "For more details, refer to the <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> and <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and reboot." msgstr "" #. Tag: para -#: boot-installer.xml:971 +#: boot-installer.xml:546 #, no-c-format msgid "The procedure for <command>GRUB</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an entry for the installer, for example (assuming <filename>/boot</filename> is on the first partition of the first disk in the system):" msgstr "" #. Tag: screen -#: boot-installer.xml:979 +#: boot-installer.xml:554 #, no-c-format msgid "" "title New Install\n" @@ -792,127 +338,133 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:981 +#: boot-installer.xml:556 #, no-c-format msgid "From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>." msgstr "" #. Tag: title -#: boot-installer.xml:990 +#: boot-installer.xml:565 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "" #. Tag: para -#: boot-installer.xml:991 +#: boot-installer.xml:566 #, no-c-format msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;." msgstr "" #. Tag: title -#: boot-installer.xml:1004 boot-installer.xml:2147 +#: boot-installer.xml:579 boot-installer.xml:1722 #, no-c-format msgid "Booting from Floppies" msgstr "" #. Tag: para -#: boot-installer.xml:1005 boot-installer.xml:2155 +#: boot-installer.xml:580 boot-installer.xml:1730 #, no-c-format msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:1012 +#: boot-installer.xml:587 #, no-c-format msgid "To boot from the installer boot floppy, place it in the primary floppy drive, shut down the system as you normally would, then turn it back on." msgstr "" #. Tag: para -#: boot-installer.xml:1018 +#: boot-installer.xml:593 #, no-c-format msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>install root=/dev/hdc</userinput> at the boot prompt." msgstr "" #. Tag: para -#: boot-installer.xml:1028 +#: boot-installer.xml:603 #, no-c-format msgid "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not properly reset the machine, so a <quote>hard</quote> reboot is recommended. If you are installing from an existing operating system (e.g., from a DOS box) you don't have a choice. Otherwise, please do a hard reboot when booting." msgstr "" #. Tag: para -#: boot-installer.xml:1037 +#: boot-installer.xml:612 #, no-c-format msgid "The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt." msgstr "" #. Tag: para -#: boot-installer.xml:1043 +#: boot-installer.xml:618 #, no-c-format msgid "Once you press &enterkey;, you should see the message <computeroutput>Loading...</computeroutput>, followed by <computeroutput>Uncompressing Linux...</computeroutput>, and then a screenfull or so of information about the hardware in your system. More information on this phase of the boot process can be found below in <xref linkend=\"kernel-msgs\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:1052 +#: boot-installer.xml:627 #, no-c-format msgid "After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched." msgstr "" +#. Tag: title +#: boot-installer.xml:637 boot-installer.xml:1164 boot-installer.xml:1305 boot-installer.xml:1359 boot-installer.xml:1667 boot-installer.xml:1776 +#, no-c-format +msgid "Booting with TFTP" +msgstr "" + #. Tag: para -#: boot-installer.xml:1086 +#: boot-installer.xml:661 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "" #. Tag: title -#: boot-installer.xml:1092 +#: boot-installer.xml:667 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "" #. Tag: para -#: boot-installer.xml:1093 +#: boot-installer.xml:668 #, no-c-format msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel</trademark> re-implementation of TFTP boot. If so, you may be able to configure your BIOS to boot from the network." msgstr "" #. Tag: title -#: boot-installer.xml:1104 +#: boot-installer.xml:679 #, no-c-format msgid "NIC with Network BootROM" msgstr "" #. Tag: para -#: boot-installer.xml:1105 +#: boot-installer.xml:680 #, no-c-format msgid "It could be that your Network Interface Card provides TFTP boot functionality." msgstr "" #. Tag: para -#: boot-installer.xml:1110 +#: boot-installer.xml:685 #, no-c-format msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document." msgstr "" #. Tag: title -#: boot-installer.xml:1118 +#: boot-installer.xml:693 #, no-c-format msgid "Etherboot" msgstr "" #. Tag: para -#: boot-installer.xml:1119 +#: boot-installer.xml:694 #, no-c-format msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" #. Tag: title -#: boot-installer.xml:1129 +#: boot-installer.xml:704 #, no-c-format msgid "The Boot Screen" msgstr "" #. Tag: para -#: boot-installer.xml:1130 +#: boot-installer.xml:705 #, no-c-format msgid "" "When the installer boots, you should be presented with a friendly graphical screen showing the Debian logo and a menu: <informalexample><screen>\n" @@ -928,25 +480,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1140 +#: boot-installer.xml:715 #, no-c-format msgid "For a normal installation, select either the <quote>Install</quote> or the <quote>Graphical install</quote> entry — using either the arrow keys on your keyboard or by typing the first (highlighted) letter — and press &enterkey; to boot the installer." msgstr "" #. Tag: para -#: boot-installer.xml:1147 +#: boot-installer.xml:722 #, no-c-format msgid "The <quote>Advanced options</quote> entry gives access to a second menu that allows to boot the installer in expert mode, in rescue mode and for automated installs." msgstr "" #. Tag: para -#: boot-installer.xml:1153 +#: boot-installer.xml:728 #, no-c-format msgid "If you wish or need to add any boot parameters for either the installer or the kernel, press &tabkey;. This will display the default boot command for the selected menu entry and allow to add additional options. The help screens (see below) list some common possible options. Press &enterkey; to boot the installer with your options; pressing &escapekey; will return you to the boot menu and undo any changes you made." msgstr "" #. Tag: para -#: boot-installer.xml:1162 +#: boot-installer.xml:737 #, no-c-format msgid "" "Choosing the <quote>Help</quote> entry will result in the first help screen being displayed which gives an overview of all available help screens. Note that it is not possible to return to the boot menu after the help screens have been displayed. However, the F3 and F4 help screens list commands that are equivalent to the boot methods listed in the menu. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>\n" @@ -955,259 +507,259 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1181 +#: boot-installer.xml:756 #, no-c-format msgid "The keyboard is assumed to have a default American English layout at this point. This means that if your keyboard has a different (language-specific) layout, the characters that appear on the screen may be different from what you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-keymap;\">schema of the US keyboard layout</ulink> which can be used as a reference to find the correct keys to use." msgstr "" #. Tag: para -#: boot-installer.xml:1191 +#: boot-installer.xml:766 #, no-c-format msgid "If you are using a system that has the BIOS configured to use serial console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot menu. The same can happen if you are installing the system via a remote management device that provides a text interface to the VGA console. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)." msgstr "" #. Tag: para -#: boot-installer.xml:1201 +#: boot-installer.xml:776 #, no-c-format msgid "To bypass the graphical boot screen you can either blindly press &escapekey; to get a text boot prompt, or (equally blindly) press <quote>H</quote> followed by &enterkey; to select the <quote>Help</quote> option described above. After that your keystrokes should be echoed at the prompt. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>fb=false</userinput> to the boot prompt, as described in the help text." msgstr "" #. Tag: title -#: boot-installer.xml:1261 +#: boot-installer.xml:836 #, no-c-format msgid "CD Contents" msgstr "" #. Tag: para -#: boot-installer.xml:1263 +#: boot-installer.xml:838 #, no-c-format msgid "There are three basic variations of Debian Install CDs. The <emphasis>Business Card</emphasis> CD has a minimal installation that will fit on the small form factor CD media. It requires a network connection in order to install the rest of the base installation and make a usable system. The <emphasis>Network Install</emphasis> CD has all of the packages for a base install but requires a network connection to a Debian mirror site in order to install the extra packages one would want for a complete system . The set of Debian CDs can install a complete system from the wide range of packages without needing access to the network." msgstr "" #. Tag: para -#: boot-installer.xml:1279 +#: boot-installer.xml:854 #, no-c-format msgid "The IA-64 architecture uses the next generation Extensible Firmware Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows little about the boot device other than the partition table and Master Boot Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted disk partitions. This simplifies the often arcane process of starting a system. The system boot loader and the EFI firmware that supports it have a full filesystem to store the files necessary for booting the machine. This means that the system disk on an IA-64 system has an additional disk partition dedicated to EFI instead of the simple MBR or boot block on more conventional systems." msgstr "" #. Tag: para -#: boot-installer.xml:1295 +#: boot-installer.xml:870 #, no-c-format msgid "The Debian Installer CD contains a small EFI partition where the <command>ELILO</command> bootloader, its configuration file, the installer's kernel, and initial filesystem (initrd) are located. The running system also contains an EFI partition where the necessary files for booting the system reside. These files are readable from the EFI Shell as described below." msgstr "" #. Tag: para -#: boot-installer.xml:1304 +#: boot-installer.xml:879 #, no-c-format msgid "Most of the details of how <command>ELILO</command> actually loads and starts a system are transparent to the system installer. However, the installer must set up an EFI partition prior to installing the base system. Otherwise, the installation of <command>ELILO</command> will fail, rendering the system un-bootable. The EFI partition is allocated and formatted in the partitioning step of the installation prior to loading any packages on the system disk. The partitioning task also verifies that a suitable EFI partition is present before allowing the installation to proceed." msgstr "" #. Tag: para -#: boot-installer.xml:1316 +#: boot-installer.xml:891 #, no-c-format msgid "The EFI Boot Manager is presented as the last step of the firmware initialization. It displays a menu list from which the user can select an option. Depending on the model of system and what other software has been loaded on the system, this menu may be different from one system to another. There should be at least two menu items displayed, <command>Boot Option Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. Using the first option is preferred, however, if that option is not available or the CD for some reason does not boot with it, use the second option." msgstr "" #. Tag: title -#: boot-installer.xml:1335 +#: boot-installer.xml:910 #, no-c-format msgid "IMPORTANT" msgstr "" #. Tag: para -#: boot-installer.xml:1336 +#: boot-installer.xml:911 #, no-c-format msgid "The EFI Boot Manager will select a default boot action, typically the first menu choice, within a pre-set number of seconds. This is indicated by a countdown at the bottom of the screen. Once the timer expires and the systems starts the default action, you may have to reboot the machine in order to continue the installation. If the default action is the EFI Shell, you can return to the Boot Manager by running <command>exit</command> at the shell prompt." msgstr "" #. Tag: title -#: boot-installer.xml:1348 +#: boot-installer.xml:923 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "" #. Tag: para -#: boot-installer.xml:1355 +#: boot-installer.xml:930 #, no-c-format msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes its system initialization." msgstr "" #. Tag: para -#: boot-installer.xml:1361 +#: boot-installer.xml:936 #, no-c-format msgid "Select <command>Boot Maintenance Menu</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a new menu." msgstr "" #. Tag: para -#: boot-installer.xml:1367 +#: boot-installer.xml:942 #, no-c-format msgid "Select <command>Boot From a File</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a list of devices probed by the firmware. You should see two menu lines containing either the label <command>Debian Inst [Acpi ...</command> or <command>Removable Media Boot</command>. If you examine the rest of the menu line, you will notice that the device and controller information should be the same." msgstr "" #. Tag: para -#: boot-installer.xml:1378 +#: boot-installer.xml:953 #, no-c-format msgid "You can choose either of the entries that refer to the CD/DVD drive. Select your choice with the arrow keys and press <command>ENTER</command>. If you choose <command>Removable Media Boot</command> the machine will immediately start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</command> instead, it will display a directory listing of the bootable portion of the CD, requiring you to proceed to the next (additional) step." msgstr "" #. Tag: para -#: boot-installer.xml:1389 +#: boot-installer.xml:964 #, no-c-format msgid "You will only need this step if you chose <command>Debian Inst [Acpi ...</command>. The directory listing will also show <command>[Treat like Removable Media Boot]</command> on the next to the last line. Select this line with the arrow keys and press <command>ENTER</command>. This will start the boot load sequence." msgstr "" #. Tag: para -#: boot-installer.xml:1401 +#: boot-installer.xml:976 #, no-c-format msgid "These steps start the Debian boot loader which will display a menu page for you to select a boot kernel and options. Proceed to selecting the boot kernel and options." msgstr "" #. Tag: title -#: boot-installer.xml:1411 +#: boot-installer.xml:986 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "" #. Tag: para -#: boot-installer.xml:1412 +#: boot-installer.xml:987 #, no-c-format msgid "If, for some reason, option 1 is not successful, reboot the machine and when the EFI Boot Manager screen appears there should be one option called <command>EFI Shell [Built-in]</command>. Boot the Debian Installer CD with the following steps:" msgstr "" #. Tag: para -#: boot-installer.xml:1423 +#: boot-installer.xml:998 #, no-c-format msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes system initialization." msgstr "" #. Tag: para -#: boot-installer.xml:1429 +#: boot-installer.xml:1004 #, no-c-format msgid "Select <command>EFI Shell</command> from the menu with the arrow keys and press <command>ENTER</command>. The EFI Shell will scan all of the bootable devices and display them to the console before displaying its command prompt. The recognized bootable partitions on devices will show a device name of <filename>fs<replaceable>n</replaceable>:</filename>. All other recognized partitions will be named <filename>blk<replaceable>n</replaceable>:</filename>. If you inserted the CD just before entering the shell, this may take a few extra seconds as it initializes the CD drive." msgstr "" #. Tag: para -#: boot-installer.xml:1443 +#: boot-installer.xml:1018 #, no-c-format msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the <filename>fs0:</filename> device although other devices with bootable partitions will also show up as <filename>fs<replaceable>n</replaceable></filename>." msgstr "" #. Tag: para -#: boot-installer.xml:1450 +#: boot-installer.xml:1025 #, no-c-format msgid "Enter <command>fs<replaceable>n</replaceable>:</command> and press <command>ENTER</command> to select that device where <replaceable>n</replaceable> is the partition number for the CDROM. The shell will now display the partition number as its prompt." msgstr "" #. Tag: para -#: boot-installer.xml:1457 +#: boot-installer.xml:1032 #, no-c-format msgid "Enter <command>elilo</command> and press <command>ENTER</command>. This will start the boot load sequence." msgstr "" #. Tag: para -#: boot-installer.xml:1464 +#: boot-installer.xml:1039 #, no-c-format msgid "As with option 1, these steps start the Debian boot loader which will display a menu page for you to select a boot kernel and options. You can also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</command> command at the shell prompt. Proceed to selecting the boot kernel and options." msgstr "" #. Tag: title -#: boot-installer.xml:1478 +#: boot-installer.xml:1053 #, no-c-format msgid "Installing using a Serial Console" msgstr "" #. Tag: para -#: boot-installer.xml:1480 +#: boot-installer.xml:1055 #, no-c-format msgid "You may choose to perform an install using a monitor and keyboard or using a serial connection. To use a monitor/keyboard setup, select an option containing the string [VGA console]. To install over a serial connection, choose an option containing the string [<replaceable>BAUD</replaceable> baud serial console], where <replaceable>BAUD</replaceable> is the speed of your serial console. Menu items for the most typical baud rate settings on the ttyS0 device are preconfigured." msgstr "" #. Tag: para -#: boot-installer.xml:1491 +#: boot-installer.xml:1066 #, no-c-format msgid "In most circumstances, you will want the installer to use the same baud rate as your connection to the EFI console. If you aren't sure what this setting is, you can obtain it using the command <command>baud</command> at the EFI shell." msgstr "" #. Tag: para -#: boot-installer.xml:1498 +#: boot-installer.xml:1073 #, no-c-format msgid "If there is not an option available that is configured for the serial device or baud rate you would like to use, you may override the console setting for one of the existing menu options. For example, to use a 57600 baud console over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into the <classname>Boot:</classname> text window." msgstr "" #. Tag: para -#: boot-installer.xml:1509 +#: boot-installer.xml:1084 #, no-c-format msgid "Most IA-64 boxes ship with a default console setting of 9600 baud. This setting is rather slow, and the normal installation process will take a significant time to draw each screen. You should consider either increasing the baud rate used for performing the installation, or performing a Text Mode installation. See the <classname>Params</classname> help menu for instructions on starting the installer in Text Mode." msgstr "" #. Tag: para -#: boot-installer.xml:1518 +#: boot-installer.xml:1093 #, no-c-format msgid "If you select the wrong console type, you will be able to select the kernel and enter parameters but both the display and your input will go dead as soon as the kernel starts, requiring you to reboot before you can begin the installation." msgstr "" #. Tag: title -#: boot-installer.xml:1527 +#: boot-installer.xml:1102 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "" #. Tag: para -#: boot-installer.xml:1529 +#: boot-installer.xml:1104 #, no-c-format msgid "The boot loader will display a form with a menu list and a text window with a <classname>Boot:</classname> prompt. The arrow keys select an item from the menu and any text typed at the keyboard will appear in the text window. There are also help screens which can be displayed by pressing the appropriate function key. The <classname>General</classname> help screen explains the menu choices and the <classname>Params</classname> screen explains the common command line options." msgstr "" #. Tag: para -#: boot-installer.xml:1541 +#: boot-installer.xml:1116 #, no-c-format msgid "Consult the <classname>General</classname> help screen for the description of the kernels and install modes most appropriate for your installation. You should also consult <xref linkend=\"boot-parms\"/> below for any additional parameters that you may want to set in the <classname>Boot:</classname> text window. The kernel version you choose selects the kernel version that will be used for both the installation process and the installed system. If you encounter kernel problems with the installation, you may also have those same problems with the system you install. The following two steps will select and start the install:" msgstr "" #. Tag: para -#: boot-installer.xml:1559 +#: boot-installer.xml:1134 #, no-c-format msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys." msgstr "" #. Tag: para -#: boot-installer.xml:1564 +#: boot-installer.xml:1139 #, no-c-format msgid "Enter any boot parameters by typing at the keyboard. The text will be displayed directly in the text window. This is where kernel parameters (such as serial console settings) are specified." msgstr "" #. Tag: para -#: boot-installer.xml:1571 +#: boot-installer.xml:1146 #, no-c-format msgid "Press <command>ENTER</command>. This will load and start the kernel. The kernel will display its usual initialization messages followed by the first screen of the Debian Installer." msgstr "" #. Tag: para -#: boot-installer.xml:1580 boot-installer.xml:1716 +#: boot-installer.xml:1155 boot-installer.xml:1291 #, no-c-format msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions." msgstr "" #. Tag: para -#: boot-installer.xml:1591 +#: boot-installer.xml:1166 #, no-c-format msgid "Booting an IA-64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed through the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive." msgstr "" #. Tag: para -#: boot-installer.xml:1625 +#: boot-installer.xml:1200 #, no-c-format msgid "Network booting an IA-64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver <command>elilo</command>. On the client a new boot option must be defined in the EFI boot manager to enable loading over a network." msgstr "" #. Tag: title -#: boot-installer.xml:1636 +#: boot-installer.xml:1211 #, no-c-format msgid "Configuring the Server" msgstr "" #. Tag: para -#: boot-installer.xml:1637 +#: boot-installer.xml:1212 #, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n" @@ -1220,13 +772,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1647 +#: boot-installer.xml:1222 #, no-c-format msgid "Extract the <filename>netboot.tar.gz</filename> file into the directory used as the root for your tftp server. Typical tftp root directories include <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This will create a <filename>debian-installer</filename> directory tree containing the boot files for an IA-64 system." msgstr "" #. Tag: screen -#: boot-installer.xml:1657 +#: boot-installer.xml:1232 #, no-c-format msgid "" "# cd /var/lib/tftp\n" @@ -1238,37 +790,37 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1657 +#: boot-installer.xml:1232 #, no-c-format msgid "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</filename> file that should work for most configurations. However, should you need to make changes to this file, you can find it in the <filename>debian-installer/ia64/</filename> directory. It is possible to have different config files for different clients by naming them using the client's IP address in hex with the suffix <filename>.conf</filename> instead of <filename>elilo.conf</filename>. See documentation provided in the <classname>elilo</classname> package for details." msgstr "" #. Tag: title -#: boot-installer.xml:1674 +#: boot-installer.xml:1249 #, no-c-format msgid "Configuring the Client" msgstr "" #. Tag: para -#: boot-installer.xml:1675 +#: boot-installer.xml:1250 #, no-c-format msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> <listitem><para> Add a boot option. </para></listitem> <listitem><para> You should see one or more lines with the text <guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose the one containing the MAC address of the interface from which you'll be booting. Use the arrow keys to highlight your choice, then press enter. </para></listitem> <listitem><para> Name the entry <userinput>Netboot</userinput> or something similar, save, and exit back to the boot options menu. </para></listitem> </itemizedlist> You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of <filename>elilo.efi</filename> from the server." msgstr "" #. Tag: para -#: boot-installer.xml:1707 +#: boot-installer.xml:1282 #, no-c-format msgid "The boot loader will display its prompt after it has downloaded and processed its configuration file. At this point, the installation proceeds with the same steps as a CD install. Select a boot option as in above and when the kernel has completed installing itself from the network, it will start the Debian Installer." msgstr "" #. Tag: title -#: boot-installer.xml:1733 boot-installer.xml:1757 +#: boot-installer.xml:1308 boot-installer.xml:1332 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:1734 +#: boot-installer.xml:1309 #, no-c-format msgid "" "After entering the command monitor use <informalexample><screen>\n" @@ -1279,19 +831,19 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:1754 boot-installer.xml:1821 boot-installer.xml:2415 +#: boot-installer.xml:1329 boot-installer.xml:1396 boot-installer.xml:1990 #, no-c-format msgid "Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1758 +#: boot-installer.xml:1333 #, no-c-format msgid "On SGI machines you can append boot parameters to the <command>bootp():</command> command in the command monitor." msgstr "" #. Tag: para -#: boot-installer.xml:1763 +#: boot-installer.xml:1338 #, no-c-format msgid "" "Following the <command>bootp():</command> command you can give the path and name of the file to boot if you did not give an explicit name via your bootp/dhcp server. Example: <informalexample><screen>\n" @@ -1300,133 +852,133 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:1773 +#: boot-installer.xml:1348 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: title -#: boot-installer.xml:1787 boot-installer.xml:1824 +#: boot-installer.xml:1362 boot-installer.xml:1399 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:1788 +#: boot-installer.xml:1363 #, no-c-format msgid "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to install an NFS server and put the installer files in <filename>/nfsroot</filename>. When you boot your Cobalt, you have to press the left and the right cursor buttons at the same time and the machine will boot via the network from NFS. It will then display several options on the display. There are the following two installation methods:" msgstr "" #. Tag: para -#: boot-installer.xml:1798 +#: boot-installer.xml:1373 #, no-c-format msgid "Via SSH (default): In this case, the installer will configure the network via DHCP and start an SSH server. It will then display a random password and other login information (such as the IP address) on the Cobalt LCD. When you connect to the machine with an SSH client you can start with the installation." msgstr "" #. Tag: para -#: boot-installer.xml:1807 +#: boot-installer.xml:1382 #, no-c-format msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way." msgstr "" #. Tag: para -#: boot-installer.xml:1825 +#: boot-installer.xml:1400 #, no-c-format msgid "You cannot pass any boot parameters directly. Instead, you have to edit the <filename>/nfsroot/default.colo</filename> file on the NFS server and add your parameters to the <replaceable>args</replaceable> variable." msgstr "" #. Tag: title -#: boot-installer.xml:1840 +#: boot-installer.xml:1415 #, no-c-format msgid "s390 Limitations" msgstr "" #. Tag: para -#: boot-installer.xml:1841 +#: boot-installer.xml:1416 #, no-c-format msgid "In order to run the installation system a working network setup and ssh session is needed on S/390." msgstr "" #. Tag: para -#: boot-installer.xml:1846 +#: boot-installer.xml:1421 #, no-c-format msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting an ssh session which will launch the standard installation system." msgstr "" #. Tag: title -#: boot-installer.xml:1857 +#: boot-installer.xml:1432 #, no-c-format msgid "s390 Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1858 +#: boot-installer.xml:1433 #, no-c-format msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images." msgstr "" #. Tag: para -#: boot-installer.xml:1918 +#: boot-installer.xml:1493 #, no-c-format msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the CD-ROM." msgstr "" #. Tag: para -#: boot-installer.xml:1927 +#: boot-installer.xml:1502 #, no-c-format msgid "OldWorld PowerMacs will not boot a Debian CD, because OldWorld computers relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-software version of this driver is not available. All OldWorld systems have floppy drives, so use the floppy drive to launch the installer, and then point the installer to the CD for the needed files." msgstr "" #. Tag: para -#: boot-installer.xml:1936 +#: boot-installer.xml:1511 #, no-c-format msgid "If your system doesn't boot directly from CD-ROM, you can still use the CD-ROM to install the system. On NewWorlds, you can also use an OpenFirmware command to boot from the CD-ROM manually. Follow the instructions in <xref linkend=\"boot-newworld\"/> for booting from the hard disk, except use the path to <command>yaboot</command> on the CD at the OF prompt, such as" msgstr "" #. Tag: screen -#: boot-installer.xml:1945 +#: boot-installer.xml:1520 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "" #. Tag: title -#: boot-installer.xml:1951 +#: boot-installer.xml:1526 #, no-c-format msgid "Booting from Hard Disk" msgstr "" #. Tag: para -#: boot-installer.xml:1957 +#: boot-installer.xml:1532 #, no-c-format msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation." msgstr "" #. Tag: para -#: boot-installer.xml:1963 +#: boot-installer.xml:1538 #, no-c-format msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files in <xref linkend=\"boot-drive-files\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:1983 +#: boot-installer.xml:1558 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" #. Tag: para -#: boot-installer.xml:1984 +#: boot-installer.xml:1559 #, no-c-format msgid "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to boot into the installation system. Double click the <guiicon>BootX</guiicon> application icon. Click on the <guibutton>Options</guibutton> button and select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the chance to select the <filename>ramdisk.image.gz</filename> file. You may need to select the <guilabel>No Video Driver</guilabel> checkbox, depending on your hardware. Then click the <guibutton>Linux</guibutton> button to shut down MacOS and launch the installer." msgstr "" #. Tag: title -#: boot-installer.xml:2002 +#: boot-installer.xml:1577 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" #. Tag: para -#: boot-installer.xml:2003 +#: boot-installer.xml:1578 #, no-c-format msgid "" "You will have already placed the <filename>vmlinux</filename>, <filename>initrd.gz</filename>, <filename>yaboot</filename>, and <filename>yaboot.conf</filename> files at the root level of your HFS partition in <xref linkend=\"files-newworld\"/>. You will now have to boot into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the prompt, type <informalexample><screen>\n" @@ -1437,31 +989,31 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:2035 +#: boot-installer.xml:1610 #, no-c-format msgid "Booting from USB memory stick" msgstr "" #. Tag: para -#: boot-installer.xml:2036 +#: boot-installer.xml:1611 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" #. Tag: para -#: boot-installer.xml:2042 +#: boot-installer.xml:1617 #, no-c-format msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. See <xref linkend=\"invoking-openfirmware\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:2051 +#: boot-installer.xml:1626 #, no-c-format msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment <command>ofpath</command> cannot work that out automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</userinput> at the Open Firmware prompt to get a list of all known devices and device aliases. On the author's system with various types of USB stick, paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work." msgstr "" #. Tag: para -#: boot-installer.xml:2063 +#: boot-installer.xml:1638 #, no-c-format msgid "" "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n" @@ -1470,25 +1022,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2077 +#: boot-installer.xml:1652 #, no-c-format msgid "The system should now boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;." msgstr "" #. Tag: para -#: boot-installer.xml:2083 +#: boot-installer.xml:1658 #, no-c-format msgid "This boot method is new, and may be difficult to get to work on some NewWorld systems. If you have problems, please file an installation report, as explained in <xref linkend=\"submit-bug\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:2116 +#: boot-installer.xml:1691 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" #. Tag: para -#: boot-installer.xml:2120 +#: boot-installer.xml:1695 #, no-c-format msgid "" "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <informalexample><screen>\n" @@ -1501,163 +1053,163 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2148 +#: boot-installer.xml:1723 #, no-c-format msgid "Booting from floppies is supported for &arch-title;, although it is generally only applicable for OldWorld systems. NewWorld systems are not equipped with floppy drives, and attached USB floppy drives are not supported for booting." msgstr "" #. Tag: para -#: boot-installer.xml:2160 +#: boot-installer.xml:1735 #, no-c-format msgid "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button." msgstr "" #. Tag: para -#: boot-installer.xml:2166 +#: boot-installer.xml:1741 #, no-c-format msgid "For those not familiar with Macintosh floppy operations: a floppy placed in the machine prior to boot will be the first priority for the system to boot from. A floppy without a valid boot system will be ejected, and the machine will then check for bootable hard disk partitions." msgstr "" #. Tag: para -#: boot-installer.xml:2173 +#: boot-installer.xml:1748 #, no-c-format msgid "After booting, the <filename>root.bin</filename> floppy is requested. Insert the root floppy and press &enterkey;. The installer program is automatically launched after the root system has been loaded into memory." msgstr "" #. Tag: title -#: boot-installer.xml:2184 +#: boot-installer.xml:1759 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2185 +#: boot-installer.xml:1760 #, no-c-format msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ." msgstr "" #. Tag: para -#: boot-installer.xml:2225 +#: boot-installer.xml:1800 #, no-c-format msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> command." msgstr "" #. Tag: para -#: boot-installer.xml:2280 +#: boot-installer.xml:1855 #, no-c-format msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems)." msgstr "" #. Tag: title -#: boot-installer.xml:2289 +#: boot-installer.xml:1864 #, no-c-format msgid "IDPROM Messages" msgstr "" #. Tag: para -#: boot-installer.xml:2290 +#: boot-installer.xml:1865 #, no-c-format msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information." msgstr "" #. Tag: title -#: boot-installer.xml:2309 +#: boot-installer.xml:1884 #, no-c-format msgid "Accessibility" msgstr "" #. Tag: para -#: boot-installer.xml:2310 +#: boot-installer.xml:1885 #, no-c-format -msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"alpha;ia64;powerpc;x86\">USB braille displays are detected automatically, but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard." +msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected automatically, but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard." msgstr "" #. Tag: title -#: boot-installer.xml:2327 +#: boot-installer.xml:1902 #, no-c-format msgid "USB Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:2328 +#: boot-installer.xml:1903 #, no-c-format msgid "USB braille displays should be automatically detected. A textual version of the installer will then be automatically selected, and support for the braille display will be automatically installed on the target system. You can thus just press &enterkey; at the boot menu. Once <classname>brltty</classname> is started, you can choose a braille table by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:2343 +#: boot-installer.xml:1918 #, no-c-format msgid "Serial Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:2344 +#: boot-installer.xml:1919 #, no-c-format msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the <userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> boot parameter to tell <classname>brltty</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the two-letter driver code for your terminal (see the <ulink url=\"&url-brltty-driver-codes;\">driver code list</ulink>). <replaceable>port</replaceable> should be replaced by the name of the serial port the display is connected to, <userinput>ttyS0</userinput> is the default. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-table-codes;\">table code list</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:2366 +#: boot-installer.xml:1941 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: boot-installer.xml:2367 +#: boot-installer.xml:1942 #, no-c-format msgid "Support for hardware speech synthesis devices is available only alongside support for graphical installer. You thus need to select the <quote>Graphical install</quote> entry in the boot menu." msgstr "" #. Tag: para -#: boot-installer.xml:2373 +#: boot-installer.xml:1948 #, no-c-format msgid "Hardware speech synthesis devices cannot be automatically detected. You thus need to append the <userinput>speakup.synth=<replaceable>driver</replaceable></userinput> boot parameter to tell <classname>speakup</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the driver code for your device (see <ulink url=\"&url-speakup-driver-codes;\">driver code list</ulink>). The textual version of the installer will then be automatically selected, and support for the speech synthesis device will be automatically installed on the target system." msgstr "" #. Tag: title -#: boot-installer.xml:2388 +#: boot-installer.xml:1963 #, no-c-format msgid "Board Devices" msgstr "" #. Tag: para -#: boot-installer.xml:2389 +#: boot-installer.xml:1964 #, no-c-format msgid "Some accessibility devices are actual boards that are plugged inside the machine and that read text directly from the video memory. To get them to work framebuffer support must be disabled by using the <userinput>fb=false</userinput> boot parameter. This will however reduce the number of available languages." msgstr "" #. Tag: title -#: boot-installer.xml:2400 +#: boot-installer.xml:1975 #, no-c-format msgid "High-Contrast Theme" msgstr "" #. Tag: para -#: boot-installer.xml:2401 +#: boot-installer.xml:1976 #, no-c-format msgid "For users with low vision, the installer can use a high-contrast theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter." msgstr "" #. Tag: para -#: boot-installer.xml:2416 +#: boot-installer.xml:1991 #, no-c-format msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit." msgstr "" #. Tag: para -#: boot-installer.xml:2423 +#: boot-installer.xml:1998 #, no-c-format msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware." msgstr "" #. Tag: para -#: boot-installer.xml:2430 +#: boot-installer.xml:2005 #, no-c-format msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:2439 +#: boot-installer.xml:2014 #, no-c-format msgid "" "When the kernel boots, a message <informalexample><screen>\n" @@ -1666,505 +1218,505 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2455 +#: boot-installer.xml:2030 #, no-c-format msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename><footnote> <para> In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter <userinput>TERM=<replaceable>type</replaceable></userinput> can be added. Note that the installer only supports the following terminal types: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> and <literal>dumb</literal>. The default for serial console in &d-i; is <userinput>vt102</userinput>. </para> </footnote>." msgstr "" #. Tag: para -#: boot-installer.xml:2479 +#: boot-installer.xml:2054 #, no-c-format msgid "For &arch-title; the serial devices are <filename>ttya</filename> or <filename>ttyb</filename>. Alternatively, set the <envar>input-device</envar> and <envar>output-device</envar> OpenPROM variables to <filename>ttya</filename>." msgstr "" #. Tag: title -#: boot-installer.xml:2490 +#: boot-installer.xml:2065 #, no-c-format msgid "Debian Installer Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2491 +#: boot-installer.xml:2066 #, no-c-format msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful." msgstr "" #. Tag: para -#: boot-installer.xml:2504 +#: boot-installer.xml:2079 #, no-c-format msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too." msgstr "" #. Tag: term -#: boot-installer.xml:2516 +#: boot-installer.xml:2091 #, no-c-format msgid "debconf/priority (priority)" msgstr "" #. Tag: para -#: boot-installer.xml:2517 +#: boot-installer.xml:2092 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" #. Tag: para -#: boot-installer.xml:2521 +#: boot-installer.xml:2096 #, no-c-format msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed." msgstr "" #. Tag: para -#: boot-installer.xml:2528 +#: boot-installer.xml:2103 #, no-c-format msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss." msgstr "" #. Tag: term -#: boot-installer.xml:2542 +#: boot-installer.xml:2117 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para -#: boot-installer.xml:2543 +#: boot-installer.xml:2118 #, no-c-format msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally, only the <userinput>newt</userinput> frontend is available on default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend." msgstr "" #. Tag: term -#: boot-installer.xml:2572 +#: boot-installer.xml:2147 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:2573 +#: boot-installer.xml:2148 #, no-c-format msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)" msgstr "" #. Tag: userinput -#: boot-installer.xml:2582 +#: boot-installer.xml:2157 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:2583 +#: boot-installer.xml:2158 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:2587 +#: boot-installer.xml:2162 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:2588 +#: boot-installer.xml:2163 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:2592 +#: boot-installer.xml:2167 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:2593 +#: boot-installer.xml:2168 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:2597 +#: boot-installer.xml:2172 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:2598 +#: boot-installer.xml:2173 #, no-c-format msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot." msgstr "" #. Tag: term -#: boot-installer.xml:2612 +#: boot-installer.xml:2187 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:2613 +#: boot-installer.xml:2188 #, no-c-format msgid "The value of the parameter is the path to the device to load the Debian installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>" msgstr "" #. Tag: para -#: boot-installer.xml:2619 +#: boot-installer.xml:2194 #, no-c-format msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device." msgstr "" #. Tag: term -#: boot-installer.xml:2629 +#: boot-installer.xml:2204 #, no-c-format msgid "lowmem" msgstr "" #. Tag: para -#: boot-installer.xml:2630 +#: boot-installer.xml:2205 #, no-c-format msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:2640 +#: boot-installer.xml:2215 #, no-c-format msgid "noshell" msgstr "" #. Tag: para -#: boot-installer.xml:2641 +#: boot-installer.xml:2216 #, no-c-format msgid "Prevents the installer from offering interactive shells on tty2 and tty3. Useful for unattended installations where physical security is limited." msgstr "" #. Tag: term -#: boot-installer.xml:2650 +#: boot-installer.xml:2225 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "" #. Tag: para -#: boot-installer.xml:2651 +#: boot-installer.xml:2226 #, no-c-format msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature by the parameter <userinput>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install." msgstr "" #. Tag: para -#: boot-installer.xml:2660 +#: boot-installer.xml:2235 #, no-c-format msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card." msgstr "" #. Tag: para -#: boot-installer.xml:2666 +#: boot-installer.xml:2241 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:2670 +#: boot-installer.xml:2245 #, no-c-format msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short." msgstr "" #. Tag: term -#: boot-installer.xml:2684 +#: boot-installer.xml:2259 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "" #. Tag: para -#: boot-installer.xml:2685 +#: boot-installer.xml:2260 #, no-c-format msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with <userinput>theme=<replaceable>dark</replaceable></userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:2697 boot-installer.xml:2947 +#: boot-installer.xml:2272 boot-installer.xml:2522 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" #. Tag: para -#: boot-installer.xml:2698 +#: boot-installer.xml:2273 #, no-c-format msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails." msgstr "" #. Tag: para -#: boot-installer.xml:2705 +#: boot-installer.xml:2280 #, no-c-format msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually." msgstr "" #. Tag: term -#: boot-installer.xml:2716 +#: boot-installer.xml:2291 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:2717 +#: boot-installer.xml:2292 #, no-c-format msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." msgstr "" #. Tag: term -#: boot-installer.xml:2727 +#: boot-installer.xml:2302 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "" #. Tag: para -#: boot-installer.xml:2728 +#: boot-installer.xml:2303 #, no-c-format msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">Debian Installer Wiki</ulink>." msgstr "" #. Tag: term -#: boot-installer.xml:2739 +#: boot-installer.xml:2314 #, no-c-format msgid "preseed/url (url)" msgstr "" #. Tag: para -#: boot-installer.xml:2740 +#: boot-installer.xml:2315 #, no-c-format msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:2749 +#: boot-installer.xml:2324 #, no-c-format msgid "preseed/file (file)" msgstr "" #. Tag: para -#: boot-installer.xml:2750 +#: boot-installer.xml:2325 #, no-c-format msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:2759 +#: boot-installer.xml:2334 #, no-c-format msgid "preseed/interactive" msgstr "" #. Tag: para -#: boot-installer.xml:2760 +#: boot-installer.xml:2335 #, no-c-format msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details." msgstr "" #. Tag: term -#: boot-installer.xml:2772 +#: boot-installer.xml:2347 #, no-c-format msgid "auto-install/enable (auto)" msgstr "" #. Tag: para -#: boot-installer.xml:2773 +#: boot-installer.xml:2348 #, no-c-format msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs." msgstr "" #. Tag: term -#: boot-installer.xml:2784 +#: boot-installer.xml:2359 #, no-c-format msgid "finish-install/keep-consoles" msgstr "" #. Tag: para -#: boot-installer.xml:2785 +#: boot-installer.xml:2360 #, no-c-format msgid "During installations from serial or management console, the regular virtual consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</filename>. Set to <userinput>true</userinput> to prevent this." msgstr "" #. Tag: term -#: boot-installer.xml:2796 +#: boot-installer.xml:2371 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:2797 +#: boot-installer.xml:2372 #, no-c-format msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically." msgstr "" #. Tag: para -#: boot-installer.xml:2806 +#: boot-installer.xml:2381 #, no-c-format msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation." msgstr "" #. Tag: term -#: boot-installer.xml:2817 +#: boot-installer.xml:2392 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "" #. Tag: para -#: boot-installer.xml:2818 +#: boot-installer.xml:2393 #, no-c-format msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>" msgstr "" #. Tag: term -#: boot-installer.xml:2829 +#: boot-installer.xml:2404 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:2830 +#: boot-installer.xml:2405 #, no-c-format msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB." msgstr "" #. Tag: term -#: boot-installer.xml:2840 +#: boot-installer.xml:2415 #, no-c-format msgid "mouse/protocol" msgstr "" #. Tag: para -#: boot-installer.xml:2841 +#: boot-installer.xml:2416 #, no-c-format msgid "For the gtk frontend (graphical installer), users can set the mouse protocol to be used by setting this parameter. Supported values are<footnote> <para> See the man page for <citerefentry><refentrytitle>directfbrc</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for additional information. </para> </footnote>: <userinput>PS/2</userinput>, <userinput>IMPS/2</userinput>, <userinput>MS</userinput>, <userinput>MS3</userinput>, <userinput>MouseMan</userinput> and <userinput>MouseSystems</userinput>. In most cases the default protocol should work correctly." msgstr "" #. Tag: term -#: boot-installer.xml:2863 +#: boot-installer.xml:2438 #, no-c-format msgid "mouse/device" msgstr "" #. Tag: para -#: boot-installer.xml:2864 +#: boot-installer.xml:2439 #, no-c-format msgid "For the gtk frontend (graphical installer), users can specify the mouse device to be used by setting this parameter. This is mostly useful if the mouse is connected to a serial port (serial mouse). Example: <userinput>mouse/device=<replaceable>/dev/ttyS1</replaceable></userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:2875 +#: boot-installer.xml:2450 #, no-c-format msgid "mouse/left" msgstr "" #. Tag: para -#: boot-installer.xml:2876 +#: boot-installer.xml:2451 #, no-c-format msgid "For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to <userinput>true</userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:2885 +#: boot-installer.xml:2460 #, no-c-format msgid "directfb/hw-accel" msgstr "" #. Tag: para -#: boot-installer.xml:2886 +#: boot-installer.xml:2461 #, no-c-format msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. Set this parameter to <userinput>true</userinput> to enable it." msgstr "" #. Tag: term -#: boot-installer.xml:2896 +#: boot-installer.xml:2471 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:2897 +#: boot-installer.xml:2472 #, no-c-format msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:2908 +#: boot-installer.xml:2483 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para -#: boot-installer.xml:2909 +#: boot-installer.xml:2484 #, no-c-format msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below." msgstr "" #. Tag: term -#: boot-installer.xml:2921 +#: boot-installer.xml:2496 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:2922 +#: boot-installer.xml:2497 #, no-c-format msgid "Can be used to set both the language and country for the installation. This will only work if the locale is supported in Debian. For example, use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country." msgstr "" #. Tag: term -#: boot-installer.xml:2933 +#: boot-installer.xml:2508 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:2934 +#: boot-installer.xml:2509 #, no-c-format msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>." msgstr "" #. Tag: para -#: boot-installer.xml:2948 +#: boot-installer.xml:2523 #, no-c-format msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration." msgstr "" #. Tag: term -#: boot-installer.xml:2957 +#: boot-installer.xml:2532 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:2958 +#: boot-installer.xml:2533 #, no-c-format msgid "By default the installer will use the http protocol to download files from Debian mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually." msgstr "" #. Tag: term -#: boot-installer.xml:2971 +#: boot-installer.xml:2546 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para -#: boot-installer.xml:2972 +#: boot-installer.xml:2547 #, no-c-format msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information." msgstr "" #. Tag: title -#: boot-installer.xml:2986 +#: boot-installer.xml:2561 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2987 +#: boot-installer.xml:2562 #, no-c-format msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:3000 +#: boot-installer.xml:2575 #, no-c-format msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually." msgstr "" #. Tag: para -#: boot-installer.xml:3007 +#: boot-installer.xml:2582 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -2173,133 +1725,133 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3017 +#: boot-installer.xml:2592 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:3023 +#: boot-installer.xml:2598 #, no-c-format msgid "Blacklisting kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:3024 +#: boot-installer.xml:2599 #, no-c-format msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first." msgstr "" #. Tag: para -#: boot-installer.xml:3033 +#: boot-installer.xml:2608 #, no-c-format msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:3041 +#: boot-installer.xml:2616 #, no-c-format msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases." msgstr "" #. Tag: title -#: boot-installer.xml:3058 +#: boot-installer.xml:2633 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:3063 +#: boot-installer.xml:2638 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3064 +#: boot-installer.xml:2639 #, no-c-format msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also — even after booting successfully from CD-ROM — fail to recognize the CD-ROM or return errors while reading from it during the installation." msgstr "" #. Tag: para -#: boot-installer.xml:3071 +#: boot-installer.xml:2646 #, no-c-format msgid "There are many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you." msgstr "" #. Tag: para -#: boot-installer.xml:3077 +#: boot-installer.xml:2652 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:3082 +#: boot-installer.xml:2657 #, no-c-format msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty." msgstr "" #. Tag: para -#: boot-installer.xml:3088 +#: boot-installer.xml:2663 #, no-c-format msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with older CD-ROM drives are known to be resolved in this way." msgstr "" #. Tag: para -#: boot-installer.xml:3098 +#: boot-installer.xml:2673 #, no-c-format msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity." msgstr "" #. Tag: para -#: boot-installer.xml:3104 +#: boot-installer.xml:2679 #, no-c-format msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available." msgstr "" #. Tag: title -#: boot-installer.xml:3112 +#: boot-installer.xml:2687 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:3115 +#: boot-installer.xml:2690 #, no-c-format msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer." msgstr "" #. Tag: para -#: boot-installer.xml:3121 +#: boot-installer.xml:2696 #, no-c-format msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)." msgstr "" #. Tag: para -#: boot-installer.xml:3128 +#: boot-installer.xml:2703 #, no-c-format msgid "Some older CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled." msgstr "" #. Tag: title -#: boot-installer.xml:3139 +#: boot-installer.xml:2714 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:3140 +#: boot-installer.xml:2715 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:3145 +#: boot-installer.xml:2720 #, no-c-format msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using." msgstr "" #. Tag: para -#: boot-installer.xml:3151 +#: boot-installer.xml:2726 #, no-c-format msgid "" "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n" @@ -2309,7 +1861,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3164 +#: boot-installer.xml:2739 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -2322,19 +1874,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3169 +#: boot-installer.xml:2744 #, no-c-format msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there." msgstr "" #. Tag: para -#: boot-installer.xml:3181 +#: boot-installer.xml:2756 #, no-c-format msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3188 +#: boot-installer.xml:2763 #, no-c-format msgid "" "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n" @@ -2347,13 +1899,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3202 +#: boot-installer.xml:2777 #, no-c-format msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdrom</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:3210 +#: boot-installer.xml:2785 #, no-c-format msgid "" "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n" @@ -2362,7 +1914,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3220 +#: boot-installer.xml:2795 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -2375,163 +1927,163 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3235 +#: boot-installer.xml:2810 #, no-c-format msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably." msgstr "" #. Tag: title -#: boot-installer.xml:3250 +#: boot-installer.xml:2825 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3252 +#: boot-installer.xml:2827 #, no-c-format msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." msgstr "" #. Tag: para -#: boot-installer.xml:3257 +#: boot-installer.xml:2832 #, no-c-format msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors." msgstr "" #. Tag: para -#: boot-installer.xml:3266 +#: boot-installer.xml:2841 #, no-c-format msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system." msgstr "" #. Tag: para -#: boot-installer.xml:3275 +#: boot-installer.xml:2850 #, no-c-format msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy." msgstr "" #. Tag: para -#: boot-installer.xml:3281 +#: boot-installer.xml:2856 #, no-c-format msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums." msgstr "" #. Tag: para -#: boot-installer.xml:3287 +#: boot-installer.xml:2862 #, no-c-format msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers." msgstr "" #. Tag: title -#: boot-installer.xml:3296 +#: boot-installer.xml:2871 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:3298 +#: boot-installer.xml:2873 #, no-c-format msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:3305 +#: boot-installer.xml:2880 #, no-c-format msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" msgstr "" #. Tag: para -#: boot-installer.xml:3311 +#: boot-installer.xml:2886 #, no-c-format msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>." msgstr "" #. Tag: title -#: boot-installer.xml:3322 boot-installer.xml:3424 +#: boot-installer.xml:2897 boot-installer.xml:2999 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3323 +#: boot-installer.xml:2898 #, no-c-format msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." msgstr "" #. Tag: para -#: boot-installer.xml:3328 +#: boot-installer.xml:2903 #, no-c-format msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3334 +#: boot-installer.xml:2909 #, no-c-format msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3343 +#: boot-installer.xml:2918 #, no-c-format msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test." msgstr "" #. Tag: para -#: boot-installer.xml:3350 +#: boot-installer.xml:2925 #, no-c-format msgid "Some systems (especially laptops) that have a native resolution that is not a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank display after the installer has been booted. In that case adding the boot parameter <userinput>vga=788</userinput><footnote> <para> The parameter <userinput>vga=788</userinput> will activate the VESA framebuffer with a resolution of 800x600. This will probably work, but may not be the optimal resolution for your system. A list of supported resolutions can be obtained by using <userinput>vga=ask</userinput>, but you should be aware that list may not be complete. </para> </footnote> may help. If that does not work, try adding the boot parameter <userinput>fb=false</userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3368 +#: boot-installer.xml:2943 #, no-c-format msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" #. Tag: title -#: boot-installer.xml:3382 +#: boot-installer.xml:2957 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:3383 +#: boot-installer.xml:2958 #, no-c-format msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems." msgstr "" #. Tag: para -#: boot-installer.xml:3393 +#: boot-installer.xml:2968 #, no-c-format msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3410 +#: boot-installer.xml:2985 #, no-c-format msgid "System Freeze while Loading USB Modules" msgstr "" #. Tag: para -#: boot-installer.xml:3411 +#: boot-installer.xml:2986 #, no-c-format 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>nousb</userinput> parameter at the boot prompt." msgstr "" #. Tag: para -#: boot-installer.xml:3425 +#: boot-installer.xml:3000 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:3431 +#: boot-installer.xml:3006 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:3432 +#: boot-installer.xml:3007 #, 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" @@ -2541,85 +2093,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3446 +#: boot-installer.xml:3021 #, 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:3457 +#: boot-installer.xml:3032 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3458 +#: boot-installer.xml:3033 #, 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:3464 +#: boot-installer.xml:3039 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3473 +#: boot-installer.xml:3048 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3475 +#: boot-installer.xml:3050 #, 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:3500 +#: boot-installer.xml:3075 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3501 +#: boot-installer.xml:3076 #, 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:3512 +#: boot-installer.xml:3087 #, 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:3523 +#: boot-installer.xml:3098 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3524 +#: boot-installer.xml:3099 #, 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:3531 +#: boot-installer.xml:3106 #, 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:3537 +#: boot-installer.xml:3112 #, no-c-format 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-reports</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3547 +#: boot-installer.xml:3122 #, 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 3cb209105..5ac17e906 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: 2009-11-02 22:05+0000\n" +"POT-Creation-Date: 2009-11-02 22:19+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -107,2825 +107,1691 @@ msgstr "" #. Tag: entry #: hardware.xml:74 #, no-c-format -msgid "DEC Alpha" -msgstr "" - -#. Tag: entry -#: hardware.xml:75 -#, no-c-format -msgid "alpha" -msgstr "" - -#. Tag: entry -#: hardware.xml:81 -#, no-c-format msgid "<entry>ARM</entry>" msgstr "" #. Tag: entry -#: hardware.xml:82 +#: hardware.xml:75 #, no-c-format msgid "armel" msgstr "" #. Tag: entry -#: hardware.xml:83 +#: hardware.xml:76 #, no-c-format msgid "Intel IOP32x" msgstr "" #. Tag: entry -#: hardware.xml:84 +#: hardware.xml:77 #, no-c-format msgid "iop32x" msgstr "" #. Tag: entry -#: hardware.xml:86 +#: hardware.xml:79 #, no-c-format msgid "Intel IXP4xx" msgstr "" #. Tag: entry -#: hardware.xml:87 +#: hardware.xml:80 #, no-c-format msgid "ixp4xx" msgstr "" #. Tag: entry -#: hardware.xml:89 +#: hardware.xml:82 #, no-c-format msgid "Marvell Kirkwood" msgstr "" #. Tag: entry -#: hardware.xml:90 +#: hardware.xml:83 #, no-c-format msgid "kirkwood" msgstr "" #. Tag: entry -#: hardware.xml:92 +#: hardware.xml:85 #, no-c-format msgid "Marvell Orion" msgstr "" #. Tag: entry -#: hardware.xml:93 +#: hardware.xml:86 #, no-c-format msgid "orion5x" msgstr "" #. Tag: entry -#: hardware.xml:95 +#: hardware.xml:88 #, no-c-format msgid "<entry>Versatile</entry>" msgstr "" #. Tag: entry -#: hardware.xml:96 +#: hardware.xml:89 #, no-c-format msgid "versatile" msgstr "" #. Tag: entry -#: hardware.xml:100 +#: hardware.xml:93 #, no-c-format msgid "HP PA-RISC" msgstr "" #. Tag: entry -#: hardware.xml:101 +#: hardware.xml:94 #, no-c-format msgid "hppa" msgstr "" #. Tag: entry -#: hardware.xml:102 +#: hardware.xml:95 #, no-c-format msgid "PA-RISC 1.1" msgstr "" #. Tag: entry -#: hardware.xml:103 +#: hardware.xml:96 #, no-c-format msgid "<entry>32</entry>" msgstr "" #. Tag: entry -#: hardware.xml:105 +#: hardware.xml:98 #, no-c-format msgid "PA-RISC 2.0" msgstr "" #. Tag: entry -#: hardware.xml:106 +#: hardware.xml:99 #, no-c-format msgid "<entry>64</entry>" msgstr "" #. Tag: entry -#: hardware.xml:110 +#: hardware.xml:103 #, no-c-format msgid "Intel IA-64" msgstr "" #. Tag: entry -#: hardware.xml:111 +#: hardware.xml:104 #, no-c-format msgid "ia64" msgstr "" #. Tag: entry -#: hardware.xml:117 +#: hardware.xml:110 #, no-c-format msgid "MIPS (big endian)" msgstr "" #. Tag: entry -#: hardware.xml:118 +#: hardware.xml:111 #, no-c-format msgid "mips" msgstr "" #. Tag: entry -#: hardware.xml:119 +#: hardware.xml:112 #, no-c-format msgid "SGI IP22 (Indy/Indigo 2)" msgstr "" #. Tag: entry -#: hardware.xml:120 +#: hardware.xml:113 #, no-c-format msgid "r4k-ip22" msgstr "" #. Tag: entry -#: hardware.xml:122 +#: hardware.xml:115 #, no-c-format msgid "SGI IP32 (O2)" msgstr "" #. Tag: entry -#: hardware.xml:123 +#: hardware.xml:116 #, no-c-format msgid "r5k-ip32" msgstr "" #. Tag: entry -#: hardware.xml:125 hardware.xml:138 +#: hardware.xml:118 hardware.xml:131 #, no-c-format msgid "MIPS Malta (32 bit)" msgstr "" #. Tag: entry -#: hardware.xml:126 hardware.xml:139 +#: hardware.xml:119 hardware.xml:132 #, no-c-format msgid "4kc-malta" msgstr "" #. Tag: entry -#: hardware.xml:128 hardware.xml:141 +#: hardware.xml:121 hardware.xml:134 #, no-c-format msgid "MIPS Malta (64 bit)" msgstr "" #. Tag: entry -#: hardware.xml:129 hardware.xml:142 +#: hardware.xml:122 hardware.xml:135 #, no-c-format msgid "5kc-malta" msgstr "" #. Tag: entry -#: hardware.xml:133 +#: hardware.xml:126 #, no-c-format msgid "MIPS (little endian)" msgstr "" #. Tag: entry -#: hardware.xml:134 +#: hardware.xml:127 #, no-c-format msgid "mipsel" msgstr "" #. Tag: entry -#: hardware.xml:135 +#: hardware.xml:128 #, no-c-format msgid "Cobalt" msgstr "" #. Tag: entry -#: hardware.xml:136 +#: hardware.xml:129 #, no-c-format msgid "cobalt" msgstr "" #. Tag: entry -#: hardware.xml:146 +#: hardware.xml:139 #, no-c-format msgid "IBM/Motorola PowerPC" msgstr "" #. Tag: entry -#: hardware.xml:147 +#: hardware.xml:140 #, no-c-format msgid "<entry>powerpc</entry>" msgstr "" #. Tag: entry -#: hardware.xml:148 +#: hardware.xml:141 #, no-c-format msgid "PowerMac" msgstr "" #. Tag: entry -#: hardware.xml:149 +#: hardware.xml:142 #, no-c-format msgid "pmac" msgstr "" #. Tag: entry -#: hardware.xml:151 +#: hardware.xml:144 #, no-c-format msgid "PReP" msgstr "" #. Tag: entry -#: hardware.xml:152 +#: hardware.xml:145 #, no-c-format msgid "prep" msgstr "" #. Tag: entry -#: hardware.xml:156 +#: hardware.xml:149 #, no-c-format msgid "Sun SPARC" msgstr "" #. Tag: entry -#: hardware.xml:157 +#: hardware.xml:150 #, no-c-format msgid "sparc" msgstr "" #. Tag: entry -#: hardware.xml:158 +#: hardware.xml:151 #, no-c-format msgid "<entry>sun4u</entry>" msgstr "" #. Tag: entry -#: hardware.xml:159 +#: hardware.xml:152 #, no-c-format msgid "sparc64" msgstr "" #. Tag: entry -#: hardware.xml:161 +#: hardware.xml:154 #, no-c-format msgid "<entry>sun4v</entry>" msgstr "" #. Tag: entry -#: hardware.xml:165 +#: hardware.xml:158 #, no-c-format msgid "IBM S/390" msgstr "" #. Tag: entry -#: hardware.xml:166 +#: hardware.xml:159 #, no-c-format msgid "s390" msgstr "" #. Tag: entry -#: hardware.xml:167 +#: hardware.xml:160 #, no-c-format msgid "IPL from VM-reader and DASD" msgstr "" #. Tag: entry -#: hardware.xml:168 +#: hardware.xml:161 #, no-c-format msgid "generic" msgstr "" #. Tag: entry -#: hardware.xml:170 +#: hardware.xml:163 #, no-c-format msgid "IPL from tape" msgstr "" #. Tag: entry -#: hardware.xml:171 +#: hardware.xml:164 #, no-c-format msgid "tape" msgstr "" #. Tag: para -#: hardware.xml:176 +#: hardware.xml:169 #, 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:185 +#: hardware.xml:178 #, no-c-format msgid "The &arch-title; architecture only supports Intel Itanium processors and not the much more common 64-bit processors from the EM64T family (including e.g. the Pentium D and the Core2 Duo). Those systems are supported by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit userland, the <emphasis>i386</emphasis> architecture." msgstr "" #. Tag: para -#: hardware.xml:195 +#: hardware.xml:188 #, 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:217 hardware.xml:676 hardware.xml:712 hardware.xml:816 hardware.xml:835 hardware.xml:918 hardware.xml:976 hardware.xml:1029 +#: hardware.xml:210 hardware.xml:246 hardware.xml:350 hardware.xml:369 hardware.xml:452 hardware.xml:510 hardware.xml:563 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para -#: hardware.xml:218 -#, 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:225 -#, 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:233 -#, 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:250 -#, no-c-format -msgid "Hardware Type" -msgstr "" - -#. Tag: entry -#: hardware.xml:251 -#, no-c-format -msgid "Aliases" -msgstr "" - -#. Tag: entry -#: hardware.xml:251 -#, no-c-format -msgid "MILO image" -msgstr "" - -#. Tag: entry -#: hardware.xml:257 -#, no-c-format -msgid "ALCOR" -msgstr "" - -#. Tag: entry -#: hardware.xml:258 -#, no-c-format -msgid "AlphaStation 500 5/266.300" -msgstr "" - -#. Tag: entry -#: hardware.xml:259 -#, no-c-format -msgid "Maverick" -msgstr "" - -#. Tag: entry -#: hardware.xml:260 hardware.xml:264 hardware.xml:268 -#, no-c-format -msgid "alcor" -msgstr "" - -#. Tag: entry -#: hardware.xml:262 -#, no-c-format -msgid "AlphaStation 500 5/333...500" -msgstr "" - -#. Tag: entry -#: hardware.xml:263 -#, no-c-format -msgid "Bret" -msgstr "" - -#. Tag: entry -#: hardware.xml:266 -#, no-c-format -msgid "AlphaStation 600/266...300" -msgstr "" - -#. Tag: entry -#: hardware.xml:267 -#, no-c-format -msgid "Alcor" -msgstr "" - -#. Tag: entry -#: hardware.xml:270 -#, no-c-format -msgid "AlphaStation 600/300...433" -msgstr "" - -#. Tag: entry -#: hardware.xml:271 -#, no-c-format -msgid "<entry>XLT</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:272 -#, no-c-format -msgid "<entry>xlt</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:276 -#, no-c-format -msgid "BOOK1" -msgstr "" - -#. Tag: entry -#: hardware.xml:277 -#, no-c-format -msgid "AlphaBook1 (laptop)" -msgstr "" - -#. Tag: entry -#: hardware.xml:278 -#, no-c-format -msgid "Alphabook1/Burns" -msgstr "" - -#. Tag: entry -#: hardware.xml:279 -#, no-c-format -msgid "book1" -msgstr "" - -#. Tag: entry -#: hardware.xml:283 -#, no-c-format -msgid "AVANTI" -msgstr "" - -#. Tag: entry -#: hardware.xml:284 -#, no-c-format -msgid "AlphaStation 200 4/100...166" -msgstr "" - -#. Tag: entry -#: hardware.xml:285 -#, no-c-format -msgid "Mustang" -msgstr "" - -#. Tag: entry -#: hardware.xml:286 hardware.xml:290 hardware.xml:294 hardware.xml:298 hardware.xml:302 hardware.xml:306 hardware.xml:310 hardware.xml:314 -#, no-c-format -msgid "avanti" -msgstr "" - -#. Tag: entry -#: hardware.xml:288 -#, no-c-format -msgid "AlphaStation 200 4/233" -msgstr "" - -#. Tag: entry -#: hardware.xml:289 -#, no-c-format -msgid "Mustang+" -msgstr "" - -#. Tag: entry -#: hardware.xml:292 -#, no-c-format -msgid "AlphaStation 205 4/133...333" -msgstr "" - -#. Tag: entry -#: hardware.xml:293 -#, no-c-format -msgid "<entry>LX3</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:296 -#, no-c-format -msgid "AlphaStation 250 4/300" -msgstr "" - -#. Tag: entry -#: hardware.xml:297 -#, no-c-format -msgid "<entry>M3+</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:300 -#, no-c-format -msgid "AlphaStation 255 4/133...333" -msgstr "" - -#. Tag: entry -#: hardware.xml:301 -#, no-c-format -msgid "LX3+" -msgstr "" - -#. Tag: entry -#: hardware.xml:304 -#, no-c-format -msgid "AlphaStation 300 4/266" -msgstr "" - -#. Tag: entry -#: hardware.xml:305 -#, no-c-format -msgid "Melmac" -msgstr "" - -#. Tag: entry -#: hardware.xml:308 -#, no-c-format -msgid "AlphaStation 400 4/166" -msgstr "" - -#. Tag: entry -#: hardware.xml:309 -#, no-c-format -msgid "Chinet" -msgstr "" - -#. Tag: entry -#: hardware.xml:312 -#, no-c-format -msgid "AlphaStation 400 4/233...300" -msgstr "" - -#. Tag: entry -#: hardware.xml:313 -#, no-c-format -msgid "Avanti" -msgstr "" - -#. Tag: entry -#: hardware.xml:318 hardware.xml:331 hardware.xml:332 -#, no-c-format -msgid "EB164" -msgstr "" - -#. Tag: entry -#: hardware.xml:319 -#, no-c-format -msgid "AlphaPC164" -msgstr "" - -#. Tag: entry -#: hardware.xml:320 -#, no-c-format -msgid "PC164" -msgstr "" - -#. Tag: entry -#: hardware.xml:321 -#, no-c-format -msgid "pc164" -msgstr "" - -#. Tag: entry -#: hardware.xml:323 -#, no-c-format -msgid "AlphaPC164-LX" -msgstr "" - -#. Tag: entry -#: hardware.xml:324 -#, no-c-format -msgid "LX164" -msgstr "" - -#. Tag: entry -#: hardware.xml:325 -#, no-c-format -msgid "lx164" -msgstr "" - -#. Tag: entry -#: hardware.xml:327 -#, no-c-format -msgid "AlphaPC164-SX" -msgstr "" - -#. Tag: entry -#: hardware.xml:328 -#, no-c-format -msgid "SX164" -msgstr "" - -#. Tag: entry -#: hardware.xml:329 -#, no-c-format -msgid "sx164" -msgstr "" - -#. Tag: entry -#: hardware.xml:333 -#, no-c-format -msgid "eb164" -msgstr "" - -#. Tag: entry -#: hardware.xml:337 hardware.xml:346 hardware.xml:347 -#, no-c-format -msgid "EB64+" -msgstr "" - -#. Tag: entry -#: hardware.xml:338 -#, no-c-format -msgid "AlphaPC64" -msgstr "" - -#. Tag: entry -#: hardware.xml:339 hardware.xml:343 -#, no-c-format -msgid "Cabriolet" -msgstr "" - -#. Tag: entry -#: hardware.xml:340 hardware.xml:344 -#, no-c-format -msgid "cabriolet" -msgstr "" - -#. Tag: entry -#: hardware.xml:342 -#, no-c-format -msgid "AlphaPCI64" -msgstr "" - -#. Tag: entry -#: hardware.xml:348 -#, no-c-format -msgid "eb64p" -msgstr "" - -#. Tag: entry -#: hardware.xml:352 hardware.xml:353 hardware.xml:354 -#, no-c-format -msgid "EB66" -msgstr "" - -#. Tag: entry -#: hardware.xml:355 -#, no-c-format -msgid "eb66" -msgstr "" - -#. Tag: entry -#: hardware.xml:357 hardware.xml:358 -#, no-c-format -msgid "EB66+" -msgstr "" - -#. Tag: entry -#: hardware.xml:359 -#, no-c-format -msgid "eb66p" -msgstr "" - -#. Tag: entry -#: hardware.xml:363 -#, no-c-format -msgid "JENSEN" -msgstr "" - -#. Tag: entry -#: hardware.xml:364 -#, no-c-format -msgid "DEC 2000 Model 300(S)" -msgstr "" - -#. Tag: entry -#: hardware.xml:365 hardware.xml:373 -#, no-c-format -msgid "Jensen" -msgstr "" - -#. Tag: entry -#: hardware.xml:366 hardware.xml:370 hardware.xml:374 hardware.xml:435 hardware.xml:439 hardware.xml:457 hardware.xml:461 hardware.xml:465 hardware.xml:469 hardware.xml:473 hardware.xml:477 hardware.xml:481 hardware.xml:495 hardware.xml:499 hardware.xml:503 hardware.xml:507 hardware.xml:511 hardware.xml:545 hardware.xml:549 hardware.xml:553 hardware.xml:557 hardware.xml:571 hardware.xml:575 hardware.xml:579 hardware.xml:583 hardware.xml:590 hardware.xml:594 hardware.xml:598 hardware.xml:602 hardware.xml:606 hardware.xml:610 hardware.xml:614 hardware.xml:618 hardware.xml:622 hardware.xml:626 hardware.xml:630 hardware.xml:634 hardware.xml:638 hardware.xml:645 hardware.xml:649 -#, no-c-format -msgid "<entry>N/A</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:368 -#, no-c-format -msgid "DEC 2000 Model 500" -msgstr "" - -#. Tag: entry -#: hardware.xml:369 -#, no-c-format -msgid "Culzen" -msgstr "" - -#. Tag: entry -#: hardware.xml:372 -#, no-c-format -msgid "DECpc 150" -msgstr "" - -#. Tag: entry -#: hardware.xml:378 -#, no-c-format -msgid "MIATA" -msgstr "" - -#. Tag: entry -#: hardware.xml:379 -#, no-c-format -msgid "Personal WorkStation 433a" -msgstr "" - -#. Tag: entry -#: hardware.xml:380 hardware.xml:384 hardware.xml:388 hardware.xml:392 hardware.xml:396 hardware.xml:400 hardware.xml:404 hardware.xml:408 -#, no-c-format -msgid "Miata" -msgstr "" - -#. Tag: entry -#: hardware.xml:381 hardware.xml:385 hardware.xml:389 hardware.xml:393 hardware.xml:397 hardware.xml:401 hardware.xml:405 hardware.xml:409 -#, no-c-format -msgid "miata" -msgstr "" - -#. Tag: entry -#: hardware.xml:383 -#, no-c-format -msgid "Personal WorkStation 433au" -msgstr "" - -#. Tag: entry -#: hardware.xml:387 -#, no-c-format -msgid "Personal WorkStation 466au" -msgstr "" - -#. Tag: entry -#: hardware.xml:391 -#, no-c-format -msgid "Personal WorkStation 500a" -msgstr "" - -#. Tag: entry -#: hardware.xml:395 -#, no-c-format -msgid "Personal WorkStation 500au" -msgstr "" - -#. Tag: entry -#: hardware.xml:399 -#, no-c-format -msgid "Personal WorkStation 550au" -msgstr "" - -#. Tag: entry -#: hardware.xml:403 -#, no-c-format -msgid "Personal WorkStation 600a" -msgstr "" - -#. Tag: entry -#: hardware.xml:407 -#, no-c-format -msgid "Personal WorkStation 600au" -msgstr "" - -#. Tag: entry -#: hardware.xml:413 -#, no-c-format -msgid "MIKASA" -msgstr "" - -#. Tag: entry -#: hardware.xml:414 -#, no-c-format -msgid "AlphaServer 1000 4/200" -msgstr "" - -#. Tag: entry -#: hardware.xml:415 -#, no-c-format -msgid "Mikasa" -msgstr "" - -#. Tag: entry -#: hardware.xml:416 hardware.xml:420 hardware.xml:424 hardware.xml:428 -#, no-c-format -msgid "mikasa" -msgstr "" - -#. Tag: entry -#: hardware.xml:418 -#, no-c-format -msgid "AlphaServer 1000 4/233..266" -msgstr "" - -#. Tag: entry -#: hardware.xml:419 -#, no-c-format -msgid "Mikasa+" -msgstr "" - -#. Tag: entry -#: hardware.xml:422 hardware.xml:426 -#, no-c-format -msgid "AlphaServer 1000 5/300" -msgstr "" - -#. Tag: entry -#: hardware.xml:423 -#, no-c-format -msgid "Mikasa-Pinnacle" -msgstr "" - -#. Tag: entry -#: hardware.xml:427 -#, no-c-format -msgid "Mikasa-Primo" -msgstr "" - -#. Tag: entry -#: hardware.xml:432 -#, no-c-format -msgid "NAUTILUS" -msgstr "" - -#. Tag: entry -#: hardware.xml:433 -#, no-c-format -msgid "UP1000" -msgstr "" - -#. Tag: entry -#: hardware.xml:434 -#, no-c-format -msgid "Nautilus" -msgstr "" - -#. Tag: entry -#: hardware.xml:437 -#, no-c-format -msgid "UP1100" -msgstr "" - -#. Tag: entry -#: hardware.xml:438 -#, no-c-format -msgid "Galaxy-Train/Nautilus Jr." -msgstr "" - -#. Tag: entry -#: hardware.xml:443 -#, no-c-format -msgid "NONAME" -msgstr "" - -#. Tag: entry -#: hardware.xml:444 -#, no-c-format -msgid "AXPpci33" -msgstr "" - -#. Tag: entry -#: hardware.xml:445 -#, no-c-format -msgid "Noname" -msgstr "" - -#. Tag: entry -#: hardware.xml:446 hardware.xml:450 -#, no-c-format -msgid "noname" -msgstr "" - -#. Tag: entry -#: hardware.xml:448 -#, no-c-format -msgid "<entry>UDB</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:449 -#, no-c-format -msgid "Multia" -msgstr "" - -#. Tag: entry -#: hardware.xml:454 -#, no-c-format -msgid "NORITAKE" -msgstr "" - -#. Tag: entry -#: hardware.xml:455 -#, no-c-format -msgid "AlphaServer 1000A 4/233...266" -msgstr "" - -#. Tag: entry -#: hardware.xml:456 -#, no-c-format -msgid "Noritake" -msgstr "" - -#. Tag: entry -#: hardware.xml:459 -#, no-c-format -msgid "AlphaServer 1000A 5/300" -msgstr "" - -#. Tag: entry -#: hardware.xml:460 -#, no-c-format -msgid "Noritake-Pinnacle" -msgstr "" - -#. Tag: entry -#: hardware.xml:463 -#, no-c-format -msgid "AlphaServer 1000A 5/333...500" -msgstr "" - -#. Tag: entry -#: hardware.xml:464 -#, no-c-format -msgid "Noritake-Primo" -msgstr "" - -#. Tag: entry -#: hardware.xml:467 -#, no-c-format -msgid "AlphaServer 800 5/333...500" -msgstr "" - -#. Tag: entry -#: hardware.xml:468 hardware.xml:476 hardware.xml:480 -#, no-c-format -msgid "Corelle" -msgstr "" - -#. Tag: entry -#: hardware.xml:471 -#, no-c-format -msgid "AlphaStation 600 A" -msgstr "" - -#. Tag: entry -#: hardware.xml:472 -#, no-c-format -msgid "Alcor-Primo" -msgstr "" - -#. Tag: entry -#: hardware.xml:475 -#, no-c-format -msgid "Digital Server 3300" -msgstr "" - -#. Tag: entry -#: hardware.xml:479 -#, no-c-format -msgid "Digital Server 3300R" -msgstr "" - -#. Tag: entry -#: hardware.xml:485 -#, no-c-format -msgid "PLATFORM 2000" -msgstr "" - -#. Tag: entry -#: hardware.xml:486 hardware.xml:487 -#, no-c-format -msgid "<entry>P2K</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:488 -#, no-c-format -msgid "<entry>p2k</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:492 -#, no-c-format -msgid "RAWHIDE" -msgstr "" - -#. Tag: entry -#: hardware.xml:493 -#, no-c-format -msgid "AlphaServer 1200 5/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:494 hardware.xml:506 -#, no-c-format -msgid "Tincup/DaVinci" -msgstr "" - -#. Tag: entry -#: hardware.xml:497 -#, no-c-format -msgid "AlphaServer 4000 5/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:498 -#, no-c-format -msgid "Wrangler/Durango" -msgstr "" - -#. Tag: entry -#: hardware.xml:501 -#, no-c-format -msgid "AlphaServer 4100 5/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:502 hardware.xml:510 -#, no-c-format -msgid "Dodge" -msgstr "" - -#. Tag: entry -#: hardware.xml:505 -#, no-c-format -msgid "Digital Server 5300" -msgstr "" - -#. Tag: entry -#: hardware.xml:509 -#, no-c-format -msgid "Digital Server 7300" -msgstr "" - -#. Tag: entry -#: hardware.xml:515 -#, no-c-format -msgid "RUFFIAN" -msgstr "" - -#. Tag: entry -#: hardware.xml:516 -#, no-c-format -msgid "DeskStation AlphaPC164-UX" -msgstr "" - -#. Tag: entry -#: hardware.xml:517 hardware.xml:521 hardware.xml:525 hardware.xml:529 hardware.xml:533 hardware.xml:537 -#, no-c-format -msgid "Ruffian" -msgstr "" - -#. Tag: entry -#: hardware.xml:518 hardware.xml:522 hardware.xml:526 hardware.xml:530 hardware.xml:534 hardware.xml:538 -#, no-c-format -msgid "ruffian" -msgstr "" - -#. Tag: entry -#: hardware.xml:520 -#, no-c-format -msgid "DeskStation RPL164-2" -msgstr "" - -#. Tag: entry -#: hardware.xml:524 -#, no-c-format -msgid "DeskStation RPL164-4" -msgstr "" - -#. Tag: entry -#: hardware.xml:528 -#, no-c-format -msgid "DeskStation RPX164-2" -msgstr "" - -#. Tag: entry -#: hardware.xml:532 -#, no-c-format -msgid "DeskStation RPX164-4" -msgstr "" - -#. Tag: entry -#: hardware.xml:536 -#, no-c-format -msgid "Samsung AlphaPC164-BX" -msgstr "" - -#. Tag: entry -#: hardware.xml:542 -#, no-c-format -msgid "SABLE" -msgstr "" - -#. Tag: entry -#: hardware.xml:543 -#, no-c-format -msgid "AlphaServer 2000 4/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:544 -#, no-c-format -msgid "Demi-Sable" -msgstr "" - -#. Tag: entry -#: hardware.xml:547 -#, no-c-format -msgid "AlphaServer 2000 5/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:548 -#, no-c-format -msgid "Demi-Gamma-Sable" -msgstr "" - -#. Tag: entry -#: hardware.xml:551 -#, no-c-format -msgid "AlphaServer 2100 4/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:552 -#, no-c-format -msgid "Sable" -msgstr "" - -#. Tag: entry -#: hardware.xml:555 -#, no-c-format -msgid "AlphaServer 2100 5/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:556 -#, no-c-format -msgid "Gamma-Sable" -msgstr "" - -#. Tag: entry -#: hardware.xml:561 -#, no-c-format -msgid "TAKARA" -msgstr "" - -#. Tag: entry -#: hardware.xml:562 -#, no-c-format -msgid "21164 PICMG SBC" -msgstr "" - -#. Tag: entry -#: hardware.xml:563 -#, no-c-format -msgid "Takara" -msgstr "" - -#. Tag: entry -#: hardware.xml:564 -#, no-c-format -msgid "takara" -msgstr "" - -#. Tag: entry -#: hardware.xml:568 -#, no-c-format -msgid "TITAN" -msgstr "" - -#. Tag: entry -#: hardware.xml:569 -#, no-c-format -msgid "AlphaServer DS15" -msgstr "" - -#. Tag: entry -#: hardware.xml:570 -#, no-c-format -msgid "HyperBrick2" -msgstr "" - -#. Tag: entry -#: hardware.xml:573 -#, no-c-format -msgid "AlphaServer DS25" -msgstr "" - -#. Tag: entry -#: hardware.xml:574 -#, no-c-format -msgid "Granite" -msgstr "" - -#. Tag: entry -#: hardware.xml:577 -#, no-c-format -msgid "AlphaServer ES45" -msgstr "" - -#. Tag: entry -#: hardware.xml:578 -#, no-c-format -msgid "Privateer" -msgstr "" - -#. Tag: entry -#: hardware.xml:581 hardware.xml:620 hardware.xml:624 -#, no-c-format -msgid "UNKNOWN" -msgstr "" - -#. Tag: entry -#: hardware.xml:582 -#, no-c-format -msgid "Yukon" -msgstr "" - -#. Tag: entry -#: hardware.xml:587 -#, no-c-format -msgid "TSUNAMI" -msgstr "" - -#. Tag: entry -#: hardware.xml:588 -#, no-c-format -msgid "AlphaServer DS10" -msgstr "" - -#. Tag: entry -#: hardware.xml:589 hardware.xml:637 -#, no-c-format -msgid "Webbrick" -msgstr "" - -#. Tag: entry -#: hardware.xml:592 -#, no-c-format -msgid "AlphaServer DS10L" -msgstr "" - -#. Tag: entry -#: hardware.xml:593 -#, no-c-format -msgid "Slate" -msgstr "" - -#. Tag: entry -#: hardware.xml:596 -#, no-c-format -msgid "AlphaServer DS20" -msgstr "" - -#. Tag: entry -#: hardware.xml:597 -#, no-c-format -msgid "Catamaran/Goldrush" -msgstr "" - -#. Tag: entry -#: hardware.xml:600 -#, no-c-format -msgid "AlphaServer DS20E" -msgstr "" - -#. Tag: entry -#: hardware.xml:601 -#, no-c-format -msgid "Goldrack" -msgstr "" - -#. Tag: entry -#: hardware.xml:604 -#, no-c-format -msgid "AlphaServer DS20L" -msgstr "" - -#. Tag: entry -#: hardware.xml:605 -#, no-c-format -msgid "Shark" -msgstr "" - -#. Tag: entry -#: hardware.xml:608 -#, no-c-format -msgid "AlphaServer ES40" -msgstr "" - -#. Tag: entry -#: hardware.xml:609 -#, no-c-format -msgid "Clipper" -msgstr "" - -#. Tag: entry -#: hardware.xml:612 hardware.xml:613 -#, no-c-format -msgid "DP264" -msgstr "" - -#. Tag: entry -#: hardware.xml:616 -#, no-c-format -msgid "SMARTengine 21264 PCI/ISA SBC" -msgstr "" - -#. Tag: entry -#: hardware.xml:617 -#, no-c-format -msgid "Eiger" -msgstr "" - -#. Tag: entry -#: hardware.xml:621 -#, no-c-format -msgid "Warhol" -msgstr "" - -#. Tag: entry -#: hardware.xml:625 -#, no-c-format -msgid "Windjammer" -msgstr "" - -#. Tag: entry -#: hardware.xml:628 -#, no-c-format -msgid "UP2000" -msgstr "" - -#. Tag: entry -#: hardware.xml:629 -#, no-c-format -msgid "Swordfish" -msgstr "" - -#. Tag: entry -#: hardware.xml:632 -#, no-c-format -msgid "XP1000" -msgstr "" - -#. Tag: entry -#: hardware.xml:633 -#, no-c-format -msgid "Monet/Brisbane" -msgstr "" - -#. Tag: entry -#: hardware.xml:636 -#, no-c-format -msgid "XP900" -msgstr "" - -#. Tag: entry -#: hardware.xml:642 -#, no-c-format -msgid "WILDFIRE" -msgstr "" - -#. Tag: entry -#: hardware.xml:643 -#, no-c-format -msgid "AlphaServer GS160" -msgstr "" - -#. Tag: entry -#: hardware.xml:644 hardware.xml:648 -#, no-c-format -msgid "Wildfire" -msgstr "" - -#. Tag: entry -#: hardware.xml:647 -#, no-c-format -msgid "AlphaServer GS320" -msgstr "" - -#. Tag: entry -#: hardware.xml:653 hardware.xml:655 -#, no-c-format -msgid "<entry>XL</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:654 -#, no-c-format -msgid "XL-233...266" -msgstr "" - -#. Tag: entry -#: hardware.xml:656 -#, no-c-format -msgid "<entry>xl</entry>" -msgstr "" - -#. Tag: para -#: hardware.xml:661 -#, 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:677 hardware.xml:836 +#: hardware.xml:211 hardware.xml:370 #, 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:685 hardware.xml:844 hardware.xml:953 +#: hardware.xml:219 hardware.xml:378 hardware.xml:487 #, no-c-format msgid "<title>CPU</title>" msgstr "" #. Tag: para -#: hardware.xml:686 +#: hardware.xml:220 #, no-c-format msgid "Both AMD64 and Intel EM64T processors are supported." msgstr "" #. Tag: para -#: hardware.xml:714 +#: hardware.xml:248 #, 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:723 +#: hardware.xml:257 #, 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:731 +#: hardware.xml:265 #, no-c-format msgid "The supported platforms are:" msgstr "" #. Tag: term -#: hardware.xml:738 +#: hardware.xml:272 #, no-c-format msgid "IOP32x" msgstr "" #. Tag: para -#: hardware.xml:739 +#: hardware.xml:273 #, no-c-format msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. Debian currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. Debian explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>." msgstr "" #. Tag: term -#: hardware.xml:752 +#: hardware.xml:286 #, no-c-format msgid "IXP4xx" msgstr "" #. Tag: para -#: hardware.xml:753 +#: hardware.xml:287 #, no-c-format msgid "The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected. There is an external site with <ulink url=\"&url-arm-cyrius-nslu2;\">installation instructions</ulink>." msgstr "" #. Tag: term -#: hardware.xml:767 +#: hardware.xml:301 #, no-c-format msgid "Kirkwood" msgstr "" #. Tag: para -#: hardware.xml:768 +#: hardware.xml:302 #, no-c-format msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: <ulink url=\"&url-arm-cyrius-sheevaplug;\">SheevaPlug</ulink> and <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (TS-119 and TS-219)." msgstr "" #. Tag: term -#: hardware.xml:781 +#: hardware.xml:315 #, no-c-format msgid "Orion5x" msgstr "" #. Tag: para -#: hardware.xml:782 +#: hardware.xml:316 #, no-c-format msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: <ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>, <ulink url=\"&url-arm-cyrius-qnap;\">QNAP Turbo Station</ulink> (TS-109, TS-209 and TS-409)." msgstr "" #. Tag: term -#: hardware.xml:797 +#: hardware.xml:331 #, no-c-format msgid "<term>Versatile</term>" msgstr "" #. Tag: para -#: hardware.xml:798 +#: hardware.xml:332 #, no-c-format msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run Debian on ARM if you don't have the hardware." msgstr "" #. Tag: para -#: hardware.xml:817 +#: hardware.xml:351 #, 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:845 +#: hardware.xml:379 #, no-c-format msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon." msgstr "" #. Tag: para -#: hardware.xml:852 +#: hardware.xml:386 #, no-c-format msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of Debian<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para> </footnote>." msgstr "" #. Tag: para -#: hardware.xml:885 +#: hardware.xml:419 #, no-c-format msgid "If your system has a 64-bit processor from the AMD64 or Intel EM64T families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture." msgstr "" #. Tag: title -#: hardware.xml:894 +#: hardware.xml:428 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:895 +#: hardware.xml:429 #, 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, PCIe, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these." msgstr "" #. Tag: para -#: hardware.xml:919 +#: hardware.xml:453 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run Debian on MIPS if you don't have the hardware. </para></listitem> </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:954 +#: hardware.xml:488 #, 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." msgstr "" #. Tag: para -#: hardware.xml:960 +#: hardware.xml:494 #, 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:977 +#: hardware.xml:511 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run Debian on MIPS if you don't have the hardware. </para></listitem> </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:1005 +#: hardware.xml:539 #, no-c-format msgid "CPU/Machine types" msgstr "" #. Tag: para -#: hardware.xml:1007 +#: hardware.xml:541 #, no-c-format msgid "All MIPS based Cobalt machines are supported with the exception of the Qube 2700 (Qube 1)." msgstr "" #. Tag: title -#: hardware.xml:1015 +#: hardware.xml:549 #, no-c-format msgid "Supported console options" msgstr "" #. Tag: para -#: hardware.xml:1016 +#: hardware.xml:550 #, no-c-format msgid "Cobalt machines use 115200 bps." msgstr "" #. Tag: para -#: hardware.xml:1030 +#: hardware.xml:564 #, no-c-format msgid "For &debian; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported." msgstr "" #. Tag: title -#: hardware.xml:1051 +#: hardware.xml:585 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:1053 +#: hardware.xml:587 #, no-c-format msgid "There are two flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:1060 +#: hardware.xml:594 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:1061 +#: hardware.xml:595 #, 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:1071 +#: hardware.xml:605 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:1072 +#: hardware.xml:606 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:1076 +#: hardware.xml:610 #, 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:1082 +#: hardware.xml:616 #, 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:1087 +#: hardware.xml:621 #, 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: title -#: hardware.xml:1121 +#: hardware.xml:655 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:1123 +#: hardware.xml:657 #, 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:1130 +#: hardware.xml:664 #, 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:1138 +#: hardware.xml:672 #, 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:1146 +#: hardware.xml:680 #, 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:1162 hardware.xml:1297 hardware.xml:1341 hardware.xml:1370 +#: hardware.xml:696 hardware.xml:831 hardware.xml:875 hardware.xml:904 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:1163 +#: hardware.xml:697 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:1169 +#: hardware.xml:703 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:1170 +#: hardware.xml:704 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:1171 hardware.xml:1174 hardware.xml:1177 hardware.xml:1180 hardware.xml:1183 hardware.xml:1186 hardware.xml:1189 hardware.xml:1192 hardware.xml:1195 hardware.xml:1198 hardware.xml:1201 hardware.xml:1204 hardware.xml:1207 hardware.xml:1210 hardware.xml:1213 hardware.xml:1216 +#: hardware.xml:705 hardware.xml:708 hardware.xml:711 hardware.xml:714 hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726 hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738 hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:1173 +#: hardware.xml:707 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:1176 +#: hardware.xml:710 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:1179 +#: hardware.xml:713 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:1182 +#: hardware.xml:716 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:1185 +#: hardware.xml:719 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:1188 +#: hardware.xml:722 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:1191 +#: hardware.xml:725 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:1194 +#: hardware.xml:728 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:1197 +#: hardware.xml:731 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:1200 +#: hardware.xml:734 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:1203 +#: hardware.xml:737 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:1206 +#: hardware.xml:740 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:1209 +#: hardware.xml:743 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:1212 +#: hardware.xml:746 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:1215 +#: hardware.xml:749 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:1218 +#: hardware.xml:752 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:1219 hardware.xml:1222 hardware.xml:1225 hardware.xml:1228 hardware.xml:1231 hardware.xml:1234 hardware.xml:1237 hardware.xml:1240 hardware.xml:1243 hardware.xml:1246 hardware.xml:1249 hardware.xml:1252 hardware.xml:1258 hardware.xml:1261 hardware.xml:1267 hardware.xml:1273 hardware.xml:1279 +#: hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762 hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774 hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786 hardware.xml:792 hardware.xml:795 hardware.xml:801 hardware.xml:807 hardware.xml:813 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:1221 +#: hardware.xml:755 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:1224 +#: hardware.xml:758 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:1227 +#: hardware.xml:761 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:1230 +#: hardware.xml:764 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:1233 +#: hardware.xml:767 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:1236 +#: hardware.xml:770 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:1239 +#: hardware.xml:773 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:1242 +#: hardware.xml:776 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:1245 +#: hardware.xml:779 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:1248 +#: hardware.xml:782 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:1251 +#: hardware.xml:785 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:1256 +#: hardware.xml:790 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:1257 +#: hardware.xml:791 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:1260 +#: hardware.xml:794 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:1265 +#: hardware.xml:799 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:1266 +#: hardware.xml:800 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:1271 +#: hardware.xml:805 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1272 +#: hardware.xml:806 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:1277 hardware.xml:1303 +#: hardware.xml:811 hardware.xml:837 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:1278 +#: hardware.xml:812 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:1287 +#: hardware.xml:821 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1304 +#: hardware.xml:838 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:1306 +#: hardware.xml:840 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:1308 +#: hardware.xml:842 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:1310 +#: hardware.xml:844 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:1312 +#: hardware.xml:846 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:1316 hardware.xml:1347 +#: hardware.xml:850 hardware.xml:881 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:1317 +#: hardware.xml:851 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:1319 +#: hardware.xml:853 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:1321 +#: hardware.xml:855 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:1323 +#: hardware.xml:857 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:1331 +#: hardware.xml:865 #, no-c-format msgid "CHRP subarchitecture (unsupported)" msgstr "" #. Tag: entry -#: hardware.xml:1348 +#: hardware.xml:882 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:1351 +#: hardware.xml:885 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:1352 +#: hardware.xml:886 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: title -#: hardware.xml:1360 +#: hardware.xml:894 #, no-c-format msgid "APUS subarchitecture (unsupported)" msgstr "" #. Tag: entry -#: hardware.xml:1376 +#: hardware.xml:910 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:1377 +#: hardware.xml:911 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:1385 +#: hardware.xml:919 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:1387 +#: hardware.xml:921 #, 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:1424 +#: hardware.xml:958 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:1426 +#: hardware.xml:960 #, 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:1435 +#: hardware.xml:969 #, 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:1443 +#: hardware.xml:977 #, 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:1459 +#: hardware.xml:993 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "" #. Tag: para -#: hardware.xml:1460 +#: hardware.xml:994 #, 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:1482 +#: hardware.xml:1016 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para -#: hardware.xml:1483 +#: hardware.xml:1017 #, 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:1494 +#: hardware.xml:1028 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "" #. Tag: para -#: hardware.xml:1496 +#: hardware.xml:1030 #, no-c-format msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1503 +#: hardware.xml:1037 #, no-c-format msgid "The last Debian release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases." msgstr "" #. Tag: term -#: hardware.xml:1513 +#: hardware.xml:1047 #, no-c-format msgid "<term>sun4u</term>" msgstr "" #. Tag: para -#: hardware.xml:1515 +#: hardware.xml:1049 #, 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:1528 +#: hardware.xml:1062 #, no-c-format msgid "<term>sun4v</term>" msgstr "" #. Tag: para -#: hardware.xml:1530 +#: hardware.xml:1064 #, 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:1541 +#: hardware.xml:1075 #, 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:1550 +#: hardware.xml:1084 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1551 +#: hardware.xml:1085 #, no-c-format msgid "Laptops are also supported and nowadays most laptops work out of the box. In case a laptop contains specialized or proprietary hardware, some specific functions may not be supported. To see if your particular laptop works well with GNU/Linux, see for example the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>." msgstr "" #. Tag: title -#: hardware.xml:1563 hardware.xml:1586 hardware.xml:1606 hardware.xml:1629 +#: hardware.xml:1097 hardware.xml:1120 hardware.xml:1140 hardware.xml:1163 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1564 +#: hardware.xml:1098 #, 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 has been compiled with SMP support. The standard kernel is also usable on non-SMP systems, but has a slight overhead which will cause a small reduction in performance. For normal system use this will hardly be noticable." msgstr "" #. Tag: para -#: hardware.xml:1573 +#: hardware.xml:1107 #, 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:1588 +#: hardware.xml:1122 #, 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 has been 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:1597 +#: hardware.xml:1131 #, 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:1607 +#: hardware.xml:1141 #, 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:1616 +#: hardware.xml:1150 #, 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:1630 +#: hardware.xml:1164 #, 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:1640 +#: hardware.xml:1174 #, 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:1646 +#: hardware.xml:1180 #, 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:1657 +#: hardware.xml:1191 #, no-c-format msgid "Graphics Card Support" msgstr "" #. Tag: para -#: hardware.xml:1658 +#: hardware.xml:1192 #, 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:1666 +#: hardware.xml:1200 #, 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:1675 +#: hardware.xml:1209 #, no-c-format msgid "The X.Org X Window System is only supported on the SGI Indy and the O2." msgstr "" #. Tag: para -#: hardware.xml:1680 +#: hardware.xml:1214 #, 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:1690 +#: hardware.xml:1224 #, 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:1712 +#: hardware.xml:1246 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:1713 +#: hardware.xml:1247 #, no-c-format msgid "Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1722 +#: hardware.xml:1256 #, no-c-format msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:" msgstr "" #. Tag: para -#: hardware.xml:1728 +#: hardware.xml:1262 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:1733 +#: hardware.xml:1267 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:1738 +#: hardware.xml:1272 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:1743 +#: hardware.xml:1277 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:1748 +#: hardware.xml:1282 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:1755 +#: hardware.xml:1289 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:1760 +#: hardware.xml:1294 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:1765 +#: hardware.xml:1299 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:1770 +#: hardware.xml:1304 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:1779 +#: hardware.xml:1313 #, no-c-format msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided. The major exception is the IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a proprietary microcode for the operation of its built-in Ethernet device. Unofficial images for Linksys NSLU2 with this proprietary microcode can be obtained from the <ulink url=\"&url-slug-firmware;\">Slug-Firmware site</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1789 +#: hardware.xml:1323 #, no-c-format msgid "ISDN is supported, but not during the installation." msgstr "" #. Tag: title -#: hardware.xml:1796 +#: hardware.xml:1330 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:1797 +#: hardware.xml:1331 #, no-c-format msgid "Wireless networking is in general supported as well and a growing number of wireless adapters is supported by the official Linux kernel, although many of them do require firmware to be loaded. Wireless NICs that are not supported by the official Linux kernel can generally be made to work under &debian;, but are not supported during the installation." msgstr "" #. Tag: para -#: hardware.xml:1805 +#: hardware.xml:1339 #, no-c-format msgid "The use of wireless networking during installation is still under development and whether it will work depends on the type of adaptor and the configuration of your wireless access point. 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." msgstr "" #. Tag: para -#: hardware.xml:1817 +#: hardware.xml:1351 #, 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:1831 +#: hardware.xml:1365 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:1832 +#: hardware.xml:1366 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:1839 +#: hardware.xml:1373 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:1841 +#: hardware.xml:1375 #, 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:1851 +#: hardware.xml:1385 #, no-c-format msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>." msgstr "" #. Tag: para -#: hardware.xml:1859 +#: hardware.xml:1393 #, no-c-format msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted." msgstr "" #. Tag: title -#: hardware.xml:1872 +#: hardware.xml:1406 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:1874 +#: hardware.xml:1408 #, no-c-format msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." msgstr "" #. Tag: title -#: hardware.xml:1889 +#: hardware.xml:1423 #, no-c-format msgid "Braille Displays" msgstr "" #. Tag: para -#: hardware.xml:1890 +#: hardware.xml:1424 #, no-c-format msgid "Support for braille displays is determined by the underlying support found in <classname>brltty</classname>. Most displays work under <classname>brltty</classname>, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the <ulink url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian; &release; ships with <classname>brltty</classname> version &brlttyver;." msgstr "" #. Tag: title -#: hardware.xml:1904 +#: hardware.xml:1438 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: hardware.xml:1905 +#: hardware.xml:1439 #, no-c-format msgid "Support for hardware speech synthesis devices is determined by the underlying support found in <classname>speakup</classname>. <classname>speakup</classname> only supports integrated boards and external devices connected to a serial port (no USB or serial-to-USB adapters are supported). Details on supported hardware speech synthesis devices can be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> website</ulink>. &debian; &release; ships with <classname>speakup</classname> version &speakupver;." msgstr "" #. Tag: title -#: hardware.xml:1925 +#: hardware.xml:1459 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:1926 +#: hardware.xml:1460 #, 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:1932 +#: hardware.xml:1466 #, no-c-format msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>)." msgstr "" #. Tag: para -#: hardware.xml:1938 +#: hardware.xml:1472 #, 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:1944 +#: hardware.xml:1478 #, 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:1950 +#: hardware.xml:1484 #, no-c-format msgid "The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." msgstr "" #. Tag: title -#: hardware.xml:1962 +#: hardware.xml:1496 #, no-c-format msgid "Devices Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:1963 +#: hardware.xml:1497 #, no-c-format msgid "Besides the availability of a device driver, some hardware also requires so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware." msgstr "" #. Tag: para -#: hardware.xml:1971 +#: hardware.xml:1505 #, no-c-format msgid "In most cases firmware is non-free according to the criteria used by the &debian; project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if &debian; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive." msgstr "" #. Tag: para -#: hardware.xml:1980 +#: hardware.xml:1514 #, no-c-format msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a floppy disk or USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation." msgstr "" #. Tag: title -#: hardware.xml:1996 +#: hardware.xml:1530 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" #. Tag: para -#: hardware.xml:1998 +#: hardware.xml:1532 #, 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:2006 +#: hardware.xml:1540 #, 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:2014 +#: hardware.xml:1548 #, 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:2025 +#: hardware.xml:1559 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:2026 +#: hardware.xml:1560 #, 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:2033 +#: hardware.xml:1567 #, 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:2045 +#: hardware.xml:1579 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:2046 +#: hardware.xml:1580 #, 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:2059 +#: hardware.xml:1593 #, no-c-format msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes it being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" #. Tag: para -#: hardware.xml:2080 +#: hardware.xml:1614 #, 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:2097 +#: hardware.xml:1631 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:2099 +#: hardware.xml:1633 #, 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:2110 +#: hardware.xml:1644 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:2111 +#: hardware.xml:1645 #, 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:2117 +#: hardware.xml:1651 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:2124 +#: hardware.xml:1658 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:2126 +#: hardware.xml:1660 #, 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:2133 +#: hardware.xml:1667 #, 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:2145 +#: hardware.xml:1679 #, no-c-format msgid "SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux." msgstr "" #. Tag: para -#: hardware.xml:2151 +#: hardware.xml:1685 #, 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:2156 -#, 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:2165 +#: hardware.xml:1690 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines." msgstr "" #. Tag: para -#: hardware.xml:2169 +#: hardware.xml:1694 #, 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." msgstr "" #. Tag: title -#: hardware.xml:2183 +#: hardware.xml:1708 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:2185 +#: hardware.xml:1710 #, 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:2191 +#: hardware.xml:1716 #, 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:2199 +#: hardware.xml:1724 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:2201 +#: hardware.xml:1726 #, 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:2213 +#: hardware.xml:1738 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:2215 +#: hardware.xml:1740 #, no-c-format msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP." msgstr "" #. Tag: para -#: hardware.xml:2225 +#: hardware.xml:1750 #, no-c-format msgid "You can also <emphasis>boot</emphasis> the installation system over the network. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:2231 +#: hardware.xml:1756 #, no-c-format msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." msgstr "" #. Tag: title -#: hardware.xml:2239 +#: hardware.xml:1764 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:2241 +#: hardware.xml:1766 #, no-c-format msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." msgstr "" #. Tag: title -#: hardware.xml:2253 +#: hardware.xml:1778 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:2255 +#: hardware.xml:1780 #, 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:2265 +#: hardware.xml:1790 #, no-c-format msgid "Generally, the Debian installation system includes support for floppies, IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." msgstr "" #. Tag: para -#: hardware.xml:2272 +#: hardware.xml:1797 #, no-c-format msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or PATA — are supported. SATA and SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." msgstr "" #. Tag: para -#: hardware.xml:2280 +#: hardware.xml:1805 #, 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:2313 -#, 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:2322 +#: hardware.xml:1838 #, 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:2328 +#: hardware.xml:1844 #, 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:2334 +#: hardware.xml:1850 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:2339 +#: hardware.xml:1855 #, 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:2356 +#: hardware.xml:1872 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:2358 +#: hardware.xml:1874 #, no-c-format msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>." msgstr "" #. Tag: para -#: hardware.xml:2365 +#: hardware.xml:1881 #, no-c-format msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users." msgstr "" diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot index ed4795fad..92bbc55bd 100644 --- a/po/pot/install-methods.pot +++ b/po/pot/install-methods.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2009-11-02 22:05+0000\n" +"POT-Creation-Date: 2009-11-02 22:19+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" @@ -81,163 +81,139 @@ msgid "The installation images are located on each Debian mirror in the director msgstr "" #. Tag: title -#: install-methods.xml:112 -#, no-c-format -msgid "Alpha Installation Files" -msgstr "" - -#. Tag: para #: install-methods.xml:113 #, no-c-format -msgid "If you choose to boot from ARC console firmware using <command>MILO</command>, you will also need to prepare a disk containing <command>MILO</command> and <command>LINLOAD.EXE</command> from the provided disk images. See <xref linkend=\"alpha-firmware\"/> for more information on Alpha firmware and boot loaders. The floppy images can be found in the <filename>MILO</filename> directory as <filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>." -msgstr "" - -#. Tag: para -#: install-methods.xml:124 -#, no-c-format -msgid "Unfortunately, these <command>MILO</command> images could not be tested and might not work for all subarchitectures. If you find it doesn't work for you, try copying the appropriate <command>MILO</command> binary onto the floppy (<ulink url=\"&disturlftp;main/disks-alpha/current/MILO/\"></ulink>). Note that those <command>MILO</command>s don't support ext2 <quote>sparse superblocks</quote>, so you can't use them to load kernels from newly generated ext2 file systems. As a workaround, you can put your kernel onto the FAT partition next to the <command>MILO</command>." -msgstr "" - -#. Tag: para -#: install-methods.xml:136 -#, no-c-format -msgid "<command>MILO</command> binaries are platform-specific. See <xref linkend=\"alpha-cpus\"/> to determine the appropriate <command>MILO</command> image for your Alpha platform." -msgstr "" - -#. Tag: title -#: install-methods.xml:151 -#, no-c-format msgid "NSLU2 Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:152 +#: install-methods.xml:114 #, no-c-format msgid "A firmware image is provided for the Linksys NSLU2 which will automatically boot <classname>debian-installer</classname>. This image can be uploaded via the Linksys web frontend or with upslug2. This firmware image can be obtained from &nslu2-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:164 +#: install-methods.xml:126 #, no-c-format msgid "Thecus N2100 Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:165 +#: install-methods.xml:127 #, no-c-format msgid "A firmware image is provided for the Thecus N2100 which will automatically boot <classname>debian-installer</classname>. This image can be installed using the Thecus firmware upgrade process. This firmware image can be obtained from &n2100-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:176 +#: install-methods.xml:138 #, no-c-format msgid "GLAN Tank Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:177 +#: install-methods.xml:139 #, no-c-format msgid "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install Debian. These images can be obtained from &glantank-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:187 +#: install-methods.xml:149 #, no-c-format msgid "Kurobox Pro Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:188 +#: install-methods.xml:150 #, no-c-format msgid "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install Debian. These images can be obtained from &kuroboxpro-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:198 +#: install-methods.xml:160 #, no-c-format msgid "HP mv2120 Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:199 +#: install-methods.xml:161 #, no-c-format msgid "A firmware image is provided for the HP mv2120 which will automatically boot <classname>debian-installer</classname>. This image can be installed with uphpmvault on Linux and other systems and with the HP Media Vault Firmware Recovery Utility on Windows. The firmware image can be obtained from &mv2120-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:211 +#: install-methods.xml:173 #, no-c-format msgid "QNAP Turbo Station Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:212 +#: install-methods.xml:174 #, no-c-format msgid "The QNAP Turbo Station (TS-109, TS-209 and TS-409) requires a kernel and ramdisk which can be obtained from &qnap-firmware-img;. A script is provided to write these images to flash." msgstr "" #. Tag: title -#: install-methods.xml:262 +#: install-methods.xml:224 #, no-c-format msgid "Creating an IPL tape" msgstr "" #. Tag: para -#: install-methods.xml:264 +#: install-methods.xml:226 #, no-c-format msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>." msgstr "" #. Tag: title -#: install-methods.xml:288 +#: install-methods.xml:250 #, no-c-format msgid "Creating Floppies from Disk Images" msgstr "" #. Tag: para -#: install-methods.xml:289 +#: install-methods.xml:251 #, no-c-format msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means." msgstr "" #. Tag: para -#: install-methods.xml:294 +#: install-methods.xml:256 #, no-c-format msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives." msgstr "" #. Tag: para -#: install-methods.xml:299 +#: install-methods.xml:261 #, no-c-format msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy." msgstr "" #. Tag: para -#: install-methods.xml:310 +#: install-methods.xml:272 #, no-c-format msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms." msgstr "" #. Tag: para -#: install-methods.xml:316 +#: install-methods.xml:278 #, no-c-format msgid "Before you can create the floppies, you will first need to download them from one of the Debian mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>" msgstr "" #. Tag: para -#: install-methods.xml:324 +#: install-methods.xml:286 #, no-c-format msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally." msgstr "" #. Tag: title -#: install-methods.xml:332 +#: install-methods.xml:294 #, no-c-format msgid "Writing Disk Images From a Linux or Unix System" msgstr "" #. Tag: para -#: install-methods.xml:333 +#: install-methods.xml:295 #, no-c-format msgid "" "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n" @@ -246,259 +222,259 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:354 +#: install-methods.xml:316 #, no-c-format msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>" msgstr "" #. Tag: para -#: install-methods.xml:375 +#: install-methods.xml:337 #, no-c-format msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it." msgstr "" #. Tag: title -#: install-methods.xml:393 +#: install-methods.xml:355 #, no-c-format msgid "Writing Disk Images From DOS, Windows, or OS/2" msgstr "" #. Tag: para -#: install-methods.xml:395 +#: install-methods.xml:357 #, no-c-format msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies." msgstr "" #. Tag: para -#: install-methods.xml:400 +#: install-methods.xml:362 #, no-c-format msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work." msgstr "" #. Tag: para -#: install-methods.xml:408 +#: install-methods.xml:370 #, no-c-format msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory." msgstr "" #. Tag: para -#: install-methods.xml:414 +#: install-methods.xml:376 #, no-c-format msgid "These tools can be found on the Official Debian CD-ROMs under the <filename>/tools</filename> directory." msgstr "" #. Tag: title -#: install-methods.xml:427 +#: install-methods.xml:389 #, no-c-format msgid "Writing Disk Images From MacOS" msgstr "" #. Tag: para -#: install-methods.xml:428 +#: install-methods.xml:390 #, no-c-format msgid "An AppleScript, <application>Make Debian Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it." msgstr "" #. Tag: para -#: install-methods.xml:439 +#: install-methods.xml:401 #, no-c-format msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities." msgstr "" #. Tag: title -#: install-methods.xml:450 +#: install-methods.xml:412 #, no-c-format msgid "Writing Disk Images with <command>Disk Copy</command>" msgstr "" #. Tag: para -#: install-methods.xml:451 +#: install-methods.xml:413 #, no-c-format msgid "If you are creating the floppy image from files which were originally on the official &debian; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a Debian mirror." msgstr "" #. Tag: para -#: install-methods.xml:460 +#: install-methods.xml:422 #, no-c-format msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file." msgstr "" #. Tag: para -#: install-methods.xml:467 +#: install-methods.xml:429 #, no-c-format msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields." msgstr "" #. Tag: para -#: install-methods.xml:474 +#: install-methods.xml:436 #, no-c-format msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted." msgstr "" #. Tag: para -#: install-methods.xml:483 +#: install-methods.xml:445 #, no-c-format msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>." msgstr "" #. Tag: para -#: install-methods.xml:490 +#: install-methods.xml:452 #, no-c-format msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy." msgstr "" #. Tag: title -#: install-methods.xml:505 +#: install-methods.xml:467 #, no-c-format msgid "Writing Disk Images with <command>suntar</command>" msgstr "" #. Tag: para -#: install-methods.xml:509 +#: install-methods.xml:471 #, no-c-format msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu." msgstr "" #. Tag: para -#: install-methods.xml:517 +#: install-methods.xml:479 #, no-c-format msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)." msgstr "" #. Tag: para -#: install-methods.xml:523 +#: install-methods.xml:485 #, no-c-format msgid "Select the <filename>root.bin</filename> file in the file-opening dialog." msgstr "" #. Tag: para -#: install-methods.xml:528 +#: install-methods.xml:490 #, no-c-format msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another." msgstr "" #. Tag: para -#: install-methods.xml:536 +#: install-methods.xml:498 #, no-c-format msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it." msgstr "" #. Tag: title -#: install-methods.xml:555 +#: install-methods.xml:517 #, no-c-format msgid "Preparing Files for USB Memory Stick Booting" msgstr "" #. Tag: para -#: install-methods.xml:557 +#: install-methods.xml:519 #, no-c-format msgid "There are two installation methods possible when booting from USB stick. The first is to install completely from the network. The second is to also copy a CD image onto the USB stick and use that as a source for packages, possibly in combination with a mirror. This second method is the more common." msgstr "" #. Tag: para -#: install-methods.xml:565 +#: install-methods.xml:527 #, no-c-format msgid "For the first installation method you'll need to download an installer image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>) and use the <quote>flexible way</quote> explained below to copy the files to the USB stick." msgstr "" #. Tag: para -#: install-methods.xml:573 +#: install-methods.xml:535 #, no-c-format msgid "Installation images for the second installation method can be found in the <filename>hd-media</filename> directory and either the <quote>easy way</quote> or the <quote>flexible way</quote> can be used to copy the image to the USB stick. For this installation method you will also need to download a CD image. The installation image and the CD image must be based on the same release of &d-i;. If they do not match you are likely to get errors<footnote> <para> The error message that is most likely to be displayed is that no kernel modules can be found. This means that the version of the kernel module udebs included on the CD image is different from the version of the running kernel. </para> </footnote> during the installation." msgstr "" #. Tag: para -#: install-methods.xml:592 +#: install-methods.xml:554 #, no-c-format msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>dmesg</command> after inserting it. To write to your stick, you may have to turn off its write protection switch." msgstr "" #. Tag: para -#: install-methods.xml:606 +#: install-methods.xml:568 #, no-c-format msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost." msgstr "" #. Tag: para -#: install-methods.xml:614 +#: install-methods.xml:576 #, no-c-format msgid "Note that the USB stick should be at least 256 MB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)." msgstr "" #. Tag: title -#: install-methods.xml:622 +#: install-methods.xml:584 #, no-c-format msgid "Copying the files — the easy way" msgstr "" #. Tag: para -#: install-methods.xml:623 +#: install-methods.xml:585 #, no-c-format msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) <phrase arch=\"x86\">as well as <classname>syslinux</classname> and its configuration file.</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</classname> and its configuration file.</phrase>" msgstr "" #. Tag: para -#: install-methods.xml:632 +#: install-methods.xml:594 #, no-c-format msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 256 MB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose. A second disadvantage is that you cannot copy a full CD image onto the USB stick, but only the smaller businesscard or netinst CD images." msgstr "" #. Tag: para -#: install-methods.xml:642 +#: install-methods.xml:604 #, no-c-format msgid "To use this image simply extract it directly to your USB stick:" msgstr "" #. Tag: screen -#: install-methods.xml:646 +#: install-methods.xml:608 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sdX</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:648 +#: install-methods.xml:610 #, no-c-format msgid "Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:" msgstr "" #. Tag: screen -#: install-methods.xml:654 +#: install-methods.xml:616 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sdX2</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:656 +#: install-methods.xml:618 #, no-c-format msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a Debian netinst or businesscard ISO image to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done." msgstr "" #. Tag: title -#: install-methods.xml:673 +#: install-methods.xml:635 #, no-c-format msgid "Copying the files — the flexible way" msgstr "" #. Tag: para -#: install-methods.xml:674 +#: install-methods.xml:636 #, no-c-format msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that — if the capacity of your USB stick is large enough — you have the option of copying a full CD ISO image to it." msgstr "" #. Tag: title -#: install-methods.xml:689 install-methods.xml:786 +#: install-methods.xml:651 install-methods.xml:748 #, no-c-format msgid "Partitioning the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:690 +#: install-methods.xml:652 #, no-c-format msgid "We will show how to set up the memory stick to use the first partition, instead of the entire device." msgstr "" #. Tag: para -#: install-methods.xml:695 +#: install-methods.xml:657 #, no-c-format msgid "" "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition, and then create the filesystem using: <informalexample><screen>\n" @@ -507,13 +483,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:709 +#: install-methods.xml:671 #, no-c-format msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <classname>lilo</classname>) should work, it's convenient to use <classname>syslinux</classname>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para -#: install-methods.xml:719 +#: install-methods.xml:681 #, no-c-format msgid "" "To put <classname>syslinux</classname> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n" @@ -522,19 +498,19 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:736 install-methods.xml:833 +#: install-methods.xml:698 install-methods.xml:795 #, no-c-format msgid "Adding the installer image" msgstr "" #. Tag: para -#: install-methods.xml:737 +#: install-methods.xml:699 #, no-c-format msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) and copy the following installer image files to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> </itemizedlist> You can choose between either the regular version or the graphical version of the installer. The latter can be found in the <filename>gtk</filename> subdirectory. If you want to rename the files, please note that <classname>syslinux</classname> can only process DOS (8.3) file names." msgstr "" #. Tag: para -#: install-methods.xml:761 +#: install-methods.xml:723 #, no-c-format msgid "" "Next you should create a <filename>syslinux.cfg</filename> configuration file, which at a bare minimum should contain the following two lines: <informalexample><screen>\n" @@ -544,13 +520,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:771 install-methods.xml:873 +#: install-methods.xml:733 install-methods.xml:835 #, no-c-format msgid "If you used an <filename>hd-media</filename> image, you should now copy a Debian ISO image (businesscard, netinst or full CD image; be sure to select one that fits) onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)." msgstr "" #. Tag: para -#: install-methods.xml:787 +#: install-methods.xml:749 #, no-c-format msgid "" "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n" @@ -559,13 +535,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:804 +#: install-methods.xml:766 #, no-c-format msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para -#: install-methods.xml:813 +#: install-methods.xml:775 #, no-c-format msgid "" "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n" @@ -578,37 +554,37 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:834 +#: install-methods.xml:796 #, no-c-format msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) and copy the following installer image files to the stick:" msgstr "" #. Tag: para -#: install-methods.xml:841 +#: install-methods.xml:803 #, no-c-format msgid "<filename>vmlinux</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:846 +#: install-methods.xml:808 #, no-c-format msgid "<filename>initrd.gz</filename> (initial ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:851 +#: install-methods.xml:813 #, no-c-format msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" msgstr "" #. Tag: para -#: install-methods.xml:856 +#: install-methods.xml:818 #, no-c-format msgid "<filename>boot.msg</filename> (optional boot message)" msgstr "" #. Tag: para -#: install-methods.xml:863 +#: install-methods.xml:825 #, no-c-format msgid "" "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n" @@ -626,259 +602,253 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:888 +#: install-methods.xml:850 #, no-c-format msgid "Booting the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:889 +#: install-methods.xml:851 #, no-c-format msgid "If your system refuses to boot from the memory stick, the stick may contain an invalid master boot record (MBR). To fix this, use the <command>install-mbr</command> command from the package <classname>mbr</classname>:" msgstr "" #. Tag: screen -#: install-methods.xml:896 +#: install-methods.xml:858 #, no-c-format msgid "# install-mbr /dev/<replaceable>sdX</replaceable>" msgstr "" #. Tag: title -#: install-methods.xml:907 +#: install-methods.xml:869 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "" #. Tag: para -#: install-methods.xml:908 +#: install-methods.xml:870 #, no-c-format msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS." msgstr "" #. Tag: para -#: install-methods.xml:914 +#: install-methods.xml:876 #, no-c-format msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks." msgstr "" #. Tag: para -#: install-methods.xml:921 +#: install-methods.xml:883 #, no-c-format msgid "The installer cannot boot from files on an NTFS file system." msgstr "" #. Tag: para -#: install-methods.xml:925 +#: install-methods.xml:887 #, no-c-format msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download." msgstr "" #. Tag: para -#: install-methods.xml:936 +#: install-methods.xml:898 #, no-c-format msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model." msgstr "" #. Tag: title -#: install-methods.xml:945 +#: install-methods.xml:907 #, no-c-format msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: install-methods.xml:947 +#: install-methods.xml:909 #, no-c-format msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>." msgstr "" #. Tag: para -#: install-methods.xml:953 +#: install-methods.xml:915 #, no-c-format msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel." msgstr "" #. Tag: para -#: install-methods.xml:959 +#: install-methods.xml:921 #, no-c-format msgid "Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>." msgstr "" #. Tag: para -#: install-methods.xml:966 +#: install-methods.xml:928 #, no-c-format msgid "<filename>vmlinuz</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:971 +#: install-methods.xml:933 #, no-c-format msgid "<filename>initrd.gz</filename> (ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:978 +#: install-methods.xml:940 #, no-c-format msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>." msgstr "" #. Tag: title -#: install-methods.xml:988 +#: install-methods.xml:950 #, no-c-format msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:989 +#: install-methods.xml:951 #, no-c-format msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your Debian installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model." msgstr "" #. Tag: para -#: install-methods.xml:1002 +#: install-methods.xml:964 #, no-c-format msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on Debian http/ftp mirrors and official Debian CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder." msgstr "" #. Tag: title -#: install-methods.xml:1022 +#: install-methods.xml:984 #, no-c-format msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1023 +#: install-methods.xml:985 #, no-c-format msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs." msgstr "" #. Tag: para -#: install-methods.xml:1034 +#: install-methods.xml:996 #, no-c-format msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the Debian archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)." msgstr "" #. Tag: filename -#: install-methods.xml:1044 install-methods.xml:1399 +#: install-methods.xml:1006 install-methods.xml:1344 #, no-c-format msgid "vmlinux" msgstr "" #. Tag: filename -#: install-methods.xml:1049 install-methods.xml:1404 +#: install-methods.xml:1011 install-methods.xml:1349 #, no-c-format msgid "initrd.gz" msgstr "" #. Tag: filename -#: install-methods.xml:1054 install-methods.xml:1409 +#: install-methods.xml:1016 install-methods.xml:1354 #, no-c-format msgid "yaboot" msgstr "" #. Tag: filename -#: install-methods.xml:1059 install-methods.xml:1414 +#: install-methods.xml:1021 install-methods.xml:1359 #, no-c-format msgid "yaboot.conf" msgstr "" #. Tag: para -#: install-methods.xml:1064 +#: install-methods.xml:1026 #, no-c-format msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer." msgstr "" #. Tag: para -#: install-methods.xml:1072 +#: install-methods.xml:1034 #, no-c-format msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1085 +#: install-methods.xml:1047 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "" #. Tag: para -#: install-methods.xml:1086 +#: install-methods.xml:1048 #, no-c-format msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine." msgstr "" #. Tag: para -#: install-methods.xml:1094 +#: install-methods.xml:1056 #, no-c-format msgid "You need to set up a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>." msgstr "" #. Tag: para -#: install-methods.xml:1101 +#: install-methods.xml:1063 #, no-c-format msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP." msgstr "" #. Tag: para -#: install-methods.xml:1115 +#: install-methods.xml:1077 #, no-c-format msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP." msgstr "" #. Tag: para -#: install-methods.xml:1121 -#, no-c-format -msgid "Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM console will <emphasis>not</emphasis> use RARP to obtain its IP address, and therefore you must use BOOTP for net booting your Alpha<footnote> <para> Alpha systems can also be net-booted using the DECNet MOP (Maintenance Operations Protocol), but this is not covered here. Presumably, your local OpenVMS operator will be happy to assist you should you have some burning need to use MOP to boot Linux on your Alpha. </para> </footnote>. You can also enter the IP configuration for network interfaces directly in the SRM console." -msgstr "" - -#. Tag: para -#: install-methods.xml:1138 +#: install-methods.xml:1083 #, no-c-format msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in Debian." msgstr "" #. Tag: para -#: install-methods.xml:1143 +#: install-methods.xml:1088 #, no-c-format msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux." msgstr "" #. Tag: para -#: install-methods.xml:1151 +#: install-methods.xml:1096 #, no-c-format msgid "To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> support. On a &debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</classname> packages qualify; we recommend <classname>tftpd-hpa</classname>." msgstr "" #. Tag: title -#: install-methods.xml:1169 +#: install-methods.xml:1114 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para -#: install-methods.xml:1170 +#: install-methods.xml:1115 #, no-c-format msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>." msgstr "" #. Tag: para -#: install-methods.xml:1182 +#: install-methods.xml:1127 #, no-c-format msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)." msgstr "" #. Tag: title -#: install-methods.xml:1204 +#: install-methods.xml:1149 #, no-c-format msgid "Setting up a BOOTP server" msgstr "" #. Tag: para -#: install-methods.xml:1205 +#: install-methods.xml:1150 #, no-c-format msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively." msgstr "" #. Tag: para -#: install-methods.xml:1213 +#: install-methods.xml:1158 #, no-c-format msgid "" "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run Debian, the line in question should look like: <informalexample><screen>\n" @@ -895,25 +865,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1246 +#: install-methods.xml:1191 #, no-c-format msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1268 +#: install-methods.xml:1213 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1269 +#: install-methods.xml:1214 #, no-c-format msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):" msgstr "" #. Tag: screen -#: install-methods.xml:1276 +#: install-methods.xml:1221 #, no-c-format msgid "" "option domain-name \"example.com\";\n" @@ -938,25 +908,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1278 +#: install-methods.xml:1223 #, no-c-format msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP." msgstr "" #. Tag: para -#: install-methods.xml:1288 +#: install-methods.xml:1233 #, no-c-format msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1296 +#: install-methods.xml:1241 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1297 +#: install-methods.xml:1242 #, no-c-format msgid "" "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n" @@ -991,13 +961,13 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1313 +#: install-methods.xml:1258 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1314 +#: install-methods.xml:1259 #, no-c-format msgid "" "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled. This is usually enabled by having something like the following line in <filename>/etc/inetd.conf</filename>: <informalexample><screen>\n" @@ -1006,19 +976,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1326 +#: install-methods.xml:1271 #, no-c-format msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/var/lib/tftpboot</filename>. You may have to adjust the configuration examples in this section accordingly." msgstr "" #. Tag: para -#: install-methods.xml:1336 +#: install-methods.xml:1281 #, no-c-format msgid "Look in <filename>/etc/inetd.conf</filename> and remember the directory which is used as the argument of <command>in.tftpd</command><footnote> <para> All <command>in.tftpd</command> alternatives available in Debian should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors. </para> </footnote>; you'll need that below. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>." msgstr "" #. Tag: para -#: install-methods.xml:1356 +#: install-methods.xml:1301 #, no-c-format msgid "" "If you intend to install Debian on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n" @@ -1029,61 +999,49 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1378 +#: install-methods.xml:1323 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1379 +#: install-methods.xml:1324 #, no-c-format msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards." msgstr "" #. Tag: para -#: install-methods.xml:1388 +#: install-methods.xml:1333 #, no-c-format msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the <filename>netboot/</filename> directory:" msgstr "" #. Tag: filename -#: install-methods.xml:1419 +#: install-methods.xml:1364 #, no-c-format msgid "boot.msg" msgstr "" #. Tag: para -#: install-methods.xml:1424 +#: install-methods.xml:1369 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: para -#: install-methods.xml:1432 +#: install-methods.xml:1377 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: title -#: install-methods.xml:1444 -#, no-c-format -msgid "Alpha TFTP Booting" -msgstr "" - -#. Tag: para -#: install-methods.xml:1445 -#, no-c-format -msgid "On Alpha, you must specify the filename (as a relative path to the boot image directory) using the <userinput>-file</userinput> argument to the SRM <userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</userinput> environment variable. Alternatively, the filename can be given via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</userinput> directive). Unlike Open Firmware, there is <emphasis>no default filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a filename by either one of these methods." -msgstr "" - -#. Tag: title -#: install-methods.xml:1460 +#: install-methods.xml:1389 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1461 +#: install-methods.xml:1390 #, no-c-format msgid "" "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n" @@ -1092,55 +1050,55 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1477 +#: install-methods.xml:1406 #, no-c-format msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested." msgstr "" #. Tag: para -#: install-methods.xml:1484 +#: install-methods.xml:1413 #, no-c-format msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in." msgstr "" #. Tag: title -#: install-methods.xml:1495 +#: install-methods.xml:1424 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1496 +#: install-methods.xml:1425 #, no-c-format msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>." msgstr "" #. Tag: title -#: install-methods.xml:1604 +#: install-methods.xml:1533 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1605 +#: install-methods.xml:1534 #, no-c-format msgid "For installing on multiple computers it's possible to do fully automatic installations. Debian packages intended for this include <classname>fai</classname> (which uses an install server), <classname>replicator</classname>, <classname>systemimager</classname>, <classname>autoinstall</classname>, and the Debian Installer itself." msgstr "" #. Tag: title -#: install-methods.xml:1618 +#: install-methods.xml:1547 #, no-c-format msgid "Automatic Installation Using the Debian Installer" msgstr "" #. Tag: para -#: install-methods.xml:1619 +#: install-methods.xml:1548 #, no-c-format msgid "The Debian Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process." msgstr "" #. Tag: para -#: install-methods.xml:1626 +#: install-methods.xml:1555 #, no-c-format msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>." msgstr "" diff --git a/po/pot/partitioning.pot b/po/pot/partitioning.pot index 90ccc5023..2ca1c97e6 100644 --- a/po/pot/partitioning.pot +++ b/po/pot/partitioning.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2009-11-02 22:05+0000\n" +"POT-Creation-Date: 2009-11-02 22:19+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" @@ -615,7 +615,7 @@ msgid "One key point when partitioning for Mac type disks is that the swap parti msgstr "" #. Tag: title -#: partitioning.xml:566 partitioning.xml:627 partitioning.xml:651 partitioning.xml:748 partitioning.xml:862 partitioning.xml:939 +#: partitioning.xml:566 partitioning.xml:590 partitioning.xml:687 partitioning.xml:801 partitioning.xml:878 #, no-c-format msgid "Partitioning for &arch-title;" msgstr "" @@ -623,113 +623,83 @@ msgstr "" #. Tag: para #: partitioning.xml:567 #, no-c-format -msgid "Booting Debian from the SRM console (the only disk boot method supported by &releasename;) requires you to have a BSD disk label, not a DOS partition table, on your boot disk. (Remember, the SRM boot block is incompatible with MS-DOS partition tables — see <xref linkend=\"alpha-firmware\"/>.) As a result, <command>partman</command> creates BSD disk labels when running on &architecture;, but if your disk has an existing DOS partition table the existing partitions will need to be deleted before <command>partman</command> can convert it to use a disk label." -msgstr "" - -#. Tag: para -#: partitioning.xml:578 -#, no-c-format -msgid "If you have chosen to use <command>fdisk</command> to partition your disk, and the disk that you have selected for partitioning does not already contain a BSD disk label, you must use the <quote>b</quote> command to enter disk label mode." -msgstr "" - -#. Tag: para -#: partitioning.xml:585 -#, no-c-format -msgid "Unless you wish to use the disk you are partitioning from Tru64 Unix or one of the free 4.4BSD-Lite derived operating systems (FreeBSD, OpenBSD, or NetBSD), you should <emphasis>not</emphasis> create the third partition as a <quote>whole disk</quote> partition (i.e. with start and end sectors to span the whole disk), as this renders the disk incompatible with the tools used to make it bootable with aboot. This means that the disk configured by the installer for use as the Debian boot disk will be inaccessible to the operating systems mentioned earlier." -msgstr "" - -#. Tag: para -#: partitioning.xml:597 -#, no-c-format -msgid "Also, because <command>aboot</command> is written to the first few sectors of the disk (currently it occupies about 70 kilobytes, or 150 sectors), you <emphasis>must</emphasis> leave enough empty space at the beginning of the disk for it. In the past, it was suggested that you make a small partition at the beginning of the disk, to be left unformatted. For the same reason mentioned above, we now suggest that you do not do this on disks that will only be used by GNU/Linux. When using <command>partman</command>, a small partition will still be created for <command>aboot</command> for convenience reasons." -msgstr "" - -#. Tag: para -#: partitioning.xml:609 -#, no-c-format -msgid "For ARC installations, you should make a small FAT partition at the beginning of the disk to contain <command>MILO</command> and <command>linload.exe</command> — 5 megabytes should be sufficient, see <xref linkend=\"non-debian-partitioning\"/>. Unfortunately, making FAT file systems from the menu is not yet supported, so you'll have to do it manually from the shell using <command>mkdosfs</command> before attempting to install the boot loader." -msgstr "" - -#. Tag: para -#: partitioning.xml:628 -#, no-c-format msgid "PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere in the first 2GB. This is where the boot loader and an optional kernel and RAMdisk will be stored, so make it big enough for that — at least 4Mb (I like 8–16MB). An additional requirement of the firmware is that the Linux kernel must reside within the first 2GB of the disk. This is typically achieved by making the root ext2 partition fit entirely within the first 2GB of the disk. Alternatively you can create a small ext2 partition near the start of the disk and mount that on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. <filename>/boot</filename> needs to be big enough to hold whatever kernels (and backups) you might wish to load; 25–50MB is generally sufficient." msgstr "" #. Tag: para -#: partitioning.xml:652 +#: partitioning.xml:591 #, no-c-format msgid "If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing Debian, you may need to resize its partition to free up space for the Debian installation. The installer supports resizing of both FAT and NTFS filesystems; when you get to the installer's partitioning step, select the option <guimenuitem>Manual</guimenuitem> and then simply select an existing partition and change its size." msgstr "" #. Tag: para -#: partitioning.xml:662 +#: partitioning.xml:601 #, no-c-format msgid "The PC BIOS generally adds additional constraints for disk partitioning. There is a limit to how many <quote>primary</quote> and <quote>logical</quote> partitions a drive can contain. Additionally, with pre 1994–98 BIOSes, there are limits to where on the drive the BIOS can boot from. More information can be found in the <ulink url=\"&url-partition-howto;\">Linux Partition HOWTO</ulink> and the <ulink url=\"&url-phoenix-bios-faq-large-disk;\">Phoenix BIOS FAQ</ulink>, but this section will include a brief overview to help you plan most situations." msgstr "" #. Tag: para -#: partitioning.xml:673 +#: partitioning.xml:612 #, no-c-format msgid "<quote>Primary</quote> partitions are the original partitioning scheme for PC disks. However, there can only be four of them. To get past this limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By setting one of your primary partitions as an extended partition, you can subdivide all the space allocated to that partition into logical partitions. You can create up to 60 logical partitions per extended partition; however, you can only have one extended partition per drive." msgstr "" #. Tag: para -#: partitioning.xml:684 +#: partitioning.xml:623 #, no-c-format msgid "Linux limits the partitions per drive to 15 partitions for SCSI disks (3 usable primary partitions, 12 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions." msgstr "" #. Tag: para -#: partitioning.xml:694 +#: partitioning.xml:633 #, no-c-format msgid "If you have a large IDE disk, and are using neither LBA addressing, nor overlay drivers (sometimes provided by hard disk manufacturers), then the boot partition (the partition containing your kernel image) must be placed within the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation)." msgstr "" #. Tag: para -#: partitioning.xml:702 +#: partitioning.xml:641 #, no-c-format msgid "This restriction doesn't apply if you have a BIOS newer than around 1995–98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and Debian's alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once Linux is booted, no matter what BIOS your computer has, these restrictions no longer apply, since Linux does not use the BIOS for disk access." msgstr "" #. Tag: para -#: partitioning.xml:716 +#: partitioning.xml:655 #, no-c-format msgid "If you have a large disk, you might have to use cylinder translation techniques, which you can set from your BIOS setup program, such as LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). More information about issues with large disks can be found in the <ulink url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a cylinder translation scheme, and the BIOS does not support the large disk access extensions, then your boot partition has to fit within the <emphasis>translated</emphasis> representation of the 1024th cylinder." msgstr "" #. Tag: para -#: partitioning.xml:728 +#: partitioning.xml:667 #, no-c-format msgid "The recommended way of accomplishing this is to create a small (25–50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions." msgstr "" #. Tag: para -#: partitioning.xml:749 +#: partitioning.xml:688 #, no-c-format msgid "The <command>partman</command> disk partitioner is the default partitioning tool for the installer. It manages the set of partitions and their mount points to ensure that the disks and filesystems are properly configured for a successful installation. It actually uses <command>parted</command> to do the on-disk partitioning." msgstr "" #. Tag: title -#: partitioning.xml:761 +#: partitioning.xml:700 #, no-c-format msgid "EFI Recognized Formats" msgstr "" #. Tag: para -#: partitioning.xml:762 +#: partitioning.xml:701 #, no-c-format msgid "The IA-64 EFI firmware supports two partition table (or disk label) formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer recommended for IA-64 systems. Although the installer also provides <command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly." msgstr "" #. Tag: para -#: partitioning.xml:774 +#: partitioning.xml:713 #, no-c-format msgid "The automatic partitioning recipes for <command>partman</command> allocate an EFI partition as the first partition on the disk. You can also set up the partition under the <guimenuitem>Guided partitioning</guimenuitem> from the main menu in a manner similar to setting up a <emphasis>swap</emphasis> partition." msgstr "" #. Tag: para -#: partitioning.xml:782 +#: partitioning.xml:721 #, no-c-format msgid "" "The <command>partman</command> partitioner will handle most disk layouts. For those rare cases where it is necessary to manually set up a disk, you can use the shell as described above and run the <command>parted</command> utility directly using its command line interface. Assuming that you want to erase your whole disk and create a GPT table and some partitions, then something similar to the following command sequence could be used: <informalexample><screen>\n" @@ -744,97 +714,97 @@ msgid "" msgstr "" #. Tag: title -#: partitioning.xml:807 +#: partitioning.xml:746 #, no-c-format msgid "Boot Loader Partition Requirements" msgstr "" #. Tag: para -#: partitioning.xml:808 +#: partitioning.xml:747 #, no-c-format msgid "ELILO, the IA-64 boot loader, requires a partition containing a FAT file system with the <userinput>boot</userinput> flag set. The partition must be big enough to hold the boot loader and any kernels or RAMdisks you may wish to boot. A minimum size would be about 20MB, but if you expect to run with multiple kernels, then 128MB might be a better size." msgstr "" #. Tag: para -#: partitioning.xml:817 +#: partitioning.xml:756 #, no-c-format msgid "The EFI Boot Manager and the EFI Shell fully support the GPT table so the boot partition does not necessarily have to be the first partition or even on the same disk. This is convenient if you should forget to allocate the partition and only find out after you have formatted the other partitions on your disk(s). The <command>partman</command> partitioner checks for an EFI partition at the same time it checks for a properly set up <emphasis>root</emphasis> partition. This gives you an opportunity to correct the disk layout before the package install begins. The easiest way to correct this omission is to shrink the last partition of the disk to make enough free space for adding an EFI partition." msgstr "" #. Tag: para -#: partitioning.xml:832 +#: partitioning.xml:771 #, no-c-format msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem." msgstr "" #. Tag: title -#: partitioning.xml:840 +#: partitioning.xml:779 #, no-c-format msgid "EFI Diagnostic Partitions" msgstr "" #. Tag: para -#: partitioning.xml:841 +#: partitioning.xml:780 #, no-c-format msgid "The EFI firmware is significantly more sophisticated than the usual BIOS seen on most x86 PCs. Some system vendors take advantage of the ability of the EFI to access files and run programs from a hard disk filesystem to store diagnostics and EFI based system management utilities on the hard disk. This is a separate FAT format filesystem on the system disk. Consult the system documentation and accessories that come with the system for details. The easiest time to set up a diagnostics partition is at the same time you set up the EFI boot partition." msgstr "" #. Tag: para -#: partitioning.xml:863 +#: partitioning.xml:802 #, no-c-format msgid "SGI machines require an SGI disk label in order to make the system bootable from hard disk. It can be created in the fdisk expert menu. The thereby created volume header (partition number 9) should be at least 3MB large. If the volume header created is too small, you can simply delete partition number 9 and re-add it with a different size. Note that the volume header must start at sector 0." msgstr "" #. Tag: title -#: partitioning.xml:880 +#: partitioning.xml:819 #, no-c-format msgid "Partitioning Newer PowerMacs" msgstr "" #. Tag: para -#: partitioning.xml:881 +#: partitioning.xml:820 #, no-c-format msgid "If you are installing onto a NewWorld PowerMac you must create a special bootstrap partition to hold the boot loader. The size of this partition must have at least 819200 bytes and its partition type must be <emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not created with the <emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made bootable from the hard disk. This partition can easily be created by creating a new partition in <command>partman</command> and telling it to use it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</command> using the <userinput>b</userinput> command." msgstr "" #. Tag: para -#: partitioning.xml:894 +#: partitioning.xml:833 #, no-c-format msgid "The special partition type Apple_Bootstrap is required to prevent MacOS from mounting and damaging the bootstrap partition, as there are special modifications made to it in order for OpenFirmware to boot it automatically." msgstr "" #. Tag: para -#: partitioning.xml:901 +#: partitioning.xml:840 #, no-c-format msgid "Note that the bootstrap partition is only meant to hold 3 very small files: the <command>yaboot</command> binary, its configuration <filename>yaboot.conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</command>. It need not and must not be mounted on your file system nor have kernels or anything else copied to it. The <command>ybin</command> and <command>mkofboot</command> utilities are used to manipulate this partition." msgstr "" #. Tag: para -#: partitioning.xml:911 +#: partitioning.xml:850 #, no-c-format msgid "In order for OpenFirmware to automatically boot &debian; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts." msgstr "" #. Tag: para -#: partitioning.xml:923 +#: partitioning.xml:862 #, no-c-format msgid "Apple disks normally have several small driver partitions. If you intend to dual boot your machine with MacOSX, you should retain these partitions and a small HFS partition (800k is the minimum size). That is because MacOSX, on every boot, offers to initialize any disks which do not have active MacOS partitions and driver partitions." msgstr "" #. Tag: para -#: partitioning.xml:940 +#: partitioning.xml:879 #, no-c-format msgid "Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. The <keycap>s</keycap> key is used in <command>fdisk</command> to create Sun disk labels." msgstr "" #. Tag: para -#: partitioning.xml:948 +#: partitioning.xml:887 #, no-c-format msgid "Furthermore, on &arch-title; disks, make sure your first partition on your boot disk starts at cylinder 0. While this is required, it also means that the first partition will contain the partition table and the boot block, which are the first two sectors of the disk. You must <emphasis>not</emphasis> put swap on the first partition of the boot drive, since swap partitions do not preserve the first few sectors of the partition. You can put Ext2 or UFS partitions there; these will leave the partition table and the boot block alone." msgstr "" #. Tag: para -#: partitioning.xml:959 +#: partitioning.xml:898 #, no-c-format msgid "It is also advised that the third partition should be of type <quote>Whole disk</quote> (type 5), and contain the entire disk (from the first cylinder to the last). This is simply a convention of Sun disk labels, and helps the <command>SILO</command> boot loader keep its bearings." msgstr "" diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot index 72df60c6b..6375256f4 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: 2009-11-02 22:05+0000\n" +"POT-Creation-Date: 2009-11-02 22:19+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -263,1235 +263,1175 @@ msgstr "" #. Tag: ulink #: preparing.xml:291 #, no-c-format -msgid "Linux/Alpha FAQ" -msgstr "" - -#. Tag: ulink -#: preparing.xml:297 -#, no-c-format msgid "Linux for SPARC Processors FAQ" msgstr "" #. Tag: ulink -#: preparing.xml:303 +#: preparing.xml:297 #, no-c-format msgid "Linux/Mips website" msgstr "" #. Tag: title -#: preparing.xml:312 +#: preparing.xml:306 #, no-c-format msgid "&arch-title; Hardware References" msgstr "" #. Tag: para -#: preparing.xml:313 +#: preparing.xml:307 #, no-c-format msgid "Installation instructions and device drivers (DASD, XPRAM, Console, tape, z90 crypto, chandev, network) for Linux on &arch-title; using kernel 2.4" msgstr "" #. Tag: ulink -#: preparing.xml:325 +#: preparing.xml:319 #, no-c-format msgid "Device Drivers and Installation Commands" msgstr "" #. Tag: para -#: preparing.xml:330 +#: preparing.xml:324 #, no-c-format msgid "IBM Redbook describing how Linux can be combined with z/VM on zSeries and &arch-title; hardware." msgstr "" #. Tag: ulink -#: preparing.xml:340 +#: preparing.xml:334 #, no-c-format msgid "Linux for &arch-title;" msgstr "" #. Tag: para -#: preparing.xml:346 +#: preparing.xml:340 #, no-c-format msgid "IBM Redbook describing the Linux distributions available for the mainframe. It has no chapter about Debian but the basic installation concepts are the same across all &arch-title; distributions." msgstr "" #. Tag: ulink -#: preparing.xml:357 +#: preparing.xml:351 #, no-c-format msgid "Linux for IBM eServer zSeries and &arch-title;: Distributions" msgstr "" #. Tag: title -#: preparing.xml:367 +#: preparing.xml:361 #, no-c-format msgid "Finding Sources of Hardware Information" msgstr "" #. Tag: para -#: preparing.xml:368 +#: preparing.xml:362 #, no-c-format msgid "In many cases, the installer will be able to automatically detect your hardware. But to be prepared, we do recommend familiarizing yourself with your hardware before the install." msgstr "" #. Tag: para -#: preparing.xml:374 +#: preparing.xml:368 #, no-c-format msgid "Hardware information can be gathered from:" msgstr "" #. Tag: para -#: preparing.xml:381 +#: preparing.xml:375 #, no-c-format msgid "The manuals that come with each piece of hardware." msgstr "" #. Tag: para -#: preparing.xml:386 +#: preparing.xml:380 #, no-c-format msgid "The BIOS setup screens of your computer. You can view these screens when you start your computer by pressing a combination of keys. Check your manual for the combination. Often, it is the <keycap>Delete</keycap> key." msgstr "" #. Tag: para -#: preparing.xml:393 +#: preparing.xml:387 #, no-c-format msgid "The cases and boxes for each piece of hardware." msgstr "" #. Tag: para -#: preparing.xml:399 +#: preparing.xml:393 #, no-c-format msgid "The System window in the Windows Control Panel." msgstr "" #. Tag: para -#: preparing.xml:405 +#: preparing.xml:399 #, no-c-format msgid "System commands or tools in another operating system, including file manager displays. This source is especially useful for information about RAM and hard drive memory." msgstr "" #. Tag: para -#: preparing.xml:412 +#: preparing.xml:406 #, no-c-format msgid "Your system administrator or Internet Service Provider. These sources can tell you the settings you need to set up your networking and e-mail." msgstr "" #. Tag: title -#: preparing.xml:424 +#: preparing.xml:418 #, no-c-format msgid "Hardware Information Needed for an Install" msgstr "" #. Tag: entry -#: preparing.xml:428 +#: preparing.xml:422 #, no-c-format msgid "Hardware" msgstr "" #. Tag: entry -#: preparing.xml:428 +#: preparing.xml:422 #, no-c-format msgid "Information You Might Need" msgstr "" #. Tag: entry -#: preparing.xml:434 +#: preparing.xml:428 #, no-c-format msgid "Hard Drives" msgstr "" #. Tag: entry -#: preparing.xml:435 +#: preparing.xml:429 #, no-c-format msgid "How many you have." msgstr "" #. Tag: entry -#: preparing.xml:437 +#: preparing.xml:431 #, no-c-format msgid "Their order on the system." msgstr "" #. Tag: entry -#: preparing.xml:439 +#: preparing.xml:433 #, no-c-format msgid "Whether IDE (also known as PATA), SATA or SCSI." msgstr "" #. Tag: entry -#: preparing.xml:441 preparing.xml:493 +#: preparing.xml:435 preparing.xml:487 #, no-c-format msgid "Available free space." msgstr "" #. Tag: entry -#: preparing.xml:442 +#: preparing.xml:436 #, no-c-format msgid "Partitions." msgstr "" #. Tag: entry -#: preparing.xml:444 +#: preparing.xml:438 #, no-c-format msgid "Partitions where other operating systems are installed." msgstr "" #. Tag: entry -#: preparing.xml:448 +#: preparing.xml:442 #, no-c-format msgid "Monitor" msgstr "" #. Tag: entry -#: preparing.xml:449 preparing.xml:469 preparing.xml:475 preparing.xml:481 +#: preparing.xml:443 preparing.xml:463 preparing.xml:469 preparing.xml:475 #, no-c-format msgid "Model and manufacturer." msgstr "" #. Tag: entry -#: preparing.xml:451 +#: preparing.xml:445 #, no-c-format msgid "Resolutions supported." msgstr "" #. Tag: entry -#: preparing.xml:452 +#: preparing.xml:446 #, no-c-format msgid "Horizontal refresh rate." msgstr "" #. Tag: entry -#: preparing.xml:453 +#: preparing.xml:447 #, no-c-format msgid "Vertical refresh rate." msgstr "" #. Tag: entry -#: preparing.xml:455 +#: preparing.xml:449 #, no-c-format msgid "Color depth (number of colors) supported." msgstr "" #. Tag: entry -#: preparing.xml:457 +#: preparing.xml:451 #, no-c-format msgid "Screen size." msgstr "" #. Tag: entry -#: preparing.xml:460 +#: preparing.xml:454 #, no-c-format msgid "Mouse" msgstr "" #. Tag: entry -#: preparing.xml:461 +#: preparing.xml:455 #, no-c-format msgid "Type: serial, PS/2, or USB." msgstr "" #. Tag: entry -#: preparing.xml:463 +#: preparing.xml:457 #, no-c-format msgid "Port." msgstr "" #. Tag: entry -#: preparing.xml:464 +#: preparing.xml:458 #, no-c-format msgid "Manufacturer." msgstr "" #. Tag: entry -#: preparing.xml:465 +#: preparing.xml:459 #, no-c-format msgid "Number of buttons." msgstr "" #. Tag: entry -#: preparing.xml:468 preparing.xml:496 +#: preparing.xml:462 preparing.xml:490 #, no-c-format msgid "Network" msgstr "" #. Tag: entry -#: preparing.xml:471 preparing.xml:497 +#: preparing.xml:465 preparing.xml:491 #, no-c-format msgid "Type of adapter." msgstr "" #. Tag: entry -#: preparing.xml:474 +#: preparing.xml:468 #, no-c-format msgid "Printer" msgstr "" #. Tag: entry -#: preparing.xml:477 +#: preparing.xml:471 #, no-c-format msgid "Printing resolutions supported." msgstr "" #. Tag: entry -#: preparing.xml:480 +#: preparing.xml:474 #, no-c-format msgid "Video Card" msgstr "" #. Tag: entry -#: preparing.xml:483 +#: preparing.xml:477 #, no-c-format msgid "Video RAM available." msgstr "" #. Tag: entry -#: preparing.xml:485 +#: preparing.xml:479 #, no-c-format msgid "Resolutions and color depths supported (these should be checked against your monitor's capabilities)." msgstr "" #. Tag: entry -#: preparing.xml:490 +#: preparing.xml:484 #, no-c-format msgid "DASD" msgstr "" #. Tag: entry -#: preparing.xml:491 +#: preparing.xml:485 #, no-c-format msgid "Device number(s)." msgstr "" #. Tag: entry -#: preparing.xml:499 +#: preparing.xml:493 #, no-c-format msgid "Device numbers." msgstr "" #. Tag: entry -#: preparing.xml:500 +#: preparing.xml:494 #, no-c-format msgid "Relative adapter number for OSA cards." msgstr "" #. Tag: title -#: preparing.xml:508 +#: preparing.xml:502 #, no-c-format msgid "Hardware Compatibility" msgstr "" #. Tag: para -#: preparing.xml:510 +#: preparing.xml:504 #, no-c-format msgid "Many brand name products work without trouble on Linux. Moreover, hardware support in Linux is improving daily. However, Linux still does not run as many different types of hardware as some operating systems." msgstr "" #. Tag: para -#: preparing.xml:516 +#: preparing.xml:510 #, no-c-format msgid "In particular, Linux usually cannot run hardware that requires a running version of Windows to work." msgstr "" #. Tag: para -#: preparing.xml:521 +#: preparing.xml:515 #, no-c-format msgid "Although some Windows-specific hardware can be made to run on Linux, doing so usually requires extra effort. In addition, Linux drivers for Windows-specific hardware are usually specific to one Linux kernel. Therefore, they can quickly become obsolete." msgstr "" #. Tag: para -#: preparing.xml:528 +#: preparing.xml:522 #, no-c-format msgid "So called win-modems are the most common type of this hardware. However, printers and other equipment may also be Windows-specific." msgstr "" #. Tag: para -#: preparing.xml:533 +#: preparing.xml:527 #, no-c-format msgid "You can check hardware compatibility by:" msgstr "" #. Tag: para -#: preparing.xml:538 +#: preparing.xml:532 #, no-c-format msgid "Checking manufacturers' web sites for new drivers." msgstr "" #. Tag: para -#: preparing.xml:543 +#: preparing.xml:537 #, no-c-format msgid "Looking at web sites or manuals for information about emulation. Lesser known brands can sometimes use the drivers or settings for better-known ones." msgstr "" #. Tag: para -#: preparing.xml:550 +#: preparing.xml:544 #, no-c-format msgid "Checking hardware compatibility lists for Linux on web sites dedicated to your architecture." msgstr "" #. Tag: para -#: preparing.xml:556 +#: preparing.xml:550 #, no-c-format msgid "Searching the Internet for other users' experiences." msgstr "" #. Tag: title -#: preparing.xml:567 +#: preparing.xml:561 #, no-c-format msgid "Network Settings" msgstr "" #. Tag: para -#: preparing.xml:569 +#: preparing.xml:563 #, no-c-format msgid "If your computer is connected to a network 24 hours a day (i.e., an Ethernet or equivalent connection — not a PPP connection), you should ask your network's system administrator for this information." msgstr "" #. Tag: para -#: preparing.xml:576 +#: preparing.xml:570 #, no-c-format msgid "Your host name (you may be able to decide this on your own)." msgstr "" #. Tag: para -#: preparing.xml:581 +#: preparing.xml:575 #, no-c-format msgid "Your domain name." msgstr "" #. Tag: para -#: preparing.xml:586 +#: preparing.xml:580 #, no-c-format msgid "Your computer's IP address." msgstr "" #. Tag: para -#: preparing.xml:591 +#: preparing.xml:585 #, no-c-format msgid "The netmask to use with your network." msgstr "" #. Tag: para -#: preparing.xml:596 +#: preparing.xml:590 #, no-c-format msgid "The IP address of the default gateway system you should route to, if your network <emphasis>has</emphasis> a gateway." msgstr "" #. Tag: para -#: preparing.xml:602 +#: preparing.xml:596 #, no-c-format msgid "The system on your network that you should use as a DNS (Domain Name Service) server." msgstr "" #. Tag: para -#: preparing.xml:610 +#: preparing.xml:604 #, no-c-format msgid "On the other hand, if your administrator tells you that a DHCP server is available and is recommended, then you don't need this information because the DHCP server will provide it directly to your computer during the installation process." msgstr "" #. Tag: para -#: preparing.xml:617 +#: preparing.xml:611 #, no-c-format msgid "If you use a wireless network, you should also find out:" msgstr "" #. Tag: para -#: preparing.xml:622 +#: preparing.xml:616 #, no-c-format msgid "ESSID of your wireless network." msgstr "" #. Tag: para -#: preparing.xml:627 +#: preparing.xml:621 #, no-c-format msgid "WEP security key (if applicable)." msgstr "" #. Tag: title -#: preparing.xml:644 +#: preparing.xml:638 #, no-c-format msgid "Meeting Minimum Hardware Requirements" msgstr "" #. Tag: para -#: preparing.xml:645 +#: preparing.xml:639 #, no-c-format msgid "Once you have gathered information about your computer's hardware, check that your hardware will let you do the type of installation that you want to do." msgstr "" #. Tag: para -#: preparing.xml:651 +#: preparing.xml:645 #, no-c-format msgid "Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions." msgstr "" #. Tag: para -#: preparing.xml:657 +#: preparing.xml:651 #, no-c-format msgid "A Pentium 4, 1GHz system is the minimum recommended for a desktop system." msgstr "" #. Tag: para -#: preparing.xml:662 +#: preparing.xml:656 #, no-c-format msgid "Any OldWorld or NewWorld PowerPC can serve well as a desktop system." msgstr "" #. Tag: title -#: preparing.xml:669 +#: preparing.xml:663 #, no-c-format msgid "Recommended Minimum System Requirements" msgstr "" #. Tag: entry -#: preparing.xml:673 +#: preparing.xml:667 #, no-c-format msgid "Install Type" msgstr "" #. Tag: entry -#: preparing.xml:674 +#: preparing.xml:668 #, no-c-format msgid "RAM (minimal)" msgstr "" #. Tag: entry -#: preparing.xml:675 +#: preparing.xml:669 #, no-c-format msgid "RAM (recommended)" msgstr "" #. Tag: entry -#: preparing.xml:676 +#: preparing.xml:670 #, no-c-format msgid "Hard Drive" msgstr "" #. Tag: entry -#: preparing.xml:682 +#: preparing.xml:676 #, no-c-format msgid "No desktop" msgstr "" #. Tag: entry -#: preparing.xml:683 preparing.xml:688 +#: preparing.xml:677 preparing.xml:682 #, no-c-format msgid "64 megabytes" msgstr "" #. Tag: entry -#: preparing.xml:684 +#: preparing.xml:678 #, no-c-format msgid "256 megabytes" msgstr "" #. Tag: entry -#: preparing.xml:685 +#: preparing.xml:679 #, no-c-format msgid "1 gigabyte" msgstr "" #. Tag: entry -#: preparing.xml:687 +#: preparing.xml:681 #, no-c-format msgid "With Desktop" msgstr "" #. Tag: entry -#: preparing.xml:689 +#: preparing.xml:683 #, no-c-format msgid "512 megabytes" msgstr "" #. Tag: entry -#: preparing.xml:690 +#: preparing.xml:684 #, no-c-format msgid "5 gigabytes" msgstr "" #. Tag: para -#: preparing.xml:695 +#: preparing.xml:689 #, no-c-format msgid "The actual minimum memory requirements are a lot less then the numbers listed in this table. Depending on the architecture, it is possible to install Debian with as little as 20MB (for s390) to 48MB (for i386 and amd64). The same goes for the disk space requirements, especially if you pick and choose which applications to install; see <xref linkend=\"tasksel-size-list\"/> for additional information on disk space requirements." msgstr "" #. Tag: para -#: preparing.xml:705 +#: preparing.xml:699 #, no-c-format msgid "It is possible to run a graphical desktop environment on older or low-end systems, but in that case it is recommended to install a window manager that is less resource-hungry than those of the GNOME or KDE desktop environments; alternatives include <classname>xfce4</classname>, <classname>icewm</classname> and <classname>wmaker</classname>, but there are others to choose from." msgstr "" #. Tag: para -#: preparing.xml:714 +#: preparing.xml:708 #, no-c-format msgid "It is practically impossible to give general memory or disk space requirements for server installations as those very much depend on what the server is to be used for." msgstr "" #. Tag: para -#: preparing.xml:720 +#: preparing.xml:714 #, no-c-format msgid "Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data." msgstr "" #. Tag: para -#: preparing.xml:727 +#: preparing.xml:721 #, no-c-format msgid "Disk space required for the smooth operation of the &debian; system itself is taken into account in these recommended system requirements. Notably, the <filename>/var</filename> partition contains a lot of state information specific to Debian in addition to its regular contents, like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 40MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 200MB for <filename>/var</filename>, and a lot more if you install a graphical desktop environment." msgstr "" #. Tag: title -#: preparing.xml:751 +#: preparing.xml:745 #, no-c-format msgid "Pre-Partitioning for Multi-Boot Systems" msgstr "" #. Tag: para -#: preparing.xml:752 +#: preparing.xml:746 #, no-c-format msgid "Partitioning your disk simply refers to the act of breaking up your disk into sections. Each section is then independent of the others. It's roughly equivalent to putting up walls inside a house; if you add furniture to one room it doesn't affect any other room." msgstr "" #. Tag: para -#: preparing.xml:759 +#: preparing.xml:753 #, no-c-format msgid "Whenever this section talks about <quote>disks</quote> you should translate this into a DASD or VM minidisk in the &arch-title; world. Also a machine means an LPAR or VM guest in this case." msgstr "" #. Tag: para -#: preparing.xml:765 +#: preparing.xml:759 #, no-c-format -msgid "If you already have an operating system on your system <phrase arch=\"x86\"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> <phrase arch=\"alpha\"> (Tru64 (Digital UNIX), OpenVMS, Windows NT, FreeBSD, …) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, …) </phrase> and want to stick Linux on the same disk, you will need to repartition the disk. Debian requires its own hard disk partitions. It cannot be installed on Windows or MacOS partitions. It may be able to share some partitions with other Linux systems, but that's not covered here. At the very least you will need a dedicated partition for the Debian root." +msgid "If you already have an operating system on your system <phrase arch=\"x86\"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, …) </phrase> and want to stick Linux on the same disk, you will need to repartition the disk. Debian requires its own hard disk partitions. It cannot be installed on Windows or MacOS partitions. It may be able to share some partitions with other Linux systems, but that's not covered here. At the very least you will need a dedicated partition for the Debian root." msgstr "" #. Tag: para -#: preparing.xml:788 +#: preparing.xml:778 #, no-c-format msgid "You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase arch=\"x86\">, such as fdisk or PartitionMagic</phrase><phrase arch=\"powerpc\">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch=\"s390\">, such as the VM diskmap</phrase>. Partitioning tools always provide a way to show existing partitions without making changes." msgstr "" #. Tag: para -#: preparing.xml:797 +#: preparing.xml:787 #, no-c-format msgid "In general, changing a partition with a file system already on it will destroy any information there. Thus you should always make backups before doing any repartitioning. Using the analogy of the house, you would probably want to move all the furniture out of the way before moving a wall or you risk destroying it." msgstr "" #. Tag: emphasis -#: preparing.xml:807 +#: preparing.xml:797 #, no-c-format msgid "FIXME: write about HP-UX disks?" msgstr "" #. Tag: para -#: preparing.xml:809 +#: preparing.xml:799 #, no-c-format msgid "If your computer has more than one hard disk, you may want to dedicate one of the hard disks completely to Debian. If so, you don't need to partition that disk before booting the installation system; the installer's included partitioning program can handle the job nicely." msgstr "" #. Tag: para -#: preparing.xml:816 +#: preparing.xml:806 #, no-c-format msgid "If your machine has only one hard disk, and you would like to completely replace the current operating system with &debian;, you also can wait to partition as part of the installation process (<xref linkend=\"di-partition\"/>), after you have booted the installation system. However this only works if you plan to boot the installer system from tapes, CD-ROM or files on a connected machine. Consider: if you boot from files placed on the hard disk, and then partition that same hard disk within the installation system, thus erasing the boot files, you'd better hope the installation is successful the first time around. At the least in this case, you should have some alternate means of reviving your machine like the original system's installation tapes or CDs." msgstr "" #. Tag: para -#: preparing.xml:831 +#: preparing.xml:821 #, no-c-format msgid "If your machine already has multiple partitions, and enough space can be provided by deleting and replacing one or more of them, then you too can wait and use the Debian installer's partitioning program. You should still read through the material below, because there may be special circumstances like the order of the existing partitions within the partition map, that force you to partition before installing anyway." msgstr "" #. Tag: para -#: preparing.xml:841 +#: preparing.xml:831 #, no-c-format msgid "If your machine has a FAT or NTFS filesystem, as used by DOS and Windows, you can wait and use Debian installer's partitioning program to resize the filesystem." msgstr "" #. Tag: para -#: preparing.xml:847 +#: preparing.xml:837 #, no-c-format msgid "If none of the above apply, you'll need to partition your hard disk before starting the installation to create partitionable space for Debian. If some of the partitions will be owned by other operating systems, you should create those partitions using native operating system partitioning programs. We recommend that you do <emphasis>not</emphasis> attempt to create partitions for &debian; using another operating system's tools. Instead, you should just create the native operating system's partitions you will want to retain." msgstr "" #. Tag: para -#: preparing.xml:859 +#: preparing.xml:849 #, no-c-format msgid "If you are going to install more than one operating system on the same machine, you should install all other system(s) before proceeding with Linux installation. Windows and other OS installations may destroy your ability to start Linux, or encourage you to reformat non-native partitions." msgstr "" #. Tag: para -#: preparing.xml:867 +#: preparing.xml:857 #, no-c-format msgid "You can recover from these actions or avoid them, but installing the native system first saves you trouble." msgstr "" #. Tag: para -#: preparing.xml:872 +#: preparing.xml:862 #, no-c-format msgid "In order for OpenFirmware to automatically boot &debian; the Linux partitions should appear before all other partitions on the disk, especially MacOS boot partitions. This should be kept in mind when pre-partitioning; you should create a Linux placeholder partition to come <emphasis>before</emphasis> the other bootable partitions on the disk. (The small partitions dedicated to Apple disk drivers are not bootable.) You can delete the placeholder with the Linux partition tools later during the actual install, and replace it with Linux partitions." msgstr "" #. Tag: para -#: preparing.xml:884 +#: preparing.xml:874 #, no-c-format msgid "If you currently have one hard disk with one partition (a common setup for desktop computers), and you want to multi-boot the native operating system and Debian, you will need to:" msgstr "" #. Tag: para -#: preparing.xml:891 +#: preparing.xml:881 #, no-c-format msgid "Back up everything on the computer." msgstr "" #. Tag: para -#: preparing.xml:896 +#: preparing.xml:886 #, no-c-format msgid "Boot from the native operating system installer media such as CD-ROM or tapes. <phrase arch=\"powerpc\">When booting from a MacOS CD, hold the <keycap>c</keycap> key while booting to force the CD to become the active MacOS system.</phrase>" msgstr "" #. Tag: para -#: preparing.xml:906 +#: preparing.xml:896 #, no-c-format msgid "Use the native partitioning tools to create native system partition(s). Leave either a place holder partition or free space for &debian;." msgstr "" #. Tag: para -#: preparing.xml:913 +#: preparing.xml:903 #, no-c-format msgid "Install the native operating system on its new partition." msgstr "" #. Tag: para -#: preparing.xml:918 +#: preparing.xml:908 #, no-c-format msgid "Boot back into the native system to verify everything's OK, and to download the Debian installer boot files." msgstr "" #. Tag: para -#: preparing.xml:924 +#: preparing.xml:914 #, no-c-format msgid "Boot the Debian installer to continue installing Debian." msgstr "" #. Tag: title -#: preparing.xml:938 -#, no-c-format -msgid "Partitioning in Tru64 UNIX" -msgstr "" - -#. Tag: para -#: preparing.xml:939 -#, no-c-format -msgid "Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly known as OSF/1, uses the partitioning scheme similar to the BSD <quote>disk label</quote>, which allows for up to eight partitions per disk drive. The partitions are numbered <quote>1</quote> through to <quote>8</quote> in Linux and <quote>lettered</quote> <quote>a</quote> through to <quote>h</quote> in UNIX. Linux kernels 2.2 and higher always correspond <quote>1</quote> to <quote>a</quote>, <quote>2</quote> to <quote>b</quote> and so on. For example, <filename>rz0e</filename> in Tru64 UNIX would most likely be called <filename>sda5</filename> in Linux." -msgstr "" - -#. Tag: para -#: preparing.xml:951 -#, no-c-format -msgid "Partitions in a Tru64 disk label may overlap. Moreover, if this disk will be used from Tru64, the <quote>c</quote> partition is required to span the entire disk (thus overlapping all other non-empty partitions). Under Linux this makes <filename>sda3</filename> identical to <filename>sda</filename> (<filename>sdb3</filename> to <filename>sdb</filename>, if present, and so on). However, the partman partitioning tool used by &d-i; cannot handle overlapping partitions at present. As a result, it is currently not recommended to share disks between Tru64 and Debian. Partitions on Tru64 disks can be mounted under Debian after installation has been completed." -msgstr "" - -#. Tag: para -#: preparing.xml:964 -#, no-c-format -msgid "Another conventional requirement is for the <quote>a</quote> partition to start from the beginning of the disk, so that it always includes the boot block with the disk label. If you intend to boot Debian from that disk, you need to size it at least 2MB to fit aboot and perhaps a kernel. Note that this partition is only required for compatibility; you must not put a file system onto it, or you'll destroy data." -msgstr "" - -#. Tag: para -#: preparing.xml:973 -#, no-c-format -msgid "It is possible, and indeed quite reasonable, to share a swap partition between UNIX and Linux. In this case it will be needed to do a <command>mkswap</command> on that partition every time the system is rebooted from UNIX into Linux, as UNIX will damage the swap signature. You may want to run <command>mkswap</command> from the Linux start-up scripts before adding swap space with <command>swapon -a</command>." -msgstr "" - -#. Tag: para -#: preparing.xml:982 -#, no-c-format -msgid "If you want to mount UNIX partitions under Linux, note that Digital UNIX can use two different file system types, UFS and AdvFS, of which Linux only understands the former." -msgstr "" - -#. Tag: title -#: preparing.xml:991 -#, no-c-format -msgid "Partitioning in Windows NT" -msgstr "" - -#. Tag: para -#: preparing.xml:993 -#, no-c-format -msgid "Windows NT uses the PC-style partition table. If you are manipulating existing FAT or NTFS partitions, it is recommended that you use the native Windows NT tools (or, more conveniently, you can also repartition your disk from the AlphaBIOS setup menu). Otherwise, it is not really necessary to partition from Windows; the Linux partitioning tools will generally do a better job. Note that when you run NT, the Disk Administrator may offer to write a <quote>harmless signature</quote> on non-Windows disks if you have any. <emphasis>Never</emphasis> let it do that, as this signature will destroy the partition information." -msgstr "" - -#. Tag: para -#: preparing.xml:1006 -#, no-c-format -msgid "If you plan to boot Linux from an ARC/AlphaBIOS/ARCSBIOS console, you will need a (small) FAT partition for MILO. 5 MB is quite sufficient. If Windows NT is installed, its 6 MB bootstrap partition can be employed for this purpose. Debian &releasename; does not support installing MILO. If you already have MILO installed on your system, or install MILO from other media, Debian can still be booted from ARC." -msgstr "" - -#. Tag: title -#: preparing.xml:1023 +#: preparing.xml:928 #, no-c-format msgid "Partitioning From DOS or Windows" msgstr "" #. Tag: para -#: preparing.xml:1024 +#: preparing.xml:929 #, no-c-format msgid "If you are manipulating existing FAT or NTFS partitions, it is recommended that you either use the scheme below or native Windows or DOS tools. Otherwise, it is not really necessary to partition from DOS or Windows; the Linux partitioning tools will generally do a better job." msgstr "" #. Tag: para -#: preparing.xml:1032 +#: preparing.xml:937 #, no-c-format msgid "But if you have a large IDE disk, and are not using LBA addressing, overlay drivers (sometimes provided by hard disk manufacturers), or a new (post 1998) BIOS that supports large disk access extensions, then you must locate your Debian boot partition carefully. In this case, you will have to put the boot partition into the first 1024 cylinders of your hard disk (usually around 524 megabytes, without BIOS translation). This may require that you move an existing FAT or NTFS partition." msgstr "" #. Tag: title -#: preparing.xml:1046 +#: preparing.xml:951 #, no-c-format msgid "Lossless Repartitioning When Starting From DOS, Win-32 or OS/2" msgstr "" #. Tag: para -#: preparing.xml:1049 +#: preparing.xml:954 #, no-c-format msgid "One of the most common installations is onto a system that already contains DOS (including Windows 3.1), Win32 (such as Windows 95, 98, Me, NT, 2000, XP), or OS/2, and it is desired to put Debian onto the same disk without destroying the previous system. Note that the installer supports resizing of FAT and NTFS filesystems as used by DOS and Windows. Simply start the installer and when you get to the partitioning step, select the option for <menuchoice> <guimenuitem>Manual</guimenuitem> </menuchoice> partitioning, select the partition to resize, and specify its new size. So in most cases you should not need to use the method described below." msgstr "" #. Tag: para -#: preparing.xml:1061 +#: preparing.xml:966 #, no-c-format msgid "Before going any further, you should have decided how you will be dividing up the disk. The method in this section will only split a partition into two pieces. One will contain the original OS and the other will be used for Debian. During the installation of Debian, you will be given the opportunity to use the Debian portion of the disk as you see fit, i.e., as swap or as a file system." msgstr "" #. Tag: para -#: preparing.xml:1070 +#: preparing.xml:975 #, no-c-format msgid "The idea is to move all the data on the partition to the beginning, before changing the partition information, so that nothing will be lost. It is important that you do as little as possible between the data movement and repartitioning to minimize the chance of a file being written near the end of the partition as this will decrease the amount of space you can take from the partition." msgstr "" #. Tag: para -#: preparing.xml:1079 +#: preparing.xml:984 #, no-c-format msgid "The first thing needed is a copy of <command>fips</command> which is available in the <filename>tools/</filename> directory on your nearest Debian mirror. Unzip the archive and copy the files <filename>RESTORRB.EXE</filename>, <filename>FIPS.EXE</filename> and <filename>ERRORS.TXT</filename> to a bootable floppy. A bootable floppy can be created using the command <filename>sys a:</filename> under DOS. <command>fips</command> comes with very good documentation which you may want to read. You will definitely need to read the documentation if you use a disk compression driver or a disk manager. Create the disk and read the documentation <emphasis>before</emphasis> you defragment the disk." msgstr "" #. Tag: para -#: preparing.xml:1092 +#: preparing.xml:997 #, no-c-format msgid "The next thing needed is to move all the data to the beginning of the partition. <command>defrag</command>, which comes standard with DOS 6.0 and later, can easily do the job. See the <command>fips</command> documentation for a list of other software that may do the trick. Note that if you have Windows 9x, you must run <command>defrag</command> from there, since DOS doesn't understand VFAT, which is used to support for long filenames, used in Windows 95 and higher." msgstr "" #. Tag: para -#: preparing.xml:1102 +#: preparing.xml:1007 #, no-c-format msgid "After running the defragmenter (which can take a while on a large disk), reboot with the <command>fips</command> disk you created in the floppy drive. Simply type <filename>a:\\fips</filename> and follow the directions." msgstr "" #. Tag: para -#: preparing.xml:1108 +#: preparing.xml:1013 #, no-c-format msgid "Note that there are many other partition managers out there, in case <command>fips</command> doesn't do the trick for you." msgstr "" #. Tag: title -#: preparing.xml:1116 +#: preparing.xml:1021 #, no-c-format msgid "Partitioning for DOS" msgstr "" #. Tag: para -#: preparing.xml:1118 +#: preparing.xml:1023 #, no-c-format msgid "If you are partitioning for DOS drives, or changing the size of DOS partitions, using Linux tools, many people experience problems working with the resulting FAT partitions. For instance, some have reported slow performance, consistent problems with <command>scandisk</command>, or other weird errors in DOS or Windows." msgstr "" #. Tag: para -#: preparing.xml:1126 +#: preparing.xml:1031 #, no-c-format msgid "Apparently, whenever you create or resize a partition for DOS use, it's a good idea to fill the first few sectors with zeros. You should do this prior to running DOS's <command>format</command> command by executing the following command from Linux:" msgstr "" #. Tag: screen -#: preparing.xml:1133 +#: preparing.xml:1038 #, no-c-format msgid "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4" msgstr "" #. Tag: title -#: preparing.xml:1144 +#: preparing.xml:1049 #, no-c-format msgid "Partitioning from SunOS" msgstr "" #. Tag: para -#: preparing.xml:1146 +#: preparing.xml:1051 #, no-c-format msgid "It's perfectly fine to partition from SunOS; in fact, if you intend to run both SunOS and Debian on the same machine, it is recommended that you partition using SunOS prior to installing Debian. The Linux kernel understands Sun disk labels, so there are no problems there. SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or iso9660 (CDROM) partitions." msgstr "" #. Tag: title -#: preparing.xml:1158 +#: preparing.xml:1063 #, no-c-format msgid "Partitioning from Linux or another OS" msgstr "" #. Tag: para -#: preparing.xml:1160 +#: preparing.xml:1065 #, no-c-format msgid "Whatever system you are using to partition, make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</keycap> key is used to create Sun disk labels. You only need to do this on drives that do not already have a Sun disk label. If you are using a drive that was previously formatted using a PC (or other architecture) you must create a new disk label, or problems with the disk geometry will most likely occur." msgstr "" #. Tag: para -#: preparing.xml:1172 +#: preparing.xml:1077 #, no-c-format msgid "You will probably be using <command>SILO</command> as your boot loader (the small program which runs the operating system kernel). <command>SILO</command> has certain requirements for partition sizes and location; see <xref linkend=\"partitioning\"/>." msgstr "" #. Tag: title -#: preparing.xml:1187 +#: preparing.xml:1092 #, no-c-format msgid "MacOS/OSX Partitioning" msgstr "" #. Tag: para -#: preparing.xml:1189 +#: preparing.xml:1094 #, no-c-format msgid "The <application>Apple Drive Setup</application> application can be found in the <filename>Utilities</filename> folder on the MacOS CD. It will not adjust existing partitions; it is limited to partitioning the entire disk at once. The disk driver partitions don't show up in <application>Drive Setup</application>." msgstr "" #. Tag: para -#: preparing.xml:1196 +#: preparing.xml:1101 #, no-c-format msgid "Remember to create a placeholder partition for GNU/Linux, preferably positioned first in the disk layout. it doesn't matter what type it is, it will be deleted and replaced later inside the &debian; installer." msgstr "" #. Tag: para -#: preparing.xml:1202 +#: preparing.xml:1107 #, no-c-format msgid "If you are planning to install both MacOS 9 and OS X, it is best to create separate partitions for OS 9 and OS X. If they are installed on the same partition, <application>Startup Disk</application> (and reboot) must be used to select between the two; the choice between the two systems can't be made at boot time. With separate partitions, separate options for OS 9 and OS X will appear when holding the <keycap>option</keycap> key at boot time, and separate options can be installed in the <application>yaboot</application> boot menu as well. Also, Startup Disk will de-bless all other mountable partitions, which can affect GNU/Linux booting. Both OS 9 and OS X partitions will be accessible from either OS 9 or OS X." msgstr "" #. Tag: para -#: preparing.xml:1215 +#: preparing.xml:1120 #, no-c-format msgid "GNU/Linux is unable to access information on UFS partitions, but does support HFS+ (aka MacOS Extended) partitions. OS X requires one of these two types for its boot partition. MacOS 9 can be installed on either HFS (aka MacOS Standard) or HFS+. To share information between the MacOS and GNU/Linux systems, an exchange partition is handy. HFS, HFS+ and MS-DOS FAT partitions are supported by both MacOS and Linux." msgstr "" #. Tag: title -#: preparing.xml:1235 +#: preparing.xml:1140 #, no-c-format msgid "Pre-Installation Hardware and Operating System Setup" msgstr "" #. Tag: para -#: preparing.xml:1236 +#: preparing.xml:1141 #, no-c-format msgid "This section will walk you through pre-installation hardware setup, if any, that you will need to do prior to installing Debian. Generally, this involves checking and possibly changing firmware settings for your system. The <quote>firmware</quote> is the core software used by the hardware; it is most critically invoked during the bootstrap process (after power-up). Known hardware issues affecting the reliability of &debian; on your system are also highlighted." msgstr "" #. Tag: title -#: preparing.xml:1258 +#: preparing.xml:1163 #, no-c-format msgid "Invoking the BIOS Set-Up Menu" msgstr "" #. Tag: para -#: preparing.xml:1260 +#: preparing.xml:1165 #, no-c-format msgid "BIOS provides the basic functions needed to boot your machine to allow your operating system to access your hardware. Your system probably provides a BIOS setup menu, which is used to configure the BIOS. Before installing, you <emphasis>must</emphasis> ensure that your BIOS is set up correctly; not doing so can lead to intermittent crashes or an inability to install Debian." msgstr "" #. Tag: para -#: preparing.xml:1269 +#: preparing.xml:1174 #, no-c-format msgid "The rest of this section is lifted from the <ulink url=\"&url-pc-hw-faq;\"></ulink>, answering the question, <quote>How do I enter the CMOS configuration menu?</quote>. How you access the BIOS (or <quote>CMOS</quote>) configuration menu depends on who wrote your BIOS software:" msgstr "" #. Tag: term -#: preparing.xml:1283 +#: preparing.xml:1188 #, no-c-format msgid "AMI BIOS" msgstr "" #. Tag: para -#: preparing.xml:1284 +#: preparing.xml:1189 #, no-c-format msgid "<keycap>Delete</keycap> key during the POST (power on self test)" msgstr "" #. Tag: term -#: preparing.xml:1292 +#: preparing.xml:1197 #, no-c-format msgid "Award BIOS" msgstr "" #. Tag: para -#: preparing.xml:1293 +#: preparing.xml:1198 #, no-c-format msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo>, or <keycap>Delete</keycap> key during the POST" msgstr "" #. Tag: term -#: preparing.xml:1302 +#: preparing.xml:1207 #, no-c-format msgid "DTK BIOS" msgstr "" #. Tag: para -#: preparing.xml:1303 +#: preparing.xml:1208 #, no-c-format msgid "<keycap>Esc</keycap> key during the POST" msgstr "" #. Tag: term -#: preparing.xml:1310 +#: preparing.xml:1215 #, no-c-format msgid "IBM PS/2 BIOS" msgstr "" #. Tag: para -#: preparing.xml:1311 +#: preparing.xml:1216 #, no-c-format msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap> </keycombo> after <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Delete</keycap> </keycombo>" msgstr "" #. Tag: term -#: preparing.xml:1325 +#: preparing.xml:1230 #, no-c-format msgid "Phoenix BIOS" msgstr "" #. Tag: para -#: preparing.xml:1326 +#: preparing.xml:1231 #, no-c-format msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo> or <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>S</keycap> </keycombo> or <keycap>F1</keycap>" msgstr "" #. Tag: para -#: preparing.xml:1342 +#: preparing.xml:1247 #, no-c-format msgid "Information on invoking other BIOS routines can be found in <ulink url=\"&url-invoking-bios-info;\"></ulink>." msgstr "" #. Tag: para -#: preparing.xml:1347 +#: preparing.xml:1252 #, no-c-format msgid "Some &arch-title; machines don't have a CMOS configuration menu in the BIOS. They require a software CMOS setup program. If you don't have the Installation and/or Diagnostics diskette for your machine, you can try using a shareware/freeware program. Try looking in <ulink url=\"&url-simtel;\"></ulink>." msgstr "" #. Tag: title -#: preparing.xml:1358 preparing.xml:1676 +#: preparing.xml:1263 preparing.xml:1581 #, no-c-format msgid "Boot Device Selection" msgstr "" #. Tag: para -#: preparing.xml:1360 +#: preparing.xml:1265 #, no-c-format msgid "Many BIOS setup menus allow you to select the devices that will be used to bootstrap the system. Set this to look for a bootable operating system on <filename>A:</filename> (the first floppy disk), then optionally the first CD-ROM device (possibly appearing as <filename>D:</filename> or <filename>E:</filename>), and then from <filename>C:</filename> (the first hard disk). This setting enables you to boot from either a floppy disk or a CD-ROM, which are the two most common boot devices used to install Debian." msgstr "" #. Tag: para -#: preparing.xml:1371 +#: preparing.xml:1276 #, no-c-format msgid "If you have a newer SCSI controller and you have a CD-ROM device attached to it, you are usually able to boot from the CD-ROM. All you have to do is enable booting from a CD-ROM in the SCSI-BIOS of your controller." msgstr "" #. Tag: para -#: preparing.xml:1378 +#: preparing.xml:1283 #, no-c-format msgid "Another popular option is to boot from a USB storage device (also called a USB memory stick or USB key). Some BIOSes can boot directly from a USB storage device, but some cannot. You may need to configure your BIOS to boot from a <quote>Removable drive</quote> or even from <quote>USB-ZIP</quote> to get it to boot from the USB device." msgstr "" #. Tag: para -#: preparing.xml:1386 +#: preparing.xml:1291 #, no-c-format msgid "Here are some details about how to set the boot order. Remember to reset the boot order after Linux is installed, so that you restart your machine from the hard drive." msgstr "" #. Tag: title -#: preparing.xml:1395 +#: preparing.xml:1300 #, no-c-format msgid "Changing the Boot Order on IDE Computers" msgstr "" #. Tag: para -#: preparing.xml:1398 +#: preparing.xml:1303 #, no-c-format msgid "As your computer starts, press the keys to enter the BIOS utility. Often, it is the <keycap>Delete</keycap> key. However, consult the hardware documentation for the exact keystrokes." msgstr "" #. Tag: para -#: preparing.xml:1405 +#: preparing.xml:1310 #, no-c-format msgid "Find the boot sequence in the setup utility. Its location depends on your BIOS, but you are looking for a field that lists drives." msgstr "" #. Tag: para -#: preparing.xml:1410 +#: preparing.xml:1315 #, no-c-format msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom." msgstr "" #. Tag: para -#: preparing.xml:1415 +#: preparing.xml:1320 #, no-c-format msgid "C is the hard drive, and A is the floppy drive." msgstr "" #. Tag: para -#: preparing.xml:1421 +#: preparing.xml:1326 #, no-c-format msgid "Change the boot sequence setting so that the CD-ROM or the floppy is first. Usually, the <keycap>Page Up</keycap> or <keycap>Page Down</keycap> keys cycle through the possible choices." msgstr "" #. Tag: para -#: preparing.xml:1429 +#: preparing.xml:1334 #, no-c-format msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer." msgstr "" #. Tag: title -#: preparing.xml:1439 +#: preparing.xml:1344 #, no-c-format msgid "Changing the Boot Order on SCSI Computers" msgstr "" #. Tag: para -#: preparing.xml:1443 +#: preparing.xml:1348 #, no-c-format msgid "As your computer starts, press the keys to enter the SCSI setup utility." msgstr "" #. Tag: para -#: preparing.xml:1448 +#: preparing.xml:1353 #, no-c-format msgid "You can start the SCSI setup utility after the memory check and the message about how to start the BIOS utility displays when you start your computer." msgstr "" #. Tag: para -#: preparing.xml:1454 +#: preparing.xml:1359 #, no-c-format msgid "The keystrokes you need depend on the utility. Often, it is <keycombo><keycap>Ctrl</keycap><keycap>F2</keycap></keycombo>. However, consult your hardware documentation for the exact keystrokes." msgstr "" #. Tag: para -#: preparing.xml:1462 +#: preparing.xml:1367 #, no-c-format msgid "Find the utility for changing the boot order." msgstr "" #. Tag: para -#: preparing.xml:1467 +#: preparing.xml:1372 #, no-c-format msgid "Set the utility so that the SCSI ID of the CD drive is first on the list." msgstr "" #. Tag: para -#: preparing.xml:1473 +#: preparing.xml:1378 #, no-c-format msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer. Often, you must press <keycap>F10</keycap>." msgstr "" #. Tag: title -#: preparing.xml:1487 +#: preparing.xml:1392 #, no-c-format msgid "Miscellaneous BIOS Settings" msgstr "" #. Tag: title -#: preparing.xml:1489 +#: preparing.xml:1394 #, no-c-format msgid "CD-ROM Settings" msgstr "" #. Tag: para -#: preparing.xml:1490 +#: preparing.xml:1395 #, no-c-format msgid "Some BIOS systems (such as Award BIOS) allow you to automatically set the CD speed. You should avoid that, and instead set it to, say, the lowest speed. If you get <userinput>seek failed</userinput> error messages, this may be your problem." msgstr "" #. Tag: title -#: preparing.xml:1500 +#: preparing.xml:1405 #, no-c-format msgid "Extended vs. Expanded Memory" msgstr "" #. Tag: para -#: preparing.xml:1501 +#: preparing.xml:1406 #, no-c-format msgid "If your system provides both ex<emphasis>ten</emphasis>ded and ex<emphasis>pan</emphasis>ded memory, set it so that there is as much extended and as little expanded memory as possible. Linux requires extended memory and cannot use expanded memory." msgstr "" #. Tag: title -#: preparing.xml:1511 +#: preparing.xml:1416 #, no-c-format msgid "Virus Protection" msgstr "" #. Tag: para -#: preparing.xml:1512 +#: preparing.xml:1417 #, no-c-format msgid "Disable any virus-warning features your BIOS may provide. If you have a virus-protection board or other special hardware, make sure it is disabled or physically removed while running GNU/Linux. These aren't compatible with GNU/Linux; moreover, due to the file system permissions and protected memory of the Linux kernel, viruses are almost unheard of<footnote> <para> After installation you can enable Boot Sector protection if you want. This offers no additional security in Linux but if you also run Windows it may prevent a catastrophe. There is no need to tamper with the Master Boot Record (MBR) after the boot manager has been set up. </para> </footnote>." msgstr "" #. Tag: title -#: preparing.xml:1533 +#: preparing.xml:1438 #, no-c-format msgid "Shadow RAM" msgstr "" #. Tag: para -#: preparing.xml:1534 +#: preparing.xml:1439 #, no-c-format msgid "Your motherboard may provide <emphasis>shadow RAM</emphasis> or BIOS caching. You may see settings for <quote>Video BIOS Shadow</quote>, <quote>C800-CBFF Shadow</quote>, etc. <emphasis>Disable</emphasis> all shadow RAM. Shadow RAM is used to accelerate access to the ROMs on your motherboard and on some of the controller cards. Linux does not use these ROMs once it has booted because it provides its own faster 32-bit software in place of the 16-bit programs in the ROMs. Disabling the shadow RAM may make some of it available for programs to use as normal memory. Leaving the shadow RAM enabled may interfere with Linux access to hardware devices." msgstr "" #. Tag: title -#: preparing.xml:1551 +#: preparing.xml:1456 #, no-c-format msgid "Memory Hole" msgstr "" #. Tag: para -#: preparing.xml:1552 +#: preparing.xml:1457 #, no-c-format msgid "If your BIOS offers something like <quote>15–16 MB Memory Hole</quote>, please disable that. Linux expects to find memory there if you have that much RAM." msgstr "" #. Tag: para -#: preparing.xml:1558 +#: preparing.xml:1463 #, no-c-format msgid "We have a report of an Intel Endeavor motherboard on which there is an option called <quote>LFB</quote> or <quote>Linear Frame Buffer</quote>. This had two settings: <quote>Disabled</quote> and <quote>1 Megabyte</quote>. Set it to <quote>1 Megabyte</quote>. When disabled, the installation floppy was not read correctly, and the system eventually crashed. At this writing we don't understand what's going on with this particular device — it just worked with that setting and not without it." msgstr "" #. Tag: title -#: preparing.xml:1574 +#: preparing.xml:1479 #, no-c-format msgid "Advanced Power Management" msgstr "" #. Tag: para -#: preparing.xml:1575 +#: preparing.xml:1480 #, no-c-format msgid "If your motherboard provides Advanced Power Management (APM), configure it so that power management is controlled by APM. Disable the doze, standby, suspend, nap, and sleep modes, and disable the hard disk's power-down timer. Linux can take over control of these modes, and can do a better job of power-management than the BIOS." msgstr "" #. Tag: title -#: preparing.xml:1593 +#: preparing.xml:1498 #, no-c-format msgid "Invoking OpenFirmware" msgstr "" #. Tag: para -#: preparing.xml:1594 +#: preparing.xml:1499 #, no-c-format msgid "There is normally no need to set up the BIOS (called OpenFirmware) on &arch-title; systems. PReP and CHRP are equipped with OpenFirmware, but unfortunately, the means you use to invoke it vary from manufacturer to manufacturer. You'll have to consult the hardware documentation which came with your machine." msgstr "" #. Tag: para -#: preparing.xml:1602 +#: preparing.xml:1507 #, no-c-format msgid "On &arch-title; Macintoshes, you invoke OpenFirmware with <keycombo><keycap>Command (cloverleaf/Apple)</keycap><keycap>Option</keycap><keycap>o</keycap><keycap>f</keycap></keycombo> while booting. Generally it will check for these keystrokes after the chime, but the exact timing varies from model to model. See <ulink url=\"&url-netbsd-powerpc-faq;\"></ulink> for more hints." msgstr "" #. Tag: para -#: preparing.xml:1610 +#: preparing.xml:1515 #, no-c-format msgid "" "The OpenFirmware prompt looks like this: <informalexample><screen>\n" @@ -1501,43 +1441,43 @@ msgid "" msgstr "" #. Tag: para -#: preparing.xml:1623 +#: preparing.xml:1528 #, no-c-format msgid "The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 and 2.4, is broken. These machines will most likely not be able to boot from the hard drive unless the firmware is patched. A firmware patch is included in the <application>System Disk 2.3.1</application> utility, available from Apple at <ulink url=\"ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin\"></ulink>. After unpacking the utility in MacOS, and launching it, select the <guibutton>Save</guibutton> button to have the firmware patches installed to nvram." msgstr "" #. Tag: title -#: preparing.xml:1643 +#: preparing.xml:1548 #, no-c-format msgid "Invoking OpenBoot" msgstr "" #. Tag: para -#: preparing.xml:1645 +#: preparing.xml:1550 #, no-c-format msgid "OpenBoot provides the basic functions needed to boot the &arch-title; architecture. This is rather similar in function to the BIOS in the x86 architecture, although much nicer. The Sun boot PROMs have a built-in forth interpreter which lets you do quite a number of things with your machine, such as diagnostics and simple scripts." msgstr "" #. Tag: para -#: preparing.xml:1653 +#: preparing.xml:1558 #, no-c-format msgid "To get to the boot prompt you need to hold down the <keycap>Stop</keycap> key (on older type 4 keyboards, use the <keycap>L1</keycap> key, if you have a PC keyboard adapter, use the <keycap>Break</keycap> key) and press the <keycap>A</keycap> key. The boot PROM will give you a prompt, either <userinput>ok</userinput> or <userinput>></userinput>. It is preferred to have the <userinput>ok</userinput> prompt. So if you get the old style prompt, hit the <keycap>n</keycap> key to get the new style prompt." msgstr "" #. Tag: para -#: preparing.xml:1665 +#: preparing.xml:1570 #, no-c-format msgid "If you are using a serial console, send a break to the machine. With Minicom, use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type <userinput>%~break</userinput>. Consult the documentation of your terminal emulator if you are using a different program." msgstr "" #. Tag: para -#: preparing.xml:1678 +#: preparing.xml:1583 #, no-c-format msgid "You can use OpenBoot to boot from specific devices, and also to change your default boot device. However, you need to know some details about how OpenBoot names devices; it's considerably different from Linux device naming, described in <xref linkend=\"device-names\"/>. Also, the command will vary a bit, depending on what version of OpenBoot you have. More information about OpenBoot can be found in the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>." msgstr "" #. Tag: para -#: preparing.xml:1688 +#: preparing.xml:1593 #, 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" @@ -1548,7 +1488,7 @@ msgid "" msgstr "" #. Tag: para -#: preparing.xml:1711 +#: preparing.xml:1616 #, no-c-format msgid "" "To boot from a specific device, use the command <userinput>boot <replaceable>device</replaceable></userinput>. You can set this behavior as the default using the <userinput>setenv</userinput> command. However, the name of the variable to set changed between OpenBoot revisions. In OpenBoot 1.x, use the command <userinput>setenv boot-from <replaceable>device</replaceable></userinput>. In later revisions of OpenBoot, use the command <userinput>setenv boot-device <replaceable>device</replaceable></userinput>. Note, this is also configurable using the <command>eeprom</command> command on Solaris, or modifying the appropriate files in <filename>/proc/openprom/options/</filename>, for example under Linux: <informalexample><screen>\n" @@ -1557,115 +1497,115 @@ msgid "" msgstr "" #. Tag: screen -#: preparing.xml:1730 +#: preparing.xml:1635 #, no-c-format msgid "eeprom boot-device=disk1:1" msgstr "" #. Tag: title -#: preparing.xml:1740 +#: preparing.xml:1645 #, no-c-format msgid "BIOS Setup" msgstr "" #. Tag: para -#: preparing.xml:1741 +#: preparing.xml:1646 #, no-c-format msgid "In order to install &debian; on a &arch-title; or zSeries machine you have first boot a kernel into the system. The boot mechanism of this platform is inherently different to other ones, especially from PC-like systems: there are no floppy devices available at all. You will notice another big difference while you work with this platform: most (if not all) of the time you will work remote, with the help of some client session software like telnet, or a browser. This is due to that special system architecture where the 3215/3270 console is line-based instead of character-based." msgstr "" #. Tag: para -#: preparing.xml:1753 +#: preparing.xml:1658 #, no-c-format msgid "Linux on this platform runs either natively on the bare machine, in a so-called LPAR (Logical Partition) or in a virtual machine supplied by the VM system. You can use a boot tape on all of those systems; you may use some other boot media, too, but those may not be generally available. For example, you can use the virtual card reader of a virtual machine, or boot from the HMC (Hardware Management Console) of an LPAR if the HMC and this option is available for you." msgstr "" #. Tag: para -#: preparing.xml:1763 +#: preparing.xml:1668 #, no-c-format msgid "Before you actually perform an installation, you have to go over some design and preparation steps. IBM has made documentation available about the whole process, e.g. how to prepare an installation medium and how actually to boot from that medium. Duplicating that information here is neither possible nor necessary. However, we will describe here which kind of Debian-specific data is needed and where to find it. Using both sources of information, you have to prepare your machine and the installation medium before you can perform a boot from it. When you see the welcome message in your client session, return to this document to go through the Debian-specific installation steps." msgstr "" #. Tag: title -#: preparing.xml:1780 +#: preparing.xml:1685 #, no-c-format msgid "Native and LPAR installations" msgstr "" #. Tag: para -#: preparing.xml:1781 +#: preparing.xml:1686 #, no-c-format msgid "Please refer to chapter 5 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.2 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up an LPAR for Linux." msgstr "" #. Tag: title -#: preparing.xml:1795 +#: preparing.xml:1700 #, no-c-format msgid "Installation as a VM guest" msgstr "" #. Tag: para -#: preparing.xml:1797 +#: preparing.xml:1702 #, no-c-format msgid "Please refer to chapter 6 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.1 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up a VM guest for running Linux." msgstr "" #. Tag: para -#: preparing.xml:1807 +#: preparing.xml:1712 #, no-c-format msgid "You need to copy all the files from the <filename>generic</filename> sub-directory to your CMS disk. Be sure to transfer <filename>kernel.debian</filename> and <filename>initrd.debian</filename> in binary mode with a fixed record length of 80 characters." msgstr "" #. Tag: title -#: preparing.xml:1819 +#: preparing.xml:1724 #, no-c-format msgid "Setting up an installation server" msgstr "" #. Tag: para -#: preparing.xml:1821 +#: preparing.xml:1726 #, no-c-format msgid "If you don't have a connection to the Internet (either directly or via a web proxy) you need to create a local installation server that can be accessed from your S/390. This server keeps all the packages you want to install and must make them available using NFS, HTTP or FTP." msgstr "" #. Tag: para -#: preparing.xml:1829 +#: preparing.xml:1734 #, no-c-format msgid "The installation server needs to copy the exact directory structure from any &debian; mirror, but only the s390 and architecture-independent files are required. You can also copy the contents of all installation CDs into such a directory tree." msgstr "" #. Tag: emphasis -#: preparing.xml:1838 +#: preparing.xml:1743 #, no-c-format msgid "FIXME: more information needed — from a Redbook?" msgstr "" #. Tag: title -#: preparing.xml:1845 +#: preparing.xml:1750 #, no-c-format msgid "Hardware Issues to Watch Out For" msgstr "" #. Tag: title -#: preparing.xml:1848 +#: preparing.xml:1753 #, no-c-format msgid "USB BIOS support and keyboards" msgstr "" #. Tag: para -#: preparing.xml:1849 +#: preparing.xml:1754 #, no-c-format msgid "If you have no AT-style keyboard and only a USB model, you may need to enable legacy AT keyboard emulation in your BIOS setup. Only do this if the installation system fails to use your keyboard in USB mode. Conversely, for some systems (especially laptops) you may need to disable legacy USB support if your keyboard does not respond. Consult your main board manual and look in the BIOS for <quote>Legacy keyboard emulation</quote> or <quote>USB keyboard support</quote> options." msgstr "" #. Tag: title -#: preparing.xml:1863 +#: preparing.xml:1768 #, no-c-format msgid "Display-visibility on OldWorld Powermacs" msgstr "" #. Tag: para -#: preparing.xml:1865 +#: preparing.xml:1770 #, no-c-format msgid "Some OldWorld Powermacs, most notably those with the <quote>control</quote> display driver, may not reliably produce a colormap under Linux when the display is configured for more than 256 colors. If you are experiencing such issues with your display after rebooting (you can sometimes see data on the monitor, but on other occasions cannot see anything) or, if the screen turns black after booting the installer instead of showing you the user interface, try changing your display settings under MacOS to use 256 colors instead of <quote>thousands</quote> or <quote>millions</quote>." msgstr "" diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index d9cdae2d4..6c75869ef 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: 2009-11-02 22:05+0000\n" +"POT-Creation-Date: 2009-11-02 22:19+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" @@ -872,17 +872,11 @@ msgstr "" #. Tag: para #: using-d-i.xml:1029 #, 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:1035 -#, 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:1041 +#: using-d-i.xml:1035 #, no-c-format msgid "" "The list of partitions might look like this: <informalexample><screen>\n" @@ -905,601 +899,601 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:1054 +#: using-d-i.xml:1048 #, no-c-format msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning." msgstr "" #. Tag: title -#: using-d-i.xml:1068 +#: using-d-i.xml:1062 #, no-c-format msgid "Manual Partitioning" msgstr "" #. Tag: para -#: using-d-i.xml:1069 +#: using-d-i.xml:1063 #, 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 set up 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:1077 +#: using-d-i.xml:1071 #, 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:1085 +#: using-d-i.xml:1079 #, no-c-format msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap, software RAID, LVM, an encrypted file system, or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem for this partition, including options to use the partition for swap, software RAID, LVM, or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen." msgstr "" #. Tag: para -#: using-d-i.xml:1107 +#: using-d-i.xml:1101 #, no-c-format msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen as is used when creating a new partition, so you can change the same settings. One thing that may not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition." msgstr "" #. Tag: para -#: using-d-i.xml:1118 +#: using-d-i.xml:1112 #, 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:1126 +#: using-d-i.xml:1120 #, 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:1132 +#: using-d-i.xml:1126 #, 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:1140 +#: using-d-i.xml:1134 #, 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:1168 +#: using-d-i.xml:1162 #, no-c-format msgid "Configuring Multidisk Devices (Software RAID)" msgstr "" #. Tag: para -#: using-d-i.xml:1169 +#: using-d-i.xml:1163 #, no-c-format msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct an MD device even from partitions residing on single physical drive, but that won't give any benefits. </para></footnote> in your computer, you can use <command>mdcfg</command> to set up 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:1182 +#: using-d-i.xml:1176 #, 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:1190 +#: using-d-i.xml:1184 #, no-c-format msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar to RAID5 except that it uses two parity devices instead of one. </para><para> A RAID6 array can survive up to two disk failures. </para></listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It creates <replaceable>n</replaceable> copies of incoming data and distributes them across the partitions so that none of the copies of the same data are on the same device. The default value of <replaceable>n</replaceable> is 2, but it can be set to something else in expert mode. The number of partitions used must be at least <replaceable>n</replaceable>. RAID10 has different layouts for distributing the copies. The default is near copies. Near copies have all of the copies at about the same offset on all of the disks. Far copies have the copies at different offsets on the disks. Offset copies copy the stripe, not the individual copies. </para><para> RAID10 can be used to achieve reliability and redundancy without the drawback of having to calculate parity. </para></listitem> </varlistentry> </variablelist> To sum it up:" msgstr "" #. Tag: entry -#: using-d-i.xml:1304 +#: using-d-i.xml:1298 #, no-c-format msgid "Type" msgstr "" #. Tag: entry -#: using-d-i.xml:1305 +#: using-d-i.xml:1299 #, no-c-format msgid "Minimum Devices" msgstr "" #. Tag: entry -#: using-d-i.xml:1306 +#: using-d-i.xml:1300 #, no-c-format msgid "Spare Device" msgstr "" #. Tag: entry -#: using-d-i.xml:1307 +#: using-d-i.xml:1301 #, no-c-format msgid "Survives disk failure?" msgstr "" #. Tag: entry -#: using-d-i.xml:1308 +#: using-d-i.xml:1302 #, no-c-format msgid "Available Space" msgstr "" #. Tag: entry -#: using-d-i.xml:1314 +#: using-d-i.xml:1308 #, no-c-format msgid "RAID0" msgstr "" #. Tag: entry -#: using-d-i.xml:1315 using-d-i.xml:1323 using-d-i.xml:1353 +#: using-d-i.xml:1309 using-d-i.xml:1317 using-d-i.xml:1347 #, no-c-format msgid "<entry>2</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1316 using-d-i.xml:1317 +#: using-d-i.xml:1310 using-d-i.xml:1311 #, no-c-format msgid "<entry>no</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1318 +#: using-d-i.xml:1312 #, no-c-format msgid "Size of the smallest partition multiplied by number of devices in RAID" msgstr "" #. Tag: entry -#: using-d-i.xml:1322 +#: using-d-i.xml:1316 #, no-c-format msgid "RAID1" msgstr "" #. Tag: entry -#: using-d-i.xml:1324 using-d-i.xml:1332 using-d-i.xml:1343 using-d-i.xml:1354 +#: using-d-i.xml:1318 using-d-i.xml:1326 using-d-i.xml:1337 using-d-i.xml:1348 #, no-c-format msgid "optional" msgstr "" #. Tag: entry -#: using-d-i.xml:1325 using-d-i.xml:1333 using-d-i.xml:1344 using-d-i.xml:1355 +#: using-d-i.xml:1319 using-d-i.xml:1327 using-d-i.xml:1338 using-d-i.xml:1349 #, no-c-format msgid "<entry>yes</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1326 +#: using-d-i.xml:1320 #, no-c-format msgid "Size of the smallest partition in RAID" msgstr "" #. Tag: entry -#: using-d-i.xml:1330 +#: using-d-i.xml:1324 #, no-c-format msgid "RAID5" msgstr "" #. Tag: entry -#: using-d-i.xml:1331 +#: using-d-i.xml:1325 #, no-c-format msgid "<entry>3</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1334 +#: using-d-i.xml:1328 #, no-c-format msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)" msgstr "" #. Tag: entry -#: using-d-i.xml:1341 +#: using-d-i.xml:1335 #, no-c-format msgid "RAID6" msgstr "" #. Tag: entry -#: using-d-i.xml:1342 +#: using-d-i.xml:1336 #, no-c-format msgid "<entry>4</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1345 +#: using-d-i.xml:1339 #, no-c-format msgid "Size of the smallest partition multiplied by (number of devices in RAID minus two)" msgstr "" #. Tag: entry -#: using-d-i.xml:1352 +#: using-d-i.xml:1346 #, no-c-format msgid "RAID10" msgstr "" #. Tag: entry -#: using-d-i.xml:1356 +#: using-d-i.xml:1350 #, no-c-format msgid "Total of all partitions divided by the number of chunk copies (defaults to two)" msgstr "" #. Tag: para -#: using-d-i.xml:1363 +#: using-d-i.xml:1357 #, 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:1368 +#: using-d-i.xml:1362 #, no-c-format msgid "To create an 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:1377 +#: using-d-i.xml:1371 #, no-c-format msgid "Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for <filename>/boot</filename> when using RAID for the root (<filename>/</filename>) file system. Most boot loaders <phrase arch=\"x86\">(including lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</filename> can be an option." msgstr "" #. Tag: para -#: using-d-i.xml:1389 +#: using-d-i.xml:1383 #, no-c-format msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) file system. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell." msgstr "" #. Tag: para -#: using-d-i.xml:1398 +#: using-d-i.xml:1392 #, 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:1411 +#: using-d-i.xml:1405 #, 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:1418 +#: using-d-i.xml:1412 #, 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 earlier. Don't worry. If you make a mistake and select a different number of partitions, &d-i; won't let you continue until you correct the issue." msgstr "" #. Tag: para -#: using-d-i.xml:1430 +#: using-d-i.xml:1424 #, no-c-format msgid "RAID5 has a setup procedure similar to RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions." msgstr "" #. Tag: para -#: using-d-i.xml:1436 +#: using-d-i.xml:1430 #, no-c-format msgid "RAID6 also has a setup procedure similar to RAID1 except that at least <emphasis>four</emphasis> active partitions are required." msgstr "" #. Tag: para -#: using-d-i.xml:1442 +#: using-d-i.xml:1436 #, no-c-format msgid "RAID10 again has a setup procedure similar to RAID1 except in expert mode. In expert mode, &d-i; will ask you for the layout. The layout has two parts. The first part is the layout type. It is either <literal>n</literal> (for near copies), <literal>f</literal> (for far copies), or <literal>o</literal> (for offset copies). The second part is the number of copies to make of the data. There must be at least that many active devices so that all of the copies can be distributed onto different disks." msgstr "" #. Tag: para -#: using-d-i.xml:1456 +#: using-d-i.xml:1450 #, no-c-format msgid "It is perfectly possible to have several types of MD at once. For example, if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine the first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)." msgstr "" #. Tag: para -#: using-d-i.xml:1465 +#: using-d-i.xml:1459 #, no-c-format msgid "After you set up 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:1480 +#: using-d-i.xml:1474 #, no-c-format msgid "Configuring the Logical Volume Manager (LVM)" msgstr "" #. Tag: para -#: using-d-i.xml:1481 +#: using-d-i.xml:1475 #, 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 by moving stuff around, symlinking, etc." msgstr "" #. Tag: para -#: using-d-i.xml:1489 +#: using-d-i.xml:1483 #, 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:1499 +#: using-d-i.xml:1493 #, 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:1510 +#: using-d-i.xml:1504 #, 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:1519 +#: using-d-i.xml:1513 #, 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:1530 +#: using-d-i.xml:1524 #, 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:1535 +#: using-d-i.xml:1529 #, no-c-format msgid "Create volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1538 +#: using-d-i.xml:1532 #, no-c-format msgid "Create logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1541 +#: using-d-i.xml:1535 #, no-c-format msgid "Delete volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1544 +#: using-d-i.xml:1538 #, no-c-format msgid "Delete logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1547 +#: using-d-i.xml:1541 #, no-c-format msgid "Extend volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1550 +#: using-d-i.xml:1544 #, no-c-format msgid "Reduce volume group" msgstr "" #. Tag: para -#: using-d-i.xml:1552 +#: using-d-i.xml:1546 #, no-c-format msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen" msgstr "" #. Tag: para -#: using-d-i.xml:1558 +#: using-d-i.xml:1552 #, 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:1563 +#: using-d-i.xml:1557 #, 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:1577 +#: using-d-i.xml:1571 #, no-c-format msgid "Configuring Encrypted Volumes" msgstr "" #. Tag: para -#: using-d-i.xml:1578 +#: using-d-i.xml:1572 #, 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:1590 +#: using-d-i.xml:1584 #, 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:1605 +#: using-d-i.xml:1599 #, 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:1612 +#: using-d-i.xml:1606 #, 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:1623 +#: using-d-i.xml:1617 #, 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:1635 +#: using-d-i.xml:1629 #, 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:1645 +#: using-d-i.xml:1639 #, no-c-format msgid "Encryption: <userinput>aes</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1647 +#: using-d-i.xml:1641 #, 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:1665 +#: using-d-i.xml:1659 #, no-c-format msgid "Key size: <userinput>256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1667 +#: using-d-i.xml:1661 #, 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:1679 +#: using-d-i.xml:1673 #, no-c-format msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1681 +#: using-d-i.xml:1675 #, 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:1691 +#: using-d-i.xml:1685 #, 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:1703 +#: using-d-i.xml:1697 #, no-c-format msgid "Encryption key: <userinput>Passphrase</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1705 +#: using-d-i.xml:1699 #, no-c-format msgid "Here you can choose the type of the encryption key for this partition." msgstr "" #. Tag: term -#: using-d-i.xml:1711 +#: using-d-i.xml:1705 #, no-c-format msgid "Passphrase" msgstr "" #. Tag: para -#: using-d-i.xml:1712 +#: using-d-i.xml:1706 #, 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:1727 using-d-i.xml:1820 +#: using-d-i.xml:1721 using-d-i.xml:1814 #, no-c-format msgid "Random key" msgstr "" #. Tag: para -#: using-d-i.xml:1728 +#: using-d-i.xml:1722 #, 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:1737 +#: using-d-i.xml:1731 #, 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:1756 using-d-i.xml:1833 +#: using-d-i.xml:1750 using-d-i.xml:1827 #, no-c-format msgid "Erase data: <userinput>yes</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1758 +#: using-d-i.xml:1752 #, 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:1778 +#: using-d-i.xml:1772 #, 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:1787 +#: using-d-i.xml:1781 #, no-c-format msgid "Encryption: <userinput>AES256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1789 +#: using-d-i.xml:1783 #, 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:1799 +#: using-d-i.xml:1793 #, no-c-format msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1801 +#: using-d-i.xml:1795 #, no-c-format msgid "Here you can select the type of the encryption key for this partition." msgstr "" #. Tag: term -#: using-d-i.xml:1807 +#: using-d-i.xml:1801 #, no-c-format msgid "Keyfile (GnuPG)" msgstr "" #. Tag: para -#: using-d-i.xml:1808 +#: using-d-i.xml:1802 #, 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:1821 +#: using-d-i.xml:1815 #, no-c-format msgid "Please see the section on random keys above." msgstr "" #. Tag: para -#: using-d-i.xml:1835 +#: using-d-i.xml:1829 #, no-c-format msgid "Please see the the section on erasing data above." msgstr "" #. Tag: para -#: using-d-i.xml:1844 +#: using-d-i.xml:1838 #, 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:1854 +#: using-d-i.xml:1848 #, 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:1863 +#: using-d-i.xml:1857 #, 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:1876 +#: using-d-i.xml:1870 #, 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:1892 +#: using-d-i.xml:1886 #, 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" @@ -1512,619 +1506,607 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:1905 +#: using-d-i.xml:1899 #, no-c-format msgid "Pay attention to 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 the ordinary boot process and the boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:1915 +#: using-d-i.xml:1909 #, no-c-format msgid "Once you are satisfied with the partitioning scheme, continue with the installation." msgstr "" #. Tag: title -#: using-d-i.xml:1926 +#: using-d-i.xml:1920 #, no-c-format msgid "Installing the Base System" msgstr "" #. Tag: para -#: using-d-i.xml:1927 +#: using-d-i.xml:1921 #, 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:1940 +#: using-d-i.xml:1934 #, 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:1949 +#: using-d-i.xml:1943 #, 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:1955 +#: using-d-i.xml:1949 #, 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:1967 +#: using-d-i.xml:1961 #, no-c-format msgid "Setting Up Users And Passwords" msgstr "" #. Tag: para -#: using-d-i.xml:1968 +#: using-d-i.xml:1962 #, no-c-format msgid "After the base system has been installed, the installer will allow you to set up the <quote>root</quote> account and/or an account for the first user. Other user accounts can be created after the installation has been completed." msgstr "" #. Tag: title -#: using-d-i.xml:1982 +#: using-d-i.xml:1976 #, no-c-format msgid "Set the Root Password" msgstr "" #. Tag: para -#: using-d-i.xml:1986 +#: using-d-i.xml:1980 #, 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:1994 +#: using-d-i.xml:1988 #, 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:2002 +#: using-d-i.xml:1996 #, 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:2012 +#: using-d-i.xml:2006 #, no-c-format msgid "Create an Ordinary User" msgstr "" #. Tag: para -#: using-d-i.xml:2014 +#: using-d-i.xml:2008 #, 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:2023 +#: using-d-i.xml:2017 #, 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:2033 +#: using-d-i.xml:2027 #, 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:2040 +#: using-d-i.xml:2034 #, 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:2051 +#: using-d-i.xml:2045 #, no-c-format msgid "Installing Additional Software" msgstr "" #. Tag: para -#: using-d-i.xml:2052 +#: using-d-i.xml:2046 #, no-c-format msgid "At this point you have a usable but limited system. Most users will want to install additional software on the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network connection." msgstr "" #. Tag: title -#: using-d-i.xml:2067 +#: using-d-i.xml:2061 #, no-c-format msgid "Configuring apt" msgstr "" #. Tag: para -#: using-d-i.xml:2069 +#: using-d-i.xml:2063 #, 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:2093 +#: using-d-i.xml:2087 #, no-c-format msgid "<command>apt</command> must be configured so that it knows from where to retrieve packages. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>. You can examine and edit this file to your liking after the installation is complete." msgstr "" #. Tag: para -#: using-d-i.xml:2100 +#: using-d-i.xml:2094 #, no-c-format msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>volatile</quote> update service." msgstr "" #. Tag: para -#: using-d-i.xml:2109 +#: using-d-i.xml:2103 #, no-c-format msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or volatile update services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive." msgstr "" #. Tag: title -#: using-d-i.xml:2120 +#: using-d-i.xml:2114 #, no-c-format msgid "Installing from more than one CD or DVD" msgstr "" #. Tag: para -#: using-d-i.xml:2122 +#: using-d-i.xml:2116 #, no-c-format msgid "If you are installing from a CD or a DVD that is part of a larger set, the installer will ask if you want to scan additional CDs or DVDs. If you have additional CDs or DVDs available, you probably want to do this so the installer can use the packages included on them." msgstr "" #. Tag: para -#: using-d-i.xml:2129 +#: using-d-i.xml:2123 #, no-c-format msgid "If you do not have any additional CDs or DVDs, that is no problem: using them is not required. If you also do not use a network mirror (as explained in the next section), it can mean that not all packages belonging to the tasks you select in the next step of the installation can be installed." msgstr "" #. Tag: para -#: using-d-i.xml:2137 +#: using-d-i.xml:2131 #, no-c-format msgid "Packages are included on CDs (and DVDs) in the order of their popularity. This means that for most uses only the first CDs in a set are needed and that only very few people actually use any of the packages included on the last CDs in a set." msgstr "" #. Tag: para -#: using-d-i.xml:2144 +#: using-d-i.xml:2138 #, no-c-format msgid "It also means that buying or downloading and burning a full CD set is just a waste of money as you'll never use most of them. In most cases you are better off getting only the first 3 to 8 CDs and installing any additional packages you may need from the Internet by using a mirror. The same goes for DVD sets: the first DVD, or maybe the first two DVDs will cover most needs." msgstr "" #. Tag: para -#: using-d-i.xml:2153 +#: using-d-i.xml:2147 #, no-c-format msgid "A good rule of thumb is that for a regular desktop installation (using the GNOME desktop environment) only the first three CDs are needed. For the alternative desktop environments (KDE or Xfce), additional CDs are needed. The first DVD easily covers all three desktop environments." msgstr "" #. Tag: para -#: using-d-i.xml:2161 +#: using-d-i.xml:2155 #, no-c-format msgid "If you do scan multiple CDs or DVDs, the installer will prompt you to exchange them when it needs packages from another CD/DVD than the one currently in the drive. Note that only CDs or DVDs that belong to the same set should be scanned. The order in which they are scanned does not really matter, but scanning them in ascending order will reduce the chance of mistakes." msgstr "" #. Tag: title -#: using-d-i.xml:2174 +#: using-d-i.xml:2168 #, no-c-format msgid "Using a network mirror" msgstr "" #. Tag: para -#: using-d-i.xml:2176 +#: using-d-i.xml:2170 #, no-c-format msgid "One question that will be asked during most installs is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions." msgstr "" #. Tag: para -#: using-d-i.xml:2182 +#: using-d-i.xml:2176 #, no-c-format msgid "If you are <emphasis>not</emphasis> installing from a full CD or DVD or using a full CD/DVD image, you really should use a network mirror as otherwise you will end up with only a very minimal system. However, if you have a limited Internet connection it is best <emphasis>not</emphasis> to select the <literal>desktop</literal> task in the next step of the installation." msgstr "" #. Tag: para -#: using-d-i.xml:2191 +#: using-d-i.xml:2185 #, no-c-format msgid "If you are installing from a single full CD or using a full CD image, using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. If you have a limited Internet connection it may still be best to <emphasis>not</emphasis> select a network mirror here, but to finish the installation using only what's available on the CD and selectively install additional packages after the installation (i.e. after you have rebooted into the new system)." msgstr "" #. Tag: para -#: using-d-i.xml:2202 +#: using-d-i.xml:2196 #, no-c-format msgid "If you are installing from a DVD or using a DVD image, any packages needed during the installation should be present on the first DVD. The same is true if you have scanned multiple CDs as explained in the previous section. Use of a network mirror is optional." msgstr "" #. Tag: para -#: using-d-i.xml:2209 +#: using-d-i.xml:2203 #, no-c-format msgid "One advantage of adding a network mirror is that updates that have occurred since the CD/DVD set was created and have been included in a point release, will become available for installation, thus extending the life of your CD/DVD set without compromising the security or stability of the installed system." msgstr "" #. Tag: para -#: using-d-i.xml:2216 +#: using-d-i.xml:2210 #, no-c-format msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available from CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on" msgstr "" #. Tag: para -#: using-d-i.xml:2225 +#: using-d-i.xml:2219 #, no-c-format msgid "the tasks you select in the next step of the installation," msgstr "" #. Tag: para -#: using-d-i.xml:2230 +#: using-d-i.xml:2224 #, no-c-format msgid "which packages are needed for those tasks," msgstr "" #. Tag: para -#: using-d-i.xml:2235 +#: using-d-i.xml:2229 #, no-c-format msgid "which of those packages are present on the CDs or DVDs you have scanned, and" msgstr "" #. Tag: para -#: using-d-i.xml:2240 +#: using-d-i.xml:2234 #, no-c-format msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or volatile updates)." msgstr "" #. Tag: para -#: using-d-i.xml:2249 +#: using-d-i.xml:2243 #, no-c-format msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or volatile update available for them and those services have been configured." msgstr "" #. Tag: title -#: using-d-i.xml:2265 +#: using-d-i.xml:2259 #, no-c-format msgid "Selecting and Installing Software" msgstr "" #. Tag: para -#: using-d-i.xml:2267 +#: using-d-i.xml:2261 #, 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:2276 +#: using-d-i.xml:2270 #, 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:2303 +#: using-d-i.xml:2297 #, no-c-format msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can deselect them. You can even opt to install no tasks at all at this point." msgstr "" #. Tag: para -#: using-d-i.xml:2310 +#: using-d-i.xml:2304 #, 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:2316 +#: using-d-i.xml:2310 #, no-c-format msgid "Unless you are using the special KDE or Xfce/LXDE CDs, the <quote>Desktop environment</quote> task will install the GNOME desktop environment." msgstr "" #. Tag: para -#: using-d-i.xml:2321 +#: using-d-i.xml:2315 #, no-c-format msgid "It is not possible to interactively select a different desktop during the installation. However, it <emphasis>is</emphasis> possible to get &d-i; to install a KDE desktop environment instead of GNOME by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter <literal>desktop=kde</literal> at the boot prompt when starting the installer. Alternatively the more lightweight Xfce and LXDE desktop environments can be selected by using <literal>desktop=xfce</literal> or <literal>desktop=lxde</literal>." msgstr "" #. Tag: para -#: using-d-i.xml:2332 +#: using-d-i.xml:2326 #, no-c-format msgid "Some CD images (businesscard, netinst and DVD) also allow selection of the desired desktop environment from the graphical boot menu. Select the <quote>Advanced options</quote> option in the main menu and look for <quote>Alternative desktop environments</quote>." msgstr "" #. Tag: para -#: using-d-i.xml:2339 +#: using-d-i.xml:2333 #, no-c-format msgid "Note that this will only work if the packages needed for the desired desktop environment are actually available. If you are installing using a single full CD image, they will need to be downloaded from a mirror as most needed packages are only included on later CDs; installing KDE, Xfce or LXDE this way should work fine if you are using a DVD image or any other installation method." msgstr "" #. Tag: para -#: using-d-i.xml:2349 +#: using-d-i.xml:2343 #, no-c-format msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache2</classname>." msgstr "" #. Tag: para -#: using-d-i.xml:2360 +#: using-d-i.xml:2354 #, no-c-format msgid "The <quote>Standard system</quote> task will install any package that has a priority <quote>standard</quote>. This includes a lot of common utilities that are normally available on any Linux or Unix system. You should leave this task selected unless you know what you are doing and want a really minimal system." msgstr "" #. Tag: para -#: using-d-i.xml:2368 +#: using-d-i.xml:2362 #, no-c-format msgid "If during language selection a default locale other than the <quote>C</quote> locale was selected, <command>tasksel</command> will check if any localization tasks are defined for that locale and will automatically try to install relevant localization packages. This includes for example packages containing word lists or special fonts for your language. If a desktop environment was selected, it will also install appropriate localization packages for that (if available)." msgstr "" #. Tag: para -#: using-d-i.xml:2378 +#: using-d-i.xml:2372 #, no-c-format msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the selected tasks. If a particular program needs more information from the user, it will prompt you during this process." msgstr "" #. Tag: para -#: using-d-i.xml:2385 +#: using-d-i.xml:2379 #, no-c-format msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started." msgstr "" #. Tag: para -#: using-d-i.xml:2394 +#: using-d-i.xml:2388 #, no-c-format msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image." msgstr "" #. Tag: title -#: using-d-i.xml:2409 +#: using-d-i.xml:2403 #, no-c-format msgid "Making Your System Bootable" msgstr "" #. Tag: para -#: using-d-i.xml:2411 +#: using-d-i.xml:2405 #, 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:2426 +#: using-d-i.xml:2420 #, no-c-format msgid "Detecting other operating systems" msgstr "" #. Tag: para -#: using-d-i.xml:2428 +#: using-d-i.xml:2422 #, 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:2436 +#: using-d-i.xml:2430 #, 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:2454 -#, no-c-format -msgid "Install <command>aboot</command> on a Hard Disk" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2455 -#, 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:2475 +#: using-d-i.xml:2448 #, no-c-format msgid "<command>palo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2476 +#: using-d-i.xml:2449 #, 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:2485 +#: using-d-i.xml:2458 #, no-c-format msgid "hppa FIXME ( need more info )" msgstr "" #. Tag: title -#: using-d-i.xml:2497 +#: using-d-i.xml:2470 #, no-c-format msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2499 +#: using-d-i.xml:2472 #, no-c-format msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for new users and old hands alike." msgstr "" #. Tag: para -#: using-d-i.xml:2505 +#: using-d-i.xml:2478 #, 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:2511 +#: using-d-i.xml:2484 #, no-c-format msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use." msgstr "" #. Tag: title -#: using-d-i.xml:2524 +#: using-d-i.xml:2497 #, no-c-format msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2526 +#: using-d-i.xml:2499 #, 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:2536 +#: using-d-i.xml:2509 #, 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:2544 +#: using-d-i.xml:2517 #, 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:2551 +#: using-d-i.xml:2524 #, no-c-format msgid "Master Boot Record (MBR)" msgstr "" #. Tag: para -#: using-d-i.xml:2551 +#: using-d-i.xml:2524 #, 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:2558 +#: using-d-i.xml:2531 #, no-c-format msgid "new Debian partition" msgstr "" #. Tag: para -#: using-d-i.xml:2558 +#: using-d-i.xml:2531 #, 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:2567 +#: using-d-i.xml:2540 #, no-c-format msgid "Other choice" msgstr "" #. Tag: para -#: using-d-i.xml:2567 +#: using-d-i.xml:2540 #, no-c-format msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use traditional device names such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>." msgstr "" #. Tag: para -#: using-d-i.xml:2577 +#: using-d-i.xml:2550 #, 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:2593 +#: using-d-i.xml:2566 #, no-c-format msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2595 +#: using-d-i.xml:2568 #, 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:2611 +#: using-d-i.xml:2584 #, 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:2623 +#: using-d-i.xml:2596 #, no-c-format msgid "Choose the correct partition!" msgstr "" #. Tag: para -#: using-d-i.xml:2625 +#: using-d-i.xml:2598 #, 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:2640 +#: using-d-i.xml:2613 #, no-c-format msgid "EFI Partition Contents" msgstr "" #. Tag: para -#: using-d-i.xml:2642 +#: using-d-i.xml:2615 #, 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:2664 +#: using-d-i.xml:2637 #, no-c-format msgid "elilo.conf" msgstr "" #. Tag: para -#: using-d-i.xml:2665 +#: using-d-i.xml:2638 #, 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:2674 +#: using-d-i.xml:2647 #, no-c-format msgid "elilo.efi" msgstr "" #. Tag: para -#: using-d-i.xml:2675 +#: using-d-i.xml:2648 #, 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:2685 +#: using-d-i.xml:2658 #, no-c-format msgid "initrd.img" msgstr "" #. Tag: para -#: using-d-i.xml:2686 +#: using-d-i.xml:2659 #, 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:2698 +#: using-d-i.xml:2671 #, no-c-format msgid "readme.txt" msgstr "" #. Tag: para -#: using-d-i.xml:2699 +#: using-d-i.xml:2672 #, 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:2709 +#: using-d-i.xml:2682 #, no-c-format msgid "vmlinuz" msgstr "" #. Tag: para -#: using-d-i.xml:2710 +#: using-d-i.xml:2683 #, 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:2730 +#: using-d-i.xml:2703 #, no-c-format msgid "<command>arcboot</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2731 +#: using-d-i.xml:2704 #, 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" @@ -2137,289 +2119,289 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2750 +#: using-d-i.xml:2723 #, no-c-format msgid "scsi" msgstr "" #. Tag: para -#: using-d-i.xml:2751 +#: using-d-i.xml:2724 #, 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:2759 +#: using-d-i.xml:2732 #, no-c-format msgid "disk" msgstr "" #. Tag: para -#: using-d-i.xml:2760 +#: using-d-i.xml:2733 #, 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:2768 +#: using-d-i.xml:2741 #, no-c-format msgid "partnr" msgstr "" #. Tag: para -#: using-d-i.xml:2769 +#: using-d-i.xml:2742 #, 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:2777 +#: using-d-i.xml:2750 #, no-c-format msgid "config" msgstr "" #. Tag: para -#: using-d-i.xml:2778 +#: using-d-i.xml:2751 #, 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:2799 +#: using-d-i.xml:2772 #, no-c-format msgid "Install <command>Yaboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2800 +#: using-d-i.xml:2773 #, 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:2818 +#: using-d-i.xml:2791 #, no-c-format msgid "Install <command>Quik</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2819 +#: using-d-i.xml:2792 #, 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:2835 +#: using-d-i.xml:2808 #, no-c-format msgid "<command>zipl</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2836 +#: using-d-i.xml:2809 #, 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:2853 +#: using-d-i.xml:2826 #, no-c-format msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2855 +#: using-d-i.xml:2828 #, 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:2880 +#: using-d-i.xml:2853 #, no-c-format msgid "Continue Without Boot Loader" msgstr "" #. Tag: para -#: using-d-i.xml:2882 +#: using-d-i.xml:2855 #, 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)." msgstr "" #. Tag: para -#: using-d-i.xml:2889 +#: using-d-i.xml:2862 #, 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:2906 +#: using-d-i.xml:2879 #, no-c-format msgid "Finishing the Installation" msgstr "" #. Tag: para -#: using-d-i.xml:2907 +#: using-d-i.xml:2880 #, no-c-format msgid "This is the last step in the Debian installation process during which the installer will do any last minute tasks. It mostly consists of tidying up after the &d-i;." msgstr "" #. Tag: title -#: using-d-i.xml:2920 +#: using-d-i.xml:2893 #, no-c-format msgid "Setting the System Clock" msgstr "" #. Tag: para -#: using-d-i.xml:2922 +#: using-d-i.xml:2895 #, no-c-format msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed." msgstr "" #. Tag: para -#: using-d-i.xml:2929 +#: using-d-i.xml:2902 #, 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=\"powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase> <phrase arch=\"x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase>" msgstr "" #. Tag: para -#: using-d-i.xml:2940 +#: using-d-i.xml:2913 #, no-c-format msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made." msgstr "" #. Tag: title -#: using-d-i.xml:2955 +#: using-d-i.xml:2928 #, no-c-format msgid "Reboot the System" msgstr "" #. Tag: para -#: using-d-i.xml:2957 +#: using-d-i.xml:2930 #, no-c-format msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2963 +#: using-d-i.xml:2936 #, no-c-format msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian; from the DASD which you selected for the root filesystem during the first steps of the installation." msgstr "" #. Tag: title -#: using-d-i.xml:2976 +#: using-d-i.xml:2949 #, no-c-format msgid "Miscellaneous" msgstr "" #. Tag: para -#: using-d-i.xml:2977 +#: using-d-i.xml:2950 #, 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:2990 +#: using-d-i.xml:2963 #, no-c-format msgid "Saving the installation logs" msgstr "" #. Tag: para -#: using-d-i.xml:2992 +#: using-d-i.xml:2965 #, 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:2999 +#: using-d-i.xml:2972 #, 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:3019 +#: using-d-i.xml:2992 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "" #. Tag: para -#: using-d-i.xml:3021 +#: using-d-i.xml:2994 #, 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 the installer itself." msgstr "" #. Tag: para -#: using-d-i.xml:3039 +#: using-d-i.xml:3012 #, no-c-format msgid "For the graphical installer see also <xref linkend=\"gtk-using\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:3043 +#: using-d-i.xml:3016 #, no-c-format msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer." msgstr "" #. Tag: para -#: using-d-i.xml:3051 +#: using-d-i.xml:3024 #, 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:3060 +#: using-d-i.xml:3033 #, 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:3067 +#: using-d-i.xml:3040 #, 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:3073 +#: using-d-i.xml:3046 #, 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:3088 +#: using-d-i.xml:3061 #, no-c-format msgid "Installation Over the Network" msgstr "" #. Tag: para -#: using-d-i.xml:3090 +#: using-d-i.xml:3063 #, 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:3100 +#: using-d-i.xml:3073 #, 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:3113 +#: using-d-i.xml:3086 #, 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:3118 +#: using-d-i.xml:3091 #, 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:3130 +#: using-d-i.xml:3103 #, 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:3136 +#: using-d-i.xml:3109 #, 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" @@ -2428,127 +2410,127 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:3153 +#: using-d-i.xml:3126 #, no-c-format msgid "The <command>ssh</command> server in the installer uses a default configuration that does not send keep-alive packets. In principle, a connection to the system being installed should be kept open indefinitely. However, in some situations — depending on your local network setup — the connection may be lost after some period of inactivity. One common case where this can happen is when there is some form of Network Address Translation (NAT) somewhere between the client and the system being installed. Depending on at which point of the installation the connection was lost, you may or may not be able to resume the installation after reconnecting." msgstr "" #. Tag: para -#: using-d-i.xml:3166 +#: using-d-i.xml:3139 #, no-c-format msgid "You may be able to avoid the connection being dropped by adding the option <userinput>-o ServerAliveInterval=<replaceable>value</replaceable></userinput> when starting the <command>ssh</command> connection, or by adding that option in your <command>ssh</command> configuration file. Note however that in some cases adding this option may also <emphasis>cause</emphasis> a connection to be dropped (for example if keep-alive packets are sent during a brief network outage, from which <command>ssh</command> would otherwise have recovered), so it should only be used when needed." msgstr "" #. Tag: para -#: using-d-i.xml:3179 +#: using-d-i.xml:3152 #, no-c-format msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename><footnote> <para> The following command will remove an existing entry for a host: <command>ssh-keygen -R <<replaceable>hostname</replaceable>|<replaceable>IP address</replaceable>></command>. </para> </footnote> and try again." msgstr "" #. Tag: para -#: using-d-i.xml:3195 +#: using-d-i.xml:3168 #, 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:3205 +#: using-d-i.xml:3178 #, 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: title -#: using-d-i.xml:3225 +#: using-d-i.xml:3198 #, no-c-format msgid "Loading Missing Firmware" msgstr "" #. Tag: para -#: using-d-i.xml:3226 +#: using-d-i.xml:3199 #, no-c-format msgid "As described in <xref linkend=\"hardware-firmware\"/>, some devices require firmware to be loaded. In most cases the device will not work at all if the firmware is not available; sometimes basic functionality is not impaired if it is missing and the firmware is only needed to enable additional features." msgstr "" #. Tag: para -#: using-d-i.xml:3234 +#: using-d-i.xml:3207 #, no-c-format msgid "If a device driver requests firmware that is not available, &d-i; will display a dialog offering to load the missing firmware. If this option is selected, &d-i; will scan available devices for either loose firmware files or packages containing firmware. If found, the firmware will be copied to the correct location (<filename>/lib/firmware</filename>) and the driver module will be reloaded." msgstr "" #. Tag: para -#: using-d-i.xml:3244 +#: using-d-i.xml:3217 #, no-c-format msgid "Which devices are scanned and which file systems are supported depends on the architecture, the installation method and the stage of the installation. Especially during the early stages of the installation, loading the firmware is most likely to succeed from a FAT-formatted floppy disk or USB stick. <phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an MMC or SD card.</phrase>" msgstr "" #. Tag: para -#: using-d-i.xml:3254 +#: using-d-i.xml:3227 #, no-c-format msgid "Note that it is possible to skip loading the firmware if you know the device will also function without it, or if the device is not needed during the installation." msgstr "" #. Tag: para -#: using-d-i.xml:3261 +#: using-d-i.xml:3234 #, no-c-format msgid "Support for loading firmware is still relatively basic and is likely to be improved in future releases of the installer. Currently &d-i; will for example not display any warning if you choose to load missing firmware, but the requested firmware is not found. Please report any issues you encounter by filing an installation report (see <xref linkend=\"submit-bug\"/>)." msgstr "" #. Tag: title -#: using-d-i.xml:3272 +#: using-d-i.xml:3245 #, no-c-format msgid "Preparing a medium" msgstr "" #. Tag: para -#: using-d-i.xml:3273 +#: using-d-i.xml:3246 #, no-c-format msgid "Although in some cases the firmware can also be loaded from a partition on a hard disk, the most common method to load firmware will be from some removable medium such as a floppy disk or a USB stick. The firmware files or packages must be placed in either the root directory or a directory named <filename>/firmware</filename> of the file system on the medium. The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation." msgstr "" #. Tag: para -#: using-d-i.xml:3283 +#: using-d-i.xml:3256 #, no-c-format msgid "Tarballs containing current packages for the most common firmware are available from: <itemizedlist> <listitem><para> <ulink url=\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just download the tarball for the correct release and unpack it to the file system on the medium." msgstr "" #. Tag: para -#: using-d-i.xml:3297 +#: using-d-i.xml:3270 #, no-c-format msgid "If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) archive. The following overview should list most available firmware packages but is not guaranteed to be complete and may also contain non-firmware packages:" msgstr "" #. Tag: para -#: using-d-i.xml:3311 +#: using-d-i.xml:3284 #, no-c-format msgid "It is also possible to copy individual firmware files to the medium. Loose firmware could be obtained for example from an already installed system or from a hardware vendor." msgstr "" #. Tag: title -#: using-d-i.xml:3320 +#: using-d-i.xml:3293 #, no-c-format msgid "Firmware and the Installed System" msgstr "" #. Tag: para -#: using-d-i.xml:3321 +#: using-d-i.xml:3294 #, no-c-format msgid "Any firmware loaded during the installation will be copied automatically to the installed system. In most cases this will ensure that the device that requires the firmware will also work correctly after the system is rebooted into the installed system. However, if the installed system runs a different kernel version from the installer there is a slight chance that the firmware cannot be loaded due to version skew." msgstr "" #. Tag: para -#: using-d-i.xml:3330 +#: using-d-i.xml:3303 #, no-c-format msgid "If the firmware was loaded from a firmware package, &d-i; will also install this package for the installed system and will automatically add the non-free section of the package archive in APT's <filename>sources.list</filename>. This has the advantage that the firmware should be updated automatically if a new version becomes available." msgstr "" #. Tag: para -#: using-d-i.xml:3338 +#: using-d-i.xml:3311 #, no-c-format msgid "If loading the firmware was skipped during the installation, the relevant device will probably not work with the installed system until the firmware (package) is installed manually." msgstr "" #. Tag: para -#: using-d-i.xml:3345 +#: using-d-i.xml:3318 #, no-c-format msgid "If the firmware was loaded from loose firmware files, the firmware copied to the installed system will <emphasis>not</emphasis> be automatically updated unless the corresponding firmware package (if available) is installed after the installation is completed." msgstr "" |