diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 264 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 312 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 246 |
3 files changed, 441 insertions, 381 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 6b76f33dd..b54490ef2 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-11-27 20:17+0000\n" +"POT-Creation-Date: 2006-11-29 17:16+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" @@ -1876,299 +1876,341 @@ msgstr "" #. Tag: para #: boot-installer.xml:2851 #, no-c-format -msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=slang</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=ncurses</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=corba</userinput></para> </listitem> </itemizedlist> The default front end is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally only the <userinput>newt</userinput> frontend is available on default install media, so this is not very useful right now." +msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally only the <userinput>newt</userinput> frontend is available on default install media. On architectures which support it, the graphical installer uses the <userinput>gtk</userinput> frontend." msgstr "" #. Tag: term -#: boot-installer.xml:2887 +#: boot-installer.xml:2880 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:2888 +#: boot-installer.xml:2881 #, no-c-format msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)" msgstr "" #. Tag: userinput -#: boot-installer.xml:2897 +#: boot-installer.xml:2890 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:2898 +#: boot-installer.xml:2891 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:2902 +#: boot-installer.xml:2895 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:2903 +#: boot-installer.xml:2896 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:2907 +#: boot-installer.xml:2900 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:2908 +#: boot-installer.xml:2901 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:2912 +#: boot-installer.xml:2905 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:2913 +#: boot-installer.xml:2906 #, no-c-format msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot." msgstr "" #. Tag: term -#: boot-installer.xml:2927 +#: boot-installer.xml:2920 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:2928 +#: boot-installer.xml:2921 #, no-c-format msgid "The value of the parameter is the path to the device to load the Debian installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>" msgstr "" #. Tag: para -#: boot-installer.xml:2934 +#: boot-installer.xml:2927 #, no-c-format msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device." msgstr "" #. Tag: term -#: boot-installer.xml:2944 +#: boot-installer.xml:2937 #, no-c-format msgid "debian-installer/framebuffer" msgstr "" #. Tag: para -#: boot-installer.xml:2945 +#: boot-installer.xml:2938 #, no-c-format msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature by the parameter <userinput>debian-installer/framebuffer=false</userinput>, or <userinput>fb=false</userinput> for short. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install." msgstr "" #. Tag: para -#: boot-installer.xml:2955 +#: boot-installer.xml:2948 #, no-c-format msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card." msgstr "" #. Tag: para -#: boot-installer.xml:2961 +#: boot-installer.xml:2954 #, no-c-format msgid "Such problems have been reported on the Amiga 1200 and SE/30." msgstr "" #. Tag: para -#: boot-installer.xml:2965 +#: boot-installer.xml:2958 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:2969 +#: boot-installer.xml:2962 #, no-c-format msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short." msgstr "" #. Tag: term -#: boot-installer.xml:2983 +#: boot-installer.xml:2976 #, no-c-format msgid "debian-installer/theme" msgstr "" #. Tag: para -#: boot-installer.xml:2984 +#: boot-installer.xml:2977 #, no-c-format msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with parameter <userinput>debian-installer/theme=<replaceable>dark</replaceable></userinput> or <userinput>theme=<replaceable>dark</replaceable></userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:2997 +#: boot-installer.xml:2990 #, no-c-format msgid "debian-installer/probe/usb" msgstr "" #. Tag: para -#: boot-installer.xml:2998 +#: boot-installer.xml:2991 #, no-c-format msgid "Set to <userinput>false</userinput> to prevent probing for USB on boot, if that causes problems." msgstr "" #. Tag: term -#: boot-installer.xml:3007 +#: boot-installer.xml:3000 boot-installer.xml:3153 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" #. Tag: para -#: boot-installer.xml:3008 +#: boot-installer.xml:3001 #, no-c-format msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails." msgstr "" #. Tag: para -#: boot-installer.xml:3015 +#: boot-installer.xml:3008 #, no-c-format msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually." msgstr "" #. Tag: term -#: boot-installer.xml:3026 +#: boot-installer.xml:3019 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:3027 +#: boot-installer.xml:3020 #, no-c-format msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." msgstr "" #. Tag: term -#: boot-installer.xml:3037 +#: boot-installer.xml:3030 #, no-c-format msgid "preseed/url" msgstr "" #. Tag: para -#: boot-installer.xml:3038 +#: boot-installer.xml:3031 #, no-c-format -msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>url</userinput>" +msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>url</userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:3048 +#: boot-installer.xml:3041 #, no-c-format msgid "preseed/file" msgstr "" #. Tag: para -#: boot-installer.xml:3049 +#: boot-installer.xml:3042 #, no-c-format -msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>file</userinput>" +msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>file</userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:3059 +#: boot-installer.xml:3052 #, no-c-format msgid "auto-install/enabled" msgstr "" #. Tag: para -#: boot-installer.xml:3060 +#: boot-installer.xml:3053 #, 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:3071 +#: boot-installer.xml:3064 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:3072 +#: boot-installer.xml:3065 #, 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:3081 +#: boot-installer.xml:3074 #, 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:3092 +#: boot-installer.xml:3085 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:3093 +#: boot-installer.xml:3086 #, 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:3101 +#: boot-installer.xml:3094 #, no-c-format msgid "mouse/left" msgstr "" #. Tag: para -#: boot-installer.xml:3102 +#: boot-installer.xml:3095 #, no-c-format msgid "For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to <userinput>true</userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:3111 +#: boot-installer.xml:3104 #, no-c-format msgid "directfb/hw-accel" msgstr "" #. Tag: para -#: boot-installer.xml:3112 +#: boot-installer.xml:3105 #, 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:3122 +#: boot-installer.xml:3115 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:3123 +#: boot-installer.xml:3116 #, 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:3134 +#: boot-installer.xml:3127 +#, no-c-format +msgid "Using boot parameters to answer questions" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3128 +#, no-c-format +msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3140 +#, no-c-format +msgid "debian-installer/locale" +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." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3154 +#, 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 +#, no-c-format +msgid "tasksel:tasksel/first" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3164 +#, 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 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:3135 +#: boot-installer.xml:3179 #, 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:3148 +#: boot-installer.xml:3192 #, 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:3155 +#: boot-installer.xml:3199 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -2177,109 +2219,109 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3165 +#: boot-installer.xml:3209 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:3177 +#: boot-installer.xml:3221 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:3182 +#: boot-installer.xml:3226 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3183 +#: boot-installer.xml:3227 #, 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:3190 +#: boot-installer.xml:3234 #, 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:3196 +#: boot-installer.xml:3240 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:3201 +#: boot-installer.xml:3245 #, 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:3207 +#: boot-installer.xml:3251 #, 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:3217 +#: boot-installer.xml:3261 #, 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:3223 +#: boot-installer.xml:3267 #, 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:3231 +#: boot-installer.xml:3275 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:3234 +#: boot-installer.xml:3278 #, 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:3240 +#: boot-installer.xml:3284 #, 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:3247 +#: boot-installer.xml:3291 #, 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:3258 +#: boot-installer.xml:3302 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:3259 +#: boot-installer.xml:3303 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:3264 +#: boot-installer.xml:3308 #, 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:3270 +#: boot-installer.xml:3314 #, 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" @@ -2289,7 +2331,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3283 +#: boot-installer.xml:3327 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -2302,19 +2344,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3288 +#: boot-installer.xml:3332 #, 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:3300 +#: boot-installer.xml:3344 #, 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:3307 +#: boot-installer.xml:3351 #, 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" @@ -2327,13 +2369,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3321 +#: boot-installer.xml:3365 #, 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:3329 +#: boot-installer.xml:3373 #, 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" @@ -2342,7 +2384,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3339 +#: boot-installer.xml:3383 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -2355,199 +2397,199 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3353 +#: boot-installer.xml:3397 #, 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:3368 +#: boot-installer.xml:3412 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3370 +#: boot-installer.xml:3414 #, 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:3375 +#: boot-installer.xml:3419 #, 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:3384 +#: boot-installer.xml:3428 #, 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:3393 +#: boot-installer.xml:3437 #, 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:3399 +#: boot-installer.xml:3443 #, 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:3405 +#: boot-installer.xml:3449 #, 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:3414 +#: boot-installer.xml:3458 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:3416 +#: boot-installer.xml:3460 #, 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:3423 +#: boot-installer.xml:3467 #, 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:3430 +#: boot-installer.xml:3474 #, 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:3436 +#: boot-installer.xml:3480 #, 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:3447 +#: boot-installer.xml:3491 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3448 +#: boot-installer.xml:3492 #, 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:3453 +#: boot-installer.xml:3497 #, 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:3459 +#: boot-installer.xml:3503 #, 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:3468 +#: boot-installer.xml:3512 #, 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:3475 +#: boot-installer.xml:3519 #, 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:3489 +#: boot-installer.xml:3533 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:3490 +#: boot-installer.xml:3534 #, 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:3500 +#: boot-installer.xml:3544 #, 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:3517 +#: boot-installer.xml:3561 #, no-c-format msgid "System Freeze while Loading the USB Modules" msgstr "" #. Tag: para -#: boot-installer.xml:3518 +#: boot-installer.xml:3562 #, 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:3532 +#: boot-installer.xml:3576 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3534 +#: boot-installer.xml:3578 #, 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:3559 +#: boot-installer.xml:3603 #, no-c-format msgid "Bug Reporter" msgstr "" #. Tag: para -#: boot-installer.xml:3560 +#: boot-installer.xml:3604 #, 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:3571 +#: boot-installer.xml:3615 #, 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:3582 +#: boot-installer.xml:3626 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3583 +#: boot-installer.xml:3627 #, 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:3590 +#: boot-installer.xml:3634 #, 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:3597 +#: boot-installer.xml:3641 #, 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 fe4f3abd6..4df0c6147 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-24 21:13+0000\n" +"POT-Creation-Date: 2006-11-29 17:16+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:604 +#: preseed.xml:23 preseed.xml:621 #, 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:461 +#: preseed.xml:63 preseed.xml:478 #, no-c-format msgid "file" msgstr "" @@ -246,53 +246,65 @@ msgstr "" #. Tag: title #: preseed.xml:281 #, no-c-format -msgid "Using boot parameters to supplement preseeding" +msgid "Using boot parameters to preseed questions" 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." +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." msgstr "" #. Tag: para -#: preseed.xml:290 +#: preseed.xml:288 #, 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." +msgid "Boot parameters can also be used if you do not really want to use preseeding, but just want to provide an answer for a specific question. Some examples where this can be useful are documented elsewhere in this manual." msgstr "" #. Tag: para -#: preseed.xml:299 +#: 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." +msgstr "" + +#. Tag: para +#: preseed.xml:306 +#, 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 #, 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 +#: preseed.xml:325 #, 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:316 +#: preseed.xml:333 #, 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 +#: preseed.xml:340 #, 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:332 +#: preseed.xml:349 #, no-c-format msgid "Auto mode" msgstr "" #. Tag: para -#: preseed.xml:333 +#: preseed.xml:350 #, 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" @@ -301,13 +313,13 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:350 +#: preseed.xml:367 #, 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 +#: preseed.xml:387 #, 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" @@ -316,25 +328,25 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:383 +#: preseed.xml:400 #, no-c-format msgid "if the URL is missing a protocol, http is assumed," msgstr "" #. Tag: para -#: preseed.xml:386 +#: preseed.xml:403 #, 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:390 +#: preseed.xml:407 #, 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:396 +#: preseed.xml:413 #, 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" @@ -343,175 +355,175 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:410 +#: preseed.xml:427 #, 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:420 +#: preseed.xml:437 #, 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:433 +#: preseed.xml:450 #, 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 +#: preseed.xml:462 #, no-c-format msgid "Aliases useful with preseeding" msgstr "" #. Tag: para -#: preseed.xml:446 +#: preseed.xml:463 #, no-c-format msgid "The following aliases can be useful when using (auto mode) preseeding." msgstr "" #. Tag: entry -#: preseed.xml:456 +#: preseed.xml:473 #, no-c-format msgid "auto" msgstr "" #. Tag: entry -#: preseed.xml:456 +#: preseed.xml:473 #, no-c-format msgid "auto-install/enabled" msgstr "" #. Tag: entry -#: preseed.xml:457 +#: preseed.xml:474 #, no-c-format msgid "classes" msgstr "" #. Tag: entry -#: preseed.xml:457 +#: preseed.xml:474 #, no-c-format msgid "auto-install/classes" msgstr "" #. Tag: entry -#: preseed.xml:458 +#: preseed.xml:475 #, no-c-format msgid "<entry>fb</entry>" msgstr "" #. Tag: entry -#: preseed.xml:458 +#: preseed.xml:475 #, no-c-format msgid "debian-installer/framebuffer" msgstr "" #. Tag: entry -#: preseed.xml:459 +#: preseed.xml:476 #, no-c-format msgid "locale" msgstr "" #. Tag: entry -#: preseed.xml:459 +#: preseed.xml:476 #, no-c-format msgid "debian-installer/locale" msgstr "" #. Tag: entry -#: preseed.xml:460 +#: preseed.xml:477 #, no-c-format msgid "priority" msgstr "" #. Tag: entry -#: preseed.xml:460 +#: preseed.xml:477 #, no-c-format msgid "debconf/priority" msgstr "" #. Tag: entry -#: preseed.xml:461 +#: preseed.xml:478 #, no-c-format msgid "preseed/file" msgstr "" #. Tag: entry -#: preseed.xml:462 +#: preseed.xml:479 #, no-c-format msgid "<entry>url</entry>" msgstr "" #. Tag: entry -#: preseed.xml:462 +#: preseed.xml:479 #, no-c-format msgid "preseed/url" msgstr "" #. Tag: entry -#: preseed.xml:463 +#: preseed.xml:480 #, no-c-format msgid "hostname " msgstr "" #. Tag: entry -#: preseed.xml:463 +#: preseed.xml:480 #, no-c-format msgid "netcfg/get_hostname" msgstr "" #. Tag: entry -#: preseed.xml:464 +#: preseed.xml:481 #, no-c-format msgid "domain" msgstr "" #. Tag: entry -#: preseed.xml:464 +#: preseed.xml:481 #, no-c-format msgid "netcfg/get_domain" msgstr "" #. Tag: entry -#: preseed.xml:465 +#: preseed.xml:482 #, no-c-format msgid "interface" msgstr "" #. Tag: entry -#: preseed.xml:465 +#: preseed.xml:482 #, no-c-format msgid "netcfg/choose_interface" msgstr "" #. Tag: entry -#: preseed.xml:466 +#: preseed.xml:483 #, no-c-format msgid "suite" msgstr "" #. Tag: entry -#: preseed.xml:466 +#: preseed.xml:483 #, no-c-format msgid "mirror/suite" msgstr "" #. Tag: title -#: preseed.xml:473 +#: preseed.xml:490 #, no-c-format msgid "Using a DHCP server to specify preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:474 +#: preseed.xml:491 #, 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:485 +#: preseed.xml:502 #, no-c-format msgid "" "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n" @@ -520,79 +532,79 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:487 +#: preseed.xml:504 #, 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:494 +#: preseed.xml:511 #, 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:508 +#: preseed.xml:525 #, no-c-format msgid "Creating a preconfiguration file" msgstr "" #. Tag: para -#: preseed.xml:509 +#: preseed.xml:526 #, 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:515 +#: preseed.xml:532 #, no-c-format msgid "<owner> <question name> <question type> <value>" msgstr "" #. Tag: para -#: preseed.xml:517 +#: preseed.xml:534 #, no-c-format msgid "There are a few rules to keep in mind when writing a preconfiguration file." msgstr "" #. Tag: para -#: preseed.xml:524 +#: preseed.xml:541 #, 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:528 +#: preseed.xml:545 #, 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:534 +#: preseed.xml:551 #, 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:540 +#: preseed.xml:557 #, 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:546 +#: preseed.xml:563 #, 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:551 +#: preseed.xml:568 #, 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:558 +#: preseed.xml:575 #, no-c-format msgid "" "$ debconf-get-selections --installer > <replaceable>file</replaceable>\n" @@ -600,67 +612,67 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:560 +#: preseed.xml:577 #, 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:568 +#: preseed.xml:585 #, 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:576 +#: preseed.xml:593 #, 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:584 +#: preseed.xml:601 #, 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:592 +#: preseed.xml:609 #, 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:603 +#: preseed.xml:620 #, no-c-format msgid "Contents of the preconfiguration file" msgstr "" #. Tag: para -#: preseed.xml:609 +#: preseed.xml:626 #, 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:620 +#: preseed.xml:637 #, no-c-format msgid "Localization" msgstr "" #. Tag: para -#: preseed.xml:621 +#: preseed.xml:638 #, 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:627 +#: preseed.xml:644 #, 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:633 +#: preseed.xml:650 #, no-c-format msgid "" "# Locale sets language and country.\n" @@ -668,13 +680,13 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:635 +#: preseed.xml:652 #, 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:642 +#: preseed.xml:659 #, no-c-format msgid "" "# Keyboard selection.\n" @@ -685,43 +697,43 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:644 +#: preseed.xml:661 #, 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:653 +#: preseed.xml:670 #, 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:663 +#: preseed.xml:680 #, no-c-format msgid "Network configuration" msgstr "" #. Tag: para -#: preseed.xml:664 +#: preseed.xml:681 #, 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:672 +#: preseed.xml:689 #, 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:678 +#: preseed.xml:695 #, 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:688 +#: preseed.xml:705 #, no-c-format msgid "" "killall.sh dhclient\n" @@ -729,7 +741,7 @@ msgid "" msgstr "" #. Tag: screen -#: preseed.xml:692 +#: preseed.xml:709 #, no-c-format msgid "" "# netcfg will choose an interface that has link if possible. This makes it\n" @@ -773,31 +785,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:697 +#: preseed.xml:714 #, no-c-format msgid "Mirror settings" msgstr "" #. Tag: para -#: preseed.xml:698 +#: preseed.xml:715 #, 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:705 +#: preseed.xml:722 #, no-c-format msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system." msgstr "" #. Tag: para -#: preseed.xml:710 +#: preseed.xml:727 #, 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:722 +#: preseed.xml:739 #, no-c-format msgid "" "d-i mirror/country string enter information manually\n" @@ -812,25 +824,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:727 +#: preseed.xml:744 #, no-c-format msgid "Partitioning" msgstr "" #. Tag: para -#: preseed.xml:728 +#: preseed.xml:745 #, 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:739 +#: preseed.xml:756 #, 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:747 +#: preseed.xml:764 #, no-c-format msgid "" "# If the system has free space you can choose to only partition that space.\n" @@ -896,31 +908,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:752 +#: preseed.xml:769 #, no-c-format msgid "Partitioning using RAID" msgstr "" #. Tag: para -#: preseed.xml:753 +#: preseed.xml:770 #, 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:763 +#: preseed.xml:780 #, 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:771 +#: preseed.xml:788 #, 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:779 +#: preseed.xml:796 #, no-c-format msgid "" "# NOTE: this option is of beta release quality and should be used carefully\n" @@ -971,13 +983,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:784 +#: preseed.xml:801 #, no-c-format msgid "Clock and time zone setup" msgstr "" #. Tag: screen -#: preseed.xml:786 +#: preseed.xml:803 #, no-c-format msgid "" "# Controls whether or not the hardware clock is set to UTC.\n" @@ -989,19 +1001,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:791 +#: preseed.xml:808 #, no-c-format msgid "Apt setup" msgstr "" #. Tag: para -#: preseed.xml:792 +#: preseed.xml:809 #, 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:800 +#: preseed.xml:817 #, no-c-format msgid "" "# You can choose to install non-free and contrib software.\n" @@ -1024,25 +1036,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:805 +#: preseed.xml:822 #, no-c-format msgid "Account setup" msgstr "" #. Tag: para -#: preseed.xml:806 +#: preseed.xml:823 #, 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:813 +#: preseed.xml:830 #, 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:823 +#: preseed.xml:840 #, no-c-format msgid "" "# Skip creation of a root account (normal user account will be able to\n" @@ -1068,37 +1080,37 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:825 +#: preseed.xml:842 #, 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:835 +#: preseed.xml:852 #, no-c-format msgid "An MD5 hash for a password can be generated using the following command." msgstr "" #. Tag: screen -#: preseed.xml:839 +#: preseed.xml:856 #, no-c-format msgid "$ echo \"r00tme\" | mkpasswd -s -H MD5" msgstr "" #. Tag: title -#: preseed.xml:845 +#: preseed.xml:862 #, no-c-format msgid "Base system installation" msgstr "" #. Tag: para -#: preseed.xml:846 +#: preseed.xml:863 #, 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:853 +#: preseed.xml:870 #, no-c-format msgid "" "# Select the initramfs generator used to generate the initrd for 2.6 kernels.\n" @@ -1106,13 +1118,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:858 +#: preseed.xml:875 #, no-c-format msgid "Boot loader installation" msgstr "" #. Tag: screen -#: preseed.xml:860 +#: preseed.xml:877 #, no-c-format msgid "" "# Grub is the default boot loader (for x86). If you want lilo installed\n" @@ -1137,97 +1149,97 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:865 +#: preseed.xml:882 #, no-c-format msgid "Package selection" msgstr "" #. Tag: para -#: preseed.xml:866 +#: preseed.xml:883 #, 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:875 +#: preseed.xml:892 #, no-c-format msgid "standard" msgstr "" #. Tag: userinput -#: preseed.xml:878 +#: preseed.xml:895 #, no-c-format msgid "desktop" msgstr "" #. Tag: userinput -#: preseed.xml:881 +#: preseed.xml:898 #, no-c-format msgid "gnome-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:884 +#: preseed.xml:901 #, no-c-format msgid "kde-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:887 +#: preseed.xml:904 #, no-c-format msgid "web-server" msgstr "" #. Tag: userinput -#: preseed.xml:890 +#: preseed.xml:907 #, no-c-format msgid "print-server" msgstr "" #. Tag: userinput -#: preseed.xml:893 +#: preseed.xml:910 #, no-c-format msgid "dns-server" msgstr "" #. Tag: userinput -#: preseed.xml:896 +#: preseed.xml:913 #, no-c-format msgid "file-server" msgstr "" #. Tag: userinput -#: preseed.xml:899 +#: preseed.xml:916 #, no-c-format msgid "mail-server" msgstr "" #. Tag: userinput -#: preseed.xml:902 +#: preseed.xml:919 #, no-c-format msgid "sql-database" msgstr "" #. Tag: userinput -#: preseed.xml:905 +#: preseed.xml:922 #, no-c-format msgid "laptop" msgstr "" #. Tag: para -#: preseed.xml:909 +#: preseed.xml:926 #, 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:915 +#: preseed.xml:932 #, 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:925 +#: preseed.xml:942 #, no-c-format msgid "" "tasksel tasksel/first multiselect standard, desktop\n" @@ -1245,13 +1257,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:930 +#: preseed.xml:947 #, no-c-format msgid "Finishing up the first stage install" msgstr "" #. Tag: screen -#: preseed.xml:932 +#: preseed.xml:949 #, no-c-format msgid "" "# Avoid that last message about the install being complete.\n" @@ -1263,19 +1275,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:937 +#: preseed.xml:954 #, no-c-format msgid "Mailer configuration" msgstr "" #. Tag: para -#: preseed.xml:938 +#: preseed.xml:955 #, 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:945 +#: preseed.xml:962 #, no-c-format msgid "" "exim4-config exim4/dc_eximconfig_configtype \\\n" @@ -1286,19 +1298,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:950 +#: preseed.xml:967 #, no-c-format msgid "X configuration" msgstr "" #. Tag: para -#: preseed.xml:951 +#: preseed.xml:968 #, 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:959 +#: preseed.xml:976 #, no-c-format msgid "" "# X can detect the right driver for some cards, but if you're preseeding,\n" @@ -1324,13 +1336,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:964 +#: preseed.xml:981 #, no-c-format msgid "Preseeding other packages" msgstr "" #. Tag: screen -#: preseed.xml:966 +#: preseed.xml:983 #, no-c-format msgid "" "# Depending on what software you choose to install, or if things go wrong\n" @@ -1343,25 +1355,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:973 +#: preseed.xml:990 #, no-c-format msgid "Advanced options" msgstr "" #. Tag: title -#: preseed.xml:976 +#: preseed.xml:993 #, no-c-format msgid "Running custom commands during the installation" msgstr "" #. Tag: para -#: preseed.xml:977 +#: preseed.xml:994 #, 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:985 +#: preseed.xml:1002 #, no-c-format msgid "" "# d-i preseeding is inherently not secure. Nothing in the installer checks\n" @@ -1383,19 +1395,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:990 +#: preseed.xml:1007 #, no-c-format msgid "Using preseeding to change default values" msgstr "" #. Tag: para -#: preseed.xml:991 +#: preseed.xml:1008 #, 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 +#: preseed.xml:1017 #, no-c-format msgid "" "d-i foo/bar string value\n" @@ -1403,19 +1415,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1005 +#: preseed.xml:1022 #, no-c-format msgid "Chainloading preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:1006 +#: preseed.xml:1023 #, 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:1016 +#: preseed.xml:1033 #, no-c-format msgid "" "# More than one file can be listed, separated by spaces; all will be\n" @@ -1442,7 +1454,7 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:1018 +#: preseed.xml:1035 #, 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 "" diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index 1d0406d14..fa976c6ef 100644 --- a/po/pot/using-d-i.pot +++ b/po/pot/using-d-i.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-17 09:33+0000\n" +"POT-Creation-Date: 2006-11-29 17:16+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" @@ -1583,377 +1583,383 @@ msgstr "" #. Tag: para #: using-d-i.xml:1976 #, no-c-format -msgid "The <quote>Desktop environment</quote> task will install the Gnome desktop environment. The options offered by the installer currently do not allow to select a different desktop environment like for example KDE." +msgid "The <quote>Desktop environment</quote> task will install the GNOME desktop environment. The options offered by the installer currently do not allow to select a different desktop environment such as for example KDE." msgstr "" #. Tag: para #: using-d-i.xml:1982 #, no-c-format -msgid "It is however possible to get the installer to install KDE by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding <literal>tasksel/first=kde-desktop</literal> at the boot prompt when starting the installer." +msgid "It is possible to get the installer to install KDE by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding <literal>tasks=\"standard, kde-desktop\"</literal> at the boot prompt when starting the installer. However, this will only work if the packages needed for KDE are actually available. If you are installing using a full CD image, they will need to be downloaded from a mirror as KDE packages are not included on the first full CD; installing KDE this way should work fine if you are using a DVD image or any other installation method." msgstr "" #. Tag: para -#: using-d-i.xml:1990 +#: using-d-i.xml:1993 #, no-c-format -msgid "Once you've selected your tasks, select <guibutton>Ok</guibutton>. At this point, <command>aptitude</command> will install the packages you've selected." +msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL server: <classname>postgresql</classname>; Web server: <classname>apache</classname>." msgstr "" #. Tag: para -#: using-d-i.xml:1998 +#: using-d-i.xml:2005 +#, no-c-format +msgid "Once you've selected your tasks, select <guibutton>Ok</guibutton>. At this point, <command>aptitude</command> will install the packages that are part of the tasks you've selected." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2012 #, no-c-format msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task." msgstr "" #. Tag: para -#: using-d-i.xml:2007 +#: using-d-i.xml:2021 #, no-c-format msgid "Each package you selected with <command>tasksel</command> is downloaded, unpacked and then installed in turn by the <command>apt-get</command> and <command>dpkg</command> programs. If a particular program needs more information from the user, it will prompt you during this process." msgstr "" #. Tag: title -#: using-d-i.xml:2016 +#: using-d-i.xml:2032 #, no-c-format msgid "Configuring Your Mail Transport Agent" msgstr "" #. Tag: para -#: using-d-i.xml:2018 +#: using-d-i.xml:2034 #, no-c-format msgid "Today, email is a very important part of many people's life, so it's no surprise Debian lets you configure your mail system right as a part of the installation process. The standard mail transport agent in Debian is <command>exim4</command>, which is relatively small, flexible, and easy to learn." msgstr "" #. Tag: para -#: using-d-i.xml:2026 +#: using-d-i.xml:2042 #, no-c-format msgid "You may ask if this is needed even if your computer is not connected to any network. The short answer is: Yes. The longer explanation: Some system utilities (like <command>cron</command>, <command>quota</command>, <command>aide</command>, …) may send you important notices via email." msgstr "" #. Tag: para -#: using-d-i.xml:2034 +#: using-d-i.xml:2050 #, no-c-format msgid "So on the first screen you will be presented with several common mail scenarios. Choose the one that most closely resembles your needs:" msgstr "" #. Tag: term -#: using-d-i.xml:2043 +#: using-d-i.xml:2059 #, no-c-format msgid "internet site" msgstr "" #. Tag: para -#: using-d-i.xml:2044 +#: using-d-i.xml:2060 #, no-c-format msgid "Your system is connected to a network and your mail is sent and received directly using SMTP. On the following screens you will be asked a few basic questions, like your machine's mail name, or a list of domains for which you accept or relay mail." msgstr "" #. Tag: term -#: using-d-i.xml:2055 +#: using-d-i.xml:2071 #, no-c-format msgid "mail sent by smarthost" msgstr "" #. Tag: para -#: using-d-i.xml:2056 +#: using-d-i.xml:2072 #, no-c-format msgid "In this scenario is your outgoing mail forwarded to another machine, called a <quote>smarthost</quote>, which does the actual job for you. Smarthost also usually stores incoming mail addressed to your computer, so you don't need to be permanently online. That also means you have to download your mail from the smarthost via programs like fetchmail. This option is suitable for dial-up users." msgstr "" #. Tag: term -#: using-d-i.xml:2069 +#: using-d-i.xml:2085 #, no-c-format msgid "local delivery only" msgstr "" #. Tag: para -#: using-d-i.xml:2070 +#: using-d-i.xml:2086 #, no-c-format msgid "Your system is not on a network and mail is sent or received only between local users. Even if you don't plan to send any messages, this option is highly recommended, because some system utilities may send you various alerts from time to time (e.g. beloved <quote>Disk quota exceeded</quote>). This option is also convenient for new users, because it doesn't ask any further questions." msgstr "" #. Tag: term -#: using-d-i.xml:2083 +#: using-d-i.xml:2099 #, no-c-format msgid "no configuration at this time" msgstr "" #. Tag: para -#: using-d-i.xml:2084 +#: using-d-i.xml:2100 #, no-c-format msgid "Choose this if you are absolutely convinced you know what you are doing. This will leave you with an unconfigured mail system — until you configure it, you won't be able to send or receive any mail and you may miss some important messages from your system utilities." msgstr "" #. Tag: para -#: using-d-i.xml:2095 +#: using-d-i.xml:2111 #, no-c-format msgid "If none of these scenarios suits your needs, or if you need a finer setup, you will need to edit configuration files under the <filename>/etc/exim4</filename> directory after the installation is complete. More information about <command>exim4</command> may be found under <filename>/usr/share/doc/exim4</filename>." msgstr "" #. Tag: title -#: using-d-i.xml:2110 +#: using-d-i.xml:2125 #, no-c-format msgid "Making Your System Bootable" msgstr "" #. Tag: para -#: using-d-i.xml:2112 +#: using-d-i.xml:2127 #, no-c-format msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set the OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>" msgstr "" #. Tag: para -#: using-d-i.xml:2120 +#: using-d-i.xml:2135 #, no-c-format msgid "Note that multiple operating systems booting on a single machine is still something of a black art. This document does not even attempt to document the various boot managers, which vary by architecture and even by subarchitecture. You should see your boot manager's documentation for more information." msgstr "" #. Tag: title -#: using-d-i.xml:2135 +#: using-d-i.xml:2150 #, no-c-format msgid "Detecting other operating systems" msgstr "" #. Tag: para -#: using-d-i.xml:2137 +#: using-d-i.xml:2152 #, no-c-format msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to Debian." msgstr "" #. Tag: para -#: using-d-i.xml:2145 +#: using-d-i.xml:2160 #, no-c-format msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information." msgstr "" #. Tag: title -#: using-d-i.xml:2163 +#: using-d-i.xml:2178 #, no-c-format msgid "Install <command>aboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2164 +#: using-d-i.xml:2179 #, no-c-format msgid "If you have booted from SRM, if you select this option, the installer will write <command>aboot</command> to the first sector of the disk on which you installed Debian. Be <emphasis>very</emphasis> careful — it is <emphasis>not</emphasis> possible to boot multiple operating systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a different operating system installed on the disk where you have installed Debian, you will have to boot GNU/Linux from a floppy instead." msgstr "" #. Tag: title -#: using-d-i.xml:2184 +#: using-d-i.xml:2199 #, no-c-format msgid "<command>palo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2185 +#: using-d-i.xml:2200 #, no-c-format msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions." msgstr "" #. Tag: para -#: using-d-i.xml:2194 +#: using-d-i.xml:2209 #, no-c-format msgid "hppa FIXME ( need more info )" msgstr "" #. Tag: title -#: using-d-i.xml:2206 +#: using-d-i.xml:2221 #, no-c-format msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2208 +#: using-d-i.xml:2223 #, no-c-format msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for newbies and old hands alike." msgstr "" #. Tag: para -#: using-d-i.xml:2214 +#: using-d-i.xml:2229 #, no-c-format msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information." msgstr "" #. Tag: para -#: using-d-i.xml:2220 +#: using-d-i.xml:2235 #, no-c-format msgid "If you do not want to install grub at all, use the Back button to get to the main menu, and from there select whatever bootloader you would like to use." msgstr "" #. Tag: title -#: using-d-i.xml:2234 +#: using-d-i.xml:2249 #, no-c-format msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2236 +#: using-d-i.xml:2251 #, no-c-format msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>." msgstr "" #. Tag: para -#: using-d-i.xml:2246 +#: using-d-i.xml:2261 #, no-c-format msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation." msgstr "" #. Tag: para -#: using-d-i.xml:2254 +#: using-d-i.xml:2269 #, no-c-format msgid "&d-i; presents you three choices where to install the <command>LILO</command> boot loader:" msgstr "" #. Tag: term -#: using-d-i.xml:2261 +#: using-d-i.xml:2276 #, no-c-format msgid "Master Boot Record (MBR)" msgstr "" #. Tag: para -#: using-d-i.xml:2261 +#: using-d-i.xml:2276 #, no-c-format msgid "This way the <command>LILO</command> will take complete control of the boot process." msgstr "" #. Tag: term -#: using-d-i.xml:2268 +#: using-d-i.xml:2283 #, no-c-format msgid "new Debian partition" msgstr "" #. Tag: para -#: using-d-i.xml:2268 +#: using-d-i.xml:2283 #, no-c-format msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new Debian partition and it will serve as a secondary boot loader." msgstr "" #. Tag: term -#: using-d-i.xml:2277 +#: using-d-i.xml:2292 #, no-c-format msgid "Other choice" msgstr "" #. Tag: para -#: using-d-i.xml:2277 +#: using-d-i.xml:2292 #, no-c-format msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use devfs style names, such as those that start with <filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and <filename>/dev/discs</filename>, as well as traditional names, such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>." msgstr "" #. Tag: para -#: using-d-i.xml:2289 +#: using-d-i.xml:2304 #, no-c-format msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record — however, this means that you'll need to use some other way to get back into Debian! For more information on this please read <xref linkend=\"reactivating-win\"/>." msgstr "" #. Tag: title -#: using-d-i.xml:2306 +#: using-d-i.xml:2321 #, no-c-format msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2308 +#: using-d-i.xml:2323 #, no-c-format msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies file into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to actually do the work of loading and starting the Linux kernel." msgstr "" #. Tag: para -#: using-d-i.xml:2324 +#: using-d-i.xml:2339 #, no-c-format msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem." msgstr "" #. Tag: title -#: using-d-i.xml:2336 +#: using-d-i.xml:2351 #, no-c-format msgid "Choose the correct partition!" msgstr "" #. Tag: para -#: using-d-i.xml:2338 +#: using-d-i.xml:2353 #, no-c-format msgid "The criteria for selecting a partition is that it is FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, the <command>elilo</command> may format the partition during the installation, erasing any previous contents!" msgstr "" #. Tag: title -#: using-d-i.xml:2353 +#: using-d-i.xml:2368 #, no-c-format msgid "EFI Partition Contents" msgstr "" #. Tag: para -#: using-d-i.xml:2355 +#: using-d-i.xml:2370 #, no-c-format msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured." msgstr "" #. Tag: filename -#: using-d-i.xml:2377 +#: using-d-i.xml:2392 #, no-c-format msgid "elilo.conf" msgstr "" #. Tag: para -#: using-d-i.xml:2378 +#: using-d-i.xml:2393 #, no-c-format msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition." msgstr "" #. Tag: filename -#: using-d-i.xml:2387 +#: using-d-i.xml:2402 #, no-c-format msgid "elilo.efi" msgstr "" #. Tag: para -#: using-d-i.xml:2388 +#: using-d-i.xml:2403 #, no-c-format msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>Debian GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu." msgstr "" #. Tag: filename -#: using-d-i.xml:2398 +#: using-d-i.xml:2413 #, no-c-format msgid "initrd.img" msgstr "" #. Tag: para -#: using-d-i.xml:2399 +#: using-d-i.xml:2414 #, no-c-format msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>." msgstr "" #. Tag: filename -#: using-d-i.xml:2411 +#: using-d-i.xml:2426 #, no-c-format msgid "readme.txt" msgstr "" #. Tag: para -#: using-d-i.xml:2412 +#: using-d-i.xml:2427 #, no-c-format msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run." msgstr "" #. Tag: filename -#: using-d-i.xml:2422 +#: using-d-i.xml:2437 #, no-c-format msgid "vmlinuz" msgstr "" #. Tag: para -#: using-d-i.xml:2423 +#: using-d-i.xml:2438 #, no-c-format msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>." msgstr "" #. Tag: title -#: using-d-i.xml:2443 +#: using-d-i.xml:2458 #, no-c-format msgid "<command>arcboot</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2444 +#: using-d-i.xml:2459 #, no-c-format msgid "" "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n" @@ -1966,61 +1972,61 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2463 +#: using-d-i.xml:2478 #, no-c-format msgid "scsi" msgstr "" #. Tag: para -#: using-d-i.xml:2464 +#: using-d-i.xml:2479 #, no-c-format msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2472 +#: using-d-i.xml:2487 #, no-c-format msgid "disk" msgstr "" #. Tag: para -#: using-d-i.xml:2473 +#: using-d-i.xml:2488 #, no-c-format msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2481 using-d-i.xml:2550 +#: using-d-i.xml:2496 using-d-i.xml:2565 #, no-c-format msgid "partnr" msgstr "" #. Tag: para -#: using-d-i.xml:2482 +#: using-d-i.xml:2497 #, no-c-format msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2490 +#: using-d-i.xml:2505 #, no-c-format msgid "config" msgstr "" #. Tag: para -#: using-d-i.xml:2491 +#: using-d-i.xml:2506 #, no-c-format msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: title -#: using-d-i.xml:2512 +#: using-d-i.xml:2527 #, no-c-format msgid "<command>delo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2513 +#: using-d-i.xml:2528 #, no-c-format msgid "" "The boot loader on DECstations is <command>DELO</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). DELO supports different configurations which are set up in <filename>/etc/delo.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After DELO has been installed, the system can be booted from hard disk by entering <informalexample><screen>\n" @@ -2029,247 +2035,247 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2532 +#: using-d-i.xml:2547 #, no-c-format msgid "<replaceable>#</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2533 +#: using-d-i.xml:2548 #, no-c-format msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2541 +#: using-d-i.xml:2556 #, no-c-format msgid "<replaceable>id</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2542 +#: using-d-i.xml:2557 #, no-c-format msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed" msgstr "" #. Tag: para -#: using-d-i.xml:2551 +#: using-d-i.xml:2566 #, no-c-format msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2559 +#: using-d-i.xml:2574 #, no-c-format msgid "name" msgstr "" #. Tag: para -#: using-d-i.xml:2560 +#: using-d-i.xml:2575 #, no-c-format msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: para -#: using-d-i.xml:2570 +#: using-d-i.xml:2585 #, no-c-format msgid "In case <filename>/etc/delo.conf</filename> is on the first partition on the disk and the default configuration shall be booted, it is sufficient to use" msgstr "" #. Tag: screen -#: using-d-i.xml:2576 +#: using-d-i.xml:2591 #, no-c-format msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>" msgstr "" #. Tag: title -#: using-d-i.xml:2586 +#: using-d-i.xml:2601 #, no-c-format msgid "Install <command>Yaboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2587 +#: using-d-i.xml:2602 #, no-c-format msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian;." msgstr "" #. Tag: title -#: using-d-i.xml:2605 +#: using-d-i.xml:2620 #, no-c-format msgid "Install <command>Quik</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2606 +#: using-d-i.xml:2621 #, no-c-format msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones." msgstr "" #. Tag: title -#: using-d-i.xml:2622 +#: using-d-i.xml:2637 #, no-c-format msgid "<command>zipl</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2623 +#: using-d-i.xml:2638 #, no-c-format msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>." msgstr "" #. Tag: title -#: using-d-i.xml:2640 +#: using-d-i.xml:2655 #, no-c-format msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2642 +#: using-d-i.xml:2657 #, no-c-format msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install." msgstr "" #. Tag: title -#: using-d-i.xml:2667 +#: using-d-i.xml:2682 #, no-c-format msgid "Continue Without Boot Loader" msgstr "" #. Tag: para -#: using-d-i.xml:2669 +#: using-d-i.xml:2684 #, no-c-format msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader). <phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, and Amiga systems, where the original operating system must be maintained on the box and used to boot GNU/Linux.</phrase>" msgstr "" #. Tag: para -#: using-d-i.xml:2678 +#: using-d-i.xml:2693 #, no-c-format msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem." msgstr "" #. Tag: title -#: using-d-i.xml:2695 +#: using-d-i.xml:2710 #, no-c-format msgid "Finishing the Installation" msgstr "" #. Tag: para -#: using-d-i.xml:2696 +#: using-d-i.xml:2711 #, no-c-format msgid "These are the last bits to do before rebooting to your new system. It mostly consists of tidying up after the &d-i;." msgstr "" #. Tag: title -#: using-d-i.xml:2708 +#: using-d-i.xml:2723 #, no-c-format msgid "Finish the Installation and Reboot" msgstr "" #. Tag: para -#: using-d-i.xml:2710 +#: using-d-i.xml:2725 #, no-c-format msgid "This is the last step in the initial Debian installation process. You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. The installer will do any last minute tasks, and then reboot into your new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2717 +#: using-d-i.xml:2732 #, no-c-format msgid "Select the <guimenuitem>Finish the installation</guimenuitem> menu item which will halt the system because rebooting is not supported on &arch-title; in this case. You then need to IPL GNU/Linux from the DASD which you selected for the root filesystem during the first steps of the installation." msgstr "" #. Tag: title -#: using-d-i.xml:2731 +#: using-d-i.xml:2746 #, no-c-format msgid "Miscellaneous" msgstr "" #. Tag: para -#: using-d-i.xml:2732 +#: using-d-i.xml:2747 #, no-c-format msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong." msgstr "" #. Tag: title -#: using-d-i.xml:2745 +#: using-d-i.xml:2760 #, no-c-format msgid "Saving the installation logs" msgstr "" #. Tag: para -#: using-d-i.xml:2747 +#: using-d-i.xml:2762 #, no-c-format msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2754 +#: using-d-i.xml:2769 #, no-c-format msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report." msgstr "" #. Tag: title -#: using-d-i.xml:2774 +#: using-d-i.xml:2789 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "" #. Tag: para -#: using-d-i.xml:2777 +#: using-d-i.xml:2792 #, no-c-format msgid "There is an <guimenuitem>Execute a Shell</guimenuitem> item on the menu. If the menu is not available when you need to use the shell, press <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap> </keycombo>) to switch to the second <emphasis>virtual console</emphasis>. That's the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap>, and the <keycap>F2</keycap> function key, at the same time. This is a separate window running a Bourne shell clone called <command>ash</command>." msgstr "" #. Tag: para -#: using-d-i.xml:2789 +#: using-d-i.xml:2804 #, no-c-format msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The text editor is <command>nano</command>. The shell has some nice features like autocompletion and history." msgstr "" #. Tag: para -#: using-d-i.xml:2798 +#: using-d-i.xml:2813 #, no-c-format msgid "Use the menus to perform any task that they are able to do — the shell and commands are only there in case something goes wrong. In particular, you should always use the menus, not the shell, to activate your swap partition, because the menu software can't detect that you've done this from the shell. Press <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to get back to menus, or type <command>exit</command> if you used a menu item to open the shell." msgstr "" #. Tag: title -#: using-d-i.xml:2817 +#: using-d-i.xml:2832 #, no-c-format msgid "Installation Over the Network" msgstr "" #. Tag: para -#: using-d-i.xml:2819 +#: using-d-i.xml:2834 #, no-c-format msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)" msgstr "" #. Tag: para -#: using-d-i.xml:2829 +#: using-d-i.xml:2844 #, no-c-format msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>." msgstr "" #. Tag: para -#: using-d-i.xml:2842 +#: using-d-i.xml:2857 #, no-c-format msgid "For installations on &arch-title;, this is the default method after setting up the network." msgstr "" #. Tag: para -#: using-d-i.xml:2847 +#: using-d-i.xml:2862 #, no-c-format msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the <quote>person who will continue the installation remotely</quote>." msgstr "" #. Tag: para -#: using-d-i.xml:2859 +#: using-d-i.xml:2874 #, no-c-format msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component." msgstr "" #. Tag: para -#: using-d-i.xml:2865 +#: using-d-i.xml:2880 #, no-c-format msgid "" "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n" @@ -2278,25 +2284,25 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:2882 +#: using-d-i.xml:2897 #, no-c-format msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename> and try again." msgstr "" #. Tag: para -#: using-d-i.xml:2891 +#: using-d-i.xml:2906 #, no-c-format msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells." msgstr "" #. Tag: para -#: using-d-i.xml:2901 +#: using-d-i.xml:2916 #, no-c-format msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system." msgstr "" #. Tag: para -#: using-d-i.xml:2909 +#: using-d-i.xml:2924 #, no-c-format msgid "Also, if you are running the SSH session from an X terminal, you should not resize the window as that will result in the connection being terminated." msgstr "" |