diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 148 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 1004 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 305 |
3 files changed, 747 insertions, 710 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index b4048e6c9..fd4185119 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: 2006-12-25 20:11+0000\n" +"POT-Creation-Date: 2006-12-26 01:54+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" @@ -2012,7 +2012,7 @@ msgid "Set to <userinput>false</userinput> to prevent probing for USB on boot, i msgstr "" #. Tag: term -#: boot-installer.xml:3000 boot-installer.xml:3153 +#: boot-installer.xml:3000 boot-installer.xml:3167 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" @@ -2164,47 +2164,59 @@ msgstr "" #. Tag: para #: boot-installer.xml:3141 #, 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. Short form: <userinput>locale</userinput>. For example, use <userinput>locale=de_CH</userinput> to select German as language and Switserland as country." +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. Short form: <userinput>locale</userinput>. For example, use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3153 +#, no-c-format +msgid "anna/choose_modules" msgstr "" #. Tag: para #: boot-installer.xml:3154 #, no-c-format +msgid "Can be used to automatically load installer components that are not loaded by default. Short form: <userinput>modules</userinput>. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation) and <classname>ppp-udeb</classname> (which supports PPPoE configuration)." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3168 +#, 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:3163 +#: boot-installer.xml:3177 #, no-c-format msgid "tasksel:tasksel/first" msgstr "" #. Tag: para -#: boot-installer.xml:3164 +#: boot-installer.xml:3178 #, 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. Short form: <userinput>tasks</userinput>." msgstr "" #. Tag: title -#: boot-installer.xml:3178 +#: boot-installer.xml:3192 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:3179 +#: boot-installer.xml:3193 #, 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:3192 +#: boot-installer.xml:3206 #, 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:3199 +#: boot-installer.xml:3213 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -2213,109 +2225,109 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3209 +#: boot-installer.xml:3223 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:3221 +#: boot-installer.xml:3235 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:3226 +#: boot-installer.xml:3240 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3227 +#: boot-installer.xml:3241 #, 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:3234 +#: boot-installer.xml:3248 #, no-c-format msgid "There are a 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:3240 +#: boot-installer.xml:3254 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:3245 +#: boot-installer.xml:3259 #, 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:3251 +#: boot-installer.xml:3265 #, 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:3261 +#: boot-installer.xml:3275 #, 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:3267 +#: boot-installer.xml:3281 #, 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:3275 +#: boot-installer.xml:3289 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:3278 +#: boot-installer.xml:3292 #, 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:3284 +#: boot-installer.xml:3298 #, 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:3291 +#: boot-installer.xml:3305 #, 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:3302 +#: boot-installer.xml:3316 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:3303 +#: boot-installer.xml:3317 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:3308 +#: boot-installer.xml:3322 #, 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:3314 +#: boot-installer.xml:3328 #, 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" @@ -2325,7 +2337,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3327 +#: boot-installer.xml:3341 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -2338,19 +2350,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3332 +#: boot-installer.xml:3346 #, 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:3344 +#: boot-installer.xml:3358 #, 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:3351 +#: boot-installer.xml:3365 #, 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" @@ -2363,13 +2375,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3365 +#: boot-installer.xml:3379 #, 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/cdroms/cdrom0</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:3373 +#: boot-installer.xml:3387 #, 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" @@ -2378,7 +2390,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3383 +#: boot-installer.xml:3397 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -2391,205 +2403,205 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3398 +#: boot-installer.xml:3412 #, 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:3413 +#: boot-installer.xml:3427 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3415 +#: boot-installer.xml:3429 #, 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:3420 +#: boot-installer.xml:3434 #, 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:3429 +#: boot-installer.xml:3443 #, 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:3438 +#: boot-installer.xml:3452 #, 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:3444 +#: boot-installer.xml:3458 #, 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:3450 +#: boot-installer.xml:3464 #, 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:3459 +#: boot-installer.xml:3473 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:3461 +#: boot-installer.xml:3475 #, 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:3468 +#: boot-installer.xml:3482 #, no-c-format msgid "If you are booting with your own kernel instead of the one supplied with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3475 +#: boot-installer.xml:3489 #, 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:3481 +#: boot-installer.xml:3495 #, 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:3492 +#: boot-installer.xml:3506 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3493 +#: boot-installer.xml:3507 #, 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:3498 +#: boot-installer.xml:3512 #, 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:3504 +#: boot-installer.xml:3518 #, 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:3513 +#: boot-installer.xml:3527 #, 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:3520 +#: boot-installer.xml:3534 #, 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 video=vga16:off</userinput> to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" #. Tag: title -#: boot-installer.xml:3534 +#: boot-installer.xml:3548 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:3535 +#: boot-installer.xml:3549 #, 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:3545 +#: boot-installer.xml:3559 #, 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:3562 +#: boot-installer.xml:3576 #, no-c-format msgid "System Freeze while Loading the USB Modules" msgstr "" #. Tag: para -#: boot-installer.xml:3563 +#: boot-installer.xml:3577 #, 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>debian-installer/probe/usb=false</userinput> parameter at the boot prompt, which will prevent the modules from being loaded." msgstr "" #. Tag: title -#: boot-installer.xml:3577 +#: boot-installer.xml:3591 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3579 +#: boot-installer.xml:3593 #, 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:3604 +#: boot-installer.xml:3618 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3605 +#: boot-installer.xml:3619 #, 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:3616 +#: boot-installer.xml:3630 #, 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:3627 +#: boot-installer.xml:3641 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3628 +#: boot-installer.xml:3642 #, 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:3635 +#: boot-installer.xml:3649 #, 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:3641 +#: boot-installer.xml:3655 #, no-c-format msgid "If you have a working Debian system, the easiest way to send an installation report is to install the installation-report and reportbug packages (<command>apt-get install installation-report reportbug</command>) and run the command <command>reportbug installation-report</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3648 +#: boot-installer.xml:3662 #, 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 a2fff05c3..72b28ff66 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: 2006-12-25 19:53+0000\n" +"POT-Creation-Date: 2006-12-26 01:54+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" @@ -315,13 +315,13 @@ msgid "DECstation" msgstr "" #. Tag: entry -#: hardware.xml:136 hardware.xml:1107 hardware.xml:1122 hardware.xml:1132 +#: hardware.xml:136 hardware.xml:1104 hardware.xml:1119 hardware.xml:1129 #, no-c-format msgid "r4k-kn04" msgstr "" #. Tag: entry -#: hardware.xml:138 hardware.xml:1102 hardware.xml:1112 hardware.xml:1117 hardware.xml:1127 +#: hardware.xml:138 hardware.xml:1099 hardware.xml:1109 hardware.xml:1114 hardware.xml:1124 #, no-c-format msgid "r3k-kn02" msgstr "" @@ -447,1513 +447,1501 @@ msgid "<entry>prep</entry>" msgstr "" #. Tag: entry -#: hardware.xml:179 -#, no-c-format -msgid "APUS" -msgstr "" - -#. Tag: entry -#: hardware.xml:180 -#, no-c-format -msgid "<entry>apus</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:184 +#: hardware.xml:181 #, no-c-format msgid "Sun SPARC" msgstr "" #. Tag: entry -#: hardware.xml:185 +#: hardware.xml:182 #, no-c-format msgid "sparc" msgstr "" #. Tag: entry -#: hardware.xml:187 +#: hardware.xml:184 #, no-c-format msgid "sun4cdm" msgstr "" #. Tag: entry -#: hardware.xml:189 +#: hardware.xml:186 #, no-c-format -msgid "sun4u" +msgid "<entry>sun4u</entry>" msgstr "" #. Tag: entry -#: hardware.xml:193 +#: hardware.xml:190 #, no-c-format msgid "IBM S/390" msgstr "" #. Tag: entry -#: hardware.xml:194 +#: hardware.xml:191 #, no-c-format msgid "s390" msgstr "" #. Tag: entry -#: hardware.xml:195 +#: hardware.xml:192 #, no-c-format msgid "IPL from VM-reader and DASD" msgstr "" #. Tag: entry -#: hardware.xml:196 +#: hardware.xml:193 #, no-c-format msgid "generic" msgstr "" #. Tag: entry -#: hardware.xml:198 +#: hardware.xml:195 #, no-c-format msgid "IPL from tape" msgstr "" #. Tag: entry -#: hardware.xml:199 +#: hardware.xml:196 #, no-c-format msgid "tape" msgstr "" #. Tag: para -#: hardware.xml:204 +#: hardware.xml:201 #, no-c-format msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture. If you are looking for information on any of the other Debian-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">Debian-Ports</ulink> pages." msgstr "" #. Tag: para -#: hardware.xml:212 +#: hardware.xml:209 #, no-c-format msgid "This is the first official release of &debian; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well." msgstr "" #. Tag: title -#: hardware.xml:234 hardware.xml:693 hardware.xml:729 hardware.xml:822 hardware.xml:841 hardware.xml:927 hardware.xml:969 hardware.xml:1037 hardware.xml:1196 hardware.xml:1642 +#: hardware.xml:231 hardware.xml:690 hardware.xml:726 hardware.xml:819 hardware.xml:838 hardware.xml:924 hardware.xml:966 hardware.xml:1034 hardware.xml:1193 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para -#: hardware.xml:235 +#: hardware.xml:232 #, no-c-format msgid "Complete information regarding supported DEC Alphas can be found at <ulink url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this section is to describe the systems supported by the boot disks." msgstr "" #. Tag: para -#: hardware.xml:242 +#: hardware.xml:239 #, no-c-format msgid "Alpha machines are subdivided into different system types because there are a number of generations of motherboard and supporting chipsets. Different systems (<quote>sub-architectures</quote>) often have radically different engineering and capabilities. Therefore, the process of installing and, more to the point, booting, can vary from system to system." msgstr "" #. Tag: para -#: hardware.xml:250 +#: hardware.xml:247 #, no-c-format msgid "The following table lists the system types supported by the Debian installation system. The table also indicates the <emphasis>code name</emphasis> for these system types. You'll need to know this code name when you actually begin the installation process:" msgstr "" #. Tag: entry -#: hardware.xml:267 +#: hardware.xml:264 #, no-c-format msgid "Hardware Type" msgstr "" #. Tag: entry -#: hardware.xml:268 +#: hardware.xml:265 #, no-c-format msgid "Aliases" msgstr "" #. Tag: entry -#: hardware.xml:268 +#: hardware.xml:265 #, no-c-format msgid "MILO image" msgstr "" #. Tag: entry -#: hardware.xml:274 +#: hardware.xml:271 #, no-c-format msgid "ALCOR" msgstr "" #. Tag: entry -#: hardware.xml:275 +#: hardware.xml:272 #, no-c-format msgid "AlphaStation 500 5/266.300" msgstr "" #. Tag: entry -#: hardware.xml:276 +#: hardware.xml:273 #, no-c-format msgid "Maverick" msgstr "" #. Tag: entry -#: hardware.xml:277 hardware.xml:281 hardware.xml:285 +#: hardware.xml:274 hardware.xml:278 hardware.xml:282 #, no-c-format msgid "alcor" msgstr "" #. Tag: entry -#: hardware.xml:279 +#: hardware.xml:276 #, no-c-format msgid "AlphaStation 500 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:280 +#: hardware.xml:277 #, no-c-format msgid "Bret" msgstr "" #. Tag: entry -#: hardware.xml:283 +#: hardware.xml:280 #, no-c-format msgid "AlphaStation 600/266...300" msgstr "" #. Tag: entry -#: hardware.xml:284 +#: hardware.xml:281 #, no-c-format msgid "Alcor" msgstr "" #. Tag: entry -#: hardware.xml:287 +#: hardware.xml:284 #, no-c-format msgid "AlphaStation 600/300...433" msgstr "" #. Tag: entry -#: hardware.xml:288 +#: hardware.xml:285 #, no-c-format msgid "<entry>XLT</entry>" msgstr "" #. Tag: entry -#: hardware.xml:289 +#: hardware.xml:286 #, no-c-format msgid "<entry>xlt</entry>" msgstr "" #. Tag: entry -#: hardware.xml:293 +#: hardware.xml:290 #, no-c-format msgid "BOOK1" msgstr "" #. Tag: entry -#: hardware.xml:294 +#: hardware.xml:291 #, no-c-format msgid "AlphaBook1 (laptop)" msgstr "" #. Tag: entry -#: hardware.xml:295 +#: hardware.xml:292 #, no-c-format msgid "Alphabook1/Burns" msgstr "" #. Tag: entry -#: hardware.xml:296 +#: hardware.xml:293 #, no-c-format msgid "book1" msgstr "" #. Tag: entry -#: hardware.xml:300 +#: hardware.xml:297 #, no-c-format msgid "AVANTI" msgstr "" #. Tag: entry -#: hardware.xml:301 +#: hardware.xml:298 #, no-c-format msgid "AlphaStation 200 4/100...166" msgstr "" #. Tag: entry -#: hardware.xml:302 +#: hardware.xml:299 #, no-c-format msgid "Mustang" msgstr "" #. Tag: entry -#: hardware.xml:303 hardware.xml:307 hardware.xml:311 hardware.xml:315 hardware.xml:319 hardware.xml:323 hardware.xml:327 hardware.xml:331 +#: hardware.xml:300 hardware.xml:304 hardware.xml:308 hardware.xml:312 hardware.xml:316 hardware.xml:320 hardware.xml:324 hardware.xml:328 #, no-c-format msgid "avanti" msgstr "" #. Tag: entry -#: hardware.xml:305 +#: hardware.xml:302 #, no-c-format msgid "AlphaStation 200 4/233" msgstr "" #. Tag: entry -#: hardware.xml:306 +#: hardware.xml:303 #, no-c-format msgid "Mustang+" msgstr "" #. Tag: entry -#: hardware.xml:309 +#: hardware.xml:306 #, no-c-format msgid "AlphaStation 205 4/133...333" msgstr "" #. Tag: entry -#: hardware.xml:310 +#: hardware.xml:307 #, no-c-format msgid "<entry>LX3</entry>" msgstr "" #. Tag: entry -#: hardware.xml:313 +#: hardware.xml:310 #, no-c-format msgid "AlphaStation 250 4/300" msgstr "" #. Tag: entry -#: hardware.xml:314 +#: hardware.xml:311 #, no-c-format msgid "<entry>M3+</entry>" msgstr "" #. Tag: entry -#: hardware.xml:317 +#: hardware.xml:314 #, no-c-format msgid "AlphaStation 255 4/133...333" msgstr "" #. Tag: entry -#: hardware.xml:318 +#: hardware.xml:315 #, no-c-format msgid "LX3+" msgstr "" #. Tag: entry -#: hardware.xml:321 +#: hardware.xml:318 #, no-c-format msgid "AlphaStation 300 4/266" msgstr "" #. Tag: entry -#: hardware.xml:322 +#: hardware.xml:319 #, no-c-format msgid "Melmac" msgstr "" #. Tag: entry -#: hardware.xml:325 +#: hardware.xml:322 #, no-c-format msgid "AlphaStation 400 4/166" msgstr "" #. Tag: entry -#: hardware.xml:326 +#: hardware.xml:323 #, no-c-format msgid "Chinet" msgstr "" #. Tag: entry -#: hardware.xml:329 +#: hardware.xml:326 #, no-c-format msgid "AlphaStation 400 4/233...300" msgstr "" #. Tag: entry -#: hardware.xml:330 +#: hardware.xml:327 #, no-c-format msgid "Avanti" msgstr "" #. Tag: entry -#: hardware.xml:335 hardware.xml:348 hardware.xml:349 +#: hardware.xml:332 hardware.xml:345 hardware.xml:346 #, no-c-format msgid "EB164" msgstr "" #. Tag: entry -#: hardware.xml:336 +#: hardware.xml:333 #, no-c-format msgid "AlphaPC164" msgstr "" #. Tag: entry -#: hardware.xml:337 +#: hardware.xml:334 #, no-c-format msgid "PC164" msgstr "" #. Tag: entry -#: hardware.xml:338 +#: hardware.xml:335 #, no-c-format msgid "pc164" msgstr "" #. Tag: entry -#: hardware.xml:340 +#: hardware.xml:337 #, no-c-format msgid "AlphaPC164-LX" msgstr "" #. Tag: entry -#: hardware.xml:341 +#: hardware.xml:338 #, no-c-format msgid "LX164" msgstr "" #. Tag: entry -#: hardware.xml:342 +#: hardware.xml:339 #, no-c-format msgid "lx164" msgstr "" #. Tag: entry -#: hardware.xml:344 +#: hardware.xml:341 #, no-c-format msgid "AlphaPC164-SX" msgstr "" #. Tag: entry -#: hardware.xml:345 +#: hardware.xml:342 #, no-c-format msgid "SX164" msgstr "" #. Tag: entry -#: hardware.xml:346 +#: hardware.xml:343 #, no-c-format msgid "sx164" msgstr "" #. Tag: entry -#: hardware.xml:350 +#: hardware.xml:347 #, no-c-format msgid "eb164" msgstr "" #. Tag: entry -#: hardware.xml:354 hardware.xml:363 hardware.xml:364 +#: hardware.xml:351 hardware.xml:360 hardware.xml:361 #, no-c-format msgid "EB64+" msgstr "" #. Tag: entry -#: hardware.xml:355 +#: hardware.xml:352 #, no-c-format msgid "AlphaPC64" msgstr "" #. Tag: entry -#: hardware.xml:356 hardware.xml:360 +#: hardware.xml:353 hardware.xml:357 #, no-c-format msgid "Cabriolet" msgstr "" #. Tag: entry -#: hardware.xml:357 hardware.xml:361 +#: hardware.xml:354 hardware.xml:358 #, no-c-format msgid "cabriolet" msgstr "" #. Tag: entry -#: hardware.xml:359 +#: hardware.xml:356 #, no-c-format msgid "AlphaPCI64" msgstr "" #. Tag: entry -#: hardware.xml:365 +#: hardware.xml:362 #, no-c-format msgid "eb64p" msgstr "" #. Tag: entry -#: hardware.xml:369 hardware.xml:370 hardware.xml:371 +#: hardware.xml:366 hardware.xml:367 hardware.xml:368 #, no-c-format msgid "EB66" msgstr "" #. Tag: entry -#: hardware.xml:372 +#: hardware.xml:369 #, no-c-format msgid "eb66" msgstr "" #. Tag: entry -#: hardware.xml:374 hardware.xml:375 +#: hardware.xml:371 hardware.xml:372 #, no-c-format msgid "EB66+" msgstr "" #. Tag: entry -#: hardware.xml:376 +#: hardware.xml:373 #, no-c-format msgid "eb66p" msgstr "" #. Tag: entry -#: hardware.xml:380 +#: hardware.xml:377 #, no-c-format msgid "JENSEN" msgstr "" #. Tag: entry -#: hardware.xml:381 +#: hardware.xml:378 #, no-c-format msgid "DEC 2000 Model 300(S)" msgstr "" #. Tag: entry -#: hardware.xml:382 hardware.xml:390 +#: hardware.xml:379 hardware.xml:387 #, no-c-format msgid "Jensen" msgstr "" #. Tag: entry -#: hardware.xml:383 hardware.xml:387 hardware.xml:391 hardware.xml:452 hardware.xml:456 hardware.xml:474 hardware.xml:478 hardware.xml:482 hardware.xml:486 hardware.xml:490 hardware.xml:494 hardware.xml:498 hardware.xml:512 hardware.xml:516 hardware.xml:520 hardware.xml:524 hardware.xml:528 hardware.xml:562 hardware.xml:566 hardware.xml:570 hardware.xml:574 hardware.xml:588 hardware.xml:592 hardware.xml:596 hardware.xml:600 hardware.xml:607 hardware.xml:611 hardware.xml:615 hardware.xml:619 hardware.xml:623 hardware.xml:627 hardware.xml:631 hardware.xml:635 hardware.xml:639 hardware.xml:643 hardware.xml:647 hardware.xml:651 hardware.xml:655 hardware.xml:662 hardware.xml:666 +#: hardware.xml:380 hardware.xml:384 hardware.xml:388 hardware.xml:449 hardware.xml:453 hardware.xml:471 hardware.xml:475 hardware.xml:479 hardware.xml:483 hardware.xml:487 hardware.xml:491 hardware.xml:495 hardware.xml:509 hardware.xml:513 hardware.xml:517 hardware.xml:521 hardware.xml:525 hardware.xml:559 hardware.xml:563 hardware.xml:567 hardware.xml:571 hardware.xml:585 hardware.xml:589 hardware.xml:593 hardware.xml:597 hardware.xml:604 hardware.xml:608 hardware.xml:612 hardware.xml:616 hardware.xml:620 hardware.xml:624 hardware.xml:628 hardware.xml:632 hardware.xml:636 hardware.xml:640 hardware.xml:644 hardware.xml:648 hardware.xml:652 hardware.xml:659 hardware.xml:663 #, no-c-format msgid "<entry>N/A</entry>" msgstr "" #. Tag: entry -#: hardware.xml:385 +#: hardware.xml:382 #, no-c-format msgid "DEC 2000 Model 500" msgstr "" #. Tag: entry -#: hardware.xml:386 +#: hardware.xml:383 #, no-c-format msgid "Culzen" msgstr "" #. Tag: entry -#: hardware.xml:389 +#: hardware.xml:386 #, no-c-format msgid "DECpc 150" msgstr "" #. Tag: entry -#: hardware.xml:395 +#: hardware.xml:392 #, no-c-format msgid "MIATA" msgstr "" #. Tag: entry -#: hardware.xml:396 +#: hardware.xml:393 #, no-c-format msgid "Personal WorkStation 433a" msgstr "" #. Tag: entry -#: hardware.xml:397 hardware.xml:401 hardware.xml:405 hardware.xml:409 hardware.xml:413 hardware.xml:417 hardware.xml:421 hardware.xml:425 +#: hardware.xml:394 hardware.xml:398 hardware.xml:402 hardware.xml:406 hardware.xml:410 hardware.xml:414 hardware.xml:418 hardware.xml:422 #, no-c-format msgid "Miata" msgstr "" #. Tag: entry -#: hardware.xml:398 hardware.xml:402 hardware.xml:406 hardware.xml:410 hardware.xml:414 hardware.xml:418 hardware.xml:422 hardware.xml:426 +#: hardware.xml:395 hardware.xml:399 hardware.xml:403 hardware.xml:407 hardware.xml:411 hardware.xml:415 hardware.xml:419 hardware.xml:423 #, no-c-format msgid "miata" msgstr "" #. Tag: entry -#: hardware.xml:400 +#: hardware.xml:397 #, no-c-format msgid "Personal WorkStation 433au" msgstr "" #. Tag: entry -#: hardware.xml:404 +#: hardware.xml:401 #, no-c-format msgid "Personal WorkStation 466au" msgstr "" #. Tag: entry -#: hardware.xml:408 +#: hardware.xml:405 #, no-c-format msgid "Personal WorkStation 500a" msgstr "" #. Tag: entry -#: hardware.xml:412 +#: hardware.xml:409 #, no-c-format msgid "Personal WorkStation 500au" msgstr "" #. Tag: entry -#: hardware.xml:416 +#: hardware.xml:413 #, no-c-format msgid "Personal WorkStation 550au" msgstr "" #. Tag: entry -#: hardware.xml:420 +#: hardware.xml:417 #, no-c-format msgid "Personal WorkStation 600a" msgstr "" #. Tag: entry -#: hardware.xml:424 +#: hardware.xml:421 #, no-c-format msgid "Personal WorkStation 600au" msgstr "" #. Tag: entry -#: hardware.xml:430 +#: hardware.xml:427 #, no-c-format msgid "MIKASA" msgstr "" #. Tag: entry -#: hardware.xml:431 +#: hardware.xml:428 #, no-c-format msgid "AlphaServer 1000 4/200" msgstr "" #. Tag: entry -#: hardware.xml:432 +#: hardware.xml:429 #, no-c-format msgid "Mikasa" msgstr "" #. Tag: entry -#: hardware.xml:433 hardware.xml:437 hardware.xml:441 hardware.xml:445 +#: hardware.xml:430 hardware.xml:434 hardware.xml:438 hardware.xml:442 #, no-c-format msgid "mikasa" msgstr "" #. Tag: entry -#: hardware.xml:435 +#: hardware.xml:432 #, no-c-format msgid "AlphaServer 1000 4/233..266" msgstr "" #. Tag: entry -#: hardware.xml:436 +#: hardware.xml:433 #, no-c-format msgid "Mikasa+" msgstr "" #. Tag: entry -#: hardware.xml:439 hardware.xml:443 +#: hardware.xml:436 hardware.xml:440 #, no-c-format msgid "AlphaServer 1000 5/300" msgstr "" #. Tag: entry -#: hardware.xml:440 +#: hardware.xml:437 #, no-c-format msgid "Mikasa-Pinnacle" msgstr "" #. Tag: entry -#: hardware.xml:444 +#: hardware.xml:441 #, no-c-format msgid "Mikasa-Primo" msgstr "" #. Tag: entry -#: hardware.xml:449 +#: hardware.xml:446 #, no-c-format msgid "NAUTILUS" msgstr "" #. Tag: entry -#: hardware.xml:450 +#: hardware.xml:447 #, no-c-format msgid "UP1000" msgstr "" #. Tag: entry -#: hardware.xml:451 +#: hardware.xml:448 #, no-c-format msgid "Nautilus" msgstr "" #. Tag: entry -#: hardware.xml:454 +#: hardware.xml:451 #, no-c-format msgid "UP1100" msgstr "" #. Tag: entry -#: hardware.xml:455 +#: hardware.xml:452 #, no-c-format msgid "Galaxy-Train/Nautilus Jr." msgstr "" #. Tag: entry -#: hardware.xml:460 +#: hardware.xml:457 #, no-c-format msgid "NONAME" msgstr "" #. Tag: entry -#: hardware.xml:461 +#: hardware.xml:458 #, no-c-format msgid "AXPpci33" msgstr "" #. Tag: entry -#: hardware.xml:462 +#: hardware.xml:459 #, no-c-format msgid "Noname" msgstr "" #. Tag: entry -#: hardware.xml:463 hardware.xml:467 +#: hardware.xml:460 hardware.xml:464 #, no-c-format msgid "noname" msgstr "" #. Tag: entry -#: hardware.xml:465 +#: hardware.xml:462 #, no-c-format msgid "<entry>UDB</entry>" msgstr "" #. Tag: entry -#: hardware.xml:466 +#: hardware.xml:463 #, no-c-format msgid "Multia" msgstr "" #. Tag: entry -#: hardware.xml:471 +#: hardware.xml:468 #, no-c-format msgid "NORITAKE" msgstr "" #. Tag: entry -#: hardware.xml:472 +#: hardware.xml:469 #, no-c-format msgid "AlphaServer 1000A 4/233...266" msgstr "" #. Tag: entry -#: hardware.xml:473 +#: hardware.xml:470 #, no-c-format msgid "Noritake" msgstr "" #. Tag: entry -#: hardware.xml:476 +#: hardware.xml:473 #, no-c-format msgid "AlphaServer 1000A 5/300" msgstr "" #. Tag: entry -#: hardware.xml:477 +#: hardware.xml:474 #, no-c-format msgid "Noritake-Pinnacle" msgstr "" #. Tag: entry -#: hardware.xml:480 +#: hardware.xml:477 #, no-c-format msgid "AlphaServer 1000A 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:481 +#: hardware.xml:478 #, no-c-format msgid "Noritake-Primo" msgstr "" #. Tag: entry -#: hardware.xml:484 +#: hardware.xml:481 #, no-c-format msgid "AlphaServer 800 5/333...500" msgstr "" #. Tag: entry -#: hardware.xml:485 hardware.xml:493 hardware.xml:497 +#: hardware.xml:482 hardware.xml:490 hardware.xml:494 #, no-c-format msgid "Corelle" msgstr "" #. Tag: entry -#: hardware.xml:488 +#: hardware.xml:485 #, no-c-format msgid "AlphaStation 600 A" msgstr "" #. Tag: entry -#: hardware.xml:489 +#: hardware.xml:486 #, no-c-format msgid "Alcor-Primo" msgstr "" #. Tag: entry -#: hardware.xml:492 +#: hardware.xml:489 #, no-c-format msgid "Digital Server 3300" msgstr "" #. Tag: entry -#: hardware.xml:496 +#: hardware.xml:493 #, no-c-format msgid "Digital Server 3300R" msgstr "" #. Tag: entry -#: hardware.xml:502 +#: hardware.xml:499 #, no-c-format msgid "PLATFORM 2000" msgstr "" #. Tag: entry -#: hardware.xml:503 hardware.xml:504 +#: hardware.xml:500 hardware.xml:501 #, no-c-format msgid "<entry>P2K</entry>" msgstr "" #. Tag: entry -#: hardware.xml:505 +#: hardware.xml:502 #, no-c-format msgid "<entry>p2k</entry>" msgstr "" #. Tag: entry -#: hardware.xml:509 +#: hardware.xml:506 #, no-c-format msgid "RAWHIDE" msgstr "" #. Tag: entry -#: hardware.xml:510 +#: hardware.xml:507 #, no-c-format msgid "AlphaServer 1200 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:511 hardware.xml:523 +#: hardware.xml:508 hardware.xml:520 #, no-c-format msgid "Tincup/DaVinci" msgstr "" #. Tag: entry -#: hardware.xml:514 +#: hardware.xml:511 #, no-c-format msgid "AlphaServer 4000 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:515 +#: hardware.xml:512 #, no-c-format msgid "Wrangler/Durango" msgstr "" #. Tag: entry -#: hardware.xml:518 +#: hardware.xml:515 #, no-c-format msgid "AlphaServer 4100 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:519 hardware.xml:527 +#: hardware.xml:516 hardware.xml:524 #, no-c-format msgid "Dodge" msgstr "" #. Tag: entry -#: hardware.xml:522 +#: hardware.xml:519 #, no-c-format msgid "Digital Server 5300" msgstr "" #. Tag: entry -#: hardware.xml:526 +#: hardware.xml:523 #, no-c-format msgid "Digital Server 7300" msgstr "" #. Tag: entry -#: hardware.xml:532 +#: hardware.xml:529 #, no-c-format msgid "RUFFIAN" msgstr "" #. Tag: entry -#: hardware.xml:533 +#: hardware.xml:530 #, no-c-format msgid "DeskStation AlphaPC164-UX" msgstr "" #. Tag: entry -#: hardware.xml:534 hardware.xml:538 hardware.xml:542 hardware.xml:546 hardware.xml:550 hardware.xml:554 +#: hardware.xml:531 hardware.xml:535 hardware.xml:539 hardware.xml:543 hardware.xml:547 hardware.xml:551 #, no-c-format msgid "Ruffian" msgstr "" #. Tag: entry -#: hardware.xml:535 hardware.xml:539 hardware.xml:543 hardware.xml:547 hardware.xml:551 hardware.xml:555 +#: hardware.xml:532 hardware.xml:536 hardware.xml:540 hardware.xml:544 hardware.xml:548 hardware.xml:552 #, no-c-format msgid "ruffian" msgstr "" #. Tag: entry -#: hardware.xml:537 +#: hardware.xml:534 #, no-c-format msgid "DeskStation RPL164-2" msgstr "" #. Tag: entry -#: hardware.xml:541 +#: hardware.xml:538 #, no-c-format msgid "DeskStation RPL164-4" msgstr "" #. Tag: entry -#: hardware.xml:545 +#: hardware.xml:542 #, no-c-format msgid "DeskStation RPX164-2" msgstr "" #. Tag: entry -#: hardware.xml:549 +#: hardware.xml:546 #, no-c-format msgid "DeskStation RPX164-4" msgstr "" #. Tag: entry -#: hardware.xml:553 +#: hardware.xml:550 #, no-c-format msgid "Samsung AlphaPC164-BX" msgstr "" #. Tag: entry -#: hardware.xml:559 +#: hardware.xml:556 #, no-c-format msgid "SABLE" msgstr "" #. Tag: entry -#: hardware.xml:560 +#: hardware.xml:557 #, no-c-format msgid "AlphaServer 2000 4/xxx" msgstr "" #. Tag: entry -#: hardware.xml:561 +#: hardware.xml:558 #, no-c-format msgid "Demi-Sable" msgstr "" #. Tag: entry -#: hardware.xml:564 +#: hardware.xml:561 #, no-c-format msgid "AlphaServer 2000 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:565 +#: hardware.xml:562 #, no-c-format msgid "Demi-Gamma-Sable" msgstr "" #. Tag: entry -#: hardware.xml:568 +#: hardware.xml:565 #, no-c-format msgid "AlphaServer 2100 4/xxx" msgstr "" #. Tag: entry -#: hardware.xml:569 +#: hardware.xml:566 #, no-c-format msgid "Sable" msgstr "" #. Tag: entry -#: hardware.xml:572 +#: hardware.xml:569 #, no-c-format msgid "AlphaServer 2100 5/xxx" msgstr "" #. Tag: entry -#: hardware.xml:573 +#: hardware.xml:570 #, no-c-format msgid "Gamma-Sable" msgstr "" #. Tag: entry -#: hardware.xml:578 +#: hardware.xml:575 #, no-c-format msgid "TAKARA" msgstr "" #. Tag: entry -#: hardware.xml:579 +#: hardware.xml:576 #, no-c-format msgid "21164 PICMG SBC" msgstr "" #. Tag: entry -#: hardware.xml:580 +#: hardware.xml:577 #, no-c-format msgid "Takara" msgstr "" #. Tag: entry -#: hardware.xml:581 +#: hardware.xml:578 #, no-c-format msgid "takara" msgstr "" #. Tag: entry -#: hardware.xml:585 +#: hardware.xml:582 #, no-c-format msgid "TITAN" msgstr "" #. Tag: entry -#: hardware.xml:586 +#: hardware.xml:583 #, no-c-format msgid "AlphaServer DS15" msgstr "" #. Tag: entry -#: hardware.xml:587 +#: hardware.xml:584 #, no-c-format msgid "HyperBrick2" msgstr "" #. Tag: entry -#: hardware.xml:590 +#: hardware.xml:587 #, no-c-format msgid "AlphaServer DS25" msgstr "" #. Tag: entry -#: hardware.xml:591 +#: hardware.xml:588 #, no-c-format msgid "Granite" msgstr "" #. Tag: entry -#: hardware.xml:594 +#: hardware.xml:591 #, no-c-format msgid "AlphaServer ES45" msgstr "" #. Tag: entry -#: hardware.xml:595 +#: hardware.xml:592 #, no-c-format msgid "Privateer" msgstr "" #. Tag: entry -#: hardware.xml:598 hardware.xml:637 hardware.xml:641 +#: hardware.xml:595 hardware.xml:634 hardware.xml:638 #, no-c-format msgid "UNKNOWN" msgstr "" #. Tag: entry -#: hardware.xml:599 +#: hardware.xml:596 #, no-c-format msgid "Yukon" msgstr "" #. Tag: entry -#: hardware.xml:604 +#: hardware.xml:601 #, no-c-format msgid "TSUNAMI" msgstr "" #. Tag: entry -#: hardware.xml:605 +#: hardware.xml:602 #, no-c-format msgid "AlphaServer DS10" msgstr "" #. Tag: entry -#: hardware.xml:606 hardware.xml:654 +#: hardware.xml:603 hardware.xml:651 #, no-c-format msgid "Webbrick" msgstr "" #. Tag: entry -#: hardware.xml:609 +#: hardware.xml:606 #, no-c-format msgid "AlphaServer DS10L" msgstr "" #. Tag: entry -#: hardware.xml:610 +#: hardware.xml:607 #, no-c-format msgid "Slate" msgstr "" #. Tag: entry -#: hardware.xml:613 +#: hardware.xml:610 #, no-c-format msgid "AlphaServer DS20" msgstr "" #. Tag: entry -#: hardware.xml:614 +#: hardware.xml:611 #, no-c-format msgid "Catamaran/Goldrush" msgstr "" #. Tag: entry -#: hardware.xml:617 +#: hardware.xml:614 #, no-c-format msgid "AlphaServer DS20E" msgstr "" #. Tag: entry -#: hardware.xml:618 +#: hardware.xml:615 #, no-c-format msgid "Goldrack" msgstr "" #. Tag: entry -#: hardware.xml:621 +#: hardware.xml:618 #, no-c-format msgid "AlphaServer DS20L" msgstr "" #. Tag: entry -#: hardware.xml:622 +#: hardware.xml:619 #, no-c-format msgid "Shark" msgstr "" #. Tag: entry -#: hardware.xml:625 +#: hardware.xml:622 #, no-c-format msgid "AlphaServer ES40" msgstr "" #. Tag: entry -#: hardware.xml:626 +#: hardware.xml:623 #, no-c-format msgid "Clipper" msgstr "" #. Tag: entry -#: hardware.xml:629 hardware.xml:630 +#: hardware.xml:626 hardware.xml:627 #, no-c-format msgid "DP264" msgstr "" #. Tag: entry -#: hardware.xml:633 +#: hardware.xml:630 #, no-c-format msgid "SMARTengine 21264 PCI/ISA SBC" msgstr "" #. Tag: entry -#: hardware.xml:634 +#: hardware.xml:631 #, no-c-format msgid "Eiger" msgstr "" #. Tag: entry -#: hardware.xml:638 +#: hardware.xml:635 #, no-c-format msgid "Warhol" msgstr "" #. Tag: entry -#: hardware.xml:642 +#: hardware.xml:639 #, no-c-format msgid "Windjammer" msgstr "" #. Tag: entry -#: hardware.xml:645 +#: hardware.xml:642 #, no-c-format msgid "UP2000" msgstr "" #. Tag: entry -#: hardware.xml:646 +#: hardware.xml:643 #, no-c-format msgid "Swordfish" msgstr "" #. Tag: entry -#: hardware.xml:649 +#: hardware.xml:646 #, no-c-format msgid "XP1000" msgstr "" #. Tag: entry -#: hardware.xml:650 +#: hardware.xml:647 #, no-c-format msgid "Monet/Brisbane" msgstr "" #. Tag: entry -#: hardware.xml:653 +#: hardware.xml:650 #, no-c-format msgid "XP900" msgstr "" #. Tag: entry -#: hardware.xml:659 +#: hardware.xml:656 #, no-c-format msgid "WILDFIRE" msgstr "" #. Tag: entry -#: hardware.xml:660 +#: hardware.xml:657 #, no-c-format msgid "AlphaServer GS160" msgstr "" #. Tag: entry -#: hardware.xml:661 hardware.xml:665 +#: hardware.xml:658 hardware.xml:662 #, no-c-format msgid "Wildfire" msgstr "" #. Tag: entry -#: hardware.xml:664 +#: hardware.xml:661 #, no-c-format msgid "AlphaServer GS320" msgstr "" #. Tag: entry -#: hardware.xml:670 hardware.xml:672 +#: hardware.xml:667 hardware.xml:669 #, no-c-format msgid "<entry>XL</entry>" msgstr "" #. Tag: entry -#: hardware.xml:671 +#: hardware.xml:668 #, no-c-format msgid "XL-233...266" msgstr "" #. Tag: entry -#: hardware.xml:673 +#: hardware.xml:670 #, no-c-format msgid "<entry>xl</entry>" msgstr "" #. Tag: para -#: hardware.xml:678 +#: hardware.xml:675 #, no-c-format msgid "It is believed that Debian &releasename; supports installing on all alpha sub-architectures with the exception of the ARC-only Ruffian and XL sub-architectures and the Titan subarchitecture, which requires a change to the kernel compile options." msgstr "" #. Tag: para -#: hardware.xml:694 hardware.xml:842 +#: hardware.xml:691 hardware.xml:839 #, 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:702 hardware.xml:850 hardware.xml:1010 +#: hardware.xml:699 hardware.xml:847 hardware.xml:1007 #, no-c-format msgid "<title>CPU</title>" msgstr "" #. Tag: para -#: hardware.xml:703 +#: hardware.xml:700 #, no-c-format msgid "Both AMD64 and Intel EM64T processors are supported." msgstr "" #. Tag: para -#: hardware.xml:731 +#: hardware.xml:728 #, no-c-format msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard Debian distribution only supports installation on a number of the most common platforms. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU." msgstr "" #. Tag: para -#: hardware.xml:740 +#: hardware.xml:737 #, no-c-format msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems." msgstr "" #. Tag: para -#: hardware.xml:748 +#: hardware.xml:745 #, no-c-format msgid "The supported platforms are:" msgstr "" #. Tag: term -#: hardware.xml:755 +#: hardware.xml:752 #, no-c-format msgid "Netwinder" msgstr "" #. Tag: para -#: hardware.xml:756 +#: hardware.xml:753 #, no-c-format msgid "This is actually the name for the group of machines based upon the StrongARM 110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff)." msgstr "" #. Tag: term -#: hardware.xml:769 +#: hardware.xml:766 #, no-c-format msgid "IOP32x" msgstr "" #. Tag: para -#: hardware.xml:770 +#: hardware.xml:767 #, no-c-format msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. Debian currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. Debian explicitly supports two such devices: the GLAN Tank from IO-Data and the Thecus N2100." msgstr "" #. Tag: term -#: hardware.xml:782 +#: hardware.xml:779 #, no-c-format msgid "IXP4xx" msgstr "" #. Tag: para -#: hardware.xml:783 +#: hardware.xml:780 #, no-c-format msgid "The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected." msgstr "" #. Tag: term -#: hardware.xml:796 +#: hardware.xml:793 #, no-c-format msgid "<term>RiscPC</term>" msgstr "" #. Tag: para -#: hardware.xml:797 +#: hardware.xml:794 #, no-c-format msgid "This machine is the oldest supported hardware but support for it in our new installer is incomplete. It has RISC OS in ROM, Linux can be booted from that OS using linloader. The RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA video, parallel port, single serial port, PS/2 keyboard and proprietary mouse port. The proprietary module expansion bus allows for up to eight expansion cards to be fitted depending on configuration, several of these modules have Linux drivers." msgstr "" #. Tag: para -#: hardware.xml:823 +#: hardware.xml:820 #, 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:851 +#: hardware.xml:848 #, 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 new processors like the Athlon XP and Intel P4 Xeon." msgstr "" #. Tag: para -#: hardware.xml:859 +#: hardware.xml:856 #, no-c-format msgid "If your system has a 64-bit AMD64, Intel EM64T or Intel Core 2 Duo processor, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture." msgstr "" #. Tag: para -#: hardware.xml:866 +#: hardware.xml:863 #, no-c-format msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", Debian Sarge has <emphasis>dropped support</emphasis> for actual 80386 processors (and their clones), which were supported by earlier releases<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: title -#: hardware.xml:903 +#: hardware.xml:900 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:904 +#: hardware.xml:901 #, 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, the Microchannel Architecture (MCA, used in IBM's PS/2 line), 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:928 +#: hardware.xml:925 #, no-c-format msgid "Complete information concerning supported M68000 based (<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the basics." msgstr "" #. Tag: para -#: hardware.xml:935 +#: hardware.xml:932 #, no-c-format msgid "The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory Management Unit) and a FPU (floating-point unit). This includes the 68020 with an external 68851 PMMU, the 68030, and better, and excludes the <quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink> for complete details." msgstr "" #. Tag: para -#: hardware.xml:943 +#: hardware.xml:940 #, no-c-format msgid "There are four major supported <emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two systems to which Linux was ported; in keeping, they are also the two most well-supported Debian ports. The Macintosh line is supported incompletely, both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> for project status and supported hardware. The BVM and Motorola single board VMEbus computers are the most recent addition to the list of machines supported by Debian. Ports to other &architecture; architectures, such as the Sun3 architecture and NeXT black box, are underway but not yet supported by Debian." msgstr "" #. Tag: para -#: hardware.xml:970 +#: hardware.xml:967 #, 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> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </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:1011 +#: hardware.xml:1008 #, 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. The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." msgstr "" #. Tag: para -#: hardware.xml:1021 +#: hardware.xml:1018 #, 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:1038 +#: hardware.xml:1035 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </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:1078 +#: hardware.xml:1075 #, no-c-format msgid "CPU/Machine types" msgstr "" #. Tag: para -#: hardware.xml:1080 +#: hardware.xml:1077 #, no-c-format msgid "Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by the Debian installation system on little endian MIPS. The Debian installation system works on the following machines:" msgstr "" #. Tag: entry -#: hardware.xml:1092 +#: hardware.xml:1089 #, no-c-format msgid "System Type" msgstr "" #. Tag: entry -#: hardware.xml:1092 +#: hardware.xml:1089 #, no-c-format msgid "<entry>CPU</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1092 +#: hardware.xml:1089 #, no-c-format msgid "Code-name" msgstr "" #. Tag: entry -#: hardware.xml:1093 +#: hardware.xml:1090 #, no-c-format msgid "Debian subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1099 +#: hardware.xml:1096 #, no-c-format msgid "DECstation 5000/1xx" msgstr "" #. Tag: entry -#: hardware.xml:1100 hardware.xml:1110 hardware.xml:1115 hardware.xml:1125 +#: hardware.xml:1097 hardware.xml:1107 hardware.xml:1112 hardware.xml:1122 #, no-c-format msgid "R3000" msgstr "" #. Tag: entry -#: hardware.xml:1101 hardware.xml:1106 +#: hardware.xml:1098 hardware.xml:1103 #, no-c-format msgid "3MIN" msgstr "" #. Tag: entry -#: hardware.xml:1104 +#: hardware.xml:1101 #, no-c-format msgid "DECstation 5000/150" msgstr "" #. Tag: entry -#: hardware.xml:1105 hardware.xml:1130 +#: hardware.xml:1102 hardware.xml:1127 #, no-c-format msgid "R4000" msgstr "" #. Tag: entry -#: hardware.xml:1109 +#: hardware.xml:1106 #, no-c-format msgid "DECstation 5000/200" msgstr "" #. Tag: entry -#: hardware.xml:1111 +#: hardware.xml:1108 #, no-c-format msgid "3MAX" msgstr "" #. Tag: entry -#: hardware.xml:1114 +#: hardware.xml:1111 #, no-c-format msgid "DECstation 5000/240" msgstr "" #. Tag: entry -#: hardware.xml:1116 hardware.xml:1121 +#: hardware.xml:1113 hardware.xml:1118 #, no-c-format msgid "3MAX+" msgstr "" #. Tag: entry -#: hardware.xml:1119 +#: hardware.xml:1116 #, no-c-format msgid "DECstation 5000/260" msgstr "" #. Tag: entry -#: hardware.xml:1120 +#: hardware.xml:1117 #, no-c-format msgid "R4400" msgstr "" #. Tag: entry -#: hardware.xml:1124 +#: hardware.xml:1121 #, no-c-format msgid "Personal DECstation 5000/xx" msgstr "" #. Tag: entry -#: hardware.xml:1126 hardware.xml:1131 +#: hardware.xml:1123 hardware.xml:1128 #, no-c-format msgid "Maxine" msgstr "" #. Tag: entry -#: hardware.xml:1129 +#: hardware.xml:1126 #, no-c-format msgid "Personal DECstation 5000/50" msgstr "" #. Tag: para -#: hardware.xml:1136 +#: hardware.xml:1133 #, no-c-format msgid "All Cobalt machines are supported. In the past, only machines with a serial console were supported (that is, all machines except for the Qube 2700, aka Qube1). However, installations are now also possible through SSH." msgstr "" #. Tag: para -#: hardware.xml:1143 +#: hardware.xml:1140 #, no-c-format msgid "The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." msgstr "" #. Tag: title -#: hardware.xml:1153 +#: hardware.xml:1150 #, no-c-format msgid "Supported console options" msgstr "" #. Tag: para -#: hardware.xml:1154 +#: hardware.xml:1151 #, no-c-format msgid "A serial console is available on all supported DECstations (9600 bps, 8N1). To use the serial console, you have to boot the installer image with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter (with <replaceable>x</replaceable> being the number of the serial port you have your terminal connected to — usually <literal>2</literal>, but <literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available with the PMAG-BA and the PMAGB-B graphics options." msgstr "" #. Tag: para -#: hardware.xml:1165 +#: hardware.xml:1162 #, no-c-format msgid "" "If you have a Linux system to use as serial terminal, an easy way is to run <command>cu</command><footnote> <para> In Woody this command was part of the <classname>uucp</classname> package, but in later releases it is available as a separate package. </para> </footnote> on it. Example: <informalexample><screen>\n" @@ -1962,1243 +1950,1279 @@ msgid "" msgstr "" #. Tag: para -#: hardware.xml:1183 +#: hardware.xml:1180 #, no-c-format msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps." msgstr "" #. Tag: para -#: hardware.xml:1197 +#: hardware.xml:1194 #, no-c-format msgid "There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga Power-UP System), and CHRP machines. Each subarchitecture has its own boot methods. In addition, there are four different kernel flavours, supporting different CPU variants." msgstr "" #. Tag: para -#: hardware.xml:1205 +#: hardware.xml:1202 #, no-c-format msgid "Ports to other <emphasis>&architecture;</emphasis> architectures, such as the Be-Box and MBX architecture, are underway but not yet supported by Debian. We may have a 64-bit port in the future." msgstr "" #. Tag: title -#: hardware.xml:1213 +#: hardware.xml:1210 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:1215 +#: hardware.xml:1212 #, no-c-format msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:1222 +#: hardware.xml:1219 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:1223 +#: hardware.xml:1220 #, 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:1233 +#: hardware.xml:1230 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:1234 +#: hardware.xml:1231 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:1238 +#: hardware.xml:1235 #, 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:1244 +#: hardware.xml:1241 #, 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:1249 +#: hardware.xml:1246 #, 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: term -#: hardware.xml:1258 +#: hardware.xml:1255 #, no-c-format msgid "<term>prep</term>" msgstr "" #. Tag: para -#: hardware.xml:1259 +#: hardware.xml:1256 #, no-c-format msgid "This kernel flavour supports the PReP subarchitecture." msgstr "" #. Tag: term -#: hardware.xml:1267 +#: hardware.xml:1264 #, no-c-format -msgid "<term>apus</term>" +msgid "apus" msgstr "" #. Tag: para -#: hardware.xml:1268 +#: hardware.xml:1265 #, no-c-format msgid "This kernel flavour supports the Amiga Power-UP System, though it is currently disabled." msgstr "" #. Tag: title -#: hardware.xml:1281 +#: hardware.xml:1278 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:1283 +#: hardware.xml:1280 #, 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:1290 +#: hardware.xml:1287 #, 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:1298 +#: hardware.xml:1295 #, 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:1306 +#: hardware.xml:1303 #, 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:1322 hardware.xml:1457 hardware.xml:1501 hardware.xml:1530 +#: hardware.xml:1319 hardware.xml:1454 hardware.xml:1498 hardware.xml:1527 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:1323 +#: hardware.xml:1320 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:1329 +#: hardware.xml:1326 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:1330 +#: hardware.xml:1327 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:1331 hardware.xml:1334 hardware.xml:1337 hardware.xml:1340 hardware.xml:1343 hardware.xml:1346 hardware.xml:1349 hardware.xml:1352 hardware.xml:1355 hardware.xml:1358 hardware.xml:1361 hardware.xml:1364 hardware.xml:1367 hardware.xml:1370 hardware.xml:1373 hardware.xml:1376 +#: hardware.xml:1328 hardware.xml:1331 hardware.xml:1334 hardware.xml:1337 hardware.xml:1340 hardware.xml:1343 hardware.xml:1346 hardware.xml:1349 hardware.xml:1352 hardware.xml:1355 hardware.xml:1358 hardware.xml:1361 hardware.xml:1364 hardware.xml:1367 hardware.xml:1370 hardware.xml:1373 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:1333 +#: hardware.xml:1330 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:1336 +#: hardware.xml:1333 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:1339 +#: hardware.xml:1336 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:1342 +#: hardware.xml:1339 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:1345 +#: hardware.xml:1342 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:1348 +#: hardware.xml:1345 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:1351 +#: hardware.xml:1348 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:1354 +#: hardware.xml:1351 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:1357 +#: hardware.xml:1354 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:1360 +#: hardware.xml:1357 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:1363 +#: hardware.xml:1360 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:1366 +#: hardware.xml:1363 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:1369 +#: hardware.xml:1366 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:1372 +#: hardware.xml:1369 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:1375 +#: hardware.xml:1372 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:1378 +#: hardware.xml:1375 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:1379 hardware.xml:1382 hardware.xml:1385 hardware.xml:1388 hardware.xml:1391 hardware.xml:1394 hardware.xml:1397 hardware.xml:1400 hardware.xml:1403 hardware.xml:1406 hardware.xml:1409 hardware.xml:1412 hardware.xml:1418 hardware.xml:1421 hardware.xml:1427 hardware.xml:1433 hardware.xml:1439 +#: hardware.xml:1376 hardware.xml:1379 hardware.xml:1382 hardware.xml:1385 hardware.xml:1388 hardware.xml:1391 hardware.xml:1394 hardware.xml:1397 hardware.xml:1400 hardware.xml:1403 hardware.xml:1406 hardware.xml:1409 hardware.xml:1415 hardware.xml:1418 hardware.xml:1424 hardware.xml:1430 hardware.xml:1436 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:1381 +#: hardware.xml:1378 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:1384 +#: hardware.xml:1381 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:1387 +#: hardware.xml:1384 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:1390 +#: hardware.xml:1387 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:1393 +#: hardware.xml:1390 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:1396 +#: hardware.xml:1393 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:1399 +#: hardware.xml:1396 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:1402 +#: hardware.xml:1399 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:1405 +#: hardware.xml:1402 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:1408 +#: hardware.xml:1405 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:1411 +#: hardware.xml:1408 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:1416 +#: hardware.xml:1413 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:1417 +#: hardware.xml:1414 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:1420 +#: hardware.xml:1417 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:1425 +#: hardware.xml:1422 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:1426 +#: hardware.xml:1423 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:1431 +#: hardware.xml:1428 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1432 +#: hardware.xml:1429 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:1437 hardware.xml:1463 +#: hardware.xml:1434 hardware.xml:1460 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:1438 +#: hardware.xml:1435 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:1447 +#: hardware.xml:1444 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1464 +#: hardware.xml:1461 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:1466 +#: hardware.xml:1463 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:1468 +#: hardware.xml:1465 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:1470 +#: hardware.xml:1467 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:1472 +#: hardware.xml:1469 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:1476 hardware.xml:1507 +#: hardware.xml:1473 hardware.xml:1504 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:1477 +#: hardware.xml:1474 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:1479 +#: hardware.xml:1476 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:1481 +#: hardware.xml:1478 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:1483 +#: hardware.xml:1480 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:1491 +#: hardware.xml:1488 #, no-c-format msgid "CHRP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1508 +#: hardware.xml:1505 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:1511 +#: hardware.xml:1508 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:1512 +#: hardware.xml:1509 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: title -#: hardware.xml:1520 +#: hardware.xml:1517 #, no-c-format msgid "APUS subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1536 +#: hardware.xml:1533 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:1537 +#: hardware.xml:1534 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:1545 +#: hardware.xml:1542 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:1547 +#: hardware.xml:1544 #, 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:1584 +#: hardware.xml:1581 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:1586 +#: hardware.xml:1583 #, 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:1595 +#: hardware.xml:1592 #, 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:1603 +#: hardware.xml:1600 #, 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:1619 +#: hardware.xml:1616 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "" #. Tag: para -#: hardware.xml:1620 +#: hardware.xml:1617 #, 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:1639 +#, no-c-format +msgid "CPU and Main Boards Support" +msgstr "" + #. Tag: para -#: hardware.xml:1643 +#: hardware.xml:1640 #, no-c-format -msgid "Currently the <emphasis>&architecture;</emphasis> port supports several types of Sparc systems. The most common identifiers for Sparc systems are sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not support very old sun4 hardware. However, the other systems are supported. Sun4d has been tested the least of these, so expect possible problems with regard to the kernel stability. Sun4c and Sun4m, the most common of the older Sparc hardware, includes such systems as SparcStation 1, 1+, IPC, IPX and the SparcStation LX, 5, 10, and 20, respectively. The UltraSPARC class systems fall under the sun4u identifier, and are supported using the sun4u set of install images. Some systems that fall under these supported identifiers are known to not be supported. Known unsupported systems are the AP1000 multicomputer and the Tadpole Sparcbook 1. See the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARCProcessors FAQ</ulink> for complete information." +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: title -#: hardware.xml:1663 +#. Tag: term +#: hardware.xml:1651 #, no-c-format -msgid "Memory Configuration" +msgid "sun4, sun4c, sun4d" msgstr "" #. Tag: para +#: hardware.xml:1653 +#, no-c-format +msgid "These subarchitectures include some very old 32-bit machines, which are no longer supported. For a complete list please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>." +msgstr "" + +#. Tag: term #: hardware.xml:1664 #, no-c-format -msgid "Some older Sun workstations, notably the Sun IPX and Sun IPC have memory banks located at fixed locations in physical memory. Thus if the banks are not filled gaps will exist in the physical memory space. The Linux installation requires a contiguous memory block into which to load the kernel and the initial RAMdisk. If this is not available a <quote>Data Access Exception</quote> will result." +msgid "sun4m" msgstr "" #. Tag: para -#: hardware.xml:1673 +#: hardware.xml:1666 #, no-c-format -msgid "Thus you must configure the memory so that the lowest memory block is contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks are mapped in at 16Mb boundaries. In effect this means that you must have a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. In this case 4Mb is <emphasis>not</emphasis> sufficient." +msgid "sun4m is the only 32-bit subarchitecture (sparc32) that is currently supported. The most popular machines belonging to this class are Sparcstation 4, 5, 10 and 20." msgstr "" #. Tag: para -#: hardware.xml:1681 +#: hardware.xml:1672 #, no-c-format -msgid "Example: In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS connectors]. You must therefore install the 16Mb SIMM in bank 0; it is then recommended to install the 4Mb SIMM in bank 2." +msgid "Note that symmetric multiprocessing (SMP) — the ability to run processes on multiple processors — is not supported on this hardware, due to stability problems with such configurations. The available uniprocessor (UP) sparc32 kernel will boot fine on multiprocessor machines, although it will activate and use only the first CPU." msgstr "" -#. Tag: title -#: hardware.xml:1692 +#. Tag: term +#: hardware.xml:1684 #, no-c-format -msgid "Graphics Configuration" +msgid "<term>sun4u</term>" msgstr "" #. Tag: para -#: hardware.xml:1693 +#: hardware.xml:1686 +#, 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:1699 #, no-c-format -msgid "Especially in the case of older Sun workstations, it is very common for there to be an onboard framebuffer which has been superseded (for example the bwtwo on a sun IPC), and an SBUS card containing a later probably accelerated buffer is then plugged in to an SBUS slot. Under Solaris/SunOS this causes no problems because both cards are initialized." +msgid "sun4v" msgstr "" #. Tag: para -#: hardware.xml:1702 +#: hardware.xml:1701 #, no-c-format -msgid "However with Linux this can cause a problem, in that the boot PROM monitor may display its output on this additional card; however the linux kernel boot messages may then be directed to the original on board framebuffer, leaving <emphasis>no</emphasis> error messages on the screen, with the machine apparently stuck loading the RAMdisk." +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:1710 +#: hardware.xml:1712 #, no-c-format -msgid "To avoid this problem, connect the monitor (if required) to the video card in the lowest numbered SBUS slot (on motherboard card counts as below external slots). Alternatively it is possible to use a serial console." +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:1722 +#: hardware.xml:1721 #, no-c-format -msgid "Graphics Card" +msgid "Graphics Card Support" msgstr "" #. Tag: para -#: hardware.xml:1723 +#: hardware.xml:1722 #, 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:1731 +#: hardware.xml:1730 #, 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:1740 +#: hardware.xml:1739 #, no-c-format msgid "The X.Org X11 window system is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: para -#: hardware.xml:1749 +#: hardware.xml:1748 #, no-c-format msgid "The X.Org X11 window system is supported on some DECstation models. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" +#. Tag: para +#: hardware.xml:1756 +#, 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:1766 +#, 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:1760 +#: hardware.xml:1783 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1761 +#: hardware.xml:1784 #, no-c-format msgid "Laptops are also supported. Laptops are often specialized or contain proprietary hardware. To see if your particular laptop works well with GNU/Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>" msgstr "" #. Tag: title -#: hardware.xml:1772 hardware.xml:1794 hardware.xml:1814 hardware.xml:1837 +#: hardware.xml:1795 hardware.xml:1817 hardware.xml:1837 hardware.xml:1860 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1773 +#: hardware.xml:1796 #, no-c-format -msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with SMP support. This should not prevent installation, since the SMP kernel should boot on non-SMP systems; the kernel will simply cause a bit more overhead." +msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with SMP support. This should not prevent installation, since the SMP kernel should boot on non-SMP systems; the kernel will simply cause a bit more overhead." msgstr "" #. Tag: para -#: hardware.xml:1781 +#: hardware.xml:1804 #, 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:1796 +#: hardware.xml:1819 #, no-c-format -msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was 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." +msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was 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:1805 +#: hardware.xml:1828 #, 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:1815 +#: hardware.xml:1838 #, no-c-format -msgid "Multi-processor support — also called <quote>symmetric multi-processing</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." +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:1824 +#: hardware.xml:1847 #, 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:1838 +#: hardware.xml:1861 #, no-c-format -msgid "Multi-processor support — also called <quote>symmetric multi-processing</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." +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:1848 +#: hardware.xml:1871 #, 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. You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." +msgid "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:1877 +#, 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:1869 +#: hardware.xml:1894 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:1871 +#: hardware.xml:1896 #, 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:1882 +#: hardware.xml:1907 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:1883 +#: hardware.xml:1908 #, 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:1889 +#: hardware.xml:1914 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:1896 +#: hardware.xml:1921 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:1898 +#: hardware.xml:1923 #, 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:1905 +#: hardware.xml:1930 #, 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:1917 +#: hardware.xml:1942 #, no-c-format msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the boot disks (such as Mitsumi and Matsushita drives). However, these models might require special boot parameters or other massaging to get them to work, and booting off these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux." msgstr "" #. Tag: para -#: hardware.xml:1927 +#: hardware.xml:1952 #, 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:1932 +#: hardware.xml:1957 #, no-c-format msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as the controller is supported by the SRM console. This rules out many add-on controller cards, but most integrated IDE and SCSI chips and controller cards that were provided by the manufacturer can be expected to work. To find out whether your device is supported from the SRM console, see the <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1941 +#: hardware.xml:1966 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-ROMs are also supported." msgstr "" #. Tag: para -#: hardware.xml:1946 +#: hardware.xml:1971 #, 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. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card." msgstr "" #. Tag: para -#: hardware.xml:1961 +#: hardware.xml:1986 #, no-c-format msgid "On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-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." msgstr "" #. Tag: para -#: hardware.xml:1970 +#: hardware.xml:1995 #, no-c-format msgid "CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal DECstation 5000/50)." msgstr "" #. Tag: para -#: hardware.xml:1979 +#: hardware.xml:2004 #, no-c-format msgid "To boot from CD, issue the command <userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware prompt, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot (3 on most DECstations) and <replaceable>id</replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" #. Tag: userinput -#: hardware.xml:1991 +#: hardware.xml:2016 #, no-c-format msgid "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=value1 param2=value2 ..." msgstr "" #. Tag: title -#: hardware.xml:1998 +#: hardware.xml:2023 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:2000 +#: hardware.xml:2025 #, 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:2006 +#: hardware.xml:2031 #, no-c-format msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines." msgstr "" #. Tag: para -#: hardware.xml:2011 +#: hardware.xml:2036 #, 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:2019 +#: hardware.xml:2044 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:2021 +#: hardware.xml:2046 #, 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:2033 +#: hardware.xml:2058 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:2035 +#: hardware.xml:2060 #, no-c-format msgid "You can also <emphasis>boot</emphasis> your system over the network. <phrase arch=\"mips\">This is the preferred installation technique for Mips.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:2041 +#: hardware.xml:2066 #, 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: para -#: hardware.xml:2046 +#: hardware.xml:2071 #, no-c-format msgid "After the operating system kernel is installed, you can install the rest of your system via any sort of network connection (including PPP after installation of the base system), via FTP or HTTP." msgstr "" #. Tag: title -#: hardware.xml:2055 +#: hardware.xml:2080 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:2057 +#: hardware.xml:2082 #, 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 the manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." msgstr "" #. Tag: title -#: hardware.xml:2069 +#: hardware.xml:2094 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:2071 +#: hardware.xml:2096 #, 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:2081 +#: hardware.xml:2106 #, no-c-format msgid "Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." msgstr "" #. Tag: para -#: hardware.xml:2088 +#: hardware.xml:2113 #, no-c-format msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or ATA — are supported. Very old 8–bit hard disk controllers used in the IBM XT computer are supported only as a module. SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." msgstr "" #. Tag: para -#: hardware.xml:2098 +#: hardware.xml:2123 #, no-c-format msgid "Pretty much all storage systems supported by the Linux kernel are supported by the Debian installation system. Note that the current Linux kernel does not support floppies on the Macintosh at all, and the Debian installation system doesn't support floppies for Amigas. Also supported on the Atari is the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) file system. Amigas support the FAT file system, and HFS as a module." msgstr "" #. Tag: para -#: hardware.xml:2108 +#: hardware.xml:2133 #, 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:2141 +#: hardware.xml:2166 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This includes both SCSI and IDE disks. Note, however, that on many systems, the SRM console is unable to boot from IDE drives, and the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;\"></ulink> for more information on booting the Jensen)" msgstr "" #. Tag: para -#: hardware.xml:2150 +#: hardware.xml:2175 #, 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:2156 +#: hardware.xml:2181 #, 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:2162 +#: hardware.xml:2187 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:2167 +#: hardware.xml:2192 #, 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:2184 +#: hardware.xml:2209 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:2185 +#: hardware.xml:2210 #, 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:2191 +#: hardware.xml:2216 #, no-c-format msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)." msgstr "" #. Tag: para -#: hardware.xml:2197 +#: hardware.xml:2222 #, 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:2203 +#: hardware.xml:2228 #, 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:2209 +#: hardware.xml:2234 #, no-c-format msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots." msgstr "" #. Tag: para -#: hardware.xml:2215 +#: hardware.xml:2240 #, no-c-format msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." msgstr "" #. Tag: title -#: hardware.xml:2225 +#: hardware.xml:2250 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" #. Tag: para -#: hardware.xml:2227 +#: hardware.xml:2252 #, 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:2235 +#: hardware.xml:2260 #, no-c-format msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all." msgstr "" #. Tag: para -#: hardware.xml:2240 +#: hardware.xml:2265 #, 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:2248 +#: hardware.xml:2273 #, 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:2259 +#: hardware.xml:2284 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:2260 +#: hardware.xml:2285 #, 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:2267 +#: hardware.xml:2292 #, no-c-format msgid "Another example is the proprietary hardware in the older Macintosh line. In fact, no specifications or documentation have ever been released for any Macintosh hardware, most notably the ADB controller (used by the mouse and keyboard), the floppy controller, and all acceleration and CLUT manipulation of the video hardware (though we do now support CLUT manipulation on nearly all internal video chips). In a nutshell, this explains why the Macintosh Linux port lags behind other Linux ports." msgstr "" #. Tag: para -#: hardware.xml:2278 +#: hardware.xml:2303 #, 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:2290 +#: hardware.xml:2315 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:2291 +#: hardware.xml:2316 #, 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:2304 +#: hardware.xml:2329 #, 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 its being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" #. Tag: para -#: hardware.xml:2325 +#: hardware.xml:2350 #, 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:2342 +#: hardware.xml:2367 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:2344 +#: hardware.xml:2369 #, no-c-format msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. For a minimal console-based system (all standard packages), 250MB is required. If you want to install a reasonable amount of software, including the X Window System, and some development programs and libraries, you'll need at least 400MB. For a more or less complete desktop system, you'll need a few gigabytes." msgstr "" #. Tag: para -#: hardware.xml:2353 +#: hardware.xml:2378 #, no-c-format msgid "On the Amiga the size of FastRAM is relevant towards the total memory requirements. Also, using Zorro cards with 16-bit RAM is not supported; you'll need 32-bit RAM. The <command>amiboot</command> program can be used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically." msgstr "" #. Tag: para -#: hardware.xml:2362 +#: hardware.xml:2387 #, no-c-format msgid "On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many users have reported problems running the kernel itself in Fast RAM, so the Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM." msgstr "" #. Tag: para -#: hardware.xml:2370 +#: hardware.xml:2395 #, no-c-format msgid "On the Macintosh, care should be taken on machines with RAM-based video (RBV). The RAM segment at physical address 0 is used as screen memory, making the default load position for the kernel unavailable. The alternate RAM segment used for kernel and RAMdisk must be at least 4 MB." msgstr "" #. Tag: emphasis -#: hardware.xml:2380 +#: hardware.xml:2405 #, no-c-format msgid "FIXME: is this still true?" msgstr "" #. Tag: title -#: hardware.xml:2391 +#: hardware.xml:2416 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:2393 +#: hardware.xml:2418 #, no-c-format msgid "Most PCI and many older ISA network cards are supported. Some network interface cards are not supported by most Debian installation disks, such as AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider & Koch G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) network cards are not supported by the standard installation system, but see <ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) instructions. FDDI networks are also not supported by the installation disks, both cards and protocols." msgstr "" #. Tag: para -#: hardware.xml:2412 +#: hardware.xml:2437 #, no-c-format msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;." msgstr "" #. Tag: para -#: hardware.xml:2420 +#: hardware.xml:2445 #, no-c-format msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details." msgstr "" #. Tag: para -#: hardware.xml:2429 +#: hardware.xml:2454 #, no-c-format msgid "The following network interface cards (NICs) are supported from the bootable kernel directly:" msgstr "" #. Tag: para -#: hardware.xml:2435 +#: hardware.xml:2460 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:2441 +#: hardware.xml:2466 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:2449 +#: hardware.xml:2474 #, no-c-format msgid "The following network interface cards are supported as modules. They can be enabled once the drivers are installed during the setup. However, due to the magic of OpenPROM, you still should be able to boot from these devices:" msgstr "" #. Tag: para -#: hardware.xml:2457 +#: hardware.xml:2482 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:2463 +#: hardware.xml:2488 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:2468 +#: hardware.xml:2493 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:2475 hardware.xml:2481 hardware.xml:2487 hardware.xml:2493 hardware.xml:2499 +#: hardware.xml:2500 hardware.xml:2506 hardware.xml:2512 hardware.xml:2518 hardware.xml:2524 #, no-c-format msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module." msgstr "" #. Tag: para -#: hardware.xml:2505 +#: hardware.xml:2530 #, no-c-format msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work." msgstr "" #. Tag: para -#: hardware.xml:2511 +#: hardware.xml:2536 #, no-c-format msgid "Any network interface card (NIC) supported by the Linux kernel is also be supported by the boot disks. All network drivers are compiled as modules so you need to load one first during the initial network setup. The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:2519 +#: hardware.xml:2544 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:2524 +#: hardware.xml:2549 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:2529 +#: hardware.xml:2554 #, no-c-format msgid "Inter-User Communication Vehicle (IUCV) — available for VM guests only" msgstr "" #. Tag: para -#: hardware.xml:2534 +#: hardware.xml:2559 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:2543 +#: hardware.xml:2568 #, no-c-format msgid "The following network interface cards are supported directly by the boot disks on Netwinder and CATS machines:" msgstr "" #. Tag: para -#: hardware.xml:2549 +#: hardware.xml:2574 #, no-c-format msgid "PCI-based NE2000" msgstr "" #. Tag: para -#: hardware.xml:2555 +#: hardware.xml:2580 #, no-c-format msgid "DECchip Tulip" msgstr "" #. Tag: para -#: hardware.xml:2562 +#: hardware.xml:2587 #, no-c-format msgid "The following network interface cards are supported directly by the boot disks on RiscPCs:" msgstr "" #. Tag: para -#: hardware.xml:2568 +#: hardware.xml:2593 #, no-c-format msgid "Ether1" msgstr "" #. Tag: para -#: hardware.xml:2573 +#: hardware.xml:2598 #, no-c-format msgid "Ether3" msgstr "" #. Tag: para -#: hardware.xml:2578 +#: hardware.xml:2603 #, no-c-format msgid "EtherH" msgstr "" #. Tag: para -#: hardware.xml:2585 +#: hardware.xml:2610 #, no-c-format msgid "If your card is mentioned in the lists above, the complete installation can be carried out from the network with no need for CD-ROMs or floppy disks." msgstr "" #. Tag: para -#: hardware.xml:2591 +#: hardware.xml:2616 #, no-c-format msgid "Any other network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module; this means that you will have to install the operating system kernel and modules using some other media." msgstr "" diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot index 4df0c6147..e8ddbfe52 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: 2006-11-29 17:16+0000\n" +"POT-Creation-Date: 2006-12-26 01:54+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:621 +#: preseed.xml:23 preseed.xml:632 #, no-c-format msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;." msgstr "" @@ -75,7 +75,7 @@ msgid "initrd" msgstr "" #. Tag: entry -#: preseed.xml:63 preseed.xml:478 +#: preseed.xml:63 preseed.xml:489 #, no-c-format msgid "file" msgstr "" @@ -264,47 +264,47 @@ msgstr "" #. Tag: para #: preseed.xml:294 #, no-c-format -msgid "To set a value to be used inside &d-i;, just pass <userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput> for any of the preseed variables listed in the examples in this appendix. If a value is to be used to configure packages for the target system, you will need to prepend the <firstterm>owner</firstterm> of the variable as in <userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>. If you don't specify the owner, the value for the variable will not be copied to the debconf database in the target system and thus remain unused during the configuration of the relevant package." +msgid "To set a value to be used inside &d-i;, just pass <userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput> for any of the preseed variables listed in the examples in this appendix. If a value is to be used to configure packages for the target system, you will need to prepend the <firstterm>owner</firstterm><footnote> <para> The owner of a debconf variable (or template) is normally the name of the package that contains the corresponding debconf template. For variables used in the installer itself the owner is <quote>d-i</quote>. Templates and variables can have more than one owner which helps to determine whether they can be removed from the debconf database if the package is purged. </para> </footnote> of the variable as in <userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>. If you don't specify the owner, the value for the variable will not be copied to the debconf database in the target system and thus remain unused during the configuration of the relevant package." msgstr "" #. Tag: para -#: preseed.xml:306 +#: preseed.xml:317 #, no-c-format msgid "Note that some variables that are frequently set at the boot prompt have a shorter alias. If an alias is available, it is used in the examples in this appendix instead of the full variable. In particular, the <literal>preseed/url</literal> variable has been aliased as <literal>url</literal> and has some extra magic to allow shortened urls to be used. Another example is the <literal>tasks</literal> alias, which translates to <literal>tasksel:tasksel/first</literal>." msgstr "" #. Tag: para -#: preseed.xml:316 +#: preseed.xml:327 #, no-c-format msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after the last <quote>--</quote> may be copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader). The installer will automatically filter out any options (like preconfiguration options) that it recognizes." msgstr "" #. Tag: para -#: preseed.xml:325 +#: preseed.xml:336 #, no-c-format msgid "Current linux kernels (2.6.9 and later) accept a maximum of 32 command line options and 32 environment options, including any options added by default for the installer. If these numbers are exceeded, the kernel will panic (crash). (For earlier kernels, these numbers were lower.)" msgstr "" #. Tag: para -#: preseed.xml:333 +#: preseed.xml:344 #, no-c-format msgid "For most installations some of the default options in your bootloader configuration file, like <literal>vga=normal</literal>, may be safely removed which may allow you to add more options for preseeding." msgstr "" #. Tag: para -#: preseed.xml:340 +#: preseed.xml:351 #, no-c-format msgid "It may not always be possible to specify values with spaces for boot parameters, even if you delimit them with quotes." msgstr "" #. Tag: title -#: preseed.xml:349 +#: preseed.xml:360 #, no-c-format msgid "Auto mode" msgstr "" #. Tag: para -#: preseed.xml:350 +#: preseed.xml:361 #, no-c-format msgid "" "There are several features of Debian Installer that combine to allow fairly simple command lines at the boot prompt to result in arbitrarily complex customized automatic installs. To illustrate this, here are some examples that can be used at the boot prompt: <informalexample><screen>\n" @@ -313,217 +313,217 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:367 +#: preseed.xml:378 #, no-c-format -msgid "The path segment of that comes from <literal>auto-install/defaultroot</literal>, which includes the directory <literal>etch</literal> by default to allow future versions to specify their own codename to let people migrate forwards in a controlled manner. The <literal>/./</literal> bit is used to indicate a root relative to which subsequent paths can be anchored (for use in preseed/include and preseed/run). This allows files to be specified either as full URLs, paths starting with / that are thus anchored, or even paths relative to the location where the last preseed file was found. This can be used to construct more portable scripts where an entire hierarchy of scripts can be moved to a new location without breaking it, for example copying the files onto a USB stick when they started out on a web server. In this example, if the preseed file sets <literal>preseed/run</literal> to <literal>/scripts/late_command.sh</literal> then the file will be fetched from <literal>http://autoserver.example.com/d-i/etch/./scripts/late_command.sh</literal>." +msgid "The last part of that url (<literal>d-i/etch/./preseed.cfg</literal>) is taken from <literal>auto-install/defaultroot</literal>. By default this includes the directory <literal>etch</literal> to allow future versions to specify their own codename and let people migrate forwards in a controlled manner. The <literal>/./</literal> bit is used to indicate a root, relative to which subsequent paths can be anchored (for use in preseed/include and preseed/run). This allows files to be specified either as full URLs, paths starting with / that are thus anchored, or even paths relative to the location where the last preseed file was found. This can be used to construct more portable scripts where an entire hierarchy of scripts can be moved to a new location without breaking it, for example copying the files onto a USB stick when they started out on a web server. In this example, if the preseed file sets <literal>preseed/run</literal> to <literal>/scripts/late_command.sh</literal> then the file will be fetched from <literal>http://autoserver.example.com/d-i/etch/./scripts/late_command.sh</literal>." msgstr "" #. Tag: para -#: preseed.xml:387 +#: preseed.xml:398 #, no-c-format msgid "" - "If there is no local DHCP or DNS infrastructure, or if you do not want to use the default path to the preseed.cfg, you can still use an explicit url, and if you don't use the <literal>/./</literal> element it will be anchored to the start of the path (i.e. the third / in the URL). Here is an example that requires minimal support from the local network infrastructure: <informalexample><screen>\n" + "If there is no local DHCP or DNS infrastructure, or if you do not want to use the default path to <filename>preseed.cfg</filename>, you can still use an explicit url, and if you don't use the <literal>/./</literal> element it will be anchored to the start of the path (i.e. the third <literal>/</literal> in the URL). Here is an example that requires minimal support from the local network infrastructure: <informalexample><screen>\n" "auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</replaceable>\n" "</screen></informalexample> The way this works is that:" msgstr "" #. Tag: para -#: preseed.xml:400 +#: preseed.xml:411 #, no-c-format msgid "if the URL is missing a protocol, http is assumed," msgstr "" #. Tag: para -#: preseed.xml:403 +#: preseed.xml:414 #, no-c-format msgid "if the hostname section contains no periods, it has the domain derived from DHCP appended to it, and" msgstr "" #. Tag: para -#: preseed.xml:407 +#: preseed.xml:418 #, no-c-format msgid "if there's no <literal>/</literal>'s after the hostname, then the default path is added." msgstr "" #. Tag: para -#: preseed.xml:413 +#: preseed.xml:424 #, no-c-format msgid "" - "In addition to specifying the url, you can also specify settings that do not directly affect the behavior of &d-i; itself, but can be passed through to any scripts that might be specified <literal>preseed/run</literal> settings in the loaded preseed file. At present, the only example of this is <literal>auto-install/classes</literal>, which has an alias <literal>classes</literal>. This can be used thus: <informalexample><screen>\n" + "In addition to specifying the url, you can also specify settings that do not directly affect the behavior of &d-i; itself, but can be passed through to scripts specified using <literal>preseed/run</literal> in the loaded preseed file. At present, the only example of this is <literal>auto-install/classes</literal>, which has an alias <literal>classes</literal>. This can be used thus: <informalexample><screen>\n" "auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;class_B</replaceable>\n" "</screen></informalexample> The classes could for example denote the type of system to be installed, or the localization to be used." msgstr "" #. Tag: para -#: preseed.xml:427 +#: preseed.xml:438 #, no-c-format msgid "It is of course possible to extend this concept, and if you do, it is reasonable to use the auto-install namespace for this. So one might have something like <literal>auto-install/style</literal> which is then used in your scripts. If you feel the need to do this, please mention it on the <email>debian-boot@lists.debian.org</email> mailing list so that we can avoid namespace conflicts, and perhaps add an alias for the parameter for you." msgstr "" #. Tag: para -#: preseed.xml:437 +#: preseed.xml:448 #, no-c-format msgid "The <literal>auto</literal> boot label is not yet defined on all architectures. The same effect may be achieved by simply adding the two parameters <literal>auto=true priority=critical</literal> to the kernel command line. The <literal>auto</literal> parameter is an alias for <literal>auto-install/enabled</literal> and controls the delay of the locale and keyboard questions until after there has been a chance to preseed them, while <literal>priority</literal> is an alias for <literal>preseed/priority</literal> and setting it to <literal>critical</literal> stops any questions with a lower priority from being asked." msgstr "" #. Tag: para -#: preseed.xml:450 +#: preseed.xml:461 #, no-c-format msgid "Additional options that may be of interest while attempting to automate an install while using DHCP are: <literal>interface=auto netcfg/dhcp_timeout=60</literal> which makes the machine choose the first viable NIC and be more patient about getting a reply to its DHCP query." msgstr "" #. Tag: title -#: preseed.xml:462 +#: preseed.xml:473 #, no-c-format msgid "Aliases useful with preseeding" msgstr "" #. Tag: para -#: preseed.xml:463 +#: preseed.xml:474 #, no-c-format msgid "The following aliases can be useful when using (auto mode) preseeding." msgstr "" #. Tag: entry -#: preseed.xml:473 +#: preseed.xml:484 #, no-c-format msgid "auto" msgstr "" #. Tag: entry -#: preseed.xml:473 +#: preseed.xml:484 #, no-c-format msgid "auto-install/enabled" msgstr "" #. Tag: entry -#: preseed.xml:474 +#: preseed.xml:485 #, no-c-format msgid "classes" msgstr "" #. Tag: entry -#: preseed.xml:474 +#: preseed.xml:485 #, no-c-format msgid "auto-install/classes" msgstr "" #. Tag: entry -#: preseed.xml:475 +#: preseed.xml:486 #, no-c-format msgid "<entry>fb</entry>" msgstr "" #. Tag: entry -#: preseed.xml:475 +#: preseed.xml:486 #, no-c-format msgid "debian-installer/framebuffer" msgstr "" #. Tag: entry -#: preseed.xml:476 +#: preseed.xml:487 #, no-c-format msgid "locale" msgstr "" #. Tag: entry -#: preseed.xml:476 +#: preseed.xml:487 #, no-c-format msgid "debian-installer/locale" msgstr "" #. Tag: entry -#: preseed.xml:477 +#: preseed.xml:488 #, no-c-format msgid "priority" msgstr "" #. Tag: entry -#: preseed.xml:477 +#: preseed.xml:488 #, no-c-format msgid "debconf/priority" msgstr "" #. Tag: entry -#: preseed.xml:478 +#: preseed.xml:489 #, no-c-format msgid "preseed/file" msgstr "" #. Tag: entry -#: preseed.xml:479 +#: preseed.xml:490 #, no-c-format msgid "<entry>url</entry>" msgstr "" #. Tag: entry -#: preseed.xml:479 +#: preseed.xml:490 #, no-c-format msgid "preseed/url" msgstr "" #. Tag: entry -#: preseed.xml:480 +#: preseed.xml:491 #, no-c-format msgid "hostname " msgstr "" #. Tag: entry -#: preseed.xml:480 +#: preseed.xml:491 #, no-c-format msgid "netcfg/get_hostname" msgstr "" #. Tag: entry -#: preseed.xml:481 +#: preseed.xml:492 #, no-c-format msgid "domain" msgstr "" #. Tag: entry -#: preseed.xml:481 +#: preseed.xml:492 #, no-c-format msgid "netcfg/get_domain" msgstr "" #. Tag: entry -#: preseed.xml:482 +#: preseed.xml:493 #, no-c-format msgid "interface" msgstr "" #. Tag: entry -#: preseed.xml:482 +#: preseed.xml:493 #, no-c-format msgid "netcfg/choose_interface" msgstr "" #. Tag: entry -#: preseed.xml:483 +#: preseed.xml:494 #, no-c-format msgid "suite" msgstr "" #. Tag: entry -#: preseed.xml:483 +#: preseed.xml:494 #, no-c-format msgid "mirror/suite" msgstr "" #. Tag: title -#: preseed.xml:490 +#: preseed.xml:501 #, no-c-format msgid "Using a DHCP server to specify preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:491 +#: preseed.xml:502 #, 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:502 +#: preseed.xml:513 #, no-c-format msgid "" "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n" @@ -532,79 +532,79 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:504 +#: preseed.xml:515 #, 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:511 +#: preseed.xml:522 #, 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:525 +#: preseed.xml:536 #, no-c-format msgid "Creating a preconfiguration file" msgstr "" #. Tag: para -#: preseed.xml:526 +#: preseed.xml:537 #, 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:532 +#: preseed.xml:543 #, no-c-format msgid "<owner> <question name> <question type> <value>" msgstr "" #. Tag: para -#: preseed.xml:534 +#: preseed.xml:545 #, no-c-format msgid "There are a few rules to keep in mind when writing a preconfiguration file." msgstr "" #. Tag: para -#: preseed.xml:541 +#: preseed.xml:552 #, 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:545 +#: preseed.xml:556 #, 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." msgstr "" #. Tag: para -#: preseed.xml:551 +#: preseed.xml:562 #, 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:557 +#: preseed.xml:568 #, 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:563 +#: preseed.xml:574 #, 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:568 +#: preseed.xml:579 #, 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:575 +#: preseed.xml:586 #, no-c-format msgid "" "$ debconf-get-selections --installer > <replaceable>file</replaceable>\n" @@ -612,67 +612,67 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:577 +#: preseed.xml:588 #, 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:585 +#: preseed.xml:596 #, 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:593 +#: preseed.xml:604 #, 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:601 +#: preseed.xml:612 #, 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:609 +#: preseed.xml:620 #, 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:620 +#: preseed.xml:631 #, no-c-format msgid "Contents of the preconfiguration file" msgstr "" #. Tag: para -#: preseed.xml:626 +#: preseed.xml:637 #, 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:637 +#: preseed.xml:648 #, no-c-format msgid "Localization" msgstr "" #. Tag: para -#: preseed.xml:638 +#: preseed.xml:649 #, 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:644 +#: preseed.xml:655 #, no-c-format msgid "The locale can be used to specify both language and country. To specify the locale as a boot parameter, use <userinput>locale=<replaceable>en_US</replaceable></userinput>." msgstr "" #. Tag: screen -#: preseed.xml:650 +#: preseed.xml:661 #, no-c-format msgid "" "# Locale sets language and country.\n" @@ -680,13 +680,13 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:652 +#: preseed.xml:663 #, 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 valid for the selected keyboard architecture." msgstr "" #. Tag: screen -#: preseed.xml:659 +#: preseed.xml:670 #, no-c-format msgid "" "# Keyboard selection.\n" @@ -697,43 +697,43 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:661 +#: preseed.xml:672 #, 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:670 +#: preseed.xml:681 #, 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:680 +#: preseed.xml:691 #, no-c-format msgid "Network configuration" msgstr "" #. Tag: para -#: preseed.xml:681 +#: preseed.xml:692 #, 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:689 +#: preseed.xml:700 #, 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:695 +#: preseed.xml:706 #, 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 lines:" msgstr "" #. Tag: screen -#: preseed.xml:705 +#: preseed.xml:716 #, no-c-format msgid "" "killall.sh dhclient\n" @@ -741,7 +741,7 @@ msgid "" msgstr "" #. Tag: screen -#: preseed.xml:709 +#: preseed.xml:720 #, no-c-format msgid "" "# netcfg will choose an interface that has link if possible. This makes it\n" @@ -785,31 +785,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:714 +#: preseed.xml:725 #, no-c-format msgid "Mirror settings" msgstr "" #. Tag: para -#: preseed.xml:715 +#: preseed.xml:726 #, no-c-format msgid "Depending on the installation method you use, a mirror may be used both to download additional components of the installer, the base system and to set up the <filename>/etc/apt/sources.list</filename> for the installed system." msgstr "" #. Tag: para -#: preseed.xml:722 +#: preseed.xml:733 #, no-c-format msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system." msgstr "" #. Tag: para -#: preseed.xml:727 +#: preseed.xml:738 #, 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. By default the value for <classname>mirror/udeb/suite</classname> is the same as <classname>mirror/suite</classname>." msgstr "" #. Tag: screen -#: preseed.xml:739 +#: preseed.xml:750 #, no-c-format msgid "" "d-i mirror/country string enter information manually\n" @@ -824,25 +824,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:744 +#: preseed.xml:755 #, no-c-format msgid "Partitioning" msgstr "" #. Tag: para -#: preseed.xml:745 +#: preseed.xml:756 #, 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 either partition 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:756 +#: preseed.xml:767 #, 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:764 +#: preseed.xml:775 #, no-c-format msgid "" "# If the system has free space you can choose to only partition that space.\n" @@ -908,31 +908,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:769 +#: preseed.xml:780 #, no-c-format msgid "Partitioning using RAID" msgstr "" #. Tag: para -#: preseed.xml:770 +#: preseed.xml:781 #, no-c-format msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1 and 5, 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:780 +#: preseed.xml:791 #, no-c-format msgid "This type of automated partitioning is easy to get wrong. It is also a very new component that may still have some bugs or missing error handling. 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: para -#: preseed.xml:788 +#: preseed.xml:799 #, no-c-format msgid "Note that only RAID 0 and RAID 1 have been tested by the developers of the component. RAID 5 is untested. Advanced RAID setup with degraded arrays or spare devices has only been tested lightly." msgstr "" #. Tag: screen -#: preseed.xml:796 +#: preseed.xml:807 #, no-c-format msgid "" "# NOTE: this option is of beta release quality and should be used carefully\n" @@ -983,13 +983,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:801 +#: preseed.xml:812 #, no-c-format msgid "Clock and time zone setup" msgstr "" #. Tag: screen -#: preseed.xml:803 +#: preseed.xml:814 #, no-c-format msgid "" "# Controls whether or not the hardware clock is set to UTC.\n" @@ -1001,19 +1001,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:808 +#: preseed.xml:819 #, no-c-format msgid "Apt setup" msgstr "" #. Tag: para -#: preseed.xml:809 +#: preseed.xml:820 #, 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:817 +#: preseed.xml:828 #, no-c-format msgid "" "# You can choose to install non-free and contrib software.\n" @@ -1036,25 +1036,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:822 +#: preseed.xml:833 #, no-c-format msgid "Account setup" msgstr "" #. Tag: para -#: preseed.xml:823 +#: preseed.xml:834 #, 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:830 +#: preseed.xml:841 #, 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:840 +#: preseed.xml:851 #, no-c-format msgid "" "# Skip creation of a root account (normal user account will be able to\n" @@ -1080,37 +1080,37 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:842 +#: preseed.xml:853 #, 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 setup to allow administrative activities or root login (for instance by using SSH key authentication or <command>sudo</command>)." msgstr "" #. Tag: para -#: preseed.xml:852 +#: preseed.xml:863 #, no-c-format msgid "An MD5 hash for a password can be generated using the following command." msgstr "" #. Tag: screen -#: preseed.xml:856 +#: preseed.xml:867 #, no-c-format msgid "$ echo \"r00tme\" | mkpasswd -s -H MD5" msgstr "" #. Tag: title -#: preseed.xml:862 +#: preseed.xml:873 #, no-c-format msgid "Base system installation" msgstr "" #. Tag: para -#: preseed.xml:863 +#: preseed.xml:874 #, 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:870 +#: preseed.xml:881 #, no-c-format msgid "" "# Select the initramfs generator used to generate the initrd for 2.6 kernels.\n" @@ -1118,13 +1118,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:875 +#: preseed.xml:886 #, no-c-format msgid "Boot loader installation" msgstr "" #. Tag: screen -#: preseed.xml:877 +#: preseed.xml:888 #, no-c-format msgid "" "# Grub is the default boot loader (for x86). If you want lilo installed\n" @@ -1149,97 +1149,97 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:882 +#: preseed.xml:893 #, no-c-format msgid "Package selection" msgstr "" #. Tag: para -#: preseed.xml:883 +#: preseed.xml:894 #, 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:892 +#: preseed.xml:903 #, no-c-format msgid "standard" msgstr "" #. Tag: userinput -#: preseed.xml:895 +#: preseed.xml:906 #, no-c-format msgid "desktop" msgstr "" #. Tag: userinput -#: preseed.xml:898 +#: preseed.xml:909 #, no-c-format msgid "gnome-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:901 +#: preseed.xml:912 #, no-c-format msgid "kde-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:904 +#: preseed.xml:915 #, no-c-format msgid "web-server" msgstr "" #. Tag: userinput -#: preseed.xml:907 +#: preseed.xml:918 #, no-c-format msgid "print-server" msgstr "" #. Tag: userinput -#: preseed.xml:910 +#: preseed.xml:921 #, no-c-format msgid "dns-server" msgstr "" #. Tag: userinput -#: preseed.xml:913 +#: preseed.xml:924 #, no-c-format msgid "file-server" msgstr "" #. Tag: userinput -#: preseed.xml:916 +#: preseed.xml:927 #, no-c-format msgid "mail-server" msgstr "" #. Tag: userinput -#: preseed.xml:919 +#: preseed.xml:930 #, no-c-format msgid "sql-database" msgstr "" #. Tag: userinput -#: preseed.xml:922 +#: preseed.xml:933 #, no-c-format msgid "laptop" msgstr "" #. Tag: para -#: preseed.xml:926 +#: preseed.xml:937 #, 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:932 +#: preseed.xml:943 #, 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 either comma-separated or space-separated, so you can also use it easily on the kernel command line." msgstr "" #. Tag: screen -#: preseed.xml:942 +#: preseed.xml:953 #, no-c-format msgid "" "tasksel tasksel/first multiselect standard, desktop\n" @@ -1257,13 +1257,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:947 +#: preseed.xml:958 #, no-c-format msgid "Finishing up the first stage install" msgstr "" #. Tag: screen -#: preseed.xml:949 +#: preseed.xml:960 #, no-c-format msgid "" "# Avoid that last message about the install being complete.\n" @@ -1275,19 +1275,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:954 +#: preseed.xml:965 #, no-c-format msgid "Mailer configuration" msgstr "" #. Tag: para -#: preseed.xml:955 +#: preseed.xml:966 #, no-c-format msgid "During a normal install, exim asks only a few questions. Here's how to avoid even those. More complicated preseeding is possible." msgstr "" #. Tag: screen -#: preseed.xml:962 +#: preseed.xml:973 #, no-c-format msgid "" "exim4-config exim4/dc_eximconfig_configtype \\\n" @@ -1298,19 +1298,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:967 +#: preseed.xml:978 #, no-c-format msgid "X configuration" msgstr "" #. Tag: para -#: preseed.xml:968 +#: preseed.xml:979 #, no-c-format msgid "Preseeding Debian's X config is possible, but you probably need to know some details about the video hardware of the machine, since Debian's X configurator does not do fully automatic configuration of everything." msgstr "" #. Tag: screen -#: preseed.xml:976 +#: preseed.xml:987 #, no-c-format msgid "" "# X can detect the right driver for some cards, but if you're preseeding,\n" @@ -1336,13 +1336,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:981 +#: preseed.xml:992 #, no-c-format msgid "Preseeding other packages" msgstr "" #. Tag: screen -#: preseed.xml:983 +#: preseed.xml:994 #, no-c-format msgid "" "# Depending on what software you choose to install, or if things go wrong\n" @@ -1355,25 +1355,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:990 +#: preseed.xml:1001 #, no-c-format msgid "Advanced options" msgstr "" #. Tag: title -#: preseed.xml:993 +#: preseed.xml:1004 #, no-c-format msgid "Running custom commands during the installation" msgstr "" #. Tag: para -#: preseed.xml:994 +#: preseed.xml:1005 #, 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:1002 +#: preseed.xml:1013 #, no-c-format msgid "" "# d-i preseeding is inherently not secure. Nothing in the installer checks\n" @@ -1395,19 +1395,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1007 +#: preseed.xml:1018 #, no-c-format msgid "Using preseeding to change default values" msgstr "" #. Tag: para -#: preseed.xml:1008 +#: preseed.xml:1019 #, 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." msgstr "" #. Tag: screen -#: preseed.xml:1017 +#: preseed.xml:1028 #, no-c-format msgid "" "d-i foo/bar string value\n" @@ -1415,19 +1415,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1022 +#: preseed.xml:1033 #, no-c-format msgid "Chainloading preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:1023 +#: preseed.xml:1034 #, 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:1033 +#: preseed.xml:1044 #, no-c-format msgid "" "# More than one file can be listed, separated by spaces; all will be\n" @@ -1448,13 +1448,14 @@ msgid "" "\n" "# Most flexibly of all, this downloads a program and runs it. The program\n" "# can use commands such as debconf-set to manipulate the debconf database.\n" + "# More than one script can be listed, separated by spaces.\n" "# Note that if the filenames are relative, they are taken from the same\n" "# directory as the preconfiguration file that runs them.\n" - "d-i preseed/run string foo.sh" + "#d-i preseed/run string foo.sh" msgstr "" #. Tag: para -#: preseed.xml:1035 +#: preseed.xml:1046 #, 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 "" |