diff options
| -rw-r--r-- | po/pot/bookinfo.pot | 6 | ||||
| -rw-r--r-- | po/pot/boot-installer.pot | 660 | ||||
| -rw-r--r-- | po/pot/boot-new.pot | 12 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 542 | ||||
| -rw-r--r-- | po/pot/install-methods.pot | 301 | ||||
| -rw-r--r-- | po/pot/installation-howto.pot | 8 | ||||
| -rw-r--r-- | po/pot/partitioning.pot | 14 | ||||
| -rw-r--r-- | po/pot/post-install.pot | 10 | ||||
| -rw-r--r-- | po/pot/preface.pot | 6 | ||||
| -rw-r--r-- | po/pot/preparing.pot | 62 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 356 | ||||
| -rw-r--r-- | po/pot/random-bits.pot | 199 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 20 | ||||
| -rw-r--r-- | po/pot/welcome.pot | 116 |
14 files changed, 1206 insertions, 1106 deletions
diff --git a/po/pot/bookinfo.pot b/po/pot/bookinfo.pot index 8fdc4a18b..d190b106e 100644 --- a/po/pot/bookinfo.pot +++ b/po/pot/bookinfo.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2010-07-16 00:17+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+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" @@ -17,13 +17,13 @@ msgstr "" #. Tag: title #: bookinfo.xml:5 #, no-c-format -msgid "&debian; Installation Guide" +msgid "&debian-gnu; Installation Guide" msgstr "" #. Tag: para #: bookinfo.xml:8 #, no-c-format -msgid "This document contains installation instructions for the &debian; &release; system (codename <quote>&releasename;</quote>), for the &arch-title; (<quote>&architecture;</quote>) architecture. It also contains pointers to more information and information on how to make the most of your new Debian system." +msgid "This document contains installation instructions for the &debian-gnu; &release; system (codename <quote>&releasename;</quote>), for the &arch-title; (<quote>&architecture;</quote>) architecture. It also contains pointers to more information and information on how to make the most of your new Debian system." msgstr "" #. Tag: para diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index b93ecc79f..9424d06a7 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: 2010-07-16 00:17+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+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:650 boot-installer.xml:1189 boot-installer.xml:1680 boot-installer.xml:1789 +#: boot-installer.xml:43 boot-installer.xml:653 boot-installer.xml:1192 boot-installer.xml:1683 boot-installer.xml:1792 #, 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:655 boot-installer.xml:1194 boot-installer.xml:1685 boot-installer.xml:1794 +#: boot-installer.xml:48 boot-installer.xml:658 boot-installer.xml:1197 boot-installer.xml:1688 boot-installer.xml:1797 #, 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:660 boot-installer.xml:1199 boot-installer.xml:1690 boot-installer.xml:1799 +#: boot-installer.xml:53 boot-installer.xml:663 boot-installer.xml:1202 boot-installer.xml:1693 boot-installer.xml:1802 #, 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:340 boot-installer.xml:808 boot-installer.xml:1466 boot-installer.xml:1828 +#: boot-installer.xml:70 boot-installer.xml:340 boot-installer.xml:811 boot-installer.xml:1469 boot-installer.xml:1831 #, 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:351 boot-installer.xml:819 boot-installer.xml:1477 boot-installer.xml:1839 +#: boot-installer.xml:81 boot-installer.xml:351 boot-installer.xml:822 boot-installer.xml:1480 boot-installer.xml:1842 #, 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:359 boot-installer.xml:827 boot-installer.xml:1485 boot-installer.xml:1847 +#: boot-installer.xml:89 boot-installer.xml:359 boot-installer.xml:830 boot-installer.xml:1488 boot-installer.xml:1850 #, 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:367 boot-installer.xml:835 boot-installer.xml:1493 boot-installer.xml:1855 +#: boot-installer.xml:97 boot-installer.xml:367 boot-installer.xml:838 boot-installer.xml:1496 boot-installer.xml:1858 #, no-c-format msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." msgstr "" @@ -267,7 +267,7 @@ msgid "The installer will now start as usual." msgstr "" #. Tag: title -#: boot-installer.xml:334 boot-installer.xml:802 boot-installer.xml:1460 boot-installer.xml:1822 +#: boot-installer.xml:334 boot-installer.xml:805 boot-installer.xml:1463 boot-installer.xml:1825 #, no-c-format msgid "Booting from a CD-ROM" msgstr "" @@ -293,41 +293,73 @@ msgstr "" #. Tag: para #: boot-installer.xml:456 #, no-c-format -msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to start the &debian; installer." +msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to start the &debian-gnu; installer." msgstr "" #. Tag: title -#: boot-installer.xml:496 +#: boot-installer.xml:465 #, no-c-format -msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" +msgid "Booting from DOS" +msgstr "" + +#. Tag: para +#: boot-installer.xml:466 +#, 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:471 +#, 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" + "d:\n" + "</screen></informalexample> else make sure you have first prepared your hard disk as explained in <xref linkend=\"files-loadlin\"/>, and change the current drive to it if needed." msgstr "" #. Tag: para +#: boot-installer.xml:481 +#, no-c-format +msgid "" + "Enter the subdirectory for the flavor you chose, e.g., <informalexample><screen>\n" + "cd \\&x86-install-dir;\n" + "</screen></informalexample> If you prefer using the graphical installer, enter the <filename>gtk</filename> sub-directory. <informalexample><screen>\n" + "cd gtk\n" + "</screen></informalexample> Next, execute <command>install.bat</command>. The kernel will load and launch the installer system." +msgstr "" + +#. Tag: title #: boot-installer.xml:499 #, no-c-format +msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" +msgstr "" + +#. Tag: para +#: boot-installer.xml:502 +#, 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:504 +#: boot-installer.xml:507 #, 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:514 +#: boot-installer.xml:517 #, 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:523 +#: boot-installer.xml:526 #, 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:544 +#: boot-installer.xml:547 #, no-c-format msgid "" "image=/boot/newinstall/vmlinuz\n" @@ -336,19 +368,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:544 +#: boot-installer.xml:547 #, 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:553 +#: boot-installer.xml:556 #, no-c-format msgid "The procedure for <command>GRUB</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an entry for the installer, for example (assuming <filename>/boot</filename> is on the first partition of the first disk in the system):" msgstr "" #. Tag: screen -#: boot-installer.xml:561 +#: boot-installer.xml:564 #, no-c-format msgid "" "title New Install\n" @@ -358,133 +390,133 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:563 +#: boot-installer.xml:566 #, 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:572 +#: boot-installer.xml:575 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "" #. Tag: para -#: boot-installer.xml:573 +#: boot-installer.xml:576 #, no-c-format msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;." msgstr "" #. Tag: title -#: boot-installer.xml:586 boot-installer.xml:1729 +#: boot-installer.xml:589 boot-installer.xml:1732 #, no-c-format msgid "Booting from Floppies" msgstr "" #. Tag: para -#: boot-installer.xml:587 boot-installer.xml:1737 +#: boot-installer.xml:590 boot-installer.xml:1740 #, 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:594 +#: boot-installer.xml:597 #, 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:600 +#: boot-installer.xml:603 #, 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:610 +#: boot-installer.xml:613 #, 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:619 +#: boot-installer.xml:622 #, 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:625 +#: boot-installer.xml:628 #, 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:634 +#: boot-installer.xml:637 #, 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:644 boot-installer.xml:1171 boot-installer.xml:1312 boot-installer.xml:1366 boot-installer.xml:1674 boot-installer.xml:1783 +#: boot-installer.xml:647 boot-installer.xml:1174 boot-installer.xml:1315 boot-installer.xml:1369 boot-installer.xml:1677 boot-installer.xml:1786 #, no-c-format msgid "Booting with TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:668 +#: boot-installer.xml:671 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "" #. Tag: title -#: boot-installer.xml:674 +#: boot-installer.xml:677 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "" #. Tag: para -#: boot-installer.xml:675 +#: boot-installer.xml:678 #, 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:686 +#: boot-installer.xml:689 #, no-c-format msgid "NIC with Network BootROM" msgstr "" #. Tag: para -#: boot-installer.xml:687 +#: boot-installer.xml:690 #, no-c-format msgid "It could be that your Network Interface Card provides TFTP boot functionality." msgstr "" #. Tag: para -#: boot-installer.xml:692 +#: boot-installer.xml:695 #, 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:700 +#: boot-installer.xml:703 #, no-c-format msgid "Etherboot" msgstr "" #. Tag: para -#: boot-installer.xml:701 +#: boot-installer.xml:704 #, 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:711 +#: boot-installer.xml:714 #, no-c-format msgid "The Boot Screen" msgstr "" #. Tag: para -#: boot-installer.xml:712 +#: boot-installer.xml:715 #, 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" @@ -500,25 +532,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:722 +#: boot-installer.xml:725 #, no-c-format msgid "For a normal installation, select either the <quote>Install</quote> or the <quote>Graphical install</quote> entry — using either the arrow keys on your keyboard or by typing the first (highlighted) letter — and press &enterkey; to boot the installer." msgstr "" #. Tag: para -#: boot-installer.xml:729 +#: boot-installer.xml:732 #, 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:735 +#: boot-installer.xml:738 #, 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:744 +#: boot-installer.xml:747 #, no-c-format msgid "" "Choosing the <quote>Help</quote> entry will result in the first help screen being displayed which gives an overview of all available help screens. Note that it is not possible to return to the boot menu after the help screens have been displayed. However, the F3 and F4 help screens list commands that are equivalent to the boot methods listed in the menu. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>\n" @@ -527,259 +559,259 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:763 +#: boot-installer.xml:766 #, 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:773 +#: boot-installer.xml:776 #, 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:783 +#: boot-installer.xml:786 #, 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:843 +#: boot-installer.xml:846 #, no-c-format msgid "CD Contents" msgstr "" #. Tag: para -#: boot-installer.xml:845 +#: boot-installer.xml:848 #, 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:861 +#: boot-installer.xml:864 #, 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:877 +#: boot-installer.xml:880 #, 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:886 +#: boot-installer.xml:889 #, 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:898 +#: boot-installer.xml:901 #, 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:917 +#: boot-installer.xml:920 #, no-c-format msgid "IMPORTANT" msgstr "" #. Tag: para -#: boot-installer.xml:918 +#: boot-installer.xml:921 #, 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:930 +#: boot-installer.xml:933 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "" #. Tag: para -#: boot-installer.xml:937 +#: boot-installer.xml:940 #, 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:943 +#: boot-installer.xml:946 #, 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:949 +#: boot-installer.xml:952 #, 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:960 +#: boot-installer.xml:963 #, 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:971 +#: boot-installer.xml:974 #, 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:983 +#: boot-installer.xml:986 #, 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:993 +#: boot-installer.xml:996 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "" #. Tag: para -#: boot-installer.xml:994 +#: boot-installer.xml:997 #, 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:1005 +#: boot-installer.xml:1008 #, 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:1011 +#: boot-installer.xml:1014 #, 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:1025 +#: boot-installer.xml:1028 #, 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:1032 +#: boot-installer.xml:1035 #, 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:1039 +#: boot-installer.xml:1042 #, 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:1046 +#: boot-installer.xml:1049 #, 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:1060 +#: boot-installer.xml:1063 #, no-c-format msgid "Installing using a Serial Console" msgstr "" #. Tag: para -#: boot-installer.xml:1062 +#: boot-installer.xml:1065 #, 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:1073 +#: boot-installer.xml:1076 #, 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:1080 +#: boot-installer.xml:1083 #, 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:1091 +#: boot-installer.xml:1094 #, 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:1100 +#: boot-installer.xml:1103 #, 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:1109 +#: boot-installer.xml:1112 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "" #. Tag: para -#: boot-installer.xml:1111 +#: boot-installer.xml:1114 #, 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:1123 +#: boot-installer.xml:1126 #, 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:1141 +#: boot-installer.xml:1144 #, 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:1146 +#: boot-installer.xml:1149 #, 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:1153 +#: boot-installer.xml:1156 #, 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:1162 boot-installer.xml:1298 +#: boot-installer.xml:1165 boot-installer.xml:1301 #, 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:1173 +#: boot-installer.xml:1176 #, 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:1207 +#: boot-installer.xml:1210 #, 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:1218 +#: boot-installer.xml:1221 #, no-c-format msgid "Configuring the Server" msgstr "" #. Tag: para -#: boot-installer.xml:1219 +#: boot-installer.xml:1222 #, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n" @@ -792,13 +824,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1229 +#: boot-installer.xml:1232 #, 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:1239 +#: boot-installer.xml:1242 #, no-c-format msgid "" "# cd /var/lib/tftp\n" @@ -810,37 +842,37 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1239 +#: boot-installer.xml:1242 #, 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:1256 +#: boot-installer.xml:1259 #, no-c-format msgid "Configuring the Client" msgstr "" #. Tag: para -#: boot-installer.xml:1257 +#: boot-installer.xml:1260 #, 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:1289 +#: boot-installer.xml:1292 #, 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:1315 boot-installer.xml:1339 +#: boot-installer.xml:1318 boot-installer.xml:1342 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:1316 +#: boot-installer.xml:1319 #, no-c-format msgid "" "After entering the command monitor use <informalexample><screen>\n" @@ -851,19 +883,19 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:1336 boot-installer.xml:1403 boot-installer.xml:2004 +#: boot-installer.xml:1339 boot-installer.xml:1406 boot-installer.xml:2007 #, no-c-format msgid "Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1340 +#: boot-installer.xml:1343 #, 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:1345 +#: boot-installer.xml:1348 #, 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" @@ -872,133 +904,133 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:1355 +#: boot-installer.xml:1358 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: title -#: boot-installer.xml:1369 boot-installer.xml:1406 +#: boot-installer.xml:1372 boot-installer.xml:1409 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:1370 +#: boot-installer.xml:1373 #, 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:1380 +#: boot-installer.xml:1383 #, 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:1389 +#: boot-installer.xml:1392 #, 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:1407 +#: boot-installer.xml:1410 #, 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:1422 +#: boot-installer.xml:1425 #, no-c-format msgid "s390 Limitations" msgstr "" #. Tag: para -#: boot-installer.xml:1423 +#: boot-installer.xml:1426 #, 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:1428 +#: boot-installer.xml:1431 #, 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:1439 +#: boot-installer.xml:1442 #, no-c-format msgid "s390 Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1440 +#: boot-installer.xml:1443 #, 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:1500 +#: boot-installer.xml:1503 #, no-c-format msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the CD-ROM." msgstr "" #. Tag: para -#: boot-installer.xml:1509 +#: boot-installer.xml:1512 #, 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:1518 +#: boot-installer.xml:1521 #, no-c-format msgid "If your system doesn't boot directly from CD-ROM, you can still use the CD-ROM to install the system. On NewWorlds, you can also use an OpenFirmware command to boot from the CD-ROM manually. Follow the instructions in <xref linkend=\"boot-newworld\"/> for booting from the hard disk, except use the path to <command>yaboot</command> on the CD at the OF prompt, such as" msgstr "" #. Tag: screen -#: boot-installer.xml:1527 +#: boot-installer.xml:1530 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "" #. Tag: title -#: boot-installer.xml:1533 +#: boot-installer.xml:1536 #, no-c-format msgid "Booting from Hard Disk" msgstr "" #. Tag: para -#: boot-installer.xml:1539 +#: boot-installer.xml:1542 #, 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:1545 +#: boot-installer.xml:1548 #, 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:1565 +#: boot-installer.xml:1568 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" #. Tag: para -#: boot-installer.xml:1566 +#: boot-installer.xml:1569 #, 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:1584 +#: boot-installer.xml:1587 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" #. Tag: para -#: boot-installer.xml:1585 +#: boot-installer.xml:1588 #, 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" @@ -1009,31 +1041,31 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:1617 +#: boot-installer.xml:1620 #, no-c-format msgid "Booting from USB memory stick" msgstr "" #. Tag: para -#: boot-installer.xml:1618 +#: boot-installer.xml:1621 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" #. Tag: para -#: boot-installer.xml:1624 +#: boot-installer.xml:1627 #, 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:1633 +#: boot-installer.xml:1636 #, 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:1645 +#: boot-installer.xml:1648 #, no-c-format msgid "" "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n" @@ -1042,25 +1074,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1659 +#: boot-installer.xml:1662 #, 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:1665 +#: boot-installer.xml:1668 #, 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:1698 +#: boot-installer.xml:1701 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" #. Tag: para -#: boot-installer.xml:1702 +#: boot-installer.xml:1705 #, 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" @@ -1073,169 +1105,169 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1730 +#: boot-installer.xml:1733 #, 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:1742 +#: boot-installer.xml:1745 #, 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:1748 +#: boot-installer.xml:1751 #, 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:1755 +#: boot-installer.xml:1758 #, 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:1766 +#: boot-installer.xml:1769 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1767 +#: boot-installer.xml:1770 #, 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:1807 +#: boot-installer.xml:1810 #, 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:1862 +#: boot-installer.xml:1865 #, 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:1871 +#: boot-installer.xml:1874 #, no-c-format msgid "IDPROM Messages" msgstr "" #. Tag: para -#: boot-installer.xml:1872 +#: boot-installer.xml:1875 #, 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:1891 +#: boot-installer.xml:1894 #, no-c-format msgid "Accessibility" msgstr "" #. Tag: para -#: boot-installer.xml:1892 +#: boot-installer.xml:1895 #, 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, 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:1911 +#: boot-installer.xml:1914 #, no-c-format msgid "USB Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:1912 +#: boot-installer.xml:1915 #, 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:1927 +#: boot-installer.xml:1930 #, no-c-format msgid "Serial Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:1928 +#: boot-installer.xml:1931 #, no-c-format msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the <userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> boot parameter to tell <classname>brltty</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the two-letter driver code for your terminal (see the <ulink url=\"&url-brltty-driver-codes;\">driver code list</ulink>). <replaceable>port</replaceable> should be replaced by the name of the serial port the display is connected to, <userinput>ttyS0</userinput> is the default. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-table-codes;\">table code list</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:1950 +#: boot-installer.xml:1953 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: boot-installer.xml:1951 +#: boot-installer.xml:1954 #, no-c-format msgid "Support for hardware speech synthesis devices is available only alongside support for graphical installer. You thus need to select the <quote>Graphical install</quote> entry in the boot menu." msgstr "" #. Tag: para -#: boot-installer.xml:1957 +#: boot-installer.xml:1960 #, 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:1972 +#: boot-installer.xml:1975 #, no-c-format msgid "Board Devices" msgstr "" #. Tag: para -#: boot-installer.xml:1973 +#: boot-installer.xml:1976 #, 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:1981 +#: boot-installer.xml:1984 #, 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:1989 +#: boot-installer.xml:1992 #, no-c-format msgid "High-Contrast Theme" msgstr "" #. Tag: para -#: boot-installer.xml:1990 +#: boot-installer.xml:1993 #, no-c-format msgid "For users with low vision, the installer can use a high-contrast theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter." msgstr "" #. Tag: para -#: boot-installer.xml:2005 +#: boot-installer.xml:2008 #, 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:2012 +#: boot-installer.xml:2015 #, 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:2019 +#: boot-installer.xml:2022 #, 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:2028 +#: boot-installer.xml:2031 #, no-c-format msgid "" "When the kernel boots, a message <informalexample><screen>\n" @@ -1244,493 +1276,493 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2044 +#: boot-installer.xml:2047 #, no-c-format msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename><footnote> <para> In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter <userinput>TERM=<replaceable>type</replaceable></userinput> can be added. Note that the installer only supports the following terminal types: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> and <literal>dumb</literal>. The default for serial console in &d-i; is <userinput>vt102</userinput>. </para> </footnote>." msgstr "" #. Tag: para -#: boot-installer.xml:2068 +#: boot-installer.xml:2071 #, 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:2079 +#: boot-installer.xml:2082 #, no-c-format msgid "Debian Installer Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2080 +#: boot-installer.xml:2083 #, 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:2093 +#: boot-installer.xml:2096 #, 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:2105 +#: boot-installer.xml:2108 #, no-c-format msgid "debconf/priority (priority)" msgstr "" #. Tag: para -#: boot-installer.xml:2106 +#: boot-installer.xml:2109 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" #. Tag: para -#: boot-installer.xml:2110 +#: boot-installer.xml:2113 #, 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:2117 +#: boot-installer.xml:2120 #, 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:2131 +#: boot-installer.xml:2134 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para -#: boot-installer.xml:2132 +#: boot-installer.xml:2135 #, no-c-format msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally, only the <userinput>newt</userinput> frontend is available on default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend." msgstr "" #. Tag: term -#: boot-installer.xml:2161 +#: boot-installer.xml:2164 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:2162 +#: boot-installer.xml:2165 #, 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:2171 +#: boot-installer.xml:2174 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:2172 +#: boot-installer.xml:2175 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:2176 +#: boot-installer.xml:2179 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:2177 +#: boot-installer.xml:2180 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:2181 +#: boot-installer.xml:2184 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:2182 +#: boot-installer.xml:2185 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:2186 +#: boot-installer.xml:2189 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:2187 +#: boot-installer.xml:2190 #, 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:2201 +#: boot-installer.xml:2204 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:2202 +#: boot-installer.xml:2205 #, 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:2208 +#: boot-installer.xml:2211 #, 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:2218 +#: boot-installer.xml:2221 #, no-c-format msgid "lowmem" msgstr "" #. Tag: para -#: boot-installer.xml:2219 +#: boot-installer.xml:2222 #, 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:2229 +#: boot-installer.xml:2232 #, no-c-format msgid "noshell" msgstr "" #. Tag: para -#: boot-installer.xml:2230 +#: boot-installer.xml:2233 #, 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:2239 +#: boot-installer.xml:2242 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "" #. Tag: para -#: boot-installer.xml:2240 +#: boot-installer.xml:2243 #, 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:2249 +#: boot-installer.xml:2252 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:2253 +#: boot-installer.xml:2256 #, 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:2267 +#: boot-installer.xml:2270 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "" #. Tag: para -#: boot-installer.xml:2268 +#: boot-installer.xml:2271 #, 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:2280 boot-installer.xml:2511 +#: boot-installer.xml:2283 boot-installer.xml:2514 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" #. Tag: para -#: boot-installer.xml:2281 +#: boot-installer.xml:2284 #, 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:2288 +#: boot-installer.xml:2291 #, 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:2299 +#: boot-installer.xml:2302 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:2300 +#: boot-installer.xml:2303 #, 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:2310 +#: boot-installer.xml:2313 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "" #. Tag: para -#: boot-installer.xml:2311 +#: boot-installer.xml:2314 #, 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:2322 +#: boot-installer.xml:2325 #, no-c-format msgid "preseed/url (url)" msgstr "" #. Tag: para -#: boot-installer.xml:2323 +#: boot-installer.xml:2326 #, 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:2332 +#: boot-installer.xml:2335 #, no-c-format msgid "preseed/file (file)" msgstr "" #. Tag: para -#: boot-installer.xml:2333 +#: boot-installer.xml:2336 #, 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:2342 +#: boot-installer.xml:2345 #, no-c-format msgid "preseed/interactive" msgstr "" #. Tag: para -#: boot-installer.xml:2343 +#: boot-installer.xml:2346 #, 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:2355 +#: boot-installer.xml:2358 #, no-c-format msgid "auto-install/enable (auto)" msgstr "" #. Tag: para -#: boot-installer.xml:2356 +#: boot-installer.xml:2359 #, 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:2367 +#: boot-installer.xml:2370 #, no-c-format msgid "finish-install/keep-consoles" msgstr "" #. Tag: para -#: boot-installer.xml:2368 +#: boot-installer.xml:2371 #, 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:2379 +#: boot-installer.xml:2382 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:2380 +#: boot-installer.xml:2383 #, 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:2389 +#: boot-installer.xml:2392 #, 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:2400 +#: boot-installer.xml:2403 #, no-c-format msgid "base-installer/install-recommends (recommends)" msgstr "" #. Tag: para -#: boot-installer.xml:2401 +#: boot-installer.xml:2404 #, 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:2408 +#: boot-installer.xml:2411 #, 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:2420 +#: boot-installer.xml:2423 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "" #. Tag: para -#: boot-installer.xml:2421 +#: boot-installer.xml:2424 #, 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:2432 +#: boot-installer.xml:2435 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:2433 +#: boot-installer.xml:2436 #, 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:2443 +#: boot-installer.xml:2446 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:2444 +#: boot-installer.xml:2447 #, 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:2455 +#: boot-installer.xml:2458 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para -#: boot-installer.xml:2456 +#: boot-installer.xml:2459 #, 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:2468 +#: boot-installer.xml:2471 #, no-c-format msgid "debian-installer/language (language)" msgstr "" #. Tag: term -#: boot-installer.xml:2469 +#: boot-installer.xml:2472 #, no-c-format msgid "debian-installer/country (country)" msgstr "" #. Tag: term -#: boot-installer.xml:2470 +#: boot-installer.xml:2473 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:2471 +#: boot-installer.xml:2474 #, 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:2476 +#: boot-installer.xml:2479 #, 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:2485 +#: boot-installer.xml:2488 #, 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:2497 +#: boot-installer.xml:2500 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:2498 +#: boot-installer.xml:2501 #, 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:2512 +#: boot-installer.xml:2515 #, 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:2521 +#: boot-installer.xml:2524 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:2522 +#: boot-installer.xml:2525 #, 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:2535 +#: boot-installer.xml:2538 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para -#: boot-installer.xml:2536 +#: boot-installer.xml:2539 #, 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:2550 +#: boot-installer.xml:2553 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2551 +#: boot-installer.xml:2554 #, 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:2564 +#: boot-installer.xml:2567 #, 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:2571 +#: boot-installer.xml:2574 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -1739,133 +1771,133 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2581 +#: boot-installer.xml:2584 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:2587 +#: boot-installer.xml:2590 #, no-c-format msgid "Blacklisting kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2588 +#: boot-installer.xml:2591 #, 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:2597 +#: boot-installer.xml:2600 #, 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:2605 +#: boot-installer.xml:2608 #, 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:2622 +#: boot-installer.xml:2625 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:2627 +#: boot-installer.xml:2630 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:2628 +#: boot-installer.xml:2631 #, 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:2635 +#: boot-installer.xml:2638 #, 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:2641 +#: boot-installer.xml:2644 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:2646 +#: boot-installer.xml:2649 #, 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:2652 +#: boot-installer.xml:2655 #, no-c-format msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with older CD-ROM drives are known to be resolved in this way." msgstr "" #. Tag: para -#: boot-installer.xml:2662 +#: boot-installer.xml:2665 #, 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:2668 +#: boot-installer.xml:2671 #, 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:2676 +#: boot-installer.xml:2679 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:2679 +#: boot-installer.xml:2682 #, 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:2685 +#: boot-installer.xml:2688 #, no-c-format -msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)." +msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that &arch-kernel; also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)." msgstr "" #. Tag: para -#: boot-installer.xml:2692 +#: boot-installer.xml:2695 #, no-c-format msgid "Some older CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled." msgstr "" #. Tag: title -#: boot-installer.xml:2703 +#: boot-installer.xml:2706 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:2704 +#: boot-installer.xml:2707 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:2709 +#: boot-installer.xml:2712 #, no-c-format msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using." msgstr "" #. Tag: para -#: boot-installer.xml:2715 +#: boot-installer.xml:2718 #, 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" @@ -1875,7 +1907,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2728 +#: boot-installer.xml:2731 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -1888,19 +1920,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2733 +#: boot-installer.xml:2736 #, no-c-format -msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there." +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:2745 +#: boot-installer.xml:2748 #, 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:2752 +#: boot-installer.xml:2755 #, 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" @@ -1913,13 +1945,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2766 +#: boot-installer.xml:2769 #, 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:2774 +#: boot-installer.xml:2777 #, 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" @@ -1928,7 +1960,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2784 +#: boot-installer.xml:2787 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -1941,163 +1973,163 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2799 +#: boot-installer.xml:2802 #, 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:2814 +#: boot-installer.xml:2817 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:2816 +#: boot-installer.xml:2819 #, 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:2821 +#: boot-installer.xml:2824 #, 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:2830 +#: boot-installer.xml:2833 #, 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:2839 +#: boot-installer.xml:2842 #, 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:2845 +#: boot-installer.xml:2848 #, 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:2851 +#: boot-installer.xml:2854 #, 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:2860 +#: boot-installer.xml:2863 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:2862 +#: boot-installer.xml:2865 #, 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:2869 +#: boot-installer.xml:2872 #, no-c-format -msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" +msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"any-x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" msgstr "" #. Tag: para -#: boot-installer.xml:2875 +#: boot-installer.xml:2878 #, no-c-format msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>." msgstr "" #. Tag: title -#: boot-installer.xml:2886 boot-installer.xml:2988 +#: boot-installer.xml:2889 boot-installer.xml:2991 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:2887 +#: boot-installer.xml:2890 #, 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:2892 +#: boot-installer.xml:2895 #, no-c-format msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:2898 +#: boot-installer.xml:2901 #, no-c-format msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:2907 +#: boot-installer.xml:2910 #, no-c-format msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test." msgstr "" #. Tag: para -#: boot-installer.xml:2914 +#: boot-installer.xml:2917 #, no-c-format msgid "Some systems (especially laptops) that have a native resolution that is not a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank display after the installer has been booted. In that case adding the boot parameter <userinput>vga=788</userinput><footnote> <para> The parameter <userinput>vga=788</userinput> will activate the VESA framebuffer with a resolution of 800x600. This will probably work, but may not be the optimal resolution for your system. A list of supported resolutions can be obtained by using <userinput>vga=ask</userinput>, but you should be aware that list may not be complete. </para> </footnote> may help. If that does not work, try adding the boot parameter <userinput>fb=false</userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:2932 +#: boot-installer.xml:2935 #, 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:2946 +#: boot-installer.xml:2949 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:2947 +#: boot-installer.xml:2950 #, no-c-format msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems." msgstr "" #. Tag: para -#: boot-installer.xml:2957 +#: boot-installer.xml:2960 #, no-c-format msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer." msgstr "" #. Tag: title -#: boot-installer.xml:2974 +#: boot-installer.xml:2977 #, no-c-format msgid "System Freeze while Loading USB Modules" msgstr "" #. Tag: para -#: boot-installer.xml:2975 +#: boot-installer.xml:2978 #, no-c-format msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>nousb</userinput> parameter at the boot prompt." msgstr "" #. Tag: para -#: boot-installer.xml:2989 +#: boot-installer.xml:2992 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:2995 +#: boot-installer.xml:2998 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:2996 +#: boot-installer.xml:2999 #, 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" @@ -2107,85 +2139,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3010 +#: boot-installer.xml:3013 #, 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:3021 +#: boot-installer.xml:3024 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3022 +#: boot-installer.xml:3025 #, 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:3028 +#: boot-installer.xml:3031 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3037 +#: boot-installer.xml:3040 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3039 +#: boot-installer.xml:3042 #, no-c-format -msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." +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:3064 +#: boot-installer.xml:3067 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3065 +#: boot-installer.xml:3068 #, 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:3076 +#: boot-installer.xml:3079 #, 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:3087 +#: boot-installer.xml:3090 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3088 +#: boot-installer.xml:3091 #, 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:3095 +#: boot-installer.xml:3098 #, 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:3101 +#: boot-installer.xml:3104 #, 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:3111 +#: boot-installer.xml:3114 #, 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/boot-new.pot b/po/pot/boot-new.pot index 119440c60..b29673b18 100644 --- a/po/pot/boot-new.pot +++ b/po/pot/boot-new.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2009-11-02 22:05+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+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,7 +35,7 @@ msgstr "" #. Tag: para #: boot-new.xml:13 #, no-c-format -msgid "If you did a default installation, the first thing you should see when you boot the system is the menu of the <classname>grub</classname> or possibly the <classname>lilo</classname> bootloader. The first choices in the menu will be for your new Debian system. If you had any other operating systems on your computer (like Windows) that were detected by the installation system, those will be listed lower down in the menu." +msgid "If you did a default installation, the first thing you should see when you boot the system is the menu of the <classname>grub</classname><phrase arch=\"x86\"> or possibly the <classname>lilo</classname> bootloader</phrase>. The first choices in the menu will be for your new Debian system. If you had any other operating systems on your computer (like Windows) that were detected by the installation system, those will be listed lower down in the menu." msgstr "" #. Tag: para @@ -47,7 +47,7 @@ msgstr "" #. Tag: para #: boot-new.xml:32 #, no-c-format -msgid "If you are new to Debian and Linux, you may need some help from more experienced users. <phrase arch=\"x86\">For direct on-line help you can try the IRC channels #debian or #debian-boot on the OFTC network. Alternatively you can contact the <ulink url=\"&url-list-subscribe;\">debian-user mailing list</ulink>.</phrase> <phrase arch=\"not-x86\">For less common architectures like &arch-title;, your best option is to ask on the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink>.</phrase> You can also file an installation report as described in <xref linkend=\"submit-bug\"/>. Please make sure that you describe your problem clearly and include any messages that are displayed and may help others to diagnose the issue." +msgid "If you are new to Debian and &arch-kernel;, you may need some help from more experienced users. <phrase arch=\"x86\">For direct on-line help you can try the IRC channels #debian or #debian-boot on the OFTC network. Alternatively you can contact the <ulink url=\"&url-list-subscribe;\">debian-user mailing list</ulink>.</phrase> <phrase arch=\"not-x86\">For less common architectures like &arch-title;, your best option is to ask on the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink>.</phrase> You can also file an installation report as described in <xref linkend=\"submit-bug\"/>. Please make sure that you describe your problem clearly and include any messages that are displayed and may help others to diagnose the issue." msgstr "" #. Tag: para @@ -89,7 +89,7 @@ msgstr "" #. Tag: para #: boot-new.xml:97 #, no-c-format -msgid "On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key and get a graphical screen with a button for each bootable OS, &debian; will be a button with a small penguin icon." +msgid "On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key and get a graphical screen with a button for each bootable OS, &debian-gnu; will be a button with a small penguin icon." msgstr "" #. Tag: para @@ -107,13 +107,13 @@ msgstr "" #. Tag: para #: boot-new.xml:118 #, no-c-format -msgid "Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian; by default (if you correctly partitioned and placed the Apple_Bootstrap partition first). If you have &debian; on a SCSI disk and MacOS on an IDE disk this may not work and you will have to enter OpenFirmware and set the <envar>boot-device</envar> variable, <command>ybin</command> normally does this automatically." +msgid "Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian-gnu; by default (if you correctly partitioned and placed the Apple_Bootstrap partition first). If you have &debian-gnu; on a SCSI disk and MacOS on an IDE disk this may not work and you will have to enter OpenFirmware and set the <envar>boot-device</envar> variable, <command>ybin</command> normally does this automatically." msgstr "" #. Tag: para #: boot-new.xml:127 #, no-c-format -msgid "After you boot &debian; for the first time you can add any additional options you desire (such as dual boot options) to <filename>/etc/yaboot.conf</filename> and run <command>ybin</command> to update your boot partition with the changed configuration. Please read the <ulink url=\"&url-powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information." +msgid "After you boot &debian-gnu; for the first time you can add any additional options you desire (such as dual boot options) to <filename>/etc/yaboot.conf</filename> and run <command>ybin</command> to update your boot partition with the changed configuration. Please read the <ulink url=\"&url-powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information." msgstr "" #. Tag: title diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index 3ce677ecd..c40c7e5b1 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2009-12-02 01:11+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+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" @@ -23,7 +23,7 @@ msgstr "" #. Tag: para #: hardware.xml:7 #, no-c-format -msgid "This section contains information about what hardware you need to get started with Debian. You will also find links to further information about hardware supported by GNU and Linux." +msgid "This section contains information about what hardware you need to get started with Debian. You will also find links to further information about hardware supported by GNU and &arch-kernel;." msgstr "" #. Tag: title @@ -35,7 +35,7 @@ msgstr "" #. Tag: para #: hardware.xml:21 #, no-c-format -msgid "Debian does not impose hardware requirements beyond the requirements of the Linux kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux kernel, libc, <command>gcc</command>, etc. have been ported, and for which a Debian port exists, can run Debian. Please refer to the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on &arch-title; architecture systems which have been tested with Debian." +msgid "Debian does not impose hardware requirements beyond the requirements of the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux or kFreeBSD kernel, libc, <command>gcc</command>, etc. have been ported, and for which a Debian port exists, can run Debian. Please refer to the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on &arch-title; architecture systems which have been tested with &debian-gnu;." msgstr "" #. Tag: para @@ -57,13 +57,13 @@ msgid "Debian GNU/Linux &release; supports eleven major architectures and severa msgstr "" #. Tag: entry -#: hardware.xml:53 +#: hardware.xml:53 hardware.xml:179 #, no-c-format msgid "Architecture" msgstr "" #. Tag: entry -#: hardware.xml:53 +#: hardware.xml:53 hardware.xml:179 #, no-c-format msgid "Debian Designation" msgstr "" @@ -81,7 +81,7 @@ msgid "Flavor" msgstr "" #. Tag: entry -#: hardware.xml:60 +#: hardware.xml:60 hardware.xml:185 #, no-c-format msgid "Intel x86-based" msgstr "" @@ -93,7 +93,7 @@ msgid "i386" msgstr "" #. Tag: entry -#: hardware.xml:67 +#: hardware.xml:67 hardware.xml:190 #, no-c-format msgid "AMD64 & Intel EM64T" msgstr "" @@ -413,1397 +413,1415 @@ msgstr "" #. Tag: para #: hardware.xml:169 #, no-c-format -msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture. If you are looking for information on any of the other Debian-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">Debian-Ports</ulink> pages." +msgid "Debian GNU/kFreeBSD &release; supports two architectures." +msgstr "" + +#. Tag: entry +#: hardware.xml:186 +#, no-c-format +msgid "kfreebsd-i386" +msgstr "" + +#. Tag: entry +#: hardware.xml:191 +#, no-c-format +msgid "kfreebsd-amd64" msgstr "" #. Tag: para -#: hardware.xml:178 +#: hardware.xml:196 +#, no-c-format +msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are looking for information on any of the other Debian-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">Debian-Ports</ulink> pages." +msgstr "" + +#. Tag: para +#: hardware.xml:206 #, no-c-format msgid "The &arch-title; architecture only supports Intel Itanium processors and not the much more common 64-bit processors from the EM64T family (including e.g. the Pentium D and the Core2 Duo). Those systems are supported by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit userland, the <emphasis>i386</emphasis> architecture." msgstr "" #. Tag: para -#: hardware.xml:188 +#: hardware.xml:216 #, no-c-format -msgid "This is the first official release of &debian; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well." +msgid "This is the first official release of &debian-gnu; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well." msgstr "" #. Tag: title -#: hardware.xml:210 hardware.xml:246 hardware.xml:352 hardware.xml:371 hardware.xml:454 hardware.xml:512 hardware.xml:565 +#: hardware.xml:239 hardware.xml:275 hardware.xml:381 hardware.xml:400 hardware.xml:483 hardware.xml:541 hardware.xml:594 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para -#: hardware.xml:211 hardware.xml:372 +#: hardware.xml:240 hardware.xml:401 #, no-c-format msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics." msgstr "" #. Tag: title -#: hardware.xml:219 hardware.xml:380 hardware.xml:489 +#: hardware.xml:248 hardware.xml:409 hardware.xml:518 #, no-c-format msgid "<title>CPU</title>" msgstr "" #. Tag: para -#: hardware.xml:220 +#: hardware.xml:249 #, no-c-format msgid "Both AMD64 and Intel EM64T processors are supported." msgstr "" #. Tag: para -#: hardware.xml:248 +#: hardware.xml:277 #, no-c-format msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard Debian distribution only supports installation on a number of the most common platforms. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU." msgstr "" #. Tag: para -#: hardware.xml:257 +#: hardware.xml:286 #, no-c-format msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems." msgstr "" #. Tag: para -#: hardware.xml:265 +#: hardware.xml:294 #, no-c-format msgid "The supported platforms are:" msgstr "" #. Tag: term -#: hardware.xml:272 +#: hardware.xml:301 #, no-c-format msgid "IOP32x" msgstr "" #. Tag: para -#: hardware.xml:273 +#: hardware.xml:302 #, no-c-format msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. Debian currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. Debian explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>." msgstr "" #. Tag: term -#: hardware.xml:286 +#: hardware.xml:315 #, no-c-format msgid "IXP4xx" msgstr "" #. Tag: para -#: hardware.xml:287 +#: hardware.xml:316 #, no-c-format msgid "The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected. There is an external site with <ulink url=\"&url-arm-cyrius-nslu2;\">installation instructions</ulink>." msgstr "" #. Tag: term -#: hardware.xml:301 +#: hardware.xml:330 #, no-c-format msgid "Kirkwood" msgstr "" #. Tag: para -#: hardware.xml:302 +#: hardware.xml:331 #, no-c-format msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base and OpenRD-Client), <ulink url=\"&url-arm-cyrius-sheevaplug;\">SheevaPlug</ulink> and <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (TS-110, TS-119, TS-210, TS-219 and TS-219P; the TS-410 and TS-419P are not yet supported)." msgstr "" #. Tag: term -#: hardware.xml:317 +#: hardware.xml:346 #, no-c-format msgid "Orion5x" msgstr "" #. Tag: para -#: hardware.xml:318 +#: hardware.xml:347 #, no-c-format msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: <ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>, <ulink url=\"&url-arm-cyrius-qnap;\">QNAP Turbo Station</ulink> (TS-109, TS-209 and TS-409)." msgstr "" #. Tag: term -#: hardware.xml:333 +#: hardware.xml:362 #, no-c-format msgid "<term>Versatile</term>" msgstr "" #. Tag: para -#: hardware.xml:334 +#: hardware.xml:363 #, no-c-format msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run Debian on ARM if you don't have the hardware." msgstr "" #. Tag: para -#: hardware.xml:353 +#: hardware.xml:382 #, no-c-format msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future." msgstr "" #. Tag: para -#: hardware.xml:381 +#: hardware.xml:410 #, no-c-format msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon." msgstr "" #. Tag: para -#: hardware.xml:388 +#: hardware.xml:417 #, no-c-format msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of Debian<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para> </footnote>." msgstr "" #. Tag: para -#: hardware.xml:421 +#: hardware.xml:450 #, no-c-format msgid "If your system has a 64-bit processor from the AMD64 or Intel EM64T families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture." msgstr "" #. Tag: title -#: hardware.xml:430 +#: hardware.xml:459 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:431 +#: hardware.xml:460 #, no-c-format msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, PCIe, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these." msgstr "" #. Tag: para -#: hardware.xml:455 +#: hardware.xml:484 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run Debian on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: para -#: hardware.xml:490 +#: hardware.xml:519 #, no-c-format msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the Debian installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported." msgstr "" #. Tag: para -#: hardware.xml:496 +#: hardware.xml:525 #, no-c-format msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture." msgstr "" #. Tag: para -#: hardware.xml:513 +#: hardware.xml:542 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run Debian on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: title -#: hardware.xml:541 +#: hardware.xml:570 #, no-c-format msgid "CPU/Machine types" msgstr "" #. Tag: para -#: hardware.xml:543 +#: hardware.xml:572 #, no-c-format msgid "All MIPS based Cobalt machines are supported with the exception of the Qube 2700 (Qube 1)." msgstr "" #. Tag: title -#: hardware.xml:551 +#: hardware.xml:580 #, no-c-format msgid "Supported console options" msgstr "" #. Tag: para -#: hardware.xml:552 +#: hardware.xml:581 #, no-c-format msgid "Cobalt machines use 115200 bps." msgstr "" #. Tag: para -#: hardware.xml:566 +#: hardware.xml:595 #, no-c-format -msgid "For &debian; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported." +msgid "For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported." msgstr "" #. Tag: title -#: hardware.xml:587 +#: hardware.xml:616 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:589 +#: hardware.xml:618 #, no-c-format msgid "There are two flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:596 +#: hardware.xml:625 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:597 +#: hardware.xml:626 #, no-c-format msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors." msgstr "" #. Tag: term -#: hardware.xml:607 +#: hardware.xml:636 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:608 +#: hardware.xml:637 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:612 +#: hardware.xml:641 #, no-c-format msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270." msgstr "" #. Tag: para -#: hardware.xml:618 +#: hardware.xml:647 #, no-c-format msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690." msgstr "" #. Tag: para -#: hardware.xml:623 +#: hardware.xml:652 #, no-c-format msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour." msgstr "" #. Tag: title -#: hardware.xml:657 +#: hardware.xml:686 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:659 +#: hardware.xml:688 #, no-c-format msgid "Apple (and briefly a few other manufacturers — Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by Debian), OldWorld, and NewWorld." msgstr "" #. Tag: para -#: hardware.xml:666 +#: hardware.xml:695 #, no-c-format msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld." msgstr "" #. Tag: para -#: hardware.xml:674 +#: hardware.xml:703 #, no-c-format msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards." msgstr "" #. Tag: para -#: hardware.xml:682 +#: hardware.xml:711 #, no-c-format msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>." msgstr "" #. Tag: entry -#: hardware.xml:698 hardware.xml:833 hardware.xml:877 hardware.xml:906 +#: hardware.xml:727 hardware.xml:862 hardware.xml:906 hardware.xml:935 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:699 +#: hardware.xml:728 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:705 +#: hardware.xml:734 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:706 +#: hardware.xml:735 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:707 hardware.xml:710 hardware.xml:713 hardware.xml:716 hardware.xml:719 hardware.xml:722 hardware.xml:725 hardware.xml:728 hardware.xml:731 hardware.xml:734 hardware.xml:737 hardware.xml:740 hardware.xml:743 hardware.xml:746 hardware.xml:749 hardware.xml:752 +#: hardware.xml:736 hardware.xml:739 hardware.xml:742 hardware.xml:745 hardware.xml:748 hardware.xml:751 hardware.xml:754 hardware.xml:757 hardware.xml:760 hardware.xml:763 hardware.xml:766 hardware.xml:769 hardware.xml:772 hardware.xml:775 hardware.xml:778 hardware.xml:781 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:709 +#: hardware.xml:738 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:712 +#: hardware.xml:741 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:715 +#: hardware.xml:744 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:718 +#: hardware.xml:747 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:721 +#: hardware.xml:750 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:724 +#: hardware.xml:753 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:727 +#: hardware.xml:756 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:730 +#: hardware.xml:759 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:733 +#: hardware.xml:762 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:736 +#: hardware.xml:765 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:739 +#: hardware.xml:768 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:742 +#: hardware.xml:771 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:745 +#: hardware.xml:774 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:748 +#: hardware.xml:777 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:751 +#: hardware.xml:780 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:754 +#: hardware.xml:783 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:755 hardware.xml:758 hardware.xml:761 hardware.xml:764 hardware.xml:767 hardware.xml:770 hardware.xml:773 hardware.xml:776 hardware.xml:779 hardware.xml:782 hardware.xml:785 hardware.xml:788 hardware.xml:794 hardware.xml:797 hardware.xml:803 hardware.xml:809 hardware.xml:815 +#: hardware.xml:784 hardware.xml:787 hardware.xml:790 hardware.xml:793 hardware.xml:796 hardware.xml:799 hardware.xml:802 hardware.xml:805 hardware.xml:808 hardware.xml:811 hardware.xml:814 hardware.xml:817 hardware.xml:823 hardware.xml:826 hardware.xml:832 hardware.xml:838 hardware.xml:844 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:757 +#: hardware.xml:786 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:760 +#: hardware.xml:789 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:763 +#: hardware.xml:792 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:766 +#: hardware.xml:795 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:769 +#: hardware.xml:798 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:772 +#: hardware.xml:801 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:775 +#: hardware.xml:804 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:778 +#: hardware.xml:807 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:781 +#: hardware.xml:810 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:784 +#: hardware.xml:813 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:787 +#: hardware.xml:816 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:792 +#: hardware.xml:821 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:793 +#: hardware.xml:822 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:796 +#: hardware.xml:825 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:801 +#: hardware.xml:830 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:802 +#: hardware.xml:831 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:807 +#: hardware.xml:836 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:808 +#: hardware.xml:837 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:813 hardware.xml:839 +#: hardware.xml:842 hardware.xml:868 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:814 +#: hardware.xml:843 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:823 +#: hardware.xml:852 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:840 +#: hardware.xml:869 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:842 +#: hardware.xml:871 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:844 +#: hardware.xml:873 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:846 +#: hardware.xml:875 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:848 +#: hardware.xml:877 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:852 hardware.xml:883 +#: hardware.xml:881 hardware.xml:912 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:853 +#: hardware.xml:882 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:855 +#: hardware.xml:884 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:857 +#: hardware.xml:886 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:859 +#: hardware.xml:888 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:867 +#: hardware.xml:896 #, no-c-format msgid "CHRP subarchitecture (unsupported)" msgstr "" #. Tag: entry -#: hardware.xml:884 +#: hardware.xml:913 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:887 +#: hardware.xml:916 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:888 +#: hardware.xml:917 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: title -#: hardware.xml:896 +#: hardware.xml:925 #, no-c-format msgid "APUS subarchitecture (unsupported)" msgstr "" #. Tag: entry -#: hardware.xml:912 +#: hardware.xml:941 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:913 +#: hardware.xml:942 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:921 +#: hardware.xml:950 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:923 +#: hardware.xml:952 #, no-c-format msgid "NuBus systems are not currently supported by Debian/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which Debian does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>." msgstr "" #. Tag: title -#: hardware.xml:960 +#: hardware.xml:989 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:962 +#: hardware.xml:991 #, no-c-format msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950." msgstr "" #. Tag: para -#: hardware.xml:971 +#: hardware.xml:1000 #, no-c-format msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD." msgstr "" #. Tag: para -#: hardware.xml:979 +#: hardware.xml:1008 #, no-c-format msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)." msgstr "" #. Tag: title -#: hardware.xml:995 +#: hardware.xml:1024 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "" #. Tag: para -#: hardware.xml:996 +#: hardware.xml:1025 #, no-c-format msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128.ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance." msgstr "" #. Tag: title -#: hardware.xml:1018 +#: hardware.xml:1047 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para -#: hardware.xml:1019 +#: hardware.xml:1048 #, no-c-format msgid "Sparc-based hardware is divided into a number of different subarchitectures, identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u or sun4v. The following list describes what machines they include and what level of support may be expected for each of them." msgstr "" #. Tag: term -#: hardware.xml:1030 +#: hardware.xml:1059 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "" #. Tag: para -#: hardware.xml:1032 +#: hardware.xml:1061 #, no-c-format msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1039 +#: hardware.xml:1068 #, no-c-format msgid "The last Debian release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases." msgstr "" #. Tag: term -#: hardware.xml:1049 +#: hardware.xml:1078 #, no-c-format msgid "<term>sun4u</term>" msgstr "" #. Tag: para -#: hardware.xml:1051 +#: hardware.xml:1080 #, no-c-format msgid "This subarchitecture includes all 64-bit machines (sparc64) based on the UltraSparc processor and its clones. Most of the machines are well supported, even though for some you may experience problems booting from CD due to firmware or bootloader bugs (this problem may be worked around by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP configurations respectively." msgstr "" #. Tag: term -#: hardware.xml:1064 +#: hardware.xml:1093 #, no-c-format msgid "<term>sun4v</term>" msgstr "" #. Tag: para -#: hardware.xml:1066 +#: hardware.xml:1095 #, no-c-format msgid "This is the newest addition to the Sparc family, which includes machines based on the Niagara multi-core CPUs. At the moment such CPUs are only available in T1000 and T2000 servers by Sun, and are well supported. Use the sparc64-smp kernel." msgstr "" #. Tag: para -#: hardware.xml:1077 +#: hardware.xml:1106 #, no-c-format msgid "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel." msgstr "" #. Tag: title -#: hardware.xml:1086 +#: hardware.xml:1115 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1087 +#: hardware.xml:1116 #, no-c-format msgid "Laptops are also supported and nowadays most laptops work out of the box. In case a laptop contains specialized or proprietary hardware, some specific functions may not be supported. To see if your particular laptop works well with GNU/Linux, see for example the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>." msgstr "" #. Tag: title -#: hardware.xml:1099 hardware.xml:1122 hardware.xml:1142 hardware.xml:1165 +#: hardware.xml:1128 hardware.xml:1151 hardware.xml:1171 hardware.xml:1194 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1100 +#: hardware.xml:1129 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image has been compiled with SMP support. The standard kernel is also usable on non-SMP systems, but has a slight overhead which will cause a small reduction in performance. For normal system use this will hardly be noticable." msgstr "" #. Tag: para -#: hardware.xml:1109 +#: hardware.xml:1138 #, no-c-format -msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." +msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard Debian kernel.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1124 +#: hardware.xml:1153 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image has been compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems." msgstr "" #. Tag: para -#: hardware.xml:1133 +#: hardware.xml:1162 #, no-c-format msgid "The 486 flavour of the Debian kernel image packages for &arch-title; is not compiled with SMP support." msgstr "" #. Tag: para -#: hardware.xml:1143 +#: hardware.xml:1172 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. However, the standard Debian &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1152 +#: hardware.xml:1181 #, no-c-format -msgid "In order to take advantage of multiple processors, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." +msgid "In order to take advantage of multiple processors, you'll have to replace the standard Debian kernel.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1166 +#: hardware.xml:1195 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture, and is supported by a precompiled Debian kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1176 +#: hardware.xml:1205 #, no-c-format msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package." msgstr "" #. Tag: para -#: hardware.xml:1182 +#: hardware.xml:1211 #, no-c-format -msgid "You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." +msgid "You can also build your own customized kernel to support SMP.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>" msgstr "" #. Tag: title -#: hardware.xml:1193 +#: hardware.xml:1222 #, no-c-format msgid "Graphics Card Support" msgstr "" #. Tag: para -#: hardware.xml:1194 +#: hardware.xml:1223 #, no-c-format msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document." msgstr "" #. Tag: para -#: hardware.xml:1202 +#: hardware.xml:1231 #, no-c-format msgid "Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian &release; ships with X.Org version &x11ver;." msgstr "" #. Tag: para -#: hardware.xml:1211 +#: hardware.xml:1240 #, no-c-format msgid "The X.Org X Window System is only supported on the SGI Indy and the O2." msgstr "" #. Tag: para -#: hardware.xml:1216 +#: hardware.xml:1245 #, no-c-format msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card." msgstr "" #. Tag: para -#: hardware.xml:1226 +#: hardware.xml:1255 #, no-c-format msgid "It is not uncommon for a Sparc machine to have two graphics cards in a default configuration. In such a case there is a possibility that the Linux kernel will not direct its output to the card initially used by the firmware. The lack of output on the graphical console may then be mistaken for a hang (usually the last message seen on console is 'Booting Linux...'). One possible solution is to physically remove one of the video cards; another option is to disable one of the cards using a kernel boot parameter. Also, if graphical output is not required or desired, serial console may be used as an alternative. On some systems use of serial console can be activated automatically by disconnecting the keyboard before booting the system." msgstr "" #. Tag: title -#: hardware.xml:1248 +#: hardware.xml:1277 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:1249 +#: hardware.xml:1278 #, no-c-format -msgid "Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>" +msgid "Almost any network interface card (NIC) supported by the &arch-kernel; kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1258 +#: hardware.xml:1287 #, no-c-format msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:" msgstr "" #. Tag: para -#: hardware.xml:1264 +#: hardware.xml:1293 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:1269 +#: hardware.xml:1298 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:1274 +#: hardware.xml:1303 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:1279 +#: hardware.xml:1308 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:1284 +#: hardware.xml:1313 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:1291 +#: hardware.xml:1320 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:1296 +#: hardware.xml:1325 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:1301 +#: hardware.xml:1330 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:1306 +#: hardware.xml:1335 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:1315 +#: hardware.xml:1344 #, no-c-format msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided. The major exception is the IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a proprietary microcode for the operation of its built-in Ethernet device. Unofficial images for Linksys NSLU2 with this proprietary microcode can be obtained from the <ulink url=\"&url-slug-firmware;\">Slug-Firmware site</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1325 +#: hardware.xml:1354 #, no-c-format msgid "ISDN is supported, but not during the installation." msgstr "" #. Tag: title -#: hardware.xml:1332 +#: hardware.xml:1361 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:1333 +#: hardware.xml:1362 #, no-c-format -msgid "Wireless networking is in general supported as well and a growing number of wireless adapters are supported by the official Linux kernel, although many of them do require firmware to be loaded. If firmware is needed, the installer will prompt you to load firmware. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware during the installation." +msgid "Wireless networking is in general supported as well and a growing number of wireless adapters are supported by the official &arch-kernel; kernel, although many of them do require firmware to be loaded. If firmware is needed, the installer will prompt you to load firmware. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware during the installation." msgstr "" #. Tag: para -#: hardware.xml:1341 +#: hardware.xml:1370 #, no-c-format -msgid "Wireless NICs that are not supported by the official Linux kernel can generally be made to work under &debian;, but are not supported during the installation." +msgid "Wireless NICs that are not supported by the official &arch-kernel; kernel can generally be made to work under &debian-gnu;, but are not supported during the installation." msgstr "" #. Tag: para -#: hardware.xml:1346 +#: hardware.xml:1375 #, no-c-format msgid "Support for encrypted wireless during installation is currently limited to WEP. If your access point uses stronger encryption, it cannot be used during the installation process." msgstr "" #. Tag: para -#: hardware.xml:1352 +#: hardware.xml:1381 #, no-c-format -msgid "If there is a problem with wireless and there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually." +msgid "If there is a problem with wireless and there is no other NIC you can use during the installation, it is still possible to install &debian-gnu; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually." msgstr "" #. Tag: para -#: hardware.xml:1362 +#: hardware.xml:1391 #, no-c-format msgid "In some cases the driver you need may not be available as a Debian package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>" msgstr "" #. Tag: title -#: hardware.xml:1376 +#: hardware.xml:1405 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:1377 +#: hardware.xml:1406 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:1384 +#: hardware.xml:1413 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:1386 +#: hardware.xml:1415 #, no-c-format msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly." msgstr "" #. Tag: para -#: hardware.xml:1396 +#: hardware.xml:1425 #, no-c-format msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>." msgstr "" #. Tag: para -#: hardware.xml:1404 +#: hardware.xml:1433 #, no-c-format msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted." msgstr "" #. Tag: title -#: hardware.xml:1417 +#: hardware.xml:1446 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:1419 +#: hardware.xml:1448 #, no-c-format msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." msgstr "" #. Tag: title -#: hardware.xml:1434 +#: hardware.xml:1463 #, no-c-format msgid "Braille Displays" msgstr "" #. Tag: para -#: hardware.xml:1435 +#: hardware.xml:1464 #, no-c-format -msgid "Support for braille displays is determined by the underlying support found in <classname>brltty</classname>. Most displays work under <classname>brltty</classname>, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the <ulink url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian; &release; ships with <classname>brltty</classname> version &brlttyver;." +msgid "Support for braille displays is determined by the underlying support found in <classname>brltty</classname>. Most displays work under <classname>brltty</classname>, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the <ulink url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-gnu; &release; ships with <classname>brltty</classname> version &brlttyver;." msgstr "" #. Tag: title -#: hardware.xml:1449 +#: hardware.xml:1478 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: hardware.xml:1450 +#: hardware.xml:1479 #, no-c-format -msgid "Support for hardware speech synthesis devices is determined by the underlying support found in <classname>speakup</classname>. <classname>speakup</classname> only supports integrated boards and external devices connected to a serial port (no USB or serial-to-USB adapters are supported). Details on supported hardware speech synthesis devices can be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> website</ulink>. &debian; &release; ships with <classname>speakup</classname> version &speakupver;." +msgid "Support for hardware speech synthesis devices is determined by the underlying support found in <classname>speakup</classname>. <classname>speakup</classname> only supports integrated boards and external devices connected to a serial port (no USB or serial-to-USB adapters are supported). Details on supported hardware speech synthesis devices can be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> website</ulink>. &debian-gnu; &release; ships with <classname>speakup</classname> version &speakupver;." msgstr "" #. Tag: title -#: hardware.xml:1470 +#: hardware.xml:1499 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:1471 +#: hardware.xml:1500 #, no-c-format -msgid "Linux supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system." +msgid "&arch-kernel; supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system." msgstr "" #. Tag: para -#: hardware.xml:1477 +#: hardware.xml:1506 #, no-c-format msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>)." msgstr "" #. Tag: para -#: hardware.xml:1483 +#: hardware.xml:1512 #, no-c-format msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux." msgstr "" #. Tag: para -#: hardware.xml:1489 +#: hardware.xml:1518 #, no-c-format msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP." msgstr "" #. Tag: para -#: hardware.xml:1495 +#: hardware.xml:1524 #, no-c-format msgid "The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." msgstr "" #. Tag: title -#: hardware.xml:1507 +#: hardware.xml:1536 #, no-c-format msgid "Devices Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:1508 +#: hardware.xml:1537 #, no-c-format msgid "Besides the availability of a device driver, some hardware also requires so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware." msgstr "" #. Tag: para -#: hardware.xml:1516 +#: hardware.xml:1545 #, no-c-format -msgid "In most cases firmware is non-free according to the criteria used by the &debian; project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if &debian; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive." +msgid "In most cases firmware is non-free according to the criteria used by the &debian-gnu; project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if &debian-gnu; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive." msgstr "" #. Tag: para -#: hardware.xml:1525 +#: hardware.xml:1554 #, no-c-format -msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a floppy disk or USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation." +msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian-gnu; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a floppy disk or USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation." msgstr "" #. Tag: title -#: hardware.xml:1541 +#: hardware.xml:1570 #, no-c-format -msgid "Purchasing Hardware Specifically for GNU/Linux" +msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;" msgstr "" #. Tag: para -#: hardware.xml:1543 +#: hardware.xml:1572 #, no-c-format msgid "There are several vendors, who ship systems with Debian or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux." msgstr "" #. Tag: para -#: hardware.xml:1551 +#: hardware.xml:1580 #, no-c-format msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that." msgstr "" #. Tag: para -#: hardware.xml:1559 +#: hardware.xml:1588 #, no-c-format -msgid "Whether or not you are purchasing a system with Linux bundled, or even a used system, it is still important to check that your hardware is supported by the Linux kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a Linux system. Support Linux-friendly hardware vendors." +msgid "Whether or not you are purchasing a system with &arch-kernel; bundled, or even a used system, it is still important to check that your hardware is supported by the &arch-kernel; kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware vendors." msgstr "" #. Tag: title -#: hardware.xml:1570 +#: hardware.xml:1599 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:1571 +#: hardware.xml:1600 #, no-c-format -msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the Linux source code." +msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the &arch-kernel; source code." msgstr "" #. Tag: para -#: hardware.xml:1578 +#: hardware.xml:1607 #, no-c-format -msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under Linux. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market." +msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under &arch-kernel;. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market." msgstr "" #. Tag: title -#: hardware.xml:1590 +#: hardware.xml:1619 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:1591 +#: hardware.xml:1620 #, no-c-format msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence." msgstr "" #. Tag: para -#: hardware.xml:1604 +#: hardware.xml:1633 #, no-c-format -msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes it being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." +msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a &arch-kernel; driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes it being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a &arch-kernel; user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" #. Tag: para -#: hardware.xml:1625 +#: hardware.xml:1654 #, no-c-format -msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>." +msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware<phrase arch=\"linux-any\"> until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink></phrase>." msgstr "" #. Tag: title -#: hardware.xml:1642 +#: hardware.xml:1672 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:1644 +#: hardware.xml:1674 #, no-c-format msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used to install Debian. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section." msgstr "" #. Tag: title -#: hardware.xml:1655 +#: hardware.xml:1685 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:1656 +#: hardware.xml:1686 #, no-c-format msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive." msgstr "" #. Tag: para -#: hardware.xml:1662 +#: hardware.xml:1692 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:1669 +#: hardware.xml:1699 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:1671 +#: hardware.xml:1701 #, no-c-format msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI." msgstr "" #. Tag: para -#: hardware.xml:1678 +#: hardware.xml:1708 #, no-c-format msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>." msgstr "" #. Tag: para -#: hardware.xml:1690 +#: hardware.xml:1720 #, no-c-format msgid "SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux." msgstr "" #. Tag: para -#: hardware.xml:1696 +#: hardware.xml:1726 #, no-c-format msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" #. Tag: para -#: hardware.xml:1701 +#: hardware.xml:1731 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines." msgstr "" #. Tag: para -#: hardware.xml:1705 +#: hardware.xml:1735 #, no-c-format msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware." msgstr "" #. Tag: title -#: hardware.xml:1719 +#: hardware.xml:1749 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:1721 +#: hardware.xml:1751 #, no-c-format msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk." msgstr "" #. Tag: para -#: hardware.xml:1727 +#: hardware.xml:1757 #, no-c-format msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)." msgstr "" #. Tag: title -#: hardware.xml:1735 +#: hardware.xml:1765 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:1737 +#: hardware.xml:1767 #, no-c-format msgid "Many Debian boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives." msgstr "" #. Tag: title -#: hardware.xml:1749 +#: hardware.xml:1779 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:1751 +#: hardware.xml:1781 #, no-c-format msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP." msgstr "" #. Tag: para -#: hardware.xml:1761 +#: hardware.xml:1791 #, no-c-format msgid "You can also <emphasis>boot</emphasis> the installation system over the network. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1767 +#: hardware.xml:1797 #, no-c-format msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." msgstr "" #. Tag: title -#: hardware.xml:1775 +#: hardware.xml:1805 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:1777 +#: hardware.xml:1807 #, no-c-format -msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." +msgid "If you are running another Unix-like system, you could use it to install &debian-gnu; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." msgstr "" #. Tag: title -#: hardware.xml:1789 +#: hardware.xml:1819 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:1791 +#: hardware.xml:1821 #, no-c-format -msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware." +msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine<phrase arch=\"linux-any\"> (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel)</phrase>. Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware." msgstr "" #. Tag: para -#: hardware.xml:1801 +#: hardware.xml:1831 #, no-c-format msgid "Generally, the Debian installation system includes support for floppies, IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." msgstr "" #. Tag: para -#: hardware.xml:1808 +#: hardware.xml:1838 #, no-c-format msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or PATA — are supported. SATA and SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." msgstr "" #. Tag: para -#: hardware.xml:1816 +#: hardware.xml:1846 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel." msgstr "" #. Tag: para -#: hardware.xml:1849 +#: hardware.xml:1879 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all." msgstr "" #. Tag: para -#: hardware.xml:1855 +#: hardware.xml:1885 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive." msgstr "" #. Tag: para -#: hardware.xml:1861 +#: hardware.xml:1891 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:1866 +#: hardware.xml:1896 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)." msgstr "" #. Tag: title -#: hardware.xml:1883 +#: hardware.xml:1913 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:1885 +#: hardware.xml:1915 #, no-c-format msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>." msgstr "" #. Tag: para -#: hardware.xml:1892 +#: hardware.xml:1922 #, no-c-format msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users." msgstr "" diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot index 7ad4deae5..6f6c15669 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: 2010-02-26 01:12+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+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" @@ -23,13 +23,13 @@ msgstr "" #. Tag: title #: install-methods.xml:12 #, no-c-format -msgid "Official &debian; CD-ROM Sets" +msgid "Official &debian-gnu; CD-ROM Sets" msgstr "" #. Tag: para #: install-methods.xml:13 #, no-c-format -msgid "By far the easiest way to install &debian; is from an Official Debian CD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD-ROM images from a Debian mirror and make your own set, if you have a fast network connection and a CD burner (see the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink> for detailed instructions). If you have a Debian CD set and CDs are bootable on your machine, you can skip right to <xref linkend=\"boot-installer\"/>; much effort has been expended to ensure the files most people need are there on the CD. Although a full set of binary packages requires several CDs, it is unlikely you will need packages on the third CD and above. You may also consider using the DVD version, which saves a lot of space on your shelf and you avoid the CD shuffling marathon." +msgid "By far the easiest way to install &debian-gnu; is from an Official Debian CD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD-ROM images from a Debian mirror and make your own set, if you have a fast network connection and a CD burner (see the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink> for detailed instructions). If you have a Debian CD set and CDs are bootable on your machine, you can skip right to <xref linkend=\"boot-installer\"/>; much effort has been expended to ensure the files most people need are there on the CD. Although a full set of binary packages requires several CDs, it is unlikely you will need packages on the third CD and above. You may also consider using the DVD version, which saves a lot of space on your shelf and you avoid the CD shuffling marathon." msgstr "" #. Tag: para @@ -302,7 +302,7 @@ msgstr "" #. Tag: para #: install-methods.xml:426 #, no-c-format -msgid "If you are creating the floppy image from files which were originally on the official &debian; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a Debian mirror." +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 @@ -380,113 +380,134 @@ msgstr "" #. Tag: para #: install-methods.xml:532 #, no-c-format -msgid "There are two installation methods possible when booting from USB stick. The first is to install completely from the network. The second is to also copy a CD image onto the USB stick and use that as a source for packages, possibly in combination with a mirror. This second method is the more common." +msgid "There are two installation methods possible when booting from USB stick. The first is to only use the USB stick to boot the installer, and then install completely from the network. The second is to also copy a CD image onto the USB stick and use that as a source for packages, possibly in combination with a mirror." msgstr "" #. Tag: para #: install-methods.xml:540 #, no-c-format -msgid "For the first installation method you'll need to download an installer image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>) and use the <quote>flexible way</quote> explained below to copy the files to the USB stick." +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:548 +#: install-methods.xml:553 #, no-c-format -msgid "Installation images for the second installation method can be found in the <filename>hd-media</filename> directory and either the <quote>easy way</quote> or the <quote>flexible way</quote> can be used to copy the image to the USB stick. For this installation method you will also need to download a CD image. The installation image and the CD image must be based on the same release of &d-i;. If they do not match you are likely to get errors<footnote> <para> The error message that is most likely to be displayed is that no kernel modules can be found. This means that the version of the kernel module udebs included on the CD image is different from the version of the running kernel. </para> </footnote> during the installation." +msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost." msgstr "" #. Tag: para -#: install-methods.xml:567 +#: install-methods.xml:560 #, 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." +msgid "To prepare a USB stick that only boots the installer, which then proceeds to install entirely from the network, you'll need to download the <filename>mini.iso</filename> image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>), and write this file directly to the USB stick, overwriting its current contents. This method will work with very small USB sticks, only a few megabytes in size." msgstr "" #. Tag: para -#: install-methods.xml:581 +#: install-methods.xml:570 #, 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." +msgid "" + "For example, when using an existing GNU/Linux system, the <filename>mini.iso</filename> file can be written to a USB stick as follows: <informalexample><screen>\n" + "# cat mini.iso > /dev/<replaceable>sdX</replaceable>\n" + "# sync\n" + "</screen></informalexample> To add firmware to a USB stick prepared in this way, obtain the necessary firmware files. See <xref linkend=\"loading-firmware\"/> for more information. 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:582 +#, no-c-format +msgid "" + "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n" + "# cd /mnt\n" + "# tar zxvf <replaceable>/path/to/</replaceable>firmware.tar.gz\n" + "# cd /\n" + "# umount" +msgstr "" + +#. Tag: para +#: install-methods.xml:584 +#, no-c-format +msgid "To prepare a USB stick that installs packages from a CD image included on the stick, use the installer images found in the <filename>hd-media</filename> directory. Either the <quote>easy way</quote> or the <quote>flexible way</quote> can be used to copy the image to the USB stick. For this installation method you will also need to download a CD image. The installation image and the CD image must be based on the same release of &d-i;. If they do not match you are likely to get errors<footnote> <para> The error message that is most likely to be displayed is that no kernel modules can be found. This means that the version of the kernel module udebs included on the CD image is different from the version of the running kernel. </para> </footnote> during the installation." msgstr "" #. Tag: para -#: install-methods.xml:589 +#: install-methods.xml:604 #, no-c-format msgid "Note that the USB stick should be at least 256 MB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)." msgstr "" #. Tag: title -#: install-methods.xml:597 +#: install-methods.xml:612 #, no-c-format msgid "Copying the files — the easy way" msgstr "" #. Tag: para -#: install-methods.xml:598 +#: install-methods.xml:613 #, 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>" +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:607 +#: install-methods.xml:622 #, no-c-format msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 256 MB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose. A second disadvantage is that you cannot copy a full CD image onto the USB stick, but only the smaller businesscard or netinst CD images." msgstr "" #. Tag: para -#: install-methods.xml:617 +#: install-methods.xml:632 #, no-c-format msgid "To use this image simply extract it directly to your USB stick:" msgstr "" #. Tag: screen -#: install-methods.xml:621 +#: install-methods.xml:636 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sdX</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:623 +#: install-methods.xml:638 #, 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:629 +#: install-methods.xml:644 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sdX2</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:631 +#: install-methods.xml:646 #, no-c-format msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a Debian netinst or businesscard ISO image to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done." msgstr "" #. Tag: title -#: install-methods.xml:648 +#: install-methods.xml:663 #, no-c-format msgid "Copying the files — the flexible way" msgstr "" #. Tag: para -#: install-methods.xml:649 +#: install-methods.xml:664 #, 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:664 install-methods.xml:776 +#: install-methods.xml:679 install-methods.xml:791 #, no-c-format msgid "Partitioning the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:665 +#: install-methods.xml:680 #, 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:670 +#: install-methods.xml:685 #, 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>, and then create the filesystem using: <informalexample><screen>\n" @@ -495,13 +516,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:689 +#: install-methods.xml:704 #, 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:699 +#: install-methods.xml:714 #, 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" @@ -510,19 +531,19 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:716 install-methods.xml:823 +#: install-methods.xml:731 install-methods.xml:838 #, no-c-format msgid "Adding the installer image" msgstr "" #. Tag: para -#: install-methods.xml:717 +#: install-methods.xml:732 #, 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:741 +#: install-methods.xml:756 #, 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" @@ -532,13 +553,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:753 +#: install-methods.xml:768 #, no-c-format msgid "If you used an <filename>hd-media</filename> image, you should now copy a Debian ISO image<footnote> <para> You can use either a businesscard, 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:777 +#: install-methods.xml:792 #, 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" @@ -547,13 +568,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:794 +#: install-methods.xml:809 #, 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:803 +#: install-methods.xml:818 #, 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" @@ -566,37 +587,37 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:824 +#: install-methods.xml:839 #, 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:831 +#: install-methods.xml:846 #, no-c-format msgid "<filename>vmlinux</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:836 +#: install-methods.xml:851 #, no-c-format msgid "<filename>initrd.gz</filename> (initial ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:841 +#: install-methods.xml:856 #, no-c-format msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" msgstr "" #. Tag: para -#: install-methods.xml:846 +#: install-methods.xml:861 #, no-c-format msgid "<filename>boot.msg</filename> (optional boot message)" msgstr "" #. Tag: para -#: install-methods.xml:853 +#: install-methods.xml:868 #, no-c-format msgid "" "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n" @@ -614,259 +635,283 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:863 +#: install-methods.xml:878 #, no-c-format msgid "If you used an <filename>hd-media</filename> image, you should now copy a Debian ISO image (businesscard, netinst or full CD image; be sure to select one that fits) onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)." msgstr "" #. Tag: title -#: install-methods.xml:878 +#: install-methods.xml:893 #, no-c-format msgid "Booting the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:879 +#: install-methods.xml:894 #, no-c-format msgid "If your system refuses to boot from the memory stick, the stick may contain an invalid master boot record (MBR). To fix this, use the <command>install-mbr</command> command from the package <classname>mbr</classname>:" msgstr "" #. Tag: screen -#: install-methods.xml:886 +#: install-methods.xml:901 #, no-c-format msgid "# install-mbr /dev/<replaceable>sdX</replaceable>" msgstr "" #. Tag: title -#: install-methods.xml:897 +#: install-methods.xml:912 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "" #. Tag: para -#: install-methods.xml:898 +#: install-methods.xml:913 #, 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:904 +#: install-methods.xml:919 #, 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:911 -#, no-c-format -msgid "The installer cannot boot from files on an NTFS file system." -msgstr "" - -#. Tag: para -#: install-methods.xml:915 +#: install-methods.xml:926 #, 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:926 +#: install-methods.xml:937 #, 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:935 +#: install-methods.xml:946 #, no-c-format msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: install-methods.xml:937 +#: install-methods.xml:948 #, 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:943 +#: install-methods.xml:954 #, 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:949 +#: install-methods.xml:960 #, no-c-format -msgid "Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>." +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:956 +#: install-methods.xml:968 #, no-c-format msgid "<filename>vmlinuz</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:961 +#: install-methods.xml:973 #, no-c-format msgid "<filename>initrd.gz</filename> (ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:968 +#: install-methods.xml:980 #, no-c-format msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>." msgstr "" #. Tag: title -#: install-methods.xml:978 +#: install-methods.xml:990 +#, no-c-format +msgid "Hard disk installer booting using <command>loadlin</command>" +msgstr "" + +#. Tag: para +#: install-methods.xml:991 +#, 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:996 +#, no-c-format +msgid "Copy the following files from a Debian CD image to <filename>c:\\</filename>." +msgstr "" + +#. Tag: para +#: install-methods.xml:1001 +#, no-c-format +msgid "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)" +msgstr "" + +#. Tag: para +#: install-methods.xml:1006 +#, no-c-format +msgid "<filename>/tools</filename> (loadlin tool)" +msgstr "" + +#. Tag: title +#: install-methods.xml:1019 #, no-c-format msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:979 +#: install-methods.xml:1020 #, 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:992 +#: install-methods.xml:1033 #, 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:1012 +#: install-methods.xml:1053 #, no-c-format msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1013 +#: install-methods.xml:1054 #, 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:1024 +#: install-methods.xml:1065 #, 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:1034 install-methods.xml:1360 +#: install-methods.xml:1075 install-methods.xml:1401 #, no-c-format msgid "vmlinux" msgstr "" #. Tag: filename -#: install-methods.xml:1039 install-methods.xml:1365 +#: install-methods.xml:1080 install-methods.xml:1406 #, no-c-format msgid "initrd.gz" msgstr "" #. Tag: filename -#: install-methods.xml:1044 install-methods.xml:1370 +#: install-methods.xml:1085 install-methods.xml:1411 #, no-c-format msgid "yaboot" msgstr "" #. Tag: filename -#: install-methods.xml:1049 install-methods.xml:1375 +#: install-methods.xml:1090 install-methods.xml:1416 #, no-c-format msgid "yaboot.conf" msgstr "" #. Tag: para -#: install-methods.xml:1054 +#: install-methods.xml:1095 #, 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:1062 +#: install-methods.xml:1103 #, no-c-format msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1075 +#: install-methods.xml:1116 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "" #. Tag: para -#: install-methods.xml:1076 +#: install-methods.xml:1117 #, 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:1084 +#: install-methods.xml:1125 #, 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:1091 +#: install-methods.xml:1132 #, 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:1105 +#: install-methods.xml:1146 #, 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:1111 +#: install-methods.xml:1152 #, 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:1116 +#: install-methods.xml:1157 #, 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:1124 +#: install-methods.xml:1165 #, no-c-format -msgid "For a &debian; 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>." +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:1140 +#: install-methods.xml:1181 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para -#: install-methods.xml:1141 +#: install-methods.xml:1182 #, 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:1153 +#: install-methods.xml:1194 #, 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:1174 +#: install-methods.xml:1215 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1175 +#: install-methods.xml:1216 #, no-c-format -msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):" +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:1182 +#: install-methods.xml:1223 #, no-c-format msgid "" "option domain-name \"example.com\";\n" @@ -891,25 +936,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1184 +#: install-methods.xml:1225 #, 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:1194 +#: install-methods.xml:1235 #, no-c-format msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1202 +#: install-methods.xml:1243 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1203 +#: install-methods.xml:1244 #, 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" @@ -944,22 +989,22 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1223 +#: install-methods.xml:1264 #, no-c-format msgid "Setting up a BOOTP server" msgstr "" #. Tag: para -#: install-methods.xml:1224 +#: install-methods.xml:1265 #, no-c-format -msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively." +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:1232 +#: install-methods.xml:1273 #, no-c-format msgid "" - "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run Debian, the line in question should look like: <informalexample><screen>\n" + "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" "bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120\n" "</screen></informalexample> Now, you must create an <filename>/etc/bootptab</filename> file. This has the same sort of familiar and cryptic format as the good old BSD <filename>printcap</filename>, <filename>termcap</filename>, and <filename>disktab</filename> files. See the <filename>bootptab</filename> manual page for more information. For CMU <command>bootpd</command>, you will need to know the hardware (MAC) address of the client. Here is an example <filename>/etc/bootptab</filename>: <informalexample><screen>\n" "client:\\\n" @@ -973,43 +1018,43 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1265 +#: install-methods.xml:1306 #, no-c-format msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1284 +#: install-methods.xml:1325 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1285 +#: install-methods.xml:1326 #, 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:1290 +#: install-methods.xml:1331 #, 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:1299 +#: install-methods.xml:1340 #, no-c-format -msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/var/lib/tftpboot</filename>. You may have to adjust the configuration examples in this section accordingly." +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>/var/lib/tftpboot</filename>. You may have to adjust the configuration examples in this section accordingly." msgstr "" #. Tag: para -#: install-methods.xml:1309 +#: install-methods.xml:1350 #, 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:1317 +#: install-methods.xml:1358 #, 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" @@ -1020,49 +1065,49 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1339 +#: install-methods.xml:1380 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1340 +#: install-methods.xml:1381 #, 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:1349 +#: install-methods.xml:1390 #, 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:1380 +#: install-methods.xml:1421 #, no-c-format msgid "boot.msg" msgstr "" #. Tag: para -#: install-methods.xml:1385 +#: install-methods.xml:1426 #, 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:1393 +#: install-methods.xml:1434 #, 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:1405 +#: install-methods.xml:1446 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1406 +#: install-methods.xml:1447 #, 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" @@ -1071,55 +1116,55 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1422 +#: install-methods.xml:1463 #, 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:1429 +#: install-methods.xml:1470 #, 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:1440 +#: install-methods.xml:1481 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1441 +#: install-methods.xml:1482 #, 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:1549 +#: install-methods.xml:1590 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1550 +#: install-methods.xml:1591 #, no-c-format -msgid "For installing on multiple computers it's possible to do fully automatic installations. Debian packages intended for this include <classname>fai</classname> (which uses an install server), <classname>replicator</classname>, <classname>systemimager</classname>, <classname>autoinstall</classname>, and the Debian Installer itself." +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:1563 +#: install-methods.xml:1603 #, no-c-format msgid "Automatic Installation Using the Debian Installer" msgstr "" #. Tag: para -#: install-methods.xml:1564 +#: install-methods.xml:1604 #, 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:1571 +#: install-methods.xml:1611 #, no-c-format msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>." msgstr "" diff --git a/po/pot/installation-howto.pot b/po/pot/installation-howto.pot index 219f609f6..8237d0e19 100644 --- a/po/pot/installation-howto.pot +++ b/po/pot/installation-howto.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: 2008-09-28 00:09+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+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" @@ -23,7 +23,7 @@ msgstr "" #. Tag: para #: installation-howto.xml:7 #, no-c-format -msgid "This document describes how to install &debian; &releasename; for the &arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a quick walkthrough of the installation process which should contain all the information you will need for most installs. When more information can be useful, we will link to more detailed explanations in other parts of this document." +msgid "This document describes how to install &debian-gnu; &releasename; for the &arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a quick walkthrough of the installation process which should contain all the information you will need for most installs. When more information can be useful, we will link to more detailed explanations in other parts of this document." msgstr "" #. Tag: title @@ -77,7 +77,7 @@ msgstr "" #. Tag: para #: installation-howto.xml:78 #, no-c-format -msgid "Download whichever type you prefer and burn it to a CD. <phrase arch=\"x86\">To boot the CD, you may need to change your BIOS configuration, as explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </phrase>" +msgid "Download whichever type you prefer and burn it to a CD. <phrase arch=\"any-x86\">To boot the CD, you may need to change your BIOS configuration, as explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </phrase>" msgstr "" #. Tag: title @@ -263,7 +263,7 @@ msgstr "" #. Tag: para #: installation-howto.xml:300 #, no-c-format -msgid "The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. <phrase arch=\"x86\">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase>" +msgid "The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. <phrase arch=\"any-x86\">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase>" msgstr "" #. Tag: para diff --git a/po/pot/partitioning.pot b/po/pot/partitioning.pot index 837b4fa42..4111fd83c 100644 --- a/po/pot/partitioning.pot +++ b/po/pot/partitioning.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2009-11-02 22:19+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+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" @@ -59,7 +59,7 @@ msgstr "" #. Tag: para #: partitioning.xml:68 #, no-c-format -msgid "&debian; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> for directory and file naming. This standard allows users and software programs to predict the location of files and directories. The root level directory is represented simply by the slash <filename>/</filename>. At the root level, all Debian systems include these directories:" +msgid "&debian-gnu; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> for directory and file naming. This standard allows users and software programs to predict the location of files and directories. The root level directory is represented simply by the slash <filename>/</filename>. At the root level, all Debian systems include these directories:" msgstr "" #. Tag: entry @@ -497,7 +497,7 @@ msgstr "" #. Tag: para #: partitioning.xml:449 #, no-c-format -msgid "Recommended partitioning tool in Debian. This Swiss army knife can also resize partitions, create filesystems <phrase arch=\"x86\"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints." +msgid "Recommended partitioning tool in Debian. This Swiss army knife can also resize partitions, create filesystems <phrase arch=\"any-x86\"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints." msgstr "" #. Tag: command @@ -647,7 +647,7 @@ msgstr "" #. Tag: para #: partitioning.xml:623 #, no-c-format -msgid "Linux limits the partitions per drive to 15 partitions for SCSI disks (3 usable primary partitions, 12 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions." +msgid "Linux limits the partitions per drive to 15 partitions for SCSI disks (3 usable primary partitions, 12 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian-gnu; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions." msgstr "" #. Tag: para @@ -659,7 +659,7 @@ msgstr "" #. Tag: para #: partitioning.xml:641 #, no-c-format -msgid "This restriction doesn't apply if you have a BIOS newer than around 1995–98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and Debian's alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once Linux is booted, no matter what BIOS your computer has, these restrictions no longer apply, since Linux does not use the BIOS for disk access." +msgid "This restriction doesn't apply if you have a BIOS newer than around 1995–98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and Debian's alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer has, these restrictions no longer apply, since &arch-kernel; does not use the BIOS for disk access." msgstr "" #. Tag: para @@ -671,7 +671,7 @@ msgstr "" #. Tag: para #: partitioning.xml:667 #, no-c-format -msgid "The recommended way of accomplishing this is to create a small (25–50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions." +msgid "The recommended way of accomplishing this is to create a small (25–50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the &arch-kernel; kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions." msgstr "" #. Tag: para @@ -782,7 +782,7 @@ msgstr "" #. Tag: para #: partitioning.xml:850 #, no-c-format -msgid "In order for OpenFirmware to automatically boot &debian; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts." +msgid "In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts." msgstr "" #. Tag: para diff --git a/po/pot/post-install.pot b/po/pot/post-install.pot index e35622311..bde5e6ca8 100644 --- a/po/pot/post-install.pot +++ b/po/pot/post-install.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2009-11-02 22:05+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -29,7 +29,7 @@ msgstr "" #. Tag: para #: post-install.xml:15 #, no-c-format -msgid "To shut down a running Linux system, you must not reboot with the reset switch on the front or back of your computer, or just turn off the computer. Linux should be shut down in a controlled manner, otherwise files might get lost and/or disk damage might occur. If you run a desktop environment, there is usually an option to <quote>log out</quote> available from the application menu that allows you to shutdown (or reboot) the system." +msgid "To shut down a running &debian-gnu; system, you must not reboot with the reset switch on the front or back of your computer, or just turn off the computer. &debian-gnu; should be shut down in a controlled manner, otherwise files might get lost and/or disk damage might occur. If you run a desktop environment, there is usually an option to <quote>log out</quote> available from the application menu that allows you to shutdown (or reboot) the system." msgstr "" #. Tag: para @@ -197,7 +197,7 @@ msgstr "" #. Tag: para #: post-install.xml:290 #, no-c-format -msgid "Even if you are planning to use a graphical mail program, it is important that a traditional MTA/MDA is also installed and correctly set up on your Linux system. Reason is that various utilities running on the system<footnote> <para> Examples are: <command>cron</command>, <command>quota</command>, <command>logcheck</command>, <command>aide</command>, … </para> </footnote> can send important notices by e-mail to inform the system administrator of (potential) problems or changes." +msgid "Even if you are planning to use a graphical mail program, it is important that a traditional MTA/MDA is also installed and correctly set up on your &debian-gnu; system. Reason is that various utilities running on the system<footnote> <para> Examples are: <command>cron</command>, <command>quota</command>, <command>logcheck</command>, <command>aide</command>, … </para> </footnote> can send important notices by e-mail to inform the system administrator of (potential) problems or changes." msgstr "" #. Tag: para @@ -467,7 +467,7 @@ msgstr "" #. Tag: para #: post-install.xml:635 #, no-c-format -msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <userinput>dpkg -i ../linux-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, you'll need to install that package as well." +msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <userinput>dpkg -i ../&kernelpackage;-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, you'll need to install that package as well." msgstr "" #. Tag: para @@ -509,7 +509,7 @@ msgstr "" #. Tag: para #: post-install.xml:710 #, no-c-format -msgid "If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. <phrase arch=\"x86\"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. </phrase>" +msgid "If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. <phrase arch=\"any-x86\"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. </phrase>" msgstr "" #. Tag: para diff --git a/po/pot/preface.pot b/po/pot/preface.pot index b0758f529..7b80e7970 100644 --- a/po/pot/preface.pot +++ b/po/pot/preface.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-07-25 21:39+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+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" @@ -17,13 +17,13 @@ msgstr "" #. Tag: title #: preface.xml:5 #, no-c-format -msgid "Installing &debian; &release; For &architecture;" +msgid "Installing &debian-gnu; &release; For &architecture;" msgstr "" #. Tag: para #: preface.xml:6 #, no-c-format -msgid "We are delighted that you have decided to try Debian, and are sure that you will find that Debian's GNU/&arch-kernel; distribution is unique. &debian; brings together high-quality free software from around the world, integrating it into a coherent whole. We believe that you will find that the result is truly more than the sum of the parts." +msgid "We are delighted that you have decided to try Debian, and are sure that you will find that Debian's GNU/&arch-kernel; distribution is unique. &debian-gnu; brings together high-quality free software from around the world, integrating it into a coherent whole. We believe that you will find that the result is truly more than the sum of the parts." msgstr "" #. Tag: para diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot index 6375256f4..beb94e753 100644 --- a/po/pot/preparing.pot +++ b/po/pot/preparing.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2009-11-02 22:19+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+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" @@ -17,7 +17,7 @@ msgstr "" #. Tag: title #: preparing.xml:5 #, no-c-format -msgid "Before Installing &debian;" +msgid "Before Installing &debian-gnu;" msgstr "" #. Tag: para @@ -47,7 +47,7 @@ msgstr "" #. Tag: para #: preparing.xml:35 #, no-c-format -msgid "Under &debian;, it is much more likely that your OS can be repaired rather than replaced if things go wrong. Upgrades never require a wholesale installation; you can always upgrade in-place. And the programs are almost always compatible with successive OS releases. If a new program version requires newer supporting software, the Debian packaging system ensures that all the necessary software is automatically identified and installed. The point is, much effort has been put into avoiding the need for re-installation, so think of it as your very last option. The installer is <emphasis>not</emphasis> designed to re-install over an existing system." +msgid "Under &debian-gnu;, it is much more likely that your OS can be repaired rather than replaced if things go wrong. Upgrades never require a wholesale installation; you can always upgrade in-place. And the programs are almost always compatible with successive OS releases. If a new program version requires newer supporting software, the Debian packaging system ensures that all the necessary software is automatically identified and installed. The point is, much effort has been put into avoiding the need for re-installation, so think of it as your very last option. The installer is <emphasis>not</emphasis> designed to re-install over an existing system." msgstr "" #. Tag: para @@ -137,7 +137,7 @@ msgstr "" #. Tag: para #: preparing.xml:128 #, no-c-format -msgid "Install a <firstterm>boot loader</firstterm> which can start up &debian; and/or your existing system." +msgid "Install a <firstterm>boot loader</firstterm> which can start up &debian-gnu; and/or your existing system." msgstr "" #. Tag: para @@ -149,7 +149,7 @@ msgstr "" #. Tag: para #: preparing.xml:141 #, no-c-format -msgid "For &arch-title; you have the option of using <phrase arch=\"x86\">a</phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version of the installation system. For more information about this graphical installer, see <xref linkend=\"graphical\"/>." +msgid "For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version of the installation system. For more information about this graphical installer, see <xref linkend=\"graphical\"/>." msgstr "" #. Tag: para @@ -173,7 +173,7 @@ msgstr "" #. Tag: para #: preparing.xml:173 #, no-c-format -msgid "One important option during the installation is whether or not to install a graphical desktop environment, consisting of the X Window System and one of the available graphical desktop environments. If you choose not to select the <quote>Desktop environment</quote> task, you will only have a relatively basic, command line driven system. Installing the Desktop environment task is optional because it requires a fairly large amount of disk space, and because many &debian; systems are servers which don't really have any need for a graphical user interface to do their job." +msgid "One important option during the installation is whether or not to install a graphical desktop environment, consisting of the X Window System and one of the available graphical desktop environments. If you choose not to select the <quote>Desktop environment</quote> task, you will only have a relatively basic, command line driven system. Installing the Desktop environment task is optional because it requires a fairly large amount of disk space, and because many &debian-gnu; systems are servers which don't really have any need for a graphical user interface to do their job." msgstr "" #. Tag: para @@ -191,7 +191,7 @@ msgstr "" #. Tag: para #: preparing.xml:201 #, no-c-format -msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system has been installed on your computer, it's quite likely you will need to re-partition your disk to make room for &debian;. Anytime you partition your disk, you run a risk of losing everything on the disk, no matter what program you use to do it. The programs used in installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up, be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work." +msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system has been installed on your computer, it's quite likely you will need to re-partition your disk to make room for &debian-gnu;. Anytime you partition your disk, you run a risk of losing everything on the disk, no matter what program you use to do it. The programs used in installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up, be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work." msgstr "" #. Tag: para @@ -575,13 +575,13 @@ msgstr "" #. Tag: para #: preparing.xml:504 #, no-c-format -msgid "Many brand name products work without trouble on Linux. Moreover, hardware support in Linux is improving daily. However, Linux still does not run as many different types of hardware as some operating systems." +msgid "Many brand name products work without trouble on &arch-kernel;. Moreover, hardware support in &arch-kernel; is improving daily. However, &arch-kernel; still does not run as many different types of hardware as some operating systems." msgstr "" #. Tag: para #: preparing.xml:510 #, no-c-format -msgid "In particular, Linux usually cannot run hardware that requires a running version of Windows to work." +msgid "In particular, &arch-kernel; usually cannot run hardware that requires a running version of Windows to work." msgstr "" #. Tag: para @@ -617,7 +617,7 @@ msgstr "" #. Tag: para #: preparing.xml:544 #, no-c-format -msgid "Checking hardware compatibility lists for Linux on web sites dedicated to your architecture." +msgid "Checking hardware compatibility lists for &arch-kernel; on web sites dedicated to your architecture." msgstr "" #. Tag: para @@ -827,7 +827,7 @@ msgstr "" #. Tag: para #: preparing.xml:721 #, no-c-format -msgid "Disk space required for the smooth operation of the &debian; system itself is taken into account in these recommended system requirements. Notably, the <filename>/var</filename> partition contains a lot of state information specific to Debian in addition to its regular contents, like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 40MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 200MB for <filename>/var</filename>, and a lot more if you install a graphical desktop environment." +msgid "Disk space required for the smooth operation of the &debian-gnu; system itself is taken into account in these recommended system requirements. Notably, the <filename>/var</filename> partition contains a lot of state information specific to Debian in addition to its regular contents, like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 40MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 200MB for <filename>/var</filename>, and a lot more if you install a graphical desktop environment." msgstr "" #. Tag: title @@ -851,13 +851,13 @@ msgstr "" #. Tag: para #: preparing.xml:759 #, no-c-format -msgid "If you already have an operating system on your system <phrase arch=\"x86\"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, …) </phrase> and want to stick Linux on the same disk, you will need to repartition the disk. Debian requires its own hard disk partitions. It cannot be installed on Windows or MacOS partitions. It may be able to share some partitions with other Linux systems, but that's not covered here. At the very least you will need a dedicated partition for the Debian root." +msgid "If you already have an operating system on your system <phrase arch=\"any-x86\"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, …) </phrase> and want to stick Debian on the same disk, you will need to repartition the disk. Debian requires its own hard disk partitions. It cannot be installed on Windows or MacOS partitions. It may be able to share some partitions with other Unix systems, but that's not covered here. At the very least you will need a dedicated partition for the Debian root." msgstr "" #. Tag: para #: preparing.xml:778 #, no-c-format -msgid "You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase arch=\"x86\">, such as fdisk or PartitionMagic</phrase><phrase arch=\"powerpc\">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch=\"s390\">, such as the VM diskmap</phrase>. Partitioning tools always provide a way to show existing partitions without making changes." +msgid "You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase arch=\"any-x86\">, such as fdisk or PartitionMagic</phrase><phrase arch=\"powerpc\">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch=\"s390\">, such as the VM diskmap</phrase>. Partitioning tools always provide a way to show existing partitions without making changes." msgstr "" #. Tag: para @@ -881,7 +881,7 @@ msgstr "" #. Tag: para #: preparing.xml:806 #, no-c-format -msgid "If your machine has only one hard disk, and you would like to completely replace the current operating system with &debian;, you also can wait to partition as part of the installation process (<xref linkend=\"di-partition\"/>), after you have booted the installation system. However this only works if you plan to boot the installer system from tapes, CD-ROM or files on a connected machine. Consider: if you boot from files placed on the hard disk, and then partition that same hard disk within the installation system, thus erasing the boot files, you'd better hope the installation is successful the first time around. At the least in this case, you should have some alternate means of reviving your machine like the original system's installation tapes or CDs." +msgid "If your machine has only one hard disk, and you would like to completely replace the current operating system with &debian-gnu;, you also can wait to partition as part of the installation process (<xref linkend=\"di-partition\"/>), after you have booted the installation system. However this only works if you plan to boot the installer system from tapes, CD-ROM or files on a connected machine. Consider: if you boot from files placed on the hard disk, and then partition that same hard disk within the installation system, thus erasing the boot files, you'd better hope the installation is successful the first time around. At the least in this case, you should have some alternate means of reviving your machine like the original system's installation tapes or CDs." msgstr "" #. Tag: para @@ -899,13 +899,13 @@ msgstr "" #. Tag: para #: preparing.xml:837 #, no-c-format -msgid "If none of the above apply, you'll need to partition your hard disk before starting the installation to create partitionable space for Debian. If some of the partitions will be owned by other operating systems, you should create those partitions using native operating system partitioning programs. We recommend that you do <emphasis>not</emphasis> attempt to create partitions for &debian; using another operating system's tools. Instead, you should just create the native operating system's partitions you will want to retain." +msgid "If none of the above apply, you'll need to partition your hard disk before starting the installation to create partitionable space for Debian. If some of the partitions will be owned by other operating systems, you should create those partitions using native operating system partitioning programs. We recommend that you do <emphasis>not</emphasis> attempt to create partitions for &debian-gnu; using another operating system's tools. Instead, you should just create the native operating system's partitions you will want to retain." msgstr "" #. Tag: para #: preparing.xml:849 #, no-c-format -msgid "If you are going to install more than one operating system on the same machine, you should install all other system(s) before proceeding with Linux installation. Windows and other OS installations may destroy your ability to start Linux, or encourage you to reformat non-native partitions." +msgid "If you are going to install more than one operating system on the same machine, you should install all other system(s) before proceeding with Debian installation. Windows and other OS installations may destroy your ability to start Debian, or encourage you to reformat non-native partitions." msgstr "" #. Tag: para @@ -917,7 +917,7 @@ msgstr "" #. Tag: para #: preparing.xml:862 #, no-c-format -msgid "In order for OpenFirmware to automatically boot &debian; the Linux partitions should appear before all other partitions on the disk, especially MacOS boot partitions. This should be kept in mind when pre-partitioning; you should create a Linux placeholder partition to come <emphasis>before</emphasis> the other bootable partitions on the disk. (The small partitions dedicated to Apple disk drivers are not bootable.) You can delete the placeholder with the Linux partition tools later during the actual install, and replace it with Linux partitions." +msgid "In order for OpenFirmware to automatically boot &debian-gnu; the &arch-parttype; partitions should appear before all other partitions on the disk, especially MacOS boot partitions. This should be kept in mind when pre-partitioning; you should create a &arch-parttype; placeholder partition to come <emphasis>before</emphasis> the other bootable partitions on the disk. (The small partitions dedicated to Apple disk drivers are not bootable.) You can delete the placeholder with the Debian partition tools later during the actual install, and replace it with &arch-parttype; partitions." msgstr "" #. Tag: para @@ -941,7 +941,7 @@ msgstr "" #. Tag: para #: preparing.xml:896 #, no-c-format -msgid "Use the native partitioning tools to create native system partition(s). Leave either a place holder partition or free space for &debian;." +msgid "Use the native partitioning tools to create native system partition(s). Leave either a place holder partition or free space for &debian-gnu;." msgstr "" #. Tag: para @@ -971,7 +971,7 @@ msgstr "" #. Tag: para #: preparing.xml:929 #, no-c-format -msgid "If you are manipulating existing FAT or NTFS partitions, it is recommended that you either use the scheme below or native Windows or DOS tools. Otherwise, it is not really necessary to partition from DOS or Windows; the Linux partitioning tools will generally do a better job." +msgid "If you are manipulating existing FAT or NTFS partitions, it is recommended that you either use the scheme below or native Windows or DOS tools. Otherwise, it is not really necessary to partition from DOS or Windows; the Debian partitioning tools will generally do a better job." msgstr "" #. Tag: para @@ -1037,13 +1037,13 @@ msgstr "" #. Tag: para #: preparing.xml:1023 #, no-c-format -msgid "If you are partitioning for DOS drives, or changing the size of DOS partitions, using Linux tools, many people experience problems working with the resulting FAT partitions. For instance, some have reported slow performance, consistent problems with <command>scandisk</command>, or other weird errors in DOS or Windows." +msgid "If you are partitioning for DOS drives, or changing the size of DOS partitions, using Debian tools, many people experience problems working with the resulting FAT partitions. For instance, some have reported slow performance, consistent problems with <command>scandisk</command>, or other weird errors in DOS or Windows." msgstr "" #. Tag: para #: preparing.xml:1031 #, no-c-format -msgid "Apparently, whenever you create or resize a partition for DOS use, it's a good idea to fill the first few sectors with zeros. You should do this prior to running DOS's <command>format</command> command by executing the following command from Linux:" +msgid "Apparently, whenever you create or resize a partition for DOS use, it's a good idea to fill the first few sectors with zeros. You should do this prior to running DOS's <command>format</command> command by executing the following command from Debian:" msgstr "" #. Tag: screen @@ -1097,7 +1097,7 @@ msgstr "" #. Tag: para #: preparing.xml:1101 #, no-c-format -msgid "Remember to create a placeholder partition for GNU/Linux, preferably positioned first in the disk layout. it doesn't matter what type it is, it will be deleted and replaced later inside the &debian; installer." +msgid "Remember to create a placeholder partition for GNU/Linux, preferably positioned first in the disk layout. it doesn't matter what type it is, it will be deleted and replaced later inside the &debian-gnu; installer." msgstr "" #. Tag: para @@ -1121,7 +1121,7 @@ msgstr "" #. Tag: para #: preparing.xml:1141 #, no-c-format -msgid "This section will walk you through pre-installation hardware setup, if any, that you will need to do prior to installing Debian. Generally, this involves checking and possibly changing firmware settings for your system. The <quote>firmware</quote> is the core software used by the hardware; it is most critically invoked during the bootstrap process (after power-up). Known hardware issues affecting the reliability of &debian; on your system are also highlighted." +msgid "This section will walk you through pre-installation hardware setup, if any, that you will need to do prior to installing Debian. Generally, this involves checking and possibly changing firmware settings for your system. The <quote>firmware</quote> is the core software used by the hardware; it is most critically invoked during the bootstrap process (after power-up). Known hardware issues affecting the reliability of &debian-gnu; on your system are also highlighted." msgstr "" #. Tag: title @@ -1241,7 +1241,7 @@ msgstr "" #. Tag: para #: preparing.xml:1291 #, no-c-format -msgid "Here are some details about how to set the boot order. Remember to reset the boot order after Linux is installed, so that you restart your machine from the hard drive." +msgid "Here are some details about how to set the boot order. Remember to reset the boot order after &arch-kernel; is installed, so that you restart your machine from the hard drive." msgstr "" #. Tag: title @@ -1355,7 +1355,7 @@ msgstr "" #. Tag: para #: preparing.xml:1406 #, no-c-format -msgid "If your system provides both ex<emphasis>ten</emphasis>ded and ex<emphasis>pan</emphasis>ded memory, set it so that there is as much extended and as little expanded memory as possible. Linux requires extended memory and cannot use expanded memory." +msgid "If your system provides both ex<emphasis>ten</emphasis>ded and ex<emphasis>pan</emphasis>ded memory, set it so that there is as much extended and as little expanded memory as possible. &arch-kernel; requires extended memory and cannot use expanded memory." msgstr "" #. Tag: title @@ -1367,7 +1367,7 @@ msgstr "" #. Tag: para #: preparing.xml:1417 #, no-c-format -msgid "Disable any virus-warning features your BIOS may provide. If you have a virus-protection board or other special hardware, make sure it is disabled or physically removed while running GNU/Linux. These aren't compatible with GNU/Linux; moreover, due to the file system permissions and protected memory of the Linux kernel, viruses are almost unheard of<footnote> <para> After installation you can enable Boot Sector protection if you want. This offers no additional security in Linux but if you also run Windows it may prevent a catastrophe. There is no need to tamper with the Master Boot Record (MBR) after the boot manager has been set up. </para> </footnote>." +msgid "Disable any virus-warning features your BIOS may provide. If you have a virus-protection board or other special hardware, make sure it is disabled or physically removed while running GNU/&arch-kernel;. These aren't compatible with GNU/&arch-kernel;; moreover, due to the file system permissions and protected memory of the &arch-kernel; kernel, viruses are almost unheard of<footnote> <para> After installation you can enable Boot Sector protection if you want. This offers no additional security in &arch-kernel; but if you also run Windows it may prevent a catastrophe. There is no need to tamper with the Master Boot Record (MBR) after the boot manager has been set up. </para> </footnote>." msgstr "" #. Tag: title @@ -1379,7 +1379,7 @@ msgstr "" #. Tag: para #: preparing.xml:1439 #, no-c-format -msgid "Your motherboard may provide <emphasis>shadow RAM</emphasis> or BIOS caching. You may see settings for <quote>Video BIOS Shadow</quote>, <quote>C800-CBFF Shadow</quote>, etc. <emphasis>Disable</emphasis> all shadow RAM. Shadow RAM is used to accelerate access to the ROMs on your motherboard and on some of the controller cards. Linux does not use these ROMs once it has booted because it provides its own faster 32-bit software in place of the 16-bit programs in the ROMs. Disabling the shadow RAM may make some of it available for programs to use as normal memory. Leaving the shadow RAM enabled may interfere with Linux access to hardware devices." +msgid "Your motherboard may provide <emphasis>shadow RAM</emphasis> or BIOS caching. You may see settings for <quote>Video BIOS Shadow</quote>, <quote>C800-CBFF Shadow</quote>, etc. <emphasis>Disable</emphasis> all shadow RAM. Shadow RAM is used to accelerate access to the ROMs on your motherboard and on some of the controller cards. &arch-kernel; does not use these ROMs once it has booted because it provides its own faster 32-bit software in place of the 16-bit programs in the ROMs. Disabling the shadow RAM may make some of it available for programs to use as normal memory. Leaving the shadow RAM enabled may interfere with &arch-kernel; access to hardware devices." msgstr "" #. Tag: title @@ -1391,7 +1391,7 @@ msgstr "" #. Tag: para #: preparing.xml:1457 #, no-c-format -msgid "If your BIOS offers something like <quote>15–16 MB Memory Hole</quote>, please disable that. Linux expects to find memory there if you have that much RAM." +msgid "If your BIOS offers something like <quote>15–16 MB Memory Hole</quote>, please disable that. &arch-kernel; expects to find memory there if you have that much RAM." msgstr "" #. Tag: para @@ -1409,7 +1409,7 @@ msgstr "" #. Tag: para #: preparing.xml:1480 #, no-c-format -msgid "If your motherboard provides Advanced Power Management (APM), configure it so that power management is controlled by APM. Disable the doze, standby, suspend, nap, and sleep modes, and disable the hard disk's power-down timer. Linux can take over control of these modes, and can do a better job of power-management than the BIOS." +msgid "If your motherboard provides Advanced Power Management (APM), configure it so that power management is controlled by APM. Disable the doze, standby, suspend, nap, and sleep modes, and disable the hard disk's power-down timer. &arch-kernel; can take over control of these modes, and can do a better job of power-management than the BIOS." msgstr "" #. Tag: title @@ -1511,7 +1511,7 @@ msgstr "" #. Tag: para #: preparing.xml:1646 #, no-c-format -msgid "In order to install &debian; on a &arch-title; or zSeries machine you have first boot a kernel into the system. The boot mechanism of this platform is inherently different to other ones, especially from PC-like systems: there are no floppy devices available at all. You will notice another big difference while you work with this platform: most (if not all) of the time you will work remote, with the help of some client session software like telnet, or a browser. This is due to that special system architecture where the 3215/3270 console is line-based instead of character-based." +msgid "In order to install &debian-gnu; on a &arch-title; or zSeries machine you have first boot a kernel into the system. The boot mechanism of this platform is inherently different to other ones, especially from PC-like systems: there are no floppy devices available at all. You will notice another big difference while you work with this platform: most (if not all) of the time you will work remote, with the help of some client session software like telnet, or a browser. This is due to that special system architecture where the 3215/3270 console is line-based instead of character-based." msgstr "" #. Tag: para @@ -1571,7 +1571,7 @@ msgstr "" #. Tag: para #: preparing.xml:1734 #, no-c-format -msgid "The installation server needs to copy the exact directory structure from any &debian; mirror, but only the s390 and architecture-independent files are required. You can also copy the contents of all installation CDs into such a directory tree." +msgid "The installation server needs to copy the exact directory structure from any &debian-gnu; mirror, but only the s390 and architecture-independent files are required. You can also copy the contents of all installation CDs into such a directory tree." msgstr "" #. Tag: emphasis diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot index 7c4cef180..d82ff75e4 100644 --- a/po/pot/preseed.pot +++ b/po/pot/preseed.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: 2010-03-28 00:13+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+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" @@ -27,7 +27,7 @@ msgid "This appendix explains how to preseed answers to questions in &d-i; to au msgstr "" #. Tag: para -#: preseed.xml:23 preseed.xml:669 +#: preseed.xml:23 preseed.xml:676 #, no-c-format msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;." msgstr "" @@ -81,7 +81,7 @@ msgid "initrd" msgstr "" #. Tag: entry -#: preseed.xml:70 preseed.xml:516 +#: preseed.xml:70 preseed.xml:523 #, no-c-format msgid "file" msgstr "" @@ -209,23 +209,23 @@ msgstr "" #. Tag: para #: preseed.xml:252 #, no-c-format -msgid "For the other preseeding methods you need to tell the installer what file to use when you boot it. This is normally done by passing the kernel a boot parameter, either manually at boot time or by editing the bootloader configuration file (e.g. <filename>syslinux.cfg</filename>) and adding the parameter to the end of the append line(s) for the kernel." +msgid "For the other preseeding methods you need to tell the installer what file to use when you boot it. This is normally done by passing the kernel a boot parameter, either manually at boot time or by editing the bootloader configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</filename>) and adding the parameter to the end of the append line(s) for the kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter as a new <literal>set</literal> line for the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</filename>) and adding the parameter to the end of the <filename>gnumach.gz</filename> line.</phrase>" msgstr "" #. Tag: para -#: preseed.xml:260 +#: preseed.xml:265 #, no-c-format -msgid "If you do specify the preconfiguration file in the bootloader configuration, you might change the configuration so you don't need to hit enter to boot the installer. For syslinux this means setting the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>." +msgid "If you do specify the preconfiguration file in the bootloader configuration, you might change the configuration so you don't need to hit enter to boot the installer. <phrase arch=\"linux-any\">For syslinux this means setting the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>" msgstr "" #. Tag: para -#: preseed.xml:267 +#: preseed.xml:274 #, no-c-format msgid "To make sure the installer gets the right preconfiguration file, you can optionally specify a checksum for the file. Currently this needs to be a md5sum, and if specified it must match the preconfiguration file or the installer will refuse to use it." msgstr "" #. Tag: screen -#: preseed.xml:276 +#: preseed.xml:283 #, no-c-format msgid "" "Boot parameters to specify:\n" @@ -244,79 +244,79 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:278 +#: preseed.xml:285 #, no-c-format msgid "Note that <filename>preseed/url</filename> can be shortened to just <filename>url</filename> and <filename>preseed/file</filename> to just <filename>file</filename> when they are passed as boot parameters." msgstr "" #. Tag: title -#: preseed.xml:288 +#: preseed.xml:295 #, no-c-format msgid "Using boot parameters to preseed questions" msgstr "" #. Tag: para -#: preseed.xml:289 +#: preseed.xml:296 #, no-c-format msgid "If a preconfiguration file cannot be used to preseed some steps, the install can still be fully automated, since you can pass preseed values on the command line when booting the installer." msgstr "" #. Tag: para -#: preseed.xml:295 +#: preseed.xml:302 #, no-c-format msgid "Boot parameters can also be used if you do not really want to use preseeding, but just want to provide an answer for a specific question. Some examples where this can be useful are documented elsewhere in this manual." msgstr "" #. Tag: para -#: preseed.xml:301 +#: preseed.xml:308 #, no-c-format msgid "To set a value to be used inside &d-i;, just pass <userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput> for any of the preseed variables listed in the examples in this appendix. If a value is to be used to configure packages for the target system, you will need to prepend the <firstterm>owner</firstterm><footnote> <para> The owner of a debconf variable (or template) is normally the name of the package that contains the corresponding debconf template. For variables used in the installer itself the owner is <quote>d-i</quote>. Templates and variables can have more than one owner which helps to determine whether they can be removed from the debconf database if the package is purged. </para> </footnote> of the variable as in <userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>. If you don't specify the owner, the value for the variable will not be copied to the debconf database in the target system and thus remain unused during the configuration of the relevant package." msgstr "" #. Tag: para -#: preseed.xml:324 +#: preseed.xml:331 #, no-c-format msgid "Normally, preseeding a question in this way will mean that the question will not be asked. To set a specific default value for a question, but still have the question asked, use <quote>?=</quote> instead of <quote>=</quote> as operator. See also <xref linkend=\"preseed-seenflag\"/>." msgstr "" #. Tag: para -#: preseed.xml:331 +#: preseed.xml:338 #, no-c-format msgid "Note that some variables that are frequently set at the boot prompt have a shorter alias. If an alias is available, it is used in the examples in this appendix instead of the full variable. The <literal>preseed/url</literal> variable for example has been aliased as <literal>url</literal>. Another example is the <literal>tasks</literal> alias, which translates to <literal>tasksel:tasksel/first</literal>." msgstr "" #. Tag: para -#: preseed.xml:340 +#: preseed.xml:347 #, no-c-format msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after the last <quote>--</quote> may be copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader). The installer will automatically filter out any options (like preconfiguration options) that it recognizes." msgstr "" #. Tag: para -#: preseed.xml:349 +#: preseed.xml:356 #, no-c-format msgid "Current linux kernels (2.6.9 and later) accept a maximum of 32 command line options and 32 environment options, including any options added by default for the installer. If these numbers are exceeded, the kernel will panic (crash). (For earlier kernels, these numbers were lower.)" msgstr "" #. Tag: para -#: preseed.xml:357 +#: preseed.xml:364 #, no-c-format msgid "For most installations some of the default options in your bootloader configuration file, like <literal>vga=normal</literal>, may be safely removed which may allow you to add more options for preseeding." msgstr "" #. Tag: para -#: preseed.xml:364 +#: preseed.xml:371 #, no-c-format msgid "It may not always be possible to specify values with spaces for boot parameters, even if you delimit them with quotes." msgstr "" #. Tag: title -#: preseed.xml:373 +#: preseed.xml:380 #, no-c-format msgid "Auto mode" msgstr "" #. Tag: para -#: preseed.xml:374 +#: preseed.xml:381 #, no-c-format msgid "" "There are several features of Debian Installer that combine to allow fairly simple command lines at the boot prompt to result in arbitrarily complex customized automatic installs. To illustrate this, here are some examples that can be used at the boot prompt: <informalexample><screen>\n" @@ -325,13 +325,13 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:391 +#: preseed.xml:398 #, no-c-format msgid "The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</literal>) is taken from <literal>auto-install/defaultroot</literal>. By default this includes the directory <literal>&releasename;</literal> to allow future versions to specify their own codename and let people migrate forwards in a controlled manner. The <literal>/./</literal> bit is used to indicate a root, relative to which subsequent paths can be anchored (for use in preseed/include and preseed/run). This allows files to be specified either as full URLs, paths starting with / that are thus anchored, or even paths relative to the location where the last preseed file was found. This can be used to construct more portable scripts where an entire hierarchy of scripts can be moved to a new location without breaking it, for example copying the files onto a USB stick when they started out on a web server. In this example, if the preseed file sets <literal>preseed/run</literal> to <literal>/scripts/late_command.sh</literal> then the file will be fetched from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/late_command.sh</literal>." msgstr "" #. Tag: para -#: preseed.xml:411 +#: preseed.xml:418 #, no-c-format msgid "" "If there is no local DHCP or DNS infrastructure, or if you do not want to use the default path to <filename>preseed.cfg</filename>, you can still use an explicit url, and if you don't use the <literal>/./</literal> element it will be anchored to the start of the path (i.e. the third <literal>/</literal> in the URL). Here is an example that requires minimal support from the local network infrastructure: <informalexample><screen>\n" @@ -340,25 +340,25 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:424 +#: preseed.xml:431 #, no-c-format msgid "if the URL is missing a protocol, http is assumed," msgstr "" #. Tag: para -#: preseed.xml:427 +#: preseed.xml:434 #, no-c-format msgid "if the hostname section contains no periods, it has the domain derived from DHCP appended to it, and" msgstr "" #. Tag: para -#: preseed.xml:431 +#: preseed.xml:438 #, no-c-format msgid "if there's no <literal>/</literal>'s after the hostname, then the default path is added." msgstr "" #. Tag: para -#: preseed.xml:437 +#: preseed.xml:444 #, no-c-format msgid "" "In addition to specifying the url, you can also specify settings that do not directly affect the behavior of &d-i; itself, but can be passed through to scripts specified using <literal>preseed/run</literal> in the loaded preseed file. At present, the only example of this is <literal>auto-install/classes</literal>, which has an alias <literal>classes</literal>. This can be used thus: <informalexample><screen>\n" @@ -367,217 +367,217 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:451 +#: preseed.xml:458 #, no-c-format msgid "It is of course possible to extend this concept, and if you do, it is reasonable to use the auto-install namespace for this. So one might have something like <literal>auto-install/style</literal> which is then used in your scripts. If you feel the need to do this, please mention it on the <email>debian-boot@lists.debian.org</email> mailing list so that we can avoid namespace conflicts, and perhaps add an alias for the parameter for you." msgstr "" #. Tag: para -#: preseed.xml:461 +#: preseed.xml:468 #, no-c-format msgid "The <literal>auto</literal> boot label is not yet defined everywhere. The same effect may be achieved by simply adding the two parameters <literal>auto=true priority=critical</literal> to the kernel command line. The <literal>auto</literal> parameter is an alias for <literal>auto-install/enable</literal> and setting it to <literal>true</literal> delays the locale and keyboard questions until after there has been a chance to preseed them, while <literal>priority</literal> is an alias for <literal>debconf/priority</literal> and setting it to <literal>critical</literal> stops any questions with a lower priority from being asked." msgstr "" #. Tag: para -#: preseed.xml:475 +#: preseed.xml:482 #, no-c-format msgid "Additional options that may be of interest while attempting to automate an install while using DHCP are: <literal>interface=auto netcfg/dhcp_timeout=60</literal> which makes the machine choose the first viable NIC and be more patient about getting a reply to its DHCP query." msgstr "" #. Tag: para -#: preseed.xml:484 +#: preseed.xml:491 #, no-c-format msgid "An extensive example of how to use this framework, including example scripts and classes, can be found on the <ulink url=\"http://hands.com/d-i/\">website of its developer</ulink>. The examples available there also show many other nice effects that can be achieved by creative use of preconfiguration." msgstr "" #. Tag: title -#: preseed.xml:495 +#: preseed.xml:502 #, no-c-format msgid "Aliases useful with preseeding" msgstr "" #. Tag: para -#: preseed.xml:496 +#: preseed.xml:503 #, no-c-format msgid "The following aliases can be useful when using (auto mode) preseeding. Note that these are simply short aliases for question names, and you always need to specify a value as well: for example, <literal>auto=true</literal> or <literal>interface=eth0</literal>." msgstr "" #. Tag: entry -#: preseed.xml:509 +#: preseed.xml:516 #, no-c-format msgid "auto" msgstr "" #. Tag: entry -#: preseed.xml:509 +#: preseed.xml:516 #, no-c-format msgid "auto-install/enable" msgstr "" #. Tag: entry -#: preseed.xml:510 +#: preseed.xml:517 #, no-c-format msgid "classes" msgstr "" #. Tag: entry -#: preseed.xml:510 +#: preseed.xml:517 #, no-c-format msgid "auto-install/classes" msgstr "" #. Tag: entry -#: preseed.xml:511 +#: preseed.xml:518 #, no-c-format msgid "<entry>fb</entry>" msgstr "" #. Tag: entry -#: preseed.xml:511 +#: preseed.xml:518 #, no-c-format msgid "debian-installer/framebuffer" msgstr "" #. Tag: entry -#: preseed.xml:512 +#: preseed.xml:519 #, no-c-format msgid "language" msgstr "" #. Tag: entry -#: preseed.xml:512 +#: preseed.xml:519 #, no-c-format msgid "debian-installer/language" msgstr "" #. Tag: entry -#: preseed.xml:513 +#: preseed.xml:520 #, no-c-format msgid "country" msgstr "" #. Tag: entry -#: preseed.xml:513 +#: preseed.xml:520 #, no-c-format msgid "debian-installer/country" msgstr "" #. Tag: entry -#: preseed.xml:514 +#: preseed.xml:521 #, no-c-format msgid "locale" msgstr "" #. Tag: entry -#: preseed.xml:514 +#: preseed.xml:521 #, no-c-format msgid "debian-installer/locale" msgstr "" #. Tag: entry -#: preseed.xml:515 +#: preseed.xml:522 #, no-c-format msgid "priority" msgstr "" #. Tag: entry -#: preseed.xml:515 +#: preseed.xml:522 #, no-c-format msgid "debconf/priority" msgstr "" #. Tag: entry -#: preseed.xml:516 +#: preseed.xml:523 #, no-c-format msgid "preseed/file" msgstr "" #. Tag: entry -#: preseed.xml:517 +#: preseed.xml:524 #, no-c-format msgid "<entry>url</entry>" msgstr "" #. Tag: entry -#: preseed.xml:517 +#: preseed.xml:524 #, no-c-format msgid "preseed/url" msgstr "" #. Tag: entry -#: preseed.xml:518 +#: preseed.xml:525 #, no-c-format msgid "interface" msgstr "" #. Tag: entry -#: preseed.xml:518 +#: preseed.xml:525 #, no-c-format msgid "netcfg/choose_interface" msgstr "" #. Tag: entry -#: preseed.xml:519 +#: preseed.xml:526 #, no-c-format msgid "hostname " msgstr "" #. Tag: entry -#: preseed.xml:519 +#: preseed.xml:526 #, no-c-format msgid "netcfg/get_hostname" msgstr "" #. Tag: entry -#: preseed.xml:520 +#: preseed.xml:527 #, no-c-format msgid "domain" msgstr "" #. Tag: entry -#: preseed.xml:520 +#: preseed.xml:527 #, no-c-format msgid "netcfg/get_domain" msgstr "" #. Tag: entry -#: preseed.xml:521 +#: preseed.xml:528 #, no-c-format msgid "protocol" msgstr "" #. Tag: entry -#: preseed.xml:521 +#: preseed.xml:528 #, no-c-format msgid "mirror/protocol" msgstr "" #. Tag: entry -#: preseed.xml:522 +#: preseed.xml:529 #, no-c-format msgid "suite" msgstr "" #. Tag: entry -#: preseed.xml:522 +#: preseed.xml:529 #, no-c-format msgid "mirror/suite" msgstr "" #. Tag: title -#: preseed.xml:529 +#: preseed.xml:536 #, no-c-format msgid "Using a DHCP server to specify preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:530 +#: preseed.xml:537 #, no-c-format msgid "It's also possible to use DHCP to specify a preconfiguration file to download from the network. DHCP allows specifying a filename. Normally this is a file to netboot, but if it appears to be an URL then installation media that support network preseeding will download the file from the URL and use it as a preconfiguration file. Here is an example of how to set it up in the dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server Debian package)." msgstr "" #. Tag: screen -#: preseed.xml:541 +#: preseed.xml:548 #, no-c-format msgid "" "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n" @@ -586,85 +586,85 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:543 +#: preseed.xml:550 #, no-c-format msgid "Note that the above example limits this filename to DHCP clients that identify themselves as \"d-i\", so it will not affect regular DHCP clients, but only the installer. You can also put the text in a stanza for only one particular host to avoid preseeding all installs on your network." msgstr "" #. Tag: para -#: preseed.xml:550 +#: preseed.xml:557 #, no-c-format msgid "A good way to use the DHCP preseeding is to only preseed values specific to your network, such as the Debian mirror to use. This way installs on your network will automatically get a good mirror selected, but the rest of the installation can be performed interactively. Using DHCP preseeding to fully automate Debian installs should only be done with care." msgstr "" #. Tag: title -#: preseed.xml:564 +#: preseed.xml:571 #, no-c-format msgid "Creating a preconfiguration file" msgstr "" #. Tag: para -#: preseed.xml:565 +#: preseed.xml:572 #, no-c-format msgid "The preconfiguration file is in the format used by the <command>debconf-set-selections</command> command. The general format of a line in a preconfiguration file is:" msgstr "" #. Tag: screen -#: preseed.xml:571 +#: preseed.xml:578 #, no-c-format msgid "<owner> <question name> <question type> <value>" msgstr "" #. Tag: para -#: preseed.xml:573 +#: preseed.xml:580 #, no-c-format msgid "There are a few rules to keep in mind when writing a preconfiguration file." msgstr "" #. Tag: para -#: preseed.xml:580 +#: preseed.xml:587 #, no-c-format msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value." msgstr "" #. Tag: para -#: preseed.xml:584 +#: preseed.xml:591 #, no-c-format msgid "A line can be split into multiple lines by appending a backslash (<quote><literal>\\</literal></quote>) as the line continuation character. A good place to split a line is after the question name; a bad place is between type and value. Split lines will be joined into a single line with all leading/trailing whitespace condensed to a single space." msgstr "" #. Tag: para -#: preseed.xml:591 +#: preseed.xml:598 #, no-c-format msgid "For debconf variables (templates) used in the installer itself, the owner should be set to <quote>d-i</quote>; to preseed variables used in the installed system, the name of the package that contains the corresponding debconf template should be used. Only variables that have their owner set to something other than <quote>d-i</quote> will be propagated to the debconf database for the installed system." msgstr "" #. Tag: para -#: preseed.xml:599 +#: preseed.xml:606 #, no-c-format msgid "Most questions need to be preseeded using the values valid in English and not the translated values. However, there are some questions (for example in <classname>partman</classname>) where the translated values need to be used." msgstr "" #. Tag: para -#: preseed.xml:605 +#: preseed.xml:612 #, no-c-format msgid "Some questions take a code as value instead of the English text that is shown during installation." msgstr "" #. Tag: para -#: preseed.xml:611 +#: preseed.xml:618 #, no-c-format msgid "The easiest way to create a preconfiguration file is to use the example file linked in <xref linkend=\"preseed-contents\"/> as basis and work from there." msgstr "" #. Tag: para -#: preseed.xml:616 +#: preseed.xml:623 #, no-c-format msgid "An alternative method is to do a manual installation and then, after rebooting, use the <command>debconf-get-selections</command> from the <classname>debconf-utils</classname> package to dump both the debconf database and the installer's cdebconf database to a single file:" msgstr "" #. Tag: screen -#: preseed.xml:623 +#: preseed.xml:630 #, no-c-format msgid "" "$ debconf-get-selections --installer > <replaceable>file</replaceable>\n" @@ -672,73 +672,73 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:625 +#: preseed.xml:632 #, no-c-format msgid "However, a file generated in this manner will have some items that should not be preseeded, and the example file is a better starting place for most users." msgstr "" #. Tag: para -#: preseed.xml:633 +#: preseed.xml:640 #, no-c-format msgid "This method relies on the fact that, at the end of the installation, the installer's cdebconf database is saved to the installed system in <filename>/var/log/installer/cdebconf</filename>. However, because the database may contain sensitive information, by default the files are only readable by root." msgstr "" #. Tag: para -#: preseed.xml:641 +#: preseed.xml:648 #, no-c-format msgid "The directory <filename>/var/log/installer</filename> and all files in it will be deleted from your system if you purge the package <classname>installation-report</classname>." msgstr "" #. Tag: para -#: preseed.xml:649 +#: preseed.xml:656 #, no-c-format msgid "To check possible values for questions, you can use <command>nano</command> to examine the files in <filename>/var/lib/cdebconf</filename> while an installation is in progress. View <filename>templates.dat</filename> for the raw templates and <filename>questions.dat</filename> for the current values and for the values assigned to variables." msgstr "" #. Tag: para -#: preseed.xml:657 +#: preseed.xml:664 #, no-c-format msgid "To check if the format of your preconfiguration file is valid before performing an install, you can use the command <command>debconf-set-selections -c <replaceable>preseed.cfg</replaceable></command>." msgstr "" #. Tag: title -#: preseed.xml:668 +#: preseed.xml:675 #, no-c-format msgid "Contents of the preconfiguration file (for &releasename;)" msgstr "" #. Tag: para -#: preseed.xml:674 +#: preseed.xml:681 #, no-c-format msgid "Note that this example is based on an installation for the Intel x86 architecture. If you are installing a different architecture, some of the examples (like keyboard selection and bootloader installation) may not be relevant and will need to be replaced by debconf settings appropriate for your architecture." msgstr "" #. Tag: title -#: preseed.xml:685 +#: preseed.xml:692 #, no-c-format msgid "Localization" msgstr "" #. Tag: para -#: preseed.xml:686 +#: preseed.xml:693 #, no-c-format msgid "Setting localization values will only work if you are using initrd preseeding. With all other methods the preconfiguration file will only be loaded after these questions have been asked." msgstr "" #. Tag: para -#: preseed.xml:692 +#: preseed.xml:699 #, no-c-format msgid "The locale can be used to specify both language and country and can be any combination of a language supported by &d-i; and a recognized country. If the combination does not form a valid locale, the installer will automatically select a locale that is valid for the selected language. To specify the locale as a boot parameter, use <userinput>locale=<replaceable>en_US</replaceable></userinput>." msgstr "" #. Tag: para -#: preseed.xml:701 +#: preseed.xml:708 #, no-c-format msgid "Although this method is very easy to use, it does not allow preseeding of all possible combinations of language, country and locale<footnote> <para> Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would for example result in <literal>en_US.UTF-8</literal> as default locale for the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred instead, the values will need to be preseeded individually. </para> </footnote>. So alternatively the values can be preseeded individually. Language and country can also be specified as boot parameters." msgstr "" #. Tag: screen -#: preseed.xml:716 +#: preseed.xml:723 #, no-c-format msgid "" "# Preseeding only locale sets language, country and locale.\n" @@ -753,13 +753,13 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:718 +#: preseed.xml:725 #, no-c-format msgid "Keyboard configuration consists of selecting a keyboard architecture and a keymap. In most cases the correct keyboard architecture is selected by default, so there's normally no need to preseed it. The keymap must be known to the &d-i; for the selected keyboard architecture." msgstr "" #. Tag: screen -#: preseed.xml:725 +#: preseed.xml:732 #, no-c-format msgid "" "# Keyboard selection.\n" @@ -770,55 +770,55 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:727 +#: preseed.xml:734 #, no-c-format msgid "To skip keyboard configuration, preseed <classname>console-tools/archs</classname> with <userinput>skip-config</userinput>. This will result in the kernel keymap remaining active." msgstr "" #. Tag: para -#: preseed.xml:736 +#: preseed.xml:743 #, no-c-format msgid "The changes in the input layer for 2.6 kernels have made the keyboard architecture virtually obsolete. For 2.6 kernels normally a <quote>PC</quote> (<userinput>at</userinput>) keymap should be selected." msgstr "" #. Tag: title -#: preseed.xml:746 +#: preseed.xml:753 #, no-c-format msgid "Network configuration" msgstr "" #. Tag: para -#: preseed.xml:747 +#: preseed.xml:754 #, no-c-format msgid "Of course, preseeding the network configuration won't work if you're loading your preconfiguration file from the network. But it's great when you're booting from CD or USB stick. If you are loading preconfiguration files from the network, you can pass network config parameters by using kernel boot parameters." msgstr "" #. Tag: para -#: preseed.xml:755 +#: preseed.xml:762 #, no-c-format msgid "If you need to pick a particular interface when netbooting before loading a preconfiguration file from the network, use a boot parameter such as <userinput>interface=<replaceable>eth1</replaceable></userinput>." msgstr "" #. Tag: para -#: preseed.xml:761 +#: preseed.xml:768 #, no-c-format msgid "Although preseeding the network configuration is normally not possible when using network preseeding (using <quote>preseed/url</quote>), you can use the following hack to work around that, for example if you'd like to set a static address for the network interface. The hack is to force the network configuration to run again after the preconfiguration file has been loaded by creating a <quote>preseed/run</quote> script containing the following commands:" msgstr "" #. Tag: screen -#: preseed.xml:771 +#: preseed.xml:778 #, no-c-format msgid "killall.sh; netcfg" msgstr "" #. Tag: para -#: preseed.xml:773 +#: preseed.xml:780 #, no-c-format msgid "The following debconf variables are relevant for network configuration." msgstr "" #. Tag: screen -#: preseed.xml:779 +#: preseed.xml:786 #, no-c-format msgid "" "# Disable network configuration entirely. This is useful for cdrom\n" @@ -872,19 +872,19 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:781 +#: preseed.xml:788 #, no-c-format msgid "Please note that <command>netcfg</command> will automatically determine the netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In this case, the variable has to be marked as <literal>seen</literal> for automatic installations. Similarly, <command>netcfg</command> will choose an appropriate address if <classname>netcfg/get_gateway</classname> is not set. As a special case, you can set <classname>netcfg/get_gateway</classname> to <quote>none</quote> to specify that no gateway should be used." msgstr "" #. Tag: title -#: preseed.xml:797 +#: preseed.xml:804 #, no-c-format msgid "Network console" msgstr "" #. Tag: screen -#: preseed.xml:799 +#: preseed.xml:806 #, no-c-format msgid "" "# Use the following settings if you wish to make use of the network-console\n" @@ -896,31 +896,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:804 +#: preseed.xml:811 #, no-c-format msgid "Mirror settings" msgstr "" #. Tag: para -#: preseed.xml:805 +#: preseed.xml:812 #, no-c-format msgid "Depending on the installation method you use, a mirror may be used to download additional components of the installer, to install the base system, and to set up the <filename>/etc/apt/sources.list</filename> for the installed system." msgstr "" #. Tag: para -#: preseed.xml:812 +#: preseed.xml:819 #, no-c-format msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system." msgstr "" #. Tag: para -#: preseed.xml:817 +#: preseed.xml:824 #, no-c-format msgid "The parameter <classname>mirror/udeb/suite</classname> determines the suite for additional components for the installer. It is only useful to set this if components are actually downloaded over the network and should match the suite that was used to build the initrd for the installation method used for the installation. Normally the installer will automatically use the correct value and there should be no need to set this." msgstr "" #. Tag: screen -#: preseed.xml:828 +#: preseed.xml:835 #, no-c-format msgid "" "# If you select ftp, the mirror/country string does not need to be set.\n" @@ -937,13 +937,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:833 +#: preseed.xml:840 #, no-c-format msgid "Clock and time zone setup" msgstr "" #. Tag: screen -#: preseed.xml:835 +#: preseed.xml:842 #, no-c-format msgid "" "# Controls whether or not the hardware clock is set to UTC.\n" @@ -960,43 +960,43 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:840 +#: preseed.xml:847 #, no-c-format msgid "Partitioning" msgstr "" #. Tag: para -#: preseed.xml:841 +#: preseed.xml:848 #, no-c-format msgid "Using preseeding to partition the harddisk is limited to what is supported by <classname>partman-auto</classname>. You can choose to partition either existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file." msgstr "" #. Tag: para -#: preseed.xml:849 +#: preseed.xml:856 #, no-c-format msgid "Preseeding of advanced partition setups using RAID, LVM and encryption is supported, but not with the full flexibility possible when partitioning during a non-preseeded install." msgstr "" #. Tag: para -#: preseed.xml:855 +#: preseed.xml:862 #, no-c-format msgid "The examples below only provide basic information on the use of recipes. For detailed information see the files <filename>partman-auto-recipe.txt</filename> and <filename>partman-auto-raid-recipe.txt</filename> included in the <classname>debian-installer</classname> package. Both files are also available from the <ulink url=\"&url-d-i-websvn;/trunk/installer/doc/devel/\">&d-i; source repository</ulink>. Note that the supported functionality may change between releases." msgstr "" #. Tag: para -#: preseed.xml:869 +#: preseed.xml:876 #, no-c-format msgid "The identification of disks is dependent on the order in which their drivers are loaded. If there are multiple disks in the system, make very sure the correct one will be selected before using preseeding." msgstr "" #. Tag: title -#: preseed.xml:878 +#: preseed.xml:885 #, no-c-format msgid "Partitioning example" msgstr "" #. Tag: screen -#: preseed.xml:880 +#: preseed.xml:887 #, no-c-format msgid "" "# If the system has free space you can choose to only partition that space.\n" @@ -1071,25 +1071,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:884 +#: preseed.xml:891 #, no-c-format msgid "Partitioning using RAID" msgstr "" #. Tag: para -#: preseed.xml:885 +#: preseed.xml:892 #, no-c-format msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and specifying spare devices. If you are using RAID 1, you can preseed grub to install to all devices used in the array; see <xref linkend=\"preseed-bootloader\"/>." msgstr "" #. Tag: para -#: preseed.xml:895 +#: preseed.xml:902 #, no-c-format msgid "This type of automated partitioning is easy to get wrong. It is also functionality that receives relatively little testing from the developers of &d-i;. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check <filename>/var/log/syslog</filename> if you run into problems." msgstr "" #. Tag: screen -#: preseed.xml:905 +#: preseed.xml:912 #, no-c-format msgid "" "# The method should be set to \"raid\".\n" @@ -1143,31 +1143,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:910 +#: preseed.xml:917 #, no-c-format msgid "Controlling how partitions are mounted" msgstr "" #. Tag: para -#: preseed.xml:911 +#: preseed.xml:918 #, no-c-format msgid "Normally, filesystems are mounted using a universally unique identifier (UUID) as a key; this allows them to be mounted properly even if their device name changes. UUIDs are long and difficult to read, so, if you prefer, the installer can mount filesystems based on the traditional device names, or based on a label you assign. If you ask the installer to mount by label, any filesystems without a label will be mounted using a UUID instead." msgstr "" #. Tag: para -#: preseed.xml:920 +#: preseed.xml:927 #, no-c-format msgid "Devices with stable names, such as LVM logical volumes, will continue to use their traditional names rather than UUIDs." msgstr "" #. Tag: para -#: preseed.xml:927 +#: preseed.xml:934 #, no-c-format msgid "Traditional device names may change based on the order in which the kernel discovers devices at boot, which may cause the wrong filesystem to be mounted. Similarly, labels are likely to clash if you plug in a new disk or a USB drive, and if that happens your system's behaviour when started will be random." msgstr "" #. Tag: screen -#: preseed.xml:937 +#: preseed.xml:944 #, no-c-format msgid "" "# The default is to mount by UUID, but you can also choose \"traditional\" to\n" @@ -1177,19 +1177,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:943 +#: preseed.xml:950 #, no-c-format msgid "Base system installation" msgstr "" #. Tag: para -#: preseed.xml:944 +#: preseed.xml:951 #, no-c-format msgid "There is actually not very much that can be preseeded for this stage of the installation. The only questions asked concern the installation of the kernel." msgstr "" #. Tag: screen -#: preseed.xml:951 +#: preseed.xml:958 #, no-c-format msgid "" "# Configure APT to not install recommended packages by default. Use of this\n" @@ -1202,29 +1202,29 @@ msgid "" "\n" "# The kernel image (meta) package to be installed; \"none\" can be used if no\n" "# kernel is to be installed.\n" - "#d-i base-installer/kernel/image string linux-image-2.6-486" + "#d-i base-installer/kernel/image string &kernelpackage;-2.6-486" msgstr "" #. Tag: title -#: preseed.xml:956 +#: preseed.xml:963 #, no-c-format msgid "Account setup" msgstr "" #. Tag: para -#: preseed.xml:957 +#: preseed.xml:964 #, no-c-format msgid "The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear text values or MD5 <emphasis>hashes</emphasis>." msgstr "" #. Tag: para -#: preseed.xml:964 +#: preseed.xml:971 #, no-c-format msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these passwords. Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks." msgstr "" #. Tag: screen -#: preseed.xml:974 +#: preseed.xml:981 #, no-c-format msgid "" "# Skip creation of a root account (normal user account will be able to\n" @@ -1256,37 +1256,37 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:976 +#: preseed.xml:983 #, no-c-format msgid "The <classname>passwd/root-password-crypted</classname> and <classname>passwd/user-password-crypted</classname> variables can also be preseeded with <quote>!</quote> as their value. In that case, the corresponding account is disabled. This may be convenient for the root account, provided of course that an alternative method is set up to allow administrative activities or root login (for instance by using SSH key authentication or <command>sudo</command>)." msgstr "" #. Tag: para -#: preseed.xml:986 +#: preseed.xml:993 #, no-c-format msgid "The following command can be used to generate an MD5 hash for a password:" msgstr "" #. Tag: screen -#: preseed.xml:990 +#: preseed.xml:997 #, no-c-format msgid "$ printf \"r00tme\" | mkpasswd -s -m md5" msgstr "" #. Tag: title -#: preseed.xml:996 +#: preseed.xml:1003 #, no-c-format msgid "Apt setup" msgstr "" #. Tag: para -#: preseed.xml:997 +#: preseed.xml:1004 #, no-c-format msgid "Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration options is fully automated based on your installation method and answers to earlier questions. You can optionally add other (local) repositories." msgstr "" #. Tag: screen -#: preseed.xml:1005 +#: preseed.xml:1012 #, no-c-format msgid "" "# You can choose to install non-free and contrib software.\n" @@ -1318,97 +1318,97 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1010 +#: preseed.xml:1017 #, no-c-format msgid "Package selection" msgstr "" #. Tag: para -#: preseed.xml:1011 +#: preseed.xml:1018 #, no-c-format msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:" msgstr "" #. Tag: userinput -#: preseed.xml:1020 +#: preseed.xml:1027 #, no-c-format msgid "standard" msgstr "" #. Tag: userinput -#: preseed.xml:1023 +#: preseed.xml:1030 #, no-c-format msgid "desktop" msgstr "" #. Tag: userinput -#: preseed.xml:1026 +#: preseed.xml:1033 #, no-c-format msgid "gnome-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:1029 +#: preseed.xml:1036 #, no-c-format msgid "kde-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:1032 +#: preseed.xml:1039 #, no-c-format msgid "web-server" msgstr "" #. Tag: userinput -#: preseed.xml:1035 +#: preseed.xml:1042 #, no-c-format msgid "print-server" msgstr "" #. Tag: userinput -#: preseed.xml:1038 +#: preseed.xml:1045 #, no-c-format msgid "dns-server" msgstr "" #. Tag: userinput -#: preseed.xml:1041 +#: preseed.xml:1048 #, no-c-format msgid "file-server" msgstr "" #. Tag: userinput -#: preseed.xml:1044 +#: preseed.xml:1051 #, no-c-format msgid "mail-server" msgstr "" #. Tag: userinput -#: preseed.xml:1047 +#: preseed.xml:1054 #, no-c-format msgid "sql-database" msgstr "" #. Tag: userinput -#: preseed.xml:1050 +#: preseed.xml:1057 #, no-c-format msgid "laptop" msgstr "" #. Tag: para -#: preseed.xml:1054 +#: preseed.xml:1061 #, no-c-format msgid "You can also choose to install no tasks, and force the installation of a set of packages in some other way. We recommend always including the <userinput>standard</userinput> task." msgstr "" #. Tag: para -#: preseed.xml:1060 +#: preseed.xml:1067 #, no-c-format msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well." msgstr "" #. Tag: screen -#: preseed.xml:1070 +#: preseed.xml:1077 #, no-c-format msgid "" "#tasksel tasksel/first multiselect standard, web-server\n" @@ -1430,21 +1430,23 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1075 +#: preseed.xml:1082 #, no-c-format msgid "Boot loader installation" msgstr "" #. Tag: screen -#: preseed.xml:1077 +#: preseed.xml:1084 #, no-c-format msgid "" - "# Grub is the default boot loader (for x86). If you want lilo installed\n" + "<phrase arch=\"linux-any\"># Grub is the default boot loader (for x86). If you want lilo installed\n" "# instead, uncomment this:\n" "#d-i grub-installer/skip boolean true\n" "# To also skip installing lilo, and install no bootloader, uncomment this\n" "# too:\n" - "#d-i lilo-installer/skip boolean true\n" + "#d-i lilo-installer/skip boolean true</phrase>\n" + "<phrase arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment this\n" + "#d-i grub-installer/skip boolean true</phrase>\n" "\n" "# With a few exceptions for unusual partitioning setups, GRUB 2 is now the\n" "# default. If you need GRUB Legacy for some particular reason, then\n" @@ -1480,19 +1482,19 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:1079 +#: preseed.xml:1086 #, no-c-format msgid "An MD5 hash for a password for <classname>grub</classname> can be generated using <command>grub-md5-crypt</command>, or using the command from the example in <xref linkend=\"preseed-account\"/>." msgstr "" #. Tag: title -#: preseed.xml:1089 +#: preseed.xml:1096 #, no-c-format msgid "Finishing up the installation" msgstr "" #. Tag: screen -#: preseed.xml:1091 +#: preseed.xml:1098 #, no-c-format msgid "" "# During installations from serial console, the regular virtual consoles\n" @@ -1515,13 +1517,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1096 +#: preseed.xml:1103 #, no-c-format msgid "Preseeding other packages" msgstr "" #. Tag: screen -#: preseed.xml:1098 +#: preseed.xml:1105 #, no-c-format msgid "" "# Depending on what software you choose to install, or if things go wrong\n" @@ -1534,25 +1536,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1105 +#: preseed.xml:1112 #, no-c-format msgid "Advanced options" msgstr "" #. Tag: title -#: preseed.xml:1108 +#: preseed.xml:1115 #, no-c-format msgid "Running custom commands during the installation" msgstr "" #. Tag: para -#: preseed.xml:1109 +#: preseed.xml:1116 #, no-c-format msgid "A very powerful and flexible option offered by the preconfiguration tools is the ability to run commands or scripts at certain points in the installation." msgstr "" #. Tag: screen -#: preseed.xml:1117 +#: preseed.xml:1124 #, no-c-format msgid "" "# d-i preseeding is inherently not secure. Nothing in the installer checks\n" @@ -1578,13 +1580,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1122 +#: preseed.xml:1129 #, no-c-format msgid "Using preseeding to change default values" msgstr "" #. Tag: para -#: preseed.xml:1123 +#: preseed.xml:1130 #, no-c-format msgid "" "It is possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a question. <informalexample><screen>\n" @@ -1594,31 +1596,31 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:1137 +#: preseed.xml:1144 #, no-c-format msgid "Note that the <quote>d-i</quote> owner should only be used for variables used in the installer itself. For variables belonging to packages installed on the target system, you should use the name of that package instead. See the footnote to <xref linkend=\"preseed-bootparms\"/>." msgstr "" #. Tag: para -#: preseed.xml:1144 +#: preseed.xml:1151 #, no-c-format msgid "If you are preseeding using boot parameters, you can make the installer ask the corresponding question by using the <quote>?=</quote> operator, i.e. <userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?=<replaceable>value</replaceable></userinput> (or <userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</replaceable>?=<replaceable>value</replaceable></userinput>). This will of course only have effect for parameters that correspond to questions that are actually displayed during an installation and not for <quote>internal</quote> parameters." msgstr "" #. Tag: title -#: preseed.xml:1158 +#: preseed.xml:1165 #, no-c-format msgid "Chainloading preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:1159 +#: preseed.xml:1166 #, no-c-format msgid "It is possible to include other preconfiguration files from a preconfiguration file. Any settings in those files will override pre-existing settings from files loaded earlier. This makes it possible to put, for example, general networking settings for your location in one file and more specific settings for certain configurations in other files." msgstr "" #. Tag: screen -#: preseed.xml:1169 +#: preseed.xml:1176 #, no-c-format msgid "" "# More than one file can be listed, separated by spaces; all will be\n" @@ -1646,7 +1648,7 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:1171 +#: preseed.xml:1178 #, no-c-format msgid "It is also possible to chainload from the initrd or file preseeding phase, into network preseeding by setting preseed/url in the earlier files. This will cause network preseeding to be performed when the network comes up. You need to be careful when doing this, since there will be two distinct runs at preseeding, meaning for example that you get another chance to run the preseed/early command, the second one happening after the network comes up." msgstr "" diff --git a/po/pot/random-bits.pot b/po/pot/random-bits.pot index c9c485f2a..4d981152b 100644 --- a/po/pot/random-bits.pot +++ b/po/pot/random-bits.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2010-04-19 00:12+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+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" @@ -697,25 +697,25 @@ msgstr "" #. Tag: title #: random-bits.xml:358 #, no-c-format -msgid "Installing &debian; from a Unix/Linux System" +msgid "Installing &debian-gnu; from a Unix/Linux System" msgstr "" #. Tag: para #: random-bits.xml:360 #, no-c-format -msgid "This section explains how to install &debian; from an existing Unix or Linux system, without using the menu-driven installer as explained in the rest of the manual. This <quote>cross-install</quote> HOWTO has been requested by users switching to &debian; from Red Hat, Mandrake, and SUSE. In this section some familiarity with entering *nix commands and navigating the file system is assumed. In this section, <prompt>$</prompt> symbolizes a command to be entered in the user's current system, while <prompt>#</prompt> refers to a command entered in the Debian chroot." +msgid "This section explains how to install &debian-gnu; from an existing Unix or Linux system, without using the menu-driven installer as explained in the rest of the manual. This <quote>cross-install</quote> HOWTO has been requested by users switching to &debian-gnu; from Red Hat, Mandrake, and SUSE. In this section some familiarity with entering *nix commands and navigating the file system is assumed. In this section, <prompt>$</prompt> symbolizes a command to be entered in the user's current system, while <prompt>#</prompt> refers to a command entered in the Debian chroot." msgstr "" #. Tag: para #: random-bits.xml:372 #, no-c-format -msgid "Once you've got the new Debian system configured to your preference, you can migrate your existing user data (if any) to it, and keep on rolling. This is therefore a <quote>zero downtime</quote> &debian; install. It's also a clever way for dealing with hardware that otherwise doesn't play friendly with various boot or installation media." +msgid "Once you've got the new Debian system configured to your preference, you can migrate your existing user data (if any) to it, and keep on rolling. This is therefore a <quote>zero downtime</quote> &debian-gnu; install. It's also a clever way for dealing with hardware that otherwise doesn't play friendly with various boot or installation media." msgstr "" #. Tag: para #: random-bits.xml:383 #, no-c-format -msgid "As this is a mostly manual procedure, you should bear in mind that you will need to do a lot of basic configuration of the system yourself, which will also require more knowledge of Debian and of Linux in general than performing a regular installation. You cannot expect this procedure to result in a system that is identical to a system from a regular installation. You should also keep in mind that this procedure only gives the basic steps to set up a system. Additional installation and/or configuration steps may be needed." +msgid "As this is a mostly manual procedure, you should bear in mind that you will need to do a lot of basic configuration of the system yourself, which will also require more knowledge of Debian and of &arch-kernel; in general than performing a regular installation. You cannot expect this procedure to result in a system that is identical to a system from a regular installation. You should also keep in mind that this procedure only gives the basic steps to set up a system. Additional installation and/or configuration steps may be needed." msgstr "" #. Tag: title @@ -810,7 +810,7 @@ msgstr "" #. Tag: para #: random-bits.xml:503 #, no-c-format -msgid "If you have a &releasename; &debian; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>" +msgid "If you have a &releasename; &debian-gnu; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>" msgstr "" #. Tag: para @@ -1087,70 +1087,47 @@ msgstr "" #. Tag: para #: random-bits.xml:728 #, no-c-format -msgid "If you intend to boot this system, you probably want a Linux kernel and a boot loader. Identify available pre-packaged kernels with:" +msgid "If you intend to boot this system, you probably want a &arch-kernel; kernel and a boot loader. Identify available pre-packaged kernels with:" msgstr "" #. Tag: screen #: random-bits.xml:733 #, no-c-format -msgid "# apt-cache search linux-image" +msgid "# apt-cache search &kernelpackage;" msgstr "" #. Tag: para #: random-bits.xml:735 #, no-c-format -msgid "If you intend to use a pre-packaged kernel, you may want to create the configuration file <filename>/etc/kernel-img.conf</filename> before you do so. Here's an example file:" +msgid "Then install the kernel package of your choice using its package name." msgstr "" #. Tag: screen -#: random-bits.xml:741 +#: random-bits.xml:739 #, no-c-format -msgid "" - "# Kernel image management overrides\n" - "# See kernel-img.conf(5) for details\n" - "do_symlinks = yes\n" - "relative_links = yes\n" - "do_bootloader = yes\n" - "do_bootfloppy = no\n" - "do_initrd = yes\n" - "link_in_boot = no" -msgstr "" - -#. Tag: para -#: random-bits.xml:743 -#, no-c-format -msgid "For detailed information about this file and the various options, consult its man page which will be available after installing the <classname>kernel-package</classname> package. We recommend that you check that the values are appropriate for your system." -msgstr "" - -#. Tag: para -#: random-bits.xml:750 -#, no-c-format -msgid "" - "Then install the kernel package of your choice using its package name. <informalexample><screen>\n" - "# aptitude install linux-image-<replaceable>&kernelversion;-arch-etc</replaceable>\n" - "</screen></informalexample> If you did not create a <filename>/etc/kernel-img.conf</filename> before installing a pre-packaged kernel, you may be asked some questions during its installation that refer to it." +msgid "# aptitude install &kernelpackage;-<replaceable>&kernelversion;-arch-etc</replaceable>" msgstr "" #. Tag: title -#: random-bits.xml:764 +#: random-bits.xml:745 #, no-c-format msgid "Set up the Boot Loader" msgstr "" #. Tag: para -#: random-bits.xml:765 +#: random-bits.xml:746 #, no-c-format -msgid "To make your &debian; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your Debian chroot to do so." +msgid "To make your &debian-gnu; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your Debian chroot to do so." msgstr "" #. Tag: para -#: random-bits.xml:772 +#: random-bits.xml:753 #, no-c-format -msgid "Check <userinput>info grub</userinput> or <userinput>man lilo.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing grub <filename>menu.lst</filename> or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call <command>lilo</command> (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)." +msgid "Check <userinput>info grub</userinput> <phrase arch=\"x86\">or <userinput>man lilo.conf</userinput></phrase> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing grub <filename>menu.lst</filename><phrase arch=\"x86\">or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call <command>lilo</command> (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)</phrase>." msgstr "" #. Tag: para -#: random-bits.xml:784 +#: random-bits.xml:765 #, no-c-format msgid "" "Installing and setting up <classname>grub</classname> is as easy as: <informalexample><screen>\n" @@ -1161,19 +1138,19 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:794 +#: random-bits.xml:775 #, no-c-format msgid "Note that this assumes that a <filename>/dev/hda</filename> device file has been created. There are alternative methods to install <command>grub</command>, but those are outside the scope of this appendix." msgstr "" #. Tag: para -#: random-bits.xml:800 +#: random-bits.xml:781 #, no-c-format msgid "Here is a basic <filename>/etc/lilo.conf</filename> as an example:" msgstr "" #. Tag: screen -#: random-bits.xml:804 +#: random-bits.xml:785 #, no-c-format msgid "" "boot=/dev/<replaceable>hda6</replaceable>\n" @@ -1187,29 +1164,13 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:806 -#, no-c-format -msgid "Depending on which bootloader you selected, you can now make some additional changes in <filename>/etc/kernel-img.conf</filename>." -msgstr "" - -#. Tag: para -#: random-bits.xml:811 -#, no-c-format -msgid "" - "For the <classname>grub</classname> bootloader, you should set the <literal>do_bootloader</literal> option to <quote>no</quote>. And to automatically update your <filename>/boot/grub/menu.lst</filename> on installation or removal of Debian kernels, add the following lines: <informalexample><screen>\n" - "postinst_hook = update-grub\n" - "postrm_hook = update-grub\n" - "</screen></informalexample> For the <classname>lilo</classname> bootloader, the value of <literal>do_bootloader</literal> needs to remain <quote>yes</quote>." -msgstr "" - -#. Tag: para -#: random-bits.xml:823 +#: random-bits.xml:787 #, no-c-format msgid "Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing <filename>yaboot.conf</filename>. You could also copy it to the new system and edit it there. After you are done editing, call ybin (remember it will use <filename>yaboot.conf</filename> relative to the system you call it from)." msgstr "" #. Tag: para -#: random-bits.xml:833 +#: random-bits.xml:797 #, no-c-format msgid "" "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n" @@ -1225,13 +1186,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:846 +#: random-bits.xml:810 #, no-c-format msgid "Finishing touches" msgstr "" #. Tag: para -#: random-bits.xml:847 +#: random-bits.xml:811 #, no-c-format msgid "" "As mentioned earlier, the installed system will be very basic. If you would like to make the system a bit more mature, there is an easy method to install all packages with <quote>standard</quote> priority: <informalexample><screen>\n" @@ -1240,91 +1201,91 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:858 +#: random-bits.xml:822 #, no-c-format msgid "After the installation there will be a lot of downloaded packages in <filename>/var/cache/apt/archives/</filename>. You can free up some diskspace by running:" msgstr "" #. Tag: screen -#: random-bits.xml:864 +#: random-bits.xml:828 #, no-c-format msgid "# aptitude clean" msgstr "" #. Tag: title -#: random-bits.xml:875 +#: random-bits.xml:839 #, no-c-format -msgid "Installing &debian; over Parallel Line IP (PLIP)" +msgid "Installing &debian-gnu; over Parallel Line IP (PLIP)" msgstr "" #. Tag: para -#: random-bits.xml:877 +#: random-bits.xml:841 #, no-c-format -msgid "This section explains how to install &debian; on a computer without an Ethernet card, but with just a remote gateway computer attached via a Null-Modem cable (also called Null-Printer cable). The gateway computer should be connected to a network that has a Debian mirror on it (e.g. to the Internet)." +msgid "This section explains how to install &debian-gnu; on a computer without an Ethernet card, but with just a remote gateway computer attached via a Null-Modem cable (also called Null-Printer cable). The gateway computer should be connected to a network that has a Debian mirror on it (e.g. to the Internet)." msgstr "" #. Tag: para -#: random-bits.xml:885 +#: random-bits.xml:849 #, no-c-format msgid "In the example in this appendix we will set up a PLIP connection using a gateway connected to the Internet over a dial-up connection (ppp0). We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the target system and the source system respectively (these addresses should be unused within your network address space)." msgstr "" #. Tag: para -#: random-bits.xml:893 +#: random-bits.xml:857 #, no-c-format msgid "The PLIP connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)." msgstr "" #. Tag: para -#: random-bits.xml:898 +#: random-bits.xml:862 #, no-c-format msgid "Before you start, you will need to check the BIOS configuration (IO base address and IRQ) for the parallel ports of both the source and target systems. The most common values are <literal>io=0x378</literal>, <literal>irq=7</literal>." msgstr "" #. Tag: title -#: random-bits.xml:908 +#: random-bits.xml:872 #, no-c-format msgid "Requirements" msgstr "" #. Tag: para -#: random-bits.xml:911 +#: random-bits.xml:875 #, no-c-format msgid "A target computer, called <emphasis>target</emphasis>, where Debian will be installed." msgstr "" #. Tag: para -#: random-bits.xml:917 +#: random-bits.xml:881 #, no-c-format msgid "System installation media; see <xref linkend=\"installation-media\"/>." msgstr "" #. Tag: para -#: random-bits.xml:922 +#: random-bits.xml:886 #, no-c-format msgid "Another computer connected to the Internet, called <emphasis>source</emphasis>, that will function as the gateway." msgstr "" #. Tag: para -#: random-bits.xml:928 +#: random-bits.xml:892 #, no-c-format msgid "A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> for more information on this cable and instructions how to make your own." msgstr "" #. Tag: title -#: random-bits.xml:940 +#: random-bits.xml:904 #, no-c-format msgid "Setting up source" msgstr "" #. Tag: para -#: random-bits.xml:941 +#: random-bits.xml:905 #, no-c-format msgid "The following shell script is a simple example of how to configure the source computer as a gateway to the Internet using ppp0." msgstr "" #. Tag: screen -#: random-bits.xml:946 +#: random-bits.xml:910 #, no-c-format msgid "" "#!/bin/sh\n" @@ -1345,13 +1306,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:952 +#: random-bits.xml:916 #, no-c-format msgid "Installing target" msgstr "" #. Tag: para -#: random-bits.xml:953 +#: random-bits.xml:917 #, no-c-format msgid "" "Boot the installation media. The installation needs to be run in expert mode; enter <userinput>expert</userinput> at the boot prompt. If you need to set parameters for kernel modules, you also need to do this at the boot prompt. For example, to boot the installer and set values for the <quote>io</quote> and <quote>irq</quote> options for the parport_pc module, enter the following at the boot prompt: <informalexample><screen>\n" @@ -1360,217 +1321,217 @@ msgid "" msgstr "" #. Tag: guimenuitem -#: random-bits.xml:972 +#: random-bits.xml:936 #, no-c-format msgid "Load installer components from CD" msgstr "" #. Tag: para -#: random-bits.xml:974 +#: random-bits.xml:938 #, no-c-format msgid "Select the <userinput>plip-modules</userinput> option from the list; this will make the PLIP drivers available to the installation system." msgstr "" #. Tag: guimenuitem -#: random-bits.xml:982 +#: random-bits.xml:946 #, no-c-format msgid "Detect network hardware" msgstr "" #. Tag: para -#: random-bits.xml:987 +#: random-bits.xml:951 #, no-c-format msgid "If target <emphasis>does</emphasis> have a network card, a list of driver modules for detected cards will be shown. If you want to force &d-i; to use plip instead, you have to deselect all listed driver modules. Obviously, if target doesn't have a network card, the installer will not show this list." msgstr "" #. Tag: para -#: random-bits.xml:996 +#: random-bits.xml:960 #, no-c-format msgid "Because no network card was detected/selected earlier, the installer will ask you to select a network driver module from a list. Select the <userinput>plip</userinput> module." msgstr "" #. Tag: guimenuitem -#: random-bits.xml:1008 +#: random-bits.xml:972 #, no-c-format msgid "Configure the network" msgstr "" #. Tag: para -#: random-bits.xml:1011 +#: random-bits.xml:975 #, no-c-format msgid "Auto-configure network with DHCP: No" msgstr "" #. Tag: para -#: random-bits.xml:1016 +#: random-bits.xml:980 #, no-c-format msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>" msgstr "" #. Tag: para -#: random-bits.xml:1021 +#: random-bits.xml:985 #, no-c-format msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>" msgstr "" #. Tag: para -#: random-bits.xml:1027 +#: random-bits.xml:991 #, no-c-format msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)" msgstr "" #. Tag: title -#: random-bits.xml:1046 +#: random-bits.xml:1010 #, no-c-format -msgid "Installing &debian; using PPP over Ethernet (PPPoE)" +msgid "Installing &debian-gnu; using PPP over Ethernet (PPPoE)" msgstr "" #. Tag: para -#: random-bits.xml:1048 +#: random-bits.xml:1012 #, no-c-format msgid "In some countries PPP over Ethernet (PPPoE) is a common protocol for broadband (ADSL or cable) connections to an Internet Service Provider. Setting up a network connection using PPPoE is not supported by default in the installer, but can be made to work very simply. This section explains how." msgstr "" #. Tag: para -#: random-bits.xml:1056 +#: random-bits.xml:1020 #, no-c-format msgid "The PPPoE connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)." msgstr "" #. Tag: para -#: random-bits.xml:1061 +#: random-bits.xml:1025 #, no-c-format msgid "To have the option of setting up and using PPPoE during the installation, you will need to install using one of the CD-ROM/DVD images that are available. It is not supported for other installation methods (e.g. netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)." msgstr "" #. Tag: para -#: random-bits.xml:1068 +#: random-bits.xml:1032 #, no-c-format msgid "Installing over PPPoE is mostly the same as any other installation. The following steps explain the differences." msgstr "" #. Tag: para -#: random-bits.xml:1076 +#: random-bits.xml:1040 #, no-c-format msgid "Boot the installer with the boot parameter <userinput>modules=ppp-udeb</userinput><footnote arch=\"x86\"> <para> See <xref linkend=\"boot-screen\"/> for information on how to add a boot parameter. </para> </footnote>. This will ensure the component responsible for the setup of PPPoE (<classname>ppp-udeb</classname>) will be loaded and run automatically." msgstr "" #. Tag: para -#: random-bits.xml:1091 +#: random-bits.xml:1055 #, no-c-format msgid "Follow the regular initial steps of the installation (language, country and keyboard selection; the loading of additional installer components<footnote> <para> The <classname>ppp-udeb</classname> component is loaded as one of the additional components in this step. If you want to install at medium or low priority (expert mode), you can also manually select the <classname>ppp-udeb</classname> instead of entering the <quote>modules</quote> parameter at the boot prompt. </para> </footnote>)." msgstr "" #. Tag: para -#: random-bits.xml:1110 +#: random-bits.xml:1074 #, no-c-format msgid "The next step is the detection of network hardware, in order to identify any Ethernet cards present in the system." msgstr "" #. Tag: para -#: random-bits.xml:1116 +#: random-bits.xml:1080 #, no-c-format msgid "After this the actual setup of PPPoE is started. The installer will probe all the detected Ethernet interfaces in an attempt to find a PPPoE concentrator (a type of server which handles PPPoE connections)." msgstr "" #. Tag: para -#: random-bits.xml:1122 +#: random-bits.xml:1086 #, no-c-format msgid "It is possible that the concentrator will not to be found at the first attempt. This can happen occasionally on slow or loaded networks or with faulty servers. In most cases a second attempt to detect the concentrator will be successful; to retry, select <guimenuitem>Configure and start a PPPoE connection</guimenuitem> from the main menu of the installer." msgstr "" #. Tag: para -#: random-bits.xml:1131 +#: random-bits.xml:1095 #, no-c-format msgid "After a concentrator is found, the user will be prompted to type the login information (the PPPoE username and password)." msgstr "" #. Tag: para -#: random-bits.xml:1137 +#: random-bits.xml:1101 #, no-c-format msgid "At this point the installer will use the provided information to establish the PPPoE connection. If the correct information was provided, the PPPoE connection should be configured and the installer should be able to use it to connect to the Internet and retrieve packages over it (if needed). If the login information is not correct or some error appears, the installer will stop, but the configuration can be attempted again by selecting the menu entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>." msgstr "" #. Tag: title -#: random-bits.xml:1157 +#: random-bits.xml:1121 #, no-c-format msgid "The Graphical Installer" msgstr "" #. Tag: para -#: random-bits.xml:1158 +#: random-bits.xml:1122 #, no-c-format msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the regular installer as it basically uses the same programs, but with a different frontend." msgstr "" #. Tag: para -#: random-bits.xml:1166 +#: random-bits.xml:1130 #, no-c-format msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the regular <quote>newt</quote> frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen." msgstr "" #. Tag: para -#: random-bits.xml:1175 +#: random-bits.xml:1139 #, no-c-format msgid "The graphical installer is available with all CD images and with the hd-media installation method. To boot the graphical installer simply select the relevant option from the boot menu. Expert and rescue mode for the graphical installer can be selected from the <quote>Advanced options</quote> menu. The previously used boot methods <userinput>installgui</userinput>, <userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can still be used from the boot prompt which is shown after selecting the <quote>Help</quote> option in the boot menu." msgstr "" #. Tag: para -#: random-bits.xml:1186 +#: random-bits.xml:1150 #, no-c-format msgid "There is also a graphical installer image that can be netbooted. And there is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a Debian mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is mainly useful for testing." msgstr "" #. Tag: para -#: random-bits.xml:1199 +#: random-bits.xml:1163 #, no-c-format msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a Debian mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems." msgstr "" #. Tag: para -#: random-bits.xml:1213 +#: random-bits.xml:1177 #, no-c-format msgid "Just as with the regular installer it is possible to add boot parameters when starting the graphical installer." msgstr "" #. Tag: para -#: random-bits.xml:1219 +#: random-bits.xml:1183 #, no-c-format msgid "The graphical installer requires significantly more memory to run than the regular installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the regular <quote>newt</quote> frontend." msgstr "" #. Tag: para -#: random-bits.xml:1226 +#: random-bits.xml:1190 #, no-c-format msgid "If the amount of memory in your system is below &minimum-memory;, the graphical installer may fail to boot at all while booting the regular installer would still work. Using the regular installer is recommended for systems with little available memory." msgstr "" #. Tag: title -#: random-bits.xml:1236 +#: random-bits.xml:1200 #, no-c-format msgid "Using the graphical installer" msgstr "" #. Tag: para -#: random-bits.xml:1237 +#: random-bits.xml:1201 #, no-c-format msgid "As already mentioned, the graphical installer basically works the same as the regular installer and thus the rest of this manual can be used to guide you through the installation process." msgstr "" #. Tag: para -#: random-bits.xml:1243 +#: random-bits.xml:1207 #, no-c-format msgid "If you prefer using the keyboard over the mouse, there are two things you need to know. To expand a collapsed list (used for example for the selection of countries within continents), you can use the <keycap>+</keycap> and <keycap>-</keycap> keys. For questions where more than one item can be selected (e.g. task selection), you first need to tab to the &BTN-CONT; button after making your selections; hitting enter will toggle a selection, not activate &BTN-CONT;." msgstr "" #. Tag: para -#: random-bits.xml:1253 +#: random-bits.xml:1217 #, no-c-format msgid "If a dialog offers additional help information, a <guibutton>Help</guibutton> button will be displayed. The help information can be accessed either by activating the button or by pressing the <keycap>F1</keycap> key." msgstr "" #. Tag: para -#: random-bits.xml:1259 +#: random-bits.xml:1223 #, no-c-format msgid "To switch to another console, you will also need to use the <keycap>Ctrl</keycap> key, just as with the X Window System. For example, to switch to VT2 (the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</keycap> <keycap>F5</keycap> </keycombo> to switch back." msgstr "" diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index 5e48bb67f..347ca0248 100644 --- a/po/pot/using-d-i.pot +++ b/po/pot/using-d-i.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2010-04-18 00:12+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+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" @@ -347,7 +347,7 @@ msgstr "" #. Tag: para #: using-d-i.xml:315 #, no-c-format -msgid "Installs the most basic set of packages which would allow the computer to operate under Linux when rebooted." +msgid "Installs the most basic set of packages which would allow the computer to operate under &debian-gnu; when rebooted." msgstr "" #. Tag: term @@ -407,7 +407,7 @@ msgstr "" #. Tag: para #: using-d-i.xml:361 #, no-c-format -msgid "The various bootloader installers each install a boot loader program on the hard disk, which is necessary for the computer to start up using Linux without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots." +msgid "The various bootloader installers each install a boot loader program on the hard disk, which is necessary for the computer to start up using &arch-kernel; without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots." msgstr "" #. Tag: term @@ -479,7 +479,7 @@ msgstr "" #. Tag: para #: using-d-i.xml:451 #, no-c-format -msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian; on your system." +msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian-gnu; on your system." msgstr "" #. Tag: para @@ -1730,7 +1730,7 @@ msgstr "" #. Tag: para #: using-d-i.xml:2105 #, no-c-format -msgid "As part of the installation, a Linux kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels." +msgid "As part of the installation, a &arch-kernel; kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels." msgstr "" #. Tag: para @@ -1832,7 +1832,7 @@ msgstr "" #. Tag: para #: using-d-i.xml:2236 #, no-c-format -msgid "One of the tools used to install packages on a &debian; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management." +msgid "One of the tools used to install packages on a &debian-gnu; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management." msgstr "" #. Tag: para @@ -2373,7 +2373,7 @@ msgstr "" #. Tag: para #: using-d-i.xml:2946 #, no-c-format -msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian;." +msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian-gnu;." msgstr "" #. Tag: title @@ -2457,7 +2457,7 @@ msgstr "" #. Tag: para #: using-d-i.xml:3075 #, no-c-format -msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase> <phrase arch=\"x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase>" +msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase> <phrase arch=\"any-x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase>" msgstr "" #. Tag: para @@ -2481,7 +2481,7 @@ msgstr "" #. Tag: para #: using-d-i.xml:3109 #, no-c-format -msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian; from the DASD which you selected for the root filesystem during the first steps of the installation." +msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian-gnu; from the DASD which you selected for the root filesystem during the first steps of the installation." msgstr "" #. Tag: title @@ -2688,7 +2688,7 @@ msgstr "" #. Tag: para #: using-d-i.xml:3429 #, no-c-format -msgid "Tarballs containing current packages for the most common firmware are available from: <itemizedlist> <listitem><para> <ulink url=\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just download the tarball for the correct release and unpack it to the file system on the medium." +msgid "Tarballs and zip files containing current packages for the most common firmware are available from: <itemizedlist> <listitem><para> <ulink url=\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just download the tarball or zip file for the correct release and unpack it to the file system on the medium." msgstr "" #. Tag: para diff --git a/po/pot/welcome.pot b/po/pot/welcome.pot index 6a3342f31..b95ec50ad 100644 --- a/po/pot/welcome.pot +++ b/po/pot/welcome.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2009-11-08 01:11+0000\n" +"POT-Creation-Date: 2010-10-05 18:28+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" @@ -23,7 +23,7 @@ msgstr "" #. Tag: para #: welcome.xml:5 #, no-c-format -msgid "This chapter provides an overview of the Debian Project and &debian;. If you already know about the Debian Project's history and the &debian; distribution, feel free to skip to the next chapter." +msgid "This chapter provides an overview of the Debian Project and &debian-gnu;. If you already know about the Debian Project's history and the &debian-gnu; distribution, feel free to skip to the next chapter." msgstr "" #. Tag: title @@ -219,187 +219,229 @@ msgid "The primary, and best, method of getting support for your Debian GNU/Linu msgstr "" #. Tag: title +#: welcome.xml:315 +#, no-c-format +msgid "What is Debian GNU/kFreeBSD?" +msgstr "" + +#. Tag: para #: welcome.xml:317 #, no-c-format +msgid "Debian GNU/kFreeBSD is a Debian GNU system with the kFreeBSD kernel." +msgstr "" + +#. Tag: para +#: welcome.xml:321 +#, no-c-format +msgid "This port of Debian is currently only being developed for the i386 and amd64 architectures, although ports to other architectures is possible." +msgstr "" + +#. Tag: para +#: welcome.xml:326 +#, no-c-format +msgid "Please note that Debian GNU/kFreeBSD is not a Linux system, and thus some information on Linux system may not apply to it." +msgstr "" + +#. Tag: para +#: welcome.xml:331 +#, no-c-format +msgid "For more information, see the <ulink url=\"http://www.debian.org/ports/kfreebsd-gnu/\"> Debian GNU/kFreeBSD ports page</ulink> and the <email>debian-bsd@lists.debian.org</email> mailing list." +msgstr "" + +#. Tag: title +#: welcome.xml:350 +#, no-c-format msgid "What is Debian GNU/Hurd?" msgstr "" #. Tag: para -#: welcome.xml:319 +#: welcome.xml:352 +#, no-c-format +msgid "Debian GNU/Hurd is a Debian GNU system with the GNU Hurd — a set of servers running on top of the GNU Mach microkernel." +msgstr "" + +#. Tag: para +#: welcome.xml:357 +#, no-c-format +msgid "The Hurd is still unfinished, and is unsuitable for day-to-day use, but work is continuing. The Hurd is currently only being developed for the i386 architecture, although ports to other architectures will be made once the system becomes more stable." +msgstr "" + +#. Tag: para +#: welcome.xml:365 #, no-c-format -msgid "Debian GNU/Hurd is a Debian GNU system that replaces the Linux monolithic kernel with the GNU Hurd — a set of servers running on top of the GNU Mach microkernel. The Hurd is still unfinished, and is unsuitable for day-to-day use, but work is continuing. The Hurd is currently only being developed for the i386 architecture, although ports to other architectures will be made once the system becomes more stable." +msgid "Please note that Debian GNU/Hurd is not a Linux system, and thus some information on Linux system may not apply to it." msgstr "" #. Tag: para -#: welcome.xml:329 +#: welcome.xml:370 #, no-c-format msgid "For more information, see the <ulink url=\"http://www.debian.org/ports/hurd/\"> Debian GNU/Hurd ports page</ulink> and the <email>debian-hurd@lists.debian.org</email> mailing list." msgstr "" #. Tag: title -#: welcome.xml:346 +#: welcome.xml:387 #, no-c-format msgid "Getting Debian" msgstr "" #. Tag: para -#: welcome.xml:348 +#: welcome.xml:389 #, no-c-format -msgid "For information on how to download &debian; from the Internet or from whom official Debian CDs can be purchased, see the <ulink url=\"&url-debian-distrib;\">distribution web page</ulink>. The <ulink url=\"&url-debian-mirrors;\">list of Debian mirrors</ulink> contains a full set of official Debian mirrors, so you can easily find the nearest one." +msgid "For information on how to download &debian-gnu; from the Internet or from whom official Debian CDs can be purchased, see the <ulink url=\"&url-debian-distrib;\">distribution web page</ulink>. The <ulink url=\"&url-debian-mirrors;\">list of Debian mirrors</ulink> contains a full set of official Debian mirrors, so you can easily find the nearest one." msgstr "" #. Tag: para -#: welcome.xml:357 +#: welcome.xml:398 #, no-c-format msgid "Debian can be upgraded after installation very easily. The installation procedure will help set up the system so that you can make those upgrades once installation is complete, if need be." msgstr "" #. Tag: title -#: welcome.xml:372 +#: welcome.xml:413 #, no-c-format msgid "Getting the Newest Version of This Document" msgstr "" #. Tag: para -#: welcome.xml:374 +#: welcome.xml:415 #, no-c-format -msgid "This document is constantly being revised. Be sure to check the <ulink url=\"&url-release-area;\"> Debian &release; pages</ulink> for any last-minute information about the &release; release of the &debian; system. Updated versions of this installation manual are also available from the <ulink url=\"&url-install-manual;\">official Install Manual pages</ulink>." +msgid "This document is constantly being revised. Be sure to check the <ulink url=\"&url-release-area;\"> Debian &release; pages</ulink> for any last-minute information about the &release; release of the &debian-gnu; system. Updated versions of this installation manual are also available from the <ulink url=\"&url-install-manual;\">official Install Manual pages</ulink>." msgstr "" #. Tag: title -#: welcome.xml:392 +#: welcome.xml:433 #, no-c-format msgid "Organization of This Document" msgstr "" #. Tag: para -#: welcome.xml:394 +#: welcome.xml:435 #, no-c-format msgid "This document is meant to serve as a manual for first-time Debian users. It tries to make as few assumptions as possible about your level of expertise. However, we do assume that you have a general understanding of how the hardware in your computer works." msgstr "" #. Tag: para -#: welcome.xml:401 +#: welcome.xml:442 #, no-c-format msgid "Expert users may also find interesting reference information in this document, including minimum installation sizes, details about the hardware supported by the Debian installation system, and so on. We encourage expert users to jump around in the document." msgstr "" #. Tag: para -#: welcome.xml:408 +#: welcome.xml:449 #, no-c-format -msgid "In general, this manual is arranged in a linear fashion, walking you through the installation process from start to finish. Here are the steps in installing &debian;, and the sections of this document which correlate with each step:" +msgid "In general, this manual is arranged in a linear fashion, walking you through the installation process from start to finish. Here are the steps in installing &debian-gnu;, and the sections of this document which correlate with each step:" msgstr "" #. Tag: para -#: welcome.xml:416 +#: welcome.xml:457 #, no-c-format msgid "Determine whether your hardware meets the requirements for using the installation system, in <xref linkend=\"hardware-req\"/>." msgstr "" #. Tag: para -#: welcome.xml:422 +#: welcome.xml:463 #, no-c-format msgid "Backup your system, perform any necessary planning and hardware configuration prior to installing Debian, in <xref linkend=\"preparing\"/>. If you are preparing a multi-boot system, you may need to create partitionable space on your hard disk for Debian to use." msgstr "" #. Tag: para -#: welcome.xml:430 +#: welcome.xml:471 #, no-c-format msgid "In <xref linkend=\"install-methods\"/>, you will obtain the necessary installation files for your method of installation." msgstr "" #. Tag: para -#: welcome.xml:436 +#: welcome.xml:477 #, no-c-format msgid "describes booting into the installation system. This chapter also discusses troubleshooting procedures in case you have problems with this step." msgstr "" #. Tag: para -#: welcome.xml:443 +#: welcome.xml:484 #, no-c-format msgid "Perform the actual installation according to <xref linkend=\"d-i-intro\"/>. This involves choosing your language, configuring peripheral driver modules, configuring your network connection, so that remaining installation files can be obtained directly from a Debian server (if you are not installing from a CD), partitioning your hard drives and installation of a base system, then selection and installation of tasks. (Some background about setting up the partitions for your Debian system is explained in <xref linkend=\"partitioning\"/>.)" msgstr "" #. Tag: para -#: welcome.xml:456 +#: welcome.xml:497 #, no-c-format msgid "Boot into your newly installed base system, from <xref linkend=\"boot-new\"/>." msgstr "" #. Tag: para -#: welcome.xml:464 +#: welcome.xml:505 #, no-c-format msgid "Once you've got your system installed, you can read <xref linkend=\"post-install\"/>. That chapter explains where to look to find more information about Unix and Debian, and how to replace your kernel." msgstr "" #. Tag: para -#: welcome.xml:474 +#: welcome.xml:515 #, no-c-format msgid "Finally, information about this document and how to contribute to it may be found in <xref linkend=\"administrivia\"/>." msgstr "" #. Tag: title -#: welcome.xml:484 +#: welcome.xml:525 #, no-c-format msgid "Your Documentation Help is Welcome" msgstr "" #. Tag: para -#: welcome.xml:486 +#: welcome.xml:527 #, no-c-format msgid "Any help, suggestions, and especially, patches, are greatly appreciated. Working versions of this document can be found at <ulink url=\"&url-d-i-alioth-manual;\"></ulink>. There you will find a list of all the different architectures and languages for which this document is available." msgstr "" #. Tag: para -#: welcome.xml:493 +#: welcome.xml:534 #, no-c-format msgid "Source is also available publicly; look in <xref linkend=\"administrivia\"/> for more information concerning how to contribute. We welcome suggestions, comments, patches, and bug reports (use the package <classname>installation-guide</classname> for bugs, but check first to see if the problem is already reported)." msgstr "" #. Tag: title -#: welcome.xml:509 +#: welcome.xml:550 #, no-c-format msgid "About Copyrights and Software Licenses" msgstr "" #. Tag: para -#: welcome.xml:512 +#: welcome.xml:553 #, no-c-format -msgid "We're sure that you've read some of the licenses that come with most commercial software — they usually say that you can only use one copy of the software on a single computer. This system's license isn't like that at all. We encourage you to put a copy of &debian; on every computer in your school or place of business. Lend your installation media to your friends and help them install it on their computers! You can even make thousands of copies and <emphasis>sell</emphasis> them — albeit with a few restrictions. Your freedom to install and use the system comes directly from Debian being based on <emphasis>free software</emphasis>." +msgid "We're sure that you've read some of the licenses that come with most commercial software — they usually say that you can only use one copy of the software on a single computer. This system's license isn't like that at all. We encourage you to put a copy of &debian-gnu; on every computer in your school or place of business. Lend your installation media to your friends and help them install it on their computers! You can even make thousands of copies and <emphasis>sell</emphasis> them — albeit with a few restrictions. Your freedom to install and use the system comes directly from Debian being based on <emphasis>free software</emphasis>." msgstr "" #. Tag: para -#: welcome.xml:525 +#: welcome.xml:566 #, no-c-format msgid "Calling software <emphasis>free</emphasis> doesn't mean that the software isn't copyrighted, and it doesn't mean that CDs containing that software must be distributed at no charge. Free software, in part, means that the licenses of individual programs do not require you to pay for the privilege of distributing or using those programs. Free software also means that not only may anyone extend, adapt, and modify the software, but that they may distribute the results of their work as well." msgstr "" #. Tag: para -#: welcome.xml:536 +#: welcome.xml:577 #, no-c-format msgid "The Debian project, as a pragmatic concession to its users, does make some packages available that do not meet our criteria for being free. These packages are not part of the official distribution, however, and are only available from the <userinput>contrib</userinput> or <userinput>non-free</userinput> areas of Debian mirrors or on third-party CD-ROMs; see the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>The Debian FTP archives</quote>, for more information about the layout and contents of the archives." msgstr "" #. Tag: para -#: welcome.xml:550 +#: welcome.xml:591 #, no-c-format msgid "Many of the programs in the system are licensed under the <emphasis>GNU</emphasis> <emphasis>General Public License</emphasis>, often simply referred to as <quote>the GPL</quote>. The GPL requires you to make the <emphasis>source code</emphasis> of the programs available whenever you distribute a binary copy of the program; that provision of the license ensures that any user will be able to modify the software. Because of this provision, the source code<footnote> <para> For information on how to locate, unpack, and build binaries from Debian source packages, see the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>Basics of the Debian Package Management System</quote>. </para> </footnote> for all such programs is available in the Debian system." msgstr "" #. Tag: para -#: welcome.xml:569 +#: welcome.xml:610 #, no-c-format msgid "There are several other forms of copyright statements and software licenses used on the programs in Debian. You can find the copyrights and licenses for every package installed on your system by looking in the file <filename>/usr/share/doc/<replaceable>package-name</replaceable>/copyright </filename> once you've installed a package on your system." msgstr "" #. Tag: para -#: welcome.xml:579 +#: welcome.xml:620 #, no-c-format msgid "For more information about licenses and how Debian determines whether software is free enough to be included in the main distribution, see the <ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink>." msgstr "" #. Tag: para -#: welcome.xml:585 +#: welcome.xml:626 #, no-c-format msgid "The most important legal notice is that this software comes with <emphasis>no warranties</emphasis>. The programmers who have created this software have done so for the benefit of the community. No guarantee is made as to the suitability of the software for any given purpose. However, since the software is free, you are empowered to modify that software to suit your needs — and to enjoy the benefits of the changes made by others who have extended the software in this way." msgstr "" |