diff options
| author | Frans Pop <elendil@planet.nl> | 2006-06-21 12:49:53 +0000 |
|---|---|---|
| committer | Frans Pop <elendil@planet.nl> | 2006-06-21 12:49:53 +0000 |
| commit | 25e8e2dad6a9c967b1e480c0fb0892d59d3bf3ab (patch) | |
| tree | cead4062e32ade57c233e52bd9b8082a28a19720 /po/pot | |
| parent | 79182dab83f65e85206d97ca20dd552624571420 (diff) | |
| download | installation-guide-25e8e2dad6a9c967b1e480c0fb0892d59d3bf3ab.zip | |
Update of POT and PO files for the manual
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 174 | ||||
| -rw-r--r-- | po/pot/preparing.pot | 1892 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 220 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 8 |
4 files changed, 208 insertions, 2086 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 547679f53..5636e2d0c 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" -"POT-Creation-Date: 2006-04-28 19:33+0000\n" +"POT-Creation-Date: 2006-06-21 12:48+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" @@ -854,13 +854,13 @@ msgstr "" #: boot-installer.xml:1077 #, no-c-format #. Tag: para -msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</keycap>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>linux</userinput>) and a space before the first parameter (e.g., <userinput>linux debconf/priority=medium</userinput>)." +msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</keycap>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>linux</userinput>) and a space before the first parameter (e.g., <userinput>linux fb=false</userinput>)." msgstr "" #: boot-installer.xml:1086 #, no-c-format #. Tag: para -msgid "If you are installing the system via a remote management device that provides a text interface to the VGA console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot prompt. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA). You can blindly press F1<footnote> <para> In some cases these devices will require special escape sequences to enact this keypress, for example the IRA uses <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</keycap>. </para> </footnote> to bypass this screen and view the help text. Once you are past the splash screen and at the help text your keystrokes will be echoed at the prompt as expected. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>debian-installer/framebuffer=false</userinput> to the boot prompt, as described in the help text." +msgid "If you are installing the system via a remote management device that provides a text interface to the VGA console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot prompt. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA). You can blindly press F1<footnote> <para> In some cases these devices will require special escape sequences to enact this keypress, for example the IRA uses <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</keycap>. </para> </footnote> to bypass this screen and view the help text. Once you are past the splash screen and at the help text your keystrokes will be echoed at the prompt as expected. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>fb=false</userinput> to the boot prompt, as described in the help text." msgstr "" #: boot-installer.xml:1161 @@ -1203,7 +1203,7 @@ msgstr "" #: boot-installer.xml:1673 #, no-c-format #. Tag: para -msgid "Amiga does not currently work with bogl, so if you are seeing bogl errors, you need to include the kernel parameter <userinput>debian-installer/framebuffer=false</userinput>." +msgid "Amiga does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter <userinput>fb=false</userinput>." msgstr "" #: boot-installer.xml:1682 @@ -1221,7 +1221,7 @@ msgstr "" #: boot-installer.xml:1690 #, no-c-format #. Tag: para -msgid "Atari does not currently work with bogl, so if you are seeing bogl errors, you need to include the kernel parameter <userinput>debian-installer/framebuffer=false</userinput>." +msgid "Atari does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter <userinput>fb=false</userinput>." msgstr "" #: boot-installer.xml:1699 @@ -1840,7 +1840,7 @@ msgstr "" #: boot-installer.xml:2805 #, no-c-format #. Tag: para -msgid "The installation system recognizes a few additional boot parameters<footnote> <para> Note that the kernel accepts a maximum of 8 command line options and 8 environment options (including any options added by default for the installer). If these numbers are exceeded, 2.4 kernels will drop any excess options and 2.6 kernels will panic. With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options. </para> </footnote> which may be useful." +msgid "The installation system recognizes a few additional boot parameters<footnote> <para> Note that the 2.4 kernel accepts a maximum of 8 command line options and 8 environment options (including any options added by default for the installer). If these numbers are exceeded, 2.4 kernels will drop any excess options. With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options. </para> </footnote> which may be useful." msgstr "" #: boot-installer.xml:2825 @@ -1852,442 +1852,442 @@ msgstr "" #: boot-installer.xml:2826 #, no-c-format #. Tag: para -msgid "This parameter sets the lowest priority of messages to be displayed." +msgid "This parameter sets the lowest priority of messages to be displayed. Short form: <userinput>priority</userinput>" msgstr "" -#: boot-installer.xml:2830 +#: boot-installer.xml:2831 #, no-c-format #. Tag: para -msgid "The default installation uses <userinput>debconf/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." +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 "" -#: boot-installer.xml:2837 +#: boot-installer.xml:2838 #, no-c-format #. Tag: para -msgid "If you add <userinput>debconf/priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>debconf/priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>debconf/priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss." +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 "" -#: boot-installer.xml:2851 +#: boot-installer.xml:2852 #, no-c-format #. Tag: term msgid "DEBIAN_FRONTEND" msgstr "" -#: boot-installer.xml:2852 +#: boot-installer.xml:2853 #, no-c-format #. Tag: para msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=slang</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=ncurses</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=corba</userinput></para> </listitem> </itemizedlist> The default front end is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally only the <userinput>newt</userinput> frontend is available on default install media, so this is not very useful right now." msgstr "" -#: boot-installer.xml:2888 +#: boot-installer.xml:2889 #, no-c-format #. Tag: term msgid "BOOT_DEBUG" msgstr "" -#: boot-installer.xml:2889 +#: boot-installer.xml:2890 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2898 +#: boot-installer.xml:2899 #, no-c-format #. Tag: userinput msgid "BOOT_DEBUG=0" msgstr "" -#: boot-installer.xml:2899 +#: boot-installer.xml:2900 #, no-c-format #. Tag: para msgid "This is the default." msgstr "" -#: boot-installer.xml:2903 +#: boot-installer.xml:2904 #, no-c-format #. Tag: userinput msgid "BOOT_DEBUG=1" msgstr "" -#: boot-installer.xml:2904 +#: boot-installer.xml:2905 #, no-c-format #. Tag: para msgid "More verbose than usual." msgstr "" -#: boot-installer.xml:2908 +#: boot-installer.xml:2909 #, no-c-format #. Tag: userinput msgid "BOOT_DEBUG=2" msgstr "" -#: boot-installer.xml:2909 +#: boot-installer.xml:2910 #, no-c-format #. Tag: para msgid "Lots of debugging information." msgstr "" -#: boot-installer.xml:2913 +#: boot-installer.xml:2914 #, no-c-format #. Tag: userinput msgid "BOOT_DEBUG=3" msgstr "" -#: boot-installer.xml:2914 +#: boot-installer.xml:2915 #, no-c-format #. Tag: para msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot." msgstr "" -#: boot-installer.xml:2928 +#: boot-installer.xml:2929 #, no-c-format #. Tag: term msgid "INSTALL_MEDIA_DEV" msgstr "" -#: boot-installer.xml:2929 +#: boot-installer.xml:2930 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2935 +#: boot-installer.xml:2936 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:2945 +#: boot-installer.xml:2946 #, no-c-format #. Tag: term msgid "debian-installer/framebuffer" msgstr "" -#: boot-installer.xml:2946 +#: boot-installer.xml:2947 #, no-c-format #. Tag: para -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>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install." +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 "" -#: boot-installer.xml:2955 +#: boot-installer.xml:2957 #, no-c-format #. Tag: para -msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card." +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 "" -#: boot-installer.xml:2961 +#: boot-installer.xml:2963 #, no-c-format #. Tag: para msgid "Such problems have been reported on the Amiga 1200 and SE/30." msgstr "" -#: boot-installer.xml:2965 +#: boot-installer.xml:2967 #, no-c-format #. Tag: para msgid "Such problems have been reported on hppa." msgstr "" -#: boot-installer.xml:2969 +#: boot-installer.xml:2971 #, no-c-format #. Tag: para 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>." msgstr "" -#: boot-installer.xml:2982 +#: boot-installer.xml:2984 #, no-c-format #. Tag: term msgid "debian-installer/probe/usb" msgstr "" -#: boot-installer.xml:2983 +#: boot-installer.xml:2985 #, no-c-format #. Tag: para msgid "Set to <userinput>false</userinput> to prevent probing for USB on boot, if that causes problems." msgstr "" -#: boot-installer.xml:2992 +#: boot-installer.xml:2994 #, no-c-format #. Tag: term msgid "netcfg/disable_dhcp" msgstr "" -#: boot-installer.xml:2993 +#: boot-installer.xml:2995 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3000 +#: boot-installer.xml:3002 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3011 +#: boot-installer.xml:3013 #, no-c-format #. Tag: term msgid "hw-detect/start_pcmcia" msgstr "" -#: boot-installer.xml:3012 +#: boot-installer.xml:3014 #, no-c-format #. Tag: para msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." msgstr "" -#: boot-installer.xml:3022 +#: boot-installer.xml:3024 #, no-c-format #. Tag: term msgid "preseed/url" msgstr "" -#: boot-installer.xml:3023 +#: boot-installer.xml:3025 #, no-c-format #. Tag: para -msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>." +msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>url</userinput>" msgstr "" -#: boot-installer.xml:3032 +#: boot-installer.xml:3035 #, no-c-format #. Tag: term msgid "preseed/file" msgstr "" -#: boot-installer.xml:3033 +#: boot-installer.xml:3036 #, no-c-format #. Tag: para -msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>." +msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>file</userinput>" msgstr "" -#: boot-installer.xml:3042 +#: boot-installer.xml:3046 #, no-c-format #. Tag: term msgid "cdrom-detect/eject" msgstr "" -#: boot-installer.xml:3043 +#: boot-installer.xml:3047 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3052 +#: boot-installer.xml:3056 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3063 +#: boot-installer.xml:3067 #, no-c-format #. Tag: term msgid "ramdisk_size" msgstr "" -#: boot-installer.xml:3064 +#: boot-installer.xml:3068 #, no-c-format #. Tag: para msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." msgstr "" -#: boot-installer.xml:3072 +#: boot-installer.xml:3076 #, no-c-format #. Tag: term msgid "rescue/enable" msgstr "" -#: boot-installer.xml:3073 +#: boot-installer.xml:3077 #, no-c-format #. Tag: para msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." msgstr "" -#: boot-installer.xml:3091 +#: boot-installer.xml:3095 #, no-c-format #. Tag: title msgid "Troubleshooting the Installation Process" msgstr "" -#: boot-installer.xml:3096 +#: boot-installer.xml:3100 #, no-c-format #. Tag: title msgid "Floppy Disk Reliability" msgstr "" -#: boot-installer.xml:3098 +#: boot-installer.xml:3102 #, no-c-format #. Tag: para msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." msgstr "" -#: boot-installer.xml:3103 +#: boot-installer.xml:3107 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3112 +#: boot-installer.xml:3116 #, no-c-format #. Tag: para msgid "If you are having the installation stall at a particular floppy, the first thing you should do is re-download the floppy disk image and write it to a <emphasis>different</emphasis> floppy. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system." msgstr "" -#: boot-installer.xml:3122 +#: boot-installer.xml:3126 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3128 +#: boot-installer.xml:3132 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3137 +#: boot-installer.xml:3141 #, no-c-format #. Tag: title msgid "Boot Configuration" msgstr "" -#: boot-installer.xml:3139 +#: boot-installer.xml:3143 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3146 +#: boot-installer.xml:3150 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3153 +#: boot-installer.xml:3157 #, no-c-format #. Tag: para msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"i386\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" msgstr "" -#: boot-installer.xml:3159 +#: boot-installer.xml:3163 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3170 +#: boot-installer.xml:3174 #, no-c-format #. Tag: title msgid "Common &arch-title; Installation Problems" msgstr "" -#: boot-installer.xml:3171 +#: boot-installer.xml:3175 #, no-c-format #. Tag: para msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." msgstr "" -#: boot-installer.xml:3176 +#: boot-installer.xml:3180 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3182 +#: boot-installer.xml:3186 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3191 +#: boot-installer.xml:3195 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3198 +#: boot-installer.xml:3202 #, no-c-format #. Tag: para -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>debian-installer/framebuffer=false</userinput> or <userinput>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." +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 "" -#: boot-installer.xml:3213 +#: boot-installer.xml:3216 #, no-c-format #. Tag: title msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" -#: boot-installer.xml:3214 +#: boot-installer.xml:3217 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3224 +#: boot-installer.xml:3227 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3241 +#: boot-installer.xml:3244 #, no-c-format #. Tag: title msgid "System Freeze while Loading the USB Modules" msgstr "" -#: boot-installer.xml:3242 +#: boot-installer.xml:3245 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3256 +#: boot-installer.xml:3259 #, no-c-format #. Tag: title msgid "Interpreting the Kernel Startup Messages" msgstr "" -#: boot-installer.xml:3258 +#: boot-installer.xml:3261 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3283 +#: boot-installer.xml:3286 #, no-c-format #. Tag: title msgid "Bug Reporter" msgstr "" -#: boot-installer.xml:3284 +#: boot-installer.xml:3287 #, no-c-format #. Tag: para msgid "If you get through the initial boot phase but cannot complete the install, the bug reporter menu choice may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them in a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report you may want to attach this information to the bug report." msgstr "" -#: boot-installer.xml:3295 +#: boot-installer.xml:3298 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3306 +#: boot-installer.xml:3309 #, no-c-format #. Tag: title msgid "Submitting Installation Reports" msgstr "" -#: boot-installer.xml:3307 +#: boot-installer.xml:3310 #, no-c-format #. Tag: para 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 "" -#: boot-installer.xml:3314 +#: boot-installer.xml:3317 #, no-c-format #. Tag: para msgid "If you have a working Debian system, the easiest way to send an installation report is to install the installation-report and reportbug packages (<command>apt-get install installation-report reportbug</command>) and run the command <command>reportbug installation-report</command>." msgstr "" -#: boot-installer.xml:3321 +#: boot-installer.xml:3324 #, no-c-format #. Tag: para msgid "" diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot index 8c42f3b45..ca9b465e2 100644 --- a/po/pot/preparing.pot +++ b/po/pot/preparing.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2006-04-28 19:34+0000\n" +"POT-Creation-Date: 2006-06-21 12:48+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" @@ -14,1893 +14,3 @@ msgstr "" "Content-Type: application/x-xml2pot; charset=UTF-8\n" "Content-Transfer-Encoding: ENCODING\n" -#: preparing.xml:5 -#, no-c-format -#. Tag: title -msgid "Before Installing &debian;" -msgstr "" - -#: preparing.xml:6 -#, no-c-format -#. Tag: para -msgid "This chapter deals with the preparation for installing Debian before you even boot the installer. This includes backing up your data, gathering information about your hardware, and locating any necessary information." -msgstr "" - -#: preparing.xml:19 -#, no-c-format -#. Tag: title -msgid "Overview of the Installation Process" -msgstr "" - -#: preparing.xml:20 -#, no-c-format -#. Tag: para -msgid "First, just a note about re-installations. With Debian, a circumstance that will require a complete re-installation of your system is very rare; perhaps mechanical failure of the hard disk would be the most common case." -msgstr "" - -#: preparing.xml:27 -#, no-c-format -#. Tag: para -msgid "Many common operating systems may require a complete installation to be performed when critical failures take place or for upgrades to new OS versions. Even if a completely new installation isn't required, often the programs you use must be re-installed to operate properly in the new OS." -msgstr "" - -#: preparing.xml:35 -#, no-c-format -#. Tag: para -msgid "Under &debian;, it is much more likely that your OS can be repaired rather than replaced if things go wrong. Upgrades never require a wholesale installation; you can always upgrade in-place. And the programs are almost always compatible with successive OS releases. If a new program version requires newer supporting software, the Debian packaging system ensures that all the necessary software is automatically identified and installed. The point is, much effort has been put into avoiding the need for re-installation, so think of it as your very last option. The installer is <emphasis>not</emphasis> designed to re-install over an existing system." -msgstr "" - -#: preparing.xml:48 -#, no-c-format -#. Tag: para -msgid "Here's a road map for the steps you will take during the installation process." -msgstr "" - -#: preparing.xml:56 -#, no-c-format -#. Tag: para -msgid "Back up any existing data or documents on the hard disk where you plan to install." -msgstr "" - -#: preparing.xml:62 -#, no-c-format -#. Tag: para -msgid "Gather information about your computer and any needed documentation, before starting the installation." -msgstr "" - -#: preparing.xml:68 -#, no-c-format -#. Tag: para -msgid "Create partition-able space for Debian on your hard disk." -msgstr "" - -#: preparing.xml:73 -#, no-c-format -#. Tag: para -msgid "Locate and/or download the installer software and any specialized driver files your machine requires (except Debian CD users)." -msgstr "" - -#: preparing.xml:79 -#, no-c-format -#. Tag: para -msgid "Set up boot tapes/floppies/USB sticks, or place boot files (most Debian CD users can boot from one of the CDs)." -msgstr "" - -#: preparing.xml:85 -#, no-c-format -#. Tag: para -msgid "Boot the installation system." -msgstr "" - -#: preparing.xml:90 -#, no-c-format -#. Tag: para -msgid "Select installation language." -msgstr "" - -#: preparing.xml:95 -#, no-c-format -#. Tag: para -msgid "Activate the ethernet network connection, if available." -msgstr "" - -#: preparing.xml:101 -#, no-c-format -#. Tag: para -msgid "Configure one network interface." -msgstr "" - -#: preparing.xml:106 -#, no-c-format -#. Tag: para -msgid "Open a ssh connection to the new system." -msgstr "" - -#: preparing.xml:111 -#, no-c-format -#. Tag: para -msgid "Attach one or more DASDs (Direct Access Storage Device)." -msgstr "" - -#: preparing.xml:117 -#, no-c-format -#. Tag: para -msgid "Create and mount the partitions on which Debian will be installed." -msgstr "" - -#: preparing.xml:122 -#, no-c-format -#. Tag: para -msgid "Watch the automatic download/install/setup of the <firstterm>base system</firstterm>." -msgstr "" - -#: preparing.xml:128 -#, no-c-format -#. Tag: para -msgid "Install a <firstterm>boot loader</firstterm> which can start up &debian; and/or your existing system." -msgstr "" - -#: preparing.xml:134 -#, no-c-format -#. Tag: para -msgid "Load the newly installed system for the first time." -msgstr "" - -#: preparing.xml:141 -#, no-c-format -#. Tag: para -msgid "If you have problems during the installation, it helps to know which packages are involved in which steps. Introducing the leading software actors in this installation drama:" -msgstr "" - -#: preparing.xml:147 -#, no-c-format -#. Tag: para -msgid "The installer software, <classname>debian-installer</classname>, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses <classname>dhcp-client</classname> to set up the network connection, and runs <classname>debootstrap</classname> to install the base system packages. Many more actors play smaller parts in this process, but <classname>debian-installer</classname> has completed its task when you load the new system for the first time." -msgstr "" - -#: preparing.xml:157 -#, no-c-format -#. Tag: para -msgid "To tune the system to your needs, <classname>tasksel</classname> allows you to choose to install various predefined bundles of software like a Web server or a Desktop environment." -msgstr "" - -#: preparing.xml:163 -#, no-c-format -#. Tag: para -msgid "When <classname>debian-installer</classname> finishes, before the first system load, you have only a very basic command line driven system. The graphical interface which displays windows on your monitor will not be installed unless you select it with <classname>tasksel</classname>. It's optional because many &debian; systems are servers which don't really have any need for a graphical user interface to do their job." -msgstr "" - -#: preparing.xml:172 -#, no-c-format -#. Tag: para -msgid "Just be aware that the X system is completely separate from <classname>debian-installer</classname>, and in fact is much more complicated. Installation and trouble shooting of the X window installation is not within the scope of this manual." -msgstr "" - -#: preparing.xml:188 -#, no-c-format -#. Tag: title -msgid "Back Up Your Existing Data!" -msgstr "" - -#: preparing.xml:189 -#, no-c-format -#. Tag: para -msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system has been installed on your computer, it's quite likely you will need to re-partition your disk to make room for &debian;. Anytime you partition your disk, you should count on losing everything on the disk, no matter what program you use to do it. The programs used in installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work." -msgstr "" - -#: preparing.xml:202 -#, no-c-format -#. Tag: para -msgid "If you are creating a multi-boot system, make sure that you have the distribution media of any other present operating systems on hand. Especially if you repartition your boot drive, you might find that you have to reinstall your operating system's boot loader, or in many cases the whole operating system itself and all files on the affected partitions." -msgstr "" - -#: preparing.xml:213 -#, no-c-format -#. Tag: para -msgid "With the exception of the BVM and Motorola VMEbus computers, the only supported installation method for m68k systems is booting from a local disk or floppy using an AmigaOS/TOS/MacOS-based bootstrap, for these machines you will need the original operating system in order to boot Linux. In order to boot Linux on the BVM and Motorola VMEbus machines you will need the <quote>BVMBug</quote> or <quote>16xBug</quote> boot ROMs." -msgstr "" - -#: preparing.xml:231 -#, no-c-format -#. Tag: title -msgid "Information You Will Need" -msgstr "" - -#: preparing.xml:234 -#, no-c-format -#. Tag: title -msgid "Documentation" -msgstr "" - -#: preparing.xml:237 -#, no-c-format -#. Tag: title -msgid "Installation Manual" -msgstr "" - -#: preparing.xml:239 -#, no-c-format -#. Tag: para -msgid "This document you are now reading, in plain ASCII, HTML or PDF format." -msgstr "" - -#: preparing.xml:245 -#, no-c-format -#. Tag: itemizedlist -msgid "&list-install-manual-files;" -msgstr "" - -#: preparing.xml:251 -#, no-c-format -#. Tag: para -msgid "The document you are now reading, which is the official version of the Installation Guide for the &releasename; release of Debian; available in <ulink url=\"&url-release-area;/installmanual\">various formats and translations</ulink>." -msgstr "" - -#: preparing.xml:260 -#, no-c-format -#. Tag: para -msgid "The document you are now reading, which is a development version of the Installation Guide for the next release of Debian; available in <ulink url=\"&url-d-i-alioth-manual;\">various formats and translations</ulink>." -msgstr "" - -#: preparing.xml:272 -#, no-c-format -#. Tag: title -msgid "Hardware documentation" -msgstr "" - -#: preparing.xml:273 -#, no-c-format -#. Tag: para -msgid "Often contains useful information on configuring or using your hardware." -msgstr "" - -#: preparing.xml:284 -#, no-c-format -#. Tag: ulink -msgid "Linux Hardware Compatibility HOWTO" -msgstr "" - -#: preparing.xml:290 -#, no-c-format -#. Tag: ulink -msgid "Linux/m68k FAQ" -msgstr "" - -#: preparing.xml:296 -#, no-c-format -#. Tag: ulink -msgid "Linux/Alpha FAQ" -msgstr "" - -#: preparing.xml:302 -#, no-c-format -#. Tag: ulink -msgid "Linux for SPARC Processors FAQ" -msgstr "" - -#: preparing.xml:308 -#, no-c-format -#. Tag: ulink -msgid "Linux/Mips website" -msgstr "" - -#: preparing.xml:317 -#, no-c-format -#. Tag: title -msgid "&arch-title; Hardware References" -msgstr "" - -#: preparing.xml:318 -#, no-c-format -#. Tag: para -msgid "Installation instructions and device drivers (DASD, XPRAM, Console, tape, z90 crypto, chandev, network) for Linux on &arch-title; using kernel 2.4" -msgstr "" - -#: preparing.xml:330 -#, no-c-format -#. Tag: ulink -msgid "Device Drivers and Installation Commands" -msgstr "" - -#: preparing.xml:335 -#, no-c-format -#. Tag: para -msgid "IBM Redbook describing how Linux can be combined with z/VM on zSeries and &arch-title; hardware." -msgstr "" - -#: preparing.xml:345 -#, no-c-format -#. Tag: ulink -msgid "Linux for &arch-title;" -msgstr "" - -#: preparing.xml:351 -#, no-c-format -#. Tag: para -msgid "IBM Redbook describing the Linux distributions available for the mainframe. It has no chapter about Debian but the basic installation concepts are the same across all &arch-title; distributions." -msgstr "" - -#: preparing.xml:362 -#, no-c-format -#. Tag: ulink -msgid "Linux for IBM eServer zSeries and &arch-title;: Distributions" -msgstr "" - -#: preparing.xml:372 -#, no-c-format -#. Tag: title -msgid "Finding Sources of Hardware Information" -msgstr "" - -#: preparing.xml:373 -#, no-c-format -#. Tag: para -msgid "In many cases, the installer will be able to automatically detect your hardware. But to be prepared, we do recommend familiarizing yourself with your hardware before the install." -msgstr "" - -#: preparing.xml:379 -#, no-c-format -#. Tag: para -msgid "Hardware information can be gathered from:" -msgstr "" - -#: preparing.xml:386 -#, no-c-format -#. Tag: para -msgid "The manuals that come with each piece of hardware." -msgstr "" - -#: preparing.xml:391 -#, no-c-format -#. Tag: para -msgid "The BIOS setup screens of your computer. You can view these screens when you start your computer by pressing a combination of keys. Check your manual for the combination. Often, it is the <keycap>Delete</keycap> key." -msgstr "" - -#: preparing.xml:398 -#, no-c-format -#. Tag: para -msgid "The cases and boxes for each piece of hardware." -msgstr "" - -#: preparing.xml:404 -#, no-c-format -#. Tag: para -msgid "The System window in the Windows Control Panel." -msgstr "" - -#: preparing.xml:410 -#, no-c-format -#. Tag: para -msgid "System commands or tools in another operating system, including file manager displays. This source is especially useful for information about RAM and hard drive memory." -msgstr "" - -#: preparing.xml:417 -#, no-c-format -#. Tag: para -msgid "Your system administrator or Internet Service Provider. These sources can tell you the settings you need to set up your networking and e-mail." -msgstr "" - -#: preparing.xml:429 -#, no-c-format -#. Tag: title -msgid "Hardware Information Needed for an Install" -msgstr "" - -#: preparing.xml:433 -#, no-c-format -#. Tag: entry -msgid "Hardware" -msgstr "" - -#: preparing.xml:433 -#, no-c-format -#. Tag: entry -msgid "Information You Might Need" -msgstr "" - -#: preparing.xml:439 -#, no-c-format -#. Tag: entry -msgid "Hard Drives" -msgstr "" - -#: preparing.xml:440 -#, no-c-format -#. Tag: entry -msgid "How many you have." -msgstr "" - -#: preparing.xml:442 -#, no-c-format -#. Tag: entry -msgid "Their order on the system." -msgstr "" - -#: preparing.xml:444 -#, no-c-format -#. Tag: entry -msgid "Whether IDE or SCSI (most computers are IDE)." -msgstr "" - -#: preparing.xml:447 -#, no-c-format -#. Tag: entry -msgid "Whether IDE or SCSI (most m68k computers are SCSI)." -msgstr "" - -#: preparing.xml:449 preparing.xml:501 -#, no-c-format -#. Tag: entry -msgid "Available free space." -msgstr "" - -#: preparing.xml:450 -#, no-c-format -#. Tag: entry -msgid "Partitions." -msgstr "" - -#: preparing.xml:452 -#, no-c-format -#. Tag: entry -msgid "Partitions where other operating systems are installed." -msgstr "" - -#: preparing.xml:456 -#, no-c-format -#. Tag: entry -msgid "Monitor" -msgstr "" - -#: preparing.xml:457 preparing.xml:477 preparing.xml:483 preparing.xml:489 -#, no-c-format -#. Tag: entry -msgid "Model and manufacturer." -msgstr "" - -#: preparing.xml:459 -#, no-c-format -#. Tag: entry -msgid "Resolutions supported." -msgstr "" - -#: preparing.xml:460 -#, no-c-format -#. Tag: entry -msgid "Horizontal refresh rate." -msgstr "" - -#: preparing.xml:461 -#, no-c-format -#. Tag: entry -msgid "Vertical refresh rate." -msgstr "" - -#: preparing.xml:463 -#, no-c-format -#. Tag: entry -msgid "Color depth (number of colors) supported." -msgstr "" - -#: preparing.xml:465 -#, no-c-format -#. Tag: entry -msgid "Screen size." -msgstr "" - -#: preparing.xml:468 -#, no-c-format -#. Tag: entry -msgid "Mouse" -msgstr "" - -#: preparing.xml:469 -#, no-c-format -#. Tag: entry -msgid "Type: serial, PS/2, or USB." -msgstr "" - -#: preparing.xml:471 -#, no-c-format -#. Tag: entry -msgid "Port." -msgstr "" - -#: preparing.xml:472 -#, no-c-format -#. Tag: entry -msgid "Manufacturer." -msgstr "" - -#: preparing.xml:473 -#, no-c-format -#. Tag: entry -msgid "Number of buttons." -msgstr "" - -#: preparing.xml:476 preparing.xml:504 -#, no-c-format -#. Tag: entry -msgid "Network" -msgstr "" - -#: preparing.xml:479 preparing.xml:505 -#, no-c-format -#. Tag: entry -msgid "Type of adapter." -msgstr "" - -#: preparing.xml:482 -#, no-c-format -#. Tag: entry -msgid "Printer" -msgstr "" - -#: preparing.xml:485 -#, no-c-format -#. Tag: entry -msgid "Printing resolutions supported." -msgstr "" - -#: preparing.xml:488 -#, no-c-format -#. Tag: entry -msgid "Video Card" -msgstr "" - -#: preparing.xml:491 -#, no-c-format -#. Tag: entry -msgid "Video RAM available." -msgstr "" - -#: preparing.xml:493 -#, no-c-format -#. Tag: entry -msgid "Resolutions and color depths supported (these should be checked against your monitor's capabilities)." -msgstr "" - -#: preparing.xml:498 -#, no-c-format -#. Tag: entry -msgid "DASD" -msgstr "" - -#: preparing.xml:499 -#, no-c-format -#. Tag: entry -msgid "Device number(s)." -msgstr "" - -#: preparing.xml:507 -#, no-c-format -#. Tag: entry -msgid "Device numbers." -msgstr "" - -#: preparing.xml:508 -#, no-c-format -#. Tag: entry -msgid "Relative adapter number for OSA cards." -msgstr "" - -#: preparing.xml:516 -#, no-c-format -#. Tag: title -msgid "Hardware Compatibility" -msgstr "" - -#: preparing.xml:518 -#, no-c-format -#. Tag: para -msgid "Many brand name products work without trouble on Linux. Moreover, hardware for Linux is improving daily. However, Linux still does not run as many different types of hardware as some operating systems." -msgstr "" - -#: preparing.xml:524 -#, no-c-format -#. Tag: para -msgid "In particular, Linux usually cannot run hardware that requires a running version of Windows to work." -msgstr "" - -#: preparing.xml:529 -#, no-c-format -#. Tag: para -msgid "Although some Windows-specific hardware can be made to run on Linux, doing so usually requires extra effort. In addition, Linux drivers for Windows-specific hardware are usually specific to one Linux kernel. Therefore, they can quickly become obsolete." -msgstr "" - -#: preparing.xml:536 -#, no-c-format -#. Tag: para -msgid "So called win-modems are the most common type of this hardware. However, printers and other equipment may also be Windows-specific." -msgstr "" - -#: preparing.xml:541 -#, no-c-format -#. Tag: para -msgid "You can check hardware compatibility by:" -msgstr "" - -#: preparing.xml:546 -#, no-c-format -#. Tag: para -msgid "Checking manufacturers' web sites for new drivers." -msgstr "" - -#: preparing.xml:551 -#, no-c-format -#. Tag: para -msgid "Looking at web sites or manuals for information about emulation. Lesser known brands can sometimes use the drivers or settings for better-known ones." -msgstr "" - -#: preparing.xml:558 -#, no-c-format -#. Tag: para -msgid "Checking hardware compatibility lists for Linux on web sites dedicated to your architecture." -msgstr "" - -#: preparing.xml:564 -#, no-c-format -#. Tag: para -msgid "Searching the Internet for other users' experiences." -msgstr "" - -#: preparing.xml:575 -#, no-c-format -#. Tag: title -msgid "Network Settings" -msgstr "" - -#: preparing.xml:577 -#, no-c-format -#. Tag: para -msgid "If your computer is connected to a network 24 hours a day (i.e., an Ethernet or equivalent connection — not a PPP connection), you should ask your network's system administrator for this information." -msgstr "" - -#: preparing.xml:584 -#, no-c-format -#. Tag: para -msgid "Your host name (you may be able to decide this on your own)." -msgstr "" - -#: preparing.xml:589 -#, no-c-format -#. Tag: para -msgid "Your domain name." -msgstr "" - -#: preparing.xml:594 -#, no-c-format -#. Tag: para -msgid "Your computer's IP address." -msgstr "" - -#: preparing.xml:599 -#, no-c-format -#. Tag: para -msgid "The netmask to use with your network." -msgstr "" - -#: preparing.xml:604 -#, no-c-format -#. Tag: para -msgid "The IP address of the default gateway system you should route to, if your network <emphasis>has</emphasis> a gateway." -msgstr "" - -#: preparing.xml:610 -#, no-c-format -#. Tag: para -msgid "The system on your network that you should use as a DNS (Domain Name Service) server." -msgstr "" - -#: preparing.xml:618 -#, no-c-format -#. Tag: para -msgid "On the other hand, if your administrator tells you that a DHCP server is available and is recommended, then you don't need this information because the DHCP server will provide it directly to your computer during the installation process." -msgstr "" - -#: preparing.xml:625 -#, no-c-format -#. Tag: para -msgid "If you use a wireless network, you should also find out:" -msgstr "" - -#: preparing.xml:630 -#, no-c-format -#. Tag: para -msgid "ESSID of your wireless network." -msgstr "" - -#: preparing.xml:635 -#, no-c-format -#. Tag: para -msgid "WEP security key (if applicable)." -msgstr "" - -#: preparing.xml:652 -#, no-c-format -#. Tag: title -msgid "Meeting Minimum Hardware Requirements" -msgstr "" - -#: preparing.xml:653 -#, no-c-format -#. Tag: para -msgid "Once you have gathered information about your computer's hardware, check that your hardware will let you do the type of installation that you want to do." -msgstr "" - -#: preparing.xml:659 -#, no-c-format -#. Tag: para -msgid "Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions." -msgstr "" - -#: preparing.xml:665 -#, no-c-format -#. Tag: para -msgid "A Pentium 100 is the minimum recommended for desktop systems, and a Pentium II-300 for a Server." -msgstr "" - -#: preparing.xml:670 -#, no-c-format -#. Tag: para -msgid "A 68030 or better processor is recommended for m68k installs. You may get by with a little less drive space than shown." -msgstr "" - -#: preparing.xml:675 -#, no-c-format -#. Tag: para -msgid "Any OldWorld or NewWorld PowerPC can serve well as a Desktop System. For servers, a minimum 132-Mhz machine is recommended." -msgstr "" - -#: preparing.xml:684 -#, no-c-format -#. Tag: title -msgid "Recommended Minimum System Requirements" -msgstr "" - -#: preparing.xml:688 -#, no-c-format -#. Tag: entry -msgid "Install Type" -msgstr "" - -#: preparing.xml:688 -#, no-c-format -#. Tag: entry -msgid "<entry>RAM</entry>" -msgstr "" - -#: preparing.xml:688 -#, no-c-format -#. Tag: entry -msgid "Hard Drive" -msgstr "" - -#: preparing.xml:694 -#, no-c-format -#. Tag: entry -msgid "No desktop" -msgstr "" - -#: preparing.xml:695 -#, no-c-format -#. Tag: entry -msgid "24 megabytes" -msgstr "" - -#: preparing.xml:696 -#, no-c-format -#. Tag: entry -msgid "450 megabytes" -msgstr "" - -#: preparing.xml:698 -#, no-c-format -#. Tag: entry -msgid "With Desktop" -msgstr "" - -#: preparing.xml:699 -#, no-c-format -#. Tag: entry -msgid "64 megabytes" -msgstr "" - -#: preparing.xml:700 -#, no-c-format -#. Tag: entry -msgid "1 gigabyte" -msgstr "" - -#: preparing.xml:702 -#, no-c-format -#. Tag: entry -msgid "Server" -msgstr "" - -#: preparing.xml:703 -#, no-c-format -#. Tag: entry -msgid "128 megabytes" -msgstr "" - -#: preparing.xml:704 -#, no-c-format -#. Tag: entry -msgid "4 gigabytes" -msgstr "" - -#: preparing.xml:709 -#, no-c-format -#. Tag: para -msgid "Here is a sampling of some common Debian system configurations. You can also get an idea of the disk space used by related groups of programs by referring to <xref linkend=\"tasksel-size-list\"/>." -msgstr "" - -#: preparing.xml:719 -#, no-c-format -#. Tag: term -msgid "Standard Server" -msgstr "" - -#: preparing.xml:720 -#, no-c-format -#. Tag: para -msgid "This is a small server profile, useful for a stripped down server which does not have a lot of niceties for shell users. It includes an FTP server, a web server, DNS, NIS, and POP. For these 100MB of disk space would suffice, and then you would need to add space for any data you serve up." -msgstr "" - -#: preparing.xml:732 -#, no-c-format -#. Tag: term -msgid "Desktop" -msgstr "" - -#: preparing.xml:733 -#, no-c-format -#. Tag: para -msgid "A standard desktop box, including the X window system, full desktop environments, sound, editors, etc. You'll need about 2GB using the standard desktop task, though it can be done in far less." -msgstr "" - -#: preparing.xml:743 -#, no-c-format -#. Tag: term -msgid "Work Console" -msgstr "" - -#: preparing.xml:744 -#, no-c-format -#. Tag: para -msgid "A more stripped-down user machine, without the X window system or X applications. Possibly suitable for a laptop or mobile computer. The size is around 140MB." -msgstr "" - -#: preparing.xml:754 -#, no-c-format -#. Tag: term -msgid "Developer" -msgstr "" - -#: preparing.xml:755 -#, no-c-format -#. Tag: para -msgid "A desktop setup with all the development packages, such as Perl, C, C++, etc. Size is around 475MB. Assuming you are adding X11 and some additional packages for other uses, you should plan around 800MB for this type of machine." -msgstr "" - -#: preparing.xml:765 -#, no-c-format -#. Tag: para -msgid "Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data. Notably, the <filename>/var</filename> partition contains a lot of state information specific to Debian in addition to its regular contents like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 20MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 100MB for <filename>/var</filename>." -msgstr "" - -#: preparing.xml:789 -#, no-c-format -#. Tag: title -msgid "Pre-Partitioning for Multi-Boot Systems" -msgstr "" - -#: preparing.xml:790 -#, no-c-format -#. Tag: para -msgid "Partitioning your disk simply refers to the act of breaking up your disk into sections. Each section is then independent of the others. It's roughly equivalent to putting up walls inside a house; if you add furniture to one room it doesn't affect any other room." -msgstr "" - -#: preparing.xml:797 -#, no-c-format -#. Tag: para -msgid "Whenever this section talks about <quote>disks</quote> you should translate this into a DASD or VM minidisk in the &arch-title; world. Also a machine means an LPAR or VM guest in this case." -msgstr "" - -#: preparing.xml:803 -#, no-c-format -#. Tag: para -msgid "If you already have an operating system on your system <phrase arch=\"i386\"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> <phrase arch=\"alpha\"> (Tru64 (Digital UNIX), OpenVMS, Windows NT, FreeBSD, …) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, …) </phrase> <phrase arch=\"m68k\"> (Amiga OS, Atari TOS, Mac OS, …) </phrase> and want to stick Linux on the same disk, you will need to repartition the disk. Debian requires its own hard disk partitions. It cannot be installed on Windows or MacOS partitions. It may be able to share some partitions with other Linux systems, but that's not covered here. At the very least you will need a dedicated partition for the Debian root." -msgstr "" - -#: preparing.xml:830 -#, no-c-format -#. Tag: para -msgid "You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase arch=\"i386\">, such as fdisk or PartitionMagic</phrase><phrase arch=\"powerpc\">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch=\"m68k\">, such as HD SC Setup, HDToolBox, or SCSITool</phrase><phrase arch=\"s390\">, such as the VM diskmap</phrase>. Partitioning tools always provide a way to show existing partitions without making changes." -msgstr "" - -#: preparing.xml:840 -#, no-c-format -#. Tag: para -msgid "In general, changing a partition with a file system already on it will destroy any information there. Thus you should always make backups before doing any repartitioning. Using the analogy of the house, you would probably want to move all the furniture out of the way before moving a wall or you risk destroying it." -msgstr "" - -#: preparing.xml:850 -#, no-c-format -#. Tag: emphasis -msgid "FIXME: write about HP-UX disks?" -msgstr "" - -#: preparing.xml:852 -#, no-c-format -#. Tag: para -msgid "If your computer has more than one hard disk, you may want to dedicate one of the hard disks completely to Debian. If so, you don't need to partition that disk before booting the installation system; the installer's included partitioning program can handle the job nicely." -msgstr "" - -#: preparing.xml:859 -#, no-c-format -#. Tag: para -msgid "If your machine has only one hard disk, and you would like to completely replace the current operating system with &debian;, you also can wait to partition as part of the installation process (<xref linkend=\"partman\"/>), after you have booted the installation system. However this only works if you plan to boot the installer system from tapes, CD-ROM or files on a connected machine. Consider: if you boot from files placed on the hard disk, and then partition that same hard disk within the installation system, thus erasing the boot files, you'd better hope the installation is successful the first time around. At the least in this case, you should have some alternate means of reviving your machine like the original system's installation tapes or CDs." -msgstr "" - -#: preparing.xml:874 -#, no-c-format -#. Tag: para -msgid "If your machine already has multiple partitions, and enough space can be provided by deleting and replacing one or more of them, then you too can wait and use the Debian installer's partitioning program. You should still read through the material below, because there may be special circumstances like the order of the existing partitions within the partition map, that force you to partition before installing anyway." -msgstr "" - -#: preparing.xml:884 -#, no-c-format -#. Tag: para -msgid "If your machine has a FAT or NTFS filesystem, as used by DOS and Windows, you can wait and use Debian installer's partitioning program to resize the filesystem." -msgstr "" - -#: preparing.xml:890 -#, no-c-format -#. Tag: para -msgid "If none of the above apply, you'll need to partition your hard disk before starting the installation to create partition-able space for Debian. If some of the partitions will be owned by other operating systems, you should create those partitions using native operating system partitioning programs. We recommend that you do <emphasis>not</emphasis> attempt to create partitions for &debian; using another operating system's tools. Instead, you should just create the native operating system's partitions you will want to retain." -msgstr "" - -#: preparing.xml:902 -#, no-c-format -#. Tag: para -msgid "If you are going to install more than one operating system on the same machine, you should install all other system(s) before proceeding with Linux installation. Windows and other OS installations may destroy your ability to start Linux, or encourage you to reformat non-native partitions." -msgstr "" - -#: preparing.xml:910 -#, no-c-format -#. Tag: para -msgid "You can recover from these actions or avoid them, but installing the native system first saves you trouble." -msgstr "" - -#: preparing.xml:915 -#, no-c-format -#. Tag: para -msgid "In order for OpenFirmware to automatically boot &debian; the Linux partitions should appear before all other partitions on the disk, especially MacOS boot partitions. This should be kept in mind when pre-partitioning; you should create a Linux placeholder partition to come <emphasis>before</emphasis> the other bootable partitions on the disk. (The small partitions dedicated to Apple disk drivers are not bootable.) You can delete the placeholder with the Linux partition tools later during the actual install, and replace it with Linux partitions." -msgstr "" - -#: preparing.xml:927 -#, no-c-format -#. Tag: para -msgid "If you currently have one hard disk with one partition (a common setup for desktop computers), and you want to multi-boot the native operating system and Debian, you will need to:" -msgstr "" - -#: preparing.xml:934 -#, no-c-format -#. Tag: para -msgid "Back up everything on the computer." -msgstr "" - -#: preparing.xml:939 -#, no-c-format -#. Tag: para -msgid "Boot from the native operating system installer media such as CD-ROM or tapes. <phrase arch=\"powerpc\">When booting from a MacOS CD, hold the <keycap>c</keycap> key while booting to force the CD to become the active MacOS system.</phrase>" -msgstr "" - -#: preparing.xml:949 -#, no-c-format -#. Tag: para -msgid "Use the native partitioning tools to create native system partition(s). Leave either a place holder partition or free space for &debian;." -msgstr "" - -#: preparing.xml:956 -#, no-c-format -#. Tag: para -msgid "Install the native operating system on its new partition." -msgstr "" - -#: preparing.xml:961 -#, no-c-format -#. Tag: para -msgid "Boot back into the native system to verify everything's OK, and to download the Debian installer boot files." -msgstr "" - -#: preparing.xml:967 -#, no-c-format -#. Tag: para -msgid "Boot the Debian installer to continue installing Debian." -msgstr "" - -#: preparing.xml:981 -#, no-c-format -#. Tag: title -msgid "Partitioning in Tru64 UNIX" -msgstr "" - -#: preparing.xml:982 -#, no-c-format -#. Tag: para -msgid "Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly known as OSF/1, uses the partitioning scheme similar to the BSD <quote>disk label</quote>, which allows for up to eight partitions per disk drive. The partitions are numbered <quote>1</quote> through to <quote>8</quote> in Linux and <quote>lettered</quote> <quote>a</quote> through to <quote>h</quote> in UNIX. Linux kernels 2.2 and higher always correspond <quote>1</quote> to <quote>a</quote>, <quote>2</quote> to <quote>b</quote> and so on. For example, <filename>rz0e</filename> in Tru64 UNIX would most likely be called <filename>sda5</filename> in Linux." -msgstr "" - -#: preparing.xml:994 -#, no-c-format -#. Tag: para -msgid "Partitions in a Tru64 disk label may overlap. Moreover, if this disk will be used from Tru64, the <quote>c</quote> partition is required to span the entire disk (thus overlapping all other non-empty partitions). Under Linux this makes <filename>sda3</filename> identical to <filename>sda</filename> (<filename>sdb3</filename> to <filename>sdb</filename>, if present, and so on). However, the partman partitioning tool used by &d-i; cannot handle overlapping partitions at present. As a result, it is currently not recommended to share disks between Tru64 and Debian. Partitions on Tru64 disks can be mounted under Debian after installation has been completed." -msgstr "" - -#: preparing.xml:1007 -#, no-c-format -#. Tag: para -msgid "Another conventional requirement is for the <quote>a</quote> partition to start from the beginning of the disk, so that it always includes the boot block with the disk label. If you intend to boot Debian from that disk, you need to size it at least 2MB to fit aboot and perhaps a kernel. Note that this partition is only required for compatibility; you must not put a file system onto it, or you'll destroy data." -msgstr "" - -#: preparing.xml:1016 -#, no-c-format -#. Tag: para -msgid "It is possible, and indeed quite reasonable, to share a swap partition between UNIX and Linux. In this case it will be needed to do a <command>mkswap</command> on that partition every time the system is rebooted from UNIX into Linux, as UNIX will damage the swap signature. You may want to run <command>mkswap</command> from the Linux start-up scripts before adding swap space with <command>swapon -a</command>." -msgstr "" - -#: preparing.xml:1025 -#, no-c-format -#. Tag: para -msgid "If you want to mount UNIX partitions under Linux, note that Digital UNIX can use two different file system types, UFS and AdvFS, of which Linux only understands the former." -msgstr "" - -#: preparing.xml:1034 -#, no-c-format -#. Tag: title -msgid "Partitioning in Windows NT" -msgstr "" - -#: preparing.xml:1036 -#, no-c-format -#. Tag: para -msgid "Windows NT uses the PC-style partition table. If you are manipulating existing FAT or NTFS partitions, it is recommended that you use the native Windows NT tools (or, more conveniently, you can also repartition your disk from the AlphaBIOS setup menu). Otherwise, it is not really necessary to partition from Windows; the Linux partitioning tools will generally do a better job. Note that when you run NT, the Disk Administrator may offer you to write a <quote>harmless signature</quote> on non-Windows disks if you have any. <emphasis>Never</emphasis> let it do that, as this signature will destroy the partition information." -msgstr "" - -#: preparing.xml:1049 -#, no-c-format -#. Tag: para -msgid "If you plan to boot Linux from an ARC/AlphaBIOS/ARCSBIOS console, you will need a (small) FAT partition for MILO. 5 MB is quite sufficient. If Windows NT is installed, its 6 MB bootstrap partition can be employed for this purpose. Debian &releasename; does not support installing MILO. If you already have MILO installed on your system, or install MILO from other media, Debian can still be booted from ARC." -msgstr "" - -#: preparing.xml:1066 -#, no-c-format -#. Tag: title -msgid "Partitioning From DOS or Windows" -msgstr "" - -#: preparing.xml:1067 -#, no-c-format -#. Tag: para -msgid "If you are manipulating existing FAT or NTFS partitions, it is recommended that you either use the scheme below or native Windows or DOS tools. Otherwise, it is not really necessary to partition from DOS or Windows; the Linux partitioning tools will generally do a better job." -msgstr "" - -#: preparing.xml:1075 -#, no-c-format -#. Tag: para -msgid "But if you have a large IDE disk, and are using neither LBA addressing, overlay drivers (sometimes provided by hard disk manufacturers), nor a new (post 1998) BIOS that supports large disk access extensions, then you must locate your Debian boot partition carefully. In this case, you will have to put the boot partition into the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation). This may require that you move an existing FAT or NTFS partition." -msgstr "" - -#: preparing.xml:1089 -#, no-c-format -#. Tag: title -msgid "Lossless Repartitioning When Starting From DOS, Win-32 or OS/2" -msgstr "" - -#: preparing.xml:1092 -#, no-c-format -#. Tag: para -msgid "One of the most common installations is onto a system that already contains DOS (including Windows 3.1), Win32 (such as Windows 95, 98, Me, NT, 2000, XP), or OS/2, and it is desired to put Debian onto the same disk without destroying the previous system. Note that the installer supports resizing of FAT and NTFS filesystems as used by DOS and Windows. Simply start the installer, select the option to <menuchoice> <guimenuitem>Manually edit partition table</guimenuitem> </menuchoice>, select the partition to resize, and specify its new size. So in most cases you should not need to use the method described below." -msgstr "" - -#: preparing.xml:1104 -#, no-c-format -#. Tag: para -msgid "Before going any further, you should have decided how you will be dividing up the disk. The method in this section will only split a partition into two pieces. One will contain the original OS and the other will be used for Debian. During the installation of Debian, you will be given the opportunity to use the Debian portion of the disk as you see fit, i.e., as swap or as a file system." -msgstr "" - -#: preparing.xml:1113 -#, no-c-format -#. Tag: para -msgid "The idea is to move all the data on the partition to the beginning, before changing the partition information, so that nothing will be lost. It is important that you do as little as possible between the data movement and repartitioning to minimize the chance of a file being written near the end of the partition as this will decrease the amount of space you can take from the partition." -msgstr "" - -#: preparing.xml:1122 -#, no-c-format -#. Tag: para -msgid "The first thing needed is a copy of <command>fips</command> which is available in the <filename>tools/</filename> directory on your nearest Debian mirror. Unzip the archive and copy the files <filename>RESTORRB.EXE</filename>, <filename>FIPS.EXE</filename> and <filename>ERRORS.TXT</filename> to a bootable floppy. A bootable floppy can be created using the command <filename>sys a:</filename> under DOS. <command>fips</command> comes with very good documentation which you may want to read. You will definitely need to read the documentation if you use a disk compression driver or a disk manager. Create the disk and read the documentation <emphasis>before</emphasis> you defragment the disk." -msgstr "" - -#: preparing.xml:1135 -#, no-c-format -#. Tag: para -msgid "The next thing needed is to move all the data to the beginning of the partition. <command>defrag</command>, which comes standard with DOS 6.0 and later, can easily do the job. See the <command>fips</command> documentation for a list of other software that may do the trick. Note that if you have Windows 9x, you must run <command>defrag</command> from there, since DOS doesn't understand VFAT, which is used to support for long filenames, used in Windows 95 and higher." -msgstr "" - -#: preparing.xml:1145 -#, no-c-format -#. Tag: para -msgid "After running the defragmenter (which can take a while on a large disk), reboot with the <command>fips</command> disk you created in the floppy drive. Simply type <filename>a:\\fips</filename> and follow the directions." -msgstr "" - -#: preparing.xml:1151 -#, no-c-format -#. Tag: para -msgid "Note that there are many other partition managers out there, in case <command>fips</command> doesn't do the trick for you." -msgstr "" - -#: preparing.xml:1159 -#, no-c-format -#. Tag: title -msgid "Partitioning for DOS" -msgstr "" - -#: preparing.xml:1161 -#, no-c-format -#. Tag: para -msgid "If you are partitioning for DOS drives, or changing the size of DOS partitions, using Linux tools, many people experience problems working with the resulting FAT partitions. For instance, some have reported slow performance, consistent problems with <command>scandisk</command>, or other weird errors in DOS or Windows." -msgstr "" - -#: preparing.xml:1169 -#, no-c-format -#. Tag: para -msgid "Apparently, whenever you create or resize a partition for DOS use, it's a good idea to fill the first few sectors with zeros. You should do this prior to running DOS's <command>format</command> command by executing the following command from Linux:" -msgstr "" - -#: preparing.xml:1176 -#, no-c-format -#. Tag: screen -msgid "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4" -msgstr "" - -#: preparing.xml:1187 -#, no-c-format -#. Tag: title -msgid "Partitioning in AmigaOS" -msgstr "" - -#: preparing.xml:1188 -#, no-c-format -#. Tag: para -msgid "If you are running AmigaOS, you can use the <command>HDToolBox</command> program to adjust your native partitions prior to installation." -msgstr "" - -#: preparing.xml:1196 -#, no-c-format -#. Tag: title -msgid "Partitioning in Atari TOS" -msgstr "" - -#: preparing.xml:1197 -#, no-c-format -#. Tag: para -msgid "Atari partition IDs are three ASCII characters, use <quote>LNX</quote> for data and <quote>SWP</quote> for swap partitions. If using the low memory installation method, a small Minix partition is also needed (about 2 MB), for which the partition ID is <quote>MNX</quote>. Failure to set the appropriate partition IDs not only prevents the Debian installation process from recognizing the partitions, but also results in TOS attempting to use the Linux partitions, which confuses the hard disk driver and renders the whole disk inaccessible." -msgstr "" - -#: preparing.xml:1208 -#, no-c-format -#. Tag: para -msgid "There are a multitude of third party partitioning tools available (the Atari <command>harddisk</command> utility doesn't permit changing the partition ID); this manual cannot give detailed descriptions for all of them. The following description covers <command>SCSITool</command> (from Hard+Soft GmBH)." -msgstr "" - -#: preparing.xml:1217 -#, no-c-format -#. Tag: para -msgid "Start <command>SCSITool</command> and select the disk you want to partition (<guimenu>Disk</guimenu> menu, item <guimenuitem>select</guimenuitem>)." -msgstr "" - -#: preparing.xml:1223 -#, no-c-format -#. Tag: para -msgid "From the <guimenu>Partition</guimenu> menu, select either <guimenuitem>New</guimenuitem> to add new partitions or change the existing partition sizes, or <guimenuitem>Change</guimenuitem> to change one specific partition. Unless you have already created partitions with the right sizes and only want to change the partition ID, <guimenuitem>New</guimenuitem> is probably the best choice." -msgstr "" - -#: preparing.xml:1233 -#, no-c-format -#. Tag: para -msgid "For the <guimenuitem>New</guimenuitem> choice, select <guilabel>existing</guilabel> in the dialog box prompting the initial settings. The next window shows a list of existing partitions which you can adjust using the scroll buttons, or by clicking in the bar graphs. The first column in the partition list is the partition type; just click on the text field to edit it. When you are finished changing partition settings, save the changes by leaving the window with the <guibutton>OK</guibutton> button." -msgstr "" - -#: preparing.xml:1245 -#, no-c-format -#. Tag: para -msgid "For the <guimenuitem>Change</guimenuitem> option, select the partition to change in the selection list, and select <guilabel>other systems</guilabel> in the dialog box. The next window lists detailed information about the location of this partition, and lets you change the partition ID. Save changes by leaving the window with the <guibutton>OK</guibutton> button." -msgstr "" - -#: preparing.xml:1255 -#, no-c-format -#. Tag: para -msgid "Write down the Linux names for each of the partitions you created or changed for use with Linux — see <xref linkend=\"device-names\"/>." -msgstr "" - -#: preparing.xml:1261 -#, no-c-format -#. Tag: para -msgid "Quit <command>SCSITool</command> using the <guimenuitem>Quit</guimenuitem> item from the <guimenu>File</guimenu> menu. The computer will reboot to make sure the changed partition table is used by TOS. If you changed any TOS/GEM partitions, they will be invalidated and have to be reinitialized (we told you to back up everything on the disk, didn't we?)." -msgstr "" - -#: preparing.xml:1273 -#, no-c-format -#. Tag: para -msgid "There is a partitioning tool for Linux/m68k called <command>atari-fdisk</command> in the installation system, but for now we recommend you partition your disk using a TOS partition editor or some disk tool. If your partition editor doesn't have an option to edit the partition type, you can do this crucial step at a later stage (from the booted temporary install RAMdisk). <command>SCSITool</command> is only one of the partition editors we know of which supports selection of arbitrary partition types. There may be others; select the tool that suits your needs." -msgstr "" - -#: preparing.xml:1288 -#, no-c-format -#. Tag: title -msgid "Partitioning in MacOS" -msgstr "" - -#: preparing.xml:1289 -#, no-c-format -#. Tag: para -msgid "Partitioning tools for Macintosh tested include <command>pdisk</command>, <command>HD SC Setup</command> 7.3.5 (Apple), <command>HDT</command> 1.8 (FWB), <command>SilverLining</command> (LaCie), and <command>DiskTool</command> (Tim Endres, GPL). Full versions are required for <command>HDT</command> and <command>SilverLining</command>. The Apple tool requires a patch in order to recognize third-party disks (a description on how to patch <command>HD SC Setup</command> using <command>ResEdit</command> can be found at <ulink url=\"http://www.euronet.nl/users/ernstoud/patch.html\"></ulink>)." -msgstr "" - -#: preparing.xml:1300 -#, no-c-format -#. Tag: para -msgid "For IDE based Macs, you need to use <command>Apple Drive Setup</command> to create empty space for the Linux partitions, and complete the partitioning under Linux, or use the MacOS version of pdisk available from the MkLinux FTP server." -msgstr "" - -#: preparing.xml:1316 -#, no-c-format -#. Tag: title -msgid "Partitioning from SunOS" -msgstr "" - -#: preparing.xml:1318 -#, no-c-format -#. Tag: para -msgid "It's perfectly fine to partition from SunOS; in fact, if you intend to run both SunOS and Debian on the same machine, it is recommended that you partition using SunOS prior to installing Debian. The Linux kernel understands Sun disk labels, so there are no problems there. Just make sure you leave room for the Debian root partition within the first 1GB area of the boot disk. You can also place the kernel image on a UFS partition if that is easier than putting the root partition there. SILO supports booting Linux and SunOS from either EXT2 (Linux), UFS (SunOS), romfs and iso9660 (CDROM) partitions." -msgstr "" - -#: preparing.xml:1333 -#, no-c-format -#. Tag: title -msgid "Partitioning from Linux or another OS" -msgstr "" - -#: preparing.xml:1335 -#, no-c-format -#. Tag: para -msgid "Whatever system you are using to partition, make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</keycap> key is used to create Sun disk labels. You only need to do this on drives that do not already have a Sun disk label. If you are using a drive that was previously formatted using a PC (or other architecture) you must create a new disk label, or problems with the disk geometry will most likely occur." -msgstr "" - -#: preparing.xml:1347 -#, no-c-format -#. Tag: para -msgid "You will probably be using <command>SILO</command> as your boot loader (the small program which runs the operating system kernel). <command>SILO</command> has certain requirements for partition sizes and location; see <xref linkend=\"partitioning\"/>." -msgstr "" - -#: preparing.xml:1362 -#, no-c-format -#. Tag: title -msgid "MacOS/OSX Partitioning" -msgstr "" - -#: preparing.xml:1364 -#, no-c-format -#. Tag: para -msgid "The <application>Apple Drive Setup</application> application can be found in the <filename>Utilities</filename> folder on the MacOS CD. It will not adjust existing partitions; it is limited to partitioning the entire disk at once. The disk driver partitions don't show up in <application>Drive Setup</application>." -msgstr "" - -#: preparing.xml:1371 -#, no-c-format -#. Tag: para -msgid "Remember to create a placeholder partition for GNU/Linux, preferably positioned first in the disk layout. it doesn't matter what type it is, it will be deleted and replaced later inside the &debian; installer." -msgstr "" - -#: preparing.xml:1377 -#, no-c-format -#. Tag: para -msgid "If you are planning to install both MacOS 9 and OS X, it is best to create separate partitions for OS 9 and OS X. If they are installed on the same partition, <application>Startup Disk</application> (and reboot) must be used to select between the two; the choice between the two systems can't be made at boot time. With separate partitions, separate options for OS 9 and OS X will appear when holding the <keycap>option</keycap> key at boot time, and separate options can be installed in the <application>yaboot</application> boot menu as well. Also, Startup Disk will de-bless all other mountable partitions, which can affect GNU/Linux booting. Both OS 9 and OS X partitions will be accessible from either OS 9 or OS X." -msgstr "" - -#: preparing.xml:1390 -#, no-c-format -#. Tag: para -msgid "GNU/Linux is unable to access information on UFS partitions, but does support HFS+ (aka MacOS Extended) partitions. OS X requires one of these two types for its boot partition. MacOS 9 can be installed on either HFS (aka MacOS Standard) or HFS+. To share information between the MacOS and GNU/Linux systems, an exchange partition is handy. HFS, HFS+ and MS-DOS FAT partitions are supported by both MacOS and Linux." -msgstr "" - -#: preparing.xml:1410 -#, no-c-format -#. Tag: title -msgid "Pre-Installation Hardware and Operating System Setup" -msgstr "" - -#: preparing.xml:1411 -#, no-c-format -#. Tag: para -msgid "This section will walk you through pre-installation hardware setup, if any, that you will need to do prior to installing Debian. Generally, this involves checking and possibly changing firmware settings for your system. The <quote>firmware</quote> is the core software used by the hardware; it is most critically invoked during the bootstrap process (after power-up). Known hardware issues affecting the reliability of &debian; on your system are also highlighted." -msgstr "" - -#: preparing.xml:1428 -#, no-c-format -#. Tag: title -msgid "Invoking the BIOS Set-Up Menu" -msgstr "" - -#: preparing.xml:1430 -#, no-c-format -#. Tag: para -msgid "BIOS provides the basic functions needed to boot your machine to allow your operating system to access your hardware. Your system probably provides a BIOS set-up menu, which is used to configure the BIOS. Before installing, you <emphasis>must</emphasis> ensure that your BIOS is setup correctly; not doing so can lead to intermittent crashes or an inability to install Debian." -msgstr "" - -#: preparing.xml:1439 -#, no-c-format -#. Tag: para -msgid "The rest of this section is lifted from the <ulink url=\"&url-pc-hw-faq;\"></ulink>, answering the question, <quote>How do I enter the CMOS configuration menu?</quote>. How you access the BIOS (or <quote>CMOS</quote>) configuration menu depends on who wrote your BIOS software:" -msgstr "" - -#: preparing.xml:1453 -#, no-c-format -#. Tag: term -msgid "AMI BIOS" -msgstr "" - -#: preparing.xml:1454 -#, no-c-format -#. Tag: para -msgid "<keycap>Delete</keycap> key during the POST (power on self test)" -msgstr "" - -#: preparing.xml:1462 -#, no-c-format -#. Tag: term -msgid "Award BIOS" -msgstr "" - -#: preparing.xml:1463 -#, no-c-format -#. Tag: para -msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo>, or <keycap>Delete</keycap> key during the POST" -msgstr "" - -#: preparing.xml:1472 -#, no-c-format -#. Tag: term -msgid "DTK BIOS" -msgstr "" - -#: preparing.xml:1473 -#, no-c-format -#. Tag: para -msgid "<keycap>Esc</keycap> key during the POST" -msgstr "" - -#: preparing.xml:1480 -#, no-c-format -#. Tag: term -msgid "IBM PS/2 BIOS" -msgstr "" - -#: preparing.xml:1481 -#, no-c-format -#. Tag: para -msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap> </keycombo> after <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Delete</keycap> </keycombo>" -msgstr "" - -#: preparing.xml:1495 -#, no-c-format -#. Tag: term -msgid "Phoenix BIOS" -msgstr "" - -#: preparing.xml:1496 -#, no-c-format -#. Tag: para -msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo> or <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>S</keycap> </keycombo> or <keycap>F1</keycap>" -msgstr "" - -#: preparing.xml:1512 -#, no-c-format -#. Tag: para -msgid "Information on invoking other BIOS routines can be found in <ulink url=\"&url-invoking-bios-info;\"></ulink>." -msgstr "" - -#: preparing.xml:1517 -#, no-c-format -#. Tag: para -msgid "Some &arch-title; machines don't have a CMOS configuration menu in the BIOS. They require a software CMOS setup program. If you don't have the Installation and/or Diagnostics diskette for your machine, you can try using a shareware/freeware program. Try looking in <ulink url=\"&url-simtel;\"></ulink>." -msgstr "" - -#: preparing.xml:1528 preparing.xml:1872 -#, no-c-format -#. Tag: title -msgid "Boot Device Selection" -msgstr "" - -#: preparing.xml:1530 -#, no-c-format -#. Tag: para -msgid "Many BIOS set-up menus allow you to select the devices that will be used to bootstrap the system. Set this to look for a bootable operating system on <filename>A:</filename> (the first floppy disk), then optionally the first CD-ROM device (possibly appearing as <filename>D:</filename> or <filename>E:</filename>), and then from <filename>C:</filename> (the first hard disk). This setting enables you to boot from either a floppy disk or a CD-ROM, which are the two most common boot devices used to install Debian." -msgstr "" - -#: preparing.xml:1541 -#, no-c-format -#. Tag: para -msgid "If you have a newer SCSI controller and you have a CD-ROM device attached to it, you are usually able to boot from the CD-ROM. All you have to do is enable booting from a CD-ROM in the SCSI-BIOS of your controller." -msgstr "" - -#: preparing.xml:1548 -#, no-c-format -#. Tag: para -msgid "Another popular option is to boot from a USB storage device (also called a USB memory stick or USB key). Some BIOSes can boot directly from a USB storage device, but some cannot. You may need to configure your BIOS to boot from a <quote>Removable drive</quote> or even from <quote>USB-ZIP</quote> to get it to boot from the USB device." -msgstr "" - -#: preparing.xml:1556 -#, no-c-format -#. Tag: para -msgid "Here are some details about how to set the boot order. Remember to reset the boot order after Linux is installed, so that you restart your machine from the hard drive." -msgstr "" - -#: preparing.xml:1565 -#, no-c-format -#. Tag: title -msgid "Changing the Boot Order on IDE Computers" -msgstr "" - -#: preparing.xml:1568 -#, no-c-format -#. Tag: para -msgid "As your computer starts, press the keys to enter the BIOS utility. Often, it is the <keycap>Delete</keycap> key. However, consult the hardware documentation for the exact keystrokes." -msgstr "" - -#: preparing.xml:1575 -#, no-c-format -#. Tag: para -msgid "Find the boot sequence in the setup utility. Its location depends on your BIOS, but you are looking for a field that lists drives." -msgstr "" - -#: preparing.xml:1580 -#, no-c-format -#. Tag: para -msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom." -msgstr "" - -#: preparing.xml:1585 -#, no-c-format -#. Tag: para -msgid "C is the hard drive, and A is the floppy drive." -msgstr "" - -#: preparing.xml:1591 -#, no-c-format -#. Tag: para -msgid "Change the boot sequence setting so that the CD-ROM or the floppy is first. Usually, the <keycap>Page Up</keycap> or <keycap>Page Down</keycap> keys cycle through the possible choices." -msgstr "" - -#: preparing.xml:1599 -#, no-c-format -#. Tag: para -msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer." -msgstr "" - -#: preparing.xml:1609 -#, no-c-format -#. Tag: title -msgid "Changing the Boot Order on SCSI Computers" -msgstr "" - -#: preparing.xml:1613 -#, no-c-format -#. Tag: para -msgid "As your computer starts, press the keys to enter the SCSI setup utility." -msgstr "" - -#: preparing.xml:1618 -#, no-c-format -#. Tag: para -msgid "You can start the SCSI setup utility after the memory check and the message about how to start the BIOS utility displays when you start your computer." -msgstr "" - -#: preparing.xml:1624 -#, no-c-format -#. Tag: para -msgid "The keystrokes you need depend on the utility. Often, it is <keycombo><keycap>Ctrl</keycap><keycap>F2</keycap></keycombo>. However, consult your hardware documentation for the exact keystrokes." -msgstr "" - -#: preparing.xml:1632 -#, no-c-format -#. Tag: para -msgid "Find the utility for changing the boot order." -msgstr "" - -#: preparing.xml:1637 -#, no-c-format -#. Tag: para -msgid "Set the utility so that the SCSI ID of the CD drive is first on the list." -msgstr "" - -#: preparing.xml:1643 -#, no-c-format -#. Tag: para -msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer. Often, you must press <keycap>F10</keycap>." -msgstr "" - -#: preparing.xml:1657 -#, no-c-format -#. Tag: title -msgid "Miscellaneous BIOS Settings" -msgstr "" - -#: preparing.xml:1659 -#, no-c-format -#. Tag: title -msgid "CD-ROM Settings" -msgstr "" - -#: preparing.xml:1660 -#, no-c-format -#. Tag: para -msgid "Some BIOS systems (such as Award BIOS) allow you to automatically set the CD speed. You should avoid that, and instead set it to, say, the lowest speed. If you get <userinput>seek failed</userinput> error messages, this may be your problem." -msgstr "" - -#: preparing.xml:1670 -#, no-c-format -#. Tag: title -msgid "Extended vs. Expanded Memory" -msgstr "" - -#: preparing.xml:1671 -#, no-c-format -#. Tag: para -msgid "If your system provides both ex<emphasis>ten</emphasis>ded and ex<emphasis>pan</emphasis>ded memory, set it so that there is as much extended and as little expanded memory as possible. Linux requires extended memory and cannot use expanded memory." -msgstr "" - -#: preparing.xml:1681 -#, no-c-format -#. Tag: title -msgid "Virus Protection" -msgstr "" - -#: preparing.xml:1682 -#, no-c-format -#. Tag: para -msgid "Disable any virus-warning features your BIOS may provide. If you have a virus-protection board or other special hardware, make sure it is disabled or physically removed while running GNU/Linux. These aren't compatible with GNU/Linux; moreover, due to the file system permissions and protected memory of the Linux kernel, viruses are almost unheard of<footnote> <para> After installation you can enable Boot Sector protection if you want. This offers no additional security in Linux but if you also run Windows it may prevent a catastrophe. There is no need to tamper with the Master Boot Record (MBR) after the boot manager has been set up. </para> </footnote>." -msgstr "" - -#: preparing.xml:1703 -#, no-c-format -#. Tag: title -msgid "Shadow RAM" -msgstr "" - -#: preparing.xml:1704 -#, no-c-format -#. Tag: para -msgid "Your motherboard may provide <emphasis>shadow RAM</emphasis> or BIOS caching. You may see settings for <quote>Video BIOS Shadow</quote>, <quote>C800-CBFF Shadow</quote>, etc. <emphasis>Disable</emphasis> all shadow RAM. Shadow RAM is used to accelerate access to the ROMs on your motherboard and on some of the controller cards. Linux does not use these ROMs once it has booted because it provides its own faster 32-bit software in place of the 16-bit programs in the ROMs. Disabling the shadow RAM may make some of it available for programs to use as normal memory. Leaving the shadow RAM enabled may interfere with Linux access to hardware devices." -msgstr "" - -#: preparing.xml:1721 -#, no-c-format -#. Tag: title -msgid "Memory Hole" -msgstr "" - -#: preparing.xml:1722 -#, no-c-format -#. Tag: para -msgid "If your BIOS offers something like <quote>15–16 MB Memory Hole</quote>, please disable that. Linux expects to find memory there if you have that much RAM." -msgstr "" - -#: preparing.xml:1728 -#, no-c-format -#. Tag: para -msgid "We have a report of an Intel Endeavor motherboard on which there is an option called <quote>LFB</quote> or <quote>Linear Frame Buffer</quote>. This had two settings: <quote>Disabled</quote> and <quote>1 Megabyte</quote>. Set it to <quote>1 Megabyte</quote>. When disabled, the installation floppy was not read correctly, and the system eventually crashed. At this writing we don't understand what's going on with this particular device — it just worked with that setting and not without it." -msgstr "" - -#: preparing.xml:1744 -#, no-c-format -#. Tag: title -msgid "Advanced Power Management" -msgstr "" - -#: preparing.xml:1745 -#, no-c-format -#. Tag: para -msgid "If your motherboard provides Advanced Power Management (APM), configure it so that power management is controlled by APM. Disable the doze, standby, suspend, nap, and sleep modes, and disable the hard disk's power-down timer. Linux can take over control of these modes, and can do a better job of power-management than the BIOS." -msgstr "" - -#: preparing.xml:1763 -#, no-c-format -#. Tag: title -msgid "Firmware Revisions and Existing OS Setup" -msgstr "" - -#: preparing.xml:1765 -#, no-c-format -#. Tag: para -msgid "&arch-title; machines are generally self-configuring and do not require firmware configuration. However, you should make sure that you have the appropriate ROM and system patches. On the Macintosh, MacOS version >= 7.1 is recommended because version 7.0.1 contains a bug in the video drivers preventing the boot loader from deactivating the video interrupts, resulting in a boot hang. On the BVM VMEbus systems you should make sure you are using BVMBug revision G or higher boot ROMs. The BVMBug boot ROMs do not come as standard on the BVM systems but are available from BVM on request free of charge." -msgstr "" - -#: preparing.xml:1788 -#, no-c-format -#. Tag: title -msgid "Invoking OpenFirmware" -msgstr "" - -#: preparing.xml:1789 -#, no-c-format -#. Tag: para -msgid "There is normally no need to set up the BIOS (called OpenFirmware) on &arch-title; systems. PReP and CHRP are equipped with OpenFirmware, but unfortunately, the means you use to invoke it vary from manufacturer to manufacturer. You'll have to consult the hardware documentation which came with your machine." -msgstr "" - -#: preparing.xml:1797 -#, no-c-format -#. Tag: para -msgid "On &arch-title; Macintoshes, you invoke OpenFirmware with <keycombo><keycap>Command</keycap> <keycap>option</keycap> <keycap>O</keycap> <keycap>F</keycap></keycombo> while booting. Generally it will check for these keystrokes after the chime, but the exact timing varies from model to model. See <ulink url=\"&url-netbsd-powerpc-faq;\"></ulink> for more hints." -msgstr "" - -#: preparing.xml:1806 -#, no-c-format -#. Tag: para -msgid "" - "The OpenFirmware prompt looks like this: <informalexample><screen>\n" - "ok\n" - "0 >\n" - "</screen></informalexample> Note that on older model &arch-title; Macs, the default and sometimes hardwired I/O for OpenFirmware user interaction is through the serial (modem) port. If you invoke OpenFirmware on one of these machines, you will just see a black screen. In that case, a terminal program running on another computer, connected to the modem port, is needed to interact with OpenFirmware." -msgstr "" - -#: preparing.xml:1819 -#, no-c-format -#. Tag: para -msgid "The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 and 2.4, is broken. These machines will most likely not be able to boot from the hard drive unless the firmware is patched. A firmware patch is included in the <application>System Disk 2.3.1</application> utility, available from Apple at <ulink url=\"ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin\"></ulink>. After unpacking the utility in MacOS, and launching it, select the <guibutton>Save button</guibutton> to have the firmware patches installed to nvram." -msgstr "" - -#: preparing.xml:1839 -#, no-c-format -#. Tag: title -msgid "Invoking OpenBoot" -msgstr "" - -#: preparing.xml:1841 -#, no-c-format -#. Tag: para -msgid "OpenBoot provides the basic functions needed to boot the &arch-title; architecture. This is rather similar in function to the BIOS in the x86 architecture, although much nicer. The Sun boot PROMs have a built-in forth interpreter which lets you do quite a number of things with your machine, such as diagnostics and simple scripts." -msgstr "" - -#: preparing.xml:1849 -#, no-c-format -#. Tag: para -msgid "To get to the boot prompt you need to hold down the <keycap>Stop</keycap> key (on older type 4 keyboards, use the <keycap>L1</keycap> key, if you have a PC keyboard adapter, use the <keycap>Break</keycap> key) and press the <keycap>A</keycap> key. The boot PROM will give you a prompt, either <userinput>ok</userinput> or <userinput>></userinput>. It is preferred to have the <userinput>ok</userinput> prompt. So if you get the old style prompt, hit the <keycap>n</keycap> key to get the new style prompt." -msgstr "" - -#: preparing.xml:1861 -#, no-c-format -#. Tag: para -msgid "If you are using a serial console, send a break to the machine. With Minicom, use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type <userinput>%~break</userinput>. Consult the documentation of your terminal emulator if you are using a different program." -msgstr "" - -#: preparing.xml:1874 -#, no-c-format -#. Tag: para -msgid "You can use OpenBoot to boot from specific devices, and also to change your default boot device. However, you need to know some details about how OpenBoot names devices; it's considerably different from Linux device naming, described in <xref linkend=\"device-names\"/>. Also, the command will vary a bit, depending on what version of OpenBoot you have. More information about OpenBoot can be found in the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>." -msgstr "" - -#: preparing.xml:1884 -#, no-c-format -#. Tag: para -msgid "" - "Typically, with newer revisions, you can use OpenBoot devices such as <quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, <quote>disk</quote>, or <quote>disk2</quote>. These have the obvious meanings; the <quote>net</quote> device is for booting from the network. Additionally, the device name can specify a particular partition of a disk, such as <quote>disk2:a</quote> to boot disk2, first partition. Full OpenBoot device names have the form <informalexample> <screen>\n" - "<replaceable>driver-name</replaceable>@\n" - "<replaceable>unit-address</replaceable>:\n" - "<replaceable>device-arguments</replaceable>\n" - "</screen></informalexample>. In older revisions of OpenBoot, device naming is a bit different: the floppy device is called <quote>/fd</quote>, and SCSI disk devices are of the form <quote>sd(<replaceable>controller</replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in newer OpenBoot revisions is useful for viewing the currently configured devices. For full information, whatever your revision, see the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>." -msgstr "" - -#: preparing.xml:1907 -#, no-c-format -#. Tag: para -msgid "" - "To boot from a specific device, use the command <userinput>boot <replaceable>device</replaceable></userinput>. You can set this behavior as the default using the <userinput>setenv</userinput> command. However, the name of the variable to set changed between OpenBoot revisions. In OpenBoot 1.x, use the command <userinput>setenv boot-from <replaceable>device</replaceable></userinput>. In later revisions of OpenBoot, use the command <userinput>setenv boot-device <replaceable>device</replaceable></userinput>. Note, this is also configurable using the <command>eeprom</command> command on Solaris, or modifying the appropriate files in <filename>/proc/openprom/options/</filename>, for example under Linux: <informalexample><screen>\n" - "# echo disk1:1 > /proc/openprom/options/boot-device\n" - "</screen></informalexample> and under Solaris:" -msgstr "" - -#: preparing.xml:1926 -#, no-c-format -#. Tag: screen -msgid "eeprom boot-device=disk1:1" -msgstr "" - -#: preparing.xml:1936 -#, no-c-format -#. Tag: title -msgid "BIOS Setup" -msgstr "" - -#: preparing.xml:1937 -#, no-c-format -#. Tag: para -msgid "In order to install &debian; on a &arch-title; or zSeries machine you have first boot a kernel into the system. The boot mechanism of this platform is inherently different to other ones, especially from PC-like systems: there are no floppy devices available at all. You will notice another big difference while you work with this platform: most (if not all) of the time you will work remote, with the help of some client session software like telnet, or a browser. This is due to that special system architecture where the 3215/3270 console is line-based instead of character-based." -msgstr "" - -#: preparing.xml:1949 -#, no-c-format -#. Tag: para -msgid "Linux on this platform runs either natively on the bare machine, in a so-called LPAR (Logical Partition) or in a virtual machine supplied by the VM system. You can use a boot tape on all of those systems; you may use some other boot media, too, but those may not be generally available. For example, you can use the virtual card reader of a virtual machine, or boot from the HMC (Hardware Management Console) of an LPAR if the HMC and this option is available for you." -msgstr "" - -#: preparing.xml:1959 -#, no-c-format -#. Tag: para -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 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 do you find them. Based on both sources of information you have to prepare your machine and the installation medium and to perform a boot from it. When you see the welcome message in your client session join this document again for the Debian-specific installation steps." -msgstr "" - -#: preparing.xml:1976 -#, no-c-format -#. Tag: title -msgid "Native and LPAR installations" -msgstr "" - -#: preparing.xml:1977 -#, no-c-format -#. Tag: para -msgid "Please refer to chapter 5 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.2 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up an LPAR for Linux." -msgstr "" - -#: preparing.xml:1991 -#, no-c-format -#. Tag: title -msgid "Installation as a VM guest" -msgstr "" - -#: preparing.xml:1993 -#, no-c-format -#. Tag: para -msgid "Please refer to chapter 6 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.1 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up a VM guest for running Linux." -msgstr "" - -#: preparing.xml:2003 -#, no-c-format -#. Tag: para -msgid "You need to copy all the files from the <filename>generic</filename> sub-directory to your CMS disk. Be sure to transfer <filename>kernel.debian</filename> and <filename>initrd.debian</filename> in binary mode with a fixed record length of 80 characters." -msgstr "" - -#: preparing.xml:2015 -#, no-c-format -#. Tag: title -msgid "Setting up an installation server" -msgstr "" - -#: preparing.xml:2017 -#, no-c-format -#. Tag: para -msgid "If you don't have a connection to the Internet (either directly or via a web proxy) you need to create a local installation server that can be accessed from your S/390. This server keeps all the packages you want to install and must make them available using NFS, HTTP or FTP." -msgstr "" - -#: preparing.xml:2025 -#, no-c-format -#. Tag: para -msgid "The installation server needs to copy the exact directory structure from any &debian; mirror, but only the s390 and architecture-independent files are required. You can also copy the contents of all installation CDs into such a directory tree." -msgstr "" - -#: preparing.xml:2034 -#, no-c-format -#. Tag: emphasis -msgid "FIXME: more information needed — from a Redbook?" -msgstr "" - -#: preparing.xml:2040 -#, no-c-format -#. Tag: title -msgid "Hardware Issues to Watch Out For" -msgstr "" - -#: preparing.xml:2041 -#, no-c-format -#. Tag: para -msgid "Many people have tried operating their 90 MHz CPU at 100 MHz, etc. It sometimes works, but is sensitive to temperature and other factors and can actually damage your system. One of the authors of this document over-clocked his own system for a year, and then the system started aborting the <command>gcc</command> program with an unexpected signal while it was compiling the operating system kernel. Turning the CPU speed back down to its rated value solved the problem." -msgstr "" - -#: preparing.xml:2051 -#, no-c-format -#. Tag: para -msgid "The <command>gcc</command> compiler is often the first thing to die from bad memory modules (or other hardware problems that change data unpredictably) because it builds huge data structures that it traverses repeatedly. An error in these data structures will cause it to execute an illegal instruction or access a non-existent address. The symptom of this will be <command>gcc</command> dying from an unexpected signal." -msgstr "" - -#: preparing.xml:2061 -#, no-c-format -#. Tag: para -msgid "Atari TT RAM boards are notorious for RAM problems under Linux; if you encounter any strange problems, try running at least the kernel in ST-RAM. Amiga users may need to exclude RAM using a booter memfile. <phrase condition=\"FIXME\"><emphasis> FIXME: more description of this needed. </emphasis></phrase>" -msgstr "" - -#: preparing.xml:2073 -#, no-c-format -#. Tag: para -msgid "The very best motherboards support parity RAM and will actually tell you if your system has a single-bit error in RAM. Unfortunately, they don't have a way to fix the error, thus they generally crash immediately after they tell you about the bad RAM. Still, it's better to be told you have bad memory than to have it silently insert errors in your data. Thus, the best systems have motherboards that support parity and true-parity memory modules; see <xref linkend=\"Parity-RAM\"/>." -msgstr "" - -#: preparing.xml:2084 -#, no-c-format -#. Tag: para -msgid "If you do have true-parity RAM and your motherboard can handle it, be sure to enable any BIOS settings that cause the motherboard to interrupt on memory parity errors." -msgstr "" - -#: preparing.xml:2092 -#, no-c-format -#. Tag: title -msgid "The Turbo Switch" -msgstr "" - -#: preparing.xml:2093 -#, no-c-format -#. Tag: para -msgid "Many systems have a <emphasis>turbo</emphasis> switch that controls the speed of the CPU. Select the high-speed setting. If your BIOS allows you to disable software control of the turbo switch (or software control of CPU speed), do so and lock the system in high-speed mode. We have one report that on a particular system, while Linux is auto-probing (looking for hardware devices) it can accidentally touch the software control for the turbo switch." -msgstr "" - -#: preparing.xml:2106 -#, no-c-format -#. Tag: title -msgid "Cyrix CPUs and Floppy Disk Errors" -msgstr "" - -#: preparing.xml:2107 -#, no-c-format -#. Tag: para -msgid "Many users of Cyrix CPUs have had to disable the cache in their systems during installation, because the floppy disk has errors if they do not. If you have to do this, be sure to re-enable your cache when you are finished with installation, as the system runs <emphasis>much</emphasis> slower with the cache disabled." -msgstr "" - -#: preparing.xml:2115 -#, no-c-format -#. Tag: para -msgid "We don't think this is necessarily the fault of the Cyrix CPU. It may be something that Linux can work around. We'll continue to look into the problem. For the technically curious, we suspect a problem with the cache being invalid after a switch from 16-bit to 32-bit code." -msgstr "" - -#: preparing.xml:2125 -#, no-c-format -#. Tag: title -msgid "Peripheral Hardware Settings" -msgstr "" - -#: preparing.xml:2126 -#, no-c-format -#. Tag: para -msgid "You may have to change some settings or jumpers on your computer's peripheral cards. Some cards have setup menus, while others rely on jumpers. This document cannot hope to provide complete information on every hardware device; what it hopes to provide is useful tips." -msgstr "" - -#: preparing.xml:2133 -#, no-c-format -#. Tag: para -msgid "If any cards provide <quote>mapped memory</quote>, the memory should be mapped somewhere between 0xA0000 and 0xFFFFF (from 640K to just below 1 megabyte) or at an address at least 1 megabyte greater than the total amount of RAM in your system." -msgstr "" - -#: preparing.xml:2144 -#, no-c-format -#. Tag: title -msgid "USB BIOS support and keyboards" -msgstr "" - -#: preparing.xml:2145 -#, no-c-format -#. Tag: para -msgid "If you have no AT-style keyboard and only a USB model, you may need to enable legacy AT keyboard emulation in your BIOS setup. Only do this if the installation system fails to use your keyboard in USB mode. Conversely, for some systems (especially laptops) you may need to disable legacy USB support if your keyboard does not respond. Consult your main board manual and look in the BIOS for <quote>Legacy keyboard emulation</quote> or <quote>USB keyboard support</quote> options." -msgstr "" - -#: preparing.xml:2158 -#, no-c-format -#. Tag: title -msgid "More than 64 MB RAM" -msgstr "" - -#: preparing.xml:2159 -#, no-c-format -#. Tag: para -msgid "The Linux Kernel cannot always detect what amount of RAM you have. If this is the case please look at <xref linkend=\"boot-parms\"/>." -msgstr "" - diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot index 51192e8c3..e1fb124a4 100644 --- a/po/pot/preseed.pot +++ b/po/pot/preseed.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2006-06-05 19:06+0000\n" +"POT-Creation-Date: 2006-06-21 12:48+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" @@ -26,7 +26,7 @@ msgstr "" msgid "This appendix explains the intricacies of preseeding answers to questions in &d-i; to automate your installation." msgstr "" -#: preseed.xml:23 preseed.xml:492 +#: preseed.xml:23 preseed.xml:504 #, no-c-format #. Tag: para msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;." @@ -278,22 +278,28 @@ msgstr "" #: preseed.xml:302 #, no-c-format #. Tag: para -msgid "While you're at it, you may want to add a boot parameter <userinput>debconf/priority=critical</userinput>. This will avoid most questions even if the preseeding below misses some." +msgid "Note that <filename>preseed/url</filename> can be shortened to just <filename>url</filename> and <filename>preseed/file</filename> to just <filename>file</filename> when they are passed as boot parameters." msgstr "" -#: preseed.xml:312 +#: preseed.xml:308 +#, no-c-format +#. Tag: para +msgid "While you're at it, you may want to add a boot parameter <userinput>priority=critical</userinput>. This will avoid most questions even if the preseeding below misses some." +msgstr "" + +#: preseed.xml:318 #, no-c-format #. Tag: title msgid "Using a DHCP server to specify preconfiguration files" msgstr "" -#: preseed.xml:313 +#: preseed.xml:319 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:324 +#: preseed.xml:330 #, no-c-format #. Tag: screen msgid "" @@ -302,121 +308,127 @@ msgid "" "}" msgstr "" -#: preseed.xml:326 +#: preseed.xml:332 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:333 +#: preseed.xml:339 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:345 +#: preseed.xml:351 #, no-c-format #. Tag: title msgid "Using boot parameters to supplement preseeding" msgstr "" -#: preseed.xml:346 +#: preseed.xml:352 #, no-c-format #. Tag: para msgid "Some parts of the installation process cannot be automated using some forms of preseeding because the questions are asked before the preconfiguration file is loaded. For example, if the preconfiguration file is downloaded over the network, the network setup must be done first. One reason to use initrd preseeding is that it allows preseeding of even these early steps of the installation process." msgstr "" -#: preseed.xml:355 +#: preseed.xml:361 #, no-c-format #. Tag: para msgid "If a preconfiguration file cannot be used to preseed some steps, the install can still be fully automated, since you can pass preseed values to the kernel on the command line. Just pass <userinput>path/to/var=value</userinput> for any of the preseed variables listed in the examples." msgstr "" -#: preseed.xml:362 +#: preseed.xml:368 +#, no-c-format +#. Tag: para +msgid "Note that some variables that are frequently set at the boot prompt have a shorter alias. If an alias is available, it is used in the examples in this appendix instead of the full variable." +msgstr "" + +#: preseed.xml:374 #, no-c-format #. Tag: para msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after it will be copied into the installed bootloader configuration (if supported by the installer for the bootloader). Note that the <quote>--</quote> may already be present in the default boot parameters." msgstr "" -#: preseed.xml:371 +#: preseed.xml:383 #, no-c-format #. Tag: para msgid "The 2.4 kernel accepts a maximum of 8 command line options and 8 environment options (including any options added by default for the installer). If these numbers are exceeded, 2.4 kernels will drop any excess options and 2.6 kernels will panic. For kernel 2.6.9 and later, you can use 32 command line options and 32 environment options." msgstr "" -#: preseed.xml:380 +#: preseed.xml:392 #, no-c-format #. Tag: para msgid "For most installations some of the default options in your bootloader configuration file, like <literal>vga=normal</literal>, may be safely removed which may allow you to add more options for preseeding." msgstr "" -#: preseed.xml:387 +#: preseed.xml:399 #, no-c-format #. Tag: para msgid "It may not always be possible to specify values with spaces for boot parameters, even if you delimit them with quotes." msgstr "" -#: preseed.xml:397 +#: preseed.xml:409 #, no-c-format #. Tag: title msgid "Creating a preconfiguration file" msgstr "" -#: preseed.xml:398 +#: preseed.xml:410 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:404 +#: preseed.xml:416 #, no-c-format #. Tag: screen msgid "<owner> <question name> <question type> <value>" msgstr "" -#: preseed.xml:406 +#: preseed.xml:418 #, no-c-format #. Tag: para msgid "There are a few rules to keep in mind when writing a preconfiguration file." msgstr "" -#: preseed.xml:413 +#: preseed.xml:425 #, no-c-format #. Tag: para msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value." msgstr "" -#: preseed.xml:417 +#: preseed.xml:429 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:423 +#: preseed.xml:435 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:429 +#: preseed.xml:441 #, no-c-format #. Tag: para msgid "Some questions take a code as value instead of the English text that is shown during installation." msgstr "" -#: preseed.xml:435 +#: preseed.xml:447 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:440 +#: preseed.xml:452 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:447 +#: preseed.xml:459 #, no-c-format #. Tag: screen msgid "" @@ -424,67 +436,67 @@ msgid "" "$ debconf-get-selections >> <replaceable>file</replaceable>" msgstr "" -#: preseed.xml:449 +#: preseed.xml:461 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:457 +#: preseed.xml:469 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:465 +#: preseed.xml:477 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:473 +#: preseed.xml:485 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:481 +#: preseed.xml:493 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:491 +#: preseed.xml:503 #, no-c-format #. Tag: title msgid "Contents of the preconfiguration file" msgstr "" -#: preseed.xml:497 +#: preseed.xml:509 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:508 +#: preseed.xml:520 #, no-c-format #. Tag: title msgid "Localization" msgstr "" -#: preseed.xml:509 +#: preseed.xml:521 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:515 +#: preseed.xml:527 #, no-c-format #. Tag: para -msgid "The locale can be used to specify both language and country. To specify the locale as a boot parameter, use <userinput>debian-installer/locale=<replaceable>en_US</replaceable></userinput>." +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 "" -#: preseed.xml:521 +#: preseed.xml:533 #, no-c-format #. Tag: screen msgid "" @@ -492,13 +504,13 @@ msgid "" "d-i debian-installer/locale string en_US" msgstr "" -#: preseed.xml:523 +#: preseed.xml:535 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:530 +#: preseed.xml:542 #, no-c-format #. Tag: screen msgid "" @@ -509,37 +521,37 @@ msgid "" "#d-i console-keymaps-usb/keymap select mac-usb-us" msgstr "" -#: preseed.xml:532 +#: preseed.xml:544 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:541 +#: preseed.xml:553 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:551 +#: preseed.xml:563 #, no-c-format #. Tag: title msgid "Network configuration" msgstr "" -#: preseed.xml:552 +#: preseed.xml:564 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:560 +#: preseed.xml:572 #, no-c-format #. Tag: para -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>netcfg/choose_interface=<replaceable>eth1</replaceable></userinput>." +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 "" -#: preseed.xml:568 +#: preseed.xml:580 #, no-c-format #. Tag: screen msgid "" @@ -583,31 +595,31 @@ msgid "" "#d-i netcfg/dhcp_hostname string radish" msgstr "" -#: preseed.xml:573 +#: preseed.xml:585 #, no-c-format #. Tag: title msgid "Mirror settings" msgstr "" -#: preseed.xml:574 +#: preseed.xml:586 #, no-c-format #. Tag: para msgid "Depending on the installation method you use, a mirror may be used both to download additional components of the installer, the base system and to set up the <filename>/etc/apt/sources.list</filename> for the installed system." msgstr "" -#: preseed.xml:581 +#: preseed.xml:593 #, no-c-format #. Tag: para msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system." msgstr "" -#: preseed.xml:586 +#: preseed.xml:598 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:598 +#: preseed.xml:610 #, no-c-format #. Tag: screen msgid "" @@ -622,25 +634,25 @@ msgid "" "#d-i mirror/udeb/suite string testing" msgstr "" -#: preseed.xml:603 +#: preseed.xml:615 #, no-c-format #. Tag: title msgid "Partitioning" msgstr "" -#: preseed.xml:604 +#: preseed.xml:616 #, no-c-format #. Tag: para msgid "Using preseeding to partition the harddisk is very much limited to what is supported by <classname>partman-auto</classname>. You can choose to either partition existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file. It is currently not possible to partition multiple disks using preseeding nor to set up RAID." msgstr "" -#: preseed.xml:616 +#: preseed.xml:628 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:624 +#: preseed.xml:636 #, no-c-format #. Tag: screen msgid "" @@ -696,13 +708,13 @@ msgid "" "d-i partman/confirm boolean true" msgstr "" -#: preseed.xml:629 +#: preseed.xml:641 #, no-c-format #. Tag: title msgid "Clock and time zone setup" msgstr "" -#: preseed.xml:631 +#: preseed.xml:643 #, no-c-format #. Tag: screen msgid "" @@ -714,19 +726,19 @@ msgid "" "d-i time/zone string US/Eastern" msgstr "" -#: preseed.xml:636 +#: preseed.xml:648 #, no-c-format #. Tag: title msgid "Apt setup" msgstr "" -#: preseed.xml:637 +#: preseed.xml:649 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:645 +#: preseed.xml:657 #, no-c-format #. Tag: screen msgid "" @@ -745,25 +757,25 @@ msgid "" "#d-i apt-setup/local0/key string http://local.server/key" msgstr "" -#: preseed.xml:650 +#: preseed.xml:662 #, no-c-format #. Tag: title msgid "Account setup" msgstr "" -#: preseed.xml:651 +#: preseed.xml:663 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:658 +#: preseed.xml:670 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:668 +#: preseed.xml:680 #, no-c-format #. Tag: screen msgid "" @@ -789,37 +801,37 @@ msgid "" "#d-i passwd/user-password-crypted password [MD5 hash]" msgstr "" -#: preseed.xml:670 +#: preseed.xml:682 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:680 +#: preseed.xml:692 #, no-c-format #. Tag: para msgid "An MD5 hash for a password can be generated using the following command." msgstr "" -#: preseed.xml:684 +#: preseed.xml:696 #, no-c-format #. Tag: screen msgid "$ echo \"r00tme\" | mkpasswd -s -H MD5" msgstr "" -#: preseed.xml:690 +#: preseed.xml:702 #, no-c-format #. Tag: title msgid "Base system installation" msgstr "" -#: preseed.xml:691 +#: preseed.xml:703 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:698 +#: preseed.xml:710 #, no-c-format #. Tag: screen msgid "" @@ -827,13 +839,13 @@ msgid "" "#d-i base-installer/kernel/linux/initramfs-generators string yaird" msgstr "" -#: preseed.xml:703 +#: preseed.xml:715 #, no-c-format #. Tag: title msgid "Boot loader installation" msgstr "" -#: preseed.xml:705 +#: preseed.xml:717 #, no-c-format #. Tag: screen msgid "" @@ -856,91 +868,91 @@ msgid "" "#d-i grub-installer/with_other_os boolean false" msgstr "" -#: preseed.xml:710 +#: preseed.xml:722 #, no-c-format #. Tag: title msgid "Package selection" msgstr "" -#: preseed.xml:711 +#: preseed.xml:723 #, no-c-format #. Tag: para msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:" msgstr "" -#: preseed.xml:720 +#: preseed.xml:732 #, no-c-format #. Tag: userinput msgid "standard" msgstr "" -#: preseed.xml:723 +#: preseed.xml:735 #, no-c-format #. Tag: userinput msgid "desktop" msgstr "" -#: preseed.xml:726 +#: preseed.xml:738 #, no-c-format #. Tag: userinput msgid "gnome-desktop" msgstr "" -#: preseed.xml:729 +#: preseed.xml:741 #, no-c-format #. Tag: userinput msgid "kde-desktop" msgstr "" -#: preseed.xml:732 +#: preseed.xml:744 #, no-c-format #. Tag: userinput msgid "web-server" msgstr "" -#: preseed.xml:735 +#: preseed.xml:747 #, no-c-format #. Tag: userinput msgid "print-server" msgstr "" -#: preseed.xml:738 +#: preseed.xml:750 #, no-c-format #. Tag: userinput msgid "dns-server" msgstr "" -#: preseed.xml:741 +#: preseed.xml:753 #, no-c-format #. Tag: userinput msgid "file-server" msgstr "" -#: preseed.xml:744 +#: preseed.xml:756 #, no-c-format #. Tag: userinput msgid "mail-server" msgstr "" -#: preseed.xml:747 +#: preseed.xml:759 #, no-c-format #. Tag: userinput msgid "sql-database" msgstr "" -#: preseed.xml:750 +#: preseed.xml:762 #, no-c-format #. Tag: userinput msgid "laptop" msgstr "" -#: preseed.xml:754 +#: preseed.xml:766 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:762 +#: preseed.xml:774 #, no-c-format #. Tag: screen msgid "" @@ -955,13 +967,13 @@ msgid "" "#popularity-contest popularity-contest/participate boolean false" msgstr "" -#: preseed.xml:767 +#: preseed.xml:779 #, no-c-format #. Tag: title msgid "Finishing up the first stage install" msgstr "" -#: preseed.xml:769 +#: preseed.xml:781 #, no-c-format #. Tag: screen msgid "" @@ -973,19 +985,19 @@ msgid "" "#d-i cdrom-detect/eject boolean false" msgstr "" -#: preseed.xml:774 +#: preseed.xml:786 #, no-c-format #. Tag: title msgid "Mailer configuration" msgstr "" -#: preseed.xml:775 +#: preseed.xml:787 #, no-c-format #. Tag: para msgid "During a normal install, exim asks only a few questions. Here's how to avoid even those. More complicated preseeding is possible." msgstr "" -#: preseed.xml:782 +#: preseed.xml:794 #, no-c-format #. Tag: screen msgid "" @@ -996,19 +1008,19 @@ msgid "" "exim4-config exim4/dc_postmaster string" msgstr "" -#: preseed.xml:787 +#: preseed.xml:799 #, no-c-format #. Tag: title msgid "X configuration" msgstr "" -#: preseed.xml:788 +#: preseed.xml:800 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:796 +#: preseed.xml:808 #, no-c-format #. Tag: screen msgid "" @@ -1034,13 +1046,13 @@ msgid "" " select 1024x768 @ 60 Hz" msgstr "" -#: preseed.xml:801 +#: preseed.xml:813 #, no-c-format #. Tag: title msgid "Preseeding other packages" msgstr "" -#: preseed.xml:803 +#: preseed.xml:815 #, no-c-format #. Tag: screen msgid "" @@ -1053,19 +1065,19 @@ msgid "" "# debconf-get-selections >> file" msgstr "" -#: preseed.xml:809 +#: preseed.xml:821 #, no-c-format #. Tag: title msgid "Advanced options" msgstr "" -#: preseed.xml:812 +#: preseed.xml:824 #, no-c-format #. Tag: title msgid "Shell commands" msgstr "" -#: preseed.xml:814 +#: preseed.xml:826 #, no-c-format #. Tag: screen msgid "" @@ -1087,19 +1099,19 @@ msgid "" "#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh" msgstr "" -#: preseed.xml:819 +#: preseed.xml:831 #, no-c-format #. Tag: title msgid "Chainloading preconfiguration files" msgstr "" -#: preseed.xml:820 +#: preseed.xml:832 #, no-c-format #. Tag: para 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 "" -#: preseed.xml:830 +#: preseed.xml:842 #, no-c-format #. Tag: screen msgid "" diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index 965818630..040668193 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" -"POT-Creation-Date: 2006-04-23 15:57+0000\n" +"POT-Creation-Date: 2006-06-21 12:48+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" @@ -53,13 +53,13 @@ msgstr "" #: using-d-i.xml:42 #, no-c-format #. Tag: para -msgid "Power users may be more comfortable with a menu-driven interface, where each step is controlled by the user rather than the installer performing each step automatically in sequence. To use the installer in a manual, menu-driven way, add the boot argument <userinput>debconf/priority=medium</userinput>." +msgid "Power users may be more comfortable with a menu-driven interface, where each step is controlled by the user rather than the installer performing each step automatically in sequence. To use the installer in a manual, menu-driven way, add the boot argument <userinput>priority=medium</userinput>." msgstr "" #: using-d-i.xml:50 #, no-c-format #. Tag: para -msgid "If your hardware requires you to pass options to kernel modules as they are installed, you will need to start the installer in <quote>expert</quote> mode. This can be done by either using the <command>expert</command> command to start the installer or by adding the boot argument <userinput>debconf/priority=low</userinput>. Expert mode gives you full control over &d-i;." +msgid "If your hardware requires you to pass options to kernel modules as they are installed, you will need to start the installer in <quote>expert</quote> mode. This can be done by either using the <command>expert</command> command to start the installer or by adding the boot argument <userinput>priority=low</userinput>. Expert mode gives you full control over &d-i;." msgstr "" #: using-d-i.xml:59 @@ -557,7 +557,7 @@ msgstr "" #: using-d-i.xml:573 #, no-c-format #. Tag: para -msgid "To get a working keyboard, you should boot the installer with parameter <userinput>debconf/priority=medium</userinput>. When you get to keyboard selection<footnote> <para> If you are installing at default priority you should use the <userinput>Go Back</userinput> button to return to the installer menu when you are shown the list of Sun type keymaps. </para> </footnote>, choose <quote>No keyboard to configure</quote> if you have a keyboard with an American (US) layout, or choose <quote>USB keyboard</quote> if you have a keyboard with a localized layout. Selecting <quote>No keyboard to configure</quote> will leave the kernel keymap in place, which is correct for US keyboards." +msgid "To get a working keyboard, you should boot the installer with parameter <userinput>priority=medium</userinput>. When you get to keyboard selection<footnote> <para> If you are installing at default priority you should use the <userinput>Go Back</userinput> button to return to the installer menu when you are shown the list of Sun type keymaps. </para> </footnote>, choose <quote>No keyboard to configure</quote> if you have a keyboard with an American (US) layout, or choose <quote>USB keyboard</quote> if you have a keyboard with a localized layout. Selecting <quote>No keyboard to configure</quote> will leave the kernel keymap in place, which is correct for US keyboards." msgstr "" #: using-d-i.xml:611 |