diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 689 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 552 | ||||
| -rw-r--r-- | po/pot/install-methods.pot | 334 |
3 files changed, 837 insertions, 738 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 71c4ab8f9..e58ff023a 100644 --- a/po/pot/boot-installer.pot +++ b/po/pot/boot-installer.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2006-02-07 15:07+0000\n" +"POT-Creation-Date: 2006-03-07 20:30+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" @@ -337,7 +337,7 @@ msgstr "" msgid "As on other architectures, you should install the newest available revision of the firmware<footnote> <para> Except on Jensen, where Linux is not supported on firmware versions newer than 1.7 — see <ulink url=\"&url-jensen-howto;\"></ulink> for more information. </para> </footnote> before installing &debian;. For Alpha, firmware updates can be obtained from <ulink url=\"&url-alpha-firmware;\">Alpha Firmware Updates</ulink>." msgstr "" -#: boot-installer.xml:283 boot-installer.xml:890 boot-installer.xml:1381 boot-installer.xml:1876 boot-installer.xml:1958 boot-installer.xml:2298 boot-installer.xml:2394 +#: boot-installer.xml:283 boot-installer.xml:1007 boot-installer.xml:1498 boot-installer.xml:1993 boot-installer.xml:2075 boot-installer.xml:2164 boot-installer.xml:2508 boot-installer.xml:2604 #, no-c-format #. Tag: title msgid "Booting with TFTP" @@ -478,19 +478,19 @@ msgstr "" msgid "Booting from TFTP" msgstr "" -#: boot-installer.xml:441 boot-installer.xml:896 boot-installer.xml:1399 boot-installer.xml:1882 boot-installer.xml:2304 boot-installer.xml:2400 +#: boot-installer.xml:441 boot-installer.xml:1013 boot-installer.xml:1516 boot-installer.xml:1999 boot-installer.xml:2514 boot-installer.xml:2610 #, no-c-format #. Tag: para msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)." msgstr "" -#: boot-installer.xml:446 boot-installer.xml:901 boot-installer.xml:1404 boot-installer.xml:1887 boot-installer.xml:2309 boot-installer.xml:2405 +#: boot-installer.xml:446 boot-installer.xml:1018 boot-installer.xml:1521 boot-installer.xml:2004 boot-installer.xml:2519 boot-installer.xml:2615 #, no-c-format #. Tag: para msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server." msgstr "" -#: boot-installer.xml:451 boot-installer.xml:906 boot-installer.xml:1409 boot-installer.xml:1892 boot-installer.xml:2314 boot-installer.xml:2410 +#: boot-installer.xml:451 boot-installer.xml:1023 boot-installer.xml:1526 boot-installer.xml:2009 boot-installer.xml:2524 boot-installer.xml:2620 #, no-c-format #. Tag: para msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>." @@ -499,67 +499,55 @@ msgstr "" #: boot-installer.xml:459 #, no-c-format #. Tag: title -msgid "Booting from TFTP on NetWinder" +msgid "Booting from TFTP on Netwinder" msgstr "" -#: boot-installer.xml:461 +#: boot-installer.xml:460 #, no-c-format #. Tag: para -msgid "NetWinders have two network interfaces: The 10Mbps NE2000-compatible card is <filename>eth0</filename> and the 100Mbps Tulip card is <filename>eth1</filename>." +msgid "Netwinders have two network interfaces: A 10Mbps NE2000-compatible card (which is generally referred to as <literal>eth0</literal>) and a 100Mbps Tulip card. There may be problems loading the image via TFTP using the 100Mbps card so it is recommended that you use the 10Mbps interfaced (the one labeled with <literal>10 Base-T</literal>)." msgstr "" -#: boot-installer.xml:467 +#: boot-installer.xml:469 #, no-c-format #. Tag: para -msgid "You need NeTTrom 2.2.1 or later to boot the installation system. NeTTrom 2.3.3 is recommended: get these files from <ulink url=\"ftp://ftp.netwinder.org/pub/netwinder/firmware/\"></ulink>:" +msgid "You need NeTTrom 2.2.1 or later to boot the installation system, and version 2.3.3 is recommended. Unfortunately, firmware files are currently not available for download because of license issues. If this situation changes, you may find new images at <ulink url=\"http//www.netwinder.org/\"></ulink>." msgstr "" -#: boot-installer.xml:476 -#, no-c-format -#. Tag: filename -msgid "nettrom-2.3-3.armv4l.rpm" -msgstr "" - -#: boot-installer.xml:481 -#, no-c-format -#. Tag: filename -msgid "nettrom-2.3.3.bin" -msgstr "" - -#: boot-installer.xml:486 -#, no-c-format -#. Tag: filename -msgid "nettrom-2.3.3.bin.md5sum" -msgstr "" - -#: boot-installer.xml:491 +#: boot-installer.xml:477 #, no-c-format #. Tag: para msgid "" - "After rebooting and interrupting the boot process during the countdown, you must first configure the network either with a static address: <informalexample><screen>\n" + "When you boot your Netwinder you have to interrupt the boot process during the countdown. This allows you to set a number of firmware settings needed in order to boot the installer. First of all, start by loading the default settings: <informalexample><screen>\n" + " NeTTrom command-> load-defaults\n" + "</screen></informalexample> Furthermore, you must configure the network, either with a static address: <informalexample><screen>\n" + " NeTTrom command-> setenv netconfig_eth0 flash\n" " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" "</screen></informalexample> where 24 is the number of set bits in the netmask, or a dynamic address: <informalexample><screen>\n" - " NeTTrom command-> boot diskless\n" - "</screen></informalexample> You may also need to configure the <userinput>route1</userinput> settings if the TFTP server is not on the local subnet. The rest of the config is pretty standard (the save-all step is optional): <informalexample><screen>\n" + " NeTTrom command-> setenv netconfig_eth0 dhcp\n" + "</screen></informalexample> You may also need to configure the <userinput>route1</userinput> settings if the TFTP server is not on the local subnet. Following these settings, you have to specify the TFTP server and the location of the image. You can then store your settings to flash. <informalexample><screen>\n" " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" " NeTTrom command-> setenv kerntftpfile boot.img\n" " NeTTrom command-> save-all\n" - " NeTTrom command-> setenv netconfig_eth0 flash\n" + "</screen></informalexample> Now you have to tell the firmware that the TFTP image should be booted: <informalexample><screen>\n" " NeTTrom command-> setenv kernconfig tftp\n" " NeTTrom command-> setenv rootdev /dev/ram\n" - " NeTTrom command-> setenv cmdappend root=/dev/ram\n" - "</screen></informalexample> Only the last four of these interfere with normal disk booting, so it is safe to issue <command>save-all</command> right before them, which will store the network settings in case you need to boot from the network again. If you want to use the serial console to install your NetWinder, you also need the following setting: <informalexample><screen>\n" + "</screen></informalexample> If you use a serial console to install your Netwinder, you need to add the following setting: <informalexample><screen>\n" " NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200\n" - "</screen></informalexample> Use the <command>printenv</command> command to review your environment settings. Finally, if your <envar>cmdappend</envar> NeTTrom variable has the <option>noinitrd</option> option, you must remove it so the downloaded kernel can boot with its attached ramdisk." + "</screen></informalexample> Alternatively, for installations using a keyboard and monitor you have to set: <informalexample><screen>\n" + " NeTTrom command-> setenv cmdappend root=/dev/ram\n" + "</screen></informalexample> You can use the <command>printenv</command> command to review your environment settings. After you have verified that the settings are correct, you can load the image: <informalexample><screen>\n" + " NeTTrom command-> boot\n" + "</screen></informalexample> In case you run into any problems, a detailed HOWTO is <ulink url=\"http://www.netwinder.org/howto/Firmware-HOWTO.html\"></ulink> is available." msgstr "" -#: boot-installer.xml:527 +#: boot-installer.xml:529 #, no-c-format #. Tag: title msgid "Booting from TFTP on CATS" msgstr "" -#: boot-installer.xml:529 +#: boot-installer.xml:530 #, no-c-format #. Tag: para msgid "On CATS machines, use <command>boot de0:</command> or similar at the Cyclone prompt." @@ -571,25 +559,25 @@ msgstr "" msgid "Booting from CD-ROM" msgstr "" -#: boot-installer.xml:546 boot-installer.xml:599 boot-installer.xml:1018 boot-installer.xml:1839 boot-installer.xml:2086 boot-installer.xml:2440 +#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1135 boot-installer.xml:1956 boot-installer.xml:2296 boot-installer.xml:2650 #, no-c-format #. Tag: para 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=\"i386\"> 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 "" -#: boot-installer.xml:557 boot-installer.xml:610 boot-installer.xml:1029 boot-installer.xml:1850 boot-installer.xml:2097 boot-installer.xml:2451 +#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1146 boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:565 boot-installer.xml:618 boot-installer.xml:1037 boot-installer.xml:1858 boot-installer.xml:2105 boot-installer.xml:2459 +#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1154 boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:573 boot-installer.xml:626 boot-installer.xml:1045 boot-installer.xml:1866 boot-installer.xml:2113 boot-installer.xml:2467 +#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1162 boot-installer.xml:1983 boot-installer.xml:2323 boot-installer.xml:2677 #, no-c-format #. Tag: para msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." @@ -601,43 +589,112 @@ msgstr "" msgid "To boot a CD-ROM from the Cyclone console prompt, use the command <command>boot cd0:cats.bin</command>" msgstr "" -#: boot-installer.xml:593 boot-installer.xml:1012 boot-installer.xml:1827 boot-installer.xml:2080 boot-installer.xml:2434 +#: boot-installer.xml:589 +#, no-c-format +#. Tag: title +msgid "Booting from Firmware" +msgstr "" + +#: boot-installer.xml:595 +#, no-c-format +#. Tag: para +msgid "There is an increasing number of consumer devices that directly boot from a flash chip on the device. The installer can be written to flash so it will automatically start when you reboot your machines." +msgstr "" + +#: boot-installer.xml:601 +#, no-c-format +#. Tag: para +msgid "In many cases, changing the firmware of an embedded device voids your warranty. Sometimes you are also not able to recover your device if there are problems during the flashing process. Therefore, please take care and follow the steps precisely." +msgstr "" + +#: boot-installer.xml:612 +#, no-c-format +#. Tag: title +msgid "Booting the NSLU2" +msgstr "" + +#: boot-installer.xml:613 +#, no-c-format +#. Tag: para +msgid "There are three ways how to put the installer firmware into flash:" +msgstr "" + +#: boot-installer.xml:619 +#, no-c-format +#. Tag: title +msgid "Using the NSLU2 web interface" +msgstr "" + +#: boot-installer.xml:620 +#, no-c-format +#. Tag: para +msgid "Go to the administration section and choose the menu item <literal>Upgrade</literal>. You can then browse your disk for the installer image you have previously downloaded. Then press the <literal>Start Upgrade</literal> button, confirm, wait for a few minutes and confirm again. The system will then boot straight into the installer." +msgstr "" + +#: boot-installer.xml:631 +#, no-c-format +#. Tag: title +msgid "Via the network using Linux/Unix" +msgstr "" + +#: boot-installer.xml:632 +#, no-c-format +#. Tag: para +msgid "" + "You can use <command>upslug2</command> from any Linux or Unix machine to upgrade the machine via the network. This software is packaged for Debian. First, you have to put your NSLU2 in upgrade mode: <orderedlist> <listitem><para> Disconnect any disks and/or devices from the USB ports. </para></listitem> <listitem><para> Power off the NSLU2 </para></listitem> <listitem><para> Press and hold the reset button (accessible through the small hole on the back just above the power input). </para></listitem> <listitem><para> Press and release the power button to power on the NSLU2. </para></listitem> <listitem><para> Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset button. </para></listitem> <listitem><para> The NSLU2 ready/status LED will flash alternately red/green (there is a 1 second delay before the first green). The NSLU2 is now in upgrade mode. </para></listitem> </orderedlist> See the <ulink url=\"http://www.nslu2-linux.org/wiki/OpenSlug/UsingTheBinary\">NSLU2-Linux pages</ulink> if you have problems with this. Once your NSLU2 is in upgrade mode, you can flash the new image: <informalexample><screen>\n" + "sudo upslug2 -i di-nslu2.bin\n" + "</screen></informalexample> Note that the tool also shows the MAC address of your NSLU2, which may come in handy to configure your DHCP server. After the whole image has been written and verified, the system will automatically reboot. Make sure you connect your USB disk again now, otherwise the installer won't be able to find it." +msgstr "" + +#: boot-installer.xml:693 +#, no-c-format +#. Tag: title +msgid "Via the network using Windows" +msgstr "" + +#: boot-installer.xml:694 +#, no-c-format +#. Tag: para +msgid "There is <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmware/all_router_utility.zip\">a tool</ulink> for Windows to upgrade the firmware via the network." +msgstr "" + +#: boot-installer.xml:710 boot-installer.xml:1129 boot-installer.xml:1944 boot-installer.xml:2290 boot-installer.xml:2644 #, no-c-format #. Tag: title msgid "Booting from a CD-ROM" msgstr "" -#: boot-installer.xml:731 +#: boot-installer.xml:848 #, no-c-format #. Tag: title msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" msgstr "" -#: boot-installer.xml:734 +#: boot-installer.xml:851 #, no-c-format #. Tag: para msgid "To boot the installer from hard disk, you must first download and place the needed files as described in <xref linkend=\"boot-drive-files\"/>." msgstr "" -#: boot-installer.xml:739 +#: boot-installer.xml:856 #, no-c-format #. Tag: para msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/i386/initrd.gz</filename> file and its corresponding kernel. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care." msgstr "" -#: boot-installer.xml:747 +#: boot-installer.xml:864 #, no-c-format #. Tag: para msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD image, without needing the network." msgstr "" -#: boot-installer.xml:756 +#: boot-installer.xml:873 #, no-c-format #. Tag: para msgid "For <command>LILO</command>, you will need to configure two essential things in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to load the <filename>initrd.gz</filename> installer at boot time; </para></listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is a <filename>/etc/lilo.conf</filename> example:" msgstr "" -#: boot-installer.xml:777 +#: boot-installer.xml:894 #, no-c-format #. Tag: screen msgid "" @@ -648,13 +705,13 @@ msgid "" " append=\"ramdisk_size=12000\"" msgstr "" -#: boot-installer.xml:777 +#: boot-installer.xml:894 #, no-c-format #. Tag: para msgid "For more details, refer to the <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> and <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and reboot." msgstr "" -#: boot-installer.xml:786 +#: boot-installer.xml:903 #, no-c-format #. Tag: para msgid "" @@ -665,133 +722,133 @@ msgid "" "</screen></informalexample> and reboot." msgstr "" -#: boot-installer.xml:797 +#: boot-installer.xml:914 #, no-c-format #. Tag: para msgid "Note that the value of the <userinput>ramdisk_size</userinput> may need to be adjusted for the size of the initrd image. From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>." msgstr "" -#: boot-installer.xml:808 +#: boot-installer.xml:925 #, no-c-format #. Tag: title msgid "Booting from USB Memory Stick" msgstr "" -#: boot-installer.xml:809 +#: boot-installer.xml:926 #, no-c-format #. Tag: para msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;." msgstr "" -#: boot-installer.xml:818 +#: boot-installer.xml:935 #, no-c-format #. Tag: para msgid "In case your computer doesn't support booting from USB memory devices, you can still use a single floppy to do the initial boot and then switch to USB. Boot your system as described in <xref linkend=\"floppy-boot\"/>; the kernel on the boot floppy should detect your USB stick automatically. When it asks for the root floppy, simply press &enterkey;. You should see &d-i; starting." msgstr "" -#: boot-installer.xml:831 boot-installer.xml:1939 boot-installer.xml:2340 boot-installer.xml:2488 +#: boot-installer.xml:948 boot-installer.xml:2056 boot-installer.xml:2550 boot-installer.xml:2698 #, no-c-format #. Tag: title msgid "Booting from Floppies" msgstr "" -#: boot-installer.xml:832 boot-installer.xml:2348 +#: boot-installer.xml:949 boot-installer.xml:2558 #, no-c-format #. Tag: para msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>." msgstr "" -#: boot-installer.xml:839 +#: boot-installer.xml:956 #, no-c-format #. Tag: para msgid "To boot from the installer boot floppy, place it in the primary floppy drive, shut down the system as you normally would, then turn it back on." msgstr "" -#: boot-installer.xml:845 +#: boot-installer.xml:962 #, no-c-format #. Tag: para msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>linux root=/dev/hdc</userinput> at the boot prompt. Installation from LS-120 is only supported by 2.4 and later kernels." msgstr "" -#: boot-installer.xml:856 +#: boot-installer.xml:973 #, no-c-format #. Tag: para msgid "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not properly reset the machine, so a <quote>hard</quote> reboot is recommended. If you are installing from an existing operating system (e.g., from a DOS box) you don't have a choice. Otherwise, please do a hard reboot when booting." msgstr "" -#: boot-installer.xml:865 +#: boot-installer.xml:982 #, no-c-format #. Tag: para msgid "The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt." msgstr "" -#: boot-installer.xml:871 +#: boot-installer.xml:988 #, no-c-format #. Tag: para msgid "Once you press &enterkey;, you should see the message <computeroutput>Loading...</computeroutput>, followed by <computeroutput>Uncompressing Linux...</computeroutput>, and then a screenfull or so of information about the hardware in your system. More information on this phase of the boot process can be found below in <xref linkend=\"kernel-msgs\"/>." msgstr "" -#: boot-installer.xml:880 +#: boot-installer.xml:997 #, no-c-format #. Tag: para msgid "After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched." msgstr "" -#: boot-installer.xml:914 +#: boot-installer.xml:1031 #, no-c-format #. Tag: para msgid "There are various ways to do a TFTP boot on i386." msgstr "" -#: boot-installer.xml:920 +#: boot-installer.xml:1037 #, no-c-format #. Tag: title msgid "NIC or Motherboard that support PXE" msgstr "" -#: boot-installer.xml:921 +#: boot-installer.xml:1038 #, no-c-format #. Tag: para msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel</trademark> re-implementation of TFTP boot. If so you may be able to configure your BIOS to boot from the network." msgstr "" -#: boot-installer.xml:932 +#: boot-installer.xml:1049 #, no-c-format #. Tag: title msgid "NIC with Network BootROM" msgstr "" -#: boot-installer.xml:933 +#: boot-installer.xml:1050 #, no-c-format #. Tag: para msgid "It could be that your Network Interface Card provides TFTP boot functionality." msgstr "" -#: boot-installer.xml:938 +#: boot-installer.xml:1055 #, no-c-format #. Tag: para msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document." msgstr "" -#: boot-installer.xml:946 +#: boot-installer.xml:1063 #, no-c-format #. Tag: title msgid "Etherboot" msgstr "" -#: boot-installer.xml:947 +#: boot-installer.xml:1064 #, no-c-format #. Tag: para msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" -#: boot-installer.xml:956 +#: boot-installer.xml:1073 #, no-c-format #. Tag: title msgid "The Boot Prompt" msgstr "" -#: boot-installer.xml:957 +#: boot-installer.xml:1074 #, no-c-format #. Tag: para msgid "" @@ -800,253 +857,253 @@ msgid "" "</screen></informalexample> At the boot prompt you can either just press &enterkey; to boot the installer with default options or enter a specific boot method and, optionally, boot parameters." msgstr "" -#: boot-installer.xml:969 +#: boot-installer.xml:1086 #, no-c-format #. Tag: para msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</keycap>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>linux</userinput>) and a space before the first parameter (e.g., <userinput>linux debconf/priority=medium</userinput>)." msgstr "" -#: boot-installer.xml:978 +#: boot-installer.xml:1095 #, no-c-format #. Tag: para msgid "If you are installing the system via a remote management device that provides a text interface to the VGA console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot prompt. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA). You can blindly press F1<footnote> <para> In some cases these devices will require special escape sequences to enact this keypress, for example the IRA uses <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</keycap>. </para> </footnote> to bypass this screen and view the help text. Once you are past the splash screen and at the help text your keystrokes will be echoed at the prompt as expected. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>debian-installer/framebuffer=false</userinput> to the boot prompt, as described in the help text." msgstr "" -#: boot-installer.xml:1053 +#: boot-installer.xml:1170 #, no-c-format #. Tag: title msgid "CD Contents" msgstr "" -#: boot-installer.xml:1055 +#: boot-installer.xml:1172 #, no-c-format #. Tag: para msgid "There are three basic variations of Debian Install CDs. The <emphasis>Business Card</emphasis> CD has a minimal installation that will fit on the small form factor CD media. It requires a network connection in order to install the rest of the base installation and make a usable system. The <emphasis>Network Install</emphasis> CD has all of the packages for a base install but requires a network connection to a Debian mirror site in order to install the extra packages one would want for a complete system . The set of Debian CDs can install a complete system from the wide range of packages without needing access to the network." msgstr "" -#: boot-installer.xml:1071 +#: boot-installer.xml:1188 #, no-c-format #. Tag: para msgid "The IA-64 architecture uses the next generation Extensible Firmware Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows little about the boot device other than the partition table and Master Boot Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted disk partitions. This simplifies the often arcane process of starting a system. The system boot loader and the EFI firmware that supports it have a full filesystem to store the files necessary for booting the machine. This means that the system disk on an IA-64 system has an additional disk partition dedicated to EFI instead of the simple MBR or boot block on more conventional systems." msgstr "" -#: boot-installer.xml:1087 +#: boot-installer.xml:1204 #, no-c-format #. Tag: para msgid "The Debian Installer CD contains a small EFI partition where the <command>ELILO</command> bootloader, its configuration file, the installer's kernel, and initial filesystem (initrd) are located. The running system also contains an EFI partition where the necessary files for booting the system reside. These files are readable from the EFI Shell as described below." msgstr "" -#: boot-installer.xml:1096 +#: boot-installer.xml:1213 #, no-c-format #. Tag: para msgid "Most of the details of how <command>ELILO</command> actually loads and starts a system are transparent to the system installer. However, the installer must set up an EFI partition prior to installing the base system. Otherwise, the installation of <command>ELILO</command> will fail, rendering the system un-bootable. The EFI partition is allocated and formatted in the partitioning step of the installation prior to loading any packages on the system disk. The partitioning task also verifies that a suitable EFI partition is present before allowing the installation to proceed." msgstr "" -#: boot-installer.xml:1108 +#: boot-installer.xml:1225 #, no-c-format #. Tag: para msgid "The EFI Boot Manager is presented as the last step of the firmware initialization. It displays a menu list from which the user can select an option. Depending on the model of system and what other software has been loaded on the system, this menu may be different from one system to another. There should be at least two menu items displayed, <command>Boot Option Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. Using the first option is preferred, however, if that option is not available or the CD for some reason does not boot with it, use the second option." msgstr "" -#: boot-installer.xml:1127 +#: boot-installer.xml:1244 #, no-c-format #. Tag: title msgid "IMPORTANT" msgstr "" -#: boot-installer.xml:1128 +#: boot-installer.xml:1245 #, no-c-format #. Tag: para msgid "The EFI Boot Manager will select a default boot action, typically the first menu choice, within a pre-set number of seconds. This is indicated by a countdown at the bottom of the screen. Once the timer expires and the systems starts the default action, you may have to reboot the machine in order to continue the installation. If the default action is the EFI Shell, you can return to the Boot Manager by running <command>exit</command> at the shell prompt." msgstr "" -#: boot-installer.xml:1140 +#: boot-installer.xml:1257 #, no-c-format #. Tag: title msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "" -#: boot-installer.xml:1147 +#: boot-installer.xml:1264 #, no-c-format #. Tag: para msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes its system initialization." msgstr "" -#: boot-installer.xml:1153 +#: boot-installer.xml:1270 #, no-c-format #. Tag: para msgid "Select <command>Boot Maintenance Menu</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a new menu." msgstr "" -#: boot-installer.xml:1159 +#: boot-installer.xml:1276 #, no-c-format #. Tag: para msgid "Select <command>Boot From a File</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a list of devices probed by the firmware. You should see two menu lines containing either the label <command>Debian Inst [Acpi ...</command> or <command>Removable Media Boot</command>. If you examine the rest of the menu line, you will notice that the device and controller information should be the same." msgstr "" -#: boot-installer.xml:1170 +#: boot-installer.xml:1287 #, no-c-format #. Tag: para msgid "You can choose either of the entries that refer to the CD/DVD drive. Select your choice with the arrow keys and press <command>ENTER</command>. If you choose <command>Removable Media Boot</command> the machine will immediately start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</command> instead, it will display a directory listing of the bootable portion of the CD, requiring you to proceed to the next (additional) step." msgstr "" -#: boot-installer.xml:1181 +#: boot-installer.xml:1298 #, no-c-format #. Tag: para msgid "You will only need this step if you chose <command>Debian Inst [Acpi ...</command>. The directory listing will also show <command>[Treat like Removable Media Boot]</command> on the next to the last line. Select this line with the arrow keys and press <command>ENTER</command>. This will start the boot load sequence." msgstr "" -#: boot-installer.xml:1193 +#: boot-installer.xml:1310 #, no-c-format #. Tag: para msgid "These steps start the Debian boot loader which will display a menu page for you to select a boot kernel and options. Proceed to selecting the boot kernel and options." msgstr "" -#: boot-installer.xml:1203 +#: boot-installer.xml:1320 #, no-c-format #. Tag: title msgid "Option 2: Booting from the EFI Shell" msgstr "" -#: boot-installer.xml:1204 +#: boot-installer.xml:1321 #, no-c-format #. Tag: para msgid "If, for some reason, option 1 is not successful, reboot the machine and when the EFI Boot Manager screen appears there should be one option called <command>EFI Shell [Built-in]</command>. Boot the Debian Installer CD with the following steps:" msgstr "" -#: boot-installer.xml:1215 +#: boot-installer.xml:1332 #, no-c-format #. Tag: para msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes system initialization." msgstr "" -#: boot-installer.xml:1221 +#: boot-installer.xml:1338 #, no-c-format #. Tag: para msgid "Select <command>EFI Shell</command> from the menu with the arrow keys and press <command>ENTER</command>. The EFI Shell will scan all of the bootable devices and display them to the console before displaying its command prompt. The recognized bootable partitions on devices will show a device name of <filename>fs<replaceable>n</replaceable>:</filename>. All other recognized partitions will be named <filename>blk<replaceable>n</replaceable>:</filename>. If you inserted the CD just before entering the shell, this may take a few extra seconds as it initializes the CD drive." msgstr "" -#: boot-installer.xml:1235 +#: boot-installer.xml:1352 #, no-c-format #. Tag: para msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the <filename>fs0:</filename> device although other devices with bootable partitions will also show up as <filename>fs<replaceable>n</replaceable></filename>." msgstr "" -#: boot-installer.xml:1242 +#: boot-installer.xml:1359 #, no-c-format #. Tag: para msgid "Enter <command>fs<replaceable>n</replaceable>:</command> and press <command>ENTER</command> to select that device where <replaceable>n</replaceable> is the partition number for the CDROM. The shell will now display the partition number as its prompt." msgstr "" -#: boot-installer.xml:1249 +#: boot-installer.xml:1366 #, no-c-format #. Tag: para msgid "Enter <command>elilo</command> and press <command>ENTER</command>. This will start the boot load sequence." msgstr "" -#: boot-installer.xml:1256 +#: boot-installer.xml:1373 #, no-c-format #. Tag: para msgid "As with option 1, these steps start the Debian boot loader which will display a menu page for you to select a boot kernel and options. You can also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</command> command at the shell prompt. Proceed to selecting the boot kernel and options." msgstr "" -#: boot-installer.xml:1270 +#: boot-installer.xml:1387 #, no-c-format #. Tag: title msgid "Installing using a Serial Console" msgstr "" -#: boot-installer.xml:1272 +#: boot-installer.xml:1389 #, no-c-format #. Tag: para msgid "You may choose to perform an install using a monitor and keyboard or using a serial connection. To use a monitor/keyboard setup, select an option containing the string [VGA console]. To install over a serial connection, choose an option containing the string [<replaceable>BAUD</replaceable> baud serial console], where <replaceable>BAUD</replaceable> is the speed of your serial console. Menu items for the most typical baud rate settings on the ttyS0 device are preconfigured." msgstr "" -#: boot-installer.xml:1283 +#: boot-installer.xml:1400 #, no-c-format #. Tag: para msgid "In most circumstances, you will want the installer to use the same baud rate as your connection to the EFI console. If you aren't sure what this setting is, you can obtain it using the command <command>baud</command> at the EFI shell." msgstr "" -#: boot-installer.xml:1290 +#: boot-installer.xml:1407 #, no-c-format #. Tag: para msgid "If there is not an option available that is configured for the serial device or baud rate you would like to use, you may override the console setting for one of the existing menu options. For example, to use a 57600 baud console over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into the <classname>Boot:</classname> text window." msgstr "" -#: boot-installer.xml:1301 +#: boot-installer.xml:1418 #, no-c-format #. Tag: para msgid "Most IA-64 boxes ship with a default console setting of 9600 baud. This setting is rather slow, and the normal installation process will take a significant time to draw each screen. You should consider either increasing the baud rate used for performing the installation, or performing a Text Mode installation. See the <classname>Params</classname> help menu for instructions on starting the installer in Text Mode." msgstr "" -#: boot-installer.xml:1310 +#: boot-installer.xml:1427 #, no-c-format #. Tag: para msgid "If you select the wrong console type, you will be able to select the kernel and enter parameters but both the display and your input will go dead as soon as the kernel starts, requiring you to reboot before you can begin the installation." msgstr "" -#: boot-installer.xml:1319 +#: boot-installer.xml:1436 #, no-c-format #. Tag: title msgid "Selecting the Boot Kernel and Options" msgstr "" -#: boot-installer.xml:1321 +#: boot-installer.xml:1438 #, no-c-format #. Tag: para msgid "The boot loader will display a form with a menu list and a text window with a <classname>Boot:</classname> prompt. The arrow keys select an item from the menu and any text typed at the keyboard will appear in the text window. There are also help screens which can be displayed by pressing the appropriate function key. The <classname>General</classname> help screen explains the menu choices and the <classname>Params</classname> screen explains the common command line options." msgstr "" -#: boot-installer.xml:1333 +#: boot-installer.xml:1450 #, no-c-format #. Tag: para msgid "Consult the <classname>General</classname> help screen for the description of the kernels and install modes most appropriate for your installation. You should also consult <xref linkend=\"boot-parms\"/> below for any additional parameters that you may want to set in the <classname>Boot:</classname> text window. The kernel version you choose selects the kernel version that will be used for both the installation process and the installed system. If you encounter kernel problems with the installation, you may also have those same problems with the system you install. The following two steps will select and start the install:" msgstr "" -#: boot-installer.xml:1351 +#: boot-installer.xml:1468 #, no-c-format #. Tag: para msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys." msgstr "" -#: boot-installer.xml:1356 +#: boot-installer.xml:1473 #, no-c-format #. Tag: para msgid "Enter any boot parameters by typing at the keyboard. The text will be displayed directly in the text window. This is where kernel parameters (such as serial console settings) are specified." msgstr "" -#: boot-installer.xml:1363 +#: boot-installer.xml:1480 #, no-c-format #. Tag: para msgid "Press <command>ENTER</command>. This will load and start the kernel. The kernel will display its usual initialization messages followed by the first screen of the Debian Installer." msgstr "" -#: boot-installer.xml:1372 +#: boot-installer.xml:1489 #, no-c-format #. Tag: para msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions." msgstr "" -#: boot-installer.xml:1383 +#: boot-installer.xml:1500 #, no-c-format #. Tag: para msgid "Booting an IA64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed thru the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive." msgstr "" -#: boot-installer.xml:1417 +#: boot-installer.xml:1534 #, no-c-format #. Tag: para msgid "Network booting an ia64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver <command>elilo</command>. On the client a new boot option must be defined in the EFI boot manager to enable loading over a network." msgstr "" -#: boot-installer.xml:1428 +#: boot-installer.xml:1545 #, no-c-format #. Tag: title msgid "Configuring the Server" msgstr "" -#: boot-installer.xml:1429 +#: boot-installer.xml:1546 #, no-c-format #. Tag: para msgid "" @@ -1059,13 +1116,13 @@ msgid "" "</screen></informalexample> Note that the goal is to get <command>elilo.efi</command> running on the client." msgstr "" -#: boot-installer.xml:1439 +#: boot-installer.xml:1556 #, no-c-format #. Tag: para msgid "Extract the <filename>netboot.tar.gz</filename> file into the directory used as the root for your tftp server. Typical tftp root directories include <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This will create a <filename>debian-installer</filename> directory tree containing the boot files for an IA-64 system." msgstr "" -#: boot-installer.xml:1449 +#: boot-installer.xml:1566 #, no-c-format #. Tag: screen msgid "" @@ -1077,337 +1134,337 @@ msgid "" "[...]" msgstr "" -#: boot-installer.xml:1449 +#: boot-installer.xml:1566 #, no-c-format #. Tag: para msgid "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</filename> file that should work for most configurations. However, should you need to make changes to this file, you can find it in the <filename>debian-installer/ia64/</filename> directory. It is possible to have different config files for different clients by naming them using the client's IP address in hex with the suffix <filename>.conf</filename> instead of <filename>elilo.conf</filename>. See documentation provided in the <classname>elilo</classname> package for details." msgstr "" -#: boot-installer.xml:1466 +#: boot-installer.xml:1583 #, no-c-format #. Tag: title msgid "Configuring the Client" msgstr "" -#: boot-installer.xml:1467 +#: boot-installer.xml:1584 #, no-c-format #. Tag: para msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> <listitem><para> Add a boot option. </para></listitem> <listitem><para> You should see one or more lines with the text <guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose the one containing the MAC address of the interface from which you'll be booting. Use the arrow keys to highlight your choice, then press enter. </para></listitem> <listitem><para> Name the entry <userinput>Netboot</userinput> or something similar, save, and exit back to the boot options menu. </para></listitem> </itemizedlist> You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of <filename>elilo.efi</filename> from the server." msgstr "" -#: boot-installer.xml:1499 +#: boot-installer.xml:1616 #, no-c-format #. Tag: para msgid "The boot loader will display its prompt after it has downloaded and processed its configuration file. At this point, the installation proceeds with the same steps as a CD install. Select a boot option as in above and when the kernel has completed installing itself from the network, it will start the Debian Installer." msgstr "" -#: boot-installer.xml:1508 +#: boot-installer.xml:1625 #, no-c-format #. Tag: para msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and the disk partitions." msgstr "" -#: boot-installer.xml:1521 +#: boot-installer.xml:1638 #, no-c-format #. Tag: title msgid "Choosing an Installation Method" msgstr "" -#: boot-installer.xml:1523 +#: boot-installer.xml:1640 #, no-c-format #. Tag: para msgid "Some &arch-title; subarchs have the option of booting using either a 2.4.x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux kernel. The installer should also require less memory when using a 2.4.x linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses tmpfs." msgstr "" -#: boot-installer.xml:1531 +#: boot-installer.xml:1648 #, no-c-format #. Tag: para msgid "If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; kernel parameter." msgstr "" -#: boot-installer.xml:1536 +#: boot-installer.xml:1653 #, no-c-format #. Tag: para msgid "Make sure <userinput>root=/dev/ram</userinput> is one of your kernel parameters." msgstr "" -#: boot-installer.xml:1541 +#: boot-installer.xml:1658 #, no-c-format #. Tag: para msgid "If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's &arch-title; debian-installer FAQ</ulink>." msgstr "" -#: boot-installer.xml:1558 +#: boot-installer.xml:1675 #, no-c-format #. Tag: title msgid "Amiga" msgstr "" -#: boot-installer.xml:1559 +#: boot-installer.xml:1676 #, no-c-format #. Tag: para msgid "The only method of installation available to amiga is the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" -#: boot-installer.xml:1565 +#: boot-installer.xml:1682 #, no-c-format #. Tag: para msgid "Amiga does not currently work with bogl, so if you are seeing bogl errors, you need to include the kernel parameter <userinput>debian-installer/framebuffer=false</userinput>." msgstr "" -#: boot-installer.xml:1574 +#: boot-installer.xml:1691 #, no-c-format #. Tag: title msgid "Atari" msgstr "" -#: boot-installer.xml:1575 +#: boot-installer.xml:1692 #, no-c-format #. Tag: para msgid "The installer for atari may be started from either the hard drive (see <xref linkend=\"m68k-boot-hd\"/>) or from floppies (see <xref linkend=\"boot-from-floppies\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" -#: boot-installer.xml:1582 +#: boot-installer.xml:1699 #, no-c-format #. Tag: para msgid "Atari does not currently work with bogl, so if you are seeing bogl errors, you need to include the kernel parameter <userinput>debian-installer/framebuffer=false</userinput>." msgstr "" -#: boot-installer.xml:1591 +#: boot-installer.xml:1708 #, no-c-format #. Tag: title msgid "BVME6000" msgstr "" -#: boot-installer.xml:1592 +#: boot-installer.xml:1709 #, no-c-format #. Tag: para msgid "The installer for BVME6000 may be started from a cdrom (see <xref linkend=\"m68k-boot-cdrom\"/>), floppies (see <xref linkend=\"boot-from-floppies\"/>), or the net (see <xref linkend=\"boot-tftp\"/>)." msgstr "" -#: boot-installer.xml:1602 +#: boot-installer.xml:1719 #, no-c-format #. Tag: title msgid "Macintosh" msgstr "" -#: boot-installer.xml:1603 +#: boot-installer.xml:1720 #, no-c-format #. Tag: para msgid "The only method of installation available to mac is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis> Macs do not have a working 2.4.x kernel." msgstr "" -#: boot-installer.xml:1610 +#: boot-installer.xml:1727 #, no-c-format #. Tag: para msgid "If your hardware uses a 53c9x-based scsi bus, then you may need to include the kernel parameter <userinput>mac53c9x=1,0</userinput>. Hardware with two such scsi buses, such as the Quadra 950, will need <userinput>mac53c9x=2,0</userinput> instead. Alternatively, the parameter can be specified as <userinput>mac53c9x=-1,0</userinput> which will leave autodetection on, but which will disable SCSI disconnects. Note that specifying this parameter is only necessary if you have more than one hard disk; otherwise, the system will run faster if you do not specify it." msgstr "" -#: boot-installer.xml:1625 +#: boot-installer.xml:1742 #, no-c-format #. Tag: title msgid "MVME147 and MVME16x" msgstr "" -#: boot-installer.xml:1626 +#: boot-installer.xml:1743 #, no-c-format #. Tag: para msgid "The installer for MVME147 and MVME16x may be started from either floppies (see <xref linkend=\"boot-from-floppies\"/>) or the net (see <xref linkend=\"boot-tftp\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" -#: boot-installer.xml:1636 +#: boot-installer.xml:1753 #, no-c-format #. Tag: title msgid "Q40/Q60" msgstr "" -#: boot-installer.xml:1637 +#: boot-installer.xml:1754 #, no-c-format #. Tag: para msgid "The only method of installation available to Q40/Q60 is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" -#: boot-installer.xml:1648 +#: boot-installer.xml:1765 #, no-c-format #. Tag: title msgid "Booting from a Hard Disk" msgstr "" -#: boot-installer.xml:1654 boot-installer.xml:2159 +#: boot-installer.xml:1771 boot-installer.xml:2369 #, no-c-format #. Tag: para msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation." msgstr "" -#: boot-installer.xml:1660 boot-installer.xml:2165 +#: boot-installer.xml:1777 boot-installer.xml:2375 #, no-c-format #. Tag: para msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files in <xref linkend=\"boot-drive-files\"/>." msgstr "" -#: boot-installer.xml:1669 +#: boot-installer.xml:1786 #, no-c-format #. Tag: para msgid "At least six different ramdisks may be used to boot from the hard drive, three different types each with and without support for a 2.2.x linux kernel (see <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink> for details)." msgstr "" -#: boot-installer.xml:1677 +#: boot-installer.xml:1794 #, no-c-format #. Tag: para msgid "The three different types of ramdisks are <filename>cdrom</filename>, <filename>hd-media</filename>, and <filename>nativehd</filename>. These ramdisks differ only in their source for installation packages. The <filename>cdrom</filename> ramdisk uses a cdrom to get debian-installer packages. The <filename>hd-media</filename> ramdisk uses an iso image file of a cdrom currently residing on a hard disk. Finally, the <filename>nativehd</filename> ramdisk uses the net to install packages." msgstr "" -#: boot-installer.xml:1698 +#: boot-installer.xml:1815 #, no-c-format #. Tag: title msgid "Booting from AmigaOS" msgstr "" -#: boot-installer.xml:1699 +#: boot-installer.xml:1816 #, no-c-format #. Tag: para msgid "In the <command>Workbench</command>, start the Linux installation process by double-clicking on the <guiicon>StartInstall</guiicon> icon in the <filename>debian</filename> directory." msgstr "" -#: boot-installer.xml:1705 +#: boot-installer.xml:1822 #, no-c-format #. Tag: para msgid "You may have to press the &enterkey; key twice after the Amiga installer program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue down at <xref linkend=\"d-i-intro\"/>." msgstr "" -#: boot-installer.xml:1720 +#: boot-installer.xml:1837 #, no-c-format #. Tag: title msgid "Booting from Atari TOS" msgstr "" -#: boot-installer.xml:1721 +#: boot-installer.xml:1838 #, no-c-format #. Tag: para msgid "At the GEM desktop, start the Linux installation process by double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the <filename>debian</filename> directory and clicking <guibutton>Ok</guibutton> at the program options dialog box." msgstr "" -#: boot-installer.xml:1728 +#: boot-installer.xml:1845 #, no-c-format #. Tag: para msgid "You may have to press the &enterkey; key after the Atari bootstrap program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" -#: boot-installer.xml:1743 +#: boot-installer.xml:1860 #, no-c-format #. Tag: title msgid "Booting from MacOS" msgstr "" -#: boot-installer.xml:1744 +#: boot-installer.xml:1861 #, no-c-format #. Tag: para msgid "You must retain the original Mac system and boot from it. It is <emphasis>essential</emphasis> that, when booting MacOS in preparation for booting the Penguin linux loader, you hold the <keycap>shift</keycap> key down to prevent extensions from loading. If you don't use MacOS except for loading linux, you can accomplish the same thing by removing all extensions and control panels from the Mac's System Folder. Otherwise extensions may be left running and cause random problems with the running linux kernel." msgstr "" -#: boot-installer.xml:1755 +#: boot-installer.xml:1872 #, no-c-format #. Tag: para msgid "Macs require the <command>Penguin</command> bootloader. If you do not have the tools to handle a <command>Stuffit</command> archive, &penguin19.hfs; is an hfs disk image with <command>Penguin</command> unpacked. <xref linkend=\"create-floppy\"/> describes how to copy this image to a floppy." msgstr "" -#: boot-installer.xml:1764 +#: boot-installer.xml:1881 #, no-c-format #. Tag: para msgid "At the MacOS desktop, start the Linux installation process by double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in the <filename>Penguin</filename> directory. The <command>Penguin</command> booter will start up. Go to the <guimenuitem>Settings</guimenuitem> item in the <guimenu>File</guimenu> menu, click the <guilabel>Kernel</guilabel> tab. Select the kernel (<filename>vmlinuz</filename>) and ramdisk (<filename>initrd.gz</filename>) images in the <filename>install</filename> directory by clicking on the corresponding buttons in the upper right corner, and navigating the file select dialogs to locate the files." msgstr "" -#: boot-installer.xml:1779 +#: boot-installer.xml:1896 #, no-c-format #. Tag: para msgid "To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -> <guimenuitem>Settings...</guimenuitem>, then switch to the <guilabel>Options</guilabel> tab. Boot parameters may be typed in to the text entry area. If you will always want to use these settings, select <guimenu>File</guimenu> -> <guimenuitem>Save Settings as Default</guimenuitem>." msgstr "" -#: boot-installer.xml:1788 +#: boot-installer.xml:1905 #, no-c-format #. Tag: para msgid "Close the <guilabel>Settings</guilabel> dialog, save the settings and start the bootstrap using the <guimenuitem>Boot Now</guimenuitem> item in the <guimenu>File</guimenu> menu." msgstr "" -#: boot-installer.xml:1795 +#: boot-installer.xml:1912 #, no-c-format #. Tag: para msgid "The <command>Penguin</command> booter will output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" -#: boot-installer.xml:1810 +#: boot-installer.xml:1927 #, no-c-format #. Tag: title msgid "Booting from Q40/Q60" msgstr "" -#: boot-installer.xml:1812 +#: boot-installer.xml:1929 #, no-c-format #. Tag: para msgid "FIXME" msgstr "" -#: boot-installer.xml:1816 +#: boot-installer.xml:1933 #, no-c-format #. Tag: para msgid "The installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" -#: boot-installer.xml:1828 +#: boot-installer.xml:1945 #, no-c-format #. Tag: para msgid "Currently, the only &arch-title; subarchitecture that supports CD-ROM booting is the BVME6000." msgstr "" -#: boot-installer.xml:1900 +#: boot-installer.xml:2017 #, no-c-format #. Tag: para msgid "After booting the VMEbus systems you will be presented with the LILO <prompt>Boot:</prompt> prompt. At that prompt enter one of the following to boot Linux and begin installation proper of the Debian software using vt102 terminal emulation:" msgstr "" -#: boot-installer.xml:1911 +#: boot-installer.xml:2028 #, no-c-format #. Tag: para msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000" msgstr "" -#: boot-installer.xml:1916 +#: boot-installer.xml:2033 #, no-c-format #. Tag: para msgid "type <screen>i162 &enterkey;</screen> to install an MVME162" msgstr "" -#: boot-installer.xml:1921 +#: boot-installer.xml:2038 #, no-c-format #. Tag: para msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167" msgstr "" -#: boot-installer.xml:1928 +#: boot-installer.xml:2045 #, no-c-format #. Tag: para msgid "You may additionally append the string <screen>TERM=vt100</screen> to use vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>." msgstr "" -#: boot-installer.xml:1940 +#: boot-installer.xml:2057 #, no-c-format #. Tag: para msgid "For most &arch-title; architectures, booting from a local filesystem is the recommended method." msgstr "" -#: boot-installer.xml:1945 +#: boot-installer.xml:2062 #, no-c-format #. Tag: para msgid "Booting from the boot floppy is supported only for Atari and VME (with a SCSI floppy drive on VME) at this time." msgstr "" -#: boot-installer.xml:1961 boot-installer.xml:2008 +#: boot-installer.xml:2078 boot-installer.xml:2125 #, no-c-format #. Tag: title msgid "SGI Indys TFTP Booting" msgstr "" -#: boot-installer.xml:1962 +#: boot-installer.xml:2079 #, no-c-format #. Tag: para msgid "" @@ -1418,13 +1475,13 @@ msgid "" "</screen></informalexample> in the command monitor to do this." msgstr "" -#: boot-installer.xml:1981 boot-installer.xml:2030 +#: boot-installer.xml:2098 boot-installer.xml:2147 boot-installer.xml:2202 boot-installer.xml:2241 #, no-c-format #. Tag: title msgid "Broadcom BCM91250A TFTP Booting" msgstr "" -#: boot-installer.xml:1982 +#: boot-installer.xml:2099 boot-installer.xml:2203 #, no-c-format #. Tag: para msgid "" @@ -1435,19 +1492,19 @@ msgid "" "</screen></informalexample> You need to substitute the IP address listed in this example with either the name or the IP address of your TFTP server. Once you issue this command, the installer will be loaded automatically." msgstr "" -#: boot-installer.xml:2005 boot-installer.xml:2539 +#: boot-installer.xml:2122 boot-installer.xml:2226 boot-installer.xml:2749 #, no-c-format #. Tag: title msgid "Boot Parameters" msgstr "" -#: boot-installer.xml:2009 +#: boot-installer.xml:2126 #, no-c-format #. Tag: para msgid "On SGI Indys you can append boot parameters to the <command>bootp():</command> command in the command monitor." msgstr "" -#: boot-installer.xml:2014 +#: boot-installer.xml:2131 #, no-c-format #. Tag: para msgid "" @@ -1456,109 +1513,139 @@ msgid "" "</screen></informalexample> Further kernel parameters can be passed via <command>append</command>:" msgstr "" -#: boot-installer.xml:2024 +#: boot-installer.xml:2141 #, no-c-format #. Tag: screen msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" -#: boot-installer.xml:2031 +#: boot-installer.xml:2148 boot-installer.xml:2242 #, no-c-format #. Tag: para msgid "You cannot pass any boot parameters directly from the CFE prompt. Instead, you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP server and add your parameters to the <replaceable>extra_args</replaceable> variable." msgstr "" -#: boot-installer.xml:2048 +#: boot-installer.xml:2167 boot-installer.xml:2229 +#, no-c-format +#. Tag: title +msgid "Cobalt TFTP Booting" +msgstr "" + +#: boot-installer.xml:2168 +#, no-c-format +#. Tag: para +msgid "Strictly speaking, Cobalt does not ue 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 "" + +#: boot-installer.xml:2178 +#, no-c-format +#. Tag: para +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 "" + +#: boot-installer.xml:2187 +#, no-c-format +#. Tag: para +msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way. This option is not available on Qube 2700 (Qube1) machines since they have no serial port." +msgstr "" + +#: boot-installer.xml:2230 +#, no-c-format +#. Tag: para +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 "" + +#: boot-installer.xml:2258 #, no-c-format #. Tag: title msgid "s390 Limitations" msgstr "" -#: boot-installer.xml:2049 +#: boot-installer.xml:2259 #, no-c-format #. Tag: para msgid "In order to run the installation system a working network setup and ssh session is needed on S/390." msgstr "" -#: boot-installer.xml:2054 +#: boot-installer.xml:2264 #, no-c-format #. Tag: para 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 a ssh session which will launch the standard installation system." msgstr "" -#: boot-installer.xml:2065 +#: boot-installer.xml:2275 #, no-c-format #. Tag: title msgid "s390 Boot Parameters" msgstr "" -#: boot-installer.xml:2066 +#: boot-installer.xml:2276 #, no-c-format #. Tag: para msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. Please read <ulink url=\"&url-s390-devices;\">Device Drivers and Installation Commands</ulink> for more information about S/390-specific boot parameters." msgstr "" -#: boot-installer.xml:2120 +#: boot-installer.xml:2330 #, no-c-format #. Tag: para msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the CD-ROM." msgstr "" -#: boot-installer.xml:2129 +#: boot-installer.xml:2339 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2138 +#: boot-installer.xml:2348 #, no-c-format #. Tag: para msgid "If your system doesn't boot directly from CD-ROM, you can still use the CD-ROM to install the system. On NewWorlds, you can also use an OpenFirmware command to boot from the CD-ROM manually. Follow the instructions in <xref linkend=\"boot-newworld\"/> for booting from the hard disk, except use the path to <command>yaboot</command> on the CD at the OF prompt, such as" msgstr "" -#: boot-installer.xml:2147 +#: boot-installer.xml:2357 #, no-c-format #. Tag: screen msgid "0 > boot cd:,\\install\\yaboot" msgstr "" -#: boot-installer.xml:2153 +#: boot-installer.xml:2363 #, no-c-format #. Tag: title msgid "Booting from Hard Disk" msgstr "" -#: boot-installer.xml:2174 +#: boot-installer.xml:2384 #, no-c-format #. Tag: title msgid "Booting CHRP from OpenFirmware" msgstr "" -#: boot-installer.xml:2178 +#: boot-installer.xml:2388 #, no-c-format #. Tag: emphasis msgid "Not yet written." msgstr "" -#: boot-installer.xml:2183 +#: boot-installer.xml:2393 #, no-c-format #. Tag: title msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" -#: boot-installer.xml:2184 +#: boot-installer.xml:2394 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2202 +#: boot-installer.xml:2412 #, no-c-format #. Tag: title msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" -#: boot-installer.xml:2203 +#: boot-installer.xml:2413 #, no-c-format #. Tag: para msgid "" @@ -1569,31 +1656,31 @@ msgid "" "</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type either <userinput>install</userinput> or <userinput>install video=ofonly</userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> argument is for maximum compatibility; you can try it if <userinput>install</userinput> doesn't work. The Debian installation program should start." msgstr "" -#: boot-installer.xml:2238 +#: boot-installer.xml:2448 #, no-c-format #. Tag: title msgid "Booting from USB memory stick" msgstr "" -#: boot-installer.xml:2239 +#: boot-installer.xml:2449 #, no-c-format #. Tag: para msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" -#: boot-installer.xml:2245 +#: boot-installer.xml:2455 #, no-c-format #. Tag: para msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. To get to the prompt, hold down <keycombo><keycap>Command</keycap> <keycap>Option</keycap> <keycap>o</keycap> <keycap>f</keycap></keycombo> all together while booting (see <xref linkend=\"invoking-openfirmware\"/>)." msgstr "" -#: boot-installer.xml:2257 +#: boot-installer.xml:2467 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2269 +#: boot-installer.xml:2479 #, no-c-format #. Tag: para msgid "" @@ -1602,79 +1689,79 @@ msgid "" "</screen></informalexample> The <replaceable>2</replaceable> matches the Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. <command>yaboot</command>) in the directory previously blessed with <command>hattrib -b</command>." msgstr "" -#: boot-installer.xml:2283 +#: boot-installer.xml:2493 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2289 +#: boot-installer.xml:2499 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2322 +#: boot-installer.xml:2532 #, no-c-format #. Tag: para msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" -#: boot-installer.xml:2326 +#: boot-installer.xml:2536 #, no-c-format #. Tag: para msgid "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <command>boot enet:0</command>. PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try <userinput>boot <replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>." msgstr "" -#: boot-installer.xml:2341 +#: boot-installer.xml:2551 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2353 +#: boot-installer.xml:2563 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2359 +#: boot-installer.xml:2569 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2366 +#: boot-installer.xml:2576 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2377 +#: boot-installer.xml:2587 #, no-c-format #. Tag: title msgid "PowerPC Boot Parameters" msgstr "" -#: boot-installer.xml:2378 +#: boot-installer.xml:2588 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2418 +#: boot-installer.xml:2628 #, no-c-format #. Tag: para 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. Some older OpenBoot revisions require using the device name, such as <userinput>boot le()</userinput>; these probably don't support BOOTP nor DHCP." msgstr "" -#: boot-installer.xml:2474 +#: boot-installer.xml:2684 #, no-c-format #. Tag: para 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). You may have to use the actual device name for older OpenBoot versions that don't support this special command. Note that some problems have been reported on Sun4m (e.g., Sparc 10s and Sparc 20s) systems booting from CD-ROM." msgstr "" -#: boot-installer.xml:2489 +#: boot-installer.xml:2699 #, no-c-format #. Tag: para msgid "" @@ -1683,13 +1770,13 @@ msgid "" "</screen></informalexample> Be warned that the newer Sun4u (ultra) architecture does not support floppy booting. A typical error message is <computeroutput>Bad magic number in disk label - Can't open disk label package</computeroutput>. Furthermore, a number of Sun4c models (such as the IPX) do not support the compressed images found on the disks, so also are not supported." msgstr "" -#: boot-installer.xml:2501 +#: boot-installer.xml:2711 #, no-c-format #. Tag: para msgid "Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from booting (instead of not supporting booting at all). The appropriate OBP update can be downloaded as product ID 106121 from <ulink url=\"http://sunsolve.sun.com\"></ulink>." msgstr "" -#: boot-installer.xml:2508 +#: boot-installer.xml:2718 #, no-c-format #. Tag: para msgid "" @@ -1699,37 +1786,37 @@ msgid "" "</screen></informalexample> then it is possible that floppy booting is simply not supported on your machine." msgstr "" -#: boot-installer.xml:2520 +#: boot-installer.xml:2730 #, no-c-format #. Tag: title msgid "IDPROM Messages" msgstr "" -#: boot-installer.xml:2521 +#: boot-installer.xml:2731 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2540 +#: boot-installer.xml:2750 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2547 +#: boot-installer.xml:2757 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2554 +#: boot-installer.xml:2764 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2563 +#: boot-installer.xml:2773 #, no-c-format #. Tag: para msgid "" @@ -1738,475 +1825,475 @@ msgid "" "</screen></informalexample> should be emitted early in the process. <replaceable>total</replaceable> should match the total amount of RAM, in kilobytes. If this doesn't match the actual amount of RAM you have installed, you need to use the <userinput>mem=<replaceable>ram</replaceable></userinput> parameter, where <replaceable>ram</replaceable> is set to the amount of memory, suffixed with <quote>k</quote> for kilobytes, or <quote>m</quote> for megabytes. For example, both <userinput>mem=65536k</userinput> and <userinput>mem=64m</userinput> mean 64MB of RAM." msgstr "" -#: boot-installer.xml:2579 +#: boot-installer.xml:2789 #, no-c-format #. Tag: para msgid "If you are booting with a serial console, generally the kernel will autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</phrase>. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>." msgstr "" -#: boot-installer.xml:2592 +#: boot-installer.xml:2802 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2603 +#: boot-installer.xml:2813 #, no-c-format #. Tag: title msgid "Debian Installer Parameters" msgstr "" -#: boot-installer.xml:2604 +#: boot-installer.xml:2814 #, no-c-format #. Tag: para msgid "The installation system recognizes a few additional boot parameters<footnote> <para> Note that the kernel accepts a maximum of 8 command line options and 8 environment options (including any options added by default for the installer). If these numbers are exceeded, 2.4 kernels will drop any excess options and 2.6 kernels will panic. With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options. </para> </footnote> which may be useful." msgstr "" -#: boot-installer.xml:2624 +#: boot-installer.xml:2834 #, no-c-format #. Tag: term msgid "debconf/priority" msgstr "" -#: boot-installer.xml:2625 +#: boot-installer.xml:2835 #, no-c-format #. Tag: para msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" -#: boot-installer.xml:2629 +#: boot-installer.xml:2839 #, no-c-format #. Tag: para msgid "The default installation uses <userinput>debconf/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 "" -#: boot-installer.xml:2636 +#: boot-installer.xml:2846 #, no-c-format #. Tag: para msgid "If you add <userinput>debconf/priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>debconf/priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>debconf/priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss." msgstr "" -#: boot-installer.xml:2650 +#: boot-installer.xml:2860 #, no-c-format #. Tag: term msgid "DEBIAN_FRONTEND" msgstr "" -#: boot-installer.xml:2651 +#: boot-installer.xml:2861 #, no-c-format #. Tag: para 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=slang</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=ncurses</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=corba</userinput></para> </listitem> </itemizedlist> The default front end is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally only the <userinput>newt</userinput> frontend is available on default install media, so this is not very useful right now." msgstr "" -#: boot-installer.xml:2687 +#: boot-installer.xml:2897 #, no-c-format #. Tag: term msgid "BOOT_DEBUG" msgstr "" -#: boot-installer.xml:2688 +#: boot-installer.xml:2898 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2697 +#: boot-installer.xml:2907 #, no-c-format #. Tag: userinput msgid "BOOT_DEBUG=0" msgstr "" -#: boot-installer.xml:2698 +#: boot-installer.xml:2908 #, no-c-format #. Tag: para msgid "This is the default." msgstr "" -#: boot-installer.xml:2702 +#: boot-installer.xml:2912 #, no-c-format #. Tag: userinput msgid "BOOT_DEBUG=1" msgstr "" -#: boot-installer.xml:2703 +#: boot-installer.xml:2913 #, no-c-format #. Tag: para msgid "More verbose than usual." msgstr "" -#: boot-installer.xml:2707 +#: boot-installer.xml:2917 #, no-c-format #. Tag: userinput msgid "BOOT_DEBUG=2" msgstr "" -#: boot-installer.xml:2708 +#: boot-installer.xml:2918 #, no-c-format #. Tag: para msgid "Lots of debugging information." msgstr "" -#: boot-installer.xml:2712 +#: boot-installer.xml:2922 #, no-c-format #. Tag: userinput msgid "BOOT_DEBUG=3" msgstr "" -#: boot-installer.xml:2713 +#: boot-installer.xml:2923 #, no-c-format #. Tag: para msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot." msgstr "" -#: boot-installer.xml:2727 +#: boot-installer.xml:2937 #, no-c-format #. Tag: term msgid "INSTALL_MEDIA_DEV" msgstr "" -#: boot-installer.xml:2728 +#: boot-installer.xml:2938 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2734 +#: boot-installer.xml:2944 #, no-c-format #. Tag: para msgid "The boot floppy, which normally scans all floppies and USB storage devices it can to find the root floppy, can be overridden by this parameter to only look at the one device." msgstr "" -#: boot-installer.xml:2744 +#: boot-installer.xml:2954 #, no-c-format #. Tag: term msgid "debian-installer/framebuffer" msgstr "" -#: boot-installer.xml:2745 +#: boot-installer.xml:2955 #, no-c-format #. Tag: para msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature by the parameter <userinput>debian-installer/framebuffer=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 "" -#: boot-installer.xml:2754 +#: boot-installer.xml:2964 #, no-c-format #. Tag: para msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card." msgstr "" -#: boot-installer.xml:2760 +#: boot-installer.xml:2970 #, no-c-format #. Tag: para msgid "Such problems have been reported on the Amiga 1200 and SE/30." msgstr "" -#: boot-installer.xml:2764 +#: boot-installer.xml:2974 #, no-c-format #. Tag: para msgid "Such problems have been reported on hppa." msgstr "" -#: boot-installer.xml:2768 +#: boot-installer.xml:2978 #, no-c-format #. Tag: para 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>." msgstr "" -#: boot-installer.xml:2781 +#: boot-installer.xml:2991 #, no-c-format #. Tag: term msgid "debian-installer/probe/usb" msgstr "" -#: boot-installer.xml:2782 +#: boot-installer.xml:2992 #, no-c-format #. Tag: para msgid "Set to <userinput>false</userinput> to prevent probing for USB on boot, if that causes problems." msgstr "" -#: boot-installer.xml:2791 +#: boot-installer.xml:3001 #, no-c-format #. Tag: term msgid "netcfg/disable_dhcp" msgstr "" -#: boot-installer.xml:2792 +#: boot-installer.xml:3002 #, no-c-format #. Tag: para msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails." msgstr "" -#: boot-installer.xml:2799 +#: boot-installer.xml:3009 #, no-c-format #. Tag: para msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually." msgstr "" -#: boot-installer.xml:2810 +#: boot-installer.xml:3020 #, no-c-format #. Tag: term msgid "hw-detect/start_pcmcia" msgstr "" -#: boot-installer.xml:2811 +#: boot-installer.xml:3021 #, no-c-format #. Tag: para msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." msgstr "" -#: boot-installer.xml:2821 +#: boot-installer.xml:3031 #, no-c-format #. Tag: term msgid "preseed/url" msgstr "" -#: boot-installer.xml:2822 +#: boot-installer.xml:3032 #, no-c-format #. Tag: para msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" -#: boot-installer.xml:2831 +#: boot-installer.xml:3041 #, no-c-format #. Tag: term msgid "preseed/file" msgstr "" -#: boot-installer.xml:2832 +#: boot-installer.xml:3042 #, no-c-format #. Tag: para msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" -#: boot-installer.xml:2841 +#: boot-installer.xml:3051 #, no-c-format #. Tag: term msgid "cdrom-detect/eject" msgstr "" -#: boot-installer.xml:2842 +#: boot-installer.xml:3052 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2851 +#: boot-installer.xml:3061 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2862 +#: boot-installer.xml:3072 #, no-c-format #. Tag: term msgid "ramdisk_size" msgstr "" -#: boot-installer.xml:2863 +#: boot-installer.xml:3073 #, no-c-format #. Tag: para msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." msgstr "" -#: boot-installer.xml:2871 +#: boot-installer.xml:3081 #, no-c-format #. Tag: term msgid "rescue/enable" msgstr "" -#: boot-installer.xml:2872 +#: boot-installer.xml:3082 #, no-c-format #. Tag: para msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." msgstr "" -#: boot-installer.xml:2890 +#: boot-installer.xml:3100 #, no-c-format #. Tag: title msgid "Troubleshooting the Installation Process" msgstr "" -#: boot-installer.xml:2895 +#: boot-installer.xml:3105 #, no-c-format #. Tag: title msgid "Floppy Disk Reliability" msgstr "" -#: boot-installer.xml:2897 +#: boot-installer.xml:3107 #, no-c-format #. Tag: para msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." msgstr "" -#: boot-installer.xml:2902 +#: boot-installer.xml:3112 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2911 +#: boot-installer.xml:3121 #, no-c-format #. Tag: para msgid "If you are having the installation stall at a particular floppy, the first thing you should do is re-download the floppy disk image and write it to a <emphasis>different</emphasis> floppy. 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 "" -#: boot-installer.xml:2921 +#: boot-installer.xml:3131 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2927 +#: boot-installer.xml:3137 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2936 +#: boot-installer.xml:3146 #, no-c-format #. Tag: title msgid "Boot Configuration" msgstr "" -#: boot-installer.xml:2938 +#: boot-installer.xml:3148 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2945 +#: boot-installer.xml:3155 #, no-c-format #. Tag: para msgid "If you are booting with your own kernel instead of the one supplied with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>." msgstr "" -#: boot-installer.xml:2952 +#: boot-installer.xml:3162 #, no-c-format #. Tag: para msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"i386\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" msgstr "" -#: boot-installer.xml:2958 +#: boot-installer.xml:3168 #, no-c-format #. Tag: para msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>." msgstr "" -#: boot-installer.xml:2969 +#: boot-installer.xml:3179 #, no-c-format #. Tag: title msgid "Common &arch-title; Installation Problems" msgstr "" -#: boot-installer.xml:2970 +#: boot-installer.xml:3180 #, no-c-format #. Tag: para msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." msgstr "" -#: boot-installer.xml:2975 +#: boot-installer.xml:3185 #, no-c-format #. Tag: para msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>." msgstr "" -#: boot-installer.xml:2981 +#: boot-installer.xml:3191 #, no-c-format #. Tag: para msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>." msgstr "" -#: boot-installer.xml:2990 +#: boot-installer.xml:3200 #, no-c-format #. Tag: para msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test." msgstr "" -#: boot-installer.xml:2997 +#: boot-installer.xml:3207 #, no-c-format #. Tag: para 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>debian-installer/framebuffer=false</userinput> or <userinput>video=vga16:off</userinput> to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" -#: boot-installer.xml:3012 +#: boot-installer.xml:3222 #, no-c-format #. Tag: title msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" -#: boot-installer.xml:3013 +#: boot-installer.xml:3223 #, no-c-format #. Tag: para msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems." msgstr "" -#: boot-installer.xml:3023 +#: boot-installer.xml:3233 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3040 +#: boot-installer.xml:3250 #, no-c-format #. Tag: title msgid "System Freeze while Loading the USB Modules" msgstr "" -#: boot-installer.xml:3041 +#: boot-installer.xml:3251 #, no-c-format #. Tag: para msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter at the boot prompt, which will prevent the modules from being loaded." msgstr "" -#: boot-installer.xml:3055 +#: boot-installer.xml:3265 #, no-c-format #. Tag: title msgid "Interpreting the Kernel Startup Messages" msgstr "" -#: boot-installer.xml:3057 +#: boot-installer.xml:3267 #, no-c-format #. Tag: para msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable> </computeroutput>, or <computeroutput> <replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable> </computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable> </computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." msgstr "" -#: boot-installer.xml:3082 +#: boot-installer.xml:3292 #, no-c-format #. Tag: title msgid "Bug Reporter" msgstr "" -#: boot-installer.xml:3083 +#: boot-installer.xml:3293 #, no-c-format #. Tag: para msgid "If you get through the initial boot phase but cannot complete the install, the bug reporter menu choice may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them in 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 "" -#: boot-installer.xml:3094 +#: boot-installer.xml:3304 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3105 +#: boot-installer.xml:3315 #, no-c-format #. Tag: title msgid "Submitting Installation Reports" msgstr "" -#: boot-installer.xml:3106 +#: boot-installer.xml:3316 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3113 +#: boot-installer.xml:3323 #, no-c-format #. Tag: para msgid "If you have a working Debian system, the easiest way to send an installation report is to install the installation-report and reportbug packages (<command>apt-get install installation-report reportbug</command>) and run the command <command>reportbug installation-report</command>." msgstr "" -#: boot-installer.xml:3120 +#: boot-installer.xml:3330 #, no-c-format #. Tag: para msgid "" diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index d32be6b88..2b604463b 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2006-02-07 15:07+0000\n" +"POT-Creation-Date: 2006-03-07 20:14+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" @@ -230,6 +230,12 @@ msgstr "" msgid "<entry>arm</entry>" msgstr "" +#: hardware.xml:111 +#, no-c-format +#. Tag: entry +msgid "Netwinder and CATS" +msgstr "" + #: hardware.xml:112 #, no-c-format #. Tag: entry @@ -239,19 +245,25 @@ msgstr "" #: hardware.xml:114 #, no-c-format #. Tag: entry -msgid "riscpc" +msgid "Linksys NSLU2" +msgstr "" + +#: hardware.xml:115 +#, no-c-format +#. Tag: entry +msgid "nslu2" msgstr "" -#: hardware.xml:116 +#: hardware.xml:117 #, no-c-format #. Tag: entry -msgid "shark" +msgid "RiscPC and Riscstation" msgstr "" #: hardware.xml:118 #, no-c-format #. Tag: entry -msgid "lart" +msgid "riscpc" msgstr "" #: hardware.xml:122 @@ -434,13 +446,13 @@ msgstr "" msgid "DECstation" msgstr "" -#: hardware.xml:173 hardware.xml:1002 hardware.xml:1017 hardware.xml:1027 +#: hardware.xml:173 hardware.xml:994 hardware.xml:1009 hardware.xml:1019 #, no-c-format #. Tag: entry msgid "r4k-kn04" msgstr "" -#: hardware.xml:175 hardware.xml:997 hardware.xml:1007 hardware.xml:1012 hardware.xml:1022 +#: hardware.xml:175 hardware.xml:989 hardware.xml:999 hardware.xml:1004 hardware.xml:1014 #, no-c-format #. Tag: entry msgid "r3k-kn02" @@ -494,7 +506,7 @@ msgstr "" msgid "This is the first official release of &debian; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&architecture; mailing list</ulink> as well." msgstr "" -#: hardware.xml:224 hardware.xml:683 hardware.xml:780 hardware.xml:799 hardware.xml:842 hardware.xml:884 hardware.xml:938 hardware.xml:1087 hardware.xml:1493 +#: hardware.xml:224 hardware.xml:683 hardware.xml:772 hardware.xml:791 hardware.xml:834 hardware.xml:876 hardware.xml:930 hardware.xml:1081 hardware.xml:1487 #, no-c-format #. Tag: title msgid "CPU, Main Boards, and Video Support" @@ -1619,7 +1631,7 @@ msgstr "" #: hardware.xml:693 #, no-c-format #. Tag: para -msgid "Most ARM CPUs may be run in either endian mode (big or little). However, almost every current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems." +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 "" #: hardware.xml:701 @@ -1628,289 +1640,277 @@ msgstr "" msgid "The commonly supported systems are" msgstr "" -#: hardware.xml:707 +#: hardware.xml:708 #, no-c-format #. Tag: term msgid "Netwinder" msgstr "" -#: hardware.xml:708 +#: hardware.xml:709 #, no-c-format #. Tag: para -msgid "This is actually the name for the group of machines based upon the StrongARM 110 CPU and Intel 21285 Northbridge. It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff)." +msgid "This is actually the name for the group of machines based upon the StrongARM 110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff)." msgstr "" -#: hardware.xml:720 +#: hardware.xml:722 #, no-c-format #. Tag: term -msgid "Bast" +msgid "NSLU2" msgstr "" -#: hardware.xml:721 +#: hardware.xml:723 #, no-c-format #. Tag: para -msgid "This is a modern ARM 920 board with a 266MHz Samsung processor. It has integrated IDE, USB, Serial, Parallel, audio, video, flash and two ethernet ports. This system has a good bootloader which is also found on the CATS and Riscstation systems." +msgid "The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected." msgstr "" -#: hardware.xml:732 +#: hardware.xml:734 #, no-c-format #. Tag: term msgid "RiscPC" msgstr "" -#: hardware.xml:733 +#: hardware.xml:735 #, no-c-format #. Tag: para msgid "This machine is the oldest supported hardware: it was released in 1994. It has RISC OS in ROM, Linux can be booted from that OS using linloader. The RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA video, parallel port, single serial port, PS/2 keyboard and proprietary mouse port. The proprietary module expansion bus allows for up to eight expansion cards to be fitted depending on configuration, several of these modules have Linux drivers." msgstr "" -#: hardware.xml:748 +#: hardware.xml:750 #, no-c-format #. Tag: term msgid "Riscstation" msgstr "" -#: hardware.xml:749 +#: hardware.xml:751 #, no-c-format #. Tag: para msgid "This is an inexpensive 56MHz 7500FE based machine with integrated video, IDE, PS/2 keyboard and mouse and two serial ports. Its lack of processing power was made up for by its price. It may be found in two configurations one with RISC OS and one with a simple bootloader." msgstr "" -#: hardware.xml:761 -#, no-c-format -#. Tag: term -msgid "LART" -msgstr "" - -#: hardware.xml:762 -#, no-c-format -#. Tag: para -msgid "This is a modular open hardware platform intended to be built by enthusiasts. To be useful to install Debian it requires its KSB expansion board." -msgstr "" - -#: hardware.xml:781 +#: hardware.xml:773 #, no-c-format #. Tag: para msgid "The 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 "" -#: hardware.xml:800 +#: hardware.xml:792 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:808 hardware.xml:914 +#: hardware.xml:800 hardware.xml:906 #, no-c-format #. Tag: title msgid "<title>CPU</title>" msgstr "" -#: hardware.xml:809 +#: hardware.xml:801 #, no-c-format #. Tag: para msgid "Nearly all x86-based processors are supported; this includes AMD and VIA (former Cyrix) processors as well. Also the new processors like Athlon XP and Intel P4 Xeon are supported. However, Linux will <emphasis>not</emphasis> run on 286 or earlier processors." msgstr "" -#: hardware.xml:819 +#: hardware.xml:811 #, no-c-format #. Tag: title msgid "I/O Bus" msgstr "" -#: hardware.xml:820 +#: hardware.xml:812 #, no-c-format #. Tag: para 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, the Microchannel Architecture (MCA, used in IBM's PS/2 line), or VESA Local Bus (VLB, sometimes called the VL bus)." msgstr "" -#: hardware.xml:843 +#: hardware.xml:835 #, no-c-format #. Tag: para msgid "Complete information concerning supported M68000 based (<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the basics." msgstr "" -#: hardware.xml:850 +#: hardware.xml:842 #, no-c-format #. Tag: para msgid "The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory Management Unit) and a FPU (floating-point unit). This includes the 68020 with an external 68851 PMMU, the 68030, and better, and excludes the <quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink> for complete details." msgstr "" -#: hardware.xml:858 +#: hardware.xml:850 #, no-c-format #. Tag: para msgid "There are four major flavors of supported <emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two systems to which Linux was ported; in keeping, they are also the two most well-supported Debian ports. The Macintosh line is supported incompletely, both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> for project status and supported hardware. The BVM and Motorola single board VMEbus computers are the most recent addition to the list of machines supported by Debian. Ports to other &architecture; architectures, such as the Sun3 architecture and NeXT black box, are underway but not yet supported by Debian." msgstr "" -#: hardware.xml:885 +#: hardware.xml:877 #, no-c-format #. Tag: para msgid "Debian on &arch-title; currently supports two subarchitectures: <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> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on their SiByte processor family. </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-&architecture; mailing list</ulink>." msgstr "" -#: hardware.xml:915 +#: hardware.xml:907 #, no-c-format #. Tag: para 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. The Broadcom BCM91250A evaluation board comes with an SB1250 chip with two SB-1 cores which are supported in SMP mode by this installer." msgstr "" -#: hardware.xml:922 +#: hardware.xml:914 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:939 +#: hardware.xml:931 #, no-c-format #. Tag: para -msgid "Debian on &arch-title; currently supports three subarchitectures: <itemizedlist> <listitem><para> DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This included the Cobalt Qube, RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on their SiByte processor family. </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-&architecture; mailing list</ulink>." +msgid "Debian on &arch-title; currently supports three subarchitectures: <itemizedlist> <listitem><para> DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This included the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on their SiByte processor family. </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-&architecture; mailing list</ulink>." msgstr "" -#: hardware.xml:973 +#: hardware.xml:965 #, no-c-format #. Tag: title msgid "CPU/Machine types" msgstr "" -#: hardware.xml:975 +#: hardware.xml:967 #, no-c-format #. Tag: para msgid "Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by the Debian installation system on little endian MIPS. The Debian installation system works on the following machines:" msgstr "" -#: hardware.xml:987 +#: hardware.xml:979 #, no-c-format #. Tag: entry msgid "System Type" msgstr "" -#: hardware.xml:987 +#: hardware.xml:979 #, no-c-format #. Tag: entry msgid "<entry>CPU</entry>" msgstr "" -#: hardware.xml:987 +#: hardware.xml:979 #, no-c-format #. Tag: entry msgid "Code-name" msgstr "" -#: hardware.xml:988 +#: hardware.xml:980 #, no-c-format #. Tag: entry msgid "Debian subarchitecture" msgstr "" -#: hardware.xml:994 +#: hardware.xml:986 #, no-c-format #. Tag: entry msgid "DECstation 5000/1xx" msgstr "" -#: hardware.xml:995 hardware.xml:1005 hardware.xml:1010 hardware.xml:1020 +#: hardware.xml:987 hardware.xml:997 hardware.xml:1002 hardware.xml:1012 #, no-c-format #. Tag: entry msgid "R3000" msgstr "" -#: hardware.xml:996 hardware.xml:1001 +#: hardware.xml:988 hardware.xml:993 #, no-c-format #. Tag: entry msgid "3MIN" msgstr "" -#: hardware.xml:999 +#: hardware.xml:991 #, no-c-format #. Tag: entry msgid "DECstation 5000/150" msgstr "" -#: hardware.xml:1000 hardware.xml:1025 +#: hardware.xml:992 hardware.xml:1017 #, no-c-format #. Tag: entry msgid "R4000" msgstr "" -#: hardware.xml:1004 +#: hardware.xml:996 #, no-c-format #. Tag: entry msgid "DECstation 5000/200" msgstr "" -#: hardware.xml:1006 +#: hardware.xml:998 #, no-c-format #. Tag: entry msgid "3MAX" msgstr "" -#: hardware.xml:1009 +#: hardware.xml:1001 #, no-c-format #. Tag: entry msgid "DECstation 5000/240" msgstr "" -#: hardware.xml:1011 hardware.xml:1016 +#: hardware.xml:1003 hardware.xml:1008 #, no-c-format #. Tag: entry msgid "3MAX+" msgstr "" -#: hardware.xml:1014 +#: hardware.xml:1006 #, no-c-format #. Tag: entry msgid "DECstation 5000/260" msgstr "" -#: hardware.xml:1015 +#: hardware.xml:1007 #, no-c-format #. Tag: entry msgid "R4400" msgstr "" -#: hardware.xml:1019 +#: hardware.xml:1011 #, no-c-format #. Tag: entry msgid "Personal DECstation 5000/xx" msgstr "" -#: hardware.xml:1021 hardware.xml:1026 +#: hardware.xml:1013 hardware.xml:1018 #, no-c-format #. Tag: entry msgid "Maxine" msgstr "" -#: hardware.xml:1024 +#: hardware.xml:1016 #, no-c-format #. Tag: entry msgid "Personal DECstation 5000/50" msgstr "" -#: hardware.xml:1031 +#: hardware.xml:1023 #, no-c-format #. Tag: para -msgid "All Cobalt machines are supported which have a serial console (which is needed for the installation)." +msgid "All Cobalt machines are supported. In the past, only machines with a serial console were supported (that is, all machines except for the Qube 2700, aka Qube1). However, installations are now also possible through SSH." msgstr "" -#: hardware.xml:1036 +#: hardware.xml:1030 #, no-c-format #. Tag: para msgid "The Broadcom BCM91250A evaluation board comes with an SB1250 chip with two SB-1 cores which are supported in SMP mode by this installer." msgstr "" -#: hardware.xml:1044 +#: hardware.xml:1038 #, no-c-format #. Tag: title msgid "Supported console options" msgstr "" -#: hardware.xml:1045 +#: hardware.xml:1039 #, no-c-format #. Tag: para msgid "Serial console is available on all supported DECstations (9600 bps, 8N1). For using serial console, you have to boot the installer image with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter (with <replaceable>x</replaceable> being the number of the serial port you have your terminal connected to — usually <literal>2</literal>, but <literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) local console is available with the PMAG-BA and the PMAGB-B graphics options." msgstr "" -#: hardware.xml:1056 +#: hardware.xml:1050 #, no-c-format #. Tag: para msgid "" @@ -1919,1219 +1919,1219 @@ msgid "" "</screen></informalexample> where the option <literal>-l</literal> (line) sets the serial port to use and <literal>-s</literal> (speed) sets the speed for the connection (9600 bits per second)." msgstr "" -#: hardware.xml:1074 +#: hardware.xml:1068 #, no-c-format #. Tag: para msgid "Both Cobalt and Broadcom BCM91250A use 115200 bps." msgstr "" -#: hardware.xml:1088 +#: hardware.xml:1082 #, no-c-format #. Tag: para msgid "There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh), PReP, APUS (Amiga Power-UP System), and CHRP machines. Each subarchitecture has its own boot methods. In addition, there are four different kernel flavours, supporting different CPU variants." msgstr "" -#: hardware.xml:1096 +#: hardware.xml:1090 #, no-c-format #. Tag: para msgid "Ports to other <emphasis>&architecture;</emphasis> architectures, such as the Be-Box and MBX architecture, are underway but not yet supported by Debian. We may have a 64-bit port in the future." msgstr "" -#: hardware.xml:1104 +#: hardware.xml:1098 #, no-c-format #. Tag: title msgid "Kernel Flavours" msgstr "" -#: hardware.xml:1106 +#: hardware.xml:1100 #, no-c-format #. Tag: para msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" -#: hardware.xml:1113 +#: hardware.xml:1107 #, no-c-format #. Tag: term msgid "<term>powerpc</term>" msgstr "" -#: hardware.xml:1114 +#: hardware.xml:1108 #, no-c-format #. Tag: para msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple Power Macintosh systems up to and including the G4 use one of these processors." msgstr "" -#: hardware.xml:1124 +#: hardware.xml:1118 #, no-c-format #. Tag: term msgid "power3" msgstr "" -#: hardware.xml:1125 +#: hardware.xml:1119 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1135 +#: hardware.xml:1129 #, no-c-format #. Tag: term msgid "power4" msgstr "" -#: hardware.xml:1136 +#: hardware.xml:1130 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1141 +#: hardware.xml:1135 #, no-c-format #. Tag: para msgid "The Apple G5 is also based on the POWER4 architecture, and uses this kernel flavour." msgstr "" -#: hardware.xml:1150 +#: hardware.xml:1144 #, no-c-format #. Tag: term msgid "<term>apus</term>" msgstr "" -#: hardware.xml:1151 +#: hardware.xml:1145 #, no-c-format #. Tag: para msgid "This kernel flavour supports the Amiga Power-UP System." msgstr "" -#: hardware.xml:1163 +#: hardware.xml:1157 #, no-c-format #. Tag: title msgid "Power Macintosh (pmac) subarchitecture" msgstr "" -#: hardware.xml:1165 +#: hardware.xml:1159 #, no-c-format #. Tag: para msgid "Apple (and briefly a few other manufacturers — Power Computing, for example) makes a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus, OldWorld PCI, and NewWorld." msgstr "" -#: hardware.xml:1172 +#: hardware.xml:1166 #, no-c-format #. Tag: para msgid "Macintosh computers using the 680x0 series of processors are not in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> or have a 3-digit model number such as Centris 650 or Quadra 950. Apple's pre-iMac PowerPC model numbers have four digits." msgstr "" -#: hardware.xml:1179 +#: hardware.xml:1173 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1212 +#: hardware.xml:1206 #, no-c-format #. Tag: para 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. The beige colored G3 systems are also OldWorld." msgstr "" -#: hardware.xml:1218 +#: hardware.xml:1212 #, no-c-format #. Tag: para msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases. 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 "" -#: hardware.xml:1226 +#: hardware.xml:1220 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1242 hardware.xml:1377 hardware.xml:1421 hardware.xml:1450 +#: hardware.xml:1236 hardware.xml:1371 hardware.xml:1415 hardware.xml:1444 #, no-c-format #. Tag: entry msgid "Model Name/Number" msgstr "" -#: hardware.xml:1243 +#: hardware.xml:1237 #, no-c-format #. Tag: entry msgid "Generation" msgstr "" -#: hardware.xml:1249 +#: hardware.xml:1243 #, no-c-format #. Tag: entry msgid "Apple" msgstr "" -#: hardware.xml:1250 +#: hardware.xml:1244 #, no-c-format #. Tag: entry msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" -#: hardware.xml:1251 hardware.xml:1254 hardware.xml:1257 hardware.xml:1260 hardware.xml:1263 hardware.xml:1266 hardware.xml:1269 hardware.xml:1272 hardware.xml:1275 hardware.xml:1278 hardware.xml:1281 hardware.xml:1284 hardware.xml:1287 hardware.xml:1290 hardware.xml:1293 hardware.xml:1296 +#: hardware.xml:1245 hardware.xml:1248 hardware.xml:1251 hardware.xml:1254 hardware.xml:1257 hardware.xml:1260 hardware.xml:1263 hardware.xml:1266 hardware.xml:1269 hardware.xml:1272 hardware.xml:1275 hardware.xml:1278 hardware.xml:1281 hardware.xml:1284 hardware.xml:1287 hardware.xml:1290 #, no-c-format #. Tag: entry msgid "NewWorld" msgstr "" -#: hardware.xml:1253 +#: hardware.xml:1247 #, no-c-format #. Tag: entry msgid "iMac Summer 2000, Early 2001" msgstr "" -#: hardware.xml:1256 +#: hardware.xml:1250 #, no-c-format #. Tag: entry msgid "iMac G5" msgstr "" -#: hardware.xml:1259 +#: hardware.xml:1253 #, no-c-format #. Tag: entry msgid "iBook, iBook SE, iBook Dual USB" msgstr "" -#: hardware.xml:1262 +#: hardware.xml:1256 #, no-c-format #. Tag: entry msgid "iBook2" msgstr "" -#: hardware.xml:1265 +#: hardware.xml:1259 #, no-c-format #. Tag: entry msgid "iBook G4" msgstr "" -#: hardware.xml:1268 +#: hardware.xml:1262 #, no-c-format #. Tag: entry msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" -#: hardware.xml:1271 +#: hardware.xml:1265 #, no-c-format #. Tag: entry msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" -#: hardware.xml:1274 +#: hardware.xml:1268 #, no-c-format #. Tag: entry msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" -#: hardware.xml:1277 +#: hardware.xml:1271 #, no-c-format #. Tag: entry msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" -#: hardware.xml:1280 +#: hardware.xml:1274 #, no-c-format #. Tag: entry msgid "Power Macintosh G5" msgstr "" -#: hardware.xml:1283 +#: hardware.xml:1277 #, no-c-format #. Tag: entry msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" -#: hardware.xml:1286 +#: hardware.xml:1280 #, no-c-format #. Tag: entry msgid "PowerBook G3 Lombard (1999)" msgstr "" -#: hardware.xml:1289 +#: hardware.xml:1283 #, no-c-format #. Tag: entry msgid "PowerBook G4 Titanium" msgstr "" -#: hardware.xml:1292 +#: hardware.xml:1286 #, no-c-format #. Tag: entry msgid "PowerBook G4 Aluminum" msgstr "" -#: hardware.xml:1295 +#: hardware.xml:1289 #, no-c-format #. Tag: entry msgid "Xserve G5" msgstr "" -#: hardware.xml:1298 +#: hardware.xml:1292 #, no-c-format #. Tag: entry msgid "Performa 4400, 54xx, 5500" msgstr "" -#: hardware.xml:1299 hardware.xml:1302 hardware.xml:1305 hardware.xml:1308 hardware.xml:1311 hardware.xml:1314 hardware.xml:1317 hardware.xml:1320 hardware.xml:1323 hardware.xml:1326 hardware.xml:1329 hardware.xml:1332 hardware.xml:1338 hardware.xml:1341 hardware.xml:1347 hardware.xml:1353 hardware.xml:1359 +#: hardware.xml:1293 hardware.xml:1296 hardware.xml:1299 hardware.xml:1302 hardware.xml:1305 hardware.xml:1308 hardware.xml:1311 hardware.xml:1314 hardware.xml:1317 hardware.xml:1320 hardware.xml:1323 hardware.xml:1326 hardware.xml:1332 hardware.xml:1335 hardware.xml:1341 hardware.xml:1347 hardware.xml:1353 #, no-c-format #. Tag: entry msgid "OldWorld" msgstr "" -#: hardware.xml:1301 +#: hardware.xml:1295 #, no-c-format #. Tag: entry msgid "Performa 6360, 6400, 6500" msgstr "" -#: hardware.xml:1304 +#: hardware.xml:1298 #, no-c-format #. Tag: entry msgid "Power Macintosh 4400, 5400" msgstr "" -#: hardware.xml:1307 +#: hardware.xml:1301 #, no-c-format #. Tag: entry msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" -#: hardware.xml:1310 +#: hardware.xml:1304 #, no-c-format #. Tag: entry msgid "Power Macintosh 8200, 8500, 8600" msgstr "" -#: hardware.xml:1313 +#: hardware.xml:1307 #, no-c-format #. Tag: entry msgid "Power Macintosh 9500, 9600" msgstr "" -#: hardware.xml:1316 +#: hardware.xml:1310 #, no-c-format #. Tag: entry msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" -#: hardware.xml:1319 +#: hardware.xml:1313 #, no-c-format #. Tag: entry msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" -#: hardware.xml:1322 +#: hardware.xml:1316 #, no-c-format #. Tag: entry msgid "PowerBook 2400, 3400, 3500" msgstr "" -#: hardware.xml:1325 +#: hardware.xml:1319 #, no-c-format #. Tag: entry msgid "PowerBook G3 Wallstreet (1998)" msgstr "" -#: hardware.xml:1328 +#: hardware.xml:1322 #, no-c-format #. Tag: entry msgid "Twentieth Anniversary Macintosh" msgstr "" -#: hardware.xml:1331 +#: hardware.xml:1325 #, no-c-format #. Tag: entry msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" -#: hardware.xml:1336 +#: hardware.xml:1330 #, no-c-format #. Tag: entry msgid "Power Computing" msgstr "" -#: hardware.xml:1337 +#: hardware.xml:1331 #, no-c-format #. Tag: entry msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" -#: hardware.xml:1340 +#: hardware.xml:1334 #, no-c-format #. Tag: entry msgid "PowerCenter / Pro, PowerCurve" msgstr "" -#: hardware.xml:1345 +#: hardware.xml:1339 #, no-c-format #. Tag: entry msgid "UMAX" msgstr "" -#: hardware.xml:1346 +#: hardware.xml:1340 #, no-c-format #. Tag: entry msgid "C500, C600, J700, S900" msgstr "" -#: hardware.xml:1351 +#: hardware.xml:1345 #, no-c-format #. Tag: entry msgid "<entry>APS</entry>" msgstr "" -#: hardware.xml:1352 +#: hardware.xml:1346 #, no-c-format #. Tag: entry msgid "APS Tech M*Power 604e/2000" msgstr "" -#: hardware.xml:1357 hardware.xml:1383 +#: hardware.xml:1351 hardware.xml:1377 #, no-c-format #. Tag: entry msgid "Motorola" msgstr "" -#: hardware.xml:1358 +#: hardware.xml:1352 #, no-c-format #. Tag: entry msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" -#: hardware.xml:1367 +#: hardware.xml:1361 #, no-c-format #. Tag: title msgid "PReP subarchitecture" msgstr "" -#: hardware.xml:1384 +#: hardware.xml:1378 #, no-c-format #. Tag: entry msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" -#: hardware.xml:1386 +#: hardware.xml:1380 #, no-c-format #. Tag: entry msgid "MPC 7xx, 8xx" msgstr "" -#: hardware.xml:1388 +#: hardware.xml:1382 #, no-c-format #. Tag: entry msgid "MTX, MTX+" msgstr "" -#: hardware.xml:1390 +#: hardware.xml:1384 #, no-c-format #. Tag: entry msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" -#: hardware.xml:1392 +#: hardware.xml:1386 #, no-c-format #. Tag: entry msgid "MCP(N)750" msgstr "" -#: hardware.xml:1396 hardware.xml:1427 +#: hardware.xml:1390 hardware.xml:1421 #, no-c-format #. Tag: entry msgid "IBM RS/6000" msgstr "" -#: hardware.xml:1397 +#: hardware.xml:1391 #, no-c-format #. Tag: entry msgid "40P, 43P" msgstr "" -#: hardware.xml:1399 +#: hardware.xml:1393 #, no-c-format #. Tag: entry msgid "Power 830/850/860 (6070, 6050)" msgstr "" -#: hardware.xml:1401 +#: hardware.xml:1395 #, no-c-format #. Tag: entry msgid "6030, 7025, 7043" msgstr "" -#: hardware.xml:1403 +#: hardware.xml:1397 #, no-c-format #. Tag: entry msgid "p640" msgstr "" -#: hardware.xml:1411 +#: hardware.xml:1405 #, no-c-format #. Tag: title msgid "CHRP subarchitecture" msgstr "" -#: hardware.xml:1428 +#: hardware.xml:1422 #, no-c-format #. Tag: entry msgid "B50, 43P-150, 44P" msgstr "" -#: hardware.xml:1431 +#: hardware.xml:1425 #, no-c-format #. Tag: entry msgid "Genesi" msgstr "" -#: hardware.xml:1432 +#: hardware.xml:1426 #, no-c-format #. Tag: entry msgid "Pegasos I, Pegasos II" msgstr "" -#: hardware.xml:1440 +#: hardware.xml:1434 #, no-c-format #. Tag: title msgid "APUS subarchitecture" msgstr "" -#: hardware.xml:1456 +#: hardware.xml:1450 #, no-c-format #. Tag: entry msgid "Amiga Power-UP Systems (APUS)" msgstr "" -#: hardware.xml:1457 +#: hardware.xml:1451 #, no-c-format #. Tag: entry msgid "A1200, A3000, A4000" msgstr "" -#: hardware.xml:1470 +#: hardware.xml:1464 #, no-c-format #. Tag: title msgid "S/390 and zSeries machine types" msgstr "" -#: hardware.xml:1471 +#: hardware.xml:1465 #, no-c-format #. Tag: para msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/documentation-2.4.shtml\">technical details web page</ulink> at <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/index.shtml\">developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance." msgstr "" -#: hardware.xml:1494 +#: hardware.xml:1488 #, no-c-format #. Tag: para msgid "Currently the <emphasis>&architecture;</emphasis> port supports several types of Sparc systems. The most common identifiers for Sparc systems are sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not support very old sun4 hardware. However, the other systems are supported. Sun4d has been tested the least of these, so expect possible problems with regard to the kernel stability. Sun4c and Sun4m, the most common of the older Sparc hardware, includes such systems as SparcStation 1, 1+, IPC, IPX and the SparcStation LX, 5, 10, and 20, respectively. The UltraSPARC class systems fall under the sun4u identifier, and are supported using the sun4u set of install images. Some systems that fall under these supported identifiers are known to not be supported. Known unsupported systems are the AP1000 multicomputer and the Tadpole Sparcbook 1. See the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARCProcessors FAQ</ulink> for complete information." msgstr "" -#: hardware.xml:1514 +#: hardware.xml:1508 #, no-c-format #. Tag: title msgid "Memory Configuration" msgstr "" -#: hardware.xml:1515 +#: hardware.xml:1509 #, no-c-format #. Tag: para msgid "Some older Sun workstations, notably the Sun IPX and Sun IPC have memory banks located at fixed locations in physical memory. Thus if the banks are not filled gaps will exist in the physical memory space. The Linux installation requires a contiguous memory block into which to load the kernel and the initial RAMdisk. If this is not available a <quote>Data Access Exception</quote> will result." msgstr "" -#: hardware.xml:1524 +#: hardware.xml:1518 #, no-c-format #. Tag: para msgid "Thus you must configure the memory so that the lowest memory block is contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks are mapped in at 16Mb boundaries. In effect this means that you must have a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. In this case 4Mb is <emphasis>not</emphasis> sufficient." msgstr "" -#: hardware.xml:1532 +#: hardware.xml:1526 #, no-c-format #. Tag: para msgid "Example: In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS connectors]. You must therefore install the 16Mb SIMM in bank 0; it is then recommended to install the 4Mb SIMM in bank 2." msgstr "" -#: hardware.xml:1543 +#: hardware.xml:1537 #, no-c-format #. Tag: title msgid "Graphics Configuration" msgstr "" -#: hardware.xml:1544 +#: hardware.xml:1538 #, no-c-format #. Tag: para msgid "Especially in the case of older Sun workstations, it is very common for there to be an onboard framebuffer which has been superseded (for example the bwtwo on a sun IPC), and an SBUS card containing a later probably accelerated buffer is then plugged in to an SBUS slot. Under Solaris/SunOS this causes no problems because both cards are initialized." msgstr "" -#: hardware.xml:1553 +#: hardware.xml:1547 #, no-c-format #. Tag: para msgid "However with Linux this can cause a problem, in that the boot PROM monitor may display its output on this additional card; however the linux kernel boot messages may then be directed to the original on board framebuffer, leaving <emphasis>no</emphasis> error messages on the screen, with the machine apparently stuck loading the RAMdisk." msgstr "" -#: hardware.xml:1561 +#: hardware.xml:1555 #, no-c-format #. Tag: para msgid "To avoid this problem, connect the monitor (if required) to the video card in the lowest numbered SBUS slot (on motherboard card counts as below external slots). Alternatively it is possible to use a serial console." msgstr "" -#: hardware.xml:1573 +#: hardware.xml:1567 #, no-c-format #. Tag: title msgid "Graphics Card" msgstr "" -#: hardware.xml:1575 +#: hardware.xml:1569 #, no-c-format #. Tag: para msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document." msgstr "" -#: hardware.xml:1583 +#: hardware.xml:1577 #, no-c-format #. Tag: para msgid "Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian &release; ships with X.Org version &x11ver;." msgstr "" -#: hardware.xml:1592 +#: hardware.xml:1586 #, no-c-format #. Tag: para msgid "The X.Org X11 window system is only supported on the SGI Indy. The Broadcom BCM91250A evaluation board has standard 3.3v PCI slots and supports VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for the BCM91250A is available." msgstr "" -#: hardware.xml:1600 +#: hardware.xml:1594 #, no-c-format #. Tag: para msgid "The X.Org X11 window system is supported on some DECstation models. The Broadcom BCM91250A evaluation board has standard 3.3v PCI slots and supports VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for the BCM91250A is available." msgstr "" -#: hardware.xml:1612 +#: hardware.xml:1606 #, no-c-format #. Tag: title msgid "Laptops" msgstr "" -#: hardware.xml:1613 +#: hardware.xml:1607 #, no-c-format #. Tag: para msgid "Laptops are also supported. Laptops are often specialized or contain proprietary hardware. To see if your particular laptop works well with GNU/Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>" msgstr "" -#: hardware.xml:1625 hardware.xml:1650 hardware.xml:1673 +#: hardware.xml:1619 hardware.xml:1644 hardware.xml:1667 #, no-c-format #. Tag: title msgid "Multiple Processors" msgstr "" -#: hardware.xml:1627 +#: hardware.xml:1621 #, no-c-format #. Tag: para msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is supported for this architecture. The standard Debian &release; kernel image was compiled with SMP support. This should not prevent installation, since the SMP kernel should boot on non-SMP systems; the kernel will simply cause a bit more overhead." msgstr "" -#: hardware.xml:1635 +#: hardware.xml:1629 #, no-c-format #. Tag: para msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" -#: hardware.xml:1651 +#: hardware.xml:1645 #, no-c-format #. Tag: para msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is supported for this architecture. However, the standard Debian &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" -#: hardware.xml:1660 +#: hardware.xml:1654 #, no-c-format #. Tag: para msgid "In order to take advantage of multiple processors, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" -#: hardware.xml:1674 +#: hardware.xml:1668 #, no-c-format #. Tag: para msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is supported 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 "" -#: hardware.xml:1684 +#: hardware.xml:1678 #, no-c-format #. Tag: para 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. You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" -#: hardware.xml:1705 +#: hardware.xml:1699 #, no-c-format #. Tag: title msgid "Installation Media" msgstr "" -#: hardware.xml:1707 +#: hardware.xml:1701 #, no-c-format #. Tag: para msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used to install Debian. There is a whole chapter devoted 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 "" -#: hardware.xml:1718 +#: hardware.xml:1712 #, no-c-format #. Tag: title msgid "Floppies" msgstr "" -#: hardware.xml:1719 +#: hardware.xml:1713 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1725 +#: hardware.xml:1719 #, no-c-format #. Tag: para msgid "For CHRP, floppy support is currently broken." msgstr "" -#: hardware.xml:1732 +#: hardware.xml:1726 #, no-c-format #. Tag: title msgid "CD-ROM/DVD-ROM" msgstr "" -#: hardware.xml:1734 +#: hardware.xml:1728 #, no-c-format #. Tag: para msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI." msgstr "" -#: hardware.xml:1741 +#: hardware.xml:1735 #, no-c-format #. Tag: para msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>." msgstr "" -#: hardware.xml:1753 +#: hardware.xml:1747 #, no-c-format #. Tag: para msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the boot disks (such as Mitsumi and Matsushita drives). However, these models might require special boot parameters or other massaging to get them to work, and booting off these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux." msgstr "" -#: hardware.xml:1763 +#: hardware.xml:1757 #, no-c-format #. Tag: para msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" -#: hardware.xml:1768 +#: hardware.xml:1762 #, no-c-format #. Tag: para msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as the controller is supported by the SRM console. This rules out many add-on controller cards, but most integrated IDE and SCSI chips and controller cards that were provided by the manufacturer can be expected to work. To find out whether your device is supported from the SRM console, see the <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>." msgstr "" -#: hardware.xml:1777 +#: hardware.xml:1771 #, no-c-format #. Tag: para msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-ROMs are also supported." msgstr "" -#: hardware.xml:1782 +#: hardware.xml:1776 #, no-c-format #. Tag: para 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-DROM drives sold for 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. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives." msgstr "" -#: hardware.xml:1795 +#: hardware.xml:1789 #, no-c-format #. Tag: para msgid "On DECstations, 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-DROM drives sold for 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." msgstr "" -#: hardware.xml:1804 +#: hardware.xml:1798 #, no-c-format #. Tag: para msgid "CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal DECstation 5000/50)." msgstr "" -#: hardware.xml:1813 +#: hardware.xml:1807 #, no-c-format #. Tag: para msgid "To boot from CD, issue the command <userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware prompt, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot (3 on most DECstations) and <replaceable>id</replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" -#: hardware.xml:1825 +#: hardware.xml:1819 #, no-c-format #. Tag: userinput msgid "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=value1 param2=value2 ..." msgstr "" -#: hardware.xml:1832 +#: hardware.xml:1826 #, no-c-format #. Tag: title msgid "Hard Disk" msgstr "" -#: hardware.xml:1834 +#: hardware.xml:1828 #, no-c-format #. Tag: para msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk." msgstr "" -#: hardware.xml:1840 +#: hardware.xml:1834 #, no-c-format #. Tag: para msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines." msgstr "" -#: hardware.xml:1845 +#: hardware.xml:1839 #, no-c-format #. Tag: para msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)." msgstr "" -#: hardware.xml:1853 +#: hardware.xml:1847 #, no-c-format #. Tag: title msgid "USB Memory Stick" msgstr "" -#: hardware.xml:1855 +#: hardware.xml:1849 #, no-c-format #. Tag: para msgid "Many Debian boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives." msgstr "" -#: hardware.xml:1867 +#: hardware.xml:1861 #, no-c-format #. Tag: title msgid "Network" msgstr "" -#: hardware.xml:1869 +#: hardware.xml:1863 #, no-c-format #. Tag: para msgid "You can also <emphasis>boot</emphasis> your system over the network. <phrase arch=\"mips\">This is the preferred installation technique for Mips.</phrase>" msgstr "" -#: hardware.xml:1875 +#: hardware.xml:1869 #, no-c-format #. Tag: para msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." msgstr "" -#: hardware.xml:1880 +#: hardware.xml:1874 #, no-c-format #. Tag: para msgid "After the operating system kernel is installed, you can install the rest of your system via any sort of network connection (including PPP after installation of the base system), via FTP or HTTP." msgstr "" -#: hardware.xml:1889 +#: hardware.xml:1883 #, no-c-format #. Tag: title msgid "Un*x or GNU system" msgstr "" -#: hardware.xml:1891 +#: hardware.xml:1885 #, no-c-format #. Tag: para msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of the manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." msgstr "" -#: hardware.xml:1903 +#: hardware.xml:1897 #, no-c-format #. Tag: title msgid "Supported Storage Systems" msgstr "" -#: hardware.xml:1905 +#: hardware.xml:1899 #, no-c-format #. Tag: para msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware." msgstr "" -#: hardware.xml:1915 +#: hardware.xml:1909 #, no-c-format #. Tag: para msgid "Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and drives, USB, and FireWire. The file systems supported include FAT, Win-32 FAT extensions (VFAT), and NTFS, among others." msgstr "" -#: hardware.xml:1922 +#: hardware.xml:1916 #, no-c-format #. Tag: para msgid "The disk interfaces that emulate the <quote>AT</quote> hard disk interface which are often called MFM, RLL, IDE, or ATA are supported. Very old 8 bit hard disk controllers used in the IBM XT computer are supported only as a module. SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." msgstr "" -#: hardware.xml:1932 +#: hardware.xml:1926 #, no-c-format #. Tag: para msgid "Pretty much all storage systems supported by the Linux kernel are supported by the Debian installation system. Note that the current Linux kernel does not support floppies on the Macintosh at all, and the Debian installation system doesn't support floppies for Amigas. Also supported on the Atari is the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) file system. Amigas support the FAT file system, and HFS as a module." msgstr "" -#: hardware.xml:1942 +#: hardware.xml:1936 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1975 +#: hardware.xml:1969 #, no-c-format #. Tag: para msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This includes both SCSI and IDE disks. Note, however, that on many systems, the SRM console is unable to boot from IDE drives, and the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;\"></ulink> for more information on booting the Jensen)" msgstr "" -#: hardware.xml:1984 +#: hardware.xml:1978 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1990 +#: hardware.xml:1984 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:1996 +#: hardware.xml:1990 #, no-c-format #. Tag: para msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" -#: hardware.xml:2001 +#: hardware.xml:1995 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2018 +#: hardware.xml:2012 #, no-c-format #. Tag: title msgid "Peripherals and Other Hardware" msgstr "" -#: hardware.xml:2019 +#: hardware.xml:2013 #, no-c-format #. Tag: para msgid "Linux supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system." msgstr "" -#: hardware.xml:2025 +#: hardware.xml:2019 #, no-c-format #. Tag: para msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)." msgstr "" -#: hardware.xml:2031 +#: hardware.xml:2025 #, no-c-format #. Tag: para msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux." msgstr "" -#: hardware.xml:2037 +#: hardware.xml:2031 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2043 +#: hardware.xml:2037 #, no-c-format #. Tag: para msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors." msgstr "" -#: hardware.xml:2048 +#: hardware.xml:2042 #, no-c-format #. Tag: para msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." msgstr "" -#: hardware.xml:2057 +#: hardware.xml:2051 #, no-c-format #. Tag: title msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" -#: hardware.xml:2059 +#: hardware.xml:2053 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2067 +#: hardware.xml:2061 #, no-c-format #. Tag: para msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all." msgstr "" -#: hardware.xml:2072 +#: hardware.xml:2066 #, no-c-format #. Tag: para 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 "" -#: hardware.xml:2080 +#: hardware.xml:2074 #, no-c-format #. Tag: para msgid "Whether or not you are purchasing a system with Linux bundled, or even a used system, it is still important to check that your hardware is supported by the Linux kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a Linux system. Support Linux-friendly hardware vendors." msgstr "" -#: hardware.xml:2091 +#: hardware.xml:2085 #, no-c-format #. Tag: title msgid "Avoid Proprietary or Closed Hardware" msgstr "" -#: hardware.xml:2092 +#: hardware.xml:2086 #, no-c-format #. Tag: para msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the Linux source code." msgstr "" -#: hardware.xml:2099 +#: hardware.xml:2093 #, no-c-format #. Tag: para msgid "Another example is the proprietary hardware in the older Macintosh line. In fact, no specifications or documentation have ever been released for any Macintosh hardware, most notably the ADB controller (used by the mouse and keyboard), the floppy controller, and all acceleration and CLUT manipulation of the video hardware (though we do now support CLUT manipulation on nearly all internal video chips). In a nutshell, this explains why the Macintosh Linux port lags behind other Linux ports." msgstr "" -#: hardware.xml:2110 +#: hardware.xml:2104 #, no-c-format #. Tag: para msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under Linux. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market." msgstr "" -#: hardware.xml:2122 +#: hardware.xml:2116 #, no-c-format #. Tag: title msgid "Windows-specific Hardware" msgstr "" -#: hardware.xml:2123 +#: hardware.xml:2117 #, no-c-format #. Tag: para msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence." msgstr "" -#: hardware.xml:2136 +#: hardware.xml:2130 #, no-c-format #. Tag: para msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes its being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" -#: hardware.xml:2157 +#: hardware.xml:2151 #, no-c-format #. Tag: para msgid "You can help this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>." msgstr "" -#: hardware.xml:2170 +#: hardware.xml:2164 #, no-c-format #. Tag: title msgid "Fake or <quote>Virtual</quote> Parity RAM" msgstr "" -#: hardware.xml:2171 +#: hardware.xml:2165 #, no-c-format #. Tag: para msgid "If you ask for Parity RAM in a computer store, you'll probably get <emphasis>virtual parity</emphasis> memory modules instead of <emphasis>true parity</emphasis> ones. Virtual parity SIMMs can often (but not always) be distinguished because they only have one more chip than an equivalent non-parity SIMM, and that one extra chip is smaller than all the others. Virtual-parity SIMMs work exactly like non-parity memory. They can't tell you when you have a single-bit RAM error the way true-parity SIMMs do in a motherboard that implements parity. Don't ever pay more for a virtual-parity SIMM than a non-parity one. Do expect to pay a little more for true-parity SIMMs, because you are actually buying one extra bit of memory for every 8 bits." msgstr "" -#: hardware.xml:2186 +#: hardware.xml:2180 #, no-c-format #. Tag: para msgid "If you want complete information on &arch-title; RAM issues, and what is the best RAM to buy, see the <ulink url=\"&url-pc-hw-faq;\">PC Hardware FAQ</ulink>." msgstr "" -#: hardware.xml:2192 +#: hardware.xml:2186 #, no-c-format #. Tag: para msgid "Most, if not all, Alpha systems require true-parity RAM." msgstr "" -#: hardware.xml:2207 +#: hardware.xml:2201 #, no-c-format #. Tag: title msgid "Memory and Disk Space Requirements" msgstr "" -#: hardware.xml:2209 +#: hardware.xml:2203 #, no-c-format #. Tag: para msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. For a minimal console-based system (all standard packages), 250MB is required. If you want to install a reasonable amount of software, including the X Window System, and some development programs and libraries, you'll need at least 400MB. For a more or less complete desktop system, you'll need a few gigabytes." msgstr "" -#: hardware.xml:2218 +#: hardware.xml:2212 #, no-c-format #. Tag: para msgid "On the Amiga the size of FastRAM is relevant towards the total memory requirements. Also, using Zorro cards with 16-bit RAM is not supported; you'll need 32-bit RAM. The <command>amiboot</command> program can be used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically." msgstr "" -#: hardware.xml:2227 +#: hardware.xml:2221 #, no-c-format #. Tag: para msgid "On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many users have reported problems running the kernel itself in Fast RAM, so the Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM." msgstr "" -#: hardware.xml:2235 +#: hardware.xml:2229 #, no-c-format #. Tag: para msgid "On the Macintosh, care should be taken on machines with RAM-based video (RBV). The RAM segment at physical address 0 is used as screen memory, making the default load position for the kernel unavailable. The alternate RAM segment used for kernel and RAMdisk must be at least 4 MB." msgstr "" -#: hardware.xml:2245 +#: hardware.xml:2239 #, no-c-format #. Tag: emphasis msgid "FIXME: is this still true?" msgstr "" -#: hardware.xml:2256 +#: hardware.xml:2250 #, no-c-format #. Tag: title msgid "Network Connectivity Hardware" msgstr "" -#: hardware.xml:2258 +#: hardware.xml:2252 #, no-c-format #. Tag: para msgid "Most PCI and many older ISA network cards are supported. Some network interface cards are not supported by most Debian installation disks, such as AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider & Koch G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) network cards are not supported by the standard installation system, but see <ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) instructions. FDDI networks are also not supported by the installation disks, both cards and protocols." msgstr "" -#: hardware.xml:2277 +#: hardware.xml:2271 #, no-c-format #. Tag: para msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;." msgstr "" -#: hardware.xml:2285 +#: hardware.xml:2279 #, no-c-format #. Tag: para msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details." msgstr "" -#: hardware.xml:2294 +#: hardware.xml:2288 #, no-c-format #. Tag: para msgid "The following network interface cards (NICs) are supported from the bootable kernel directly:" msgstr "" -#: hardware.xml:2300 +#: hardware.xml:2294 #, no-c-format #. Tag: para msgid "Sun LANCE" msgstr "" -#: hardware.xml:2306 +#: hardware.xml:2300 #, no-c-format #. Tag: para msgid "Sun Happy Meal" msgstr "" -#: hardware.xml:2314 +#: hardware.xml:2308 #, no-c-format #. Tag: para msgid "The following network interface cards are supported as modules. They can be enabled once the drivers are installed during the setup. However, due to the magic of OpenPROM, you still should be able to boot from these devices:" msgstr "" -#: hardware.xml:2322 +#: hardware.xml:2316 #, no-c-format #. Tag: para msgid "Sun BigMAC" msgstr "" -#: hardware.xml:2328 +#: hardware.xml:2322 #, no-c-format #. Tag: para msgid "Sun QuadEthernet" msgstr "" -#: hardware.xml:2333 +#: hardware.xml:2327 #, no-c-format #. Tag: para msgid "MyriCOM Gigabit Ethernet" msgstr "" -#: hardware.xml:2340 hardware.xml:2346 hardware.xml:2352 hardware.xml:2358 hardware.xml:2364 +#: hardware.xml:2334 hardware.xml:2340 hardware.xml:2346 hardware.xml:2352 hardware.xml:2358 #, no-c-format #. Tag: para msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module." msgstr "" -#: hardware.xml:2370 +#: hardware.xml:2364 #, no-c-format #. Tag: para msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work." msgstr "" -#: hardware.xml:2376 +#: hardware.xml:2370 #, no-c-format #. Tag: para msgid "Any network interface card (NIC) supported by the Linux kernel are also be supported by the boot disks. All network drivers are compiled as modules so you need to load one first during the initial network setup. The list of supported network devices is:" msgstr "" -#: hardware.xml:2384 +#: hardware.xml:2378 #, no-c-format #. Tag: para msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" -#: hardware.xml:2389 +#: hardware.xml:2383 #, no-c-format #. Tag: para msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" -#: hardware.xml:2394 +#: hardware.xml:2388 #, no-c-format #. Tag: para msgid "Inter-User Communication Vehicle (IUCV) — available for VM guests only" msgstr "" -#: hardware.xml:2399 +#: hardware.xml:2393 #, no-c-format #. Tag: para msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" -#: hardware.xml:2408 +#: hardware.xml:2402 #, no-c-format #. Tag: para -msgid "The following network interface cards are supported directly by the boot disks on NetWinder and CATS machines:" +msgid "The following network interface cards are supported directly by the boot disks on Netwinder and CATS machines:" msgstr "" -#: hardware.xml:2414 +#: hardware.xml:2408 #, no-c-format #. Tag: para msgid "PCI-based NE2000" msgstr "" -#: hardware.xml:2420 +#: hardware.xml:2414 #, no-c-format #. Tag: para msgid "DECchip Tulip" msgstr "" -#: hardware.xml:2427 +#: hardware.xml:2421 #, no-c-format #. Tag: para msgid "The following network interface cards are supported directly by the boot disks on RiscPCs:" msgstr "" -#: hardware.xml:2433 +#: hardware.xml:2427 #, no-c-format #. Tag: para msgid "Ether1" msgstr "" -#: hardware.xml:2438 +#: hardware.xml:2432 #, no-c-format #. Tag: para msgid "Ether3" msgstr "" -#: hardware.xml:2443 +#: hardware.xml:2437 #, no-c-format #. Tag: para msgid "EtherH" msgstr "" -#: hardware.xml:2450 +#: hardware.xml:2444 #, no-c-format #. Tag: para msgid "If your card is mentioned in the lists above, the complete installation can be carried out from the network with no need for CD-ROMs or floppy disks." msgstr "" -#: hardware.xml:2456 +#: hardware.xml:2450 #, no-c-format #. Tag: para msgid "Any other network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module; this means that you will have to install the operating system kernel and modules using some other media." diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot index 422ecd239..48b681b92 100644 --- a/po/pot/install-methods.pot +++ b/po/pot/install-methods.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2006-02-07 15:07+0000\n" +"POT-Creation-Date: 2006-03-07 20:15+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" @@ -119,13 +119,13 @@ msgstr "" #: install-methods.xml:165 #, no-c-format #. Tag: title -msgid "NetWinder Installation Files" +msgid "Netwinder Installation Files" msgstr "" #: install-methods.xml:166 #, no-c-format #. Tag: para -msgid "The easiest way to boot a NetWinder is over the network, using the supplied TFTP image &netwinder-boot-img;." +msgid "The easiest way to boot a Netwinder is over the network, using the supplied TFTP image &netwinder-boot-img;." msgstr "" #: install-methods.xml:175 @@ -137,88 +137,100 @@ msgstr "" #: install-methods.xml:176 #, no-c-format #. Tag: para -msgid "The only supported boot method for CATS is to use the combined image &cats-boot-img;. This can be loaded from any device accessible to the Cyclone bootloader." +msgid "CATS be be booted either via the network or from CD-ROM. The kernel and initrd can be obtained from &cats-boot-img;." msgstr "" -#: install-methods.xml:221 +#: install-methods.xml:185 +#, no-c-format +#. Tag: title +msgid "NSLU2 Installation Files" +msgstr "" + +#: install-methods.xml:186 +#, no-c-format +#. Tag: para +msgid "A firmware image is provided for the Linksys NSLU2 which will automatically boot debian-installer. This firmware image an be obtained from &nslu2-firmware-img;." +msgstr "" + +#: install-methods.xml:232 #, no-c-format #. Tag: title msgid "Choosing a Kernel" msgstr "" -#: install-methods.xml:223 +#: install-methods.xml:234 #, no-c-format #. Tag: para msgid "Some m68k subarchs have a choice of kernels to install. In general we recommend trying the most recent version first. If your subarch or machine needs to use a 2.2.x kernel, make sure you choose one of the images that supports 2.2.x kernels (see the <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink>)." msgstr "" -#: install-methods.xml:232 +#: install-methods.xml:243 #, no-c-format #. Tag: para msgid "All of the m68k images for use with 2.2.x kernels, require the kernel parameter &ramdisksize;." msgstr "" -#: install-methods.xml:250 +#: install-methods.xml:261 #, no-c-format #. Tag: title msgid "Creating an IPL tape" msgstr "" -#: install-methods.xml:252 +#: install-methods.xml:263 #, no-c-format #. Tag: para msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>," msgstr "" -#: install-methods.xml:276 +#: install-methods.xml:287 #, no-c-format #. Tag: title msgid "Creating Floppies from Disk Images" msgstr "" -#: install-methods.xml:277 +#: install-methods.xml:288 #, no-c-format #. Tag: para msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means." msgstr "" -#: install-methods.xml:282 +#: install-methods.xml:293 #, no-c-format #. Tag: para msgid "Floppy disk booting reportedly fails on Mac USB floppy drives." msgstr "" -#: install-methods.xml:286 +#: install-methods.xml:297 #, no-c-format #. Tag: para msgid "Floppy disk booting is not supported on Amigas or 68k Macs." msgstr "" -#: install-methods.xml:291 +#: install-methods.xml:302 #, no-c-format #. Tag: para msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy." msgstr "" -#: install-methods.xml:302 +#: install-methods.xml:313 #, no-c-format #. Tag: para msgid "There are different techniques for creating floppies from disk images, which depend on your platform. This section describes how to create floppies from disk images on different platforms." msgstr "" -#: install-methods.xml:308 +#: install-methods.xml:319 #, no-c-format #. Tag: para msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally." msgstr "" -#: install-methods.xml:316 +#: install-methods.xml:327 #, no-c-format #. Tag: title msgid "Writing Disk Images From a Linux or Unix System" msgstr "" -#: install-methods.xml:317 +#: install-methods.xml:328 #, no-c-format #. Tag: para msgid "" @@ -227,253 +239,253 @@ msgid "" "</screen></informalexample> where <replaceable>filename</replaceable> is one of the floppy disk image files (see <xref linkend=\"downloading-files\"/> for what <replaceable>filename</replaceable> should be). <filename>/dev/fd0</filename> is a commonly used name of the floppy disk device, it may be different on your workstation <phrase arch=\"sparc\">(on Solaris, it is <filename>/dev/fd/0</filename>)</phrase>. The command may return to the prompt before Unix has finished writing the floppy disk, so look for the disk-in-use light on the floppy drive and be sure that the light is out and the disk has stopped revolving before you remove it from the drive. On some systems, you'll have to run a command to eject the floppy from the drive <phrase arch=\"sparc\">(on Solaris, use <command>eject</command>, see the manual page)</phrase>." msgstr "" -#: install-methods.xml:341 +#: install-methods.xml:352 #, no-c-format #. Tag: para msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>" msgstr "" -#: install-methods.xml:362 +#: install-methods.xml:373 #, no-c-format #. Tag: para msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it." msgstr "" -#: install-methods.xml:380 +#: install-methods.xml:391 #, no-c-format #. Tag: title msgid "Writing Disk Images From DOS, Windows, or OS/2" msgstr "" -#: install-methods.xml:382 +#: install-methods.xml:393 #, no-c-format #. Tag: para msgid "If you have access to an i386 machine, you can use one of the following programs to copy images to floppies." msgstr "" -#: install-methods.xml:387 +#: install-methods.xml:398 #, no-c-format #. Tag: para msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work." msgstr "" -#: install-methods.xml:395 +#: install-methods.xml:406 #, no-c-format #. Tag: para msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory." msgstr "" -#: install-methods.xml:401 +#: install-methods.xml:412 #, no-c-format #. Tag: para msgid "These tools can be found on the Official Debian CD-ROMs under the <filename>/tools</filename> directory." msgstr "" -#: install-methods.xml:414 +#: install-methods.xml:425 #, no-c-format #. Tag: title msgid "Writing Disk Images on Atari Systems" msgstr "" -#: install-methods.xml:415 +#: install-methods.xml:426 #, no-c-format #. Tag: para msgid "You'll find the &rawwrite.ttp; program in the same directory as the floppy disk images. Start the program by double clicking on the program icon, and type in the name of the floppy image file you want written to the floppy at the TOS program command line dialog box." msgstr "" -#: install-methods.xml:426 +#: install-methods.xml:437 #, no-c-format #. Tag: title msgid "Writing Disk Images on Macintosh Systems" msgstr "" -#: install-methods.xml:427 +#: install-methods.xml:438 #, no-c-format #. Tag: para msgid "There is no MacOS application to write images to floppy disks (and there would be no point in doing this as you can't use these floppies to boot the installation system or install kernel and modules from on Macintosh). However, these files are needed for the installation of the operating system and modules, later in the process." msgstr "" -#: install-methods.xml:445 +#: install-methods.xml:456 #, no-c-format #. Tag: title msgid "Writing Disk Images From MacOS" msgstr "" -#: install-methods.xml:446 +#: install-methods.xml:457 #, no-c-format #. Tag: para msgid "An AppleScript, <application>Make Debian Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it." msgstr "" -#: install-methods.xml:457 +#: install-methods.xml:468 #, no-c-format #. Tag: para msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities." msgstr "" -#: install-methods.xml:468 +#: install-methods.xml:479 #, no-c-format #. Tag: title msgid "Writing Disk Images with <command>Disk Copy</command>" msgstr "" -#: install-methods.xml:469 +#: install-methods.xml:480 #, no-c-format #. Tag: para msgid "If you are creating the floppy image from files which were originally on the official &debian; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a Debian mirror." msgstr "" -#: install-methods.xml:478 +#: install-methods.xml:489 #, no-c-format #. Tag: para msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file." msgstr "" -#: install-methods.xml:485 +#: install-methods.xml:496 #, no-c-format #. Tag: para msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields." msgstr "" -#: install-methods.xml:492 +#: install-methods.xml:503 #, no-c-format #. Tag: para msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted." msgstr "" -#: install-methods.xml:501 +#: install-methods.xml:512 #, no-c-format #. Tag: para msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>." msgstr "" -#: install-methods.xml:508 +#: install-methods.xml:519 #, no-c-format #. Tag: para msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy." msgstr "" -#: install-methods.xml:523 +#: install-methods.xml:534 #, no-c-format #. Tag: title msgid "Writing Disk Images with <command>suntar</command>" msgstr "" -#: install-methods.xml:527 +#: install-methods.xml:538 #, no-c-format #. Tag: para msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu." msgstr "" -#: install-methods.xml:535 +#: install-methods.xml:546 #, no-c-format #. Tag: para msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)." msgstr "" -#: install-methods.xml:541 +#: install-methods.xml:552 #, no-c-format #. Tag: para msgid "Select the <filename>root.bin</filename> file in the file-opening dialog." msgstr "" -#: install-methods.xml:546 +#: install-methods.xml:557 #, no-c-format #. Tag: para msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another." msgstr "" -#: install-methods.xml:554 +#: install-methods.xml:565 #, no-c-format #. Tag: para msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it." msgstr "" -#: install-methods.xml:573 +#: install-methods.xml:584 #, no-c-format #. Tag: title msgid "Preparing Files for USB Memory Stick Booting" msgstr "" -#: install-methods.xml:575 +#: install-methods.xml:586 #, no-c-format #. Tag: para msgid "For preparing the USB stick you will need a system where GNU/Linux is already running and where USB is supported. You should ensure that the usb-storage kernel module is loaded (<userinput>modprobe usb-storage</userinput>) and try to find out which SCSI device the USB stick has been mapped to (in this example <filename>/dev/sda</filename> is used). To write to your stick, you will probably have to turn off its write protection switch." msgstr "" -#: install-methods.xml:585 +#: install-methods.xml:596 #, no-c-format #. Tag: para msgid "Note, that the USB stick should be at least 128 MB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)." msgstr "" -#: install-methods.xml:593 +#: install-methods.xml:604 #, no-c-format #. Tag: title msgid "Copying the files — the easy way" msgstr "" -#: install-methods.xml:594 +#: install-methods.xml:605 #, no-c-format #. Tag: para msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) as well as <command>SYSLINUX</command> and its configuration file. You only have to extract it directly to your USB stick:" msgstr "" -#: install-methods.xml:601 +#: install-methods.xml:612 #, no-c-format #. Tag: screen msgid "# zcat boot.img.gz > /dev/<replaceable>sda</replaceable>" msgstr "" -#: install-methods.xml:603 +#: install-methods.xml:614 #, no-c-format #. Tag: para msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) as well as <command>yaboot</command> and its configuration file. Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:" msgstr "" -#: install-methods.xml:612 +#: install-methods.xml:623 #, no-c-format #. Tag: screen msgid "# zcat boot.img.gz > /dev/<replaceable>sda2</replaceable>" msgstr "" -#: install-methods.xml:615 +#: install-methods.xml:626 #, no-c-format #. Tag: para msgid "Using this method will destroy anything already on the device. Make sure that you use the correct device name for your USB stick." msgstr "" -#: install-methods.xml:621 +#: install-methods.xml:632 #, no-c-format #. Tag: para msgid "After that, mount the USB memory stick (<userinput>mount <replaceable arch=\"i386\">/dev/sda</replaceable> <replaceable arch=\"powerpc\">/dev/sda2</replaceable> /mnt</userinput>), which will now have <phrase arch=\"i386\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a Debian netinst or businesscard ISO image to it. Please note that the file name must end in <filename>.iso</filename>. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done." msgstr "" -#: install-methods.xml:637 +#: install-methods.xml:648 #, no-c-format #. Tag: title msgid "Copying the files — the flexible way" msgstr "" -#: install-methods.xml:638 +#: install-methods.xml:649 #, no-c-format #. Tag: para msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick." msgstr "" -#: install-methods.xml:650 install-methods.xml:742 +#: install-methods.xml:661 install-methods.xml:753 #, no-c-format #. Tag: title msgid "USB stick partitioning on &arch-title;" msgstr "" -#: install-methods.xml:651 +#: install-methods.xml:662 #, no-c-format #. Tag: para msgid "We will show how to setup the memory stick to use the first partition, instead of the entire device." msgstr "" -#: install-methods.xml:656 +#: install-methods.xml:667 #, no-c-format #. Tag: para msgid "" @@ -482,13 +494,13 @@ msgid "" "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>mkdosfs</command> command is contained in the <classname>dosfstools</classname> Debian package." msgstr "" -#: install-methods.xml:670 +#: install-methods.xml:681 #, no-c-format #. Tag: para msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <command>LILO</command>) should work, it's convenient to use <command>SYSLINUX</command>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader." msgstr "" -#: install-methods.xml:680 +#: install-methods.xml:691 #, no-c-format #. Tag: para msgid "" @@ -497,13 +509,13 @@ msgid "" "</screen></informalexample> Again, take care that you use the correct device name. The partition must not be mounted when starting <command>SYSLINUX</command>. This procedure writes a boot sector to the partition and creates the file <filename>ldlinux.sys</filename> which contains the boot loader code." msgstr "" -#: install-methods.xml:693 +#: install-methods.xml:704 #, no-c-format #. Tag: para msgid "Mount the partition (<userinput>mount /dev/sda1 /mnt</userinput>) and copy the following files from the Debian archives to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> <listitem><para> <filename>syslinux.cfg</filename> (SYSLINUX configuration file) </para></listitem> <listitem><para> Optional kernel modules </para></listitem> </itemizedlist> If you want to rename the files, please note that <command>SYSLINUX</command> can only process DOS (8.3) file names." msgstr "" -#: install-methods.xml:724 +#: install-methods.xml:735 #, no-c-format #. Tag: para msgid "" @@ -513,7 +525,7 @@ msgid "" "</screen></informalexample> Please note that the <userinput>ramdisk_size</userinput> parameter may need to be increased, depending on the image you are booting." msgstr "" -#: install-methods.xml:743 +#: install-methods.xml:754 #, no-c-format #. Tag: para msgid "" @@ -522,13 +534,13 @@ msgid "" "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>hformat</command> command is contained in the <classname>hfsutils</classname> Debian package." msgstr "" -#: install-methods.xml:759 +#: install-methods.xml:770 #, no-c-format #. Tag: para msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader." msgstr "" -#: install-methods.xml:768 +#: install-methods.xml:779 #, no-c-format #. Tag: para msgid "" @@ -541,43 +553,43 @@ msgid "" "</screen></informalexample> Again, take care that you use the correct device name. The partition must not be otherwise mounted during this procedure. This procedure writes the boot loader to the partition, and uses the HFS utilities to mark it in such a way that Open Firmware will boot it. Having done this, the rest of the USB stick may be prepared using the normal Unix utilities." msgstr "" -#: install-methods.xml:784 +#: install-methods.xml:795 #, no-c-format #. Tag: para msgid "Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and copy the following files from the Debian archives to the stick:" msgstr "" -#: install-methods.xml:790 +#: install-methods.xml:801 #, no-c-format #. Tag: para msgid "<filename>vmlinux</filename> (kernel binary)" msgstr "" -#: install-methods.xml:795 +#: install-methods.xml:806 #, no-c-format #. Tag: para msgid "<filename>initrd.gz</filename> (initial ramdisk image)" msgstr "" -#: install-methods.xml:800 +#: install-methods.xml:811 #, no-c-format #. Tag: para msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" msgstr "" -#: install-methods.xml:805 +#: install-methods.xml:816 #, no-c-format #. Tag: para msgid "<filename>boot.msg</filename> (optional boot message)" msgstr "" -#: install-methods.xml:810 +#: install-methods.xml:821 #, no-c-format #. Tag: para msgid "Optional kernel modules" msgstr "" -#: install-methods.xml:817 +#: install-methods.xml:828 #, no-c-format #. Tag: para msgid "" @@ -595,265 +607,265 @@ msgid "" "</screen></informalexample> Please note that the <userinput>initrd-size</userinput> parameter may need to be increased, depending on the image you are booting." msgstr "" -#: install-methods.xml:832 +#: install-methods.xml:843 #, no-c-format #. Tag: title msgid "Adding an ISO image" msgstr "" -#: install-methods.xml:833 +#: install-methods.xml:844 #, no-c-format #. Tag: para msgid "Now you should put any Debian ISO image (businesscard, netinst or even a full one) onto your stick (if it fits). The file name of such an image must end in <filename>.iso</filename>." msgstr "" -#: install-methods.xml:839 +#: install-methods.xml:850 #, no-c-format #. Tag: para msgid "If you want to install over the network, without using an ISO image, you will of course skip the previous step. Moreover you will have to use the initial ramdisk from the <filename>netboot</filename> directory instead of the one from <filename>hd-media</filename>, because <filename>hd-media/initrd.gz</filename> does not have network support." msgstr "" -#: install-methods.xml:848 +#: install-methods.xml:859 #, no-c-format #. Tag: para msgid "When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>) and activate its write protection switch." msgstr "" -#: install-methods.xml:858 +#: install-methods.xml:869 #, no-c-format #. Tag: title msgid "Booting the USB stick" msgstr "" -#: install-methods.xml:859 +#: install-methods.xml:870 #, no-c-format #. Tag: para msgid "If your system refuses to boot from the memory stick, the stick may contain an invalid master boot record (MBR). To fix this, use the <command>install-mbr</command> command from the package <classname>mbr</classname>:" msgstr "" -#: install-methods.xml:866 +#: install-methods.xml:877 #, no-c-format #. Tag: screen msgid "# install-mbr /dev/<replaceable>sda</replaceable>" msgstr "" -#: install-methods.xml:878 +#: install-methods.xml:889 #, no-c-format #. Tag: title msgid "Preparing Files for Hard Disk Booting" msgstr "" -#: install-methods.xml:879 +#: install-methods.xml:890 #, no-c-format #. Tag: para msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS." msgstr "" -#: install-methods.xml:885 +#: install-methods.xml:896 #, no-c-format #. Tag: para msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks." msgstr "" -#: install-methods.xml:892 +#: install-methods.xml:903 #, no-c-format #. Tag: para msgid "The installer cannot boot from files on an NTFS file system." msgstr "" -#: install-methods.xml:896 +#: install-methods.xml:907 #, no-c-format #. Tag: para msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download." msgstr "" -#: install-methods.xml:907 +#: install-methods.xml:918 #, no-c-format #. Tag: para msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model." msgstr "" -#: install-methods.xml:916 +#: install-methods.xml:927 #, no-c-format #. Tag: title msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>" msgstr "" -#: install-methods.xml:918 +#: install-methods.xml:929 #, no-c-format #. Tag: para msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>." msgstr "" -#: install-methods.xml:924 +#: install-methods.xml:935 #, no-c-format #. Tag: para msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel." msgstr "" -#: install-methods.xml:930 +#: install-methods.xml:941 #, no-c-format #. Tag: para msgid "Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>." msgstr "" -#: install-methods.xml:937 +#: install-methods.xml:948 #, no-c-format #. Tag: para msgid "<filename>vmlinuz</filename> (kernel binary)" msgstr "" -#: install-methods.xml:942 +#: install-methods.xml:953 #, no-c-format #. Tag: para msgid "<filename>initrd.gz</filename> (ramdisk image)" msgstr "" -#: install-methods.xml:949 +#: install-methods.xml:960 #, no-c-format #. Tag: para msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>." msgstr "" -#: install-methods.xml:959 +#: install-methods.xml:970 #, no-c-format #. Tag: title msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "" -#: install-methods.xml:960 +#: install-methods.xml:971 #, no-c-format #. Tag: para msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your Debian installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model." msgstr "" -#: install-methods.xml:973 +#: install-methods.xml:984 #, no-c-format #. Tag: para msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on Debian http/ftp mirrors and official Debian CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder." msgstr "" -#: install-methods.xml:993 +#: install-methods.xml:1004 #, no-c-format #. Tag: title msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "" -#: install-methods.xml:994 +#: install-methods.xml:1005 #, no-c-format #. Tag: para msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs." msgstr "" -#: install-methods.xml:1005 +#: install-methods.xml:1016 #, no-c-format #. Tag: para msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the Debian archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)." msgstr "" -#: install-methods.xml:1015 +#: install-methods.xml:1026 #, no-c-format #. Tag: filename msgid "vmlinux" msgstr "" -#: install-methods.xml:1020 +#: install-methods.xml:1031 #, no-c-format #. Tag: filename msgid "initrd.gz" msgstr "" -#: install-methods.xml:1025 +#: install-methods.xml:1036 #, no-c-format #. Tag: filename msgid "yaboot" msgstr "" -#: install-methods.xml:1030 +#: install-methods.xml:1041 #, no-c-format #. Tag: filename msgid "yaboot.conf" msgstr "" -#: install-methods.xml:1035 +#: install-methods.xml:1046 #, no-c-format #. Tag: para msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the L command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer." msgstr "" -#: install-methods.xml:1043 +#: install-methods.xml:1054 #, no-c-format #. Tag: para msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>." msgstr "" -#: install-methods.xml:1056 +#: install-methods.xml:1067 #, no-c-format #. Tag: title msgid "Preparing Files for TFTP Net Booting" msgstr "" -#: install-methods.xml:1057 +#: install-methods.xml:1068 #, no-c-format #. Tag: para msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine." msgstr "" -#: install-methods.xml:1065 +#: install-methods.xml:1076 #, no-c-format #. Tag: para msgid "You need to setup a TFTP server, and for many machines, a BOOTP server <phrase condition=\"supports-rarp\">, or RARP server</phrase> <phrase condition=\"supports-dhcp\">, or DHCP server</phrase>." msgstr "" -#: install-methods.xml:1071 +#: install-methods.xml:1082 #, no-c-format #. Tag: para msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol. </phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image. </phrase> <phrase arch=\"m68k\"> Yet another alternative exists on VMEbus systems: the IP address can be manually configured in boot ROM. </phrase> <phrase condition=\"supports-dhcp\">The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP. </phrase>" msgstr "" -#: install-methods.xml:1088 +#: install-methods.xml:1099 #, no-c-format #. Tag: para msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP." msgstr "" -#: install-methods.xml:1094 +#: install-methods.xml:1105 #, no-c-format #. Tag: para msgid "Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM console will <emphasis>not</emphasis> use RARP to obtain its IP address, and therefore you must use BOOTP for net booting your Alpha<footnote> <para> Alpha systems can also be net-booted using the DECNet MOP (Maintenance Operations Protocol), but this is not covered here. Presumably, your local OpenVMS operator will be happy to assist you should you have some burning need to use MOP to boot Linux on your Alpha. </para> </footnote>. You can also enter the IP configuration for network interfaces directly in the SRM console." msgstr "" -#: install-methods.xml:1111 +#: install-methods.xml:1122 #, no-c-format #. Tag: para msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in Debian." msgstr "" -#: install-methods.xml:1116 +#: install-methods.xml:1127 #, no-c-format #. Tag: para msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux." msgstr "" -#: install-methods.xml:1124 +#: install-methods.xml:1135 #, no-c-format #. Tag: para msgid "To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> support. On a &debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</classname> packages qualify; we recommend <classname>tftpd-hpa</classname>." msgstr "" -#: install-methods.xml:1142 +#: install-methods.xml:1153 #, no-c-format #. Tag: title msgid "Setting up RARP server" msgstr "" -#: install-methods.xml:1143 +#: install-methods.xml:1154 #, no-c-format #. Tag: para msgid "To setup RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>." msgstr "" -#: install-methods.xml:1155 +#: install-methods.xml:1166 #, no-c-format #. Tag: para msgid "" @@ -870,31 +882,31 @@ msgid "" "</screen></informalexample> you probably need to load the RARP kernel module or else recompile the kernel to support RARP. Try <userinput>modprobe rarp</userinput> and then try the <command>rarp</command> command again." msgstr "" -#: install-methods.xml:1171 +#: install-methods.xml:1182 #, no-c-format #. Tag: para msgid "On a RARP server system using a Linux 2.4.x kernel, there is no RARP module, and you should instead use the <command>rarpd</command> program. The procedure is similar to that used under SunOS in the following paragraph." msgstr "" -#: install-methods.xml:1179 +#: install-methods.xml:1190 #, no-c-format #. Tag: para msgid "Under SunOS, you need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. In SunOS 4, issue the command (as root): <userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use <userinput>/usr/sbin/rarpd -a</userinput>." msgstr "" -#: install-methods.xml:1198 +#: install-methods.xml:1209 #, no-c-format #. Tag: title msgid "Setting up BOOTP server" msgstr "" -#: install-methods.xml:1199 +#: install-methods.xml:1210 #, no-c-format #. Tag: para msgid "There are two BOOTP servers available for GNU/Linux, the CMU <command>bootpd</command> and the other is actually a DHCP server, ISC <command>dhcpd</command>, which are contained in the <classname>bootp</classname> and <classname>dhcp</classname> packages in &debian;." msgstr "" -#: install-methods.xml:1207 +#: install-methods.xml:1218 #, no-c-format #. Tag: para msgid "" @@ -911,19 +923,19 @@ msgid "" "</screen></informalexample> You will need to change at least the <quote>ha</quote> option, which specifies the hardware address of the client. The <quote>bf</quote> option specifies the file a client should retrieve via TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI Indys you can just enter the command monitor and type <userinput>printenv</userinput>. The value of the <userinput>eaddr</userinput> variable is the machine's MAC address. </phrase>" msgstr "" -#: install-methods.xml:1240 +#: install-methods.xml:1251 #, no-c-format #. Tag: para msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise, you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd restart</userinput>." msgstr "" -#: install-methods.xml:1261 +#: install-methods.xml:1272 #, no-c-format #. Tag: title msgid "Setting up a DHCP server" msgstr "" -#: install-methods.xml:1262 +#: install-methods.xml:1273 #, no-c-format #. Tag: para msgid "" @@ -950,25 +962,25 @@ msgid "" "</screen></informalexample> Note: the new (and preferred) <classname>dhcp3</classname> package uses <filename>/etc/dhcp3/dhcpd.conf</filename>." msgstr "" -#: install-methods.xml:1274 +#: install-methods.xml:1285 #, no-c-format #. Tag: para msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP." msgstr "" -#: install-methods.xml:1284 +#: install-methods.xml:1295 #, no-c-format #. Tag: para msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd restart</userinput>." msgstr "" -#: install-methods.xml:1292 +#: install-methods.xml:1303 #, no-c-format #. Tag: title msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" -#: install-methods.xml:1293 +#: install-methods.xml:1304 #, no-c-format #. Tag: para msgid "" @@ -1003,13 +1015,13 @@ msgid "" "</screen></informalexample> Note that for PXE booting, the client filename <filename>pxelinux.0</filename> is a boot loader, not a kernel image (see <xref linkend=\"tftp-images\"/> below)." msgstr "" -#: install-methods.xml:1309 +#: install-methods.xml:1320 #, no-c-format #. Tag: title msgid "Enabling the TFTP Server" msgstr "" -#: install-methods.xml:1310 +#: install-methods.xml:1321 #, no-c-format #. Tag: para msgid "" @@ -1018,13 +1030,13 @@ msgid "" "</screen></informalexample> Debian packages will in general set this up correctly by default when they are installed." msgstr "" -#: install-methods.xml:1321 +#: install-methods.xml:1332 #, no-c-format #. Tag: para msgid "Look in that file and remember the directory which is used as the argument of <command>in.tftpd</command>; you'll need that below. The <userinput>-l</userinput> argument enables some versions of <command>in.tftpd</command> to log all requests to the system logs; this is useful for diagnosing boot errors. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>." msgstr "" -#: install-methods.xml:1335 +#: install-methods.xml:1346 #, no-c-format #. Tag: para msgid "" @@ -1035,85 +1047,85 @@ msgid "" "</screen></informalexample> to adjust the range of source ports the Linux TFTP server uses." msgstr "" -#: install-methods.xml:1357 +#: install-methods.xml:1368 #, no-c-format #. Tag: title msgid "Move TFTP Images Into Place" msgstr "" -#: install-methods.xml:1358 +#: install-methods.xml:1369 #, no-c-format #. Tag: para msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. Generally, this directory will be <filename>/tftpboot</filename>. You'll have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards." msgstr "" -#: install-methods.xml:1368 +#: install-methods.xml:1379 #, no-c-format #. Tag: para msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP directory." msgstr "" -#: install-methods.xml:1377 +#: install-methods.xml:1388 #, no-c-format #. Tag: para msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/pxelinux.0</filename> to <command>tftpd</command> as the filename to boot." msgstr "" -#: install-methods.xml:1385 +#: install-methods.xml:1396 #, no-c-format #. Tag: para msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot." msgstr "" -#: install-methods.xml:1397 +#: install-methods.xml:1408 #, no-c-format #. Tag: title msgid "DECstation TFTP Images" msgstr "" -#: install-methods.xml:1398 +#: install-methods.xml:1409 #, no-c-format #. Tag: para msgid "For DECstations, there are tftpimage files for each subarchitecture, which contain both kernel and installer in one file. The naming convention is <replaceable>subarchitecture</replaceable>/netboot-boot.img. Copy the tftpimage file you would like to use to <userinput>/tftpboot/tftpboot.img</userinput> if you work with the example BOOTP/DHCP setups described above." msgstr "" -#: install-methods.xml:1407 +#: install-methods.xml:1418 #, no-c-format #. Tag: para msgid "The DECstation firmware boots by TFTP with the command <userinput>boot <replaceable>#</replaceable>/tftp</userinput>, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot. On most DECstations this is <quote>3</quote>. If the BOOTP/DHCP server does not supply the filename or you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" -#: install-methods.xml:1419 +#: install-methods.xml:1430 #, no-c-format #. Tag: userinput msgid "boot #/tftp/filename param1=value1 param2=value2 ..." msgstr "" -#: install-methods.xml:1421 +#: install-methods.xml:1432 #, no-c-format #. Tag: para msgid "Several DECstation firmware revisions show a problem with regard to net booting: the transfer starts, but after some time it stops with an <computeroutput>a.out err</computeroutput>. This can have several reasons: <orderedlist> <listitem><para> The firmware does not respond to ARP requests during a TFTP transfer. This leads to an ARP timeout and the transfer stops. The solution is to add the MAC address of the Ethernet card in the DECstation statically to the ARP table of the TFTP server. This is done by running <userinput>arp -s <replaceable>IP-address</replaceable> <replaceable>MAC-address</replaceable></userinput> as root on the machine acting as TFTP server. The MAC-address of the DECstation can be read out by entering <command>cnfg</command> at the DECstation firmware prompt. </para></listitem> <listitem><para> The firmware has a size limit on the files that can be booted by TFTP. </para></listitem> </orderedlist> There are also firmware revisions that cannot boot via TFTP at all. An overview about the different firmware revisions can be found at the NetBSD web pages: <ulink url=\"http://www.netbsd.org/Ports/pmax/board-list.html#proms\"></ulink>." msgstr "" -#: install-methods.xml:1459 +#: install-methods.xml:1470 #, no-c-format #. Tag: title msgid "Alpha TFTP Booting" msgstr "" -#: install-methods.xml:1460 +#: install-methods.xml:1471 #, no-c-format #. Tag: para msgid "On Alpha, you must specify the filename (as a relative path to the boot image directory) using the <userinput>-file</userinput> argument to the SRM <userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</userinput> environment variable. Alternatively, the filename can be given via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</userinput> directive). Unlike Open Firmware, there is <emphasis>no default filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a filename by either one of these methods." msgstr "" -#: install-methods.xml:1475 +#: install-methods.xml:1486 #, no-c-format #. Tag: title msgid "SPARC TFTP Booting" msgstr "" -#: install-methods.xml:1476 +#: install-methods.xml:1487 #, no-c-format #. Tag: para msgid "" @@ -1122,79 +1134,79 @@ msgid "" "</screen></informalexample> This will spit out the IP in hexadecimal; to get to the correct filename, you will need to change all letters to uppercase and if necessary append the subarchitecture name." msgstr "" -#: install-methods.xml:1493 +#: install-methods.xml:1504 #, no-c-format #. Tag: para msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in." msgstr "" -#: install-methods.xml:1504 +#: install-methods.xml:1515 #, no-c-format #. Tag: title msgid "BVM/Motorola TFTP Booting" msgstr "" -#: install-methods.xml:1505 +#: install-methods.xml:1516 #, no-c-format #. Tag: para msgid "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to <filename>/tftpboot/</filename>." msgstr "" -#: install-methods.xml:1510 +#: install-methods.xml:1521 #, no-c-format #. Tag: para msgid "Next, configure your boot ROMs or BOOTP server to initially load the <filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> files from the TFTP server. Refer to the <filename>tftplilo.txt</filename> file for your subarchitecture for additional system-specific configuration information." msgstr "" -#: install-methods.xml:1522 +#: install-methods.xml:1533 #, no-c-format #. Tag: title msgid "SGI Indys TFTP Booting" msgstr "" -#: install-methods.xml:1523 +#: install-methods.xml:1534 #, no-c-format #. Tag: para msgid "On SGI Indys you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>." msgstr "" -#: install-methods.xml:1535 +#: install-methods.xml:1546 #, no-c-format #. Tag: title msgid "Broadcom BCM91250A TFTP Booting" msgstr "" -#: install-methods.xml:1536 +#: install-methods.xml:1547 #, no-c-format #. Tag: para msgid "You don't have to configure DHCP in a special way because you'll pass the full path of the file to the loaded to CFE." msgstr "" -#: install-methods.xml:1641 +#: install-methods.xml:1652 #, no-c-format #. Tag: title msgid "Automatic Installation" msgstr "" -#: install-methods.xml:1642 +#: install-methods.xml:1653 #, no-c-format #. Tag: para msgid "For installing on multiple computers it's possible to do fully automatic installations. Debian packages intended for this include <classname>fai</classname> (which uses an install server), <classname>replicator</classname>, <classname>systemimager</classname>, <classname>autoinstall</classname>, and the Debian Installer itself." msgstr "" -#: install-methods.xml:1655 +#: install-methods.xml:1666 #, no-c-format #. Tag: title msgid "Automatic Installation Using the Debian Installer" msgstr "" -#: install-methods.xml:1656 +#: install-methods.xml:1667 #, no-c-format #. Tag: para msgid "The Debian Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process." msgstr "" -#: install-methods.xml:1663 +#: install-methods.xml:1674 #, no-c-format #. Tag: para msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>." |