diff options
| author | Holger Wansing <linux@wansing-online.de> | 2015-04-15 20:43:58 +0000 |
|---|---|---|
| committer | Holger Wansing <linux@wansing-online.de> | 2015-04-15 20:43:58 +0000 |
| commit | 77481c858815c2e23a738ea8f9a357509c34cbd9 (patch) | |
| tree | 31f30a46732c48a7c472fe5bcde646de2279efff /po/pot | |
| parent | 00f642d6102e7a01d949a3ebaa6fb99218ba5da5 (diff) | |
| download | installation-guide-77481c858815c2e23a738ea8f9a357509c34cbd9.zip | |
Refresh po and pot files after changings in en
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 912 | ||||
| -rw-r--r-- | po/pot/boot-new.pot | 4 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 834 | ||||
| -rw-r--r-- | po/pot/install-methods.pot | 306 | ||||
| -rw-r--r-- | po/pot/partitioning.pot | 140 | ||||
| -rw-r--r-- | po/pot/post-install.pot | 14 | ||||
| -rw-r--r-- | po/pot/preparing.pot | 386 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 6 | ||||
| -rw-r--r-- | po/pot/random-bits.pot | 488 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 474 |
10 files changed, 1977 insertions, 1587 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 20c7a62eb..80fdbd9e9 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: 2015-03-22 13:58+0000\n" +"POT-Creation-Date: 2015-04-15 20:29+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" @@ -53,7 +53,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:47 #, no-c-format -msgid "uImage/uInitrd are image formats designed for the u-boot firmware that is used on many ARM-based systems. Older u-boot versions can only boot files in uImage/uInitrd format, so these are often used on older armel systems. Newer u-boot versions can - besides booting uImages/uInitrds - also boot standard Linux kernels and ramdisk images, but the command syntax to do that is slightly different from that for booting uImages." +msgid "uImage/uInitrd are image formats designed for the U-Boot firmware that is used on many ARM-based systems. Older U-Boot versions can only boot files in uImage/uInitrd format, so these are often used on older armel systems. Newer U-Boot versions can - besides booting uImages/uInitrds - also boot standard Linux kernels and ramdisk images, but the command syntax to do that is slightly different from that for booting uImages." msgstr "" #. Tag: para @@ -63,43 +63,61 @@ msgid "For systems using a multiplatform kernel, besides kernel and initial ramd msgstr "" #. Tag: title -#: boot-installer.xml:64 +#: boot-installer.xml:65 +#, no-c-format +msgid "Console configuration" +msgstr "" + +#. Tag: para +#: boot-installer.xml:66 +#, no-c-format +msgid "The netboot tarball (<xref linkend=\"boot-armhf-netboot.tar.gz\"/>), the hd-media tarball (<xref linkend=\"boot-hd-media\"/>) and the installer SD-card images (<xref linkend=\"boot-installer-sd-image\"/>) use the (platform-specific) default console that is defined by U-Boot in the <quote>console</quote> variable. In most cases that is a serial console, so on those platforms you by default need a serial console cable to use the installer." +msgstr "" + +#. Tag: para +#: boot-installer.xml:75 +#, no-c-format +msgid "On platforms which also support a video console, you can modify the U-Boot <quote>console</quote> variable accordingly if you would like the installer to start on the video console." +msgstr "" + +#. Tag: title +#: boot-installer.xml:82 #, no-c-format msgid "Booting by TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:70 boot-installer.xml:689 boot-installer.xml:1311 boot-installer.xml:1495 boot-installer.xml:1818 boot-installer.xml:1928 +#: boot-installer.xml:88 boot-installer.xml:727 boot-installer.xml:1362 boot-installer.xml:1546 boot-installer.xml:1868 boot-installer.xml:2016 #, no-c-format msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (and probably also a DHCP, RARP, or BOOTP server for automatic network configuration)." msgstr "" #. Tag: para -#: boot-installer.xml:76 boot-installer.xml:695 boot-installer.xml:1317 boot-installer.xml:1501 boot-installer.xml:1824 boot-installer.xml:1934 +#: boot-installer.xml:94 boot-installer.xml:733 boot-installer.xml:1368 boot-installer.xml:1552 boot-installer.xml:1874 boot-installer.xml:2022 #, 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:81 boot-installer.xml:700 boot-installer.xml:1322 boot-installer.xml:1506 boot-installer.xml:1829 boot-installer.xml:1939 +#: boot-installer.xml:99 boot-installer.xml:738 boot-installer.xml:1373 boot-installer.xml:1557 boot-installer.xml:1879 boot-installer.xml:2027 #, no-c-format msgid "The server-side setup to support network booting is described in <xref linkend=\"install-tftp\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:90 +#: boot-installer.xml:108 #, no-c-format -msgid "TFTP-booting in u-boot" +msgid "TFTP-booting in U-Boot" msgstr "" #. Tag: para -#: boot-installer.xml:91 +#: boot-installer.xml:109 #, no-c-format -msgid "Network booting on systems using the u-boot firmware consists of three steps: a) configuring the network, b) loading the images (kernel/initial ramdisk/dtb) into memory and c) actually executing the previosly loaded code." +msgid "Network booting on systems using the U-Boot firmware consists of three steps: a) configuring the network, b) loading the images (kernel/initial ramdisk/dtb) into memory and c) actually executing the previosly loaded code." msgstr "" #. Tag: para -#: boot-installer.xml:97 +#: boot-installer.xml:115 #, no-c-format msgid "" "First you have to configure the network, either automatically via DHCP by running <informalexample><screen>\n" @@ -115,28 +133,28 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:104 +#: boot-installer.xml:122 #, no-c-format msgid "saveenv" msgstr "" #. Tag: para -#: boot-installer.xml:106 +#: boot-installer.xml:124 #, no-c-format msgid "Afterwards you need to load the images (kernel/initial ramdisk/dtb) into memory. This is done with the tftpboot command, which has to be provided with the address at which the image shall be stored in memory. Unfortunately the memory map can vary from system to system, so there is no general rule which addresses can be used for this." msgstr "" #. Tag: para -#: boot-installer.xml:114 +#: boot-installer.xml:132 #, no-c-format msgid "" - "On some systems, u-boot predefines a set of environment variables with suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. You can check whether they are defined by running <informalexample><screen>\n" + "On some systems, U-Boot predefines a set of environment variables with suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. You can check whether they are defined by running <informalexample><screen>\n" "printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n" "</screen></informalexample> If they are not defined, you have to check your system's documentation for appropriate values and set them manually. For systems based on Allwinner SunXi SOCs (e.g. the Allwinner A10, architecture name <quote>sun4i</quote> or the Allwinner A20, architecture name <quote>sun7i</quote>), you can e.g. use the follwing values:" msgstr "" #. Tag: screen -#: boot-installer.xml:125 +#: boot-installer.xml:143 #, no-c-format msgid "" "setenv kernel_addr_r 0x46000000\n" @@ -145,13 +163,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:127 +#: boot-installer.xml:145 #, no-c-format msgid "When the load addresses are defined, you can load the images into memory from the previously defined tftp server with" msgstr "" #. Tag: screen -#: boot-installer.xml:130 +#: boot-installer.xml:148 #, no-c-format msgid "" "tftpboot ${kernel_addr_r} <filename of the kernel image>\n" @@ -160,10 +178,10 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:132 +#: boot-installer.xml:150 #, no-c-format msgid "" - "The third part is setting the kernel commandline and actually executing the loaded code. U-boot passes the content of the <quote>bootargs</quote> environment variable as commandline to the kernel, so any parameters for the kernel and the installer - such as the console device (see <xref linkend=\"boot-console\"/>) or preseeding options (see <xref linkend=\"installer-args\"/> and <xref linkend=\"appendix-preseed\"/>) - can be set with a command like <informalexample><screen>\n" + "The third part is setting the kernel commandline and actually executing the loaded code. U-Boot passes the content of the <quote>bootargs</quote> environment variable as commandline to the kernel, so any parameters for the kernel and the installer - such as the console device (see <xref linkend=\"boot-console\"/>) or preseeding options (see <xref linkend=\"installer-args\"/> and <xref linkend=\"appendix-preseed\"/>) - can be set with a command like <informalexample><screen>\n" "setenv bootargs console=ttyS0,115200 rootwait panic=10\n" "</screen></informalexample> The exact command to execute the previously loaded code depends on the image format used. With uImage/uInitrd, the command is <informalexample><screen>\n" "bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}\n" @@ -171,133 +189,215 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:145 +#: boot-installer.xml:163 #, no-c-format msgid "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}" msgstr "" #. Tag: para -#: boot-installer.xml:147 +#: boot-installer.xml:165 +#, no-c-format +msgid "Note: When booting standard linux images, it is important to load the initial ramdisk image after the kernel and the dtb as U-Boot sets the filesize variable to the size of the last file loaded and the bootz command requires the size of the ramdisk image to work correctly. In case of booting a platform-specific kernel, i.e. a kernel without device-tree, simply omit the ${fdt_addr_r} parameter." +msgstr "" + +#. Tag: title +#: boot-installer.xml:176 +#, no-c-format +msgid "Pre-built netboot tarball" +msgstr "" + +#. Tag: para +#: boot-installer.xml:177 +#, no-c-format +msgid "&debian; provides a pre-built tarball (&armmp-netboot-tarball;) that can simply be unpacked on your tftp server and contains all files necessary for netbooting. It also includes a boot script that automates all steps to load the installer. Modern U-Boot versions contain a tftp autoboot feature that becomes active if there is no bootable local storage device (MMC/SD, USB, IDE/SATA/SCSI) and then loads this boot script from the tftp server. Prerequisite for using this feature is that you have a dhcp server in your network which provides the client with the address of the tftp server." +msgstr "" + +#. Tag: para +#: boot-installer.xml:189 +#, no-c-format +msgid "If you would like to trigger the tftp autoboot feature from the U-Boot commandline, you can use the follwing command:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:192 +#, no-c-format +msgid "run bootcmd_dhcp" +msgstr "" + +#. Tag: para +#: boot-installer.xml:194 #, no-c-format -msgid "Note: When booting standard linux images, it is important to load the initial ramdisk image after the kernel and the dtb as u-boot sets the filesize variable to the size of the last file loaded and the bootz command requires the size of the ramdisk image to work correctly. In case of booting a platform-specific kernel, i.e. a kernel without device-tree, simply omit the ${fdt_addr_r} parameter." +msgid "To manually load the bootscript provided by the tarball, you can alternatively issue the following commands at the U-Boot prompt:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:198 +#, no-c-format +msgid "" + "setenv autoload no\n" + "dhcp\n" + "tftpboot ${scriptaddr} /debian-installer/armhf/tftpboot.scr\n" + "source ${scriptaddr}" msgstr "" #. Tag: title -#: boot-installer.xml:160 +#: boot-installer.xml:206 #, no-c-format -msgid "Booting from a USB stick in u-boot" +msgid "Booting from a USB stick in U-Boot" msgstr "" #. Tag: para -#: boot-installer.xml:161 +#: boot-installer.xml:207 #, no-c-format -msgid "Many modern u-boot versions have USB support and allow booting from USB mass storage devices such as USB sticks. Unfortunately the exact steps required to do that can vary quite a bit from device to device." +msgid "Many modern U-Boot versions have USB support and allow booting from USB mass storage devices such as USB sticks. Unfortunately the exact steps required to do that can vary quite a bit from device to device." msgstr "" #. Tag: para -#: boot-installer.xml:168 +#: boot-installer.xml:214 #, no-c-format msgid "U-Boot v2014.10 has introduced a common commandline handling and autoboot framework. This allows building generic boot images that work on any system implementing this framework. The &d-i; supports installation from a USB stick on such systems, but unfortunately not all platforms have adopted this new framework yet." msgstr "" #. Tag: para -#: boot-installer.xml:177 +#: boot-installer.xml:223 +#, no-c-format +msgid "To build a bootable USB stick for installing &debian;, unpack the hd-media tarball (see <xref linkend=\"where-files\"/>) onto a USB stick formatted with a filesystem supported by the U-Boot version on your device. For modern U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / ext4 usually works. Then copy the ISO image file of the first &debian; installation CD or DVD onto the stick." +msgstr "" + +#. Tag: para +#: boot-installer.xml:233 +#, no-c-format +msgid "The autoboot framework in modern U-Boot versions works similar to the boot ordering options in a PC BIOS, i.e. it checks a list of possible boot devices for a valid boot image and starts the first one it finds. If there is no operating system installed, plugging in the USB stick and powering up the system should result in starting the installer. You can also initiate the USB-boot process any time from the U-Boot prompt by entering the <quote>run bootcmd_usb0</quote> command." +msgstr "" + +#. Tag: para +#: boot-installer.xml:243 +#, no-c-format +msgid "One problem that can come up when booting from a USB stick while using a serial console can be a console baudrate mismatch. If a console variable is defined in U-Boot, the &d-i; boot script automatically passes it to the kernel to set the primary console device and, if applicable, the console baudrate. Unfortunately the handling of the console variable varies from platform to platform - on some platforms, the console variable includes the baudrate (as in <quote>console=ttyS0,115200</quote>), while on other platforms the console variable contains only the device (as in <quote>console=ttyS0</quote>). The latter case leads to a garbled console output when the default baudrate differs between U-Boot and the kernel. Modern U-Boot versions often use 115200 baud while the kernel still defaults to the traditional 9600 baud. If this happens, you should manually set the console variable to contain the correct baudrate for your system and then start the installer with the <quote>run bootcmd_usb0</quote> command." +msgstr "" + +#. Tag: title +#: boot-installer.xml:264 +#, no-c-format +msgid "Using pre-built SD-card images with the installer" +msgstr "" + +#. Tag: para +#: boot-installer.xml:265 #, no-c-format -msgid "To build a bootable USB stick for installing &debian;, unpack the hd-media tarball (see <xref linkend=\"where-files\"/>) onto a USB stick formatted with a filesystem supported by the u-boot version on your device. For modern u-boot versions, any of FAT16 / FAT32 / ext2 / ext3 / ext4 usually works. Then copy the ISO image file of the first &debian; installation CD or DVD onto the stick." +msgid "For a number of systems, Debian provides SD card images that contain both U-Boot and the &d-i;. These images are provided in two variants - one for downloading the software packages over the network (available at &armmp-netboot-sd-img;) and one for offline installations using a Debian CD/DVD (available at &armmp-hd-media-sd-img;). To save space and network bandwidth, the images consist of two parts - a system-dependent part named <quote>firmware.<system-type>.img.gz</quote>, and a system-independent part named <quote>partition.img.gz</quote>." msgstr "" #. Tag: para -#: boot-installer.xml:187 +#: boot-installer.xml:276 #, no-c-format -msgid "The autoboot framework in modern u-boot versions works similar to the boot ordering options in a PC BIOS, i.e. it checks a list of possible boot devices for a valid boot image and starts the first one it finds. If there is no operating system installed, plugging in the USB stick and powering up the system should result in starting the installer. You can also initiate the USB-boot process any time from the u-boot prompt by entering the <quote>run bootcmd_usb0</quote> command." +msgid "To create a complete image from the two parts on Linux systems, you can use zcat as follows: <informalexample><screen>zcat firmware.<system-type>.img.gz partition.img.gz > complete_image.img</screen></informalexample> On Windows systems, you have to first decompress the two parts separately, which can be done e.g. by using 7-Zip, and then concatenate the decompressed parts together by running the command <informalexample><screen>copy /b firmware.<system-type>.img + partition.img complete_image.img</screen></informalexample> in a Windows CMD.exe window." msgstr "" #. Tag: para -#: boot-installer.xml:197 +#: boot-installer.xml:290 #, no-c-format -msgid "One problem that can come up when booting from a USB stick while using a serial console can be a console baudrate mismatch. If a console variable is defined in u-boot, the &d-i; boot script automatically passes it to the kernel to set the primary console device and, if applicable, the console baudrate. Unfortunately the handling of the console variable varies from platform to platform - on some platforms, the console variable includes the baudrate (as in <quote>console=ttyS0,115200</quote>), while on other platforms the console variable contains only the device (as in <quote>console=ttyS0</quote>). The latter case leads to a garbled console output when the default baudrate differs between u-boot and the kernel. Modern u-boot versions often use 115200 baud while the kernel still defaults to the traditional 9600 baud. If this happens, you should manually set the console variable to contain the correct baudrate for your system and then start the installer with the <quote>run bootcmd_usb0</quote> command." +msgid "Write the resulting image onto an SD card, e.g. by running the following command on a Linux system: <informalexample><screen>cat complete_image.img > /dev/SD_CARD_DEVICE</screen></informalexample> After plugging the SD card into the target system and powering the system up, the installer is loaded from the SD card. If you use the hd-media variant for offline installations, you must provide the installer with access to the first &debian; CD/DVD on a separate medium, which can e.g. be a CD/DVD ISO image on a USB stick." +msgstr "" + +#. Tag: para +#: boot-installer.xml:302 +#, no-c-format +msgid "When you come to the partitioning step in the installer (see <xref linkend=\"di-partition\"/>), you can delete or replace any previous partitions on the card. Once the installer is started, it runs completely in the system's main memory and does not need to access the SD card anymore, so you can use the full card for installing &debian;. The easiest way to create a proper partition layout on the SD card is to let the installer automatically create one for you (see <xref linkend=\"partman-auto\"/>)." msgstr "" #. Tag: title -#: boot-installer.xml:345 boot-installer.xml:924 boot-installer.xml:1581 boot-installer.xml:1962 +#: boot-installer.xml:443 +#, no-c-format +msgid "Booting from USB Memory Stick" +msgstr "" + +#. Tag: para +#: boot-installer.xml:449 +#, no-c-format +msgid "If your computer will boot from USB, this will probably be the easiest route for installation. Assuming you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>, just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and unless you have used the flexible way to build the stick and not enabled it, you should be presented with a graphical boot menu. Here you can select various installer options, or just hit &enterkey;." +msgstr "" + +#. Tag: title +#: boot-installer.xml:463 boot-installer.xml:976 boot-installer.xml:1632 boot-installer.xml:2050 #, no-c-format msgid "Booting from a CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:351 boot-installer.xml:930 boot-installer.xml:1587 boot-installer.xml:1968 +#: boot-installer.xml:469 boot-installer.xml:982 boot-installer.xml:1638 boot-installer.xml:2056 #, 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." +msgid "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:362 boot-installer.xml:941 boot-installer.xml:1598 boot-installer.xml:1979 +#: boot-installer.xml:479 boot-installer.xml:992 boot-installer.xml:1648 boot-installer.xml:2066 #, 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:370 boot-installer.xml:949 boot-installer.xml:1606 boot-installer.xml:1987 +#: boot-installer.xml:487 boot-installer.xml:1000 boot-installer.xml:1656 boot-installer.xml:2074 #, 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 medium and 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:378 boot-installer.xml:957 boot-installer.xml:1614 boot-installer.xml:1995 +#: boot-installer.xml:495 boot-installer.xml:1008 boot-installer.xml:1664 boot-installer.xml:2082 #, no-c-format msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:452 +#: boot-installer.xml:505 #, no-c-format msgid "Booting from Windows" msgstr "" #. Tag: para -#: boot-installer.xml:453 +#: boot-installer.xml:506 #, no-c-format msgid "To start the installer from Windows, you can either" msgstr "" #. Tag: para -#: boot-installer.xml:458 +#: boot-installer.xml:511 #, no-c-format msgid "obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory stick</phrase> installation media as described in <xref linkend=\"official-cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-usb-files\"/></phrase> or" msgstr "" #. Tag: para -#: boot-installer.xml:466 +#: boot-installer.xml:519 #, no-c-format msgid "download a standalone Windows executable, which is available as tools/win32-loader/stable/win32-loader.exe on the &debian; mirrors." msgstr "" #. Tag: para -#: boot-installer.xml:474 +#: boot-installer.xml:527 #, no-c-format msgid "If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing <command>setup.exe</command>." msgstr "" #. Tag: para -#: boot-installer.xml:482 +#: boot-installer.xml:535 #, no-c-format msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to reboot into the &debian-gnu; installer." msgstr "" #. Tag: title -#: boot-installer.xml:492 +#: boot-installer.xml:545 #, no-c-format msgid "Booting from DOS using loadlin" msgstr "" #. Tag: para -#: boot-installer.xml:493 +#: boot-installer.xml:546 #, 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:498 +#: boot-installer.xml:551 #, 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" @@ -306,7 +406,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:508 +#: boot-installer.xml:561 #, no-c-format msgid "" "Enter the subdirectory for the flavor you chose, e.g., <informalexample><screen>\n" @@ -317,37 +417,37 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:526 +#: boot-installer.xml:579 #, no-c-format msgid "Booting from Linux using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: boot-installer.xml:529 +#: boot-installer.xml:582 #, 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:534 +#: boot-installer.xml:587 #, 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:544 +#: boot-installer.xml:597 #, 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:553 +#: boot-installer.xml:606 #, 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:574 +#: boot-installer.xml:627 #, no-c-format msgid "" "image=/boot/newinstall/vmlinuz\n" @@ -356,19 +456,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:574 +#: boot-installer.xml:627 #, 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:583 +#: boot-installer.xml:636 #, no-c-format msgid "The procedure for <command>GRUB1</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an entry for the installer, for example (assuming <filename>/boot</filename> is on the first partition of the first disk in the system):" msgstr "" #. Tag: screen -#: boot-installer.xml:591 +#: boot-installer.xml:644 #, no-c-format msgid "" "title New Install\n" @@ -378,13 +478,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:593 +#: boot-installer.xml:646 #, no-c-format msgid "The procedure for <command>GRUB2</command> is very similar. The file is named <filename>grub.cfg</filename> instead of <filename>menu.lst</filename>. An entry for the installer would be for instance for example:" msgstr "" #. Tag: screen -#: boot-installer.xml:599 +#: boot-installer.xml:652 #, no-c-format msgid "" "menuentry 'New Install' {\n" @@ -397,168 +497,170 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:601 +#: boot-installer.xml:654 #, 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:610 -#, no-c-format -msgid "Booting from USB Memory Stick" -msgstr "" - -#. Tag: para -#: boot-installer.xml:611 -#, no-c-format -msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and unless you have used the flexible way to build the stick and not enabled it, you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;." -msgstr "" - -#. Tag: title -#: boot-installer.xml:625 boot-installer.xml:1868 +#: boot-installer.xml:663 boot-installer.xml:1918 #, no-c-format msgid "Booting from Floppies" msgstr "" #. Tag: para -#: boot-installer.xml:626 boot-installer.xml:1876 +#: boot-installer.xml:664 boot-installer.xml:1926 #, 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:633 +#: boot-installer.xml:671 #, 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:639 +#: boot-installer.xml:677 #, 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:649 +#: boot-installer.xml:687 #, 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:658 +#: boot-installer.xml:696 #, 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:664 +#: boot-installer.xml:702 #, 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:673 +#: boot-installer.xml:711 #, 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:683 boot-installer.xml:1293 boot-installer.xml:1435 boot-installer.xml:1489 boot-installer.xml:1812 boot-installer.xml:1922 +#: boot-installer.xml:721 boot-installer.xml:1344 boot-installer.xml:1486 boot-installer.xml:1540 boot-installer.xml:1862 boot-installer.xml:2010 #, no-c-format msgid "Booting with TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:708 +#: boot-installer.xml:746 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "" #. Tag: title -#: boot-installer.xml:714 +#: boot-installer.xml:752 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "" #. Tag: para -#: boot-installer.xml:715 +#: boot-installer.xml:753 #, 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:726 +#: boot-installer.xml:764 #, no-c-format msgid "NIC with Network BootROM" msgstr "" #. Tag: para -#: boot-installer.xml:727 +#: boot-installer.xml:765 #, no-c-format msgid "It could be that your Network Interface Card provides TFTP boot functionality." msgstr "" #. Tag: para -#: boot-installer.xml:732 +#: boot-installer.xml:770 #, 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:740 +#: boot-installer.xml:778 #, no-c-format msgid "Etherboot" msgstr "" #. Tag: para -#: boot-installer.xml:741 +#: boot-installer.xml:779 #, 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:751 +#: boot-installer.xml:789 #, no-c-format msgid "The Boot Screen" msgstr "" #. Tag: para -#: boot-installer.xml:752 +#: boot-installer.xml:790 +#, no-c-format +msgid "When the installer boots, you should be presented with a friendly graphical screen showing the &debian; logo and a menu:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:795 #, 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" "Installer boot menu\n" "\n" "Install\n" "Graphical install\n" "Advanced options >\n" "Help\n" - "Install with speech synthesis\n" - "\n" - "Press ENTER to boot or TAB to edit a menu entry\n" - "</screen></informalexample> Depending on the installation method you are using, the <quote>Graphical install</quote> option may not be available. Bi-arch images additionally have a 64 bit variant for each install option, right below it, thus almost doubling the number of options." + "Install with speech synthesis" msgstr "" #. Tag: para -#: boot-installer.xml:764 +#: boot-installer.xml:799 +#, no-c-format +msgid "This graphical screen will look very slightly different depending on how your computer has booted (BIOS or UEFI), but the same options will be shown." +msgstr "" + +#. Tag: para +#: boot-installer.xml:807 +#, no-c-format +msgid "Depending on the installation method you are using, the <quote>Graphical install</quote> option may not be available. Bi-arch images additionally have a 64 bit variant for each install option, right below it, thus almost doubling the number of options." +msgstr "" + +#. Tag: para +#: boot-installer.xml:814 #, no-c-format msgid "For a normal installation, select either the <quote>Graphical install</quote> or the <quote>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. The <quote>Graphical install</quote> entry is already selected by default." msgstr "" #. Tag: para -#: boot-installer.xml:772 +#: boot-installer.xml:822 #, 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:778 +#: boot-installer.xml:828 #, 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." +msgid "If you wish or need to add any boot parameters for either the installer or the kernel, press &tabkey; (BIOS boot) or &ekey; (UEFI boot). This will display the boot command for the selected menu entry and allow you to edit it to suit your needs. The help screens (see below) list some common possible options. Press &enterkey; (BIOS boot) or &f10key; (UEFI boot) 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:787 +#: boot-installer.xml:839 #, no-c-format msgid "" "Choosing the <quote>Help</quote> entry will result in the first help screen being displayed which gives an overview of all available help screens. To return to the boot menu after the help screens have been displayed, type 'menu' at the boot prompt and press &enterkey;. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>\n" @@ -567,313 +669,313 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:805 +#: boot-installer.xml:857 #, 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:815 +#: boot-installer.xml:867 #, 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:825 +#: boot-installer.xml:877 #, 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:841 +#: boot-installer.xml:893 #, no-c-format msgid "The Graphical Installer" msgstr "" #. Tag: para -#: boot-installer.xml:842 +#: boot-installer.xml:894 #, 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 text-based installer as it basically uses the same programs, but with a different frontend." msgstr "" #. Tag: para -#: boot-installer.xml:850 +#: boot-installer.xml:902 #, 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 text-based <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 -#: boot-installer.xml:859 +#: boot-installer.xml:911 #, 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 -#: boot-installer.xml:870 +#: boot-installer.xml:922 #, 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 -#: boot-installer.xml:883 +#: boot-installer.xml:935 #, 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 -#: boot-installer.xml:897 +#: boot-installer.xml:949 #, no-c-format msgid "Just as with the text-based installer it is possible to add boot parameters when starting the graphical installer." msgstr "" #. Tag: para -#: boot-installer.xml:903 +#: boot-installer.xml:955 #, no-c-format msgid "The graphical installer requires significantly more memory to run than the text-based installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the text-based <quote>newt</quote> frontend." msgstr "" #. Tag: para -#: boot-installer.xml:910 +#: boot-installer.xml:962 #, 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 text-based installer would still work. Using the text-based installer is recommended for systems with little available memory." msgstr "" #. Tag: title -#: boot-installer.xml:965 +#: boot-installer.xml:1016 #, no-c-format msgid "CD Contents" msgstr "" #. Tag: para -#: boot-installer.xml:967 +#: boot-installer.xml:1018 #, 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:983 +#: boot-installer.xml:1034 #, 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:999 +#: boot-installer.xml:1050 #, 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:1008 +#: boot-installer.xml:1059 #, 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:1020 +#: boot-installer.xml:1071 #, 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:1039 +#: boot-installer.xml:1090 #, no-c-format msgid "IMPORTANT" msgstr "" #. Tag: para -#: boot-installer.xml:1040 +#: boot-installer.xml:1091 #, 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:1052 +#: boot-installer.xml:1103 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "" #. Tag: para -#: boot-installer.xml:1059 +#: boot-installer.xml:1110 #, 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:1065 +#: boot-installer.xml:1116 #, 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:1071 +#: boot-installer.xml:1122 #, 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:1082 +#: boot-installer.xml:1133 #, 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:1093 +#: boot-installer.xml:1144 #, 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:1105 +#: boot-installer.xml:1156 #, 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:1115 +#: boot-installer.xml:1166 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "" #. Tag: para -#: boot-installer.xml:1116 +#: boot-installer.xml:1167 #, 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:1127 +#: boot-installer.xml:1178 #, 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:1133 +#: boot-installer.xml:1184 #, 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:1147 +#: boot-installer.xml:1198 #, 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:1154 +#: boot-installer.xml:1205 #, 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:1161 +#: boot-installer.xml:1212 #, 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:1168 +#: boot-installer.xml:1219 #, 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:1182 +#: boot-installer.xml:1233 #, no-c-format msgid "Installing using a Serial Console" msgstr "" #. Tag: para -#: boot-installer.xml:1184 +#: boot-installer.xml:1235 #, 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:1195 +#: boot-installer.xml:1246 #, 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:1202 +#: boot-installer.xml:1253 #, 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:1213 +#: boot-installer.xml:1264 #, 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:1222 +#: boot-installer.xml:1273 #, 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:1231 +#: boot-installer.xml:1282 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "" #. Tag: para -#: boot-installer.xml:1233 +#: boot-installer.xml:1284 #, 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:1245 +#: boot-installer.xml:1296 #, 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:1263 +#: boot-installer.xml:1314 #, 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:1268 +#: boot-installer.xml:1319 #, 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:1275 +#: boot-installer.xml:1326 #, 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:1284 boot-installer.xml:1421 +#: boot-installer.xml:1335 boot-installer.xml:1472 #, 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:1295 +#: boot-installer.xml:1346 #, 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:1330 +#: boot-installer.xml:1381 #, 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:1341 +#: boot-installer.xml:1392 #, no-c-format msgid "Configuring the Server" msgstr "" #. Tag: para -#: boot-installer.xml:1342 +#: boot-installer.xml:1393 #, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n" @@ -886,13 +988,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1352 +#: boot-installer.xml:1403 #, 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:1362 +#: boot-installer.xml:1413 #, no-c-format msgid "" "# cd /var/lib/tftp\n" @@ -904,37 +1006,37 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1362 +#: boot-installer.xml:1413 #, 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:1379 +#: boot-installer.xml:1430 #, no-c-format msgid "Configuring the Client" msgstr "" #. Tag: para -#: boot-installer.xml:1380 +#: boot-installer.xml:1431 #, 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:1412 +#: boot-installer.xml:1463 #, 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:1438 boot-installer.xml:1462 +#: boot-installer.xml:1489 boot-installer.xml:1513 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:1439 +#: boot-installer.xml:1490 #, no-c-format msgid "" "After entering the command monitor use <informalexample><screen>\n" @@ -945,19 +1047,19 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:1459 boot-installer.xml:2214 +#: boot-installer.xml:1510 boot-installer.xml:2301 #, no-c-format msgid "Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1463 +#: boot-installer.xml:1514 #, 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:1468 +#: boot-installer.xml:1519 #, 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" @@ -966,43 +1068,43 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:1478 +#: boot-installer.xml:1529 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: title -#: boot-installer.xml:1521 +#: boot-installer.xml:1572 #, no-c-format msgid "s390 Limitations" msgstr "" #. Tag: para -#: boot-installer.xml:1522 +#: boot-installer.xml:1573 #, 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:1527 +#: boot-installer.xml:1578 #, 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:1538 +#: boot-installer.xml:1589 #, no-c-format msgid "s390 Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1539 +#: boot-installer.xml:1590 #, 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. It needs to be fixed-width with 80 characters per line. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images. If a parameter is too long to fit into the 80 characters limit it can simply be continued in the first column of the next line. All the lines are concatenated without spaces when being passed to the kernel." msgstr "" #. Tag: para -#: boot-installer.xml:1556 +#: boot-installer.xml:1607 #, no-c-format msgid "" "If you boot the installer in a logical partition (LPAR) or virtual machine (VM) where a lot of devices are visible, you can instruct the kernel to restrict the list to a fixed set of devices. This is advised for the installer's boot process if a lot of disks are visible, most likely in LPAR mode. The <quote>cio_ignore</quote> option supports both a blacklist (to only disallow a few devices) and a whitelist (to only allow specific devices): <informalexample role=\"example\"><screen>\n" @@ -1014,13 +1116,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1621 +#: boot-installer.xml:1671 #, no-c-format msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP/CHRP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the factory default CD/DVD drive." msgstr "" #. Tag: para -#: boot-installer.xml:1630 +#: boot-installer.xml:1680 #, no-c-format msgid "" "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then type <informalexample><screen>\n" @@ -1029,79 +1131,79 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:1641 +#: boot-installer.xml:1691 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "" #. Tag: para -#: boot-installer.xml:1643 +#: boot-installer.xml:1693 #, 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:1652 +#: boot-installer.xml:1702 #, no-c-format msgid "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key immediately after pressing the power-on button, when SmartFirmware prompt appears, type" msgstr "" #. Tag: screen -#: boot-installer.xml:1658 +#: boot-installer.xml:1708 #, no-c-format msgid "boot cd install/pegasos" msgstr "" #. Tag: para -#: boot-installer.xml:1660 +#: boot-installer.xml:1710 #, no-c-format msgid "On YDL Powerstation machine, pres <keycap>s</keycap> immediately after <quote>Press 's' to enter Open Firmware</quote> message, when SLOF prompt appears type" msgstr "" #. Tag: screen -#: boot-installer.xml:1665 +#: boot-installer.xml:1715 #, no-c-format msgid "0 > boot cdrom" msgstr "" #. Tag: title -#: boot-installer.xml:1671 +#: boot-installer.xml:1721 #, no-c-format msgid "Booting from Hard Disk" msgstr "" #. Tag: para -#: boot-installer.xml:1677 +#: boot-installer.xml:1727 #, 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:1683 +#: boot-installer.xml:1733 #, 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:1703 +#: boot-installer.xml:1753 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" #. Tag: para -#: boot-installer.xml:1704 +#: boot-installer.xml:1754 #, 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:1722 +#: boot-installer.xml:1772 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" #. Tag: para -#: boot-installer.xml:1723 +#: boot-installer.xml:1773 #, 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" @@ -1112,31 +1214,31 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:1755 +#: boot-installer.xml:1805 #, no-c-format msgid "Booting from USB memory stick" msgstr "" #. Tag: para -#: boot-installer.xml:1756 +#: boot-installer.xml:1806 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" #. Tag: para -#: boot-installer.xml:1762 +#: boot-installer.xml:1812 #, 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:1771 +#: boot-installer.xml:1821 #, 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:1783 +#: boot-installer.xml:1833 #, no-c-format msgid "" "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n" @@ -1145,25 +1247,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1797 +#: boot-installer.xml:1847 #, 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:1803 +#: boot-installer.xml:1853 #, 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:1837 +#: boot-installer.xml:1887 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" #. Tag: para -#: boot-installer.xml:1841 +#: boot-installer.xml:1891 #, 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" @@ -1176,751 +1278,781 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1869 +#: boot-installer.xml:1919 #, 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:1881 +#: boot-installer.xml:1931 #, 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:1887 +#: boot-installer.xml:1937 #, 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:1894 +#: boot-installer.xml:1944 #, 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:1905 +#: boot-installer.xml:1955 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1906 +#: boot-installer.xml:1956 #, 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: title +#: boot-installer.xml:1968 +#, no-c-format +msgid "Booting a ppc64el machine" +msgstr "" + #. Tag: para -#: boot-installer.xml:1947 +#: boot-installer.xml:1969 +#, no-c-format +msgid "How to boot a ppc64el machine:" +msgstr "" + +#. Tag: title +#: boot-installer.xml:1975 +#, no-c-format +msgid "Petitboot" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1976 +#, no-c-format +msgid "Petitboot is a platform independent bootloader based on the Linux kexec. Petitboot supports loading kernel, initrd and device tree files from any Linux mountable filesystem, plus can load files from the network using the FTP, SFTP, TFTP, NFS, HTTP and HTTPS protocols. Petitboot can boot any operating system that includes kexec boot support." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1984 +#, no-c-format +msgid "Petitboot looks for bootloader configuration files on mountable devices in the system, and can also be configured to use boot information from a DHCP server." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2035 #, 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:2002 +#: boot-installer.xml:2089 #, 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:2011 +#: boot-installer.xml:2098 #, no-c-format msgid "IDPROM Messages" msgstr "" #. Tag: para -#: boot-installer.xml:2012 +#: boot-installer.xml:2099 #, 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:2031 +#: boot-installer.xml:2118 #, no-c-format msgid "Accessibility" msgstr "" #. Tag: para -#: boot-installer.xml:2032 +#: boot-installer.xml:2119 #, no-c-format -msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features<phrase arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard." +msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;ppc64el;x86\">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features<phrase arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard." msgstr "" #. Tag: title -#: boot-installer.xml:2052 +#: boot-installer.xml:2139 #, no-c-format msgid "Installer front-end" msgstr "" #. Tag: para -#: boot-installer.xml:2053 +#: boot-installer.xml:2140 #, no-c-format msgid "The &debian; installer supports several front-ends for asking questions, with varying convenience for accessibility: notably, <userinput>text</userinput> uses plain text while <userinput>newt</userinput> uses text-based dialog boxes. The choice can be made at the boot prompt, see the documentation for <userinput>DEBIAN_FRONTEND</userinput> in <xref linkend=\"installer-args\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:2065 +#: boot-installer.xml:2152 #, no-c-format msgid "USB Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:2066 +#: boot-installer.xml:2153 #, 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:2081 +#: boot-installer.xml:2168 #, no-c-format msgid "Serial Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:2082 +#: boot-installer.xml:2169 #, no-c-format msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the <userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> boot parameter to tell <classname>brltty</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the two-letter driver code for your terminal (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be replaced by the name of the serial port the display is connected to, <userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> can be typically used when using a serial-to-USB converter. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:2105 boot-installer.xml:3114 +#: boot-installer.xml:2192 boot-installer.xml:3201 #, no-c-format msgid "Software Speech Synthesis" msgstr "" #. Tag: para -#: boot-installer.xml:2106 +#: boot-installer.xml:2193 #, no-c-format msgid "Support for software speech synthesis is available on all installer images which have the graphical installer, i.e. all netinst, CD and DVD images, and the netboot gtk variant. It can be activated by selecting it in the boot menu by typing <userinput>s</userinput> &enterkey;. The textual version of the installer will then be automatically selected, and support for software speech synthesis will be automatically installed on the target system." msgstr "" #. Tag: para -#: boot-installer.xml:2115 +#: boot-installer.xml:2202 #, no-c-format msgid "The first question (language) is spoken in english, and the remainder of installation is spoken in the selected language (if available in <classname>espeak</classname>)." msgstr "" #. Tag: para -#: boot-installer.xml:2121 +#: boot-installer.xml:2208 #, no-c-format msgid "The default speech rate is quite slow. To make it faster, press <keycombo><keycap>CapsLock</keycap><keycap>6</keycap></keycombo>. To make it slower, press <keycombo><keycap>CapsLock</keycap><keycap>5</keycap></keycombo>. The default volume should be medium. To make it louder, press <keycombo><keycap>CapsLock</keycap><keycap>2</keycap></keycombo>. To make it quieter, press <keycombo><keycap>CapsLock</keycap><keycap>1</keycap></keycombo>. To get more details on the browsing shortcuts, see the <ulink url=\"&url-speakup-guide;\">Speakup guide</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:2140 +#: boot-installer.xml:2227 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: boot-installer.xml:2141 +#: boot-installer.xml:2228 #, no-c-format msgid "Support for hardware speech synthesis devices is available on all installer images which have the graphical installer, i.e. all netinst, CD and DVD images, and the netboot gtk variant. You thus need to select a <quote>Graphical install</quote> entry in the boot menu." msgstr "" #. Tag: para -#: boot-installer.xml:2148 +#: boot-installer.xml:2235 #, 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-guide;\">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:2163 +#: boot-installer.xml:2250 #, no-c-format msgid "Board Devices" msgstr "" #. Tag: para -#: boot-installer.xml:2164 +#: boot-installer.xml:2251 #, 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:2172 +#: boot-installer.xml:2259 #, 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:2180 +#: boot-installer.xml:2267 #, no-c-format msgid "High-Contrast Theme" msgstr "" #. Tag: para -#: boot-installer.xml:2181 +#: boot-installer.xml:2268 #, no-c-format msgid "For users with low vision, the installer can use a high-contrast color theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter." msgstr "" #. Tag: title -#: boot-installer.xml:2190 +#: boot-installer.xml:2277 #, no-c-format msgid "Preseeding" msgstr "" #. Tag: para -#: boot-installer.xml:2191 +#: boot-installer.xml:2278 #, no-c-format msgid "Alternatively, &debian; can be installed completely automatically by using preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:2199 +#: boot-installer.xml:2286 #, no-c-format msgid "Accessibility of the installed system" msgstr "" #. Tag: para -#: boot-installer.xml:2200 +#: boot-installer.xml:2287 #, no-c-format msgid "Documentation on accessibility of the installed system is available on the <ulink url=\"&url-debian-wiki-accessibility;\">Debian Accessibility wiki page</ulink>." msgstr "" #. Tag: para -#: boot-installer.xml:2215 +#: boot-installer.xml:2302 #, 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:2222 +#: boot-installer.xml:2309 #, 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:2229 +#: boot-installer.xml:2316 #, 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: title -#: boot-installer.xml:2241 +#: boot-installer.xml:2328 #, no-c-format msgid "Boot console" msgstr "" #. Tag: para -#: boot-installer.xml:2243 +#: boot-installer.xml:2330 #, no-c-format msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:2255 +#: boot-installer.xml:2342 #, no-c-format msgid "You may need to specify parameters for the serial port, such as speed and parity, for instance <userinput>console=ttyS0,9600n8</userinput>; other typical speeds may be 57600 or 115200. Be sure to specify this option after <quote>---</quote>, so that it is copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader)." msgstr "" #. Tag: para -#: boot-installer.xml:2263 +#: boot-installer.xml:2350 #, no-c-format msgid "In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter <userinput>TERM=<replaceable>type</replaceable></userinput> can be added. Note that the installer only supports the following terminal types: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> and <literal>dumb</literal>. The default for serial console in &d-i; is <userinput>vt102</userinput>. If you are using a virtualization tool which does not provide conversion into such terminals types itself, e.g. QEMU/KVM, you can start it inside a <command>screen</command> session. That will indeed perform translation into the <literal>screen</literal> terminal type, which is very close to <literal>vt102</literal>." msgstr "" #. Tag: para -#: boot-installer.xml:2279 +#: boot-installer.xml:2366 #, 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:2291 +#: boot-installer.xml:2378 #, no-c-format msgid "&debian; Installer Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2292 +#: boot-installer.xml:2379 #, 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:2305 +#: boot-installer.xml:2392 #, 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:2317 +#: boot-installer.xml:2404 #, no-c-format msgid "debconf/priority (priority)" msgstr "" #. Tag: para -#: boot-installer.xml:2318 +#: boot-installer.xml:2405 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" #. Tag: para -#: boot-installer.xml:2322 +#: boot-installer.xml:2409 #, 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:2329 +#: boot-installer.xml:2416 #, 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:2343 +#: boot-installer.xml:2430 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para -#: boot-installer.xml:2344 +#: boot-installer.xml:2431 #, no-c-format msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Some specialized types of install media may only offer a limited selection of frontends, but the <userinput>newt</userinput> and <userinput>text</userinput> frontends are available on most default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend." msgstr "" #. Tag: term -#: boot-installer.xml:2375 +#: boot-installer.xml:2462 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:2376 +#: boot-installer.xml:2463 #, 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:2385 +#: boot-installer.xml:2472 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:2386 +#: boot-installer.xml:2473 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:2390 +#: boot-installer.xml:2477 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:2391 +#: boot-installer.xml:2478 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:2395 +#: boot-installer.xml:2482 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:2396 +#: boot-installer.xml:2483 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:2400 +#: boot-installer.xml:2487 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:2401 +#: boot-installer.xml:2488 #, 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:2415 +#: boot-installer.xml:2502 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:2416 +#: boot-installer.xml:2503 #, 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:2422 +#: boot-installer.xml:2509 #, 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:2433 +#: boot-installer.xml:2520 #, no-c-format msgid "log_host" msgstr "" #. Tag: term -#: boot-installer.xml:2434 +#: boot-installer.xml:2521 #, no-c-format msgid "log_port" msgstr "" #. Tag: para -#: boot-installer.xml:2435 +#: boot-installer.xml:2522 #, no-c-format msgid "Causes the installer to send log messages to a remote syslog on the specified host and port as well as to a local file. If not specified, the port defaults to the standard syslog port 514." msgstr "" #. Tag: term -#: boot-installer.xml:2446 +#: boot-installer.xml:2533 #, no-c-format msgid "lowmem" msgstr "" #. Tag: para -#: boot-installer.xml:2447 +#: boot-installer.xml:2534 #, 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:2457 +#: boot-installer.xml:2544 #, no-c-format msgid "noshell" msgstr "" #. Tag: para -#: boot-installer.xml:2458 +#: boot-installer.xml:2545 #, 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:2467 +#: boot-installer.xml:2554 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "" #. Tag: para -#: boot-installer.xml:2468 +#: boot-installer.xml:2555 #, 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:2477 +#: boot-installer.xml:2564 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:2481 +#: boot-installer.xml:2568 #, 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:2495 +#: boot-installer.xml:2582 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "" #. Tag: para -#: boot-installer.xml:2496 +#: boot-installer.xml:2583 #, 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:2508 boot-installer.xml:2741 +#: boot-installer.xml:2595 boot-installer.xml:2828 #, no-c-format msgid "netcfg/disable_autoconfig" msgstr "" #. Tag: para -#: boot-installer.xml:2509 +#: boot-installer.xml:2596 #, no-c-format msgid "By default, the &d-i; automatically probes for network configuration via IPv6 autoconfiguration and 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 automatic configuration fails." msgstr "" #. Tag: para -#: boot-installer.xml:2516 +#: boot-installer.xml:2603 #, no-c-format msgid "If you have an IPv6 router or a DHCP server on your local network, but want to avoid them because e.g. they give wrong answers, you can use the parameter <userinput>netcfg/disable_autoconfig=true</userinput> to prevent any automatic configuration of the network (neither v4 nor v6) and to enter the information manually." msgstr "" #. Tag: term -#: boot-installer.xml:2527 +#: boot-installer.xml:2614 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:2528 +#: boot-installer.xml:2615 #, 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:2538 +#: boot-installer.xml:2625 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "" #. Tag: para -#: boot-installer.xml:2539 +#: boot-installer.xml:2626 #, 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:2550 +#: boot-installer.xml:2637 #, no-c-format msgid "preseed/url (url)" msgstr "" #. Tag: para -#: boot-installer.xml:2551 +#: boot-installer.xml:2638 #, 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:2560 +#: boot-installer.xml:2647 #, no-c-format msgid "preseed/file (file)" msgstr "" #. Tag: para -#: boot-installer.xml:2561 +#: boot-installer.xml:2648 #, 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:2570 +#: boot-installer.xml:2657 #, no-c-format msgid "preseed/interactive" msgstr "" #. Tag: para -#: boot-installer.xml:2571 +#: boot-installer.xml:2658 #, 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:2583 +#: boot-installer.xml:2670 #, no-c-format msgid "auto-install/enable (auto)" msgstr "" #. Tag: para -#: boot-installer.xml:2584 +#: boot-installer.xml:2671 #, 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:2595 +#: boot-installer.xml:2682 #, no-c-format msgid "finish-install/keep-consoles" msgstr "" #. Tag: para -#: boot-installer.xml:2596 +#: boot-installer.xml:2683 #, 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:2607 +#: boot-installer.xml:2694 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:2608 +#: boot-installer.xml:2695 #, 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:2617 +#: boot-installer.xml:2704 #, 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:2628 +#: boot-installer.xml:2715 #, no-c-format msgid "base-installer/install-recommends (recommends)" msgstr "" #. Tag: para -#: boot-installer.xml:2629 +#: boot-installer.xml:2716 #, 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:2636 +#: boot-installer.xml:2723 #, 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:2648 +#: boot-installer.xml:2735 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "" #. Tag: para -#: boot-installer.xml:2649 +#: boot-installer.xml:2736 #, 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:2660 +#: boot-installer.xml:2747 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:2661 +#: boot-installer.xml:2748 #, 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:2671 +#: boot-installer.xml:2758 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:2672 +#: boot-installer.xml:2759 #, 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:2685 +#: boot-installer.xml:2772 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para -#: boot-installer.xml:2686 +#: boot-installer.xml:2773 #, 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:2698 +#: boot-installer.xml:2785 #, no-c-format msgid "debian-installer/language (language)" msgstr "" #. Tag: term -#: boot-installer.xml:2699 +#: boot-installer.xml:2786 #, no-c-format msgid "debian-installer/country (country)" msgstr "" #. Tag: term -#: boot-installer.xml:2700 +#: boot-installer.xml:2787 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:2701 +#: boot-installer.xml:2788 #, 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:2706 +#: boot-installer.xml:2793 #, 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:2715 +#: boot-installer.xml:2802 #, 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:2727 +#: boot-installer.xml:2814 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:2728 +#: boot-installer.xml:2815 #, 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:2742 +#: boot-installer.xml:2829 #, no-c-format msgid "Set to <userinput>true</userinput> if you want to disable IPv6 autoconfiguration and DHCP and instead force static network configuration." msgstr "" #. Tag: term -#: boot-installer.xml:2751 +#: boot-installer.xml:2838 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:2752 +#: boot-installer.xml:2839 #, 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:2765 +#: boot-installer.xml:2852 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para -#: boot-installer.xml:2766 +#: boot-installer.xml:2853 #, 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:2780 +#: boot-installer.xml:2867 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2781 +#: boot-installer.xml:2868 #, 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:2794 +#: boot-installer.xml:2881 #, 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:2801 +#: boot-installer.xml:2888 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -1929,127 +2061,127 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2811 +#: boot-installer.xml:2898 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:2817 +#: boot-installer.xml:2904 #, no-c-format msgid "Blacklisting kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2818 +#: boot-installer.xml:2905 #, 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:2827 +#: boot-installer.xml:2914 #, 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:2835 +#: boot-installer.xml:2922 #, 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:2851 +#: boot-installer.xml:2938 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:2856 +#: boot-installer.xml:2943 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:2857 +#: boot-installer.xml:2944 #, 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:2864 +#: boot-installer.xml:2951 #, 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:2870 +#: boot-installer.xml:2957 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:2875 +#: boot-installer.xml:2962 #, 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:2881 +#: boot-installer.xml:2968 #, no-c-format msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with very old CD-ROM drives are known to be resolved in this way." msgstr "" #. Tag: para -#: boot-installer.xml:2891 +#: boot-installer.xml:2978 #, 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:2897 +#: boot-installer.xml:2984 #, 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:2905 +#: boot-installer.xml:2992 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:2908 +#: boot-installer.xml:2995 #, 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:2925 +#: boot-installer.xml:3012 #, no-c-format msgid "Some very old CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled for them." msgstr "" #. Tag: title -#: boot-installer.xml:2936 +#: boot-installer.xml:3023 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:2937 +#: boot-installer.xml:3024 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:2942 +#: boot-installer.xml:3029 #, no-c-format msgid "Check that your BIOS actually supports booting from CD-ROM (only an issue for very old systems) and that CD booting is enabled in the BIOS." msgstr "" #. Tag: para -#: boot-installer.xml:2949 +#: boot-installer.xml:3036 #, 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" @@ -2059,7 +2191,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2962 +#: boot-installer.xml:3049 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -2072,19 +2204,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2967 +#: boot-installer.xml:3054 #, no-c-format msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of &arch-kernel; is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there." msgstr "" #. Tag: para -#: boot-installer.xml:2979 +#: boot-installer.xml:3066 #, 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:2986 +#: boot-installer.xml:3073 #, 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" @@ -2097,13 +2229,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3000 +#: boot-installer.xml:3087 #, 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:3008 +#: boot-installer.xml:3095 #, 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" @@ -2112,7 +2244,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3018 +#: boot-installer.xml:3105 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -2125,151 +2257,151 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3033 +#: boot-installer.xml:3120 #, 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:3048 +#: boot-installer.xml:3135 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3050 +#: boot-installer.xml:3137 #, 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:3055 +#: boot-installer.xml:3142 #, 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:3064 +#: boot-installer.xml:3151 #, 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:3073 +#: boot-installer.xml:3160 #, 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:3079 +#: boot-installer.xml:3166 #, 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:3085 +#: boot-installer.xml:3172 #, 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:3094 +#: boot-installer.xml:3181 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:3096 +#: boot-installer.xml:3183 #, 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:3105 +#: boot-installer.xml:3192 #, no-c-format msgid "In some cases, malfunctions can be caused by missing device firmware (see <xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/>)." msgstr "" #. Tag: para -#: boot-installer.xml:3116 +#: boot-installer.xml:3203 #, no-c-format msgid "If software speech synthesis does not work, there is most probably an issue with your sound board, usually because either the driver for it is not included in the installer, or because it has unusual mixer level names which are set to muted by default. You should thus submit a bug report which includes the output of the following commands, run on the same machine from a Linux system which is known to have sound working (e.g., a live CD)." msgstr "" #. Tag: userinput -#: boot-installer.xml:3127 +#: boot-installer.xml:3214 #, no-c-format msgid "dmesg" msgstr "" #. Tag: userinput -#: boot-installer.xml:3129 +#: boot-installer.xml:3216 #, no-c-format msgid "lspci" msgstr "" #. Tag: userinput -#: boot-installer.xml:3131 +#: boot-installer.xml:3218 #, no-c-format msgid "lsmod" msgstr "" #. Tag: userinput -#: boot-installer.xml:3133 +#: boot-installer.xml:3220 #, no-c-format msgid "amixer" msgstr "" #. Tag: title -#: boot-installer.xml:3141 boot-installer.xml:3252 +#: boot-installer.xml:3228 boot-installer.xml:3339 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3142 +#: boot-installer.xml:3229 #, 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:3193 +#: boot-installer.xml:3280 #, 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:3207 +#: boot-installer.xml:3294 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:3208 +#: boot-installer.xml:3295 #, no-c-format msgid "Some very old laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems." msgstr "" #. Tag: para -#: boot-installer.xml:3218 +#: boot-installer.xml:3305 #, no-c-format msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer." msgstr "" #. Tag: para -#: boot-installer.xml:3253 +#: boot-installer.xml:3340 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:3259 +#: boot-installer.xml:3346 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:3260 +#: boot-installer.xml:3347 #, 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" @@ -2279,85 +2411,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3274 +#: boot-installer.xml:3361 #, 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:3285 +#: boot-installer.xml:3372 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3286 +#: boot-installer.xml:3373 #, 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:3292 +#: boot-installer.xml:3379 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3301 +#: boot-installer.xml:3388 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3303 +#: boot-installer.xml:3390 #, no-c-format msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-baking\"/>)</phrase>." msgstr "" #. Tag: title -#: boot-installer.xml:3328 +#: boot-installer.xml:3415 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3329 +#: boot-installer.xml:3416 #, 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:3340 +#: boot-installer.xml:3427 #, 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:3351 +#: boot-installer.xml:3438 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3352 +#: boot-installer.xml:3439 #, 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:3359 +#: boot-installer.xml:3446 #, 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:3365 +#: boot-installer.xml:3452 #, 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:3375 +#: boot-installer.xml:3462 #, 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 4dd59fa11..e6ed5b3a9 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: 2014-08-26 20:40+0000\n" +"POT-Creation-Date: 2015-04-15 20:29+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" @@ -77,7 +77,7 @@ msgstr "" #. Tag: para #: boot-new.xml:84 #, no-c-format -msgid "If you use <command>BootX</command> to boot into the installed system, just select your desired kernel in the <filename>Linux Kernels</filename> folder, un-choose the ramdisk option, and add a root device corresponding to your installation; e.g. <userinput>/dev/hda8</userinput>." +msgid "If you use <command>BootX</command> to boot into the installed system, just select your desired kernel in the <filename>Linux Kernels</filename> folder, un-choose the ramdisk option, and add a root device corresponding to your installation; e.g. <userinput>/dev/sda8</userinput>." msgstr "" #. Tag: title diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index 136009735..342231f03 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: 2015-03-21 16:42+0000\n" +"POT-Creation-Date: 2015-04-15 20:29+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" @@ -53,17 +53,17 @@ msgstr "" #. Tag: para #: hardware.xml:42 #, no-c-format -msgid "&debian; GNU/Linux &release; supports eight major architectures and several variations of each architecture known as <quote>flavors</quote>." +msgid "&debian; GNU/Linux &release; supports ten major architectures and several variations of each architecture known as <quote>flavors</quote>." msgstr "" #. Tag: entry -#: hardware.xml:53 hardware.xml:197 +#: hardware.xml:53 hardware.xml:193 #, no-c-format msgid "Architecture" msgstr "" #. Tag: entry -#: hardware.xml:53 hardware.xml:197 +#: hardware.xml:53 hardware.xml:193 #, no-c-format msgid "&debian; Designation" msgstr "" @@ -81,7 +81,7 @@ msgid "Flavor" msgstr "" #. Tag: entry -#: hardware.xml:60 hardware.xml:203 +#: hardware.xml:60 hardware.xml:199 #, no-c-format msgid "Intel x86-based" msgstr "" @@ -93,7 +93,7 @@ msgid "i386" msgstr "" #. Tag: entry -#: hardware.xml:67 hardware.xml:208 +#: hardware.xml:67 hardware.xml:204 #, no-c-format msgid "AMD64 & Intel 64" msgstr "" @@ -177,1819 +177,1909 @@ msgid "armhf" msgstr "" #. Tag: entry -#: hardware.xml:101 +#: hardware.xml:97 #, no-c-format msgid "multiplatform" msgstr "" #. Tag: entry -#: hardware.xml:102 +#: hardware.xml:98 #, no-c-format msgid "armmp" msgstr "" #. Tag: entry -#: hardware.xml:104 +#: hardware.xml:100 #, no-c-format msgid "multiplatform for LPAE-capable systems" msgstr "" #. Tag: entry -#: hardware.xml:105 +#: hardware.xml:101 #, no-c-format msgid "armmp-lpae" msgstr "" #. Tag: entry -#: hardware.xml:109 +#: hardware.xml:105 #, no-c-format msgid "64bit ARM" msgstr "" #. Tag: entry -#: hardware.xml:110 +#: hardware.xml:106 #, no-c-format msgid "arm64" msgstr "" #. Tag: entry -#: hardware.xml:116 +#: hardware.xml:112 #, no-c-format msgid "MIPS (big endian)" msgstr "" #. Tag: entry -#: hardware.xml:117 +#: hardware.xml:113 #, no-c-format msgid "mips" msgstr "" #. Tag: entry -#: hardware.xml:118 +#: hardware.xml:114 #, no-c-format msgid "SGI IP22 (Indy/Indigo 2)" msgstr "" #. Tag: entry -#: hardware.xml:119 +#: hardware.xml:115 #, no-c-format msgid "r4k-ip22" msgstr "" #. Tag: entry -#: hardware.xml:121 +#: hardware.xml:117 #, no-c-format msgid "SGI IP32 (O2)" msgstr "" #. Tag: entry -#: hardware.xml:122 +#: hardware.xml:118 #, no-c-format msgid "r5k-ip32" msgstr "" #. Tag: entry -#: hardware.xml:124 hardware.xml:134 +#: hardware.xml:120 hardware.xml:130 #, no-c-format msgid "MIPS Malta (32 bit)" msgstr "" #. Tag: entry -#: hardware.xml:125 hardware.xml:135 +#: hardware.xml:121 hardware.xml:131 #, no-c-format msgid "4kc-malta" msgstr "" #. Tag: entry -#: hardware.xml:127 hardware.xml:137 +#: hardware.xml:123 hardware.xml:133 #, no-c-format msgid "MIPS Malta (64 bit)" msgstr "" #. Tag: entry -#: hardware.xml:128 hardware.xml:138 +#: hardware.xml:124 hardware.xml:134 #, no-c-format msgid "5kc-malta" msgstr "" #. Tag: entry -#: hardware.xml:132 +#: hardware.xml:128 #, no-c-format msgid "MIPS (little endian)" msgstr "" #. Tag: entry -#: hardware.xml:133 +#: hardware.xml:129 #, no-c-format msgid "mipsel" msgstr "" #. Tag: entry -#: hardware.xml:142 +#: hardware.xml:138 #, no-c-format msgid "IBM/Motorola PowerPC" msgstr "" #. Tag: entry -#: hardware.xml:143 +#: hardware.xml:139 #, no-c-format msgid "<entry morerows=\"1\">powerpc</entry>" msgstr "" #. Tag: entry -#: hardware.xml:144 +#: hardware.xml:140 #, no-c-format msgid "PowerMac" msgstr "" #. Tag: entry -#: hardware.xml:145 +#: hardware.xml:141 #, no-c-format msgid "pmac" msgstr "" #. Tag: entry -#: hardware.xml:147 +#: hardware.xml:143 #, no-c-format msgid "PReP" msgstr "" #. Tag: entry -#: hardware.xml:148 +#: hardware.xml:144 #, no-c-format msgid "prep" msgstr "" #. Tag: entry -#: hardware.xml:152 +#: hardware.xml:148 #, no-c-format -msgid "IBM PowerPC (little endian)" +msgid "Power Systems" msgstr "" #. Tag: entry -#: hardware.xml:153 +#: hardware.xml:149 #, no-c-format msgid "ppc64el" msgstr "" #. Tag: entry -#: hardware.xml:179 +#: hardware.xml:150 +#, no-c-format +msgid "IBM POWER8 or newer machines" +msgstr "" + +#. Tag: entry +#: hardware.xml:175 #, no-c-format msgid "64bit IBM S/390" msgstr "" #. Tag: entry -#: hardware.xml:180 +#: hardware.xml:176 #, no-c-format msgid "s390x" msgstr "" #. Tag: entry -#: hardware.xml:181 +#: hardware.xml:177 #, no-c-format msgid "IPL from VM-reader and DASD" msgstr "" #. Tag: entry -#: hardware.xml:182 +#: hardware.xml:178 #, no-c-format msgid "generic" msgstr "" #. Tag: para -#: hardware.xml:187 +#: hardware.xml:183 #, no-c-format msgid "&debian; GNU/kFreeBSD &release; supports two architectures." msgstr "" #. Tag: entry -#: hardware.xml:204 +#: hardware.xml:200 #, no-c-format msgid "kfreebsd-i386" msgstr "" #. Tag: entry -#: hardware.xml:209 +#: hardware.xml:205 #, no-c-format msgid "kfreebsd-amd64" msgstr "" #. Tag: para -#: hardware.xml:214 +#: hardware.xml:210 #, 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:224 -#, no-c-format -msgid "The &arch-title; architecture only supports Intel Itanium processors and not the much more common 64-bit processors from the Intel 64 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:234 +#: hardware.xml:220 #, no-c-format 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:256 +#: hardware.xml:242 #, no-c-format msgid "CPU Support" msgstr "" #. Tag: para -#: hardware.xml:257 +#: hardware.xml:243 #, no-c-format msgid "Both AMD64 and Intel 64 processors are supported." msgstr "" #. Tag: title -#: hardware.xml:282 hardware.xml:637 hardware.xml:656 hardware.xml:714 hardware.xml:772 hardware.xml:802 +#: hardware.xml:268 hardware.xml:723 hardware.xml:780 hardware.xml:838 hardware.xml:868 hardware.xml:1311 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para -#: hardware.xml:284 +#: hardware.xml:270 #, no-c-format -msgid "ARM systems are a lot more heterogenous than the i386/amd64-based PC architecture, where all systems share a common system firmware (BIOS or/and UEFI) which handles the board-specific basic hardware initialization in a standardized way. The ARM architecture is used mainly in so-called <quote>systems-on-chip</quote> (SoCs). These SoCs are designed by many different companies with vastly varying hardware components even for the very basic functionality required to bring the system up. Systems using them usually lack a common system firmware interface and as a result, on ARM systems the Linux kernel has to take care of many system-specific low-level issues which are handled by the mainboard's BIOS in the PC world." +msgid "ARM systems are much more heterogeneous than the i386/amd64-based PC architecture, so whilst 64-bit ARM machines should boot in a standardised way, like PCs, the situation is more complicated for 32-bit ARM machines." msgstr "" #. Tag: para -#: hardware.xml:301 +#: hardware.xml:279 #, no-c-format -msgid "At the beginning of the ARM support in the Linux kernel, this resulted in the requirement of having a seperate kernel for each ARM system in contrast to the <quote>one-fits-all</quote> kernel for PC systems. As this approach does not scale to a large number of different systems, work has started to be able to provide a single ARM kernel that can run on different ARM systems. Support for newer ARM systems gets implemented in a way that allows the use of such a multiplatform kernel, but for several older systems a seperate specific kernel is still required. Because of this, the standard &debian; distribution only supports installation on a selected number of older ARM systems in addition to the newer systems which are supported by the ARM multiplatform (armmp) kernel." +msgid "The ARM architecture is used mainly in so-called <quote>systems-on-chip</quote> (SoCs). These SoCs are designed by many different companies with vastly varying hardware components even for the very basic functionality required to bring the system up. System firmware interfaces have been increasingly standardised over time, but especially on older hardware firmware/boot interfaces vary a great deal, so on these systems the Linux kernel has to take care of many system-specific low-level issues which are handled by the mainboard's BIOS in the PC world." msgstr "" #. Tag: para -#: hardware.xml:318 +#: hardware.xml:292 #, no-c-format -msgid "The ARM architecture has evolved over time and modern ARM processors provide features which are not available in older models. &debian; therefore provides two ARM ports, the &debian;/armel and the &debian;/armhf port. &debian;/armel targets older ARM processors without support for a hardware floating point unit (FPU), while &debian;/armhf works only on newer ARM processors which implement at least the ARMv7 architecture with version 3 of the ARM vector floating point specification (VFPv3). &debian;/armhf makes use of the extended features and performance enhancements available on these models." +msgid "At the beginning of the ARM support in the Linux kernel, the hardware variety resulted in the requirement of having a separate kernel for each ARM system in contrast to the <quote>one-fits-all</quote> kernel for PC systems. As this approach does not scale to a large number of different systems, work was done to allow booting with a single ARM kernel that can run on different ARM systems. Support for newer ARM systems gets implemented in a way that allows the use of such a multiplatform kernel, but for several older systems a separate specific kernel is still required." msgstr "" #. Tag: para -#: hardware.xml:346 +#: hardware.xml:304 #, no-c-format -msgid "Technically, several ARM CPUs can be run in either endian mode (big or little), but in practice the vast majority of currently available systems uses little-endian mode. Both &debian;/armhf and &debian;/armel support only little-endian systems." -msgstr "" - -#. Tag: title -#: hardware.xml:354 -#, no-c-format -msgid "Platforms supported by Debian/armel" +msgid "Because of this, the standard &debian; distribution only supports installation on a selected number of older 32-bit ARM systems in addition to the newer (32 and 64-bit) systems which are supported by the ARM multiplatform kernels (called 'armmp' on 32-bit armhf, no flavour name on 64-bit arm64)." msgstr "" #. Tag: para -#: hardware.xml:356 +#: hardware.xml:313 #, no-c-format -msgid "The following platforms are supported by &debian;/armel; they require platform-specific kernels." -msgstr "" - -#. Tag: term -#: hardware.xml:364 -#, no-c-format -msgid "IXP4xx" +msgid "The ARM architecture has evolved over time and modern ARM processors provide features which are not available in older models. &debian; therefore provides three ARM ports: the &debian;/arm64 port for all 64-bit machines, and the &debian;/armel and the &debian;/armhf ports for 32-bit machines. &debian;/armel targets older ARM processors without support for a hardware floating point unit (FPU), while &debian;/armhf works only on newer ARM processors which implement at least the ARMv7 architecture with version 3 of the ARM vector floating point specification (VFPv3). &debian;/armhf makes use of the extended features and performance enhancements available on these models. &debian;/arm64 works on processors which implement at least the ARMv8 architecture (which is 64bit)." msgstr "" #. Tag: para -#: hardware.xml:365 +#: hardware.xml:350 #, no-c-format -msgid "The Intel IXP4xx processor series is used in network attached storage devices like the Linksys NSLU2." +msgid "Technically, all currently available ARM CPUs can be run in either endian mode (big or little), but in practice the vast majority use little-endian mode. All of &debian;/arm64, &debian;/armhf and &debian;/armel support only little-endian systems." msgstr "" -#. Tag: term -#: hardware.xml:374 +#. Tag: title +#: hardware.xml:357 #, no-c-format -msgid "Kirkwood" +msgid "Platforms supported by Debian/arm64" msgstr "" #. Tag: para -#: hardware.xml:375 +#: hardware.xml:359 #, 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, OpenRD-Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)." +msgid "Arm64/AArch64/ARMv8 hardware became available quite late in the &debian; &releasename-cap; release cycle so not many platforms have had support merged in the mainline kernel version in this release, which is the main requirement to have &d-i; working on them." msgstr "" -#. Tag: term -#: hardware.xml:391 +#. Tag: para +#: hardware.xml:368 #, no-c-format -msgid "Orion5x" +msgid "The tested platforms are listed below, but in general, the multiplatform support in the arm64 Linux kernel also allows running &d-i; on arm64 systems not explicitly listed below, so long as the kernel used by &d-i; has support for the target system's components and a device-tree file for the target is available. In these cases, the installer can usually provide a working userland installation, and so long as UEFI is in use, it should be able to make the system bootable as well. If UEFI is not used (some 64-bit machines have been shipped with U-Boot) you will probably also need some manual steps to make the system bootable." msgstr "" #. Tag: para -#: hardware.xml:392 +#: hardware.xml:382 #, 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-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>." +msgid "The following platforms are known to be supported by &debian;/arm64 in this release. There is only one kernel, which supports all the listed platforms." msgstr "" #. Tag: term -#: hardware.xml:406 +#: hardware.xml:389 #, no-c-format -msgid "<term>Versatile</term>" +msgid "Applied Micro (APM) Mustang/X-Gene" msgstr "" #. Tag: para -#: hardware.xml:407 -#, 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: title -#: hardware.xml:420 +#: hardware.xml:391 #, no-c-format -msgid "Platforms no longer supported by Debian/armel" +msgid "The APM Mustang was the first Linux-capable ARMv8 system available. It uses the X-gene SoC, since also used in other machines, which is an 8-core CPU, with ethernet, USB, serial. A common form-factor looks just like a desktop PC box, but many versions are expected. Most of the hardware is supported in the mainline kernel, but USB support is lacking in the &releasename-cap; kernel." msgstr "" #. Tag: term -#: hardware.xml:424 +#: hardware.xml:404 #, no-c-format -msgid "IOP32x" +msgid "ARM Juno Development Platform" msgstr "" #. Tag: para -#: hardware.xml:425 -#, no-c-format -msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing, such as the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>. &debian; has supported the IOP32x platform in &debian; 7, but does not support it anymore from version 8 on due to hardware constraints of the platform which make it unsuitable for the installation of newer &debian; releases." -msgstr "" - -#. Tag: term -#: hardware.xml:439 +#: hardware.xml:406 #, no-c-format -msgid "MV78xx0" +msgid "Juno is a capable development board with a 6-core (2xA57, 4xA53) ARMv8-A 800Mhz CPU, Mali (T624) graphics, 8GB DDR3 RAM, Ethernet, USB, Serial. It was designed for system bring-up and power testing so is neither small nor cheap, but was one of the first boards available. All the hardware is supported in the mainline kernel and in &releasename-cap;." msgstr "" #. Tag: para -#: hardware.xml:440 +#: hardware.xml:420 #, no-c-format -msgid "The MV78xx0 platform has been used on the Marvell DB-78xx0-BP development board. It was supported in Debian 7 with a platform-specific kernel (based on the Linux kernel version 3.2), but is not supported anymore from Debian 8 onwards." +msgid "When using &d-i; on non-UEFI systems, you may have to manually make the system bootable at the end of the installation, e.g. by running the required commands in a shell started from within &d-i;. flash-kernel knows how to set up an X-Gene system booting with U-Boot." msgstr "" #. Tag: title -#: hardware.xml:455 +#: hardware.xml:430 #, no-c-format msgid "Platforms supported by Debian/armhf" msgstr "" #. Tag: para -#: hardware.xml:457 +#: hardware.xml:432 #, no-c-format msgid "The following systems are known to work with &debian;/armhf using the multiplatform (armmp) kernel:" msgstr "" #. Tag: term -#: hardware.xml:464 +#: hardware.xml:439 #, no-c-format msgid "Freescale MX53 Quick Start Board" msgstr "" #. Tag: para -#: hardware.xml:466 +#: hardware.xml:441 #, no-c-format msgid "The IMX53QSB is a development board based on the i.MX53 SoC." msgstr "" #. Tag: term -#: hardware.xml:473 +#: hardware.xml:448 #, no-c-format msgid "Versatile Express" msgstr "" #. Tag: para -#: hardware.xml:475 +#: hardware.xml:450 #, no-c-format -msgid "The Versatile Express is a development board series from ARM consisting of a baseboard which can be equipped with various CPU daughterboards." +msgid "The Versatile Express is a development board series from ARM consisting of a baseboard which can be equipped with various CPU daughter boards." msgstr "" #. Tag: term -#: hardware.xml:484 +#: hardware.xml:459 #, no-c-format msgid "Certain Allwinner sunXi-based development boards and embedded systems" msgstr "" #. Tag: para -#: hardware.xml:487 +#: hardware.xml:462 #, no-c-format msgid "The armmp kernel supports several development boards and embedded systems based on the Allwinner A10 (architecture codename <quote>sun4i</quote>), A10s/A13 (architecture codename <quote>sun5i</quote>) and A20 (architecture codename <quote>sun7i</quote>) SoCs. Full installer support is currently available for the following sunXi-based systems:" msgstr "" #. Tag: para -#: hardware.xml:495 +#: hardware.xml:470 #, no-c-format msgid "Cubietech Cubieboard 1 + 2 / Cubietruck" msgstr "" #. Tag: para -#: hardware.xml:498 +#: hardware.xml:473 #, no-c-format msgid "LeMaker Banana Pi and Banana Pro" msgstr "" #. Tag: para -#: hardware.xml:501 +#: hardware.xml:476 #, no-c-format -msgid "LinkSprite pcDuino" +msgid "LinkSprite pcDuino and pcDuino3" msgstr "" #. Tag: para -#: hardware.xml:504 +#: hardware.xml:479 #, no-c-format msgid "Mele A1000" msgstr "" #. Tag: para -#: hardware.xml:507 +#: hardware.xml:482 #, no-c-format msgid "Miniand Hackberry" msgstr "" #. Tag: para -#: hardware.xml:510 +#: hardware.xml:485 #, no-c-format msgid "Olimex A10-Olinuxino-LIME / A10s-Olinuxino Micro / A13-Olinuxino / A13-Olinuxino Micro / A20-Olinuxino-LIME / A20-Olinuxino-LIME2 / A20-Olinuxino Micro" msgstr "" #. Tag: para -#: hardware.xml:515 +#: hardware.xml:490 #, no-c-format msgid "PineRiver Mini X-Plus" msgstr "" #. Tag: para -#: hardware.xml:521 +#: hardware.xml:496 #, no-c-format msgid "System support for Allwinner sunXi-based devices is limited to drivers and device-tree information available in the mainline Linux kernel. The android-derived linux-sunxi.org 3.4 kernel series is not supported by Debian." msgstr "" #. Tag: para -#: hardware.xml:527 +#: hardware.xml:502 #, no-c-format msgid "The mainline Linux kernel generally supports serial console, ethernet, SATA, USB and MMC/SD-cards on Allwinner A10, A10s/A13 and A20 SoCs, but it does not have native drivers for the display (HDMI/VGA/LCD) and audio hardware in these SoCs. The NAND flash memory that is built into some sunXi-based systems is not supported." msgstr "" #. Tag: para -#: hardware.xml:535 +#: hardware.xml:510 #, no-c-format -msgid "Using a local display is technically possible without native display drivers via the <quote>simplefb</quote> infrastructure in the mainline kernel, which relies on the <quote>u-boot</quote> bootloader for initializing the display hardware, but this is not supported by the u-boot version in &debian; 8." +msgid "Using a local display is technically possible without native display drivers via the <quote>simplefb</quote> infrastructure in the mainline kernel, which relies on the <quote>U-Boot</quote> bootloader for initialising the display hardware, but this is not supported by the U-Boot version in &debian; 8." msgstr "" #. Tag: term -#: hardware.xml:547 +#: hardware.xml:522 #, no-c-format msgid "SolidRun Cubox-i2eX / Cubox-i4Pro" msgstr "" #. Tag: para -#: hardware.xml:549 +#: hardware.xml:524 #, no-c-format msgid "The Cubox-i series is a set of small, cubical-shaped systems based on the Freescale i.MX6 SoC family. System support for the Cubox-i series is limited to drivers and device-tree information available in the mainline Linux kernel; the Freescale 3.0 kernel series for the Cubox-i is not supported by Debian. Available drivers in the mainline kernel include serial console, ethernet, USB, MMC/SD-card and display support over HDMI (console and X11). In addition to that, the eSATA port on the Cubox-i4Pro is supported." msgstr "" #. Tag: term -#: hardware.xml:564 +#: hardware.xml:539 #, no-c-format msgid "Wandboard Quad" msgstr "" #. Tag: para -#: hardware.xml:566 +#: hardware.xml:541 #, no-c-format msgid "The Wandboard Quad is a development board based on the Freescale i.MX6 Quad SoC. System support for it is limited to drivers and device-tree information available in the mainline Linux kernel; the wandboard-specific 3.0 and 3.10 kernel series from wandboard.org are not supported by Debian. The mainline kernel includes driver support for serial console, display via HDMI (console and X11), ethernet, USB, MMC/SD and SATA. Support for the onboard audio options (analog, S/PDIF, HDMI-Audio) and for the onboard WLAN/Bluetooth module is not available in &debian; 8." msgstr "" #. Tag: para -#: hardware.xml:584 +#: hardware.xml:559 #, no-c-format msgid "Generally, the ARM multiplatform support in the Linux kernel allows running &d-i; on armhf systems not explicitly listed above, as long as the kernel used by &d-i; has support for the target system's components and a device-tree file for the target is available. In these cases, the installer can usually provide a working userland installation, but it probably cannot automatically make the system bootable, as doing that in many cases requires device-specific information." msgstr "" #. Tag: para -#: hardware.xml:595 +#: hardware.xml:570 #, no-c-format -msgid "When using &d-i; on such systems, you have to manually make the system bootable at the end of the installation, e.g. by running the required commands in a shell started from within &d-i;." +msgid "When using &d-i; on such systems, you may have to manually make the system bootable at the end of the installation, e.g. by running the required commands in a shell started from within &d-i;." msgstr "" #. Tag: title -#: hardware.xml:604 +#: hardware.xml:579 #, no-c-format msgid "Platforms no longer supported by Debian/armhf" msgstr "" #. Tag: term -#: hardware.xml:608 +#: hardware.xml:583 #, no-c-format msgid "EfikaMX" msgstr "" #. Tag: para -#: hardware.xml:609 +#: hardware.xml:584 #, no-c-format -msgid "The EfikaMX platform (Genesi Efika Smartbook and Genesi EfikaMX nettop) has been supported in &debian; 7 with a platform-specific kernel, but is not supported anymore from &debian; 8 onwards. The code required to build the formerly used platform-specific kernel has been removed from the upstream Linux kernel source in 2012, so Debian cannot provide newer builds." +msgid "The EfikaMX platform (Genesi Efika Smartbook and Genesi EfikaMX nettop) has been supported in &debian; 7 with a platform-specific kernel, but is no longer supported from &debian; 8 onwards. The code required to build the formerly used platform-specific kernel has been removed from the upstream Linux kernel source in 2012, so Debian cannot provide newer builds." msgstr "" #. Tag: para -#: hardware.xml:617 +#: hardware.xml:591 #, no-c-format msgid "Using the armmp multiplatform kernel on the EfikaMX platform would require device-tree support for it, which is currently not available." msgstr "" +#. Tag: title +#: hardware.xml:603 +#, no-c-format +msgid "Platforms supported by Debian/armel" +msgstr "" + +#. Tag: para +#: hardware.xml:605 +#, no-c-format +msgid "The following platforms are supported by &debian;/armel; they require platform-specific kernels." +msgstr "" + +#. Tag: term +#: hardware.xml:613 +#, no-c-format +msgid "IXP4xx" +msgstr "" + +#. Tag: para +#: hardware.xml:614 +#, no-c-format +msgid "The Intel IXP4xx processor series is used in network attached storage devices like the Linksys NSLU2." +msgstr "" + +#. Tag: para +#: hardware.xml:619 +#, no-c-format +msgid "While there is kernel support for this platform in &debian; 8, it is not supported by the &d-i;. It is possible to do a <quote>dist-upgrade</quote> from Debian 7 to Debian 8 for existing installations, though. Due to the low amount of RAM that systems based on the IXP4xx usually have, this requires that swap space is enabled prior to upgrading. Support for the IXP4xx platform will be dropped completely in &debian; 9." +msgstr "" + +#. Tag: term +#: hardware.xml:632 +#, no-c-format +msgid "Kirkwood" +msgstr "" + +#. Tag: para +#: hardware.xml:633 +#, 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, OpenRD-Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)." +msgstr "" + +#. Tag: term +#: hardware.xml:649 +#, no-c-format +msgid "Orion5x" +msgstr "" + +#. Tag: para +#: hardware.xml:650 +#, 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-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>." +msgstr "" + +#. Tag: term +#: hardware.xml:664 +#, no-c-format +msgid "<term>Versatile</term>" +msgstr "" + +#. Tag: para +#: hardware.xml:665 +#, 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: title +#: hardware.xml:678 +#, no-c-format +msgid "Platforms no longer supported by Debian/armel" +msgstr "" + +#. Tag: term +#: hardware.xml:682 +#, no-c-format +msgid "IOP32x" +msgstr "" + +#. Tag: para +#: hardware.xml:683 +#, no-c-format +msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing, such as the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>. &debian; has supported the IOP32x platform in &debian; 7, but does not support it any longer from version 8 on due to hardware constraints of the platform which make it unsuitable for the installation of newer &debian; releases." +msgstr "" + +#. Tag: term +#: hardware.xml:698 +#, no-c-format +msgid "MV78xx0" +msgstr "" + #. Tag: para -#: hardware.xml:638 +#: hardware.xml:699 #, 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." +msgid "The MV78xx0 platform has been used on the Marvell DB-78xx0-BP development board. It was supported in Debian 7 with a platform-specific kernel (based on the Linux kernel version 3.2), but is not supported any more from Debian 8 onwards." msgstr "" #. Tag: para -#: hardware.xml:657 +#: hardware.xml:724 #, 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:665 hardware.xml:749 +#: hardware.xml:732 hardware.xml:815 #, no-c-format msgid "<title>CPU</title>" msgstr "" #. Tag: para -#: hardware.xml:666 +#: hardware.xml:733 #, 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:673 +#: hardware.xml:740 #, no-c-format msgid "However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run on 486 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 and 80486 processors (and their clones) was dropped with the Sarge (r3.1) and Squeeze (r6.0) releases of &debian;, respectively. The Intel Pentium and clones, including those without an FPU (Floating-Point Unit or math coprocessor), are supported. The Intel Quark is <emphasis>not</emphasis> supported, due to hardware errata." msgstr "" #. Tag: para -#: hardware.xml:685 +#: hardware.xml:752 #, no-c-format msgid "If your system has a 64-bit processor from the AMD64 or Intel 64 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:694 +#: hardware.xml:761 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:695 +#: hardware.xml:762 #, 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, PCI-X, 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:715 +#: hardware.xml:781 #, 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:750 +#: hardware.xml:816 #, 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:756 +#: hardware.xml:822 #, 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:773 +#: hardware.xml:839 #, no-c-format msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <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:803 +#: hardware.xml:869 #, no-c-format msgid "For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported." msgstr "" #. Tag: title -#: hardware.xml:824 +#: hardware.xml:890 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:826 +#: hardware.xml:892 #, no-c-format msgid "There are two flavours of the powerpc kernel in &debian;, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:833 +#: hardware.xml:899 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:834 +#: hardware.xml:900 #, no-c-format msgid "This kernel flavour 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:844 +#: hardware.xml:910 #, no-c-format msgid "powerpc-smp" msgstr "" #. Tag: para -#: hardware.xml:845 +#: hardware.xml:911 #, no-c-format msgid "All Apple PowerMac G4 SMP machines." msgstr "" #. Tag: term -#: hardware.xml:853 +#: hardware.xml:919 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:854 +#: hardware.xml:920 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:858 +#: hardware.xml:924 #, 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:864 +#: hardware.xml:930 #, 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:869 +#: hardware.xml:935 #, no-c-format msgid "Systems using the PPC970 processor (Apple G5, YDL PowerStation, IBM Intellistation POWER 185) are also based on the POWER4 architecture, and use this kernel flavour." msgstr "" #. Tag: para -#: hardware.xml:875 +#: hardware.xml:941 #, no-c-format msgid "Newer IBM systems using POWER5, POWER6, and POWER7 processors." msgstr "" #. Tag: title -#: hardware.xml:908 +#: hardware.xml:974 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:910 +#: hardware.xml:976 #, 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:917 +#: hardware.xml:983 #, 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:925 +#: hardware.xml:991 #, 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:933 +#: hardware.xml:999 #, 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:949 hardware.xml:1084 hardware.xml:1128 hardware.xml:1161 +#: hardware.xml:1015 hardware.xml:1150 hardware.xml:1194 hardware.xml:1227 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:950 +#: hardware.xml:1016 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:956 +#: hardware.xml:1022 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:957 +#: hardware.xml:1023 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:958 hardware.xml:961 hardware.xml:964 hardware.xml:967 hardware.xml:970 hardware.xml:973 hardware.xml:976 hardware.xml:979 hardware.xml:982 hardware.xml:985 hardware.xml:988 hardware.xml:991 hardware.xml:994 hardware.xml:997 hardware.xml:1000 hardware.xml:1003 +#: hardware.xml:1024 hardware.xml:1027 hardware.xml:1030 hardware.xml:1033 hardware.xml:1036 hardware.xml:1039 hardware.xml:1042 hardware.xml:1045 hardware.xml:1048 hardware.xml:1051 hardware.xml:1054 hardware.xml:1057 hardware.xml:1060 hardware.xml:1063 hardware.xml:1066 hardware.xml:1069 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:960 +#: hardware.xml:1026 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:963 +#: hardware.xml:1029 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:966 +#: hardware.xml:1032 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:969 +#: hardware.xml:1035 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:972 +#: hardware.xml:1038 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:975 +#: hardware.xml:1041 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:978 +#: hardware.xml:1044 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:981 +#: hardware.xml:1047 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:984 +#: hardware.xml:1050 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:987 +#: hardware.xml:1053 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:990 +#: hardware.xml:1056 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:993 +#: hardware.xml:1059 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:996 +#: hardware.xml:1062 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:999 +#: hardware.xml:1065 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:1002 +#: hardware.xml:1068 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:1005 +#: hardware.xml:1071 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:1006 hardware.xml:1009 hardware.xml:1012 hardware.xml:1015 hardware.xml:1018 hardware.xml:1021 hardware.xml:1024 hardware.xml:1027 hardware.xml:1030 hardware.xml:1033 hardware.xml:1036 hardware.xml:1039 hardware.xml:1045 hardware.xml:1048 hardware.xml:1054 hardware.xml:1060 hardware.xml:1066 +#: hardware.xml:1072 hardware.xml:1075 hardware.xml:1078 hardware.xml:1081 hardware.xml:1084 hardware.xml:1087 hardware.xml:1090 hardware.xml:1093 hardware.xml:1096 hardware.xml:1099 hardware.xml:1102 hardware.xml:1105 hardware.xml:1111 hardware.xml:1114 hardware.xml:1120 hardware.xml:1126 hardware.xml:1132 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:1008 +#: hardware.xml:1074 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:1011 +#: hardware.xml:1077 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:1014 +#: hardware.xml:1080 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:1017 +#: hardware.xml:1083 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:1020 +#: hardware.xml:1086 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:1023 +#: hardware.xml:1089 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:1026 +#: hardware.xml:1092 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:1029 +#: hardware.xml:1095 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:1032 +#: hardware.xml:1098 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:1035 +#: hardware.xml:1101 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:1038 +#: hardware.xml:1104 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:1043 +#: hardware.xml:1109 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:1044 +#: hardware.xml:1110 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:1047 +#: hardware.xml:1113 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:1052 +#: hardware.xml:1118 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:1053 +#: hardware.xml:1119 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:1058 +#: hardware.xml:1124 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1059 +#: hardware.xml:1125 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:1064 hardware.xml:1090 +#: hardware.xml:1130 hardware.xml:1156 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:1065 +#: hardware.xml:1131 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:1074 +#: hardware.xml:1140 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1091 +#: hardware.xml:1157 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:1093 +#: hardware.xml:1159 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:1095 +#: hardware.xml:1161 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:1097 +#: hardware.xml:1163 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:1099 +#: hardware.xml:1165 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:1103 hardware.xml:1134 +#: hardware.xml:1169 hardware.xml:1200 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:1104 +#: hardware.xml:1170 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:1106 +#: hardware.xml:1172 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:1108 +#: hardware.xml:1174 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:1110 +#: hardware.xml:1176 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:1118 +#: hardware.xml:1184 #, no-c-format msgid "CHRP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1135 +#: hardware.xml:1201 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:1138 +#: hardware.xml:1204 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:1139 +#: hardware.xml:1205 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: entry -#: hardware.xml:1142 +#: hardware.xml:1208 #, no-c-format msgid "Fixstars" msgstr "" #. Tag: entry -#: hardware.xml:1143 +#: hardware.xml:1209 #, no-c-format msgid "YDL PowerStation" msgstr "" #. Tag: title -#: hardware.xml:1151 +#: hardware.xml:1217 #, no-c-format msgid "APUS subarchitecture (unsupported)" msgstr "" #. Tag: entry -#: hardware.xml:1167 +#: hardware.xml:1233 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:1168 +#: hardware.xml:1234 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:1176 +#: hardware.xml:1242 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:1178 +#: hardware.xml:1244 #, 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:1215 +#: hardware.xml:1281 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:1217 +#: hardware.xml:1283 #, 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:1226 +#: hardware.xml:1292 #, 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:1234 +#: hardware.xml:1300 #, 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:1250 +#: hardware.xml:1314 +#, no-c-format +msgid "Machines" +msgstr "" + +#. Tag: para +#: hardware.xml:1317 +#, no-c-format +msgid "S822L" +msgstr "" + +#. Tag: para +#: hardware.xml:1322 +#, no-c-format +msgid "S821L" +msgstr "" + +#. Tag: para +#: hardware.xml:1327 +#, no-c-format +msgid "S822" +msgstr "" + +#. Tag: para +#: hardware.xml:1332 +#, no-c-format +msgid "S821" +msgstr "" + +#. Tag: para +#: hardware.xml:1337 +#, no-c-format +msgid "TYAN GN70-BP010" +msgstr "" + +#. Tag: title +#: hardware.xml:1352 #, no-c-format msgid "zSeries and System z machine types" msgstr "" #. Tag: para -#: hardware.xml:1251 +#: hardware.xml:1353 #, no-c-format msgid "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. Your machine needs to support the z/Architecture, 64-bit support is mandatory. The userland of the s390 port is still compiled for ESA/390, though. All zSeries and System z hardware is fully supported. &arch-title; support software is included from the kernel 3.1 development stream. The most current information about IBM's Linux support can be found at the <ulink url=\"http://www.ibm.com/developerworks/linux/linux390/development_technical.html\"> Linux on <trademark class=\"registered\">System z</trademark> page on developerWorks</ulink>." msgstr "" #. Tag: title -#: hardware.xml:1268 +#: hardware.xml:1370 #, no-c-format msgid "PAV and HyperPAV" msgstr "" #. Tag: para -#: hardware.xml:1269 +#: hardware.xml:1371 #, no-c-format msgid "PAV and HyperPAV are supported transparently, multipathing is not needed to take advantage of these storage system features. Be sure to configure the devices during DASD device selection. The alias devices will not be offered neither for formatting, partitioning nor direct use." msgstr "" #. Tag: title -#: hardware.xml:1285 +#: hardware.xml:1387 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para -#: hardware.xml:1286 +#: hardware.xml:1388 #, 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:1297 +#: hardware.xml:1399 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "" #. Tag: para -#: hardware.xml:1299 +#: hardware.xml:1401 #, 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:1306 +#: hardware.xml:1408 #, 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:1316 +#: hardware.xml:1418 #, no-c-format msgid "sun4u" msgstr "" #. Tag: para -#: hardware.xml:1318 +#: hardware.xml:1420 #, 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:1331 +#: hardware.xml:1433 #, no-c-format msgid "sun4v" msgstr "" #. Tag: para -#: hardware.xml:1333 +#: hardware.xml:1435 #, 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:1344 +#: hardware.xml:1446 #, 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:1353 +#: hardware.xml:1455 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1354 +#: hardware.xml:1456 #, no-c-format msgid "From a technical point of view, laptops are normal PCs, so all information regarding PC systems applies to laptops as well. Installations on laptops nowadays usually work out of the box, including things like automatically suspending the system on closing the lid and laptop specfic hardware buttons like those for disabling the wifi interfaces (<quote>airplane mode</quote>). Nonetheless sometimes the hardware vendors use specialized or proprietary hardware for some laptop-specific functions which might 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:1371 hardware.xml:1391 hardware.xml:1418 hardware.xml:1441 +#: hardware.xml:1473 hardware.xml:1493 hardware.xml:1520 hardware.xml:1543 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1372 +#: hardware.xml:1474 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. Having multiple processors in a computer was originally only an issue for high-end server systems but has become common in recent years nearly everywhere with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip." msgstr "" #. Tag: para -#: hardware.xml:1382 +#: hardware.xml:1484 #, no-c-format msgid "The standard &debian; &release; kernel image has been compiled with SMP support. It is also usable on non-SMP systems without problems." msgstr "" #. Tag: para -#: hardware.xml:1393 +#: hardware.xml:1495 #, 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:1402 +#: hardware.xml:1504 #, no-c-format msgid "Having multiple processors in a computer was originally only an issue for high-end server systems but has become common in recent years nearly everywhere with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip." msgstr "" #. Tag: para -#: hardware.xml:1409 +#: hardware.xml:1511 #, no-c-format msgid "The 586 flavour of the &debian; kernel image packages for &arch-title; is not compiled with SMP support." msgstr "" #. Tag: para -#: hardware.xml:1419 +#: hardware.xml:1521 #, 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 only the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1428 +#: hardware.xml:1530 #, no-c-format 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:1442 +#: hardware.xml:1544 #, 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:1452 +#: hardware.xml:1554 #, 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:1458 +#: hardware.xml:1560 #, no-c-format 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:1469 +#: hardware.xml:1571 #, no-c-format msgid "Graphics Card Support" msgstr "" #. Tag: para -#: hardware.xml:1470 +#: hardware.xml:1572 #, no-c-format msgid "&debian;'s support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. On modern PCs, having a graphical display usually works out of the box. Whether advanced graphics card features such as 3D-hardware acceleration or hardware-accelerated video are available, depends on the actual graphics hardware used in the system and in some cases on the installation of additional <quote>firmware</quote> images (see <xref linkend=\"hardware-firmware\"/>). In very few cases there have been reports about hardware on which installation of additional graphics card firmware was required even for basic graphics support, but these have been rare exceptions." msgstr "" #. Tag: para -#: hardware.xml:1483 +#: hardware.xml:1585 #, no-c-format msgid "Details on supported graphics cards 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:1488 +#: hardware.xml:1590 #, 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:1493 +#: hardware.xml:1595 #, 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:1503 +#: hardware.xml:1605 #, 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:1525 +#: hardware.xml:1627 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:1526 +#: hardware.xml:1628 #, no-c-format msgid "Almost any network interface card (NIC) supported by the &arch-kernel; kernel should also be supported by the installation system; drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1536 +#: hardware.xml:1638 #, 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:1542 +#: hardware.xml:1644 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:1547 +#: hardware.xml:1649 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:1552 +#: hardware.xml:1654 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:1557 +#: hardware.xml:1659 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:1562 +#: hardware.xml:1664 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:1569 +#: hardware.xml:1671 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:1574 +#: hardware.xml:1676 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:1579 +#: hardware.xml:1681 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:1584 +#: hardware.xml:1686 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:1593 +#: hardware.xml:1695 #, no-c-format msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided." msgstr "" #. Tag: para -#: hardware.xml:1598 +#: hardware.xml:1700 #, no-c-format msgid "ISDN is supported, but not during the installation." msgstr "" #. Tag: title -#: hardware.xml:1605 +#: hardware.xml:1707 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:1606 +#: hardware.xml:1708 #, no-c-format 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." msgstr "" #. Tag: para -#: hardware.xml:1613 +#: hardware.xml:1715 #, no-c-format msgid "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:1618 +#: hardware.xml:1720 #, no-c-format 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:1623 +#: hardware.xml:1725 #, 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-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:1633 +#: hardware.xml:1735 #, 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:1647 +#: hardware.xml:1749 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:1648 +#: hardware.xml:1750 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:1655 +#: hardware.xml:1757 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:1657 +#: hardware.xml:1759 #, 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:1667 +#: hardware.xml:1769 #, 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:1675 +#: hardware.xml:1777 #, 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:1688 +#: hardware.xml:1790 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:1690 +#: hardware.xml:1792 #, no-c-format msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." msgstr "" #. Tag: title -#: hardware.xml:1705 +#: hardware.xml:1807 #, no-c-format msgid "Braille Displays" msgstr "" #. Tag: para -#: hardware.xml:1706 +#: hardware.xml:1808 #, 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-gnu; &release; ships with <classname>brltty</classname> version &brlttyver;." msgstr "" #. Tag: title -#: hardware.xml:1720 +#: hardware.xml:1822 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: hardware.xml:1721 +#: hardware.xml:1823 #, 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, serial-to-USB or PCI 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:1741 +#: hardware.xml:1843 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:1742 +#: hardware.xml:1844 #, no-c-format msgid "&arch-kernel; supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA/CardBus/ExpressCard and USB devices. However, most of these devices are not required while installing the system." msgstr "" #. Tag: para -#: hardware.xml:1748 +#: hardware.xml:1850 #, no-c-format msgid "USB hardware generally works fine. On some very old PC systems some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>). On modern PCs, USB keyboards and mice work without requiring any specific configuration." msgstr "" #. Tag: para -#: hardware.xml:1757 +#: hardware.xml:1859 #, 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: title -#: hardware.xml:1770 +#: hardware.xml:1872 #, no-c-format msgid "Devices Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:1771 +#: hardware.xml:1873 #, 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. With many graphics cards, basic functionality is available without additional firmware, but the use of advanced features requires an appropriate firmware file to be installed in the system." msgstr "" #. Tag: para -#: hardware.xml:1782 +#: hardware.xml:1884 #, no-c-format msgid "On many older devices which require firmware to work, the firmware file was permanently placed in an EEPROM/Flash chip on the device itself by the manufacturer. Nowadays most new devices do not have the firmware embedded this way anymore, so the firmware file must be uploaded into the device by the host operating system every time the system boots." msgstr "" #. Tag: para -#: hardware.xml:1790 +#: hardware.xml:1892 #, no-c-format 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:1799 +#: hardware.xml:1901 #, no-c-format 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 USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation." msgstr "" #. Tag: para -#: hardware.xml:1808 +#: hardware.xml:1910 #, no-c-format msgid "If the &d-i; prompts for a firmware file and you do not have this firmware file available or do not want to install a non-free firmware file on your system, you can try to proceed without loading the firmware. There are several cases where a driver prompts for additional firmware because it may be needed under certain circumstances, but the device does work without it on most systems (this e.g. happens with certain network cards using the tg3 driver)." msgstr "" #. Tag: title -#: hardware.xml:1825 +#: hardware.xml:1927 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;" msgstr "" #. Tag: para -#: hardware.xml:1827 +#: hardware.xml:1929 #, 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:1835 +#: hardware.xml:1937 #, 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:1843 +#: hardware.xml:1945 #, no-c-format 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:1854 +#: hardware.xml:1956 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:1855 +#: hardware.xml:1957 #, 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 driver's source code, which is one of the central elements of free software. Since we haven't been granted access to usable documentation on these devices, they simply won't work under &arch-kernel;." msgstr "" #. Tag: para -#: hardware.xml:1865 +#: hardware.xml:1967 #, no-c-format msgid "In many cases there are standards (or at least some de-facto standards) describing how an operating system and its device drivers communicate with a certain class of devices. All devices which comply to such a (de-facto-)standard can be used with a single generic device driver and no device-specific drivers are required. With some kinds of hardware (e.g. USB <quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB mass storage devices like USB flash disks and memory card readers) this works very well and practically every device sold in the market is standards-compliant." msgstr "" #. Tag: para -#: hardware.xml:1877 +#: hardware.xml:1979 #, no-c-format msgid "In other fields, among them e.g. printers, this is unfortunately not the case. While there are many printers which can be addressed via a small set of (de-facto-)standard control languages and therefore can be made to work without problems in any operating system, there are quite a few models which only understand proprietary control commands for which no usable documentation is available and therefore either cannot be used at all on free operating systems or can only be used with a vendor-supplied closed-source driver." msgstr "" #. Tag: para -#: hardware.xml:1888 +#: hardware.xml:1990 #, no-c-format msgid "Even if there is a vendor-provided closed-source driver for such hardware when purchasing the device, the practical lifespan of the device is limited by driver availability. Nowadays product cycles have become short and it is not uncommon that a short time after a consumer device has ceased production, no driver updates get made available any more by the manufacturer. If the old closed-source driver does not work anymore after a system update, an otherwise perfectly working device becomes unusable due to lacking driver support and there is nothing that can be done in this case. You should therefore avoid buying closed hardware in the first place, regardless of the operating system you want to use it with." msgstr "" #. Tag: para -#: hardware.xml:1901 +#: hardware.xml:2003 #, no-c-format msgid "You can help improve this situation by encouraging manufacturers of closed hardware to release the documentation and other resources necessary for us to provide free drivers for their hardware." msgstr "" #. Tag: title -#: hardware.xml:1916 +#: hardware.xml:2018 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:1918 +#: hardware.xml:2020 #, no-c-format msgid "This section will help you determine which different media types you can use 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:1928 +#: hardware.xml:2030 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:1929 +#: hardware.xml:2031 #, 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:1935 +#: hardware.xml:2037 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:1942 +#: hardware.xml:2044 #, no-c-format -msgid "CD-ROM/DVD-ROM" +msgid "CD-ROM/DVD-ROM/BD-ROM" msgstr "" #. Tag: para -#: hardware.xml:1944 +#: hardware.xml:2046 #, 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." +msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to all of CD-ROMs, DVD-ROMs and BD-ROMs, because all these technologies are really the same from the operating system's point of view." msgstr "" #. Tag: para -#: hardware.xml:1950 +#: hardware.xml:2052 #, no-c-format msgid "CD-ROM based installation is supported for most architectures." msgstr "" #. Tag: para -#: hardware.xml:1954 +#: hardware.xml:2056 #, no-c-format -msgid "On PCs SATA, IDE/ATAPI and SCSI CD-ROMs are supported." +msgid "On PCs SATA, IDE/ATAPI, USB and SCSI CD-ROMs are supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" #. Tag: para -#: hardware.xml:1958 -#, 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:1963 -#, no-c-format -msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines." -msgstr "" - -#. Tag: para -#: hardware.xml:1967 +#: hardware.xml:2071 #, 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:1981 +#: hardware.xml:2085 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:1983 +#: hardware.xml:2087 #, no-c-format -msgid "USB flash disks a.k.a. USB memory sticks have become a commonly used and cheap storage device. Most modern computer systems also allow booting the &d-i; from such a stick. Many modern computer systems, in particular netbooks and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting from USB media ist the standard way of installing a new operating system on them." +msgid "USB flash disks a.k.a. USB memory sticks have become a commonly used and cheap storage device. Most modern computer systems also allow booting the &d-i; from such a stick. Many modern computer systems, in particular netbooks and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting from USB media is the standard way of installing a new operating system on them." msgstr "" #. Tag: title -#: hardware.xml:1995 +#: hardware.xml:2099 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:1997 +#: hardware.xml:2101 #, 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:2007 +#: hardware.xml:2111 #, no-c-format msgid "You can also <emphasis>boot</emphasis> the installation system over the network without needing any local media like CDs/DVDs or USB sticks. If you already have a netboot-infrastructure available (i.e. you are already running DHCP and TFTP services in your network), this allows an easy and fast deployment of a large number of machines. Setting up the necessary infrastructure requires a certain level of technical experience, so this is not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:2020 +#: hardware.xml:2124 #, 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:2029 +#: hardware.xml:2133 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:2031 +#: hardware.xml:2135 #, 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. This method is only recommended for special cases when no other installation method is available." msgstr "" #. Tag: para -#: hardware.xml:2038 +#: hardware.xml:2142 #, 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:2047 +#: hardware.xml:2151 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:2049 +#: hardware.xml:2153 #, no-c-format 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\"/>. This installation method is only recommended for advanced users when no other installation method is available." msgstr "" #. Tag: title -#: hardware.xml:2062 +#: hardware.xml:2166 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:2064 +#: hardware.xml:2168 #, no-c-format msgid "The &debian; installer contains a kernel which is built to maximize the number of systems it runs on." msgstr "" #. Tag: para -#: hardware.xml:2068 +#: hardware.xml:2172 #, no-c-format msgid "Generally, the &debian; installation system includes support for IDE (also known as PATA) drives, 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:2085 +#: hardware.xml:2189 #, 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:2118 +#: hardware.xml:2222 #, 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:2124 +#: hardware.xml:2228 #, 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:2130 +#: hardware.xml:2234 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:2135 +#: hardware.xml:2239 #, 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:2152 +#: hardware.xml:2256 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:2154 +#: hardware.xml:2258 #, 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:2161 +#: hardware.xml:2265 #, 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 text-based 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 fcbac0e7f..37ce9f490 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: 2015-02-23 20:58+0000\n" +"POT-Creation-Date: 2015-04-15 20:29+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" @@ -158,56 +158,62 @@ msgstr "" msgid "The installation files for systems supported by the armhf multiplatform kernel (see <xref linkend=\"armhf-armmp-supported-platforms\"/>) consist of a standard Linux kernel image, a standard Linux initial ramdisk image and a system-specific device-tree blob. The kernel and the initial ramdisk image for tftp-booting can be obtained from &armmp-firmware-img; and the device-tree blob can be obtained from &armmp-dtb-img;. The tar archive for creating a bootable USB stick with the installer can be obtained from &armmp-hd-media-tarball;." msgstr "" +#. Tag: para +#: install-methods.xml:223 +#, no-c-format +msgid "U-boot images for various armhf platforms are available at &armmp-uboot-img;." +msgstr "" + #. Tag: title -#: install-methods.xml:265 +#: install-methods.xml:269 #, no-c-format msgid "Creating Floppies from Disk Images" msgstr "" #. Tag: para -#: install-methods.xml:266 +#: install-methods.xml:270 #, no-c-format msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means." msgstr "" #. Tag: para -#: install-methods.xml:271 +#: install-methods.xml:275 #, no-c-format msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives." msgstr "" #. Tag: para -#: install-methods.xml:276 +#: install-methods.xml:280 #, no-c-format msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy." msgstr "" #. Tag: para -#: install-methods.xml:287 +#: install-methods.xml:291 #, no-c-format msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms." msgstr "" #. Tag: para -#: install-methods.xml:293 +#: install-methods.xml:297 #, no-c-format msgid "Before you can create the floppies, you will first need to download them from one of the &debian; mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>" msgstr "" #. Tag: para -#: install-methods.xml:301 +#: install-methods.xml:305 #, no-c-format msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally." msgstr "" #. Tag: title -#: install-methods.xml:309 +#: install-methods.xml:313 #, no-c-format msgid "Writing Disk Images From a Linux or Unix System" msgstr "" #. Tag: para -#: install-methods.xml:310 +#: install-methods.xml:314 #, no-c-format msgid "" "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n" @@ -216,181 +222,181 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:331 +#: install-methods.xml:335 #, no-c-format msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>" msgstr "" #. Tag: para -#: install-methods.xml:352 +#: install-methods.xml:356 #, no-c-format msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it." msgstr "" #. Tag: title -#: install-methods.xml:370 +#: install-methods.xml:374 #, no-c-format msgid "Writing Disk Images From DOS, Windows, or OS/2" msgstr "" #. Tag: para -#: install-methods.xml:372 +#: install-methods.xml:376 #, no-c-format msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies." msgstr "" #. Tag: para -#: install-methods.xml:377 +#: install-methods.xml:381 #, no-c-format msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work." msgstr "" #. Tag: para -#: install-methods.xml:385 +#: install-methods.xml:389 #, no-c-format msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory." msgstr "" #. Tag: para -#: install-methods.xml:391 +#: install-methods.xml:395 #, no-c-format msgid "These tools can be found on the Official &debian; CD-ROMs under the <filename>/tools</filename> directory." msgstr "" #. Tag: title -#: install-methods.xml:404 +#: install-methods.xml:408 #, no-c-format msgid "Writing Disk Images From MacOS" msgstr "" #. Tag: para -#: install-methods.xml:405 +#: install-methods.xml:409 #, no-c-format msgid "An AppleScript, <application>Make &debian; Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it." msgstr "" #. Tag: para -#: install-methods.xml:416 +#: install-methods.xml:420 #, no-c-format msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities." msgstr "" #. Tag: title -#: install-methods.xml:427 +#: install-methods.xml:431 #, no-c-format msgid "Writing Disk Images with <command>Disk Copy</command>" msgstr "" #. Tag: para -#: install-methods.xml:428 +#: install-methods.xml:432 #, no-c-format msgid "If you are creating the floppy image from files which were originally on the official &debian-gnu; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a &debian; mirror." msgstr "" #. Tag: para -#: install-methods.xml:437 +#: install-methods.xml:441 #, no-c-format msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file." msgstr "" #. Tag: para -#: install-methods.xml:444 +#: install-methods.xml:448 #, no-c-format msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields." msgstr "" #. Tag: para -#: install-methods.xml:451 +#: install-methods.xml:455 #, no-c-format msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted." msgstr "" #. Tag: para -#: install-methods.xml:460 +#: install-methods.xml:464 #, no-c-format msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>." msgstr "" #. Tag: para -#: install-methods.xml:467 +#: install-methods.xml:471 #, no-c-format msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy." msgstr "" #. Tag: title -#: install-methods.xml:482 +#: install-methods.xml:486 #, no-c-format msgid "Writing Disk Images with <command>suntar</command>" msgstr "" #. Tag: para -#: install-methods.xml:486 +#: install-methods.xml:490 #, no-c-format msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu." msgstr "" #. Tag: para -#: install-methods.xml:494 +#: install-methods.xml:498 #, no-c-format msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)." msgstr "" #. Tag: para -#: install-methods.xml:500 +#: install-methods.xml:504 #, no-c-format msgid "Select the <filename>root.bin</filename> file in the file-opening dialog." msgstr "" #. Tag: para -#: install-methods.xml:505 +#: install-methods.xml:509 #, no-c-format msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another." msgstr "" #. Tag: para -#: install-methods.xml:513 +#: install-methods.xml:517 #, no-c-format msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it." msgstr "" #. Tag: title -#: install-methods.xml:532 +#: install-methods.xml:536 #, no-c-format msgid "Preparing Files for USB Memory Stick Booting" msgstr "" #. Tag: para -#: install-methods.xml:534 +#: install-methods.xml:538 #, no-c-format msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>dmesg</command> after inserting it. To write to your stick, you may have to turn off its write protection switch." msgstr "" #. Tag: para -#: install-methods.xml:547 +#: install-methods.xml:551 #, no-c-format msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost." msgstr "" #. Tag: title -#: install-methods.xml:557 +#: install-methods.xml:561 #, no-c-format msgid "Preparing a USB stick using a hybrid CD or DVD image" msgstr "" #. Tag: para -#: install-methods.xml:558 +#: install-methods.xml:562 #, no-c-format msgid "Debian CD and DVD images can now be written directly to a USB stick, which is a very easy way to make a bootable USB stick. Simply choose a CD or DVD image (such as the netinst, CD-1, DVD-1, or netboot) that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to get a CD or DVD image." msgstr "" #. Tag: para -#: install-methods.xml:566 +#: install-methods.xml:570 #, no-c-format msgid "Alternatively, for very small USB sticks, only a few megabytes in size, you can download the <filename>mini.iso</filename> image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>)." msgstr "" #. Tag: para -#: install-methods.xml:573 +#: install-methods.xml:577 #, no-c-format msgid "" "The CD or DVD image you choose should be written directly to the USB stick, overwriting its current contents. For example, when using an existing GNU/Linux system, the CD or DVD image file can be written to a USB stick as follows, after having made sure that the stick is unmounted: <informalexample><screen>\n" @@ -400,31 +406,31 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:587 +#: install-methods.xml:591 #, no-c-format msgid "The image must be written to the whole-disk device and not a partition, e.g. /dev/sdb and not /dev/sdb1. Do not use tools like <command>unetbootin</command> which alter the image." msgstr "" #. Tag: para -#: install-methods.xml:593 +#: install-methods.xml:597 #, no-c-format msgid "Simply writing the CD or DVD image to USB like this should work fine for most users. The other options below are more complex, mainly for people with specialised needs." msgstr "" #. Tag: para -#: install-methods.xml:601 +#: install-methods.xml:605 #, no-c-format msgid "The hybrid image on the stick does not occupy all the storage space, so it may be worth considering using the free space to hold firmware files or packages or any other files of your choice. This could be useful if you have only one stick or just want to keep everything you need on one device." msgstr "" #. Tag: para -#: install-methods.xml:609 +#: install-methods.xml:613 #, no-c-format msgid "Create a second, FAT partition on the stick, mount the partition and copy or unpack the firmware onto it. For example:" msgstr "" #. Tag: screen -#: install-methods.xml:614 +#: install-methods.xml:618 #, no-c-format msgid "" "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n" @@ -435,91 +441,91 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:616 +#: install-methods.xml:620 #, no-c-format msgid "You might have written the <filename>mini.iso</filename> to the USB stick. In this case the second partition doesn't have to be created as, very nicely, it will already be present. Unplugging and replugging the USB stick should make the two partitions visible." msgstr "" #. Tag: title -#: install-methods.xml:630 +#: install-methods.xml:634 #, no-c-format msgid "Manually copying files to the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:631 +#: install-methods.xml:635 #, no-c-format msgid "An alternative way to set up your USB stick is to manually copy the installer files, and also a CD image to it. Note that the USB stick should be at least 1 GB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)." msgstr "" #. Tag: para -#: install-methods.xml:638 +#: install-methods.xml:642 #, no-c-format msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) <phrase arch=\"x86\">as well as <classname>syslinux</classname> and its configuration file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</classname> and its configuration file</phrase>." msgstr "" #. Tag: para -#: install-methods.xml:647 +#: install-methods.xml:651 #, no-c-format msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 1 GB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose." msgstr "" #. Tag: para -#: install-methods.xml:655 +#: install-methods.xml:659 #, no-c-format msgid "To use this image simply extract it directly to your USB stick:" msgstr "" #. Tag: screen -#: install-methods.xml:659 +#: install-methods.xml:663 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sdX</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:661 +#: install-methods.xml:665 #, 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:667 +#: install-methods.xml:671 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sdX2</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:669 +#: install-methods.xml:673 #, no-c-format msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done." msgstr "" #. Tag: title -#: install-methods.xml:686 +#: install-methods.xml:690 #, no-c-format msgid "Manually copying files to the USB stick — the flexible way" msgstr "" #. Tag: para -#: install-methods.xml:687 +#: install-methods.xml:691 #, 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 any ISO image, even a DVD image, to it." msgstr "" #. Tag: title -#: install-methods.xml:702 install-methods.xml:824 +#: install-methods.xml:706 install-methods.xml:828 #, no-c-format msgid "Partitioning the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:703 +#: install-methods.xml:707 #, 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:708 +#: install-methods.xml:712 #, no-c-format msgid "" "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition<footnote> <para> Don't forget to set the <quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR using: <informalexample><screen>\n" @@ -530,13 +536,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:732 +#: install-methods.xml:736 #, 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:742 +#: install-methods.xml:746 #, 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" @@ -545,19 +551,19 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:759 install-methods.xml:871 +#: install-methods.xml:763 install-methods.xml:875 #, no-c-format msgid "Adding the installer image" msgstr "" #. Tag: para -#: install-methods.xml:760 +#: install-methods.xml:764 #, 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 text-based 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:784 +#: install-methods.xml:788 #, 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" @@ -567,19 +573,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:796 +#: install-methods.xml:800 #, no-c-format msgid "To enable the boot prompt to permit further parameter appending, add a <userinput>prompt 1</userinput> line." msgstr "" #. Tag: para -#: install-methods.xml:801 install-methods.xml:911 +#: install-methods.xml:805 install-methods.xml:915 #, no-c-format msgid "If you used an <filename>hd-media</filename> image, you should now copy the ISO file of a &debian; ISO image<footnote> <para> You can use either a netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure to select one that fits. Note that the <quote>netboot <filename>mini.iso</filename></quote> image is not usable for this purpose. </para> </footnote> onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)." msgstr "" #. Tag: para -#: install-methods.xml:825 +#: install-methods.xml:829 #, 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" @@ -588,13 +594,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:842 +#: install-methods.xml:846 #, 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:851 +#: install-methods.xml:855 #, 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" @@ -607,37 +613,37 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:872 +#: install-methods.xml:876 #, 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:879 +#: install-methods.xml:883 #, no-c-format msgid "<filename>vmlinux</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:884 +#: install-methods.xml:888 #, no-c-format msgid "<filename>initrd.gz</filename> (initial ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:889 +#: install-methods.xml:893 #, no-c-format msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" msgstr "" #. Tag: para -#: install-methods.xml:894 +#: install-methods.xml:898 #, no-c-format msgid "<filename>boot.msg</filename> (optional boot message)" msgstr "" #. Tag: para -#: install-methods.xml:901 +#: install-methods.xml:905 #, no-c-format msgid "" "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n" @@ -655,259 +661,259 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:939 +#: install-methods.xml:943 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "" #. Tag: para -#: install-methods.xml:940 +#: install-methods.xml:944 #, 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:946 +#: install-methods.xml:950 #, 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:953 +#: install-methods.xml:957 #, 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:964 +#: install-methods.xml:968 #, 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:973 +#: install-methods.xml:977 #, no-c-format msgid "Hard disk installer booting from Linux using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: install-methods.xml:975 +#: install-methods.xml:979 #, 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:981 +#: install-methods.xml:985 #, 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:987 +#: install-methods.xml:991 #, no-c-format msgid "Copy the following files from the &debian; archives to a convenient location on your hard drive (note that LILO can not boot from files on an NTFS file system), for instance to <filename>/boot/newinstall/</filename>." msgstr "" #. Tag: para -#: install-methods.xml:995 +#: install-methods.xml:999 #, no-c-format msgid "<filename>vmlinuz</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:1000 +#: install-methods.xml:1004 #, no-c-format msgid "<filename>initrd.gz</filename> (ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:1007 +#: install-methods.xml:1011 #, no-c-format msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1017 +#: install-methods.xml:1021 #, no-c-format msgid "Hard disk installer booting from DOS using <command>loadlin</command>" msgstr "" #. Tag: para -#: install-methods.xml:1018 +#: install-methods.xml:1022 #, 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:1023 +#: install-methods.xml:1027 #, no-c-format msgid "Copy the following directories from a &debian; CD image to <filename>c:\\</filename>." msgstr "" #. Tag: para -#: install-methods.xml:1028 +#: install-methods.xml:1032 #, no-c-format msgid "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:1033 +#: install-methods.xml:1037 #, no-c-format msgid "<filename>/tools</filename> (loadlin tool)" msgstr "" #. Tag: title -#: install-methods.xml:1046 +#: install-methods.xml:1050 #, no-c-format msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1047 +#: install-methods.xml:1051 #, 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:1060 +#: install-methods.xml:1064 #, 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:1080 +#: install-methods.xml:1084 #, no-c-format msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1081 +#: install-methods.xml:1085 #, 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:1092 +#: install-methods.xml:1096 #, 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:1102 install-methods.xml:1428 +#: install-methods.xml:1106 install-methods.xml:1432 #, no-c-format msgid "vmlinux" msgstr "" #. Tag: filename -#: install-methods.xml:1107 install-methods.xml:1433 +#: install-methods.xml:1111 install-methods.xml:1437 #, no-c-format msgid "initrd.gz" msgstr "" #. Tag: filename -#: install-methods.xml:1112 install-methods.xml:1438 +#: install-methods.xml:1116 install-methods.xml:1442 #, no-c-format msgid "yaboot" msgstr "" #. Tag: filename -#: install-methods.xml:1117 install-methods.xml:1443 +#: install-methods.xml:1121 install-methods.xml:1447 #, no-c-format msgid "yaboot.conf" msgstr "" #. Tag: para -#: install-methods.xml:1122 +#: install-methods.xml:1126 #, 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:1130 +#: install-methods.xml:1134 #, no-c-format msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1143 +#: install-methods.xml:1147 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "" #. Tag: para -#: install-methods.xml:1144 +#: install-methods.xml:1148 #, 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:1152 +#: install-methods.xml:1156 #, 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:1159 +#: install-methods.xml:1163 #, 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:1173 +#: install-methods.xml:1177 #, 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:1179 +#: install-methods.xml:1183 #, 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:1184 +#: install-methods.xml:1188 #, 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:1192 +#: install-methods.xml:1196 #, no-c-format msgid "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. It's written by the same author as the <classname>syslinux</classname> bootloader and is therefore least likely to cause issues. A good alternative is <classname>atftpd</classname>." msgstr "" #. Tag: title -#: install-methods.xml:1208 +#: install-methods.xml:1212 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para -#: install-methods.xml:1209 +#: install-methods.xml:1213 #, 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:1221 +#: install-methods.xml:1225 #, no-c-format msgid "On a RARP server system using a Linux 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:1242 +#: install-methods.xml:1246 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1243 +#: install-methods.xml:1247 #, no-c-format msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-gnu;, the <classname>isc-dhcp-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp/dhcpd.conf</filename>):" msgstr "" #. Tag: screen -#: install-methods.xml:1250 +#: install-methods.xml:1254 #, no-c-format msgid "" "option domain-name \"example.com\";\n" @@ -932,25 +938,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1252 +#: install-methods.xml:1256 #, 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:1262 +#: install-methods.xml:1266 #, no-c-format msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/isc-dhcp-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1270 +#: install-methods.xml:1274 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1271 +#: install-methods.xml:1275 #, 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" @@ -985,19 +991,19 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1291 +#: install-methods.xml:1295 #, no-c-format msgid "Setting up a BOOTP server" msgstr "" #. Tag: para -#: install-methods.xml:1292 +#: install-methods.xml:1296 #, no-c-format msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian-gnu; these are contained in the <classname>bootp</classname> and <classname>isc-dhcp-server</classname> packages respectively." msgstr "" #. Tag: para -#: install-methods.xml:1300 +#: install-methods.xml:1304 #, no-c-format msgid "" "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run &debian;, the line in question should look like: <informalexample><screen>\n" @@ -1014,43 +1020,43 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1333 +#: install-methods.xml:1337 #, 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/dhcp/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/isc-dhcp-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1352 +#: install-methods.xml:1356 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1353 +#: install-methods.xml:1357 #, 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:1358 +#: install-methods.xml:1362 #, 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:1367 +#: install-methods.xml:1371 #, no-c-format msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian-gnu; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/srv/tftp</filename>. You may have to adjust the configuration examples in this section accordingly." msgstr "" #. Tag: para -#: install-methods.xml:1377 +#: install-methods.xml:1381 #, 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:1385 +#: install-methods.xml:1389 #, 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" @@ -1061,49 +1067,49 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1407 +#: install-methods.xml:1411 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1408 +#: install-methods.xml:1412 #, 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:1417 +#: install-methods.xml:1421 #, 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:1448 +#: install-methods.xml:1452 #, no-c-format msgid "boot.msg" msgstr "" #. Tag: para -#: install-methods.xml:1453 +#: install-methods.xml:1457 #, 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:1461 +#: install-methods.xml:1465 #, 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:1473 +#: install-methods.xml:1477 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1474 +#: install-methods.xml:1478 #, 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" @@ -1112,55 +1118,55 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1490 +#: install-methods.xml:1494 #, 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:1497 +#: install-methods.xml:1501 #, 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:1508 +#: install-methods.xml:1512 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1509 +#: install-methods.xml:1513 #, 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:1617 +#: install-methods.xml:1621 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1618 +#: install-methods.xml:1622 #, no-c-format msgid "For installing on multiple computers it's possible to do fully automatic installations. &debian; packages intended for this include <classname>fai-quickstart</classname> (which can use an install server) and the &debian; Installer itself. Have a look at the <ulink url=\"http://fai-project.org\">FAI home page</ulink> for detailed information." msgstr "" #. Tag: title -#: install-methods.xml:1630 +#: install-methods.xml:1634 #, no-c-format msgid "Automatic Installation Using the &debian; Installer" msgstr "" #. Tag: para -#: install-methods.xml:1631 +#: install-methods.xml:1635 #, 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:1638 +#: install-methods.xml:1642 #, no-c-format msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>." msgstr "" diff --git a/po/pot/partitioning.pot b/po/pot/partitioning.pot index 1a78d1584..dc43fc047 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: 2015-01-09 19:07+0000\n" +"POT-Creation-Date: 2015-04-15 20:29+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" @@ -371,7 +371,7 @@ msgstr "" #. Tag: para #: partitioning.xml:291 #, no-c-format -msgid "As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE drive on <filename>/dev/hda</filename>. There might be a 500MB partition for another operating system on <filename>/dev/hda1</filename>, a 32MB swap partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/dev/hda2</filename> as the Linux partition." +msgid "As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE drive on <filename>/dev/sda</filename>. There might be a 500MB partition for another operating system on <filename>/dev/sda1</filename>, a 32MB swap partition on <filename>/dev/sda3</filename> and about 1.2GB on <filename>/dev/sda2</filename> as the Linux partition." msgstr "" #. Tag: para @@ -407,263 +407,245 @@ msgstr "" #. Tag: para #: partitioning.xml:335 #, no-c-format -msgid "The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</filename>." +msgid "The first hard disk detected is named <filename>/dev/sda</filename>." msgstr "" #. Tag: para -#: partitioning.xml:341 +#: partitioning.xml:340 #, no-c-format -msgid "The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, and so on." +msgid "The second hard disk detected is named <filename>/dev/sdb</filename>, and so on." msgstr "" #. Tag: para -#: partitioning.xml:347 +#: partitioning.xml:346 #, no-c-format msgid "The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as <filename>/dev/sr0</filename>." msgstr "" #. Tag: para -#: partitioning.xml:353 -#, no-c-format -msgid "The master disk on IDE primary controller is named <filename>/dev/hda</filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:359 -#, no-c-format -msgid "The slave disk on IDE primary controller is named <filename>/dev/hdb</filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:365 -#, no-c-format -msgid "The master and slave disks of the secondary controller can be called <filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, respectively. Newer IDE controllers can actually have two channels, effectively acting like two controllers." -msgstr "" - -#. Tag: para -#: partitioning.xml:376 +#: partitioning.xml:355 #, no-c-format msgid "The first DASD device is named <filename>/dev/dasda</filename>." msgstr "" #. Tag: para -#: partitioning.xml:382 +#: partitioning.xml:361 #, no-c-format msgid "The second DASD device is named <filename>/dev/dasdb</filename>, and so on." msgstr "" #. Tag: para -#: partitioning.xml:390 +#: partitioning.xml:369 #, no-c-format msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>sda1</filename> and <filename>sda2</filename> represent the first and second partitions of the first SCSI disk drive in your system." msgstr "" #. Tag: para -#: partitioning.xml:397 +#: partitioning.xml:376 #, no-c-format msgid "Here is a real-life example. Let's assume you have a system with 2 SCSI disks, one at SCSI address 2 and the other at SCSI address 4. The first disk (at address 2) is then named <filename>sda</filename>, and the second <filename>sdb</filename>. If the <filename>sda</filename> drive has 3 partitions on it, these will be named <filename>sda1</filename>, <filename>sda2</filename>, and <filename>sda3</filename>. The same applies to the <filename>sdb</filename> disk and its partitions." msgstr "" #. Tag: para -#: partitioning.xml:408 +#: partitioning.xml:387 #, no-c-format msgid "Note that if you have two SCSI host bus adapters (i.e., controllers), the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities." msgstr "" #. Tag: para -#: partitioning.xml:415 +#: partitioning.xml:394 #, no-c-format -msgid "Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are numbered starting at 5, so the first logical partition on that same drive is <filename>/dev/hda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. This applies to SCSI disks as well as IDE disks." +msgid "Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the first drive is <filename>/dev/sda1</filename>. The logical partitions are numbered starting at 5, so the first logical partition on that same drive is <filename>/dev/sda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself." msgstr "" #. Tag: para -#: partitioning.xml:426 +#: partitioning.xml:404 #, no-c-format msgid "Sun disk partitions allow for 8 separate partitions (or slices). The third partition is usually (and is preferred to have) the <quote>Whole Disk</quote> partition. This partition references all of the sectors of the disk, and is used by the boot loader (either SILO, or Sun's)." msgstr "" #. Tag: para -#: partitioning.xml:433 +#: partitioning.xml:411 #, no-c-format msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> represent the first and second partitions of the first DASD device in your system." msgstr "" #. Tag: title -#: partitioning.xml:448 +#: partitioning.xml:426 #, no-c-format msgid "&debian; Partitioning Programs" msgstr "" #. Tag: para -#: partitioning.xml:449 +#: partitioning.xml:427 #, no-c-format msgid "Several varieties of partitioning programs have been adapted by &debian; developers to work on various types of hard disks and computer architectures. Following is a list of the program(s) applicable for your architecture." msgstr "" #. Tag: para -#: partitioning.xml:462 +#: partitioning.xml:440 #, no-c-format 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: para -#: partitioning.xml:474 +#: partitioning.xml:452 #, no-c-format msgid "The original Linux disk partitioner, good for gurus." msgstr "" #. Tag: para -#: partitioning.xml:478 +#: partitioning.xml:456 #, no-c-format msgid "Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that <command>fdisk</command> represents them (or not) can make the device names differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</ulink>." msgstr "" #. Tag: para -#: partitioning.xml:491 +#: partitioning.xml:469 #, no-c-format msgid "A simple-to-use, full-screen disk partitioner for the rest of us." msgstr "" #. Tag: para -#: partitioning.xml:495 +#: partitioning.xml:473 #, no-c-format msgid "Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result." msgstr "" #. Tag: para -#: partitioning.xml:505 +#: partitioning.xml:483 #, no-c-format msgid "Atari-aware version of <command>fdisk</command>." msgstr "" #. Tag: para -#: partitioning.xml:514 +#: partitioning.xml:492 #, no-c-format msgid "Amiga-aware version of <command>fdisk</command>." msgstr "" #. Tag: para -#: partitioning.xml:523 +#: partitioning.xml:501 #, no-c-format msgid "Mac-aware version of <command>fdisk</command>." msgstr "" #. Tag: para -#: partitioning.xml:532 +#: partitioning.xml:510 #, no-c-format msgid "PowerMac-aware version of <command>fdisk</command>, also used by BVM and Motorola VMEbus systems." msgstr "" #. Tag: para -#: partitioning.xml:542 +#: partitioning.xml:520 #, no-c-format msgid "&arch-title; version of <command>fdisk</command>; Please read the fdasd manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and Installation Commands</ulink> for details." msgstr "" #. Tag: para -#: partitioning.xml:553 +#: partitioning.xml:531 #, no-c-format msgid "One of these programs will be run by default when you select <guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible to use a different partitioning tool from the command line on VT2, but this is not recommended." msgstr "" #. Tag: para -#: partitioning.xml:560 +#: partitioning.xml:538 #, no-c-format msgid "Remember to mark your boot partition as <quote>Bootable</quote>." msgstr "" #. Tag: para -#: partitioning.xml:563 +#: partitioning.xml:541 #, no-c-format msgid "One key point when partitioning for Mac type disks is that the swap partition is identified by its name; it must be named <quote>swap</quote>. All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you should take if you are sharing your disk with MacOS." msgstr "" #. Tag: title -#: partitioning.xml:579 partitioning.xml:603 partitioning.xml:699 partitioning.xml:813 partitioning.xml:890 +#: partitioning.xml:557 partitioning.xml:581 partitioning.xml:677 partitioning.xml:791 partitioning.xml:868 #, no-c-format msgid "Partitioning for &arch-title;" msgstr "" #. Tag: para -#: partitioning.xml:580 +#: partitioning.xml:558 #, no-c-format msgid "PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere in the first 2GB. This is where the boot loader and an optional kernel and RAMdisk will be stored, so make it big enough for that — at least 4Mb (I like 8–16MB). An additional requirement of the firmware is that the Linux kernel must reside within the first 2GB of the disk. This is typically achieved by making the root ext2 partition fit entirely within the first 2GB of the disk. Alternatively you can create a small ext2 partition near the start of the disk and mount that on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. <filename>/boot</filename> needs to be big enough to hold whatever kernels (and backups) you might wish to load; 25–50MB is generally sufficient." msgstr "" #. Tag: para -#: partitioning.xml:604 +#: partitioning.xml:582 #, no-c-format msgid "If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing &debian;, you may need to resize its partition to free up space for the &debian; installation. The installer supports resizing of both FAT and NTFS filesystems; when you get to the installer's partitioning step, select the option <guimenuitem>Manual</guimenuitem> and then simply select an existing partition and change its size." msgstr "" #. Tag: para -#: partitioning.xml:614 +#: partitioning.xml:592 #, no-c-format msgid "The PC BIOS generally adds additional constraints for disk partitioning. There is a limit to how many <quote>primary</quote> and <quote>logical</quote> partitions a drive can contain. Additionally, with pre 1994–98 BIOSes, there are limits to where on the drive the BIOS can boot from. More information can be found in the <ulink url=\"&url-partition-howto;\">Linux Partition HOWTO</ulink>, but this section will include a brief overview to help you plan most situations." msgstr "" #. Tag: para -#: partitioning.xml:624 +#: partitioning.xml:602 #, no-c-format msgid "<quote>Primary</quote> partitions are the original partitioning scheme for PC disks. However, there can only be four of them. To get past this limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By setting one of your primary partitions as an extended partition, you can subdivide all the space allocated to that partition into logical partitions. You can create up to 60 logical partitions per extended partition; however, you can only have one extended partition per drive." msgstr "" #. Tag: para -#: partitioning.xml:635 +#: partitioning.xml:613 #, no-c-format msgid "Linux limits the partitions per drive to 255 partitions for SCSI disks (3 usable primary partitions, 252 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 -#: partitioning.xml:645 +#: partitioning.xml:623 #, no-c-format msgid "If you have a large IDE disk, and are using neither LBA addressing, nor overlay drivers (sometimes provided by hard disk manufacturers), then the boot partition (the partition containing your kernel image) must be placed within the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation)." msgstr "" #. Tag: para -#: partitioning.xml:653 +#: partitioning.xml:631 #, 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 &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 -#: partitioning.xml:667 +#: partitioning.xml:645 #, no-c-format msgid "If you have a large disk, you might have to use cylinder translation techniques, which you can set from your BIOS setup program, such as LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). More information about issues with large disks can be found in the <ulink url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a cylinder translation scheme, and the BIOS does not support the large disk access extensions, then your boot partition has to fit within the <emphasis>translated</emphasis> representation of the 1024th cylinder." msgstr "" #. Tag: para -#: partitioning.xml:679 +#: partitioning.xml:657 #, 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 &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 -#: partitioning.xml:700 +#: partitioning.xml:678 #, no-c-format msgid "The <command>partman</command> disk partitioner is the default partitioning tool for the installer. It manages the set of partitions and their mount points to ensure that the disks and filesystems are properly configured for a successful installation. It actually uses <command>parted</command> to do the on-disk partitioning." msgstr "" #. Tag: title -#: partitioning.xml:712 +#: partitioning.xml:690 #, no-c-format msgid "EFI Recognized Formats" msgstr "" #. Tag: para -#: partitioning.xml:713 +#: partitioning.xml:691 #, no-c-format msgid "The IA-64 EFI firmware supports two partition table (or disk label) formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer recommended for IA-64 systems. Although the installer also provides <command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly." msgstr "" #. Tag: para -#: partitioning.xml:725 +#: partitioning.xml:703 #, no-c-format msgid "The automatic partitioning recipes for <command>partman</command> allocate an EFI partition as the first partition on the disk. You can also set up the partition under the <guimenuitem>Guided partitioning</guimenuitem> from the main menu in a manner similar to setting up a <emphasis>swap</emphasis> partition." msgstr "" #. Tag: para -#: partitioning.xml:733 +#: partitioning.xml:711 #, no-c-format msgid "" "The <command>partman</command> partitioner will handle most disk layouts. For those rare cases where it is necessary to manually set up a disk, you can use the shell as described above and run the <command>parted</command> utility directly using its command line interface. Assuming that you want to erase your whole disk and create a GPT table and some partitions, then something similar to the following command sequence could be used: <informalexample><screen>\n" @@ -678,97 +660,97 @@ msgid "" msgstr "" #. Tag: title -#: partitioning.xml:758 +#: partitioning.xml:736 #, no-c-format msgid "Boot Loader Partition Requirements" msgstr "" #. Tag: para -#: partitioning.xml:759 +#: partitioning.xml:737 #, no-c-format msgid "ELILO, the IA-64 boot loader, requires a partition containing a FAT file system with the <userinput>boot</userinput> flag set. The partition must be big enough to hold the boot loader and any kernels or RAMdisks you may wish to boot. A minimum size would be about 20MB, but if you expect to run with multiple kernels, then 128MB might be a better size." msgstr "" #. Tag: para -#: partitioning.xml:768 +#: partitioning.xml:746 #, no-c-format msgid "The EFI Boot Manager and the EFI Shell fully support the GPT table so the boot partition does not necessarily have to be the first partition or even on the same disk. This is convenient if you should forget to allocate the partition and only find out after you have formatted the other partitions on your disk(s). The <command>partman</command> partitioner checks for an EFI partition at the same time it checks for a properly set up <emphasis>root</emphasis> partition. This gives you an opportunity to correct the disk layout before the package install begins. The easiest way to correct this omission is to shrink the last partition of the disk to make enough free space for adding an EFI partition." msgstr "" #. Tag: para -#: partitioning.xml:783 +#: partitioning.xml:761 #, no-c-format msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem." msgstr "" #. Tag: title -#: partitioning.xml:791 +#: partitioning.xml:769 #, no-c-format msgid "EFI Diagnostic Partitions" msgstr "" #. Tag: para -#: partitioning.xml:792 +#: partitioning.xml:770 #, no-c-format msgid "The EFI firmware is significantly more sophisticated than the usual BIOS seen on most x86 PCs. Some system vendors take advantage of the ability of the EFI to access files and run programs from a hard disk filesystem to store diagnostics and EFI based system management utilities on the hard disk. This is a separate FAT format filesystem on the system disk. Consult the system documentation and accessories that come with the system for details. The easiest time to set up a diagnostics partition is at the same time you set up the EFI boot partition." msgstr "" #. Tag: para -#: partitioning.xml:814 +#: partitioning.xml:792 #, no-c-format msgid "SGI machines require an SGI disk label in order to make the system bootable from hard disk. It can be created in the fdisk expert menu. The thereby created volume header (partition number 9) should be at least 3MB large. If the volume header created is too small, you can simply delete partition number 9 and re-add it with a different size. Note that the volume header must start at sector 0." msgstr "" #. Tag: title -#: partitioning.xml:831 +#: partitioning.xml:809 #, no-c-format msgid "Partitioning Newer PowerMacs" msgstr "" #. Tag: para -#: partitioning.xml:832 +#: partitioning.xml:810 #, no-c-format msgid "If you are installing onto a NewWorld PowerMac you must create a special bootstrap partition to hold the boot loader. The size of this partition must have at least 819200 bytes and its partition type must be <emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not created with the <emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made bootable from the hard disk. This partition can easily be created by creating a new partition in <command>partman</command> and telling it to use it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</command> using the <userinput>b</userinput> command." msgstr "" #. Tag: para -#: partitioning.xml:845 +#: partitioning.xml:823 #, no-c-format msgid "The special partition type Apple_Bootstrap is required to prevent MacOS from mounting and damaging the bootstrap partition, as there are special modifications made to it in order for OpenFirmware to boot it automatically." msgstr "" #. Tag: para -#: partitioning.xml:852 +#: partitioning.xml:830 #, no-c-format msgid "Note that the bootstrap partition is only meant to hold 3 very small files: the <command>yaboot</command> binary, its configuration <filename>yaboot.conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</command>. It need not and must not be mounted on your file system nor have kernels or anything else copied to it. The <command>ybin</command> and <command>mkofboot</command> utilities are used to manipulate this partition." msgstr "" #. Tag: para -#: partitioning.xml:862 +#: partitioning.xml:840 #, no-c-format 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 -#: partitioning.xml:874 +#: partitioning.xml:852 #, no-c-format msgid "Apple disks normally have several small driver partitions. If you intend to dual boot your machine with MacOSX, you should retain these partitions and a small HFS partition (800k is the minimum size). That is because MacOSX, on every boot, offers to initialize any disks which do not have active MacOS partitions and driver partitions." msgstr "" #. Tag: para -#: partitioning.xml:891 +#: partitioning.xml:869 #, no-c-format msgid "Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. The <keycap>s</keycap> key is used in <command>fdisk</command> to create Sun disk labels." msgstr "" #. Tag: para -#: partitioning.xml:899 +#: partitioning.xml:877 #, no-c-format msgid "Furthermore, on &arch-title; disks, make sure your first partition on your boot disk starts at cylinder 0. While this is required, it also means that the first partition will contain the partition table and the boot block, which are the first two sectors of the disk. You must <emphasis>not</emphasis> put swap on the first partition of the boot drive, since swap partitions do not preserve the first few sectors of the partition. You can put Ext2 or UFS partitions there; these will leave the partition table and the boot block alone." msgstr "" #. Tag: para -#: partitioning.xml:910 +#: partitioning.xml:888 #, no-c-format msgid "It is also advised that the third partition should be of type <quote>Whole disk</quote> (type 5), and contain the entire disk (from the first cylinder to the last). This is simply a convention of Sun disk labels, and helps the <command>SILO</command> boot loader keep its bearings." msgstr "" diff --git a/po/pot/post-install.pot b/po/pot/post-install.pot index 81dee7174..825c248e2 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: 2014-01-29 10:50+0000\n" +"POT-Creation-Date: 2015-04-15 20:29+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" @@ -509,35 +509,35 @@ msgstr "" #. Tag: para #: post-install.xml:700 #, no-c-format -msgid "To access rescue mode, type <userinput>rescue</userinput> at the <prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/enable=true</userinput> boot parameter. You'll be shown the first few screens of the installer, with a note in the corner of the display to indicate that this is rescue mode, not a full installation. Don't worry, your system is not about to be overwritten! Rescue mode simply takes advantage of the hardware detection facilities available in the installer to ensure that your disks, network devices, and so on are available to you while repairing your system." +msgid "To access rescue mode, select <userinput>rescue</userinput> from the boot menu, type <userinput>rescue</userinput> at the <prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/enable=true</userinput> boot parameter. You'll be shown the first few screens of the installer, with a note in the corner of the display to indicate that this is rescue mode, not a full installation. Don't worry, your system is not about to be overwritten! Rescue mode simply takes advantage of the hardware detection facilities available in the installer to ensure that your disks, network devices, and so on are available to you while repairing your system." msgstr "" #. Tag: para -#: post-install.xml:715 +#: post-install.xml:717 #, no-c-format msgid "Instead of the partitioning tool, you should now be presented with a list of the partitions on your system, and asked to select one of them. Normally, you should select the partition containing the root file system that you need to repair. You may select partitions on RAID and LVM devices as well as those created directly on disks." msgstr "" #. Tag: para -#: post-install.xml:723 +#: post-install.xml:725 #, 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=\"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 -#: post-install.xml:735 +#: post-install.xml:737 #, no-c-format msgid "If the installer cannot run a usable shell in the root file system you selected, perhaps because the file system is corrupt, then it will issue a warning and offer to give you a shell in the installer environment instead. You may not have as many tools available in this environment, but they will often be enough to repair your system anyway. The root file system you selected will be mounted on the <filename>/target</filename> directory." msgstr "" #. Tag: para -#: post-install.xml:744 +#: post-install.xml:746 #, no-c-format msgid "In either case, after you exit the shell, the system will reboot." msgstr "" #. Tag: para -#: post-install.xml:748 +#: post-install.xml:750 #, no-c-format msgid "Finally, note that repairing broken systems can be difficult, and this manual does not attempt to go into all the things that might have gone wrong or how to fix them. If you have problems, consult an expert." msgstr "" diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot index 4fb9012b2..b94b51f6e 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: 2014-08-05 21:38+0000\n" +"POT-Creation-Date: 2015-04-15 20:29+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" @@ -981,7 +981,7 @@ msgid "The BIOS provides the basic functions needed to boot your machine and to msgstr "" #. Tag: title -#: preparing.xml:1138 preparing.xml:1290 +#: preparing.xml:1138 preparing.xml:1479 #, no-c-format msgid "Boot Device Selection" msgstr "" @@ -1001,13 +1001,13 @@ msgstr "" #. Tag: para #: preparing.xml:1154 #, no-c-format -msgid "Most BIOS versions allow to call up a boot menu on system startup in which you select from which device the computer should start for the current session. If this option is available, the BIOS usually displays a short message like <quote>press <keycap>F12</keycap> for boot menu</quote> on system startup. The actual key used to select this menu varies from system to system; commonly used keys are <keycap>F12</keycap>, <keycap>F11</keycap> and <keycap>F8</keycap>. Choosing a device from this menu does not change the default boot order of the BIOS, i.e. you can start once from a USB stick while having configured the internal harddisk as the normal primary boot device." +msgid "Most BIOS versions allow you to call up a boot menu on system startup in which you select from which device the computer should start for the current session. If this option is available, the BIOS usually displays a short message like <quote>press <keycap>F12</keycap> for boot menu</quote> on system startup. The actual key used to select this menu varies from system to system; commonly used keys are <keycap>F12</keycap>, <keycap>F11</keycap> and <keycap>F8</keycap>. Choosing a device from this menu does not change the default boot order of the BIOS, i.e. you can start once from a USB stick while having configured the internal harddisk as the normal primary boot device." msgstr "" #. Tag: para #: preparing.xml:1168 #, no-c-format -msgid "If your BIOS does not provide you with a boot menu to do ad-hoc choices of the current boot device, you have to change your BIOS setup to make the device from which the &d-i; shall be booted the primary boot device." +msgid "If your BIOS does not provide you with a boot menu to do ad-hoc choices of the current boot device, you will have to change your BIOS setup to make the device from which the &d-i; shall be booted the primary boot device." msgstr "" #. Tag: para @@ -1057,37 +1057,279 @@ msgid "The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 and 2.4 msgstr "" #. Tag: title -#: preparing.xml:1257 +#: preparing.xml:1253 #, no-c-format -msgid "Invoking OpenBoot" +msgid "How to update bare metal ppc64el firmware" +msgstr "" + +#. Tag: para +#: preparing.xml:1254 +#, no-c-format +msgid "This is an excerpt from <ulink url=\"&url-ibm-powerkvm;\">IBM PowerKVM on IBM POWER8</ulink>" msgstr "" #. Tag: para #: preparing.xml:1259 #, no-c-format +msgid "Open Power Abstraction Layer (OPAL) is the system firmware in the stack of POWER processor-based server." +msgstr "" + +#. Tag: para +#: preparing.xml:1264 +#, no-c-format +msgid "There may be instances when the user might have to upgrade the Power Systems firmware to a more recent level to acquire new features or additional support for devices." +msgstr "" + +#. Tag: para +#: preparing.xml:1270 +#, no-c-format +msgid "Make sure that the following requirements are met:" +msgstr "" + +#. Tag: para +#: preparing.xml:1275 +#, no-c-format +msgid "an OS to be running on the system;" +msgstr "" + +#. Tag: para +#: preparing.xml:1277 +#, no-c-format +msgid "the .img file of the OPAL level that the user needs to update to;" +msgstr "" + +#. Tag: para +#: preparing.xml:1279 +#, no-c-format +msgid "the machine isn't under HMC control." +msgstr "" + +#. Tag: para +#: preparing.xml:1283 +#, no-c-format +msgid "Power Systems has two sides of flash to boot firmware from, namely permanent and temporary. This provides a way to test firmware updates on the temporary side of the flash before committing the tested changes to the permanent side, thereby committing the new updates." +msgstr "" + +#. Tag: para +#: preparing.xml:1290 +#, no-c-format +msgid "Perform the following steps for the update:" +msgstr "" + +#. Tag: para +#: preparing.xml:1295 +#, no-c-format +msgid "Save the level of the existing firmware before really updating. In ASM, in the system menu, click <command>Service Aids ??? Service Processor Command Line</command>, and run the following command:" +msgstr "" + +#. Tag: screen +#: preparing.xml:1299 +#, no-c-format +msgid "cupdcmd -f" +msgstr "" + +#. Tag: para +#: preparing.xml:1300 +#, no-c-format +msgid "Download the .img file of the level of firmware to be updated to a location in the host filesystem. Refer to IBM Fix Central for downloading the image file." +msgstr "" + +#. Tag: para +#: preparing.xml:1304 +#, no-c-format +msgid "Verify the image downloaded by running the following command and save the output." +msgstr "" + +#. Tag: screen +#: preparing.xml:1307 +#, no-c-format +msgid "$update_flash -v -f <file_name.img>" +msgstr "" + +#. Tag: para +#: preparing.xml:1309 +#, no-c-format +msgid "Update the firmware by running the following command." +msgstr "" + +#. Tag: screen +#: preparing.xml:1311 +#, no-c-format +msgid "$update_flash -f <file_name.img>" +msgstr "" + +#. Tag: para +#: preparing.xml:1317 +#, no-c-format +msgid "The command reboots the system and therefore, sessions if any, would be lost." +msgstr "" + +#. Tag: para +#: preparing.xml:1320 +#, no-c-format +msgid "Do not reboot or switch off the system until it is back." +msgstr "" + +#. Tag: para +#: preparing.xml:1327 +#, no-c-format +msgid "Verify the updated firmware level of the temporary side of the flash as in step 1." +msgstr "" + +#. Tag: para +#: preparing.xml:1330 +#, no-c-format +msgid "" + "In case the update has to be reverted, the user can do so by running this command: <informalexample><screen>\n" + " $update_flash -r\n" + "</screen></informalexample> Rejection would reject only the temporary side of the flash. Therefore, the new level should be committed to the permanent side only after thorough testing of the new firmware." +msgstr "" + +#. Tag: para +#: preparing.xml:1337 +#, no-c-format +msgid "The new updated level can be committed to the permanent side of the flash by running the following command." +msgstr "" + +#. Tag: screen +#: preparing.xml:1340 +#, no-c-format +msgid "$update_flash -c" +msgstr "" + +#. Tag: title +#: preparing.xml:1348 +#, no-c-format +msgid "Updating KVM guest firmware (SLOF)" +msgstr "" + +#. Tag: para +#: preparing.xml:1349 +#, no-c-format +msgid "Slimline Open Firmware (SLOF) is an implementation of the IEEE 1275 standard. It can be used as partition firmware for pSeries machines running on QEMU or KVM." +msgstr "" + +#. Tag: para +#: preparing.xml:1356 +#, no-c-format +msgid "" + "The package qemu-slof is, in fact, a dependency of package qemu-system-ppc (which also provides the virtual package qemu-system-ppc64), and can be installed or updated via <command>apt-get</command> tool on Debian-based distros. Like so: <informalexample><screen>\n" + "# apt-get install qemu-slof\n" + "</screen></informalexample> SLOF can also be installed into rpm-based distribution systems, given the proper repository or rpm package. Additionally, the upstream source code is available at http://github.com/leilihh/SLOF." +msgstr "" + +#. Tag: para +#: preparing.xml:1370 +#, no-c-format +msgid "Thus, one can use a different SLOF file rather than the default, when running <command>qemu-system</command>, by adding the command line argument <userinput>-bios <slof_file> </userinput> when starting qemu." +msgstr "" + +#. Tag: title +#: preparing.xml:1380 +#, no-c-format +msgid "Updating PowerKVM hypervisor" +msgstr "" + +#. Tag: title +#: preparing.xml:1381 +#, no-c-format +msgid "Instructions for Netboot installation" +msgstr "" + +#. Tag: para +#: preparing.xml:1382 +#, no-c-format +msgid "" + "You will need a DHCP/TFTP (BOOTP) server, as well as a web server. After downloading ibm-powerkvm-*-ppc64-service-*.iso, mount loop it and unpack it into some directory within your HTTP server www root structure (say wwwroot): <informalexample><screen>\n" + "# cd <directory-where-the-iso-is>\n" + "# mkdir ./iso\n" + "# sudo mount -o loop ibm-powerkvm-*-ppc64-service-*.iso ./iso\n" + "# cp -a ./iso/* <path-to-wwwroot>\n" + "</screen></informalexample> Create the petitboot.conf file in a directory under your tftproot, say /tftproot/powerkvm, with the following contents: <informalexample><screen>\n" + "label PowerKVM Automated Install\n" + "kernel http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/ppc/ppc64/vmlinuz\n" + "initrd http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/ppc/ppc64/initrd.img\n" + "append root=live:http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/LiveOS/squashfs.img repo=http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/packages rd.dm=0 rd.md=0 console=hvc0 console=tty0\n" + "</screen></informalexample> Editing your dhcpd.conf, set this directive at the beginning: <informalexample><screen>\n" + "option conf-file code 209 = text;\n" + "</screen></informalexample> Add the system directive: <informalexample><screen>\n" + "host <your-system> {\n" + " hardware ethernet <system macaddr>\n" + " fixed-address <system ip>;\n" + " option host-name \"<system hostname>\";\n" + " option conf-file \"<powerkvm/petitboot.conf>\";\n" + " }\n" + "</screen></informalexample> Reboot the dhcp server." +msgstr "" + +#. Tag: para +#: preparing.xml:1406 +#, no-c-format +msgid "Boot your PowerLinux machine." +msgstr "" + +#. Tag: para +#: preparing.xml:1410 +#, no-c-format +msgid "" + "There should be the following option at petitboot (select it): <informalexample><screen>\n" + "\"Power KVM Automated Install\" \n" + "</screen></informalexample> The installer menu should appear automatically." +msgstr "" + +#. Tag: title +#: preparing.xml:1421 +#, no-c-format +msgid "Instructions for DVD" +msgstr "" + +#. Tag: para +#: preparing.xml:1422 +#, no-c-format +msgid "Boot the ISO ibm-powerkvm-*-ppc64-service-*.iso (either burn a DVD or make it virtual if using QEMU) and simply wait for the boot." +msgstr "" + +#. Tag: para +#: preparing.xml:1425 +#, no-c-format +msgid "" + "There should be the following option at petitboot (select it): <informalexample><screen>\n" + "\"POWERKVM_LIVECD\" \n" + "</screen></informalexample> The installer menu should appear automatically." +msgstr "" + +#. Tag: title +#: preparing.xml:1446 +#, no-c-format +msgid "Invoking OpenBoot" +msgstr "" + +#. Tag: para +#: preparing.xml:1448 +#, no-c-format msgid "OpenBoot provides the basic functions needed to boot the &arch-title; architecture. This is rather similar in function to the BIOS in the x86 architecture, although much nicer. The Sun boot PROMs have a built-in forth interpreter which lets you do quite a number of things with your machine, such as diagnostics and simple scripts." msgstr "" #. Tag: para -#: preparing.xml:1267 +#: preparing.xml:1456 #, no-c-format msgid "To get to the boot prompt you need to hold down the <keycap>Stop</keycap> key (on older type 4 keyboards, use the <keycap>L1</keycap> key, if you have a PC keyboard adapter, use the <keycap>Break</keycap> key) and press the <keycap>A</keycap> key. The boot PROM will give you a prompt, either <userinput>ok</userinput> or <userinput>></userinput>. It is preferred to have the <userinput>ok</userinput> prompt. So if you get the old style prompt, hit the <keycap>n</keycap> key to get the new style prompt." msgstr "" #. Tag: para -#: preparing.xml:1279 +#: preparing.xml:1468 #, no-c-format msgid "If you are using a serial console, send a break to the machine. With Minicom, use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type <userinput>%~break</userinput>. Consult the documentation of your terminal emulator if you are using a different program." msgstr "" #. Tag: para -#: preparing.xml:1292 +#: preparing.xml:1481 #, no-c-format msgid "You can use OpenBoot to boot from specific devices, and also to change your default boot device. However, you need to know some details about how OpenBoot names devices; it's considerably different from Linux device naming, described in <xref linkend=\"device-names\"/>. Also, the command will vary a bit, depending on what version of OpenBoot you have. More information about OpenBoot can be found in the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>." msgstr "" #. Tag: para -#: preparing.xml:1302 +#: preparing.xml:1491 #, no-c-format msgid "" "Typically, with newer revisions, you can use OpenBoot devices such as <quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, <quote>disk</quote>, or <quote>disk2</quote>. These have the obvious meanings; the <quote>net</quote> device is for booting from the network. Additionally, the device name can specify a particular partition of a disk, such as <quote>disk2:a</quote> to boot disk2, first partition. Full OpenBoot device names have the form: <informalexample> <screen>\n" @@ -1098,7 +1340,7 @@ msgid "" msgstr "" #. Tag: para -#: preparing.xml:1325 +#: preparing.xml:1514 #, no-c-format msgid "" "To boot from a specific device, use the command <userinput>boot <replaceable>device</replaceable></userinput>. You can set this behavior as the default using the <userinput>setenv</userinput> command. However, the name of the variable to set changed between OpenBoot revisions. In OpenBoot 1.x, use the command <userinput>setenv boot-from <replaceable>device</replaceable></userinput>. In later revisions of OpenBoot, use the command <userinput>setenv boot-device <replaceable>device</replaceable></userinput>. Note, this is also configurable using the <command>eeprom</command> command on Solaris, or modifying the appropriate files in <filename>/proc/openprom/options/</filename>, for example under Linux: <informalexample><screen>\n" @@ -1107,235 +1349,259 @@ msgid "" msgstr "" #. Tag: screen -#: preparing.xml:1344 +#: preparing.xml:1533 #, no-c-format msgid "eeprom boot-device=disk1:1" msgstr "" #. Tag: title -#: preparing.xml:1354 +#: preparing.xml:1543 #, no-c-format msgid "BIOS Setup" msgstr "" #. Tag: para -#: preparing.xml:1355 +#: preparing.xml:1544 #, no-c-format 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 -#: preparing.xml:1367 +#: preparing.xml:1556 #, no-c-format msgid "Linux on this platform runs either natively on the bare machine, in a so-called LPAR (Logical Partition) or in a virtual machine supplied by the VM system. Boot media differs depending on the runtime mode. For example, you can use the virtual card reader of a virtual machine, or boot from the HMC (Hardware Management Console) of an LPAR if the HMC and this option is available for you." msgstr "" #. Tag: para -#: preparing.xml:1376 +#: preparing.xml:1565 #, no-c-format msgid "Before you actually perform an installation, you have to go over some design and preparation steps. IBM has made documentation available about the whole process, e.g. how to prepare an installation medium and how actually to boot from that medium. Duplicating that information here is neither possible nor necessary. However, we will describe here which kind of &debian;-specific data is needed and where to find it. Using both sources of information, you have to prepare your machine and the installation medium before you can perform a boot from it. When you see the welcome message in your client session, return to this document to go through the &debian;-specific installation steps." msgstr "" #. Tag: title -#: preparing.xml:1393 +#: preparing.xml:1582 #, no-c-format msgid "Native and LPAR installations" msgstr "" #. Tag: para -#: preparing.xml:1394 +#: preparing.xml:1583 #, no-c-format msgid "Please refer to chapter 5 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.2 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up an LPAR for Linux." msgstr "" #. Tag: title -#: preparing.xml:1408 +#: preparing.xml:1597 #, no-c-format msgid "Installation as a VM guest" msgstr "" #. Tag: para -#: preparing.xml:1410 +#: preparing.xml:1599 #, no-c-format msgid "Please refer to chapter 6 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.1 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up a VM guest for running Linux." msgstr "" #. Tag: para -#: preparing.xml:1420 +#: preparing.xml:1609 #, no-c-format msgid "You need to copy all the files from the <filename>generic</filename> sub-directory to your CMS disk. Be sure to transfer <filename>kernel.debian</filename> and <filename>initrd.debian</filename> in binary mode with a fixed record length of 80 characters (by specifying <userinput>BINARY</userinput> and <userinput>LOCSITE FIX 80</userinput> in your FTP client). <filename>parmfile.debian</filename> can be in either ASCII or EBCDIC format. A sample <filename>debian.exec</filename> script, which will punch the files in the proper order, is included with the images." msgstr "" #. Tag: title -#: preparing.xml:1437 +#: preparing.xml:1626 #, no-c-format msgid "Setting up an installation server" msgstr "" #. Tag: para -#: preparing.xml:1439 +#: preparing.xml:1628 #, no-c-format msgid "If you don't have a connection to the Internet (either directly or via a web proxy) you need to create a local installation server that can be accessed from your S/390. This server keeps all the packages you want to install and must make them available using NFS, HTTP or FTP." msgstr "" #. Tag: para -#: preparing.xml:1447 +#: preparing.xml:1636 #, no-c-format 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 -#: preparing.xml:1456 +#: preparing.xml:1645 #, no-c-format msgid "FIXME: more information needed — from a Redbook?" msgstr "" #. Tag: title -#: preparing.xml:1466 +#: preparing.xml:1655 #, no-c-format msgid "ARM firmware" msgstr "" #. Tag: para -#: preparing.xml:1468 +#: preparing.xml:1657 #, no-c-format msgid "As already mentioned before, there is unfortunately no standard for system firmware on ARM systems. Even the behaviour of different systems which use nominally the same firmware can be quite different. This results from the fact that a large part of the devices using the ARM architecture are embedded systems, for which the manufacturers usually build heavily customized firmware versions and include device-specific patches. Unfortunately the manufacturers often do not submit their changes and extensions back to the mainline firmware developers, so their changes are not integrated into newer versions of the original firmware." msgstr "" #. Tag: para -#: preparing.xml:1480 +#: preparing.xml:1669 #, no-c-format msgid "As a result even newly sold systems often use a firmware that is based on a years-old manufacturer-modified version of a firmware whose mainline codebase has evolved a lot further in the meantime and offers additional features or shows different behaviour in certain aspects. In addition to that, the naming of onboard devices is not consistent between different manufacturer-modified versions of the same firmware, therefore it is nearly impossible to provide usable product-independend instructions for ARM-based systems." msgstr "" #. Tag: title -#: preparing.xml:1493 +#: preparing.xml:1682 +#, no-c-format +msgid "Debian-provided U-Boot (system firmware) images" +msgstr "" + +#. Tag: para +#: preparing.xml:1683 +#, no-c-format +msgid "Debian provides U-Boot images for various armhf systems that can load their U-Boot from an SD card at &armmp-uboot-img;. The U-Boot builds are offered in two formats: raw U-Boot components and a ready-made card image that can easily be written onto an SD card. The raw U-Boot components are provided for advanced users; the generally recommended way is to use one of the ready-made SD card images. They are named <system-type>.sdcard.img.gz and can be written to a card e.g. with <informalexample><screen>zcat <system-type>.sdcard.img.gz > /dev/SD_CARD_DEVICE</screen></informalexample> As with all images, please be aware that writing the image to an SD card wipes all previous contents of the card!" +msgstr "" + +#. Tag: para +#: preparing.xml:1698 +#, no-c-format +msgid "If Debian provides a U-Boot image for your system, it is recommended that you use this image instead of the vendor-provided U-Boot, as the version in Debian is usually newer and has more features." +msgstr "" + +#. Tag: title +#: preparing.xml:1706 #, no-c-format -msgid "Setting the ethernet MAC address in u-boot" +msgid "Setting the ethernet MAC address in U-Boot" msgstr "" #. Tag: para -#: preparing.xml:1494 +#: preparing.xml:1707 #, no-c-format msgid "The MAC address of every ethernet interface should normally be globally unique, and it technically has to be unique within its ethernet broadcast domain. To achieve this, the manufacturer usually allocates a block of MAC addresses from a centrally-administered pool (for which a fee has to be paid) and preconfigures one of these addresses on each item sold." msgstr "" #. Tag: para -#: preparing.xml:1502 +#: preparing.xml:1715 #, no-c-format msgid "In the case of development boards, sometimes the manufacturer wants to avoid paying these fees and therefore provides no globally unique addresses. In these cases the users themselves have to define MAC addresses for their systems. When no MAC address is defined for an ethernet interface, some network drivers generate a random MAC address that can change on every boot, and if this happens, network access would be possible even when the user has not manually set an address, but e.g. assigning semi-static IP addresses by DHCP based on the MAC address of the requesting client would obviously not work reliably." msgstr "" #. Tag: para -#: preparing.xml:1513 +#: preparing.xml:1726 #, no-c-format msgid "To avoid conflicts with existing officially-assigned MAC addresses, there is an address pool which is reserved for so-called <quote>locally administered</quote> addresses. It is defined by the value of two specific bits in the first byte of the address (the article <quote>MAC address</quote> in the English language Wikipedia gives a good explanation). In practice this means that e.g. any address starting with hexadecimal ca (such as ca:ff:ee:12:34:56) can be used as a locally administered address." msgstr "" #. Tag: para -#: preparing.xml:1523 +#: preparing.xml:1736 #, no-c-format -msgid "On systems using u-boot as system firmware, the ethernet MAC address is placed in the <quote>ethaddr</quote> environment variable. It can be checked at the u-boot command prompt with the command <quote>printenv ethaddr</quote> and can be set with the command <quote>setenv ethaddr ca:ff:ee:12:34:56</quote>. After setting the value, the command <quote>saveenv</quote> makes the assignment permanent." +msgid "On systems using U-Boot as system firmware, the ethernet MAC address is placed in the <quote>ethaddr</quote> environment variable. It can be checked at the U-Boot command prompt with the command <quote>printenv ethaddr</quote> and can be set with the command <quote>setenv ethaddr ca:ff:ee:12:34:56</quote>. After setting the value, the command <quote>saveenv</quote> makes the assignment permanent." msgstr "" #. Tag: title -#: preparing.xml:1534 +#: preparing.xml:1747 #, no-c-format -msgid "Kernel/Initrd/Device-Tree relocation issues in u-boot" +msgid "Kernel/Initrd/Device-Tree relocation issues in U-Boot" msgstr "" #. Tag: para -#: preparing.xml:1535 +#: preparing.xml:1748 #, no-c-format -msgid "On some systems with older u-boot versions there can be problems with properly relocating the Linux kernel, the initial ramdisk and the device-tree blob in memory during the boot process. In this case, u-boot shows the message <quote>Starting kernel ...</quote>, but the system freezes afterwards without further output. These issues have been solved with newer u-boot versions from v2014.07 onwards." +msgid "On some systems with older U-Boot versions there can be problems with properly relocating the Linux kernel, the initial ramdisk and the device-tree blob in memory during the boot process. In this case, U-Boot shows the message <quote>Starting kernel ...</quote>, but the system freezes afterwards without further output. These issues have been solved with newer U-Boot versions from v2014.07 onwards." msgstr "" #. Tag: para -#: preparing.xml:1544 +#: preparing.xml:1757 #, no-c-format -msgid "If the system has originally used a u-boot version older than v2014.07 and has been upgraded to a newer version later, the problem might still occur even after upgrading u-boot. Upgrading u-boot usually does not modify the existing u-boot environment variables and the fix requires an additional environment variable (bootm_size) to be set, which u-boot does automatically only on fresh installations without existing environment data. It is possible to manually set bootm_size to the new u-boot's default value by running the command <quote>env default bootm_size; saveenv</quote> at the u-boot prompt." +msgid "If the system has originally used a U-Boot version older than v2014.07 and has been upgraded to a newer version later, the problem might still occur even after upgrading U-Boot. Upgrading U-Boot usually does not modify the existing U-Boot environment variables and the fix requires an additional environment variable (bootm_size) to be set, which U-Boot does automatically only on fresh installations without existing environment data. It is possible to manually set bootm_size to the new U-Boot's default value by running the command <quote>env default bootm_size; saveenv</quote> at the U-Boot prompt." msgstr "" #. Tag: para -#: preparing.xml:1555 +#: preparing.xml:1768 #, no-c-format -msgid "Another possibility to circumvent relocation-related problems is to run the command <quote>setenv fdt_high ffffffff; setenv initrd_high 0xffffffff; saveenv</quote> at the u-boot prompt to completely disable the relocation of the initial ramdisk and the device-tree blob." +msgid "Another possibility to circumvent relocation-related problems is to run the command <quote>setenv fdt_high ffffffff; setenv initrd_high 0xffffffff; saveenv</quote> at the U-Boot prompt to completely disable the relocation of the initial ramdisk and the device-tree blob." msgstr "" #. Tag: title -#: preparing.xml:1565 +#: preparing.xml:1778 #, no-c-format msgid "Systems with UEFI firmware" msgstr "" #. Tag: para -#: preparing.xml:1566 +#: preparing.xml:1779 #, no-c-format msgid "UEFI (<quote>Unified Extensible Firmware Interface</quote>) is a new kind of system firmware that is used on many modern systems and is - among other uses - intended to replace the classic PC BIOS." msgstr "" #. Tag: para -#: preparing.xml:1572 +#: preparing.xml:1785 #, no-c-format -msgid "Currently most PC systems that use UEFI also have a so-called <quote>Compatibility Support Module</quote> (CSM) in the firmware, which provides excatly the same interfaces to an operating system as a classic PC BIOS, so that software written for the classic PC BIOS can be used unchanged. Nonetheless UEFI is intended to one day completely replace the old PC BIOS without being fully backwards-compatible and there are already a few systems with UEFI but without CSM." +msgid "Currently most PC systems that use UEFI also have a so-called <quote>Compatibility Support Module</quote> (CSM) in the firmware, which provides excatly the same interfaces to an operating system as a classic PC BIOS, so that software written for the classic PC BIOS can be used unchanged. Nonetheless UEFI is intended to one day completely replace the old PC BIOS without being fully backwards-compatible and there are already a lot of systems with UEFI but without CSM." msgstr "" #. Tag: para -#: preparing.xml:1582 +#: preparing.xml:1795 #, no-c-format -msgid "On systems with UEFI there are a few things to take into consideration when installing an operating system. The way the firmware loads an operating system is fundamentally different between the classic BIOS (or UEFI in CSM mode) and native UEFI. One major difference is the way the harddisk partitions get recorded on the harddisk. While the classic BIOS and UEFI in CSM mode use a DOS partition table, native UEFI uses a different partitioning scheme called <quote>GUID Partition Table</quote> (GPT). On a single disk, for all practical purposes only one of the two can be used and in case of a multi-boot setup with different operating systems on one disk, all of them must therefore use the same type of partition table. Booting from a disk with GPT is only possible in native UEFI mode, but using GPT becomes more and more common as hard disk sizes grow, because the classic DOS partition table cannot address disks larger than about 2 Terabytes while GPT allows for by far larger disks. The other major difference between BIOS (or UEFI in CSM mode) and native UEFI is from where boot code is loaded and in which format it has to be, so that different bootloaders are needed for both systems." +msgid "On systems with UEFI there are a few things to take into consideration when installing an operating system. The way the firmware loads an operating system is fundamentally different between the classic BIOS (or UEFI in CSM mode) and native UEFI. One major difference is the way the harddisk partitions are recorded on the harddisk. While the classic BIOS and UEFI in CSM mode use a DOS partition table, native UEFI uses a different partitioning scheme called <quote>GUID Partition Table</quote> (GPT). On a single disk, for all practical purposes only one of the two can be used and in case of a multi-boot setup with different operating systems on one disk, all of them must therefore use the same type of partition table. Booting from a disk with GPT is only possible in native UEFI mode, but using GPT becomes more and more common as hard disk sizes grow, because the classic DOS partition table cannot address disks larger than about 2 Terabytes while GPT allows for far larger disks. The other major difference between BIOS (or UEFI in CSM mode) and native UEFI is the location where boot code is stored and in which format it has to be. This means that different bootloaders are needed for each system." msgstr "" #. Tag: para -#: preparing.xml:1602 +#: preparing.xml:1815 #, no-c-format msgid "The latter becomes important when booting &d-i; on a UEFI system with CSM because &d-i; checks whether it was started on a BIOS- or on a native UEFI system and installs the corresponding bootloader. Normally this simply works but there can be a problem in multi-boot environments. On some UEFI systems with CSM the default boot mode for removable devices can be different from what is actually used when booting from hard disk, so when booting the installer from a USB stick in a different mode from what is used when booting another already installed operating system from the hard disk, the wrong bootloader might be installed and the system might be unbootable after finishing the installation. When choosing the boot device from a firmware boot menu, some systems offer two seperate choices for each device, so that the user can select whether booting shall happen in CSM or in native UEFI mode." msgstr "" #. Tag: para -#: preparing.xml:1618 +#: preparing.xml:1831 #, no-c-format -msgid "Another UEFI-related topic is the so-called <quote>secure boot</quote> mechanism. Secure boot means a function of UEFI implementations that allows the firmware to only load and execute code that is cryptographically signed with certain keys and thereby blocking any (potentially malicious) boot code that is unsigned or signed with unknown keys. In practice the only key accepted by default on most UEFI systems with secure boot is a key from Microsoft used for signing the Windows bootloader. As the boot code used by &d-i; is not signed by Microsoft, booting the installer requires prior deactivation of secure boot in case it is enabled. Secure boot is often enabled by default on systems that come preinstalled with a 64Bit version of Windows 8 and there is unfortunately no standard where in the UEFI setup it can be disabled. On some systems, the option to disable secure boot is only made visible when a BIOS password has been set by the user, so if you have a system with secure boot enabled, but cannot find an option to disable it, try setting a BIOS password, powercycle the machine and look again for an appropriate option." +msgid "Another UEFI-related topic is the so-called <quote>secure boot</quote> mechanism. Secure boot means a function of UEFI implementations that allows the firmware to only load and execute code that is cryptographically signed with certain keys and thereby blocking any (potentially malicious) boot code that is unsigned or signed with unknown keys. In practice the only key accepted by default on most UEFI systems with secure boot is a key from Microsoft used for signing the Windows bootloader. As the boot code used by &d-i; is not signed by Microsoft, booting the installer requires prior deactivation of secure boot in case it is enabled. Secure boot is often enabled by default on systems that come preinstalled with a 64-bit version of Windows 8 and there is unfortunately no standard way to disable it in the UEFI setup. On some systems, the option to disable secure boot is only made visible when a BIOS password has been set by the user, so if you have a system with secure boot enabled, but cannot find an option to disable it, try setting a BIOS password, powercycle the machine and look again for an appropriate option." msgstr "" #. Tag: title -#: preparing.xml:1640 +#: preparing.xml:1853 #, no-c-format msgid "Disabling the Windows 8 <quote>fast boot</quote> feature" msgstr "" #. Tag: para -#: preparing.xml:1641 +#: preparing.xml:1854 +#, no-c-format +msgid "Windows 8 offers a feature called <quote>fast boot</quote> to cut down system startup time. Technically, when this feature is enabled, Windows 8 does not do a real shutdown and a real cold boot afterwards when ordered to shut down, but instead does something resembling a partial suspend to disk to reduce the <quote>boot</quote> time. As long as Windows 8 is the only operating system on the machine, this is unproblematic, but it can result in problems and data loss when you have a dual boot setup in which another operating system accesses the same filesystems as Windows 8 does. In that case the real state of the filesystem can be different from what Windows 8 believes it to be after the <quote>boot</quote> and this could cause filesystem corruption upon further write accesses to the filesystem. Therefore in a dual boot setup, to avoid filesystem corruption the <quote>fast boot</quote> feature has to be disabled within Windows." +msgstr "" + +#. Tag: para +#: preparing.xml:1870 #, no-c-format -msgid "Windows 8 offers a feature called <quote>fast boot</quote> to cut down the time needed to boot itself. Technically, when this feature is enabled, Windows 8 does not do a real shutdown and a real cold boot afterwards when ordered to shut down, but instead does something resembling a partial suspend to disk to reduce the <quote>boot</quote> time. As long as Windows 8 is the only operating system on the machine, this is unproblematic, but it can result in problems and data loss when you have a dual boot setup in which another operating system accesses the same filesystems as Windows 8 does. In that case the real state of the filesystem can be different from what Windows 8 believes it to be after the <quote>boot</quote> and this could cause filesystem corruption upon further write accesses to the filesystem. Therefore in a dual boot setup, to avoid filesystem corruption the <quote>fast boot</quote> feature has to be disabled within Windows." +msgid "It may also be necessary to disable <quote>fast boot</quote> to even allow access to UEFI setup to choose to boot another operating system or &d-i;. On some UEFI systems, the firmware will reduce <quote>boot</quote> time by not initialising the keyboard controller or USB hardware; in these cases, it is necessary to boot into Windows and disable this feature to allow for a change of boot order." msgstr "" #. Tag: title -#: preparing.xml:1659 +#: preparing.xml:1882 #, no-c-format msgid "Hardware Issues to Watch Out For" msgstr "" #. Tag: title -#: preparing.xml:1662 +#: preparing.xml:1885 #, no-c-format msgid "USB BIOS support and keyboards" msgstr "" #. Tag: para -#: preparing.xml:1663 +#: preparing.xml:1886 #, no-c-format msgid "If you have no PS/2-style keyboard, but only a USB model, on some very old PCs you may need to enable legacy keyboard emulation in your BIOS setup to be able to use your keyboard in the bootloader menu, but this is not an issue for modern systems. If your keyboard does not work in the bootloader menu, consult your mainboard manual and look in the BIOS for <quote>Legacy keyboard emulation</quote> or <quote>USB keyboard support</quote> options." msgstr "" #. Tag: title -#: preparing.xml:1676 +#: preparing.xml:1899 #, no-c-format msgid "Display-visibility on OldWorld Powermacs" msgstr "" #. Tag: para -#: preparing.xml:1678 +#: preparing.xml:1901 #, no-c-format msgid "Some OldWorld Powermacs, most notably those with the <quote>control</quote> display driver, may not reliably produce a colormap under Linux when the display is configured for more than 256 colors. If you are experiencing such issues with your display after rebooting (you can sometimes see data on the monitor, but on other occasions cannot see anything) or, if the screen turns black after booting the installer instead of showing you the user interface, try changing your display settings under MacOS to use 256 colors instead of <quote>thousands</quote> or <quote>millions</quote>." msgstr "" diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot index 820b8b17a..04e09f56c 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: 2015-03-21 16:42+0000\n" +"POT-Creation-Date: 2015-04-15 20:29+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" @@ -1208,8 +1208,8 @@ msgid "" "\n" "# Alternatively, you may specify a disk to partition. If the system has only\n" "# one disk the installer will default to using that, but otherwise the device\n" - "# name must be given in traditional, non-devfs format (so e.g. /dev/hda or\n" - "# /dev/sda, and not e.g. /dev/discs/disc0/disc).\n" + "# name must be given in traditional, non-devfs format (so e.g. /dev/sda\n" + "# and not e.g. /dev/discs/disc0/disc).\n" "# For example, to use the first SCSI/SATA hard disk:\n" "#d-i partman-auto/disk string /dev/sda\n" "# In addition, you'll need to specify the method to use.\n" diff --git a/po/pot/random-bits.pot b/po/pot/random-bits.pot index 86a259732..1e7096e2f 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: 2015-01-09 19:07+0000\n" +"POT-Creation-Date: 2015-04-15 20:29+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,281 +59,197 @@ msgstr "" #. Tag: filename #: random-bits.xml:37 #, no-c-format -msgid "<filename>hda</filename>" +msgid "<filename>sda</filename>" msgstr "" #. Tag: entry #: random-bits.xml:38 #, no-c-format -msgid "IDE Hard disk / CD-ROM on the first IDE port (Master)" +msgid "First hard disk" msgstr "" #. Tag: filename #: random-bits.xml:40 #, no-c-format -msgid "<filename>hdb</filename>" +msgid "<filename>sdb</filename>" msgstr "" #. Tag: entry #: random-bits.xml:41 #, no-c-format -msgid "IDE Hard disk / CD-ROM on the first IDE port (Slave)" +msgid "Second hard disk" msgstr "" #. Tag: filename #: random-bits.xml:43 #, no-c-format -msgid "<filename>hdc</filename>" +msgid "sda1" msgstr "" #. Tag: entry #: random-bits.xml:44 #, no-c-format -msgid "IDE Hard disk / CD-ROM on the second IDE port (Master)" +msgid "First partition of the first hard disk" msgstr "" #. Tag: filename #: random-bits.xml:46 #, no-c-format -msgid "<filename>hdd</filename>" +msgid "sdb7" msgstr "" #. Tag: entry #: random-bits.xml:47 #, no-c-format -msgid "IDE Hard disk / CD-ROM on the second IDE port (Slave)" +msgid "Seventh partition of the second hard disk" msgstr "" #. Tag: filename -#: random-bits.xml:49 -#, no-c-format -msgid "hda1" -msgstr "" - -#. Tag: entry -#: random-bits.xml:50 -#, no-c-format -msgid "First partition of the first IDE hard disk" -msgstr "" - -#. Tag: filename -#: random-bits.xml:52 -#, no-c-format -msgid "hdd15" -msgstr "" - -#. Tag: entry #: random-bits.xml:53 #, no-c-format -msgid "Fifteenth partition of the fourth IDE hard disk" -msgstr "" - -#. Tag: filename -#: random-bits.xml:59 -#, no-c-format -msgid "<filename>sda</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:60 -#, no-c-format -msgid "SCSI Hard disk with lowest SCSI ID (e.g. 0)" -msgstr "" - -#. Tag: filename -#: random-bits.xml:62 -#, no-c-format -msgid "<filename>sdb</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:63 -#, no-c-format -msgid "SCSI Hard disk with next higher SCSI ID (e.g. 1)" -msgstr "" - -#. Tag: filename -#: random-bits.xml:65 -#, no-c-format -msgid "<filename>sdc</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:66 -#, no-c-format -msgid "SCSI Hard disk with next higher SCSI ID (e.g. 2)" -msgstr "" - -#. Tag: filename -#: random-bits.xml:68 -#, no-c-format -msgid "sda1" -msgstr "" - -#. Tag: entry -#: random-bits.xml:69 -#, no-c-format -msgid "First partition of the first SCSI hard disk" -msgstr "" - -#. Tag: filename -#: random-bits.xml:71 -#, no-c-format -msgid "sdd10" -msgstr "" - -#. Tag: entry -#: random-bits.xml:72 -#, no-c-format -msgid "Tenth partition of the fourth SCSI hard disk" -msgstr "" - -#. Tag: filename -#: random-bits.xml:78 -#, no-c-format msgid "<filename>sr0</filename>" msgstr "" #. Tag: entry -#: random-bits.xml:79 +#: random-bits.xml:54 #, no-c-format -msgid "SCSI CD-ROM with the lowest SCSI ID" +msgid "First CD-ROM" msgstr "" #. Tag: filename -#: random-bits.xml:81 +#: random-bits.xml:56 #, no-c-format msgid "<filename>sr1</filename>" msgstr "" #. Tag: entry -#: random-bits.xml:82 +#: random-bits.xml:57 #, no-c-format -msgid "SCSI CD-ROM with the next higher SCSI ID" +msgid "Second CD-ROM" msgstr "" #. Tag: filename -#: random-bits.xml:88 +#: random-bits.xml:63 #, no-c-format msgid "ttyS0" msgstr "" #. Tag: entry -#: random-bits.xml:89 +#: random-bits.xml:64 #, no-c-format msgid "Serial port 0, COM1 under MS-DOS" msgstr "" #. Tag: filename -#: random-bits.xml:91 +#: random-bits.xml:66 #, no-c-format msgid "ttyS1" msgstr "" #. Tag: entry -#: random-bits.xml:92 +#: random-bits.xml:67 #, no-c-format msgid "Serial port 1, COM2 under MS-DOS" msgstr "" #. Tag: filename -#: random-bits.xml:94 +#: random-bits.xml:69 #, no-c-format msgid "psaux" msgstr "" #. Tag: entry -#: random-bits.xml:95 +#: random-bits.xml:70 #, no-c-format msgid "PS/2 mouse device" msgstr "" #. Tag: filename -#: random-bits.xml:97 +#: random-bits.xml:72 #, no-c-format msgid "gpmdata" msgstr "" #. Tag: entry -#: random-bits.xml:98 +#: random-bits.xml:73 #, no-c-format msgid "Pseudo device, repeater data from GPM (mouse) daemon" msgstr "" #. Tag: filename -#: random-bits.xml:104 +#: random-bits.xml:79 #, no-c-format msgid "cdrom" msgstr "" #. Tag: entry -#: random-bits.xml:105 +#: random-bits.xml:80 #, no-c-format msgid "Symbolic link to the CD-ROM drive" msgstr "" #. Tag: filename -#: random-bits.xml:107 +#: random-bits.xml:82 #, no-c-format msgid "mouse" msgstr "" #. Tag: entry -#: random-bits.xml:108 +#: random-bits.xml:83 #, no-c-format msgid "Symbolic link to the mouse device file" msgstr "" #. Tag: filename -#: random-bits.xml:114 +#: random-bits.xml:89 #, no-c-format msgid "null" msgstr "" #. Tag: entry -#: random-bits.xml:115 +#: random-bits.xml:90 #, no-c-format msgid "Anything written to this device will disappear" msgstr "" #. Tag: filename -#: random-bits.xml:117 +#: random-bits.xml:92 #, no-c-format msgid "zero" msgstr "" #. Tag: entry -#: random-bits.xml:118 +#: random-bits.xml:93 #, no-c-format msgid "One can endlessly read zeros out of this device" msgstr "" #. Tag: title -#: random-bits.xml:125 +#: random-bits.xml:100 #, no-c-format msgid "Setting Up Your Mouse" msgstr "" #. Tag: para -#: random-bits.xml:126 +#: random-bits.xml:101 #, no-c-format msgid "The mouse can be used in both the Linux console (with gpm) and the X window environment. Normally, this is a simple matter of installing <filename>gpm</filename> and the X server itself. Both should be configured to use <filename>/dev/input/mice</filename> as the mouse device. The correct mouse protocol is named <userinput>exps2</userinput> in gpm, and <userinput>ExplorerPS/2</userinput> in X. The respective configuration files are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</filename>." msgstr "" #. Tag: para -#: random-bits.xml:137 +#: random-bits.xml:112 #, no-c-format msgid "Certain kernel modules must be loaded in order for your mouse to work. In most cases the correct modules are autodetected, but not always for old-style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole D-shaped connector; bus mice have an 8-pin round connector, not to be confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round connector of an ADB mouse. </para> </footnote>, which are quite rare except on very old computers. Summary of Linux kernel modules needed for different mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</entry> <entry>Description</entry> </row> </thead><tbody> <row> <entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> </row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></informaltable> To load a mouse driver module, you can use the <command>modconf</command> command (from the package with the same name) and look in the category <userinput>kernel/drivers/input/mouse</userinput>." msgstr "" #. Tag: para -#: random-bits.xml:184 +#: random-bits.xml:159 #, no-c-format msgid "Modern kernels give you the capability to emulate a three-button mouse when your mouse only has one button. Just add the following lines to <filename>/etc/sysctl.conf</filename> file." msgstr "" #. Tag: screen -#: random-bits.xml:191 +#: random-bits.xml:166 #, no-c-format msgid "" "# 3-button mouse emulation\n" @@ -347,407 +263,407 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:198 +#: random-bits.xml:173 #, no-c-format msgid "Disk Space Needed for Tasks" msgstr "" #. Tag: para -#: random-bits.xml:199 +#: random-bits.xml:174 #, no-c-format msgid "A standard installation for the amd64 architecture, including all standard packages and using the default kernel, takes up &std-system-size;MB of disk space. A minimal base installation, without the <quote>Standard system</quote> task selected, will take &base-system-size;MB." msgstr "" #. Tag: para -#: random-bits.xml:207 +#: random-bits.xml:182 #, no-c-format msgid "In both cases this is the actual disk space used <emphasis>after</emphasis> the installation is finished and any temporary files deleted. It also does not take into account overhead used by the file system, for example for journal files. This means that significantly more disk space is needed both <emphasis>during</emphasis> the installation and for normal system use." msgstr "" #. Tag: para -#: random-bits.xml:216 +#: random-bits.xml:191 #, no-c-format msgid "The following table lists sizes reported by aptitude for the tasks listed in tasksel. Note that some tasks have overlapping constituents, so the total installed size for two tasks together may be less than the total obtained by adding up the numbers." msgstr "" #. Tag: para -#: random-bits.xml:223 +#: random-bits.xml:198 #, no-c-format msgid "By default the installer will install the GNOME desktop environment, but alternative desktop environments can be selected either by using one of the special CD images, or by specifying the desired desktop environment when the installer is booted (see <xref linkend=\"pkgsel\"/>)." msgstr "" #. Tag: para -#: random-bits.xml:230 +#: random-bits.xml:205 #, no-c-format msgid "Note that you will need to add the sizes listed in the table to the size of the standard installation when determining the size of partitions. Most of the size listed as <quote>Installed size</quote> will end up in <filename>/usr</filename> and in <filename>/lib</filename>; the size listed as <quote>Download size</quote> is (temporarily) required in <filename>/var</filename>." msgstr "" #. Tag: entry -#: random-bits.xml:244 +#: random-bits.xml:219 #, no-c-format msgid "Task" msgstr "" #. Tag: entry -#: random-bits.xml:245 +#: random-bits.xml:220 #, no-c-format msgid "Installed size (MB)" msgstr "" #. Tag: entry -#: random-bits.xml:246 +#: random-bits.xml:221 #, no-c-format msgid "Download size (MB)" msgstr "" #. Tag: entry -#: random-bits.xml:247 +#: random-bits.xml:222 #, no-c-format msgid "Space needed to install (MB)" msgstr "" #. Tag: entry -#: random-bits.xml:253 +#: random-bits.xml:228 #, no-c-format msgid "Desktop environment" msgstr "" #. Tag: entry -#: random-bits.xml:254 random-bits.xml:255 random-bits.xml:256 +#: random-bits.xml:229 random-bits.xml:230 random-bits.xml:231 #, no-c-format msgid " " msgstr "" #. Tag: entry -#: random-bits.xml:259 +#: random-bits.xml:234 #, no-c-format msgid " • GNOME (default)" msgstr "" #. Tag: entry -#: random-bits.xml:260 +#: random-bits.xml:235 #, no-c-format msgid "&task-desktop-gnome-inst;" msgstr "" #. Tag: entry -#: random-bits.xml:261 +#: random-bits.xml:236 #, no-c-format msgid "&task-desktop-gnome-dl;" msgstr "" #. Tag: entry -#: random-bits.xml:262 +#: random-bits.xml:237 #, no-c-format msgid "&task-desktop-gnome-tot;" msgstr "" #. Tag: entry -#: random-bits.xml:265 +#: random-bits.xml:240 #, no-c-format msgid " • KDE" msgstr "" #. Tag: entry -#: random-bits.xml:266 +#: random-bits.xml:241 #, no-c-format msgid "&task-desktop-kde-inst;" msgstr "" #. Tag: entry -#: random-bits.xml:267 +#: random-bits.xml:242 #, no-c-format msgid "&task-desktop-kde-dl;" msgstr "" #. Tag: entry -#: random-bits.xml:268 +#: random-bits.xml:243 #, no-c-format msgid "&task-desktop-kde-tot;" msgstr "" #. Tag: entry -#: random-bits.xml:271 +#: random-bits.xml:246 #, no-c-format msgid " • Xfce" msgstr "" #. Tag: entry -#: random-bits.xml:272 +#: random-bits.xml:247 #, no-c-format msgid "&task-desktop-xfce-inst;" msgstr "" #. Tag: entry -#: random-bits.xml:273 +#: random-bits.xml:248 #, no-c-format msgid "&task-desktop-xfce-dl;" msgstr "" #. Tag: entry -#: random-bits.xml:274 +#: random-bits.xml:249 #, no-c-format msgid "&task-desktop-xfce-tot;" msgstr "" #. Tag: entry -#: random-bits.xml:277 +#: random-bits.xml:252 #, no-c-format msgid " • LXDE" msgstr "" #. Tag: entry -#: random-bits.xml:278 +#: random-bits.xml:253 #, no-c-format msgid "&task-desktop-lxde-inst;" msgstr "" #. Tag: entry -#: random-bits.xml:279 +#: random-bits.xml:254 #, no-c-format msgid "&task-desktop-lxde-dl;" msgstr "" #. Tag: entry -#: random-bits.xml:280 +#: random-bits.xml:255 #, no-c-format msgid "&task-desktop-lxde-tot;" msgstr "" #. Tag: entry -#: random-bits.xml:283 +#: random-bits.xml:258 #, no-c-format msgid " • MATE" msgstr "" #. Tag: entry -#: random-bits.xml:284 +#: random-bits.xml:259 #, no-c-format msgid "&task-desktop-mate-inst;" msgstr "" #. Tag: entry -#: random-bits.xml:285 +#: random-bits.xml:260 #, no-c-format msgid "&task-desktop-mate-dl;" msgstr "" #. Tag: entry -#: random-bits.xml:286 +#: random-bits.xml:261 #, no-c-format msgid "&task-desktop-mate-tot;" msgstr "" #. Tag: entry -#: random-bits.xml:289 +#: random-bits.xml:264 #, no-c-format msgid " • Cinnamon" msgstr "" #. Tag: entry -#: random-bits.xml:290 +#: random-bits.xml:265 #, no-c-format msgid "&task-desktop-cinnamon-inst;" msgstr "" #. Tag: entry -#: random-bits.xml:291 +#: random-bits.xml:266 #, no-c-format msgid "&task-desktop-cinnamon-dl;" msgstr "" #. Tag: entry -#: random-bits.xml:292 +#: random-bits.xml:267 #, no-c-format msgid "&task-desktop-cinnamon-tot;" msgstr "" #. Tag: entry -#: random-bits.xml:296 +#: random-bits.xml:271 #, no-c-format msgid "Laptop" msgstr "" #. Tag: entry -#: random-bits.xml:297 +#: random-bits.xml:272 #, no-c-format msgid "&task-laptop-inst;" msgstr "" #. Tag: entry -#: random-bits.xml:298 +#: random-bits.xml:273 #, no-c-format msgid "&task-laptop-dl;" msgstr "" #. Tag: entry -#: random-bits.xml:299 +#: random-bits.xml:274 #, no-c-format msgid "&task-laptop-tot;" msgstr "" #. Tag: entry -#: random-bits.xml:303 +#: random-bits.xml:278 #, no-c-format msgid "Web server" msgstr "" #. Tag: entry -#: random-bits.xml:304 +#: random-bits.xml:279 #, no-c-format msgid "&task-web-inst;" msgstr "" #. Tag: entry -#: random-bits.xml:305 +#: random-bits.xml:280 #, no-c-format msgid "&task-web-dl;" msgstr "" #. Tag: entry -#: random-bits.xml:306 +#: random-bits.xml:281 #, no-c-format msgid "&task-web-tot;" msgstr "" #. Tag: entry -#: random-bits.xml:310 +#: random-bits.xml:285 #, no-c-format msgid "Print server" msgstr "" #. Tag: entry -#: random-bits.xml:311 +#: random-bits.xml:286 #, no-c-format msgid "&task-print-inst;" msgstr "" #. Tag: entry -#: random-bits.xml:312 +#: random-bits.xml:287 #, no-c-format msgid "&task-print-dl;" msgstr "" #. Tag: entry -#: random-bits.xml:313 +#: random-bits.xml:288 #, no-c-format msgid "&task-print-tot;" msgstr "" #. Tag: entry -#: random-bits.xml:317 +#: random-bits.xml:292 #, no-c-format msgid "SSH server" msgstr "" #. Tag: entry -#: random-bits.xml:318 +#: random-bits.xml:293 #, no-c-format msgid "&task-ssh-inst;" msgstr "" #. Tag: entry -#: random-bits.xml:319 +#: random-bits.xml:294 #, no-c-format msgid "&task-ssh-dl;" msgstr "" #. Tag: entry -#: random-bits.xml:320 +#: random-bits.xml:295 #, no-c-format msgid "&task-ssh-tot;" msgstr "" #. Tag: para -#: random-bits.xml:326 +#: random-bits.xml:301 #, no-c-format msgid "If you install in a language other than English, <command>tasksel</command> may automatically install a <firstterm>localization task</firstterm>, if one is available for your language. Space requirements differ per language; you should allow up to 350MB in total for download and installation." msgstr "" #. Tag: title -#: random-bits.xml:341 +#: random-bits.xml:316 #, no-c-format msgid "Installing &debian-gnu; from a Unix/Linux System" msgstr "" #. Tag: para -#: random-bits.xml:343 +#: random-bits.xml:318 #, no-c-format 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, Mandriva, 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:355 +#: random-bits.xml:330 #, 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-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:366 +#: random-bits.xml:341 #, 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 &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 -#: random-bits.xml:380 +#: random-bits.xml:355 #, no-c-format msgid "Getting Started" msgstr "" #. Tag: para -#: random-bits.xml:381 +#: random-bits.xml:356 #, no-c-format msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need around &base-system-size;MB of space available for a console only install, or about &task-desktop-lxde-inst;MB if you plan to install X (more if you intend to install desktop environments like GNOME or KDE)." msgstr "" #. Tag: para -#: random-bits.xml:389 +#: random-bits.xml:364 #, no-c-format msgid "" - "Next, create file systems on the partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n" - "# mke2fs -j /dev/<replaceable>hda6</replaceable>\n" + "Next, create file systems on the partitions. For example, to create an ext3 file system on partition <filename>/dev/sda6</filename> (that's our example root partition): <informalexample><screen>\n" + "# mke2fs -j /dev/<replaceable>sda6</replaceable>\n" "</screen></informalexample> To create an ext2 file system instead, omit <userinput>-j</userinput>." msgstr "" #. Tag: para -#: random-bits.xml:399 +#: random-bits.xml:374 #, no-c-format msgid "" "Initialize and activate swap (substitute the partition number for your intended &debian; swap partition): <informalexample><screen>\n" - "# mkswap /dev/<replaceable>hda5</replaceable>\n" + "# mkswap /dev/<replaceable>sda5</replaceable>\n" "# sync\n" - "# swapon /dev/<replaceable>hda5</replaceable>\n" + "# swapon /dev/<replaceable>sda5</replaceable>\n" "</screen></informalexample> Mount one partition as <filename>/mnt/debinst</filename> (the installation point, to be the root (<filename>/</filename>) filesystem on your new system). The mount point name is strictly arbitrary, it is referenced later below." msgstr "" #. Tag: screen -#: random-bits.xml:411 +#: random-bits.xml:386 #, no-c-format msgid "" "# mkdir /mnt/debinst\n" - "# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst" + "# mount /dev/<replaceable>sda6</replaceable> /mnt/debinst" msgstr "" #. Tag: para -#: random-bits.xml:414 +#: random-bits.xml:389 #, no-c-format msgid "If you want to have parts of the filesystem (e.g. /usr) mounted on separate partitions, you will need to create and mount these directories manually before proceding with the next stage." msgstr "" #. Tag: title -#: random-bits.xml:424 +#: random-bits.xml:399 #, no-c-format msgid "Install <command>debootstrap</command>" msgstr "" #. Tag: para -#: random-bits.xml:425 +#: random-bits.xml:400 #, no-c-format msgid "The utility used by the &debian; installer, and recognized as the official way to install a &debian; base system, is <command>debootstrap</command>. It uses <command>wget</command> and <command>ar</command>, but otherwise depends only on <classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> <para> These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>. </para> </footnote>. Install <command>wget</command> and <command>ar</command> if they aren't already on your current system, then download and install <command>debootstrap</command>." msgstr "" #. Tag: para -#: random-bits.xml:455 +#: random-bits.xml:430 #, no-c-format msgid "" "Or, you can use the following procedure to install it manually. Make a work folder for extracting the .deb into: <informalexample><screen>\n" @@ -757,7 +673,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:470 +#: random-bits.xml:445 #, no-c-format msgid "" "# ar -x debootstrap_0.X.X_all.deb\n" @@ -766,31 +682,31 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:476 +#: random-bits.xml:451 #, no-c-format msgid "Run <command>debootstrap</command>" msgstr "" #. Tag: para -#: random-bits.xml:477 +#: random-bits.xml:452 #, no-c-format msgid "<command>debootstrap</command> can download the needed files directly from the archive when you run it. You can substitute any &debian; archive mirror for <userinput>&archive-mirror;/debian</userinput> in the command example below, preferably a mirror close to you network-wise. Mirrors are listed at <ulink url=\"http://www.debian.org/mirror/list\"></ulink>." msgstr "" #. Tag: para -#: random-bits.xml:486 +#: random-bits.xml:461 #, no-c-format 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 -#: random-bits.xml:492 +#: random-bits.xml:467 #, no-c-format msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>amd64</userinput>, <userinput>arm64</userinput>, <userinput>armel</userinput>, <userinput>armhf</userinput>, <userinput>i386</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>ppc64el</userinput>, or <userinput>s390x</userinput>." msgstr "" #. Tag: screen -#: random-bits.xml:508 +#: random-bits.xml:483 #, no-c-format msgid "" "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n" @@ -798,13 +714,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:514 +#: random-bits.xml:489 #, no-c-format msgid "Configure The Base System" msgstr "" #. Tag: para -#: random-bits.xml:515 +#: random-bits.xml:490 #, no-c-format msgid "" "Now you've got a real &debian; system, though rather lean, on disk. <command>chroot</command> into it: <informalexample><screen>\n" @@ -815,31 +731,31 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:533 +#: random-bits.xml:508 #, no-c-format msgid "Create device files" msgstr "" #. Tag: para -#: random-bits.xml:534 +#: random-bits.xml:509 #, no-c-format msgid "At this point <filename>/dev/</filename> only contains very basic device files. For the next steps of the installation additional device files may be needed. There are different ways to go about this and which method you should use depends on the host system you are using for the installation, on whether you intend to use a modular kernel or not, and on whether you intend to use dynamic (e.g. using <classname>udev</classname>) or static device files for the new system." msgstr "" #. Tag: para -#: random-bits.xml:544 +#: random-bits.xml:519 #, no-c-format msgid "A few of the available options are:" msgstr "" #. Tag: para -#: random-bits.xml:549 +#: random-bits.xml:524 #, no-c-format msgid "install the makedev package, and create a default set of static device files using (after chrooting)" msgstr "" #. Tag: screen -#: random-bits.xml:553 +#: random-bits.xml:528 #, no-c-format msgid "" "# apt-get install makedev\n" @@ -849,25 +765,25 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:556 +#: random-bits.xml:531 #, no-c-format msgid "manually create only specific device files using <command>MAKEDEV</command>" msgstr "" #. Tag: para -#: random-bits.xml:561 +#: random-bits.xml:536 #, no-c-format msgid "bind mount /dev from your host system on top of /dev in the target system; note that the postinst scripts of some packages may try to create device files, so this option should only be used with care" msgstr "" #. Tag: title -#: random-bits.xml:574 +#: random-bits.xml:549 #, no-c-format msgid "Mount Partitions" msgstr "" #. Tag: para -#: random-bits.xml:575 +#: random-bits.xml:550 #, no-c-format msgid "" "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n" @@ -901,31 +817,31 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:601 +#: random-bits.xml:576 #, no-c-format msgid "# mount -t proc proc /proc" msgstr "" #. Tag: para -#: random-bits.xml:603 +#: random-bits.xml:578 #, no-c-format msgid "The command <userinput>ls /proc</userinput> should now show a non-empty directory. Should this fail, you may be able to mount proc from outside the chroot:" msgstr "" #. Tag: screen -#: random-bits.xml:609 +#: random-bits.xml:584 #, no-c-format msgid "# mount -t proc proc /mnt/debinst/proc" msgstr "" #. Tag: title -#: random-bits.xml:615 +#: random-bits.xml:590 #, no-c-format msgid "Setting Timezone" msgstr "" #. Tag: para -#: random-bits.xml:616 +#: random-bits.xml:591 #, no-c-format msgid "" "Setting the third line of the file <filename>/etc/adjtime</filename> to <quote>UTC</quote> or <quote>LOCAL</quote> determines whether the system will interpret the hardware clock as being set to UTC respective local time. The following command allows you to set that. <informalexample><screen>\n" @@ -938,19 +854,19 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:630 +#: random-bits.xml:605 #, no-c-format msgid "# dpkg-reconfigure tzdata" msgstr "" #. Tag: title -#: random-bits.xml:636 +#: random-bits.xml:611 #, no-c-format msgid "Configure Networking" msgstr "" #. Tag: para -#: random-bits.xml:637 +#: random-bits.xml:612 #, no-c-format msgid "" "To configure networking, edit <filename>/etc/network/interfaces</filename>, <filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> and <filename>/etc/hosts</filename>. <informalexample><screen>\n" @@ -1004,13 +920,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:678 +#: random-bits.xml:653 #, no-c-format msgid "Configure Apt" msgstr "" #. Tag: para -#: random-bits.xml:679 +#: random-bits.xml:654 #, no-c-format msgid "" "Debootstrap will have created a very basic <filename>/etc/apt/sources.list</filename> that will allow installing additional packages. However, you may want to add some additional sources, for example for source packages and security updates: <informalexample><screen>\n" @@ -1022,13 +938,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:695 +#: random-bits.xml:670 #, no-c-format msgid "Configure Locales and Keyboard" msgstr "" #. Tag: para -#: random-bits.xml:696 +#: random-bits.xml:671 #, no-c-format msgid "" "To configure your locale settings to use a language other than English, install the <classname>locales</classname> support package and configure it. Currently the use of UTF-8 locales is recommended. <informalexample><screen>\n" @@ -1038,7 +954,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:706 +#: random-bits.xml:681 #, no-c-format msgid "" "# aptitude install console-setup\n" @@ -1046,88 +962,88 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:708 +#: random-bits.xml:683 #, no-c-format msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot." msgstr "" #. Tag: title -#: random-bits.xml:718 +#: random-bits.xml:693 #, no-c-format msgid "Install a Kernel" msgstr "" #. Tag: para -#: random-bits.xml:719 +#: random-bits.xml:694 #, no-c-format 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:724 +#: random-bits.xml:699 #, no-c-format msgid "# apt-cache search &kernelpackage;" msgstr "" #. Tag: para -#: random-bits.xml:726 +#: random-bits.xml:701 #, no-c-format msgid "Then install the kernel package of your choice using its package name." msgstr "" #. Tag: screen -#: random-bits.xml:730 +#: random-bits.xml:705 #, no-c-format msgid "# aptitude install &kernelpackage;-<replaceable>arch-etc</replaceable>" msgstr "" #. Tag: title -#: random-bits.xml:736 +#: random-bits.xml:711 #, no-c-format msgid "Set up the Boot Loader" msgstr "" #. Tag: para -#: random-bits.xml:737 +#: random-bits.xml:712 #, no-c-format 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:744 +#: random-bits.xml:719 #, no-c-format 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 grub2 <filename>grub.cfg</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:756 +#: random-bits.xml:731 #, no-c-format msgid "" "Installing and setting up <classname>grub2</classname> is as easy as: <informalexample><screen>\n" "# aptitude install grub-pc\n" - "# grub-install /dev/<replaceable>hda</replaceable>\n" + "# grub-install /dev/<replaceable>sda</replaceable>\n" "# update-grub\n" - "</screen></informalexample> The second command will install <command>grub2</command> (in this case in the MBR of <literal>hda</literal>). The last command will create a sane and working <filename>/boot/grub/grub.cfg</filename>." + "</screen></informalexample> The second command will install <command>grub2</command> (in this case in the MBR of <literal>sda</literal>). The last command will create a sane and working <filename>/boot/grub/grub.cfg</filename>." msgstr "" #. Tag: para -#: random-bits.xml:766 +#: random-bits.xml:741 #, 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>grub2</command>, but those are outside the scope of this appendix." +msgid "Note that this assumes that a <filename>/dev/sda</filename> device file has been created. There are alternative methods to install <command>grub2</command>, but those are outside the scope of this appendix." msgstr "" #. Tag: para -#: random-bits.xml:772 +#: random-bits.xml:747 #, no-c-format msgid "Here is a basic <filename>/etc/lilo.conf</filename> as an example:" msgstr "" #. Tag: screen -#: random-bits.xml:776 +#: random-bits.xml:751 #, no-c-format msgid "" - "boot=/dev/<replaceable>hda6</replaceable>\n" - "root=/dev/<replaceable>hda6</replaceable>\n" + "boot=/dev/<replaceable>sda6</replaceable>\n" + "root=/dev/<replaceable>sda6</replaceable>\n" "install=menu\n" "delay=20\n" "lba32\n" @@ -1137,20 +1053,20 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:778 +#: random-bits.xml:753 #, 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:788 +#: random-bits.xml:763 #, no-c-format msgid "" "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n" - "boot=/dev/hda2\n" + "boot=/dev/sda2\n" "device=hd:\n" "partition=6\n" - "root=/dev/hda6\n" + "root=/dev/sda6\n" "magicboot=/usr/lib/yaboot/ofboot\n" "timeout=50\n" "image=/vmlinux\n" @@ -1159,13 +1075,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:801 +#: random-bits.xml:776 #, no-c-format msgid "Remote access: Installing SSH and setting up access" msgstr "" #. Tag: para -#: random-bits.xml:802 +#: random-bits.xml:777 #, no-c-format msgid "" "In case you can login to the system via console, you can skip this section. If the system should be accessible via the network later on, you need to install SSH and set up access. <informalexample><screen>\n" @@ -1184,7 +1100,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:826 +#: random-bits.xml:801 #, no-c-format msgid "" "# adduser joe\n" @@ -1192,13 +1108,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:831 +#: random-bits.xml:806 #, no-c-format msgid "Finishing touches" msgstr "" #. Tag: para -#: random-bits.xml:832 +#: random-bits.xml:807 #, 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" @@ -1207,91 +1123,91 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:843 +#: random-bits.xml:818 #, 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:849 +#: random-bits.xml:824 #, no-c-format msgid "# aptitude clean" msgstr "" #. Tag: title -#: random-bits.xml:860 +#: random-bits.xml:835 #, no-c-format msgid "Installing &debian-gnu; over Parallel Line IP (PLIP)" msgstr "" #. Tag: para -#: random-bits.xml:862 +#: random-bits.xml:837 #, no-c-format 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:870 +#: random-bits.xml:845 #, 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:878 +#: random-bits.xml:853 #, 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:883 +#: random-bits.xml:858 #, 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:893 +#: random-bits.xml:868 #, no-c-format msgid "Requirements" msgstr "" #. Tag: para -#: random-bits.xml:896 +#: random-bits.xml:871 #, no-c-format msgid "A target computer, called <emphasis>target</emphasis>, where &debian; will be installed." msgstr "" #. Tag: para -#: random-bits.xml:902 +#: random-bits.xml:877 #, no-c-format msgid "System installation media; see <xref linkend=\"installation-media\"/>." msgstr "" #. Tag: para -#: random-bits.xml:907 +#: random-bits.xml:882 #, 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:913 +#: random-bits.xml:888 #, 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:925 +#: random-bits.xml:900 #, no-c-format msgid "Setting up source" msgstr "" #. Tag: para -#: random-bits.xml:926 +#: random-bits.xml:901 #, 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:931 +#: random-bits.xml:906 #, no-c-format msgid "" "#!/bin/sh\n" @@ -1312,13 +1228,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:937 +#: random-bits.xml:912 #, no-c-format msgid "Installing target" msgstr "" #. Tag: para -#: random-bits.xml:938 +#: random-bits.xml:913 #, 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" @@ -1327,133 +1243,133 @@ msgid "" msgstr "" #. Tag: guimenuitem -#: random-bits.xml:957 +#: random-bits.xml:932 #, no-c-format msgid "Load installer components from CD" msgstr "" #. Tag: para -#: random-bits.xml:959 +#: random-bits.xml:934 #, 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:967 +#: random-bits.xml:942 #, no-c-format msgid "Detect network hardware" msgstr "" #. Tag: para -#: random-bits.xml:972 +#: random-bits.xml:947 #, 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:981 +#: random-bits.xml:956 #, 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:993 +#: random-bits.xml:968 #, no-c-format msgid "Configure the network" msgstr "" #. Tag: para -#: random-bits.xml:996 +#: random-bits.xml:971 #, no-c-format msgid "Auto-configure network with DHCP: No" msgstr "" #. Tag: para -#: random-bits.xml:1001 +#: random-bits.xml:976 #, no-c-format msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>" msgstr "" #. Tag: para -#: random-bits.xml:1006 +#: random-bits.xml:981 #, no-c-format msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>" msgstr "" #. Tag: para -#: random-bits.xml:1012 +#: random-bits.xml:987 #, 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:1031 +#: random-bits.xml:1006 #, no-c-format msgid "Installing &debian-gnu; using PPP over Ethernet (PPPoE)" msgstr "" #. Tag: para -#: random-bits.xml:1033 +#: random-bits.xml:1008 #, 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:1041 +#: random-bits.xml:1016 #, 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:1046 +#: random-bits.xml:1021 #, 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:1053 +#: random-bits.xml:1028 #, 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:1061 +#: random-bits.xml:1036 #, 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:1076 +#: random-bits.xml:1051 #, 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:1095 +#: random-bits.xml:1070 #, 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:1101 +#: random-bits.xml:1076 #, 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:1107 +#: random-bits.xml:1082 #, 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:1116 +#: random-bits.xml:1091 #, 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:1122 +#: random-bits.xml:1097 #, 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 "" diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index c0a58390b..2e796ff93 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: 2015-01-09 19:07+0000\n" +"POT-Creation-Date: 2015-04-15 20:29+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" @@ -877,7 +877,7 @@ msgstr "" #, no-c-format msgid "" "If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to <quote>zero</quote> the first few sectors of the drive: <informalexample><screen>\n" - "# dd if=/dev/zero of=/dev/hd<replaceable>X</replaceable> bs=512 count=2; sync\n" + "# dd if=/dev/zero of=/dev/sd<replaceable>X</replaceable> bs=512 count=2; sync\n" "</screen></informalexample> Note that this will make any existing data on that disk inaccessible." msgstr "" @@ -1220,7 +1220,7 @@ msgstr "" #. Tag: para #: using-d-i.xml:1367 #, no-c-format -msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition." +msgid "If you have booted in EFI mode then within the guided partitioning setup there will be an additional partition, formatted as a FAT32 bootable filesystem, for the EFI boot loader. This partition is known as an EFI System Partition (ESP). There is also an additional menu item in the formatting menu to manually set up a partition as an ESP." msgstr "" #. Tag: para @@ -1234,22 +1234,20 @@ msgstr "" #, no-c-format msgid "" "The list of partitions might look like this: <informalexample><screen>\n" - " IDE1 master (hda) - 6.4 GB WDC AC36400L\n" + " SCSI1 (0,0,0) (sda) - 6.4 GB WDC AC36400L\n" " #1 primary 16.4 MB B f ext2 /boot\n" " #2 primary 551.0 MB swap swap\n" " #3 primary 5.8 GB ntfs\n" " pri/log 8.2 MB FREE SPACE\n" "\n" - " IDE1 slave (hdb) - 80.0 GB ST380021A\n" + " SCSI2 (1,0,0) (sdb) - 80.0 GB ST380021A\n" " #1 primary 15.9 MB ext3\n" " #2 primary 996.0 MB fat16\n" " #3 primary 3.9 GB xfs /home\n" - " #5 logical 6.0 GB f ext3 /\n" + " #5 logical 6.0 GB f ext4 /\n" " #6 logical 1.0 GB f ext3 /var\n" " #7 logical 498.8 MB ext3\n" - " #8 logical 551.5 MB swap swap\n" - " #9 logical 65.8 GB ext2\n" - "</screen></informalexample> This example shows two IDE harddrives divided into several partitions; the first disk has some free space. Each partition line consists of the partition number, its type, size, optional flags, file system, and mountpoint (if any). Note: this particular setup cannot be created using guided partitioning but it does show possible variation that can be achieved using manual partitioning." + "</screen></informalexample> This example shows two hard drives divided into several partitions; the first disk has some free space. Each partition line consists of the partition number, its type, size, optional flags, file system, and mountpoint (if any). Note: this particular setup cannot be created using guided partitioning but it does show possible variation that can be achieved using manual partitioning." msgstr "" #. Tag: para @@ -1297,7 +1295,7 @@ msgstr "" #. Tag: para #: using-d-i.xml:1465 #, no-c-format -msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one." +msgid "If you boot in EFI mode but forget to select and format an EFI System Partition, <command>partman</command> will detect this and will not let you continue until you allocate one." msgstr "" #. Tag: para @@ -1481,319 +1479,313 @@ msgid "Make sure that the system can be booted with the partitioning scheme you msgstr "" #. Tag: para -#: using-d-i.xml:1728 -#, no-c-format -msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) file system. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1737 +#: using-d-i.xml:1727 #, no-c-format msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected." msgstr "" #. Tag: para -#: using-d-i.xml:1750 +#: using-d-i.xml:1740 #, no-c-format msgid "RAID0 is simple — you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD." msgstr "" #. Tag: para -#: using-d-i.xml:1757 +#: using-d-i.xml:1747 #, no-c-format msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided earlier. Don't worry. If you make a mistake and select a different number of partitions, &d-i; won't let you continue until you correct the issue." msgstr "" #. Tag: para -#: using-d-i.xml:1769 +#: using-d-i.xml:1759 #, no-c-format msgid "RAID5 has a setup procedure similar to RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions." msgstr "" #. Tag: para -#: using-d-i.xml:1775 +#: using-d-i.xml:1765 #, no-c-format msgid "RAID6 also has a setup procedure similar to RAID1 except that at least <emphasis>four</emphasis> active partitions are required." msgstr "" #. Tag: para -#: using-d-i.xml:1781 +#: using-d-i.xml:1771 #, no-c-format msgid "RAID10 again has a setup procedure similar to RAID1 except in expert mode. In expert mode, &d-i; will ask you for the layout. The layout has two parts. The first part is the layout type. It is either <literal>n</literal> (for near copies), <literal>f</literal> (for far copies), or <literal>o</literal> (for offset copies). The second part is the number of copies to make of the data. There must be at least that many active devices so that all of the copies can be distributed onto different disks." msgstr "" #. Tag: para -#: using-d-i.xml:1795 +#: using-d-i.xml:1785 #, no-c-format msgid "It is perfectly possible to have several types of MD at once. For example, if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine the first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)." msgstr "" #. Tag: para -#: using-d-i.xml:1804 +#: using-d-i.xml:1794 #, no-c-format msgid "After you set up MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints." msgstr "" #. Tag: title -#: using-d-i.xml:1819 +#: using-d-i.xml:1809 #, no-c-format msgid "Configuring the Logical Volume Manager (LVM)" msgstr "" #. Tag: para -#: using-d-i.xml:1820 +#: using-d-i.xml:1810 #, no-c-format msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation by moving stuff around, symlinking, etc." msgstr "" #. Tag: para -#: using-d-i.xml:1828 +#: using-d-i.xml:1818 #, no-c-format msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disk (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks." msgstr "" #. Tag: para -#: using-d-i.xml:1838 +#: using-d-i.xml:1828 #, no-c-format msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk to the computer, join it with your existing volume group and then resize the logical volume which holds your <filename>/home</filename> filesystem and voila — your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>." msgstr "" #. Tag: para -#: using-d-i.xml:1849 +#: using-d-i.xml:1839 #, no-c-format msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>." msgstr "" #. Tag: para -#: using-d-i.xml:1858 +#: using-d-i.xml:1848 #, no-c-format msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:" msgstr "" #. Tag: para -#: using-d-i.xml:1869 +#: using-d-i.xml:1859 #, no-c-format msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1874 +#: using-d-i.xml:1864 #, no-c-format msgid "Create volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1877 +#: using-d-i.xml:1867 #, no-c-format msgid "Create logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1880 +#: using-d-i.xml:1870 #, no-c-format msgid "Delete volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1883 +#: using-d-i.xml:1873 #, no-c-format msgid "Delete logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1886 +#: using-d-i.xml:1876 #, no-c-format msgid "Extend volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1889 +#: using-d-i.xml:1879 #, no-c-format msgid "Reduce volume group" msgstr "" #. Tag: para -#: using-d-i.xml:1891 +#: using-d-i.xml:1881 #, no-c-format msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen" msgstr "" #. Tag: para -#: using-d-i.xml:1897 +#: using-d-i.xml:1887 #, no-c-format msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it." msgstr "" #. Tag: para -#: using-d-i.xml:1902 +#: using-d-i.xml:1892 #, no-c-format msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)." msgstr "" #. Tag: title -#: using-d-i.xml:1916 +#: using-d-i.xml:1906 #, no-c-format msgid "Configuring Encrypted Volumes" msgstr "" #. Tag: para -#: using-d-i.xml:1917 +#: using-d-i.xml:1907 #, no-c-format msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters." msgstr "" #. Tag: para -#: using-d-i.xml:1929 +#: using-d-i.xml:1919 #, no-c-format msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition." msgstr "" #. Tag: para -#: using-d-i.xml:1944 +#: using-d-i.xml:1934 #, no-c-format msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length." msgstr "" #. Tag: para -#: using-d-i.xml:1951 +#: using-d-i.xml:1941 #, no-c-format msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition." msgstr "" #. Tag: para -#: using-d-i.xml:1962 +#: using-d-i.xml:1952 #, no-c-format msgid "The encryption method supported by &d-i; is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes)." msgstr "" #. Tag: para -#: using-d-i.xml:1971 +#: using-d-i.xml:1961 #, no-c-format msgid "Let's have a look at the options available when you select encryption via <userinput>Device-mapper (dm-crypt)</userinput>. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind." msgstr "" #. Tag: term -#: using-d-i.xml:1981 +#: using-d-i.xml:1971 #, no-c-format msgid "Encryption: <userinput>aes</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1983 +#: using-d-i.xml:1973 #, no-c-format msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century." msgstr "" #. Tag: term -#: using-d-i.xml:2001 +#: using-d-i.xml:1991 #, no-c-format msgid "Key size: <userinput>256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:2003 +#: using-d-i.xml:1993 #, no-c-format msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher." msgstr "" #. Tag: term -#: using-d-i.xml:2015 +#: using-d-i.xml:2005 #, no-c-format msgid "IV algorithm: <userinput>xts-plain64</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:2017 +#: using-d-i.xml:2007 #, no-c-format msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data." msgstr "" #. Tag: para -#: using-d-i.xml:2027 +#: using-d-i.xml:2017 #, no-c-format msgid "From the provided alternatives, the default <userinput>xts-plain64</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms." msgstr "" #. Tag: term -#: using-d-i.xml:2039 +#: using-d-i.xml:2029 #, no-c-format msgid "Encryption key: <userinput>Passphrase</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:2041 +#: using-d-i.xml:2031 #, no-c-format msgid "Here you can choose the type of the encryption key for this partition." msgstr "" #. Tag: term -#: using-d-i.xml:2047 +#: using-d-i.xml:2037 #, no-c-format msgid "Passphrase" msgstr "" #. Tag: para -#: using-d-i.xml:2048 +#: using-d-i.xml:2038 #, no-c-format msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process." msgstr "" #. Tag: term -#: using-d-i.xml:2063 +#: using-d-i.xml:2053 #, no-c-format msgid "Random key" msgstr "" #. Tag: para -#: using-d-i.xml:2064 +#: using-d-i.xml:2054 #, no-c-format msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)" msgstr "" #. Tag: para -#: using-d-i.xml:2073 +#: using-d-i.xml:2063 #, no-c-format msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition." msgstr "" #. Tag: term -#: using-d-i.xml:2092 +#: using-d-i.xml:2082 #, no-c-format msgid "Erase data: <userinput>yes</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:2094 +#: using-d-i.xml:2084 #, no-c-format msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>." msgstr "" #. Tag: para -#: using-d-i.xml:2115 +#: using-d-i.xml:2105 #, no-c-format msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time." msgstr "" #. Tag: para -#: using-d-i.xml:2125 +#: using-d-i.xml:2115 #, no-c-format msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)." msgstr "" #. Tag: para -#: using-d-i.xml:2134 +#: using-d-i.xml:2124 #, no-c-format msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system." msgstr "" #. Tag: para -#: using-d-i.xml:2147 +#: using-d-i.xml:2137 #, no-c-format msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted." msgstr "" #. Tag: para -#: using-d-i.xml:2163 +#: using-d-i.xml:2153 #, no-c-format msgid "" "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows a volume encrypted via dm-crypt. <informalexample><screen>\n" @@ -1803,571 +1795,571 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:2175 +#: using-d-i.xml:2165 #, no-c-format msgid "Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between the ordinary boot process and the boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:2185 +#: using-d-i.xml:2175 #, no-c-format msgid "Once you are satisfied with the partitioning scheme, continue with the installation." msgstr "" #. Tag: title -#: using-d-i.xml:2196 +#: using-d-i.xml:2186 #, no-c-format msgid "Installing the Base System" msgstr "" #. Tag: para -#: using-d-i.xml:2197 +#: using-d-i.xml:2187 #, no-c-format msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time." msgstr "" #. Tag: para -#: using-d-i.xml:2210 +#: using-d-i.xml:2200 #, no-c-format msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>." msgstr "" #. Tag: para -#: using-d-i.xml:2219 +#: using-d-i.xml:2209 #, no-c-format msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console." msgstr "" #. Tag: para -#: using-d-i.xml:2225 +#: using-d-i.xml:2215 #, no-c-format 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 -#: using-d-i.xml:2232 +#: using-d-i.xml:2222 #, no-c-format msgid "When packages are installed using the package management system, it will by default also install packages that are recommended by those packages. Recommended packages are not strictly required for the core functionality of the selected software, but they do enhance that software and should, in the view of the package maintainers, normally be installed together with that software." msgstr "" #. Tag: para -#: using-d-i.xml:2242 +#: using-d-i.xml:2232 #, no-c-format msgid "For technical reasons packages installed during the installation of the base system are installed without their <quote>Recommends</quote>. The rule described above only takes effect after this point in the installation process." msgstr "" #. Tag: title -#: using-d-i.xml:2254 +#: using-d-i.xml:2244 #, no-c-format msgid "Installing Additional Software" msgstr "" #. Tag: para -#: using-d-i.xml:2255 +#: using-d-i.xml:2245 #, no-c-format msgid "At this point you have a usable but limited system. Most users will want to install additional software on the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network connection." msgstr "" #. Tag: title -#: using-d-i.xml:2270 +#: using-d-i.xml:2260 #, no-c-format msgid "Configuring apt" msgstr "" #. Tag: para -#: using-d-i.xml:2272 +#: using-d-i.xml:2262 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2295 +#: using-d-i.xml:2285 #, no-c-format msgid "<command>apt</command> must be configured so that it knows from where to retrieve packages. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>. You can examine and edit this file to your liking after the installation is complete." msgstr "" #. Tag: para -#: using-d-i.xml:2302 +#: using-d-i.xml:2292 #, no-c-format msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>stable-updates</quote> service." msgstr "" #. Tag: para -#: using-d-i.xml:2311 +#: using-d-i.xml:2301 #, no-c-format msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or stable-updates services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive." msgstr "" #. Tag: title -#: using-d-i.xml:2322 +#: using-d-i.xml:2312 #, no-c-format msgid "Installing from more than one CD or DVD" msgstr "" #. Tag: para -#: using-d-i.xml:2324 +#: using-d-i.xml:2314 #, no-c-format msgid "If you are installing from a CD or a DVD that is part of a larger set, the installer will ask if you want to scan additional CDs or DVDs. If you have additional CDs or DVDs available, you probably want to do this so the installer can use the packages included on them." msgstr "" #. Tag: para -#: using-d-i.xml:2331 +#: using-d-i.xml:2321 #, no-c-format msgid "If you do not have any additional CDs or DVDs, that is no problem: using them is not required. If you also do not use a network mirror (as explained in the next section), it can mean that not all packages belonging to the tasks you select in the next step of the installation can be installed." msgstr "" #. Tag: para -#: using-d-i.xml:2339 +#: using-d-i.xml:2329 #, no-c-format msgid "Packages are included on CDs (and DVDs) in the order of their popularity. This means that for most uses only the first CDs in a set are needed and that only very few people actually use any of the packages included on the last CDs in a set." msgstr "" #. Tag: para -#: using-d-i.xml:2346 +#: using-d-i.xml:2336 #, no-c-format msgid "It also means that buying or downloading and burning a full CD set is just a waste of money as you'll never use most of them. In most cases you are better off getting only the first 3 to 8 CDs and installing any additional packages you may need from the Internet by using a mirror. The same goes for DVD sets: the first DVD, or maybe the first two DVDs will cover most needs." msgstr "" #. Tag: para -#: using-d-i.xml:2356 +#: using-d-i.xml:2346 #, no-c-format msgid "If you do scan multiple CDs or DVDs, the installer will prompt you to exchange them when it needs packages from another CD/DVD than the one currently in the drive. Note that only CDs or DVDs that belong to the same set should be scanned. The order in which they are scanned does not really matter, but scanning them in ascending order will reduce the chance of mistakes." msgstr "" #. Tag: title -#: using-d-i.xml:2369 +#: using-d-i.xml:2359 #, no-c-format msgid "Using a network mirror" msgstr "" #. Tag: para -#: using-d-i.xml:2371 +#: using-d-i.xml:2361 #, no-c-format msgid "One question that will be asked during most installs is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions." msgstr "" #. Tag: para -#: using-d-i.xml:2377 +#: using-d-i.xml:2367 #, no-c-format msgid "If you are <emphasis>not</emphasis> installing from a full CD or DVD or using a full CD/DVD image, you really should use a network mirror as otherwise you will end up with only a very minimal system. However, if you have a limited Internet connection it is best <emphasis>not</emphasis> to select the <literal>desktop</literal> task in the next step of the installation." msgstr "" #. Tag: para -#: using-d-i.xml:2386 +#: using-d-i.xml:2376 #, no-c-format msgid "If you are installing from a single full CD or using a full CD image, using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. If you have a limited Internet connection it may still be best to <emphasis>not</emphasis> select a network mirror here, but to finish the installation using only what's available on the CD and selectively install additional packages after the installation (i.e. after you have rebooted into the new system)." msgstr "" #. Tag: para -#: using-d-i.xml:2397 +#: using-d-i.xml:2387 #, no-c-format msgid "If you are installing from a DVD or using a DVD image, any packages needed during the installation should be present on the first DVD. The same is true if you have scanned multiple CDs as explained in the previous section. Use of a network mirror is optional." msgstr "" #. Tag: para -#: using-d-i.xml:2404 +#: using-d-i.xml:2394 #, no-c-format msgid "One advantage of adding a network mirror is that updates that have occurred since the CD/DVD set was created and have been included in a point release, will become available for installation, thus extending the life of your CD/DVD set without compromising the security or stability of the installed system." msgstr "" #. Tag: para -#: using-d-i.xml:2411 +#: using-d-i.xml:2401 #, no-c-format msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available from CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on" msgstr "" #. Tag: para -#: using-d-i.xml:2420 +#: using-d-i.xml:2410 #, no-c-format msgid "the tasks you select in the next step of the installation," msgstr "" #. Tag: para -#: using-d-i.xml:2425 +#: using-d-i.xml:2415 #, no-c-format msgid "which packages are needed for those tasks," msgstr "" #. Tag: para -#: using-d-i.xml:2430 +#: using-d-i.xml:2420 #, no-c-format msgid "which of those packages are present on the CDs or DVDs you have scanned, and" msgstr "" #. Tag: para -#: using-d-i.xml:2435 +#: using-d-i.xml:2425 #, no-c-format msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or stable-updates)." msgstr "" #. Tag: para -#: using-d-i.xml:2444 +#: using-d-i.xml:2434 #, no-c-format msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or stable-updates update available for them and those services have been configured." msgstr "" #. Tag: title -#: using-d-i.xml:2455 +#: using-d-i.xml:2445 #, no-c-format msgid "Choosing a network mirror" msgstr "" #. Tag: para -#: using-d-i.xml:2456 +#: using-d-i.xml:2446 #, no-c-format msgid "If you have selected to use a network mirror during the installation (optional for CD/DVD installs, required for netboot images), you will be presented with a list of geographically nearby (and therefore hopefully fast) network mirrors, based upon your country selection earlier in the installation process. Choosing the offered default is usually fine." msgstr "" #. Tag: para -#: using-d-i.xml:2464 +#: using-d-i.xml:2454 #, no-c-format msgid "A mirror can also be specified by hand by choosing <quote>enter information manually</quote> . You can then specify a mirror host name and an optional port number. As of Wheezy, that actually has to be a URL base, i.e. when specifying an IPv6 address, one has to add square brackets around it, for instance <quote>[2001:db8::1]</quote>." msgstr "" #. Tag: para -#: using-d-i.xml:2472 +#: using-d-i.xml:2462 #, no-c-format msgid "If your computer is on an IPv6-only network (which is probably not the case for the vast majority of users), using the default mirror for your country might not work. All the mirrors in the list are reachable via IPv4, but only some of them can be used via IPv6. As connectivity of individual mirrors can change over time, this information is not available in the installer. If there is no IPv6 connectivity for the default mirror for your country, you can either try some of the other mirrors offered to you or choose the <quote>enter information manually</quote> option. You can then specify <quote>ftp.ipv6.debian.org</quote> as the mirror name, which is an alias for a mirror available via IPv6, although it will probably not be the fastest possible one." msgstr "" #. Tag: para -#: using-d-i.xml:2486 +#: using-d-i.xml:2476 #, no-c-format -msgid "Another option when choosing to specify the mirror manually is to use <quote>http.debian.net</quote> as your mirror. <quote>http.debian.net</quote> is not a physical mirror but a mirror redirection service, i.e. it automatically refers your system to a real mirror near you in terms of network topology. It takes into account by which protocol you connect to it, i.e. if you use IPv6, it will refer you to an IPv6-capable mirror near you." +msgid "Another option when choosing to specify the mirror manually is to use <quote>httpredir.debian.org</quote> as your mirror. <quote>httpredir.debian.org</quote> is not a physical mirror but a mirror redirection service, i.e. it automatically refers your system to a real mirror near you in terms of network topology. It takes into account by which protocol you connect to it, i.e. if you use IPv6, it will refer you to an IPv6-capable mirror near you." msgstr "" #. Tag: title -#: using-d-i.xml:2505 +#: using-d-i.xml:2495 #, no-c-format msgid "Selecting and Installing Software" msgstr "" #. Tag: para -#: using-d-i.xml:2507 +#: using-d-i.xml:2497 #, no-c-format msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks." msgstr "" #. Tag: para -#: using-d-i.xml:2516 +#: using-d-i.xml:2506 #, no-c-format msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks." msgstr "" #. Tag: para -#: using-d-i.xml:2543 +#: using-d-i.xml:2533 #, no-c-format msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can deselect them. You can even opt to install no tasks at all at this point." msgstr "" #. Tag: para -#: using-d-i.xml:2550 +#: using-d-i.xml:2540 #, no-c-format msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task." msgstr "" #. Tag: para -#: using-d-i.xml:2556 +#: using-d-i.xml:2546 #, no-c-format msgid "The <quote>Desktop environment</quote> task will install a graphical desktop environment." msgstr "" #. Tag: para -#: using-d-i.xml:2561 +#: using-d-i.xml:2551 #, no-c-format msgid "By default, &d-i; installs the <phrase arch=\"x86\">Gnome</phrase> <phrase arch=\"non-x86\">Xfce</phrase> desktop environment. It is possible to interactively select a different desktop environment during the installation. It is also possible to install multiple desktops, but some combinations of desktop may not be co-installable." msgstr "" #. Tag: para -#: using-d-i.xml:2569 +#: using-d-i.xml:2559 #, no-c-format msgid "Note that this will only work if the packages needed for the desired desktop environment are actually available. If you are installing using a single full CD image, they will possibly need to be downloaded from a network mirror as some of the needed packages for your choice might only be included on later CDs. Installing any of the available desktop environments this way should work fine if you are using a DVD image or any other installation method." msgstr "" #. Tag: para -#: using-d-i.xml:2579 +#: using-d-i.xml:2569 #, no-c-format msgid "The various server tasks will install software roughly as follows. Web server: <classname>apache2</classname>; Print server: <classname>cups</classname>; SSH server: <classname>openssh</classname>." msgstr "" #. Tag: para -#: using-d-i.xml:2586 +#: using-d-i.xml:2576 #, no-c-format msgid "The <quote>Standard system</quote> task will install any package that has a priority <quote>standard</quote>. This includes a lot of common utilities that are normally available on any Linux or Unix system. You should leave this task selected unless you know what you are doing and want a really minimal system." msgstr "" #. Tag: para -#: using-d-i.xml:2594 +#: using-d-i.xml:2584 #, no-c-format msgid "If during language selection a default locale other than the <quote>C</quote> locale was selected, <command>tasksel</command> will check if any localization tasks are defined for that locale and will automatically try to install relevant localization packages. This includes for example packages containing word lists or special fonts for your language. If a desktop environment was selected, it will also install appropriate localization packages for that (if available)." msgstr "" #. Tag: para -#: using-d-i.xml:2604 +#: using-d-i.xml:2594 #, no-c-format msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the selected tasks. If a particular program needs more information from the user, it will prompt you during this process." msgstr "" #. Tag: para -#: using-d-i.xml:2611 +#: using-d-i.xml:2601 #, no-c-format msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started." msgstr "" #. Tag: para -#: using-d-i.xml:2620 +#: using-d-i.xml:2610 #, no-c-format msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image." msgstr "" #. Tag: title -#: using-d-i.xml:2635 +#: using-d-i.xml:2625 #, no-c-format msgid "Making Your System Bootable" msgstr "" #. Tag: para -#: using-d-i.xml:2637 +#: using-d-i.xml:2627 #, no-c-format msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>" msgstr "" #. Tag: title -#: using-d-i.xml:2652 +#: using-d-i.xml:2642 #, no-c-format msgid "Detecting other operating systems" msgstr "" #. Tag: para -#: using-d-i.xml:2654 +#: using-d-i.xml:2644 #, no-c-format msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to &debian;." msgstr "" #. Tag: para -#: using-d-i.xml:2662 +#: using-d-i.xml:2652 #, no-c-format msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information." msgstr "" #. Tag: title -#: using-d-i.xml:2680 +#: using-d-i.xml:2670 #, no-c-format msgid "<command>palo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2681 +#: using-d-i.xml:2671 #, no-c-format msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions." msgstr "" #. Tag: para -#: using-d-i.xml:2690 +#: using-d-i.xml:2680 #, no-c-format msgid "hppa FIXME ( need more info )" msgstr "" #. Tag: title -#: using-d-i.xml:2702 +#: using-d-i.xml:2692 using-d-i.xml:3030 #, no-c-format msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2704 +#: using-d-i.xml:2694 using-d-i.xml:3032 #, no-c-format msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for new users and old hands alike." msgstr "" #. Tag: para -#: using-d-i.xml:2710 +#: using-d-i.xml:2700 #, no-c-format msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information." msgstr "" #. Tag: para -#: using-d-i.xml:2716 +#: using-d-i.xml:2706 #, no-c-format msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use." msgstr "" #. Tag: title -#: using-d-i.xml:2729 +#: using-d-i.xml:2719 #, no-c-format msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2731 +#: using-d-i.xml:2721 #, no-c-format msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>." msgstr "" #. Tag: para -#: using-d-i.xml:2741 +#: using-d-i.xml:2731 #, no-c-format msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation." msgstr "" #. Tag: para -#: using-d-i.xml:2749 +#: using-d-i.xml:2739 #, no-c-format msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:" msgstr "" #. Tag: term -#: using-d-i.xml:2756 +#: using-d-i.xml:2746 #, no-c-format msgid "Master Boot Record (MBR)" msgstr "" #. Tag: para -#: using-d-i.xml:2756 +#: using-d-i.xml:2746 #, no-c-format msgid "This way the <command>LILO</command> will take complete control of the boot process." msgstr "" #. Tag: term -#: using-d-i.xml:2763 +#: using-d-i.xml:2753 #, no-c-format msgid "new &debian; partition" msgstr "" #. Tag: para -#: using-d-i.xml:2763 +#: using-d-i.xml:2753 #, no-c-format msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new &debian; partition and it will serve as a secondary boot loader." msgstr "" #. Tag: term -#: using-d-i.xml:2772 +#: using-d-i.xml:2762 #, no-c-format msgid "Other choice" msgstr "" #. Tag: para -#: using-d-i.xml:2772 +#: using-d-i.xml:2762 #, no-c-format -msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use traditional device names such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>." +msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use traditional device names such as <filename>/dev/sda</filename>." msgstr "" #. Tag: para -#: using-d-i.xml:2782 +#: using-d-i.xml:2772 #, no-c-format msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record — however, this means that you'll need to use some other way to get back into &debian;!" msgstr "" #. Tag: title -#: using-d-i.xml:2798 +#: using-d-i.xml:2788 #, no-c-format msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2800 +#: using-d-i.xml:2790 #, no-c-format msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to do the actual work of loading and starting the Linux kernel." msgstr "" #. Tag: para -#: using-d-i.xml:2816 +#: using-d-i.xml:2806 #, no-c-format msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem." msgstr "" #. Tag: title -#: using-d-i.xml:2828 +#: using-d-i.xml:2818 #, no-c-format msgid "Choose the correct partition!" msgstr "" #. Tag: para -#: using-d-i.xml:2830 +#: using-d-i.xml:2820 #, no-c-format msgid "The criterion for selecting a partition is that it must be a FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!" msgstr "" #. Tag: title -#: using-d-i.xml:2845 +#: using-d-i.xml:2835 #, no-c-format msgid "EFI Partition Contents" msgstr "" #. Tag: para -#: using-d-i.xml:2847 +#: using-d-i.xml:2837 #, no-c-format msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured." msgstr "" #. Tag: filename -#: using-d-i.xml:2869 +#: using-d-i.xml:2859 #, no-c-format msgid "elilo.conf" msgstr "" #. Tag: para -#: using-d-i.xml:2870 +#: using-d-i.xml:2860 #, no-c-format msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition." msgstr "" #. Tag: filename -#: using-d-i.xml:2879 +#: using-d-i.xml:2869 #, no-c-format msgid "elilo.efi" msgstr "" #. Tag: para -#: using-d-i.xml:2880 +#: using-d-i.xml:2870 #, no-c-format msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>&debian; GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu." msgstr "" #. Tag: filename -#: using-d-i.xml:2890 +#: using-d-i.xml:2880 #, no-c-format msgid "initrd.img" msgstr "" #. Tag: para -#: using-d-i.xml:2891 +#: using-d-i.xml:2881 #, no-c-format msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard &debian; installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>." msgstr "" #. Tag: filename -#: using-d-i.xml:2903 +#: using-d-i.xml:2893 #, no-c-format msgid "readme.txt" msgstr "" #. Tag: para -#: using-d-i.xml:2904 +#: using-d-i.xml:2894 #, no-c-format msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run." msgstr "" #. Tag: filename -#: using-d-i.xml:2914 +#: using-d-i.xml:2904 #, no-c-format msgid "vmlinuz" msgstr "" #. Tag: para -#: using-d-i.xml:2915 +#: using-d-i.xml:2905 #, no-c-format msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard &debian; installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>." msgstr "" #. Tag: title -#: using-d-i.xml:2935 +#: using-d-i.xml:2925 #, no-c-format msgid "<command>arcboot</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2936 +#: using-d-i.xml:2926 #, no-c-format msgid "" "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n" @@ -2380,313 +2372,319 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2955 +#: using-d-i.xml:2945 #, no-c-format msgid "scsi" msgstr "" #. Tag: para -#: using-d-i.xml:2956 +#: using-d-i.xml:2946 #, no-c-format msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2964 +#: using-d-i.xml:2954 #, no-c-format msgid "disk" msgstr "" #. Tag: para -#: using-d-i.xml:2965 +#: using-d-i.xml:2955 #, no-c-format msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2973 +#: using-d-i.xml:2963 #, no-c-format msgid "partnr" msgstr "" #. Tag: para -#: using-d-i.xml:2974 +#: using-d-i.xml:2964 #, no-c-format msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2982 +#: using-d-i.xml:2972 #, no-c-format msgid "config" msgstr "" #. Tag: para -#: using-d-i.xml:2983 +#: using-d-i.xml:2973 #, no-c-format msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: title -#: using-d-i.xml:3004 +#: using-d-i.xml:2994 #, no-c-format msgid "Install <command>Yaboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:3005 +#: using-d-i.xml:2995 #, 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-gnu;." msgstr "" #. Tag: title -#: using-d-i.xml:3023 +#: using-d-i.xml:3013 #, no-c-format msgid "Install <command>Quik</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:3024 +#: using-d-i.xml:3014 #, no-c-format msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones." msgstr "" +#. Tag: para +#: using-d-i.xml:3038 +#, no-c-format +msgid "By default, Grub will be installed into the PReP partition, where it will over complete control of the boot process." +msgstr "" + #. Tag: title -#: using-d-i.xml:3040 +#: using-d-i.xml:3051 #, no-c-format msgid "<command>zipl</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:3041 +#: using-d-i.xml:3052 #, no-c-format msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>." msgstr "" #. Tag: title -#: using-d-i.xml:3058 +#: using-d-i.xml:3069 #, no-c-format msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:3060 +#: using-d-i.xml:3071 #, no-c-format msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install." msgstr "" #. Tag: title -#: using-d-i.xml:3085 +#: using-d-i.xml:3096 #, no-c-format msgid "Making the system bootable with flash-kernel" msgstr "" #. Tag: para -#: using-d-i.xml:3086 +#: using-d-i.xml:3097 #, no-c-format msgid "As there is no common firmware interface on all ARM platforms, the steps required to make the system bootable on ARM devices are highly device-dependent. &debian; uses a tool called <command>flash-kernel </command> to take care of this. Flash-kernel contains a database which describes the particular operations that are required to make the system bootable on various devices. It detects whether the current device is supported, and if yes, performs the necessary operations." msgstr "" #. Tag: para -#: using-d-i.xml:3097 +#: using-d-i.xml:3108 #, no-c-format msgid "On devices which boot from internal NOR- or NAND-flash memory, flash-kernel writes the kernel and the initial ramdisk to this internal memory. This method is particularly common on older armel devices. Please note that most of these devices do not allow having multiple kernels and ramdisks in their internal flash memory, i.e. running flash-kernel on them usually overwrites the previous contents of the flash memory!" msgstr "" #. Tag: para -#: using-d-i.xml:3107 +#: using-d-i.xml:3118 #, no-c-format msgid "For ARM systems that use u-boot as their system firmware and boot the kernel and the initial ramdisk from external storage media (such as MMC/SD-cards, USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an appropriate boot script to allow autobooting without user interaction." msgstr "" #. Tag: title -#: using-d-i.xml:3123 +#: using-d-i.xml:3134 #, no-c-format msgid "Continue Without Boot Loader" msgstr "" #. Tag: para -#: using-d-i.xml:3125 +#: using-d-i.xml:3136 #, no-c-format msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader)." msgstr "" #. Tag: para -#: using-d-i.xml:3132 +#: using-d-i.xml:3143 #, no-c-format msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem." msgstr "" #. Tag: title -#: using-d-i.xml:3149 +#: using-d-i.xml:3160 #, no-c-format msgid "Finishing the Installation" msgstr "" #. Tag: para -#: using-d-i.xml:3150 +#: using-d-i.xml:3161 #, no-c-format msgid "This is the last step in the &debian; installation process during which the installer will do any last minute tasks. It mostly consists of tidying up after the &d-i;." msgstr "" #. Tag: title -#: using-d-i.xml:3163 +#: using-d-i.xml:3174 #, no-c-format msgid "Setting the System Clock" msgstr "" #. Tag: para -#: using-d-i.xml:3165 +#: using-d-i.xml:3176 #, no-c-format msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed." msgstr "" #. Tag: para -#: using-d-i.xml:3172 +#: using-d-i.xml:3183 #, 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=\"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 -#: using-d-i.xml:3183 +#: using-d-i.xml:3194 #, no-c-format msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made." msgstr "" #. Tag: title -#: using-d-i.xml:3198 +#: using-d-i.xml:3209 #, no-c-format msgid "Reboot the System" msgstr "" #. Tag: para -#: using-d-i.xml:3200 +#: using-d-i.xml:3211 #, no-c-format msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new &debian; system." msgstr "" #. Tag: para -#: using-d-i.xml:3206 +#: using-d-i.xml:3217 #, 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-gnu; from the DASD which you selected for the root filesystem during the first steps of the installation." msgstr "" #. Tag: title -#: using-d-i.xml:3219 +#: using-d-i.xml:3230 #, no-c-format msgid "Troubleshooting" msgstr "" #. Tag: para -#: using-d-i.xml:3220 +#: using-d-i.xml:3231 #, no-c-format msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong." msgstr "" #. Tag: title -#: using-d-i.xml:3233 +#: using-d-i.xml:3244 #, no-c-format msgid "Saving the installation logs" msgstr "" #. Tag: para -#: using-d-i.xml:3235 +#: using-d-i.xml:3246 #, no-c-format msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new &debian; system." msgstr "" #. Tag: para -#: using-d-i.xml:3242 +#: using-d-i.xml:3253 #, no-c-format msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report." msgstr "" #. Tag: title -#: using-d-i.xml:3262 +#: using-d-i.xml:3273 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "" #. Tag: para -#: using-d-i.xml:3264 +#: using-d-i.xml:3275 #, no-c-format msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to the installer itself." msgstr "" #. Tag: para -#: using-d-i.xml:3282 +#: using-d-i.xml:3293 #, no-c-format msgid "For the graphical installer see also <xref linkend=\"gtk-using\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:3286 +#: using-d-i.xml:3297 #, no-c-format msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer." msgstr "" #. Tag: para -#: using-d-i.xml:3294 +#: using-d-i.xml:3305 #, no-c-format msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history." msgstr "" #. Tag: para -#: using-d-i.xml:3303 +#: using-d-i.xml:3314 #, no-c-format msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory." msgstr "" #. Tag: para -#: using-d-i.xml:3310 +#: using-d-i.xml:3321 #, no-c-format msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging." msgstr "" #. Tag: para -#: using-d-i.xml:3316 +#: using-d-i.xml:3327 #, no-c-format msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell." msgstr "" #. Tag: title -#: using-d-i.xml:3332 +#: using-d-i.xml:3343 #, no-c-format msgid "Installation Over the Network" msgstr "" #. Tag: para -#: using-d-i.xml:3334 +#: using-d-i.xml:3345 #, no-c-format msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)" msgstr "" #. Tag: para -#: using-d-i.xml:3344 +#: using-d-i.xml:3355 #, no-c-format msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>." msgstr "" #. Tag: para -#: using-d-i.xml:3357 +#: using-d-i.xml:3368 #, no-c-format msgid "For installations on &arch-title;, this is the default method after setting up the network." msgstr "" #. Tag: para -#: using-d-i.xml:3362 +#: using-d-i.xml:3373 #, no-c-format msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the person who will continue the installation remotely." msgstr "" #. Tag: para -#: using-d-i.xml:3374 +#: using-d-i.xml:3385 #, no-c-format msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component." msgstr "" #. Tag: para -#: using-d-i.xml:3380 +#: using-d-i.xml:3391 #, no-c-format msgid "" "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n" @@ -2695,127 +2693,127 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:3397 +#: using-d-i.xml:3408 #, no-c-format msgid "The <command>ssh</command> server in the installer uses a default configuration that does not send keep-alive packets. In principle, a connection to the system being installed should be kept open indefinitely. However, in some situations — depending on your local network setup — the connection may be lost after some period of inactivity. One common case where this can happen is when there is some form of Network Address Translation (NAT) somewhere between the client and the system being installed. Depending on at which point of the installation the connection was lost, you may or may not be able to resume the installation after reconnecting." msgstr "" #. Tag: para -#: using-d-i.xml:3410 +#: using-d-i.xml:3421 #, no-c-format msgid "You may be able to avoid the connection being dropped by adding the option <userinput>-o ServerAliveInterval=<replaceable>value</replaceable></userinput> when starting the <command>ssh</command> connection, or by adding that option in your <command>ssh</command> configuration file. Note however that in some cases adding this option may also <emphasis>cause</emphasis> a connection to be dropped (for example if keep-alive packets are sent during a brief network outage, from which <command>ssh</command> would otherwise have recovered), so it should only be used when needed." msgstr "" #. Tag: para -#: using-d-i.xml:3423 +#: using-d-i.xml:3434 #, no-c-format msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename><footnote> <para> The following command will remove an existing entry for a host: <command>ssh-keygen -R <<replaceable>hostname</replaceable>|<replaceable>IP address</replaceable>></command>. </para> </footnote> and try again." msgstr "" #. Tag: para -#: using-d-i.xml:3439 +#: using-d-i.xml:3450 #, no-c-format msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells." msgstr "" #. Tag: para -#: using-d-i.xml:3449 +#: using-d-i.xml:3460 #, no-c-format msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system." msgstr "" #. Tag: title -#: using-d-i.xml:3468 +#: using-d-i.xml:3479 #, no-c-format msgid "Loading Missing Firmware" msgstr "" #. Tag: para -#: using-d-i.xml:3469 +#: using-d-i.xml:3480 #, no-c-format msgid "As described in <xref linkend=\"hardware-firmware\"/>, some devices require firmware to be loaded. In most cases the device will not work at all if the firmware is not available; sometimes basic functionality is not impaired if it is missing and the firmware is only needed to enable additional features." msgstr "" #. Tag: para -#: using-d-i.xml:3477 +#: using-d-i.xml:3488 #, no-c-format msgid "If a device driver requests firmware that is not available, &d-i; will display a dialog offering to load the missing firmware. If this option is selected, &d-i; will scan available devices for either loose firmware files or packages containing firmware. If found, the firmware will be copied to the correct location (<filename>/lib/firmware</filename>) and the driver module will be reloaded." msgstr "" #. Tag: para -#: using-d-i.xml:3487 +#: using-d-i.xml:3498 #, no-c-format msgid "Which devices are scanned and which file systems are supported depends on the architecture, the installation method and the stage of the installation. Especially during the early stages of the installation, loading the firmware is most likely to succeed from a FAT-formatted floppy disk or USB stick. <phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an MMC or SD card.</phrase>" msgstr "" #. Tag: para -#: using-d-i.xml:3497 +#: using-d-i.xml:3508 #, no-c-format msgid "Note that it is possible to skip loading the firmware if you know the device will also function without it, or if the device is not needed during the installation." msgstr "" #. Tag: para -#: using-d-i.xml:3503 +#: using-d-i.xml:3514 #, no-c-format msgid "&d-i; only prompts for firmware needed by kernel modules loaded during the installation. Not all drivers are included in &d-i;, in particular radeon is not, so this implies that the capabilities of some devices may be no different at the end of the installation from what they were at the beginning. Consequently, some of your hardware may not be being used to its full potential. If you suspect this is the case, or are just curious, it is not a bad idea to check the output of the <command>dmesg</command> command on the newly booted system and search for <quote>firmware</quote>." msgstr "" #. Tag: title -#: using-d-i.xml:3517 +#: using-d-i.xml:3528 #, no-c-format msgid "Preparing a medium" msgstr "" #. Tag: para -#: using-d-i.xml:3518 +#: using-d-i.xml:3529 #, no-c-format msgid "Official CD images do not include non-free firmware. The most common method to load such firmware is from some removable medium such as a USB stick. Alternatively, unofficial CD builds containing non-free firmware can be found at <ulink url=\"&url-firmware-cds;\"></ulink>. To prepare a USB stick (or other medium like a hard drive partition, or floppy disk), the firmware files or packages must be placed in either the root directory or a directory named <filename>/firmware</filename> of the file system on the medium. The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation." msgstr "" #. Tag: para -#: using-d-i.xml:3531 +#: using-d-i.xml:3542 #, no-c-format 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 -#: using-d-i.xml:3545 +#: using-d-i.xml:3556 #, no-c-format msgid "If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) archive. The following overview should list most available firmware packages but is not guaranteed to be complete and may also contain non-firmware packages:" msgstr "" #. Tag: para -#: using-d-i.xml:3559 +#: using-d-i.xml:3570 #, no-c-format msgid "It is also possible to copy individual firmware files to the medium. Loose firmware could be obtained for example from an already installed system or from a hardware vendor." msgstr "" #. Tag: title -#: using-d-i.xml:3568 +#: using-d-i.xml:3579 #, no-c-format msgid "Firmware and the Installed System" msgstr "" #. Tag: para -#: using-d-i.xml:3569 +#: using-d-i.xml:3580 #, no-c-format msgid "Any firmware loaded during the installation will be copied automatically to the installed system. In most cases this will ensure that the device that requires the firmware will also work correctly after the system is rebooted into the installed system. However, if the installed system runs a different kernel version from the installer there is a slight chance that the firmware cannot be loaded due to version skew." msgstr "" #. Tag: para -#: using-d-i.xml:3578 +#: using-d-i.xml:3589 #, no-c-format msgid "If the firmware was loaded from a firmware package, &d-i; will also install this package for the installed system and will automatically add the non-free section of the package archive in APT's <filename>sources.list</filename>. This has the advantage that the firmware should be updated automatically if a new version becomes available." msgstr "" #. Tag: para -#: using-d-i.xml:3586 +#: using-d-i.xml:3597 #, no-c-format msgid "If loading the firmware was skipped during the installation, the relevant device will probably not work with the installed system until the firmware (package) is installed manually." msgstr "" #. Tag: para -#: using-d-i.xml:3593 +#: using-d-i.xml:3604 #, no-c-format msgid "If the firmware was loaded from loose firmware files, the firmware copied to the installed system will <emphasis>not</emphasis> be automatically updated unless the corresponding firmware package (if available) is installed after the installation is completed." msgstr "" |