diff options
| author | Felipe Augusto van de Wiel <faw@debian.org> | 2009-11-18 01:13:23 +0000 |
|---|---|---|
| committer | Felipe Augusto van de Wiel <faw@debian.org> | 2009-11-18 01:13:23 +0000 |
| commit | 3b9419cb72e6894609f81dcc535100a2b3bf84af (patch) | |
| tree | aa9811a9b48c3b6f7331afe4fe2ed58059233c07 /po/pot | |
| parent | 94af3558c3244435c0d3541f4998810f20bcfde4 (diff) | |
| download | installation-guide-3b9419cb72e6894609f81dcc535100a2b3bf84af.zip | |
[SILENT_COMMIT] Update of POT and PO files for the manual
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 194 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 440 | ||||
| -rw-r--r-- | po/pot/install-methods.pot | 300 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 299 |
4 files changed, 653 insertions, 580 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index f14831a73..28c309d14 100644 --- a/po/pot/boot-installer.pot +++ b/po/pot/boot-installer.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2009-11-08 01:11+0000\n" +"POT-Creation-Date: 2009-11-18 01:11+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" @@ -1428,7 +1428,7 @@ msgid "A theme determines how the user interface of the installer looks (colors, msgstr "" #. Tag: term -#: boot-installer.xml:2272 boot-installer.xml:2551 +#: boot-installer.xml:2272 boot-installer.xml:2568 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" @@ -1670,77 +1670,101 @@ msgstr "" #. Tag: term #: boot-installer.xml:2525 #, no-c-format +msgid "debian-installer/language (language)" +msgstr "" + +#. Tag: term +#: boot-installer.xml:2526 +#, no-c-format +msgid "debian-installer/country (country)" +msgstr "" + +#. Tag: term +#: boot-installer.xml:2527 +#, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:2526 +#: boot-installer.xml:2528 #, no-c-format -msgid "Can be used to set both the language and country for the installation. This will only work if the locale is supported in Debian. For example, use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country." +msgid "There are two ways to specify the language, country and locale to use for the installation and the installed system." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2533 +#, no-c-format +msgid "The first and easiest is to pass only the parameter <literal>locale</literal>. Language and country will then be derived from its value. You can for example use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be set as default locale for the installed system). Limitation is that not all possible combinations of language, country and locale can be achieved this way." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2542 +#, no-c-format +msgid "The second, more flexible option is to specify <literal>language</literal> and <literal>country</literal> separately. In this case <literal>locale</literal> can optionally be added to specify a specific default locale for the installed system. Example: <userinput>language=en country=DE locale=en_GB.UTF-8</userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:2537 +#: boot-installer.xml:2554 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:2538 +#: boot-installer.xml:2555 #, no-c-format msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>." msgstr "" #. Tag: para -#: boot-installer.xml:2552 +#: boot-installer.xml:2569 #, no-c-format msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration." msgstr "" #. Tag: term -#: boot-installer.xml:2561 +#: boot-installer.xml:2578 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:2562 +#: boot-installer.xml:2579 #, no-c-format msgid "By default the installer will use the http protocol to download files from Debian mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually." msgstr "" #. Tag: term -#: boot-installer.xml:2575 +#: boot-installer.xml:2592 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para -#: boot-installer.xml:2576 +#: boot-installer.xml:2593 #, no-c-format msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information." msgstr "" #. Tag: title -#: boot-installer.xml:2590 +#: boot-installer.xml:2607 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2591 +#: boot-installer.xml:2608 #, no-c-format msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:2604 +#: boot-installer.xml:2621 #, no-c-format msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually." msgstr "" #. Tag: para -#: boot-installer.xml:2611 +#: boot-installer.xml:2628 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -1749,133 +1773,133 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2621 +#: boot-installer.xml:2638 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:2627 +#: boot-installer.xml:2644 #, no-c-format msgid "Blacklisting kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2628 +#: boot-installer.xml:2645 #, no-c-format msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first." msgstr "" #. Tag: para -#: boot-installer.xml:2637 +#: boot-installer.xml:2654 #, no-c-format msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:2645 +#: boot-installer.xml:2662 #, no-c-format msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases." msgstr "" #. Tag: title -#: boot-installer.xml:2662 +#: boot-installer.xml:2679 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:2667 +#: boot-installer.xml:2684 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:2668 +#: boot-installer.xml:2685 #, no-c-format msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also — even after booting successfully from CD-ROM — fail to recognize the CD-ROM or return errors while reading from it during the installation." msgstr "" #. Tag: para -#: boot-installer.xml:2675 +#: boot-installer.xml:2692 #, no-c-format msgid "There are many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you." msgstr "" #. Tag: para -#: boot-installer.xml:2681 +#: boot-installer.xml:2698 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:2686 +#: boot-installer.xml:2703 #, no-c-format msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty." msgstr "" #. Tag: para -#: boot-installer.xml:2692 +#: boot-installer.xml:2709 #, no-c-format msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with older CD-ROM drives are known to be resolved in this way." msgstr "" #. Tag: para -#: boot-installer.xml:2702 +#: boot-installer.xml:2719 #, no-c-format msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity." msgstr "" #. Tag: para -#: boot-installer.xml:2708 +#: boot-installer.xml:2725 #, no-c-format msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available." msgstr "" #. Tag: title -#: boot-installer.xml:2716 +#: boot-installer.xml:2733 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:2719 +#: boot-installer.xml:2736 #, no-c-format msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer." msgstr "" #. Tag: para -#: boot-installer.xml:2725 +#: boot-installer.xml:2742 #, no-c-format msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)." msgstr "" #. Tag: para -#: boot-installer.xml:2732 +#: boot-installer.xml:2749 #, no-c-format msgid "Some older CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled." msgstr "" #. Tag: title -#: boot-installer.xml:2743 +#: boot-installer.xml:2760 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:2744 +#: boot-installer.xml:2761 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:2749 +#: boot-installer.xml:2766 #, no-c-format msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using." msgstr "" #. Tag: para -#: boot-installer.xml:2755 +#: boot-installer.xml:2772 #, no-c-format msgid "" "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n" @@ -1885,7 +1909,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2768 +#: boot-installer.xml:2785 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -1898,19 +1922,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2773 +#: boot-installer.xml:2790 #, no-c-format msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there." msgstr "" #. Tag: para -#: boot-installer.xml:2785 +#: boot-installer.xml:2802 #, no-c-format msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>." msgstr "" #. Tag: para -#: boot-installer.xml:2792 +#: boot-installer.xml:2809 #, no-c-format msgid "" "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n" @@ -1923,13 +1947,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2806 +#: boot-installer.xml:2823 #, no-c-format msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdrom</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:2814 +#: boot-installer.xml:2831 #, no-c-format msgid "" "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n" @@ -1938,7 +1962,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2824 +#: boot-installer.xml:2841 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -1951,163 +1975,163 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2839 +#: boot-installer.xml:2856 #, no-c-format msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably." msgstr "" #. Tag: title -#: boot-installer.xml:2854 +#: boot-installer.xml:2871 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:2856 +#: boot-installer.xml:2873 #, no-c-format msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." msgstr "" #. Tag: para -#: boot-installer.xml:2861 +#: boot-installer.xml:2878 #, no-c-format msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors." msgstr "" #. Tag: para -#: boot-installer.xml:2870 +#: boot-installer.xml:2887 #, no-c-format msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system." msgstr "" #. Tag: para -#: boot-installer.xml:2879 +#: boot-installer.xml:2896 #, no-c-format msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy." msgstr "" #. Tag: para -#: boot-installer.xml:2885 +#: boot-installer.xml:2902 #, no-c-format msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums." msgstr "" #. Tag: para -#: boot-installer.xml:2891 +#: boot-installer.xml:2908 #, no-c-format msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers." msgstr "" #. Tag: title -#: boot-installer.xml:2900 +#: boot-installer.xml:2917 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:2902 +#: boot-installer.xml:2919 #, no-c-format msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:2909 +#: boot-installer.xml:2926 #, no-c-format msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" msgstr "" #. Tag: para -#: boot-installer.xml:2915 +#: boot-installer.xml:2932 #, no-c-format msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>." msgstr "" #. Tag: title -#: boot-installer.xml:2926 boot-installer.xml:3028 +#: boot-installer.xml:2943 boot-installer.xml:3045 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:2927 +#: boot-installer.xml:2944 #, no-c-format msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." msgstr "" #. Tag: para -#: boot-installer.xml:2932 +#: boot-installer.xml:2949 #, no-c-format msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:2938 +#: boot-installer.xml:2955 #, no-c-format msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:2947 +#: boot-installer.xml:2964 #, no-c-format msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test." msgstr "" #. Tag: para -#: boot-installer.xml:2954 +#: boot-installer.xml:2971 #, no-c-format msgid "Some systems (especially laptops) that have a native resolution that is not a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank display after the installer has been booted. In that case adding the boot parameter <userinput>vga=788</userinput><footnote> <para> The parameter <userinput>vga=788</userinput> will activate the VESA framebuffer with a resolution of 800x600. This will probably work, but may not be the optimal resolution for your system. A list of supported resolutions can be obtained by using <userinput>vga=ask</userinput>, but you should be aware that list may not be complete. </para> </footnote> may help. If that does not work, try adding the boot parameter <userinput>fb=false</userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:2972 +#: boot-installer.xml:2989 #, no-c-format msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" #. Tag: title -#: boot-installer.xml:2986 +#: boot-installer.xml:3003 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:2987 +#: boot-installer.xml:3004 #, no-c-format msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems." msgstr "" #. Tag: para -#: boot-installer.xml:2997 +#: boot-installer.xml:3014 #, no-c-format msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3014 +#: boot-installer.xml:3031 #, no-c-format msgid "System Freeze while Loading USB Modules" msgstr "" #. Tag: para -#: boot-installer.xml:3015 +#: boot-installer.xml:3032 #, no-c-format msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>nousb</userinput> parameter at the boot prompt." msgstr "" #. Tag: para -#: boot-installer.xml:3029 +#: boot-installer.xml:3046 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:3035 +#: boot-installer.xml:3052 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:3036 +#: boot-installer.xml:3053 #, no-c-format msgid "" "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n" @@ -2117,85 +2141,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3050 +#: boot-installer.xml:3067 #, no-c-format msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>." msgstr "" #. Tag: title -#: boot-installer.xml:3061 +#: boot-installer.xml:3078 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3062 +#: boot-installer.xml:3079 #, no-c-format msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems." msgstr "" #. Tag: para -#: boot-installer.xml:3068 +#: boot-installer.xml:3085 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3077 +#: boot-installer.xml:3094 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3079 +#: boot-installer.xml:3096 #, no-c-format msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." msgstr "" #. Tag: title -#: boot-installer.xml:3104 +#: boot-installer.xml:3121 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3105 +#: boot-installer.xml:3122 #, no-c-format msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report, you may want to attach this information to the bug report." msgstr "" #. Tag: para -#: boot-installer.xml:3116 +#: boot-installer.xml:3133 #, no-c-format msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system." msgstr "" #. Tag: title -#: boot-installer.xml:3127 +#: boot-installer.xml:3144 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3128 +#: boot-installer.xml:3145 #, no-c-format msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations." msgstr "" #. Tag: para -#: boot-installer.xml:3135 +#: boot-installer.xml:3152 #, no-c-format msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public." msgstr "" #. Tag: para -#: boot-installer.xml:3141 +#: boot-installer.xml:3158 #, no-c-format msgid "If you have a working Debian system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-reports</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3151 +#: boot-installer.xml:3168 #, no-c-format msgid "" "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n" diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index 5ac17e906..9d10fb625 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2009-11-02 22:19+0000\n" +"POT-Creation-Date: 2009-11-18 01:11+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" @@ -429,19 +429,19 @@ msgid "This is the first official release of &debian; for the &arch-title; archi msgstr "" #. Tag: title -#: hardware.xml:210 hardware.xml:246 hardware.xml:350 hardware.xml:369 hardware.xml:452 hardware.xml:510 hardware.xml:563 +#: hardware.xml:210 hardware.xml:246 hardware.xml:352 hardware.xml:371 hardware.xml:454 hardware.xml:512 hardware.xml:565 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para -#: hardware.xml:211 hardware.xml:370 +#: hardware.xml:211 hardware.xml:372 #, no-c-format msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics." msgstr "" #. Tag: title -#: hardware.xml:219 hardware.xml:378 hardware.xml:487 +#: hardware.xml:219 hardware.xml:380 hardware.xml:489 #, no-c-format msgid "<title>CPU</title>" msgstr "" @@ -503,1295 +503,1295 @@ msgstr "" #. Tag: para #: hardware.xml:302 #, no-c-format -msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: <ulink url=\"&url-arm-cyrius-sheevaplug;\">SheevaPlug</ulink> and <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (TS-119 and TS-219)." +msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base and OpenRD-Client), <ulink url=\"&url-arm-cyrius-sheevaplug;\">SheevaPlug</ulink> and <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (TS-110, TS-119, TS-210, TS-219 and TS-219P; the TS-410 and TS-419P are not yet supported)." msgstr "" #. Tag: term -#: hardware.xml:315 +#: hardware.xml:317 #, no-c-format msgid "Orion5x" msgstr "" #. Tag: para -#: hardware.xml:316 +#: hardware.xml:318 #, no-c-format msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: <ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>, <ulink url=\"&url-arm-cyrius-qnap;\">QNAP Turbo Station</ulink> (TS-109, TS-209 and TS-409)." msgstr "" #. Tag: term -#: hardware.xml:331 +#: hardware.xml:333 #, no-c-format msgid "<term>Versatile</term>" msgstr "" #. Tag: para -#: hardware.xml:332 +#: hardware.xml:334 #, no-c-format msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run Debian on ARM if you don't have the hardware." msgstr "" #. Tag: para -#: hardware.xml:351 +#: hardware.xml:353 #, no-c-format msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future." msgstr "" #. Tag: para -#: hardware.xml:379 +#: hardware.xml:381 #, no-c-format msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon." msgstr "" #. Tag: para -#: hardware.xml:386 +#: hardware.xml:388 #, no-c-format msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of Debian<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para> </footnote>." msgstr "" #. Tag: para -#: hardware.xml:419 +#: hardware.xml:421 #, no-c-format msgid "If your system has a 64-bit processor from the AMD64 or Intel EM64T families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture." msgstr "" #. Tag: title -#: hardware.xml:428 +#: hardware.xml:430 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:429 +#: hardware.xml:431 #, no-c-format msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, PCIe, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these." msgstr "" #. Tag: para -#: hardware.xml:453 +#: hardware.xml:455 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run Debian on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: para -#: hardware.xml:488 +#: hardware.xml:490 #, no-c-format msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the Debian installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported." msgstr "" #. Tag: para -#: hardware.xml:494 +#: hardware.xml:496 #, no-c-format msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture." msgstr "" #. Tag: para -#: hardware.xml:511 +#: hardware.xml:513 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run Debian on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: title -#: hardware.xml:539 +#: hardware.xml:541 #, no-c-format msgid "CPU/Machine types" msgstr "" #. Tag: para -#: hardware.xml:541 +#: hardware.xml:543 #, no-c-format msgid "All MIPS based Cobalt machines are supported with the exception of the Qube 2700 (Qube 1)." msgstr "" #. Tag: title -#: hardware.xml:549 +#: hardware.xml:551 #, no-c-format msgid "Supported console options" msgstr "" #. Tag: para -#: hardware.xml:550 +#: hardware.xml:552 #, no-c-format msgid "Cobalt machines use 115200 bps." msgstr "" #. Tag: para -#: hardware.xml:564 +#: hardware.xml:566 #, no-c-format msgid "For &debian; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported." msgstr "" #. Tag: title -#: hardware.xml:585 +#: hardware.xml:587 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:587 +#: hardware.xml:589 #, no-c-format msgid "There are two flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:594 +#: hardware.xml:596 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:595 +#: hardware.xml:597 #, no-c-format msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors." msgstr "" #. Tag: term -#: hardware.xml:605 +#: hardware.xml:607 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:606 +#: hardware.xml:608 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:610 +#: hardware.xml:612 #, no-c-format msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270." msgstr "" #. Tag: para -#: hardware.xml:616 +#: hardware.xml:618 #, no-c-format msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690." msgstr "" #. Tag: para -#: hardware.xml:621 +#: hardware.xml:623 #, no-c-format msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour." msgstr "" #. Tag: title -#: hardware.xml:655 +#: hardware.xml:657 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:657 +#: hardware.xml:659 #, no-c-format msgid "Apple (and briefly a few other manufacturers — Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by Debian), OldWorld, and NewWorld." msgstr "" #. Tag: para -#: hardware.xml:664 +#: hardware.xml:666 #, no-c-format msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld." msgstr "" #. Tag: para -#: hardware.xml:672 +#: hardware.xml:674 #, no-c-format msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards." msgstr "" #. Tag: para -#: hardware.xml:680 +#: hardware.xml:682 #, no-c-format msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>." msgstr "" #. Tag: entry -#: hardware.xml:696 hardware.xml:831 hardware.xml:875 hardware.xml:904 +#: hardware.xml:698 hardware.xml:833 hardware.xml:877 hardware.xml:906 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:697 +#: hardware.xml:699 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:703 +#: hardware.xml:705 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:704 +#: hardware.xml:706 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:705 hardware.xml:708 hardware.xml:711 hardware.xml:714 hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726 hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738 hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750 +#: hardware.xml:707 hardware.xml:710 hardware.xml:713 hardware.xml:716 hardware.xml:719 hardware.xml:722 hardware.xml:725 hardware.xml:728 hardware.xml:731 hardware.xml:734 hardware.xml:737 hardware.xml:740 hardware.xml:743 hardware.xml:746 hardware.xml:749 hardware.xml:752 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:707 +#: hardware.xml:709 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:710 +#: hardware.xml:712 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:713 +#: hardware.xml:715 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:716 +#: hardware.xml:718 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:719 +#: hardware.xml:721 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:722 +#: hardware.xml:724 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:725 +#: hardware.xml:727 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:728 +#: hardware.xml:730 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:731 +#: hardware.xml:733 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:734 +#: hardware.xml:736 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:737 +#: hardware.xml:739 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:740 +#: hardware.xml:742 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:743 +#: hardware.xml:745 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:746 +#: hardware.xml:748 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:749 +#: hardware.xml:751 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:752 +#: hardware.xml:754 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762 hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774 hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786 hardware.xml:792 hardware.xml:795 hardware.xml:801 hardware.xml:807 hardware.xml:813 +#: hardware.xml:755 hardware.xml:758 hardware.xml:761 hardware.xml:764 hardware.xml:767 hardware.xml:770 hardware.xml:773 hardware.xml:776 hardware.xml:779 hardware.xml:782 hardware.xml:785 hardware.xml:788 hardware.xml:794 hardware.xml:797 hardware.xml:803 hardware.xml:809 hardware.xml:815 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:755 +#: hardware.xml:757 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:758 +#: hardware.xml:760 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:761 +#: hardware.xml:763 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:764 +#: hardware.xml:766 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:767 +#: hardware.xml:769 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:770 +#: hardware.xml:772 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:773 +#: hardware.xml:775 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:776 +#: hardware.xml:778 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:779 +#: hardware.xml:781 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:782 +#: hardware.xml:784 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:785 +#: hardware.xml:787 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:790 +#: hardware.xml:792 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:791 +#: hardware.xml:793 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:794 +#: hardware.xml:796 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:799 +#: hardware.xml:801 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:800 +#: hardware.xml:802 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:805 +#: hardware.xml:807 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:806 +#: hardware.xml:808 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:811 hardware.xml:837 +#: hardware.xml:813 hardware.xml:839 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:812 +#: hardware.xml:814 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:821 +#: hardware.xml:823 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:838 +#: hardware.xml:840 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:840 +#: hardware.xml:842 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:842 +#: hardware.xml:844 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:844 +#: hardware.xml:846 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:846 +#: hardware.xml:848 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:850 hardware.xml:881 +#: hardware.xml:852 hardware.xml:883 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:851 +#: hardware.xml:853 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:853 +#: hardware.xml:855 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:855 +#: hardware.xml:857 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:857 +#: hardware.xml:859 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:865 +#: hardware.xml:867 #, no-c-format msgid "CHRP subarchitecture (unsupported)" msgstr "" #. Tag: entry -#: hardware.xml:882 +#: hardware.xml:884 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:885 +#: hardware.xml:887 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:886 +#: hardware.xml:888 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: title -#: hardware.xml:894 +#: hardware.xml:896 #, no-c-format msgid "APUS subarchitecture (unsupported)" msgstr "" #. Tag: entry -#: hardware.xml:910 +#: hardware.xml:912 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:911 +#: hardware.xml:913 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:919 +#: hardware.xml:921 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:921 +#: hardware.xml:923 #, no-c-format msgid "NuBus systems are not currently supported by Debian/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which Debian does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>." msgstr "" #. Tag: title -#: hardware.xml:958 +#: hardware.xml:960 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:960 +#: hardware.xml:962 #, no-c-format msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950." msgstr "" #. Tag: para -#: hardware.xml:969 +#: hardware.xml:971 #, no-c-format msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD." msgstr "" #. Tag: para -#: hardware.xml:977 +#: hardware.xml:979 #, no-c-format msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)." msgstr "" #. Tag: title -#: hardware.xml:993 +#: hardware.xml:995 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "" #. Tag: para -#: hardware.xml:994 +#: hardware.xml:996 #, no-c-format msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128.ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance." msgstr "" #. Tag: title -#: hardware.xml:1016 +#: hardware.xml:1018 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para -#: hardware.xml:1017 +#: hardware.xml:1019 #, no-c-format msgid "Sparc-based hardware is divided into a number of different subarchitectures, identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u or sun4v. The following list describes what machines they include and what level of support may be expected for each of them." msgstr "" #. Tag: term -#: hardware.xml:1028 +#: hardware.xml:1030 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "" #. Tag: para -#: hardware.xml:1030 +#: hardware.xml:1032 #, no-c-format msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1037 +#: hardware.xml:1039 #, no-c-format msgid "The last Debian release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases." msgstr "" #. Tag: term -#: hardware.xml:1047 +#: hardware.xml:1049 #, no-c-format msgid "<term>sun4u</term>" msgstr "" #. Tag: para -#: hardware.xml:1049 +#: hardware.xml:1051 #, no-c-format msgid "This subarchitecture includes all 64-bit machines (sparc64) based on the UltraSparc processor and its clones. Most of the machines are well supported, even though for some you may experience problems booting from CD due to firmware or bootloader bugs (this problem may be worked around by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP configurations respectively." msgstr "" #. Tag: term -#: hardware.xml:1062 +#: hardware.xml:1064 #, no-c-format msgid "<term>sun4v</term>" msgstr "" #. Tag: para -#: hardware.xml:1064 +#: hardware.xml:1066 #, no-c-format msgid "This is the newest addition to the Sparc family, which includes machines based on the Niagara multi-core CPUs. At the moment such CPUs are only available in T1000 and T2000 servers by Sun, and are well supported. Use the sparc64-smp kernel." msgstr "" #. Tag: para -#: hardware.xml:1075 +#: hardware.xml:1077 #, no-c-format msgid "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel." msgstr "" #. Tag: title -#: hardware.xml:1084 +#: hardware.xml:1086 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1085 +#: hardware.xml:1087 #, no-c-format msgid "Laptops are also supported and nowadays most laptops work out of the box. In case a laptop contains specialized or proprietary hardware, some specific functions may not be supported. To see if your particular laptop works well with GNU/Linux, see for example the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>." msgstr "" #. Tag: title -#: hardware.xml:1097 hardware.xml:1120 hardware.xml:1140 hardware.xml:1163 +#: hardware.xml:1099 hardware.xml:1122 hardware.xml:1142 hardware.xml:1165 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1098 +#: hardware.xml:1100 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image has been compiled with SMP support. The standard kernel is also usable on non-SMP systems, but has a slight overhead which will cause a small reduction in performance. For normal system use this will hardly be noticable." msgstr "" #. Tag: para -#: hardware.xml:1107 +#: hardware.xml:1109 #, no-c-format msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" #. Tag: para -#: hardware.xml:1122 +#: hardware.xml:1124 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image has been compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems." msgstr "" #. Tag: para -#: hardware.xml:1131 +#: hardware.xml:1133 #, no-c-format msgid "The 486 flavour of the Debian kernel image packages for &arch-title; is not compiled with SMP support." msgstr "" #. Tag: para -#: hardware.xml:1141 +#: hardware.xml:1143 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. However, the standard Debian &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1150 +#: hardware.xml:1152 #, no-c-format msgid "In order to take advantage of multiple processors, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" #. Tag: para -#: hardware.xml:1164 +#: hardware.xml:1166 #, no-c-format msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture, and is supported by a precompiled Debian kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1174 +#: hardware.xml:1176 #, no-c-format msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package." msgstr "" #. Tag: para -#: hardware.xml:1180 +#: hardware.xml:1182 #, no-c-format msgid "You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" #. Tag: title -#: hardware.xml:1191 +#: hardware.xml:1193 #, no-c-format msgid "Graphics Card Support" msgstr "" #. Tag: para -#: hardware.xml:1192 +#: hardware.xml:1194 #, no-c-format msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document." msgstr "" #. Tag: para -#: hardware.xml:1200 +#: hardware.xml:1202 #, no-c-format msgid "Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian &release; ships with X.Org version &x11ver;." msgstr "" #. Tag: para -#: hardware.xml:1209 +#: hardware.xml:1211 #, no-c-format msgid "The X.Org X Window System is only supported on the SGI Indy and the O2." msgstr "" #. Tag: para -#: hardware.xml:1214 +#: hardware.xml:1216 #, no-c-format msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card." msgstr "" #. Tag: para -#: hardware.xml:1224 +#: hardware.xml:1226 #, no-c-format msgid "It is not uncommon for a Sparc machine to have two graphics cards in a default configuration. In such a case there is a possibility that the Linux kernel will not direct its output to the card initially used by the firmware. The lack of output on the graphical console may then be mistaken for a hang (usually the last message seen on console is 'Booting Linux...'). One possible solution is to physically remove one of the video cards; another option is to disable one of the cards using a kernel boot parameter. Also, if graphical output is not required or desired, serial console may be used as an alternative. On some systems use of serial console can be activated automatically by disconnecting the keyboard before booting the system." msgstr "" #. Tag: title -#: hardware.xml:1246 +#: hardware.xml:1248 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:1247 +#: hardware.xml:1249 #, no-c-format msgid "Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1256 +#: hardware.xml:1258 #, no-c-format msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:" msgstr "" #. Tag: para -#: hardware.xml:1262 +#: hardware.xml:1264 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:1267 +#: hardware.xml:1269 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:1272 +#: hardware.xml:1274 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:1277 +#: hardware.xml:1279 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:1282 +#: hardware.xml:1284 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:1289 +#: hardware.xml:1291 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:1294 +#: hardware.xml:1296 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:1299 +#: hardware.xml:1301 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:1304 +#: hardware.xml:1306 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:1313 +#: hardware.xml:1315 #, no-c-format msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided. The major exception is the IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a proprietary microcode for the operation of its built-in Ethernet device. Unofficial images for Linksys NSLU2 with this proprietary microcode can be obtained from the <ulink url=\"&url-slug-firmware;\">Slug-Firmware site</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1323 +#: hardware.xml:1325 #, no-c-format msgid "ISDN is supported, but not during the installation." msgstr "" #. Tag: title -#: hardware.xml:1330 +#: hardware.xml:1332 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:1331 +#: hardware.xml:1333 #, no-c-format msgid "Wireless networking is in general supported as well and a growing number of wireless adapters is supported by the official Linux kernel, although many of them do require firmware to be loaded. Wireless NICs that are not supported by the official Linux kernel can generally be made to work under &debian;, but are not supported during the installation." msgstr "" #. Tag: para -#: hardware.xml:1339 +#: hardware.xml:1341 #, no-c-format msgid "The use of wireless networking during installation is still under development and whether it will work depends on the type of adaptor and the configuration of your wireless access point. If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually." msgstr "" #. Tag: para -#: hardware.xml:1351 +#: hardware.xml:1353 #, no-c-format msgid "In some cases the driver you need may not be available as a Debian package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>" msgstr "" #. Tag: title -#: hardware.xml:1365 +#: hardware.xml:1367 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:1366 +#: hardware.xml:1368 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:1373 +#: hardware.xml:1375 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:1375 +#: hardware.xml:1377 #, no-c-format msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly." msgstr "" #. Tag: para -#: hardware.xml:1385 +#: hardware.xml:1387 #, no-c-format msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>." msgstr "" #. Tag: para -#: hardware.xml:1393 +#: hardware.xml:1395 #, no-c-format msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted." msgstr "" #. Tag: title -#: hardware.xml:1406 +#: hardware.xml:1408 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:1408 +#: hardware.xml:1410 #, no-c-format msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." msgstr "" #. Tag: title -#: hardware.xml:1423 +#: hardware.xml:1425 #, no-c-format msgid "Braille Displays" msgstr "" #. Tag: para -#: hardware.xml:1424 +#: hardware.xml:1426 #, no-c-format msgid "Support for braille displays is determined by the underlying support found in <classname>brltty</classname>. Most displays work under <classname>brltty</classname>, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the <ulink url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian; &release; ships with <classname>brltty</classname> version &brlttyver;." msgstr "" #. Tag: title -#: hardware.xml:1438 +#: hardware.xml:1440 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: hardware.xml:1439 +#: hardware.xml:1441 #, no-c-format msgid "Support for hardware speech synthesis devices is determined by the underlying support found in <classname>speakup</classname>. <classname>speakup</classname> only supports integrated boards and external devices connected to a serial port (no USB or serial-to-USB adapters are supported). Details on supported hardware speech synthesis devices can be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> website</ulink>. &debian; &release; ships with <classname>speakup</classname> version &speakupver;." msgstr "" #. Tag: title -#: hardware.xml:1459 +#: hardware.xml:1461 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:1460 +#: hardware.xml:1462 #, no-c-format msgid "Linux supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system." msgstr "" #. Tag: para -#: hardware.xml:1466 +#: hardware.xml:1468 #, no-c-format msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>)." msgstr "" #. Tag: para -#: hardware.xml:1472 +#: hardware.xml:1474 #, no-c-format msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux." msgstr "" #. Tag: para -#: hardware.xml:1478 +#: hardware.xml:1480 #, no-c-format msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP." msgstr "" #. Tag: para -#: hardware.xml:1484 +#: hardware.xml:1486 #, no-c-format msgid "The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." msgstr "" #. Tag: title -#: hardware.xml:1496 +#: hardware.xml:1498 #, no-c-format msgid "Devices Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:1497 +#: hardware.xml:1499 #, no-c-format msgid "Besides the availability of a device driver, some hardware also requires so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware." msgstr "" #. Tag: para -#: hardware.xml:1505 +#: hardware.xml:1507 #, no-c-format msgid "In most cases firmware is non-free according to the criteria used by the &debian; project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if &debian; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive." msgstr "" #. Tag: para -#: hardware.xml:1514 +#: hardware.xml:1516 #, no-c-format msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a floppy disk or USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation." msgstr "" #. Tag: title -#: hardware.xml:1530 +#: hardware.xml:1532 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" #. Tag: para -#: hardware.xml:1532 +#: hardware.xml:1534 #, no-c-format msgid "There are several vendors, who ship systems with Debian or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux." msgstr "" #. Tag: para -#: hardware.xml:1540 +#: hardware.xml:1542 #, no-c-format msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that." msgstr "" #. Tag: para -#: hardware.xml:1548 +#: hardware.xml:1550 #, no-c-format msgid "Whether or not you are purchasing a system with Linux bundled, or even a used system, it is still important to check that your hardware is supported by the Linux kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a Linux system. Support Linux-friendly hardware vendors." msgstr "" #. Tag: title -#: hardware.xml:1559 +#: hardware.xml:1561 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:1560 +#: hardware.xml:1562 #, no-c-format msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the Linux source code." msgstr "" #. Tag: para -#: hardware.xml:1567 +#: hardware.xml:1569 #, no-c-format msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under Linux. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market." msgstr "" #. Tag: title -#: hardware.xml:1579 +#: hardware.xml:1581 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:1580 +#: hardware.xml:1582 #, no-c-format msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence." msgstr "" #. Tag: para -#: hardware.xml:1593 +#: hardware.xml:1595 #, no-c-format msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes it being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" #. Tag: para -#: hardware.xml:1614 +#: hardware.xml:1616 #, no-c-format msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>." msgstr "" #. Tag: title -#: hardware.xml:1631 +#: hardware.xml:1633 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:1633 +#: hardware.xml:1635 #, no-c-format msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used to install Debian. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section." msgstr "" #. Tag: title -#: hardware.xml:1644 +#: hardware.xml:1646 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:1645 +#: hardware.xml:1647 #, no-c-format msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive." msgstr "" #. Tag: para -#: hardware.xml:1651 +#: hardware.xml:1653 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:1658 +#: hardware.xml:1660 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:1660 +#: hardware.xml:1662 #, no-c-format msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI." msgstr "" #. Tag: para -#: hardware.xml:1667 +#: hardware.xml:1669 #, no-c-format msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>." msgstr "" #. Tag: para -#: hardware.xml:1679 +#: hardware.xml:1681 #, no-c-format msgid "SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux." msgstr "" #. Tag: para -#: hardware.xml:1685 +#: hardware.xml:1687 #, no-c-format msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" #. Tag: para -#: hardware.xml:1690 +#: hardware.xml:1692 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines." msgstr "" #. Tag: para -#: hardware.xml:1694 +#: hardware.xml:1696 #, no-c-format msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware." msgstr "" #. Tag: title -#: hardware.xml:1708 +#: hardware.xml:1710 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:1710 +#: hardware.xml:1712 #, no-c-format msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk." msgstr "" #. Tag: para -#: hardware.xml:1716 +#: hardware.xml:1718 #, no-c-format msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)." msgstr "" #. Tag: title -#: hardware.xml:1724 +#: hardware.xml:1726 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:1726 +#: hardware.xml:1728 #, no-c-format msgid "Many Debian boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives." msgstr "" #. Tag: title -#: hardware.xml:1738 +#: hardware.xml:1740 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:1740 +#: hardware.xml:1742 #, no-c-format msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP." msgstr "" #. Tag: para -#: hardware.xml:1750 +#: hardware.xml:1752 #, no-c-format msgid "You can also <emphasis>boot</emphasis> the installation system over the network. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1756 +#: hardware.xml:1758 #, no-c-format msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." msgstr "" #. Tag: title -#: hardware.xml:1764 +#: hardware.xml:1766 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:1766 +#: hardware.xml:1768 #, no-c-format msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." msgstr "" #. Tag: title -#: hardware.xml:1778 +#: hardware.xml:1780 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:1780 +#: hardware.xml:1782 #, no-c-format msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware." msgstr "" #. Tag: para -#: hardware.xml:1790 +#: hardware.xml:1792 #, no-c-format msgid "Generally, the Debian installation system includes support for floppies, IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." msgstr "" #. Tag: para -#: hardware.xml:1797 +#: hardware.xml:1799 #, no-c-format msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or PATA — are supported. SATA and SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." msgstr "" #. Tag: para -#: hardware.xml:1805 +#: hardware.xml:1807 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel." msgstr "" #. Tag: para -#: hardware.xml:1838 +#: hardware.xml:1840 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all." msgstr "" #. Tag: para -#: hardware.xml:1844 +#: hardware.xml:1846 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive." msgstr "" #. Tag: para -#: hardware.xml:1850 +#: hardware.xml:1852 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:1855 +#: hardware.xml:1857 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)." msgstr "" #. Tag: title -#: hardware.xml:1872 +#: hardware.xml:1874 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:1874 +#: hardware.xml:1876 #, no-c-format msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>." msgstr "" #. Tag: para -#: hardware.xml:1881 +#: hardware.xml:1883 #, no-c-format msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users." msgstr "" diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot index b2bfe9ad5..cc4c0e930 100644 --- a/po/pot/install-methods.pot +++ b/po/pot/install-methods.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2009-11-08 01:11+0000\n" +"POT-Creation-Date: 2009-11-18 01:11+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" @@ -149,71 +149,83 @@ msgstr "" #. Tag: para #: install-methods.xml:174 #, no-c-format -msgid "The QNAP Turbo Station (TS-109, TS-209 and TS-409) requires a kernel and ramdisk which can be obtained from &qnap-orion-firmware-img;. A script is provided to write these images to flash." +msgid "The installation files for the QNAP Turbo Station consist of a kernel and ramdisk as well as a script to write these images to flash. You can obtain the installation files for QNAP TS-109 and TS-209 from &qnap-orion-firmware-img; and for QNAP TS-110, TS-119, TS-210, TS-219, TS-219P from &qnap-kirkwood-firmware-img;." msgstr "" #. Tag: title -#: install-methods.xml:224 +#: install-methods.xml:186 +#, no-c-format +msgid "SheevaPlug and OpenRD Installation Files" +msgstr "" + +#. Tag: para +#: install-methods.xml:187 +#, no-c-format +msgid "The installation files for the Marvell SheevaPlug and OpenRD devices consist of a kernel and initrd for U-Boot. You can obtain these files from &kirkwood-marvell-firmware-img;." +msgstr "" + +#. Tag: title +#: install-methods.xml:237 #, no-c-format msgid "Creating an IPL tape" msgstr "" #. Tag: para -#: install-methods.xml:226 +#: install-methods.xml:239 #, no-c-format msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>." msgstr "" #. Tag: title -#: install-methods.xml:250 +#: install-methods.xml:263 #, no-c-format msgid "Creating Floppies from Disk Images" msgstr "" #. Tag: para -#: install-methods.xml:251 +#: install-methods.xml:264 #, no-c-format msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means." msgstr "" #. Tag: para -#: install-methods.xml:256 +#: install-methods.xml:269 #, no-c-format msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives." msgstr "" #. Tag: para -#: install-methods.xml:261 +#: install-methods.xml:274 #, no-c-format msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy." msgstr "" #. Tag: para -#: install-methods.xml:272 +#: install-methods.xml:285 #, no-c-format msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms." msgstr "" #. Tag: para -#: install-methods.xml:278 +#: install-methods.xml:291 #, no-c-format msgid "Before you can create the floppies, you will first need to download them from one of the Debian mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>" msgstr "" #. Tag: para -#: install-methods.xml:286 +#: install-methods.xml:299 #, no-c-format msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally." msgstr "" #. Tag: title -#: install-methods.xml:294 +#: install-methods.xml:307 #, no-c-format msgid "Writing Disk Images From a Linux or Unix System" msgstr "" #. Tag: para -#: install-methods.xml:295 +#: install-methods.xml:308 #, no-c-format msgid "" "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n" @@ -222,259 +234,259 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:316 +#: install-methods.xml:329 #, no-c-format msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>" msgstr "" #. Tag: para -#: install-methods.xml:337 +#: install-methods.xml:350 #, no-c-format msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it." msgstr "" #. Tag: title -#: install-methods.xml:355 +#: install-methods.xml:368 #, no-c-format msgid "Writing Disk Images From DOS, Windows, or OS/2" msgstr "" #. Tag: para -#: install-methods.xml:357 +#: install-methods.xml:370 #, no-c-format msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies." msgstr "" #. Tag: para -#: install-methods.xml:362 +#: install-methods.xml:375 #, no-c-format msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work." msgstr "" #. Tag: para -#: install-methods.xml:370 +#: install-methods.xml:383 #, no-c-format msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory." msgstr "" #. Tag: para -#: install-methods.xml:376 +#: install-methods.xml:389 #, no-c-format msgid "These tools can be found on the Official Debian CD-ROMs under the <filename>/tools</filename> directory." msgstr "" #. Tag: title -#: install-methods.xml:389 +#: install-methods.xml:402 #, no-c-format msgid "Writing Disk Images From MacOS" msgstr "" #. Tag: para -#: install-methods.xml:390 +#: install-methods.xml:403 #, no-c-format msgid "An AppleScript, <application>Make Debian Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it." msgstr "" #. Tag: para -#: install-methods.xml:401 +#: install-methods.xml:414 #, no-c-format msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities." msgstr "" #. Tag: title -#: install-methods.xml:412 +#: install-methods.xml:425 #, no-c-format msgid "Writing Disk Images with <command>Disk Copy</command>" msgstr "" #. Tag: para -#: install-methods.xml:413 +#: install-methods.xml:426 #, no-c-format msgid "If you are creating the floppy image from files which were originally on the official &debian; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a Debian mirror." msgstr "" #. Tag: para -#: install-methods.xml:422 +#: install-methods.xml:435 #, no-c-format msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file." msgstr "" #. Tag: para -#: install-methods.xml:429 +#: install-methods.xml:442 #, no-c-format msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields." msgstr "" #. Tag: para -#: install-methods.xml:436 +#: install-methods.xml:449 #, no-c-format msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted." msgstr "" #. Tag: para -#: install-methods.xml:445 +#: install-methods.xml:458 #, no-c-format msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>." msgstr "" #. Tag: para -#: install-methods.xml:452 +#: install-methods.xml:465 #, no-c-format msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy." msgstr "" #. Tag: title -#: install-methods.xml:467 +#: install-methods.xml:480 #, no-c-format msgid "Writing Disk Images with <command>suntar</command>" msgstr "" #. Tag: para -#: install-methods.xml:471 +#: install-methods.xml:484 #, no-c-format msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu." msgstr "" #. Tag: para -#: install-methods.xml:479 +#: install-methods.xml:492 #, no-c-format msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)." msgstr "" #. Tag: para -#: install-methods.xml:485 +#: install-methods.xml:498 #, no-c-format msgid "Select the <filename>root.bin</filename> file in the file-opening dialog." msgstr "" #. Tag: para -#: install-methods.xml:490 +#: install-methods.xml:503 #, no-c-format msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another." msgstr "" #. Tag: para -#: install-methods.xml:498 +#: install-methods.xml:511 #, no-c-format msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it." msgstr "" #. Tag: title -#: install-methods.xml:517 +#: install-methods.xml:530 #, no-c-format msgid "Preparing Files for USB Memory Stick Booting" msgstr "" #. Tag: para -#: install-methods.xml:519 +#: install-methods.xml:532 #, no-c-format msgid "There are two installation methods possible when booting from USB stick. The first is to install completely from the network. The second is to also copy a CD image onto the USB stick and use that as a source for packages, possibly in combination with a mirror. This second method is the more common." msgstr "" #. Tag: para -#: install-methods.xml:527 +#: install-methods.xml:540 #, no-c-format msgid "For the first installation method you'll need to download an installer image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>) and use the <quote>flexible way</quote> explained below to copy the files to the USB stick." msgstr "" #. Tag: para -#: install-methods.xml:535 +#: install-methods.xml:548 #, no-c-format msgid "Installation images for the second installation method can be found in the <filename>hd-media</filename> directory and either the <quote>easy way</quote> or the <quote>flexible way</quote> can be used to copy the image to the USB stick. For this installation method you will also need to download a CD image. The installation image and the CD image must be based on the same release of &d-i;. If they do not match you are likely to get errors<footnote> <para> The error message that is most likely to be displayed is that no kernel modules can be found. This means that the version of the kernel module udebs included on the CD image is different from the version of the running kernel. </para> </footnote> during the installation." msgstr "" #. Tag: para -#: install-methods.xml:554 +#: install-methods.xml:567 #, no-c-format msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>dmesg</command> after inserting it. To write to your stick, you may have to turn off its write protection switch." msgstr "" #. Tag: para -#: install-methods.xml:568 +#: install-methods.xml:581 #, no-c-format msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost." msgstr "" #. Tag: para -#: install-methods.xml:576 +#: install-methods.xml:589 #, no-c-format msgid "Note that the USB stick should be at least 256 MB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)." msgstr "" #. Tag: title -#: install-methods.xml:584 +#: install-methods.xml:597 #, no-c-format msgid "Copying the files — the easy way" msgstr "" #. Tag: para -#: install-methods.xml:585 +#: install-methods.xml:598 #, no-c-format msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) <phrase arch=\"x86\">as well as <classname>syslinux</classname> and its configuration file.</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</classname> and its configuration file.</phrase>" msgstr "" #. Tag: para -#: install-methods.xml:594 +#: install-methods.xml:607 #, no-c-format msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 256 MB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose. A second disadvantage is that you cannot copy a full CD image onto the USB stick, but only the smaller businesscard or netinst CD images." msgstr "" #. Tag: para -#: install-methods.xml:604 +#: install-methods.xml:617 #, no-c-format msgid "To use this image simply extract it directly to your USB stick:" msgstr "" #. Tag: screen -#: install-methods.xml:608 +#: install-methods.xml:621 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sdX</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:610 +#: install-methods.xml:623 #, no-c-format msgid "Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:" msgstr "" #. Tag: screen -#: install-methods.xml:616 +#: install-methods.xml:629 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sdX2</replaceable>" msgstr "" #. Tag: para -#: install-methods.xml:618 +#: install-methods.xml:631 #, no-c-format msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a Debian netinst or businesscard ISO image to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done." msgstr "" #. Tag: title -#: install-methods.xml:635 +#: install-methods.xml:648 #, no-c-format msgid "Copying the files — the flexible way" msgstr "" #. Tag: para -#: install-methods.xml:636 +#: install-methods.xml:649 #, no-c-format msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that — if the capacity of your USB stick is large enough — you have the option of copying a full CD ISO image to it." msgstr "" #. Tag: title -#: install-methods.xml:651 install-methods.xml:763 +#: install-methods.xml:664 install-methods.xml:776 #, no-c-format msgid "Partitioning the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:652 +#: install-methods.xml:665 #, no-c-format msgid "We will show how to set up the memory stick to use the first partition, instead of the entire device." msgstr "" #. Tag: para -#: install-methods.xml:657 +#: install-methods.xml:670 #, no-c-format msgid "" "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition<footnote> <para> Don't forget to set the <quote>bootable</quote> bootable flag. </para> </footnote>, and then create the filesystem using: <informalexample><screen>\n" @@ -483,13 +495,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:676 +#: install-methods.xml:689 #, no-c-format msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <classname>lilo</classname>) should work, it's convenient to use <classname>syslinux</classname>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para -#: install-methods.xml:686 +#: install-methods.xml:699 #, no-c-format msgid "" "To put <classname>syslinux</classname> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n" @@ -498,19 +510,19 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:703 install-methods.xml:810 +#: install-methods.xml:716 install-methods.xml:823 #, no-c-format msgid "Adding the installer image" msgstr "" #. Tag: para -#: install-methods.xml:704 +#: install-methods.xml:717 #, no-c-format msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) and copy the following installer image files to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> or <filename>linux</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> </itemizedlist> You can choose between either the regular version or the graphical version of the installer. The latter can be found in the <filename>gtk</filename> subdirectory. If you want to rename the files, please note that <classname>syslinux</classname> can only process DOS (8.3) file names." msgstr "" #. Tag: para -#: install-methods.xml:728 +#: install-methods.xml:741 #, no-c-format msgid "" "Next you should create a <filename>syslinux.cfg</filename> configuration file, which at a bare minimum should contain the following two lines (change the name of the kernel binary to <quote><filename>linux</filename></quote> if you used a <filename>netboot</filename> image): <informalexample><screen>\n" @@ -520,13 +532,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:740 +#: install-methods.xml:753 #, no-c-format msgid "If you used an <filename>hd-media</filename> image, you should now copy a Debian ISO image<footnote> <para> You can use either a businesscard, a netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure to select one that fits. Note that the <quote>netboot <filename>mini.iso</filename></quote> image is not usable for this purpose. </para> </footnote> onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)." msgstr "" #. Tag: para -#: install-methods.xml:764 +#: install-methods.xml:777 #, no-c-format msgid "" "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n" @@ -535,13 +547,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:781 +#: install-methods.xml:794 #, no-c-format msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para -#: install-methods.xml:790 +#: install-methods.xml:803 #, no-c-format msgid "" "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n" @@ -554,37 +566,37 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:811 +#: install-methods.xml:824 #, no-c-format msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) and copy the following installer image files to the stick:" msgstr "" #. Tag: para -#: install-methods.xml:818 +#: install-methods.xml:831 #, no-c-format msgid "<filename>vmlinux</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:823 +#: install-methods.xml:836 #, no-c-format msgid "<filename>initrd.gz</filename> (initial ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:828 +#: install-methods.xml:841 #, no-c-format msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" msgstr "" #. Tag: para -#: install-methods.xml:833 +#: install-methods.xml:846 #, no-c-format msgid "<filename>boot.msg</filename> (optional boot message)" msgstr "" #. Tag: para -#: install-methods.xml:840 +#: install-methods.xml:853 #, no-c-format msgid "" "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n" @@ -602,259 +614,259 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:850 +#: install-methods.xml:863 #, no-c-format msgid "If you used an <filename>hd-media</filename> image, you should now copy a Debian ISO image (businesscard, netinst or full CD image; be sure to select one that fits) onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)." msgstr "" #. Tag: title -#: install-methods.xml:865 +#: install-methods.xml:878 #, no-c-format msgid "Booting the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:866 +#: install-methods.xml:879 #, no-c-format msgid "If your system refuses to boot from the memory stick, the stick may contain an invalid master boot record (MBR). To fix this, use the <command>install-mbr</command> command from the package <classname>mbr</classname>:" msgstr "" #. Tag: screen -#: install-methods.xml:873 +#: install-methods.xml:886 #, no-c-format msgid "# install-mbr /dev/<replaceable>sdX</replaceable>" msgstr "" #. Tag: title -#: install-methods.xml:884 +#: install-methods.xml:897 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "" #. Tag: para -#: install-methods.xml:885 +#: install-methods.xml:898 #, no-c-format msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS." msgstr "" #. Tag: para -#: install-methods.xml:891 +#: install-methods.xml:904 #, no-c-format msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks." msgstr "" #. Tag: para -#: install-methods.xml:898 +#: install-methods.xml:911 #, no-c-format msgid "The installer cannot boot from files on an NTFS file system." msgstr "" #. Tag: para -#: install-methods.xml:902 +#: install-methods.xml:915 #, no-c-format msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download." msgstr "" #. Tag: para -#: install-methods.xml:913 +#: install-methods.xml:926 #, no-c-format msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model." msgstr "" #. Tag: title -#: install-methods.xml:922 +#: install-methods.xml:935 #, no-c-format msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: install-methods.xml:924 +#: install-methods.xml:937 #, no-c-format msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>." msgstr "" #. Tag: para -#: install-methods.xml:930 +#: install-methods.xml:943 #, no-c-format msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel." msgstr "" #. Tag: para -#: install-methods.xml:936 +#: install-methods.xml:949 #, no-c-format msgid "Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>." msgstr "" #. Tag: para -#: install-methods.xml:943 +#: install-methods.xml:956 #, no-c-format msgid "<filename>vmlinuz</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:948 +#: install-methods.xml:961 #, no-c-format msgid "<filename>initrd.gz</filename> (ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:955 +#: install-methods.xml:968 #, no-c-format msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>." msgstr "" #. Tag: title -#: install-methods.xml:965 +#: install-methods.xml:978 #, no-c-format msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:966 +#: install-methods.xml:979 #, no-c-format msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your Debian installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model." msgstr "" #. Tag: para -#: install-methods.xml:979 +#: install-methods.xml:992 #, no-c-format msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on Debian http/ftp mirrors and official Debian CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder." msgstr "" #. Tag: title -#: install-methods.xml:999 +#: install-methods.xml:1012 #, no-c-format msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1000 +#: install-methods.xml:1013 #, no-c-format msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs." msgstr "" #. Tag: para -#: install-methods.xml:1011 +#: install-methods.xml:1024 #, no-c-format msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the Debian archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)." msgstr "" #. Tag: filename -#: install-methods.xml:1021 install-methods.xml:1359 +#: install-methods.xml:1034 install-methods.xml:1372 #, no-c-format msgid "vmlinux" msgstr "" #. Tag: filename -#: install-methods.xml:1026 install-methods.xml:1364 +#: install-methods.xml:1039 install-methods.xml:1377 #, no-c-format msgid "initrd.gz" msgstr "" #. Tag: filename -#: install-methods.xml:1031 install-methods.xml:1369 +#: install-methods.xml:1044 install-methods.xml:1382 #, no-c-format msgid "yaboot" msgstr "" #. Tag: filename -#: install-methods.xml:1036 install-methods.xml:1374 +#: install-methods.xml:1049 install-methods.xml:1387 #, no-c-format msgid "yaboot.conf" msgstr "" #. Tag: para -#: install-methods.xml:1041 +#: install-methods.xml:1054 #, no-c-format msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer." msgstr "" #. Tag: para -#: install-methods.xml:1049 +#: install-methods.xml:1062 #, no-c-format msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1062 +#: install-methods.xml:1075 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "" #. Tag: para -#: install-methods.xml:1063 +#: install-methods.xml:1076 #, no-c-format msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine." msgstr "" #. Tag: para -#: install-methods.xml:1071 +#: install-methods.xml:1084 #, no-c-format msgid "You need to set up a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>." msgstr "" #. Tag: para -#: install-methods.xml:1078 +#: install-methods.xml:1091 #, no-c-format msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP." msgstr "" #. Tag: para -#: install-methods.xml:1092 +#: install-methods.xml:1105 #, no-c-format msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP." msgstr "" #. Tag: para -#: install-methods.xml:1098 +#: install-methods.xml:1111 #, no-c-format msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in Debian." msgstr "" #. Tag: para -#: install-methods.xml:1103 +#: install-methods.xml:1116 #, no-c-format msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux." msgstr "" #. Tag: para -#: install-methods.xml:1111 +#: install-methods.xml:1124 #, no-c-format 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 "" #. Tag: title -#: install-methods.xml:1129 +#: install-methods.xml:1142 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para -#: install-methods.xml:1130 +#: install-methods.xml:1143 #, no-c-format msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>." msgstr "" #. Tag: para -#: install-methods.xml:1142 +#: install-methods.xml:1155 #, no-c-format msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)." msgstr "" #. Tag: title -#: install-methods.xml:1164 +#: install-methods.xml:1177 #, no-c-format msgid "Setting up a BOOTP server" msgstr "" #. Tag: para -#: install-methods.xml:1165 +#: install-methods.xml:1178 #, no-c-format msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively." msgstr "" #. Tag: para -#: install-methods.xml:1173 +#: install-methods.xml:1186 #, no-c-format msgid "" "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run Debian, the line in question should look like: <informalexample><screen>\n" @@ -871,25 +883,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1206 +#: install-methods.xml:1219 #, no-c-format msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1228 +#: install-methods.xml:1241 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1229 +#: install-methods.xml:1242 #, no-c-format msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):" msgstr "" #. Tag: screen -#: install-methods.xml:1236 +#: install-methods.xml:1249 #, no-c-format msgid "" "option domain-name \"example.com\";\n" @@ -914,25 +926,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1238 +#: install-methods.xml:1251 #, no-c-format msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP." msgstr "" #. Tag: para -#: install-methods.xml:1248 +#: install-methods.xml:1261 #, no-c-format msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1256 +#: install-methods.xml:1269 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1257 +#: install-methods.xml:1270 #, no-c-format msgid "" "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n" @@ -967,13 +979,13 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1273 +#: install-methods.xml:1286 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1274 +#: install-methods.xml:1287 #, no-c-format msgid "" "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled. This is usually enabled by having something like the following line in <filename>/etc/inetd.conf</filename>: <informalexample><screen>\n" @@ -982,19 +994,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1286 +#: install-methods.xml:1299 #, no-c-format msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/var/lib/tftpboot</filename>. You may have to adjust the configuration examples in this section accordingly." msgstr "" #. Tag: para -#: install-methods.xml:1296 +#: install-methods.xml:1309 #, no-c-format msgid "Look in <filename>/etc/inetd.conf</filename> and remember the directory which is used as the argument of <command>in.tftpd</command><footnote> <para> All <command>in.tftpd</command> alternatives available in Debian should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors. </para> </footnote>; you'll need that below. 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 "" #. Tag: para -#: install-methods.xml:1316 +#: install-methods.xml:1329 #, no-c-format msgid "" "If you intend to install Debian on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n" @@ -1005,49 +1017,49 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1338 +#: install-methods.xml:1351 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1339 +#: install-methods.xml:1352 #, no-c-format msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards." msgstr "" #. Tag: para -#: install-methods.xml:1348 +#: install-methods.xml:1361 #, no-c-format msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the <filename>netboot/</filename> directory:" msgstr "" #. Tag: filename -#: install-methods.xml:1379 +#: install-methods.xml:1392 #, no-c-format msgid "boot.msg" msgstr "" #. Tag: para -#: install-methods.xml:1384 +#: install-methods.xml:1397 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: para -#: install-methods.xml:1392 +#: install-methods.xml:1405 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: title -#: install-methods.xml:1404 +#: install-methods.xml:1417 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1405 +#: install-methods.xml:1418 #, no-c-format msgid "" "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n" @@ -1056,55 +1068,55 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1421 +#: install-methods.xml:1434 #, no-c-format msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested." msgstr "" #. Tag: para -#: install-methods.xml:1428 +#: install-methods.xml:1441 #, no-c-format msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in." msgstr "" #. Tag: title -#: install-methods.xml:1439 +#: install-methods.xml:1452 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1440 +#: install-methods.xml:1453 #, no-c-format msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>." msgstr "" #. Tag: title -#: install-methods.xml:1548 +#: install-methods.xml:1561 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1549 +#: install-methods.xml:1562 #, no-c-format msgid "For installing on multiple computers it's possible to do fully automatic installations. Debian packages intended for this include <classname>fai</classname> (which uses an install server), <classname>replicator</classname>, <classname>systemimager</classname>, <classname>autoinstall</classname>, and the Debian Installer itself." msgstr "" #. Tag: title -#: install-methods.xml:1562 +#: install-methods.xml:1575 #, no-c-format msgid "Automatic Installation Using the Debian Installer" msgstr "" #. Tag: para -#: install-methods.xml:1563 +#: install-methods.xml:1576 #, no-c-format msgid "The Debian Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process." msgstr "" #. Tag: para -#: install-methods.xml:1570 +#: install-methods.xml:1583 #, no-c-format msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>." msgstr "" diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot index 6612d7992..42fa48285 100644 --- a/po/pot/preseed.pot +++ b/po/pot/preseed.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2009-11-08 01:11+0000\n" +"POT-Creation-Date: 2009-11-18 01:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -27,7 +27,7 @@ msgid "This appendix explains how to preseed answers to questions in &d-i; to au msgstr "" #. Tag: para -#: preseed.xml:23 preseed.xml:667 +#: preseed.xml:23 preseed.xml:669 #, no-c-format msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;." msgstr "" @@ -81,7 +81,7 @@ msgid "initrd" msgstr "" #. Tag: entry -#: preseed.xml:70 preseed.xml:514 +#: preseed.xml:70 preseed.xml:516 #, no-c-format msgid "file" msgstr "" @@ -441,119 +441,143 @@ msgstr "" #. Tag: entry #: preseed.xml:512 #, no-c-format -msgid "locale" +msgid "language" msgstr "" #. Tag: entry #: preseed.xml:512 #, no-c-format -msgid "debian-installer/locale" +msgid "debian-installer/language" msgstr "" #. Tag: entry #: preseed.xml:513 #, no-c-format -msgid "priority" +msgid "country" msgstr "" #. Tag: entry #: preseed.xml:513 #, no-c-format -msgid "debconf/priority" +msgid "debian-installer/country" msgstr "" #. Tag: entry #: preseed.xml:514 #, no-c-format -msgid "preseed/file" +msgid "locale" +msgstr "" + +#. Tag: entry +#: preseed.xml:514 +#, no-c-format +msgid "debian-installer/locale" msgstr "" #. Tag: entry #: preseed.xml:515 #, no-c-format -msgid "<entry>url</entry>" +msgid "priority" msgstr "" #. Tag: entry #: preseed.xml:515 #, no-c-format -msgid "preseed/url" +msgid "debconf/priority" msgstr "" #. Tag: entry #: preseed.xml:516 #, no-c-format +msgid "preseed/file" +msgstr "" + +#. Tag: entry +#: preseed.xml:517 +#, no-c-format +msgid "<entry>url</entry>" +msgstr "" + +#. Tag: entry +#: preseed.xml:517 +#, no-c-format +msgid "preseed/url" +msgstr "" + +#. Tag: entry +#: preseed.xml:518 +#, no-c-format msgid "interface" msgstr "" #. Tag: entry -#: preseed.xml:516 +#: preseed.xml:518 #, no-c-format msgid "netcfg/choose_interface" msgstr "" #. Tag: entry -#: preseed.xml:517 +#: preseed.xml:519 #, no-c-format msgid "hostname " msgstr "" #. Tag: entry -#: preseed.xml:517 +#: preseed.xml:519 #, no-c-format msgid "netcfg/get_hostname" msgstr "" #. Tag: entry -#: preseed.xml:518 +#: preseed.xml:520 #, no-c-format msgid "domain" msgstr "" #. Tag: entry -#: preseed.xml:518 +#: preseed.xml:520 #, no-c-format msgid "netcfg/get_domain" msgstr "" #. Tag: entry -#: preseed.xml:519 +#: preseed.xml:521 #, no-c-format msgid "protocol" msgstr "" #. Tag: entry -#: preseed.xml:519 +#: preseed.xml:521 #, no-c-format msgid "mirror/protocol" msgstr "" #. Tag: entry -#: preseed.xml:520 +#: preseed.xml:522 #, no-c-format msgid "suite" msgstr "" #. Tag: entry -#: preseed.xml:520 +#: preseed.xml:522 #, no-c-format msgid "mirror/suite" msgstr "" #. Tag: title -#: preseed.xml:527 +#: preseed.xml:529 #, no-c-format msgid "Using a DHCP server to specify preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:528 +#: preseed.xml:530 #, no-c-format msgid "It's also possible to use DHCP to specify a preconfiguration file to download from the network. DHCP allows specifying a filename. Normally this is a file to netboot, but if it appears to be an URL then installation media that support network preseeding will download the file from the URL and use it as a preconfiguration file. Here is an example of how to set it up in the dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server Debian package)." msgstr "" #. Tag: screen -#: preseed.xml:539 +#: preseed.xml:541 #, no-c-format msgid "" "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n" @@ -562,85 +586,85 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:541 +#: preseed.xml:543 #, no-c-format msgid "Note that the above example limits this filename to DHCP clients that identify themselves as \"d-i\", so it will not affect regular DHCP clients, but only the installer. You can also put the text in a stanza for only one particular host to avoid preseeding all installs on your network." msgstr "" #. Tag: para -#: preseed.xml:548 +#: preseed.xml:550 #, no-c-format msgid "A good way to use the DHCP preseeding is to only preseed values specific to your network, such as the Debian mirror to use. This way installs on your network will automatically get a good mirror selected, but the rest of the installation can be performed interactively. Using DHCP preseeding to fully automate Debian installs should only be done with care." msgstr "" #. Tag: title -#: preseed.xml:562 +#: preseed.xml:564 #, no-c-format msgid "Creating a preconfiguration file" msgstr "" #. Tag: para -#: preseed.xml:563 +#: preseed.xml:565 #, no-c-format msgid "The preconfiguration file is in the format used by the <command>debconf-set-selections</command> command. The general format of a line in a preconfiguration file is:" msgstr "" #. Tag: screen -#: preseed.xml:569 +#: preseed.xml:571 #, no-c-format msgid "<owner> <question name> <question type> <value>" msgstr "" #. Tag: para -#: preseed.xml:571 +#: preseed.xml:573 #, no-c-format msgid "There are a few rules to keep in mind when writing a preconfiguration file." msgstr "" #. Tag: para -#: preseed.xml:578 +#: preseed.xml:580 #, no-c-format msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value." msgstr "" #. Tag: para -#: preseed.xml:582 +#: preseed.xml:584 #, no-c-format msgid "A line can be split into multiple lines by appending a backslash (<quote><literal>\\</literal></quote>) as the line continuation character. A good place to split a line is after the question name; a bad place is between type and value. Split lines will be joined into a single line with all leading/trailing whitespace condensed to a single space." msgstr "" #. Tag: para -#: preseed.xml:589 +#: preseed.xml:591 #, no-c-format msgid "For debconf variables (templates) used in the installer itself, the owner should be set to <quote>d-i</quote>; to preseed variables used in the installed system, the name of the package that contains the corresponding debconf template should be used. Only variables that have their owner set to something other than <quote>d-i</quote> will be propagated to the debconf database for the installed system." msgstr "" #. Tag: para -#: preseed.xml:597 +#: preseed.xml:599 #, no-c-format msgid "Most questions need to be preseeded using the values valid in English and not the translated values. However, there are some questions (for example in <classname>partman</classname>) where the translated values need to be used." msgstr "" #. Tag: para -#: preseed.xml:603 +#: preseed.xml:605 #, no-c-format msgid "Some questions take a code as value instead of the English text that is shown during installation." msgstr "" #. Tag: para -#: preseed.xml:609 +#: preseed.xml:611 #, no-c-format msgid "The easiest way to create a preconfiguration file is to use the example file linked in <xref linkend=\"preseed-contents\"/> as basis and work from there." msgstr "" #. Tag: para -#: preseed.xml:614 +#: preseed.xml:616 #, no-c-format msgid "An alternative method is to do a manual installation and then, after rebooting, use the <command>debconf-get-selections</command> from the <classname>debconf-utils</classname> package to dump both the debconf database and the installer's cdebconf database to a single file:" msgstr "" #. Tag: screen -#: preseed.xml:621 +#: preseed.xml:623 #, no-c-format msgid "" "$ debconf-get-selections --installer > <replaceable>file</replaceable>\n" @@ -648,81 +672,94 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:623 +#: preseed.xml:625 #, no-c-format msgid "However, a file generated in this manner will have some items that should not be preseeded, and the example file is a better starting place for most users." msgstr "" #. Tag: para -#: preseed.xml:631 +#: preseed.xml:633 #, no-c-format msgid "This method relies on the fact that, at the end of the installation, the installer's cdebconf database is saved to the installed system in <filename>/var/log/installer/cdebconf</filename>. However, because the database may contain sensitive information, by default the files are only readable by root." msgstr "" #. Tag: para -#: preseed.xml:639 +#: preseed.xml:641 #, no-c-format msgid "The directory <filename>/var/log/installer</filename> and all files in it will be deleted from your system if you purge the package <classname>installation-report</classname>." msgstr "" #. Tag: para -#: preseed.xml:647 +#: preseed.xml:649 #, no-c-format msgid "To check possible values for questions, you can use <command>nano</command> to examine the files in <filename>/var/lib/cdebconf</filename> while an installation is in progress. View <filename>templates.dat</filename> for the raw templates and <filename>questions.dat</filename> for the current values and for the values assigned to variables." msgstr "" #. Tag: para -#: preseed.xml:655 +#: preseed.xml:657 #, no-c-format msgid "To check if the format of your preconfiguration file is valid before performing an install, you can use the command <command>debconf-set-selections -c <replaceable>preseed.cfg</replaceable></command>." msgstr "" #. Tag: title -#: preseed.xml:666 +#: preseed.xml:668 #, no-c-format msgid "Contents of the preconfiguration file (for &releasename;)" msgstr "" #. Tag: para -#: preseed.xml:672 +#: preseed.xml:674 #, no-c-format msgid "Note that this example is based on an installation for the Intel x86 architecture. If you are installing a different architecture, some of the examples (like keyboard selection and bootloader installation) may not be relevant and will need to be replaced by debconf settings appropriate for your architecture." msgstr "" #. Tag: title -#: preseed.xml:683 +#: preseed.xml:685 #, no-c-format msgid "Localization" msgstr "" #. Tag: para -#: preseed.xml:684 +#: preseed.xml:686 #, no-c-format msgid "Setting localization values will only work if you are using initrd preseeding. With all other methods the preconfiguration file will only be loaded after these questions have been asked." msgstr "" #. Tag: para -#: preseed.xml:690 +#: preseed.xml:692 #, no-c-format msgid "The locale can be used to specify both language and country and can be any combination of a language supported by &d-i; and a recognized country. If the combination does not form a valid locale, the installer will automatically select a locale that is valid for the selected language. To specify the locale as a boot parameter, use <userinput>locale=<replaceable>en_US</replaceable></userinput>." msgstr "" +#. Tag: para +#: preseed.xml:701 +#, no-c-format +msgid "Although this method is very easy to use, it does not allow preseeding of all possible combinations of language, country and locale<footnote> <para> Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would for example result in <literal>en_US.UTF-8</literal> as default locale for the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred instead, the values will need to be preseeded individually. </para> </footnote>. So alternatively the values can be preseeded individually. Language and country can also be specified as boot parameters." +msgstr "" + #. Tag: screen -#: preseed.xml:699 +#: preseed.xml:716 #, no-c-format msgid "" - "# Locale sets language and country.\n" - "d-i debian-installer/locale string en_US" + "# Preseeding only locale sets language, country and locale.\n" + "d-i debian-installer/locale string en_US\n" + "\n" + "# The values can also be preseeded individually for greater flexibility.\n" + "#d-i debian-installer/language string en\n" + "#d-i debian-installer/country string NL\n" + "#d-i debian-installer/locale string en_GB.UTF-8\n" + "# Optionally specify additional locales to be generated.\n" + "#d-i localechooser/supported-locales en_US.UTF-8, nl_NL.UTF-8" msgstr "" #. Tag: para -#: preseed.xml:701 +#: preseed.xml:718 #, no-c-format msgid "Keyboard configuration consists of selecting a keyboard architecture and a keymap. In most cases the correct keyboard architecture is selected by default, so there's normally no need to preseed it. The keymap must be known to the &d-i; for the selected keyboard architecture." msgstr "" #. Tag: screen -#: preseed.xml:708 +#: preseed.xml:725 #, no-c-format msgid "" "# Keyboard selection.\n" @@ -733,55 +770,55 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:710 +#: preseed.xml:727 #, no-c-format msgid "To skip keyboard configuration, preseed <classname>console-tools/archs</classname> with <userinput>skip-config</userinput>. This will result in the kernel keymap remaining active." msgstr "" #. Tag: para -#: preseed.xml:719 +#: preseed.xml:736 #, no-c-format msgid "The changes in the input layer for 2.6 kernels have made the keyboard architecture virtually obsolete. For 2.6 kernels normally a <quote>PC</quote> (<userinput>at</userinput>) keymap should be selected." msgstr "" #. Tag: title -#: preseed.xml:729 +#: preseed.xml:746 #, no-c-format msgid "Network configuration" msgstr "" #. Tag: para -#: preseed.xml:730 +#: preseed.xml:747 #, no-c-format msgid "Of course, preseeding the network configuration won't work if you're loading your preconfiguration file from the network. But it's great when you're booting from CD or USB stick. If you are loading preconfiguration files from the network, you can pass network config parameters by using kernel boot parameters." msgstr "" #. Tag: para -#: preseed.xml:738 +#: preseed.xml:755 #, no-c-format msgid "If you need to pick a particular interface when netbooting before loading a preconfiguration file from the network, use a boot parameter such as <userinput>interface=<replaceable>eth1</replaceable></userinput>." msgstr "" #. Tag: para -#: preseed.xml:744 +#: preseed.xml:761 #, no-c-format msgid "Although preseeding the network configuration is normally not possible when using network preseeding (using <quote>preseed/url</quote>), you can use the following hack to work around that, for example if you'd like to set a static address for the network interface. The hack is to force the network configuration to run again after the preconfiguration file has been loaded by creating a <quote>preseed/run</quote> script containing the following commands:" msgstr "" #. Tag: screen -#: preseed.xml:754 +#: preseed.xml:771 #, no-c-format msgid "killall.sh; netcfg" msgstr "" #. Tag: para -#: preseed.xml:756 +#: preseed.xml:773 #, no-c-format msgid "The following debconf variables are relevant for network configuration." msgstr "" #. Tag: screen -#: preseed.xml:762 +#: preseed.xml:779 #, no-c-format msgid "" "# Disable network configuration entirely. This is useful for cdrom\n" @@ -835,19 +872,19 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:764 +#: preseed.xml:781 #, no-c-format msgid "Please note that <command>netcfg</command> will automatically determine the netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In this case, the variable has to be marked as <literal>seen</literal> for automatic installations. Similarly, <command>netcfg</command> will choose an appropriate address if <classname>netcfg/get_gateway</classname> is not set. As a special case, you can set <classname>netcfg/get_gateway</classname> to <quote>none</quote> to specify that no gateway should be used." msgstr "" #. Tag: title -#: preseed.xml:780 +#: preseed.xml:797 #, no-c-format msgid "Network console" msgstr "" #. Tag: screen -#: preseed.xml:782 +#: preseed.xml:799 #, no-c-format msgid "" "# Use the following settings if you wish to make use of the network-console\n" @@ -859,31 +896,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:787 +#: preseed.xml:804 #, no-c-format msgid "Mirror settings" msgstr "" #. Tag: para -#: preseed.xml:788 +#: preseed.xml:805 #, no-c-format msgid "Depending on the installation method you use, a mirror may be used to download additional components of the installer, to install the base system, and to set up the <filename>/etc/apt/sources.list</filename> for the installed system." msgstr "" #. Tag: para -#: preseed.xml:795 +#: preseed.xml:812 #, no-c-format msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system." msgstr "" #. Tag: para -#: preseed.xml:800 +#: preseed.xml:817 #, no-c-format msgid "The parameter <classname>mirror/udeb/suite</classname> determines the suite for additional components for the installer. It is only useful to set this if components are actually downloaded over the network and should match the suite that was used to build the initrd for the installation method used for the installation. Normally the installer will automatically use the correct value and there should be no need to set this." msgstr "" #. Tag: screen -#: preseed.xml:811 +#: preseed.xml:828 #, no-c-format msgid "" "# If you select ftp, the mirror/country string does not need to be set.\n" @@ -900,13 +937,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:816 +#: preseed.xml:833 #, no-c-format msgid "Clock and time zone setup" msgstr "" #. Tag: screen -#: preseed.xml:818 +#: preseed.xml:835 #, no-c-format msgid "" "# Controls whether or not the hardware clock is set to UTC.\n" @@ -923,25 +960,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:823 +#: preseed.xml:840 #, no-c-format msgid "Partitioning" msgstr "" #. Tag: para -#: preseed.xml:824 +#: preseed.xml:841 #, no-c-format msgid "Using preseeding to partition the harddisk is very much limited to what is supported by <classname>partman-auto</classname>. You can choose to partition either existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file. It is currently not possible to partition multiple disks using preseeding." msgstr "" #. Tag: para -#: preseed.xml:835 +#: preseed.xml:852 #, no-c-format msgid "The identification of disks is dependent on the order in which their drivers are loaded. If there are multiple disks in the system, make very sure the correct one will be selected before using preseeding." msgstr "" #. Tag: screen -#: preseed.xml:843 +#: preseed.xml:860 #, no-c-format msgid "" "# If the system has free space you can choose to only partition that space.\n" @@ -1006,25 +1043,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:848 +#: preseed.xml:865 #, no-c-format msgid "Partitioning using RAID" msgstr "" #. Tag: para -#: preseed.xml:849 +#: preseed.xml:866 #, no-c-format msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and specifying spare devices. If you are using RAID 1, you can preseed grub to install to all devices used in the array; see <xref linkend=\"preseed-bootloader\"/>." msgstr "" #. Tag: para -#: preseed.xml:859 +#: preseed.xml:876 #, no-c-format msgid "This type of automated partitioning is easy to get wrong. It is also functionality that receives relatively little testing from the developers of &d-i;. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check <filename>/var/log/syslog</filename> if you run into problems." msgstr "" #. Tag: screen -#: preseed.xml:869 +#: preseed.xml:886 #, no-c-format msgid "" "# NOTE: this option is of beta release quality and should be used carefully\n" @@ -1074,31 +1111,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:874 +#: preseed.xml:891 #, no-c-format msgid "Controlling how partitions are mounted" msgstr "" #. Tag: para -#: preseed.xml:875 +#: preseed.xml:892 #, no-c-format msgid "Normally, filesystems are mounted using a universally unique identifier (UUID) as a key; this allows them to be mounted properly even if their device name changes. UUIDs are long and difficult to read, so, if you prefer, the installer can mount filesystems based on the traditional device names, or based on a label you assign. If you ask the installer to mount by label, any filesystems without a label will be mounted using a UUID instead." msgstr "" #. Tag: para -#: preseed.xml:884 +#: preseed.xml:901 #, no-c-format msgid "Devices with stable names, such as LVM logical volumes, will continue to use their traditional names rather than UUIDs." msgstr "" #. Tag: para -#: preseed.xml:891 +#: preseed.xml:908 #, no-c-format msgid "Traditional device names may change based on the order in which the kernel discovers devices at boot, which may cause the wrong filesystem to be mounted. Similarly, labels are likely to clash if you plug in a new disk or a USB drive, and if that happens your system's behaviour when started will be random." msgstr "" #. Tag: screen -#: preseed.xml:901 +#: preseed.xml:918 #, no-c-format msgid "" "# The default is to mount by UUID, but you can also choose \"traditional\" to\n" @@ -1108,19 +1145,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:906 +#: preseed.xml:923 #, no-c-format msgid "Base system installation" msgstr "" #. Tag: para -#: preseed.xml:907 +#: preseed.xml:924 #, no-c-format msgid "There is actually not very much that can be preseeded for this stage of the installation. The only questions asked concern the installation of the kernel." msgstr "" #. Tag: screen -#: preseed.xml:914 +#: preseed.xml:931 #, no-c-format msgid "" "# Configure APT to not install recommended packages by default. Use of this\n" @@ -1137,25 +1174,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:919 +#: preseed.xml:936 #, no-c-format msgid "Account setup" msgstr "" #. Tag: para -#: preseed.xml:920 +#: preseed.xml:937 #, no-c-format msgid "The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear text values or MD5 <emphasis>hashes</emphasis>." msgstr "" #. Tag: para -#: preseed.xml:927 +#: preseed.xml:944 #, no-c-format msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these passwords. Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks." msgstr "" #. Tag: screen -#: preseed.xml:937 +#: preseed.xml:954 #, no-c-format msgid "" "# Skip creation of a root account (normal user account will be able to\n" @@ -1187,37 +1224,37 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:939 +#: preseed.xml:956 #, no-c-format msgid "The <classname>passwd/root-password-crypted</classname> and <classname>passwd/user-password-crypted</classname> variables can also be preseeded with <quote>!</quote> as their value. In that case, the corresponding account is disabled. This may be convenient for the root account, provided of course that an alternative method is set up to allow administrative activities or root login (for instance by using SSH key authentication or <command>sudo</command>)." msgstr "" #. Tag: para -#: preseed.xml:949 +#: preseed.xml:966 #, no-c-format msgid "The following command can be used to generate an MD5 hash for a password:" msgstr "" #. Tag: screen -#: preseed.xml:953 +#: preseed.xml:970 #, no-c-format msgid "$ printf \"r00tme\" | mkpasswd -s -m md5" msgstr "" #. Tag: title -#: preseed.xml:959 +#: preseed.xml:976 #, no-c-format msgid "Apt setup" msgstr "" #. Tag: para -#: preseed.xml:960 +#: preseed.xml:977 #, no-c-format msgid "Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration options is fully automated based on your installation method and answers to earlier questions. You can optionally add other (local) repositories." msgstr "" #. Tag: screen -#: preseed.xml:968 +#: preseed.xml:985 #, no-c-format msgid "" "# You can choose to install non-free and contrib software.\n" @@ -1249,97 +1286,97 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:973 +#: preseed.xml:990 #, no-c-format msgid "Package selection" msgstr "" #. Tag: para -#: preseed.xml:974 +#: preseed.xml:991 #, no-c-format msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:" msgstr "" #. Tag: userinput -#: preseed.xml:983 +#: preseed.xml:1000 #, no-c-format msgid "standard" msgstr "" #. Tag: userinput -#: preseed.xml:986 +#: preseed.xml:1003 #, no-c-format msgid "desktop" msgstr "" #. Tag: userinput -#: preseed.xml:989 +#: preseed.xml:1006 #, no-c-format msgid "gnome-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:992 +#: preseed.xml:1009 #, no-c-format msgid "kde-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:995 +#: preseed.xml:1012 #, no-c-format msgid "web-server" msgstr "" #. Tag: userinput -#: preseed.xml:998 +#: preseed.xml:1015 #, no-c-format msgid "print-server" msgstr "" #. Tag: userinput -#: preseed.xml:1001 +#: preseed.xml:1018 #, no-c-format msgid "dns-server" msgstr "" #. Tag: userinput -#: preseed.xml:1004 +#: preseed.xml:1021 #, no-c-format msgid "file-server" msgstr "" #. Tag: userinput -#: preseed.xml:1007 +#: preseed.xml:1024 #, no-c-format msgid "mail-server" msgstr "" #. Tag: userinput -#: preseed.xml:1010 +#: preseed.xml:1027 #, no-c-format msgid "sql-database" msgstr "" #. Tag: userinput -#: preseed.xml:1013 +#: preseed.xml:1030 #, no-c-format msgid "laptop" msgstr "" #. Tag: para -#: preseed.xml:1017 +#: preseed.xml:1034 #, no-c-format msgid "You can also choose to install no tasks, and force the installation of a set of packages in some other way. We recommend always including the <userinput>standard</userinput> task." msgstr "" #. Tag: para -#: preseed.xml:1023 +#: preseed.xml:1040 #, no-c-format msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well." msgstr "" #. Tag: screen -#: preseed.xml:1033 +#: preseed.xml:1050 #, no-c-format msgid "" "#tasksel tasksel/first multiselect standard, web-server\n" @@ -1363,13 +1400,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1038 +#: preseed.xml:1055 #, no-c-format msgid "Boot loader installation" msgstr "" #. Tag: screen -#: preseed.xml:1040 +#: preseed.xml:1057 #, no-c-format msgid "" "# Grub is the default boot loader (for x86). If you want lilo installed\n" @@ -1408,19 +1445,19 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:1042 +#: preseed.xml:1059 #, no-c-format msgid "An MD5 hash for a password for <classname>grub</classname> can be generated using <command>grub-md5-crypt</command>, or using the command from the example in <xref linkend=\"preseed-account\"/>." msgstr "" #. Tag: title -#: preseed.xml:1052 +#: preseed.xml:1069 #, no-c-format msgid "Finishing up the installation" msgstr "" #. Tag: screen -#: preseed.xml:1054 +#: preseed.xml:1071 #, no-c-format msgid "" "# During installations from serial console, the regular virtual consoles\n" @@ -1443,13 +1480,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1059 +#: preseed.xml:1076 #, no-c-format msgid "Preseeding other packages" msgstr "" #. Tag: screen -#: preseed.xml:1061 +#: preseed.xml:1078 #, no-c-format msgid "" "# Depending on what software you choose to install, or if things go wrong\n" @@ -1462,25 +1499,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1068 +#: preseed.xml:1085 #, no-c-format msgid "Advanced options" msgstr "" #. Tag: title -#: preseed.xml:1071 +#: preseed.xml:1088 #, no-c-format msgid "Running custom commands during the installation" msgstr "" #. Tag: para -#: preseed.xml:1072 +#: preseed.xml:1089 #, no-c-format msgid "A very powerful and flexible option offered by the preconfiguration tools is the ability to run commands or scripts at certain points in the installation." msgstr "" #. Tag: screen -#: preseed.xml:1080 +#: preseed.xml:1097 #, no-c-format msgid "" "# d-i preseeding is inherently not secure. Nothing in the installer checks\n" @@ -1506,13 +1543,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1085 +#: preseed.xml:1102 #, no-c-format msgid "Using preseeding to change default values" msgstr "" #. Tag: para -#: preseed.xml:1086 +#: preseed.xml:1103 #, no-c-format msgid "" "It is possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a question. <informalexample><screen>\n" @@ -1522,31 +1559,31 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:1100 +#: preseed.xml:1117 #, no-c-format msgid "Note that the <quote>d-i</quote> owner should only be used for variables used in the installer itself. For variables belonging to packages installed on the target system, you should use the name of that package instead. See the footnote to <xref linkend=\"preseed-bootparms\"/>." msgstr "" #. Tag: para -#: preseed.xml:1107 +#: preseed.xml:1124 #, no-c-format msgid "If you are preseeding using boot parameters, you can make the installer ask the corresponding question by using the <quote>?=</quote> operator, i.e. <userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?=<replaceable>value</replaceable></userinput> (or <userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</replaceable>?=<replaceable>value</replaceable></userinput>). This will of course only have effect for parameters that correspond to questions that are actually displayed during an installation and not for <quote>internal</quote> parameters." msgstr "" #. Tag: title -#: preseed.xml:1121 +#: preseed.xml:1138 #, no-c-format msgid "Chainloading preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:1122 +#: preseed.xml:1139 #, no-c-format msgid "It is possible to include other preconfiguration files from a preconfiguration file. Any settings in those files will override pre-existing settings from files loaded earlier. This makes it possible to put, for example, general networking settings for your location in one file and more specific settings for certain configurations in other files." msgstr "" #. Tag: screen -#: preseed.xml:1132 +#: preseed.xml:1149 #, no-c-format msgid "" "# More than one file can be listed, separated by spaces; all will be\n" @@ -1574,7 +1611,7 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:1134 +#: preseed.xml:1151 #, no-c-format msgid "It is also possible to chainload from the initrd or file preseeding phase, into network preseeding by setting preseed/url in the earlier files. This will cause network preseeding to be performed when the network comes up. You need to be careful when doing this, since there will be two distinct runs at preseeding, meaning for example that you get another chance to run the preseed/early command, the second one happening after the network comes up." msgstr "" |