diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/administrivia.pot | 4 | ||||
| -rw-r--r-- | po/pot/bookinfo.pot | 4 | ||||
| -rw-r--r-- | po/pot/boot-installer.pot | 498 | ||||
| -rw-r--r-- | po/pot/boot-new.pot | 4 | ||||
| -rw-r--r-- | po/pot/gpl.pot | 4 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 574 | ||||
| -rw-r--r-- | po/pot/install-methods.pot | 4 | ||||
| -rw-r--r-- | po/pot/installation-howto.pot | 4 | ||||
| -rw-r--r-- | po/pot/partitioning.pot | 52 | ||||
| -rw-r--r-- | po/pot/post-install.pot | 4 | ||||
| -rw-r--r-- | po/pot/preface.pot | 4 | ||||
| -rw-r--r-- | po/pot/preparing.pot | 4 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 12 | ||||
| -rw-r--r-- | po/pot/random-bits.pot | 205 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 4 | ||||
| -rw-r--r-- | po/pot/welcome.pot | 6 |
16 files changed, 635 insertions, 752 deletions
diff --git a/po/pot/administrivia.pot b/po/pot/administrivia.pot index a0d3315c0..4aebb0e29 100644 --- a/po/pot/administrivia.pot +++ b/po/pot/administrivia.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-04-16 19:15+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title diff --git a/po/pot/bookinfo.pot b/po/pot/bookinfo.pot index 50b0174a2..5d39e4b12 100644 --- a/po/pot/bookinfo.pot +++ b/po/pot/bookinfo.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-04-16 19:15+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 5878bb0d5..603fa3841 100644 --- a/po/pot/boot-installer.pot +++ b/po/pot/boot-installer.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-05-22 19:06+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title @@ -45,19 +45,19 @@ msgid "Booting from TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127 boot-installer.xml:1657 boot-installer.xml:1766 +#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127 boot-installer.xml:1310 boot-installer.xml:1632 boot-installer.xml:1741 #, no-c-format msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)." msgstr "" #. Tag: para -#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132 boot-installer.xml:1662 boot-installer.xml:1771 +#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132 boot-installer.xml:1315 boot-installer.xml:1637 boot-installer.xml:1746 #, no-c-format msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server." msgstr "" #. Tag: para -#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137 boot-installer.xml:1667 boot-installer.xml:1776 +#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137 boot-installer.xml:1320 boot-installer.xml:1642 boot-installer.xml:1751 #, no-c-format msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>." msgstr "" @@ -69,25 +69,25 @@ msgid "Booting from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746 boot-installer.xml:1426 boot-installer.xml:1805 +#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746 boot-installer.xml:1401 boot-installer.xml:1780 #, no-c-format msgid "The easiest route for most people will be to use a set of &debian; CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply <phrase arch=\"x86\"> configure your system for booting off a CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert your CD, reboot, and proceed to the next chapter." msgstr "" #. Tag: para -#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757 boot-installer.xml:1437 boot-installer.xml:1816 +#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757 boot-installer.xml:1412 boot-installer.xml:1791 #, no-c-format msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you." msgstr "" #. Tag: para -#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765 boot-installer.xml:1445 boot-installer.xml:1824 +#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765 boot-installer.xml:1420 boot-installer.xml:1799 #, no-c-format msgid "Even if you cannot boot from CD-ROM, you can probably install the &debian; system components and any packages you want from CD-ROM. Simply boot using a different media, such as floppies. When it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive." msgstr "" #. Tag: para -#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773 boot-installer.xml:1453 boot-installer.xml:1832 +#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773 boot-installer.xml:1428 boot-installer.xml:1807 #, no-c-format msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." msgstr "" @@ -216,7 +216,7 @@ msgid "The installer will now start as usual." msgstr "" #. Tag: title -#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1420 boot-installer.xml:1799 +#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1395 boot-installer.xml:1774 #, no-c-format msgid "Booting from a CD-ROM" msgstr "" @@ -388,13 +388,13 @@ msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-s msgstr "" #. Tag: title -#: boot-installer.xml:522 boot-installer.xml:1706 +#: boot-installer.xml:522 boot-installer.xml:1681 #, no-c-format msgid "Booting from Floppies" msgstr "" #. Tag: para -#: boot-installer.xml:523 boot-installer.xml:1714 +#: boot-installer.xml:523 boot-installer.xml:1689 #, 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 "" @@ -436,7 +436,7 @@ msgid "After booting from the boot floppy, the root floppy is requested. Insert msgstr "" #. Tag: title -#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250 boot-installer.xml:1304 boot-installer.xml:1651 boot-installer.xml:1760 +#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250 boot-installer.xml:1304 boot-installer.xml:1626 boot-installer.xml:1735 #, no-c-format msgid "Booting with TFTP" msgstr "" @@ -864,7 +864,7 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:2038 +#: boot-installer.xml:1274 boot-installer.xml:2013 #, no-c-format msgid "Boot Parameters" msgstr "" @@ -891,67 +891,37 @@ msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: title -#: boot-installer.xml:1307 boot-installer.xml:1344 -#, no-c-format -msgid "Cobalt TFTP Booting" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1308 -#, no-c-format -msgid "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to install an NFS server and put the installer files in <filename>/nfsroot</filename>. When you boot your Cobalt, you have to press the left and the right cursor buttons at the same time and the machine will boot via the network from NFS. It will then display several options on the display. There are the following two installation methods:" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1318 -#, no-c-format -msgid "Via SSH (default): In this case, the installer will configure the network via DHCP and start an SSH server. It will then display a random password and other login information (such as the IP address) on the Cobalt LCD. When you connect to the machine with an SSH client you can start with the installation." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1327 -#, no-c-format -msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1345 -#, no-c-format -msgid "You cannot pass any boot parameters directly. Instead, you have to edit the <filename>/nfsroot/default.colo</filename> file on the NFS server and add your parameters to the <replaceable>args</replaceable> variable." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1360 +#: boot-installer.xml:1335 #, no-c-format msgid "s390 Limitations" msgstr "" #. Tag: para -#: boot-installer.xml:1361 +#: boot-installer.xml:1336 #, 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:1366 +#: boot-installer.xml:1341 #, 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:1377 +#: boot-installer.xml:1352 #, no-c-format msgid "s390 Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1378 +#: boot-installer.xml:1353 #, 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:1395 +#: boot-installer.xml:1370 #, 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" @@ -963,13 +933,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1460 +#: boot-installer.xml:1435 #, 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:1469 +#: boot-installer.xml:1444 #, 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" @@ -978,79 +948,79 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:1480 +#: boot-installer.xml:1455 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "" #. Tag: para -#: boot-installer.xml:1482 +#: boot-installer.xml:1457 #, 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:1491 +#: boot-installer.xml:1466 #, 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:1497 +#: boot-installer.xml:1472 #, no-c-format msgid "boot cd install/pegasos" msgstr "" #. Tag: para -#: boot-installer.xml:1499 +#: boot-installer.xml:1474 #, 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:1504 +#: boot-installer.xml:1479 #, no-c-format msgid "0 > boot cdrom" msgstr "" #. Tag: title -#: boot-installer.xml:1510 +#: boot-installer.xml:1485 #, no-c-format msgid "Booting from Hard Disk" msgstr "" #. Tag: para -#: boot-installer.xml:1516 +#: boot-installer.xml:1491 #, 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:1522 +#: boot-installer.xml:1497 #, 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:1542 +#: boot-installer.xml:1517 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" #. Tag: para -#: boot-installer.xml:1543 +#: boot-installer.xml:1518 #, 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:1561 +#: boot-installer.xml:1536 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" #. Tag: para -#: boot-installer.xml:1562 +#: boot-installer.xml:1537 #, 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" @@ -1061,31 +1031,31 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:1594 +#: boot-installer.xml:1569 #, no-c-format msgid "Booting from USB memory stick" msgstr "" #. Tag: para -#: boot-installer.xml:1595 +#: boot-installer.xml:1570 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" #. Tag: para -#: boot-installer.xml:1601 +#: boot-installer.xml:1576 #, 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:1610 +#: boot-installer.xml:1585 #, 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:1622 +#: boot-installer.xml:1597 #, no-c-format msgid "" "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n" @@ -1094,25 +1064,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1636 +#: boot-installer.xml:1611 #, 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:1642 +#: boot-installer.xml:1617 #, 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:1675 +#: boot-installer.xml:1650 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" #. Tag: para -#: boot-installer.xml:1679 +#: boot-installer.xml:1654 #, 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" @@ -1125,739 +1095,739 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1707 +#: boot-installer.xml:1682 #, 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:1719 +#: boot-installer.xml:1694 #, 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:1725 +#: boot-installer.xml:1700 #, 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:1732 +#: boot-installer.xml:1707 #, 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:1743 +#: boot-installer.xml:1718 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1744 +#: boot-installer.xml:1719 #, no-c-format msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ." msgstr "" #. Tag: para -#: boot-installer.xml:1784 +#: boot-installer.xml:1759 #, 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:1839 +#: boot-installer.xml:1814 #, 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:1848 +#: boot-installer.xml:1823 #, no-c-format msgid "IDPROM Messages" msgstr "" #. Tag: para -#: boot-installer.xml:1849 +#: boot-installer.xml:1824 #, 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:1868 +#: boot-installer.xml:1843 #, no-c-format msgid "Accessibility" msgstr "" #. Tag: para -#: boot-installer.xml:1869 +#: boot-installer.xml:1844 #, no-c-format msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features<phrase arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard." msgstr "" #. Tag: title -#: boot-installer.xml:1889 +#: boot-installer.xml:1864 #, no-c-format msgid "USB Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:1890 +#: boot-installer.xml:1865 #, 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:1905 +#: boot-installer.xml:1880 #, no-c-format msgid "Serial Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:1906 +#: boot-installer.xml:1881 #, 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:1929 boot-installer.xml:2936 +#: boot-installer.xml:1904 boot-installer.xml:2911 #, no-c-format msgid "Software Speech Synthesis" msgstr "" #. Tag: para -#: boot-installer.xml:1930 +#: boot-installer.xml:1905 #, 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:1939 +#: boot-installer.xml:1914 #, 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:1945 +#: boot-installer.xml:1920 #, 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:1964 +#: boot-installer.xml:1939 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: boot-installer.xml:1965 +#: boot-installer.xml:1940 #, 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:1972 +#: boot-installer.xml:1947 #, 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:1987 +#: boot-installer.xml:1962 #, no-c-format msgid "Board Devices" msgstr "" #. Tag: para -#: boot-installer.xml:1988 +#: boot-installer.xml:1963 #, 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:1996 +#: boot-installer.xml:1971 #, 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:2004 +#: boot-installer.xml:1979 #, no-c-format msgid "High-Contrast Theme" msgstr "" #. Tag: para -#: boot-installer.xml:2005 +#: boot-installer.xml:1980 #, 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:2014 +#: boot-installer.xml:1989 #, no-c-format msgid "Preseeding" msgstr "" #. Tag: para -#: boot-installer.xml:2015 +#: boot-installer.xml:1990 #, 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:2023 +#: boot-installer.xml:1998 #, no-c-format msgid "Accessibility of the installed system" msgstr "" #. Tag: para -#: boot-installer.xml:2024 +#: boot-installer.xml:1999 #, 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:2039 +#: boot-installer.xml:2014 #, 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:2046 +#: boot-installer.xml:2021 #, 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:2053 +#: boot-installer.xml:2028 #, 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:2065 +#: boot-installer.xml:2040 #, no-c-format msgid "Boot console" msgstr "" #. Tag: para -#: boot-installer.xml:2067 +#: boot-installer.xml:2042 #, 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:2079 +#: boot-installer.xml:2054 #, 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." msgstr "" #. Tag: para -#: boot-installer.xml:2085 +#: boot-installer.xml:2060 #, 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:2101 +#: boot-installer.xml:2076 #, 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:2113 +#: boot-installer.xml:2088 #, no-c-format msgid "&debian; Installer Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2114 +#: boot-installer.xml:2089 #, 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:2127 +#: boot-installer.xml:2102 #, 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:2139 +#: boot-installer.xml:2114 #, no-c-format msgid "debconf/priority (priority)" msgstr "" #. Tag: para -#: boot-installer.xml:2140 +#: boot-installer.xml:2115 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" #. Tag: para -#: boot-installer.xml:2144 +#: boot-installer.xml:2119 #, 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:2151 +#: boot-installer.xml:2126 #, 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:2165 +#: boot-installer.xml:2140 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para -#: boot-installer.xml:2166 +#: boot-installer.xml:2141 #, 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:2197 +#: boot-installer.xml:2172 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:2198 +#: boot-installer.xml:2173 #, 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:2207 +#: boot-installer.xml:2182 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:2208 +#: boot-installer.xml:2183 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:2212 +#: boot-installer.xml:2187 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:2213 +#: boot-installer.xml:2188 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:2217 +#: boot-installer.xml:2192 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:2218 +#: boot-installer.xml:2193 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:2222 +#: boot-installer.xml:2197 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:2223 +#: boot-installer.xml:2198 #, 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:2237 +#: boot-installer.xml:2212 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:2238 +#: boot-installer.xml:2213 #, 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:2244 +#: boot-installer.xml:2219 #, 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:2255 +#: boot-installer.xml:2230 #, no-c-format msgid "log_host" msgstr "" #. Tag: term -#: boot-installer.xml:2256 +#: boot-installer.xml:2231 #, no-c-format msgid "log_port" msgstr "" #. Tag: para -#: boot-installer.xml:2257 +#: boot-installer.xml:2232 #, 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:2268 +#: boot-installer.xml:2243 #, no-c-format msgid "lowmem" msgstr "" #. Tag: para -#: boot-installer.xml:2269 +#: boot-installer.xml:2244 #, 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:2279 +#: boot-installer.xml:2254 #, no-c-format msgid "noshell" msgstr "" #. Tag: para -#: boot-installer.xml:2280 +#: boot-installer.xml:2255 #, 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:2289 +#: boot-installer.xml:2264 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "" #. Tag: para -#: boot-installer.xml:2290 +#: boot-installer.xml:2265 #, 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:2299 +#: boot-installer.xml:2274 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:2303 +#: boot-installer.xml:2278 #, 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:2317 +#: boot-installer.xml:2292 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "" #. Tag: para -#: boot-installer.xml:2318 +#: boot-installer.xml:2293 #, 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:2330 boot-installer.xml:2563 +#: boot-installer.xml:2305 boot-installer.xml:2538 #, no-c-format msgid "netcfg/disable_autoconfig" msgstr "" #. Tag: para -#: boot-installer.xml:2331 +#: boot-installer.xml:2306 #, 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:2338 +#: boot-installer.xml:2313 #, 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:2349 +#: boot-installer.xml:2324 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:2350 +#: boot-installer.xml:2325 #, 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:2360 +#: boot-installer.xml:2335 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "" #. Tag: para -#: boot-installer.xml:2361 +#: boot-installer.xml:2336 #, 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:2372 +#: boot-installer.xml:2347 #, no-c-format msgid "preseed/url (url)" msgstr "" #. Tag: para -#: boot-installer.xml:2373 +#: boot-installer.xml:2348 #, 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:2382 +#: boot-installer.xml:2357 #, no-c-format msgid "preseed/file (file)" msgstr "" #. Tag: para -#: boot-installer.xml:2383 +#: boot-installer.xml:2358 #, 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:2392 +#: boot-installer.xml:2367 #, no-c-format msgid "preseed/interactive" msgstr "" #. Tag: para -#: boot-installer.xml:2393 +#: boot-installer.xml:2368 #, 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:2405 +#: boot-installer.xml:2380 #, no-c-format msgid "auto-install/enable (auto)" msgstr "" #. Tag: para -#: boot-installer.xml:2406 +#: boot-installer.xml:2381 #, 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:2417 +#: boot-installer.xml:2392 #, no-c-format msgid "finish-install/keep-consoles" msgstr "" #. Tag: para -#: boot-installer.xml:2418 +#: boot-installer.xml:2393 #, 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:2429 +#: boot-installer.xml:2404 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:2430 +#: boot-installer.xml:2405 #, 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:2439 +#: boot-installer.xml:2414 #, 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:2450 +#: boot-installer.xml:2425 #, no-c-format msgid "base-installer/install-recommends (recommends)" msgstr "" #. Tag: para -#: boot-installer.xml:2451 +#: boot-installer.xml:2426 #, 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:2458 +#: boot-installer.xml:2433 #, 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:2470 +#: boot-installer.xml:2445 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "" #. Tag: para -#: boot-installer.xml:2471 +#: boot-installer.xml:2446 #, 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:2482 +#: boot-installer.xml:2457 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:2483 +#: boot-installer.xml:2458 #, 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:2493 +#: boot-installer.xml:2468 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:2494 +#: boot-installer.xml:2469 #, 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:2507 +#: boot-installer.xml:2482 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para -#: boot-installer.xml:2508 +#: boot-installer.xml:2483 #, 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:2520 +#: boot-installer.xml:2495 #, no-c-format msgid "debian-installer/language (language)" msgstr "" #. Tag: term -#: boot-installer.xml:2521 +#: boot-installer.xml:2496 #, no-c-format msgid "debian-installer/country (country)" msgstr "" #. Tag: term -#: boot-installer.xml:2522 +#: boot-installer.xml:2497 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:2523 +#: boot-installer.xml:2498 #, 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:2528 +#: boot-installer.xml:2503 #, 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:2537 +#: boot-installer.xml:2512 #, 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:2549 +#: boot-installer.xml:2524 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:2550 +#: boot-installer.xml:2525 #, 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:2564 +#: boot-installer.xml:2539 #, 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:2573 +#: boot-installer.xml:2548 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:2574 +#: boot-installer.xml:2549 #, 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:2587 +#: boot-installer.xml:2562 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para -#: boot-installer.xml:2588 +#: boot-installer.xml:2563 #, 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:2602 +#: boot-installer.xml:2577 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2603 +#: boot-installer.xml:2578 #, 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:2616 +#: boot-installer.xml:2591 #, 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:2623 +#: boot-installer.xml:2598 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -1866,127 +1836,127 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2633 +#: boot-installer.xml:2608 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:2639 +#: boot-installer.xml:2614 #, no-c-format msgid "Blacklisting kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2640 +#: boot-installer.xml:2615 #, 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:2649 +#: boot-installer.xml:2624 #, 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:2657 +#: boot-installer.xml:2632 #, 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:2673 +#: boot-installer.xml:2648 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:2678 +#: boot-installer.xml:2653 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:2679 +#: boot-installer.xml:2654 #, 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:2686 +#: boot-installer.xml:2661 #, 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:2692 +#: boot-installer.xml:2667 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:2697 +#: boot-installer.xml:2672 #, 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:2703 +#: boot-installer.xml:2678 #, 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:2713 +#: boot-installer.xml:2688 #, 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:2719 +#: boot-installer.xml:2694 #, 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:2727 +#: boot-installer.xml:2702 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:2730 +#: boot-installer.xml:2705 #, 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:2747 +#: boot-installer.xml:2722 #, 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:2758 +#: boot-installer.xml:2733 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:2759 +#: boot-installer.xml:2734 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:2764 +#: boot-installer.xml:2739 #, 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:2771 +#: boot-installer.xml:2746 #, 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" @@ -1996,7 +1966,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2784 +#: boot-installer.xml:2759 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -2009,19 +1979,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2789 +#: boot-installer.xml:2764 #, 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:2801 +#: boot-installer.xml:2776 #, 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:2808 +#: boot-installer.xml:2783 #, 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" @@ -2034,13 +2004,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2822 +#: boot-installer.xml:2797 #, 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:2830 +#: boot-installer.xml:2805 #, 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" @@ -2049,7 +2019,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2840 +#: boot-installer.xml:2815 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -2062,151 +2032,151 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2855 +#: boot-installer.xml:2830 #, 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:2870 +#: boot-installer.xml:2845 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:2872 +#: boot-installer.xml:2847 #, 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:2877 +#: boot-installer.xml:2852 #, 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:2886 +#: boot-installer.xml:2861 #, 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:2895 +#: boot-installer.xml:2870 #, 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:2901 +#: boot-installer.xml:2876 #, 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:2907 +#: boot-installer.xml:2882 #, 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:2916 +#: boot-installer.xml:2891 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:2918 +#: boot-installer.xml:2893 #, 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:2927 +#: boot-installer.xml:2902 #, 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:2938 +#: boot-installer.xml:2913 #, 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:2949 +#: boot-installer.xml:2924 #, no-c-format msgid "dmesg" msgstr "" #. Tag: userinput -#: boot-installer.xml:2951 +#: boot-installer.xml:2926 #, no-c-format msgid "lspci" msgstr "" #. Tag: userinput -#: boot-installer.xml:2953 +#: boot-installer.xml:2928 #, no-c-format msgid "lsmod" msgstr "" #. Tag: userinput -#: boot-installer.xml:2955 +#: boot-installer.xml:2930 #, no-c-format msgid "amixer" msgstr "" #. Tag: title -#: boot-installer.xml:2963 boot-installer.xml:3074 +#: boot-installer.xml:2938 boot-installer.xml:3049 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:2964 +#: boot-installer.xml:2939 #, 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:3015 +#: boot-installer.xml:2990 #, 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:3029 +#: boot-installer.xml:3004 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:3030 +#: boot-installer.xml:3005 #, 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:3040 +#: boot-installer.xml:3015 #, 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:3075 +#: boot-installer.xml:3050 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:3081 +#: boot-installer.xml:3056 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:3082 +#: boot-installer.xml:3057 #, 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" @@ -2216,85 +2186,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3096 +#: boot-installer.xml:3071 #, 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:3107 +#: boot-installer.xml:3082 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3108 +#: boot-installer.xml:3083 #, 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:3114 +#: boot-installer.xml:3089 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3123 +#: boot-installer.xml:3098 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3125 +#: boot-installer.xml:3100 #, 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:3150 +#: boot-installer.xml:3125 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3151 +#: boot-installer.xml:3126 #, 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:3162 +#: boot-installer.xml:3137 #, 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:3173 +#: boot-installer.xml:3148 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3174 +#: boot-installer.xml:3149 #, 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:3181 +#: boot-installer.xml:3156 #, 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:3187 +#: boot-installer.xml:3162 #, 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:3197 +#: boot-installer.xml:3172 #, 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 e56c2f178..ed8d2658a 100644 --- a/po/pot/boot-new.pot +++ b/po/pot/boot-new.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-05-22 19:06+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title diff --git a/po/pot/gpl.pot b/po/pot/gpl.pot index a217b2f70..9c1bf54cf 100644 --- a/po/pot/gpl.pot +++ b/po/pot/gpl.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-04-16 19:15+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index 8514ff317..065e33979 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-05-22 19:06+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title @@ -57,13 +57,13 @@ msgid "&debian; GNU/Linux &release; supports eleven major architectures and seve msgstr "" #. Tag: entry -#: hardware.xml:53 hardware.xml:180 +#: hardware.xml:53 hardware.xml:178 #, no-c-format msgid "Architecture" msgstr "" #. Tag: entry -#: hardware.xml:53 hardware.xml:180 +#: hardware.xml:53 hardware.xml:178 #, no-c-format msgid "&debian; Designation" msgstr "" @@ -81,7 +81,7 @@ msgid "Flavor" msgstr "" #. Tag: entry -#: hardware.xml:60 hardware.xml:186 +#: hardware.xml:60 hardware.xml:184 #, no-c-format msgid "Intel x86-based" msgstr "" @@ -93,7 +93,7 @@ msgid "i386" msgstr "" #. Tag: entry -#: hardware.xml:67 hardware.xml:191 +#: hardware.xml:67 hardware.xml:189 #, no-c-format msgid "AMD64 & Intel 64" msgstr "" @@ -249,25 +249,25 @@ msgid "r5k-ip32" msgstr "" #. Tag: entry -#: hardware.xml:115 hardware.xml:128 +#: hardware.xml:115 hardware.xml:126 #, no-c-format msgid "MIPS Malta (32 bit)" msgstr "" #. Tag: entry -#: hardware.xml:116 hardware.xml:129 +#: hardware.xml:116 hardware.xml:127 #, no-c-format msgid "4kc-malta" msgstr "" #. Tag: entry -#: hardware.xml:118 hardware.xml:131 +#: hardware.xml:118 hardware.xml:129 #, no-c-format msgid "MIPS Malta (64 bit)" msgstr "" #. Tag: entry -#: hardware.xml:119 hardware.xml:132 +#: hardware.xml:119 hardware.xml:130 #, no-c-format msgid "5kc-malta" msgstr "" @@ -285,1567 +285,1525 @@ msgid "mipsel" msgstr "" #. Tag: entry -#: hardware.xml:125 -#, no-c-format -msgid "Cobalt" -msgstr "" - -#. Tag: entry -#: hardware.xml:126 -#, no-c-format -msgid "cobalt" -msgstr "" - -#. Tag: entry -#: hardware.xml:136 +#: hardware.xml:134 #, no-c-format msgid "IBM/Motorola PowerPC" msgstr "" #. Tag: entry -#: hardware.xml:137 +#: hardware.xml:135 #, no-c-format -msgid "<entry>powerpc</entry>" +msgid "<entry morerows=\"1\">powerpc</entry>" msgstr "" #. Tag: entry -#: hardware.xml:138 +#: hardware.xml:136 #, no-c-format msgid "PowerMac" msgstr "" #. Tag: entry -#: hardware.xml:139 +#: hardware.xml:137 #, no-c-format msgid "pmac" msgstr "" #. Tag: entry -#: hardware.xml:141 +#: hardware.xml:139 #, no-c-format msgid "PReP" msgstr "" #. Tag: entry -#: hardware.xml:142 +#: hardware.xml:140 #, no-c-format msgid "prep" msgstr "" #. Tag: entry -#: hardware.xml:146 +#: hardware.xml:144 #, no-c-format msgid "Sun SPARC" msgstr "" #. Tag: entry -#: hardware.xml:147 +#: hardware.xml:145 #, no-c-format msgid "sparc" msgstr "" #. Tag: entry -#: hardware.xml:148 +#: hardware.xml:146 #, no-c-format msgid "<entry>sun4u</entry>" msgstr "" #. Tag: entry -#: hardware.xml:149 +#: hardware.xml:147 #, no-c-format msgid "sparc64" msgstr "" #. Tag: entry -#: hardware.xml:151 +#: hardware.xml:149 #, no-c-format msgid "<entry>sun4v</entry>" msgstr "" #. Tag: entry -#: hardware.xml:155 +#: hardware.xml:153 #, no-c-format msgid "IBM S/390" msgstr "" #. Tag: entry -#: hardware.xml:156 +#: hardware.xml:154 #, no-c-format msgid "s390" msgstr "" #. Tag: entry -#: hardware.xml:157 hardware.xml:164 +#: hardware.xml:155 hardware.xml:162 #, no-c-format msgid "IPL from VM-reader and DASD" msgstr "" #. Tag: entry -#: hardware.xml:158 hardware.xml:165 +#: hardware.xml:156 hardware.xml:163 #, no-c-format msgid "generic" msgstr "" #. Tag: entry -#: hardware.xml:162 +#: hardware.xml:160 #, no-c-format msgid "64bit IBM S/390" msgstr "" #. Tag: entry -#: hardware.xml:163 +#: hardware.xml:161 #, no-c-format msgid "s390x" msgstr "" #. Tag: para -#: hardware.xml:170 +#: hardware.xml:168 #, no-c-format msgid "&debian; GNU/kFreeBSD &release; supports two architectures." msgstr "" #. Tag: entry -#: hardware.xml:187 +#: hardware.xml:185 #, no-c-format msgid "kfreebsd-i386" msgstr "" #. Tag: entry -#: hardware.xml:192 +#: hardware.xml:190 #, no-c-format msgid "kfreebsd-amd64" msgstr "" #. Tag: para -#: hardware.xml:197 +#: hardware.xml:195 #, 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:207 +#: hardware.xml:205 #, 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:217 +#: hardware.xml:215 #, 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:239 +#: hardware.xml:237 #, no-c-format msgid "CPU Support" msgstr "" #. Tag: para -#: hardware.xml:240 +#: hardware.xml:238 #, no-c-format msgid "Both AMD64 and Intel 64 processors are supported." msgstr "" #. Tag: title -#: hardware.xml:265 hardware.xml:356 hardware.xml:375 hardware.xml:458 hardware.xml:516 hardware.xml:569 +#: hardware.xml:263 hardware.xml:354 hardware.xml:373 hardware.xml:456 hardware.xml:514 hardware.xml:544 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para -#: hardware.xml:267 +#: hardware.xml:265 #, no-c-format msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard &debian; distribution only supports installation on a number of the most common platforms. The &debian; userland however may be used by <emphasis>any</emphasis> ARM CPU." msgstr "" #. Tag: para -#: hardware.xml:276 +#: hardware.xml:274 #, no-c-format msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. &debian; currently only supports little-endian ARM systems." msgstr "" #. Tag: para -#: hardware.xml:284 +#: hardware.xml:282 #, no-c-format msgid "The supported platforms are:" msgstr "" #. Tag: term -#: hardware.xml:291 +#: hardware.xml:289 #, no-c-format msgid "IOP32x" msgstr "" #. Tag: para -#: hardware.xml:292 +#: hardware.xml:290 #, no-c-format msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. &debian; currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. &debian; explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>." msgstr "" #. Tag: term -#: hardware.xml:305 +#: hardware.xml:303 #, no-c-format msgid "Kirkwood" msgstr "" #. Tag: para -#: hardware.xml:306 +#: hardware.xml:304 #, 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:322 +#: hardware.xml:320 #, no-c-format msgid "Orion5x" msgstr "" #. Tag: para -#: hardware.xml:323 +#: hardware.xml:321 #, 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:337 +#: hardware.xml:335 #, no-c-format msgid "<term>Versatile</term>" msgstr "" #. Tag: para -#: hardware.xml:338 +#: hardware.xml:336 #, no-c-format msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run &debian; on ARM if you don't have the hardware." msgstr "" #. Tag: para -#: hardware.xml:357 +#: hardware.xml:355 #, no-c-format msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future." msgstr "" #. Tag: para -#: hardware.xml:376 +#: hardware.xml:374 #, 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:384 hardware.xml:493 +#: hardware.xml:382 hardware.xml:491 #, no-c-format msgid "<title>CPU</title>" msgstr "" #. Tag: para -#: hardware.xml:385 +#: hardware.xml:383 #, 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:392 +#: hardware.xml:390 #, no-c-format msgid "However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of &debian;<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run &debian; GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many &debian; packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most &debian; packages; now they can. </para> </footnote>." msgstr "" #. Tag: para -#: hardware.xml:425 +#: hardware.xml:423 #, 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:434 +#: hardware.xml:432 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:435 +#: hardware.xml:433 #, 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:459 +#: hardware.xml:457 #, 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:494 +#: hardware.xml:492 #, 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:500 +#: hardware.xml:498 #, 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:517 -#, no-c-format -msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." -msgstr "" - -#. Tag: title -#: hardware.xml:545 -#, no-c-format -msgid "CPU/Machine types" -msgstr "" - -#. Tag: para -#: hardware.xml:547 -#, no-c-format -msgid "All MIPS based Cobalt machines are supported with the exception of the Qube 2700 (Qube 1)." -msgstr "" - -#. Tag: title -#: hardware.xml:555 -#, no-c-format -msgid "Supported console options" -msgstr "" - -#. Tag: para -#: hardware.xml:556 +#: hardware.xml:515 #, no-c-format -msgid "Cobalt machines use 115200 bps." +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:570 +#: hardware.xml:545 #, 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:591 +#: hardware.xml:566 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:593 +#: hardware.xml:568 #, no-c-format msgid "There are two flavours of the powerpc kernel in &debian;, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:600 +#: hardware.xml:575 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:601 +#: hardware.xml:576 #, 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:611 +#: hardware.xml:586 #, no-c-format msgid "powerpc-smp" msgstr "" #. Tag: para -#: hardware.xml:612 +#: hardware.xml:587 #, no-c-format msgid "All Apple PowerMac G4 SMP machines." msgstr "" #. Tag: term -#: hardware.xml:620 +#: hardware.xml:595 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:621 +#: hardware.xml:596 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:625 +#: hardware.xml:600 #, 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:631 +#: hardware.xml:606 #, 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:636 +#: hardware.xml:611 #, 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:642 +#: hardware.xml:617 #, no-c-format msgid "Newer IBM systems using POWER5, POWER6, and POWER7 processors." msgstr "" #. Tag: title -#: hardware.xml:675 +#: hardware.xml:650 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:677 +#: hardware.xml:652 #, 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:684 +#: hardware.xml:659 #, 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:692 +#: hardware.xml:667 #, 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:700 +#: hardware.xml:675 #, 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:716 hardware.xml:851 hardware.xml:895 hardware.xml:928 +#: hardware.xml:691 hardware.xml:826 hardware.xml:870 hardware.xml:903 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:717 +#: hardware.xml:692 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:723 +#: hardware.xml:698 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:724 +#: hardware.xml:699 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:725 hardware.xml:728 hardware.xml:731 hardware.xml:734 hardware.xml:737 hardware.xml:740 hardware.xml:743 hardware.xml:746 hardware.xml:749 hardware.xml:752 hardware.xml:755 hardware.xml:758 hardware.xml:761 hardware.xml:764 hardware.xml:767 hardware.xml:770 +#: hardware.xml:700 hardware.xml:703 hardware.xml:706 hardware.xml:709 hardware.xml:712 hardware.xml:715 hardware.xml:718 hardware.xml:721 hardware.xml:724 hardware.xml:727 hardware.xml:730 hardware.xml:733 hardware.xml:736 hardware.xml:739 hardware.xml:742 hardware.xml:745 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:727 +#: hardware.xml:702 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:730 +#: hardware.xml:705 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:733 +#: hardware.xml:708 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:736 +#: hardware.xml:711 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:739 +#: hardware.xml:714 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:742 +#: hardware.xml:717 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:745 +#: hardware.xml:720 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:748 +#: hardware.xml:723 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:751 +#: hardware.xml:726 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:754 +#: hardware.xml:729 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:757 +#: hardware.xml:732 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:760 +#: hardware.xml:735 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:763 +#: hardware.xml:738 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:766 +#: hardware.xml:741 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:769 +#: hardware.xml:744 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:772 +#: hardware.xml:747 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:773 hardware.xml:776 hardware.xml:779 hardware.xml:782 hardware.xml:785 hardware.xml:788 hardware.xml:791 hardware.xml:794 hardware.xml:797 hardware.xml:800 hardware.xml:803 hardware.xml:806 hardware.xml:812 hardware.xml:815 hardware.xml:821 hardware.xml:827 hardware.xml:833 +#: hardware.xml:748 hardware.xml:751 hardware.xml:754 hardware.xml:757 hardware.xml:760 hardware.xml:763 hardware.xml:766 hardware.xml:769 hardware.xml:772 hardware.xml:775 hardware.xml:778 hardware.xml:781 hardware.xml:787 hardware.xml:790 hardware.xml:796 hardware.xml:802 hardware.xml:808 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:775 +#: hardware.xml:750 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:778 +#: hardware.xml:753 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:781 +#: hardware.xml:756 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:784 +#: hardware.xml:759 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:787 +#: hardware.xml:762 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:790 +#: hardware.xml:765 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:793 +#: hardware.xml:768 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:796 +#: hardware.xml:771 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:799 +#: hardware.xml:774 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:802 +#: hardware.xml:777 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:805 +#: hardware.xml:780 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:810 +#: hardware.xml:785 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:811 +#: hardware.xml:786 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:814 +#: hardware.xml:789 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:819 +#: hardware.xml:794 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:820 +#: hardware.xml:795 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:825 +#: hardware.xml:800 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:826 +#: hardware.xml:801 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:831 hardware.xml:857 +#: hardware.xml:806 hardware.xml:832 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:832 +#: hardware.xml:807 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:841 +#: hardware.xml:816 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:858 +#: hardware.xml:833 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:860 +#: hardware.xml:835 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:862 +#: hardware.xml:837 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:864 +#: hardware.xml:839 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:866 +#: hardware.xml:841 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:870 hardware.xml:901 +#: hardware.xml:845 hardware.xml:876 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:871 +#: hardware.xml:846 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:873 +#: hardware.xml:848 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:875 +#: hardware.xml:850 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:877 +#: hardware.xml:852 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:885 +#: hardware.xml:860 #, no-c-format msgid "CHRP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:902 +#: hardware.xml:877 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:905 +#: hardware.xml:880 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:906 +#: hardware.xml:881 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: entry -#: hardware.xml:909 +#: hardware.xml:884 #, no-c-format msgid "Fixstars" msgstr "" #. Tag: entry -#: hardware.xml:910 +#: hardware.xml:885 #, no-c-format msgid "YDL PowerStation" msgstr "" #. Tag: title -#: hardware.xml:918 +#: hardware.xml:893 #, no-c-format msgid "APUS subarchitecture (unsupported)" msgstr "" #. Tag: entry -#: hardware.xml:934 +#: hardware.xml:909 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:935 +#: hardware.xml:910 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:943 +#: hardware.xml:918 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:945 +#: hardware.xml:920 #, 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:982 +#: hardware.xml:957 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:984 +#: hardware.xml:959 #, 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:993 +#: hardware.xml:968 #, 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:1001 +#: hardware.xml:976 #, 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:1017 +#: hardware.xml:992 #, no-c-format msgid "zSeries and System z machine types" msgstr "" #. Tag: para -#: hardware.xml:1018 +#: hardware.xml:993 #, 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:1035 +#: hardware.xml:1010 #, no-c-format msgid "PAV and HyperPAV" msgstr "" #. Tag: para -#: hardware.xml:1036 +#: hardware.xml:1011 #, 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:1052 +#: hardware.xml:1027 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para -#: hardware.xml:1053 +#: hardware.xml:1028 #, 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:1064 +#: hardware.xml:1039 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "" #. Tag: para -#: hardware.xml:1066 +#: hardware.xml:1041 #, 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:1073 +#: hardware.xml:1048 #, 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:1083 +#: hardware.xml:1058 #, no-c-format msgid "<term>sun4u</term>" msgstr "" #. Tag: para -#: hardware.xml:1085 +#: hardware.xml:1060 #, 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:1098 +#: hardware.xml:1073 #, no-c-format msgid "<term>sun4v</term>" msgstr "" #. Tag: para -#: hardware.xml:1100 +#: hardware.xml:1075 #, 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:1111 +#: hardware.xml:1086 #, 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:1120 +#: hardware.xml:1095 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1121 +#: hardware.xml:1096 #, 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:1138 hardware.xml:1158 hardware.xml:1186 hardware.xml:1209 +#: hardware.xml:1113 hardware.xml:1133 hardware.xml:1161 hardware.xml:1184 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1139 +#: hardware.xml:1114 #, 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 quite common in recent years even for rather low-end desktop computers and laptops 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:1149 +#: hardware.xml:1124 #, 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:1160 +#: hardware.xml:1135 #, 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:1169 +#: hardware.xml:1144 #, no-c-format msgid "Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops 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:1177 +#: hardware.xml:1152 #, no-c-format msgid "The 486 flavour of the &debian; kernel image packages for &arch-title; is not compiled with SMP support." msgstr "" #. Tag: para -#: hardware.xml:1187 +#: hardware.xml:1162 #, 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:1196 +#: hardware.xml:1171 #, 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:1210 +#: hardware.xml:1185 #, 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:1220 +#: hardware.xml:1195 #, 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:1226 +#: hardware.xml:1201 #, 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:1237 +#: hardware.xml:1212 #, no-c-format msgid "Graphics Card Support" msgstr "" #. Tag: para -#: hardware.xml:1238 +#: hardware.xml:1213 #, 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:1251 +#: hardware.xml:1226 #, 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:1256 +#: hardware.xml:1231 #, 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:1261 +#: hardware.xml:1236 #, 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:1271 +#: hardware.xml:1246 #, 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:1293 +#: hardware.xml:1268 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:1294 +#: hardware.xml:1269 #, 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:1304 +#: hardware.xml:1279 #, 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:1310 +#: hardware.xml:1285 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:1315 +#: hardware.xml:1290 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:1320 +#: hardware.xml:1295 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:1325 +#: hardware.xml:1300 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:1330 +#: hardware.xml:1305 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:1337 +#: hardware.xml:1312 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:1342 +#: hardware.xml:1317 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:1347 +#: hardware.xml:1322 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:1352 +#: hardware.xml:1327 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:1361 +#: hardware.xml:1336 #, 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:1366 +#: hardware.xml:1341 #, no-c-format msgid "ISDN is supported, but not during the installation." msgstr "" #. Tag: title -#: hardware.xml:1373 +#: hardware.xml:1348 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:1374 +#: hardware.xml:1349 #, 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:1381 +#: hardware.xml:1356 #, 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:1386 +#: hardware.xml:1361 #, 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:1391 +#: hardware.xml:1366 #, 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:1401 +#: hardware.xml:1376 #, 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:1415 +#: hardware.xml:1390 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:1416 +#: hardware.xml:1391 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:1423 +#: hardware.xml:1398 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:1425 +#: hardware.xml:1400 #, 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:1435 +#: hardware.xml:1410 #, 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:1443 +#: hardware.xml:1418 #, 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:1456 +#: hardware.xml:1431 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:1458 +#: hardware.xml:1433 #, no-c-format msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." msgstr "" #. Tag: title -#: hardware.xml:1473 +#: hardware.xml:1448 #, no-c-format msgid "Braille Displays" msgstr "" #. Tag: para -#: hardware.xml:1474 +#: hardware.xml:1449 #, 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:1488 +#: hardware.xml:1463 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: hardware.xml:1489 +#: hardware.xml:1464 #, 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:1509 +#: hardware.xml:1484 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:1510 +#: hardware.xml:1485 #, no-c-format msgid "&arch-kernel; supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system." msgstr "" #. Tag: para -#: hardware.xml:1516 +#: hardware.xml:1491 #, 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:1525 +#: hardware.xml:1500 #, no-c-format msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP." msgstr "" -#. Tag: para -#: hardware.xml:1531 -#, no-c-format -msgid "The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." -msgstr "" - #. Tag: title -#: hardware.xml:1543 +#: hardware.xml:1513 #, no-c-format msgid "Devices Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:1544 +#: hardware.xml:1514 #, 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:1555 +#: hardware.xml:1525 #, 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:1563 +#: hardware.xml:1533 #, 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:1572 +#: hardware.xml:1542 #, 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:1581 +#: hardware.xml:1551 #, 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:1598 +#: hardware.xml:1568 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;" msgstr "" #. Tag: para -#: hardware.xml:1600 +#: hardware.xml:1570 #, 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:1608 +#: hardware.xml:1578 #, 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:1616 +#: hardware.xml:1586 #, 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:1627 +#: hardware.xml:1597 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:1628 +#: hardware.xml:1598 #, 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:1638 +#: hardware.xml:1608 #, 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:1650 +#: hardware.xml:1620 #, 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:1661 +#: hardware.xml:1631 #, 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:1674 +#: hardware.xml:1644 #, 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:1689 +#: hardware.xml:1659 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:1691 +#: hardware.xml:1661 #, 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:1701 +#: hardware.xml:1671 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:1702 +#: hardware.xml:1672 #, 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:1708 +#: hardware.xml:1678 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:1715 +#: hardware.xml:1685 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:1717 +#: hardware.xml:1687 #, 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." msgstr "" #. Tag: para -#: hardware.xml:1723 +#: hardware.xml:1693 #, no-c-format msgid "CD-ROM based installation is supported for most architectures." msgstr "" #. Tag: para -#: hardware.xml:1727 +#: hardware.xml:1697 #, no-c-format msgid "On PCs SATA, IDE/ATAPI and SCSI CD-ROMs are supported." msgstr "" #. Tag: para -#: hardware.xml:1731 +#: hardware.xml:1701 #, 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:1736 +#: hardware.xml:1706 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines." msgstr "" #. Tag: para -#: hardware.xml:1740 +#: hardware.xml:1710 #, 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:1754 +#: hardware.xml:1724 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:1756 +#: hardware.xml:1726 #, 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." msgstr "" #. Tag: title -#: hardware.xml:1768 +#: hardware.xml:1738 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:1770 +#: hardware.xml:1740 #, no-c-format msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP." msgstr "" #. Tag: para -#: hardware.xml:1780 +#: hardware.xml:1750 #, 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:1793 +#: hardware.xml:1763 #, 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:1802 +#: hardware.xml:1772 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:1804 +#: hardware.xml:1774 #, 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:1811 +#: hardware.xml:1781 #, 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:1820 +#: hardware.xml:1790 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:1822 +#: hardware.xml:1792 #, 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:1835 +#: hardware.xml:1805 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:1837 +#: hardware.xml:1807 #, 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:1841 +#: hardware.xml:1811 #, 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:1858 +#: hardware.xml:1828 #, 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:1891 +#: hardware.xml:1861 #, 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:1897 +#: hardware.xml:1867 #, 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:1903 +#: hardware.xml:1873 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:1908 +#: hardware.xml:1878 #, 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:1925 +#: hardware.xml:1895 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:1927 +#: hardware.xml:1897 #, 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:1934 +#: hardware.xml:1904 #, no-c-format msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users." msgstr "" diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot index 79909c870..307ec4ca1 100644 --- a/po/pot/install-methods.pot +++ b/po/pot/install-methods.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-05-22 19:06+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title diff --git a/po/pot/installation-howto.pot b/po/pot/installation-howto.pot index 63578487d..09a63eac5 100644 --- a/po/pot/installation-howto.pot +++ b/po/pot/installation-howto.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-04-16 19:15+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title diff --git a/po/pot/partitioning.pot b/po/pot/partitioning.pot index 67ce2b0d3..c88e1168c 100644 --- a/po/pot/partitioning.pot +++ b/po/pot/partitioning.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-05-22 19:06+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title @@ -500,24 +500,12 @@ msgstr "" 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: command -#: partitioning.xml:451 -#, no-c-format -msgid "partman" -msgstr "" - #. Tag: para #: partitioning.xml:452 #, 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: command -#: partitioning.xml:463 -#, no-c-format -msgid "fdisk" -msgstr "" - #. Tag: para #: partitioning.xml:464 #, no-c-format @@ -530,12 +518,6 @@ msgstr "" 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: command -#: partitioning.xml:480 -#, no-c-format -msgid "cfdisk" -msgstr "" - #. Tag: para #: partitioning.xml:481 #, no-c-format @@ -548,60 +530,30 @@ msgstr "" msgid "Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result." msgstr "" -#. Tag: command -#: partitioning.xml:494 -#, no-c-format -msgid "atari-fdisk" -msgstr "" - #. Tag: para #: partitioning.xml:495 #, no-c-format msgid "Atari-aware version of <command>fdisk</command>." msgstr "" -#. Tag: command -#: partitioning.xml:503 -#, no-c-format -msgid "amiga-fdisk" -msgstr "" - #. Tag: para #: partitioning.xml:504 #, no-c-format msgid "Amiga-aware version of <command>fdisk</command>." msgstr "" -#. Tag: command -#: partitioning.xml:512 -#, no-c-format -msgid "mac-fdisk" -msgstr "" - #. Tag: para #: partitioning.xml:513 #, no-c-format msgid "Mac-aware version of <command>fdisk</command>." msgstr "" -#. Tag: command -#: partitioning.xml:521 -#, no-c-format -msgid "pmac-fdisk" -msgstr "" - #. Tag: para #: partitioning.xml:522 #, no-c-format msgid "PowerMac-aware version of <command>fdisk</command>, also used by BVM and Motorola VMEbus systems." msgstr "" -#. Tag: command -#: partitioning.xml:531 -#, no-c-format -msgid "fdasd" -msgstr "" - #. Tag: para #: partitioning.xml:532 #, no-c-format diff --git a/po/pot/post-install.pot b/po/pot/post-install.pot index a7ddf3c8e..81dee7174 100644 --- a/po/pot/post-install.pot +++ b/po/pot/post-install.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-04-16 19:15+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title diff --git a/po/pot/preface.pot b/po/pot/preface.pot index 2a9693f67..335f04b88 100644 --- a/po/pot/preface.pot +++ b/po/pot/preface.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-04-16 19:15+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot index aaa77d2ed..567e5acb6 100644 --- a/po/pot/preparing.pot +++ b/po/pot/preparing.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-05-27 08:42+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot index 5ca3765bd..d04c8d767 100644 --- a/po/pot/preseed.pot +++ b/po/pot/preseed.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-05-22 19:06+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title @@ -99,7 +99,7 @@ msgid "CD/DVD" msgstr "" #. Tag: entry -#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91 preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100 preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109 preseed.xml:111 +#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91 preseed.xml:94 preseed.xml:95 preseed.xml:99 preseed.xml:100 preseed.xml:104 preseed.xml:106 preseed.xml:109 preseed.xml:111 #, no-c-format msgid "<entry>yes</entry>" msgstr "" @@ -129,6 +129,12 @@ msgid "hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase msgstr "" #. Tag: entry +#: preseed.xml:96 preseed.xml:101 +#, no-c-format +msgid "yes<footnoteref linkend=\"apx-ps-net\"/>" +msgstr "" + +#. Tag: entry #: preseed.xml:98 #, no-c-format msgid "floppy based (cd-drivers)" diff --git a/po/pot/random-bits.pot b/po/pot/random-bits.pot index eacef1a11..9c842fefc 100644 --- a/po/pot/random-bits.pot +++ b/po/pot/random-bits.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-04-16 19:15+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title @@ -863,68 +863,65 @@ msgstr "" msgid "" "Now you've got a real &debian; system, though rather lean, on disk. <command>chroot</command> into it: <informalexample><screen>\n" "# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash\n" - "</screen></informalexample> After chrooting you may need to set the terminal definition to be compatible with the &debian; base system, for example:" -msgstr "" - -#. Tag: screen -#: random-bits.xml:550 -#, no-c-format -msgid "# export TERM=<replaceable>xterm-color</replaceable>" + "</screen></informalexample> After chrooting you may need to set the terminal definition to be compatible with the &debian; base system, for example: <informalexample><screen>\n" + "# export TERM=<replaceable>xterm-color</replaceable>\n" + "</screen></informalexample> Depending on the value of TERM, you may have to install the <classname>ncurses-term</classname> package to get support for it." msgstr "" #. Tag: title -#: random-bits.xml:555 +#: random-bits.xml:558 #, no-c-format msgid "Create device files" msgstr "" #. Tag: para -#: random-bits.xml:556 +#: random-bits.xml:559 #, 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:566 +#: random-bits.xml:569 #, no-c-format msgid "A few of the available options are:" msgstr "" #. Tag: para -#: random-bits.xml:571 +#: random-bits.xml:574 #, 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:575 +#: random-bits.xml:578 #, no-c-format msgid "" "# apt-get install makedev\n" + "# mount none /proc -t proc\n" "# cd /dev\n" "# MAKEDEV generic" msgstr "" #. Tag: para -#: random-bits.xml:578 +#: random-bits.xml:581 #, no-c-format msgid "manually create only specific device files using <command>MAKEDEV</command>" msgstr "" #. Tag: para -#: random-bits.xml:583 +#: random-bits.xml:586 #, 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:596 +#: random-bits.xml:599 #, no-c-format msgid "Mount Partitions" msgstr "" #. Tag: para -#: random-bits.xml:597 +#: random-bits.xml:600 #, no-c-format msgid "" "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n" @@ -958,31 +955,31 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:623 +#: random-bits.xml:626 #, no-c-format msgid "# mount -t proc proc /proc" msgstr "" #. Tag: para -#: random-bits.xml:625 +#: random-bits.xml:628 #, 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:631 +#: random-bits.xml:634 #, no-c-format msgid "# mount -t proc proc /mnt/debinst/proc" msgstr "" #. Tag: title -#: random-bits.xml:637 +#: random-bits.xml:640 #, no-c-format msgid "Setting Timezone" msgstr "" #. Tag: para -#: random-bits.xml:638 +#: random-bits.xml:641 #, 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" @@ -995,19 +992,19 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:652 +#: random-bits.xml:655 #, no-c-format msgid "# dpkg-reconfigure tzdata" msgstr "" #. Tag: title -#: random-bits.xml:658 +#: random-bits.xml:661 #, no-c-format msgid "Configure Networking" msgstr "" #. Tag: para -#: random-bits.xml:659 +#: random-bits.xml:662 #, 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" @@ -1061,13 +1058,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:700 +#: random-bits.xml:703 #, no-c-format msgid "Configure Apt" msgstr "" #. Tag: para -#: random-bits.xml:701 +#: random-bits.xml:704 #, 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" @@ -1079,13 +1076,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:717 +#: random-bits.xml:720 #, no-c-format msgid "Configure Locales and Keyboard" msgstr "" #. Tag: para -#: random-bits.xml:718 +#: random-bits.xml:721 #, 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" @@ -1095,7 +1092,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:728 +#: random-bits.xml:731 #, no-c-format msgid "" "# aptitude install console-setup\n" @@ -1103,61 +1100,61 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:730 +#: random-bits.xml:733 #, 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:740 +#: random-bits.xml:743 #, no-c-format msgid "Install a Kernel" msgstr "" #. Tag: para -#: random-bits.xml:741 +#: random-bits.xml:744 #, 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:746 +#: random-bits.xml:749 #, no-c-format msgid "# apt-cache search &kernelpackage;" msgstr "" #. Tag: para -#: random-bits.xml:748 +#: random-bits.xml:751 #, no-c-format msgid "Then install the kernel package of your choice using its package name." msgstr "" #. Tag: screen -#: random-bits.xml:752 +#: random-bits.xml:755 #, no-c-format msgid "# aptitude install &kernelpackage;-<replaceable>arch-etc</replaceable>" msgstr "" #. Tag: title -#: random-bits.xml:758 +#: random-bits.xml:761 #, no-c-format msgid "Set up the Boot Loader" msgstr "" #. Tag: para -#: random-bits.xml:759 +#: random-bits.xml:762 #, 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:766 +#: random-bits.xml:769 #, 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:778 +#: random-bits.xml:781 #, no-c-format msgid "" "Installing and setting up <classname>grub2</classname> is as easy as: <informalexample><screen>\n" @@ -1168,19 +1165,19 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:788 +#: random-bits.xml:791 #, 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." msgstr "" #. Tag: para -#: random-bits.xml:794 +#: random-bits.xml:797 #, no-c-format msgid "Here is a basic <filename>/etc/lilo.conf</filename> as an example:" msgstr "" #. Tag: screen -#: random-bits.xml:798 +#: random-bits.xml:801 #, no-c-format msgid "" "boot=/dev/<replaceable>hda6</replaceable>\n" @@ -1194,13 +1191,13 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:800 +#: random-bits.xml:803 #, 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:810 +#: random-bits.xml:813 #, no-c-format msgid "" "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n" @@ -1216,19 +1213,19 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:823 +#: random-bits.xml:826 #, no-c-format msgid "Remote access: Installing SSH and setting a password" msgstr "" #. Tag: para -#: random-bits.xml:824 +#: random-bits.xml:827 #, 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 a password for root:" msgstr "" #. Tag: screen -#: random-bits.xml:830 +#: random-bits.xml:833 #, no-c-format msgid "" "# aptitude install ssh\n" @@ -1236,13 +1233,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:835 +#: random-bits.xml:838 #, no-c-format msgid "Finishing touches" msgstr "" #. Tag: para -#: random-bits.xml:836 +#: random-bits.xml:839 #, 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" @@ -1251,91 +1248,91 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:847 +#: random-bits.xml:850 #, 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:853 +#: random-bits.xml:856 #, no-c-format msgid "# aptitude clean" msgstr "" #. Tag: title -#: random-bits.xml:864 +#: random-bits.xml:867 #, no-c-format msgid "Installing &debian-gnu; over Parallel Line IP (PLIP)" msgstr "" #. Tag: para -#: random-bits.xml:866 +#: random-bits.xml:869 #, 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:874 +#: random-bits.xml:877 #, 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:882 +#: random-bits.xml:885 #, 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:887 +#: random-bits.xml:890 #, 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:897 +#: random-bits.xml:900 #, no-c-format msgid "Requirements" msgstr "" #. Tag: para -#: random-bits.xml:900 +#: random-bits.xml:903 #, no-c-format msgid "A target computer, called <emphasis>target</emphasis>, where &debian; will be installed." msgstr "" #. Tag: para -#: random-bits.xml:906 +#: random-bits.xml:909 #, no-c-format msgid "System installation media; see <xref linkend=\"installation-media\"/>." msgstr "" #. Tag: para -#: random-bits.xml:911 +#: random-bits.xml:914 #, 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:917 +#: random-bits.xml:920 #, 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:929 +#: random-bits.xml:932 #, no-c-format msgid "Setting up source" msgstr "" #. Tag: para -#: random-bits.xml:930 +#: random-bits.xml:933 #, 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:935 +#: random-bits.xml:938 #, no-c-format msgid "" "#!/bin/sh\n" @@ -1356,13 +1353,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:941 +#: random-bits.xml:944 #, no-c-format msgid "Installing target" msgstr "" #. Tag: para -#: random-bits.xml:942 +#: random-bits.xml:945 #, 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" @@ -1371,217 +1368,217 @@ msgid "" msgstr "" #. Tag: guimenuitem -#: random-bits.xml:961 +#: random-bits.xml:964 #, no-c-format msgid "Load installer components from CD" msgstr "" #. Tag: para -#: random-bits.xml:963 +#: random-bits.xml:966 #, 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:971 +#: random-bits.xml:974 #, no-c-format msgid "Detect network hardware" msgstr "" #. Tag: para -#: random-bits.xml:976 +#: random-bits.xml:979 #, 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:985 +#: random-bits.xml:988 #, 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:997 +#: random-bits.xml:1000 #, no-c-format msgid "Configure the network" msgstr "" #. Tag: para -#: random-bits.xml:1000 +#: random-bits.xml:1003 #, no-c-format msgid "Auto-configure network with DHCP: No" msgstr "" #. Tag: para -#: random-bits.xml:1005 +#: random-bits.xml:1008 #, no-c-format msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>" msgstr "" #. Tag: para -#: random-bits.xml:1010 +#: random-bits.xml:1013 #, no-c-format msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>" msgstr "" #. Tag: para -#: random-bits.xml:1016 +#: random-bits.xml:1019 #, 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:1035 +#: random-bits.xml:1038 #, no-c-format msgid "Installing &debian-gnu; using PPP over Ethernet (PPPoE)" msgstr "" #. Tag: para -#: random-bits.xml:1037 +#: random-bits.xml:1040 #, 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:1045 +#: random-bits.xml:1048 #, 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:1050 +#: random-bits.xml:1053 #, 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:1057 +#: random-bits.xml:1060 #, 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:1065 +#: random-bits.xml:1068 #, 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:1080 +#: random-bits.xml:1083 #, 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:1099 +#: random-bits.xml:1102 #, 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:1105 +#: random-bits.xml:1108 #, 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:1111 +#: random-bits.xml:1114 #, 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:1120 +#: random-bits.xml:1123 #, 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:1126 +#: random-bits.xml:1129 #, no-c-format msgid "At this point the installer will use the provided information to establish the PPPoE connection. If the correct information was provided, the PPPoE connection should be configured and the installer should be able to use it to connect to the Internet and retrieve packages over it (if needed). If the login information is not correct or some error appears, the installer will stop, but the configuration can be attempted again by selecting the menu entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>." msgstr "" #. Tag: title -#: random-bits.xml:1146 +#: random-bits.xml:1149 #, no-c-format msgid "The Graphical Installer" msgstr "" #. Tag: para -#: random-bits.xml:1147 +#: random-bits.xml:1150 #, no-c-format msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the regular installer as it basically uses the same programs, but with a different frontend." msgstr "" #. Tag: para -#: random-bits.xml:1155 +#: random-bits.xml:1158 #, no-c-format msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the regular <quote>newt</quote> frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen." msgstr "" #. Tag: para -#: random-bits.xml:1164 +#: random-bits.xml:1167 #, no-c-format msgid "The graphical installer is available with all CD images and with the hd-media installation method. To boot the graphical installer simply select the relevant option from the boot menu. Expert and rescue mode for the graphical installer can be selected from the <quote>Advanced options</quote> menu. The previously used boot methods <userinput>installgui</userinput>, <userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can still be used from the boot prompt which is shown after selecting the <quote>Help</quote> option in the boot menu." msgstr "" #. Tag: para -#: random-bits.xml:1175 +#: random-bits.xml:1178 #, no-c-format msgid "There is also a graphical installer image that can be netbooted. And there is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is mainly useful for testing." msgstr "" #. Tag: para -#: random-bits.xml:1188 +#: random-bits.xml:1191 #, no-c-format msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems." msgstr "" #. Tag: para -#: random-bits.xml:1202 +#: random-bits.xml:1205 #, no-c-format msgid "Just as with the regular installer it is possible to add boot parameters when starting the graphical installer." msgstr "" #. Tag: para -#: random-bits.xml:1208 +#: random-bits.xml:1211 #, no-c-format msgid "The graphical installer requires significantly more memory to run than the regular installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the regular <quote>newt</quote> frontend." msgstr "" #. Tag: para -#: random-bits.xml:1215 +#: random-bits.xml:1218 #, no-c-format msgid "If the amount of memory in your system is below &minimum-memory;, the graphical installer may fail to boot at all while booting the regular installer would still work. Using the regular installer is recommended for systems with little available memory." msgstr "" #. Tag: title -#: random-bits.xml:1225 +#: random-bits.xml:1228 #, no-c-format msgid "Using the graphical installer" msgstr "" #. Tag: para -#: random-bits.xml:1226 +#: random-bits.xml:1229 #, no-c-format msgid "As already mentioned, the graphical installer basically works the same as the regular installer and thus the rest of this manual can be used to guide you through the installation process." msgstr "" #. Tag: para -#: random-bits.xml:1232 +#: random-bits.xml:1235 #, no-c-format msgid "If you prefer using the keyboard over the mouse, there are two things you need to know. To expand a collapsed list (used for example for the selection of countries within continents), you can use the <keycap>+</keycap> and <keycap>-</keycap> keys. For questions where more than one item can be selected (e.g. task selection), you first need to tab to the &BTN-CONT; button after making your selections; hitting enter will toggle a selection, not activate &BTN-CONT;." msgstr "" #. Tag: para -#: random-bits.xml:1242 +#: random-bits.xml:1245 #, no-c-format msgid "If a dialog offers additional help information, a <guibutton>Help</guibutton> button will be displayed. The help information can be accessed either by activating the button or by pressing the <keycap>F1</keycap> key." msgstr "" #. Tag: para -#: random-bits.xml:1248 +#: random-bits.xml:1251 #, no-c-format msgid "To switch to another console, you will also need to use the <keycap>Ctrl</keycap> key, just as with the X Window System. For example, to switch to VT2 (the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</keycap> <keycap>F5</keycap> </keycombo> to switch back." msgstr "" diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index 74a62d175..4f7809b1b 100644 --- a/po/pot/using-d-i.pot +++ b/po/pot/using-d-i.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-05-22 19:06+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title diff --git a/po/pot/welcome.pot b/po/pot/welcome.pot index 4b1a04cef..54cd05f6f 100644 --- a/po/pot/welcome.pot +++ b/po/pot/welcome.pot @@ -6,12 +6,12 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2013-04-16 19:15+0000\n" +"POT-Creation-Date: 2014-01-29 10:50+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" "MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title @@ -149,7 +149,7 @@ msgstr "" #. Tag: para #: welcome.xml:194 #, no-c-format -msgid "Linus Torvalds continues to coordinate the work of several hundred developers with the help of a number of subsystem maintainers. There is an <ulink url=\"&url-kernel-org;\">official website</ulink> for the Linux kernel. More information about the <userinput>linux-kernel</userinput> mailing list can be found on the <ulink url=\"&url-linux-kernel-list-faq;\">linux-kernel mailing list FAQ</ulink>." +msgid "Linus Torvalds continues to coordinate the work of several hundred developers with the help of a number of subsystem maintainers. There is an <ulink url=\"&url-kernel-org;\">official website</ulink> for the Linux kernel. Information about the <userinput>linux-kernel</userinput> mailing list can be found on the <ulink url=\"&url-linux-kernel-list-faq;\">linux-kernel mailing list FAQ</ulink>." msgstr "" #. Tag: para |