diff options
| author | Frans Pop <elendil@planet.nl> | 2006-12-29 19:36:52 +0000 |
|---|---|---|
| committer | Frans Pop <elendil@planet.nl> | 2006-12-29 19:36:52 +0000 |
| commit | 39193e1e56af8d7856801221cdbb1ae431e347cc (patch) | |
| tree | 282b6c95630d9f69ae2da3bd99f1c3ef3862f42d /po/pot | |
| parent | c8fc73c10d721db52054f9dbe173a512636a400e (diff) | |
| download | installation-guide-39193e1e56af8d7856801221cdbb1ae431e347cc.zip | |
[SILENT_COMMIT] Update of POT and PO files for the manual
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 312 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 84 | ||||
| -rw-r--r-- | po/pot/preparing.pot | 6 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 240 | ||||
| -rw-r--r-- | po/pot/random-bits.pot | 4 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 534 |
6 files changed, 581 insertions, 599 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 1ff1b0700..2ecfab06c 100644 --- a/po/pot/boot-installer.pot +++ b/po/pot/boot-installer.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-29 10:24+0000\n" +"POT-Creation-Date: 2006-12-29 19:35+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" @@ -1837,386 +1837,404 @@ msgstr "" msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful." msgstr "" +#. Tag: para +#: boot-installer.xml:2819 +#, no-c-format +msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too." +msgstr "" + #. Tag: term -#: boot-installer.xml:2823 +#: boot-installer.xml:2831 #, no-c-format -msgid "debconf/priority" +msgid "debconf/priority (priority)" msgstr "" #. Tag: para -#: boot-installer.xml:2824 +#: boot-installer.xml:2832 #, no-c-format -msgid "This parameter sets the lowest priority of messages to be displayed. Short form: <userinput>priority</userinput>." +msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" #. Tag: para -#: boot-installer.xml:2829 +#: boot-installer.xml:2836 #, no-c-format msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed." msgstr "" #. Tag: para -#: boot-installer.xml:2836 +#: boot-installer.xml:2843 #, no-c-format msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss." msgstr "" #. Tag: term -#: boot-installer.xml:2850 +#: boot-installer.xml:2857 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para -#: boot-installer.xml:2851 +#: boot-installer.xml:2858 #, 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=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:2880 +#: boot-installer.xml:2887 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:2881 +#: boot-installer.xml:2888 #, 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:2890 +#: boot-installer.xml:2897 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:2891 +#: boot-installer.xml:2898 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:2895 +#: boot-installer.xml:2902 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:2896 +#: boot-installer.xml:2903 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:2900 +#: boot-installer.xml:2907 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:2901 +#: boot-installer.xml:2908 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:2905 +#: boot-installer.xml:2912 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:2906 +#: boot-installer.xml:2913 #, 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:2920 +#: boot-installer.xml:2927 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:2921 +#: boot-installer.xml:2928 #, 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:2927 +#: boot-installer.xml:2934 #, 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:2937 +#: boot-installer.xml:2944 #, no-c-format msgid "debian-installer/framebuffer" msgstr "" #. Tag: para -#: boot-installer.xml:2938 +#: boot-installer.xml:2945 #, 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:2948 +#: boot-installer.xml:2955 #, 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:2954 +#: boot-installer.xml:2961 #, no-c-format msgid "Such problems have been reported on the Amiga 1200 and SE/30." msgstr "" #. Tag: para -#: boot-installer.xml:2958 +#: boot-installer.xml:2965 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:2962 +#: boot-installer.xml:2969 #, 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:2976 +#: boot-installer.xml:2983 #, no-c-format -msgid "debian-installer/theme" +msgid "debian-installer/theme (theme)" msgstr "" #. Tag: para -#: boot-installer.xml:2977 +#: boot-installer.xml:2984 #, 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>." +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 <userinput>theme=<replaceable>dark</replaceable></userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:2990 +#: boot-installer.xml:2996 #, no-c-format msgid "debian-installer/probe/usb" msgstr "" #. Tag: para -#: boot-installer.xml:2991 +#: boot-installer.xml:2997 #, 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:3000 boot-installer.xml:3167 +#: boot-installer.xml:3006 boot-installer.xml:3170 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" #. Tag: para -#: boot-installer.xml:3001 +#: boot-installer.xml:3007 #, 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:3008 +#: boot-installer.xml:3014 #, 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:3019 +#: boot-installer.xml:3025 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:3020 +#: boot-installer.xml:3026 #, 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:3030 +#: boot-installer.xml:3036 #, no-c-format -msgid "preseed/url" +msgid "preseed/url (url)" msgstr "" #. Tag: para -#: boot-installer.xml:3031 +#: boot-installer.xml:3037 #, 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\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:3041 +#: boot-installer.xml:3046 #, no-c-format -msgid "preseed/file" +msgid "preseed/file (file)" msgstr "" #. Tag: para -#: boot-installer.xml:3042 +#: boot-installer.xml:3047 #, 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\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:3052 +#: boot-installer.xml:3056 #, no-c-format -msgid "auto-install/enabled" +msgid "auto-install/enabled (auto)" msgstr "" #. Tag: para -#: boot-installer.xml:3053 +#: boot-installer.xml:3057 #, 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." +msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs." msgstr "" #. Tag: term -#: boot-installer.xml:3064 +#: boot-installer.xml:3068 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:3065 +#: boot-installer.xml:3069 #, 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:3074 +#: boot-installer.xml:3078 #, 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:3085 +#: boot-installer.xml:3089 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:3086 +#: boot-installer.xml:3090 #, 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:3094 +#: boot-installer.xml:3098 #, no-c-format msgid "mouse/left" msgstr "" #. Tag: para -#: boot-installer.xml:3095 +#: boot-installer.xml:3099 #, 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:3104 +#: boot-installer.xml:3108 #, no-c-format msgid "directfb/hw-accel" msgstr "" #. Tag: para -#: boot-installer.xml:3105 +#: boot-installer.xml:3109 #, 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:3115 +#: boot-installer.xml:3119 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:3116 +#: boot-installer.xml:3120 #, 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:3127 +#: boot-installer.xml:3131 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para -#: boot-installer.xml:3128 +#: boot-installer.xml:3132 #, 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 +#: boot-installer.xml:3144 #, no-c-format -msgid "debian-installer/locale" +msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:3141 +#: boot-installer.xml:3145 #, 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 Switzerland as country." +msgid "Can be used to set both the language and country for the installation. This will only work if the locale is supported in Debian. For example, use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country." msgstr "" #. Tag: term -#: boot-installer.xml:3153 +#: boot-installer.xml:3156 #, no-c-format -msgid "anna/choose_modules" +msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:3154 +#: boot-installer.xml:3157 #, no-c-format -msgid "Can be used to automatically load installer components that are not loaded by default. Short form: <userinput>modules</userinput>. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation) and <classname>ppp-udeb</classname> (which supports PPPoE configuration)." +msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation) and <classname>ppp-udeb</classname> (which supports PPPoE configuration)." msgstr "" #. Tag: para -#: boot-installer.xml:3168 +#: boot-installer.xml:3171 #, 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:3177 +#: boot-installer.xml:3180 #, no-c-format -msgid "tasksel:tasksel/first" +msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:3178 +#: boot-installer.xml:3181 #, 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>." +msgid "By default the installer will use the http protocol to download files from Debian mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3194 +#, no-c-format +msgid "tasksel:tasksel/first (tasks)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3195 +#, no-c-format +msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information." msgstr "" #. Tag: title -#: boot-installer.xml:3192 +#: boot-installer.xml:3208 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:3193 +#: boot-installer.xml:3209 #, 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:3206 +#: boot-installer.xml:3222 #, 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:3213 +#: boot-installer.xml:3229 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -2225,109 +2243,109 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3223 +#: boot-installer.xml:3239 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:3235 +#: boot-installer.xml:3251 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:3240 +#: boot-installer.xml:3256 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3241 +#: boot-installer.xml:3257 #, 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:3248 +#: boot-installer.xml:3264 #, 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:3254 +#: boot-installer.xml:3270 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:3259 +#: boot-installer.xml:3275 #, 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:3265 +#: boot-installer.xml:3281 #, no-c-format msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with older CD-ROM drives are known to be resolved in this way." msgstr "" #. Tag: para -#: boot-installer.xml:3275 +#: boot-installer.xml:3291 #, 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:3281 +#: boot-installer.xml:3297 #, 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:3289 +#: boot-installer.xml:3305 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:3292 +#: boot-installer.xml:3308 #, 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:3298 +#: boot-installer.xml:3314 #, 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:3305 +#: boot-installer.xml:3321 #, 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:3316 +#: boot-installer.xml:3332 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:3317 +#: boot-installer.xml:3333 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:3322 +#: boot-installer.xml:3338 #, 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:3328 +#: boot-installer.xml:3344 #, 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" @@ -2337,7 +2355,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3341 +#: boot-installer.xml:3357 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -2350,19 +2368,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3346 +#: boot-installer.xml:3362 #, 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:3358 +#: boot-installer.xml:3374 #, 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:3365 +#: boot-installer.xml:3381 #, 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" @@ -2375,13 +2393,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3379 +#: boot-installer.xml:3395 #, 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:3387 +#: boot-installer.xml:3403 #, 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" @@ -2390,7 +2408,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3397 +#: boot-installer.xml:3413 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -2403,163 +2421,163 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3412 +#: boot-installer.xml:3428 #, 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:3427 +#: boot-installer.xml:3443 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3429 +#: boot-installer.xml:3445 #, 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:3434 +#: boot-installer.xml:3450 #, 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:3443 +#: boot-installer.xml:3459 #, 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:3452 +#: boot-installer.xml:3468 #, 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:3458 +#: boot-installer.xml:3474 #, 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:3464 +#: boot-installer.xml:3480 #, 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:3473 +#: boot-installer.xml:3489 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:3475 +#: boot-installer.xml:3491 #, 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:3482 +#: boot-installer.xml:3498 #, 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:3489 +#: boot-installer.xml:3505 #, 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:3495 +#: boot-installer.xml:3511 #, 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:3506 boot-installer.xml:3591 +#: boot-installer.xml:3522 boot-installer.xml:3607 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3507 +#: boot-installer.xml:3523 #, 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:3512 +#: boot-installer.xml:3528 #, 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:3518 +#: boot-installer.xml:3534 #, 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:3527 +#: boot-installer.xml:3543 #, 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:3534 +#: boot-installer.xml:3550 #, 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:3548 +#: boot-installer.xml:3564 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:3549 +#: boot-installer.xml:3565 #, 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:3559 +#: boot-installer.xml:3575 #, 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:3576 +#: boot-installer.xml:3592 #, no-c-format msgid "System Freeze while Loading USB Modules" msgstr "" #. Tag: para -#: boot-installer.xml:3577 +#: boot-installer.xml:3593 #, 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: para -#: boot-installer.xml:3592 +#: boot-installer.xml:3608 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:3598 +#: boot-installer.xml:3614 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:3599 +#: boot-installer.xml:3615 #, no-c-format msgid "" "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n" @@ -2569,85 +2587,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3613 +#: boot-installer.xml:3629 #, no-c-format msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>." msgstr "" #. Tag: title -#: boot-installer.xml:3624 +#: boot-installer.xml:3640 #, no-c-format msgid "Failure to Boot or Kernel from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3625 +#: boot-installer.xml:3641 #, no-c-format msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems." msgstr "" #. Tag: para -#: boot-installer.xml:3631 +#: boot-installer.xml:3647 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3640 +#: boot-installer.xml:3656 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3642 +#: boot-installer.xml:3658 #, 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:3667 +#: boot-installer.xml:3683 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3668 +#: boot-installer.xml:3684 #, no-c-format msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report you may want to attach this information to the bug report." msgstr "" #. Tag: para -#: boot-installer.xml:3679 +#: boot-installer.xml:3695 #, 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:3690 +#: boot-installer.xml:3706 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3691 +#: boot-installer.xml:3707 #, 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:3698 +#: boot-installer.xml:3714 #, no-c-format msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an E-Mail address that you do not mind being made public." msgstr "" #. Tag: para -#: boot-installer.xml:3704 +#: boot-installer.xml:3720 #, no-c-format msgid "If you have a working Debian system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-report</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3714 +#: boot-installer.xml:3730 #, no-c-format msgid "" "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n" diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index cf394da5b..d833e3fd2 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-29 10:24+0000\n" +"POT-Creation-Date: 2006-12-29 19:35+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" @@ -3158,149 +3158,101 @@ msgstr "" #. Tag: para #: hardware.xml:2489 #, no-c-format -msgid "The following network interface cards are supported directly by the installation images for Netwinder and CATS machines:" +msgid "##TODO## Something about NLSU needed." msgstr "" #. Tag: para -#: hardware.xml:2495 -#, no-c-format -msgid "PCI-based NE2000" -msgstr "" - -#. Tag: para -#: hardware.xml:2500 -#, no-c-format -msgid "DECchip Tulip" -msgstr "" - -#. Tag: para -#: hardware.xml:2507 -#, no-c-format -msgid "The following network interface cards are supported directly by the installation images for RiscPCs:" -msgstr "" - -#. Tag: para -#: hardware.xml:2513 -#, no-c-format -msgid "Ether1" -msgstr "" - -#. Tag: para -#: hardware.xml:2518 -#, no-c-format -msgid "Ether3" -msgstr "" - -#. Tag: para -#: hardware.xml:2523 -#, no-c-format -msgid "EtherH" -msgstr "" - -#. Tag: para -#: hardware.xml:2530 -#, no-c-format -msgid "If your card is mentioned in the lists above, the complete installation can be carried out from the network with no need for CD-ROMs or floppy disks." -msgstr "" - -#. Tag: para -#: hardware.xml:2536 -#, no-c-format -msgid "Any other network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module; this means that you will have to install the operating system kernel and modules using some other media." -msgstr "" - -#. Tag: para -#: hardware.xml:2543 +#: hardware.xml:2493 #, no-c-format msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;. Using ISDN during the installation is not supported." msgstr "" #. Tag: title -#: hardware.xml:2552 +#: hardware.xml:2502 #, no-c-format msgid "Drivers Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:2553 +#: hardware.xml:2503 #, no-c-format msgid "The installation system currently does not support retrieving firmware. This means that any network cards that use a driver that requires firmware to be loaded, is not supported by default." msgstr "" #. Tag: para -#: hardware.xml:2559 +#: hardware.xml:2509 #, no-c-format msgid "If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually. Note that the firmware may be packaged separately from the driver and may not be available in the <quote>main</quote> section of the &debian; archive." msgstr "" #. Tag: para -#: hardware.xml:2570 +#: hardware.xml:2520 #, no-c-format msgid "If the driver itself <emphasis>is</emphasis> supported, you may also be able to use the NIC during installation by copying the firmware from some medium to <filename>/usr/lib/hotplug/firmware</filename>. Don't forget to also copy the firmware to that location for the installed system before the reboot at the end of the installation." msgstr "" #. Tag: title -#: hardware.xml:2582 +#: hardware.xml:2532 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:2583 +#: hardware.xml:2533 #, no-c-format msgid "Wireless NICs are in general supported as well, with one big proviso. A lot of wireless adapters require drivers that are either non-free or have not been accepted into the official Linux kernel. These NICs can generally be made to work under &debian;, but are not supported during the installation." msgstr "" #. Tag: para -#: hardware.xml:2590 +#: hardware.xml:2540 #, no-c-format msgid "If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Use the same procedure as described above for NICs that require firmware." msgstr "" #. Tag: para -#: hardware.xml:2596 +#: hardware.xml:2546 #, no-c-format msgid "In some cases the driver you need may not be available as a Debian package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>" msgstr "" #. Tag: title -#: hardware.xml:2610 +#: hardware.xml:2560 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:2611 +#: hardware.xml:2561 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:2618 +#: hardware.xml:2568 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:2620 +#: hardware.xml:2570 #, no-c-format msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly." msgstr "" #. Tag: para -#: hardware.xml:2630 +#: hardware.xml:2580 #, no-c-format msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. During the installation the solution is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>." msgstr "" #. Tag: title -#: hardware.xml:2645 +#: hardware.xml:2595 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:2647 +#: hardware.xml:2597 #, no-c-format msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." msgstr "" diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot index 677802b3c..673e34aae 100644 --- a/po/pot/preparing.pot +++ b/po/pot/preparing.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-29 10:24+0000\n" +"POT-Creation-Date: 2006-12-29 19:35+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" @@ -1739,7 +1739,7 @@ msgstr "" #. Tag: para #: preparing.xml:1965 #, no-c-format -msgid "Before you actually perform an installation, you have to go over some design and preparation steps. IBM has made documentation available about the whole process, e.g. how to prepare an installation medium and how actually to boot from that medium. Duplicating that information here is neither possible nor necessary. However, we will describe here which kind of Debian-specific data is needed and where to find it. Using both sources of information you have to prepare your machine and the installation medium do you can perform a boot from it. When you see the welcome message in your client session, return to this document to go through the Debian-specific installation steps." +msgid "Before you actually perform an installation, you have to go over some design and preparation steps. IBM has made documentation available about the whole process, e.g. how to prepare an installation medium and how actually to boot from that medium. Duplicating that information here is neither possible nor necessary. However, we will describe here which kind of Debian-specific data is needed and where to find it. Using both sources of information, you have to prepare your machine and the installation medium before you can perform a boot from it. When you see the welcome message in your client session, return to this document to go through the Debian-specific installation steps." msgstr "" #. Tag: title @@ -1907,6 +1907,6 @@ msgstr "" #. Tag: para #: preparing.xml:2164 #, no-c-format -msgid "Some OldWorld Powermacs, most notably those with the <quote>control</quote> display driver, may not reliable produce a colormap under Linux when the display is configured for more than 256 colors. If you are experiencing such issues with your display after rebooting (you can sometimes see data on the monitor, but on other occasions cannot see anything) or, if the screen turns black after booting the installer instead of showing you the user interface, try changing your display settings under MacOS to use 256 colors instead of <quote>thousands</quote> or <quote>millions</quote>." +msgid "Some OldWorld Powermacs, most notably those with the <quote>control</quote> display driver, may not reliably produce a colormap under Linux when the display is configured for more than 256 colors. If you are experiencing such issues with your display after rebooting (you can sometimes see data on the monitor, but on other occasions cannot see anything) or, if the screen turns black after booting the installer instead of showing you the user interface, try changing your display settings under MacOS to use 256 colors instead of <quote>thousands</quote> or <quote>millions</quote>." msgstr "" diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot index bb92af6df..59e462442 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-12-27 04:04+0000\n" +"POT-Creation-Date: 2006-12-29 19:35+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:632 +#: preseed.xml:23 preseed.xml:633 #, no-c-format msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;." msgstr "" @@ -465,65 +465,77 @@ msgstr "" #. Tag: entry #: preseed.xml:491 #, no-c-format -msgid "hostname " +msgid "interface" msgstr "" #. Tag: entry #: preseed.xml:491 #, no-c-format -msgid "netcfg/get_hostname" +msgid "netcfg/choose_interface" msgstr "" #. Tag: entry #: preseed.xml:492 #, no-c-format -msgid "domain" +msgid "hostname " msgstr "" #. Tag: entry #: preseed.xml:492 #, no-c-format -msgid "netcfg/get_domain" +msgid "netcfg/get_hostname" msgstr "" #. Tag: entry #: preseed.xml:493 #, no-c-format -msgid "interface" +msgid "domain" msgstr "" #. Tag: entry #: preseed.xml:493 #, no-c-format -msgid "netcfg/choose_interface" +msgid "netcfg/get_domain" msgstr "" #. Tag: entry #: preseed.xml:494 #, no-c-format -msgid "suite" +msgid "protocol" msgstr "" #. Tag: entry #: preseed.xml:494 #, no-c-format +msgid "mirror/protocol" +msgstr "" + +#. Tag: entry +#: preseed.xml:495 +#, no-c-format +msgid "suite" +msgstr "" + +#. Tag: entry +#: preseed.xml:495 +#, no-c-format msgid "mirror/suite" msgstr "" #. Tag: title -#: preseed.xml:501 +#: preseed.xml:502 #, no-c-format msgid "Using a DHCP server to specify preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:502 +#: preseed.xml:503 #, 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:513 +#: preseed.xml:514 #, no-c-format msgid "" "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n" @@ -532,79 +544,79 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:515 +#: preseed.xml:516 #, 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:522 +#: preseed.xml:523 #, 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:536 +#: preseed.xml:537 #, no-c-format msgid "Creating a preconfiguration file" msgstr "" #. Tag: para -#: preseed.xml:537 +#: preseed.xml:538 #, 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:543 +#: preseed.xml:544 #, no-c-format msgid "<owner> <question name> <question type> <value>" msgstr "" #. Tag: para -#: preseed.xml:545 +#: preseed.xml:546 #, no-c-format msgid "There are a few rules to keep in mind when writing a preconfiguration file." msgstr "" #. Tag: para -#: preseed.xml:552 +#: preseed.xml:553 #, 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:556 +#: preseed.xml:557 #, 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:562 +#: preseed.xml:563 #, 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:568 +#: preseed.xml:569 #, 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:574 +#: preseed.xml:575 #, 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:579 +#: preseed.xml:580 #, 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:586 +#: preseed.xml:587 #, no-c-format msgid "" "$ debconf-get-selections --installer > <replaceable>file</replaceable>\n" @@ -612,67 +624,67 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:588 +#: preseed.xml:589 #, 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:596 +#: preseed.xml:597 #, 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:604 +#: preseed.xml:605 #, 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:612 +#: preseed.xml:613 #, 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:620 +#: preseed.xml:621 #, 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:631 +#: preseed.xml:632 #, no-c-format msgid "Contents of the preconfiguration file" msgstr "" #. Tag: para -#: preseed.xml:637 +#: preseed.xml:638 #, 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:648 +#: preseed.xml:649 #, no-c-format msgid "Localization" msgstr "" #. Tag: para -#: preseed.xml:649 +#: preseed.xml:650 #, 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:655 +#: preseed.xml:656 #, 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:661 +#: preseed.xml:662 #, no-c-format msgid "" "# Locale sets language and country.\n" @@ -680,13 +692,13 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:663 +#: preseed.xml:664 #, 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:670 +#: preseed.xml:671 #, no-c-format msgid "" "# Keyboard selection.\n" @@ -697,43 +709,43 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:672 +#: preseed.xml:673 #, 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:681 +#: preseed.xml:682 #, 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:691 +#: preseed.xml:692 #, no-c-format msgid "Network configuration" msgstr "" #. Tag: para -#: preseed.xml:692 +#: preseed.xml:693 #, 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:700 +#: preseed.xml:701 #, 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:706 +#: preseed.xml:707 #, 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:716 +#: preseed.xml:717 #, no-c-format msgid "" "killall.sh dhclient\n" @@ -741,7 +753,7 @@ msgid "" msgstr "" #. Tag: screen -#: preseed.xml:720 +#: preseed.xml:721 #, no-c-format msgid "" "# netcfg will choose an interface that has link if possible. This makes it\n" @@ -785,31 +797,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:725 +#: preseed.xml:726 #, no-c-format msgid "Mirror settings" msgstr "" #. Tag: para -#: preseed.xml:726 +#: preseed.xml:727 #, no-c-format msgid "Depending on the installation method you use, a mirror may be used to download additional components of the installer, to install the base system, and to set up the <filename>/etc/apt/sources.list</filename> for the installed system." msgstr "" #. Tag: para -#: preseed.xml:733 +#: preseed.xml:734 #, no-c-format msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system." msgstr "" #. Tag: para -#: preseed.xml:738 +#: preseed.xml:739 #, 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:750 +#: preseed.xml:751 #, no-c-format msgid "" "d-i mirror/country string enter information manually\n" @@ -824,25 +836,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:755 +#: preseed.xml:756 #, no-c-format msgid "Partitioning" msgstr "" #. Tag: para -#: preseed.xml:756 +#: preseed.xml:757 #, no-c-format msgid "Using preseeding to partition the harddisk is very much limited to what is supported by <classname>partman-auto</classname>. You can choose to partition either existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file. It is currently not possible to partition multiple disks using preseeding." msgstr "" #. Tag: para -#: preseed.xml:767 +#: preseed.xml:768 #, 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:775 +#: preseed.xml:776 #, no-c-format msgid "" "# If the system has free space you can choose to only partition that space.\n" @@ -908,31 +920,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:780 +#: preseed.xml:781 #, no-c-format msgid "Partitioning using RAID" msgstr "" #. Tag: para -#: preseed.xml:781 +#: preseed.xml:782 #, 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:791 +#: preseed.xml:792 #, 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:799 +#: preseed.xml:800 #, 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:807 +#: preseed.xml:808 #, no-c-format msgid "" "# NOTE: this option is of beta release quality and should be used carefully\n" @@ -983,13 +995,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:812 +#: preseed.xml:813 #, no-c-format msgid "Clock and time zone setup" msgstr "" #. Tag: screen -#: preseed.xml:814 +#: preseed.xml:815 #, no-c-format msgid "" "# Controls whether or not the hardware clock is set to UTC.\n" @@ -1001,19 +1013,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:819 +#: preseed.xml:820 #, no-c-format msgid "Apt setup" msgstr "" #. Tag: para -#: preseed.xml:820 +#: preseed.xml:821 #, 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:828 +#: preseed.xml:829 #, no-c-format msgid "" "# You can choose to install non-free and contrib software.\n" @@ -1036,25 +1048,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:833 +#: preseed.xml:834 #, no-c-format msgid "Account setup" msgstr "" #. Tag: para -#: preseed.xml:834 +#: preseed.xml:835 #, 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:841 +#: preseed.xml:842 #, 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:851 +#: preseed.xml:852 #, no-c-format msgid "" "# Skip creation of a root account (normal user account will be able to\n" @@ -1080,37 +1092,37 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:853 +#: preseed.xml:854 #, 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:863 +#: preseed.xml:864 #, no-c-format msgid "An MD5 hash for a password can be generated using the following command." msgstr "" #. Tag: screen -#: preseed.xml:867 +#: preseed.xml:868 #, no-c-format msgid "$ echo \"r00tme\" | mkpasswd -s -H MD5" msgstr "" #. Tag: title -#: preseed.xml:873 +#: preseed.xml:874 #, no-c-format msgid "Base system installation" msgstr "" #. Tag: para -#: preseed.xml:874 +#: preseed.xml:875 #, 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:881 +#: preseed.xml:882 #, no-c-format msgid "" "# Select the initramfs generator used to generate the initrd for 2.6 kernels.\n" @@ -1118,13 +1130,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:886 +#: preseed.xml:887 #, no-c-format msgid "Boot loader installation" msgstr "" #. Tag: screen -#: preseed.xml:888 +#: preseed.xml:889 #, no-c-format msgid "" "# Grub is the default boot loader (for x86). If you want lilo installed\n" @@ -1149,97 +1161,97 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:893 +#: preseed.xml:894 #, no-c-format msgid "Package selection" msgstr "" #. Tag: para -#: preseed.xml:894 +#: preseed.xml:895 #, 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:903 +#: preseed.xml:904 #, no-c-format msgid "standard" msgstr "" #. Tag: userinput -#: preseed.xml:906 +#: preseed.xml:907 #, no-c-format msgid "desktop" msgstr "" #. Tag: userinput -#: preseed.xml:909 +#: preseed.xml:910 #, no-c-format msgid "gnome-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:912 +#: preseed.xml:913 #, no-c-format msgid "kde-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:915 +#: preseed.xml:916 #, no-c-format msgid "web-server" msgstr "" #. Tag: userinput -#: preseed.xml:918 +#: preseed.xml:919 #, no-c-format msgid "print-server" msgstr "" #. Tag: userinput -#: preseed.xml:921 +#: preseed.xml:922 #, no-c-format msgid "dns-server" msgstr "" #. Tag: userinput -#: preseed.xml:924 +#: preseed.xml:925 #, no-c-format msgid "file-server" msgstr "" #. Tag: userinput -#: preseed.xml:927 +#: preseed.xml:928 #, no-c-format msgid "mail-server" msgstr "" #. Tag: userinput -#: preseed.xml:930 +#: preseed.xml:931 #, no-c-format msgid "sql-database" msgstr "" #. Tag: userinput -#: preseed.xml:933 +#: preseed.xml:934 #, no-c-format msgid "laptop" msgstr "" #. Tag: para -#: preseed.xml:937 +#: preseed.xml:938 #, 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:943 +#: preseed.xml:944 #, no-c-format msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well." msgstr "" #. Tag: screen -#: preseed.xml:953 +#: preseed.xml:954 #, no-c-format msgid "" "tasksel tasksel/first multiselect standard, desktop\n" @@ -1257,13 +1269,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:958 +#: preseed.xml:959 #, no-c-format msgid "Finishing up the first stage install" msgstr "" #. Tag: screen -#: preseed.xml:960 +#: preseed.xml:961 #, no-c-format msgid "" "# Avoid that last message about the install being complete.\n" @@ -1275,19 +1287,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:965 +#: preseed.xml:966 #, no-c-format msgid "Mailer configuration" msgstr "" #. Tag: para -#: preseed.xml:966 +#: preseed.xml:967 #, 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:973 +#: preseed.xml:974 #, no-c-format msgid "" "exim4-config exim4/dc_eximconfig_configtype \\\n" @@ -1298,19 +1310,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:978 +#: preseed.xml:979 #, no-c-format msgid "X configuration" msgstr "" #. Tag: para -#: preseed.xml:979 +#: preseed.xml:980 #, 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:987 +#: preseed.xml:988 #, no-c-format msgid "" "# X can detect the right driver for some cards, but if you're preseeding,\n" @@ -1336,13 +1348,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:992 +#: preseed.xml:993 #, no-c-format msgid "Preseeding other packages" msgstr "" #. Tag: screen -#: preseed.xml:994 +#: preseed.xml:995 #, no-c-format msgid "" "# Depending on what software you choose to install, or if things go wrong\n" @@ -1355,25 +1367,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1001 +#: preseed.xml:1002 #, no-c-format msgid "Advanced options" msgstr "" #. Tag: title -#: preseed.xml:1004 +#: preseed.xml:1005 #, no-c-format msgid "Running custom commands during the installation" msgstr "" #. Tag: para -#: preseed.xml:1005 +#: preseed.xml:1006 #, 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:1013 +#: preseed.xml:1014 #, no-c-format msgid "" "# d-i preseeding is inherently not secure. Nothing in the installer checks\n" @@ -1395,19 +1407,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1018 +#: preseed.xml:1019 #, no-c-format msgid "Using preseeding to change default values" msgstr "" #. Tag: para -#: preseed.xml:1019 +#: preseed.xml:1020 #, 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:1028 +#: preseed.xml:1029 #, no-c-format msgid "" "d-i foo/bar string value\n" @@ -1415,19 +1427,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1033 +#: preseed.xml:1034 #, no-c-format msgid "Chainloading preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:1034 +#: preseed.xml:1035 #, 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:1044 +#: preseed.xml:1045 #, no-c-format msgid "" "# More than one file can be listed, separated by spaces; all will be\n" @@ -1455,7 +1467,7 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:1046 +#: preseed.xml:1047 #, 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/random-bits.pot b/po/pot/random-bits.pot index 0fc78e716..66623935f 100644 --- a/po/pot/random-bits.pot +++ b/po/pot/random-bits.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-27 04:04+0000\n" +"POT-Creation-Date: 2006-12-29 19:35+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" @@ -1052,7 +1052,7 @@ msgstr "" #: random-bits.xml:705 #, no-c-format msgid "" - "As mentioned earlier, the installed system will be very basic. If you would like to make the system a bit more mature, there is an easy method to packages of <quote>standard</quote> priority: <informalexample><screen>\n" + "As mentioned earlier, the installed system will be very basic. If you would like to make the system a bit more mature, there is an easy method to install all packages with <quote>standard</quote> priority: <informalexample><screen>\n" "# tasksel install standard\n" "</screen></informalexample> Of course, you can also just use <command>aptitude</command> to install packages individually." msgstr "" diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index 250a8da82..2325012da 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-12-29 10:24+0000\n" +"POT-Creation-Date: 2006-12-29 19:35+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" @@ -633,31 +633,31 @@ msgid "Some technical details you might, or might not, find handy: the program a msgstr "" #. Tag: title -#: using-d-i.xml:746 +#: using-d-i.xml:752 #, no-c-format msgid "Partitioning and Mount Point Selection" msgstr "" #. Tag: para -#: using-d-i.xml:747 +#: using-d-i.xml:753 #, no-c-format msgid "At this time, after hardware detection has been executed a final time, &d-i; should be at its full strength, customized for the user's needs and ready to do some real work. As the title of this section indicates, the main task of the next few components lies in partitioning your disks, creating filesystems, assigning mountpoints and optionally configuring closely related issues like LVM or RAID devices." msgstr "" #. Tag: title -#: using-d-i.xml:769 +#: using-d-i.xml:775 #, no-c-format msgid "Partitioning Your Disks" msgstr "" #. Tag: para -#: using-d-i.xml:771 +#: using-d-i.xml:777 #, no-c-format msgid "Now it is time to partition your disks. If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:778 +#: using-d-i.xml:784 #, no-c-format msgid "" "If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to <quote>zero</quote> the first few sectors of the drive: <informalexample><screen>\n" @@ -666,157 +666,157 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:791 +#: using-d-i.xml:797 #, no-c-format msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu." msgstr "" #. Tag: para -#: using-d-i.xml:798 +#: using-d-i.xml:804 #, no-c-format msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>." msgstr "" #. Tag: para -#: using-d-i.xml:813 +#: using-d-i.xml:819 #, no-c-format msgid "The option to use (encrypted) LVM may not be available on all architectures." msgstr "" #. Tag: para -#: using-d-i.xml:818 +#: using-d-i.xml:824 #, no-c-format msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data." msgstr "" #. Tag: para -#: using-d-i.xml:827 +#: using-d-i.xml:833 #, no-c-format msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk." msgstr "" #. Tag: para -#: using-d-i.xml:836 +#: using-d-i.xml:842 #, no-c-format msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk." msgstr "" #. Tag: para -#: using-d-i.xml:846 +#: using-d-i.xml:852 #, no-c-format msgid "If you choose guided partitioning (either classic or using (encrypted) LVM) for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them." msgstr "" #. Tag: para -#: using-d-i.xml:855 +#: using-d-i.xml:861 #, no-c-format msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible." msgstr "" #. Tag: para -#: using-d-i.xml:863 +#: using-d-i.xml:869 #, no-c-format msgid "Next, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail." msgstr "" #. Tag: entry -#: using-d-i.xml:879 +#: using-d-i.xml:885 #, no-c-format msgid "Partitioning scheme" msgstr "" #. Tag: entry -#: using-d-i.xml:880 +#: using-d-i.xml:886 #, no-c-format msgid "Minimum space" msgstr "" #. Tag: entry -#: using-d-i.xml:881 +#: using-d-i.xml:887 #, no-c-format msgid "Created partitions" msgstr "" #. Tag: entry -#: using-d-i.xml:887 +#: using-d-i.xml:893 #, no-c-format msgid "All files in one partition" msgstr "" #. Tag: entry -#: using-d-i.xml:888 +#: using-d-i.xml:894 #, no-c-format msgid "600MB" msgstr "" #. Tag: entry -#: using-d-i.xml:889 +#: using-d-i.xml:895 #, no-c-format msgid "<filename>/</filename>, swap" msgstr "" #. Tag: entry -#: using-d-i.xml:891 +#: using-d-i.xml:897 #, no-c-format msgid "Separate /home partition" msgstr "" #. Tag: entry -#: using-d-i.xml:892 +#: using-d-i.xml:898 #, no-c-format msgid "500MB" msgstr "" #. Tag: entry -#: using-d-i.xml:893 +#: using-d-i.xml:899 #, no-c-format msgid "<filename>/</filename>, <filename>/home</filename>, swap" msgstr "" #. Tag: entry -#: using-d-i.xml:897 +#: using-d-i.xml:903 #, no-c-format msgid "Separate /home, /usr, /var and /tmp partitions" msgstr "" #. Tag: entry -#: using-d-i.xml:898 +#: using-d-i.xml:904 #, no-c-format msgid "<entry>1GB</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:899 +#: using-d-i.xml:905 #, no-c-format msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap" msgstr "" #. Tag: para -#: using-d-i.xml:908 +#: using-d-i.xml:914 #, no-c-format msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, except for the swap partition, will be created inside the LVM partition." msgstr "" #. Tag: para -#: using-d-i.xml:914 +#: using-d-i.xml:920 #, no-c-format msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition." msgstr "" #. Tag: para -#: using-d-i.xml:922 +#: using-d-i.xml:928 #, no-c-format msgid "If you choose guided partitioning for your Alpha system, an additional, unformatted partition will be allocated at the beginning of your disk to reserve this space for the aboot boot loader." msgstr "" #. Tag: para -#: using-d-i.xml:928 +#: using-d-i.xml:934 #, no-c-format msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted." msgstr "" #. Tag: para -#: using-d-i.xml:934 +#: using-d-i.xml:940 #, no-c-format msgid "" "The list of partitions might look like this: <informalexample><screen>\n" @@ -839,553 +839,553 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:947 +#: using-d-i.xml:953 #, no-c-format msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning." msgstr "" #. Tag: para -#: using-d-i.xml:957 +#: using-d-i.xml:963 #, no-c-format msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually setup your partition table and the usage of partitions by your new Debian system will be covered in the remainder of this section." msgstr "" #. Tag: para -#: using-d-i.xml:965 +#: using-d-i.xml:971 #, no-c-format msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk." msgstr "" #. Tag: para -#: using-d-i.xml:973 +#: using-d-i.xml:979 #, no-c-format -msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap, software RAID, LVM, an encrypted file system, or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose different filesystem for this partition including options to use the partition for swap, software RAID, LVM, or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen." +msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap, software RAID, LVM, an encrypted file system, or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem for this partition, including options to use the partition for swap, software RAID, LVM, or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen." msgstr "" #. Tag: para -#: using-d-i.xml:995 +#: using-d-i.xml:1001 #, no-c-format msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen like when creating a new partition, so you can change the same settings. One thing which might not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition." msgstr "" #. Tag: para -#: using-d-i.xml:1006 +#: using-d-i.xml:1012 #, no-c-format msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue." msgstr "" #. Tag: para -#: using-d-i.xml:1014 +#: using-d-i.xml:1020 #, no-c-format msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one." msgstr "" #. Tag: para -#: using-d-i.xml:1020 +#: using-d-i.xml:1026 #, no-c-format msgid "Capabilities of <command>partman</command> can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)." msgstr "" #. Tag: para -#: using-d-i.xml:1028 +#: using-d-i.xml:1034 #, no-c-format msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested." msgstr "" #. Tag: title -#: using-d-i.xml:1056 +#: using-d-i.xml:1062 #, no-c-format msgid "Configuring Multidisk Device (Software RAID)" msgstr "" #. Tag: para -#: using-d-i.xml:1057 +#: using-d-i.xml:1063 #, no-c-format msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct MD device even from partitions residing on single physical drive, but that won't bring you anything useful. </para></footnote> in your computer, you can use <command>mdcfg</command> to setup your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)." msgstr "" #. Tag: para -#: using-d-i.xml:1071 +#: using-d-i.xml:1077 #, no-c-format msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)." msgstr "" #. Tag: para -#: using-d-i.xml:1079 +#: using-d-i.xml:1085 #, no-c-format msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> </variablelist> To sum it up:" msgstr "" #. Tag: entry -#: using-d-i.xml:1157 +#: using-d-i.xml:1163 #, no-c-format msgid "Type" msgstr "" #. Tag: entry -#: using-d-i.xml:1158 +#: using-d-i.xml:1164 #, no-c-format msgid "Minimum Devices" msgstr "" #. Tag: entry -#: using-d-i.xml:1159 +#: using-d-i.xml:1165 #, no-c-format msgid "Spare Device" msgstr "" #. Tag: entry -#: using-d-i.xml:1160 +#: using-d-i.xml:1166 #, no-c-format msgid "Survives disk failure?" msgstr "" #. Tag: entry -#: using-d-i.xml:1161 +#: using-d-i.xml:1167 #, no-c-format msgid "Available Space" msgstr "" #. Tag: entry -#: using-d-i.xml:1167 +#: using-d-i.xml:1173 #, no-c-format msgid "RAID0" msgstr "" #. Tag: entry -#: using-d-i.xml:1168 using-d-i.xml:1176 +#: using-d-i.xml:1174 using-d-i.xml:1182 #, no-c-format msgid "<entry>2</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1169 using-d-i.xml:1170 +#: using-d-i.xml:1175 using-d-i.xml:1176 #, no-c-format msgid "<entry>no</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1171 +#: using-d-i.xml:1177 #, no-c-format msgid "Size of the smallest partition multiplied by number of devices in RAID" msgstr "" #. Tag: entry -#: using-d-i.xml:1175 +#: using-d-i.xml:1181 #, no-c-format msgid "RAID1" msgstr "" #. Tag: entry -#: using-d-i.xml:1177 using-d-i.xml:1185 +#: using-d-i.xml:1183 using-d-i.xml:1191 #, no-c-format msgid "optional" msgstr "" #. Tag: entry -#: using-d-i.xml:1178 using-d-i.xml:1186 +#: using-d-i.xml:1184 using-d-i.xml:1192 #, no-c-format msgid "<entry>yes</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1179 +#: using-d-i.xml:1185 #, no-c-format msgid "Size of the smallest partition in RAID" msgstr "" #. Tag: entry -#: using-d-i.xml:1183 +#: using-d-i.xml:1189 #, no-c-format msgid "RAID5" msgstr "" #. Tag: entry -#: using-d-i.xml:1184 +#: using-d-i.xml:1190 #, no-c-format msgid "<entry>3</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1187 +#: using-d-i.xml:1193 #, no-c-format msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)" msgstr "" #. Tag: para -#: using-d-i.xml:1195 +#: using-d-i.xml:1201 #, no-c-format msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>." msgstr "" #. Tag: para -#: using-d-i.xml:1200 +#: using-d-i.xml:1206 #, no-c-format msgid "To create a MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)" msgstr "" #. Tag: para -#: using-d-i.xml:1209 +#: using-d-i.xml:1215 #, no-c-format msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) filesystem. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell." msgstr "" #. Tag: para -#: using-d-i.xml:1218 +#: using-d-i.xml:1224 #, no-c-format msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected." msgstr "" #. Tag: para -#: using-d-i.xml:1231 +#: using-d-i.xml:1237 #, no-c-format msgid "RAID0 is simple — you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD." msgstr "" #. Tag: para -#: using-d-i.xml:1238 +#: using-d-i.xml:1244 #, no-c-format msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided few seconds ago. Don't worry. If you make a mistake and select different number of partitions, the &d-i; won't let you continue until you correct the issue." msgstr "" #. Tag: para -#: using-d-i.xml:1250 +#: using-d-i.xml:1256 #, no-c-format msgid "RAID5 has similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions." msgstr "" #. Tag: para -#: using-d-i.xml:1258 +#: using-d-i.xml:1264 #, no-c-format msgid "It is perfectly possible to have several types of MD at once. For example if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)." msgstr "" #. Tag: para -#: using-d-i.xml:1267 +#: using-d-i.xml:1273 #, no-c-format msgid "After you setup MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints." msgstr "" #. Tag: title -#: using-d-i.xml:1282 +#: using-d-i.xml:1288 #, no-c-format msgid "Configuring the Logical Volume Manager (LVM)" msgstr "" #. Tag: para -#: using-d-i.xml:1283 +#: using-d-i.xml:1289 #, no-c-format msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation with moving stuff around, symlinking, etc." msgstr "" #. Tag: para -#: using-d-i.xml:1291 +#: using-d-i.xml:1297 #, no-c-format msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disk (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks." msgstr "" #. Tag: para -#: using-d-i.xml:1301 +#: using-d-i.xml:1307 #, no-c-format msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk to the computer, join it with your existing volume group and then resize the logical volume which holds your <filename>/home</filename> filesystem and voila — your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>." msgstr "" #. Tag: para -#: using-d-i.xml:1312 +#: using-d-i.xml:1318 #, no-c-format msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>." msgstr "" #. Tag: para -#: using-d-i.xml:1321 +#: using-d-i.xml:1327 #, no-c-format msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:" msgstr "" #. Tag: para -#: using-d-i.xml:1332 +#: using-d-i.xml:1338 #, no-c-format msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1337 +#: using-d-i.xml:1343 #, no-c-format msgid "Create volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1340 +#: using-d-i.xml:1346 #, no-c-format msgid "Create logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1343 +#: using-d-i.xml:1349 #, no-c-format msgid "Delete volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1346 +#: using-d-i.xml:1352 #, no-c-format msgid "Delete logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1349 +#: using-d-i.xml:1355 #, no-c-format msgid "Extend volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1352 +#: using-d-i.xml:1358 #, no-c-format msgid "Reduce volume group" msgstr "" #. Tag: para -#: using-d-i.xml:1354 +#: using-d-i.xml:1360 #, no-c-format msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen" msgstr "" #. Tag: para -#: using-d-i.xml:1360 +#: using-d-i.xml:1366 #, no-c-format msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it." msgstr "" #. Tag: para -#: using-d-i.xml:1365 +#: using-d-i.xml:1371 #, no-c-format msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)." msgstr "" #. Tag: title -#: using-d-i.xml:1379 +#: using-d-i.xml:1385 #, no-c-format msgid "Configuring Encrypted Volumes" msgstr "" #. Tag: para -#: using-d-i.xml:1380 +#: using-d-i.xml:1386 #, no-c-format msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters." msgstr "" #. Tag: para -#: using-d-i.xml:1392 +#: using-d-i.xml:1398 #, no-c-format msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition." msgstr "" #. Tag: para -#: using-d-i.xml:1407 +#: using-d-i.xml:1413 #, no-c-format msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length." msgstr "" #. Tag: para -#: using-d-i.xml:1414 +#: using-d-i.xml:1420 #, no-c-format msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition." msgstr "" #. Tag: para -#: using-d-i.xml:1425 +#: using-d-i.xml:1431 #, no-c-format msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default." msgstr "" #. Tag: para -#: using-d-i.xml:1437 +#: using-d-i.xml:1443 #, no-c-format msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind." msgstr "" #. Tag: term -#: using-d-i.xml:1447 +#: using-d-i.xml:1453 #, no-c-format msgid "Encryption: <userinput>aes</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1449 +#: using-d-i.xml:1455 #, no-c-format msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century." msgstr "" #. Tag: term -#: using-d-i.xml:1467 +#: using-d-i.xml:1473 #, no-c-format msgid "Key size: <userinput>256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1469 +#: using-d-i.xml:1475 #, no-c-format msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher." msgstr "" #. Tag: term -#: using-d-i.xml:1481 +#: using-d-i.xml:1487 #, no-c-format msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1483 +#: using-d-i.xml:1489 #, no-c-format msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data." msgstr "" #. Tag: para -#: using-d-i.xml:1493 +#: using-d-i.xml:1499 #, no-c-format msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms." msgstr "" #. Tag: term -#: using-d-i.xml:1505 +#: using-d-i.xml:1511 #, no-c-format msgid "Encryption key: <userinput>Passphrase</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1507 +#: using-d-i.xml:1513 #, no-c-format msgid "Here you can choose the type of the encryption key for this partition." msgstr "" #. Tag: term -#: using-d-i.xml:1513 +#: using-d-i.xml:1519 #, no-c-format msgid "Passphrase" msgstr "" #. Tag: para -#: using-d-i.xml:1514 +#: using-d-i.xml:1520 #, no-c-format msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process." msgstr "" #. Tag: term -#: using-d-i.xml:1529 using-d-i.xml:1622 +#: using-d-i.xml:1535 using-d-i.xml:1628 #, no-c-format msgid "Random key" msgstr "" #. Tag: para -#: using-d-i.xml:1530 +#: using-d-i.xml:1536 #, no-c-format msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)" msgstr "" #. Tag: para -#: using-d-i.xml:1539 +#: using-d-i.xml:1545 #, no-c-format msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition." msgstr "" #. Tag: term -#: using-d-i.xml:1558 using-d-i.xml:1635 +#: using-d-i.xml:1564 using-d-i.xml:1641 #, no-c-format msgid "Erase data: <userinput>yes</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1560 +#: using-d-i.xml:1566 #, no-c-format msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>." msgstr "" #. Tag: para -#: using-d-i.xml:1580 +#: using-d-i.xml:1586 #, no-c-format msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:" msgstr "" #. Tag: term -#: using-d-i.xml:1589 +#: using-d-i.xml:1595 #, no-c-format msgid "Encryption: <userinput>AES256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1591 +#: using-d-i.xml:1597 #, no-c-format msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information." msgstr "" #. Tag: term -#: using-d-i.xml:1601 +#: using-d-i.xml:1607 #, no-c-format msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1603 +#: using-d-i.xml:1609 #, no-c-format msgid "Here you can select the type of the encryption key for this partition." msgstr "" #. Tag: term -#: using-d-i.xml:1609 +#: using-d-i.xml:1615 #, no-c-format msgid "Keyfile (GnuPG)" msgstr "" #. Tag: para -#: using-d-i.xml:1610 +#: using-d-i.xml:1616 #, no-c-format msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)." msgstr "" #. Tag: para -#: using-d-i.xml:1623 +#: using-d-i.xml:1629 #, no-c-format msgid "Please see the the section on random keys above." msgstr "" #. Tag: para -#: using-d-i.xml:1637 +#: using-d-i.xml:1643 #, no-c-format msgid "Please see the the section on erasing data above." msgstr "" #. Tag: para -#: using-d-i.xml:1646 +#: using-d-i.xml:1652 #, no-c-format msgid "Please note that the <emphasis>graphical</emphasis> version of the installer still has some limitations when compared to the textual one. For cryptography it means you can set up only volumes using <emphasis>passphrases</emphasis> as the encryption keys." msgstr "" #. Tag: para -#: using-d-i.xml:1653 +#: using-d-i.xml:1659 #, no-c-format msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time." msgstr "" #. Tag: para -#: using-d-i.xml:1664 +#: using-d-i.xml:1670 #, no-c-format msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)." msgstr "" #. Tag: para -#: using-d-i.xml:1673 +#: using-d-i.xml:1679 #, no-c-format msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system." msgstr "" #. Tag: para -#: using-d-i.xml:1686 +#: using-d-i.xml:1692 #, no-c-format msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted." msgstr "" #. Tag: para -#: using-d-i.xml:1702 +#: using-d-i.xml:1708 #, no-c-format msgid "" "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n" @@ -1398,505 +1398,505 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:1715 +#: using-d-i.xml:1721 #, no-c-format msgid "One thing to note here are the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between ordinary boot process and boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:1725 +#: using-d-i.xml:1731 #, no-c-format msgid "Once you are satisfied with the partitioning scheme, continue with the installation." msgstr "" #. Tag: title -#: using-d-i.xml:1736 +#: using-d-i.xml:1742 #, no-c-format msgid "Setting up the System" msgstr "" #. Tag: para -#: using-d-i.xml:1737 +#: using-d-i.xml:1743 #, no-c-format msgid "After partitioning the installer asks a few more questions that will be used to set up the system it is about to install." msgstr "" #. Tag: title -#: using-d-i.xml:1749 +#: using-d-i.xml:1755 #, no-c-format msgid "Configuring Your Time Zone" msgstr "" #. Tag: para -#: using-d-i.xml:1751 +#: using-d-i.xml:1757 #, no-c-format msgid "Depending on the location selected at the beginning of the installation process, you might be shown a list of timezones relevant for that location. If your location has only one time zone, you will not be asked anything and the system will assume that time zone." msgstr "" #. Tag: title -#: using-d-i.xml:1767 +#: using-d-i.xml:1773 #, no-c-format msgid "Configuring the Clock" msgstr "" #. Tag: para -#: using-d-i.xml:1769 +#: using-d-i.xml:1775 #, no-c-format msgid "The installer might ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed." msgstr "" #. Tag: para -#: using-d-i.xml:1776 +#: using-d-i.xml:1782 #, no-c-format msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"m68k;powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> <phrase arch=\"x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase>" msgstr "" #. Tag: para -#: using-d-i.xml:1787 +#: using-d-i.xml:1793 #, no-c-format msgid "Note that the installer does not currently allow you to actually set the time in the computer's clock. You can set the clock to the current time after you have installed, if it is incorrect or if it was previously not set to UTC." msgstr "" #. Tag: title -#: using-d-i.xml:1803 +#: using-d-i.xml:1809 #, no-c-format msgid "Setting Up Users And Passwords" msgstr "" #. Tag: title -#: using-d-i.xml:1806 +#: using-d-i.xml:1812 #, no-c-format msgid "Set the Root Password" msgstr "" #. Tag: para -#: using-d-i.xml:1808 +#: using-d-i.xml:1814 #, no-c-format msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible." msgstr "" #. Tag: para -#: using-d-i.xml:1816 +#: using-d-i.xml:1822 #, no-c-format msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed." msgstr "" #. Tag: para -#: using-d-i.xml:1824 +#: using-d-i.xml:1830 #, no-c-format msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator." msgstr "" #. Tag: title -#: using-d-i.xml:1834 +#: using-d-i.xml:1840 #, no-c-format msgid "Create an Ordinary User" msgstr "" #. Tag: para -#: using-d-i.xml:1836 +#: using-d-i.xml:1842 #, no-c-format msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login." msgstr "" #. Tag: para -#: using-d-i.xml:1843 +#: using-d-i.xml:1849 #, no-c-format msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program — that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail — consider reading one if it is new to you." msgstr "" #. Tag: para -#: using-d-i.xml:1853 +#: using-d-i.xml:1859 #, no-c-format msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account." msgstr "" #. Tag: para -#: using-d-i.xml:1860 +#: using-d-i.xml:1866 #, no-c-format msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command." msgstr "" #. Tag: title -#: using-d-i.xml:1872 +#: using-d-i.xml:1878 #, no-c-format msgid "Installing the Base System" msgstr "" #. Tag: para -#: using-d-i.xml:1873 +#: using-d-i.xml:1879 #, no-c-format msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time." msgstr "" #. Tag: para -#: using-d-i.xml:1886 +#: using-d-i.xml:1892 #, no-c-format msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>." msgstr "" #. Tag: para -#: using-d-i.xml:1895 +#: using-d-i.xml:1901 #, no-c-format msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console." msgstr "" #. Tag: para -#: using-d-i.xml:1901 +#: using-d-i.xml:1907 #, no-c-format msgid "As part of the installation, a Linux kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels." msgstr "" #. Tag: title -#: using-d-i.xml:1913 +#: using-d-i.xml:1919 #, no-c-format msgid "Installing Additional Software" msgstr "" #. Tag: para -#: using-d-i.xml:1914 +#: using-d-i.xml:1920 #, no-c-format msgid "After the base system is installed, you have a usable but limited system. Most users will want to install additional software to the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network." msgstr "" #. Tag: title -#: using-d-i.xml:1928 +#: using-d-i.xml:1934 #, no-c-format msgid "Configuring apt" msgstr "" #. Tag: para -#: using-d-i.xml:1930 +#: using-d-i.xml:1936 #, no-c-format msgid "One of the tools used to install packages on a &debian; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management." msgstr "" #. Tag: para -#: using-d-i.xml:1956 +#: using-d-i.xml:1962 #, no-c-format msgid "<command>apt</command> must be configured so that it knows where to retrieve packages from. The installer largely takes care of this automatically based on what it knows about your installation medium. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>, and you can examine and edit it to your liking after the install is complete." msgstr "" #. Tag: title -#: using-d-i.xml:1972 +#: using-d-i.xml:1978 #, no-c-format msgid "Selecting and Installing Software" msgstr "" #. Tag: para -#: using-d-i.xml:1974 +#: using-d-i.xml:1980 #, no-c-format msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks." msgstr "" #. Tag: para -#: using-d-i.xml:1983 +#: using-d-i.xml:1989 #, no-c-format msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks." msgstr "" #. Tag: para -#: using-d-i.xml:2008 +#: using-d-i.xml:2014 #, no-c-format msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can un-select the tasks. You can even opt to install no tasks at all at this point." msgstr "" #. Tag: para -#: using-d-i.xml:2015 +#: using-d-i.xml:2021 #, 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 such as for example KDE." msgstr "" #. Tag: para -#: using-d-i.xml:2021 +#: using-d-i.xml:2027 #, no-c-format 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:2032 +#: using-d-i.xml:2038 #, no-c-format 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:2044 +#: using-d-i.xml:2050 #, 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:2051 +#: using-d-i.xml:2057 #, 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:2060 +#: using-d-i.xml:2066 #, 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:2073 +#: using-d-i.xml:2079 #, no-c-format msgid "Making Your System Bootable" msgstr "" #. Tag: para -#: using-d-i.xml:2075 +#: using-d-i.xml:2081 #, 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 OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>" msgstr "" #. Tag: title -#: using-d-i.xml:2090 +#: using-d-i.xml:2096 #, no-c-format msgid "Detecting other operating systems" msgstr "" #. Tag: para -#: using-d-i.xml:2092 +#: using-d-i.xml:2098 #, 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:2100 +#: using-d-i.xml:2106 #, 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:2118 +#: using-d-i.xml:2124 #, no-c-format msgid "Install <command>aboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2119 +#: using-d-i.xml:2125 #, no-c-format msgid "If you have booted from SRM and 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:2139 +#: using-d-i.xml:2145 #, no-c-format msgid "<command>palo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2140 +#: using-d-i.xml:2146 #, 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:2149 +#: using-d-i.xml:2155 #, no-c-format msgid "hppa FIXME ( need more info )" msgstr "" #. Tag: title -#: using-d-i.xml:2161 +#: using-d-i.xml:2167 #, no-c-format msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2163 +#: using-d-i.xml:2169 #, 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:2169 +#: using-d-i.xml:2175 #, 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:2175 +#: using-d-i.xml:2181 #, 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:2189 +#: using-d-i.xml:2195 #, no-c-format msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2191 +#: using-d-i.xml:2197 #, 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:2201 +#: using-d-i.xml:2207 #, 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:2209 +#: using-d-i.xml:2215 #, no-c-format msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:" msgstr "" #. Tag: term -#: using-d-i.xml:2216 +#: using-d-i.xml:2222 #, no-c-format msgid "Master Boot Record (MBR)" msgstr "" #. Tag: para -#: using-d-i.xml:2216 +#: using-d-i.xml:2222 #, 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:2223 +#: using-d-i.xml:2229 #, no-c-format msgid "new Debian partition" msgstr "" #. Tag: para -#: using-d-i.xml:2223 +#: using-d-i.xml:2229 #, 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:2232 +#: using-d-i.xml:2238 #, no-c-format msgid "Other choice" msgstr "" #. Tag: para -#: using-d-i.xml:2232 +#: using-d-i.xml:2238 #, 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:2244 +#: using-d-i.xml:2250 #, 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!" msgstr "" #. Tag: title -#: using-d-i.xml:2260 +#: using-d-i.xml:2266 #, no-c-format msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2262 +#: using-d-i.xml:2268 #, 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 files 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 do the actual work of loading and starting the Linux kernel." msgstr "" #. Tag: para -#: using-d-i.xml:2278 +#: using-d-i.xml:2284 #, 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:2290 +#: using-d-i.xml:2296 #, no-c-format msgid "Choose the correct partition!" msgstr "" #. Tag: para -#: using-d-i.xml:2292 +#: using-d-i.xml:2298 #, 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, <command>elilo</command> may format the partition during the installation, erasing any previous contents!" msgstr "" #. Tag: title -#: using-d-i.xml:2307 +#: using-d-i.xml:2313 #, no-c-format msgid "EFI Partition Contents" msgstr "" #. Tag: para -#: using-d-i.xml:2309 +#: using-d-i.xml:2315 #, 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:2331 +#: using-d-i.xml:2337 #, no-c-format msgid "elilo.conf" msgstr "" #. Tag: para -#: using-d-i.xml:2332 +#: using-d-i.xml:2338 #, 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:2341 +#: using-d-i.xml:2347 #, no-c-format msgid "elilo.efi" msgstr "" #. Tag: para -#: using-d-i.xml:2342 +#: using-d-i.xml:2348 #, 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:2352 +#: using-d-i.xml:2358 #, no-c-format msgid "initrd.img" msgstr "" #. Tag: para -#: using-d-i.xml:2353 +#: using-d-i.xml:2359 #, 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:2365 +#: using-d-i.xml:2371 #, no-c-format msgid "readme.txt" msgstr "" #. Tag: para -#: using-d-i.xml:2366 +#: using-d-i.xml:2372 #, 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:2376 +#: using-d-i.xml:2382 #, no-c-format msgid "vmlinuz" msgstr "" #. Tag: para -#: using-d-i.xml:2377 +#: using-d-i.xml:2383 #, 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:2397 +#: using-d-i.xml:2403 #, no-c-format msgid "<command>arcboot</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2398 +#: using-d-i.xml:2404 #, 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" @@ -1909,61 +1909,61 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2417 +#: using-d-i.xml:2423 #, no-c-format msgid "scsi" msgstr "" #. Tag: para -#: using-d-i.xml:2418 +#: using-d-i.xml:2424 #, 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:2426 +#: using-d-i.xml:2432 #, no-c-format msgid "disk" msgstr "" #. Tag: para -#: using-d-i.xml:2427 +#: using-d-i.xml:2433 #, 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:2435 using-d-i.xml:2504 +#: using-d-i.xml:2441 using-d-i.xml:2510 #, no-c-format msgid "partnr" msgstr "" #. Tag: para -#: using-d-i.xml:2436 +#: using-d-i.xml:2442 #, 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:2444 +#: using-d-i.xml:2450 #, no-c-format msgid "config" msgstr "" #. Tag: para -#: using-d-i.xml:2445 +#: using-d-i.xml:2451 #, 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:2466 +#: using-d-i.xml:2472 #, no-c-format msgid "<command>delo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2467 +#: using-d-i.xml:2473 #, 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" @@ -1972,265 +1972,265 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2486 +#: using-d-i.xml:2492 #, no-c-format msgid "<replaceable>#</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2487 +#: using-d-i.xml:2493 #, 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:2495 +#: using-d-i.xml:2501 #, no-c-format msgid "<replaceable>id</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2496 +#: using-d-i.xml:2502 #, 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:2505 +#: using-d-i.xml:2511 #, 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:2513 +#: using-d-i.xml:2519 #, no-c-format msgid "name" msgstr "" #. Tag: para -#: using-d-i.xml:2514 +#: using-d-i.xml:2520 #, 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:2524 +#: using-d-i.xml:2530 #, 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:2530 +#: using-d-i.xml:2536 #, no-c-format msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>" msgstr "" #. Tag: title -#: using-d-i.xml:2540 +#: using-d-i.xml:2546 #, no-c-format msgid "Install <command>Yaboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2541 +#: using-d-i.xml:2547 #, 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:2559 +#: using-d-i.xml:2565 #, no-c-format msgid "Install <command>Quik</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2560 +#: using-d-i.xml:2566 #, 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:2576 +#: using-d-i.xml:2582 #, no-c-format msgid "<command>zipl</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2577 +#: using-d-i.xml:2583 #, 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:2594 +#: using-d-i.xml:2600 #, no-c-format msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2596 +#: using-d-i.xml:2602 #, 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:2621 +#: using-d-i.xml:2627 #, no-c-format msgid "Continue Without Boot Loader" msgstr "" #. Tag: para -#: using-d-i.xml:2623 +#: using-d-i.xml:2629 #, 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:2632 +#: using-d-i.xml:2638 #, 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:2649 +#: using-d-i.xml:2655 #, no-c-format msgid "Finishing the Installation" msgstr "" #. Tag: para -#: using-d-i.xml:2650 +#: using-d-i.xml:2656 #, 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:2662 +#: using-d-i.xml:2668 #, no-c-format msgid "Finish the Installation and Reboot" msgstr "" #. Tag: para -#: using-d-i.xml:2664 +#: using-d-i.xml:2670 #, 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:2671 +#: using-d-i.xml:2677 #, 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:2685 +#: using-d-i.xml:2691 #, no-c-format msgid "Miscellaneous" msgstr "" #. Tag: para -#: using-d-i.xml:2686 +#: using-d-i.xml:2692 #, 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:2699 +#: using-d-i.xml:2705 #, no-c-format msgid "Saving the installation logs" msgstr "" #. Tag: para -#: using-d-i.xml:2701 +#: using-d-i.xml:2707 #, 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:2708 +#: using-d-i.xml:2714 #, 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:2728 +#: using-d-i.xml:2734 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "" #. Tag: para -#: using-d-i.xml:2730 +#: using-d-i.xml:2736 #, no-c-format msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press 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. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to installer itself." msgstr "" #. Tag: para -#: using-d-i.xml:2748 +#: using-d-i.xml:2754 #, no-c-format msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. To get back to the installer itself, type <userinput>exit</userinput> to close the shell." msgstr "" #. Tag: para -#: using-d-i.xml:2755 +#: using-d-i.xml:2761 #, 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 shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history." msgstr "" #. Tag: para -#: using-d-i.xml:2764 +#: using-d-i.xml:2770 #, no-c-format msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory." msgstr "" #. Tag: para -#: using-d-i.xml:2771 +#: using-d-i.xml:2777 #, no-c-format msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging." msgstr "" #. Tag: para -#: using-d-i.xml:2777 +#: using-d-i.xml:2783 #, no-c-format msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell." msgstr "" #. Tag: title -#: using-d-i.xml:2792 +#: using-d-i.xml:2798 #, no-c-format msgid "Installation Over the Network" msgstr "" #. Tag: para -#: using-d-i.xml:2794 +#: using-d-i.xml:2800 #, 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:2804 +#: using-d-i.xml:2810 #, 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:2817 +#: using-d-i.xml:2823 #, 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:2822 +#: using-d-i.xml:2828 #, 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:2834 +#: using-d-i.xml:2840 #, 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:2840 +#: using-d-i.xml:2846 #, 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" @@ -2239,25 +2239,25 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:2857 +#: using-d-i.xml:2863 #, 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:2866 +#: using-d-i.xml:2872 #, 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:2876 +#: using-d-i.xml:2882 #, 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:2884 +#: using-d-i.xml:2890 #, 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 "" |