diff options
author | Holger Wansing <linux@wansing-online.de> | 2012-11-24 22:19:41 +0000 |
---|---|---|
committer | Holger Wansing <linux@wansing-online.de> | 2012-11-24 22:19:41 +0000 |
commit | 34135d24396541ab382b27057b20afb92afc96e1 (patch) | |
tree | c8327238a476f186fe9d40d4ffa9de418fe7d231 /po/pot | |
parent | 258fa4da6502f390ea5abcfa2e25f35fa328db10 (diff) | |
download | installation-guide-34135d24396541ab382b27057b20afb92afc96e1.zip |
Update po and pot files:
M po/tl/administrivia.po
M po/tl/install-methods.po
M po/tl/partitioning.po
M po/tl/random-bits.po
M po/tl/gpl.po
M po/tl/preparing.po
M po/tl/preseed.po
M po/tl/post-install.po
M po/tl/boot-new.po
M po/tl/using-d-i.po
M po/tl/hardware.po
M po/tl/boot-installer.po
M po/tl/installation-howto.po
M po/ro/administrivia.po
M po/ro/install-methods.po
M po/ro/partitioning.po
M po/ro/random-bits.po
M po/ro/gpl.po
M po/ro/preparing.po
M po/ro/preseed.po
M po/ro/post-install.po
M po/ro/boot-new.po
M po/ro/hardware.po
M po/ro/boot-installer.po
M po/ro/installation-howto.po
M po/pt/install-methods.po
M po/pt/hardware.po
M po/pt/boot-installer.po
M po/da/install-methods.po
M po/da/partitioning.po
M po/da/random-bits.po
M po/da/gpl.po
M po/da/preparing.po
M po/da/preseed.po
M po/da/post-install.po
M po/da/using-d-i.po
M po/da/hardware.po
M po/da/boot-installer.po
M po/da/installation-howto.po
M po/ru/install-methods.po
M po/ru/boot-installer.po
M po/sv/install-methods.po
M po/sv/boot-installer.po
M po/ja/install-methods.po
M po/ja/boot-installer.po
M po/zh_TW/install-methods.po
M po/zh_TW/preseed.po
M po/zh_TW/boot-installer.po
M po/fi/install-methods.po
M po/fi/boot-installer.po
M po/el/install-methods.po
M po/el/boot-installer.po
M po/zh_CN/install-methods.po
M po/zh_CN/boot-installer.po
M po/pot/boot-installer.pot
M po/pot/install-methods.pot
M po/es/install-methods.po
M po/es/boot-installer.po
M po/ko/install-methods.po
M po/ko/boot-installer.po
M po/nl/administrivia.po
M po/nl/install-methods.po
M po/nl/partitioning.po
M po/nl/random-bits.po
M po/nl/gpl.po
M po/nl/preparing.po
M po/nl/preseed.po
M po/nl/post-install.po
M po/nl/boot-new.po
M po/nl/welcome.po
M po/nl/using-d-i.po
M po/nl/hardware.po
M po/nl/boot-installer.po
M po/nl/installation-howto.po
M po/nn/administrivia.po
M po/nn/install-methods.po
M po/nn/partitioning.po
M po/nn/random-bits.po
M po/nn/gpl.po
M po/nn/preparing.po
M po/nn/preseed.po
M po/nn/post-install.po
M po/nn/boot-new.po
M po/nn/welcome.po
M po/nn/using-d-i.po
M po/nn/hardware.po
M po/nn/boot-installer.po
M po/nn/installation-howto.po
M po/vi/install-methods.po
M po/vi/boot-installer.po
Diffstat (limited to 'po/pot')
-rw-r--r-- | po/pot/boot-installer.pot | 650 | ||||
-rw-r--r-- | po/pot/install-methods.pot | 346 |
2 files changed, 498 insertions, 498 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index fef4c4a2d..997aa861d 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: 2012-10-24 19:53+0000\n" +"POT-Creation-Date: 2012-11-24 22:10+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -45,19 +45,19 @@ msgid "Booting from TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1125 boot-installer.xml:1626 boot-installer.xml:1735 +#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127 boot-installer.xml:1628 boot-installer.xml:1737 #, 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:48 boot-installer.xml:589 boot-installer.xml:1130 boot-installer.xml:1631 boot-installer.xml:1740 +#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132 boot-installer.xml:1633 boot-installer.xml:1742 #, 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:53 boot-installer.xml:594 boot-installer.xml:1135 boot-installer.xml:1636 boot-installer.xml:1745 +#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137 boot-installer.xml:1638 boot-installer.xml:1747 #, no-c-format msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>." msgstr "" @@ -69,25 +69,25 @@ msgid "Booting from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744 boot-installer.xml:1402 boot-installer.xml:1774 +#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746 boot-installer.xml:1404 boot-installer.xml:1776 #, 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:81 boot-installer.xml:259 boot-installer.xml:755 boot-installer.xml:1413 boot-installer.xml:1785 +#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757 boot-installer.xml:1415 boot-installer.xml:1787 #, 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:89 boot-installer.xml:267 boot-installer.xml:763 boot-installer.xml:1421 boot-installer.xml:1793 +#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765 boot-installer.xml:1423 boot-installer.xml:1795 #, 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:97 boot-installer.xml:275 boot-installer.xml:771 boot-installer.xml:1429 boot-installer.xml:1801 +#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773 boot-installer.xml:1431 boot-installer.xml:1803 #, no-c-format msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." msgstr "" @@ -216,7 +216,7 @@ msgid "The installer will now start as usual." msgstr "" #. Tag: title -#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396 boot-installer.xml:1768 +#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1398 boot-installer.xml:1770 #, no-c-format msgid "Booting from a CD-ROM" msgstr "" @@ -236,41 +236,41 @@ msgstr "" #. Tag: para #: boot-installer.xml:355 #, no-c-format -msgid "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>, or" +msgid "obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory stick</phrase> installation media as described in <xref linkend=\"official-cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-usb-files\"/></phrase> or" msgstr "" #. Tag: para -#: boot-installer.xml:361 +#: boot-installer.xml:363 #, no-c-format msgid "download a standalone Windows executable, which is available as tools/win32-loader/stable/win32-loader.exe on the &debian; mirrors," msgstr "" #. Tag: para -#: boot-installer.xml:369 +#: boot-installer.xml:371 #, no-c-format msgid "If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing <command>setup.exe</command>." msgstr "" #. Tag: para -#: boot-installer.xml:377 +#: boot-installer.xml:379 #, no-c-format msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to reboot into the &debian-gnu; installer." msgstr "" #. Tag: title -#: boot-installer.xml:387 +#: boot-installer.xml:389 #, no-c-format msgid "Booting from DOS" msgstr "" #. Tag: para -#: boot-installer.xml:388 +#: boot-installer.xml:390 #, no-c-format msgid "Boot into DOS (not Windows). To do this, you can for instance boot from a recovery or diagnostic disk." msgstr "" #. Tag: para -#: boot-installer.xml:393 +#: boot-installer.xml:395 #, no-c-format msgid "" "If you can access the installation CD, change the current drive to the CD-ROM drive, e.g. <informalexample><screen>\n" @@ -279,7 +279,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:403 +#: boot-installer.xml:405 #, no-c-format msgid "" "Enter the subdirectory for the flavor you chose, e.g., <informalexample><screen>\n" @@ -290,37 +290,37 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:421 +#: boot-installer.xml:423 #, no-c-format msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: boot-installer.xml:424 +#: boot-installer.xml:426 #, 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:429 +#: boot-installer.xml:431 #, 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:439 +#: boot-installer.xml:441 #, no-c-format msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD/DVD image, without needing the network." msgstr "" #. Tag: para -#: boot-installer.xml:448 +#: boot-installer.xml:450 #, 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:469 +#: boot-installer.xml:471 #, no-c-format msgid "" "image=/boot/newinstall/vmlinuz\n" @@ -329,19 +329,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:469 +#: boot-installer.xml:471 #, 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:478 +#: boot-installer.xml:480 #, no-c-format msgid "The procedure for <command>GRUB1</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an entry for the installer, for example (assuming <filename>/boot</filename> is on the first partition of the first disk in the system):" msgstr "" #. Tag: screen -#: boot-installer.xml:486 +#: boot-installer.xml:488 #, no-c-format msgid "" "title New Install\n" @@ -351,13 +351,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:488 +#: boot-installer.xml:490 #, no-c-format msgid "The procedure for <command>GRUB2</command> is very similar. The file is named <filename>grub.cfg</filename> instead of <filename>menu.lst</filename>. An entry for the installer would be for instance for example:" msgstr "" #. Tag: screen -#: boot-installer.xml:494 +#: boot-installer.xml:496 #, no-c-format msgid "" "menuentry 'New Install' {\n" @@ -370,133 +370,133 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:496 +#: boot-installer.xml:498 #, no-c-format msgid "From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>." msgstr "" #. Tag: title -#: boot-installer.xml:505 +#: boot-installer.xml:507 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "" #. Tag: para -#: boot-installer.xml:506 +#: boot-installer.xml:508 #, 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 unless you have used the flexible way to build the stick and not enabled it, 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:520 boot-installer.xml:1675 +#: boot-installer.xml:522 boot-installer.xml:1677 #, no-c-format msgid "Booting from Floppies" msgstr "" #. Tag: para -#: boot-installer.xml:521 boot-installer.xml:1683 +#: boot-installer.xml:523 boot-installer.xml:1685 #, 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:528 +#: boot-installer.xml:530 #, 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:534 +#: boot-installer.xml:536 #, 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:544 +#: boot-installer.xml:546 #, 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:553 +#: boot-installer.xml:555 #, 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:559 +#: boot-installer.xml:561 #, 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:568 +#: boot-installer.xml:570 #, no-c-format msgid "After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched." msgstr "" #. Tag: title -#: boot-installer.xml:578 boot-installer.xml:1107 boot-installer.xml:1248 boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729 +#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250 boot-installer.xml:1304 boot-installer.xml:1622 boot-installer.xml:1731 #, no-c-format msgid "Booting with TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:602 +#: boot-installer.xml:604 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "" #. Tag: title -#: boot-installer.xml:608 +#: boot-installer.xml:610 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "" #. Tag: para -#: boot-installer.xml:609 +#: boot-installer.xml:611 #, 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:620 +#: boot-installer.xml:622 #, no-c-format msgid "NIC with Network BootROM" msgstr "" #. Tag: para -#: boot-installer.xml:621 +#: boot-installer.xml:623 #, no-c-format msgid "It could be that your Network Interface Card provides TFTP boot functionality." msgstr "" #. Tag: para -#: boot-installer.xml:626 +#: boot-installer.xml:628 #, 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:634 +#: boot-installer.xml:636 #, no-c-format msgid "Etherboot" msgstr "" #. Tag: para -#: boot-installer.xml:635 +#: boot-installer.xml:637 #, 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:645 +#: boot-installer.xml:647 #, no-c-format msgid "The Boot Screen" msgstr "" #. Tag: para -#: boot-installer.xml:646 +#: boot-installer.xml:648 #, no-c-format msgid "" "When the installer boots, you should be presented with a friendly graphical screen showing the &debian; logo and a menu: <informalexample><screen>\n" @@ -513,25 +513,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:658 +#: boot-installer.xml:660 #, no-c-format msgid "For a normal installation, select either the <quote>Install</quote> or the <quote>Graphical install</quote> entry — using either the arrow keys on your keyboard or by typing the first (highlighted) letter, the <quote>Install</quote> entry is already selected by default — and press &enterkey; to boot the installer." msgstr "" #. Tag: para -#: boot-installer.xml:666 +#: boot-installer.xml:668 #, no-c-format msgid "The <quote>Advanced options</quote> entry gives access to a second menu that allows to boot the installer in expert mode, in rescue mode and for automated installs." msgstr "" #. Tag: para -#: boot-installer.xml:672 +#: boot-installer.xml:674 #, no-c-format msgid "If you wish or need to add any boot parameters for either the installer or the kernel, press &tabkey;. This will display the default boot command for the selected menu entry and allow to add additional options. The help screens (see below) list some common possible options. Press &enterkey; to boot the installer with your options; pressing &escapekey; will return you to the boot menu and undo any changes you made." msgstr "" #. Tag: para -#: boot-installer.xml:681 +#: boot-installer.xml:683 #, no-c-format msgid "" "Choosing the <quote>Help</quote> entry will result in the first help screen being displayed which gives an overview of all available help screens. To return to the boot menu after the help screens have been displayed, type 'menu' at the boot prompt and press &enterkey;. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>\n" @@ -540,259 +540,259 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:699 +#: boot-installer.xml:701 #, no-c-format msgid "The keyboard is assumed to have a default American English layout at this point. This means that if your keyboard has a different (language-specific) layout, the characters that appear on the screen may be different from what you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-keymap;\">schema of the US keyboard layout</ulink> which can be used as a reference to find the correct keys to use." msgstr "" #. Tag: para -#: boot-installer.xml:709 +#: boot-installer.xml:711 #, no-c-format msgid "If you are using a system that has the BIOS configured to use serial console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot menu. The same can happen if you are installing the system via a remote management device that provides a text interface to the VGA console. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)." msgstr "" #. Tag: para -#: boot-installer.xml:719 +#: boot-installer.xml:721 #, no-c-format msgid "To bypass the graphical boot screen you can either blindly press &escapekey; to get a text boot prompt, or (equally blindly) press <quote>H</quote> followed by &enterkey; to select the <quote>Help</quote> option described above. After that your keystrokes should be echoed at the prompt. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>vga=normal fb=false</userinput> to the boot prompt, as described in the help text." msgstr "" #. Tag: title -#: boot-installer.xml:779 +#: boot-installer.xml:781 #, no-c-format msgid "CD Contents" msgstr "" #. Tag: para -#: boot-installer.xml:781 +#: boot-installer.xml:783 #, 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:797 +#: boot-installer.xml:799 #, 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:813 +#: boot-installer.xml:815 #, 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:822 +#: boot-installer.xml:824 #, 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:834 +#: boot-installer.xml:836 #, 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:853 +#: boot-installer.xml:855 #, no-c-format msgid "IMPORTANT" msgstr "" #. Tag: para -#: boot-installer.xml:854 +#: boot-installer.xml:856 #, 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:866 +#: boot-installer.xml:868 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "" #. Tag: para -#: boot-installer.xml:873 +#: boot-installer.xml:875 #, 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:879 +#: boot-installer.xml:881 #, 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:885 +#: boot-installer.xml:887 #, 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:896 +#: boot-installer.xml:898 #, 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:907 +#: boot-installer.xml:909 #, 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:919 +#: boot-installer.xml:921 #, 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:929 +#: boot-installer.xml:931 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "" #. Tag: para -#: boot-installer.xml:930 +#: boot-installer.xml:932 #, 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:941 +#: boot-installer.xml:943 #, 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:947 +#: boot-installer.xml:949 #, 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:961 +#: boot-installer.xml:963 #, 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:968 +#: boot-installer.xml:970 #, 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:975 +#: boot-installer.xml:977 #, 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:982 +#: boot-installer.xml:984 #, 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:996 +#: boot-installer.xml:998 #, no-c-format msgid "Installing using a Serial Console" msgstr "" #. Tag: para -#: boot-installer.xml:998 +#: boot-installer.xml:1000 #, 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:1009 +#: boot-installer.xml:1011 #, 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:1016 +#: boot-installer.xml:1018 #, 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:1027 +#: boot-installer.xml:1029 #, 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:1036 +#: boot-installer.xml:1038 #, 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:1045 +#: boot-installer.xml:1047 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "" #. Tag: para -#: boot-installer.xml:1047 +#: boot-installer.xml:1049 #, 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:1059 +#: boot-installer.xml:1061 #, 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:1077 +#: boot-installer.xml:1079 #, 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:1082 +#: boot-installer.xml:1084 #, 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:1089 +#: boot-installer.xml:1091 #, 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:1098 boot-installer.xml:1234 +#: boot-installer.xml:1100 boot-installer.xml:1236 #, 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:1109 +#: boot-installer.xml:1111 #, no-c-format msgid "Booting an IA-64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed through the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive." msgstr "" #. Tag: para -#: boot-installer.xml:1143 +#: boot-installer.xml:1145 #, 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:1154 +#: boot-installer.xml:1156 #, no-c-format msgid "Configuring the Server" msgstr "" #. Tag: para -#: boot-installer.xml:1155 +#: boot-installer.xml:1157 #, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n" @@ -805,13 +805,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1165 +#: boot-installer.xml:1167 #, 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:1175 +#: boot-installer.xml:1177 #, no-c-format msgid "" "# cd /var/lib/tftp\n" @@ -823,37 +823,37 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1175 +#: boot-installer.xml:1177 #, 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:1192 +#: boot-installer.xml:1194 #, no-c-format msgid "Configuring the Client" msgstr "" #. Tag: para -#: boot-installer.xml:1193 +#: boot-installer.xml:1195 #, 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:1225 +#: boot-installer.xml:1227 #, 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:1251 boot-installer.xml:1275 +#: boot-installer.xml:1253 boot-installer.xml:1277 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:1252 +#: boot-installer.xml:1254 #, no-c-format msgid "" "After entering the command monitor use <informalexample><screen>\n" @@ -864,19 +864,19 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973 +#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:1975 #, no-c-format msgid "Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1276 +#: boot-installer.xml:1278 #, 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:1281 +#: boot-installer.xml:1283 #, 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" @@ -885,79 +885,79 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:1291 +#: boot-installer.xml:1293 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: title -#: boot-installer.xml:1305 boot-installer.xml:1342 +#: boot-installer.xml:1307 boot-installer.xml:1344 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:1306 +#: boot-installer.xml:1308 #, 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:1316 +#: boot-installer.xml:1318 #, 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:1325 +#: boot-installer.xml:1327 #, no-c-format msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way." msgstr "" #. Tag: para -#: boot-installer.xml:1343 +#: boot-installer.xml:1345 #, 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:1358 +#: boot-installer.xml:1360 #, no-c-format msgid "s390 Limitations" msgstr "" #. Tag: para -#: boot-installer.xml:1359 +#: boot-installer.xml:1361 #, 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:1364 +#: boot-installer.xml:1366 #, 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:1375 +#: boot-installer.xml:1377 #, no-c-format msgid "s390 Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1376 +#: boot-installer.xml:1378 #, 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:1436 +#: boot-installer.xml:1438 #, no-c-format msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP/CHRP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the factory default CD/DVD drive." msgstr "" #. Tag: para -#: boot-installer.xml:1445 +#: boot-installer.xml:1447 #, no-c-format msgid "" "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then type <informalexample><screen>\n" @@ -966,67 +966,67 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:1456 +#: boot-installer.xml:1458 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "" #. Tag: para -#: boot-installer.xml:1458 +#: boot-installer.xml:1460 #, 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:1467 +#: boot-installer.xml:1469 #, no-c-format msgid "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key immediately after pressing the power-on button, when SmartFirmware prompt appears, type" msgstr "" #. Tag: screen -#: boot-installer.xml:1473 +#: boot-installer.xml:1475 #, no-c-format msgid "boot cd install/pegasos" msgstr "" #. Tag: title -#: boot-installer.xml:1479 +#: boot-installer.xml:1481 #, no-c-format msgid "Booting from Hard Disk" msgstr "" #. Tag: para -#: boot-installer.xml:1485 +#: boot-installer.xml:1487 #, 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:1491 +#: boot-installer.xml:1493 #, no-c-format msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files as described in <xref linkend=\"boot-drive-files\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:1511 +#: boot-installer.xml:1513 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" #. Tag: para -#: boot-installer.xml:1512 +#: boot-installer.xml:1514 #, 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:1530 +#: boot-installer.xml:1532 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" #. Tag: para -#: boot-installer.xml:1531 +#: boot-installer.xml:1533 #, no-c-format msgid "" "You will have already placed the <filename>vmlinux</filename>, <filename>initrd.gz</filename>, <filename>yaboot</filename>, and <filename>yaboot.conf</filename> files at the root level of your HFS partition in <xref linkend=\"files-newworld\"/>. You will now have to boot into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the prompt, type <informalexample><screen>\n" @@ -1037,31 +1037,31 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:1563 +#: boot-installer.xml:1565 #, no-c-format msgid "Booting from USB memory stick" msgstr "" #. Tag: para -#: boot-installer.xml:1564 +#: boot-installer.xml:1566 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" #. Tag: para -#: boot-installer.xml:1570 +#: boot-installer.xml:1572 #, no-c-format msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. See <xref linkend=\"invoking-openfirmware\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:1579 +#: boot-installer.xml:1581 #, 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:1591 +#: boot-installer.xml:1593 #, no-c-format msgid "" "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n" @@ -1070,25 +1070,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1605 +#: boot-installer.xml:1607 #, 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:1611 +#: boot-installer.xml:1613 #, 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:1644 +#: boot-installer.xml:1646 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" #. Tag: para -#: boot-installer.xml:1648 +#: boot-installer.xml:1650 #, no-c-format msgid "" "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <informalexample><screen>\n" @@ -1101,703 +1101,703 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1676 +#: boot-installer.xml:1678 #, 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:1688 +#: boot-installer.xml:1690 #, 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:1694 +#: boot-installer.xml:1696 #, 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:1701 +#: boot-installer.xml:1703 #, 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:1712 +#: boot-installer.xml:1714 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1713 +#: boot-installer.xml:1715 #, 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:1753 +#: boot-installer.xml:1755 #, no-c-format msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> command." msgstr "" #. Tag: para -#: boot-installer.xml:1808 +#: boot-installer.xml:1810 #, no-c-format msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems)." msgstr "" #. Tag: title -#: boot-installer.xml:1817 +#: boot-installer.xml:1819 #, no-c-format msgid "IDPROM Messages" msgstr "" #. Tag: para -#: boot-installer.xml:1818 +#: boot-installer.xml:1820 #, no-c-format msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information." msgstr "" #. Tag: title -#: boot-installer.xml:1837 +#: boot-installer.xml:1839 #, no-c-format msgid "Accessibility" msgstr "" #. Tag: para -#: boot-installer.xml:1838 +#: boot-installer.xml:1840 #, no-c-format msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features<phrase arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard." msgstr "" #. Tag: title -#: boot-installer.xml:1858 +#: boot-installer.xml:1860 #, no-c-format msgid "USB Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:1859 +#: boot-installer.xml:1861 #, no-c-format msgid "USB braille displays should be automatically detected. A textual version of the installer will then be automatically selected, and support for the braille display will be automatically installed on the target system. You can thus just press &enterkey; at the boot menu. Once <classname>brltty</classname> is started, you can choose a braille table by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:1874 +#: boot-installer.xml:1876 #, no-c-format msgid "Serial Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:1875 +#: boot-installer.xml:1877 #, no-c-format msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the <userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> boot parameter to tell <classname>brltty</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the two-letter driver code for your terminal (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be replaced by the name of the serial port the display is connected to, <userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> can be typically used when using a serial-to-USB converter. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:1897 boot-installer.xml:2861 +#: boot-installer.xml:1899 boot-installer.xml:2863 #, no-c-format msgid "Software Speech Synthesis" msgstr "" #. Tag: para -#: boot-installer.xml:1898 +#: boot-installer.xml:1900 #, no-c-format msgid "Support for software speech synthesis can be activated by selecting it in the boot menu by typing <userinput>s</userinput> &enterkey;. The first question (language) is spoken in english, and the remainder of installation is spoken in the selected language (if available in <classname>espeak</classname>)." msgstr "" #. Tag: title -#: boot-installer.xml:1909 +#: boot-installer.xml:1911 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: boot-installer.xml:1910 +#: boot-installer.xml:1912 #, no-c-format msgid "Support for hardware speech synthesis devices is available only alongside support for graphical installer. You thus need to select a <quote>Graphical install</quote> entry in the boot menu." msgstr "" #. Tag: para -#: boot-installer.xml:1916 +#: boot-installer.xml:1918 #, no-c-format msgid "Hardware speech synthesis devices cannot be automatically detected. You thus need to append the <userinput>speakup.synth=<replaceable>driver</replaceable></userinput> boot parameter to tell <classname>speakup</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the driver code for your device (see <ulink url=\"&url-speakup-driver-codes;\">driver code list</ulink>). The textual version of the installer will then be automatically selected, and support for the speech synthesis device will be automatically installed on the target system." msgstr "" #. Tag: title -#: boot-installer.xml:1931 +#: boot-installer.xml:1933 #, no-c-format msgid "Board Devices" msgstr "" #. Tag: para -#: boot-installer.xml:1932 +#: boot-installer.xml:1934 #, no-c-format msgid "Some accessibility devices are actual boards that are plugged inside the machine and that read text directly from the video memory. To get them to work framebuffer support must be disabled by using the <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot parameter. This will however reduce the number of available languages." msgstr "" #. Tag: para -#: boot-installer.xml:1940 +#: boot-installer.xml:1942 #, no-c-format msgid "If desired a textual version of the bootloader can be activated before adding the boot parameter by typing <userinput>h</userinput> &enterkey;." msgstr "" #. Tag: title -#: boot-installer.xml:1948 +#: boot-installer.xml:1950 #, no-c-format msgid "High-Contrast Theme" msgstr "" #. Tag: para -#: boot-installer.xml:1949 +#: boot-installer.xml:1951 #, no-c-format msgid "For users with low vision, the installer can use a high-contrast theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter." msgstr "" #. Tag: title -#: boot-installer.xml:1958 +#: boot-installer.xml:1960 #, no-c-format msgid "Preseeding" msgstr "" #. Tag: para -#: boot-installer.xml:1959 +#: boot-installer.xml:1961 #, no-c-format msgid "Alternatively, &debian; can be installed completely automatically by using preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:1974 +#: boot-installer.xml:1976 #, 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:1981 +#: boot-installer.xml:1983 #, 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:1988 +#: boot-installer.xml:1990 #, 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:1999 +#: boot-installer.xml:2001 #, no-c-format msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:2011 +#: boot-installer.xml:2013 #, no-c-format msgid "In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter <userinput>TERM=<replaceable>type</replaceable></userinput> can be added. Note that the installer only supports the following terminal types: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> and <literal>dumb</literal>. The default for serial console in &d-i; is <userinput>vt102</userinput>. If you are using a virtualization tool which does not provide conversion into such terminals types itself, e.g. QEMU/KVM, you can start it inside a <command>screen</command> session. That will indeed perform translation into the <literal>screen</literal> terminal type, which is very close to <literal>vt102</literal>." msgstr "" #. Tag: para -#: boot-installer.xml:2027 +#: boot-installer.xml:2029 #, 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:2038 +#: boot-installer.xml:2040 #, no-c-format msgid "&debian; Installer Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2039 +#: boot-installer.xml:2041 #, 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:2052 +#: boot-installer.xml:2054 #, 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:2064 +#: boot-installer.xml:2066 #, no-c-format msgid "debconf/priority (priority)" msgstr "" #. Tag: para -#: boot-installer.xml:2065 +#: boot-installer.xml:2067 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" #. Tag: para -#: boot-installer.xml:2069 +#: boot-installer.xml:2071 #, 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:2076 +#: boot-installer.xml:2078 #, 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:2090 +#: boot-installer.xml:2092 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para -#: boot-installer.xml:2091 +#: boot-installer.xml:2093 #, 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. Some specialized types of install media may only offer a limited selection of frontends, but the <userinput>newt</userinput> and <userinput>text</userinput> frontends are available on most default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend." msgstr "" #. Tag: term -#: boot-installer.xml:2122 +#: boot-installer.xml:2124 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:2123 +#: boot-installer.xml:2125 #, 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:2132 +#: boot-installer.xml:2134 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:2133 +#: boot-installer.xml:2135 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:2137 +#: boot-installer.xml:2139 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:2138 +#: boot-installer.xml:2140 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:2142 +#: boot-installer.xml:2144 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:2143 +#: boot-installer.xml:2145 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:2147 +#: boot-installer.xml:2149 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:2148 +#: boot-installer.xml:2150 #, 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:2162 +#: boot-installer.xml:2164 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:2163 +#: boot-installer.xml:2165 #, 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:2169 +#: boot-installer.xml:2171 #, 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:2180 +#: boot-installer.xml:2182 #, no-c-format msgid "log_host" msgstr "" #. Tag: term -#: boot-installer.xml:2181 +#: boot-installer.xml:2183 #, no-c-format msgid "log_port" msgstr "" #. Tag: para -#: boot-installer.xml:2182 +#: boot-installer.xml:2184 #, no-c-format msgid "Causes the installer to send log messages to a remote syslog on the specified host and port as well as to a local file. If not specified, the port defaults to the standard syslog port 514." msgstr "" #. Tag: term -#: boot-installer.xml:2193 +#: boot-installer.xml:2195 #, no-c-format msgid "lowmem" msgstr "" #. Tag: para -#: boot-installer.xml:2194 +#: boot-installer.xml:2196 #, no-c-format msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:2204 +#: boot-installer.xml:2206 #, no-c-format msgid "noshell" msgstr "" #. Tag: para -#: boot-installer.xml:2205 +#: boot-installer.xml:2207 #, no-c-format msgid "Prevents the installer from offering interactive shells on tty2 and tty3. Useful for unattended installations where physical security is limited." msgstr "" #. Tag: term -#: boot-installer.xml:2214 +#: boot-installer.xml:2216 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "" #. Tag: para -#: boot-installer.xml:2215 +#: boot-installer.xml:2217 #, 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 using the parameter <userinput arch=\"x86\">vga=normal</userinput> <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:2224 +#: boot-installer.xml:2226 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:2228 +#: boot-installer.xml:2230 #, 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:2242 +#: boot-installer.xml:2244 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "" #. Tag: para -#: boot-installer.xml:2243 +#: boot-installer.xml:2245 #, 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:2255 boot-installer.xml:2488 +#: boot-installer.xml:2257 boot-installer.xml:2490 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" #. Tag: para -#: boot-installer.xml:2256 +#: boot-installer.xml:2258 #, 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:2263 +#: boot-installer.xml:2265 #, 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:2274 +#: boot-installer.xml:2276 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:2275 +#: boot-installer.xml:2277 #, 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:2285 +#: boot-installer.xml:2287 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "" #. Tag: para -#: boot-installer.xml:2286 +#: boot-installer.xml:2288 #, no-c-format msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>." msgstr "" #. Tag: term -#: boot-installer.xml:2297 +#: boot-installer.xml:2299 #, no-c-format msgid "preseed/url (url)" msgstr "" #. Tag: para -#: boot-installer.xml:2298 +#: boot-installer.xml:2300 #, no-c-format msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:2307 +#: boot-installer.xml:2309 #, no-c-format msgid "preseed/file (file)" msgstr "" #. Tag: para -#: boot-installer.xml:2308 +#: boot-installer.xml:2310 #, no-c-format msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:2317 +#: boot-installer.xml:2319 #, no-c-format msgid "preseed/interactive" msgstr "" #. Tag: para -#: boot-installer.xml:2318 +#: boot-installer.xml:2320 #, no-c-format msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details." msgstr "" #. Tag: term -#: boot-installer.xml:2330 +#: boot-installer.xml:2332 #, no-c-format msgid "auto-install/enable (auto)" msgstr "" #. Tag: para -#: boot-installer.xml:2331 +#: boot-installer.xml:2333 #, 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:2342 +#: boot-installer.xml:2344 #, no-c-format msgid "finish-install/keep-consoles" msgstr "" #. Tag: para -#: boot-installer.xml:2343 +#: boot-installer.xml:2345 #, no-c-format msgid "During installations from serial or management console, the regular virtual consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</filename>. Set to <userinput>true</userinput> to prevent this." msgstr "" #. Tag: term -#: boot-installer.xml:2354 +#: boot-installer.xml:2356 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:2355 +#: boot-installer.xml:2357 #, 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:2364 +#: boot-installer.xml:2366 #, 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:2375 +#: boot-installer.xml:2377 #, no-c-format msgid "base-installer/install-recommends (recommends)" msgstr "" #. Tag: para -#: boot-installer.xml:2376 +#: boot-installer.xml:2378 #, no-c-format msgid "By setting this option to <userinput>false</userinput>, the package management system will be configured to not automatically install <quote>Recommends</quote>, both during the installation and for the installed system. See also <xref linkend=\"di-install-base\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:2383 +#: boot-installer.xml:2385 #, no-c-format msgid "Note that this option allows to have a leaner system, but can also result in features being missing that you might normally expect to be available. You may have to manually install some of the recommended packages to obtain the full functionality you want. This option should therefore only be used by very experienced users." msgstr "" #. Tag: term -#: boot-installer.xml:2395 +#: boot-installer.xml:2397 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "" #. Tag: para -#: boot-installer.xml:2396 +#: boot-installer.xml:2398 #, no-c-format msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>" msgstr "" #. Tag: term -#: boot-installer.xml:2407 +#: boot-installer.xml:2409 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:2408 +#: boot-installer.xml:2410 #, 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:2418 +#: boot-installer.xml:2420 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:2419 +#: boot-installer.xml:2421 #, 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:2432 +#: boot-installer.xml:2434 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para -#: boot-installer.xml:2433 +#: boot-installer.xml:2435 #, 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:2445 +#: boot-installer.xml:2447 #, no-c-format msgid "debian-installer/language (language)" msgstr "" #. Tag: term -#: boot-installer.xml:2446 +#: boot-installer.xml:2448 #, no-c-format msgid "debian-installer/country (country)" msgstr "" #. Tag: term -#: boot-installer.xml:2447 +#: boot-installer.xml:2449 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:2448 +#: boot-installer.xml:2450 #, no-c-format msgid "There are two ways to specify the language, country and locale to use for the installation and the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:2453 +#: boot-installer.xml:2455 #, no-c-format msgid "The first and easiest is to pass only the parameter <literal>locale</literal>. Language and country will then be derived from its value. You can for example use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be set as default locale for the installed system). Limitation is that not all possible combinations of language, country and locale can be achieved this way." msgstr "" #. Tag: para -#: boot-installer.xml:2462 +#: boot-installer.xml:2464 #, no-c-format msgid "The second, more flexible option is to specify <literal>language</literal> and <literal>country</literal> separately. In this case <literal>locale</literal> can optionally be added to specify a specific default locale for the installed system. Example: <userinput>language=en country=DE locale=en_GB.UTF-8</userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:2474 +#: boot-installer.xml:2476 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:2475 +#: boot-installer.xml:2477 #, no-c-format msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>." msgstr "" #. Tag: para -#: boot-installer.xml:2489 +#: boot-installer.xml:2491 #, 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:2498 +#: boot-installer.xml:2500 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:2499 +#: boot-installer.xml:2501 #, 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:2512 +#: boot-installer.xml:2514 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para -#: boot-installer.xml:2513 +#: boot-installer.xml:2515 #, 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:2527 +#: boot-installer.xml:2529 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2528 +#: boot-installer.xml:2530 #, 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:2541 +#: boot-installer.xml:2543 #, 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:2548 +#: boot-installer.xml:2550 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -1806,127 +1806,127 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2558 +#: boot-installer.xml:2560 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:2564 +#: boot-installer.xml:2566 #, no-c-format msgid "Blacklisting kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2565 +#: boot-installer.xml:2567 #, no-c-format msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first." msgstr "" #. Tag: para -#: boot-installer.xml:2574 +#: boot-installer.xml:2576 #, no-c-format msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:2582 +#: boot-installer.xml:2584 #, no-c-format msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases." msgstr "" #. Tag: title -#: boot-installer.xml:2598 +#: boot-installer.xml:2600 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:2603 +#: boot-installer.xml:2605 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:2604 +#: boot-installer.xml:2606 #, 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:2611 +#: boot-installer.xml:2613 #, no-c-format msgid "There are many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you." msgstr "" #. Tag: para -#: boot-installer.xml:2617 +#: boot-installer.xml:2619 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:2622 +#: boot-installer.xml:2624 #, 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:2628 +#: boot-installer.xml:2630 #, 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 very old CD-ROM drives are known to be resolved in this way." msgstr "" #. Tag: para -#: boot-installer.xml:2638 +#: boot-installer.xml:2640 #, 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:2644 +#: boot-installer.xml:2646 #, 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:2652 +#: boot-installer.xml:2654 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:2655 +#: boot-installer.xml:2657 #, 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:2672 +#: boot-installer.xml:2674 #, no-c-format msgid "Some very old CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled for them." msgstr "" #. Tag: title -#: boot-installer.xml:2683 +#: boot-installer.xml:2685 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:2684 +#: boot-installer.xml:2686 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:2689 +#: boot-installer.xml:2691 #, no-c-format msgid "Check that your BIOS actually supports booting from CD-ROM (only an issue for very old systems) and that CD booting is enabled in the BIOS." msgstr "" #. Tag: para -#: boot-installer.xml:2696 +#: boot-installer.xml:2698 #, 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" @@ -1936,7 +1936,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2709 +#: boot-installer.xml:2711 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -1949,19 +1949,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2714 +#: boot-installer.xml:2716 #, 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 &arch-kernel; 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:2726 +#: boot-installer.xml:2728 #, 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:2733 +#: boot-installer.xml:2735 #, 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" @@ -1974,13 +1974,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2747 +#: boot-installer.xml:2749 #, no-c-format msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdrom</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:2755 +#: boot-installer.xml:2757 #, 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" @@ -1989,7 +1989,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2765 +#: boot-installer.xml:2767 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -2002,151 +2002,151 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2780 +#: boot-installer.xml:2782 #, 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:2795 +#: boot-installer.xml:2797 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:2797 +#: boot-installer.xml:2799 #, 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:2802 +#: boot-installer.xml:2804 #, 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:2811 +#: boot-installer.xml:2813 #, 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:2820 +#: boot-installer.xml:2822 #, 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:2826 +#: boot-installer.xml:2828 #, 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:2832 +#: boot-installer.xml:2834 #, 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:2841 +#: boot-installer.xml:2843 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:2843 +#: boot-installer.xml:2845 #, 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:2852 +#: boot-installer.xml:2854 #, no-c-format msgid "In some cases, malfunctions can be caused by missing device firmware (see <xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/>)." msgstr "" #. Tag: para -#: boot-installer.xml:2863 +#: boot-installer.xml:2865 #, no-c-format msgid "If software speech synthesis does not work, there is most probably an issue with your sound board, usually because either the driver for it is not included in the installer, or because it has unusual mixer level names which are set to muted by default. You should thus submit a bug report which includes the output of the following commands, run on the same machine from a Linux system which is known to have sound working (e.g., a live CD)." msgstr "" #. Tag: userinput -#: boot-installer.xml:2874 +#: boot-installer.xml:2876 #, no-c-format msgid "dmesg" msgstr "" #. Tag: userinput -#: boot-installer.xml:2876 +#: boot-installer.xml:2878 #, no-c-format msgid "lspci" msgstr "" #. Tag: userinput -#: boot-installer.xml:2878 +#: boot-installer.xml:2880 #, no-c-format msgid "lsmod" msgstr "" #. Tag: userinput -#: boot-installer.xml:2880 +#: boot-installer.xml:2882 #, no-c-format msgid "amixer" msgstr "" #. Tag: title -#: boot-installer.xml:2888 boot-installer.xml:2999 +#: boot-installer.xml:2890 boot-installer.xml:3001 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:2889 +#: boot-installer.xml:2891 #, 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:2940 +#: boot-installer.xml:2942 #, no-c-format msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" #. Tag: title -#: boot-installer.xml:2954 +#: boot-installer.xml:2956 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:2955 +#: boot-installer.xml:2957 #, no-c-format msgid "Some very old 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:2965 +#: boot-installer.xml:2967 #, 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: para -#: boot-installer.xml:3000 +#: boot-installer.xml:3002 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:3006 +#: boot-installer.xml:3008 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:3007 +#: boot-installer.xml:3009 #, 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" @@ -2156,85 +2156,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3021 +#: boot-installer.xml:3023 #, 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:3032 +#: boot-installer.xml:3034 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3033 +#: boot-installer.xml:3035 #, 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:3039 +#: boot-installer.xml:3041 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3048 +#: boot-installer.xml:3050 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3050 +#: boot-installer.xml:3052 #, 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 <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-baking\"/>)</phrase>." msgstr "" #. Tag: title -#: boot-installer.xml:3075 +#: boot-installer.xml:3077 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3076 +#: boot-installer.xml:3078 #, 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:3087 +#: boot-installer.xml:3089 #, 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:3098 +#: boot-installer.xml:3100 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3099 +#: boot-installer.xml:3101 #, 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:3106 +#: boot-installer.xml:3108 #, 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:3112 +#: boot-installer.xml:3114 #, no-c-format msgid "If you have a working &debian; system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-reports</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3122 +#: boot-installer.xml:3124 #, 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/install-methods.pot b/po/pot/install-methods.pot index 596946c2b..d98faeb1a 100644 --- a/po/pot/install-methods.pot +++ b/po/pot/install-methods.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2012-10-24 19:53+0000\n" +"POT-Creation-Date: 2012-11-24 22:10+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -35,203 +35,203 @@ msgstr "" #. Tag: para #: install-methods.xml:30 #, no-c-format -msgid "As CDs have a rather limited capacity by today's standards, not all graphical desktop environments are installable with only the first CD; only XFCE (which is the default desktop environment installed by &debian-gnu; &release;) completely fits on the first CD. For all other desktop environments a CD installation requires either network connectivity during the installation to download the remaining files or additional CDs." +msgid "As CDs have a rather limited capacity by today's standards, not all graphical desktop environments are installable with only the first CD; for some desktop environments a CD installation requires either network connectivity during the installation to download the remaining files or additional CDs." msgstr "" #. Tag: para -#: install-methods.xml:39 +#: install-methods.xml:38 #, no-c-format msgid "If your machine doesn't support CD booting<phrase arch=\"x86\"> (only relevant on very old PC systems)</phrase>, but you do have a CD set, you can use an alternative strategy such as <phrase condition=\"supports-floppy-boot\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net boot,</phrase> or manually loading the kernel from the CD to initially boot the system installer. The files you need for booting by another means are also on the CD; the &debian; network archive and CD folder organization are identical. So when archive file paths are given below for particular files you need for booting, look for those files in the same directories and subdirectories on your CD." msgstr "" #. Tag: para -#: install-methods.xml:62 +#: install-methods.xml:61 #, no-c-format msgid "Once the installer is booted, it will be able to obtain all the other files it needs from the CD." msgstr "" #. Tag: para -#: install-methods.xml:67 +#: install-methods.xml:66 #, no-c-format msgid "If you don't have a CD set, then you will need to download the installer system files and place them on the <phrase arch=\"s390\">installation tape</phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> <phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition=\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a connected computer</phrase> so they can be used to boot the installer." msgstr "" #. Tag: title -#: install-methods.xml:93 +#: install-methods.xml:92 #, no-c-format msgid "Downloading Files from &debian; Mirrors" msgstr "" #. Tag: para -#: install-methods.xml:95 +#: install-methods.xml:94 #, no-c-format msgid "To find the nearest (and thus probably the fastest) mirror, see the <ulink url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink>." msgstr "" #. Tag: para -#: install-methods.xml:100 +#: install-methods.xml:99 #, no-c-format msgid "When downloading files from a &debian; mirror using FTP, be sure to download the files in <emphasis>binary</emphasis> mode, not text or automatic mode." msgstr "" #. Tag: title -#: install-methods.xml:108 +#: install-methods.xml:107 #, no-c-format msgid "Where to Find Installation Images" msgstr "" #. Tag: para -#: install-methods.xml:110 +#: install-methods.xml:109 #, no-c-format msgid "The installation images are located on each &debian; mirror in the directory <ulink url=\"&url-debian-installer;images\">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> — the <ulink url=\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> lists each image and its purpose." msgstr "" #. Tag: title -#: install-methods.xml:123 +#: install-methods.xml:122 #, no-c-format msgid "Thecus N2100 Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:124 +#: install-methods.xml:123 #, no-c-format msgid "A firmware image is provided for the Thecus N2100 which will automatically boot <classname>debian-installer</classname>. This image can be installed using the Thecus firmware upgrade process. This firmware image can be obtained from &n2100-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:135 +#: install-methods.xml:134 #, no-c-format msgid "GLAN Tank Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:136 +#: install-methods.xml:135 #, no-c-format msgid "The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &glantank-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:146 +#: install-methods.xml:145 #, no-c-format msgid "Kurobox Pro Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:147 +#: install-methods.xml:146 #, no-c-format msgid "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &kuroboxpro-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:157 +#: install-methods.xml:156 #, no-c-format msgid "HP mv2120 Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:158 +#: install-methods.xml:157 #, no-c-format msgid "A firmware image is provided for the HP mv2120 which will automatically boot <classname>debian-installer</classname>. This image can be installed with uphpmvault on Linux and other systems and with the HP Media Vault Firmware Recovery Utility on Windows. The firmware image can be obtained from &mv2120-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:170 +#: install-methods.xml:169 #, no-c-format msgid "QNAP Turbo Station Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:171 +#: install-methods.xml:170 #, no-c-format msgid "The installation files for the QNAP Turbo Station consist of a kernel and ramdisk as well as a script to write these images to flash. You can obtain the installation files for QNAP TS-11x, TS-21x and TS-41x models from &qnap-kirkwood-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:182 +#: install-methods.xml:181 #, no-c-format msgid "Plug Computer and OpenRD Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:183 +#: install-methods.xml:182 #, no-c-format msgid "The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can obtain these files from &kirkwood-marvell-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:193 +#: install-methods.xml:192 #, no-c-format msgid "LaCie NASes Installation Files" msgstr "" #. Tag: para -#: install-methods.xml:194 +#: install-methods.xml:193 #, no-c-format msgid "The installation files for LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) consist of a kernel and initrd for U-Boot. You can obtain these files from &lacie-kirkwood-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:245 +#: install-methods.xml:244 #, no-c-format msgid "Creating an IPL tape" msgstr "" #. Tag: para -#: install-methods.xml:247 +#: install-methods.xml:246 #, no-c-format msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>." msgstr "" #. Tag: title -#: install-methods.xml:271 +#: install-methods.xml:270 #, no-c-format msgid "Creating Floppies from Disk Images" msgstr "" #. Tag: para -#: install-methods.xml:272 +#: install-methods.xml:271 #, no-c-format msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means." msgstr "" #. Tag: para -#: install-methods.xml:277 +#: install-methods.xml:276 #, no-c-format msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives." msgstr "" #. Tag: para -#: install-methods.xml:282 +#: install-methods.xml:281 #, no-c-format msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy." msgstr "" #. Tag: para -#: install-methods.xml:293 +#: install-methods.xml:292 #, no-c-format msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms." msgstr "" #. Tag: para -#: install-methods.xml:299 +#: install-methods.xml:298 #, no-c-format msgid "Before you can create the floppies, you will first need to download them from one of the &debian; mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>" msgstr "" #. Tag: para -#: install-methods.xml:307 +#: install-methods.xml:306 #, no-c-format msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally." msgstr "" #. Tag: title -#: install-methods.xml:315 +#: install-methods.xml:314 #, no-c-format msgid "Writing Disk Images From a Linux or Unix System" msgstr "" #. Tag: para -#: install-methods.xml:316 +#: install-methods.xml:315 #, no-c-format msgid "" "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n" @@ -240,187 +240,187 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:337 +#: install-methods.xml:336 #, no-c-format msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>" msgstr "" #. Tag: para -#: install-methods.xml:358 +#: install-methods.xml:357 #, no-c-format msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it." msgstr "" #. Tag: title -#: install-methods.xml:376 +#: install-methods.xml:375 #, no-c-format msgid "Writing Disk Images From DOS, Windows, or OS/2" msgstr "" #. Tag: para -#: install-methods.xml:378 +#: install-methods.xml:377 #, no-c-format msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies." msgstr "" #. Tag: para -#: install-methods.xml:383 +#: install-methods.xml:382 #, no-c-format msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work." msgstr "" #. Tag: para -#: install-methods.xml:391 +#: install-methods.xml:390 #, no-c-format msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory." msgstr "" #. Tag: para -#: install-methods.xml:397 +#: install-methods.xml:396 #, no-c-format msgid "These tools can be found on the Official &debian; CD-ROMs under the <filename>/tools</filename> directory." msgstr "" #. Tag: title -#: install-methods.xml:410 +#: install-methods.xml:409 #, no-c-format msgid "Writing Disk Images From MacOS" msgstr "" #. Tag: para -#: install-methods.xml:411 +#: install-methods.xml:410 #, no-c-format msgid "An AppleScript, <application>Make &debian; Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it." msgstr "" #. Tag: para -#: install-methods.xml:422 +#: install-methods.xml:421 #, no-c-format msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities." msgstr "" #. Tag: title -#: install-methods.xml:433 +#: install-methods.xml:432 #, no-c-format msgid "Writing Disk Images with <command>Disk Copy</command>" msgstr "" #. Tag: para -#: install-methods.xml:434 +#: install-methods.xml:433 #, no-c-format msgid "If you are creating the floppy image from files which were originally on the official &debian-gnu; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a &debian; mirror." msgstr "" #. Tag: para -#: install-methods.xml:443 +#: install-methods.xml:442 #, no-c-format msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file." msgstr "" #. Tag: para -#: install-methods.xml:450 +#: install-methods.xml:449 #, no-c-format msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields." msgstr "" #. Tag: para -#: install-methods.xml:457 +#: install-methods.xml:456 #, no-c-format msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted." msgstr "" #. Tag: para -#: install-methods.xml:466 +#: install-methods.xml:465 #, no-c-format msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>." msgstr "" #. Tag: para -#: install-methods.xml:473 +#: install-methods.xml:472 #, no-c-format msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy." msgstr "" #. Tag: title -#: install-methods.xml:488 +#: install-methods.xml:487 #, no-c-format msgid "Writing Disk Images with <command>suntar</command>" msgstr "" #. Tag: para -#: install-methods.xml:492 +#: install-methods.xml:491 #, no-c-format msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu." msgstr "" #. Tag: para -#: install-methods.xml:500 +#: install-methods.xml:499 #, no-c-format msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)." msgstr "" #. Tag: para -#: install-methods.xml:506 +#: install-methods.xml:505 #, no-c-format msgid "Select the <filename>root.bin</filename> file in the file-opening dialog." msgstr "" #. Tag: para -#: install-methods.xml:511 +#: install-methods.xml:510 #, no-c-format msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another." msgstr "" #. Tag: para -#: install-methods.xml:519 +#: install-methods.xml:518 #, no-c-format msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it." msgstr "" #. Tag: title -#: install-methods.xml:538 +#: install-methods.xml:537 #, no-c-format msgid "Preparing Files for USB Memory Stick Booting" msgstr "" #. Tag: para -#: install-methods.xml:540 +#: install-methods.xml:539 #, no-c-format msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>dmesg</command> after inserting it. To write to your stick, you may have to turn off its write protection switch." msgstr "" #. Tag: para -#: install-methods.xml:553 +#: install-methods.xml:552 #, no-c-format msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost." msgstr "" #. Tag: title -#: install-methods.xml:563 +#: install-methods.xml:562 #, no-c-format msgid "Preparing a USB stick using a hybrid CD or DVD image" msgstr "" #. Tag: para -#: install-methods.xml:564 +#: install-methods.xml:563 #, no-c-format msgid "Debian CD and DVD images can now be written directly a USB stick, which is a very easy way to make a bootable USB stick. Simply choose a CD or DVD image that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to get a CD or DVD image." msgstr "" #. Tag: para -#: install-methods.xml:571 +#: install-methods.xml:570 #, no-c-format msgid "Alternatively, for very small USB sticks, only a few megabytes in size, you can download the <filename>mini.iso</filename> image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>)." msgstr "" #. Tag: para -#: install-methods.xml:579 +#: install-methods.xml:578 #, no-c-format msgid "A special method can be used to add firmware to the <filename>mini.iso</filename>. First, write the <filename>mini.iso</filename> to the USB stick. Next obtain the necessary firmware files. See <xref linkend=\"loading-firmware\"/> for more information about firmware. Now unplug and replug the USB stick, and two partitions should now be visible on it. You should mount the second of the two partitions, and unpack the firmware onto it." msgstr "" #. Tag: screen -#: install-methods.xml:589 +#: install-methods.xml:588 #, no-c-format msgid "" "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n" @@ -431,13 +431,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:595 +#: install-methods.xml:594 #, no-c-format msgid "The CD or DVD image you choose should be written directly to the USB stick, overwriting its current contents. For example, when using an existing GNU/Linux system, the CD or DVD image file can be written to a USB stick as follows, after having made sure that the stick is unmounted:" msgstr "" #. Tag: screen -#: install-methods.xml:602 +#: install-methods.xml:601 #, no-c-format msgid "" "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/<replaceable>sdX</replaceable></userinput>\n" @@ -445,91 +445,91 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:604 +#: install-methods.xml:603 #, no-c-format msgid "Simply writing the CD or DVD image to USB like this should work fine for most users. The other options below are more complex, mainly for people with specialised needs." msgstr "" #. Tag: title -#: install-methods.xml:615 +#: install-methods.xml:614 #, no-c-format msgid "Manually copying files to the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:616 +#: install-methods.xml:615 #, no-c-format msgid "An alternative way to set up your USB stick is to manually copy the installer files, and also a CD image to it. Note that the USB stick should be at least 1 GB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)." msgstr "" #. Tag: para -#: install-methods.xml:623 +#: install-methods.xml:622 #, no-c-format msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) <phrase arch=\"x86\">as well as <classname>syslinux</classname> and its configuration file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</classname> and its configuration file</phrase>." msgstr "" #. Tag: para -#: install-methods.xml:632 +#: install-methods.xml:631 #, no-c-format msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 1 GB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose." msgstr "" #. Tag: para -#: install-methods.xml:640 +#: install-methods.xml:639 #, no-c-format msgid "To use this image simply extract it directly to your USB stick:" msgstr "" #. Tag: screen -#: install-methods.xml:644 +#: install-methods.xml:643 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sdX</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:646 +#: install-methods.xml:645 #, no-c-format msgid "Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:" msgstr "" #. Tag: screen -#: install-methods.xml:652 +#: install-methods.xml:651 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sdX2</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:654 +#: install-methods.xml:653 #, no-c-format msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done." msgstr "" #. Tag: title -#: install-methods.xml:671 +#: install-methods.xml:670 #, no-c-format msgid "Manually copying files to the USB stick — the flexible way" msgstr "" #. Tag: para -#: install-methods.xml:672 +#: install-methods.xml:671 #, no-c-format msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that — if the capacity of your USB stick is large enough — you have the option of copying a full CD ISO image to it." msgstr "" #. Tag: title -#: install-methods.xml:687 install-methods.xml:809 +#: install-methods.xml:686 install-methods.xml:808 #, no-c-format msgid "Partitioning the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:688 +#: install-methods.xml:687 #, no-c-format msgid "We will show how to set up the memory stick to use the first partition, instead of the entire device." msgstr "" #. Tag: para -#: install-methods.xml:693 +#: install-methods.xml:692 #, no-c-format msgid "" "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition<footnote> <para> Don't forget to set the <quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR using: <informalexample><screen>\n" @@ -540,13 +540,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:717 +#: install-methods.xml:716 #, no-c-format msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <classname>lilo</classname>) should work, it's convenient to use <classname>syslinux</classname>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para -#: install-methods.xml:727 +#: install-methods.xml:726 #, no-c-format msgid "" "To put <classname>syslinux</classname> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n" @@ -555,19 +555,19 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:744 install-methods.xml:856 +#: install-methods.xml:743 install-methods.xml:855 #, no-c-format msgid "Adding the installer image" msgstr "" #. Tag: para -#: install-methods.xml:745 +#: install-methods.xml:744 #, no-c-format msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) and copy the following installer image files to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> or <filename>linux</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> </itemizedlist> You can choose between either the regular version or the graphical version of the installer. The latter can be found in the <filename>gtk</filename> subdirectory. If you want to rename the files, please note that <classname>syslinux</classname> can only process DOS (8.3) file names." msgstr "" #. Tag: para -#: install-methods.xml:769 +#: install-methods.xml:768 #, no-c-format msgid "" "Next you should create a <filename>syslinux.cfg</filename> configuration file, which at a bare minimum should contain the following two lines (change the name of the kernel binary to <quote><filename>linux</filename></quote> if you used a <filename>netboot</filename> image): <informalexample><screen>\n" @@ -577,19 +577,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:781 +#: install-methods.xml:780 #, no-c-format msgid "To enable the boot prompt to permit further parameter appending, add a <userinput>prompt 1</userinput> line." msgstr "" #. Tag: para -#: install-methods.xml:786 install-methods.xml:896 +#: install-methods.xml:785 install-methods.xml:895 #, no-c-format msgid "If you used an <filename>hd-media</filename> image, you should now copy the ISO file of a &debian; ISO image<footnote> <para> You can use either a netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure to select one that fits. Note that the <quote>netboot <filename>mini.iso</filename></quote> image is not usable for this purpose. </para> </footnote> onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)." msgstr "" #. Tag: para -#: install-methods.xml:810 +#: install-methods.xml:809 #, no-c-format msgid "" "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n" @@ -598,13 +598,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:827 +#: install-methods.xml:826 #, no-c-format msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para -#: install-methods.xml:836 +#: install-methods.xml:835 #, no-c-format msgid "" "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n" @@ -617,37 +617,37 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:857 +#: install-methods.xml:856 #, no-c-format msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) and copy the following installer image files to the stick:" msgstr "" #. Tag: para -#: install-methods.xml:864 +#: install-methods.xml:863 #, no-c-format msgid "<filename>vmlinux</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:869 +#: install-methods.xml:868 #, no-c-format msgid "<filename>initrd.gz</filename> (initial ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:874 +#: install-methods.xml:873 #, no-c-format msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" msgstr "" #. Tag: para -#: install-methods.xml:879 +#: install-methods.xml:878 #, no-c-format msgid "<filename>boot.msg</filename> (optional boot message)" msgstr "" #. Tag: para -#: install-methods.xml:886 +#: install-methods.xml:885 #, no-c-format msgid "" "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n" @@ -665,259 +665,259 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:924 +#: install-methods.xml:923 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "" #. Tag: para -#: install-methods.xml:925 +#: install-methods.xml:924 #, no-c-format msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS." msgstr "" #. Tag: para -#: install-methods.xml:931 +#: install-methods.xml:930 #, no-c-format msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks." msgstr "" #. Tag: para -#: install-methods.xml:938 +#: install-methods.xml:937 #, no-c-format msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download." msgstr "" #. Tag: para -#: install-methods.xml:949 +#: install-methods.xml:948 #, no-c-format msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model." msgstr "" #. Tag: title -#: install-methods.xml:958 +#: install-methods.xml:957 #, no-c-format msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: install-methods.xml:960 +#: install-methods.xml:959 #, no-c-format msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>." msgstr "" #. Tag: para -#: install-methods.xml:966 +#: install-methods.xml:965 #, no-c-format msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel." msgstr "" #. Tag: para -#: install-methods.xml:972 +#: install-methods.xml:971 #, no-c-format msgid "Copy the following files from the &debian; archives to a convenient location on your hard drive (note that LILO can not boot from files on an NTFS file system), for instance to <filename>/boot/newinstall/</filename>." msgstr "" #. Tag: para -#: install-methods.xml:980 +#: install-methods.xml:979 #, no-c-format msgid "<filename>vmlinuz</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:985 +#: install-methods.xml:984 #, no-c-format msgid "<filename>initrd.gz</filename> (ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:992 +#: install-methods.xml:991 #, no-c-format msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1002 +#: install-methods.xml:1001 #, no-c-format msgid "Hard disk installer booting using <command>loadlin</command>" msgstr "" #. Tag: para -#: install-methods.xml:1003 +#: install-methods.xml:1002 #, no-c-format msgid "This section explains how to prepare your hard drive for booting the installer from DOS using <command>loadlin</command>." msgstr "" #. Tag: para -#: install-methods.xml:1008 +#: install-methods.xml:1007 #, no-c-format msgid "Copy the following directories from a &debian; CD image to <filename>c:\\</filename>." msgstr "" #. Tag: para -#: install-methods.xml:1013 +#: install-methods.xml:1012 #, no-c-format msgid "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:1018 +#: install-methods.xml:1017 #, no-c-format msgid "<filename>/tools</filename> (loadlin tool)" msgstr "" #. Tag: title -#: install-methods.xml:1031 +#: install-methods.xml:1030 #, no-c-format msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1032 +#: install-methods.xml:1031 #, no-c-format msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your &debian; installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model." msgstr "" #. Tag: para -#: install-methods.xml:1045 +#: install-methods.xml:1044 #, no-c-format msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on &debian; http/ftp mirrors and official &debian; CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder." msgstr "" #. Tag: title -#: install-methods.xml:1065 +#: install-methods.xml:1064 #, no-c-format msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1066 +#: install-methods.xml:1065 #, no-c-format msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs." msgstr "" #. Tag: para -#: install-methods.xml:1077 +#: install-methods.xml:1076 #, no-c-format msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the &debian; archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)." msgstr "" #. Tag: filename -#: install-methods.xml:1087 install-methods.xml:1413 +#: install-methods.xml:1086 install-methods.xml:1412 #, no-c-format msgid "vmlinux" msgstr "" #. Tag: filename -#: install-methods.xml:1092 install-methods.xml:1418 +#: install-methods.xml:1091 install-methods.xml:1417 #, no-c-format msgid "initrd.gz" msgstr "" #. Tag: filename -#: install-methods.xml:1097 install-methods.xml:1423 +#: install-methods.xml:1096 install-methods.xml:1422 #, no-c-format msgid "yaboot" msgstr "" #. Tag: filename -#: install-methods.xml:1102 install-methods.xml:1428 +#: install-methods.xml:1101 install-methods.xml:1427 #, no-c-format msgid "yaboot.conf" msgstr "" #. Tag: para -#: install-methods.xml:1107 +#: install-methods.xml:1106 #, no-c-format msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer." msgstr "" #. Tag: para -#: install-methods.xml:1115 +#: install-methods.xml:1114 #, no-c-format msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1128 +#: install-methods.xml:1127 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "" #. Tag: para -#: install-methods.xml:1129 +#: install-methods.xml:1128 #, no-c-format msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine." msgstr "" #. Tag: para -#: install-methods.xml:1137 +#: install-methods.xml:1136 #, no-c-format msgid "You need to set up a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>." msgstr "" #. Tag: para -#: install-methods.xml:1144 +#: install-methods.xml:1143 #, no-c-format msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP." msgstr "" #. Tag: para -#: install-methods.xml:1158 +#: install-methods.xml:1157 #, no-c-format msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP." msgstr "" #. Tag: para -#: install-methods.xml:1164 +#: install-methods.xml:1163 #, no-c-format msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in &debian;." msgstr "" #. Tag: para -#: install-methods.xml:1169 +#: install-methods.xml:1168 #, no-c-format msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux." msgstr "" #. Tag: para -#: install-methods.xml:1177 +#: install-methods.xml:1176 #, no-c-format msgid "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. It's written by the same author as the <classname>syslinux</classname> bootloader and is therefore least likely to cause issues. A good alternative is <classname>atftpd</classname>." msgstr "" #. Tag: title -#: install-methods.xml:1193 +#: install-methods.xml:1192 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para -#: install-methods.xml:1194 +#: install-methods.xml:1193 #, no-c-format msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>ip addr show dev eth0</userinput>." msgstr "" #. Tag: para -#: install-methods.xml:1206 +#: install-methods.xml:1205 #, no-c-format msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)." msgstr "" #. Tag: title -#: install-methods.xml:1227 +#: install-methods.xml:1226 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1228 +#: install-methods.xml:1227 #, no-c-format msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-gnu;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):" msgstr "" #. Tag: screen -#: install-methods.xml:1235 +#: install-methods.xml:1234 #, no-c-format msgid "" "option domain-name \"example.com\";\n" @@ -942,25 +942,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1237 +#: install-methods.xml:1236 #, no-c-format msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP." msgstr "" #. Tag: para -#: install-methods.xml:1247 +#: install-methods.xml:1246 #, no-c-format msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1255 +#: install-methods.xml:1254 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1256 +#: install-methods.xml:1255 #, no-c-format msgid "" "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n" @@ -995,19 +995,19 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1276 +#: install-methods.xml:1275 #, no-c-format msgid "Setting up a BOOTP server" msgstr "" #. Tag: para -#: install-methods.xml:1277 +#: install-methods.xml:1276 #, no-c-format msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian-gnu; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively." msgstr "" #. Tag: para -#: install-methods.xml:1285 +#: install-methods.xml:1284 #, no-c-format msgid "" "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run &debian;, the line in question should look like: <informalexample><screen>\n" @@ -1024,43 +1024,43 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1318 +#: install-methods.xml:1317 #, no-c-format msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcp3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1337 +#: install-methods.xml:1336 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1338 +#: install-methods.xml:1337 #, no-c-format msgid "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled." msgstr "" #. Tag: para -#: install-methods.xml:1343 +#: install-methods.xml:1342 #, no-c-format msgid "In the case of <classname>tftpd-hpa</classname> there are two ways the service can be run. It can be started on demand by the system's <classname>inetd</classname> daemon, or it can be set up to run as an independent daemon. Which of these methods is used is selected when the package is installed and can be changed by reconfiguring the package." msgstr "" #. Tag: para -#: install-methods.xml:1352 +#: install-methods.xml:1351 #, no-c-format msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian-gnu; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/srv/tftp</filename>. You may have to adjust the configuration examples in this section accordingly." msgstr "" #. Tag: para -#: install-methods.xml:1362 +#: install-methods.xml:1361 #, no-c-format msgid "All <command>in.tftpd</command> alternatives available in &debian; should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors." msgstr "" #. Tag: para -#: install-methods.xml:1370 +#: install-methods.xml:1369 #, no-c-format msgid "" "If you intend to install &debian; on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n" @@ -1071,49 +1071,49 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1392 +#: install-methods.xml:1391 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1393 +#: install-methods.xml:1392 #, no-c-format msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards." msgstr "" #. Tag: para -#: install-methods.xml:1402 +#: install-methods.xml:1401 #, no-c-format msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the <filename>netboot/</filename> directory:" msgstr "" #. Tag: filename -#: install-methods.xml:1433 +#: install-methods.xml:1432 #, no-c-format msgid "boot.msg" msgstr "" #. Tag: para -#: install-methods.xml:1438 +#: install-methods.xml:1437 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: para -#: install-methods.xml:1446 +#: install-methods.xml:1445 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: title -#: install-methods.xml:1458 +#: install-methods.xml:1457 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1459 +#: install-methods.xml:1458 #, no-c-format msgid "" "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n" @@ -1122,55 +1122,55 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1475 +#: install-methods.xml:1474 #, no-c-format msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested." msgstr "" #. Tag: para -#: install-methods.xml:1482 +#: install-methods.xml:1481 #, no-c-format msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in." msgstr "" #. Tag: title -#: install-methods.xml:1493 +#: install-methods.xml:1492 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1494 +#: install-methods.xml:1493 #, no-c-format msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>." msgstr "" #. Tag: title -#: install-methods.xml:1602 +#: install-methods.xml:1601 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1603 +#: install-methods.xml:1602 #, no-c-format msgid "For installing on multiple computers it's possible to do fully automatic installations. &debian; packages intended for this include <classname>fai-quickstart</classname> (which can use an install server) and the &debian; Installer itself. Have a look at the <ulink url=\"http://fai-project.org\">FAI home page</ulink> for detailed information." msgstr "" #. Tag: title -#: install-methods.xml:1615 +#: install-methods.xml:1614 #, no-c-format msgid "Automatic Installation Using the &debian; Installer" msgstr "" #. Tag: para -#: install-methods.xml:1616 +#: install-methods.xml:1615 #, no-c-format msgid "The &debian; Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process." msgstr "" #. Tag: para -#: install-methods.xml:1623 +#: install-methods.xml:1622 #, no-c-format msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>." msgstr "" |