diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 840 | ||||
| -rw-r--r-- | po/pot/preparing.pot | 554 | ||||
| -rw-r--r-- | po/pot/random-bits.pot | 116 |
3 files changed, 818 insertions, 692 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index c5f9187da..80d6a02d8 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: 2007-01-02 23:42+0000\n" +"POT-Creation-Date: 2007-01-03 07:31+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" @@ -26,296 +26,302 @@ msgstr "" msgid "Booting the Installer on &arch-title;" msgstr "" +#. Tag: para +#: boot-installer.xml:15 +#, no-c-format +msgid "For information on how to boot the graphical installer, see <xref linkend=\"graphical\"/>." +msgstr "" + #. Tag: title -#: boot-installer.xml:20 +#: boot-installer.xml:27 #, no-c-format msgid "Alpha Console Firmware" msgstr "" #. Tag: para -#: boot-installer.xml:21 +#: boot-installer.xml:28 #, 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:31 +#: boot-installer.xml:38 #, 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:38 +#: boot-installer.xml:45 #, 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:47 +#: boot-installer.xml:54 #, 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:54 +#: boot-installer.xml:61 #, 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:63 +#: boot-installer.xml:70 #, 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:76 +#: boot-installer.xml:83 #, 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:87 +#: boot-installer.xml:94 #, 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:95 +#: boot-installer.xml:102 #, 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:107 +#: boot-installer.xml:114 #, no-c-format msgid "System Type" msgstr "" #. Tag: entry -#: boot-installer.xml:108 +#: boot-installer.xml:115 #, no-c-format msgid "Console Type Supported" msgstr "" #. Tag: entry -#: boot-installer.xml:114 +#: boot-installer.xml:121 #, no-c-format msgid "alcor" msgstr "" #. Tag: entry -#: boot-installer.xml:115 boot-installer.xml:118 boot-installer.xml:124 boot-installer.xml:130 boot-installer.xml:133 boot-installer.xml:136 boot-installer.xml:139 boot-installer.xml:145 boot-installer.xml:148 boot-installer.xml:151 boot-installer.xml:160 boot-installer.xml:169 boot-installer.xml:184 boot-installer.xml:187 +#: boot-installer.xml:122 boot-installer.xml:125 boot-installer.xml:131 boot-installer.xml:137 boot-installer.xml:140 boot-installer.xml:143 boot-installer.xml:146 boot-installer.xml:152 boot-installer.xml:155 boot-installer.xml:158 boot-installer.xml:167 boot-installer.xml:176 boot-installer.xml:191 boot-installer.xml:194 #, no-c-format msgid "ARC or SRM" msgstr "" #. Tag: entry -#: boot-installer.xml:117 +#: boot-installer.xml:124 #, no-c-format msgid "avanti" msgstr "" #. Tag: entry -#: boot-installer.xml:120 +#: boot-installer.xml:127 #, no-c-format msgid "book1" msgstr "" #. Tag: entry -#: boot-installer.xml:121 boot-installer.xml:127 boot-installer.xml:142 boot-installer.xml:154 boot-installer.xml:163 boot-installer.xml:166 boot-installer.xml:172 boot-installer.xml:178 boot-installer.xml:181 +#: boot-installer.xml:128 boot-installer.xml:134 boot-installer.xml:149 boot-installer.xml:161 boot-installer.xml:170 boot-installer.xml:173 boot-installer.xml:179 boot-installer.xml:185 boot-installer.xml:188 #, no-c-format msgid "SRM only" msgstr "" #. Tag: entry -#: boot-installer.xml:123 +#: boot-installer.xml:130 #, no-c-format msgid "cabriolet" msgstr "" #. Tag: entry -#: boot-installer.xml:126 +#: boot-installer.xml:133 #, no-c-format msgid "dp264" msgstr "" #. Tag: entry -#: boot-installer.xml:129 +#: boot-installer.xml:136 #, no-c-format msgid "eb164" msgstr "" #. Tag: entry -#: boot-installer.xml:132 +#: boot-installer.xml:139 #, no-c-format msgid "eb64p" msgstr "" #. Tag: entry -#: boot-installer.xml:135 +#: boot-installer.xml:142 #, no-c-format msgid "eb66" msgstr "" #. Tag: entry -#: boot-installer.xml:138 +#: boot-installer.xml:145 #, no-c-format msgid "eb66p" msgstr "" #. Tag: entry -#: boot-installer.xml:141 +#: boot-installer.xml:148 #, no-c-format msgid "jensen" msgstr "" #. Tag: entry -#: boot-installer.xml:144 +#: boot-installer.xml:151 #, no-c-format msgid "lx164" msgstr "" #. Tag: entry -#: boot-installer.xml:147 +#: boot-installer.xml:154 #, no-c-format msgid "miata" msgstr "" #. Tag: entry -#: boot-installer.xml:150 +#: boot-installer.xml:157 #, no-c-format msgid "mikasa" msgstr "" #. Tag: entry -#: boot-installer.xml:153 +#: boot-installer.xml:160 #, no-c-format msgid "mikasa-p" msgstr "" #. Tag: entry -#: boot-installer.xml:156 +#: boot-installer.xml:163 #, no-c-format msgid "nautilus" msgstr "" #. Tag: entry -#: boot-installer.xml:157 +#: boot-installer.xml:164 #, no-c-format msgid "ARC (see motherboard manual) or SRM" msgstr "" #. Tag: entry -#: boot-installer.xml:159 +#: boot-installer.xml:166 #, no-c-format msgid "noname" msgstr "" #. Tag: entry -#: boot-installer.xml:162 +#: boot-installer.xml:169 #, no-c-format msgid "noritake" msgstr "" #. Tag: entry -#: boot-installer.xml:165 +#: boot-installer.xml:172 #, no-c-format msgid "noritake-p" msgstr "" #. Tag: entry -#: boot-installer.xml:168 +#: boot-installer.xml:175 #, no-c-format msgid "pc164" msgstr "" #. Tag: entry -#: boot-installer.xml:171 +#: boot-installer.xml:178 #, no-c-format msgid "rawhide" msgstr "" #. Tag: entry -#: boot-installer.xml:174 +#: boot-installer.xml:181 #, no-c-format msgid "ruffian" msgstr "" #. Tag: entry -#: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193 +#: boot-installer.xml:182 boot-installer.xml:197 boot-installer.xml:200 #, no-c-format msgid "ARC only" msgstr "" #. Tag: entry -#: boot-installer.xml:177 +#: boot-installer.xml:184 #, no-c-format msgid "sable" msgstr "" #. Tag: entry -#: boot-installer.xml:180 +#: boot-installer.xml:187 #, no-c-format msgid "sable-g" msgstr "" #. Tag: entry -#: boot-installer.xml:183 +#: boot-installer.xml:190 #, no-c-format msgid "sx164" msgstr "" #. Tag: entry -#: boot-installer.xml:186 +#: boot-installer.xml:193 #, no-c-format msgid "takara" msgstr "" #. Tag: entry -#: boot-installer.xml:189 +#: boot-installer.xml:196 #, no-c-format msgid "<entry>xl</entry>" msgstr "" #. Tag: entry -#: boot-installer.xml:192 +#: boot-installer.xml:199 #, no-c-format msgid "<entry>xlt</entry>" msgstr "" #. Tag: para -#: boot-installer.xml:200 +#: boot-installer.xml:207 #, 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:209 +#: boot-installer.xml:216 #, 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:215 +#: boot-installer.xml:222 #, 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:221 +#: boot-installer.xml:228 #, 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:231 +#: boot-installer.xml:238 #, 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:238 +#: boot-installer.xml:245 #, 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" @@ -326,25 +332,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:253 +#: boot-installer.xml:260 #, 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:264 +#: boot-installer.xml:271 #, 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:283 boot-installer.xml:999 boot-installer.xml:1490 boot-installer.xml:1985 boot-installer.xml:2067 boot-installer.xml:2156 boot-installer.xml:2506 boot-installer.xml:2602 +#: boot-installer.xml:290 boot-installer.xml:1006 boot-installer.xml:1497 boot-installer.xml:1992 boot-installer.xml:2074 boot-installer.xml:2163 boot-installer.xml:2513 boot-installer.xml:2609 #, no-c-format msgid "Booting with TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:284 +#: boot-installer.xml:291 #, 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" @@ -360,7 +366,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:302 +#: boot-installer.xml:309 #, no-c-format msgid "" "Then, to boot from the first Ethernet interface, you would type: <informalexample><screen>\n" @@ -369,25 +375,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:311 +#: boot-installer.xml:318 #, 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:323 +#: boot-installer.xml:330 #, no-c-format msgid ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0"" msgstr "" #. Tag: title -#: boot-installer.xml:328 +#: boot-installer.xml:335 #, no-c-format msgid "Booting from CD-ROM with the SRM Console" msgstr "" #. Tag: para -#: boot-installer.xml:329 +#: boot-installer.xml:336 #, no-c-format msgid "" "Type <informalexample><screen>\n" @@ -396,25 +402,25 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:341 +#: boot-installer.xml:348 #, no-c-format msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" msgstr "" #. Tag: para -#: boot-installer.xml:342 +#: boot-installer.xml:349 #, 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:358 +#: boot-installer.xml:365 #, no-c-format msgid "Booting from Floppies with the SRM Console" msgstr "" #. Tag: para -#: boot-installer.xml:359 +#: boot-installer.xml:366 #, no-c-format msgid "" "At the SRM prompt (<prompt>>>></prompt>), issue the following command: <informalexample><screen>\n" @@ -425,7 +431,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:376 +#: boot-installer.xml:383 #, no-c-format msgid "" "If you want to specify kernel parameters when booting via <command>aboot</command>, use the following command: <informalexample><screen>\n" @@ -434,37 +440,37 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:388 +#: boot-installer.xml:395 #, 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:398 +#: boot-installer.xml:405 #, no-c-format msgid "Booting from Floppies with the ARC or AlphaBIOS Console" msgstr "" #. Tag: para -#: boot-installer.xml:400 +#: boot-installer.xml:407 #, 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:409 +#: boot-installer.xml:416 #, no-c-format msgid "Booting with MILO" msgstr "" #. Tag: para -#: boot-installer.xml:410 +#: boot-installer.xml:417 #, 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:416 +#: boot-installer.xml:423 #, 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" @@ -473,49 +479,49 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:435 +#: boot-installer.xml:442 #, no-c-format msgid "Booting from TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:441 boot-installer.xml:1005 boot-installer.xml:1508 boot-installer.xml:1991 boot-installer.xml:2512 boot-installer.xml:2608 +#: boot-installer.xml:448 boot-installer.xml:1012 boot-installer.xml:1515 boot-installer.xml:1998 boot-installer.xml:2519 boot-installer.xml:2615 #, 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:446 boot-installer.xml:1010 boot-installer.xml:1513 boot-installer.xml:1996 boot-installer.xml:2517 boot-installer.xml:2613 +#: boot-installer.xml:453 boot-installer.xml:1017 boot-installer.xml:1520 boot-installer.xml:2003 boot-installer.xml:2524 boot-installer.xml:2620 #, 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:451 boot-installer.xml:1015 boot-installer.xml:1518 boot-installer.xml:2001 boot-installer.xml:2522 boot-installer.xml:2618 +#: boot-installer.xml:458 boot-installer.xml:1022 boot-installer.xml:1525 boot-installer.xml:2008 boot-installer.xml:2529 boot-installer.xml:2625 #, no-c-format msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:459 +#: boot-installer.xml:466 #, no-c-format msgid "Booting from TFTP on Netwinder" msgstr "" #. Tag: para -#: boot-installer.xml:460 +#: boot-installer.xml:467 #, no-c-format msgid "Netwinders have two network interfaces: A 10Mbps NE2000-compatible card (which is generally referred to as <literal>eth0</literal>) and a 100Mbps Tulip card. There may be problems loading the image via TFTP using the 100Mbps card so it is recommended that you use the 10Mbps interface (the one labeled with <literal>10 Base-T</literal>)." msgstr "" #. Tag: para -#: boot-installer.xml:469 +#: boot-installer.xml:476 #, no-c-format msgid "You need NeTTrom 2.2.1 or later to boot the installation system, and version 2.3.3 is recommended. Unfortunately, firmware files are currently not available for download because of license issues. If this situation changes, you may find new images at <ulink url=\"http//www.netwinder.org/\"></ulink>." msgstr "" #. Tag: para -#: boot-installer.xml:477 +#: boot-installer.xml:484 #, no-c-format msgid "" "When you boot your Netwinder you have to interrupt the boot process during the countdown. This allows you to set a number of firmware settings needed in order to boot the installer. First of all, start by loading the default settings: <informalexample><screen>\n" @@ -542,103 +548,103 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:529 +#: boot-installer.xml:536 #, no-c-format msgid "Booting from TFTP on CATS" msgstr "" #. Tag: para -#: boot-installer.xml:530 +#: boot-installer.xml:537 #, no-c-format msgid "On CATS machines, use <command>boot de0:</command> or similar at the Cyclone prompt." msgstr "" #. Tag: title -#: boot-installer.xml:540 +#: boot-installer.xml:547 #, no-c-format msgid "Booting from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1127 boot-installer.xml:1948 boot-installer.xml:2294 boot-installer.xml:2646 +#: boot-installer.xml:553 boot-installer.xml:723 boot-installer.xml:1134 boot-installer.xml:1955 boot-installer.xml:2301 boot-installer.xml:2653 #, 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:557 boot-installer.xml:727 boot-installer.xml:1138 boot-installer.xml:1959 boot-installer.xml:2305 boot-installer.xml:2657 +#: boot-installer.xml:564 boot-installer.xml:734 boot-installer.xml:1145 boot-installer.xml:1966 boot-installer.xml:2312 boot-installer.xml:2664 #, 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:565 boot-installer.xml:735 boot-installer.xml:1146 boot-installer.xml:1967 boot-installer.xml:2313 boot-installer.xml:2665 +#: boot-installer.xml:572 boot-installer.xml:742 boot-installer.xml:1153 boot-installer.xml:1974 boot-installer.xml:2320 boot-installer.xml:2672 #, 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:573 boot-installer.xml:743 boot-installer.xml:1154 boot-installer.xml:1975 boot-installer.xml:2321 boot-installer.xml:2673 +#: boot-installer.xml:580 boot-installer.xml:750 boot-installer.xml:1161 boot-installer.xml:1982 boot-installer.xml:2328 boot-installer.xml:2680 #, no-c-format msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:580 +#: boot-installer.xml:587 #, no-c-format msgid "To boot a CD-ROM from the Cyclone console prompt, use the command <command>boot cd0:cats.bin</command>" msgstr "" #. Tag: title -#: boot-installer.xml:589 +#: boot-installer.xml:596 #, no-c-format msgid "Booting from Firmware" msgstr "" #. Tag: para -#: boot-installer.xml:595 +#: boot-installer.xml:602 #, 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:601 +#: boot-installer.xml:608 #, 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:612 +#: boot-installer.xml:619 #, no-c-format msgid "Booting the NSLU2" msgstr "" #. Tag: para -#: boot-installer.xml:613 +#: boot-installer.xml:620 #, no-c-format msgid "There are three ways how to put the installer firmware into flash:" msgstr "" #. Tag: title -#: boot-installer.xml:619 +#: boot-installer.xml:626 #, no-c-format msgid "Using the NSLU2 web interface" msgstr "" #. Tag: para -#: boot-installer.xml:620 +#: boot-installer.xml:627 #, 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:631 +#: boot-installer.xml:638 #, no-c-format msgid "Via the network using Linux/Unix" msgstr "" #. Tag: para -#: boot-installer.xml:632 +#: boot-installer.xml:639 #, 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" @@ -647,55 +653,55 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:693 +#: boot-installer.xml:700 #, no-c-format msgid "Via the network using Windows" msgstr "" #. Tag: para -#: boot-installer.xml:694 +#: boot-installer.xml:701 #, 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:710 boot-installer.xml:1121 boot-installer.xml:1936 boot-installer.xml:2288 boot-installer.xml:2640 +#: boot-installer.xml:717 boot-installer.xml:1128 boot-installer.xml:1943 boot-installer.xml:2295 boot-installer.xml:2647 #, no-c-format msgid "Booting from a CD-ROM" msgstr "" #. Tag: title -#: boot-installer.xml:848 +#: boot-installer.xml:855 #, no-c-format msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: boot-installer.xml:851 +#: boot-installer.xml:858 #, 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:856 +#: boot-installer.xml:863 #, 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:866 +#: boot-installer.xml:873 #, 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 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 image, without needing the network." msgstr "" #. Tag: para -#: boot-installer.xml:875 +#: boot-installer.xml:882 #, 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:896 +#: boot-installer.xml:903 #, no-c-format msgid "" "image=/boot/newinstall/vmlinuz\n" @@ -704,13 +710,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:896 +#: boot-installer.xml:903 #, 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:905 +#: boot-installer.xml:912 #, 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 (sometimes in the <filename>/boot/boot/grub/</filename>), add the following lines: <informalexample><screen>\n" @@ -721,127 +727,127 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:916 +#: boot-installer.xml:923 #, no-c-format msgid "Note that the value of the <userinput>ramdisk_size</userinput> may need to be adjusted for the size of the initrd image. From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>." msgstr "" #. Tag: title -#: boot-installer.xml:927 +#: boot-installer.xml:934 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "" #. Tag: para -#: boot-installer.xml:928 +#: boot-installer.xml:935 #, 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:941 boot-installer.xml:2048 boot-installer.xml:2548 boot-installer.xml:2691 +#: boot-installer.xml:948 boot-installer.xml:2055 boot-installer.xml:2555 boot-installer.xml:2698 #, no-c-format msgid "Booting from Floppies" msgstr "" #. Tag: para -#: boot-installer.xml:942 boot-installer.xml:2556 +#: boot-installer.xml:949 boot-installer.xml:2563 #, 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:949 +#: boot-installer.xml:956 #, 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:955 +#: boot-installer.xml:962 #, 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:965 +#: boot-installer.xml:972 #, 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:974 +#: boot-installer.xml:981 #, 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:980 +#: boot-installer.xml:987 #, 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:989 +#: boot-installer.xml:996 #, 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: para -#: boot-installer.xml:1023 +#: boot-installer.xml:1030 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "" #. Tag: title -#: boot-installer.xml:1029 +#: boot-installer.xml:1036 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "" #. Tag: para -#: boot-installer.xml:1030 +#: boot-installer.xml:1037 #, 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:1041 +#: boot-installer.xml:1048 #, no-c-format msgid "NIC with Network BootROM" msgstr "" #. Tag: para -#: boot-installer.xml:1042 +#: boot-installer.xml:1049 #, no-c-format msgid "It could be that your Network Interface Card provides TFTP boot functionality." msgstr "" #. Tag: para -#: boot-installer.xml:1047 +#: boot-installer.xml:1054 #, 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:1055 +#: boot-installer.xml:1062 #, no-c-format msgid "Etherboot" msgstr "" #. Tag: para -#: boot-installer.xml:1056 +#: boot-installer.xml:1063 #, 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:1065 +#: boot-installer.xml:1072 #, no-c-format msgid "The Boot Prompt" msgstr "" #. Tag: para -#: boot-installer.xml:1066 +#: boot-installer.xml:1073 #, no-c-format msgid "" "When the installer boots, you should be presented with a friendly graphical screen showing the Debian logo and the boot prompt: <informalexample><screen>\n" @@ -850,253 +856,253 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1078 +#: boot-installer.xml:1085 #, no-c-format msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</keycap>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>install</userinput>) and a space before the first parameter (e.g., <userinput>install fb=false</userinput>)." msgstr "" #. Tag: para -#: boot-installer.xml:1087 +#: boot-installer.xml:1094 #, no-c-format msgid "If you are installing the system via a remote management device that provides a text interface to the VGA console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot prompt. 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). You can blindly press F1<footnote> <para> In some cases these devices will require special escape sequences to enact this keypress, for example the IRA uses <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</keycap>. </para> </footnote> to bypass this screen and view the help text. Once you are past the splash screen and at the help text your keystrokes will be echoed at the prompt as expected. 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:1162 +#: boot-installer.xml:1169 #, no-c-format msgid "CD Contents" msgstr "" #. Tag: para -#: boot-installer.xml:1164 +#: boot-installer.xml:1171 #, 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:1180 +#: boot-installer.xml:1187 #, 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:1196 +#: boot-installer.xml:1203 #, 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:1205 +#: boot-installer.xml:1212 #, 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:1217 +#: boot-installer.xml:1224 #, 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:1236 +#: boot-installer.xml:1243 #, no-c-format msgid "IMPORTANT" msgstr "" #. Tag: para -#: boot-installer.xml:1237 +#: boot-installer.xml:1244 #, 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:1249 +#: boot-installer.xml:1256 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "" #. Tag: para -#: boot-installer.xml:1256 +#: boot-installer.xml:1263 #, 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:1262 +#: boot-installer.xml:1269 #, 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:1268 +#: boot-installer.xml:1275 #, 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:1279 +#: boot-installer.xml:1286 #, 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:1290 +#: boot-installer.xml:1297 #, 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:1302 +#: boot-installer.xml:1309 #, 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:1312 +#: boot-installer.xml:1319 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "" #. Tag: para -#: boot-installer.xml:1313 +#: boot-installer.xml:1320 #, 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:1324 +#: boot-installer.xml:1331 #, 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:1330 +#: boot-installer.xml:1337 #, 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:1344 +#: boot-installer.xml:1351 #, 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:1351 +#: boot-installer.xml:1358 #, 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:1358 +#: boot-installer.xml:1365 #, 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:1365 +#: boot-installer.xml:1372 #, 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:1379 +#: boot-installer.xml:1386 #, no-c-format msgid "Installing using a Serial Console" msgstr "" #. Tag: para -#: boot-installer.xml:1381 +#: boot-installer.xml:1388 #, 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:1392 +#: boot-installer.xml:1399 #, 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:1399 +#: boot-installer.xml:1406 #, 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:1410 +#: boot-installer.xml:1417 #, 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:1419 +#: boot-installer.xml:1426 #, 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:1428 +#: boot-installer.xml:1435 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "" #. Tag: para -#: boot-installer.xml:1430 +#: boot-installer.xml:1437 #, 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:1442 +#: boot-installer.xml:1449 #, 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:1460 +#: boot-installer.xml:1467 #, 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:1465 +#: boot-installer.xml:1472 #, 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:1472 +#: boot-installer.xml:1479 #, 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:1481 boot-installer.xml:1617 +#: boot-installer.xml:1488 boot-installer.xml:1624 #, 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:1492 +#: boot-installer.xml:1499 #, 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 thru 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:1526 +#: boot-installer.xml:1533 #, 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:1537 +#: boot-installer.xml:1544 #, no-c-format msgid "Configuring the Server" msgstr "" #. Tag: para -#: boot-installer.xml:1538 +#: boot-installer.xml:1545 #, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n" @@ -1109,13 +1115,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1548 +#: boot-installer.xml:1555 #, 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:1558 +#: boot-installer.xml:1565 #, no-c-format msgid "" "# cd /var/lib/tftp\n" @@ -1127,331 +1133,331 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1558 +#: boot-installer.xml:1565 #, 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:1575 +#: boot-installer.xml:1582 #, no-c-format msgid "Configuring the Client" msgstr "" #. Tag: para -#: boot-installer.xml:1576 +#: boot-installer.xml:1583 #, 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:1608 +#: boot-installer.xml:1615 #, 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:1630 +#: boot-installer.xml:1637 #, no-c-format msgid "Choosing an Installation Method" msgstr "" #. Tag: para -#: boot-installer.xml:1632 +#: boot-installer.xml:1639 #, no-c-format msgid "Some &arch-title; subarchs have the option of booting using either a 2.4.x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux kernel. The installer should also require less memory when using a 2.4.x linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses tmpfs." msgstr "" #. Tag: para -#: boot-installer.xml:1640 +#: boot-installer.xml:1647 #, no-c-format msgid "If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; kernel parameter." msgstr "" #. Tag: para -#: boot-installer.xml:1645 +#: boot-installer.xml:1652 #, no-c-format msgid "Make sure <userinput>root=/dev/ram</userinput> is one of your kernel parameters." msgstr "" #. Tag: para -#: boot-installer.xml:1650 +#: boot-installer.xml:1657 #, no-c-format msgid "If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's &arch-title; debian-installer FAQ</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:1667 +#: boot-installer.xml:1674 #, no-c-format msgid "Amiga" msgstr "" #. Tag: para -#: boot-installer.xml:1668 +#: boot-installer.xml:1675 #, no-c-format msgid "The only method of installation available to amiga is the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" #. Tag: para -#: boot-installer.xml:1674 +#: boot-installer.xml:1681 #, no-c-format msgid "Amiga does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter <userinput>fb=false</userinput>." msgstr "" #. Tag: title -#: boot-installer.xml:1683 +#: boot-installer.xml:1690 #, no-c-format msgid "Atari" msgstr "" #. Tag: para -#: boot-installer.xml:1684 +#: boot-installer.xml:1691 #, no-c-format msgid "The installer for atari may be started from either the hard drive (see <xref linkend=\"m68k-boot-hd\"/>) or from floppies (see <xref linkend=\"boot-from-floppies\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" #. Tag: para -#: boot-installer.xml:1691 +#: boot-installer.xml:1698 #, no-c-format msgid "Atari does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter <userinput>fb=false</userinput>." msgstr "" #. Tag: title -#: boot-installer.xml:1700 +#: boot-installer.xml:1707 #, no-c-format msgid "BVME6000" msgstr "" #. Tag: para -#: boot-installer.xml:1701 +#: boot-installer.xml:1708 #, no-c-format msgid "The installer for BVME6000 may be started from a cdrom (see <xref linkend=\"m68k-boot-cdrom\"/>), floppies (see <xref linkend=\"boot-from-floppies\"/>), or the net (see <xref linkend=\"boot-tftp\"/>)." msgstr "" #. Tag: title -#: boot-installer.xml:1711 +#: boot-installer.xml:1718 #, no-c-format msgid "Macintosh" msgstr "" #. Tag: para -#: boot-installer.xml:1712 +#: boot-installer.xml:1719 #, no-c-format msgid "The only method of installation available to mac is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis> Macs do not have a working 2.4.x kernel." msgstr "" #. Tag: para -#: boot-installer.xml:1719 +#: boot-installer.xml:1726 #, no-c-format msgid "If your hardware uses a 53c9x-based scsi bus, then you may need to include the kernel parameter <userinput>mac53c9x=1,0</userinput>. Hardware with two such scsi buses, such as the Quadra 950, will need <userinput>mac53c9x=2,0</userinput> instead. Alternatively, the parameter can be specified as <userinput>mac53c9x=-1,0</userinput> which will leave autodetection on, but which will disable SCSI disconnects. Note that specifying this parameter is only necessary if you have more than one hard disk; otherwise, the system will run faster if you do not specify it." msgstr "" #. Tag: title -#: boot-installer.xml:1734 +#: boot-installer.xml:1741 #, no-c-format msgid "MVME147 and MVME16x" msgstr "" #. Tag: para -#: boot-installer.xml:1735 +#: boot-installer.xml:1742 #, no-c-format msgid "The installer for MVME147 and MVME16x may be started from either floppies (see <xref linkend=\"boot-from-floppies\"/>) or the net (see <xref linkend=\"boot-tftp\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" #. Tag: title -#: boot-installer.xml:1745 +#: boot-installer.xml:1752 #, no-c-format msgid "Q40/Q60" msgstr "" #. Tag: para -#: boot-installer.xml:1746 +#: boot-installer.xml:1753 #, no-c-format msgid "The only method of installation available to Q40/Q60 is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" #. Tag: title -#: boot-installer.xml:1757 +#: boot-installer.xml:1764 #, no-c-format msgid "Booting from a Hard Disk" msgstr "" #. Tag: para -#: boot-installer.xml:1763 boot-installer.xml:2367 +#: boot-installer.xml:1770 boot-installer.xml:2374 #, 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:1769 boot-installer.xml:2373 +#: boot-installer.xml:1776 boot-installer.xml:2380 #, 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: para -#: boot-installer.xml:1778 +#: boot-installer.xml:1785 #, no-c-format msgid "At least six different ramdisks may be used to boot from the hard drive, three different types each with and without support for a 2.2.x linux kernel (see <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink> for details)." msgstr "" #. Tag: para -#: boot-installer.xml:1786 +#: boot-installer.xml:1793 #, no-c-format msgid "The three different types of ramdisks are <filename>cdrom</filename>, <filename>hd-media</filename>, and <filename>nativehd</filename>. These ramdisks differ only in their source for installation packages. The <filename>cdrom</filename> ramdisk uses a cdrom to get debian-installer packages. The <filename>hd-media</filename> ramdisk uses an iso image file of a cdrom currently residing on a hard disk. Finally, the <filename>nativehd</filename> ramdisk uses the net to install packages." msgstr "" #. Tag: title -#: boot-installer.xml:1807 +#: boot-installer.xml:1814 #, no-c-format msgid "Booting from AmigaOS" msgstr "" #. Tag: para -#: boot-installer.xml:1808 +#: boot-installer.xml:1815 #, no-c-format msgid "In the <command>Workbench</command>, start the Linux installation process by double-clicking on the <guiicon>StartInstall</guiicon> icon in the <filename>debian</filename> directory." msgstr "" #. Tag: para -#: boot-installer.xml:1814 +#: boot-installer.xml:1821 #, no-c-format msgid "You may have to press the &enterkey; key twice after the Amiga installer program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue down at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:1829 +#: boot-installer.xml:1836 #, no-c-format msgid "Booting from Atari TOS" msgstr "" #. Tag: para -#: boot-installer.xml:1830 +#: boot-installer.xml:1837 #, no-c-format msgid "At the GEM desktop, start the Linux installation process by double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the <filename>debian</filename> directory and clicking <guibutton>Ok</guibutton> at the program options dialog box." msgstr "" #. Tag: para -#: boot-installer.xml:1837 +#: boot-installer.xml:1844 #, no-c-format msgid "You may have to press the &enterkey; key after the Atari bootstrap program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:1852 +#: boot-installer.xml:1859 #, no-c-format msgid "Booting from MacOS" msgstr "" #. Tag: para -#: boot-installer.xml:1853 +#: boot-installer.xml:1860 #, no-c-format msgid "You must retain the original Mac system and boot from it. It is <emphasis>essential</emphasis> that, when booting MacOS in preparation for booting the Penguin linux loader, you hold the <keycap>shift</keycap> key down to prevent extensions from loading. If you don't use MacOS except for loading linux, you can accomplish the same thing by removing all extensions and control panels from the Mac's System Folder. Otherwise extensions may be left running and cause random problems with the running linux kernel." msgstr "" #. Tag: para -#: boot-installer.xml:1864 +#: boot-installer.xml:1871 #, no-c-format msgid "Macs require the <command>Penguin</command> bootloader. If you do not have the tools to handle a <command>Stuffit</command> archive, &penguin19.hfs; is an hfs disk image with <command>Penguin</command> unpacked. <xref linkend=\"create-floppy\"/> describes how to copy this image to a floppy." msgstr "" #. Tag: para -#: boot-installer.xml:1873 +#: boot-installer.xml:1880 #, no-c-format msgid "At the MacOS desktop, start the Linux installation process by double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in the <filename>Penguin</filename> directory. The <command>Penguin</command> booter will start up. Go to the <guimenuitem>Settings</guimenuitem> item in the <guimenu>File</guimenu> menu, click the <guilabel>Kernel</guilabel> tab. Select the kernel (<filename>vmlinuz</filename>) and ramdisk (<filename>initrd.gz</filename>) images in the <filename>install</filename> directory by clicking on the corresponding buttons in the upper right corner, and navigating the file select dialogs to locate the files." msgstr "" #. Tag: para -#: boot-installer.xml:1888 +#: boot-installer.xml:1895 #, no-c-format msgid "To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -> <guimenuitem>Settings...</guimenuitem>, then switch to the <guilabel>Options</guilabel> tab. Boot parameters may be typed in to the text entry area. If you will always want to use these settings, select <guimenu>File</guimenu> -> <guimenuitem>Save Settings as Default</guimenuitem>." msgstr "" #. Tag: para -#: boot-installer.xml:1897 +#: boot-installer.xml:1904 #, no-c-format msgid "Close the <guilabel>Settings</guilabel> dialog, save the settings and start the bootstrap using the <guimenuitem>Boot Now</guimenuitem> item in the <guimenu>File</guimenu> menu." msgstr "" #. Tag: para -#: boot-installer.xml:1904 +#: boot-installer.xml:1911 #, no-c-format msgid "The <command>Penguin</command> booter will output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:1919 +#: boot-installer.xml:1926 #, no-c-format msgid "Booting from Q40/Q60" msgstr "" #. Tag: para -#: boot-installer.xml:1921 +#: boot-installer.xml:1928 #, no-c-format msgid "FIXME" msgstr "" #. Tag: para -#: boot-installer.xml:1925 +#: boot-installer.xml:1932 #, no-c-format msgid "The installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:1937 +#: boot-installer.xml:1944 #, no-c-format msgid "Currently, the only &arch-title; subarchitecture that supports CD-ROM booting is the BVME6000." msgstr "" #. Tag: para -#: boot-installer.xml:2009 +#: boot-installer.xml:2016 #, no-c-format msgid "After booting the VMEbus systems you will be presented with the LILO <prompt>Boot:</prompt> prompt. At that prompt enter one of the following to boot Linux and begin installation proper of the Debian software using vt102 terminal emulation:" msgstr "" #. Tag: para -#: boot-installer.xml:2020 +#: boot-installer.xml:2027 #, no-c-format msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000" msgstr "" #. Tag: para -#: boot-installer.xml:2025 +#: boot-installer.xml:2032 #, no-c-format msgid "type <screen>i162 &enterkey;</screen> to install an MVME162" msgstr "" #. Tag: para -#: boot-installer.xml:2030 +#: boot-installer.xml:2037 #, no-c-format msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167" msgstr "" #. Tag: para -#: boot-installer.xml:2037 +#: boot-installer.xml:2044 #, no-c-format msgid "You may additionally append the string <screen>TERM=vt100</screen> to use vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>." msgstr "" #. Tag: para -#: boot-installer.xml:2049 +#: boot-installer.xml:2056 #, no-c-format msgid "For most &arch-title; architectures, booting from a local filesystem is the recommended method." msgstr "" #. Tag: para -#: boot-installer.xml:2054 +#: boot-installer.xml:2061 #, no-c-format msgid "Booting from the boot floppy is supported only for Atari and VME (with a SCSI floppy drive on VME) at this time." msgstr "" #. Tag: title -#: boot-installer.xml:2070 boot-installer.xml:2117 +#: boot-installer.xml:2077 boot-installer.xml:2124 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:2071 +#: boot-installer.xml:2078 #, no-c-format msgid "" "After entering the command monitor use <informalexample><screen>\n" @@ -1462,13 +1468,13 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:2090 boot-installer.xml:2139 boot-installer.xml:2194 boot-installer.xml:2233 +#: boot-installer.xml:2097 boot-installer.xml:2146 boot-installer.xml:2201 boot-installer.xml:2240 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:2091 boot-installer.xml:2195 +#: boot-installer.xml:2098 boot-installer.xml:2202 #, no-c-format msgid "" "On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load the SiByl boot loader via TFTP which will then load and start the Debian installer. In most cases, you will first obtain an IP address via DHCP but it is also possible to configure a static address. In order to use DHCP, you can enter the following command on the CFE prompt: <informalexample><screen>\n" @@ -1479,19 +1485,19 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:2114 boot-installer.xml:2218 boot-installer.xml:2749 +#: boot-installer.xml:2121 boot-installer.xml:2225 boot-installer.xml:2756 #, no-c-format msgid "Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2118 +#: boot-installer.xml:2125 #, 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:2123 +#: boot-installer.xml:2130 #, 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" @@ -1500,139 +1506,139 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2133 +#: boot-installer.xml:2140 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: para -#: boot-installer.xml:2140 boot-installer.xml:2234 +#: boot-installer.xml:2147 boot-installer.xml:2241 #, no-c-format msgid "You cannot pass any boot parameters directly from the CFE prompt. Instead, you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP server and add your parameters to the <replaceable>extra_args</replaceable> variable." msgstr "" #. Tag: title -#: boot-installer.xml:2159 boot-installer.xml:2221 +#: boot-installer.xml:2166 boot-installer.xml:2228 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:2160 +#: boot-installer.xml:2167 #, 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:2170 +#: boot-installer.xml:2177 #, 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:2179 +#: boot-installer.xml:2186 #, 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. This option is not available on Qube 2700 (Qube1) machines since they have no serial port." msgstr "" #. Tag: para -#: boot-installer.xml:2222 +#: boot-installer.xml:2229 #, 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:2250 +#: boot-installer.xml:2257 #, no-c-format msgid "s390 Limitations" msgstr "" #. Tag: para -#: boot-installer.xml:2251 +#: boot-installer.xml:2258 #, 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:2256 +#: boot-installer.xml:2263 #, 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:2267 +#: boot-installer.xml:2274 #, no-c-format msgid "s390 Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2268 +#: boot-installer.xml:2275 #, 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:2328 +#: boot-installer.xml:2335 #, no-c-format msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP 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:2337 +#: boot-installer.xml:2344 #, 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:2346 +#: boot-installer.xml:2353 #, 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:2355 +#: boot-installer.xml:2362 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "" #. Tag: title -#: boot-installer.xml:2361 +#: boot-installer.xml:2368 #, no-c-format msgid "Booting from Hard Disk" msgstr "" #. Tag: title -#: boot-installer.xml:2382 +#: boot-installer.xml:2389 #, no-c-format msgid "Booting CHRP from OpenFirmware" msgstr "" #. Tag: emphasis -#: boot-installer.xml:2386 +#: boot-installer.xml:2393 #, no-c-format msgid "Not yet written." msgstr "" #. Tag: title -#: boot-installer.xml:2391 +#: boot-installer.xml:2398 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" #. Tag: para -#: boot-installer.xml:2392 +#: boot-installer.xml:2399 #, 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:2410 +#: boot-installer.xml:2417 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" #. Tag: para -#: boot-installer.xml:2411 +#: boot-installer.xml:2418 #, 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\"/>. Restart the computer, and immediately (during the chime) hold down the <keycap>Option</keycap>, <keycap>Command (cloverleaf/Apple)</keycap>, <keycap>o</keycap>, and <keycap>f</keycap> keys all together. After a few seconds you will be presented with the Open Firmware prompt. At the prompt, type <informalexample><screen>\n" @@ -1643,31 +1649,31 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:2446 +#: boot-installer.xml:2453 #, no-c-format msgid "Booting from USB memory stick" msgstr "" #. Tag: para -#: boot-installer.xml:2447 +#: boot-installer.xml:2454 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" #. Tag: para -#: boot-installer.xml:2453 +#: boot-installer.xml:2460 #, 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. To get to the prompt, hold down <keycombo><keycap>Command</keycap> <keycap>Option</keycap> <keycap>o</keycap> <keycap>f</keycap></keycombo> all together while booting (see <xref linkend=\"invoking-openfirmware\"/>)." msgstr "" #. Tag: para -#: boot-installer.xml:2465 +#: boot-installer.xml:2472 #, 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:2477 +#: boot-installer.xml:2484 #, no-c-format msgid "" "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n" @@ -1676,85 +1682,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2491 +#: boot-installer.xml:2498 #, 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:2497 +#: boot-installer.xml:2504 #, 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:2530 +#: boot-installer.xml:2537 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" #. Tag: para -#: boot-installer.xml:2534 +#: boot-installer.xml:2541 #, 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 <command>boot enet:0</command>. PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try <userinput>boot <replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:2549 +#: boot-installer.xml:2556 #, 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:2561 +#: boot-installer.xml:2568 #, 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:2567 +#: boot-installer.xml:2574 #, 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:2574 +#: boot-installer.xml:2581 #, 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:2585 +#: boot-installer.xml:2592 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2586 +#: boot-installer.xml:2593 #, 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:2626 +#: boot-installer.xml:2633 #, 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." msgstr "" #. Tag: para -#: boot-installer.xml:2680 +#: boot-installer.xml:2687 #, 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: para -#: boot-installer.xml:2692 +#: boot-installer.xml:2699 #, no-c-format msgid "Floppy images are currently only available for sparc32, but, for techinical reasons, not for official releases. (The reason is that they can only be built as root, which is not supported by our build daemons.) Look under <quote>daily built images</quote> on the <ulink url=\"&url-d-i;\">Debian Installer project website</ulink> for links to floppy images for sparc32." msgstr "" #. Tag: para -#: boot-installer.xml:2701 +#: boot-installer.xml:2708 #, no-c-format msgid "" "To boot from floppy on a Sparc, use <informalexample><screen>\n" @@ -1763,13 +1769,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2711 +#: boot-installer.xml:2718 #, no-c-format msgid "Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from booting (instead of not supporting booting at all). The appropriate OBP update can be downloaded as product ID 106121 from <ulink url=\"http://sunsolve.sun.com\"></ulink>." msgstr "" #. Tag: para -#: boot-installer.xml:2718 +#: boot-installer.xml:2725 #, no-c-format msgid "" "If you are booting from the floppy, and you see messages such as <informalexample><screen>\n" @@ -1779,37 +1785,37 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:2730 +#: boot-installer.xml:2737 #, no-c-format msgid "IDPROM Messages" msgstr "" #. Tag: para -#: boot-installer.xml:2731 +#: boot-installer.xml:2738 #, 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: para -#: boot-installer.xml:2750 +#: boot-installer.xml:2757 #, 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:2757 +#: boot-installer.xml:2764 #, 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:2764 +#: boot-installer.xml:2771 #, 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:2773 +#: boot-installer.xml:2780 #, no-c-format msgid "" "When the kernel boots, a message <informalexample><screen>\n" @@ -1818,427 +1824,427 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2789 +#: boot-installer.xml:2796 #, no-c-format msgid "If you are booting with a serial console, generally the kernel will autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</phrase>. 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>." msgstr "" #. Tag: para -#: boot-installer.xml:2802 +#: boot-installer.xml:2809 #, 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:2813 +#: boot-installer.xml:2820 #, no-c-format msgid "Debian Installer Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2814 +#: boot-installer.xml:2821 #, 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:2827 +#: boot-installer.xml:2834 #, 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:2839 +#: boot-installer.xml:2846 #, no-c-format msgid "debconf/priority (priority)" msgstr "" #. Tag: para -#: boot-installer.xml:2840 +#: boot-installer.xml:2847 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" #. Tag: para -#: boot-installer.xml:2844 +#: boot-installer.xml:2851 #, 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:2851 +#: boot-installer.xml:2858 #, 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:2865 +#: boot-installer.xml:2872 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para -#: boot-installer.xml:2866 +#: boot-installer.xml:2873 #, 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 which support it, the graphical installer uses the <userinput>gtk</userinput> frontend." msgstr "" #. Tag: term -#: boot-installer.xml:2895 +#: boot-installer.xml:2902 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:2896 +#: boot-installer.xml:2903 #, 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:2905 +#: boot-installer.xml:2912 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:2906 +#: boot-installer.xml:2913 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:2910 +#: boot-installer.xml:2917 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:2911 +#: boot-installer.xml:2918 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:2915 +#: boot-installer.xml:2922 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:2916 +#: boot-installer.xml:2923 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:2920 +#: boot-installer.xml:2927 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:2921 +#: boot-installer.xml:2928 #, 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:2935 +#: boot-installer.xml:2942 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:2936 +#: boot-installer.xml:2943 #, 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:2942 +#: boot-installer.xml:2949 #, 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:2952 +#: boot-installer.xml:2959 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "" #. Tag: para -#: boot-installer.xml:2953 +#: boot-installer.xml:2960 #, 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:2962 +#: boot-installer.xml:2969 #, 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:2968 +#: boot-installer.xml:2975 #, no-c-format msgid "Such problems have been reported on the Amiga 1200 and SE/30." msgstr "" #. Tag: para -#: boot-installer.xml:2972 +#: boot-installer.xml:2979 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:2976 +#: boot-installer.xml:2983 #, 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:2990 +#: boot-installer.xml:2997 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "" #. Tag: para -#: boot-installer.xml:2991 +#: boot-installer.xml:2998 #, 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:3003 +#: boot-installer.xml:3010 #, no-c-format msgid "debian-installer/probe/usb" msgstr "" #. Tag: para -#: boot-installer.xml:3004 +#: boot-installer.xml:3011 #, no-c-format msgid "Set to <userinput>false</userinput> to prevent probing for USB on boot, if that causes problems." msgstr "" #. Tag: term -#: boot-installer.xml:3013 boot-installer.xml:3179 +#: boot-installer.xml:3020 boot-installer.xml:3186 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" #. Tag: para -#: boot-installer.xml:3014 +#: boot-installer.xml:3021 #, 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:3021 +#: boot-installer.xml:3028 #, 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:3032 +#: boot-installer.xml:3039 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:3033 +#: boot-installer.xml:3040 #, 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:3043 +#: boot-installer.xml:3050 #, no-c-format msgid "preseed/url (url)" msgstr "" #. Tag: para -#: boot-installer.xml:3044 +#: boot-installer.xml:3051 #, no-c-format msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:3053 +#: boot-installer.xml:3060 #, no-c-format msgid "preseed/file (file)" msgstr "" #. Tag: para -#: boot-installer.xml:3054 +#: boot-installer.xml:3061 #, no-c-format msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:3063 +#: boot-installer.xml:3070 #, no-c-format msgid "auto-install/enabled (auto)" msgstr "" #. Tag: para -#: boot-installer.xml:3064 +#: boot-installer.xml:3071 #, 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:3075 +#: boot-installer.xml:3082 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:3076 +#: boot-installer.xml:3083 #, 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:3085 +#: boot-installer.xml:3092 #, 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:3096 +#: boot-installer.xml:3103 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:3097 +#: boot-installer.xml:3104 #, 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:3107 +#: boot-installer.xml:3114 #, no-c-format msgid "mouse/left" msgstr "" #. Tag: para -#: boot-installer.xml:3108 +#: boot-installer.xml:3115 #, 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:3117 +#: boot-installer.xml:3124 #, no-c-format msgid "directfb/hw-accel" msgstr "" #. Tag: para -#: boot-installer.xml:3118 +#: boot-installer.xml:3125 #, no-c-format msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. To enable it, set this parameter to <userinput>true</userinput> when booting the installer." msgstr "" #. Tag: term -#: boot-installer.xml:3128 +#: boot-installer.xml:3135 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:3129 +#: boot-installer.xml:3136 #, 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:3140 +#: boot-installer.xml:3147 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para -#: boot-installer.xml:3141 +#: boot-installer.xml:3148 #, 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:3153 +#: boot-installer.xml:3160 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:3154 +#: boot-installer.xml:3161 #, 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:3165 +#: boot-installer.xml:3172 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:3166 +#: boot-installer.xml:3173 #, 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) and <classname>ppp-udeb</classname> (which supports PPPoE configuration)." msgstr "" #. Tag: para -#: boot-installer.xml:3180 +#: boot-installer.xml:3187 #, 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:3189 +#: boot-installer.xml:3196 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:3190 +#: boot-installer.xml:3197 #, 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:3203 +#: boot-installer.xml:3210 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para -#: boot-installer.xml:3204 +#: boot-installer.xml:3211 #, 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:3217 +#: boot-installer.xml:3224 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:3218 +#: boot-installer.xml:3225 #, 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:3231 +#: boot-installer.xml:3238 #, 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:3238 +#: boot-installer.xml:3245 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -2247,109 +2253,109 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3248 +#: boot-installer.xml:3255 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:3260 +#: boot-installer.xml:3267 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:3265 +#: boot-installer.xml:3272 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3266 +#: boot-installer.xml:3273 #, 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:3273 +#: boot-installer.xml:3280 #, no-c-format msgid "There are a 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:3279 +#: boot-installer.xml:3286 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:3284 +#: boot-installer.xml:3291 #, 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:3290 +#: boot-installer.xml:3297 #, 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:3300 +#: boot-installer.xml:3307 #, 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:3306 +#: boot-installer.xml:3313 #, 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:3314 +#: boot-installer.xml:3321 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:3317 +#: boot-installer.xml:3324 #, 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:3323 +#: boot-installer.xml:3330 #, 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:3330 +#: boot-installer.xml:3337 #, 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:3341 +#: boot-installer.xml:3348 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:3342 +#: boot-installer.xml:3349 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:3347 +#: boot-installer.xml:3354 #, 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:3353 +#: boot-installer.xml:3360 #, 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" @@ -2359,7 +2365,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3366 +#: boot-installer.xml:3373 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -2372,19 +2378,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3371 +#: boot-installer.xml:3378 #, 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:3383 +#: boot-installer.xml:3390 #, 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:3390 +#: boot-installer.xml:3397 #, 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" @@ -2397,13 +2403,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3404 +#: boot-installer.xml:3411 #, 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/cdroms/cdrom0</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:3412 +#: boot-installer.xml:3419 #, 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" @@ -2412,7 +2418,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3422 +#: boot-installer.xml:3429 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -2425,157 +2431,157 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3437 +#: boot-installer.xml:3444 #, 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:3452 +#: boot-installer.xml:3459 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3454 +#: boot-installer.xml:3461 #, 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:3459 +#: boot-installer.xml:3466 #, 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:3468 +#: boot-installer.xml:3475 #, 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:3477 +#: boot-installer.xml:3484 #, 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:3483 +#: boot-installer.xml:3490 #, 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:3489 +#: boot-installer.xml:3496 #, 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:3498 +#: boot-installer.xml:3505 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:3500 +#: boot-installer.xml:3507 #, 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:3507 +#: boot-installer.xml:3514 #, 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:3513 +#: boot-installer.xml:3520 #, 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:3524 boot-installer.xml:3609 +#: boot-installer.xml:3531 boot-installer.xml:3616 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3525 +#: boot-installer.xml:3532 #, 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:3530 +#: boot-installer.xml:3537 #, 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:3536 +#: boot-installer.xml:3543 #, 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:3545 +#: boot-installer.xml:3552 #, 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:3552 +#: boot-installer.xml:3559 #, 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 video=vga16:off</userinput> to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" #. Tag: title -#: boot-installer.xml:3566 +#: boot-installer.xml:3573 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:3567 +#: boot-installer.xml:3574 #, 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:3577 +#: boot-installer.xml:3584 #, 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:3594 +#: boot-installer.xml:3601 #, no-c-format msgid "System Freeze while Loading USB Modules" msgstr "" #. Tag: para -#: boot-installer.xml:3595 +#: boot-installer.xml:3602 #, 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>debian-installer/probe/usb=false</userinput> parameter at the boot prompt, which will prevent the modules from being loaded." msgstr "" #. Tag: para -#: boot-installer.xml:3610 +#: boot-installer.xml:3617 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:3616 +#: boot-installer.xml:3623 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:3617 +#: boot-installer.xml:3624 #, 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" @@ -2585,85 +2591,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3631 +#: boot-installer.xml:3638 #, 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:3642 +#: boot-installer.xml:3649 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3643 +#: boot-installer.xml:3650 #, 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:3649 +#: boot-installer.xml:3656 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3658 +#: boot-installer.xml:3665 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3660 +#: boot-installer.xml:3667 #, 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:3685 +#: boot-installer.xml:3692 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3686 +#: boot-installer.xml:3693 #, 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:3697 +#: boot-installer.xml:3704 #, 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:3708 +#: boot-installer.xml:3715 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3709 +#: boot-installer.xml:3716 #, 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:3716 +#: boot-installer.xml:3723 #, 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:3722 +#: boot-installer.xml:3729 #, 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-report</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3732 +#: boot-installer.xml:3739 #, 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/preparing.pot b/po/pot/preparing.pot index 773d9be7c..ed04c3207 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: 2007-01-01 11:02+0000\n" +"POT-Creation-Date: 2007-01-03 07:31+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" @@ -149,1469 +149,1475 @@ msgstr "" #. Tag: para #: preparing.xml:141 #, no-c-format +msgid "For &arch-title; you have the option of using <phrase arch=\"x86\">a</phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version of the installation system. For more information about this graphical installer, see <xref linkend=\"graphical\"/>." +msgstr "" + +#. Tag: para +#: preparing.xml:149 +#, no-c-format msgid "If you have problems during the installation, it helps to know which packages are involved in which steps. Introducing the leading software actors in this installation drama:" msgstr "" #. Tag: para -#: preparing.xml:147 +#: preparing.xml:155 #, no-c-format msgid "The installer software, <classname>debian-installer</classname>, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses <classname>dhcp-client</classname> to set up the network connection, runs <classname>debootstrap</classname> to install the base system packages, and runs <classname>tasksel</classname> to allow you to install certain additional software. Many more actors play smaller parts in this process, but <classname>debian-installer</classname> has completed its task when you load the new system for the first time." msgstr "" #. Tag: para -#: preparing.xml:159 +#: preparing.xml:167 #, no-c-format msgid "To tune the system to your needs, <classname>tasksel</classname> allows you to choose to install various predefined bundles of software like a Web server or a Desktop environment." msgstr "" #. Tag: para -#: preparing.xml:165 +#: preparing.xml:173 #, no-c-format msgid "One important option during the installation is whether or not to install a graphical desktop environment, consisting of the X11 window system and one of the available graphical desktop environments. If you choose not to select the <quote>Desktop environment</quote> task, you will only have a relatively basic, command line driven system. Installing the Desktop environment task is optional because it requires a fairly large amount of disk space, and because many &debian; systems are servers which don't really have any need for a graphical user interface to do their job." msgstr "" #. Tag: para -#: preparing.xml:177 +#: preparing.xml:185 #, no-c-format -msgid "Just be aware that the X11 window system is completely separate from <classname>debian-installer</classname>, and in fact is much more complicated. Installation and trouble shooting of the X window installation is not within the scope of this manual." +msgid "Just be aware that the X11 window system is completely separate from <classname>debian-installer</classname>, and in fact is much more complicated. Installation and trouble shooting of the X window system is not within the scope of this manual." msgstr "" #. Tag: title -#: preparing.xml:192 +#: preparing.xml:200 #, no-c-format msgid "Back Up Your Existing Data!" msgstr "" #. Tag: para -#: preparing.xml:193 +#: preparing.xml:201 #, no-c-format msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system has been installed on your computer, it's quite likely you will need to re-partition your disk to make room for &debian;. Anytime you partition your disk, you run a risk of losing everything on the disk, no matter what program you use to do it. The programs used in installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up, be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work." msgstr "" #. Tag: para -#: preparing.xml:206 +#: preparing.xml:214 #, no-c-format msgid "If you are creating a multi-boot system, make sure that you have the distribution media of any other present operating systems on hand. Especially if you repartition your boot drive, you might find that you have to reinstall your operating system's boot loader, or in many cases the whole operating system itself and all files on the affected partitions." msgstr "" #. Tag: para -#: preparing.xml:217 +#: preparing.xml:225 #, no-c-format msgid "With the exception of the BVM and Motorola VMEbus computers, the only supported installation method for m68k systems is booting from a local disk or floppy using an AmigaOS/TOS/MacOS-based bootstrap, for these machines you will need the original operating system in order to boot Linux. In order to boot Linux on the BVM and Motorola VMEbus machines you will need the <quote>BVMBug</quote> or <quote>16xBug</quote> boot ROMs." msgstr "" #. Tag: title -#: preparing.xml:235 +#: preparing.xml:243 #, no-c-format msgid "Information You Will Need" msgstr "" #. Tag: title -#: preparing.xml:238 +#: preparing.xml:246 #, no-c-format msgid "Documentation" msgstr "" #. Tag: title -#: preparing.xml:241 +#: preparing.xml:249 #, no-c-format msgid "Installation Manual" msgstr "" #. Tag: para -#: preparing.xml:243 +#: preparing.xml:251 #, no-c-format msgid "This document you are now reading, in plain ASCII, HTML or PDF format." msgstr "" #. Tag: itemizedlist -#: preparing.xml:249 +#: preparing.xml:257 #, no-c-format msgid "&list-install-manual-files;" msgstr "" #. Tag: para -#: preparing.xml:255 +#: preparing.xml:263 #, no-c-format msgid "The document you are now reading, which is the official version of the Installation Guide for the &releasename; release of Debian; available in <ulink url=\"&url-release-area;/installmanual\">various formats and translations</ulink>." msgstr "" #. Tag: para -#: preparing.xml:264 +#: preparing.xml:272 #, no-c-format msgid "The document you are now reading, which is a development version of the Installation Guide for the next release of Debian; available in <ulink url=\"&url-d-i-alioth-manual;\">various formats and translations</ulink>." msgstr "" #. Tag: title -#: preparing.xml:276 +#: preparing.xml:284 #, no-c-format msgid "Hardware documentation" msgstr "" #. Tag: para -#: preparing.xml:277 +#: preparing.xml:285 #, no-c-format msgid "Often contains useful information on configuring or using your hardware." msgstr "" #. Tag: ulink -#: preparing.xml:288 +#: preparing.xml:296 #, no-c-format msgid "Linux Hardware Compatibility HOWTO" msgstr "" #. Tag: ulink -#: preparing.xml:294 +#: preparing.xml:302 #, no-c-format msgid "Linux/m68k FAQ" msgstr "" #. Tag: ulink -#: preparing.xml:300 +#: preparing.xml:308 #, no-c-format msgid "Linux/Alpha FAQ" msgstr "" #. Tag: ulink -#: preparing.xml:306 +#: preparing.xml:314 #, no-c-format msgid "Linux for SPARC Processors FAQ" msgstr "" #. Tag: ulink -#: preparing.xml:312 +#: preparing.xml:320 #, no-c-format msgid "Linux/Mips website" msgstr "" #. Tag: title -#: preparing.xml:321 +#: preparing.xml:329 #, no-c-format msgid "&arch-title; Hardware References" msgstr "" #. Tag: para -#: preparing.xml:322 +#: preparing.xml:330 #, 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:334 +#: preparing.xml:342 #, no-c-format msgid "Device Drivers and Installation Commands" msgstr "" #. Tag: para -#: preparing.xml:339 +#: preparing.xml:347 #, 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:349 +#: preparing.xml:357 #, no-c-format msgid "Linux for &arch-title;" msgstr "" #. Tag: para -#: preparing.xml:355 +#: preparing.xml:363 #, 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:366 +#: preparing.xml:374 #, no-c-format msgid "Linux for IBM eServer zSeries and &arch-title;: Distributions" msgstr "" #. Tag: title -#: preparing.xml:376 +#: preparing.xml:384 #, no-c-format msgid "Finding Sources of Hardware Information" msgstr "" #. Tag: para -#: preparing.xml:377 +#: preparing.xml:385 #, 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:383 +#: preparing.xml:391 #, no-c-format msgid "Hardware information can be gathered from:" msgstr "" #. Tag: para -#: preparing.xml:390 +#: preparing.xml:398 #, no-c-format msgid "The manuals that come with each piece of hardware." msgstr "" #. Tag: para -#: preparing.xml:395 +#: preparing.xml:403 #, 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:402 +#: preparing.xml:410 #, no-c-format msgid "The cases and boxes for each piece of hardware." msgstr "" #. Tag: para -#: preparing.xml:408 +#: preparing.xml:416 #, no-c-format msgid "The System window in the Windows Control Panel." msgstr "" #. Tag: para -#: preparing.xml:414 +#: preparing.xml:422 #, 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:421 +#: preparing.xml:429 #, 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:433 +#: preparing.xml:441 #, no-c-format msgid "Hardware Information Needed for an Install" msgstr "" #. Tag: entry -#: preparing.xml:437 +#: preparing.xml:445 #, no-c-format msgid "Hardware" msgstr "" #. Tag: entry -#: preparing.xml:437 +#: preparing.xml:445 #, no-c-format msgid "Information You Might Need" msgstr "" #. Tag: entry -#: preparing.xml:443 +#: preparing.xml:451 #, no-c-format msgid "Hard Drives" msgstr "" #. Tag: entry -#: preparing.xml:444 +#: preparing.xml:452 #, no-c-format msgid "How many you have." msgstr "" #. Tag: entry -#: preparing.xml:446 +#: preparing.xml:454 #, no-c-format msgid "Their order on the system." msgstr "" #. Tag: entry -#: preparing.xml:449 +#: preparing.xml:457 #, no-c-format msgid "Whether IDE or SCSI (most computers are IDE)." msgstr "" #. Tag: entry -#: preparing.xml:452 +#: preparing.xml:460 #, no-c-format msgid "Whether IDE or SCSI (most m68k computers are SCSI)." msgstr "" #. Tag: entry -#: preparing.xml:454 preparing.xml:506 +#: preparing.xml:462 preparing.xml:514 #, no-c-format msgid "Available free space." msgstr "" #. Tag: entry -#: preparing.xml:455 +#: preparing.xml:463 #, no-c-format msgid "Partitions." msgstr "" #. Tag: entry -#: preparing.xml:457 +#: preparing.xml:465 #, no-c-format msgid "Partitions where other operating systems are installed." msgstr "" #. Tag: entry -#: preparing.xml:461 +#: preparing.xml:469 #, no-c-format msgid "Monitor" msgstr "" #. Tag: entry -#: preparing.xml:462 preparing.xml:482 preparing.xml:488 preparing.xml:494 +#: preparing.xml:470 preparing.xml:490 preparing.xml:496 preparing.xml:502 #, no-c-format msgid "Model and manufacturer." msgstr "" #. Tag: entry -#: preparing.xml:464 +#: preparing.xml:472 #, no-c-format msgid "Resolutions supported." msgstr "" #. Tag: entry -#: preparing.xml:465 +#: preparing.xml:473 #, no-c-format msgid "Horizontal refresh rate." msgstr "" #. Tag: entry -#: preparing.xml:466 +#: preparing.xml:474 #, no-c-format msgid "Vertical refresh rate." msgstr "" #. Tag: entry -#: preparing.xml:468 +#: preparing.xml:476 #, no-c-format msgid "Color depth (number of colors) supported." msgstr "" #. Tag: entry -#: preparing.xml:470 +#: preparing.xml:478 #, no-c-format msgid "Screen size." msgstr "" #. Tag: entry -#: preparing.xml:473 +#: preparing.xml:481 #, no-c-format msgid "Mouse" msgstr "" #. Tag: entry -#: preparing.xml:474 +#: preparing.xml:482 #, no-c-format msgid "Type: serial, PS/2, or USB." msgstr "" #. Tag: entry -#: preparing.xml:476 +#: preparing.xml:484 #, no-c-format msgid "Port." msgstr "" #. Tag: entry -#: preparing.xml:477 +#: preparing.xml:485 #, no-c-format msgid "Manufacturer." msgstr "" #. Tag: entry -#: preparing.xml:478 +#: preparing.xml:486 #, no-c-format msgid "Number of buttons." msgstr "" #. Tag: entry -#: preparing.xml:481 preparing.xml:509 +#: preparing.xml:489 preparing.xml:517 #, no-c-format msgid "Network" msgstr "" #. Tag: entry -#: preparing.xml:484 preparing.xml:510 +#: preparing.xml:492 preparing.xml:518 #, no-c-format msgid "Type of adapter." msgstr "" #. Tag: entry -#: preparing.xml:487 +#: preparing.xml:495 #, no-c-format msgid "Printer" msgstr "" #. Tag: entry -#: preparing.xml:490 +#: preparing.xml:498 #, no-c-format msgid "Printing resolutions supported." msgstr "" #. Tag: entry -#: preparing.xml:493 +#: preparing.xml:501 #, no-c-format msgid "Video Card" msgstr "" #. Tag: entry -#: preparing.xml:496 +#: preparing.xml:504 #, no-c-format msgid "Video RAM available." msgstr "" #. Tag: entry -#: preparing.xml:498 +#: preparing.xml:506 #, no-c-format msgid "Resolutions and color depths supported (these should be checked against your monitor's capabilities)." msgstr "" #. Tag: entry -#: preparing.xml:503 +#: preparing.xml:511 #, no-c-format msgid "DASD" msgstr "" #. Tag: entry -#: preparing.xml:504 +#: preparing.xml:512 #, no-c-format msgid "Device number(s)." msgstr "" #. Tag: entry -#: preparing.xml:512 +#: preparing.xml:520 #, no-c-format msgid "Device numbers." msgstr "" #. Tag: entry -#: preparing.xml:513 +#: preparing.xml:521 #, no-c-format msgid "Relative adapter number for OSA cards." msgstr "" #. Tag: title -#: preparing.xml:521 +#: preparing.xml:529 #, no-c-format msgid "Hardware Compatibility" msgstr "" #. Tag: para -#: preparing.xml:523 +#: preparing.xml:531 #, no-c-format msgid "Many brand name products work without trouble on Linux. Moreover, hardware for 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:529 +#: preparing.xml:537 #, 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:534 +#: preparing.xml:542 #, 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:541 +#: preparing.xml:549 #, 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:546 +#: preparing.xml:554 #, no-c-format msgid "You can check hardware compatibility by:" msgstr "" #. Tag: para -#: preparing.xml:551 +#: preparing.xml:559 #, no-c-format msgid "Checking manufacturers' web sites for new drivers." msgstr "" #. Tag: para -#: preparing.xml:556 +#: preparing.xml:564 #, 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:563 +#: preparing.xml:571 #, no-c-format msgid "Checking hardware compatibility lists for Linux on web sites dedicated to your architecture." msgstr "" #. Tag: para -#: preparing.xml:569 +#: preparing.xml:577 #, no-c-format msgid "Searching the Internet for other users' experiences." msgstr "" #. Tag: title -#: preparing.xml:580 +#: preparing.xml:588 #, no-c-format msgid "Network Settings" msgstr "" #. Tag: para -#: preparing.xml:582 +#: preparing.xml:590 #, 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:589 +#: preparing.xml:597 #, no-c-format msgid "Your host name (you may be able to decide this on your own)." msgstr "" #. Tag: para -#: preparing.xml:594 +#: preparing.xml:602 #, no-c-format msgid "Your domain name." msgstr "" #. Tag: para -#: preparing.xml:599 +#: preparing.xml:607 #, no-c-format msgid "Your computer's IP address." msgstr "" #. Tag: para -#: preparing.xml:604 +#: preparing.xml:612 #, no-c-format msgid "The netmask to use with your network." msgstr "" #. Tag: para -#: preparing.xml:609 +#: preparing.xml:617 #, 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:615 +#: preparing.xml:623 #, 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:623 +#: preparing.xml:631 #, 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:630 +#: preparing.xml:638 #, no-c-format msgid "If you use a wireless network, you should also find out:" msgstr "" #. Tag: para -#: preparing.xml:635 +#: preparing.xml:643 #, no-c-format msgid "ESSID of your wireless network." msgstr "" #. Tag: para -#: preparing.xml:640 +#: preparing.xml:648 #, no-c-format msgid "WEP security key (if applicable)." msgstr "" #. Tag: title -#: preparing.xml:657 +#: preparing.xml:665 #, no-c-format msgid "Meeting Minimum Hardware Requirements" msgstr "" #. Tag: para -#: preparing.xml:658 +#: preparing.xml:666 #, 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:664 +#: preparing.xml:672 #, 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:670 +#: preparing.xml:678 #, no-c-format msgid "A Pentium 4, 1GHz system is the minimum recommended for a desktop systems." msgstr "" #. Tag: para -#: preparing.xml:675 +#: preparing.xml:683 #, no-c-format msgid "A 68030 or better processor is recommended for m68k installs. You may get by with a little less drive space than shown." msgstr "" #. Tag: para -#: preparing.xml:680 +#: preparing.xml:688 #, no-c-format msgid "Any OldWorld or NewWorld PowerPC can serve well as a desktop system." msgstr "" #. Tag: title -#: preparing.xml:687 +#: preparing.xml:695 #, no-c-format msgid "Recommended Minimum System Requirements" msgstr "" #. Tag: entry -#: preparing.xml:691 +#: preparing.xml:699 #, no-c-format msgid "Install Type" msgstr "" #. Tag: entry -#: preparing.xml:692 +#: preparing.xml:700 #, no-c-format msgid "RAM (minimal)" msgstr "" #. Tag: entry -#: preparing.xml:693 +#: preparing.xml:701 #, no-c-format msgid "RAM (recommended)" msgstr "" #. Tag: entry -#: preparing.xml:694 +#: preparing.xml:702 #, no-c-format msgid "Hard Drive" msgstr "" #. Tag: entry -#: preparing.xml:700 +#: preparing.xml:708 #, no-c-format msgid "No desktop" msgstr "" #. Tag: entry -#: preparing.xml:701 preparing.xml:706 +#: preparing.xml:709 preparing.xml:714 #, no-c-format msgid "64 megabytes" msgstr "" #. Tag: entry -#: preparing.xml:702 +#: preparing.xml:710 #, no-c-format msgid "256 megabytes" msgstr "" #. Tag: entry -#: preparing.xml:703 +#: preparing.xml:711 #, no-c-format msgid "1 gigabyte" msgstr "" #. Tag: entry -#: preparing.xml:705 +#: preparing.xml:713 #, no-c-format msgid "With Desktop" msgstr "" #. Tag: entry -#: preparing.xml:707 +#: preparing.xml:715 #, no-c-format msgid "512 megabytes" msgstr "" #. Tag: entry -#: preparing.xml:708 +#: preparing.xml:716 #, no-c-format msgid "5 gigabyte" msgstr "" #. Tag: para -#: preparing.xml:713 +#: preparing.xml:721 #, 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:723 +#: preparing.xml:731 #, 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>icewm</classname> and <classname>wmaker</classname>, but there are others to choose from." msgstr "" #. Tag: para -#: preparing.xml:732 +#: preparing.xml:740 #, 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:738 +#: preparing.xml:746 #, 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:745 +#: preparing.xml:753 #, 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:769 +#: preparing.xml:777 #, no-c-format msgid "Pre-Partitioning for Multi-Boot Systems" msgstr "" #. Tag: para -#: preparing.xml:770 +#: preparing.xml:778 #, 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:777 +#: preparing.xml:785 #, 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:783 +#: preparing.xml:791 #, 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> <phrase arch=\"m68k\"> (Amiga OS, Atari TOS, Mac OS, …) </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:810 +#: preparing.xml:818 #, 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=\"m68k\">, such as HD SC Setup, HDToolBox, or SCSITool</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:820 +#: preparing.xml:828 #, 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:830 +#: preparing.xml:838 #, no-c-format msgid "FIXME: write about HP-UX disks?" msgstr "" #. Tag: para -#: preparing.xml:832 +#: preparing.xml:840 #, 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:839 +#: preparing.xml:847 #, 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=\"partman\"/>), 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:854 +#: preparing.xml:862 #, 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:864 +#: preparing.xml:872 #, 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:870 +#: preparing.xml:878 #, no-c-format msgid "If none of the above apply, you'll need to partition your hard disk before starting the installation to create partition-able 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:882 +#: preparing.xml:890 #, 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:890 +#: preparing.xml:898 #, 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:895 +#: preparing.xml:903 #, 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:907 +#: preparing.xml:915 #, 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:914 +#: preparing.xml:922 #, no-c-format msgid "Back up everything on the computer." msgstr "" #. Tag: para -#: preparing.xml:919 +#: preparing.xml:927 #, 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:929 +#: preparing.xml:937 #, 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:936 +#: preparing.xml:944 #, no-c-format msgid "Install the native operating system on its new partition." msgstr "" #. Tag: para -#: preparing.xml:941 +#: preparing.xml:949 #, 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:947 +#: preparing.xml:955 #, no-c-format msgid "Boot the Debian installer to continue installing Debian." msgstr "" #. Tag: title -#: preparing.xml:961 +#: preparing.xml:969 #, no-c-format msgid "Partitioning in Tru64 UNIX" msgstr "" #. Tag: para -#: preparing.xml:962 +#: preparing.xml:970 #, 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:974 +#: preparing.xml:982 #, 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:987 +#: preparing.xml:995 #, 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:996 +#: preparing.xml:1004 #, 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:1005 +#: preparing.xml:1013 #, 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:1014 +#: preparing.xml:1022 #, no-c-format msgid "Partitioning in Windows NT" msgstr "" #. Tag: para -#: preparing.xml:1016 +#: preparing.xml:1024 #, 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:1029 +#: preparing.xml:1037 #, 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:1046 +#: preparing.xml:1054 #, no-c-format msgid "Partitioning From DOS or Windows" msgstr "" #. Tag: para -#: preparing.xml:1047 +#: preparing.xml:1055 #, 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:1055 +#: preparing.xml:1063 #, 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:1069 +#: preparing.xml:1077 #, no-c-format msgid "Lossless Repartitioning When Starting From DOS, Win-32 or OS/2" msgstr "" #. Tag: para -#: preparing.xml:1072 +#: preparing.xml:1080 #, 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:1084 +#: preparing.xml:1092 #, 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:1093 +#: preparing.xml:1101 #, 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:1102 +#: preparing.xml:1110 #, 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:1115 +#: preparing.xml:1123 #, 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:1125 +#: preparing.xml:1133 #, 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:1131 +#: preparing.xml:1139 #, 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:1139 +#: preparing.xml:1147 #, no-c-format msgid "Partitioning for DOS" msgstr "" #. Tag: para -#: preparing.xml:1141 +#: preparing.xml:1149 #, 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:1149 +#: preparing.xml:1157 #, 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:1156 +#: preparing.xml:1164 #, no-c-format msgid "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4" msgstr "" #. Tag: title -#: preparing.xml:1167 +#: preparing.xml:1175 #, no-c-format msgid "Partitioning in AmigaOS" msgstr "" #. Tag: para -#: preparing.xml:1168 +#: preparing.xml:1176 #, no-c-format msgid "If you are running AmigaOS, you can use the <command>HDToolBox</command> program to adjust your native partitions prior to installation." msgstr "" #. Tag: title -#: preparing.xml:1176 +#: preparing.xml:1184 #, no-c-format msgid "Partitioning in Atari TOS" msgstr "" #. Tag: para -#: preparing.xml:1177 +#: preparing.xml:1185 #, no-c-format msgid "Atari partition IDs are three ASCII characters, use <quote>LNX</quote> for data and <quote>SWP</quote> for swap partitions. If using the low memory installation method, a small Minix partition is also needed (about 2 MB), for which the partition ID is <quote>MNX</quote>. Failure to set the appropriate partition IDs not only prevents the Debian installation process from recognizing the partitions, but also results in TOS attempting to use the Linux partitions, which confuses the hard disk driver and renders the whole disk inaccessible." msgstr "" #. Tag: para -#: preparing.xml:1188 +#: preparing.xml:1196 #, no-c-format msgid "There are a multitude of third party partitioning tools available (the Atari <command>harddisk</command> utility doesn't permit changing the partition ID); this manual cannot give detailed descriptions for all of them. The following description covers <command>SCSITool</command> (from Hard+Soft GmBH)." msgstr "" #. Tag: para -#: preparing.xml:1197 +#: preparing.xml:1205 #, no-c-format msgid "Start <command>SCSITool</command> and select the disk you want to partition (<guimenu>Disk</guimenu> menu, item <guimenuitem>select</guimenuitem>)." msgstr "" #. Tag: para -#: preparing.xml:1203 +#: preparing.xml:1211 #, no-c-format msgid "From the <guimenu>Partition</guimenu> menu, select either <guimenuitem>New</guimenuitem> to add new partitions or change the existing partition sizes, or <guimenuitem>Change</guimenuitem> to change one specific partition. Unless you have already created partitions with the right sizes and only want to change the partition ID, <guimenuitem>New</guimenuitem> is probably the best choice." msgstr "" #. Tag: para -#: preparing.xml:1213 +#: preparing.xml:1221 #, no-c-format msgid "For the <guimenuitem>New</guimenuitem> choice, select <guilabel>existing</guilabel> in the dialog box prompting the initial settings. The next window shows a list of existing partitions which you can adjust using the scroll buttons, or by clicking in the bar graphs. The first column in the partition list is the partition type; just click on the text field to edit it. When you are finished changing partition settings, save the changes by leaving the window with the <guibutton>OK</guibutton> button." msgstr "" #. Tag: para -#: preparing.xml:1225 +#: preparing.xml:1233 #, no-c-format msgid "For the <guimenuitem>Change</guimenuitem> option, select the partition to change in the selection list, and select <guilabel>other systems</guilabel> in the dialog box. The next window lists detailed information about the location of this partition, and lets you change the partition ID. Save changes by leaving the window with the <guibutton>OK</guibutton> button." msgstr "" #. Tag: para -#: preparing.xml:1235 +#: preparing.xml:1243 #, no-c-format msgid "Write down the Linux names for each of the partitions you created or changed for use with Linux — see <xref linkend=\"device-names\"/>." msgstr "" #. Tag: para -#: preparing.xml:1241 +#: preparing.xml:1249 #, no-c-format msgid "Quit <command>SCSITool</command> using the <guimenuitem>Quit</guimenuitem> item from the <guimenu>File</guimenu> menu. The computer will reboot to make sure the changed partition table is used by TOS. If you changed any TOS/GEM partitions, they will be invalidated and have to be reinitialized (we told you to back up everything on the disk, didn't we?)." msgstr "" #. Tag: para -#: preparing.xml:1253 +#: preparing.xml:1261 #, no-c-format msgid "There is a partitioning tool for Linux/m68k called <command>atari-fdisk</command> in the installation system, but for now we recommend you partition your disk using a TOS partition editor or some disk tool. If your partition editor doesn't have an option to edit the partition type, you can do this crucial step at a later stage (from the booted temporary install RAMdisk). <command>SCSITool</command> is only one of the partition editors we know of which supports selection of arbitrary partition types. There may be others; select the tool that suits your needs." msgstr "" #. Tag: title -#: preparing.xml:1268 +#: preparing.xml:1276 #, no-c-format msgid "Partitioning in MacOS" msgstr "" #. Tag: para -#: preparing.xml:1269 +#: preparing.xml:1277 #, no-c-format msgid "Partitioning tools for Macintosh tested include <command>pdisk</command>, <command>HD SC Setup</command> 7.3.5 (Apple), <command>HDT</command> 1.8 (FWB), <command>SilverLining</command> (LaCie), and <command>DiskTool</command> (Tim Endres, GPL). Full versions are required for <command>HDT</command> and <command>SilverLining</command>. The Apple tool requires a patch in order to recognize third-party disks (a description on how to patch <command>HD SC Setup</command> using <command>ResEdit</command> can be found at <ulink url=\"http://www.euronet.nl/users/ernstoud/patch.html\"></ulink>)." msgstr "" #. Tag: para -#: preparing.xml:1280 +#: preparing.xml:1288 #, no-c-format msgid "For IDE based Macs, you need to use <command>Apple Drive Setup</command> to create empty space for the Linux partitions, and complete the partitioning under Linux, or use the MacOS version of pdisk available for download from <ulink url=\"http://homepage.mac.com/alk/downloads/pdisk.sit.hqx\">Alsoft</ulink>." msgstr "" #. Tag: title -#: preparing.xml:1296 +#: preparing.xml:1304 #, no-c-format msgid "Partitioning from SunOS" msgstr "" #. Tag: para -#: preparing.xml:1298 +#: preparing.xml:1306 #, 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:1310 +#: preparing.xml:1318 #, no-c-format msgid "Partitioning from Linux or another OS" msgstr "" #. Tag: para -#: preparing.xml:1312 +#: preparing.xml:1320 #, 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:1324 +#: preparing.xml:1332 #, 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:1339 +#: preparing.xml:1347 #, no-c-format msgid "MacOS/OSX Partitioning" msgstr "" #. Tag: para -#: preparing.xml:1341 +#: preparing.xml:1349 #, 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:1348 +#: preparing.xml:1356 #, 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:1354 +#: preparing.xml:1362 #, 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:1367 +#: preparing.xml:1375 #, 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:1387 +#: preparing.xml:1395 #, no-c-format msgid "Pre-Installation Hardware and Operating System Setup" msgstr "" #. Tag: para -#: preparing.xml:1388 +#: preparing.xml:1396 #, 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:1410 +#: preparing.xml:1418 #, no-c-format msgid "Invoking the BIOS Set-Up Menu" msgstr "" #. Tag: para -#: preparing.xml:1412 +#: preparing.xml:1420 #, 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 set-up menu, which is used to configure the BIOS. Before installing, you <emphasis>must</emphasis> ensure that your BIOS is setup correctly; not doing so can lead to intermittent crashes or an inability to install Debian." msgstr "" #. Tag: para -#: preparing.xml:1421 +#: preparing.xml:1429 #, 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:1435 +#: preparing.xml:1443 #, no-c-format msgid "AMI BIOS" msgstr "" #. Tag: para -#: preparing.xml:1436 +#: preparing.xml:1444 #, no-c-format msgid "<keycap>Delete</keycap> key during the POST (power on self test)" msgstr "" #. Tag: term -#: preparing.xml:1444 +#: preparing.xml:1452 #, no-c-format msgid "Award BIOS" msgstr "" #. Tag: para -#: preparing.xml:1445 +#: preparing.xml:1453 #, 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:1454 +#: preparing.xml:1462 #, no-c-format msgid "DTK BIOS" msgstr "" #. Tag: para -#: preparing.xml:1455 +#: preparing.xml:1463 #, no-c-format msgid "<keycap>Esc</keycap> key during the POST" msgstr "" #. Tag: term -#: preparing.xml:1462 +#: preparing.xml:1470 #, no-c-format msgid "IBM PS/2 BIOS" msgstr "" #. Tag: para -#: preparing.xml:1463 +#: preparing.xml:1471 #, 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:1477 +#: preparing.xml:1485 #, no-c-format msgid "Phoenix BIOS" msgstr "" #. Tag: para -#: preparing.xml:1478 +#: preparing.xml:1486 #, 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:1494 +#: preparing.xml:1502 #, 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:1499 +#: preparing.xml:1507 #, 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:1510 preparing.xml:1854 +#: preparing.xml:1518 preparing.xml:1862 #, no-c-format msgid "Boot Device Selection" msgstr "" #. Tag: para -#: preparing.xml:1512 +#: preparing.xml:1520 #, no-c-format msgid "Many BIOS set-up 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:1523 +#: preparing.xml:1531 #, 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:1530 +#: preparing.xml:1538 #, 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:1538 +#: preparing.xml:1546 #, 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:1547 +#: preparing.xml:1555 #, no-c-format msgid "Changing the Boot Order on IDE Computers" msgstr "" #. Tag: para -#: preparing.xml:1550 +#: preparing.xml:1558 #, 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:1557 +#: preparing.xml:1565 #, 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:1562 +#: preparing.xml:1570 #, no-c-format msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom." msgstr "" #. Tag: para -#: preparing.xml:1567 +#: preparing.xml:1575 #, no-c-format msgid "C is the hard drive, and A is the floppy drive." msgstr "" #. Tag: para -#: preparing.xml:1573 +#: preparing.xml:1581 #, 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:1581 +#: preparing.xml:1589 #, 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:1591 +#: preparing.xml:1599 #, no-c-format msgid "Changing the Boot Order on SCSI Computers" msgstr "" #. Tag: para -#: preparing.xml:1595 +#: preparing.xml:1603 #, no-c-format msgid "As your computer starts, press the keys to enter the SCSI setup utility." msgstr "" #. Tag: para -#: preparing.xml:1600 +#: preparing.xml:1608 #, 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:1606 +#: preparing.xml:1614 #, 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:1614 +#: preparing.xml:1622 #, no-c-format msgid "Find the utility for changing the boot order." msgstr "" #. Tag: para -#: preparing.xml:1619 +#: preparing.xml:1627 #, 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:1625 +#: preparing.xml:1633 #, 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:1639 +#: preparing.xml:1647 #, no-c-format msgid "Miscellaneous BIOS Settings" msgstr "" #. Tag: title -#: preparing.xml:1641 +#: preparing.xml:1649 #, no-c-format msgid "CD-ROM Settings" msgstr "" #. Tag: para -#: preparing.xml:1642 +#: preparing.xml:1650 #, 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:1652 +#: preparing.xml:1660 #, no-c-format msgid "Extended vs. Expanded Memory" msgstr "" #. Tag: para -#: preparing.xml:1653 +#: preparing.xml:1661 #, 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:1663 +#: preparing.xml:1671 #, no-c-format msgid "Virus Protection" msgstr "" #. Tag: para -#: preparing.xml:1664 +#: preparing.xml:1672 #, 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:1685 +#: preparing.xml:1693 #, no-c-format msgid "Shadow RAM" msgstr "" #. Tag: para -#: preparing.xml:1686 +#: preparing.xml:1694 #, 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:1703 +#: preparing.xml:1711 #, no-c-format msgid "Memory Hole" msgstr "" #. Tag: para -#: preparing.xml:1704 +#: preparing.xml:1712 #, 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:1710 +#: preparing.xml:1718 #, 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:1726 +#: preparing.xml:1734 #, no-c-format msgid "Advanced Power Management" msgstr "" #. Tag: para -#: preparing.xml:1727 +#: preparing.xml:1735 #, 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:1745 +#: preparing.xml:1753 #, no-c-format msgid "Firmware Revisions and Existing OS Setup" msgstr "" #. Tag: para -#: preparing.xml:1747 +#: preparing.xml:1755 #, no-c-format msgid "&arch-title; machines are generally self-configuring and do not require firmware configuration. However, you should make sure that you have the appropriate ROM and system patches. On the Macintosh, MacOS version >= 7.1 is recommended because version 7.0.1 contains a bug in the video drivers preventing the boot loader from deactivating the video interrupts, resulting in a boot hang. On the BVM VMEbus systems you should make sure you are using BVMBug revision G or higher boot ROMs. The BVMBug boot ROMs do not come as standard on the BVM systems but are available from BVM on request free of charge." msgstr "" #. Tag: title -#: preparing.xml:1770 +#: preparing.xml:1778 #, no-c-format msgid "Invoking OpenFirmware" msgstr "" #. Tag: para -#: preparing.xml:1771 +#: preparing.xml:1779 #, 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:1779 +#: preparing.xml:1787 #, no-c-format msgid "On &arch-title; Macintoshes, you invoke OpenFirmware with <keycombo><keycap>Command</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:1788 +#: preparing.xml:1796 #, no-c-format msgid "" "The OpenFirmware prompt looks like this: <informalexample><screen>\n" @@ -1621,43 +1627,43 @@ msgid "" msgstr "" #. Tag: para -#: preparing.xml:1801 +#: preparing.xml:1809 #, 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 button</guibutton> to have the firmware patches installed to nvram." msgstr "" #. Tag: title -#: preparing.xml:1821 +#: preparing.xml:1829 #, no-c-format msgid "Invoking OpenBoot" msgstr "" #. Tag: para -#: preparing.xml:1823 +#: preparing.xml:1831 #, 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:1831 +#: preparing.xml:1839 #, 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:1843 +#: preparing.xml:1851 #, 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:1856 +#: preparing.xml:1864 #, 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:1866 +#: preparing.xml:1874 #, 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" @@ -1668,7 +1674,7 @@ msgid "" msgstr "" #. Tag: para -#: preparing.xml:1889 +#: preparing.xml:1897 #, 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" @@ -1677,121 +1683,121 @@ msgid "" msgstr "" #. Tag: screen -#: preparing.xml:1908 +#: preparing.xml:1916 #, no-c-format msgid "eeprom boot-device=disk1:1" msgstr "" #. Tag: title -#: preparing.xml:1918 +#: preparing.xml:1926 #, no-c-format msgid "BIOS Setup" msgstr "" #. Tag: para -#: preparing.xml:1919 +#: preparing.xml:1927 #, 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:1931 +#: preparing.xml:1939 #, 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:1941 +#: preparing.xml:1949 #, 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:1958 +#: preparing.xml:1966 #, no-c-format msgid "Native and LPAR installations" msgstr "" #. Tag: para -#: preparing.xml:1959 +#: preparing.xml:1967 #, 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:1973 +#: preparing.xml:1981 #, no-c-format msgid "Installation as a VM guest" msgstr "" #. Tag: para -#: preparing.xml:1975 +#: preparing.xml:1983 #, 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:1985 +#: preparing.xml:1993 #, 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:1997 +#: preparing.xml:2005 #, no-c-format msgid "Setting up an installation server" msgstr "" #. Tag: para -#: preparing.xml:1999 +#: preparing.xml:2007 #, 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:2007 +#: preparing.xml:2015 #, 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:2016 +#: preparing.xml:2024 #, no-c-format msgid "FIXME: more information needed — from a Redbook?" msgstr "" #. Tag: title -#: preparing.xml:2023 +#: preparing.xml:2031 #, no-c-format msgid "Hardware Issues to Watch Out For" msgstr "" #. Tag: para -#: preparing.xml:2025 +#: preparing.xml:2033 #, no-c-format msgid "Atari TT RAM boards are notorious for RAM problems under Linux; if you encounter any strange problems, try running at least the kernel in ST-RAM. Amiga users may need to exclude RAM using a booter memfile. <phrase condition=\"FIXME\"><emphasis> FIXME: more description of this needed. </emphasis></phrase>" msgstr "" #. Tag: title -#: preparing.xml:2040 +#: preparing.xml:2048 #, no-c-format msgid "USB BIOS support and keyboards" msgstr "" #. Tag: para -#: preparing.xml:2041 +#: preparing.xml:2049 #, 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:2055 +#: preparing.xml:2063 #, no-c-format msgid "Display-visibility on OldWorld Powermacs" msgstr "" #. Tag: para -#: preparing.xml:2057 +#: preparing.xml:2065 #, 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/random-bits.pot b/po/pot/random-bits.pot index 41cf6a425..703ae5a1e 100644 --- a/po/pot/random-bits.pot +++ b/po/pot/random-bits.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2007-01-02 23:42+0000\n" +"POT-Creation-Date: 2007-01-03 07:31+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" @@ -1291,3 +1291,117 @@ msgstr "" msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)" msgstr "" +#. Tag: title +#: random-bits.xml:952 +#, no-c-format +msgid "Using the Graphical Installer" +msgstr "" + +#. Tag: para +#: random-bits.xml:953 +#, no-c-format +msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the regular installer as it basically uses the same programs, but with a different frontend." +msgstr "" + +#. Tag: para +#: random-bits.xml:961 +#, no-c-format +msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the regular <quote>newt</quote> frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen." +msgstr "" + +#. Tag: para +#: random-bits.xml:970 +#, no-c-format +msgid "The graphical installer is available with all CD images and with the hd-media installation method. As the graphical installer uses a separate (much larger) initrd than the regular installer, it has to be booted using <userinput>installgui</userinput> instead of <userinput>install</userinput>. Analogous, the expert and rescue modes are booted using <userinput>expertgui</userinput> and <userinput>rescuegui</userinput> respectively." +msgstr "" + +#. Tag: para +#: random-bits.xml:980 +#, no-c-format +msgid "It is also available as a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a Debian mirror as described in <xref linkend=\"downloading-files\"/>. Look for <quote>gtk-miniiso</quote>. </para> </footnote>, which is mainly useful for testing; in this case the image is booted just using <userinput>install</userinput>. There is no graphical installer image that can be netbooted." +msgstr "" + +#. Tag: para +#: random-bits.xml:994 +#, no-c-format +msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a Debian mirror as described in <xref linkend=\"downloading-files\"/>. Look for <quote>gtk-miniiso</quote>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems." +msgstr "" + +#. Tag: para +#: random-bits.xml:1007 +#, no-c-format +msgid "The graphical installer requires significantly more memory to run than the regular installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the regular <quote>newt</quote> frontend." +msgstr "" + +#. Tag: para +#: random-bits.xml:1014 +#, no-c-format +msgid "You can add boot parameters when starting the graphical installer, just as with the regular installer. One of those parameters allows you to configure the mouse for left-handed use. See <xref linkend=\"boot-parms\"/> for valid parameters." +msgstr "" + +#. Tag: title +#: random-bits.xml:1024 +#, no-c-format +msgid "Using the graphical installer" +msgstr "" + +#. Tag: para +#: random-bits.xml:1025 +#, no-c-format +msgid "As already mentioned, the graphical installer basically works the same as the regular installer and thus the rest of this manual can be used to guide you through the installation process." +msgstr "" + +#. Tag: para +#: random-bits.xml:1031 +#, no-c-format +msgid "If you prefer using the keyboard over the mouse, there are two things you need to know. To expand a collapsed list (used for example for the selection of countries within continents), you can use the <keycap>+</keycap> and <keycap>-</keycap> keys. For questions where more than one item can be selected (e.g. task selection), you first need to tab to the <guibutton>Continue</guibutton> button after making your selections; hitting enter will toggle a selection, not activate <guibutton>Continue</guibutton>." +msgstr "" + +#. Tag: para +#: random-bits.xml:1041 +#, no-c-format +msgid "To switch to another console, you will also need to use the <keycap>Ctrl</keycap> key, just as with the X Window System. For example, to switch to VT1 you would use: <keycombo> <keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F1</keycap> </keycombo>." +msgstr "" + +#. Tag: title +#: random-bits.xml:1052 +#, no-c-format +msgid "Known issues" +msgstr "" + +#. Tag: para +#: random-bits.xml:1053 +#, no-c-format +msgid "Etch is the first release that includes the graphical installer and uses some relatively new technology. There are a few known issues that you may run into during the installation. We expect to be able to fix these issues for the next release of &debian;." +msgstr "" + +#. Tag: para +#: random-bits.xml:1063 +#, no-c-format +msgid "Information on some screens is not nicely formatted into columns as it should be. The most obvious example is the first screen where you select your language. Another example is the main screen of partman." +msgstr "" + +#. Tag: para +#: random-bits.xml:1070 +#, no-c-format +msgid "Typing some characters may not work and in some cases the wrong character may be printed. For example, \"composing\" a character by typing an accent and then the letter over/under which the accent should appear does not work." +msgstr "" + +#. Tag: para +#: random-bits.xml:1077 +#, no-c-format +msgid "Support for touchpads is not yet optimal." +msgstr "" + +#. Tag: para +#: random-bits.xml:1082 +#, no-c-format +msgid "You should not switch to a different console while the installer is busy; this may cause the frontend to crash. The frontend will be restarted automatically, but this may still cause problems with the installation. Switching to another console while the installer is waiting for input should work without causing any problems." +msgstr "" + +#. Tag: para +#: random-bits.xml:1091 +#, no-c-format +msgid "Support for creating encrypted partitions is limited as it is not possible to generate a random encryption key. It is possible to set up an encrypted partition using a passphrase as encryption key." +msgstr "" + |