diff options
| author | Frans Pop <elendil@planet.nl> | 2006-11-04 17:29:15 +0000 |
|---|---|---|
| committer | Frans Pop <elendil@planet.nl> | 2006-11-04 17:29:15 +0000 |
| commit | c9370baa3c260ca72e5b1f8264a8107af2d40bd2 (patch) | |
| tree | ebc117a6306e9ed79220225e0a7a2c6a9604c0bc /po/pot | |
| parent | 227eaa2e27a9bcdab9eca6c4bf9fdb4891e5b23d (diff) | |
| download | installation-guide-c9370baa3c260ca72e5b1f8264a8107af2d40bd2.zip | |
Update of POT and PO files for the manual
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 193 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 613 |
2 files changed, 535 insertions, 271 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 0de9c3ea7..a04bb250a 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-10-29 14:49+0000\n" +"POT-Creation-Date: 2006-11-04 17:26+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" @@ -2074,131 +2074,200 @@ msgstr "" #. Tag: term #: boot-installer.xml:3057 #, no-c-format -msgid "cdrom-detect/eject" +msgid "auto-install/enabled" msgstr "" #. Tag: para #: boot-installer.xml:3058 #, no-c-format +msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. Short form: <userinput>auto=true</userinput> See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3069 +#, no-c-format +msgid "cdrom-detect/eject" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3070 +#, no-c-format msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically." msgstr "" #. Tag: para -#: boot-installer.xml:3067 +#: boot-installer.xml:3079 #, no-c-format msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation." msgstr "" #. Tag: term -#: boot-installer.xml:3078 +#: boot-installer.xml:3090 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:3079 +#: boot-installer.xml:3091 #, no-c-format msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." msgstr "" #. Tag: term -#: boot-installer.xml:3087 +#: boot-installer.xml:3099 #, no-c-format msgid "directfb/hw-accel" msgstr "" #. Tag: para -#: boot-installer.xml:3088 +#: boot-installer.xml:3100 #, no-c-format msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. To enable it, set this parameter to <userinput>true</userinput> when booting the installer." msgstr "" #. Tag: term -#: boot-installer.xml:3098 +#: boot-installer.xml:3110 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:3099 +#: boot-installer.xml:3111 #, no-c-format msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:3117 +#: boot-installer.xml:3122 +#, no-c-format +msgid "Passing parameters to kernel modules" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3123 +#, 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:3136 +#, 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:3143 +#, no-c-format +msgid "" + "The syntax to use to set parameters for modules is: <informalexample><screen>\n" + "<replaceable>module_name</replaceable>.<replaceable>parameter_name</replaceable>=<replaceable>value</replaceable>\n" + "</screen></informalexample> If you need to pass multiple parameters to the same or different modules, just repeat this. For example, to set an old 3Com network interface card to use the BNC (coax) connector and IRQ 10, you would pass:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:3153 +#, no-c-format +msgid "3c509.xcvr=3 3c509.irq=10" +msgstr "" + +#. Tag: title +#: boot-installer.xml:3165 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:3122 +#: boot-installer.xml:3170 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3123 +#: boot-installer.xml:3171 #, 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:3130 +#: boot-installer.xml:3178 #, 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:3136 +#: boot-installer.xml:3184 +#, no-c-format +msgid "There are two very simple things that you should try first." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3189 +#, 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:3195 +#, 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 isses with older CD-ROM drives are known to be resolved in this way." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3205 +#, 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:3211 #, 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:3144 +#: boot-installer.xml:3219 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:3147 +#: boot-installer.xml:3222 #, 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:3153 +#: boot-installer.xml:3228 #, 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:3160 +#: boot-installer.xml:3235 #, 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:3171 +#: boot-installer.xml:3246 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:3172 +#: boot-installer.xml:3247 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:3177 +#: boot-installer.xml:3252 #, 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:3183 +#: boot-installer.xml:3258 #, 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" @@ -2208,7 +2277,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3196 +#: boot-installer.xml:3271 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -2221,19 +2290,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3201 +#: boot-installer.xml:3276 #, 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:3213 +#: boot-installer.xml:3288 #, 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:3220 +#: boot-installer.xml:3295 #, 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" @@ -2246,13 +2315,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3234 +#: boot-installer.xml:3309 #, 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:3242 +#: boot-installer.xml:3317 #, 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" @@ -2261,7 +2330,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3252 +#: boot-installer.xml:3327 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -2274,199 +2343,199 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3266 +#: boot-installer.xml:3341 #, 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:3281 +#: boot-installer.xml:3356 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3283 +#: boot-installer.xml:3358 #, 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:3288 +#: boot-installer.xml:3363 #, 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:3297 +#: boot-installer.xml:3372 #, no-c-format msgid "If you are having the installation stall at a particular floppy, the first thing you should write it to a <emphasis>different</emphasis> floppy. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system." msgstr "" #. Tag: para -#: boot-installer.xml:3306 +#: boot-installer.xml:3381 #, no-c-format msgid "Normally you should not have 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:3312 +#: boot-installer.xml:3387 #, 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:3318 +#: boot-installer.xml:3393 #, 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:3327 +#: boot-installer.xml:3402 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:3329 +#: boot-installer.xml:3404 #, 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:3336 +#: boot-installer.xml:3411 #, 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:3343 +#: boot-installer.xml:3418 #, 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:3349 +#: boot-installer.xml:3424 #, 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:3360 +#: boot-installer.xml:3435 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3361 +#: boot-installer.xml:3436 #, 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:3366 +#: boot-installer.xml:3441 #, 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:3372 +#: boot-installer.xml:3447 #, 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:3381 +#: boot-installer.xml:3456 #, 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:3388 +#: boot-installer.xml:3463 #, 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:3402 +#: boot-installer.xml:3477 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:3403 +#: boot-installer.xml:3478 #, 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:3413 +#: boot-installer.xml:3488 #, 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:3430 +#: boot-installer.xml:3505 #, no-c-format msgid "System Freeze while Loading the USB Modules" msgstr "" #. Tag: para -#: boot-installer.xml:3431 +#: boot-installer.xml:3506 #, 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:3445 +#: boot-installer.xml:3520 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3447 +#: boot-installer.xml:3522 #, 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:3472 +#: boot-installer.xml:3547 #, no-c-format msgid "Bug Reporter" msgstr "" #. Tag: para -#: boot-installer.xml:3473 +#: boot-installer.xml:3548 #, no-c-format msgid "If you get through the initial boot phase but cannot complete the install, the bug reporter menu choice may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them in a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report you may want to attach this information to the bug report." msgstr "" #. Tag: para -#: boot-installer.xml:3484 +#: boot-installer.xml:3559 #, 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:3495 +#: boot-installer.xml:3570 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3496 +#: boot-installer.xml:3571 #, 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:3503 +#: boot-installer.xml:3578 #, 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:3510 +#: boot-installer.xml:3585 #, no-c-format msgid "" "Please 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/preseed.pot b/po/pot/preseed.pot index 8fbf77ec0..2ef10178f 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-10-29 14:48+0000\n" +"POT-Creation-Date: 2006-11-04 17:26+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" @@ -23,11 +23,11 @@ msgstr "" #. Tag: para #: preseed.xml:18 #, no-c-format -msgid "This appendix explains the intricacies of preseeding answers to questions in &d-i; to automate your installation." +msgid "This appendix explains how to preseed answers to questions in &d-i; to automate your installation." msgstr "" #. Tag: para -#: preseed.xml:23 preseed.xml:508 +#: preseed.xml:23 preseed.xml:604 #, no-c-format msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;." msgstr "" @@ -53,211 +53,173 @@ msgstr "" #. Tag: para #: preseed.xml:44 #, no-c-format -msgid "There are three methods that can be used for preseeding: <firstterm>initrd</firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. Initrd preseeding will work with any installation method and supports preseeding of more things, but it requires the most preparation. File and network preseeding each can be used with different installation methods. With file and network preseeding the first few installer questions cannot be preseeded because the preconfiguration file is only loaded after they have been asked." +msgid "There are three methods that can be used for preseeding: <firstterm>initrd</firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. Initrd preseeding will work with any installation method and supports preseeding of more things, but it requires the most preparation. File and network preseeding each can be used with different installation methods." msgstr "" #. Tag: para -#: preseed.xml:55 +#: preseed.xml:53 #, no-c-format msgid "The following table shows which preseeding methods can be used with which installation methods." msgstr "" #. Tag: entry -#: preseed.xml:64 +#: preseed.xml:62 #, no-c-format msgid "Installation method" msgstr "" #. Tag: entry -#: preseed.xml:64 +#: preseed.xml:62 #, no-c-format msgid "initrd" msgstr "" #. Tag: entry -#: preseed.xml:65 +#: preseed.xml:63 preseed.xml:461 #, no-c-format msgid "file" msgstr "" #. Tag: entry -#: preseed.xml:65 +#: preseed.xml:63 #, no-c-format msgid "network" msgstr "" #. Tag: entry -#: preseed.xml:71 +#: preseed.xml:69 #, no-c-format msgid "CD/DVD" msgstr "" #. Tag: entry -#: preseed.xml:72 preseed.xml:73 preseed.xml:77 preseed.xml:79 preseed.xml:82 preseed.xml:83 preseed.xml:87 preseed.xml:88 preseed.xml:92 preseed.xml:94 preseed.xml:97 preseed.xml:99 +#: preseed.xml:70 preseed.xml:71 preseed.xml:72 preseed.xml:82 preseed.xml:84 preseed.xml:87 preseed.xml:88 preseed.xml:89 preseed.xml:92 preseed.xml:93 preseed.xml:94 preseed.xml:97 preseed.xml:99 preseed.xml:102 preseed.xml:104 #, no-c-format msgid "<entry>yes</entry>" msgstr "" -#. Tag: entry -#: preseed.xml:74 preseed.xml:78 preseed.xml:84 preseed.xml:89 preseed.xml:93 preseed.xml:98 +#. Tag: para +#: preseed.xml:74 #, no-c-format -msgid "<entry>no</entry>" +msgid "but only if you have network access, and set <literal>preseed/url</literal> appropriately" msgstr "" #. Tag: entry -#: preseed.xml:76 +#: preseed.xml:81 #, no-c-format msgid "netboot" msgstr "" #. Tag: entry -#: preseed.xml:81 +#: preseed.xml:83 preseed.xml:98 preseed.xml:103 #, no-c-format -msgid "hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>" +msgid "<entry>no</entry>" msgstr "" #. Tag: entry #: preseed.xml:86 #, no-c-format -msgid "floppy based (cd-drivers)" +msgid "hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>" msgstr "" #. Tag: entry #: preseed.xml:91 #, no-c-format -msgid "floppy based (net-drivers)" +msgid "floppy based (cd-drivers)" msgstr "" #. Tag: entry #: preseed.xml:96 #, no-c-format +msgid "floppy based (net-drivers)" +msgstr "" + +#. Tag: entry +#: preseed.xml:101 +#, no-c-format msgid "generic/tape" msgstr "" #. Tag: para -#: preseed.xml:105 +#: preseed.xml:110 #, no-c-format msgid "An important difference between the preseeding methods is the point at which the preconfiguration file is loaded and processed. For initrd preseeding this is right at the start of the installation, before the first question is even asked. For file preseeding this is after the CD or CD image has been loaded. For network preseeding it is only after the network has been configured." msgstr "" #. Tag: para -#: preseed.xml:114 +#: preseed.xml:119 #, no-c-format -msgid "In practical terms this means for file and network preseeding that the questions about language, country and keyboard selection will already have been asked. For network preseeding add to that any questions related to network configuration. Some other questions that are only displayed at medium or low priority (like the first hardware detection run) will also already have been processed." +msgid "Obviously, any questions that have been processed before the preconfiguration file is loaded cannot be preseeded (this will include questions that are only displayed at medium or low priority, like the first hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way to avoid these questions being asked." msgstr "" #. Tag: para -#: preseed.xml:123 +#: preseed.xml:127 #, no-c-format -msgid "Obviously, any questions that have been processed before the preconfiguration file is loaded cannot be preseeded. <xref linkend=\"preseed-bootparms\"/> offers a way to avoid these questions being asked." +msgid "In order to avoid the questions that would normally appear before the preseeding occurs, you can start the installer in <quote>auto</quote> mode. This delays questions that would normally be asked too early for preseeding (i.e. language, country and keyboard selection) until after the network comes up, thus allowing them to be preseeded. It also runs the installation in crtitical priority, which avoids many unimportant questions. See <xref linkend=\"preseed-auto\"/> for details." msgstr "" #. Tag: title -#: preseed.xml:134 +#: preseed.xml:141 #, no-c-format msgid "Limitations" msgstr "" #. Tag: para -#: preseed.xml:135 +#: preseed.xml:142 #, no-c-format msgid "Although most questions used by &d-i; can be preseeded using this method, there are some notable exceptions. You must (re)partition an entire disk or use available free space on a disk; it is not possible to use existing partitions." msgstr "" #. Tag: title -#: preseed.xml:207 -#, no-c-format -msgid "Running custom commands during the installation" -msgstr "" - -#. Tag: para -#: preseed.xml:208 -#, 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. See <xref linkend=\"preseed-shell\"/> for details." -msgstr "" - -#. Tag: para -#: preseed.xml:217 -#, no-c-format -msgid "<userinput>preseed/early_command</userinput>: is run as soon as the preconfiguration file has been loaded" -msgstr "" - -#. Tag: para -#: preseed.xml:221 -#, no-c-format -msgid "<userinput>preseed/late_command</userinput>: is run just before the reboot at the end of the install, but before the <filename>/target</filename> filesystem has been unmounted" -msgstr "" - -#. Tag: title -#: preseed.xml:231 -#, no-c-format -msgid "Using preseeding to change default values" -msgstr "" - -#. Tag: para -#: preseed.xml:232 -#, 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:241 -#, no-c-format -msgid "" - "d-i foo/bar string value\n" - "d-i foo/bar seen false" -msgstr "" - -#. Tag: title -#: preseed.xml:247 +#: preseed.xml:216 #, no-c-format msgid "Using preseeding" msgstr "" #. Tag: para -#: preseed.xml:248 +#: preseed.xml:217 #, no-c-format -msgid "Of course you will first need to create a preconfiguration file and place it in the location from where you want to use it. Creating the preconfiguration file is covered later in this appendix. Putting it in the correct location is fairly straightforward for network preseeding or if you want to read the file off a floppy or usb-stick. If you want to include the file on a CD or DVD, you will have to remaster the ISO image. How to get the preconfiguration file included in the initrd is outside the scope of this document; please consult the developers documentation for &d-i;." +msgid "You will first need to create a preconfiguration file and place it in the location from where you want to use it. Creating the preconfiguration file is covered later in this appendix. Putting it in the correct location is fairly straightforward for network preseeding or if you want to read the file off a floppy or usb-stick. If you want to include the file on a CD or DVD, you will have to remaster the ISO image. How to get the preconfiguration file included in the initrd is outside the scope of this document; please consult the developers' documentation for &d-i;." msgstr "" #. Tag: para -#: preseed.xml:259 +#: preseed.xml:228 #, no-c-format msgid "An example preconfiguration file that you can use as basis for your own preconfiguration file is available from &urlset-example-preseed;. This file is based on the configuration fragments included in this appendix." msgstr "" #. Tag: title -#: preseed.xml:268 +#: preseed.xml:237 #, no-c-format msgid "Loading the preconfiguration file" msgstr "" #. Tag: para -#: preseed.xml:269 +#: preseed.xml:238 #, no-c-format msgid "If you are using initrd preseeding, you only have to make sure a file named <filename>preseed.cfg</filename> is included in the root directory of the initrd. The installer will automatically check if this file is present and load it." msgstr "" #. Tag: para -#: preseed.xml:276 +#: preseed.xml:245 #, no-c-format msgid "For the other preseeding methods you need to tell the installer what file to use when you boot it. This is normally done by passing the kernel a boot parameter, either manually at boot time or by editing the bootloader configuration file (e.g. <filename>syslinux.cfg</filename>) and adding the parameter to the end of the append line(s) for the kernel." msgstr "" #. Tag: para -#: preseed.xml:284 +#: preseed.xml:253 #, no-c-format msgid "If you do specify the preconfiguration file in the bootloader configuration, you might change the configuration so you don't need to hit enter to boot the installer. For syslinux this means setting the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>." msgstr "" #. Tag: para -#: preseed.xml:291 +#: preseed.xml:260 #, no-c-format msgid "To make sure the installer gets the right preconfiguration file, you can optionally specify a checksum for the file. Currently this needs to be a md5sum, and if specified it must match the preconfiguration file or the installer will refuse to use it." msgstr "" #. Tag: screen -#: preseed.xml:300 +#: preseed.xml:269 #, no-c-format msgid "" "Boot parameters to specify:\n" @@ -276,160 +238,361 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:302 +#: preseed.xml:271 #, no-c-format msgid "Note that <filename>preseed/url</filename> can be shortened to just <filename>url</filename> and <filename>preseed/file</filename> to just <filename>file</filename> when they are passed as boot parameters." msgstr "" +#. Tag: title +#: preseed.xml:281 +#, no-c-format +msgid "Using boot parameters to supplement preseeding" +msgstr "" + +#. Tag: para +#: preseed.xml:282 +#, no-c-format +msgid "If a preconfiguration file cannot be used to preseed some steps, the install can still be fully automated, since you can pass preseed values on the command line when booting the installer. Just pass <userinput>path/to/var=value</userinput> for any of the preseed variables listed in the examples." +msgstr "" + +#. Tag: para +#: preseed.xml:290 +#, 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." +msgstr "" + +#. Tag: para +#: preseed.xml:299 +#, 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:308 #, no-c-format -msgid "While you're at it, you may want to add a boot parameter <userinput>priority=critical</userinput>. This will avoid most questions even if the preseeding below misses some." +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:316 +#, 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:323 +#, 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:318 +#: preseed.xml:332 #, no-c-format -msgid "Using a DHCP server to specify preconfiguration files" +msgid "Auto mode" msgstr "" #. Tag: para -#: preseed.xml:319 +#: preseed.xml:333 #, 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)." +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" + "auto url=autoserver\n" + "</screen></informalexample> This relies on there being a DHCP server that will get the machine to the point where <literal>autoserver</literal> can be resolved by DNS, perhaps after adding the local domain if that was provided by DHCP. If this was done at a site where the domain is <literal>example.com</literal>, and they have a reasonably sane DHCP setup, it would result in the preseed file being retrieved from <literal>http://autoserver.example.com/d-i/etch/./preseed.cfg</literal>." msgstr "" -#. Tag: screen -#: preseed.xml:330 +#. Tag: para +#: preseed.xml:350 +#, 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>." +msgstr "" + +#. Tag: para +#: preseed.xml:370 #, no-c-format msgid "" - "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n" - " filename \"http://host/preseed.cfg\";\n" - "}" + "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" + "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:332 +#: preseed.xml:383 #, 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." +msgid "if the URL is missing a protocol, http is assumed," msgstr "" #. Tag: para -#: preseed.xml:339 +#: preseed.xml:386 #, 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." +msgid "if the hostname section contains no periods, it has the domain derived from DHCP appended to it, and" msgstr "" -#. Tag: title -#: preseed.xml:351 +#. Tag: para +#: preseed.xml:390 #, no-c-format -msgid "Using boot parameters to supplement preseeding" +msgid "if there's no <literal>/</literal>'s after the hostname, then the default path is added." msgstr "" #. Tag: para -#: preseed.xml:352 +#: preseed.xml:396 #, no-c-format -msgid "Some parts of the installation process cannot be automated using some forms of preseeding because the questions are asked before the preconfiguration file is loaded. For example, if the preconfiguration file is downloaded over the network, the network setup must be done first. One reason to use initrd preseeding is that it allows preseeding of even these early steps of the installation process." +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" + "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:361 +#: preseed.xml:410 #, no-c-format -msgid "If a preconfiguration file cannot be used to preseed some steps, the install can still be fully automated, since you can pass preseed values to the kernel on the command line. Just pass <userinput>path/to/var=value</userinput> for any of the preseed variables listed in the examples." +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:368 +#: preseed.xml:420 #, 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." +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:374 +#: preseed.xml:433 +#, 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:445 #, no-c-format -msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after the last <quote>--</quote> will be copied into the installed bootloader configuration (if supported by the installer for the bootloader). Note that the <quote>--</quote> may already be present in the default boot parameters, which means that unless you add another <quote>--</quote> all parameters specified at the boot prompt will be copied. That being the case, you should specify any preconfiguration options before any options required by the hardware in order to boot, and separate them with a <quote>--</quote> to ensure that only the latter are copied onto the target system." +msgid "Aliases useful with preseeding" msgstr "" #. Tag: para -#: preseed.xml:388 +#: preseed.xml:446 #, 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.)" +msgid "The following aliases can be useful when using (auto mode) preseeding." +msgstr "" + +#. Tag: entry +#: preseed.xml:456 +#, no-c-format +msgid "auto" +msgstr "" + +#. Tag: entry +#: preseed.xml:456 +#, no-c-format +msgid "auto-install/enabled" +msgstr "" + +#. Tag: entry +#: preseed.xml:457 +#, no-c-format +msgid "classes" +msgstr "" + +#. Tag: entry +#: preseed.xml:457 +#, no-c-format +msgid "auto-install/classes" +msgstr "" + +#. Tag: entry +#: preseed.xml:458 +#, no-c-format +msgid "<entry>fb</entry>" +msgstr "" + +#. Tag: entry +#: preseed.xml:458 +#, no-c-format +msgid "debian-installer/framebuffer" +msgstr "" + +#. Tag: entry +#: preseed.xml:459 +#, no-c-format +msgid "locale" +msgstr "" + +#. Tag: entry +#: preseed.xml:459 +#, no-c-format +msgid "debian-installer/locale" +msgstr "" + +#. Tag: entry +#: preseed.xml:460 +#, no-c-format +msgid "priority" +msgstr "" + +#. Tag: entry +#: preseed.xml:460 +#, no-c-format +msgid "debconf/priority" +msgstr "" + +#. Tag: entry +#: preseed.xml:461 +#, no-c-format +msgid "preseed/file" +msgstr "" + +#. Tag: entry +#: preseed.xml:462 +#, no-c-format +msgid "<entry>url</entry>" +msgstr "" + +#. Tag: entry +#: preseed.xml:462 +#, no-c-format +msgid "preseed/url" +msgstr "" + +#. Tag: entry +#: preseed.xml:463 +#, no-c-format +msgid "hostname " +msgstr "" + +#. Tag: entry +#: preseed.xml:463 +#, no-c-format +msgid "netcfg/get_hostname" +msgstr "" + +#. Tag: entry +#: preseed.xml:464 +#, no-c-format +msgid "domain" +msgstr "" + +#. Tag: entry +#: preseed.xml:464 +#, no-c-format +msgid "netcfg/get_domain" +msgstr "" + +#. Tag: entry +#: preseed.xml:465 +#, no-c-format +msgid "interface" +msgstr "" + +#. Tag: entry +#: preseed.xml:465 +#, no-c-format +msgid "netcfg/choose_interface" +msgstr "" + +#. Tag: entry +#: preseed.xml:466 +#, no-c-format +msgid "suite" +msgstr "" + +#. Tag: entry +#: preseed.xml:466 +#, no-c-format +msgid "mirror/suite" +msgstr "" + +#. Tag: title +#: preseed.xml:473 +#, no-c-format +msgid "Using a DHCP server to specify preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:396 +#: preseed.xml:474 #, 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." +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:485 +#, no-c-format +msgid "" + "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n" + " filename \"http://host/preseed.cfg\";\n" + "}" msgstr "" #. Tag: para -#: preseed.xml:403 +#: preseed.xml:487 #, 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." +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:494 +#, 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:413 +#: preseed.xml:508 #, no-c-format msgid "Creating a preconfiguration file" msgstr "" #. Tag: para -#: preseed.xml:414 +#: preseed.xml:509 #, 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:420 +#: preseed.xml:515 #, no-c-format msgid "<owner> <question name> <question type> <value>" msgstr "" #. Tag: para -#: preseed.xml:422 +#: preseed.xml:517 #, no-c-format msgid "There are a few rules to keep in mind when writing a preconfiguration file." msgstr "" #. Tag: para -#: preseed.xml:429 +#: preseed.xml:524 #, 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:433 +#: preseed.xml:528 #, 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:439 +#: preseed.xml:534 #, 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:445 +#: preseed.xml:540 #, 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:451 +#: preseed.xml:546 #, 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:456 +#: preseed.xml:551 #, 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:463 +#: preseed.xml:558 #, no-c-format msgid "" "$ debconf-get-selections --installer > <replaceable>file</replaceable>\n" @@ -437,67 +600,67 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:465 +#: preseed.xml:560 #, 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:473 +#: preseed.xml:568 #, 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:481 +#: preseed.xml:576 #, 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:489 +#: preseed.xml:584 #, 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:497 +#: preseed.xml:592 #, 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:507 +#: preseed.xml:603 #, no-c-format msgid "Contents of the preconfiguration file" msgstr "" #. Tag: para -#: preseed.xml:513 +#: preseed.xml:609 #, 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:524 +#: preseed.xml:620 #, no-c-format msgid "Localization" msgstr "" #. Tag: para -#: preseed.xml:525 +#: preseed.xml:621 #, 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:531 +#: preseed.xml:627 #, 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:537 +#: preseed.xml:633 #, no-c-format msgid "" "# Locale sets language and country.\n" @@ -505,13 +668,13 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:539 +#: preseed.xml:635 #, 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:546 +#: preseed.xml:642 #, no-c-format msgid "" "# Keyboard selection.\n" @@ -522,43 +685,43 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:548 +#: preseed.xml:644 #, 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:557 +#: preseed.xml:653 #, 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:567 +#: preseed.xml:663 #, no-c-format msgid "Network configuration" msgstr "" #. Tag: para -#: preseed.xml:568 +#: preseed.xml:664 #, 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:576 +#: preseed.xml:672 #, 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:582 +#: preseed.xml:678 #, 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:592 +#: preseed.xml:688 #, no-c-format msgid "" "killall.sh dhclient\n" @@ -566,7 +729,7 @@ msgid "" msgstr "" #. Tag: screen -#: preseed.xml:596 +#: preseed.xml:692 #, no-c-format msgid "" "# netcfg will choose an interface that has link if possible. This makes it\n" @@ -610,31 +773,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:601 +#: preseed.xml:697 #, no-c-format msgid "Mirror settings" msgstr "" #. Tag: para -#: preseed.xml:602 +#: preseed.xml:698 #, 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:609 +#: preseed.xml:705 #, no-c-format msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system." msgstr "" #. Tag: para -#: preseed.xml:614 +#: preseed.xml:710 #, 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:626 +#: preseed.xml:722 #, no-c-format msgid "" "d-i mirror/country string enter information manually\n" @@ -649,25 +812,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:631 +#: preseed.xml:727 #, no-c-format msgid "Partitioning" msgstr "" #. Tag: para -#: preseed.xml:632 +#: preseed.xml:728 #, 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:643 +#: preseed.xml:739 #, 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:651 +#: preseed.xml:747 #, no-c-format msgid "" "# If the system has free space you can choose to only partition that space.\n" @@ -733,31 +896,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:656 +#: preseed.xml:752 #, no-c-format msgid "Partitioning using RAID" msgstr "" #. Tag: para -#: preseed.xml:657 +#: preseed.xml:753 #, 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:667 +#: preseed.xml:763 #, 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:675 +#: preseed.xml:771 #, 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:683 +#: preseed.xml:779 #, no-c-format msgid "" "# NOTE: this option is of beta release quality and should be used carefully\n" @@ -808,13 +971,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:688 +#: preseed.xml:784 #, no-c-format msgid "Clock and time zone setup" msgstr "" #. Tag: screen -#: preseed.xml:690 +#: preseed.xml:786 #, no-c-format msgid "" "# Controls whether or not the hardware clock is set to UTC.\n" @@ -826,19 +989,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:695 +#: preseed.xml:791 #, no-c-format msgid "Apt setup" msgstr "" #. Tag: para -#: preseed.xml:696 +#: preseed.xml:792 #, 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:704 +#: preseed.xml:800 #, no-c-format msgid "" "# You can choose to install non-free and contrib software.\n" @@ -859,25 +1022,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:709 +#: preseed.xml:805 #, no-c-format msgid "Account setup" msgstr "" #. Tag: para -#: preseed.xml:710 +#: preseed.xml:806 #, 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:717 +#: preseed.xml:813 #, 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:727 +#: preseed.xml:823 #, no-c-format msgid "" "# Skip creation of a root account (normal user account will be able to\n" @@ -903,37 +1066,37 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:729 +#: preseed.xml:825 #, 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:739 +#: preseed.xml:835 #, no-c-format msgid "An MD5 hash for a password can be generated using the following command." msgstr "" #. Tag: screen -#: preseed.xml:743 +#: preseed.xml:839 #, no-c-format msgid "$ echo \"r00tme\" | mkpasswd -s -H MD5" msgstr "" #. Tag: title -#: preseed.xml:749 +#: preseed.xml:845 #, no-c-format msgid "Base system installation" msgstr "" #. Tag: para -#: preseed.xml:750 +#: preseed.xml:846 #, 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:757 +#: preseed.xml:853 #, no-c-format msgid "" "# Select the initramfs generator used to generate the initrd for 2.6 kernels.\n" @@ -941,13 +1104,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:762 +#: preseed.xml:858 #, no-c-format msgid "Boot loader installation" msgstr "" #. Tag: screen -#: preseed.xml:764 +#: preseed.xml:860 #, no-c-format msgid "" "# Grub is the default boot loader (for x86). If you want lilo installed\n" @@ -972,97 +1135,97 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:769 +#: preseed.xml:865 #, no-c-format msgid "Package selection" msgstr "" #. Tag: para -#: preseed.xml:770 +#: preseed.xml:866 #, 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:779 +#: preseed.xml:875 #, no-c-format msgid "standard" msgstr "" #. Tag: userinput -#: preseed.xml:782 +#: preseed.xml:878 #, no-c-format msgid "desktop" msgstr "" #. Tag: userinput -#: preseed.xml:785 +#: preseed.xml:881 #, no-c-format msgid "gnome-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:788 +#: preseed.xml:884 #, no-c-format msgid "kde-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:791 +#: preseed.xml:887 #, no-c-format msgid "web-server" msgstr "" #. Tag: userinput -#: preseed.xml:794 +#: preseed.xml:890 #, no-c-format msgid "print-server" msgstr "" #. Tag: userinput -#: preseed.xml:797 +#: preseed.xml:893 #, no-c-format msgid "dns-server" msgstr "" #. Tag: userinput -#: preseed.xml:800 +#: preseed.xml:896 #, no-c-format msgid "file-server" msgstr "" #. Tag: userinput -#: preseed.xml:803 +#: preseed.xml:899 #, no-c-format msgid "mail-server" msgstr "" #. Tag: userinput -#: preseed.xml:806 +#: preseed.xml:902 #, no-c-format msgid "sql-database" msgstr "" #. Tag: userinput -#: preseed.xml:809 +#: preseed.xml:905 #, no-c-format msgid "laptop" msgstr "" #. Tag: para -#: preseed.xml:813 +#: preseed.xml:909 #, 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:819 +#: preseed.xml:915 #, 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:829 +#: preseed.xml:925 #, no-c-format msgid "" "tasksel tasksel/first multiselect standard, desktop\n" @@ -1080,13 +1243,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:834 +#: preseed.xml:930 #, no-c-format msgid "Finishing up the first stage install" msgstr "" #. Tag: screen -#: preseed.xml:836 +#: preseed.xml:932 #, no-c-format msgid "" "# Avoid that last message about the install being complete.\n" @@ -1098,19 +1261,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:841 +#: preseed.xml:937 #, no-c-format msgid "Mailer configuration" msgstr "" #. Tag: para -#: preseed.xml:842 +#: preseed.xml:938 #, 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:849 +#: preseed.xml:945 #, no-c-format msgid "" "exim4-config exim4/dc_eximconfig_configtype \\\n" @@ -1121,19 +1284,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:854 +#: preseed.xml:950 #, no-c-format msgid "X configuration" msgstr "" #. Tag: para -#: preseed.xml:855 +#: preseed.xml:951 #, 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:863 +#: preseed.xml:959 #, no-c-format msgid "" "# X can detect the right driver for some cards, but if you're preseeding,\n" @@ -1159,13 +1322,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:868 +#: preseed.xml:964 #, no-c-format msgid "Preseeding other packages" msgstr "" #. Tag: screen -#: preseed.xml:870 +#: preseed.xml:966 #, no-c-format msgid "" "# Depending on what software you choose to install, or if things go wrong\n" @@ -1178,19 +1341,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:876 +#: preseed.xml:973 #, no-c-format msgid "Advanced options" msgstr "" #. Tag: title -#: preseed.xml:879 +#: preseed.xml:976 +#, no-c-format +msgid "Running custom commands during the installation" +msgstr "" + +#. Tag: para +#: preseed.xml:977 #, no-c-format -msgid "Shell commands" +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:881 +#: preseed.xml:985 #, no-c-format msgid "" "# d-i preseeding is inherently not secure. Nothing in the installer checks\n" @@ -1212,22 +1381,42 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:886 +#: preseed.xml:990 +#, no-c-format +msgid "Using preseeding to change default values" +msgstr "" + +#. Tag: para +#: preseed.xml:991 +#, 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:1000 +#, no-c-format +msgid "" + "d-i foo/bar string value\n" + "d-i foo/bar seen false" +msgstr "" + +#. Tag: title +#: preseed.xml:1005 #, no-c-format msgid "Chainloading preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:887 +#: preseed.xml:1006 #, 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:897 +#: preseed.xml:1016 #, no-c-format msgid "" - "# More that one file can be listed, separated by spaces; all will be\n" + "# More than one file can be listed, separated by spaces; all will be\n" "# loaded. The included files can have preseed/include directives of their\n" "# own as well. Note that if the filenames are relative, they are taken from\n" "# the same directory as the preconfiguration file that includes them.\n" @@ -1250,3 +1439,9 @@ msgid "" "d-i preseed/run string foo.sh" msgstr "" +#. Tag: para +#: preseed.xml:1018 +#, 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 "" + |