diff options
Diffstat (limited to 'po/nn')
| -rw-r--r-- | po/nn/boot-installer.po | 2809 | ||||
| -rw-r--r-- | po/nn/preseed.po | 1337 | ||||
| -rw-r--r-- | po/nn/random-bits.po | 952 | ||||
| -rw-r--r-- | po/nn/using-d-i.po | 2210 |
4 files changed, 5354 insertions, 1954 deletions
diff --git a/po/nn/boot-installer.po b/po/nn/boot-installer.po index c6571372d..b87c57d57 100644 --- a/po/nn/boot-installer.po +++ b/po/nn/boot-installer.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2008-04-20 00:10+0000\n" +"POT-Creation-Date: 2008-05-11 00:10+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" @@ -29,13 +29,21 @@ msgstr "" #. Tag: para #: boot-installer.xml:15 #, no-c-format -msgid "If you have any other operating systems on your system that you wish to keep (dual boot setup), you should make sure that they have been properly shut down <emphasis>before</emphasis> you boot the installer. Installing an operating system while another operating system is in hibernation (has been suspended to disk) could result in loss of, or damage to the state of the suspended operating system which could cause problems when it is rebooted." +msgid "" +"If you have any other operating systems on your system that you wish to keep " +"(dual boot setup), you should make sure that they have been properly shut " +"down <emphasis>before</emphasis> you boot the installer. Installing an " +"operating system while another operating system is in hibernation (has been " +"suspended to disk) could result in loss of, or damage to the state of the " +"suspended operating system which could cause problems when it is rebooted." msgstr "" #. Tag: para #: boot-installer.xml:26 #, no-c-format -msgid "For information on how to boot the graphical installer, see <xref linkend=\"graphical\"/>." +msgid "" +"For information on how to boot the graphical installer, see <xref linkend=" +"\"graphical\"/>." msgstr "" #. Tag: title @@ -47,55 +55,95 @@ msgstr "" #. Tag: para #: boot-installer.xml:39 #, no-c-format -msgid "Console firmware is stored in a flash ROM and started when an Alpha system is powered up or reset. There are two different console specifications used on Alpha systems, and hence two classes of console firmware available:" +msgid "" +"Console firmware is stored in a flash ROM and started when an Alpha system " +"is powered up or reset. There are two different console specifications used " +"on Alpha systems, and hence two classes of console firmware available:" msgstr "" #. Tag: para #: boot-installer.xml:49 #, no-c-format -msgid "<emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem specification, which provides an operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems." +msgid "" +"<emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem " +"specification, which provides an operating environment for OpenVMS, Tru64 " +"UNIX, and Linux operating systems." msgstr "" #. Tag: para #: boot-installer.xml:56 #, no-c-format -msgid "<emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the Advanced RISC Computing (ARC) specification, which provides an operating environment for Windows NT." +msgid "" +"<emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the " +"Advanced RISC Computing (ARC) specification, which provides an operating " +"environment for Windows NT." msgstr "" #. Tag: para #: boot-installer.xml:65 #, no-c-format -msgid "From the user's perspective, the most important difference between SRM and ARC is that the choice of console constrains the possible disk-partitioning scheme for the hard disk which you wish to boot off of." +msgid "" +"From the user's perspective, the most important difference between SRM and " +"ARC is that the choice of console constrains the possible disk-partitioning " +"scheme for the hard disk which you wish to boot off of." msgstr "" #. Tag: para #: boot-installer.xml:72 #, no-c-format -msgid "ARC requires that you use an MS-DOS partition table (as created by <command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition tables are the <quote>native</quote> partition format when booting from ARC. In fact, since AlphaBIOS contains a disk partitioning utility, you may prefer to partition your disks from the firmware menus before installing Linux." +msgid "" +"ARC requires that you use an MS-DOS partition table (as created by " +"<command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition " +"tables are the <quote>native</quote> partition format when booting from ARC. " +"In fact, since AlphaBIOS contains a disk partitioning utility, you may " +"prefer to partition your disks from the firmware menus before installing " +"Linux." msgstr "" #. Tag: para #: boot-installer.xml:81 #, no-c-format -msgid "Conversely, SRM is <emphasis>incompatible</emphasis><footnote> <para> Specifically, the bootsector format required by the Console Subsystem Specification conflicts with the placement of the DOS partition table. </para> </footnote> with MS-DOS partition tables. Since Tru64 Unix uses the BSD disklabel format, this is the <quote>native</quote> partition format for SRM installations." +msgid "" +"Conversely, SRM is <emphasis>incompatible</emphasis><footnote> <para> " +"Specifically, the bootsector format required by the Console Subsystem " +"Specification conflicts with the placement of the DOS partition table. </" +"para> </footnote> with MS-DOS partition tables. Since Tru64 Unix uses the " +"BSD disklabel format, this is the <quote>native</quote> partition format for " +"SRM installations." msgstr "" #. Tag: para #: boot-installer.xml:94 #, no-c-format -msgid "GNU/Linux is the only operating system on Alpha that can be booted from both console types, but &debian; &release; only supports booting on SRM-based systems. If you have an Alpha for which no version of SRM is available, if you will be dual-booting the system with Windows NT, or if your boot device requires ARC console support for BIOS initialization, you will not be able to use the &debian; &release; installer. You can still run &debian; &release; on such systems by using other install media; for instance, you can install Debian woody with MILO and upgrade." +msgid "" +"GNU/Linux is the only operating system on Alpha that can be booted from both " +"console types, but &debian; &release; only supports booting on SRM-based " +"systems. If you have an Alpha for which no version of SRM is available, if " +"you will be dual-booting the system with Windows NT, or if your boot device " +"requires ARC console support for BIOS initialization, you will not be able " +"to use the &debian; &release; installer. You can still run &debian; " +"&release; on such systems by using other install media; for instance, you " +"can install Debian woody with MILO and upgrade." msgstr "" #. Tag: para #: boot-installer.xml:105 #, no-c-format -msgid "Because <command>MILO</command> is not available for any of the Alpha systems currently in production (as of February 2000), and because it is no longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM firmware on your older Alpha, it is recommended that you use SRM when possible." +msgid "" +"Because <command>MILO</command> is not available for any of the Alpha " +"systems currently in production (as of February 2000), and because it is no " +"longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM " +"firmware on your older Alpha, it is recommended that you use SRM when " +"possible." msgstr "" #. Tag: para #: boot-installer.xml:113 #, no-c-format -msgid "The following table summarizes available and supported system type/console combinations (see <xref linkend=\"alpha-cpus\"/> for the system type names). The word <quote>ARC</quote> below denotes any of the ARC-compliant consoles." +msgid "" +"The following table summarizes available and supported system type/console " +"combinations (see <xref linkend=\"alpha-cpus\"/> for the system type names). " +"The word <quote>ARC</quote> below denotes any of the ARC-compliant consoles." msgstr "" #. Tag: entry @@ -117,7 +165,11 @@ msgid "alcor" msgstr "" #. Tag: entry -#: boot-installer.xml:133 boot-installer.xml:136 boot-installer.xml:142 boot-installer.xml:148 boot-installer.xml:151 boot-installer.xml:154 boot-installer.xml:157 boot-installer.xml:163 boot-installer.xml:166 boot-installer.xml:169 boot-installer.xml:178 boot-installer.xml:187 boot-installer.xml:202 boot-installer.xml:205 +#: boot-installer.xml:133 boot-installer.xml:136 boot-installer.xml:142 +#: boot-installer.xml:148 boot-installer.xml:151 boot-installer.xml:154 +#: boot-installer.xml:157 boot-installer.xml:163 boot-installer.xml:166 +#: boot-installer.xml:169 boot-installer.xml:178 boot-installer.xml:187 +#: boot-installer.xml:202 boot-installer.xml:205 #, no-c-format msgid "ARC or SRM" msgstr "" @@ -135,7 +187,9 @@ msgid "book1" msgstr "" #. Tag: entry -#: boot-installer.xml:139 boot-installer.xml:145 boot-installer.xml:160 boot-installer.xml:172 boot-installer.xml:181 boot-installer.xml:184 boot-installer.xml:190 boot-installer.xml:196 boot-installer.xml:199 +#: boot-installer.xml:139 boot-installer.xml:145 boot-installer.xml:160 +#: boot-installer.xml:172 boot-installer.xml:181 boot-installer.xml:184 +#: boot-installer.xml:190 boot-installer.xml:196 boot-installer.xml:199 #, no-c-format msgid "SRM only" msgstr "" @@ -299,58 +353,102 @@ msgstr "" #. Tag: para #: boot-installer.xml:218 #, no-c-format -msgid "Generally, none of these consoles can boot Linux directly, so the assistance of an intermediary bootloader is required. For the SRM console, <command>aboot</command>, a small, platform-independent bootloader, is used. See the (unfortunately outdated) <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</command>." +msgid "" +"Generally, none of these consoles can boot Linux directly, so the assistance " +"of an intermediary bootloader is required. For the SRM console, " +"<command>aboot</command>, a small, platform-independent bootloader, is used. " +"See the (unfortunately outdated) <ulink url=\"&url-srm-howto;\">SRM HOWTO</" +"ulink> for more information on <command>aboot</command>." msgstr "" #. Tag: para #: boot-installer.xml:227 #, no-c-format -msgid "The following paragraphs are from the woody install manual, and are included here for reference; they may be useful to someone at a later date when Debian supports MILO-based installs again." +msgid "" +"The following paragraphs are from the woody install manual, and are included " +"here for reference; they may be useful to someone at a later date when " +"Debian supports MILO-based installs again." msgstr "" #. Tag: para #: boot-installer.xml:233 #, no-c-format -msgid "Generally, none of these consoles can boot Linux directly, so the assistance of an intermediary bootloader is required. There are two mainstream Linux loaders: <command>MILO</command> and <command>aboot</command>." +msgid "" +"Generally, none of these consoles can boot Linux directly, so the assistance " +"of an intermediary bootloader is required. There are two mainstream Linux " +"loaders: <command>MILO</command> and <command>aboot</command>." msgstr "" #. Tag: para #: boot-installer.xml:239 #, no-c-format -msgid "<command>MILO</command> is itself a console, which replaces ARC or SRM in memory. <command>MILO</command> can be booted from both ARC and SRM and is the only way to bootstrap Linux from the ARC console. <command>MILO</command> is platform-specific (a different <command>MILO</command> is needed for each system type) and exist only for those systems, for which ARC support is shown in the table above. See also the (unfortunately outdated) <ulink url=\"&url-milo-howto;\">MILO HOWTO</ulink>." +msgid "" +"<command>MILO</command> is itself a console, which replaces ARC or SRM in " +"memory. <command>MILO</command> can be booted from both ARC and SRM and is " +"the only way to bootstrap Linux from the ARC console. <command>MILO</" +"command> is platform-specific (a different <command>MILO</command> is needed " +"for each system type) and exist only for those systems, for which ARC " +"support is shown in the table above. See also the (unfortunately outdated) " +"<ulink url=\"&url-milo-howto;\">MILO HOWTO</ulink>." msgstr "" #. Tag: para #: boot-installer.xml:249 #, no-c-format -msgid "<command>aboot</command> is a small, platform-independent bootloader, which runs from SRM only. See the (also unfortunately outdated) <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</command>." +msgid "" +"<command>aboot</command> is a small, platform-independent bootloader, which " +"runs from SRM only. See the (also unfortunately outdated) <ulink url=\"&url-" +"srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</" +"command>." msgstr "" #. Tag: para #: boot-installer.xml:256 #, no-c-format msgid "" - "Thus, three scenarios are generally possible, depending on the system's console firmware and whether or not <command>MILO</command> is available: <informalexample><screen>\n" - "SRM -> aboot\n" - "SRM -> MILO\n" - "ARC -> MILO\n" - "</screen></informalexample> Because <command>MILO</command> is not available for any of the Alpha systems currently in production (as of February 2000), and because it is no longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM firmware on your older Alpha, it is recommended that you use SRM and <command>aboot</command> on new installations of GNU/Linux, unless you wish to dual-boot with Windows NT." +"Thus, three scenarios are generally possible, depending on the system's " +"console firmware and whether or not <command>MILO</command> is available: " +"<informalexample><screen>\n" +"SRM -> aboot\n" +"SRM -> MILO\n" +"ARC -> MILO\n" +"</screen></informalexample> Because <command>MILO</command> is not available " +"for any of the Alpha systems currently in production (as of February 2000), " +"and because it is no longer necessary to buy an OpenVMS or Tru64 Unix " +"license to have SRM firmware on your older Alpha, it is recommended that you " +"use SRM and <command>aboot</command> on new installations of GNU/Linux, " +"unless you wish to dual-boot with Windows NT." msgstr "" #. Tag: para #: boot-installer.xml:271 #, no-c-format -msgid "The majority of AlphaServers and all current server and workstation products contain both SRM and AlphaBIOS in their firmware. For <quote>half-flash</quote> machines such as the various evaluation boards, it is possible to switch from one version to another by reflashing the firmware. Also, once SRM is installed, it is possible to run ARC/AlphaBIOS from a floppy disk (using the <command>arc</command> command). For the reasons mentioned above, we recommend switching to SRM before installing &debian;." +msgid "" +"The majority of AlphaServers and all current server and workstation products " +"contain both SRM and AlphaBIOS in their firmware. For <quote>half-flash</" +"quote> machines such as the various evaluation boards, it is possible to " +"switch from one version to another by reflashing the firmware. Also, once " +"SRM is installed, it is possible to run ARC/AlphaBIOS from a floppy disk " +"(using the <command>arc</command> command). For the reasons mentioned above, " +"we recommend switching to SRM before installing &debian;." msgstr "" #. Tag: para #: boot-installer.xml:282 #, no-c-format -msgid "As on other architectures, you should install the newest available revision of the firmware<footnote> <para> Except on Jensen, where Linux is not supported on firmware versions newer than 1.7 — see <ulink url=\"&url-jensen-howto;\"></ulink> for more information. </para> </footnote> before installing &debian;. For Alpha, firmware updates can be obtained from <ulink url=\"&url-alpha-firmware;\">Alpha Firmware Updates</ulink>." +msgid "" +"As on other architectures, you should install the newest available revision " +"of the firmware<footnote> <para> Except on Jensen, where Linux is not " +"supported on firmware versions newer than 1.7 — see <ulink url=\"&url-" +"jensen-howto;\"></ulink> for more information. </para> </footnote> before " +"installing &debian;. For Alpha, firmware updates can be obtained from <ulink " +"url=\"&url-alpha-firmware;\">Alpha Firmware Updates</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:301 boot-installer.xml:1050 boot-installer.xml:1541 boot-installer.xml:2038 boot-installer.xml:2120 boot-installer.xml:2209 boot-installer.xml:2559 boot-installer.xml:2658 +#: boot-installer.xml:301 boot-installer.xml:1050 boot-installer.xml:1577 +#: boot-installer.xml:2074 boot-installer.xml:2156 boot-installer.xml:2245 +#: boot-installer.xml:2595 boot-installer.xml:2694 #, no-c-format msgid "Booting with TFTP" msgstr "" @@ -359,37 +457,54 @@ msgstr "" #: boot-installer.xml:302 #, no-c-format msgid "" - "In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput> prefix, and will be listed in the output of the <userinput>show dev</userinput> command, like this (edited slightly): <informalexample><screen>\n" - ">>> show dev\n" - "ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65\n" - "ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54\n" - "ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0\n" - "</screen></informalexample> You first need to set the boot protocol: <informalexample><screen>\n" - ">>> set ewa0_protocols bootp\n" - "</screen></informalexample> Then check the medium type is correct: <informalexample><screen>\n" - ">>> set ewa0_mode <replaceable>mode</replaceable>\n" - "</screen></informalexample> You can get a listing of valid modes with <userinput>>>>set ewa0_mode</userinput>." +"In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput> " +"prefix, and will be listed in the output of the <userinput>show dev</" +"userinput> command, like this (edited slightly): <informalexample><screen>\n" +">>> show dev\n" +"ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65\n" +"ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54\n" +"ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0\n" +"</screen></informalexample> You first need to set the boot protocol: " +"<informalexample><screen>\n" +">>> set ewa0_protocols bootp\n" +"</screen></informalexample> Then check the medium type is correct: " +"<informalexample><screen>\n" +">>> set ewa0_mode <replaceable>mode</replaceable>\n" +"</screen></informalexample> You can get a listing of valid modes with " +"<userinput>>>>set ewa0_mode</userinput>." msgstr "" #. Tag: para #: boot-installer.xml:320 #, no-c-format msgid "" - "Then, to boot from the first Ethernet interface, you would type: <informalexample><screen>\n" - ">>> boot ewa0 -flags \"\"\n" - "</screen></informalexample> This will boot using the default kernel parameters as included in the netboot image." +"Then, to boot from the first Ethernet interface, you would type: " +"<informalexample><screen>\n" +">>> boot ewa0 -flags \"\"\n" +"</screen></informalexample> This will boot using the default kernel " +"parameters as included in the netboot image." msgstr "" #. Tag: para #: boot-installer.xml:329 #, no-c-format -msgid "If you wish to use a serial console, you <emphasis>must</emphasis> pass the <userinput>console=</userinput> parameter to the kernel. This can be done using the <userinput>-flags</userinput> argument to the SRM <userinput>boot</userinput> command. The serial ports are named the same as their corresponding files in <userinput>/dev</userinput>. Also, when specifying additional kernel parameters, you must repeat certain default options that are needed by the &d-i; images. For example, to boot from <userinput>ewa0</userinput> and use a console on the first serial port, you would type:" +msgid "" +"If you wish to use a serial console, you <emphasis>must</emphasis> pass the " +"<userinput>console=</userinput> parameter to the kernel. This can be done " +"using the <userinput>-flags</userinput> argument to the SRM <userinput>boot</" +"userinput> command. The serial ports are named the same as their " +"corresponding files in <userinput>/dev</userinput>. Also, when specifying " +"additional kernel parameters, you must repeat certain default options that " +"are needed by the &d-i; images. For example, to boot from <userinput>ewa0</" +"userinput> and use a console on the first serial port, you would type:" msgstr "" #. Tag: screen #: boot-installer.xml:341 #, no-c-format -msgid ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0"" +msgid "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" msgstr "" #. Tag: title @@ -402,11 +517,14 @@ msgstr "" #: boot-installer.xml:347 #, no-c-format msgid "" - "The &debian; install CDs include several preconfigured boot options for VGA and serial consoles. Type <informalexample><screen>\n" - ">>> boot xxxx -flags 0\n" - "</screen></informalexample> to boot using VGA console, where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation. To use serial console on the first serial device, type <informalexample><screen>\n" - ">>> boot xxxx -flags 1\n" - "</screen></informalexample> and for console on the second serial port, type" +"The &debian; install CDs include several preconfigured boot options for VGA " +"and serial consoles. Type <informalexample><screen>\n" +">>> boot xxxx -flags 0\n" +"</screen></informalexample> to boot using VGA console, where " +"<replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation. To use " +"serial console on the first serial device, type <informalexample><screen>\n" +">>> boot xxxx -flags 1\n" +"</screen></informalexample> and for console on the second serial port, type" msgstr "" #. Tag: screen @@ -424,7 +542,14 @@ msgstr "" #. Tag: para #: boot-installer.xml:369 #, no-c-format -msgid "To boot a CD-ROM from the ARC console, find your sub-architecture code name (see <xref linkend=\"alpha-cpus\"/>), then enter <filename>\\milo\\linload.exe</filename> as the boot loader and <filename>\\milo\\<replaceable>subarch</replaceable></filename> (where <replaceable>subarch</replaceable> is the proper subarchitecture name) as the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: You need to use <filename>\\milo\\ldmilo.exe</filename> as boot loader." +msgid "" +"To boot a CD-ROM from the ARC console, find your sub-architecture code name " +"(see <xref linkend=\"alpha-cpus\"/>), then enter <filename>\\milo\\linload." +"exe</filename> as the boot loader and <filename>\\milo" +"\\<replaceable>subarch</replaceable></filename> (where <replaceable>subarch</" +"replaceable> is the proper subarchitecture name) as the OS Path in the `OS " +"Selection Setup' menu. Ruffians make an exception: You need to use <filename>" +"\\milo\\ldmilo.exe</filename> as boot loader." msgstr "" #. Tag: title @@ -437,26 +562,41 @@ msgstr "" #: boot-installer.xml:386 #, no-c-format msgid "" - "At the SRM prompt (<prompt>>>></prompt>), issue the following command: <informalexample><screen>\n" - ">>> boot dva0 -flags 0\n" - "</screen></informalexample> possibly replacing <filename>dva0</filename> with the actual device name. Usually, <filename>dva0</filename> is the floppy; type <informalexample><screen>\n" - ">>> show dev\n" - "</screen></informalexample> to see the list of devices (e.g., if you want to boot from a CD). Note that if you are booting via MILO, <command>-flags</command> argument is ignored, so you can just type <command>boot dva0</command>. If everything works OK, you will eventually see the Linux kernel boot." +"At the SRM prompt (<prompt>>>></prompt>), issue the following " +"command: <informalexample><screen>\n" +">>> boot dva0 -flags 0\n" +"</screen></informalexample> possibly replacing <filename>dva0</filename> " +"with the actual device name. Usually, <filename>dva0</filename> is the " +"floppy; type <informalexample><screen>\n" +">>> show dev\n" +"</screen></informalexample> to see the list of devices (e.g., if you want to " +"boot from a CD). Note that if you are booting via MILO, <command>-flags</" +"command> argument is ignored, so you can just type <command>boot dva0</" +"command>. If everything works OK, you will eventually see the Linux kernel " +"boot." msgstr "" #. Tag: para #: boot-installer.xml:403 #, no-c-format msgid "" - "If you want to specify kernel parameters when booting via <command>aboot</command>, use the following command: <informalexample><screen>\n" - ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 load_ramdisk=1 arguments\"\n" - "</screen></informalexample> (typed on one line), substituting, if necessary, the actual SRM boot device name for <filename>dva0</filename>, the Linux boot device name for <filename>fd0</filename>, and the desired kernel parameters for <filename>arguments</filename>." +"If you want to specify kernel parameters when booting via <command>aboot</" +"command>, use the following command: <informalexample><screen>\n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +"</screen></informalexample> (typed on one line), substituting, if necessary, " +"the actual SRM boot device name for <filename>dva0</filename>, the Linux " +"boot device name for <filename>fd0</filename>, and the desired kernel " +"parameters for <filename>arguments</filename>." msgstr "" #. Tag: para #: boot-installer.xml:415 #, no-c-format -msgid "If you want to specify kernel parameters when booting via <command>MILO</command>, you will have to interrupt bootstrap once you get into MILO. See <xref linkend=\"booting-from-milo\"/>." +msgid "" +"If you want to specify kernel parameters when booting via <command>MILO</" +"command>, you will have to interrupt bootstrap once you get into MILO. See " +"<xref linkend=\"booting-from-milo\"/>." msgstr "" #. Tag: title @@ -468,7 +608,10 @@ msgstr "" #. Tag: para #: boot-installer.xml:427 #, no-c-format -msgid "In the OS Selection menu, set <command>linload.exe</command> as the boot loader, and <command>milo</command> as the OS Path. Bootstrap using the newly created entry." +msgid "" +"In the OS Selection menu, set <command>linload.exe</command> as the boot " +"loader, and <command>milo</command> as the OS Path. Bootstrap using the " +"newly created entry." msgstr "" #. Tag: title @@ -480,16 +623,24 @@ msgstr "" #. Tag: para #: boot-installer.xml:437 #, no-c-format -msgid "MILO contained on the bootstrap media is configured to proceed straight to Linux automatically. Should you wish to intervene, all you need is to press space during MILO countdown." +msgid "" +"MILO contained on the bootstrap media is configured to proceed straight to " +"Linux automatically. Should you wish to intervene, all you need is to press " +"space during MILO countdown." msgstr "" #. Tag: para #: boot-installer.xml:443 #, no-c-format msgid "" - "If you want to specify all the bits explicitly (for example, to supply additional parameters), you can use a command like this: <informalexample><screen>\n" - "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->\n" - "</screen></informalexample> If you are booting from something other than a floppy, substitute <filename>fd0</filename> in the above example with the appropriate device name in Linux notation. The <command>help</command> command would give you a brief MILO command reference." +"If you want to specify all the bits explicitly (for example, to supply " +"additional parameters), you can use a command like this: " +"<informalexample><screen>\n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->\n" +"</screen></informalexample> If you are booting from something other than a " +"floppy, substitute <filename>fd0</filename> in the above example with the " +"appropriate device name in Linux notation. The <command>help</command> " +"command would give you a brief MILO command reference." msgstr "" #. Tag: title @@ -499,21 +650,30 @@ msgid "Booting from TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:468 boot-installer.xml:1056 boot-installer.xml:1559 boot-installer.xml:2044 boot-installer.xml:2565 boot-installer.xml:2664 +#: boot-installer.xml:468 boot-installer.xml:1056 boot-installer.xml:1595 +#: boot-installer.xml:2080 boot-installer.xml:2601 boot-installer.xml:2700 #, no-c-format -msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)." +msgid "" +"Booting from the network requires that you have a network connection and a " +"TFTP network boot server (DHCP, RARP, or BOOTP)." msgstr "" #. Tag: para -#: boot-installer.xml:473 boot-installer.xml:1061 boot-installer.xml:1564 boot-installer.xml:2049 boot-installer.xml:2570 boot-installer.xml:2669 +#: boot-installer.xml:473 boot-installer.xml:1061 boot-installer.xml:1600 +#: boot-installer.xml:2085 boot-installer.xml:2606 boot-installer.xml:2705 #, no-c-format -msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server." +msgid "" +"Older systems such as the 715 might require the use of an RBOOT server " +"instead of a BOOTP server." msgstr "" #. Tag: para -#: boot-installer.xml:478 boot-installer.xml:1066 boot-installer.xml:1569 boot-installer.xml:2054 boot-installer.xml:2575 boot-installer.xml:2674 +#: boot-installer.xml:478 boot-installer.xml:1066 boot-installer.xml:1605 +#: boot-installer.xml:2090 boot-installer.xml:2611 boot-installer.xml:2710 #, no-c-format -msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>." +msgid "" +"The installation method to support network booting is described in <xref " +"linkend=\"install-tftp\"/>." msgstr "" #. Tag: title @@ -525,40 +685,66 @@ msgstr "" #. Tag: para #: boot-installer.xml:487 #, no-c-format -msgid "Netwinders have two network interfaces: A 10Mbps NE2000-compatible card (which is generally referred to as <literal>eth0</literal>) and a 100Mbps Tulip card. There may be problems loading the image via TFTP using the 100Mbps card so it is recommended that you use the 10Mbps interface (the one labeled with <literal>10 Base-T</literal>)." +msgid "" +"Netwinders have two network interfaces: A 10Mbps NE2000-compatible card " +"(which is generally referred to as <literal>eth0</literal>) and a 100Mbps " +"Tulip card. There may be problems loading the image via TFTP using the " +"100Mbps card so it is recommended that you use the 10Mbps interface (the one " +"labeled with <literal>10 Base-T</literal>)." msgstr "" #. Tag: para #: boot-installer.xml:496 #, no-c-format -msgid "You need NeTTrom 2.2.1 or later to boot the installation system, and version 2.3.3 is recommended. Unfortunately, firmware files are currently not available for download because of license issues. If this situation changes, you may find new images at <ulink url=\"http//www.netwinder.org/\"></ulink>." +msgid "" +"You need NeTTrom 2.2.1 or later to boot the installation system, and version " +"2.3.3 is recommended. Unfortunately, firmware files are currently not " +"available for download because of license issues. If this situation changes, " +"you may find new images at <ulink url=\"http//www.netwinder.org/\"></ulink>." msgstr "" #. Tag: para #: boot-installer.xml:504 #, no-c-format msgid "" - "When you boot your Netwinder you have to interrupt the boot process during the countdown. This allows you to set a number of firmware settings needed in order to boot the installer. First of all, start by loading the default settings: <informalexample><screen>\n" - " NeTTrom command-> load-defaults\n" - "</screen></informalexample> Furthermore, you must configure the network, either with a static address: <informalexample><screen>\n" - " NeTTrom command-> setenv netconfig_eth0 flash\n" - " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" - "</screen></informalexample> where 24 is the number of set bits in the netmask, or a dynamic address: <informalexample><screen>\n" - " NeTTrom command-> setenv netconfig_eth0 dhcp\n" - "</screen></informalexample> You may also need to configure the <userinput>route1</userinput> settings if the TFTP server is not on the local subnet. Following these settings, you have to specify the TFTP server and the location of the image. You can then store your settings to flash. <informalexample><screen>\n" - " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" - " NeTTrom command-> setenv kerntftpfile boot.img\n" - " NeTTrom command-> save-all\n" - "</screen></informalexample> Now you have to tell the firmware that the TFTP image should be booted: <informalexample><screen>\n" - " NeTTrom command-> setenv kernconfig tftp\n" - " NeTTrom command-> setenv rootdev /dev/ram\n" - "</screen></informalexample> If you use a serial console to install your Netwinder, you need to add the following setting: <informalexample><screen>\n" - " NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200\n" - "</screen></informalexample> Alternatively, for installations using a keyboard and monitor you have to set: <informalexample><screen>\n" - " NeTTrom command-> setenv cmdappend root=/dev/ram\n" - "</screen></informalexample> You can use the <command>printenv</command> command to review your environment settings. After you have verified that the settings are correct, you can load the image: <informalexample><screen>\n" - " NeTTrom command-> boot\n" - "</screen></informalexample> In case you run into any problems, a <ulink url=\"http://www.netwinder.org/howto/Firmware-HOWTO.html\">detailed HOWTO</ulink> is available." +"When you boot your Netwinder you have to interrupt the boot process during " +"the countdown. This allows you to set a number of firmware settings needed " +"in order to boot the installer. First of all, start by loading the default " +"settings: <informalexample><screen>\n" +" NeTTrom command-> load-defaults\n" +"</screen></informalexample> Furthermore, you must configure the network, " +"either with a static address: <informalexample><screen>\n" +" NeTTrom command-> setenv netconfig_eth0 flash\n" +" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" +"</screen></informalexample> where 24 is the number of set bits in the " +"netmask, or a dynamic address: <informalexample><screen>\n" +" NeTTrom command-> setenv netconfig_eth0 dhcp\n" +"</screen></informalexample> You may also need to configure the " +"<userinput>route1</userinput> settings if the TFTP server is not on the " +"local subnet. Following these settings, you have to specify the TFTP server " +"and the location of the image. You can then store your settings to flash. " +"<informalexample><screen>\n" +" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" +" NeTTrom command-> setenv kerntftpfile boot.img\n" +" NeTTrom command-> save-all\n" +"</screen></informalexample> Now you have to tell the firmware that the TFTP " +"image should be booted: <informalexample><screen>\n" +" NeTTrom command-> setenv kernconfig tftp\n" +" NeTTrom command-> setenv rootdev /dev/ram\n" +"</screen></informalexample> If you use a serial console to install your " +"Netwinder, you need to add the following setting: <informalexample><screen>\n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +"</screen></informalexample> Alternatively, for installations using a " +"keyboard and monitor you have to set: <informalexample><screen>\n" +" NeTTrom command-> setenv cmdappend root=/dev/ram\n" +"</screen></informalexample> You can use the <command>printenv</command> " +"command to review your environment settings. After you have verified that " +"the settings are correct, you can load the image: <informalexample><screen>\n" +" NeTTrom command-> boot\n" +"</screen></informalexample> In case you run into any problems, a <ulink url=" +"\"http://www.netwinder.org/howto/Firmware-HOWTO.html\">detailed HOWTO</" +"ulink> is available." msgstr "" #. Tag: title @@ -570,7 +756,9 @@ msgstr "" #. Tag: para #: boot-installer.xml:557 #, no-c-format -msgid "On CATS machines, use <command>boot de0:</command> or similar at the Cyclone prompt." +msgid "" +"On CATS machines, use <command>boot de0:</command> or similar at the Cyclone " +"prompt." msgstr "" #. Tag: title @@ -580,33 +768,55 @@ msgid "Booting from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1178 boot-installer.xml:2001 boot-installer.xml:2347 boot-installer.xml:2702 +#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1214 +#: boot-installer.xml:2037 boot-installer.xml:2383 boot-installer.xml:2738 #, no-c-format -msgid "The easiest route for most people will be to use a set of Debian CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply <phrase arch=\"x86\"> configure your system for booting off a CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert your CD, reboot, and proceed to the next chapter." +msgid "" +"The easiest route for most people will be to use a set of Debian CDs. If you " +"have a CD set, and if your machine supports booting directly off the CD, " +"great! Simply <phrase arch=\"x86\"> configure your system for booting off a " +"CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert " +"your CD, reboot, and proceed to the next chapter." msgstr "" #. Tag: para -#: boot-installer.xml:584 boot-installer.xml:754 boot-installer.xml:1189 boot-installer.xml:2012 boot-installer.xml:2358 boot-installer.xml:2713 +#: boot-installer.xml:584 boot-installer.xml:754 boot-installer.xml:1225 +#: boot-installer.xml:2048 boot-installer.xml:2394 boot-installer.xml:2749 #, no-c-format -msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you." +msgid "" +"Note that certain CD drives may require special drivers, and thus be " +"inaccessible in the early installation stages. If it turns out the standard " +"way of booting off a CD doesn't work for your hardware, revisit this chapter " +"and read about alternate kernels and installation methods which may work for " +"you." msgstr "" #. Tag: para -#: boot-installer.xml:592 boot-installer.xml:762 boot-installer.xml:1197 boot-installer.xml:2020 boot-installer.xml:2366 boot-installer.xml:2721 +#: boot-installer.xml:592 boot-installer.xml:762 boot-installer.xml:1233 +#: boot-installer.xml:2056 boot-installer.xml:2402 boot-installer.xml:2757 #, no-c-format -msgid "Even if you cannot boot from CD-ROM, you can probably install the Debian system components and any packages you want from CD-ROM. Simply boot using a different media, such as floppies. When it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive." +msgid "" +"Even if you cannot boot from CD-ROM, you can probably install the Debian " +"system components and any packages you want from CD-ROM. Simply boot using a " +"different media, such as floppies. When it's time to install the operating " +"system, base system, and any additional packages, point the installation " +"system at the CD-ROM drive." msgstr "" #. Tag: para -#: boot-installer.xml:600 boot-installer.xml:770 boot-installer.xml:1205 boot-installer.xml:2028 boot-installer.xml:2374 boot-installer.xml:2729 +#: boot-installer.xml:600 boot-installer.xml:770 boot-installer.xml:1241 +#: boot-installer.xml:2064 boot-installer.xml:2410 boot-installer.xml:2765 #, no-c-format -msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." +msgid "" +"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." msgstr "" #. Tag: para #: boot-installer.xml:607 #, no-c-format -msgid "To boot a CD-ROM from the Cyclone console prompt, use the command <command>boot cd0:cats.bin</command>" +msgid "" +"To boot a CD-ROM from the Cyclone console prompt, use the command " +"<command>boot cd0:cats.bin</command>" msgstr "" #. Tag: title @@ -618,13 +828,20 @@ msgstr "" #. Tag: para #: boot-installer.xml:622 #, no-c-format -msgid "There is an increasing number of consumer devices that directly boot from a flash chip on the device. The installer can be written to flash so it will automatically start when you reboot your machines." +msgid "" +"There is an increasing number of consumer devices that directly boot from a " +"flash chip on the device. The installer can be written to flash so it will " +"automatically start when you reboot your machines." msgstr "" #. Tag: para #: boot-installer.xml:628 #, no-c-format -msgid "In many cases, changing the firmware of an embedded device voids your warranty. Sometimes you are also not able to recover your device if there are problems during the flashing process. Therefore, please take care and follow the steps precisely." +msgid "" +"In many cases, changing the firmware of an embedded device voids your " +"warranty. Sometimes you are also not able to recover your device if there " +"are problems during the flashing process. Therefore, please take care and " +"follow the steps precisely." msgstr "" #. Tag: title @@ -648,7 +865,12 @@ msgstr "" #. Tag: para #: boot-installer.xml:647 #, no-c-format -msgid "Go to the administration section and choose the menu item <literal>Upgrade</literal>. You can then browse your disk for the installer image you have previously downloaded. Then press the <literal>Start Upgrade</literal> button, confirm, wait for a few minutes and confirm again. The system will then boot straight into the installer." +msgid "" +"Go to the administration section and choose the menu item <literal>Upgrade</" +"literal>. You can then browse your disk for the installer image you have " +"previously downloaded. Then press the <literal>Start Upgrade</literal> " +"button, confirm, wait for a few minutes and confirm again. The system will " +"then boot straight into the installer." msgstr "" #. Tag: title @@ -661,9 +883,29 @@ msgstr "" #: boot-installer.xml:659 #, no-c-format msgid "" - "You can use <command>upslug2</command> from any Linux or Unix machine to upgrade the machine via the network. This software is packaged for Debian. First, you have to put your NSLU2 in upgrade mode: <orderedlist> <listitem><para> Disconnect any disks and/or devices from the USB ports. </para></listitem> <listitem><para> Power off the NSLU2 </para></listitem> <listitem><para> Press and hold the reset button (accessible through the small hole on the back just above the power input). </para></listitem> <listitem><para> Press and release the power button to power on the NSLU2. </para></listitem> <listitem><para> Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset button. </para></listitem> <listitem><para> The NSLU2 ready/status LED will flash alternately red/green (there is a 1 second delay before the first green). The NSLU2 is now in upgrade mode. </para></listitem> </orderedlist> See the <ulink url=\"http://www.nslu2-linux.org/wiki/OpenSlug/UsingTheBinary\">NSLU2-Linux pages</ulink> if you have problems with this. Once your NSLU2 is in upgrade mode, you can flash the new image: <informalexample><screen>\n" - "sudo upslug2 -i di-nslu2.bin\n" - "</screen></informalexample> Note that the tool also shows the MAC address of your NSLU2, which may come in handy to configure your DHCP server. After the whole image has been written and verified, the system will automatically reboot. Make sure you connect your USB disk again now, otherwise the installer won't be able to find it." +"You can use <command>upslug2</command> from any Linux or Unix machine to " +"upgrade the machine via the network. This software is packaged for Debian. " +"First, you have to put your NSLU2 in upgrade mode: <orderedlist> " +"<listitem><para> Disconnect any disks and/or devices from the USB ports. </" +"para></listitem> <listitem><para> Power off the NSLU2 </para></listitem> " +"<listitem><para> Press and hold the reset button (accessible through the " +"small hole on the back just above the power input). </para></listitem> " +"<listitem><para> Press and release the power button to power on the NSLU2. </" +"para></listitem> <listitem><para> Wait for 10 seconds watching the ready/" +"status LED. After 10 seconds it will change from amber to red. Immediately " +"release the reset button. </para></listitem> <listitem><para> The NSLU2 " +"ready/status LED will flash alternately red/green (there is a 1 second delay " +"before the first green). The NSLU2 is now in upgrade mode. </para></" +"listitem> </orderedlist> See the <ulink url=\"http://www.nslu2-linux.org/" +"wiki/OpenSlug/UsingTheBinary\">NSLU2-Linux pages</ulink> if you have " +"problems with this. Once your NSLU2 is in upgrade mode, you can flash the " +"new image: <informalexample><screen>\n" +"sudo upslug2 -i di-nslu2.bin\n" +"</screen></informalexample> Note that the tool also shows the MAC address of " +"your NSLU2, which may come in handy to configure your DHCP server. After the " +"whole image has been written and verified, the system will automatically " +"reboot. Make sure you connect your USB disk again now, otherwise the " +"installer won't be able to find it." msgstr "" #. Tag: title @@ -675,11 +917,15 @@ msgstr "" #. Tag: para #: boot-installer.xml:721 #, no-c-format -msgid "There is <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmware/all_router_utility.zip\">a tool</ulink> for Windows to upgrade the firmware via the network." +msgid "" +"There is <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmware/" +"all_router_utility.zip\">a tool</ulink> for Windows to upgrade the firmware " +"via the network." msgstr "" #. Tag: title -#: boot-installer.xml:737 boot-installer.xml:1172 boot-installer.xml:1989 boot-installer.xml:2341 boot-installer.xml:2696 +#: boot-installer.xml:737 boot-installer.xml:1208 boot-installer.xml:2025 +#: boot-installer.xml:2377 boot-installer.xml:2732 #, no-c-format msgid "Booting from a CD-ROM" msgstr "" @@ -693,81 +939,123 @@ msgstr "" #. Tag: para #: boot-installer.xml:845 #, no-c-format -msgid "To start the installer from Windows, you must first obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in <xref linkend=\"official-cdrom\"/> and <xref linkend=\"boot-usb-files\"/>." +msgid "" +"To start the installer from Windows, you must first obtain CD-ROM/DVD-ROM or " +"USB memory stick installation media as described in <xref linkend=\"official-" +"cdrom\"/> and <xref linkend=\"boot-usb-files\"/>." msgstr "" #. Tag: para #: boot-installer.xml:851 #, no-c-format -msgid "If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing <command>setup.exe</command>." +msgid "" +"If you use an installation CD or DVD, a pre-installation program should be " +"launched automatically when you insert the disc. In case Windows does not " +"start it automatically, or if you are using a USB memory stick, you can run " +"it manually by accessing the device and executing <command>setup.exe</" +"command>." msgstr "" #. Tag: para #: boot-installer.xml:859 #, no-c-format -msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to start the &debian; installer." +msgid "" +"After the program has been started, a few preliminary questions will be " +"asked and the system will be prepared to start the &debian; installer." msgstr "" #. Tag: title #: boot-installer.xml:899 #, no-c-format -msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" +msgid "" +"Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para #: boot-installer.xml:902 #, no-c-format -msgid "To boot the installer from hard disk, you must first download and place the needed files as described in <xref linkend=\"boot-drive-files\"/>." +msgid "" +"To boot the installer from hard disk, you must first download and place the " +"needed files as described in <xref linkend=\"boot-drive-files\"/>." msgstr "" #. Tag: para #: boot-installer.xml:907 #, no-c-format -msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/&architecture;/initrd.gz</filename> file and its corresponding kernel <filename>netboot/debian-installer/&architecture;/linux</filename>. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care." +msgid "" +"If you intend to use the hard drive only for booting and then download " +"everything over the network, you should download the <filename>netboot/" +"debian-installer/&architecture;/initrd.gz</filename> file and its " +"corresponding kernel <filename>netboot/debian-installer/&architecture;/" +"linux</filename>. This will allow you to repartition the hard disk from " +"which you boot the installer, although you should do so with care." msgstr "" #. Tag: para #: boot-installer.xml:917 #, no-c-format -msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD image, without needing the network." +msgid "" +"Alternatively, if you intend to keep an existing partition on the hard drive " +"unchanged during the install, you can download the <filename>hd-media/initrd." +"gz</filename> file and its kernel, as well as copy a CD iso to the drive " +"(make sure the file is named ending in <literal>.iso</literal>). The " +"installer can then boot from the drive and install from the CD image, " +"without needing the network." msgstr "" #. Tag: para #: boot-installer.xml:926 #, no-c-format -msgid "For <command>LILO</command>, you will need to configure two essential things in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to load the <filename>initrd.gz</filename> installer at boot time; </para></listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is a <filename>/etc/lilo.conf</filename> example:" +msgid "" +"For <command>LILO</command>, you will need to configure two essential things " +"in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to " +"load the <filename>initrd.gz</filename> installer at boot time; </para></" +"listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use " +"a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is " +"a <filename>/etc/lilo.conf</filename> example:" msgstr "" #. Tag: screen #: boot-installer.xml:947 #, no-c-format msgid "" - "image=/boot/newinstall/vmlinuz\n" - " label=newinstall\n" - " initrd=/boot/newinstall/initrd.gz" +"image=/boot/newinstall/vmlinuz\n" +" label=newinstall\n" +" initrd=/boot/newinstall/initrd.gz" msgstr "" #. Tag: para #: boot-installer.xml:947 #, no-c-format -msgid "For more details, refer to the <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> and <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and reboot." +msgid "" +"For more details, refer to the <citerefentry><refentrytitle>initrd</" +"refentrytitle> <manvolnum>4</manvolnum></citerefentry> and " +"<citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</" +"manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and " +"reboot." msgstr "" #. Tag: para #: boot-installer.xml:956 #, no-c-format msgid "" - "The procedure for <command>GRUB</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (sometimes in the <filename>/boot/boot/grub/</filename>), add the following lines: <informalexample><screen>\n" - "title New Install\n" - "kernel (hd0,0)/boot/newinstall/vmlinuz\n" - "initrd (hd0,0)/boot/newinstall/initrd.gz\n" - "</screen></informalexample> and reboot." +"The procedure for <command>GRUB</command> is quite similar. Locate your " +"<filename>menu.lst</filename> in the <filename>/boot/grub/</filename> " +"directory (sometimes in the <filename>/boot/boot/grub/</filename>), add the " +"following lines: <informalexample><screen>\n" +"title New Install\n" +"kernel (hd0,0)/boot/newinstall/vmlinuz\n" +"initrd (hd0,0)/boot/newinstall/initrd.gz\n" +"</screen></informalexample> and reboot." msgstr "" #. Tag: para #: boot-installer.xml:967 #, no-c-format -msgid "Note that the value of the <userinput>ramdisk_size</userinput> may need to be adjusted for the size of the initrd image. From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>." +msgid "" +"Note that the value of the <userinput>ramdisk_size</userinput> may need to " +"be adjusted for the size of the initrd image. From here on, there should be " +"no difference between <command>GRUB</command> or <command>LILO</command>." msgstr "" #. Tag: title @@ -779,55 +1067,87 @@ msgstr "" #. Tag: para #: boot-installer.xml:979 #, no-c-format -msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;." +msgid "" +"Let's assume you have prepared everything from <xref linkend=\"boot-dev-" +"select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB " +"stick into some free USB connector and reboot the computer. The system " +"should boot up, and you should be presented with the <prompt>boot:</prompt> " +"prompt. Here you can enter optional boot arguments, or just hit &enterkey;." msgstr "" #. Tag: title -#: boot-installer.xml:992 boot-installer.xml:2101 boot-installer.xml:2604 +#: boot-installer.xml:992 boot-installer.xml:2137 boot-installer.xml:2640 #, no-c-format msgid "Booting from Floppies" msgstr "" #. Tag: para -#: boot-installer.xml:993 boot-installer.xml:2612 +#: boot-installer.xml:993 boot-installer.xml:2648 #, no-c-format -msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>." +msgid "" +"You will have already downloaded the floppy images you needed and created " +"floppies from the images in <xref linkend=\"create-floppy\"/>." msgstr "" #. Tag: para #: boot-installer.xml:1000 #, no-c-format -msgid "To boot from the installer boot floppy, place it in the primary floppy drive, shut down the system as you normally would, then turn it back on." +msgid "" +"To boot from the installer boot floppy, place it in the primary floppy " +"drive, shut down the system as you normally would, then turn it back on." msgstr "" #. Tag: para #: boot-installer.xml:1006 #, no-c-format -msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>install root=/dev/hdc</userinput> at the boot prompt." +msgid "" +"For installing from an LS-120 drive (ATAPI version) with a set of floppies, " +"you need to specify the virtual location for the floppy device. This is done " +"with the <emphasis>root=</emphasis> boot argument, giving the device that " +"the ide-floppy driver maps the device to. For example, if your LS-120 drive " +"is connected as the first IDE device (master) on the second cable, you enter " +"<userinput>install root=/dev/hdc</userinput> at the boot prompt." msgstr "" #. Tag: para #: boot-installer.xml:1016 #, no-c-format -msgid "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not properly reset the machine, so a <quote>hard</quote> reboot is recommended. If you are installing from an existing operating system (e.g., from a DOS box) you don't have a choice. Otherwise, please do a hard reboot when booting." +msgid "" +"Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</" +"keycap> <keycap>Delete</keycap></keycombo> does not properly reset the " +"machine, so a <quote>hard</quote> reboot is recommended. If you are " +"installing from an existing operating system (e.g., from a DOS box) you " +"don't have a choice. Otherwise, please do a hard reboot when booting." msgstr "" #. Tag: para #: boot-installer.xml:1025 #, no-c-format -msgid "The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt." +msgid "" +"The floppy disk will be accessed, and you should then see a screen that " +"introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt." msgstr "" #. Tag: para #: boot-installer.xml:1031 #, no-c-format -msgid "Once you press &enterkey;, you should see the message <computeroutput>Loading...</computeroutput>, followed by <computeroutput>Uncompressing Linux...</computeroutput>, and then a screenfull or so of information about the hardware in your system. More information on this phase of the boot process can be found below in <xref linkend=\"kernel-msgs\"/>." +msgid "" +"Once you press &enterkey;, you should see the message " +"<computeroutput>Loading...</computeroutput>, followed by " +"<computeroutput>Uncompressing Linux...</computeroutput>, and then a " +"screenfull or so of information about the hardware in your system. More " +"information on this phase of the boot process can be found below in <xref " +"linkend=\"kernel-msgs\"/>." msgstr "" #. Tag: para #: boot-installer.xml:1040 #, no-c-format -msgid "After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched." +msgid "" +"After booting from the boot floppy, the root floppy is requested. Insert the " +"root floppy and press &enterkey;, and the contents are loaded into memory. " +"The installer program <command>debian-installer</command> is automatically " +"launched." msgstr "" #. Tag: para @@ -845,7 +1165,11 @@ msgstr "" #. Tag: para #: boot-installer.xml:1081 #, no-c-format -msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel</trademark> re-implementation of TFTP boot. If so, you may be able to configure your BIOS to boot from the network." +msgid "" +"It could be that your Network Interface Card or Motherboard provides PXE " +"boot functionality. This is a <trademark class=\"trade\">Intel</trademark> " +"re-implementation of TFTP boot. If so, you may be able to configure your " +"BIOS to boot from the network." msgstr "" #. Tag: title @@ -857,13 +1181,17 @@ msgstr "" #. Tag: para #: boot-installer.xml:1093 #, no-c-format -msgid "It could be that your Network Interface Card provides TFTP boot functionality." +msgid "" +"It could be that your Network Interface Card provides TFTP boot " +"functionality." msgstr "" #. Tag: para #: boot-installer.xml:1098 #, no-c-format -msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document." +msgid "" +"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. " +"Please refer to this document." msgstr "" #. Tag: title @@ -875,1929 +1203,2932 @@ msgstr "" #. Tag: para #: boot-installer.xml:1107 #, no-c-format -msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot." +msgid "" +"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> " +"provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" #. Tag: title -#: boot-installer.xml:1116 +#: boot-installer.xml:1117 #, no-c-format -msgid "The Boot Prompt" +msgid "The Boot Screen" msgstr "" #. Tag: para -#: boot-installer.xml:1117 +#: boot-installer.xml:1118 +#, no-c-format +msgid "" +"When the installer boots, you should be presented with a friendly graphical " +"screen showing the Debian logo and a menu: <informalexample><screen>\n" +"Installer boot menu\n" +"\n" +"Install\n" +"Graphical install\n" +"Advanced options >\n" +"Help\n" +"\n" +"Press ENTER to boot or TAB to edit a menu entry\n" +"</screen></informalexample> Depending on the installation method you are " +"using, the <quote>Graphical install</quote> option may not be available." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1128 +#, no-c-format +msgid "" +"For a normal installation, select either the <quote>Install</quote> or the " +"<quote>Graphical install</quote> entry — using either the arrow keys " +"on your keyboard or by typing the first (highlighted) letter — and " +"press &enterkey; to boot the installer." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1135 +#, no-c-format +msgid "" +"The <quote>Advanced options</quote> entry gives access to a second menu that " +"allows to boot the installer in expert mode, in rescue mode and for " +"automated installs." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1141 +#, no-c-format +msgid "" +"If you wish or need to add any boot parameters for either the installer or " +"the kernel, press &tabkey;. This will display the default boot command for " +"the selected menu entry and allow to add additional options. The help " +"screens (see below) list some common possible options. Press &enterkey; to " +"boot the installer with your options; pressing &escapekey; will return you " +"to the boot menu." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1150 +#, no-c-format +msgid "" +"Choosing the <quote>Help</quote> entry will result in the first help screen " +"being displayed which gives an overview of all available help screens. Note " +"that it is not possible to return to the boot menu after the help screens " +"have been displayed. However, the F3 and F4 help screens list commands that " +"are equivalent to the boot methods listed in the menu. All help screens have " +"a boot prompt at which the boot command can be typed: " +"<informalexample><screen>\n" +"Press F1 for the help index, or ENTER to boot:\n" +"</screen></informalexample> At this boot prompt you can either just press " +"&enterkey; to boot the installer with default options or enter a specific " +"boot command and, optionally, boot parameters. A number of boot parameters " +"which might be useful can be found on the various help screens. If you do " +"add any parameters to the boot command line, be sure to first type the boot " +"method (the default is <userinput>install</userinput>) and a space before " +"the first parameter (e.g., <userinput>install fb=false</userinput>)." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1169 #, no-c-format msgid "" - "When the installer boots, you should be presented with a friendly graphical screen showing the Debian logo and the boot prompt: <informalexample><screen>\n" - "Press F1 for help, or ENTER to boot:\n" - "</screen></informalexample> At the boot prompt you can either just press &enterkey; to boot the installer with default options or enter a specific boot method and, optionally, boot parameters." +"The keyboard is assumed to have a default American English layout at this " +"point. This means that if your keyboard has a different (language-specific) " +"layout, the characters that appear on the screen may be different from what " +"you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-" +"keymap;\">schema of the US keyboard layout</ulink> which can be used as a " +"reference to find the correct keys to use." msgstr "" #. Tag: para -#: boot-installer.xml:1129 +#: boot-installer.xml:1179 #, no-c-format -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>install</userinput>) and a space before the first parameter (e.g., <userinput>install fb=false</userinput>)." +msgid "" +"If you are using a system that has the BIOS configured to use serial " +"console, you may not be able to see the initial graphical splash screen upon " +"booting the installer; you may even not see the boot menu. The same can " +"happen if you are installing the system via a remote management device that " +"provides a text interface to the VGA console. 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)." msgstr "" #. Tag: para -#: boot-installer.xml:1138 +#: boot-installer.xml:1189 #, no-c-format -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." +msgid "" +"To bypass the graphical boot screen you can either blindly press &escapekey; " +"to get a text boot prompt, or (equally blindly) press <quote>H</quote> " +"followed by &enterkey; to select the <quote>Help</quote> option described " +"above. After that your keystrokes should be echoed at the prompt. 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 "" #. Tag: title -#: boot-installer.xml:1213 +#: boot-installer.xml:1249 #, no-c-format msgid "CD Contents" msgstr "" #. Tag: para -#: boot-installer.xml:1215 +#: boot-installer.xml:1251 #, no-c-format -msgid "There are three basic variations of Debian Install CDs. The <emphasis>Business Card</emphasis> CD has a minimal installation that will fit on the small form factor CD media. It requires a network connection in order to install the rest of the base installation and make a usable system. The <emphasis>Network Install</emphasis> CD has all of the packages for a base install but requires a network connection to a Debian mirror site in order to install the extra packages one would want for a complete system . The set of Debian CDs can install a complete system from the wide range of packages without needing access to the network." +msgid "" +"There are three basic variations of Debian Install CDs. The " +"<emphasis>Business Card</emphasis> CD has a minimal installation that will " +"fit on the small form factor CD media. It requires a network connection in " +"order to install the rest of the base installation and make a usable system. " +"The <emphasis>Network Install</emphasis> CD has all of the packages for a " +"base install but requires a network connection to a Debian mirror site in " +"order to install the extra packages one would want for a complete system . " +"The set of Debian CDs can install a complete system from the wide range of " +"packages without needing access to the network." msgstr "" #. Tag: para -#: boot-installer.xml:1231 +#: boot-installer.xml:1267 #, no-c-format -msgid "The IA-64 architecture uses the next generation Extensible Firmware Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows little about the boot device other than the partition table and Master Boot Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted disk partitions. This simplifies the often arcane process of starting a system. The system boot loader and the EFI firmware that supports it have a full filesystem to store the files necessary for booting the machine. This means that the system disk on an IA-64 system has an additional disk partition dedicated to EFI instead of the simple MBR or boot block on more conventional systems." +msgid "" +"The IA-64 architecture uses the next generation Extensible Firmware " +"Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows " +"little about the boot device other than the partition table and Master Boot " +"Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted " +"disk partitions. This simplifies the often arcane process of starting a " +"system. The system boot loader and the EFI firmware that supports it have a " +"full filesystem to store the files necessary for booting the machine. This " +"means that the system disk on an IA-64 system has an additional disk " +"partition dedicated to EFI instead of the simple MBR or boot block on more " +"conventional systems." msgstr "" #. Tag: para -#: boot-installer.xml:1247 +#: boot-installer.xml:1283 #, no-c-format -msgid "The Debian Installer CD contains a small EFI partition where the <command>ELILO</command> bootloader, its configuration file, the installer's kernel, and initial filesystem (initrd) are located. The running system also contains an EFI partition where the necessary files for booting the system reside. These files are readable from the EFI Shell as described below." +msgid "" +"The Debian Installer CD contains a small EFI partition where the " +"<command>ELILO</command> bootloader, its configuration file, the installer's " +"kernel, and initial filesystem (initrd) are located. The running system also " +"contains an EFI partition where the necessary files for booting the system " +"reside. These files are readable from the EFI Shell as described below." msgstr "" #. Tag: para -#: boot-installer.xml:1256 +#: boot-installer.xml:1292 #, no-c-format -msgid "Most of the details of how <command>ELILO</command> actually loads and starts a system are transparent to the system installer. However, the installer must set up an EFI partition prior to installing the base system. Otherwise, the installation of <command>ELILO</command> will fail, rendering the system un-bootable. The EFI partition is allocated and formatted in the partitioning step of the installation prior to loading any packages on the system disk. The partitioning task also verifies that a suitable EFI partition is present before allowing the installation to proceed." +msgid "" +"Most of the details of how <command>ELILO</command> actually loads and " +"starts a system are transparent to the system installer. However, the " +"installer must set up an EFI partition prior to installing the base system. " +"Otherwise, the installation of <command>ELILO</command> will fail, rendering " +"the system un-bootable. The EFI partition is allocated and formatted in the " +"partitioning step of the installation prior to loading any packages on the " +"system disk. The partitioning task also verifies that a suitable EFI " +"partition is present before allowing the installation to proceed." msgstr "" #. Tag: para -#: boot-installer.xml:1268 +#: boot-installer.xml:1304 #, no-c-format -msgid "The EFI Boot Manager is presented as the last step of the firmware initialization. It displays a menu list from which the user can select an option. Depending on the model of system and what other software has been loaded on the system, this menu may be different from one system to another. There should be at least two menu items displayed, <command>Boot Option Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. Using the first option is preferred, however, if that option is not available or the CD for some reason does not boot with it, use the second option." +msgid "" +"The EFI Boot Manager is presented as the last step of the firmware " +"initialization. It displays a menu list from which the user can select an " +"option. Depending on the model of system and what other software has been " +"loaded on the system, this menu may be different from one system to another. " +"There should be at least two menu items displayed, <command>Boot Option " +"Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. " +"Using the first option is preferred, however, if that option is not " +"available or the CD for some reason does not boot with it, use the second " +"option." msgstr "" #. Tag: title -#: boot-installer.xml:1287 +#: boot-installer.xml:1323 #, no-c-format msgid "IMPORTANT" msgstr "" #. Tag: para -#: boot-installer.xml:1288 +#: boot-installer.xml:1324 #, no-c-format -msgid "The EFI Boot Manager will select a default boot action, typically the first menu choice, within a pre-set number of seconds. This is indicated by a countdown at the bottom of the screen. Once the timer expires and the systems starts the default action, you may have to reboot the machine in order to continue the installation. If the default action is the EFI Shell, you can return to the Boot Manager by running <command>exit</command> at the shell prompt." +msgid "" +"The EFI Boot Manager will select a default boot action, typically the first " +"menu choice, within a pre-set number of seconds. This is indicated by a " +"countdown at the bottom of the screen. Once the timer expires and the " +"systems starts the default action, you may have to reboot the machine in " +"order to continue the installation. If the default action is the EFI Shell, " +"you can return to the Boot Manager by running <command>exit</command> at the " +"shell prompt." msgstr "" #. Tag: title -#: boot-installer.xml:1300 +#: boot-installer.xml:1336 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "" #. Tag: para -#: boot-installer.xml:1307 +#: boot-installer.xml:1343 #, no-c-format -msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes its system initialization." +msgid "" +"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " +"display the EFI Boot Manager page and menu after it completes its system " +"initialization." msgstr "" #. Tag: para -#: boot-installer.xml:1313 +#: boot-installer.xml:1349 #, no-c-format -msgid "Select <command>Boot Maintenance Menu</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a new menu." +msgid "" +"Select <command>Boot Maintenance Menu</command> from the menu with the arrow " +"keys and press <command>ENTER</command>. This will display a new menu." msgstr "" #. Tag: para -#: boot-installer.xml:1319 +#: boot-installer.xml:1355 #, no-c-format -msgid "Select <command>Boot From a File</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a list of devices probed by the firmware. You should see two menu lines containing either the label <command>Debian Inst [Acpi ...</command> or <command>Removable Media Boot</command>. If you examine the rest of the menu line, you will notice that the device and controller information should be the same." +msgid "" +"Select <command>Boot From a File</command> from the menu with the arrow keys " +"and press <command>ENTER</command>. This will display a list of devices " +"probed by the firmware. You should see two menu lines containing either the " +"label <command>Debian Inst [Acpi ...</command> or <command>Removable Media " +"Boot</command>. If you examine the rest of the menu line, you will notice " +"that the device and controller information should be the same." msgstr "" #. Tag: para -#: boot-installer.xml:1330 +#: boot-installer.xml:1366 #, no-c-format -msgid "You can choose either of the entries that refer to the CD/DVD drive. Select your choice with the arrow keys and press <command>ENTER</command>. If you choose <command>Removable Media Boot</command> the machine will immediately start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</command> instead, it will display a directory listing of the bootable portion of the CD, requiring you to proceed to the next (additional) step." +msgid "" +"You can choose either of the entries that refer to the CD/DVD drive. Select " +"your choice with the arrow keys and press <command>ENTER</command>. If you " +"choose <command>Removable Media Boot</command> the machine will immediately " +"start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</" +"command> instead, it will display a directory listing of the bootable " +"portion of the CD, requiring you to proceed to the next (additional) step." msgstr "" #. Tag: para -#: boot-installer.xml:1341 +#: boot-installer.xml:1377 #, no-c-format -msgid "You will only need this step if you chose <command>Debian Inst [Acpi ...</command>. The directory listing will also show <command>[Treat like Removable Media Boot]</command> on the next to the last line. Select this line with the arrow keys and press <command>ENTER</command>. This will start the boot load sequence." +msgid "" +"You will only need this step if you chose <command>Debian Inst [Acpi ...</" +"command>. The directory listing will also show <command>[Treat like " +"Removable Media Boot]</command> on the next to the last line. Select this " +"line with the arrow keys and press <command>ENTER</command>. This will start " +"the boot load sequence." msgstr "" #. Tag: para -#: boot-installer.xml:1353 +#: boot-installer.xml:1389 #, no-c-format -msgid "These steps start the Debian boot loader which will display a menu page for you to select a boot kernel and options. Proceed to selecting the boot kernel and options." +msgid "" +"These steps start the Debian boot loader which will display a menu page for " +"you to select a boot kernel and options. Proceed to selecting the boot " +"kernel and options." msgstr "" #. Tag: title -#: boot-installer.xml:1363 +#: boot-installer.xml:1399 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "" #. Tag: para -#: boot-installer.xml:1364 +#: boot-installer.xml:1400 #, no-c-format -msgid "If, for some reason, option 1 is not successful, reboot the machine and when the EFI Boot Manager screen appears there should be one option called <command>EFI Shell [Built-in]</command>. Boot the Debian Installer CD with the following steps:" +msgid "" +"If, for some reason, option 1 is not successful, reboot the machine and when " +"the EFI Boot Manager screen appears there should be one option called " +"<command>EFI Shell [Built-in]</command>. Boot the Debian Installer CD with " +"the following steps:" msgstr "" #. Tag: para -#: boot-installer.xml:1375 +#: boot-installer.xml:1411 #, no-c-format -msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes system initialization." +msgid "" +"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " +"display the EFI Boot Manager page and menu after it completes system " +"initialization." msgstr "" #. Tag: para -#: boot-installer.xml:1381 +#: boot-installer.xml:1417 #, no-c-format -msgid "Select <command>EFI Shell</command> from the menu with the arrow keys and press <command>ENTER</command>. The EFI Shell will scan all of the bootable devices and display them to the console before displaying its command prompt. The recognized bootable partitions on devices will show a device name of <filename>fs<replaceable>n</replaceable>:</filename>. All other recognized partitions will be named <filename>blk<replaceable>n</replaceable>:</filename>. If you inserted the CD just before entering the shell, this may take a few extra seconds as it initializes the CD drive." +msgid "" +"Select <command>EFI Shell</command> from the menu with the arrow keys and " +"press <command>ENTER</command>. The EFI Shell will scan all of the bootable " +"devices and display them to the console before displaying its command " +"prompt. The recognized bootable partitions on devices will show a device " +"name of <filename>fs<replaceable>n</replaceable>:</filename>. All other " +"recognized partitions will be named <filename>blk<replaceable>n</" +"replaceable>:</filename>. If you inserted the CD just before entering the " +"shell, this may take a few extra seconds as it initializes the CD drive." msgstr "" #. Tag: para -#: boot-installer.xml:1395 +#: boot-installer.xml:1431 #, no-c-format -msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the <filename>fs0:</filename> device although other devices with bootable partitions will also show up as <filename>fs<replaceable>n</replaceable></filename>." +msgid "" +"Examine the output from the shell looking for the CDROM drive. It is most " +"likely the <filename>fs0:</filename> device although other devices with " +"bootable partitions will also show up as <filename>fs<replaceable>n</" +"replaceable></filename>." msgstr "" #. Tag: para -#: boot-installer.xml:1402 +#: boot-installer.xml:1438 #, no-c-format -msgid "Enter <command>fs<replaceable>n</replaceable>:</command> and press <command>ENTER</command> to select that device where <replaceable>n</replaceable> is the partition number for the CDROM. The shell will now display the partition number as its prompt." +msgid "" +"Enter <command>fs<replaceable>n</replaceable>:</command> and press " +"<command>ENTER</command> to select that device where <replaceable>n</" +"replaceable> is the partition number for the CDROM. The shell will now " +"display the partition number as its prompt." msgstr "" #. Tag: para -#: boot-installer.xml:1409 +#: boot-installer.xml:1445 #, no-c-format -msgid "Enter <command>elilo</command> and press <command>ENTER</command>. This will start the boot load sequence." +msgid "" +"Enter <command>elilo</command> and press <command>ENTER</command>. This will " +"start the boot load sequence." msgstr "" #. Tag: para -#: boot-installer.xml:1416 +#: boot-installer.xml:1452 #, no-c-format -msgid "As with option 1, these steps start the Debian boot loader which will display a menu page for you to select a boot kernel and options. You can also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</command> command at the shell prompt. Proceed to selecting the boot kernel and options." +msgid "" +"As with option 1, these steps start the Debian boot loader which will " +"display a menu page for you to select a boot kernel and options. You can " +"also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</" +"command> command at the shell prompt. Proceed to selecting the boot kernel " +"and options." msgstr "" #. Tag: title -#: boot-installer.xml:1430 +#: boot-installer.xml:1466 #, no-c-format msgid "Installing using a Serial Console" msgstr "" #. Tag: para -#: boot-installer.xml:1432 +#: boot-installer.xml:1468 #, no-c-format -msgid "You may choose to perform an install using a monitor and keyboard or using a serial connection. To use a monitor/keyboard setup, select an option containing the string [VGA console]. To install over a serial connection, choose an option containing the string [<replaceable>BAUD</replaceable> baud serial console], where <replaceable>BAUD</replaceable> is the speed of your serial console. Menu items for the most typical baud rate settings on the ttyS0 device are preconfigured." +msgid "" +"You may choose to perform an install using a monitor and keyboard or using a " +"serial connection. To use a monitor/keyboard setup, select an option " +"containing the string [VGA console]. To install over a serial connection, " +"choose an option containing the string [<replaceable>BAUD</replaceable> baud " +"serial console], where <replaceable>BAUD</replaceable> is the speed of your " +"serial console. Menu items for the most typical baud rate settings on the " +"ttyS0 device are preconfigured." msgstr "" #. Tag: para -#: boot-installer.xml:1443 +#: boot-installer.xml:1479 #, no-c-format -msgid "In most circumstances, you will want the installer to use the same baud rate as your connection to the EFI console. If you aren't sure what this setting is, you can obtain it using the command <command>baud</command> at the EFI shell." +msgid "" +"In most circumstances, you will want the installer to use the same baud rate " +"as your connection to the EFI console. If you aren't sure what this setting " +"is, you can obtain it using the command <command>baud</command> at the EFI " +"shell." msgstr "" #. Tag: para -#: boot-installer.xml:1450 +#: boot-installer.xml:1486 #, no-c-format -msgid "If there is not an option available that is configured for the serial device or baud rate you would like to use, you may override the console setting for one of the existing menu options. For example, to use a 57600 baud console over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into the <classname>Boot:</classname> text window." +msgid "" +"If there is not an option available that is configured for the serial device " +"or baud rate you would like to use, you may override the console setting for " +"one of the existing menu options. For example, to use a 57600 baud console " +"over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into " +"the <classname>Boot:</classname> text window." msgstr "" #. Tag: para -#: boot-installer.xml:1461 +#: boot-installer.xml:1497 #, no-c-format -msgid "Most IA-64 boxes ship with a default console setting of 9600 baud. This setting is rather slow, and the normal installation process will take a significant time to draw each screen. You should consider either increasing the baud rate used for performing the installation, or performing a Text Mode installation. See the <classname>Params</classname> help menu for instructions on starting the installer in Text Mode." +msgid "" +"Most IA-64 boxes ship with a default console setting of 9600 baud. This " +"setting is rather slow, and the normal installation process will take a " +"significant time to draw each screen. You should consider either increasing " +"the baud rate used for performing the installation, or performing a Text " +"Mode installation. See the <classname>Params</classname> help menu for " +"instructions on starting the installer in Text Mode." msgstr "" #. Tag: para -#: boot-installer.xml:1470 +#: boot-installer.xml:1506 #, no-c-format -msgid "If you select the wrong console type, you will be able to select the kernel and enter parameters but both the display and your input will go dead as soon as the kernel starts, requiring you to reboot before you can begin the installation." +msgid "" +"If you select the wrong console type, you will be able to select the kernel " +"and enter parameters but both the display and your input will go dead as " +"soon as the kernel starts, requiring you to reboot before you can begin the " +"installation." msgstr "" #. Tag: title -#: boot-installer.xml:1479 +#: boot-installer.xml:1515 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "" #. Tag: para -#: boot-installer.xml:1481 +#: boot-installer.xml:1517 #, no-c-format -msgid "The boot loader will display a form with a menu list and a text window with a <classname>Boot:</classname> prompt. The arrow keys select an item from the menu and any text typed at the keyboard will appear in the text window. There are also help screens which can be displayed by pressing the appropriate function key. The <classname>General</classname> help screen explains the menu choices and the <classname>Params</classname> screen explains the common command line options." +msgid "" +"The boot loader will display a form with a menu list and a text window with " +"a <classname>Boot:</classname> prompt. The arrow keys select an item from " +"the menu and any text typed at the keyboard will appear in the text window. " +"There are also help screens which can be displayed by pressing the " +"appropriate function key. The <classname>General</classname> help screen " +"explains the menu choices and the <classname>Params</classname> screen " +"explains the common command line options." msgstr "" #. Tag: para -#: boot-installer.xml:1493 +#: boot-installer.xml:1529 #, no-c-format -msgid "Consult the <classname>General</classname> help screen for the description of the kernels and install modes most appropriate for your installation. You should also consult <xref linkend=\"boot-parms\"/> below for any additional parameters that you may want to set in the <classname>Boot:</classname> text window. The kernel version you choose selects the kernel version that will be used for both the installation process and the installed system. If you encounter kernel problems with the installation, you may also have those same problems with the system you install. The following two steps will select and start the install:" +msgid "" +"Consult the <classname>General</classname> help screen for the description " +"of the kernels and install modes most appropriate for your installation. You " +"should also consult <xref linkend=\"boot-parms\"/> below for any additional " +"parameters that you may want to set in the <classname>Boot:</classname> text " +"window. The kernel version you choose selects the kernel version that will " +"be used for both the installation process and the installed system. If you " +"encounter kernel problems with the installation, you may also have those " +"same problems with the system you install. The following two steps will " +"select and start the install:" msgstr "" #. Tag: para -#: boot-installer.xml:1511 +#: boot-installer.xml:1547 #, no-c-format -msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys." +msgid "" +"Select the kernel version and installation mode most appropriate to your " +"needs with the arrow keys." msgstr "" #. Tag: para -#: boot-installer.xml:1516 +#: boot-installer.xml:1552 #, no-c-format -msgid "Enter any boot parameters by typing at the keyboard. The text will be displayed directly in the text window. This is where kernel parameters (such as serial console settings) are specified." +msgid "" +"Enter any boot parameters by typing at the keyboard. The text will be " +"displayed directly in the text window. This is where kernel parameters (such " +"as serial console settings) are specified." msgstr "" #. Tag: para -#: boot-installer.xml:1523 +#: boot-installer.xml:1559 #, no-c-format -msgid "Press <command>ENTER</command>. This will load and start the kernel. The kernel will display its usual initialization messages followed by the first screen of the Debian Installer." +msgid "" +"Press <command>ENTER</command>. This will load and start the kernel. The " +"kernel will display its usual initialization messages followed by the first " +"screen of the Debian Installer." msgstr "" #. Tag: para -#: boot-installer.xml:1532 boot-installer.xml:1668 +#: boot-installer.xml:1568 boot-installer.xml:1704 #, no-c-format -msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions." +msgid "" +"Proceed to the next chapter to continue the installation where you will set " +"up the language locale, network, and disk partitions." msgstr "" #. Tag: para -#: boot-installer.xml:1543 +#: boot-installer.xml:1579 #, no-c-format -msgid "Booting an IA-64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed through the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive." +msgid "" +"Booting an IA-64 system from the network is similar to a CD boot. The only " +"difference is how the installation kernel is loaded. The EFI Boot Manager " +"can load and start programs from a server on the network. Once the " +"installation kernel is loaded and starts, the system install will proceed " +"through the same steps as the CD install with the exception that the " +"packages of the base install will be loaded from the network rather than the " +"CD drive." msgstr "" #. Tag: para -#: boot-installer.xml:1577 +#: boot-installer.xml:1613 #, no-c-format -msgid "Network booting an IA-64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver <command>elilo</command>. On the client a new boot option must be defined in the EFI boot manager to enable loading over a network." +msgid "" +"Network booting an IA-64 system requires two architecture-specific actions. " +"On the boot server, DHCP and TFTP must be configured to deliver " +"<command>elilo</command>. On the client a new boot option must be defined in " +"the EFI boot manager to enable loading over a network." msgstr "" #. Tag: title -#: boot-installer.xml:1588 +#: boot-installer.xml:1624 #, no-c-format msgid "Configuring the Server" msgstr "" #. Tag: para -#: boot-installer.xml:1589 +#: boot-installer.xml:1625 #, no-c-format msgid "" - "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n" - "host mcmuffin {\n" - " hardware ethernet 00:30:6e:1e:0e:83;\n" - " fixed-address 10.0.0.21;\n" - " filename \"debian-installer/ia64/elilo.efi\";\n" - "}\n" - "</screen></informalexample> Note that the goal is to get <command>elilo.efi</command> running on the client." +"A suitable TFTP entry for network booting an IA-64 system looks something " +"like this: <informalexample><screen>\n" +"host mcmuffin {\n" +" hardware ethernet 00:30:6e:1e:0e:83;\n" +" fixed-address 10.0.0.21;\n" +" filename \"debian-installer/ia64/elilo.efi\";\n" +"}\n" +"</screen></informalexample> Note that the goal is to get <command>elilo.efi</" +"command> running on the client." msgstr "" #. Tag: para -#: boot-installer.xml:1599 +#: boot-installer.xml:1635 #, no-c-format -msgid "Extract the <filename>netboot.tar.gz</filename> file into the directory used as the root for your tftp server. Typical tftp root directories include <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This will create a <filename>debian-installer</filename> directory tree containing the boot files for an IA-64 system." +msgid "" +"Extract the <filename>netboot.tar.gz</filename> file into the directory used " +"as the root for your tftp server. Typical tftp root directories include " +"<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This " +"will create a <filename>debian-installer</filename> directory tree " +"containing the boot files for an IA-64 system." msgstr "" #. Tag: screen -#: boot-installer.xml:1609 +#: boot-installer.xml:1645 #, no-c-format msgid "" - "# cd /var/lib/tftp\n" - "# tar xvfz /home/user/netboot.tar.gz\n" - "./\n" - "./debian-installer/\n" - "./debian-installer/ia64/\n" - "[...]" +"# cd /var/lib/tftp\n" +"# tar xvfz /home/user/netboot.tar.gz\n" +"./\n" +"./debian-installer/\n" +"./debian-installer/ia64/\n" +"[...]" msgstr "" #. Tag: para -#: boot-installer.xml:1609 +#: boot-installer.xml:1645 #, no-c-format -msgid "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</filename> file that should work for most configurations. However, should you need to make changes to this file, you can find it in the <filename>debian-installer/ia64/</filename> directory. It is possible to have different config files for different clients by naming them using the client's IP address in hex with the suffix <filename>.conf</filename> instead of <filename>elilo.conf</filename>. See documentation provided in the <classname>elilo</classname> package for details." +msgid "" +"The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</" +"filename> file that should work for most configurations. However, should you " +"need to make changes to this file, you can find it in the <filename>debian-" +"installer/ia64/</filename> directory. It is possible to have different " +"config files for different clients by naming them using the client's IP " +"address in hex with the suffix <filename>.conf</filename> instead of " +"<filename>elilo.conf</filename>. See documentation provided in the " +"<classname>elilo</classname> package for details." msgstr "" #. Tag: title -#: boot-installer.xml:1626 +#: boot-installer.xml:1662 #, no-c-format msgid "Configuring the Client" msgstr "" #. Tag: para -#: boot-installer.xml:1627 +#: boot-installer.xml:1663 #, no-c-format -msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> <listitem><para> Add a boot option. </para></listitem> <listitem><para> You should see one or more lines with the text <guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose the one containing the MAC address of the interface from which you'll be booting. Use the arrow keys to highlight your choice, then press enter. </para></listitem> <listitem><para> Name the entry <userinput>Netboot</userinput> or something similar, save, and exit back to the boot options menu. </para></listitem> </itemizedlist> You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of <filename>elilo.efi</filename> from the server." +msgid "" +"To configure the client to support TFTP booting, start by booting to EFI and " +"entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> " +"<listitem><para> Add a boot option. </para></listitem> <listitem><para> You " +"should see one or more lines with the text <guimenuitem>Load File [Acpi" +"()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose " +"the one containing the MAC address of the interface from which you'll be " +"booting. Use the arrow keys to highlight your choice, then press enter. </" +"para></listitem> <listitem><para> Name the entry <userinput>Netboot</" +"userinput> or something similar, save, and exit back to the boot options " +"menu. </para></listitem> </itemizedlist> You should see the new boot option " +"you just created, and selecting it should initiate a DHCP query, leading to " +"a TFTP load of <filename>elilo.efi</filename> from the server." msgstr "" #. Tag: para -#: boot-installer.xml:1659 +#: boot-installer.xml:1695 #, no-c-format -msgid "The boot loader will display its prompt after it has downloaded and processed its configuration file. At this point, the installation proceeds with the same steps as a CD install. Select a boot option as in above and when the kernel has completed installing itself from the network, it will start the Debian Installer." +msgid "" +"The boot loader will display its prompt after it has downloaded and " +"processed its configuration file. At this point, the installation proceeds " +"with the same steps as a CD install. Select a boot option as in above and " +"when the kernel has completed installing itself from the network, it will " +"start the Debian Installer." msgstr "" #. Tag: title -#: boot-installer.xml:1681 +#: boot-installer.xml:1717 #, no-c-format msgid "Choosing an Installation Method" msgstr "" #. Tag: para -#: boot-installer.xml:1683 +#: boot-installer.xml:1719 #, no-c-format -msgid "Some &arch-title; subarchs have the option of booting using either a 2.4.x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux kernel. The installer should also require less memory when using a 2.4.x linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses tmpfs." +msgid "" +"Some &arch-title; subarchs have the option of booting using either a 2.4.x " +"or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux " +"kernel. The installer should also require less memory when using a 2.4.x " +"linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses " +"tmpfs." msgstr "" #. Tag: para -#: boot-installer.xml:1691 +#: boot-installer.xml:1727 #, no-c-format -msgid "If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; kernel parameter." +msgid "" +"If you are using a 2.2.x linux kernel, then you need to use the " +"&ramdisksize; kernel parameter." msgstr "" #. Tag: para -#: boot-installer.xml:1696 +#: boot-installer.xml:1732 #, no-c-format -msgid "Make sure <userinput>root=/dev/ram</userinput> is one of your kernel parameters." +msgid "" +"Make sure <userinput>root=/dev/ram</userinput> is one of your kernel " +"parameters." msgstr "" #. Tag: para -#: boot-installer.xml:1701 +#: boot-installer.xml:1737 #, no-c-format -msgid "If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's &arch-title; debian-installer FAQ</ulink>." +msgid "" +"If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's " +"&arch-title; debian-installer FAQ</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:1718 +#: boot-installer.xml:1754 #, no-c-format msgid "Amiga" msgstr "" #. Tag: para -#: boot-installer.xml:1719 +#: boot-installer.xml:1755 #, no-c-format -msgid "The only method of installation available to amiga is the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" +msgid "" +"The only method of installation available to amiga is the hard drive (see " +"<xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not " +"bootable.</emphasis>" msgstr "" #. Tag: para -#: boot-installer.xml:1725 +#: boot-installer.xml:1761 #, no-c-format -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>." +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 "" #. Tag: title -#: boot-installer.xml:1734 +#: boot-installer.xml:1770 #, no-c-format msgid "Atari" msgstr "" #. Tag: para -#: boot-installer.xml:1735 +#: boot-installer.xml:1771 #, no-c-format -msgid "The installer for atari may be started from either the hard drive (see <xref linkend=\"m68k-boot-hd\"/>) or from floppies (see <xref linkend=\"boot-from-floppies\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" +msgid "" +"The installer for atari may be started from either the hard drive (see <xref " +"linkend=\"m68k-boot-hd\"/>) or from floppies (see <xref linkend=\"boot-from-" +"floppies\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" #. Tag: para -#: boot-installer.xml:1742 +#: boot-installer.xml:1778 #, no-c-format -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>." +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 "" #. Tag: title -#: boot-installer.xml:1751 +#: boot-installer.xml:1787 #, no-c-format msgid "BVME6000" msgstr "" #. Tag: para -#: boot-installer.xml:1752 +#: boot-installer.xml:1788 #, no-c-format -msgid "The installer for BVME6000 may be started from a cdrom (see <xref linkend=\"m68k-boot-cdrom\"/>), floppies (see <xref linkend=\"boot-from-floppies\"/>), or the net (see <xref linkend=\"boot-tftp\"/>)." +msgid "" +"The installer for BVME6000 may be started from a cdrom (see <xref linkend=" +"\"m68k-boot-cdrom\"/>), floppies (see <xref linkend=\"boot-from-floppies\"/" +">), or the net (see <xref linkend=\"boot-tftp\"/>)." msgstr "" #. Tag: title -#: boot-installer.xml:1762 +#: boot-installer.xml:1798 #, no-c-format msgid "Macintosh" msgstr "" #. Tag: para -#: boot-installer.xml:1763 +#: boot-installer.xml:1799 #, no-c-format -msgid "The only method of installation available to mac is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis> Macs do not have a working 2.4.x kernel." +msgid "" +"The only method of installation available to mac is from the hard drive (see " +"<xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not " +"bootable.</emphasis> Macs do not have a working 2.4.x kernel." msgstr "" #. Tag: para -#: boot-installer.xml:1770 +#: boot-installer.xml:1806 #, no-c-format -msgid "If your hardware uses a 53c9x-based scsi bus, then you may need to include the kernel parameter <userinput>mac53c9x=1,0</userinput>. Hardware with two such scsi buses, such as the Quadra 950, will need <userinput>mac53c9x=2,0</userinput> instead. Alternatively, the parameter can be specified as <userinput>mac53c9x=-1,0</userinput> which will leave autodetection on, but which will disable SCSI disconnects. Note that specifying this parameter is only necessary if you have more than one hard disk; otherwise, the system will run faster if you do not specify it." +msgid "" +"If your hardware uses a 53c9x-based scsi bus, then you may need to include " +"the kernel parameter <userinput>mac53c9x=1,0</userinput>. Hardware with two " +"such scsi buses, such as the Quadra 950, will need <userinput>mac53c9x=2,0</" +"userinput> instead. Alternatively, the parameter can be specified as " +"<userinput>mac53c9x=-1,0</userinput> which will leave autodetection on, but " +"which will disable SCSI disconnects. Note that specifying this parameter is " +"only necessary if you have more than one hard disk; otherwise, the system " +"will run faster if you do not specify it." msgstr "" #. Tag: title -#: boot-installer.xml:1785 +#: boot-installer.xml:1821 #, no-c-format msgid "MVME147 and MVME16x" msgstr "" #. Tag: para -#: boot-installer.xml:1786 +#: boot-installer.xml:1822 #, no-c-format -msgid "The installer for MVME147 and MVME16x may be started from either floppies (see <xref linkend=\"boot-from-floppies\"/>) or the net (see <xref linkend=\"boot-tftp\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" +msgid "" +"The installer for MVME147 and MVME16x may be started from either floppies " +"(see <xref linkend=\"boot-from-floppies\"/>) or the net (see <xref linkend=" +"\"boot-tftp\"/>). <emphasis>In other words the cdrom is not bootable.</" +"emphasis>" msgstr "" #. Tag: title -#: boot-installer.xml:1796 +#: boot-installer.xml:1832 #, no-c-format msgid "Q40/Q60" msgstr "" #. Tag: para -#: boot-installer.xml:1797 +#: boot-installer.xml:1833 #, no-c-format -msgid "The only method of installation available to Q40/Q60 is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" +msgid "" +"The only method of installation available to Q40/Q60 is from the hard drive " +"(see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom " +"is not bootable.</emphasis>" msgstr "" #. Tag: title -#: boot-installer.xml:1808 +#: boot-installer.xml:1844 #, no-c-format msgid "Booting from a Hard Disk" msgstr "" #. Tag: para -#: boot-installer.xml:1814 boot-installer.xml:2420 +#: boot-installer.xml:1850 boot-installer.xml:2456 #, no-c-format -msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation." +msgid "" +"Booting from an existing operating system is often a convenient option; for " +"some systems it is the only supported method of installation." msgstr "" #. Tag: para -#: boot-installer.xml:1820 boot-installer.xml:2426 +#: boot-installer.xml:1856 boot-installer.xml:2462 #, no-c-format -msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files in <xref linkend=\"boot-drive-files\"/>." +msgid "" +"To boot the installer from hard disk, you will have already completed " +"downloading and placing the needed files in <xref linkend=\"boot-drive-files" +"\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:1829 +#: boot-installer.xml:1865 #, no-c-format -msgid "At least six different ramdisks may be used to boot from the hard drive, three different types each with and without support for a 2.2.x linux kernel (see <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink> for details)." +msgid "" +"At least six different ramdisks may be used to boot from the hard drive, " +"three different types each with and without support for a 2.2.x linux kernel " +"(see <ulink url=\"&disturl;/main/installer-&architecture;/current/images/" +"MANIFEST\">MANIFEST</ulink> for details)." msgstr "" #. Tag: para -#: boot-installer.xml:1837 +#: boot-installer.xml:1873 #, no-c-format -msgid "The three different types of ramdisks are <filename>cdrom</filename>, <filename>hd-media</filename>, and <filename>nativehd</filename>. These ramdisks differ only in their source for installation packages. The <filename>cdrom</filename> ramdisk uses a cdrom to get debian-installer packages. The <filename>hd-media</filename> ramdisk uses an iso image file of a cdrom currently residing on a hard disk. Finally, the <filename>nativehd</filename> ramdisk uses the net to install packages." +msgid "" +"The three different types of ramdisks are <filename>cdrom</filename>, " +"<filename>hd-media</filename>, and <filename>nativehd</filename>. These " +"ramdisks differ only in their source for installation packages. The " +"<filename>cdrom</filename> ramdisk uses a cdrom to get debian-installer " +"packages. The <filename>hd-media</filename> ramdisk uses an iso image file " +"of a cdrom currently residing on a hard disk. Finally, the " +"<filename>nativehd</filename> ramdisk uses the net to install packages." msgstr "" #. Tag: title -#: boot-installer.xml:1858 +#: boot-installer.xml:1894 #, no-c-format msgid "Booting from AmigaOS" msgstr "" #. Tag: para -#: boot-installer.xml:1859 +#: boot-installer.xml:1895 #, no-c-format -msgid "In the <command>Workbench</command>, start the Linux installation process by double-clicking on the <guiicon>StartInstall</guiicon> icon in the <filename>debian</filename> directory." +msgid "" +"In the <command>Workbench</command>, start the Linux installation process by " +"double-clicking on the <guiicon>StartInstall</guiicon> icon in the " +"<filename>debian</filename> directory." msgstr "" #. Tag: para -#: boot-installer.xml:1865 +#: boot-installer.xml:1901 #, no-c-format -msgid "You may have to press the &enterkey; key twice after the Amiga installer program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue down at <xref linkend=\"d-i-intro\"/>." +msgid "" +"You may have to press the &enterkey; key twice after the Amiga installer " +"program has output some debugging information into a window. After this, the " +"screen will go grey, there will be a few seconds' delay. Next, a black " +"screen with white text should come up, displaying all kinds of kernel " +"debugging information. These messages may scroll by too fast for you to " +"read, but that's OK. After a couple of seconds, the installation program " +"should start automatically, so you can continue down at <xref linkend=\"d-i-" +"intro\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:1880 +#: boot-installer.xml:1916 #, no-c-format msgid "Booting from Atari TOS" msgstr "" #. Tag: para -#: boot-installer.xml:1881 +#: boot-installer.xml:1917 #, no-c-format -msgid "At the GEM desktop, start the Linux installation process by double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the <filename>debian</filename> directory and clicking <guibutton>Ok</guibutton> at the program options dialog box." +msgid "" +"At the GEM desktop, start the Linux installation process by double-clicking " +"on the <guiicon>bootstra.prg</guiicon> icon in the <filename>debian</" +"filename> directory and clicking <guibutton>Ok</guibutton> at the program " +"options dialog box." msgstr "" #. Tag: para -#: boot-installer.xml:1888 +#: boot-installer.xml:1924 #, no-c-format -msgid "You may have to press the &enterkey; key after the Atari bootstrap program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." +msgid "" +"You may have to press the &enterkey; key after the Atari bootstrap program " +"has output some debugging information into a window. After this, the screen " +"will go grey, there will be a few seconds' delay. Next, a black screen with " +"white text should come up, displaying all kinds of kernel debugging " +"information. These messages may scroll by too fast for you to read, but " +"that's OK. After a couple of seconds, the installation program should start " +"automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:1903 +#: boot-installer.xml:1939 #, no-c-format msgid "Booting from MacOS" msgstr "" #. Tag: para -#: boot-installer.xml:1904 +#: boot-installer.xml:1940 #, no-c-format -msgid "You must retain the original Mac system and boot from it. It is <emphasis>essential</emphasis> that, when booting MacOS in preparation for booting the Penguin linux loader, you hold the <keycap>shift</keycap> key down to prevent extensions from loading. If you don't use MacOS except for loading linux, you can accomplish the same thing by removing all extensions and control panels from the Mac's System Folder. Otherwise extensions may be left running and cause random problems with the running linux kernel." +msgid "" +"You must retain the original Mac system and boot from it. It is " +"<emphasis>essential</emphasis> that, when booting MacOS in preparation for " +"booting the Penguin linux loader, you hold the <keycap>shift</keycap> key " +"down to prevent extensions from loading. If you don't use MacOS except for " +"loading linux, you can accomplish the same thing by removing all extensions " +"and control panels from the Mac's System Folder. Otherwise extensions may be " +"left running and cause random problems with the running linux kernel." msgstr "" #. Tag: para -#: boot-installer.xml:1915 +#: boot-installer.xml:1951 #, no-c-format -msgid "Macs require the <command>Penguin</command> bootloader, which can be downloaded from <ulink url=\"&url-m68k-mac;\">the Linux/mac68k sourceforge.net project</ulink>. If you do not have the tools to handle a <command>Stuffit</command> archive, you can put it on a MacOS-formatted floppy using a second GNU/Linux machine of any architecture and the <command>hmount</command>, <command>hcopy</command>, and <command>humount</command> tools from the <classname>hfsutils</classname> suite." +msgid "" +"Macs require the <command>Penguin</command> bootloader, which can be " +"downloaded from <ulink url=\"&url-m68k-mac;\">the Linux/mac68k sourceforge." +"net project</ulink>. If you do not have the tools to handle a " +"<command>Stuffit</command> archive, you can put it on a MacOS-formatted " +"floppy using a second GNU/Linux machine of any architecture and the " +"<command>hmount</command>, <command>hcopy</command>, and <command>humount</" +"command> tools from the <classname>hfsutils</classname> suite." msgstr "" #. Tag: para -#: boot-installer.xml:1926 +#: boot-installer.xml:1962 #, no-c-format -msgid "At the MacOS desktop, start the Linux installation process by double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in the <filename>Penguin</filename> directory. The <command>Penguin</command> booter will start up. Go to the <guimenuitem>Settings</guimenuitem> item in the <guimenu>File</guimenu> menu, click the <guilabel>Kernel</guilabel> tab. Select the kernel (<filename>vmlinuz</filename>) and ramdisk (<filename>initrd.gz</filename>) images in the <filename>install</filename> directory by clicking on the corresponding buttons in the upper right corner, and navigating the file select dialogs to locate the files." +msgid "" +"At the MacOS desktop, start the Linux installation process by double-" +"clicking on the <guiicon>Penguin Prefs</guiicon> icon in the " +"<filename>Penguin</filename> directory. The <command>Penguin</command> " +"booter will start up. Go to the <guimenuitem>Settings</guimenuitem> item in " +"the <guimenu>File</guimenu> menu, click the <guilabel>Kernel</guilabel> tab. " +"Select the kernel (<filename>vmlinuz</filename>) and ramdisk " +"(<filename>initrd.gz</filename>) images in the <filename>install</filename> " +"directory by clicking on the corresponding buttons in the upper right " +"corner, and navigating the file select dialogs to locate the files." msgstr "" #. Tag: para -#: boot-installer.xml:1941 +#: boot-installer.xml:1977 #, no-c-format -msgid "To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -> <guimenuitem>Settings...</guimenuitem>, then switch to the <guilabel>Options</guilabel> tab. Boot parameters may be typed in to the text entry area. If you will always want to use these settings, select <guimenu>File</guimenu> -> <guimenuitem>Save Settings as Default</guimenuitem>." +msgid "" +"To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -> " +"<guimenuitem>Settings...</guimenuitem>, then switch to the " +"<guilabel>Options</guilabel> tab. Boot parameters may be typed in to the " +"text entry area. If you will always want to use these settings, select " +"<guimenu>File</guimenu> -> <guimenuitem>Save Settings as Default</" +"guimenuitem>." msgstr "" #. Tag: para -#: boot-installer.xml:1950 +#: boot-installer.xml:1986 #, no-c-format -msgid "Close the <guilabel>Settings</guilabel> dialog, save the settings and start the bootstrap using the <guimenuitem>Boot Now</guimenuitem> item in the <guimenu>File</guimenu> menu." +msgid "" +"Close the <guilabel>Settings</guilabel> dialog, save the settings and start " +"the bootstrap using the <guimenuitem>Boot Now</guimenuitem> item in the " +"<guimenu>File</guimenu> menu." msgstr "" #. Tag: para -#: boot-installer.xml:1957 +#: boot-installer.xml:1993 #, no-c-format -msgid "The <command>Penguin</command> booter will output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." +msgid "" +"The <command>Penguin</command> booter will output some debugging information " +"into a window. After this, the screen will go grey, there will be a few " +"seconds' delay. Next, a black screen with white text should come up, " +"displaying all kinds of kernel debugging information. These messages may " +"scroll by too fast for you to read, but that's OK. After a couple of " +"seconds, the installation program should start automatically, so you can " +"continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:1972 +#: boot-installer.xml:2008 #, no-c-format msgid "Booting from Q40/Q60" msgstr "" #. Tag: para -#: boot-installer.xml:1974 +#: boot-installer.xml:2010 #, no-c-format msgid "FIXME" msgstr "" #. Tag: para -#: boot-installer.xml:1978 +#: boot-installer.xml:2014 #, no-c-format -msgid "The installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." +msgid "" +"The installation program should start automatically, so you can continue " +"below at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:1990 +#: boot-installer.xml:2026 #, no-c-format -msgid "Currently, the only &arch-title; subarchitecture that supports CD-ROM booting is the BVME6000." +msgid "" +"Currently, the only &arch-title; subarchitecture that supports CD-ROM " +"booting is the BVME6000." msgstr "" #. Tag: para -#: boot-installer.xml:2062 +#: boot-installer.xml:2098 #, no-c-format -msgid "After booting the VMEbus systems you will be presented with the LILO <prompt>Boot:</prompt> prompt. At that prompt enter one of the following to boot Linux and begin installation proper of the Debian software using vt102 terminal emulation:" +msgid "" +"After booting the VMEbus systems you will be presented with the LILO " +"<prompt>Boot:</prompt> prompt. At that prompt enter one of the following to " +"boot Linux and begin installation proper of the Debian software using vt102 " +"terminal emulation:" msgstr "" #. Tag: para -#: boot-installer.xml:2073 +#: boot-installer.xml:2109 #, no-c-format msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000" msgstr "" #. Tag: para -#: boot-installer.xml:2078 +#: boot-installer.xml:2114 #, no-c-format msgid "type <screen>i162 &enterkey;</screen> to install an MVME162" msgstr "" #. Tag: para -#: boot-installer.xml:2083 +#: boot-installer.xml:2119 #, no-c-format msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167" msgstr "" #. Tag: para -#: boot-installer.xml:2090 +#: boot-installer.xml:2126 #, no-c-format -msgid "You may additionally append the string <screen>TERM=vt100</screen> to use vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>." +msgid "" +"You may additionally append the string <screen>TERM=vt100</screen> to use " +"vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>." msgstr "" #. Tag: para -#: boot-installer.xml:2102 +#: boot-installer.xml:2138 #, no-c-format -msgid "For most &arch-title; architectures, booting from a local filesystem is the recommended method." +msgid "" +"For most &arch-title; architectures, booting from a local filesystem is the " +"recommended method." msgstr "" #. Tag: para -#: boot-installer.xml:2107 +#: boot-installer.xml:2143 #, no-c-format -msgid "Booting from the boot floppy is supported only for Atari and VME (with a SCSI floppy drive on VME) at this time." +msgid "" +"Booting from the boot floppy is supported only for Atari and VME (with a " +"SCSI floppy drive on VME) at this time." msgstr "" #. Tag: title -#: boot-installer.xml:2123 boot-installer.xml:2170 +#: boot-installer.xml:2159 boot-installer.xml:2206 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:2124 +#: boot-installer.xml:2160 #, no-c-format msgid "" - "After entering the command monitor use <informalexample><screen>\n" - "bootp():\n" - "</screen></informalexample> on SGI machines to boot linux and to begin installation of the Debian Software. In order to make this work you may have to unset the <envar>netaddr</envar> environment variable. Type <informalexample><screen>\n" - "unsetenv netaddr\n" - "</screen></informalexample> in the command monitor to do this." +"After entering the command monitor use <informalexample><screen>\n" +"bootp():\n" +"</screen></informalexample> on SGI machines to boot linux and to begin " +"installation of the Debian Software. In order to make this work you may have " +"to unset the <envar>netaddr</envar> environment variable. Type " +"<informalexample><screen>\n" +"unsetenv netaddr\n" +"</screen></informalexample> in the command monitor to do this." msgstr "" #. Tag: title -#: boot-installer.xml:2143 boot-installer.xml:2192 boot-installer.xml:2247 boot-installer.xml:2286 +#: boot-installer.xml:2179 boot-installer.xml:2228 boot-installer.xml:2283 +#: boot-installer.xml:2322 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:2144 boot-installer.xml:2248 +#: boot-installer.xml:2180 boot-installer.xml:2284 #, no-c-format msgid "" - "On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load the SiByl boot loader via TFTP which will then load and start the Debian installer. In most cases, you will first obtain an IP address via DHCP but it is also possible to configure a static address. In order to use DHCP, you can enter the following command on the CFE prompt: <informalexample><screen>\n" - "ifconfig eth0 -auto\n" - "</screen></informalexample> Once you have obtained an IP address, you can load SiByl with the following command: <informalexample><screen>\n" - "boot 192.168.1.1:/boot/sibyl\n" - "</screen></informalexample> You need to substitute the IP address listed in this example with either the name or the IP address of your TFTP server. Once you issue this command, the installer will be loaded automatically." +"On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load " +"the SiByl boot loader via TFTP which will then load and start the Debian " +"installer. In most cases, you will first obtain an IP address via DHCP but " +"it is also possible to configure a static address. In order to use DHCP, you " +"can enter the following command on the CFE prompt: " +"<informalexample><screen>\n" +"ifconfig eth0 -auto\n" +"</screen></informalexample> Once you have obtained an IP address, you can " +"load SiByl with the following command: <informalexample><screen>\n" +"boot 192.168.1.1:/boot/sibyl\n" +"</screen></informalexample> You need to substitute the IP address listed in " +"this example with either the name or the IP address of your TFTP server. " +"Once you issue this command, the installer will be loaded automatically." msgstr "" #. Tag: title -#: boot-installer.xml:2167 boot-installer.xml:2271 boot-installer.xml:2764 +#: boot-installer.xml:2203 boot-installer.xml:2307 boot-installer.xml:2800 #, no-c-format msgid "Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2171 +#: boot-installer.xml:2207 #, no-c-format -msgid "On SGI machines you can append boot parameters to the <command>bootp():</command> command in the command monitor." +msgid "" +"On SGI machines you can append boot parameters to the <command>bootp():</" +"command> command in the command monitor." msgstr "" #. Tag: para -#: boot-installer.xml:2176 +#: boot-installer.xml:2212 #, no-c-format msgid "" - "Following the <command>bootp():</command> command you can give the path and name of the file to boot if you did not give an explicit name via your bootp/dhcp server. Example: <informalexample><screen>\n" - "bootp():/boot/tftpboot.img\n" - "</screen></informalexample> Further kernel parameters can be passed via <command>append</command>:" +"Following the <command>bootp():</command> command you can give the path and " +"name of the file to boot if you did not give an explicit name via your bootp/" +"dhcp server. Example: <informalexample><screen>\n" +"bootp():/boot/tftpboot.img\n" +"</screen></informalexample> Further kernel parameters can be passed via " +"<command>append</command>:" msgstr "" #. Tag: screen -#: boot-installer.xml:2186 +#: boot-installer.xml:2222 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: para -#: boot-installer.xml:2193 boot-installer.xml:2287 +#: boot-installer.xml:2229 boot-installer.xml:2323 #, no-c-format -msgid "You cannot pass any boot parameters directly from the CFE prompt. Instead, you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP server and add your parameters to the <replaceable>extra_args</replaceable> variable." +msgid "" +"You cannot pass any boot parameters directly from the CFE prompt. Instead, " +"you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP " +"server and add your parameters to the <replaceable>extra_args</replaceable> " +"variable." msgstr "" #. Tag: title -#: boot-installer.xml:2212 boot-installer.xml:2274 +#: boot-installer.xml:2248 boot-installer.xml:2310 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:2213 +#: boot-installer.xml:2249 #, no-c-format -msgid "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to install an NFS server and put the installer files in <filename>/nfsroot</filename>. When you boot your Cobalt, you have to press the left and the right cursor buttons at the same time and the machine will boot via the network from NFS. It will then display several options on the display. There are the following two installation methods:" +msgid "" +"Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to " +"install an NFS server and put the installer files in <filename>/nfsroot</" +"filename>. When you boot your Cobalt, you have to press the left and the " +"right cursor buttons at the same time and the machine will boot via the " +"network from NFS. It will then display several options on the display. There " +"are the following two installation methods:" msgstr "" #. Tag: para -#: boot-installer.xml:2223 +#: boot-installer.xml:2259 #, no-c-format -msgid "Via SSH (default): In this case, the installer will configure the network via DHCP and start an SSH server. It will then display a random password and other login information (such as the IP address) on the Cobalt LCD. When you connect to the machine with an SSH client you can start with the installation." +msgid "" +"Via SSH (default): In this case, the installer will configure the network " +"via DHCP and start an SSH server. It will then display a random password and " +"other login information (such as the IP address) on the Cobalt LCD. When you " +"connect to the machine with an SSH client you can start with the " +"installation." msgstr "" #. Tag: para -#: boot-installer.xml:2232 +#: boot-installer.xml:2268 #, no-c-format -msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way. This option is not available on Qube 2700 (Qube1) machines since they have no serial port." +msgid "" +"Via serial console: Using a null modem cable, you can connect to the serial " +"port of your Cobalt machine (using 115200 bps) and perform the installation " +"this way. This option is not available on Qube 2700 (Qube1) machines since " +"they have no serial port." msgstr "" #. Tag: para -#: boot-installer.xml:2275 +#: boot-installer.xml:2311 #, no-c-format -msgid "You cannot pass any boot parameters directly. Instead, you have to edit the <filename>/nfsroot/default.colo</filename> file on the NFS server and add your parameters to the <replaceable>args</replaceable> variable." +msgid "" +"You cannot pass any boot parameters directly. Instead, you have to edit the " +"<filename>/nfsroot/default.colo</filename> file on the NFS server and add " +"your parameters to the <replaceable>args</replaceable> variable." msgstr "" #. Tag: title -#: boot-installer.xml:2303 +#: boot-installer.xml:2339 #, no-c-format msgid "s390 Limitations" msgstr "" #. Tag: para -#: boot-installer.xml:2304 +#: boot-installer.xml:2340 #, no-c-format -msgid "In order to run the installation system a working network setup and ssh session is needed on S/390." +msgid "" +"In order to run the installation system a working network setup and ssh " +"session is needed on S/390." msgstr "" #. Tag: para -#: boot-installer.xml:2309 +#: boot-installer.xml:2345 #, no-c-format -msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting an ssh session which will launch the standard installation system." +msgid "" +"The booting process starts with a network setup that prompts you for several " +"network parameters. If the setup is successful, you will login to the system " +"by starting an ssh session which will launch the standard installation " +"system." msgstr "" #. Tag: title -#: boot-installer.xml:2320 +#: boot-installer.xml:2356 #, no-c-format msgid "s390 Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2321 +#: boot-installer.xml:2357 #, no-c-format -msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images." +msgid "" +"On S/390 you can append boot parameters in the parm file. This file can " +"either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile." +"debian</filename> is provided with the installation images." msgstr "" #. Tag: para -#: boot-installer.xml:2381 +#: boot-installer.xml:2417 #, no-c-format -msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the CD-ROM." +msgid "" +"Currently, the only &arch-title; subarchitectures that support CD-ROM " +"booting are PReP (though not all systems) and New World PowerMacs. On " +"PowerMacs, hold the <keycap>c</keycap> key, or else the combination of " +"<keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, " +"and <keycap>Delete</keycap> keys together while booting to boot from the CD-" +"ROM." msgstr "" #. Tag: para -#: boot-installer.xml:2390 +#: boot-installer.xml:2426 #, no-c-format -msgid "OldWorld PowerMacs will not boot a Debian CD, because OldWorld computers relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-software version of this driver is not available. All OldWorld systems have floppy drives, so use the floppy drive to launch the installer, and then point the installer to the CD for the needed files." +msgid "" +"OldWorld PowerMacs will not boot a Debian CD, because OldWorld computers " +"relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-" +"software version of this driver is not available. All OldWorld systems have " +"floppy drives, so use the floppy drive to launch the installer, and then " +"point the installer to the CD for the needed files." msgstr "" #. Tag: para -#: boot-installer.xml:2399 +#: boot-installer.xml:2435 #, no-c-format -msgid "If your system doesn't boot directly from CD-ROM, you can still use the CD-ROM to install the system. On NewWorlds, you can also use an OpenFirmware command to boot from the CD-ROM manually. Follow the instructions in <xref linkend=\"boot-newworld\"/> for booting from the hard disk, except use the path to <command>yaboot</command> on the CD at the OF prompt, such as" +msgid "" +"If your system doesn't boot directly from CD-ROM, you can still use the CD-" +"ROM to install the system. On NewWorlds, you can also use an OpenFirmware " +"command to boot from the CD-ROM manually. Follow the instructions in <xref " +"linkend=\"boot-newworld\"/> for booting from the hard disk, except use the " +"path to <command>yaboot</command> on the CD at the OF prompt, such as" msgstr "" #. Tag: screen -#: boot-installer.xml:2408 +#: boot-installer.xml:2444 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "" #. Tag: title -#: boot-installer.xml:2414 +#: boot-installer.xml:2450 #, no-c-format msgid "Booting from Hard Disk" msgstr "" #. Tag: title -#: boot-installer.xml:2435 +#: boot-installer.xml:2471 #, no-c-format msgid "Booting CHRP from OpenFirmware" msgstr "" #. Tag: emphasis -#: boot-installer.xml:2439 +#: boot-installer.xml:2475 #, no-c-format msgid "Not yet written." msgstr "" #. Tag: title -#: boot-installer.xml:2444 +#: boot-installer.xml:2480 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" #. Tag: para -#: boot-installer.xml:2445 +#: boot-installer.xml:2481 #, no-c-format -msgid "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to boot into the installation system. Double click the <guiicon>BootX</guiicon> application icon. Click on the <guibutton>Options</guibutton> button and select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the chance to select the <filename>ramdisk.image.gz</filename> file. You may need to select the <guilabel>No Video Driver</guilabel> checkbox, depending on your hardware. Then click the <guibutton>Linux</guibutton> button to shut down MacOS and launch the installer." +msgid "" +"If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to " +"boot into the installation system. Double click the <guiicon>BootX</guiicon> " +"application icon. Click on the <guibutton>Options</guibutton> button and " +"select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the " +"chance to select the <filename>ramdisk.image.gz</filename> file. You may " +"need to select the <guilabel>No Video Driver</guilabel> checkbox, depending " +"on your hardware. Then click the <guibutton>Linux</guibutton> button to shut " +"down MacOS and launch the installer." msgstr "" #. Tag: title -#: boot-installer.xml:2463 +#: boot-installer.xml:2499 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" #. Tag: para -#: boot-installer.xml:2464 +#: boot-installer.xml:2500 #, no-c-format msgid "" - "You will have already placed the <filename>vmlinux</filename>, <filename>initrd.gz</filename>, <filename>yaboot</filename>, and <filename>yaboot.conf</filename> files at the root level of your HFS partition in <xref linkend=\"files-newworld\"/>. Restart the computer, and immediately (during the chime) hold down the <keycap>Option</keycap>, <keycap>Command (cloverleaf/Apple)</keycap>, <keycap>o</keycap>, and <keycap>f</keycap> keys all together. After a few seconds you will be presented with the Open Firmware prompt. At the prompt, type <informalexample><screen>\n" - "0 > boot hd:<replaceable>x</replaceable>,yaboot\n" - "</screen></informalexample> replacing <replaceable>x</replaceable> with the partition number of the HFS partition where the kernel and yaboot files were placed, followed by a &enterkey;. On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few more seconds you will see a yaboot prompt <informalexample><screen>\n" - "boot:\n" - "</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type either <userinput>install</userinput> or <userinput>install video=ofonly</userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> argument is for maximum compatibility; you can try it if <userinput>install</userinput> doesn't work. The Debian installation program should start." +"You will have already placed the <filename>vmlinux</filename>, " +"<filename>initrd.gz</filename>, <filename>yaboot</filename>, and " +"<filename>yaboot.conf</filename> files at the root level of your HFS " +"partition in <xref linkend=\"files-newworld\"/>. Restart the computer, and " +"immediately (during the chime) hold down the <keycap>Option</keycap>, " +"<keycap>Command (cloverleaf/Apple)</keycap>, <keycap>o</keycap>, and " +"<keycap>f</keycap> keys all together. After a few seconds you will be " +"presented with the Open Firmware prompt. At the prompt, type " +"<informalexample><screen>\n" +"0 > boot hd:<replaceable>x</replaceable>,yaboot\n" +"</screen></informalexample> replacing <replaceable>x</replaceable> with the " +"partition number of the HFS partition where the kernel and yaboot files were " +"placed, followed by a &enterkey;. On some machines, you may need to use " +"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few " +"more seconds you will see a yaboot prompt <informalexample><screen>\n" +"boot:\n" +"</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type " +"either <userinput>install</userinput> or <userinput>install video=ofonly</" +"userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> " +"argument is for maximum compatibility; you can try it if <userinput>install</" +"userinput> doesn't work. The Debian installation program should start." msgstr "" #. Tag: title -#: boot-installer.xml:2499 +#: boot-installer.xml:2535 #, no-c-format msgid "Booting from USB memory stick" msgstr "" #. Tag: para -#: boot-installer.xml:2500 +#: boot-installer.xml:2536 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" #. Tag: para -#: boot-installer.xml:2506 +#: boot-installer.xml:2542 #, no-c-format -msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. To get to the prompt, hold down <keycombo><keycap>Command</keycap> <keycap>Option</keycap> <keycap>o</keycap> <keycap>f</keycap></keycombo> all together while booting (see <xref linkend=\"invoking-openfirmware\"/>)." +msgid "" +"Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/" +">. To boot a Macintosh system from a USB stick, you will need to use the " +"Open Firmware prompt, since Open Firmware does not search USB storage " +"devices by default. To get to the prompt, hold down " +"<keycombo><keycap>Command</keycap> <keycap>Option</keycap> <keycap>o</" +"keycap> <keycap>f</keycap></keycombo> all together while booting (see <xref " +"linkend=\"invoking-openfirmware\"/>)." msgstr "" #. Tag: para -#: boot-installer.xml:2518 +#: boot-installer.xml:2554 #, no-c-format -msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment <command>ofpath</command> cannot work that out automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</userinput> at the Open Firmware prompt to get a list of all known devices and device aliases. On the author's system with various types of USB stick, paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work." +msgid "" +"You will need to work out where the USB storage device appears in the device " +"tree, since at the moment <command>ofpath</command> cannot work that out " +"automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</" +"userinput> at the Open Firmware prompt to get a list of all known devices " +"and device aliases. On the author's system with various types of USB stick, " +"paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</" +"filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and " +"<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work." msgstr "" #. Tag: para -#: boot-installer.xml:2530 +#: boot-installer.xml:2566 #, no-c-format msgid "" - "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n" - "boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:tbxi\n" - "</screen></informalexample> The <replaceable>2</replaceable> matches the Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. <command>yaboot</command>) in the directory previously blessed with <command>hattrib -b</command>." +"Having worked out the device path, use a command like this to boot the " +"installer: <informalexample><screen>\n" +"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:" +"tbxi\n" +"</screen></informalexample> The <replaceable>2</replaceable> matches the " +"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image " +"earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open " +"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. " +"<command>yaboot</command>) in the directory previously blessed with " +"<command>hattrib -b</command>." msgstr "" #. Tag: para -#: boot-installer.xml:2544 +#: boot-installer.xml:2580 #, no-c-format -msgid "The system should now boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;." +msgid "" +"The system should now boot up, and you should be presented with the " +"<prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, " +"or just hit &enterkey;." msgstr "" #. Tag: para -#: boot-installer.xml:2550 +#: boot-installer.xml:2586 #, no-c-format -msgid "This boot method is new, and may be difficult to get to work on some NewWorld systems. If you have problems, please file an installation report, as explained in <xref linkend=\"submit-bug\"/>." +msgid "" +"This boot method is new, and may be difficult to get to work on some " +"NewWorld systems. If you have problems, please file an installation report, " +"as explained in <xref linkend=\"submit-bug\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:2583 +#: boot-installer.xml:2619 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" #. Tag: para -#: boot-installer.xml:2587 +#: boot-installer.xml:2623 #, no-c-format -msgid "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <command>boot enet:0</command>. PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try <userinput>boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>. On some PReP systems (e.g. Motorola PowerStack machines) the command <userinput>help boot</userinput> may give a description of syntax and available options." +msgid "" +"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " +"monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command " +"<command>boot enet:0</command>. PReP and CHRP boxes may have different ways " +"of addressing the network. On a PReP machine, you should try <userinput>boot " +"net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>," +"<replaceable>client_ipaddr</replaceable></userinput>. On some PReP systems " +"(e.g. Motorola PowerStack machines) the command <userinput>help boot</" +"userinput> may give a description of syntax and available options." msgstr "" #. Tag: para -#: boot-installer.xml:2605 +#: boot-installer.xml:2641 #, no-c-format -msgid "Booting from floppies is supported for &arch-title;, although it is generally only applicable for OldWorld systems. NewWorld systems are not equipped with floppy drives, and attached USB floppy drives are not supported for booting." +msgid "" +"Booting from floppies is supported for &arch-title;, although it is " +"generally only applicable for OldWorld systems. NewWorld systems are not " +"equipped with floppy drives, and attached USB floppy drives are not " +"supported for booting." msgstr "" #. Tag: para -#: boot-installer.xml:2617 +#: boot-installer.xml:2653 #, no-c-format -msgid "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button." +msgid "" +"To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it " +"in floppy drive after shutting the system down, and before pressing the " +"power-on button." msgstr "" #. Tag: para -#: boot-installer.xml:2623 +#: boot-installer.xml:2659 #, no-c-format -msgid "For those not familiar with Macintosh floppy operations: a floppy placed in the machine prior to boot will be the first priority for the system to boot from. A floppy without a valid boot system will be ejected, and the machine will then check for bootable hard disk partitions." +msgid "" +"For those not familiar with Macintosh floppy operations: a floppy placed in " +"the machine prior to boot will be the first priority for the system to boot " +"from. A floppy without a valid boot system will be ejected, and the machine " +"will then check for bootable hard disk partitions." msgstr "" #. Tag: para -#: boot-installer.xml:2630 +#: boot-installer.xml:2666 #, no-c-format -msgid "After booting, the <filename>root.bin</filename> floppy is requested. Insert the root floppy and press &enterkey;. The installer program is automatically launched after the root system has been loaded into memory." +msgid "" +"After booting, the <filename>root.bin</filename> floppy is requested. Insert " +"the root floppy and press &enterkey;. The installer program is automatically " +"launched after the root system has been loaded into memory." msgstr "" #. Tag: title -#: boot-installer.xml:2641 +#: boot-installer.xml:2677 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2642 +#: boot-installer.xml:2678 #, no-c-format -msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ." +msgid "" +"Many older Apple monitors used a 640x480 67Hz mode. If your video appears " +"skewed on an older Apple monitor, try appending the boot argument " +"<userinput>video=atyfb:vmode:6</userinput> , which will select that mode for " +"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to " +"<userinput>video=aty128fb:vmode:6</userinput> ." msgstr "" #. Tag: para -#: boot-installer.xml:2682 +#: boot-installer.xml:2718 #, no-c-format -msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server." +msgid "" +"On machines with OpenBoot, simply enter the boot monitor on the machine " +"which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use " +"the command <userinput>boot net</userinput> to boot from a TFTP and RARP " +"server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:" +"dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server." msgstr "" #. Tag: para -#: boot-installer.xml:2736 +#: boot-installer.xml:2772 #, no-c-format -msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems)." +msgid "" +"Most OpenBoot versions support the <userinput>boot cdrom</userinput> command " +"which is simply an alias to boot from the SCSI device on ID 6 (or the " +"secondary master for IDE based systems)." msgstr "" #. Tag: title -#: boot-installer.xml:2745 +#: boot-installer.xml:2781 #, no-c-format msgid "IDPROM Messages" msgstr "" #. Tag: para -#: boot-installer.xml:2746 +#: boot-installer.xml:2782 #, no-c-format -msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information." +msgid "" +"If you cannot boot because you get messages about a problem with " +"<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which " +"holds configuration information for you firmware, has run out. See the " +"<ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more " +"information." msgstr "" #. Tag: para -#: boot-installer.xml:2765 +#: boot-installer.xml:2801 #, no-c-format -msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit." +msgid "" +"Boot parameters are Linux kernel parameters which are generally used to make " +"sure that peripherals are dealt with properly. For the most part, the kernel " +"can auto-detect information about your peripherals. However, in some cases " +"you'll have to help the kernel a bit." msgstr "" #. Tag: para -#: boot-installer.xml:2772 +#: boot-installer.xml:2808 #, no-c-format -msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware." +msgid "" +"If this is the first time you're booting the system, try the default boot " +"parameters (i.e., don't try setting parameters) and see if it works " +"correctly. It probably will. If not, you can reboot later and look for any " +"special parameters that inform the system about your hardware." msgstr "" #. Tag: para -#: boot-installer.xml:2779 +#: boot-installer.xml:2815 #, no-c-format -msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>." +msgid "" +"Information on many boot parameters can be found in the <ulink url=\"http://" +"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, " +"including tips for obscure hardware. This section contains only a sketch of " +"the most salient parameters. Some common gotchas are included below in <xref " +"linkend=\"boot-troubleshooting\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:2788 +#: boot-installer.xml:2824 #, no-c-format msgid "" - "When the kernel boots, a message <informalexample><screen>\n" - "Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k available\n" - "</screen></informalexample> should be emitted early in the process. <replaceable>total</replaceable> should match the total amount of RAM, in kilobytes. If this doesn't match the actual amount of RAM you have installed, you need to use the <userinput>mem=<replaceable>ram</replaceable></userinput> parameter, where <replaceable>ram</replaceable> is set to the amount of memory, suffixed with <quote>k</quote> for kilobytes, or <quote>m</quote> for megabytes. For example, both <userinput>mem=65536k</userinput> and <userinput>mem=64m</userinput> mean 64MB of RAM." +"When the kernel boots, a message <informalexample><screen>\n" +"Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k " +"available\n" +"</screen></informalexample> should be emitted early in the process. " +"<replaceable>total</replaceable> should match the total amount of RAM, in " +"kilobytes. If this doesn't match the actual amount of RAM you have " +"installed, you need to use the <userinput>mem=<replaceable>ram</" +"replaceable></userinput> parameter, where <replaceable>ram</replaceable> is " +"set to the amount of memory, suffixed with <quote>k</quote> for kilobytes, " +"or <quote>m</quote> for megabytes. For example, both <userinput>mem=65536k</" +"userinput> and <userinput>mem=64m</userinput> mean 64MB of RAM." msgstr "" #. Tag: para -#: boot-installer.xml:2804 +#: boot-installer.xml:2840 #, no-c-format -msgid "If you are booting with a serial console, generally the kernel will autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</phrase>. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>." +msgid "" +"If you are booting with a serial console, generally the kernel will " +"autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</" +"phrase>. If you have a videocard (framebuffer) and a keyboard also attached " +"to the computer which you wish to boot via serial console, you may have to " +"pass the <userinput>console=<replaceable>device</replaceable></userinput> " +"argument to the kernel, where <replaceable>device</replaceable> is your " +"serial device, which is usually something like <filename>ttyS0</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:2817 +#: boot-installer.xml:2853 #, no-c-format -msgid "For &arch-title; the serial devices are <filename>ttya</filename> or <filename>ttyb</filename>. Alternatively, set the <envar>input-device</envar> and <envar>output-device</envar> OpenPROM variables to <filename>ttya</filename>." +msgid "" +"For &arch-title; the serial devices are <filename>ttya</filename> or " +"<filename>ttyb</filename>. Alternatively, set the <envar>input-device</" +"envar> and <envar>output-device</envar> OpenPROM variables to " +"<filename>ttya</filename>." msgstr "" #. Tag: title -#: boot-installer.xml:2828 +#: boot-installer.xml:2864 #, no-c-format msgid "Debian Installer Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2829 +#: boot-installer.xml:2865 #, no-c-format -msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful." +msgid "" +"The installation system recognizes a few additional boot " +"parameters<footnote> <para> With current kernels (2.6.9 or newer) you can " +"use 32 command line options and 32 environment options. If these numbers are " +"exceeded, the kernel will panic. </para> </footnote> which may be useful." msgstr "" #. Tag: para -#: boot-installer.xml:2842 +#: boot-installer.xml:2878 #, no-c-format -msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too." +msgid "" +"A number of parameters have a <quote>short form</quote> that helps avoid the " +"limitations of the kernel command line options and makes entering the " +"parameters easier. If a parameter has a short form, it will be listed in " +"brackets behind the (normal) long form. Examples in this manual will " +"normally use the short form too." msgstr "" #. Tag: term -#: boot-installer.xml:2854 +#: boot-installer.xml:2890 #, no-c-format msgid "debconf/priority (priority)" msgstr "" #. Tag: para -#: boot-installer.xml:2855 +#: boot-installer.xml:2891 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" #. Tag: para -#: boot-installer.xml:2859 +#: boot-installer.xml:2895 #, no-c-format -msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed." +msgid "" +"The default installation uses <userinput>priority=high</userinput>. This " +"means that both high and critical priority messages are shown, but medium " +"and low priority messages are skipped. If problems are encountered, the " +"installer adjusts the priority as needed." msgstr "" #. Tag: para -#: boot-installer.xml:2866 +#: boot-installer.xml:2902 #, no-c-format -msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss." +msgid "" +"If you add <userinput>priority=medium</userinput> as boot parameter, you " +"will be shown the installation menu and gain more control over the " +"installation. When <userinput>priority=low</userinput> is used, all messages " +"are shown (this is equivalent to the <emphasis>expert</emphasis> boot " +"method). With <userinput>priority=critical</userinput>, the installation " +"system will display only critical messages and try to do the right thing " +"without fuss." msgstr "" #. Tag: term -#: boot-installer.xml:2880 +#: boot-installer.xml:2916 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para -#: boot-installer.xml:2881 +#: boot-installer.xml:2917 #, no-c-format -msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally, only the <userinput>newt</userinput> frontend is available on default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend." +msgid "" +"This boot parameter controls the type of user interface used for the " +"installer. The current possible parameter settings are: <itemizedlist> " +"<listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></" +"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</" +"userinput></para> </listitem><listitem> " +"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </" +"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> " +"</listitem> </itemizedlist> The default frontend is " +"<userinput>DEBIAN_FRONTEND=newt</userinput>. " +"<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial " +"console installs. Generally, only the <userinput>newt</userinput> frontend " +"is available on default install media. On architectures that support it, the " +"graphical installer uses the <userinput>gtk</userinput> frontend." msgstr "" #. Tag: term -#: boot-installer.xml:2910 +#: boot-installer.xml:2946 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:2911 +#: boot-installer.xml:2947 #, no-c-format -msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)" +msgid "" +"Setting this boot parameter to 2 will cause the installer's boot process to " +"be verbosely logged. Setting it to 3 makes debug shells available at " +"strategic points in the boot process. (Exit the shells to continue the boot " +"process.)" msgstr "" #. Tag: userinput -#: boot-installer.xml:2920 +#: boot-installer.xml:2956 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:2921 +#: boot-installer.xml:2957 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:2925 +#: boot-installer.xml:2961 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:2926 +#: boot-installer.xml:2962 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:2930 +#: boot-installer.xml:2966 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:2931 +#: boot-installer.xml:2967 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:2935 +#: boot-installer.xml:2971 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:2936 +#: boot-installer.xml:2972 #, no-c-format -msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot." +msgid "" +"Shells are run at various points in the boot process to allow detailed " +"debugging. Exit the shell to continue the boot." msgstr "" #. Tag: term -#: boot-installer.xml:2950 +#: boot-installer.xml:2986 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:2951 +#: boot-installer.xml:2987 #, no-c-format -msgid "The value of the parameter is the path to the device to load the Debian installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>" +msgid "" +"The value of the parameter is the path to the device to load the Debian " +"installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</" +"userinput>" msgstr "" #. Tag: para -#: boot-installer.xml:2957 +#: boot-installer.xml:2993 #, no-c-format -msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device." +msgid "" +"The boot floppy, which normally scans all floppies it can to find the root " +"floppy, can be overridden by this parameter to only look at the one device." msgstr "" #. Tag: term -#: boot-installer.xml:2967 +#: boot-installer.xml:3003 #, no-c-format msgid "lowmem" msgstr "" #. Tag: para -#: boot-installer.xml:2968 +#: boot-installer.xml:3004 #, no-c-format -msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>." +msgid "" +"Can be used to force the installer to a lowmem level higher than the one the " +"installer sets by default based on available memory. Possible values are 1 " +"and 2. See also <xref linkend=\"lowmem\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:2978 +#: boot-installer.xml:3014 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "" #. Tag: para -#: boot-installer.xml:2979 +#: boot-installer.xml:3015 #, no-c-format -msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature by the parameter <userinput>fb=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>fb=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." msgstr "" #. Tag: para -#: boot-installer.xml:2988 +#: boot-installer.xml:3024 #, no-c-format -msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card." +msgid "" +"The <userinput>video=vga16:off</userinput> argument may also be used to " +"disable the kernel's use of the framebuffer. Such problems have been " +"reported on a Dell Inspiron with Mobile Radeon card." msgstr "" #. Tag: para -#: boot-installer.xml:2994 +#: boot-installer.xml:3030 #, no-c-format msgid "Such problems have been reported on the Amiga 1200 and SE/30." msgstr "" #. Tag: para -#: boot-installer.xml:2998 +#: boot-installer.xml:3034 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:3002 +#: boot-installer.xml:3038 #, no-c-format -msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short." +msgid "" +"Because of display problems on some systems, framebuffer support is " +"<emphasis>disabled by default</emphasis> for &arch-title;. This can result " +"in ugly display on systems that do properly support the framebuffer, like " +"those with ATI graphical cards. If you see display problems in the " +"installer, you can try booting with parameter <userinput>debian-installer/" +"framebuffer=true</userinput> or <userinput>fb=true</userinput> for short." msgstr "" #. Tag: term -#: boot-installer.xml:3016 +#: boot-installer.xml:3052 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "" #. Tag: para -#: boot-installer.xml:3017 +#: boot-installer.xml:3053 #, no-c-format -msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with <userinput>theme=<replaceable>dark</replaceable></userinput>." +msgid "" +"A theme determines how the user interface of the installer looks (colors, " +"icons, etc.). What themes are available differs per frontend. Currently both " +"the newt and gtk frontends only have a <quote>dark</quote> theme that was " +"designed for visually impaired users. Set the theme by booting with " +"<userinput>theme=<replaceable>dark</replaceable></userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:3029 boot-installer.xml:3267 +#: boot-installer.xml:3065 boot-installer.xml:3315 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" #. Tag: para -#: boot-installer.xml:3030 +#: boot-installer.xml:3066 #, no-c-format -msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails." +msgid "" +"By default, the &d-i; automatically probes for network configuration via " +"DHCP. If the probe succeeds, you won't have a chance to review and change " +"the obtained settings. You can get to the manual network setup only in case " +"the DHCP probe fails." msgstr "" #. Tag: para -#: boot-installer.xml:3037 +#: boot-installer.xml:3073 #, no-c-format -msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually." +msgid "" +"If you have a DHCP server on your local network, but want to avoid it " +"because e.g. it gives wrong answers, you can use the parameter " +"<userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the " +"network with DHCP and to enter the information manually." msgstr "" #. Tag: term -#: boot-installer.xml:3048 +#: boot-installer.xml:3084 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:3049 +#: boot-installer.xml:3085 #, no-c-format -msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." +msgid "" +"Set to <userinput>false</userinput> to prevent starting PCMCIA services, if " +"that causes problems. Some laptops are well known for this misbehavior." msgstr "" #. Tag: term -#: boot-installer.xml:3059 +#: boot-installer.xml:3095 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "" #. Tag: para -#: boot-installer.xml:3060 +#: boot-installer.xml:3096 #, no-c-format -msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">Debian Installer Wiki</ulink>." +msgid "" +"Set to <userinput>true</userinput> to enable support for Serial ATA RAID " +"(also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note " +"that this support is currently experimental. Additional information can be " +"found on the <ulink url=\"&url-d-i-wiki;\">Debian Installer Wiki</ulink>." msgstr "" #. Tag: term -#: boot-installer.xml:3071 +#: boot-installer.xml:3107 #, no-c-format msgid "preseed/url (url)" msgstr "" #. Tag: para -#: boot-installer.xml:3072 +#: boot-installer.xml:3108 #, no-c-format -msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>." +msgid "" +"Specify the url to a preconfiguration file to download and use for " +"automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:3081 +#: boot-installer.xml:3117 #, no-c-format msgid "preseed/file (file)" msgstr "" #. Tag: para -#: boot-installer.xml:3082 +#: boot-installer.xml:3118 #, no-c-format -msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>." +msgid "" +"Specify the path to a preconfiguration file to load for automating the " +"install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term -#: boot-installer.xml:3091 +#: boot-installer.xml:3127 #, no-c-format msgid "preseed/interactive" msgstr "" #. Tag: para -#: boot-installer.xml:3092 +#: boot-installer.xml:3128 #, no-c-format -msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details." +msgid "" +"Set to <userinput>true</userinput> to display questions even if they have " +"been preseeded. Can be useful for testing or debugging a preconfiguration " +"file. Note that this will have no effect on parameters that are passed as " +"boot parameters, but for those a special syntax can be used. See <xref " +"linkend=\"preseed-seenflag\"/> for details." msgstr "" #. Tag: term -#: boot-installer.xml:3104 +#: boot-installer.xml:3140 #, no-c-format msgid "auto-install/enable (auto)" msgstr "" #. Tag: para -#: boot-installer.xml:3105 +#: boot-installer.xml:3141 #, no-c-format -msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs." +msgid "" +"Delay questions that are normally asked before preseeding is possible until " +"after the network is configured. See <xref linkend=\"preseed-auto\"/> for " +"details about using this to automate installs." msgstr "" #. Tag: term -#: boot-installer.xml:3116 +#: boot-installer.xml:3152 +#, no-c-format +msgid "finish-install/keep-consoles" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3153 +#, no-c-format +msgid "" +"During installations from serial or management console, the regular virtual " +"consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</" +"filename>. Set to <userinput>true</userinput> to prevent this." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3164 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:3117 +#: boot-installer.xml:3165 #, no-c-format -msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically." +msgid "" +"By default, before rebooting, &d-i; automatically ejects the optical media " +"used during the installation. This can be unnecessary if the system does not " +"automatically boot off the CD. In some cases it may even be undesirable, for " +"example if the optical drive cannot reinsert the media itself and the user " +"is not there to do it manually. Many slot loading, slim-line, and caddy " +"style drives cannot reload media automatically." msgstr "" #. Tag: para -#: boot-installer.xml:3126 +#: boot-installer.xml:3174 #, no-c-format -msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation." +msgid "" +"Set to <userinput>false</userinput> to disable automatic ejection, and be " +"aware that you may need to ensure that the system does not automatically " +"boot from the optical drive after the initial installation." msgstr "" #. Tag: term -#: boot-installer.xml:3137 +#: boot-installer.xml:3185 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "" #. Tag: para -#: boot-installer.xml:3138 +#: boot-installer.xml:3186 #, no-c-format -msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>" +msgid "" +"By default the installer requires that repositories be authenticated using a " +"known gpg key. Set to <userinput>true</userinput> to disable that " +"authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</" +"emphasis>" msgstr "" #. Tag: term -#: boot-installer.xml:3149 +#: boot-installer.xml:3197 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:3150 +#: boot-installer.xml:3198 #, no-c-format -msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB." +msgid "" +"This parameter should already be set to a correct value where needed; set it " +"only it you see errors during the boot that indicate the ramdisk could not " +"be loaded completely. The value is in kB." msgstr "" #. Tag: term -#: boot-installer.xml:3160 +#: boot-installer.xml:3208 #, no-c-format msgid "mouse/protocol" msgstr "" #. Tag: para -#: boot-installer.xml:3161 +#: boot-installer.xml:3209 #, no-c-format -msgid "For the gtk frontend (graphical installer), users can set the mouse protocol to be used by setting this parameter. Supported values are<footnote> <para> See the man page for <citerefentry><refentrytitle>directfbrc</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for additional information. </para> </footnote>: <userinput>PS/2</userinput>, <userinput>IMPS/2</userinput>, <userinput>MS</userinput>, <userinput>MS3</userinput>, <userinput>MouseMan</userinput> and <userinput>MouseSystems</userinput>. In most cases the default protocol should work correctly." +msgid "" +"For the gtk frontend (graphical installer), users can set the mouse protocol " +"to be used by setting this parameter. Supported values are<footnote> <para> " +"See the man page for <citerefentry><refentrytitle>directfbrc</refentrytitle> " +"<manvolnum>5</manvolnum></citerefentry> for additional information. </para> " +"</footnote>: <userinput>PS/2</userinput>, <userinput>IMPS/2</userinput>, " +"<userinput>MS</userinput>, <userinput>MS3</userinput>, <userinput>MouseMan</" +"userinput> and <userinput>MouseSystems</userinput>. In most cases the " +"default protocol should work correctly." msgstr "" #. Tag: term -#: boot-installer.xml:3183 +#: boot-installer.xml:3231 #, no-c-format msgid "mouse/device" msgstr "" #. Tag: para -#: boot-installer.xml:3184 +#: boot-installer.xml:3232 #, no-c-format -msgid "For the gtk frontend (graphical installer), users can specify the mouse device to be used by setting this parameter. This is mostly useful if the mouse is connected to a serial port (serial mouse). Example: <userinput>mouse/device=<replaceable>/dev/ttyS1</replaceable></userinput>." +msgid "" +"For the gtk frontend (graphical installer), users can specify the mouse " +"device to be used by setting this parameter. This is mostly useful if the " +"mouse is connected to a serial port (serial mouse). Example: " +"<userinput>mouse/device=<replaceable>/dev/ttyS1</replaceable></userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:3195 +#: boot-installer.xml:3243 #, no-c-format msgid "mouse/left" msgstr "" #. Tag: para -#: boot-installer.xml:3196 +#: boot-installer.xml:3244 #, no-c-format -msgid "For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to <userinput>true</userinput>." +msgid "" +"For the gtk frontend (graphical installer), users can switch the mouse to " +"left-handed operation by setting this parameter to <userinput>true</" +"userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:3205 +#: boot-installer.xml:3253 #, no-c-format msgid "directfb/hw-accel" msgstr "" #. Tag: para -#: boot-installer.xml:3206 +#: boot-installer.xml:3254 #, no-c-format -msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. Set this parameter to <userinput>true</userinput> to enable it." +msgid "" +"For the gtk frontend (graphical installer), hardware acceleration in " +"directfb is disabled by default. Set this parameter to <userinput>true</" +"userinput> to enable it." msgstr "" #. Tag: term -#: boot-installer.xml:3216 +#: boot-installer.xml:3264 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:3217 +#: boot-installer.xml:3265 #, no-c-format -msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." +msgid "" +"Set to <userinput>true</userinput> to enter rescue mode rather than " +"performing a normal installation. See <xref linkend=\"rescue\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:3228 +#: boot-installer.xml:3276 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para -#: boot-installer.xml:3229 +#: boot-installer.xml:3277 #, no-c-format -msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below." +msgid "" +"With some exceptions, a value can be set at the boot prompt for any question " +"asked during the installation, though this is only really useful in specific " +"cases. General instructions how to do this can be found in <xref linkend=" +"\"preseed-bootparms\"/>. Some specific examples are listed below." msgstr "" #. Tag: term -#: boot-installer.xml:3241 +#: boot-installer.xml:3289 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:3242 +#: boot-installer.xml:3290 #, no-c-format -msgid "Can be used to set both the language and country for the installation. This will only work if the locale is supported in Debian. For example, use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country." +msgid "" +"Can be used to set both the language and country for the installation. This " +"will only work if the locale is supported in Debian. For example, use " +"<userinput>locale=de_CH</userinput> to select German as language and " +"Switzerland as country." msgstr "" #. Tag: term -#: boot-installer.xml:3253 +#: boot-installer.xml:3301 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:3254 +#: boot-installer.xml:3302 #, no-c-format -msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>." +msgid "" +"Can be used to automatically load installer components that are not loaded " +"by default. Examples of optional components that may be useful are " +"<classname>openssh-client-udeb</classname> (so you can use <command>scp</" +"command> during the installation)<phrase arch=\"not-s390\"> and " +"<classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>." msgstr "" #. Tag: para -#: boot-installer.xml:3268 +#: boot-installer.xml:3316 #, no-c-format -msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration." +msgid "" +"Set to <userinput>true</userinput> if you want to disable DHCP and instead " +"force static network configuration." msgstr "" #. Tag: term -#: boot-installer.xml:3277 +#: boot-installer.xml:3325 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:3278 +#: boot-installer.xml:3326 #, no-c-format -msgid "By default the installer will use the http protocol to download files from Debian mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually." +msgid "" +"By default the installer will use the http protocol to download files from " +"Debian mirrors and changing that to ftp is not possible during installations " +"at normal priority. By setting this parameter to <userinput>ftp</userinput>, " +"you can force the installer to use that protocol instead. Note that you " +"cannot select an ftp mirror from a list, you have to enter the hostname " +"manually." msgstr "" #. Tag: term -#: boot-installer.xml:3291 +#: boot-installer.xml:3339 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para -#: boot-installer.xml:3292 +#: boot-installer.xml:3340 #, no-c-format -msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information." +msgid "" +"Can be used to select tasks that are not available from the interactive task " +"list, such as the <literal>kde-desktop</literal> task. See <xref linkend=" +"\"pkgsel\"/> for additional information." msgstr "" #. Tag: title -#: boot-installer.xml:3306 +#: boot-installer.xml:3354 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:3307 +#: boot-installer.xml:3355 #, no-c-format -msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system." +msgid "" +"If drivers are compiled into the kernel, you can pass parameters to them as " +"described in the kernel documentation. However, if drivers are compiled as " +"modules and because kernel modules are loaded a bit differently during an " +"installation than when booting an installed system, it is not possible to " +"pass parameters to modules as you would normally do. Instead, you need to " +"use a special syntax recognized by the installer which will then make sure " +"that the parameters are saved in the proper configuration files and will " +"thus be used when the modules are actually loaded. The parameters will also " +"be propagated automatically to the configuration for the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:3320 +#: boot-installer.xml:3368 #, no-c-format -msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually." +msgid "" +"Note that it is now quite rare that parameters need to be passed to modules. " +"In most cases the kernel will be able to probe the hardware present in a " +"system and set good defaults that way. However, in some situations it may " +"still be needed to set parameters manually." msgstr "" #. Tag: para -#: boot-installer.xml:3327 +#: boot-installer.xml:3375 #, no-c-format msgid "" - "The syntax to use to set parameters for modules is: <informalexample><screen>\n" - "<replaceable>module_name</replaceable>.<replaceable>parameter_name</replaceable>=<replaceable>value</replaceable>\n" - "</screen></informalexample> If you need to pass multiple parameters to the same or different modules, just repeat this. For example, to set an old 3Com network interface card to use the BNC (coax) connector and IRQ 10, you would pass:" +"The syntax to use to set parameters for modules is: " +"<informalexample><screen>\n" +"<replaceable>module_name</replaceable>.<replaceable>parameter_name</" +"replaceable>=<replaceable>value</replaceable>\n" +"</screen></informalexample> If you need to pass multiple parameters to the " +"same or different modules, just repeat this. For example, to set an old 3Com " +"network interface card to use the BNC (coax) connector and IRQ 10, you would " +"pass:" msgstr "" #. Tag: screen -#: boot-installer.xml:3337 +#: boot-installer.xml:3385 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:3343 +#: boot-installer.xml:3391 #, no-c-format msgid "Blacklisting kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:3344 +#: boot-installer.xml:3392 #, no-c-format -msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first." +msgid "" +"Sometimes it may be necessary to blacklist a module to prevent it from being " +"loaded automatically by the kernel and udev. One reason could be that a " +"particular module causes problems with your hardware. The kernel also " +"sometimes lists two different drivers for the same device. This can cause " +"the device to not work correctly if the drivers conflict or if the wrong " +"driver is loaded first." msgstr "" #. Tag: para -#: boot-installer.xml:3353 +#: boot-installer.xml:3401 #, no-c-format -msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system." +msgid "" +"You can blacklist a module using the following syntax: " +"<userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. " +"This will cause the module to be blacklisted in <filename>/etc/modprobe.d/" +"blacklist.local</filename> both during the installation and for the " +"installed system." msgstr "" #. Tag: para -#: boot-installer.xml:3361 +#: boot-installer.xml:3409 #, no-c-format -msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases." +msgid "" +"Note that a module may still be loaded by the installation system itself. " +"You can prevent that from happening by running the installation in expert " +"mode and unselecting the module from the list of modules displayed during " +"the hardware detection phases." msgstr "" #. Tag: title -#: boot-installer.xml:3378 +#: boot-installer.xml:3426 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:3383 +#: boot-installer.xml:3431 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3384 +#: boot-installer.xml:3432 #, no-c-format -msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also — even after booting successfully from CD-ROM — fail to recognize the CD-ROM or return errors while reading from it during the installation." +msgid "" +"Sometimes, especially with older CD-ROM drives, the installer may fail to " +"boot from a CD-ROM. The installer may also — even after booting " +"successfully from CD-ROM — fail to recognize the CD-ROM or return " +"errors while reading from it during the installation." msgstr "" #. Tag: para -#: boot-installer.xml:3391 +#: boot-installer.xml:3439 #, no-c-format -msgid "There are a many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you." +msgid "" +"There are a many different possible causes for these problems. We can only " +"list some common issues and provide general suggestions on how to deal with " +"them. The rest is up to you." msgstr "" #. Tag: para -#: boot-installer.xml:3397 +#: boot-installer.xml:3445 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:3402 +#: boot-installer.xml:3450 #, no-c-format -msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty." +msgid "" +"If the CD-ROM does not boot, check that it was inserted correctly and that " +"it is not dirty." msgstr "" #. Tag: para -#: boot-installer.xml:3408 +#: boot-installer.xml:3456 #, no-c-format -msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with older CD-ROM drives are known to be resolved in this way." +msgid "" +"If the installer fails to recognize a CD-ROM, try just running the option " +"<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </" +"menuchoice> a second time. Some DMA related issues with older CD-ROM drives " +"are known to be resolved in this way." msgstr "" #. Tag: para -#: boot-installer.xml:3418 +#: boot-installer.xml:3466 #, no-c-format -msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity." +msgid "" +"If this does not work, then try the suggestions in the subsections below. " +"Most, but not all, suggestions discussed there are valid for both CD-ROM and " +"DVD, but we'll use the term CD-ROM for simplicity." msgstr "" #. Tag: para -#: boot-installer.xml:3424 +#: boot-installer.xml:3472 #, no-c-format -msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available." +msgid "" +"If you cannot get the installation working from CD-ROM, try one of the other " +"installation methods that are available." msgstr "" #. Tag: title -#: boot-installer.xml:3432 +#: boot-installer.xml:3480 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:3435 +#: boot-installer.xml:3483 #, no-c-format -msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer." +msgid "" +"Some older CD-ROM drives do not support reading from discs that were burned " +"at high speeds using a modern CD writer." msgstr "" #. Tag: para -#: boot-installer.xml:3441 +#: boot-installer.xml:3489 #, no-c-format -msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)." +msgid "" +"If your system boots correctly from the CD-ROM, it does not necessarily mean " +"that Linux also supports the CD-ROM (or, more correctly, the controller that " +"your CD-ROM drive is connected to)." msgstr "" #. Tag: para -#: boot-installer.xml:3448 +#: boot-installer.xml:3496 #, no-c-format -msgid "Some older CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled." +msgid "" +"Some older CD-ROM drives do not work correctly if <quote>direct memory " +"access</quote> (DMA) is enabled." msgstr "" #. Tag: title -#: boot-installer.xml:3459 +#: boot-installer.xml:3507 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:3460 +#: boot-installer.xml:3508 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:3465 +#: boot-installer.xml:3513 #, no-c-format -msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using." +msgid "" +"Check that your BIOS actually supports booting from CD-ROM (older systems " +"possibly don't) and that your CD-ROM drive supports the media you are using." msgstr "" #. Tag: para -#: boot-installer.xml:3471 +#: boot-installer.xml:3519 #, no-c-format msgid "" - "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n" - "$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n" - "a20391b12f7ff22ef705cee4059c6b92 <replaceable>debian-testing-i386-netinst.iso</replaceable>\n" - "</screen></informalexample> Next, check that the md5sum of the burned CD-ROM matches as well. The following command should work. It uses the size of the image to read the correct number of bytes from the CD-ROM." +"If you downloaded an iso image, check that the md5sum of that image matches " +"the one listed for the image in the <filename>MD5SUMS</filename> file that " +"should be present in the same location as where you downloaded the image " +"from. <informalexample><screen>\n" +"$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n" +"a20391b12f7ff22ef705cee4059c6b92 <replaceable>debian-testing-i386-netinst." +"iso</replaceable>\n" +"</screen></informalexample> Next, check that the md5sum of the burned CD-ROM " +"matches as well. The following command should work. It uses the size of the " +"image to read the correct number of bytes from the CD-ROM." msgstr "" #. Tag: screen -#: boot-installer.xml:3484 +#: boot-installer.xml:3532 #, no-c-format msgid "" - "$ dd if=/dev/cdrom | \\\n" - "> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</replaceable>` | \\\n" - "> md5sum\n" - "a20391b12f7ff22ef705cee4059c6b92 -\n" - "262668+0 records in\n" - "262668+0 records out\n" - "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" +"$ dd if=/dev/cdrom | \\\n" +"> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</" +"replaceable>` | \\\n" +"> md5sum\n" +"a20391b12f7ff22ef705cee4059c6b92 -\n" +"262668+0 records in\n" +"262668+0 records out\n" +"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" msgstr "" #. Tag: para -#: boot-installer.xml:3489 +#: boot-installer.xml:3537 #, no-c-format -msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there." +msgid "" +"If, after the installer has been booted successfully, the CD-ROM is not " +"detected, sometimes simply trying again may solve the problem. If you have " +"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If " +"that does not work or if the CD-ROM is recognized but there are errors when " +"reading from it, try the suggestions listed below. Some basic knowledge of " +"Linux is required for this. To execute any of the commands, you should first " +"switch to the second virtual console (VT2) and activate the shell there." msgstr "" #. Tag: para -#: boot-installer.xml:3501 +#: boot-installer.xml:3549 #, no-c-format -msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>." +msgid "" +"Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> " +"(use <command>nano</command> as editor) to check for any specific error " +"messages. After that, also check the output of <command>dmesg</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3508 +#: boot-installer.xml:3556 #, no-c-format msgid "" - "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n" - "Probing IDE interface ide1...\n" - "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" - "ide1 at 0x170-0x177,0x376 on irq 15\n" - "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" - "Uniform CD-ROM driver Revision: 3.20\n" - "</screen></informalexample> If you don't see something like that, chances are the controller your CD-ROM is connected to was not recognized or may be not supported at all. If you know what driver is needed for the controller, you can try loading it manually using <command>modprobe</command>." +"Check in the output of <command>dmesg</command> if your CD-ROM drive was " +"recognized. You should see something like (the lines do not necessarily have " +"to be consecutive): <informalexample><screen>\n" +"Probing IDE interface ide1...\n" +"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" +"ide1 at 0x170-0x177,0x376 on irq 15\n" +"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" +"Uniform CD-ROM driver Revision: 3.20\n" +"</screen></informalexample> If you don't see something like that, chances " +"are the controller your CD-ROM is connected to was not recognized or may be " +"not supported at all. If you know what driver is needed for the controller, " +"you can try loading it manually using <command>modprobe</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3522 +#: boot-installer.xml:3570 #, no-c-format -msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdroms/cdrom0</filename>." +msgid "" +"Check that there is a device node for your CD-ROM drive under <filename>/dev/" +"</filename>. In the example above, this would be <filename>/dev/hdc</" +"filename>. There should also be a <filename>/dev/cdroms/cdrom0</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:3530 +#: boot-installer.xml:3578 #, no-c-format msgid "" - "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n" - "$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n" - "</screen></informalexample> Check if there are any error messages after that command." +"Use the <command>mount</command> command to check if the CD-ROM is already " +"mounted; if not, try mounting it manually: <informalexample><screen>\n" +"$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n" +"</screen></informalexample> Check if there are any error messages after that " +"command." msgstr "" #. Tag: para -#: boot-installer.xml:3540 +#: boot-installer.xml:3588 #, no-c-format msgid "" - "Check if DMA is currently enabled: <informalexample><screen>\n" - "$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n" - "$ grep using_dma settings\n" - "using_dma 1 0 1 rw\n" - "</screen></informalexample> A <quote>1</quote> in the first column after <literal>using_dma</literal> means it is enabled. If it is, try disabling it: <informalexample><screen>\n" - "$ echo -n \"using_dma:0\" >settings\n" - "</screen></informalexample> Make sure that you are in the directory for the device that corresponds to your CD-ROM drive." +"Check if DMA is currently enabled: <informalexample><screen>\n" +"$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n" +"$ grep using_dma settings\n" +"using_dma 1 0 1 rw\n" +"</screen></informalexample> A <quote>1</quote> in the first column after " +"<literal>using_dma</literal> means it is enabled. If it is, try disabling " +"it: <informalexample><screen>\n" +"$ echo -n \"using_dma:0\" >settings\n" +"</screen></informalexample> Make sure that you are in the directory for the " +"device that corresponds to your CD-ROM drive." msgstr "" #. Tag: para -#: boot-installer.xml:3555 +#: boot-installer.xml:3603 #, no-c-format -msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably." +msgid "" +"If there are any problems during the installation, try checking the " +"integrity of the CD-ROM using the option near the bottom of the installer's " +"main menu. This option can also be used as a general test if the CD-ROM can " +"be read reliably." msgstr "" #. Tag: title -#: boot-installer.xml:3570 +#: boot-installer.xml:3618 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3572 +#: boot-installer.xml:3620 #, no-c-format -msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." +msgid "" +"The biggest problem for people using floppy disks to install Debian seems to " +"be floppy disk reliability." msgstr "" #. Tag: para -#: boot-installer.xml:3577 +#: boot-installer.xml:3625 #, no-c-format -msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors." +msgid "" +"The boot floppy is the floppy with the worst problems, because it is read by " +"the hardware directly, before Linux boots. Often, the hardware doesn't read " +"as reliably as the Linux floppy disk driver, and may just stop without " +"printing an error message if it reads incorrect data. There can also be " +"failures in the driver floppies, most of which indicate themselves with a " +"flood of messages about disk I/O errors." msgstr "" #. Tag: para -#: boot-installer.xml:3586 +#: boot-installer.xml:3634 #, no-c-format -msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system." +msgid "" +"If you are having the installation stall at a particular floppy, the first " +"thing you should do is write the image to a <emphasis>different</emphasis> " +"floppy and see if that solves the problem. Simply reformatting the old " +"floppy may not be sufficient, even if it appears that the floppy was " +"reformatted and written with no errors. It is sometimes useful to try " +"writing the floppy on a different system." msgstr "" #. Tag: para -#: boot-installer.xml:3595 +#: boot-installer.xml:3643 #, no-c-format -msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy." +msgid "" +"One user reports he had to write the images to floppy <emphasis>three</" +"emphasis> times before one worked, and then everything was fine with the " +"third floppy." msgstr "" #. Tag: para -#: boot-installer.xml:3601 +#: boot-installer.xml:3649 #, no-c-format -msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums." +msgid "" +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." msgstr "" #. Tag: para -#: boot-installer.xml:3607 +#: boot-installer.xml:3655 #, no-c-format -msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers." +msgid "" +"Other users have reported that simply rebooting a few times with the same " +"floppy in the floppy drive can lead to a successful boot. This is all due to " +"buggy hardware or firmware floppy drivers." msgstr "" #. Tag: title -#: boot-installer.xml:3616 +#: boot-installer.xml:3664 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:3618 +#: boot-installer.xml:3666 #, no-c-format -msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>." +msgid "" +"If you have problems and the kernel hangs during the boot process, doesn't " +"recognize peripherals you actually have, or drives are not recognized " +"properly, the first thing to check is the boot parameters, as discussed in " +"<xref linkend=\"boot-parms\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:3625 +#: boot-installer.xml:3673 #, no-c-format -msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" +msgid "" +"Often, problems can be solved by removing add-ons and peripherals, and then " +"trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and " +"Plug-n-Play devices can be especially problematic.</phrase>" msgstr "" #. Tag: para -#: boot-installer.xml:3631 +#: boot-installer.xml:3679 #, no-c-format -msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>." +msgid "" +"If you have a large amount of memory installed in your machine, more than " +"512M, and the installer hangs when booting the kernel, you may need to " +"include a boot argument to limit the amount of memory the kernel sees, such " +"as <userinput>mem=512m</userinput>." msgstr "" #. Tag: title -#: boot-installer.xml:3642 boot-installer.xml:3726 +#: boot-installer.xml:3690 boot-installer.xml:3774 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3643 +#: boot-installer.xml:3691 #, no-c-format -msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." +msgid "" +"There are some common installation problems that can be solved or avoided by " +"passing certain boot parameters to the installer." msgstr "" #. Tag: para -#: boot-installer.xml:3648 +#: boot-installer.xml:3696 #, no-c-format -msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>." +msgid "" +"Some systems have floppies with <quote>inverted DCLs</quote>. If you receive " +"errors reading from the floppy, even when you know the floppy is good, try " +"the parameter <userinput>floppy=thinkpad</userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3654 +#: boot-installer.xml:3702 #, no-c-format -msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>." +msgid "" +"On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk " +"drivers), the IDE drive may not be properly recognized. Again, try it first " +"without the parameters and see if the IDE drive is recognized properly. If " +"not, determine your drive geometry (cylinders, heads, and sectors), and use " +"the parameter <userinput>hd=<replaceable>cylinders</replaceable>," +"<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></" +"userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3663 +#: boot-installer.xml:3711 #, no-c-format -msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test." +msgid "" +"If you have a very old machine, and the kernel hangs after saying " +"<computeroutput>Checking 'hlt' instruction...</computeroutput>, then you " +"should try the <userinput>no-hlt</userinput> boot argument, which disables " +"this test." msgstr "" #. Tag: para -#: boot-installer.xml:3670 +#: boot-installer.xml:3718 #, no-c-format -msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false video=vga16:off</userinput> to disable the framebuffer console. Only a reduced set of languages 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 a " +"reduced set of languages will be available during the installation due to " +"limited console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" #. Tag: title -#: boot-installer.xml:3684 +#: boot-installer.xml:3732 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:3685 +#: boot-installer.xml:3733 #, no-c-format -msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems." +msgid "" +"Some laptop models produced by Dell are known to crash when PCMCIA device " +"detection tries to access some hardware addresses. Other laptops may display " +"similar problems. If you experience such a problem and you don't need PCMCIA " +"support during the installation, you can disable PCMCIA using the " +"<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can " +"then configure PCMCIA after the installation is completed and exclude the " +"resource range causing the problems." msgstr "" #. Tag: para -#: boot-installer.xml:3695 +#: boot-installer.xml:3743 #, no-c-format -msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer." +msgid "" +"Alternatively, you can boot the installer in expert mode. You will then be " +"asked to enter the resource range options your hardware needs. For example, " +"if you have one of the Dell laptops mentioned above, you should enter " +"<userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list " +"of some common resource range options in the <ulink url=\"http://pcmcia-cs." +"sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource " +"settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the " +"commas, if any, when you enter this value in the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3712 +#: boot-installer.xml:3760 #, no-c-format msgid "System Freeze while Loading USB Modules" msgstr "" #. Tag: para -#: boot-installer.xml:3713 +#: boot-installer.xml:3761 #, no-c-format -msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>nousb</userinput> parameter at the boot prompt." +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>nousb</userinput> parameter at the boot " +"prompt." msgstr "" #. Tag: para -#: boot-installer.xml:3727 +#: boot-installer.xml:3775 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:3733 +#: boot-installer.xml:3781 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:3734 +#: boot-installer.xml:3782 #, no-c-format msgid "" - "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n" - "Remapping the kernel... done\n" - "Booting Linux...\n" - "</screen></informalexample> To work around this, you can either pull out one of the video cards, or disable the one not used during the OpenProm boot phase using a kernel parameter. For example, to disable an ATI card, you should boot the installer with <userinput>video=atyfb:off</userinput>." +"It is fairly common for &arch-title; to have two video cards in one machine, " +"for example an ATI card and a Sun Creator 3D. In some cases, this may result " +"in the video output getting misdirected soon after the system boots. In " +"typical cases, the display will only show: <informalexample><screen>\n" +"Remapping the kernel... done\n" +"Booting Linux...\n" +"</screen></informalexample> To work around this, you can either pull out one " +"of the video cards, or disable the one not used during the OpenProm boot " +"phase using a kernel parameter. For example, to disable an ATI card, you " +"should boot the installer with <userinput>video=atyfb:off</userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3748 +#: boot-installer.xml:3796 #, no-c-format -msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>." +msgid "" +"Note that you may also have to manually add this parameter to the silo " +"configuration (edit <filename>/target/etc/silo.conf</filename> before " +"rebooting) and, if you installed X11, modify the video driver in <filename>/" +"etc/X11/xorg.conf</filename>." msgstr "" #. Tag: title -#: boot-installer.xml:3759 +#: boot-installer.xml:3807 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3760 +#: boot-installer.xml:3808 #, no-c-format -msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems." +msgid "" +"Some Sparc systems are notoriously difficult to boot from CD-ROM and even if " +"they do boot, there may be inexplicable failures during the installation. " +"Most problems have been reported with SunBlade systems." msgstr "" #. Tag: para -#: boot-installer.xml:3766 +#: boot-installer.xml:3814 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3775 +#: boot-installer.xml:3823 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3777 +#: boot-installer.xml:3825 #, no-c-format -msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." +msgid "" +"During the boot sequence, you may see many messages in the form " +"<computeroutput>can't find <replaceable>something</replaceable></" +"computeroutput>, or <computeroutput><replaceable>something</replaceable> not " +"present</computeroutput>, <computeroutput>can't initialize " +"<replaceable>something</replaceable></computeroutput>, or even " +"<computeroutput>this driver release depends on <replaceable>something</" +"replaceable></computeroutput>. Most of these messages are harmless. You see " +"them because the kernel for the installation system is built to run on " +"computers with many different peripheral devices. Obviously, no one computer " +"will have every possible peripheral device, so the operating system may emit " +"a few complaints while it looks for peripherals you don't own. You may also " +"see the system pause for a while. This happens when it is waiting for a " +"device to respond, and that device is not present on your system. If you " +"find the time it takes to boot the system unacceptably long, you can create " +"a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." msgstr "" #. Tag: title -#: boot-installer.xml:3802 +#: boot-installer.xml:3850 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3803 +#: boot-installer.xml:3851 #, no-c-format -msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report, you may want to attach this information to the bug report." +msgid "" +"If you get through the initial boot phase but cannot complete the install, " +"the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. " +"It lets you store system error logs and configuration information from the " +"installer to a floppy, or download them using a web browser. This " +"information may provide clues as to what went wrong and how to fix it. If " +"you are submitting a bug report, you may want to attach this information to " +"the bug report." msgstr "" #. Tag: para -#: boot-installer.xml:3814 +#: boot-installer.xml:3862 #, no-c-format -msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system." +msgid "" +"Other pertinent installation messages may be found in <filename>/var/log/</" +"filename> during the installation, and <filename>/var/log/installer/</" +"filename> after the computer has been booted into the installed system." msgstr "" #. Tag: title -#: boot-installer.xml:3825 +#: boot-installer.xml:3873 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3826 +#: boot-installer.xml:3874 #, no-c-format -msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations." +msgid "" +"If you still have problems, please submit an installation report. We also " +"encourage installation reports to be sent even if the installation is " +"successful, so that we can get as much information as possible on the " +"largest number of hardware configurations." msgstr "" #. Tag: para -#: boot-installer.xml:3833 +#: boot-installer.xml:3881 #, no-c-format -msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public." +msgid "" +"Note that your installation report will be published in the Debian Bug " +"Tracking System (BTS) and forwarded to a public mailing list. Make sure that " +"you use an e-mail address that you do not mind being made public." msgstr "" #. Tag: para -#: boot-installer.xml:3839 +#: boot-installer.xml:3887 #, no-c-format -msgid "If you have a working Debian system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-reports</command>." +msgid "" +"If you have a working Debian system, the easiest way to send an installation " +"report is to install the <classname>installation-report</classname> and " +"<classname>reportbug</classname> packages (<command>aptitude install " +"installation-report reportbug</command>), configure <classname>reportbug</" +"classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the " +"command <command>reportbug installation-reports</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3849 +#: boot-installer.xml:3897 #, no-c-format msgid "" - "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n" - "Package: installation-reports\n" - "\n" - "Boot method: <How did you boot the installer? CD? floppy? network?>\n" - "Image version: <Full URL to image you downloaded is best>\n" - "Date: <Date and time of the install>\n" - "\n" - "Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" - "Processor:\n" - "Memory:\n" - "Partitions: <df -Tl will do; the raw partition table is preferred>\n" - "\n" - "Output of lspci -nn and lspci -vnn:\n" - "\n" - "Base System Installation Checklist:\n" - "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" - "\n" - "Initial boot: [ ]\n" - "Detect network card: [ ]\n" - "Configure network: [ ]\n" - "Detect CD: [ ]\n" - "Load installer modules: [ ]\n" - "Detect hard drives: [ ]\n" - "Partition hard drives: [ ]\n" - "Install base system: [ ]\n" - "Clock/timezone setup: [ ]\n" - "User/password setup: [ ]\n" - "Install tasks: [ ]\n" - "Install boot loader: [ ]\n" - "Overall install: [ ]\n" - "\n" - "Comments/Problems:\n" - "\n" - "<Description of the install, in prose, and any thoughts, comments\n" - " and ideas you had during the initial install.>\n" - "</screen></informalexample> In the bug report, describe what the problem is, including the last visible kernel messages in the event of a kernel hang. Describe the steps that you did which brought the system into the problem state." +"Alternatively you can use this template when filling out installation " +"reports, and file the report as a bug report against the " +"<classname>installation-reports</classname> pseudo package, by sending it to " +"<email>submit@bugs.debian.org</email>. <informalexample><screen>\n" +"Package: installation-reports\n" +"\n" +"Boot method: <How did you boot the installer? CD? floppy? network?>\n" +"Image version: <Full URL to image you downloaded is best>\n" +"Date: <Date and time of the install>\n" +"\n" +"Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" +"Processor:\n" +"Memory:\n" +"Partitions: <df -Tl will do; the raw partition table is preferred>\n" +"\n" +"Output of lspci -nn and lspci -vnn:\n" +"\n" +"Base System Installation Checklist:\n" +"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" +"\n" +"Initial boot: [ ]\n" +"Detect network card: [ ]\n" +"Configure network: [ ]\n" +"Detect CD: [ ]\n" +"Load installer modules: [ ]\n" +"Detect hard drives: [ ]\n" +"Partition hard drives: [ ]\n" +"Install base system: [ ]\n" +"Clock/timezone setup: [ ]\n" +"User/password setup: [ ]\n" +"Install tasks: [ ]\n" +"Install boot loader: [ ]\n" +"Overall install: [ ]\n" +"\n" +"Comments/Problems:\n" +"\n" +"<Description of the install, in prose, and any thoughts, comments\n" +" and ideas you had during the initial install.>\n" +"</screen></informalexample> In the bug report, describe what the problem is, " +"including the last visible kernel messages in the event of a kernel hang. " +"Describe the steps that you did which brought the system into the problem " +"state." msgstr "" - diff --git a/po/nn/preseed.po b/po/nn/preseed.po index 810935491..7d2ad8523 100644 --- a/po/nn/preseed.po +++ b/po/nn/preseed.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2008-04-30 00:09+0000\n" +"POT-Creation-Date: 2008-05-09 00:10+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -23,13 +23,17 @@ msgstr "" #. Tag: para #: preseed.xml:18 #, no-c-format -msgid "This appendix explains how to preseed answers to questions in &d-i; to automate your installation." +msgid "" +"This appendix explains how to preseed answers to questions in &d-i; to " +"automate your installation." msgstr "" #. Tag: para #: preseed.xml:23 preseed.xml:662 #, no-c-format -msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;." +msgid "" +"The configuration fragments used in this appendix are also available as an " +"example preconfiguration file from &urlset-example-preseed;." msgstr "" #. Tag: title @@ -41,13 +45,22 @@ msgstr "" #. Tag: para #: preseed.xml:32 #, no-c-format -msgid "Preseeding provides a way to set answers to questions asked during the installation process, without having to manually enter the answers while the installation is running. This makes it possible to fully automate most types of installation and even offers some features not available during normal installations." +msgid "" +"Preseeding provides a way to set answers to questions asked during the " +"installation process, without having to manually enter the answers while the " +"installation is running. This makes it possible to fully automate most types " +"of installation and even offers some features not available during normal " +"installations." msgstr "" #. Tag: para #: preseed.xml:40 #, no-c-format -msgid "Preseeding is not required. If you use an empty preseed file, the installer will behave just the same way as in a normal manual installation. Each question you preseed will (if you got it right!) modify the installation in some way from that baseline." +msgid "" +"Preseeding is not required. If you use an empty preseed file, the installer " +"will behave just the same way as in a normal manual installation. Each " +"question you preseed will (if you got it right!) modify the installation in " +"some way from that baseline." msgstr "" #. Tag: title @@ -59,13 +72,20 @@ msgstr "" #. Tag: para #: preseed.xml:51 #, no-c-format -msgid "There are three methods that can be used for preseeding: <firstterm>initrd</firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. Initrd preseeding will work with any installation method and supports preseeding of more things, but it requires the most preparation. File and network preseeding each can be used with different installation methods." +msgid "" +"There are three methods that can be used for preseeding: <firstterm>initrd</" +"firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. " +"Initrd preseeding will work with any installation method and supports " +"preseeding of more things, but it requires the most preparation. File and " +"network preseeding each can be used with different installation methods." msgstr "" #. Tag: para #: preseed.xml:60 #, no-c-format -msgid "The following table shows which preseeding methods can be used with which installation methods." +msgid "" +"The following table shows which preseeding methods can be used with which " +"installation methods." msgstr "" #. Tag: entry @@ -99,7 +119,10 @@ msgid "CD/DVD" msgstr "" #. Tag: entry -#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91 preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100 preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109 preseed.xml:111 +#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91 +#: preseed.xml:94 preseed.xml:95 preseed.xml:96 preseed.xml:99 preseed.xml:100 +#: preseed.xml:101 preseed.xml:104 preseed.xml:106 preseed.xml:109 +#: preseed.xml:111 #, no-c-format msgid "<entry>yes</entry>" msgstr "" @@ -107,7 +130,9 @@ msgstr "" #. Tag: para #: preseed.xml:81 #, no-c-format -msgid "but only if you have network access, and set <literal>preseed/url</literal> appropriately" +msgid "" +"but only if you have network access, and set <literal>preseed/url</literal> " +"appropriately" msgstr "" #. Tag: entry @@ -125,7 +150,8 @@ msgstr "" #. Tag: entry #: preseed.xml:93 #, no-c-format -msgid "hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>" +msgid "" +"hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>" msgstr "" #. Tag: entry @@ -149,19 +175,37 @@ msgstr "" #. Tag: para #: preseed.xml:117 #, no-c-format -msgid "An important difference between the preseeding methods is the point at which the preconfiguration file is loaded and processed. For initrd preseeding this is right at the start of the installation, before the first question is even asked. For file preseeding this is after the CD or CD image has been loaded. For network preseeding it is only after the network has been configured." +msgid "" +"An important difference between the preseeding methods is the point at which " +"the preconfiguration file is loaded and processed. For initrd preseeding " +"this is right at the start of the installation, before the first question is " +"even asked. For file preseeding this is after the CD or CD image has been " +"loaded. For network preseeding it is only after the network has been " +"configured." msgstr "" #. Tag: para #: preseed.xml:126 #, no-c-format -msgid "Obviously, any questions that have been processed before the preconfiguration file is loaded cannot be preseeded (this will include questions that are only displayed at medium or low priority, like the first hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way to avoid these questions being asked." +msgid "" +"Obviously, any questions that have been processed before the " +"preconfiguration file is loaded cannot be preseeded (this will include " +"questions that are only displayed at medium or low priority, like the first " +"hardware detection run). <xref linkend=\"preseed-bootparms\"/> offers a way " +"to avoid these questions being asked." msgstr "" #. Tag: para #: preseed.xml:134 #, no-c-format -msgid "In order to avoid the questions that would normally appear before the preseeding occurs, you can start the installer in <quote>auto</quote> mode. This delays questions that would normally be asked too early for preseeding (i.e. language, country and keyboard selection) until after the network comes up, thus allowing them to be preseeded. It also runs the installation at critical priority, which avoids many unimportant questions. See <xref linkend=\"preseed-auto\"/> for details." +msgid "" +"In order to avoid the questions that would normally appear before the " +"preseeding occurs, you can start the installer in <quote>auto</quote> mode. " +"This delays questions that would normally be asked too early for preseeding " +"(i.e. language, country and keyboard selection) until after the network " +"comes up, thus allowing them to be preseeded. It also runs the installation " +"at critical priority, which avoids many unimportant questions. See <xref " +"linkend=\"preseed-auto\"/> for details." msgstr "" #. Tag: title @@ -173,7 +217,11 @@ msgstr "" #. Tag: para #: preseed.xml:149 #, no-c-format -msgid "Although most questions used by &d-i; can be preseeded using this method, there are some notable exceptions. You must (re)partition an entire disk or use available free space on a disk; it is not possible to use existing partitions." +msgid "" +"Although most questions used by &d-i; can be preseeded using this method, " +"there are some notable exceptions. You must (re)partition an entire disk or " +"use available free space on a disk; it is not possible to use existing " +"partitions." msgstr "" #. Tag: title @@ -185,13 +233,24 @@ msgstr "" #. Tag: para #: preseed.xml:224 #, no-c-format -msgid "You will first need to create a preconfiguration file and place it in the location from where you want to use it. Creating the preconfiguration file is covered later in this appendix. Putting it in the correct location is fairly straightforward for network preseeding or if you want to read the file off a floppy or usb-stick. If you want to include the file on a CD or DVD, you will have to remaster the ISO image. How to get the preconfiguration file included in the initrd is outside the scope of this document; please consult the developers' documentation for &d-i;." +msgid "" +"You will first need to create a preconfiguration file and place it in the " +"location from where you want to use it. Creating the preconfiguration file " +"is covered later in this appendix. Putting it in the correct location is " +"fairly straightforward for network preseeding or if you want to read the " +"file off a floppy or usb-stick. If you want to include the file on a CD or " +"DVD, you will have to remaster the ISO image. How to get the " +"preconfiguration file included in the initrd is outside the scope of this " +"document; please consult the developers' documentation for &d-i;." msgstr "" #. Tag: para #: preseed.xml:235 #, no-c-format -msgid "An example preconfiguration file that you can use as basis for your own preconfiguration file is available from &urlset-example-preseed;. This file is based on the configuration fragments included in this appendix." +msgid "" +"An example preconfiguration file that you can use as basis for your own " +"preconfiguration file is available from &urlset-example-preseed;. This file " +"is based on the configuration fragments included in this appendix." msgstr "" #. Tag: title @@ -203,50 +262,70 @@ msgstr "" #. Tag: para #: preseed.xml:245 #, no-c-format -msgid "If you are using initrd preseeding, you only have to make sure a file named <filename>preseed.cfg</filename> is included in the root directory of the initrd. The installer will automatically check if this file is present and load it." +msgid "" +"If you are using initrd preseeding, you only have to make sure a file named " +"<filename>preseed.cfg</filename> is included in the root directory of the " +"initrd. The installer will automatically check if this file is present and " +"load it." msgstr "" #. Tag: para #: preseed.xml:252 #, no-c-format -msgid "For the other preseeding methods you need to tell the installer what file to use when you boot it. This is normally done by passing the kernel a boot parameter, either manually at boot time or by editing the bootloader configuration file (e.g. <filename>syslinux.cfg</filename>) and adding the parameter to the end of the append line(s) for the kernel." +msgid "" +"For the other preseeding methods you need to tell the installer what file to " +"use when you boot it. This is normally done by passing the kernel a boot " +"parameter, either manually at boot time or by editing the bootloader " +"configuration file (e.g. <filename>syslinux.cfg</filename>) and adding the " +"parameter to the end of the append line(s) for the kernel." msgstr "" #. Tag: para #: preseed.xml:260 #, no-c-format -msgid "If you do specify the preconfiguration file in the bootloader configuration, you might change the configuration so you don't need to hit enter to boot the installer. For syslinux this means setting the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>." +msgid "" +"If you do specify the preconfiguration file in the bootloader configuration, " +"you might change the configuration so you don't need to hit enter to boot " +"the installer. For syslinux this means setting the timeout to <literal>1</" +"literal> in <filename>syslinux.cfg</filename>." msgstr "" #. Tag: para #: preseed.xml:267 #, no-c-format -msgid "To make sure the installer gets the right preconfiguration file, you can optionally specify a checksum for the file. Currently this needs to be a md5sum, and if specified it must match the preconfiguration file or the installer will refuse to use it." +msgid "" +"To make sure the installer gets the right preconfiguration file, you can " +"optionally specify a checksum for the file. Currently this needs to be a " +"md5sum, and if specified it must match the preconfiguration file or the " +"installer will refuse to use it." msgstr "" #. Tag: screen #: preseed.xml:276 #, no-c-format msgid "" - "Boot parameters to specify:\n" - "- if you're netbooting:\n" - " preseed/url=http://host/path/to/preseed.cfg\n" - " preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n" - "\n" - "- if you're booting a remastered CD:\n" - " preseed/file=/cdrom/preseed.cfg\n" - " preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n" - "\n" - "- if you're installing from USB media (put the preconfiguration file in the\n" - " toplevel directory of the USB stick):\n" - " preseed/file=/hd-media/preseed.cfg\n" - " preseed/file/checksum=5da499872becccfeda2c4872f9171c3d" +"Boot parameters to specify:\n" +"- if you're netbooting:\n" +" preseed/url=http://host/path/to/preseed.cfg\n" +" preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n" +"\n" +"- if you're booting a remastered CD:\n" +" preseed/file=/cdrom/preseed.cfg\n" +" preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n" +"\n" +"- if you're installing from USB media (put the preconfiguration file in the\n" +" toplevel directory of the USB stick):\n" +" preseed/file=/hd-media/preseed.cfg\n" +" preseed/file/checksum=5da499872becccfeda2c4872f9171c3d" msgstr "" #. Tag: para #: preseed.xml:278 #, no-c-format -msgid "Note that <filename>preseed/url</filename> can be shortened to just <filename>url</filename> and <filename>preseed/file</filename> to just <filename>file</filename> when they are passed as boot parameters." +msgid "" +"Note that <filename>preseed/url</filename> can be shortened to just " +"<filename>url</filename> and <filename>preseed/file</filename> to just " +"<filename>file</filename> when they are passed as boot parameters." msgstr "" #. Tag: title @@ -258,55 +337,101 @@ msgstr "" #. Tag: para #: preseed.xml:289 #, no-c-format -msgid "If a preconfiguration file cannot be used to preseed some steps, the install can still be fully automated, since you can pass preseed values on the command line when booting the installer." +msgid "" +"If a preconfiguration file cannot be used to preseed some steps, the install " +"can still be fully automated, since you can pass preseed values on the " +"command line when booting the installer." msgstr "" #. Tag: para #: preseed.xml:295 #, no-c-format -msgid "Boot parameters can also be used if you do not really want to use preseeding, but just want to provide an answer for a specific question. Some examples where this can be useful are documented elsewhere in this manual." +msgid "" +"Boot parameters can also be used if you do not really want to use " +"preseeding, but just want to provide an answer for a specific question. Some " +"examples where this can be useful are documented elsewhere in this manual." msgstr "" #. Tag: para #: preseed.xml:301 #, no-c-format -msgid "To set a value to be used inside &d-i;, just pass <userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput> for any of the preseed variables listed in the examples in this appendix. If a value is to be used to configure packages for the target system, you will need to prepend the <firstterm>owner</firstterm><footnote> <para> The owner of a debconf variable (or template) is normally the name of the package that contains the corresponding debconf template. For variables used in the installer itself the owner is <quote>d-i</quote>. Templates and variables can have more than one owner which helps to determine whether they can be removed from the debconf database if the package is purged. </para> </footnote> of the variable as in <userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>. If you don't specify the owner, the value for the variable will not be copied to the debconf database in the target system and thus remain unused during the configuration of the relevant package." +msgid "" +"To set a value to be used inside &d-i;, just pass " +"<userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</" +"replaceable></userinput> for any of the preseed variables listed in the " +"examples in this appendix. If a value is to be used to configure packages " +"for the target system, you will need to prepend the <firstterm>owner</" +"firstterm><footnote> <para> The owner of a debconf variable (or template) is " +"normally the name of the package that contains the corresponding debconf " +"template. For variables used in the installer itself the owner is <quote>d-" +"i</quote>. Templates and variables can have more than one owner which helps " +"to determine whether they can be removed from the debconf database if the " +"package is purged. </para> </footnote> of the variable as in " +"<userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</" +"replaceable>=<replaceable>value</replaceable></userinput>. If you don't " +"specify the owner, the value for the variable will not be copied to the " +"debconf database in the target system and thus remain unused during the " +"configuration of the relevant package." msgstr "" #. Tag: para #: preseed.xml:324 #, no-c-format -msgid "Normally, preseeding a question in this way will mean that the question will not be asked. To set a specific default value for a question, but still have the question asked, use <quote>?=</quote> instead of <quote>=</quote> as operator. See also <xref linkend=\"preseed-seenflag\"/>." +msgid "" +"Normally, preseeding a question in this way will mean that the question will " +"not be asked. To set a specific default value for a question, but still have " +"the question asked, use <quote>?=</quote> instead of <quote>=</quote> as " +"operator. See also <xref linkend=\"preseed-seenflag\"/>." msgstr "" #. Tag: para #: preseed.xml:331 #, no-c-format -msgid "Note that some variables that are frequently set at the boot prompt have a shorter alias. If an alias is available, it is used in the examples in this appendix instead of the full variable. The <literal>preseed/url</literal> variable for example has been aliased as <literal>url</literal>. Another example is the <literal>tasks</literal> alias, which translates to <literal>tasksel:tasksel/first</literal>." +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. The <literal>preseed/url</literal> " +"variable for example has been aliased as <literal>url</literal>. Another " +"example is the <literal>tasks</literal> alias, which translates to " +"<literal>tasksel:tasksel/first</literal>." msgstr "" #. Tag: para #: preseed.xml:340 #, no-c-format -msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after the last <quote>--</quote> may be copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader). The installer will automatically filter out any options (like preconfiguration options) that it recognizes." +msgid "" +"A <quote>--</quote> in the boot options has special meaning. Kernel " +"parameters that appear after the last <quote>--</quote> may be copied into " +"the bootloader configuration for the installed system (if supported by the " +"installer for the bootloader). The installer will automatically filter out " +"any options (like preconfiguration options) that it recognizes." msgstr "" #. Tag: para #: preseed.xml:349 #, no-c-format -msgid "Current linux kernels (2.6.9 and later) accept a maximum of 32 command line options and 32 environment options, including any options added by default for the installer. If these numbers are exceeded, the kernel will panic (crash). (For earlier kernels, these numbers were lower.)" +msgid "" +"Current linux kernels (2.6.9 and later) accept a maximum of 32 command line " +"options and 32 environment options, including any options added by default " +"for the installer. If these numbers are exceeded, the kernel will panic " +"(crash). (For earlier kernels, these numbers were lower.)" msgstr "" #. Tag: para #: preseed.xml:357 #, no-c-format -msgid "For most installations some of the default options in your bootloader configuration file, like <literal>vga=normal</literal>, may be safely removed which may allow you to add more options for preseeding." +msgid "" +"For most installations some of the default options in your bootloader " +"configuration file, like <literal>vga=normal</literal>, may be safely " +"removed which may allow you to add more options for preseeding." msgstr "" #. Tag: para #: preseed.xml:364 #, no-c-format -msgid "It may not always be possible to specify values with spaces for boot parameters, even if you delimit them with quotes." +msgid "" +"It may not always be possible to specify values with spaces for boot " +"parameters, even if you delimit them with quotes." msgstr "" #. Tag: title @@ -319,24 +444,55 @@ msgstr "" #: preseed.xml:374 #, no-c-format msgid "" - "There are several features of Debian Installer that combine to allow fairly simple command lines at the boot prompt to result in arbitrarily complex customized automatic installs. To illustrate this, here are some examples that can be used at the boot prompt: <informalexample><screen>\n" - "auto url=autoserver\n" - "</screen></informalexample> This relies on there being a DHCP server that will get the machine to the point where <literal>autoserver</literal> can be resolved by DNS, perhaps after adding the local domain if that was provided by DHCP. If this was done at a site where the domain is <literal>example.com</literal>, and they have a reasonably sane DHCP setup, it would result in the preseed file being retrieved from <literal>http://autoserver.example.com/d-i/&releasename;/./preseed.cfg</literal>." +"There are several features of Debian Installer that combine to allow fairly " +"simple command lines at the boot prompt to result in arbitrarily complex " +"customized automatic installs. To illustrate this, here are some examples " +"that can be used at the boot prompt: <informalexample><screen>\n" +"auto url=autoserver\n" +"</screen></informalexample> This relies on there being a DHCP server that " +"will get the machine to the point where <literal>autoserver</literal> can be " +"resolved by DNS, perhaps after adding the local domain if that was provided " +"by DHCP. If this was done at a site where the domain is <literal>example." +"com</literal>, and they have a reasonably sane DHCP setup, it would result " +"in the preseed file being retrieved from <literal>http://autoserver.example." +"com/d-i/&releasename;/./preseed.cfg</literal>." msgstr "" #. Tag: para #: preseed.xml:391 #, no-c-format -msgid "The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</literal>) is taken from <literal>auto-install/defaultroot</literal>. By default this includes the directory <literal>&releasename;</literal> to allow future versions to specify their own codename and let people migrate forwards in a controlled manner. The <literal>/./</literal> bit is used to indicate a root, relative to which subsequent paths can be anchored (for use in preseed/include and preseed/run). This allows files to be specified either as full URLs, paths starting with / that are thus anchored, or even paths relative to the location where the last preseed file was found. This can be used to construct more portable scripts where an entire hierarchy of scripts can be moved to a new location without breaking it, for example copying the files onto a USB stick when they started out on a web server. In this example, if the preseed file sets <literal>preseed/run</literal> to <literal>/scripts/late_command.sh</literal> then the file will be fetched from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/late_command.sh</literal>." +msgid "" +"The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</" +"literal>) is taken from <literal>auto-install/defaultroot</literal>. By " +"default this includes the directory <literal>&releasename;</literal> to " +"allow future versions to specify their own codename and let people migrate " +"forwards in a controlled manner. The <literal>/./</literal> bit is used to " +"indicate a root, relative to which subsequent paths can be anchored (for use " +"in preseed/include and preseed/run). This allows files to be specified " +"either as full URLs, paths starting with / that are thus anchored, or even " +"paths relative to the location where the last preseed file was found. This " +"can be used to construct more portable scripts where an entire hierarchy of " +"scripts can be moved to a new location without breaking it, for example " +"copying the files onto a USB stick when they started out on a web server. In " +"this example, if the preseed file sets <literal>preseed/run</literal> to " +"<literal>/scripts/late_command.sh</literal> then the file will be fetched " +"from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/" +"late_command.sh</literal>." msgstr "" #. Tag: para #: preseed.xml:411 #, no-c-format msgid "" - "If there is no local DHCP or DNS infrastructure, or if you do not want to use the default path to <filename>preseed.cfg</filename>, you can still use an explicit url, and if you don't use the <literal>/./</literal> element it will be anchored to the start of the path (i.e. the third <literal>/</literal> in the URL). Here is an example that requires minimal support from the local network infrastructure: <informalexample><screen>\n" - "auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</replaceable>\n" - "</screen></informalexample> The way this works is that:" +"If there is no local DHCP or DNS infrastructure, or if you do not want to " +"use the default path to <filename>preseed.cfg</filename>, you can still use " +"an explicit url, and if you don't use the <literal>/./</literal> element it " +"will be anchored to the start of the path (i.e. the third <literal>/</" +"literal> in the URL). Here is an example that requires minimal support from " +"the local network infrastructure: <informalexample><screen>\n" +"auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</" +"replaceable>\n" +"</screen></informalexample> The way this works is that:" msgstr "" #. Tag: para @@ -348,46 +504,82 @@ msgstr "" #. Tag: para #: preseed.xml:427 #, no-c-format -msgid "if the hostname section contains no periods, it has the domain derived from DHCP appended to it, and" +msgid "" +"if the hostname section contains no periods, it has the domain derived from " +"DHCP appended to it, and" msgstr "" #. Tag: para #: preseed.xml:431 #, no-c-format -msgid "if there's no <literal>/</literal>'s after the hostname, then the default path is added." +msgid "" +"if there's no <literal>/</literal>'s after the hostname, then the default " +"path is added." msgstr "" #. Tag: para #: preseed.xml:437 #, no-c-format msgid "" - "In addition to specifying the url, you can also specify settings that do not directly affect the behavior of &d-i; itself, but can be passed through to scripts specified using <literal>preseed/run</literal> in the loaded preseed file. At present, the only example of this is <literal>auto-install/classes</literal>, which has an alias <literal>classes</literal>. This can be used thus: <informalexample><screen>\n" - "auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;class_B</replaceable>\n" - "</screen></informalexample> The classes could for example denote the type of system to be installed, or the localization to be used." +"In addition to specifying the url, you can also specify settings that do not " +"directly affect the behavior of &d-i; itself, but can be passed through to " +"scripts specified using <literal>preseed/run</literal> in the loaded preseed " +"file. At present, the only example of this is <literal>auto-install/classes</" +"literal>, which has an alias <literal>classes</literal>. This can be used " +"thus: <informalexample><screen>\n" +"auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;" +"class_B</replaceable>\n" +"</screen></informalexample> The classes could for example denote the type of " +"system to be installed, or the localization to be used." msgstr "" #. Tag: para #: preseed.xml:451 #, no-c-format -msgid "It is of course possible to extend this concept, and if you do, it is reasonable to use the auto-install namespace for this. So one might have something like <literal>auto-install/style</literal> which is then used in your scripts. If you feel the need to do this, please mention it on the <email>debian-boot@lists.debian.org</email> mailing list so that we can avoid namespace conflicts, and perhaps add an alias for the parameter for you." +msgid "" +"It is of course possible to extend this concept, and if you do, it is " +"reasonable to use the auto-install namespace for this. So one might have " +"something like <literal>auto-install/style</literal> which is then used in " +"your scripts. If you feel the need to do this, please mention it on the " +"<email>debian-boot@lists.debian.org</email> mailing list so that we can " +"avoid namespace conflicts, and perhaps add an alias for the parameter for " +"you." msgstr "" #. Tag: para #: preseed.xml:461 #, no-c-format -msgid "The <literal>auto</literal> boot label is not yet defined on all architectures. The same effect may be achieved by simply adding the two parameters <literal>auto=true priority=critical</literal> to the kernel command line. The <literal>auto</literal> parameter is an alias for <literal>auto-install/enable</literal> and controls the delay of the locale and keyboard questions until after there has been a chance to preseed them, while <literal>priority</literal> is an alias for <literal>debconf/priority</literal> and setting it to <literal>critical</literal> stops any questions with a lower priority from being asked." +msgid "" +"The <literal>auto</literal> boot label is not yet defined on all " +"architectures. The same effect may be achieved by simply adding the two " +"parameters <literal>auto=true priority=critical</literal> to the kernel " +"command line. The <literal>auto</literal> parameter is an alias for " +"<literal>auto-install/enable</literal> and controls the delay of the locale " +"and keyboard questions until after there has been a chance to preseed them, " +"while <literal>priority</literal> is an alias for <literal>debconf/priority</" +"literal> and setting it to <literal>critical</literal> stops any questions " +"with a lower priority from being asked." msgstr "" #. Tag: para #: preseed.xml:474 #, no-c-format -msgid "Additional options that may be of interest while attempting to automate an install while using DHCP are: <literal>interface=auto netcfg/dhcp_timeout=60</literal> which makes the machine choose the first viable NIC and be more patient about getting a reply to its DHCP query." +msgid "" +"Additional options that may be of interest while attempting to automate an " +"install while using DHCP are: <literal>interface=auto netcfg/" +"dhcp_timeout=60</literal> which makes the machine choose the first viable " +"NIC and be more patient about getting a reply to its DHCP query." msgstr "" #. Tag: para #: preseed.xml:483 #, no-c-format -msgid "An extensive example of how to use this framework, including example scripts and classes, can be found on the <ulink url=\"http://hands.com/d-i/\">website of its developer</ulink>. The examples available there also show many other nice effects that can be achieved by creative use of preconfiguration." +msgid "" +"An extensive example of how to use this framework, including example scripts " +"and classes, can be found on the <ulink url=\"http://hands.com/d-i/" +"\">website of its developer</ulink>. The examples available there also show " +"many other nice effects that can be achieved by creative use of " +"preconfiguration." msgstr "" #. Tag: title @@ -549,28 +741,44 @@ msgstr "" #. Tag: para #: preseed.xml:524 #, no-c-format -msgid "It's also possible to use DHCP to specify a preconfiguration file to download from the network. DHCP allows specifying a filename. Normally this is a file to netboot, but if it appears to be an URL then installation media that support network preseeding will download the file from the URL and use it as a preconfiguration file. Here is an example of how to set it up in the dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server Debian package)." +msgid "" +"It's also possible to use DHCP to specify a preconfiguration file to " +"download from the network. DHCP allows specifying a filename. Normally this " +"is a file to netboot, but if it appears to be an URL then installation media " +"that support network preseeding will download the file from the URL and use " +"it as a preconfiguration file. Here is an example of how to set it up in the " +"dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server Debian " +"package)." msgstr "" #. Tag: screen #: preseed.xml:535 #, no-c-format msgid "" - "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n" - " filename \"http://host/preseed.cfg\";\n" - "}" +"if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n" +" filename \"http://host/preseed.cfg\";\n" +"}" msgstr "" #. Tag: para #: preseed.xml:537 #, no-c-format -msgid "Note that the above example limits this filename to DHCP clients that identify themselves as \"d-i\", so it will not affect regular DHCP clients, but only the installer. You can also put the text in a stanza for only one particular host to avoid preseeding all installs on your network." +msgid "" +"Note that the above example limits this filename to DHCP clients that " +"identify themselves as \"d-i\", so it will not affect regular DHCP clients, " +"but only the installer. You can also put the text in a stanza for only one " +"particular host to avoid preseeding all installs on your network." msgstr "" #. Tag: para #: preseed.xml:544 #, no-c-format -msgid "A good way to use the DHCP preseeding is to only preseed values specific to your network, such as the Debian mirror to use. This way installs on your network will automatically get a good mirror selected, but the rest of the installation can be performed interactively. Using DHCP preseeding to fully automate Debian installs should only be done with care." +msgid "" +"A good way to use the DHCP preseeding is to only preseed values specific to " +"your network, such as the Debian mirror to use. This way installs on your " +"network will automatically get a good mirror selected, but the rest of the " +"installation can be performed interactively. Using DHCP preseeding to fully " +"automate Debian installs should only be done with care." msgstr "" #. Tag: title @@ -582,7 +790,10 @@ msgstr "" #. Tag: para #: preseed.xml:559 #, no-c-format -msgid "The preconfiguration file is in the format used by the <command>debconf-set-selections</command> command. The general format of a line in a preconfiguration file is:" +msgid "" +"The preconfiguration file is in the format used by the <command>debconf-set-" +"selections</command> command. The general format of a line in a " +"preconfiguration file is:" msgstr "" #. Tag: screen @@ -594,87 +805,130 @@ msgstr "" #. Tag: para #: preseed.xml:567 #, no-c-format -msgid "There are a few rules to keep in mind when writing a preconfiguration file." +msgid "" +"There are a few rules to keep in mind when writing a preconfiguration file." msgstr "" #. Tag: para #: preseed.xml:574 #, no-c-format -msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value." +msgid "" +"Put only a single space or tab between type and value: any additional " +"whitespace will be interpreted as belonging to the value." msgstr "" #. Tag: para #: preseed.xml:578 #, no-c-format -msgid "A line can be split into multiple lines by appending a backslash (<quote><literal>\\</literal></quote>) as the line continuation character. A good place to split a line is after the question name; a bad place is between type and value." +msgid "" +"A line can be split into multiple lines by appending a backslash " +"(<quote><literal>\\</literal></quote>) as the line continuation character. A " +"good place to split a line is after the question name; a bad place is " +"between type and value." msgstr "" #. Tag: para #: preseed.xml:584 #, no-c-format -msgid "For debconf variables (templates) used in the installer itself, the owner should be set to <quote>d-i</quote>; to preseed variables used in the installed system, the name of the package that contains the corresponding debconf template should be used. Only variables that have their owner set to something other than <quote>d-i</quote> will be propagated to the debconf database for the installed system." +msgid "" +"For debconf variables (templates) used in the installer itself, the owner " +"should be set to <quote>d-i</quote>; to preseed variables used in the " +"installed system, the name of the package that contains the corresponding " +"debconf template should be used. Only variables that have their owner set to " +"something other than <quote>d-i</quote> will be propagated to the debconf " +"database for the installed system." msgstr "" #. Tag: para #: preseed.xml:592 #, no-c-format -msgid "Most questions need to be preseeded using the values valid in English and not the translated values. However, there are some questions (for example in <classname>partman</classname>) where the translated values need to be used." +msgid "" +"Most questions need to be preseeded using the values valid in English and " +"not the translated values. However, there are some questions (for example in " +"<classname>partman</classname>) where the translated values need to be used." msgstr "" #. Tag: para #: preseed.xml:598 #, no-c-format -msgid "Some questions take a code as value instead of the English text that is shown during installation." +msgid "" +"Some questions take a code as value instead of the English text that is " +"shown during installation." msgstr "" #. Tag: para #: preseed.xml:604 #, no-c-format -msgid "The easiest way to create a preconfiguration file is to use the example file linked in <xref linkend=\"preseed-contents\"/> as basis and work from there." +msgid "" +"The easiest way to create a preconfiguration file is to use the example file " +"linked in <xref linkend=\"preseed-contents\"/> as basis and work from there." msgstr "" #. Tag: para #: preseed.xml:609 #, no-c-format -msgid "An alternative method is to do a manual installation and then, after rebooting, use the <command>debconf-get-selections</command> from the <classname>debconf-utils</classname> package to dump both the debconf database and the installer's cdebconf database to a single file:" +msgid "" +"An alternative method is to do a manual installation and then, after " +"rebooting, use the <command>debconf-get-selections</command> from the " +"<classname>debconf-utils</classname> package to dump both the debconf " +"database and the installer's cdebconf database to a single file:" msgstr "" #. Tag: screen #: preseed.xml:616 #, no-c-format msgid "" - "$ debconf-get-selections --installer > <replaceable>file</replaceable>\n" - "$ debconf-get-selections >> <replaceable>file</replaceable>" +"$ debconf-get-selections --installer > <replaceable>file</replaceable>\n" +"$ debconf-get-selections >> <replaceable>file</replaceable>" msgstr "" #. Tag: para #: preseed.xml:618 #, no-c-format -msgid "However, a file generated in this manner will have some items that should not be preseeded, and the example file is a better starting place for most users." +msgid "" +"However, a file generated in this manner will have some items that should " +"not be preseeded, and the example file is a better starting place for most " +"users." msgstr "" #. Tag: para #: preseed.xml:626 #, no-c-format -msgid "This method relies on the fact that, at the end of the installation, the installer's cdebconf database is saved to the installed system in <filename>/var/log/installer/cdebconf</filename>. However, because the database may contain sensitive information, by default the files are only readable by root." +msgid "" +"This method relies on the fact that, at the end of the installation, the " +"installer's cdebconf database is saved to the installed system in <filename>/" +"var/log/installer/cdebconf</filename>. However, because the database may " +"contain sensitive information, by default the files are only readable by " +"root." msgstr "" #. Tag: para #: preseed.xml:634 #, no-c-format -msgid "The directory <filename>/var/log/installer</filename> and all files in it will be deleted from your system if you purge the package <classname>installation-report</classname>." +msgid "" +"The directory <filename>/var/log/installer</filename> and all files in it " +"will be deleted from your system if you purge the package " +"<classname>installation-report</classname>." msgstr "" #. Tag: para #: preseed.xml:642 #, no-c-format -msgid "To check possible values for questions, you can use <command>nano</command> to examine the files in <filename>/var/lib/cdebconf</filename> while an installation is in progress. View <filename>templates.dat</filename> for the raw templates and <filename>questions.dat</filename> for the current values and for the values assigned to variables." +msgid "" +"To check possible values for questions, you can use <command>nano</command> " +"to examine the files in <filename>/var/lib/cdebconf</filename> while an " +"installation is in progress. View <filename>templates.dat</filename> for the " +"raw templates and <filename>questions.dat</filename> for the current values " +"and for the values assigned to variables." msgstr "" #. Tag: para #: preseed.xml:650 #, no-c-format -msgid "To check if the format of your preconfiguration file is valid before performing an install, you can use the command <command>debconf-set-selections -c <replaceable>preseed.cfg</replaceable></command>." +msgid "" +"To check if the format of your preconfiguration file is valid before " +"performing an install, you can use the command <command>debconf-set-" +"selections -c <replaceable>preseed.cfg</replaceable></command>." msgstr "" #. Tag: title @@ -686,7 +940,12 @@ msgstr "" #. Tag: para #: preseed.xml:667 #, no-c-format -msgid "Note that this example is based on an installation for the Intel x86 architecture. If you are installing a different architecture, some of the examples (like keyboard selection and bootloader installation) may not be relevant and will need to be replaced by debconf settings appropriate for your architecture." +msgid "" +"Note that this example is based on an installation for the Intel x86 " +"architecture. If you are installing a different architecture, some of the " +"examples (like keyboard selection and bootloader installation) may not be " +"relevant and will need to be replaced by debconf settings appropriate for " +"your architecture." msgstr "" #. Tag: title @@ -698,50 +957,66 @@ msgstr "" #. Tag: para #: preseed.xml:679 #, no-c-format -msgid "Setting localization values will only work if you are using initrd preseeding. With all other methods the preconfiguration file will only be loaded after these questions have been asked." +msgid "" +"Setting localization values will only work if you are using initrd " +"preseeding. With all other methods the preconfiguration file will only be " +"loaded after these questions have been asked." msgstr "" #. Tag: para #: preseed.xml:685 #, no-c-format -msgid "The locale can be used to specify both language and country. To specify the locale as a boot parameter, use <userinput>locale=<replaceable>en_US</replaceable></userinput>." +msgid "" +"The locale can be used to specify both language and country. To specify the " +"locale as a boot parameter, use <userinput>locale=<replaceable>en_US</" +"replaceable></userinput>." msgstr "" #. Tag: screen #: preseed.xml:691 #, no-c-format msgid "" - "# Locale sets language and country.\n" - "d-i debian-installer/locale string en_US" +"# Locale sets language and country.\n" +"d-i debian-installer/locale string en_US" msgstr "" #. Tag: para #: preseed.xml:693 #, no-c-format -msgid "Keyboard configuration consists of selecting a keyboard architecture and a keymap. In most cases the correct keyboard architecture is selected by default, so there's normally no need to preseed it. The keymap must be valid for the selected keyboard architecture." +msgid "" +"Keyboard configuration consists of selecting a keyboard architecture and a " +"keymap. In most cases the correct keyboard architecture is selected by " +"default, so there's normally no need to preseed it. The keymap must be valid " +"for the selected keyboard architecture." msgstr "" #. Tag: screen #: preseed.xml:700 #, no-c-format msgid "" - "# Keyboard selection.\n" - "#d-i console-tools/archs select at\n" - "d-i console-keymaps-at/keymap select us\n" - "# Example for a different keyboard architecture\n" - "#d-i console-keymaps-usb/keymap select mac-usb-us" +"# Keyboard selection.\n" +"#d-i console-tools/archs select at\n" +"d-i console-keymaps-at/keymap select us\n" +"# Example for a different keyboard architecture\n" +"#d-i console-keymaps-usb/keymap select mac-usb-us" msgstr "" #. Tag: para #: preseed.xml:702 #, no-c-format -msgid "To skip keyboard configuration, preseed <classname>console-tools/archs</classname> with <userinput>skip-config</userinput>. This will result in the kernel keymap remaining active." +msgid "" +"To skip keyboard configuration, preseed <classname>console-tools/archs</" +"classname> with <userinput>skip-config</userinput>. This will result in the " +"kernel keymap remaining active." msgstr "" #. Tag: para #: preseed.xml:711 #, no-c-format -msgid "The changes in the input layer for 2.6 kernels have made the keyboard architecture virtually obsolete. For 2.6 kernels normally a <quote>PC</quote> (<userinput>at</userinput>) keymap should be selected." +msgid "" +"The changes in the input layer for 2.6 kernels have made the keyboard " +"architecture virtually obsolete. For 2.6 kernels normally a <quote>PC</" +"quote> (<userinput>at</userinput>) keymap should be selected." msgstr "" #. Tag: title @@ -753,19 +1028,34 @@ msgstr "" #. Tag: para #: preseed.xml:722 #, no-c-format -msgid "Of course, preseeding the network configuration won't work if you're loading your preconfiguration file from the network. But it's great when you're booting from CD or USB stick. If you are loading preconfiguration files from the network, you can pass network config parameters by using kernel boot parameters." +msgid "" +"Of course, preseeding the network configuration won't work if you're loading " +"your preconfiguration file from the network. But it's great when you're " +"booting from CD or USB stick. If you are loading preconfiguration files from " +"the network, you can pass network config parameters by using kernel boot " +"parameters." msgstr "" #. Tag: para #: preseed.xml:730 #, no-c-format -msgid "If you need to pick a particular interface when netbooting before loading a preconfiguration file from the network, use a boot parameter such as <userinput>interface=<replaceable>eth1</replaceable></userinput>." +msgid "" +"If you need to pick a particular interface when netbooting before loading a " +"preconfiguration file from the network, use a boot parameter such as " +"<userinput>interface=<replaceable>eth1</replaceable></userinput>." msgstr "" #. Tag: para #: preseed.xml:736 #, no-c-format -msgid "Although preseeding the network configuration is normally not possible when using network preseeding (using <quote>preseed/url</quote>), you can use the following hack to work around that, for example if you'd like to set a static address for the network interface. The hack is to force the network configuration to run again after the preconfiguration file has been loaded by creating a <quote>preseed/run</quote> script containing the following commands:" +msgid "" +"Although preseeding the network configuration is normally not possible when " +"using network preseeding (using <quote>preseed/url</quote>), you can use the " +"following hack to work around that, for example if you'd like to set a " +"static address for the network interface. The hack is to force the network " +"configuration to run again after the preconfiguration file has been loaded " +"by creating a <quote>preseed/run</quote> script containing the following " +"commands:" msgstr "" #. Tag: screen @@ -784,44 +1074,44 @@ msgstr "" #: preseed.xml:754 #, no-c-format msgid "" - "# netcfg will choose an interface that has link if possible. This makes it\n" - "# skip displaying a list if there is more than one interface.\n" - "d-i netcfg/choose_interface select auto\n" - "\n" - "# To pick a particular interface instead:\n" - "#d-i netcfg/choose_interface select eth1\n" - "\n" - "# If you have a slow dhcp server and the installer times out waiting for\n" - "# it, this might be useful.\n" - "#d-i netcfg/dhcp_timeout string 60\n" - "\n" - "# If you prefer to configure the network manually, uncomment this line and\n" - "# the static network configuration below.\n" - "#d-i netcfg/disable_dhcp boolean true\n" - "\n" - "# If you want the preconfiguration file to work on systems both with and\n" - "# without a dhcp server, uncomment these lines and the static network\n" - "# configuration below.\n" - "#d-i netcfg/dhcp_failed note\n" - "#d-i netcfg/dhcp_options select Configure network manually\n" - "\n" - "# Static network configuration.\n" - "#d-i netcfg/get_nameservers string 192.168.1.1\n" - "#d-i netcfg/get_ipaddress string 192.168.1.42\n" - "#d-i netcfg/get_netmask string 255.255.255.0\n" - "#d-i netcfg/get_gateway string 192.168.1.1\n" - "#d-i netcfg/confirm_static boolean true\n" - "\n" - "# Any hostname and domain names assigned from dhcp take precedence over\n" - "# values set here. However, setting the values still prevents the questions\n" - "# from being shown, even if values come from dhcp.\n" - "d-i netcfg/get_hostname string unassigned-hostname\n" - "d-i netcfg/get_domain string unassigned-domain\n" - "\n" - "# Disable that annoying WEP key dialog.\n" - "d-i netcfg/wireless_wep string\n" - "# The wacky dhcp hostname that some ISPs use as a password of sorts.\n" - "#d-i netcfg/dhcp_hostname string radish" +"# netcfg will choose an interface that has link if possible. This makes it\n" +"# skip displaying a list if there is more than one interface.\n" +"d-i netcfg/choose_interface select auto\n" +"\n" +"# To pick a particular interface instead:\n" +"#d-i netcfg/choose_interface select eth1\n" +"\n" +"# If you have a slow dhcp server and the installer times out waiting for\n" +"# it, this might be useful.\n" +"#d-i netcfg/dhcp_timeout string 60\n" +"\n" +"# If you prefer to configure the network manually, uncomment this line and\n" +"# the static network configuration below.\n" +"#d-i netcfg/disable_dhcp boolean true\n" +"\n" +"# If you want the preconfiguration file to work on systems both with and\n" +"# without a dhcp server, uncomment these lines and the static network\n" +"# configuration below.\n" +"#d-i netcfg/dhcp_failed note\n" +"#d-i netcfg/dhcp_options select Configure network manually\n" +"\n" +"# Static network configuration.\n" +"#d-i netcfg/get_nameservers string 192.168.1.1\n" +"#d-i netcfg/get_ipaddress string 192.168.1.42\n" +"#d-i netcfg/get_netmask string 255.255.255.0\n" +"#d-i netcfg/get_gateway string 192.168.1.1\n" +"#d-i netcfg/confirm_static boolean true\n" +"\n" +"# Any hostname and domain names assigned from dhcp take precedence over\n" +"# values set here. However, setting the values still prevents the questions\n" +"# from being shown, even if values come from dhcp.\n" +"d-i netcfg/get_hostname string unassigned-hostname\n" +"d-i netcfg/get_domain string unassigned-domain\n" +"\n" +"# Disable that annoying WEP key dialog.\n" +"d-i netcfg/wireless_wep string\n" +"# The wacky dhcp hostname that some ISPs use as a password of sorts.\n" +"#d-i netcfg/dhcp_hostname string radish" msgstr "" #. Tag: title @@ -833,36 +1123,48 @@ msgstr "" #. Tag: para #: preseed.xml:760 #, no-c-format -msgid "Depending on the installation method you use, a mirror may be used to download additional components of the installer, to install the base system, and to set up the <filename>/etc/apt/sources.list</filename> for the installed system." +msgid "" +"Depending on the installation method you use, a mirror may be used to " +"download additional components of the installer, to install the base system, " +"and to set up the <filename>/etc/apt/sources.list</filename> for the " +"installed system." msgstr "" #. Tag: para #: preseed.xml:767 #, no-c-format -msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system." +msgid "" +"The parameter <classname>mirror/suite</classname> determines the suite for " +"the installed system." msgstr "" #. Tag: para #: preseed.xml:772 #, no-c-format -msgid "The parameter <classname>mirror/udeb/suite</classname> determines the suite for additional components for the installer. It is only useful to set this if components are actually downloaded over the network and should match the suite that was used to build the initrd for the installation method used for the installation. By default the value for <classname>mirror/udeb/suite</classname> is the same as <classname>mirror/suite</classname>." +msgid "" +"The parameter <classname>mirror/udeb/suite</classname> determines the suite " +"for additional components for the installer. It is only useful to set this " +"if components are actually downloaded over the network and should match the " +"suite that was used to build the initrd for the installation method used for " +"the installation. By default the value for <classname>mirror/udeb/suite</" +"classname> is the same as <classname>mirror/suite</classname>." msgstr "" #. Tag: screen #: preseed.xml:784 #, no-c-format msgid "" - "# If you select ftp, the mirror/country string does not need to be set.\n" - "#d-i mirror/protocol string ftp\n" - "d-i mirror/country string manual\n" - "d-i mirror/http/hostname string &archive-mirror;\n" - "d-i mirror/http/directory string /debian\n" - "d-i mirror/http/proxy string\n" - "\n" - "# Suite to install.\n" - "#d-i mirror/suite string testing\n" - "# Suite to use for loading installer components (optional).\n" - "#d-i mirror/udeb/suite string testing" +"# If you select ftp, the mirror/country string does not need to be set.\n" +"#d-i mirror/protocol string ftp\n" +"d-i mirror/country string manual\n" +"d-i mirror/http/hostname string &archive-mirror;\n" +"d-i mirror/http/directory string /debian\n" +"d-i mirror/http/proxy string\n" +"\n" +"# Suite to install.\n" +"#d-i mirror/suite string testing\n" +"# Suite to use for loading installer components (optional).\n" +"#d-i mirror/udeb/suite string testing" msgstr "" #. Tag: title @@ -875,17 +1177,17 @@ msgstr "" #: preseed.xml:791 #, no-c-format msgid "" - "# Controls whether or not the hardware clock is set to UTC.\n" - "d-i clock-setup/utc boolean true\n" - "\n" - "# You may set this to any valid setting for $TZ; see the contents of\n" - "# /usr/share/zoneinfo/ for valid values.\n" - "d-i time/zone string US/Eastern\n" - "\n" - "# Controls whether to use NTP to set the clock during the install\n" - "d-i clock-setup/ntp boolean true\n" - "# NTP server to use. The default is almost always fine here.\n" - "#d-i clock-setup/ntp-server ntp.example.com" +"# Controls whether or not the hardware clock is set to UTC.\n" +"d-i clock-setup/utc boolean true\n" +"\n" +"# You may set this to any valid setting for $TZ; see the contents of\n" +"# /usr/share/zoneinfo/ for valid values.\n" +"d-i time/zone string US/Eastern\n" +"\n" +"# Controls whether to use NTP to set the clock during the install\n" +"d-i clock-setup/ntp boolean true\n" +"# NTP server to use. The default is almost always fine here.\n" +"#d-i clock-setup/ntp-server ntp.example.com" msgstr "" #. Tag: title @@ -897,83 +1199,94 @@ msgstr "" #. Tag: para #: preseed.xml:797 #, no-c-format -msgid "Using preseeding to partition the harddisk is very much limited to what is supported by <classname>partman-auto</classname>. You can choose to partition either existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file. It is currently not possible to partition multiple disks using preseeding." +msgid "" +"Using preseeding to partition the harddisk is very much limited to what is " +"supported by <classname>partman-auto</classname>. You can choose to " +"partition either existing free space on a disk or a whole disk. The layout " +"of the disk can be determined by using a predefined recipe, a custom recipe " +"from a recipe file or a recipe included in the preconfiguration file. It is " +"currently not possible to partition multiple disks using preseeding." msgstr "" #. Tag: para #: preseed.xml:808 #, no-c-format -msgid "The identification of disks is dependent on the order in which their drivers are loaded. If there are multiple disks in the system, make very sure the correct one will be selected before using preseeding." +msgid "" +"The identification of disks is dependent on the order in which their drivers " +"are loaded. If there are multiple disks in the system, make very sure the " +"correct one will be selected before using preseeding." msgstr "" #. Tag: screen #: preseed.xml:816 #, no-c-format msgid "" - "# If the system has free space you can choose to only partition that space.\n" - "# Note: this must be preseeded with a localized (translated) value.\n" - "#d-i partman-auto/init_automatically_partition \\\n" - "# select Guided - use the largest continuous free space\n" - "\n" - "# Alternatively, you can specify a disk to partition. The device name must\n" - "# be given in traditional non-devfs format.\n" - "# For example, to use the first SCSI/SATA hard disk:\n" - "d-i partman-auto/disk string /dev/sda\n" - "# Note: If you want to use whatever disk is available, no matter\n" - "# what its device name, comment the line above out. This will only work if\n" - "# the system only has one disk.\n" - "# In addition, you'll need to specify the method to use.\n" - "# The presently available methods are: \"regular\", \"lvm\" and \"crypto\"\n" - "d-i partman-auto/method string lvm\n" - "\n" - "# If one of the disks that are going to be automatically partitioned\n" - "# contains an old LVM configuration, the user will normally receive a\n" - "# warning. This can be preseeded away...\n" - "d-i partman-lvm/device_remove_lvm boolean true\n" - "# And the same goes for the confirmation to write the lvm partitions.\n" - "d-i partman-lvm/confirm boolean true\n" - "\n" - "# You can choose from any of the predefined partitioning recipes.\n" - "# Note: this must be preseeded with a localized (translated) value.\n" - "d-i partman-auto/choose_recipe \\\n" - " select All files in one partition (recommended for new users)\n" - "#d-i partman-auto/choose_recipe \\\n" - "# select Separate /home partition\n" - "#d-i partman-auto/choose_recipe \\\n" - "# select Separate /home, /usr, /var, and /tmp partitions\n" - "\n" - "# Or provide a recipe of your own...\n" - "# The recipe format is documented in the file devel/partman-auto-recipe.txt.\n" - "# If you have a way to get a recipe file into the d-i environment, you can\n" - "# just point at it.\n" - "#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n" - "\n" - "# If not, you can put an entire recipe into the preconfiguration file in one\n" - "# (logical) line. This example creates a small /boot partition, suitable\n" - "# swap, and uses the rest of the space for the root partition:\n" - "#d-i partman-auto/expert_recipe string \\\n" - "# boot-root :: \\\n" - "# 40 50 100 ext3 \\\n" - "# $primary{ } $bootable{ } \\\n" - "# method{ format } format{ } \\\n" - "# use_filesystem{ } filesystem{ ext3 } \\\n" - "# mountpoint{ /boot } \\\n" - "# . \\\n" - "# 500 10000 1000000000 ext3 \\\n" - "# method{ format } format{ } \\\n" - "# use_filesystem{ } filesystem{ ext3 } \\\n" - "# mountpoint{ / } \\\n" - "# . \\\n" - "# 64 512 300% linux-swap \\\n" - "# method{ swap } format{ } \\\n" - "# .\n" - "\n" - "# This makes partman automatically partition without confirmation, provided\n" - "# that you told it what to do using one of the methods above.\n" - "d-i partman/confirm_write_new_label boolean true\n" - "d-i partman/choose_partition \\\n" - " select Finish partitioning and write changes to disk\n" - "d-i partman/confirm boolean true" +"# If the system has free space you can choose to only partition that space.\n" +"# Note: this must be preseeded with a localized (translated) value.\n" +"#d-i partman-auto/init_automatically_partition \\\n" +"# select Guided - use the largest continuous free space\n" +"\n" +"# Alternatively, you can specify a disk to partition. The device name must\n" +"# be given in traditional non-devfs format.\n" +"# For example, to use the first SCSI/SATA hard disk:\n" +"d-i partman-auto/disk string /dev/sda\n" +"# Note: If you want to use whatever disk is available, no matter\n" +"# what its device name, comment the line above out. This will only work if\n" +"# the system only has one disk.\n" +"# In addition, you'll need to specify the method to use.\n" +"# The presently available methods are: \"regular\", \"lvm\" and \"crypto\"\n" +"d-i partman-auto/method string lvm\n" +"\n" +"# If one of the disks that are going to be automatically partitioned\n" +"# contains an old LVM configuration, the user will normally receive a\n" +"# warning. This can be preseeded away...\n" +"d-i partman-lvm/device_remove_lvm boolean true\n" +"# And the same goes for the confirmation to write the lvm partitions.\n" +"d-i partman-lvm/confirm boolean true\n" +"\n" +"# You can choose from any of the predefined partitioning recipes.\n" +"# Note: this must be preseeded with a localized (translated) value.\n" +"d-i partman-auto/choose_recipe \\\n" +" select All files in one partition (recommended for new users)\n" +"#d-i partman-auto/choose_recipe \\\n" +"# select Separate /home partition\n" +"#d-i partman-auto/choose_recipe \\\n" +"# select Separate /home, /usr, /var, and /tmp partitions\n" +"\n" +"# Or provide a recipe of your own...\n" +"# The recipe format is documented in the file devel/partman-auto-recipe." +"txt.\n" +"# If you have a way to get a recipe file into the d-i environment, you can\n" +"# just point at it.\n" +"#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n" +"\n" +"# If not, you can put an entire recipe into the preconfiguration file in " +"one\n" +"# (logical) line. This example creates a small /boot partition, suitable\n" +"# swap, and uses the rest of the space for the root partition:\n" +"#d-i partman-auto/expert_recipe string \\\n" +"# boot-root :: \\\n" +"# 40 50 100 ext3 \\\n" +"# $primary{ } $bootable{ } \\\n" +"# method{ format } format{ } \\\n" +"# use_filesystem{ } filesystem{ ext3 } \\\n" +"# mountpoint{ /boot } \\\n" +"# . \\\n" +"# 500 10000 1000000000 ext3 \\\n" +"# method{ format } format{ } \\\n" +"# use_filesystem{ } filesystem{ ext3 } \\\n" +"# mountpoint{ / } \\\n" +"# . \\\n" +"# 64 512 300% linux-swap \\\n" +"# method{ swap } format{ } \\\n" +"# .\n" +"\n" +"# This makes partman automatically partition without confirmation, provided\n" +"# that you told it what to do using one of the methods above.\n" +"d-i partman/confirm_write_new_label boolean true\n" +"d-i partman/choose_partition \\\n" +" select Finish partitioning and write changes to disk\n" +"d-i partman/confirm boolean true" msgstr "" #. Tag: title @@ -985,70 +1298,84 @@ msgstr "" #. Tag: para #: preseed.xml:822 #, no-c-format -msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1 and 5, creating degraded arrays and specifying spare devices. If you are using RAID 1, you can preseed grub to install to all devices used in the array; see <xref linkend=\"preseed-bootloader\"/>." +msgid "" +"You can also use preseeding to set up partitions on software RAID arrays. " +"Supported are RAID levels 0, 1 and 5, creating degraded arrays and " +"specifying spare devices. If you are using RAID 1, you can preseed grub to " +"install to all devices used in the array; see <xref linkend=\"preseed-" +"bootloader\"/>." msgstr "" #. Tag: para #: preseed.xml:832 #, no-c-format -msgid "This type of automated partitioning is easy to get wrong. It is also a very new component that may still have some bugs or missing error handling. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check <filename>/var/log/syslog</filename> if you run into problems." +msgid "" +"This type of automated partitioning is easy to get wrong. It is also a very " +"new component that may still have some bugs or missing error handling. The " +"responsibility to get the various recipes right (so they make sense and " +"don't conflict) lies with the user. Check <filename>/var/log/syslog</" +"filename> if you run into problems." msgstr "" #. Tag: para #: preseed.xml:840 #, no-c-format -msgid "Note that only RAID 0 and RAID 1 have been tested by the developers of the component. RAID 5 is untested. Advanced RAID setup with degraded arrays or spare devices has only been tested lightly." +msgid "" +"Note that only RAID 0 and RAID 1 have been tested by the developers of the " +"component. RAID 5 is untested. Advanced RAID setup with degraded arrays or " +"spare devices has only been tested lightly." msgstr "" #. Tag: screen #: preseed.xml:848 #, no-c-format msgid "" - "# NOTE: this option is of beta release quality and should be used carefully\n" - "\n" - "# The method should be set to \"raid\".\n" - "#d-i partman-auto/method string raid\n" - "# Specify the disks to be partitioned. They will all get the same layout,\n" - "# so this will only work if the disks are the same size.\n" - "#d-i partman-auto/disk string /dev/discs/disc0/disc /dev/discs/disc1/disc\n" - "\n" - "# Next you need to specify the physical partitions that will be used. \n" - "#d-i partman-auto/expert_recipe string \\\n" - "# multiraid :: \\\n" - "# 1000 5000 4000 raid \\\n" - "# $primary{ } method{ raid } \\\n" - "# . \\\n" - "# 64 512 300% raid \\\n" - "# method{ raid } \\\n" - "# . \\\n" - "# 500 10000 1000000000 raid \\\n" - "# method{ raid } \\\n" - "# .\n" - "\n" - "# Last you need to specify how the previously defined partitions will be\n" - "# used in the RAID setup. Remember to use the correct partition numbers\n" - "# for logical partitions.\n" - "# Parameters are:\n" - "# <raidtype> <devcount> <sparecount> <fstype> <mountpoint> \\\n" - "# <devices> <sparedevices>\n" - "# RAID levels 0, 1 and 5 are supported; devices are separated using \"#\"\n" - "#d-i partman-auto-raid/recipe string \\\n" - "# 1 2 0 ext3 / \\\n" - "# /dev/discs/disc0/part1#/dev/discs/disc1/part1 \\\n" - "# . \\\n" - "# 1 2 0 swap - \\\n" - "# /dev/discs/disc0/part5#/dev/discs/disc1/part5 \\\n" - "# . \\\n" - "# 0 2 0 ext3 /home \\\n" - "# /dev/discs/disc0/part6#/dev/discs/disc1/part6 \\\n" - "# .\n" - "\n" - "# This makes partman automatically partition without confirmation.\n" - "d-i partman-md/confirm boolean true\n" - "d-i partman/confirm_write_new_label boolean true\n" - "d-i partman/choose_partition \\\n" - " select Finish partitioning and write changes to disk\n" - "d-i partman/confirm boolean true" +"# NOTE: this option is of beta release quality and should be used carefully\n" +"\n" +"# The method should be set to \"raid\".\n" +"#d-i partman-auto/method string raid\n" +"# Specify the disks to be partitioned. They will all get the same layout,\n" +"# so this will only work if the disks are the same size.\n" +"#d-i partman-auto/disk string /dev/discs/disc0/disc /dev/discs/disc1/disc\n" +"\n" +"# Next you need to specify the physical partitions that will be used. \n" +"#d-i partman-auto/expert_recipe string \\\n" +"# multiraid :: \\\n" +"# 1000 5000 4000 raid \\\n" +"# $primary{ } method{ raid } \\\n" +"# . \\\n" +"# 64 512 300% raid \\\n" +"# method{ raid } \\\n" +"# . \\\n" +"# 500 10000 1000000000 raid \\\n" +"# method{ raid } \\\n" +"# .\n" +"\n" +"# Last you need to specify how the previously defined partitions will be\n" +"# used in the RAID setup. Remember to use the correct partition numbers\n" +"# for logical partitions.\n" +"# Parameters are:\n" +"# <raidtype> <devcount> <sparecount> <fstype> <" +"mountpoint> \\\n" +"# <devices> <sparedevices>\n" +"# RAID levels 0, 1 and 5 are supported; devices are separated using \"#\"\n" +"#d-i partman-auto-raid/recipe string \\\n" +"# 1 2 0 ext3 / \\\n" +"# /dev/discs/disc0/part1#/dev/discs/disc1/part1 \\\n" +"# . \\\n" +"# 1 2 0 swap - \\\n" +"# /dev/discs/disc0/part5#/dev/discs/disc1/part5 \\\n" +"# . \\\n" +"# 0 2 0 ext3 /home \\\n" +"# /dev/discs/disc0/part6#/dev/discs/disc1/part6 \\\n" +"# .\n" +"\n" +"# This makes partman automatically partition without confirmation.\n" +"d-i partman-md/confirm boolean true\n" +"d-i partman/confirm_write_new_label boolean true\n" +"d-i partman/choose_partition \\\n" +" select Finish partitioning and write changes to disk\n" +"d-i partman/confirm boolean true" msgstr "" #. Tag: title @@ -1060,19 +1387,24 @@ msgstr "" #. Tag: para #: preseed.xml:854 #, no-c-format -msgid "There is actually not very much that can be preseeded for this stage of the installation. The only questions asked concern the installation of the kernel." +msgid "" +"There is actually not very much that can be preseeded for this stage of the " +"installation. The only questions asked concern the installation of the " +"kernel." msgstr "" #. Tag: screen #: preseed.xml:861 #, no-c-format msgid "" - "# Select the initramfs generator used to generate the initrd for 2.6 kernels.\n" - "#d-i base-installer/kernel/linux/initramfs-generators string yaird\n" - "\n" - "# The kernel image (meta) package to be installed; \"none\" can be used if no\n" - "# kernel is to be installed.\n" - "#d-i base-installer/kernel/image string linux-image-2.6-486" +"# Select the initramfs generator used to generate the initrd for 2.6 " +"kernels.\n" +"#d-i base-installer/kernel/linux/initramfs-generators string yaird\n" +"\n" +"# The kernel image (meta) package to be installed; \"none\" can be used if " +"no\n" +"# kernel is to be installed.\n" +"#d-i base-installer/kernel/image string linux-image-2.6-486" msgstr "" #. Tag: title @@ -1084,57 +1416,73 @@ msgstr "" #. Tag: para #: preseed.xml:867 #, no-c-format -msgid "The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear text values or MD5 <emphasis>hashes</emphasis>." +msgid "" +"The password for the root account and name and password for a first regular " +"user's account can be preseeded. For the passwords you can use either clear " +"text values or MD5 <emphasis>hashes</emphasis>." msgstr "" #. Tag: para #: preseed.xml:874 #, no-c-format -msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these passwords. Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks." +msgid "" +"Be aware that preseeding passwords is not completely secure as everyone with " +"access to the preconfiguration file will have the knowledge of these " +"passwords. Using MD5 hashes is considered slightly better in terms of " +"security but it might also give a false sense of security as access to a MD5 " +"hash allows for brute force attacks." msgstr "" #. Tag: screen #: preseed.xml:884 #, no-c-format msgid "" - "# Skip creation of a root account (normal user account will be able to\n" - "# use sudo).\n" - "#d-i passwd/root-login boolean false\n" - "# Alternatively, to skip creation of a normal user account.\n" - "#d-i passwd/make-user boolean false\n" - "\n" - "# Root password, either in clear text\n" - "#d-i passwd/root-password password r00tme\n" - "#d-i passwd/root-password-again password r00tme\n" - "# or encrypted using an MD5 hash.\n" - "#d-i passwd/root-password-crypted password [MD5 hash]\n" - "\n" - "# To create a normal user account.\n" - "#d-i passwd/user-fullname string Debian User\n" - "#d-i passwd/username string debian\n" - "# Normal user's password, either in clear text\n" - "#d-i passwd/user-password password insecure\n" - "#d-i passwd/user-password-again password insecure\n" - "# or encrypted using an MD5 hash.\n" - "#d-i passwd/user-password-crypted password [MD5 hash]\n" - "# Create the first user with the specified UID instead of the default.\n" - "#d-i passwd/user-uid string 1010\n" - "\n" - "# The user account will be added to some standard initial groups. To\n" - "# override that, use this.\n" - "#d-i passwd/user-default-groups string audio cdrom video" +"# Skip creation of a root account (normal user account will be able to\n" +"# use sudo).\n" +"#d-i passwd/root-login boolean false\n" +"# Alternatively, to skip creation of a normal user account.\n" +"#d-i passwd/make-user boolean false\n" +"\n" +"# Root password, either in clear text\n" +"#d-i passwd/root-password password r00tme\n" +"#d-i passwd/root-password-again password r00tme\n" +"# or encrypted using an MD5 hash.\n" +"#d-i passwd/root-password-crypted password [MD5 hash]\n" +"\n" +"# To create a normal user account.\n" +"#d-i passwd/user-fullname string Debian User\n" +"#d-i passwd/username string debian\n" +"# Normal user's password, either in clear text\n" +"#d-i passwd/user-password password insecure\n" +"#d-i passwd/user-password-again password insecure\n" +"# or encrypted using an MD5 hash.\n" +"#d-i passwd/user-password-crypted password [MD5 hash]\n" +"# Create the first user with the specified UID instead of the default.\n" +"#d-i passwd/user-uid string 1010\n" +"\n" +"# The user account will be added to some standard initial groups. To\n" +"# override that, use this.\n" +"#d-i passwd/user-default-groups string audio cdrom video" msgstr "" #. Tag: para #: preseed.xml:886 #, no-c-format -msgid "The <classname>passwd/root-password-crypted</classname> and <classname>passwd/user-password-crypted</classname> variables can also be preseeded with <quote>!</quote> as their value. In that case, the corresponding account is disabled. This may be convenient for the root account, provided of course that an alternative method is setup to allow administrative activities or root login (for instance by using SSH key authentication or <command>sudo</command>)." +msgid "" +"The <classname>passwd/root-password-crypted</classname> and " +"<classname>passwd/user-password-crypted</classname> variables can also be " +"preseeded with <quote>!</quote> as their value. In that case, the " +"corresponding account is disabled. This may be convenient for the root " +"account, provided of course that an alternative method is setup to allow " +"administrative activities or root login (for instance by using SSH key " +"authentication or <command>sudo</command>)." msgstr "" #. Tag: para #: preseed.xml:896 #, no-c-format -msgid "The following command can be used to generate an MD5 hash for a password:" +msgid "" +"The following command can be used to generate an MD5 hash for a password:" msgstr "" #. Tag: screen @@ -1152,39 +1500,43 @@ msgstr "" #. Tag: para #: preseed.xml:907 #, no-c-format -msgid "Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration options is fully automated based on your installation method and answers to earlier questions. You can optionally add other (local) repositories." +msgid "" +"Setup of the <filename>/etc/apt/sources.list</filename> and basic " +"configuration options is fully automated based on your installation method " +"and answers to earlier questions. You can optionally add other (local) " +"repositories." msgstr "" #. Tag: screen #: preseed.xml:915 #, no-c-format msgid "" - "# You can choose to install non-free and contrib software.\n" - "#d-i apt-setup/non-free boolean true\n" - "#d-i apt-setup/contrib boolean true\n" - "# Uncomment this if you don't want to use a network mirror.\n" - "#d-i apt-setup/use_mirror boolean false\n" - "# Select which update services to use; define the mirrors to be used.\n" - "# Values shown below are the normal defaults.\n" - "#d-i apt-setup/services-select multiselect security, volatile\n" - "#d-i apt-setup/security_host string security.debian.org\n" - "#d-i apt-setup/volatile_host string volatile.debian.org\n" - "\n" - "# Additional repositories, local[0-9] available\n" - "#d-i apt-setup/local0/repository string \\\n" - "# http://local.server/debian stable main\n" - "#d-i apt-setup/local0/comment string local server\n" - "# Enable deb-src lines\n" - "#d-i apt-setup/local0/source boolean true\n" - "# URL to the public key of the local repository; you must provide a key or\n" - "# apt will complain about the unauthenticated repository and so the\n" - "# sources.list line will be left commented out\n" - "#d-i apt-setup/local0/key string http://local.server/key\n" - "\n" - "# By default the installer requires that repositories be authenticated\n" - "# using a known gpg key. This setting can be used to disable that\n" - "# authentication. Warning: Insecure, not recommended.\n" - "#d-i debian-installer/allow_unauthenticated string true" +"# You can choose to install non-free and contrib software.\n" +"#d-i apt-setup/non-free boolean true\n" +"#d-i apt-setup/contrib boolean true\n" +"# Uncomment this if you don't want to use a network mirror.\n" +"#d-i apt-setup/use_mirror boolean false\n" +"# Select which update services to use; define the mirrors to be used.\n" +"# Values shown below are the normal defaults.\n" +"#d-i apt-setup/services-select multiselect security, volatile\n" +"#d-i apt-setup/security_host string security.debian.org\n" +"#d-i apt-setup/volatile_host string volatile.debian.org\n" +"\n" +"# Additional repositories, local[0-9] available\n" +"#d-i apt-setup/local0/repository string \\\n" +"# http://local.server/debian stable main\n" +"#d-i apt-setup/local0/comment string local server\n" +"# Enable deb-src lines\n" +"#d-i apt-setup/local0/source boolean true\n" +"# URL to the public key of the local repository; you must provide a key or\n" +"# apt will complain about the unauthenticated repository and so the\n" +"# sources.list line will be left commented out\n" +"#d-i apt-setup/local0/key string http://local.server/key\n" +"\n" +"# By default the installer requires that repositories be authenticated\n" +"# using a known gpg key. This setting can be used to disable that\n" +"# authentication. Warning: Insecure, not recommended.\n" +"#d-i debian-installer/allow_unauthenticated string true" msgstr "" #. Tag: title @@ -1196,7 +1548,9 @@ msgstr "" #. Tag: para #: preseed.xml:921 #, no-c-format -msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:" +msgid "" +"You can choose to install any combination of tasks that are available. " +"Available tasks as of this writing include:" msgstr "" #. Tag: userinput @@ -1268,32 +1622,40 @@ msgstr "" #. Tag: para #: preseed.xml:964 #, no-c-format -msgid "You can also choose to install no tasks, and force the installation of a set of packages in some other way. We recommend always including the <userinput>standard</userinput> task." +msgid "" +"You can also choose to install no tasks, and force the installation of a set " +"of packages in some other way. We recommend always including the " +"<userinput>standard</userinput> task." msgstr "" #. Tag: para #: preseed.xml:970 #, no-c-format -msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well." +msgid "" +"If you want to install some individual packages in addition to packages " +"installed by tasks, you can use the parameter <classname>pkgsel/include</" +"classname>. The value of this parameter can be a list of packages separated " +"by either commas or spaces, which allows it to be used easily on the kernel " +"command line as well." msgstr "" #. Tag: screen #: preseed.xml:980 #, no-c-format msgid "" - "#tasksel tasksel/first multiselect standard, web-server\n" - "# If the desktop task is selected, install the kde and xfce desktops\n" - "# instead of the default gnome desktop.\n" - "#tasksel tasksel/desktop multiselect kde, xfce\n" - "\n" - "# Individual additional packages to install\n" - "#d-i pkgsel/include string openssh-server build-essential\n" - "\n" - "# Some versions of the installer can report back on what software you have\n" - "# installed, and what software you use. The default is not to report back,\n" - "# but sending reports helps the project determine what software is most\n" - "# popular and include it on CDs.\n" - "#popularity-contest popularity-contest/participate boolean false" +"#tasksel tasksel/first multiselect standard, web-server\n" +"# If the desktop task is selected, install the kde and xfce desktops\n" +"# instead of the default gnome desktop.\n" +"#tasksel tasksel/desktop multiselect kde, xfce\n" +"\n" +"# Individual additional packages to install\n" +"#d-i pkgsel/include string openssh-server build-essential\n" +"\n" +"# Some versions of the installer can report back on what software you have\n" +"# installed, and what software you use. The default is not to report back,\n" +"# but sending reports helps the project determine what software is most\n" +"# popular and include it on CDs.\n" +"#popularity-contest popularity-contest/participate boolean false" msgstr "" #. Tag: title @@ -1306,40 +1668,45 @@ msgstr "" #: preseed.xml:987 #, no-c-format msgid "" - "# Grub is the default boot loader (for x86). If you want lilo installed\n" - "# instead, uncomment this:\n" - "#d-i grub-installer/skip boolean true\n" - "# To also skip installing lilo, and install no bootloader, uncomment this\n" - "# too:\n" - "#d-i lilo-installer/skip boolean true\n" - "\n" - "# This is fairly safe to set, it makes grub install automatically to the MBR\n" - "# if no other operating system is detected on the machine.\n" - "d-i grub-installer/only_debian boolean true\n" - "\n" - "# This one makes grub-installer install to the MBR if it also finds some other\n" - "# OS, which is less safe as it might not be able to boot that other OS.\n" - "d-i grub-installer/with_other_os boolean true\n" - "\n" - "# Alternatively, if you want to install to a location other than the mbr,\n" - "# uncomment and edit these lines:\n" - "#d-i grub-installer/only_debian boolean false\n" - "#d-i grub-installer/with_other_os boolean false\n" - "#d-i grub-installer/bootdev string (hd0,0)\n" - "# To install grub to multiple disks:\n" - "#d-i grub-installer/bootdev string (hd0,0) (hd1,0) (hd2,0)\n" - "\n" - "# Optional password for grub, either in clear text\n" - "#d-i grub-installer/password password r00tme\n" - "#d-i grub-installer/password-again password r00tme\n" - "# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n" - "#d-i grub-installer/password-crypted password [MD5 hash]" +"# Grub is the default boot loader (for x86). If you want lilo installed\n" +"# instead, uncomment this:\n" +"#d-i grub-installer/skip boolean true\n" +"# To also skip installing lilo, and install no bootloader, uncomment this\n" +"# too:\n" +"#d-i lilo-installer/skip boolean true\n" +"\n" +"# This is fairly safe to set, it makes grub install automatically to the " +"MBR\n" +"# if no other operating system is detected on the machine.\n" +"d-i grub-installer/only_debian boolean true\n" +"\n" +"# This one makes grub-installer install to the MBR if it also finds some " +"other\n" +"# OS, which is less safe as it might not be able to boot that other OS.\n" +"d-i grub-installer/with_other_os boolean true\n" +"\n" +"# Alternatively, if you want to install to a location other than the mbr,\n" +"# uncomment and edit these lines:\n" +"#d-i grub-installer/only_debian boolean false\n" +"#d-i grub-installer/with_other_os boolean false\n" +"#d-i grub-installer/bootdev string (hd0,0)\n" +"# To install grub to multiple disks:\n" +"#d-i grub-installer/bootdev string (hd0,0) (hd1,0) (hd2,0)\n" +"\n" +"# Optional password for grub, either in clear text\n" +"#d-i grub-installer/password password r00tme\n" +"#d-i grub-installer/password-again password r00tme\n" +"# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n" +"#d-i grub-installer/password-crypted password [MD5 hash]" msgstr "" #. Tag: para #: preseed.xml:989 #, no-c-format -msgid "An MD5 hash for a password for <classname>grub</classname> can be generated using <command>grub-md5-crypt</command>, or using the command from the example in <xref linkend=\"preseed-account\"/>." +msgid "" +"An MD5 hash for a password for <classname>grub</classname> can be generated " +"using <command>grub-md5-crypt</command>, or using the command from the " +"example in <xref linkend=\"preseed-account\"/>." msgstr "" #. Tag: title @@ -1352,16 +1719,21 @@ msgstr "" #: preseed.xml:1001 #, no-c-format msgid "" - "# Avoid that last message about the install being complete.\n" - "d-i finish-install/reboot_in_progress note\n" - "\n" - "# This will prevent the installer from ejecting the CD during the reboot,\n" - "# which is useful in some situations.\n" - "#d-i cdrom-detect/eject boolean false\n" - "\n" - "# This is how to make the installer shutdown when finished, but not\n" - "# reboot into the installed system.\n" - "#d-i debian-installer/exit/halt boolean true" +"# During installations from serial console, the regular virtual consoles\n" +"# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n" +"# line to prevent this.\n" +"#d-i finish-install/keep-consoles boolean true\n" +"\n" +"# Avoid that last message about the install being complete.\n" +"d-i finish-install/reboot_in_progress note\n" +"\n" +"# This will prevent the installer from ejecting the CD during the reboot,\n" +"# which is useful in some situations.\n" +"#d-i cdrom-detect/eject boolean false\n" +"\n" +"# This is how to make the installer shutdown when finished, but not\n" +"# reboot into the installed system.\n" +"#d-i debian-installer/exit/halt boolean true" msgstr "" #. Tag: title @@ -1373,33 +1745,37 @@ msgstr "" #. Tag: para #: preseed.xml:1007 #, no-c-format -msgid "Preseeding Debian's X config is possible, but you probably need to know some details about the video hardware of the machine, since Debian's X configurator does not do fully automatic configuration of everything." +msgid "" +"Preseeding Debian's X config is possible, but you probably need to know some " +"details about the video hardware of the machine, since Debian's X " +"configurator does not do fully automatic configuration of everything." msgstr "" #. Tag: screen #: preseed.xml:1015 #, no-c-format msgid "" - "# X can detect the right driver for some cards, but if you're preseeding,\n" - "# you override whatever it chooses. Still, vesa will work most places.\n" - "#xserver-xorg xserver-xorg/config/device/driver select vesa\n" - "\n" - "# A caveat with mouse autodetection is that if it fails, X will retry it\n" - "# over and over. So if it's preseeded to be done, there is a possibility of\n" - "# an infinite loop if the mouse is not autodetected.\n" - "#xserver-xorg xserver-xorg/autodetect_mouse boolean true\n" - "\n" - "# Monitor autodetection is recommended.\n" - "xserver-xorg xserver-xorg/autodetect_monitor boolean true\n" - "# Uncomment if you have an LCD display.\n" - "#xserver-xorg xserver-xorg/config/monitor/lcd boolean true\n" - "# X has three configuration paths for the monitor. Here's how to preseed\n" - "# the \"medium\" path, which is always available. The \"simple\" path may not\n" - "# be available, and the \"advanced\" path asks too many questions.\n" - "xserver-xorg xserver-xorg/config/monitor/selection-method \\\n" - " select medium\n" - "xserver-xorg xserver-xorg/config/monitor/mode-list \\\n" - " select 1024x768 @ 60 Hz" +"# X can detect the right driver for some cards, but if you're preseeding,\n" +"# you override whatever it chooses. Still, vesa will work most places.\n" +"#xserver-xorg xserver-xorg/config/device/driver select vesa\n" +"\n" +"# A caveat with mouse autodetection is that if it fails, X will retry it\n" +"# over and over. So if it's preseeded to be done, there is a possibility of\n" +"# an infinite loop if the mouse is not autodetected.\n" +"#xserver-xorg xserver-xorg/autodetect_mouse boolean true\n" +"\n" +"# Monitor autodetection is recommended.\n" +"xserver-xorg xserver-xorg/autodetect_monitor boolean true\n" +"# Uncomment if you have an LCD display.\n" +"#xserver-xorg xserver-xorg/config/monitor/lcd boolean true\n" +"# X has three configuration paths for the monitor. Here's how to preseed\n" +"# the \"medium\" path, which is always available. The \"simple\" path may " +"not\n" +"# be available, and the \"advanced\" path asks too many questions.\n" +"xserver-xorg xserver-xorg/config/monitor/selection-method \\\n" +" select medium\n" +"xserver-xorg xserver-xorg/config/monitor/mode-list \\\n" +" select 1024x768 @ 60 Hz" msgstr "" #. Tag: title @@ -1412,13 +1788,13 @@ msgstr "" #: preseed.xml:1022 #, no-c-format msgid "" - "# Depending on what software you choose to install, or if things go wrong\n" - "# during the installation process, it's possible that other questions may\n" - "# be asked. You can preseed those too, of course. To get a list of every\n" - "# possible question that could be asked during an install, do an\n" - "# installation, and then run these commands:\n" - "# debconf-get-selections --installer > file\n" - "# debconf-get-selections >> file" +"# Depending on what software you choose to install, or if things go wrong\n" +"# during the installation process, it's possible that other questions may\n" +"# be asked. You can preseed those too, of course. To get a list of every\n" +"# possible question that could be asked during an install, do an\n" +"# installation, and then run these commands:\n" +"# debconf-get-selections --installer > file\n" +"# debconf-get-selections >> file" msgstr "" #. Tag: title @@ -1436,29 +1812,31 @@ msgstr "" #. Tag: para #: preseed.xml:1033 #, no-c-format -msgid "A very powerful and flexible option offered by the preconfiguration tools is the ability to run commands or scripts at certain points in the installation." +msgid "" +"A very powerful and flexible option offered by the preconfiguration tools is " +"the ability to run commands or scripts at certain points in the installation." msgstr "" #. Tag: screen #: preseed.xml:1041 #, no-c-format msgid "" - "# d-i preseeding is inherently not secure. Nothing in the installer checks\n" - "# for attempts at buffer overflows or other exploits of the values of a\n" - "# preconfiguration file like this one. Only use preconfiguration files from\n" - "# trusted locations! To drive that home, and because it's generally useful,\n" - "# here's a way to run any shell command you'd like inside the installer,\n" - "# automatically.\n" - "\n" - "# This first command is run as early as possible, just after\n" - "# preseeding is read.\n" - "#d-i preseed/early_command string anna-install some-udeb\n" - "\n" - "# This command is run just before the install finishes, but when there is\n" - "# still a usable /target directory. You can chroot to /target and use it\n" - "# directly, or use the apt-install and in-target commands to easily install\n" - "# packages and run commands in the target system.\n" - "#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh" +"# d-i preseeding is inherently not secure. Nothing in the installer checks\n" +"# for attempts at buffer overflows or other exploits of the values of a\n" +"# preconfiguration file like this one. Only use preconfiguration files from\n" +"# trusted locations! To drive that home, and because it's generally useful,\n" +"# here's a way to run any shell command you'd like inside the installer,\n" +"# automatically.\n" +"\n" +"# This first command is run as early as possible, just after\n" +"# preseeding is read.\n" +"#d-i preseed/early_command string anna-install some-udeb\n" +"\n" +"# This command is run just before the install finishes, but when there is\n" +"# still a usable /target directory. You can chroot to /target and use it\n" +"# directly, or use the apt-install and in-target commands to easily install\n" +"# packages and run commands in the target system.\n" +"#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh" msgstr "" #. Tag: title @@ -1471,16 +1849,29 @@ msgstr "" #: preseed.xml:1047 #, no-c-format msgid "" - "It is possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a question. <informalexample><screen>\n" - "d-i foo/bar string value\n" - "d-i foo/bar seen false\n" - "</screen></informalexample> The same effect can be achieved for <emphasis>all</emphasis> questions by setting the parameter <classname>preseed/interactive=true</classname> at the boot prompt. This can also be useful for testing or debugging your preconfiguration file." +"It is possible to use preseeding to change the default answer for a " +"question, but still have the question asked. To do this the <firstterm>seen</" +"firstterm> flag must be reset to <quote>false</quote> after setting the " +"value for a question. <informalexample><screen>\n" +"d-i foo/bar string value\n" +"d-i foo/bar seen false\n" +"</screen></informalexample> The same effect can be achieved for " +"<emphasis>all</emphasis> questions by setting the parameter " +"<classname>preseed/interactive=true</classname> at the boot prompt. This can " +"also be useful for testing or debugging your preconfiguration file." msgstr "" #. Tag: para #: preseed.xml:1061 #, no-c-format -msgid "If you are preseeding using boot parameters, you can make the installer ask the corresponding question by using the <quote>?=</quote> operator, i.e. <userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?=<replaceable>value</replaceable></userinput>. This will of course only have effect for parameters that correspond to questions that are actually displayed during an installation and not for <quote>internal</quote> parameters." +msgid "" +"If you are preseeding using boot parameters, you can make the installer ask " +"the corresponding question by using the <quote>?=</quote> operator, i.e. " +"<userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?" +"=<replaceable>value</replaceable></userinput>. This will of course only have " +"effect for parameters that correspond to questions that are actually " +"displayed during an installation and not for <quote>internal</quote> " +"parameters." msgstr "" #. Tag: title @@ -1492,40 +1883,50 @@ msgstr "" #. Tag: para #: preseed.xml:1077 #, no-c-format -msgid "It is possible to include other preconfiguration files from a preconfiguration file. Any settings in those files will override pre-existing settings from files loaded earlier. This makes it possible to put, for example, general networking settings for your location in one file and more specific settings for certain configurations in other files." +msgid "" +"It is possible to include other preconfiguration files from a " +"preconfiguration file. Any settings in those files will override pre-" +"existing settings from files loaded earlier. This makes it possible to put, " +"for example, general networking settings for your location in one file and " +"more specific settings for certain configurations in other files." msgstr "" #. Tag: screen #: preseed.xml:1087 #, no-c-format msgid "" - "# More than one file can be listed, separated by spaces; all will be\n" - "# loaded. The included files can have preseed/include directives of their\n" - "# own as well. Note that if the filenames are relative, they are taken from\n" - "# the same directory as the preconfiguration file that includes them.\n" - "#d-i preseed/include string x.cfg\n" - "\n" - "# The installer can optionally verify checksums of preconfiguration files\n" - "# before using them. Currently only md5sums are supported, list the md5sums\n" - "# in the same order as the list of files to include.\n" - "#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n" - "\n" - "# More flexibly, this runs a shell command and if it outputs the names of\n" - "# preconfiguration files, includes those files. \n" - "#d-i preseed/include_command \\\n" - "# string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n" - "\n" - "# Most flexibly of all, this downloads a program and runs it. The program\n" - "# can use commands such as debconf-set to manipulate the debconf database.\n" - "# More than one script can be listed, separated by spaces.\n" - "# Note that if the filenames are relative, they are taken from the same\n" - "# directory as the preconfiguration file that runs them.\n" - "#d-i preseed/run string foo.sh" +"# More than one file can be listed, separated by spaces; all will be\n" +"# loaded. The included files can have preseed/include directives of their\n" +"# own as well. Note that if the filenames are relative, they are taken from\n" +"# the same directory as the preconfiguration file that includes them.\n" +"#d-i preseed/include string x.cfg\n" +"\n" +"# The installer can optionally verify checksums of preconfiguration files\n" +"# before using them. Currently only md5sums are supported, list the md5sums\n" +"# in the same order as the list of files to include.\n" +"#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n" +"\n" +"# More flexibly, this runs a shell command and if it outputs the names of\n" +"# preconfiguration files, includes those files. \n" +"#d-i preseed/include_command \\\n" +"# string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n" +"\n" +"# Most flexibly of all, this downloads a program and runs it. The program\n" +"# can use commands such as debconf-set to manipulate the debconf database.\n" +"# More than one script can be listed, separated by spaces.\n" +"# Note that if the filenames are relative, they are taken from the same\n" +"# directory as the preconfiguration file that runs them.\n" +"#d-i preseed/run string foo.sh" msgstr "" #. Tag: para #: preseed.xml:1089 #, no-c-format -msgid "It is also possible to chainload from the initrd or file preseeding phase, into network preseeding by setting preseed/url in the earlier files. This will cause network preseeding to be performed when the network comes up. You need to be careful when doing this, since there will be two distinct runs at preseeding, meaning for example that you get another chance to run the preseed/early command, the second one happening after the network comes up." +msgid "" +"It is also possible to chainload from the initrd or file preseeding phase, " +"into network preseeding by setting preseed/url in the earlier files. This " +"will cause network preseeding to be performed when the network comes up. You " +"need to be careful when doing this, since there will be two distinct runs at " +"preseeding, meaning for example that you get another chance to run the " +"preseed/early command, the second one happening after the network comes up." msgstr "" - diff --git a/po/nn/random-bits.po b/po/nn/random-bits.po index 9a6db4a57..53a86bbb1 100644 --- a/po/nn/random-bits.po +++ b/po/nn/random-bits.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2008-05-02 00:09+0000\n" +"POT-Creation-Date: 2008-05-11 10:00+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" @@ -29,7 +29,14 @@ msgstr "" #. Tag: para #: random-bits.xml:12 #, no-c-format -msgid "In Linux various special files can be found under the directory <filename>/dev</filename>. These files are called device files and behave unlike ordinary files. The most common types of device files are for block devices and character devices. These files are an interface to the actual driver (part of the Linux kernel) which in turn accesses the hardware. Another, less common, type of device file is the named <firstterm>pipe</firstterm>. The most important device files are listed in the tables below." +msgid "" +"In Linux various special files can be found under the directory <filename>/" +"dev</filename>. These files are called device files and behave unlike " +"ordinary files. The most common types of device files are for block devices " +"and character devices. These files are an interface to the actual driver " +"(part of the Linux kernel) which in turn accesses the hardware. Another, " +"less common, type of device file is the named <firstterm>pipe</firstterm>. " +"The most important device files are listed in the tables below." msgstr "" #. Tag: filename @@ -317,33 +324,62 @@ msgstr "" #. Tag: para #: random-bits.xml:126 #, no-c-format -msgid "The mouse can be used in both the Linux console (with gpm) and the X window environment. Normally, this is a simple matter of installing <filename>gpm</filename> and the X server itself. Both should be configured to use <filename>/dev/input/mice</filename> as the mouse device. The correct mouse protocol is named <userinput>exps2</userinput> in gpm, and <userinput>ExplorerPS/2</userinput> in X. The respective configuration files are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</filename>." +msgid "" +"The mouse can be used in both the Linux console (with gpm) and the X window " +"environment. Normally, this is a simple matter of installing <filename>gpm</" +"filename> and the X server itself. Both should be configured to use " +"<filename>/dev/input/mice</filename> as the mouse device. The correct mouse " +"protocol is named <userinput>exps2</userinput> in gpm, and " +"<userinput>ExplorerPS/2</userinput> in X. The respective configuration files " +"are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</" +"filename>." msgstr "" #. Tag: para #: random-bits.xml:137 #, no-c-format -msgid "Certain kernel modules must be loaded in order for your mouse to work. In most cases the correct modules are autodetected, but not always for old-style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole D-shaped connector; bus mice have an 8-pin round connector, not to be confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round connector of an ADB mouse. </para> </footnote>, which are quite rare except on very old computers. Summary of Linux kernel modules needed for different mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</entry> <entry>Description</entry> </row> </thead><tbody> <row> <entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> </row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></informaltable> To load a mouse driver module, you can use the <command>modconf</command> command (from the package with the same name) and look in the category <userinput>kernel/drivers/input/mouse</userinput>." +msgid "" +"Certain kernel modules must be loaded in order for your mouse to work. In " +"most cases the correct modules are autodetected, but not always for old-" +"style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole " +"D-shaped connector; bus mice have an 8-pin round connector, not to be " +"confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round " +"connector of an ADB mouse. </para> </footnote>, which are quite rare except " +"on very old computers. Summary of Linux kernel modules needed for different " +"mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</" +"entry> <entry>Description</entry> </row> </thead><tbody> <row> " +"<entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </" +"row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</" +"entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> " +"</row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech " +"adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse " +"connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></" +"informaltable> To load a mouse driver module, you can use the " +"<command>modconf</command> command (from the package with the same name) and " +"look in the category <userinput>kernel/drivers/input/mouse</userinput>." msgstr "" #. Tag: para #: random-bits.xml:184 #, no-c-format -msgid "Modern kernels give you the capability to emulate a three-button mouse when your mouse only has one button. Just add the following lines to <filename>/etc/sysctl.conf</filename> file." +msgid "" +"Modern kernels give you the capability to emulate a three-button mouse when " +"your mouse only has one button. Just add the following lines to <filename>/" +"etc/sysctl.conf</filename> file." msgstr "" #. Tag: screen #: random-bits.xml:191 #, no-c-format msgid "" - "# 3-button mouse emulation\n" - "# turn on emulation\n" - "/dev/mac_hid/mouse_button_emulation = 1\n" - "# Send middle mouse button signal with the F11 key\n" - "/dev/mac_hid/mouse_button2_keycode = 87\n" - "# Send right mouse button signal with the F12 key\n" - "/dev/mac_hid/mouse_button3_keycode = 88\n" - "# For different keys, use showkey to tell you what the code is." +"# 3-button mouse emulation\n" +"# turn on emulation\n" +"/dev/mac_hid/mouse_button_emulation = 1\n" +"# Send middle mouse button signal with the F11 key\n" +"/dev/mac_hid/mouse_button2_keycode = 87\n" +"# Send right mouse button signal with the F12 key\n" +"/dev/mac_hid/mouse_button3_keycode = 88\n" +"# For different keys, use showkey to tell you what the code is." msgstr "" #. Tag: title @@ -355,25 +391,44 @@ msgstr "" #. Tag: para #: random-bits.xml:199 #, no-c-format -msgid "A standard installation for the i386 architecture, including all standard packages and using the default 2.6 kernel, takes up &std-system-size;MB of disk space. A minimal base installation, without the <quote>Standard system</quote> task selected, will take &base-system-size;MB." +msgid "" +"A standard installation for the i386 architecture, including all standard " +"packages and using the default 2.6 kernel, takes up &std-system-size;MB of " +"disk space. A minimal base installation, without the <quote>Standard system</" +"quote> task selected, will take &base-system-size;MB." msgstr "" #. Tag: para #: random-bits.xml:207 #, no-c-format -msgid "In both cases this is the actual disk space used <emphasis>after</emphasis> the installation is finished and any temporary files deleted. It also does not take into account overhead used by the file system, for example for journal files. This means that significantly more disk space is needed both <emphasis>during</emphasis> the installation and for normal system use." +msgid "" +"In both cases this is the actual disk space used <emphasis>after</emphasis> " +"the installation is finished and any temporary files deleted. It also does " +"not take into account overhead used by the file system, for example for " +"journal files. This means that significantly more disk space is needed both " +"<emphasis>during</emphasis> the installation and for normal system use." msgstr "" #. Tag: para #: random-bits.xml:216 #, no-c-format -msgid "The following table lists sizes reported by aptitude for the tasks listed in tasksel. Note that some tasks have overlapping constituents, so the total installed size for two tasks together may be less than the total obtained by adding up the numbers." +msgid "" +"The following table lists sizes reported by aptitude for the tasks listed in " +"tasksel. Note that some tasks have overlapping constituents, so the total " +"installed size for two tasks together may be less than the total obtained by " +"adding up the numbers." msgstr "" #. Tag: para #: random-bits.xml:223 #, no-c-format -msgid "Note that you will need to add the sizes listed in the table to the size of the standard installation when determining the size of partitions. Most of the size listed as <quote>Installed size</quote> will end up in <filename>/usr</filename> and in <filename>/lib</filename>; the size listed as <quote>Download size</quote> is (temporarily) required in <filename>/var</filename>." +msgid "" +"Note that you will need to add the sizes listed in the table to the size of " +"the standard installation when determining the size of partitions. Most of " +"the size listed as <quote>Installed size</quote> will end up in <filename>/" +"usr</filename> and in <filename>/lib</filename>; the size listed as " +"<quote>Download size</quote> is (temporarily) required in <filename>/var</" +"filename>." msgstr "" #. Tag: entry @@ -433,7 +488,10 @@ msgstr "" #. Tag: para #: random-bits.xml:255 #, no-c-format -msgid "There is some overlap of the Laptop task with the Desktop environment task. If you install both, the Laptop task will only require a few MB additional disk space." +msgid "" +"There is some overlap of the Laptop task with the Desktop environment task. " +"If you install both, the Laptop task will only require a few MB additional " +"disk space." msgstr "" #. Tag: entry @@ -601,13 +659,19 @@ msgstr "" #. Tag: para #: random-bits.xml:312 #, no-c-format -msgid "The <emphasis>Desktop</emphasis> task will install the GNOME desktop environment." +msgid "" +"The <emphasis>Desktop</emphasis> task will install the GNOME desktop " +"environment." msgstr "" #. Tag: para #: random-bits.xml:319 #, no-c-format -msgid "If you install in a language other than English, <command>tasksel</command> may automatically install a <firstterm>localization task</firstterm>, if one is available for your language. Space requirements differ per language; you should allow up to 350MB in total for download and installation." +msgid "" +"If you install in a language other than English, <command>tasksel</command> " +"may automatically install a <firstterm>localization task</firstterm>, if one " +"is available for your language. Space requirements differ per language; you " +"should allow up to 350MB in total for download and installation." msgstr "" #. Tag: title @@ -619,19 +683,40 @@ msgstr "" #. Tag: para #: random-bits.xml:336 #, no-c-format -msgid "This section explains how to install &debian; from an existing Unix or Linux system, without using the menu-driven installer as explained in the rest of the manual. This <quote>cross-install</quote> HOWTO has been requested by users switching to &debian; from Red Hat, Mandrake, and SUSE. In this section some familiarity with entering *nix commands and navigating the file system is assumed. In this section, <prompt>$</prompt> symbolizes a command to be entered in the user's current system, while <prompt>#</prompt> refers to a command entered in the Debian chroot." +msgid "" +"This section explains how to install &debian; from an existing Unix or Linux " +"system, without using the menu-driven installer as explained in the rest of " +"the manual. This <quote>cross-install</quote> HOWTO has been requested by " +"users switching to &debian; from Red Hat, Mandrake, and SUSE. In this " +"section some familiarity with entering *nix commands and navigating the file " +"system is assumed. In this section, <prompt>$</prompt> symbolizes a command " +"to be entered in the user's current system, while <prompt>#</prompt> refers " +"to a command entered in the Debian chroot." msgstr "" #. Tag: para #: random-bits.xml:348 #, no-c-format -msgid "Once you've got the new Debian system configured to your preference, you can migrate your existing user data (if any) to it, and keep on rolling. This is therefore a <quote>zero downtime</quote> &debian; install. It's also a clever way for dealing with hardware that otherwise doesn't play friendly with various boot or installation media." +msgid "" +"Once you've got the new Debian system configured to your preference, you can " +"migrate your existing user data (if any) to it, and keep on rolling. This is " +"therefore a <quote>zero downtime</quote> &debian; install. It's also a " +"clever way for dealing with hardware that otherwise doesn't play friendly " +"with various boot or installation media." msgstr "" #. Tag: para #: random-bits.xml:359 #, no-c-format -msgid "As this is a mostly manual procedure, you should bear in mind that you will need to do a lot of basic configuration of the system yourself, which will also require more knowledge of Debian and of Linux in general than performing a regular installation. You cannot expect this procedure to result in a system that is identical to a system from a regular installation. You should also keep in mind that this procedure only gives the basic steps to set up a system. Additional installation and/or configuration steps may be needed." +msgid "" +"As this is a mostly manual procedure, you should bear in mind that you will " +"need to do a lot of basic configuration of the system yourself, which will " +"also require more knowledge of Debian and of Linux in general than " +"performing a regular installation. You cannot expect this procedure to " +"result in a system that is identical to a system from a regular " +"installation. You should also keep in mind that this procedure only gives " +"the basic steps to set up a system. Additional installation and/or " +"configuration steps may be needed." msgstr "" #. Tag: title @@ -643,41 +728,56 @@ msgstr "" #. Tag: para #: random-bits.xml:374 #, no-c-format -msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need around 350MB of space available for a console only install, or about 1GB if you plan to install X (more if you intend to install desktop environments like GNOME or KDE)." +msgid "" +"With your current *nix partitioning tools, repartition the hard drive as " +"needed, creating at least one filesystem plus swap. You need around 350MB of " +"space available for a console only install, or about 1GB if you plan to " +"install X (more if you intend to install desktop environments like GNOME or " +"KDE)." msgstr "" #. Tag: para #: random-bits.xml:382 #, no-c-format msgid "" - "Next, create file systems on the partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n" - "# mke2fs -j /dev/<replaceable>hda6</replaceable>\n" - "</screen></informalexample> To create an ext2 file system instead, omit <userinput>-j</userinput>." +"Next, create file systems on the partitions. For example, to create an ext3 " +"file system on partition <filename>/dev/hda6</filename> (that's our example " +"root partition): <informalexample><screen>\n" +"# mke2fs -j /dev/<replaceable>hda6</replaceable>\n" +"</screen></informalexample> To create an ext2 file system instead, omit " +"<userinput>-j</userinput>." msgstr "" #. Tag: para #: random-bits.xml:392 #, no-c-format msgid "" - "Initialize and activate swap (substitute the partition number for your intended Debian swap partition): <informalexample><screen>\n" - "# mkswap /dev/<replaceable>hda5</replaceable>\n" - "# sync; sync; sync\n" - "# swapon /dev/<replaceable>hda5</replaceable>\n" - "</screen></informalexample> Mount one partition as <filename>/mnt/debinst</filename> (the installation point, to be the root (<filename>/</filename>) filesystem on your new system). The mount point name is strictly arbitrary, it is referenced later below." +"Initialize and activate swap (substitute the partition number for your " +"intended Debian swap partition): <informalexample><screen>\n" +"# mkswap /dev/<replaceable>hda5</replaceable>\n" +"# sync; sync; sync\n" +"# swapon /dev/<replaceable>hda5</replaceable>\n" +"</screen></informalexample> Mount one partition as <filename>/mnt/debinst</" +"filename> (the installation point, to be the root (<filename>/</filename>) " +"filesystem on your new system). The mount point name is strictly arbitrary, " +"it is referenced later below." msgstr "" #. Tag: screen #: random-bits.xml:404 #, no-c-format msgid "" - "# mkdir /mnt/debinst\n" - "# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst" +"# mkdir /mnt/debinst\n" +"# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst" msgstr "" #. Tag: para #: random-bits.xml:407 #, no-c-format -msgid "If you want to have parts of the filesystem (e.g. /usr) mounted on separate partitions, you will need to create and mount these directories manually before proceding with the next stage." +msgid "" +"If you want to have parts of the filesystem (e.g. /usr) mounted on separate " +"partitions, you will need to create and mount these directories manually " +"before proceding with the next stage." msgstr "" #. Tag: title @@ -689,26 +789,41 @@ msgstr "" #. Tag: para #: random-bits.xml:418 #, no-c-format -msgid "The utility used by the Debian installer, and recognized as the official way to install a Debian base system, is <command>debootstrap</command>. It uses <command>wget</command> and <command>ar</command>, but otherwise depends only on <classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> <para> These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>. </para> </footnote>. Install <command>wget</command> and <command>ar</command> if they aren't already on your current system, then download and install <command>debootstrap</command>." +msgid "" +"The utility used by the Debian installer, and recognized as the official way " +"to install a Debian base system, is <command>debootstrap</command>. It uses " +"<command>wget</command> and <command>ar</command>, but otherwise depends " +"only on <classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> " +"<para> These include the GNU core utilities and commands like <command>sed</" +"command>, <command>grep</command>, <command>tar</command> and <command>gzip</" +"command>. </para> </footnote>. Install <command>wget</command> and " +"<command>ar</command> if they aren't already on your current system, then " +"download and install <command>debootstrap</command>." msgstr "" #. Tag: para #: random-bits.xml:448 #, no-c-format msgid "" - "Or, you can use the following procedure to install it manually. Make a work folder for extracting the .deb into: <informalexample><screen>\n" - "# mkdir work\n" - "# cd work\n" - "</screen></informalexample> The <command>debootstrap</command> binary is located in the Debian archive (be sure to select the proper file for your architecture). Download the <command>debootstrap</command> .deb from the <ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</ulink>, copy the package to the work folder, and extract the files from it. You will need to have root privileges to install the files." +"Or, you can use the following procedure to install it manually. Make a work " +"folder for extracting the .deb into: <informalexample><screen>\n" +"# mkdir work\n" +"# cd work\n" +"</screen></informalexample> The <command>debootstrap</command> binary is " +"located in the Debian archive (be sure to select the proper file for your " +"architecture). Download the <command>debootstrap</command> .deb from the " +"<ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</" +"ulink>, copy the package to the work folder, and extract the files from it. " +"You will need to have root privileges to install the files." msgstr "" #. Tag: screen #: random-bits.xml:463 #, no-c-format msgid "" - "# ar -x debootstrap_0.X.X_all.deb\n" - "# cd /\n" - "# zcat /full-path-to-work/work/data.tar.gz | tar xv" +"# ar -x debootstrap_0.X.X_all.deb\n" +"# cd /\n" +"# zcat /full-path-to-work/work/data.tar.gz | tar xv" msgstr "" #. Tag: title @@ -720,27 +835,42 @@ msgstr "" #. Tag: para #: random-bits.xml:470 #, no-c-format -msgid "<command>debootstrap</command> can download the needed files directly from the archive when you run it. You can substitute any Debian archive mirror for <userinput>&archive-mirror;/debian</userinput> in the command example below, preferably a mirror close to you network-wise. Mirrors are listed at <ulink url=\"http://www.debian.org/misc/README.mirrors\"></ulink>." +msgid "" +"<command>debootstrap</command> can download the needed files directly from " +"the archive when you run it. You can substitute any Debian archive mirror " +"for <userinput>&archive-mirror;/debian</userinput> in the command example " +"below, preferably a mirror close to you network-wise. Mirrors are listed at " +"<ulink url=\"http://www.debian.org/misc/README.mirrors\"></ulink>." msgstr "" #. Tag: para #: random-bits.xml:479 #, no-c-format -msgid "If you have a &releasename; &debian; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>" +msgid "" +"If you have a &releasename; &debian; CD mounted at <filename>/cdrom</" +"filename>, you could substitute a file URL instead of the http URL: " +"<userinput>file:/cdrom/debian/</userinput>" msgstr "" #. Tag: para #: random-bits.xml:485 #, no-c-format -msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>alpha</userinput>, <userinput>amd64</userinput>, <userinput>arm</userinput>, <userinput>hppa</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>m68k</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, or <userinput>sparc</userinput>." +msgid "" +"Substitute one of the following for <replaceable>ARCH</replaceable> in the " +"<command>debootstrap</command> command: <userinput>alpha</userinput>, " +"<userinput>amd64</userinput>, <userinput>arm</userinput>, <userinput>hppa</" +"userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, " +"<userinput>m68k</userinput>, <userinput>mips</userinput>, <userinput>mipsel</" +"userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, or " +"<userinput>sparc</userinput>." msgstr "" #. Tag: screen #: random-bits.xml:503 #, no-c-format msgid "" - "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n" - " /mnt/debinst http://ftp.us.debian.org/debian" +"# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n" +" /mnt/debinst http://ftp.us.debian.org/debian" msgstr "" #. Tag: title @@ -753,9 +883,11 @@ msgstr "" #: random-bits.xml:510 #, no-c-format msgid "" - "Now you've got a real Debian system, though rather lean, on disk. <command>chroot</command> into it: <informalexample><screen>\n" - "# LANG=C chroot /mnt/debinst /bin/bash\n" - "</screen></informalexample> After chrooting you may need to set the terminal definition to be compatible with the Debian base system, for example:" +"Now you've got a real Debian system, though rather lean, on disk. " +"<command>chroot</command> into it: <informalexample><screen>\n" +"# LANG=C chroot /mnt/debinst /bin/bash\n" +"</screen></informalexample> After chrooting you may need to set the terminal " +"definition to be compatible with the Debian base system, for example:" msgstr "" #. Tag: screen @@ -773,7 +905,14 @@ msgstr "" #. Tag: para #: random-bits.xml:526 #, no-c-format -msgid "At this point <filename>/dev/</filename> only contains very basic device files. For the next steps of the installation additional device files may be needed. There are different ways to go about this and which method you should use depends on the host system you are using for the installation, on whether you intend to use a modular kernel or not, and on whether you intend to use dynamic (e.g. using <classname>udev</classname>) or static device files for the new system." +msgid "" +"At this point <filename>/dev/</filename> only contains very basic device " +"files. For the next steps of the installation additional device files may be " +"needed. There are different ways to go about this and which method you " +"should use depends on the host system you are using for the installation, on " +"whether you intend to use a modular kernel or not, and on whether you intend " +"to use dynamic (e.g. using <classname>udev</classname>) or static device " +"files for the new system." msgstr "" #. Tag: para @@ -792,20 +931,24 @@ msgstr "" #: random-bits.xml:544 #, no-c-format msgid "" - "# cd /dev\n" - "# MAKEDEV generic" +"# cd /dev\n" +"# MAKEDEV generic" msgstr "" #. Tag: para #: random-bits.xml:547 #, no-c-format -msgid "manually create only specific device files using <command>MAKEDEV</command>" +msgid "" +"manually create only specific device files using <command>MAKEDEV</command>" msgstr "" #. Tag: para #: random-bits.xml:552 #, no-c-format -msgid "bind mount /dev from your host system on top of /dev in the target system; note that the postinst scripts of some packages may try to create device files, so this option should only be used with care" +msgid "" +"bind mount /dev from your host system on top of /dev in the target system; " +"note that the postinst scripts of some packages may try to create device " +"files, so this option should only be used with care" msgstr "" #. Tag: title @@ -818,34 +961,44 @@ msgstr "" #: random-bits.xml:566 #, no-c-format msgid "" - "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n" - "# editor /etc/fstab\n" - "</screen></informalexample> Here is a sample you can modify to suit: <informalexample><screen>\n" - "# /etc/fstab: static file system information.\n" - "#\n" - "# file system mount point type options dump pass\n" - "/dev/XXX / ext3 defaults 0 1\n" - "/dev/XXX /boot ext3 ro,nosuid,nodev 0 2\n" - "\n" - "/dev/XXX none swap sw 0 0\n" - "proc /proc proc defaults 0 0\n" - "\n" - "/dev/fd0 /media/floppy auto noauto,rw,sync,user,exec 0 0\n" - "/dev/cdrom /media/cdrom iso9660 noauto,ro,user,exec 0 0\n" - "\n" - "/dev/XXX /tmp ext3 rw,nosuid,nodev 0 2\n" - "/dev/XXX /var ext3 rw,nosuid,nodev 0 2\n" - "/dev/XXX /usr ext3 rw,nodev 0 2\n" - "/dev/XXX /home ext3 rw,nosuid,nodev 0 2\n" - "</screen></informalexample> Use <userinput>mount -a</userinput> to mount all the file systems you have specified in your <filename>/etc/fstab</filename>, or, to mount file systems individually, use: <informalexample><screen>\n" - "# mount /path # e.g.: mount /usr\n" - "</screen></informalexample> Current Debian systems have mountpoints for removable media under <filename>/media</filename>, but keep compatibility symlinks in <filename>/</filename>. Create these as as needed, for example: <informalexample><screen>\n" - "# cd /media\n" - "# mkdir cdrom0\n" - "# ln -s cdrom0 cdrom\n" - "# cd /\n" - "# ln -s media/cdrom\n" - "</screen></informalexample> You can mount the proc file system multiple times and to arbitrary locations, though <filename>/proc</filename> is customary. If you didn't use <userinput>mount -a</userinput>, be sure to mount proc before continuing:" +"You need to create <filename>/etc/fstab</filename>. " +"<informalexample><screen>\n" +"# editor /etc/fstab\n" +"</screen></informalexample> Here is a sample you can modify to suit: " +"<informalexample><screen>\n" +"# /etc/fstab: static file system information.\n" +"#\n" +"# file system mount point type options dump pass\n" +"/dev/XXX / ext3 defaults 0 1\n" +"/dev/XXX /boot ext3 ro,nosuid,nodev 0 2\n" +"\n" +"/dev/XXX none swap sw 0 0\n" +"proc /proc proc defaults 0 0\n" +"\n" +"/dev/fd0 /media/floppy auto noauto,rw,sync,user,exec 0 0\n" +"/dev/cdrom /media/cdrom iso9660 noauto,ro,user,exec 0 0\n" +"\n" +"/dev/XXX /tmp ext3 rw,nosuid,nodev 0 2\n" +"/dev/XXX /var ext3 rw,nosuid,nodev 0 2\n" +"/dev/XXX /usr ext3 rw,nodev 0 2\n" +"/dev/XXX /home ext3 rw,nosuid,nodev 0 2\n" +"</screen></informalexample> Use <userinput>mount -a</userinput> to mount all " +"the file systems you have specified in your <filename>/etc/fstab</filename>, " +"or, to mount file systems individually, use: <informalexample><screen>\n" +"# mount /path # e.g.: mount /usr\n" +"</screen></informalexample> Current Debian systems have mountpoints for " +"removable media under <filename>/media</filename>, but keep compatibility " +"symlinks in <filename>/</filename>. Create these as as needed, for example: " +"<informalexample><screen>\n" +"# cd /media\n" +"# mkdir cdrom0\n" +"# ln -s cdrom0 cdrom\n" +"# cd /\n" +"# ln -s media/cdrom\n" +"</screen></informalexample> You can mount the proc file system multiple " +"times and to arbitrary locations, though <filename>/proc</filename> is " +"customary. If you didn't use <userinput>mount -a</userinput>, be sure to " +"mount proc before continuing:" msgstr "" #. Tag: screen @@ -857,7 +1010,10 @@ msgstr "" #. Tag: para #: random-bits.xml:594 #, no-c-format -msgid "The command <userinput>ls /proc</userinput> should now show a non-empty directory. Should this fail, you may be able to mount proc from outside the chroot:" +msgid "" +"The command <userinput>ls /proc</userinput> should now show a non-empty " +"directory. Should this fail, you may be able to mount proc from outside the " +"chroot:" msgstr "" #. Tag: screen @@ -875,15 +1031,19 @@ msgstr "" #. Tag: para #: random-bits.xml:607 #, no-c-format -msgid "An option in the file <filename>/etc/default/rcS</filename> determines whether the system will interpret the hardware clock as being set to UTC or local time. The following command allow you to set that and choose your timezone." +msgid "" +"An option in the file <filename>/etc/default/rcS</filename> determines " +"whether the system will interpret the hardware clock as being set to UTC or " +"local time. The following command allow you to set that and choose your " +"timezone." msgstr "" #. Tag: screen #: random-bits.xml:614 #, no-c-format msgid "" - "# editor /etc/default/rcS\n" - "# tzconfig" +"# editor /etc/default/rcS\n" +"# tzconfig" msgstr "" #. Tag: title @@ -896,53 +1056,63 @@ msgstr "" #: random-bits.xml:621 #, no-c-format msgid "" - "To configure networking, edit <filename>/etc/network/interfaces</filename>, <filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> and <filename>/etc/hosts</filename>. <informalexample><screen>\n" - "# editor /etc/network/interfaces\n" - "</screen></informalexample> Here are some simple examples from <filename>/usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n" - "######################################################################\n" - "# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n" - "# See the interfaces(5) manpage for information on what options are\n" - "# available.\n" - "######################################################################\n" - "\n" - "# We always want the loopback interface.\n" - "#\n" - "auto lo\n" - "iface lo inet loopback\n" - "\n" - "# To use dhcp:\n" - "#\n" - "# auto eth0\n" - "# iface eth0 inet dhcp\n" - "\n" - "# An example static IP setup: (broadcast and gateway are optional)\n" - "#\n" - "# auto eth0\n" - "# iface eth0 inet static\n" - "# address 192.168.0.42\n" - "# network 192.168.0.0\n" - "# netmask 255.255.255.0\n" - "# broadcast 192.168.0.255\n" - "# gateway 192.168.0.1\n" - "</screen></informalexample> Enter your nameserver(s) and search directives in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n" - "# editor /etc/resolv.conf\n" - "</screen></informalexample> A simple example <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n" - "search hqdom.local\n" - "nameserver 10.1.1.36\n" - "nameserver 192.168.9.100\n" - "</screen></informalexample> Enter your system's host name (2 to 63 characters): <informalexample><screen>\n" - "# echo DebianHostName > /etc/hostname\n" - "</screen></informalexample> And a basic <filename>/etc/hosts</filename> with IPv6 support: <informalexample><screen>\n" - "127.0.0.1 localhost DebianHostName\n" - "\n" - "# The following lines are desirable for IPv6 capable hosts\n" - "::1 ip6-localhost ip6-loopback\n" - "fe00::0 ip6-localnet\n" - "ff00::0 ip6-mcastprefix\n" - "ff02::1 ip6-allnodes\n" - "ff02::2 ip6-allrouters\n" - "ff02::3 ip6-allhosts\n" - "</screen></informalexample> If you have multiple network cards, you should arrange the names of driver modules in the <filename>/etc/modules</filename> file into the desired order. Then during boot, each card will be associated with the interface name (eth0, eth1, etc.) that you expect." +"To configure networking, edit <filename>/etc/network/interfaces</filename>, " +"<filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> " +"and <filename>/etc/hosts</filename>. <informalexample><screen>\n" +"# editor /etc/network/interfaces\n" +"</screen></informalexample> Here are some simple examples from <filename>/" +"usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n" +"######################################################################\n" +"# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n" +"# See the interfaces(5) manpage for information on what options are\n" +"# available.\n" +"######################################################################\n" +"\n" +"# We always want the loopback interface.\n" +"#\n" +"auto lo\n" +"iface lo inet loopback\n" +"\n" +"# To use dhcp:\n" +"#\n" +"# auto eth0\n" +"# iface eth0 inet dhcp\n" +"\n" +"# An example static IP setup: (broadcast and gateway are optional)\n" +"#\n" +"# auto eth0\n" +"# iface eth0 inet static\n" +"# address 192.168.0.42\n" +"# network 192.168.0.0\n" +"# netmask 255.255.255.0\n" +"# broadcast 192.168.0.255\n" +"# gateway 192.168.0.1\n" +"</screen></informalexample> Enter your nameserver(s) and search directives " +"in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n" +"# editor /etc/resolv.conf\n" +"</screen></informalexample> A simple example <filename>/etc/resolv.conf</" +"filename>: <informalexample><screen>\n" +"search hqdom.local\n" +"nameserver 10.1.1.36\n" +"nameserver 192.168.9.100\n" +"</screen></informalexample> Enter your system's host name (2 to 63 " +"characters): <informalexample><screen>\n" +"# echo DebianHostName > /etc/hostname\n" +"</screen></informalexample> And a basic <filename>/etc/hosts</filename> with " +"IPv6 support: <informalexample><screen>\n" +"127.0.0.1 localhost DebianHostName\n" +"\n" +"# The following lines are desirable for IPv6 capable hosts\n" +"::1 ip6-localhost ip6-loopback\n" +"fe00::0 ip6-localnet\n" +"ff00::0 ip6-mcastprefix\n" +"ff02::1 ip6-allnodes\n" +"ff02::2 ip6-allrouters\n" +"ff02::3 ip6-allhosts\n" +"</screen></informalexample> If you have multiple network cards, you should " +"arrange the names of driver modules in the <filename>/etc/modules</filename> " +"file into the desired order. Then during boot, each card will be associated " +"with the interface name (eth0, eth1, etc.) that you expect." msgstr "" #. Tag: title @@ -955,12 +1125,16 @@ msgstr "" #: random-bits.xml:663 #, no-c-format msgid "" - "Debootstrap will have created a very basic <filename>/etc/apt/sources.list</filename> that will allow installing additional packages. However, you may want to add some additional sources, for example for source packages and security updates: <informalexample><screen>\n" - "deb-src http://ftp.us.debian.org/debian &releasename; main\n" - "\n" - "deb http://security.debian.org/ &releasename;/updates main\n" - "deb-src http://security.debian.org/ &releasename;/updates main\n" - "</screen></informalexample> Make sure to run <userinput>aptitude update</userinput> after you have made changes to the sources list." +"Debootstrap will have created a very basic <filename>/etc/apt/sources.list</" +"filename> that will allow installing additional packages. However, you may " +"want to add some additional sources, for example for source packages and " +"security updates: <informalexample><screen>\n" +"deb-src http://ftp.us.debian.org/debian &releasename; main\n" +"\n" +"deb http://security.debian.org/ &releasename;/updates main\n" +"deb-src http://security.debian.org/ &releasename;/updates main\n" +"</screen></informalexample> Make sure to run <userinput>aptitude update</" +"userinput> after you have made changes to the sources list." msgstr "" #. Tag: title @@ -973,24 +1147,29 @@ msgstr "" #: random-bits.xml:680 #, no-c-format msgid "" - "To configure your locale settings to use a language other than English, install the <classname>locales</classname> support package and configure it. Currently the use of UTF-8 locales is recommended. <informalexample><screen>\n" - "# aptitude install locales\n" - "# dpkg-reconfigure locales\n" - "</screen></informalexample> To configure your keyboard (if needed):" +"To configure your locale settings to use a language other than English, " +"install the <classname>locales</classname> support package and configure it. " +"Currently the use of UTF-8 locales is recommended. " +"<informalexample><screen>\n" +"# aptitude install locales\n" +"# dpkg-reconfigure locales\n" +"</screen></informalexample> To configure your keyboard (if needed):" msgstr "" #. Tag: screen #: random-bits.xml:690 #, no-c-format msgid "" - "# aptitude install console-data\n" - "# dpkg-reconfigure console-data" +"# aptitude install console-data\n" +"# dpkg-reconfigure console-data" msgstr "" #. Tag: para #: random-bits.xml:692 #, no-c-format -msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot." +msgid "" +"Note that the keyboard cannot be set while in the chroot, but will be " +"configured for the next reboot." msgstr "" #. Tag: title @@ -1002,7 +1181,9 @@ msgstr "" #. Tag: para #: random-bits.xml:703 #, no-c-format -msgid "If you intend to boot this system, you probably want a Linux kernel and a boot loader. Identify available pre-packaged kernels with:" +msgid "" +"If you intend to boot this system, you probably want a Linux kernel and a " +"boot loader. Identify available pre-packaged kernels with:" msgstr "" #. Tag: screen @@ -1014,36 +1195,47 @@ msgstr "" #. Tag: para #: random-bits.xml:710 #, no-c-format -msgid "If you intend to use a pre-packaged kernel, you may want to create the configuration file <filename>/etc/kernel-img.conf</filename> before you do so. Here's an example file:" +msgid "" +"If you intend to use a pre-packaged kernel, you may want to create the " +"configuration file <filename>/etc/kernel-img.conf</filename> before you do " +"so. Here's an example file:" msgstr "" #. Tag: screen #: random-bits.xml:716 #, no-c-format msgid "" - "# Kernel image management overrides\n" - "# See kernel-img.conf(5) for details\n" - "do_symlinks = yes\n" - "relative_links = yes\n" - "do_bootloader = yes\n" - "do_bootfloppy = no\n" - "do_initrd = yes\n" - "link_in_boot = no" +"# Kernel image management overrides\n" +"# See kernel-img.conf(5) for details\n" +"do_symlinks = yes\n" +"relative_links = yes\n" +"do_bootloader = yes\n" +"do_bootfloppy = no\n" +"do_initrd = yes\n" +"link_in_boot = no" msgstr "" #. Tag: para #: random-bits.xml:718 #, no-c-format -msgid "For detailed information about this file and the various options, consult its man page which will be available after installing the <classname>kernel-package</classname> package. We recommend that you check that the values are appropriate for your system." +msgid "" +"For detailed information about this file and the various options, consult " +"its man page which will be available after installing the <classname>kernel-" +"package</classname> package. We recommend that you check that the values are " +"appropriate for your system." msgstr "" #. Tag: para #: random-bits.xml:725 #, no-c-format msgid "" - "Then install the kernel package of your choice using its package name. <informalexample><screen>\n" - "# aptitude install linux-image-<replaceable>&kernelversion;-arch-etc</replaceable>\n" - "</screen></informalexample> If you did not create a <filename>/etc/kernel-img.conf</filename> before installing a pre-packaged kernel, you may be asked some questions during its installation that refer to it." +"Then install the kernel package of your choice using its package name. " +"<informalexample><screen>\n" +"# aptitude install linux-image-<replaceable>&kernelversion;-arch-etc</" +"replaceable>\n" +"</screen></informalexample> If you did not create a <filename>/etc/kernel-" +"img.conf</filename> before installing a pre-packaged kernel, you may be " +"asked some questions during its installation that refer to it." msgstr "" #. Tag: title @@ -1055,30 +1247,49 @@ msgstr "" #. Tag: para #: random-bits.xml:740 #, no-c-format -msgid "To make your &debian; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your Debian chroot to do so." +msgid "" +"To make your &debian; system bootable, set up your boot loader to load the " +"installed kernel with your new root partition. Note that " +"<command>debootstrap</command> does not install a boot loader, though you " +"can use <command>aptitude</command> inside your Debian chroot to do so." msgstr "" #. Tag: para #: random-bits.xml:747 #, no-c-format -msgid "Check <userinput>info grub</userinput> or <userinput>man lilo.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing grub <filename>menu.lst</filename> or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call <command>lilo</command> (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)." +msgid "" +"Check <userinput>info grub</userinput> or <userinput>man lilo.conf</" +"userinput> for instructions on setting up the bootloader. If you are keeping " +"the system you used to install Debian, just add an entry for the Debian " +"install to your existing grub <filename>menu.lst</filename> or " +"<filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you " +"could also copy it to the new system and edit it there. After you are done " +"editing, call <command>lilo</command> (remember it will use <filename>lilo." +"conf</filename> relative to the system you call it from)." msgstr "" #. Tag: para #: random-bits.xml:759 #, no-c-format msgid "" - "Installing and setting up <classname>grub</classname> is as easy as: <informalexample><screen>\n" - "# aptitude install grub\n" - "# grub-install /dev/<replaceable>hda</replaceable>\n" - "# update-grub\n" - "</screen></informalexample> The second command will install <command>grub</command> (in this case in the MBR of <literal>hda</literal>). The last command will create a sane and working <filename>/boot/grub/menu.lst</filename>." +"Installing and setting up <classname>grub</classname> is as easy as: " +"<informalexample><screen>\n" +"# aptitude install grub\n" +"# grub-install /dev/<replaceable>hda</replaceable>\n" +"# update-grub\n" +"</screen></informalexample> The second command will install <command>grub</" +"command> (in this case in the MBR of <literal>hda</literal>). The last " +"command will create a sane and working <filename>/boot/grub/menu.lst</" +"filename>." msgstr "" #. Tag: para #: random-bits.xml:769 #, no-c-format -msgid "Note that this assumes that a <filename>/dev/hda</filename> device file has been created. There are alternative methods to install <command>grub</command>, but those are outside the scope of this appendix." +msgid "" +"Note that this assumes that a <filename>/dev/hda</filename> device file has " +"been created. There are alternative methods to install <command>grub</" +"command>, but those are outside the scope of this appendix." msgstr "" #. Tag: para @@ -1091,52 +1302,68 @@ msgstr "" #: random-bits.xml:779 #, no-c-format msgid "" - "boot=/dev/<replaceable>hda6</replaceable>\n" - "root=/dev/<replaceable>hda6</replaceable>\n" - "install=menu\n" - "delay=20\n" - "lba32\n" - "image=/vmlinuz\n" - "initrd=/initrd.img\n" - "label=Debian" +"boot=/dev/<replaceable>hda6</replaceable>\n" +"root=/dev/<replaceable>hda6</replaceable>\n" +"install=menu\n" +"delay=20\n" +"lba32\n" +"image=/vmlinuz\n" +"initrd=/initrd.img\n" +"label=Debian" msgstr "" #. Tag: para #: random-bits.xml:781 #, no-c-format -msgid "Depending on which bootloader you selected, you can now make some additional changes in <filename>/etc/kernel-img.conf</filename>." +msgid "" +"Depending on which bootloader you selected, you can now make some additional " +"changes in <filename>/etc/kernel-img.conf</filename>." msgstr "" #. Tag: para #: random-bits.xml:786 #, no-c-format msgid "" - "For the <classname>grub</classname> bootloader, you should set the <literal>do_bootloader</literal> option to <quote>no</quote>. And to automatically update your <filename>/boot/grub/menu.lst</filename> on installation or removal of Debian kernels, add the following lines: <informalexample><screen>\n" - "postinst_hook = update-grub\n" - "postrm_hook = update-grub\n" - "</screen></informalexample> For the <classname>lilo</classname> bootloader, the value of <literal>do_bootloader</literal> needs to remain <quote>yes</quote>." +"For the <classname>grub</classname> bootloader, you should set the " +"<literal>do_bootloader</literal> option to <quote>no</quote>. And to " +"automatically update your <filename>/boot/grub/menu.lst</filename> on " +"installation or removal of Debian kernels, add the following lines: " +"<informalexample><screen>\n" +"postinst_hook = update-grub\n" +"postrm_hook = update-grub\n" +"</screen></informalexample> For the <classname>lilo</classname> bootloader, " +"the value of <literal>do_bootloader</literal> needs to remain <quote>yes</" +"quote>." msgstr "" #. Tag: para #: random-bits.xml:798 #, no-c-format -msgid "Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing <filename>yaboot.conf</filename>. You could also copy it to the new system and edit it there. After you are done editing, call ybin (remember it will use <filename>yaboot.conf</filename> relative to the system you call it from)." +msgid "" +"Check <userinput>man yaboot.conf</userinput> for instructions on setting up " +"the bootloader. If you are keeping the system you used to install Debian, " +"just add an entry for the Debian install to your existing <filename>yaboot." +"conf</filename>. You could also copy it to the new system and edit it there. " +"After you are done editing, call ybin (remember it will use <filename>yaboot." +"conf</filename> relative to the system you call it from)." msgstr "" #. Tag: para #: random-bits.xml:808 #, no-c-format msgid "" - "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n" - "boot=/dev/hda2\n" - "device=hd:\n" - "partition=6\n" - "root=/dev/hda6\n" - "magicboot=/usr/lib/yaboot/ofboot\n" - "timeout=50\n" - "image=/vmlinux\n" - "label=Debian\n" - "</screen></informalexample> On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>." +"Here is a basic <filename>/etc/yaboot.conf</filename> as an example: " +"<informalexample><screen>\n" +"boot=/dev/hda2\n" +"device=hd:\n" +"partition=6\n" +"root=/dev/hda6\n" +"magicboot=/usr/lib/yaboot/ofboot\n" +"timeout=50\n" +"image=/vmlinux\n" +"label=Debian\n" +"</screen></informalexample> On some machines, you may need to use " +"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>." msgstr "" #. Tag: title @@ -1149,15 +1376,22 @@ msgstr "" #: random-bits.xml:822 #, no-c-format msgid "" - "As mentioned earlier, the installed system will be very basic. If you would like to make the system a bit more mature, there is an easy method to install all packages with <quote>standard</quote> priority: <informalexample><screen>\n" - "# tasksel install standard\n" - "</screen></informalexample> Of course, you can also just use <command>aptitude</command> to install packages individually." +"As mentioned earlier, the installed system will be very basic. If you would " +"like to make the system a bit more mature, there is an easy method to " +"install all packages with <quote>standard</quote> priority: " +"<informalexample><screen>\n" +"# tasksel install standard\n" +"</screen></informalexample> Of course, you can also just use " +"<command>aptitude</command> to install packages individually." msgstr "" #. Tag: para #: random-bits.xml:833 #, no-c-format -msgid "After the installation there will be a lot of downloaded packages in <filename>/var/cache/apt/archives/</filename>. You can free up some diskspace by running:" +msgid "" +"After the installation there will be a lot of downloaded packages in " +"<filename>/var/cache/apt/archives/</filename>. You can free up some " +"diskspace by running:" msgstr "" #. Tag: screen @@ -1175,25 +1409,41 @@ msgstr "" #. Tag: para #: random-bits.xml:852 #, no-c-format -msgid "This section explains how to install &debian; on a computer without an Ethernet card, but with just a remote gateway computer attached via a Null-Modem cable (also called Null-Printer cable). The gateway computer should be connected to a network that has a Debian mirror on it (e.g. to the Internet)." +msgid "" +"This section explains how to install &debian; on a computer without an " +"Ethernet card, but with just a remote gateway computer attached via a Null-" +"Modem cable (also called Null-Printer cable). The gateway computer should be " +"connected to a network that has a Debian mirror on it (e.g. to the Internet)." msgstr "" #. Tag: para #: random-bits.xml:860 #, no-c-format -msgid "In the example in this appendix we will set up a PLIP connection using a gateway connected to the Internet over a dial-up connection (ppp0). We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the target system and the source system respectively (these addresses should be unused within your network address space)." +msgid "" +"In the example in this appendix we will set up a PLIP connection using a " +"gateway connected to the Internet over a dial-up connection (ppp0). We will " +"use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the " +"target system and the source system respectively (these addresses should be " +"unused within your network address space)." msgstr "" #. Tag: para #: random-bits.xml:868 #, no-c-format -msgid "The PLIP connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)." +msgid "" +"The PLIP connection set up during the installation will also be available " +"after the reboot into the installed system (see <xref linkend=\"boot-new\"/" +">)." msgstr "" #. Tag: para #: random-bits.xml:873 #, no-c-format -msgid "Before you start, you will need to check the BIOS configuration (IO base address and IRQ) for the parallel ports of both the source and target systems. The most common values are <literal>io=0x378</literal>, <literal>irq=7</literal>." +msgid "" +"Before you start, you will need to check the BIOS configuration (IO base " +"address and IRQ) for the parallel ports of both the source and target " +"systems. The most common values are <literal>io=0x378</literal>, " +"<literal>irq=7</literal>." msgstr "" #. Tag: title @@ -1205,7 +1455,9 @@ msgstr "" #. Tag: para #: random-bits.xml:886 #, no-c-format -msgid "A target computer, called <emphasis>target</emphasis>, where Debian will be installed." +msgid "" +"A target computer, called <emphasis>target</emphasis>, where Debian will be " +"installed." msgstr "" #. Tag: para @@ -1217,13 +1469,18 @@ msgstr "" #. Tag: para #: random-bits.xml:897 #, no-c-format -msgid "Another computer connected to the Internet, called <emphasis>source</emphasis>, that will function as the gateway." +msgid "" +"Another computer connected to the Internet, called <emphasis>source</" +"emphasis>, that will function as the gateway." msgstr "" #. Tag: para #: random-bits.xml:903 #, no-c-format -msgid "A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> for more information on this cable and instructions how to make your own." +msgid "" +"A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;" +"\">PLIP-Install-HOWTO</ulink> for more information on this cable and " +"instructions how to make your own." msgstr "" #. Tag: title @@ -1235,28 +1492,33 @@ msgstr "" #. Tag: para #: random-bits.xml:916 #, no-c-format -msgid "The following shell script is a simple example of how to configure the source computer as a gateway to the Internet using ppp0." +msgid "" +"The following shell script is a simple example of how to configure the " +"source computer as a gateway to the Internet using ppp0." msgstr "" #. Tag: screen #: random-bits.xml:921 #, no-c-format msgid "" - "#!/bin/sh\n" - "\n" - "# We remove running modules from kernel to avoid conflicts and to\n" - "# reconfigure them manually.\n" - "modprobe -r lp parport_pc\n" - "modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</replaceable>\n" - "modprobe plip\n" - "\n" - "# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n" - "ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint <replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n" - "\n" - "# Configure gateway\n" - "modprobe iptable_nat\n" - "iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j MASQUERADE\n" - "echo 1 > /proc/sys/net/ipv4/ip_forward" +"#!/bin/sh\n" +"\n" +"# We remove running modules from kernel to avoid conflicts and to\n" +"# reconfigure them manually.\n" +"modprobe -r lp parport_pc\n" +"modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</" +"replaceable>\n" +"modprobe plip\n" +"\n" +"# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n" +"ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint " +"<replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n" +"\n" +"# Configure gateway\n" +"modprobe iptable_nat\n" +"iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j " +"MASQUERADE\n" +"echo 1 > /proc/sys/net/ipv4/ip_forward" msgstr "" #. Tag: title @@ -1269,9 +1531,16 @@ msgstr "" #: random-bits.xml:928 #, no-c-format msgid "" - "Boot the installation media. The installation needs to be run in expert mode; enter <userinput>expert</userinput> at the boot prompt. If you need to set parameters for kernel modules, you also need to do this at the boot prompt. For example, to boot the installer and set values for the <quote>io</quote> and <quote>irq</quote> options for the parport_pc module, enter the following at the boot prompt: <informalexample><screen>\n" - "expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc.irq=<replaceable>7</replaceable>\n" - "</screen></informalexample> Below are the answers that should be given during various stages of the installation." +"Boot the installation media. The installation needs to be run in expert " +"mode; enter <userinput>expert</userinput> at the boot prompt. If you need to " +"set parameters for kernel modules, you also need to do this at the boot " +"prompt. For example, to boot the installer and set values for the <quote>io</" +"quote> and <quote>irq</quote> options for the parport_pc module, enter the " +"following at the boot prompt: <informalexample><screen>\n" +"expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc." +"irq=<replaceable>7</replaceable>\n" +"</screen></informalexample> Below are the answers that should be given " +"during various stages of the installation." msgstr "" #. Tag: guimenuitem @@ -1283,7 +1552,9 @@ msgstr "" #. Tag: para #: random-bits.xml:949 #, no-c-format -msgid "Select the <userinput>plip-modules</userinput> option from the list; this will make the PLIP drivers available to the installation system." +msgid "" +"Select the <userinput>plip-modules</userinput> option from the list; this " +"will make the PLIP drivers available to the installation system." msgstr "" #. Tag: guimenuitem @@ -1295,13 +1566,20 @@ msgstr "" #. Tag: para #: random-bits.xml:962 #, no-c-format -msgid "If target <emphasis>does</emphasis> have a network card, a list of driver modules for detected cards will be shown. If you want to force &d-i; to use plip instead, you have to deselect all listed driver modules. Obviously, if target doesn't have a network card, the installer will not show this list." +msgid "" +"If target <emphasis>does</emphasis> have a network card, a list of driver " +"modules for detected cards will be shown. If you want to force &d-i; to use " +"plip instead, you have to deselect all listed driver modules. Obviously, if " +"target doesn't have a network card, the installer will not show this list." msgstr "" #. Tag: para #: random-bits.xml:971 #, no-c-format -msgid "Because no network card was detected/selected earlier, the installer will ask you to select a network driver module from a list. Select the <userinput>plip</userinput> module." +msgid "" +"Because no network card was detected/selected earlier, the installer will " +"ask you to select a network driver module from a list. Select the " +"<userinput>plip</userinput> module." msgstr "" #. Tag: guimenuitem @@ -1319,19 +1597,24 @@ msgstr "" #. Tag: para #: random-bits.xml:991 #, no-c-format -msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>" +msgid "" +"IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>" msgstr "" #. Tag: para #: random-bits.xml:996 #, no-c-format -msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>" +msgid "" +"Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></" +"userinput>" msgstr "" #. Tag: para #: random-bits.xml:1002 #, no-c-format -msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)" +msgid "" +"Name server addresses: you can enter the same addresses used on source (see " +"<filename>/etc/resolv.conf</filename>)" msgstr "" #. Tag: title @@ -1343,72 +1626,117 @@ msgstr "" #. Tag: para #: random-bits.xml:1023 #, no-c-format -msgid "In some countries PPP over Ethernet (PPPoE) is a common protocol for broadband (ADSL or cable) connections to an Internet Service Provider. Setting up a network connection using PPPoE is not supported by default in the installer, but can be made to work very simply. This section explains how." +msgid "" +"In some countries PPP over Ethernet (PPPoE) is a common protocol for " +"broadband (ADSL or cable) connections to an Internet Service Provider. " +"Setting up a network connection using PPPoE is not supported by default in " +"the installer, but can be made to work very simply. This section explains " +"how." msgstr "" #. Tag: para #: random-bits.xml:1031 #, no-c-format -msgid "The PPPoE connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)." +msgid "" +"The PPPoE connection set up during the installation will also be available " +"after the reboot into the installed system (see <xref linkend=\"boot-new\"/" +">)." msgstr "" #. Tag: para #: random-bits.xml:1036 #, no-c-format -msgid "To have the option of setting up and using PPPoE during the installation, you will need to install using one of the CD-ROM/DVD images that are available. It is not supported for other installation methods (e.g. netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)." +msgid "" +"To have the option of setting up and using PPPoE during the installation, " +"you will need to install using one of the CD-ROM/DVD images that are " +"available. It is not supported for other installation methods (e.g. " +"netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)." msgstr "" #. Tag: para #: random-bits.xml:1043 #, no-c-format -msgid "Installing over PPPoE is mostly the same as any other installation. The following steps explain the differences." +msgid "" +"Installing over PPPoE is mostly the same as any other installation. The " +"following steps explain the differences." msgstr "" #. Tag: para #: random-bits.xml:1051 #, no-c-format msgid "" - "Boot the installer with <userinput>modules=ppp-udeb</userinput> as boot parameter. This means that at the boot prompt you should enter: <informalexample><screen>\n" - "install modules=ppp-udeb\n" - "</screen></informalexample> or, if you prefer using the graphical installer: <informalexample><screen>\n" - "installgui modules=ppp-udeb\n" - "</screen></informalexample> This will ensure the component responsible for the setup of PPPoE (<classname>ppp-udeb</classname>) will be loaded and run automatically." +"Boot the installer with <userinput>modules=ppp-udeb</userinput> as boot " +"parameter. This means that at the boot prompt you should enter: " +"<informalexample><screen>\n" +"install modules=ppp-udeb\n" +"</screen></informalexample> or, if you prefer using the graphical installer: " +"<informalexample><screen>\n" +"installgui modules=ppp-udeb\n" +"</screen></informalexample> This will ensure the component responsible for " +"the setup of PPPoE (<classname>ppp-udeb</classname>) will be loaded and run " +"automatically." msgstr "" #. Tag: para #: random-bits.xml:1066 #, no-c-format -msgid "Follow the regular initial steps of the installation (language, country and keyboard selection; the loading of additional installer components<footnote> <para> The <classname>ppp-udeb</classname> component is loaded as one of the additional components in this step. If you want to install at medium or low priority (expert mode), you can also manually select the <classname>ppp-udeb</classname> instead of entering the <quote>modules</quote> parameter at the boot prompt. </para> </footnote>)." +msgid "" +"Follow the regular initial steps of the installation (language, country and " +"keyboard selection; the loading of additional installer components<footnote> " +"<para> The <classname>ppp-udeb</classname> component is loaded as one of the " +"additional components in this step. If you want to install at medium or low " +"priority (expert mode), you can also manually select the <classname>ppp-" +"udeb</classname> instead of entering the <quote>modules</quote> parameter at " +"the boot prompt. </para> </footnote>)." msgstr "" #. Tag: para #: random-bits.xml:1085 #, no-c-format -msgid "The next step is the detection of network hardware, in order to identify any Ethernet cards present in the system." +msgid "" +"The next step is the detection of network hardware, in order to identify any " +"Ethernet cards present in the system." msgstr "" #. Tag: para #: random-bits.xml:1091 #, no-c-format -msgid "After this the actual setup of PPPoE is started. The installer will probe all the detected Ethernet interfaces in an attempt to find a PPPoE concentrator (a type of server which handles PPPoE connections)." +msgid "" +"After this the actual setup of PPPoE is started. The installer will probe " +"all the detected Ethernet interfaces in an attempt to find a PPPoE " +"concentrator (a type of server which handles PPPoE connections)." msgstr "" #. Tag: para #: random-bits.xml:1097 #, no-c-format -msgid "It is possible that the concentrator will not to be found at the first attempt. This can happen occasionally on slow or loaded networks or with faulty servers. In most cases a second attempt to detect the concentrator will be successful; to retry, select <guimenuitem>Configure and start a PPPoE connection</guimenuitem> from the main menu of the installer." +msgid "" +"It is possible that the concentrator will not to be found at the first " +"attempt. This can happen occasionally on slow or loaded networks or with " +"faulty servers. In most cases a second attempt to detect the concentrator " +"will be successful; to retry, select <guimenuitem>Configure and start a " +"PPPoE connection</guimenuitem> from the main menu of the installer." msgstr "" #. Tag: para #: random-bits.xml:1106 #, no-c-format -msgid "After a concentrator is found, the user will be prompted to type the login information (the PPPoE username and password)." +msgid "" +"After a concentrator is found, the user will be prompted to type the login " +"information (the PPPoE username and password)." msgstr "" #. Tag: para #: random-bits.xml:1112 #, no-c-format -msgid "At this point the installer will use the provided information to establish the PPPoE connection. If the correct information was provided, the PPPoE connection should be configured and the installer should be able to use it to connect to the Internet and retrieve packages over it (if needed). If the login information is not correct or some error appears, the installer will stop, but the configuration can be attempted again by selecting the menu entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>." +msgid "" +"At this point the installer will use the provided information to establish " +"the PPPoE connection. If the correct information was provided, the PPPoE " +"connection should be configured and the installer should be able to use it " +"to connect to the Internet and retrieve packages over it (if needed). If the " +"login information is not correct or some error appears, the installer will " +"stop, but the configuration can be attempted again by selecting the menu " +"entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>." msgstr "" #. Tag: title @@ -1420,49 +1748,93 @@ msgstr "" #. Tag: para #: random-bits.xml:1133 #, no-c-format -msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the regular installer as it basically uses the same programs, but with a different frontend." +msgid "" +"The graphical version of the installer is only available for a limited " +"number of architectures, including &arch-title;. The functionality of the " +"graphical installer is essentially the same as that of the regular installer " +"as it basically uses the same programs, but with a different frontend." msgstr "" #. Tag: para #: random-bits.xml:1141 #, no-c-format -msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the regular <quote>newt</quote> frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen." +msgid "" +"Although the functionality is identical, the graphical installer still has a " +"few significant advantages. The main advantage is that it supports more " +"languages, namely those that use a character set that cannot be displayed " +"with the regular <quote>newt</quote> frontend. It also has a few usability " +"advantages such as the option to use a mouse, and in some cases several " +"questions can be displayed on a single screen." msgstr "" #. Tag: para #: random-bits.xml:1150 #, no-c-format -msgid "The graphical installer is available with all CD images and with the hd-media installation method. As the graphical installer uses a separate (much larger) initrd than the regular installer, it has to be booted using <userinput>installgui</userinput> instead of <userinput>install</userinput>. Analogous, the expert and rescue modes are booted using <userinput>expertgui</userinput> and <userinput>rescuegui</userinput> respectively." +msgid "" +"The graphical installer is available with all CD images and with the hd-" +"media installation method. To boot the graphical installer simply select the " +"relevant option from the boot menu. Expert and rescue mode for the graphical " +"installer can be selected from the <quote>Advanced options</quote> menu. The " +"previously used boot methods <userinput>installgui</userinput>, " +"<userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can " +"still be used from the boot prompt which is shown after selecting the " +"<quote>Help</quote> option in the boot menu." msgstr "" #. Tag: para -#: random-bits.xml:1160 +#: random-bits.xml:1161 #, no-c-format -msgid "It is also available as a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a Debian mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is mainly useful for testing; in this case the image is booted just using <userinput>install</userinput>. There is no graphical installer image that can be netbooted." +msgid "" +"There is also a graphical installer image that can be netbooted. And there " +"is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> " +"<para> The mini ISO image can be downloaded from a Debian mirror as " +"described in <xref linkend=\"downloading-files\"/>. Look for " +"<filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is " +"mainly useful for testing." msgstr "" #. Tag: para -#: random-bits.xml:1175 +#: random-bits.xml:1174 #, no-c-format -msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a Debian mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems." +msgid "" +"For &arch-title;, currently only an experimental <quote>mini</quote> ISO " +"image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image " +"can be downloaded from a Debian mirror as described in <xref linkend=" +"\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. " +"</para> </footnote>. It should work on almost all PowerPC systems that have " +"an ATI graphical card, but is unlikely to work on other systems." msgstr "" #. Tag: para -#: random-bits.xml:1189 +#: random-bits.xml:1188 #, no-c-format -msgid "Just as with the regular installer it is possible to add boot parameters when starting the graphical installer. One of those parameters allows to configure the mouse for left-handed use. Others allow to select the mouse device (e.g. for a serial mouse) and the mouse protocol. See <xref linkend=\"boot-parms\"/> for valid parameters." +msgid "" +"Just as with the regular installer it is possible to add boot parameters " +"when starting the graphical installer. One of those parameters allows to " +"configure the mouse for left-handed use. Others allow to select the mouse " +"device (e.g. for a serial mouse) and the mouse protocol. See <xref linkend=" +"\"boot-parms\"/> for valid parameters<phrase arch=\"x86\"> and <xref linkend=" +"\"boot-screen\"/> for information on how to pass them</phrase>." msgstr "" #. Tag: para #: random-bits.xml:1198 #, no-c-format -msgid "The graphical installer requires significantly more memory to run than the regular installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the regular <quote>newt</quote> frontend." +msgid "" +"The graphical installer requires significantly more memory to run than the " +"regular installer: &minimum-memory-gtk;. If insufficient memory is " +"available, it will automatically fall back to the regular <quote>newt</" +"quote> frontend." msgstr "" #. Tag: para #: random-bits.xml:1205 #, no-c-format -msgid "If the amount of memory in your system is below &minimum-memory;, the graphical installer may fail to boot at all while booting the regular installer would still work. Using the regular installer is recommended for systems with little available memory." +msgid "" +"If the amount of memory in your system is below &minimum-memory;, the " +"graphical installer may fail to boot at all while booting the regular " +"installer would still work. Using the regular installer is recommended for " +"systems with little available memory." msgstr "" #. Tag: title @@ -1474,19 +1846,35 @@ msgstr "" #. Tag: para #: random-bits.xml:1216 #, no-c-format -msgid "As already mentioned, the graphical installer basically works the same as the regular installer and thus the rest of this manual can be used to guide you through the installation process." +msgid "" +"As already mentioned, the graphical installer basically works the same as " +"the regular installer and thus the rest of this manual can be used to guide " +"you through the installation process." msgstr "" #. Tag: para #: random-bits.xml:1222 #, no-c-format -msgid "If you prefer using the keyboard over the mouse, there are two things you need to know. To expand a collapsed list (used for example for the selection of countries within continents), you can use the <keycap>+</keycap> and <keycap>-</keycap> keys. For questions where more than one item can be selected (e.g. task selection), you first need to tab to the &BTN-CONT; button after making your selections; hitting enter will toggle a selection, not activate &BTN-CONT;." +msgid "" +"If you prefer using the keyboard over the mouse, there are two things you " +"need to know. To expand a collapsed list (used for example for the selection " +"of countries within continents), you can use the <keycap>+</keycap> and " +"<keycap>-</keycap> keys. For questions where more than one item can be " +"selected (e.g. task selection), you first need to tab to the &BTN-CONT; " +"button after making your selections; hitting enter will toggle a selection, " +"not activate &BTN-CONT;." msgstr "" #. Tag: para #: random-bits.xml:1232 #, no-c-format -msgid "To switch to another console, you will also need to use the <keycap>Ctrl</keycap> key, just as with the X Window System. For example, to switch to VT2 (the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</keycap> <keycap>F5</keycap> </keycombo> to switch back." +msgid "" +"To switch to another console, you will also need to use the <keycap>Ctrl</" +"keycap> key, just as with the X Window System. For example, to switch to VT2 " +"(the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> " +"<keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical " +"installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</" +"keycap> <keycap>F5</keycap> </keycombo> to switch back." msgstr "" #. Tag: title @@ -1498,48 +1886,58 @@ msgstr "" #. Tag: para #: random-bits.xml:1247 #, no-c-format -msgid "Etch is the first release that includes the graphical installer and uses some relatively new technology. There are a few known issues that you may run into during the installation. We expect to be able to fix these issues for the next release of &debian;." +msgid "" +"The graphical frontend to the installer is relatively new and because of " +"that there are some known issues. We continue to work on resolving these." msgstr "" #. Tag: para -#: random-bits.xml:1257 +#: random-bits.xml:1255 #, no-c-format -msgid "Information on some screens is not nicely formatted into columns as it should be. The most obvious example is the first screen where you select your language. Another example is the main screen of partman." +msgid "" +"Information on some screens is not yet nicely formatted into columns as it " +"should be. This is most visible during partitioning." msgstr "" #. Tag: para -#: random-bits.xml:1264 +#: random-bits.xml:1261 #, no-c-format -msgid "Typing some characters may not work and in some cases the wrong character may be printed. For example, \"composing\" a character by typing an accent and then the letter over/under which the accent should appear does not work." +msgid "" +"Typing some characters may not work and in some cases the wrong character " +"may be printed. For example, \"composing\" a character by typing an accent " +"and then the letter over/under which the accent should appear does not work." msgstr "" #. Tag: para -#: random-bits.xml:1271 +#: random-bits.xml:1268 #, no-c-format msgid "Support for touchpads is not yet optimal." msgstr "" #. Tag: para -#: random-bits.xml:1276 -#, no-c-format -msgid "Support for creating encrypted partitions is limited as it is not possible to generate a random encryption key. It is possible to set up an encrypted partition using a passphrase as encryption key." -msgstr "" - -#. Tag: para -#: random-bits.xml:1283 +#: random-bits.xml:1273 #, no-c-format -msgid "Starting a shell from the graphical frontend is currently not supported. This means that relevant options to do that (which are available when you use the textual frontend), will not be shown in the main menu of the installation system and in the menu for the rescue mode. You will instead have to switch (as described above) to the shells that are available on virtual consoles VT2 and VT3." +msgid "" +"Starting a shell from the graphical frontend is currently not supported. " +"This means that relevant options to do that (which are available when you " +"use the textual frontend), will not be shown in the main menu of the " +"installation system and in the menu for the rescue mode. You will instead " +"have to switch (as described above) to the shells that are available on " +"virtual consoles VT2 and VT3." msgstr "" #. Tag: para -#: random-bits.xml:1292 +#: random-bits.xml:1282 #, no-c-format -msgid "After booting the installer in rescue mode, it may be useful to start a shell in the root partition of an already installed system. This is possible (after you have selected the partition to be mounted as the root partition) by switching to VT2 or VT3 and entering the following command:" +msgid "" +"After booting the installer in rescue mode, it may be useful to start a " +"shell in the root partition of an already installed system. This is possible " +"(after you have selected the partition to be mounted as the root partition) " +"by switching to VT2 or VT3 and entering the following command:" msgstr "" #. Tag: screen -#: random-bits.xml:1299 +#: random-bits.xml:1289 #, no-c-format msgid "# chroot /target" msgstr "" - diff --git a/po/nn/using-d-i.po b/po/nn/using-d-i.po index 14c3a9bfd..399b6914c 100644 --- a/po/nn/using-d-i.po +++ b/po/nn/using-d-i.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2008-03-30 00:11+0000\n" +"POT-Creation-Date: 2008-05-05 00:09+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" @@ -29,61 +29,120 @@ msgstr "" #. Tag: para #: using-d-i.xml:8 #, no-c-format -msgid "The Debian Installer consists of a number of special-purpose components to perform each installation task. Each component performs its task, asking the user questions as necessary to do its job. The questions themselves are given priorities, and the priority of questions to be asked is set when the installer is started." +msgid "" +"The Debian Installer consists of a number of special-purpose components to " +"perform each installation task. Each component performs its task, asking the " +"user questions as necessary to do its job. The questions themselves are " +"given priorities, and the priority of questions to be asked is set when the " +"installer is started." msgstr "" #. Tag: para #: using-d-i.xml:16 #, no-c-format -msgid "When a default installation is performed, only essential (high priority) questions will be asked. This results in a highly automated installation process with little user interaction. Components are automatically run in sequence; which components are run depends mainly on the installation method you use and on your hardware. The installer will use default values for questions that are not asked." +msgid "" +"When a default installation is performed, only essential (high priority) " +"questions will be asked. This results in a highly automated installation " +"process with little user interaction. Components are automatically run in " +"sequence; which components are run depends mainly on the installation method " +"you use and on your hardware. The installer will use default values for " +"questions that are not asked." msgstr "" #. Tag: para #: using-d-i.xml:25 #, no-c-format -msgid "If there is a problem, the user will see an error screen, and the installer menu may be shown in order to select some alternative action. If there are no problems, the user will never see the installer menu, but will simply answer questions for each component in turn. Serious error notifications are set to priority <quote>critical</quote> so the user will always be notified." +msgid "" +"If there is a problem, the user will see an error screen, and the installer " +"menu may be shown in order to select some alternative action. If there are " +"no problems, the user will never see the installer menu, but will simply " +"answer questions for each component in turn. Serious error notifications are " +"set to priority <quote>critical</quote> so the user will always be notified." msgstr "" #. Tag: para #: using-d-i.xml:34 #, no-c-format -msgid "Some of the defaults that the installer uses can be influenced by passing boot arguments when &d-i; is started. If, for example, you wish to force static network configuration (DHCP is used by default if available), you could add the boot parameter <userinput>netcfg/disable_dhcp=true</userinput>. See <xref linkend=\"installer-args\"/> for available options." +msgid "" +"Some of the defaults that the installer uses can be influenced by passing " +"boot arguments when &d-i; is started. If, for example, you wish to force " +"static network configuration (DHCP is used by default if available), you " +"could add the boot parameter <userinput>netcfg/disable_dhcp=true</" +"userinput>. See <xref linkend=\"installer-args\"/> for available options." msgstr "" #. Tag: para #: using-d-i.xml:42 #, no-c-format -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>." +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 "" #. Tag: para #: using-d-i.xml:50 #, no-c-format -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;." +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 "" #. Tag: para #: using-d-i.xml:59 #, no-c-format -msgid "The normal installer display is character-based (as opposed to the now more familiar graphical interface). The mouse is not operational in this environment. Here are the keys you can use to navigate within the various dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move <quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> <keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move <quote>backward</quote> between displayed buttons and selections. The <keycap>up</keycap> and <keycap>down</keycap> arrow select different items within a scrollable list, and also scroll the list itself. In addition, in long lists, you can type a letter to cause the list to scroll directly to the section with items starting with the letter you typed and use <keycap>Pg-Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The <keycap>space bar</keycap> selects an item such as a checkbox. Use &enterkey; to activate choices." +msgid "" +"The normal installer display is character-based (as opposed to the now more " +"familiar graphical interface). The mouse is not operational in this " +"environment. Here are the keys you can use to navigate within the various " +"dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move " +"<quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> " +"<keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move " +"<quote>backward</quote> between displayed buttons and selections. The " +"<keycap>up</keycap> and <keycap>down</keycap> arrow select different items " +"within a scrollable list, and also scroll the list itself. In addition, in " +"long lists, you can type a letter to cause the list to scroll directly to " +"the section with items starting with the letter you typed and use <keycap>Pg-" +"Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The " +"<keycap>space bar</keycap> selects an item such as a checkbox. Use " +"&enterkey; to activate choices." msgstr "" #. Tag: para #: using-d-i.xml:77 #, no-c-format -msgid "S/390 does not support virtual consoles. You may open a second and third ssh session to view the logs described below." +msgid "" +"S/390 does not support virtual consoles. You may open a second and third ssh " +"session to view the logs described below." msgstr "" #. Tag: para #: using-d-i.xml:82 #, no-c-format -msgid "Error messages and logs are redirected to the fourth console. You can access this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing the <keycap>F4</keycap> function key); get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>." +msgid "" +"Error messages and logs are redirected to the fourth console. You can access " +"this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</" +"keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing " +"the <keycap>F4</keycap> function key); get back to the main installer " +"process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></" +"keycombo>." msgstr "" #. Tag: para #: using-d-i.xml:92 #, no-c-format -msgid "These messages can also be found in <filename>/var/log/syslog</filename>. After installation, this log is copied to <filename>/var/log/installer/syslog</filename> on your new system. Other 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." +msgid "" +"These messages can also be found in <filename>/var/log/syslog</filename>. " +"After installation, this log is copied to <filename>/var/log/installer/" +"syslog</filename> on your new system. Other installation messages may be " +"found in <filename>/var/log/</filename> during the installation, and " +"<filename>/var/log/installer/</filename> after the computer has been booted " +"into the installed system." msgstr "" #. Tag: title @@ -95,7 +154,10 @@ msgstr "" #. Tag: para #: using-d-i.xml:107 #, no-c-format -msgid "Here is a list of installer components with a brief description of each component's purpose. Details you might need to know about using a particular component are in <xref linkend=\"module-details\"/>." +msgid "" +"Here is a list of installer components with a brief description of each " +"component's purpose. Details you might need to know about using a particular " +"component are in <xref linkend=\"module-details\"/>." msgstr "" #. Tag: term @@ -107,13 +169,22 @@ msgstr "" #. Tag: para #: using-d-i.xml:118 #, no-c-format -msgid "Shows the list of components to the user during installer operation, and starts a component when it is selected. Main-menu's questions are set to priority medium, so if your priority is set to high or critical (high is the default), you will not see the menu. On the other hand, if there is an error which requires your intervention, the question priority may be downgraded temporarily to allow you to resolve the problem, and in that case the menu may appear." +msgid "" +"Shows the list of components to the user during installer operation, and " +"starts a component when it is selected. Main-menu's questions are set to " +"priority medium, so if your priority is set to high or critical (high is the " +"default), you will not see the menu. On the other hand, if there is an error " +"which requires your intervention, the question priority may be downgraded " +"temporarily to allow you to resolve the problem, and in that case the menu " +"may appear." msgstr "" #. Tag: para #: using-d-i.xml:128 #, no-c-format -msgid "You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly to back all the way out of the currently running component." +msgid "" +"You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly " +"to back all the way out of the currently running component." msgstr "" #. Tag: term @@ -125,7 +196,11 @@ msgstr "" #. Tag: para #: using-d-i.xml:137 #, no-c-format -msgid "Allows the user to select localization options for the installation and the installed system: language, country and locales. The installer will display messages in the selected language, unless the translation for that language is not complete in which case some messages may be shown in English." +msgid "" +"Allows the user to select localization options for the installation and the " +"installed system: language, country and locales. The installer will display " +"messages in the selected language, unless the translation for that language " +"is not complete in which case some messages may be shown in English." msgstr "" #. Tag: term @@ -137,7 +212,9 @@ msgstr "" #. Tag: para #: using-d-i.xml:149 #, no-c-format -msgid "Shows a list of keyboards, from which the user chooses the model which matches his own." +msgid "" +"Shows a list of keyboards, from which the user chooses the model which " +"matches his own." msgstr "" #. Tag: term @@ -149,7 +226,9 @@ msgstr "" #. Tag: para #: using-d-i.xml:158 #, no-c-format -msgid "Automatically detects most of the system's hardware, including network cards, disk drives, and PCMCIA." +msgid "" +"Automatically detects most of the system's hardware, including network " +"cards, disk drives, and PCMCIA." msgstr "" #. Tag: term @@ -173,7 +252,9 @@ msgstr "" #. Tag: para #: using-d-i.xml:175 #, no-c-format -msgid "Configures the computer's network connections so it can communicate over the internet." +msgid "" +"Configures the computer's network connections so it can communicate over the " +"internet." msgstr "" #. Tag: term @@ -185,7 +266,8 @@ msgstr "" #. Tag: para #: using-d-i.xml:184 #, no-c-format -msgid "Looks for ISO file systems, which may be on a CD-ROM or on the hard drive." +msgid "" +"Looks for ISO file systems, which may be on a CD-ROM or on the hard drive." msgstr "" #. Tag: term @@ -197,7 +279,9 @@ msgstr "" #. Tag: para #: using-d-i.xml:193 #, no-c-format -msgid "Presents a list of Debian archive mirrors. The user may choose the source of his installation packages." +msgid "" +"Presents a list of Debian archive mirrors. The user may choose the source of " +"his installation packages." msgstr "" #. Tag: term @@ -209,7 +293,9 @@ msgstr "" #. Tag: para #: using-d-i.xml:202 #, no-c-format -msgid "Checks integrity of a CD-ROM. This way, the user may assure him/herself that the installation CD-ROM was not corrupted." +msgid "" +"Checks integrity of a CD-ROM. This way, the user may assure him/herself that " +"the installation CD-ROM was not corrupted." msgstr "" #. Tag: term @@ -221,7 +307,10 @@ msgstr "" #. Tag: para #: using-d-i.xml:211 #, no-c-format -msgid "Lowmem tries to detect systems with low memory and then does various tricks to remove unnecessary parts of &d-i; from the memory (at the cost of some features)." +msgid "" +"Lowmem tries to detect systems with low memory and then does various tricks " +"to remove unnecessary parts of &d-i; from the memory (at the cost of some " +"features)." msgstr "" #. Tag: term @@ -233,7 +322,9 @@ msgstr "" #. Tag: para #: using-d-i.xml:221 #, no-c-format -msgid "Anna's Not Nearly APT. Installs packages which have been retrieved from the chosen mirror or CD." +msgid "" +"Anna's Not Nearly APT. Installs packages which have been retrieved from the " +"chosen mirror or CD." msgstr "" #. Tag: term @@ -245,7 +336,9 @@ msgstr "" #. Tag: para #: using-d-i.xml:230 #, no-c-format -msgid "Updates the system clock and determines whether the clock is set to UTC or not." +msgid "" +"Updates the system clock and determines whether the clock is set to UTC or " +"not." msgstr "" #. Tag: term @@ -269,7 +362,11 @@ msgstr "" #. Tag: para #: using-d-i.xml:247 #, no-c-format -msgid "Allows the user to partition disks attached to the system, create file systems on the selected partitions, and attach them to the mountpoints. Included are also interesting features like a fully automatic mode or LVM support. This is the preferred partitioning tool in Debian." +msgid "" +"Allows the user to partition disks attached to the system, create file " +"systems on the selected partitions, and attach them to the mountpoints. " +"Included are also interesting features like a fully automatic mode or LVM " +"support. This is the preferred partitioning tool in Debian." msgstr "" #. Tag: term @@ -281,7 +378,9 @@ msgstr "" #. Tag: para #: using-d-i.xml:259 #, no-c-format -msgid "Allows the user to partition disks attached to the system. A partitioning program appropriate to your computer's architecture is chosen." +msgid "" +"Allows the user to partition disks attached to the system. A partitioning " +"program appropriate to your computer's architecture is chosen." msgstr "" #. Tag: term @@ -293,7 +392,9 @@ msgstr "" #. Tag: para #: using-d-i.xml:269 #, no-c-format -msgid "Displays a list of partitions, and creates file systems on the selected partitions according to user instructions." +msgid "" +"Displays a list of partitions, and creates file systems on the selected " +"partitions according to user instructions." msgstr "" #. Tag: term @@ -305,7 +406,9 @@ msgstr "" #. Tag: para #: using-d-i.xml:278 #, no-c-format -msgid "Helps the user with the configuration of the <firstterm>LVM</firstterm> (Logical Volume Manager)." +msgid "" +"Helps the user with the configuration of the <firstterm>LVM</firstterm> " +"(Logical Volume Manager)." msgstr "" #. Tag: term @@ -317,7 +420,10 @@ msgstr "" #. Tag: para #: using-d-i.xml:287 #, no-c-format -msgid "Allows the user to setup Software <firstterm>RAID</firstterm> (Redundant Array of Inexpensive Disks). This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards." +msgid "" +"Allows the user to setup Software <firstterm>RAID</firstterm> (Redundant " +"Array of Inexpensive Disks). This Software RAID is usually superior to the " +"cheap IDE (pseudo hardware) RAID controllers found on newer motherboards." msgstr "" #. Tag: term @@ -329,7 +435,9 @@ msgstr "" #. Tag: para #: using-d-i.xml:298 #, no-c-format -msgid "Installs the most basic set of packages which would allow the computer to operate under Linux when rebooted." +msgid "" +"Installs the most basic set of packages which would allow the computer to " +"operate under Linux when rebooted." msgstr "" #. Tag: term @@ -353,7 +461,9 @@ msgstr "" #. Tag: para #: using-d-i.xml:315 #, no-c-format -msgid "Configures apt, mostly automatically, based on what media the installer is running from." +msgid "" +"Configures apt, mostly automatically, based on what media the installer is " +"running from." msgstr "" #. Tag: term @@ -365,7 +475,9 @@ msgstr "" #. Tag: para #: using-d-i.xml:324 #, no-c-format -msgid "Uses <classname>tasksel</classname> to select and install additional software." +msgid "" +"Uses <classname>tasksel</classname> to select and install additional " +"software." msgstr "" #. Tag: term @@ -377,7 +489,12 @@ msgstr "" #. Tag: para #: using-d-i.xml:332 #, no-c-format -msgid "Detects currently installed operating systems on the computer and passes this information to the bootloader-installer, which may offer you an ability to add discovered operating systems to the bootloader's start menu. This way the user could easily choose at the boot time which operating system to start." +msgid "" +"Detects currently installed operating systems on the computer and passes " +"this information to the bootloader-installer, which may offer you an ability " +"to add discovered operating systems to the bootloader's start menu. This way " +"the user could easily choose at the boot time which operating system to " +"start." msgstr "" #. Tag: term @@ -389,7 +506,11 @@ msgstr "" #. Tag: para #: using-d-i.xml:344 #, no-c-format -msgid "The various bootloader installers each install a boot loader program on the hard disk, which is necessary for the computer to start up using Linux without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots." +msgid "" +"The various bootloader installers each install a boot loader program on the " +"hard disk, which is necessary for the computer to start up using Linux " +"without using a floppy or CD-ROM. Many boot loaders allow the user to choose " +"an alternate operating system each time the computer boots." msgstr "" #. Tag: term @@ -401,7 +522,8 @@ msgstr "" #. Tag: para #: using-d-i.xml:355 #, no-c-format -msgid "Allows the user to execute a shell from the menu, or in the second console." +msgid "" +"Allows the user to execute a shell from the menu, or in the second console." msgstr "" #. Tag: term @@ -413,7 +535,10 @@ msgstr "" #. Tag: para #: using-d-i.xml:364 #, no-c-format -msgid "Provides a way for the user to record information on a floppy disk, network, hard disk, or other media when trouble is encountered, in order to accurately report installer software problems to Debian developers later." +msgid "" +"Provides a way for the user to record information on a floppy disk, network, " +"hard disk, or other media when trouble is encountered, in order to " +"accurately report installer software problems to Debian developers later." msgstr "" #. Tag: title @@ -425,7 +550,13 @@ msgstr "" #. Tag: para #: using-d-i.xml:383 #, no-c-format -msgid "In this section we will describe each installer component in detail. The components have been grouped into stages that should be recognizable for users. They are presented in the order they appear during the install. Note that not all modules will be used for every installation; which modules are actually used depends on the installation method you use and on your hardware." +msgid "" +"In this section we will describe each installer component in detail. The " +"components have been grouped into stages that should be recognizable for " +"users. They are presented in the order they appear during the install. Note " +"that not all modules will be used for every installation; which modules are " +"actually used depends on the installation method you use and on your " +"hardware." msgstr "" #. Tag: title @@ -437,13 +568,27 @@ msgstr "" #. Tag: para #: using-d-i.xml:396 #, no-c-format -msgid "Let's assume the Debian Installer has booted and you are facing its first screen. At this time, the capabilities of &d-i; are still quite limited. It doesn't know much about your hardware, preferred language, or even the task it should perform. Don't worry. Because &d-i; is quite clever, it can automatically probe your hardware, locate the rest of its components and upgrade itself to a capable installation system. However, you still need to help &d-i; with some information it can't determine automatically (like selecting your preferred language, keyboard layout or desired network mirror)." +msgid "" +"Let's assume the Debian Installer has booted and you are facing its first " +"screen. At this time, the capabilities of &d-i; are still quite limited. It " +"doesn't know much about your hardware, preferred language, or even the task " +"it should perform. Don't worry. Because &d-i; is quite clever, it can " +"automatically probe your hardware, locate the rest of its components and " +"upgrade itself to a capable installation system. However, you still need to " +"help &d-i; with some information it can't determine automatically (like " +"selecting your preferred language, keyboard layout or desired network " +"mirror)." msgstr "" #. Tag: para #: using-d-i.xml:409 #, no-c-format -msgid "You will notice that &d-i; performs <firstterm>hardware detection</firstterm> several times during this stage. The first time is targeted specifically at the hardware needed to load installer components (e.g. your CD-ROM or network card). As not all drivers may be available during this first run, hardware detection needs to be repeated later in the process." +msgid "" +"You will notice that &d-i; performs <firstterm>hardware detection</" +"firstterm> several times during this stage. The first time is targeted " +"specifically at the hardware needed to load installer components (e.g. your " +"CD-ROM or network card). As not all drivers may be available during this " +"first run, hardware detection needs to be repeated later in the process." msgstr "" #. Tag: title @@ -455,43 +600,75 @@ msgstr "" #. Tag: para #: using-d-i.xml:426 #, no-c-format -msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian; on your system." +msgid "" +"One of the first things &d-i; does, is to check available memory. If the " +"available memory is limited, this component will make some changes in the " +"installation process which hopefully will allow you to install &debian; on " +"your system." msgstr "" #. Tag: para #: using-d-i.xml:433 #, no-c-format -msgid "The first measure taken to reduce memory consumption by the installer is to disable translations, which means that the installation can only be done in English. Of course, you can still localize the installed system after the installation has completed." +msgid "" +"The first measure taken to reduce memory consumption by the installer is to " +"disable translations, which means that the installation can only be done in " +"English. Of course, you can still localize the installed system after the " +"installation has completed." msgstr "" #. Tag: para #: using-d-i.xml:440 #, no-c-format -msgid "If that is not sufficient, the installer will further reduce memory consumption by loading only those components essential to complete a basic installation. This reduces the functionality of the installation system. You will be given the opportunity to load additional components manually, but you should be aware that each component you select will use additional memory and thus may cause the installation to fail." +msgid "" +"If that is not sufficient, the installer will further reduce memory " +"consumption by loading only those components essential to complete a basic " +"installation. This reduces the functionality of the installation system. You " +"will be given the opportunity to load additional components manually, but " +"you should be aware that each component you select will use additional " +"memory and thus may cause the installation to fail." msgstr "" #. Tag: para #: using-d-i.xml:449 #, no-c-format -msgid "If the installer runs in low memory mode, it is recommended to create a relatively large swap partition (64–128MB). The swap partition will be used as virtual memory and thus increases the amount of memory available to the system. The installer will activate the swap partition as early as possible in the installation process. Note that heavy use of swap will reduce performance of your system and may lead to high disk activity." +msgid "" +"If the installer runs in low memory mode, it is recommended to create a " +"relatively large swap partition (64–128MB). The swap partition will be " +"used as virtual memory and thus increases the amount of memory available to " +"the system. The installer will activate the swap partition as early as " +"possible in the installation process. Note that heavy use of swap will " +"reduce performance of your system and may lead to high disk activity." msgstr "" #. Tag: para #: using-d-i.xml:459 #, no-c-format -msgid "Despite these measures, it is still possible that your system freezes, that unexpected errors occur or that processes are killed by the kernel because the system runs out of memory (which will result in <quote>Out of memory</quote> messages on VT4 and in the syslog)." +msgid "" +"Despite these measures, it is still possible that your system freezes, that " +"unexpected errors occur or that processes are killed by the kernel because " +"the system runs out of memory (which will result in <quote>Out of memory</" +"quote> messages on VT4 and in the syslog)." msgstr "" #. Tag: para #: using-d-i.xml:466 #, no-c-format -msgid "For example, it has been reported that creating a big ext3 file system fails in low memory mode when there is insufficient swap space. If a larger swap doesn't help, try creating the file system as ext2 (which is an essential component of the installer) instead. It is possible to change an ext2 partition to ext3 after the installation." +msgid "" +"For example, it has been reported that creating a big ext3 file system fails " +"in low memory mode when there is insufficient swap space. If a larger swap " +"doesn't help, try creating the file system as ext2 (which is an essential " +"component of the installer) instead. It is possible to change an ext2 " +"partition to ext3 after the installation." msgstr "" #. Tag: para #: using-d-i.xml:474 #, no-c-format -msgid "It is possible to force the installer to use a higher lowmem level than the one based on available memory by using the boot parameter <quote>lowmem</quote> as described in <xref linkend=\"installer-args\"/>." +msgid "" +"It is possible to force the installer to use a higher lowmem level than the " +"one based on available memory by using the boot parameter <quote>lowmem</" +"quote> as described in <xref linkend=\"installer-args\"/>." msgstr "" #. Tag: title @@ -503,37 +680,70 @@ msgstr "" #. Tag: para #: using-d-i.xml:491 #, no-c-format -msgid "In most cases the first questions you will be asked concern the selection of localization options to be used both for the installation and for the installed system. The localization options consist of language, country and locales." +msgid "" +"In most cases the first questions you will be asked concern the selection of " +"localization options to be used both for the installation and for the " +"installed system. The localization options consist of language, country and " +"locales." msgstr "" #. Tag: para #: using-d-i.xml:498 #, no-c-format -msgid "The language you choose will be used for the rest of the installation process, provided a translation of the different dialogs is available. If no valid translation is available for the selected language, the installer will default to English." +msgid "" +"The language you choose will be used for the rest of the installation " +"process, provided a translation of the different dialogs is available. If no " +"valid translation is available for the selected language, the installer will " +"default to English." msgstr "" #. Tag: para #: using-d-i.xml:505 #, no-c-format -msgid "The selected country will be used later in the installation process to pick the default timezone and a Debian mirror appropriate for your geographic location. Language and country together will be used to set the default locale for your system and to help select your keyboard." +msgid "" +"The selected country will be used later in the installation process to pick " +"the default timezone and a Debian mirror appropriate for your geographic " +"location. Language and country together will be used to set the default " +"locale for your system and to help select your keyboard." msgstr "" #. Tag: para #: using-d-i.xml:512 #, no-c-format -msgid "You will first be asked to select your preferred language. The language names are listed in both English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names. At the top of the list is an extra option that allows you to select the <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed." +msgid "" +"You will first be asked to select your preferred language. The language " +"names are listed in both English (left side) and in the language itself " +"(right side); the names on the right side are also shown in the proper " +"script for the language. The list is sorted on the English names. At the top " +"of the list is an extra option that allows you to select the <quote>C</" +"quote> locale instead of a language. Choosing the <quote>C</quote> locale " +"will result in the installation proceding in English; the installed system " +"will have no localization support as the <classname>locales</classname> " +"package will not be installed." msgstr "" #. Tag: para #: using-d-i.xml:524 #, no-c-format -msgid "If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will next be asked to select a country. If you choose <guimenuitem>Other</guimenuitem> at the bottom of the list, you will be presented with a list of all countries, grouped by continent. If the language has only one country associated with it, that country will be selected automatically." +msgid "" +"If you selected a language that is recognized as an official language for " +"more than one country<footnote> <para> In technical terms: where multiple " +"locales exist for that language with differing country codes. </para> </" +"footnote>, you will next be asked to select a country. If you choose " +"<guimenuitem>Other</guimenuitem> at the bottom of the list, you will be " +"presented with a list of all countries, grouped by continent. If the " +"language has only one country associated with it, that country will be " +"selected automatically." msgstr "" #. Tag: para #: using-d-i.xml:542 #, no-c-format -msgid "A default locale will be selected based on the selected language and country. If you are installing at medium or low priority, you will have the option of selecting a different default locale and of selecting additional locales to be generated for the installed system." +msgid "" +"A default locale will be selected based on the selected language and " +"country. If you are installing at medium or low priority, you will have the " +"option of selecting a different default locale and of selecting additional " +"locales to be generated for the installed system." msgstr "" #. Tag: title @@ -545,25 +755,47 @@ msgstr "" #. Tag: para #: using-d-i.xml:559 #, no-c-format -msgid "Keyboards are often tailored to the characters used in a language. Select a layout that conforms to the keyboard you are using, or select something close if the keyboard layout you want isn't represented. Once the system installation is complete, you'll be able to select a keyboard layout from a wider range of choices (run <command>kbdconfig</command> as root after you have completed the installation)." +msgid "" +"Keyboards are often tailored to the characters used in a language. Select a " +"layout that conforms to the keyboard you are using, or select something " +"close if the keyboard layout you want isn't represented. Once the system " +"installation is complete, you'll be able to select a keyboard layout from a " +"wider range of choices (run <command>kbdconfig</command> as root after you " +"have completed the installation)." msgstr "" #. Tag: para #: using-d-i.xml:569 #, no-c-format -msgid "Move the highlight to the keyboard selection you desire and press &enterkey;. Use the arrow keys to move the highlight — they are in the same place in all national language keyboard layouts, so they are independent of the keyboard configuration. An 'extended' keyboard is one with <keycap>F1</keycap> through <keycap>F10</keycap> keys along the top row." +msgid "" +"Move the highlight to the keyboard selection you desire and press " +"&enterkey;. Use the arrow keys to move the highlight — they are in the " +"same place in all national language keyboard layouts, so they are " +"independent of the keyboard configuration. An 'extended' keyboard is one " +"with <keycap>F1</keycap> through <keycap>F10</keycap> keys along the top row." msgstr "" #. Tag: para #: using-d-i.xml:578 #, no-c-format -msgid "On DECstations there is currently no loadable keymap available, so you have to skip the keyboard selection and keep the default kernel keymap (LK201 US). This may change in the future as it depends on further Linux/MIPS kernel development." +msgid "" +"On DECstations there is currently no loadable keymap available, so you have " +"to skip the keyboard selection and keep the default kernel keymap (LK201 " +"US). This may change in the future as it depends on further Linux/MIPS " +"kernel development." msgstr "" #. Tag: para #: using-d-i.xml:585 #, no-c-format -msgid "There are two keyboard layouts for US keyboards; the qwerty/mac-usb-us (Apple USB) layout will place the Alt function on the <keycap>Command/Apple</keycap> key (in the keyboard position next to the <keycap>space</keycap> key similar to <keycap>Alt</keycap> on PC keyboards), while the qwerty/us (Standard) layout will place the Alt function on the <keycap>Option</keycap> key (engraved with 'alt' on most Mac keyboards). In other respects the two layouts are similar." +msgid "" +"There are two keyboard layouts for US keyboards; the qwerty/mac-usb-us " +"(Apple USB) layout will place the Alt function on the <keycap>Command/Apple</" +"keycap> key (in the keyboard position next to the <keycap>space</keycap> key " +"similar to <keycap>Alt</keycap> on PC keyboards), while the qwerty/us " +"(Standard) layout will place the Alt function on the <keycap>Option</keycap> " +"key (engraved with 'alt' on most Mac keyboards). In other respects the two " +"layouts are similar." msgstr "" #. Tag: title @@ -575,25 +807,51 @@ msgstr "" #. Tag: para #: using-d-i.xml:616 #, no-c-format -msgid "When installing via the <emphasis>hd-media</emphasis> method, there will be a moment where you need to find and mount the Debian Installer iso image in order to get the rest of the installation files. The component <command>iso-scan</command> does exactly this." +msgid "" +"When installing via the <emphasis>hd-media</emphasis> method, there will be " +"a moment where you need to find and mount the Debian Installer iso image in " +"order to get the rest of the installation files. The component <command>iso-" +"scan</command> does exactly this." msgstr "" #. Tag: para #: using-d-i.xml:623 #, no-c-format -msgid "At first, <command>iso-scan</command> automatically mounts all block devices (e.g. partitions) which have some known filesystem on them and sequentially searches for filenames ending with <filename>.iso</filename> (or <filename>.ISO</filename> for that matter). Beware that the first attempt scans only files in the root directory and in the first level of subdirectories (i.e. it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, <filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not <filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). After an iso image has been found, <command>iso-scan</command> checks its content to determine if the image is a valid Debian iso image or not. In the former case we are done, in the latter <command>iso-scan</command> seeks for another image." +msgid "" +"At first, <command>iso-scan</command> automatically mounts all block devices " +"(e.g. partitions) which have some known filesystem on them and sequentially " +"searches for filenames ending with <filename>.iso</filename> (or <filename>." +"ISO</filename> for that matter). Beware that the first attempt scans only " +"files in the root directory and in the first level of subdirectories (i.e. " +"it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, " +"<filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not " +"<filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). " +"After an iso image has been found, <command>iso-scan</command> checks its " +"content to determine if the image is a valid Debian iso image or not. In the " +"former case we are done, in the latter <command>iso-scan</command> seeks for " +"another image." msgstr "" #. Tag: para #: using-d-i.xml:640 #, no-c-format -msgid "In case the previous attempt to find an installer iso image fails, <command>iso-scan</command> will ask you whether you would like to perform a more thorough search. This pass doesn't just look into the topmost directories, but really traverses whole filesystem." +msgid "" +"In case the previous attempt to find an installer iso image fails, " +"<command>iso-scan</command> will ask you whether you would like to perform a " +"more thorough search. This pass doesn't just look into the topmost " +"directories, but really traverses whole filesystem." msgstr "" #. Tag: para #: using-d-i.xml:647 #, no-c-format -msgid "If <command>iso-scan</command> does not discover your installer iso image, reboot back to your original operating system and check if the image is named correctly (ending in <filename>.iso</filename>), if it is placed on a filesystem recognizable by &d-i;, and if it is not corrupted (verify the checksum). Experienced Unix users could do this without rebooting on the second console." +msgid "" +"If <command>iso-scan</command> does not discover your installer iso image, " +"reboot back to your original operating system and check if the image is " +"named correctly (ending in <filename>.iso</filename>), if it is placed on a " +"filesystem recognizable by &d-i;, and if it is not corrupted (verify the " +"checksum). Experienced Unix users could do this without rebooting on the " +"second console." msgstr "" #. Tag: title @@ -605,25 +863,58 @@ msgstr "" #. Tag: para #: using-d-i.xml:670 #, no-c-format -msgid "As you enter this step, if the system detects that you have more than one network device, you'll be asked to choose which device will be your <emphasis>primary</emphasis> network interface, i.e. the one which you want to use for installation. The other interfaces won't be configured at this time. You may configure additional interfaces after installation is complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> man page." +msgid "" +"As you enter this step, if the system detects that you have more than one " +"network device, you'll be asked to choose which device will be your " +"<emphasis>primary</emphasis> network interface, i.e. the one which you want " +"to use for installation. The other interfaces won't be configured at this " +"time. You may configure additional interfaces after installation is " +"complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> " +"<manvolnum>5</manvolnum> </citerefentry> man page." msgstr "" #. Tag: para #: using-d-i.xml:681 #, no-c-format -msgid "By default, &d-i; tries to configure your computer's network automatically via DHCP. If the DHCP probe succeeds, you are done. If the probe fails, it may be caused by many factors ranging from unplugged network cable, to a misconfigured DHCP setup. Or maybe you don't have a DHCP server in your local network at all. For further explanation, check the error messages on the fourth console. In any case, you will be asked if you want to retry, or if you want to perform a manual setup. DHCP servers are sometimes really slow in their responses, so if you are sure everything is in place, try again." +msgid "" +"By default, &d-i; tries to configure your computer's network automatically " +"via DHCP. If the DHCP probe succeeds, you are done. If the probe fails, it " +"may be caused by many factors ranging from unplugged network cable, to a " +"misconfigured DHCP setup. Or maybe you don't have a DHCP server in your " +"local network at all. For further explanation, check the error messages on " +"the fourth console. In any case, you will be asked if you want to retry, or " +"if you want to perform a manual setup. DHCP servers are sometimes really " +"slow in their responses, so if you are sure everything is in place, try " +"again." msgstr "" #. Tag: para #: using-d-i.xml:693 #, no-c-format -msgid "The manual network setup in turn asks you a number of questions about your network, notably <computeroutput>IP address</computeroutput>, <computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</computeroutput>, <computeroutput>Name server addresses</computeroutput>, and a <computeroutput>Hostname</computeroutput>. Moreover, if you have a wireless network interface, you will be asked to provide your <computeroutput>Wireless ESSID</computeroutput> and a <computeroutput>WEP key</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/>." +msgid "" +"The manual network setup in turn asks you a number of questions about your " +"network, notably <computeroutput>IP address</computeroutput>, " +"<computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</" +"computeroutput>, <computeroutput>Name server addresses</computeroutput>, and " +"a <computeroutput>Hostname</computeroutput>. Moreover, if you have a " +"wireless network interface, you will be asked to provide your " +"<computeroutput>Wireless ESSID</computeroutput> and a <computeroutput>WEP " +"key</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/" +">." msgstr "" #. Tag: para #: using-d-i.xml:707 #, no-c-format -msgid "Some technical details you might, or might not, find handy: the program assumes the network IP address is the bitwise-AND of your system's IP address and your netmask. The default broadcast address is calculated as the bitwise OR of your system's IP address with the bitwise negation of the netmask. It will also guess your gateway. If you can't find any of these answers, use the offered defaults — if necessary, you can change them by editing <filename>/etc/network/interfaces</filename> once the system has been installed." +msgid "" +"Some technical details you might, or might not, find handy: the program " +"assumes the network IP address is the bitwise-AND of your system's IP " +"address and your netmask. The default broadcast address is calculated as the " +"bitwise OR of your system's IP address with the bitwise negation of the " +"netmask. It will also guess your gateway. If you can't find any of these " +"answers, use the offered defaults — if necessary, you can change them " +"by editing <filename>/etc/network/interfaces</filename> once the system has " +"been installed." msgstr "" #. Tag: title @@ -635,25 +926,41 @@ msgstr "" #. Tag: para #: using-d-i.xml:754 #, no-c-format -msgid "The installer will first attempt to connect to a time server on the Internet (using the <firstterm>NTP</firstterm> protocol) in order to correctly set the system time. If this does not succeed, the installer will assume the time and date obtained from the system clock when the installation system was booted are correct. It is not possible to manually set the system time during the installation process." +msgid "" +"The installer will first attempt to connect to a time server on the Internet " +"(using the <firstterm>NTP</firstterm> protocol) in order to correctly set " +"the system time. If this does not succeed, the installer will assume the " +"time and date obtained from the system clock when the installation system " +"was booted are correct. It is not possible to manually set the system time " +"during the installation process." msgstr "" #. Tag: para #: using-d-i.xml:772 #, no-c-format -msgid "Depending on the location selected earlier in the installation process, you may be shown a list of timezones relevant for that location. If your location has only one time zone, you will not be asked anything and the system will assume that time zone." +msgid "" +"Depending on the location selected earlier in the installation process, you " +"may be shown a list of timezones relevant for that location. If your " +"location has only one time zone, you will not be asked anything and the " +"system will assume that time zone." msgstr "" #. Tag: para #: using-d-i.xml:779 #, no-c-format -msgid "If for some reason you wish to set a time zone for the installed system that does <emphasis>not</emphasis> match the selected location, there are two options." +msgid "" +"If for some reason you wish to set a time zone for the installed system that " +"does <emphasis>not</emphasis> match the selected location, there are two " +"options." msgstr "" #. Tag: para #: using-d-i.xml:790 #, no-c-format -msgid "The simplest option is to just select a different timezone after the installation has been completed and you've booted into the new system. The command to do this is:" +msgid "" +"The simplest option is to just select a different timezone after the " +"installation has been completed and you've booted into the new system. The " +"command to do this is:" msgstr "" #. Tag: screen @@ -665,13 +972,19 @@ msgstr "" #. Tag: para #: using-d-i.xml:802 #, no-c-format -msgid "Alternatively, the time zone can be set at the very start of the installation by passing the parameter <userinput>time/zone=<replaceable>value</replaceable></userinput> when you boot the installation system. The value should of course be a valid time zone, for example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>." +msgid "" +"Alternatively, the time zone can be set at the very start of the " +"installation by passing the parameter <userinput>time/" +"zone=<replaceable>value</replaceable></userinput> when you boot the " +"installation system. The value should of course be a valid time zone, for " +"example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>." msgstr "" #. Tag: para #: using-d-i.xml:816 #, no-c-format -msgid "For automated installations the time zone can also be set using preseeding." +msgid "" +"For automated installations the time zone can also be set using preseeding." msgstr "" #. Tag: title @@ -683,28 +996,45 @@ msgstr "" #. Tag: para #: using-d-i.xml:830 #, no-c-format -msgid "At this time, after hardware detection has been executed a final time, &d-i; should be at its full strength, customized for the user's needs and ready to do some real work. As the title of this section indicates, the main task of the next few components lies in partitioning your disks, creating filesystems, assigning mountpoints and optionally configuring closely related options like RAID, LVM or encrypted devices." +msgid "" +"At this time, after hardware detection has been executed a final time, &d-i; " +"should be at its full strength, customized for the user's needs and ready to " +"do some real work. As the title of this section indicates, the main task of " +"the next few components lies in partitioning your disks, creating " +"filesystems, assigning mountpoints and optionally configuring closely " +"related options like RAID, LVM or encrypted devices." msgstr "" #. Tag: para #: using-d-i.xml:851 #, no-c-format -msgid "If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>." +msgid "" +"If you are uncomfortable with partitioning, or just want to know more " +"details, see <xref linkend=\"partitioning\"/>." msgstr "" #. Tag: para #: using-d-i.xml:857 #, no-c-format msgid "" - "If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to <quote>zero</quote> the first few sectors of the drive: <informalexample><screen>\n" - "# dd if=/dev/zero of=/dev/hd<replaceable>X</replaceable> bs=512 count=2; sync\n" - "</screen></informalexample> Note that this will make any existing data on that disk inaccessible." +"If a hard disk has previously used under Solaris, the partitioner may not " +"detect the size of the drive correctly. Creating a new partition table does " +"not fix this issue. What does help, is to <quote>zero</quote> the first few " +"sectors of the drive: <informalexample><screen>\n" +"# dd if=/dev/zero of=/dev/hd<replaceable>X</replaceable> bs=512 count=2; " +"sync\n" +"</screen></informalexample> Note that this will make any existing data on " +"that disk inaccessible." msgstr "" #. Tag: para #: using-d-i.xml:870 #, no-c-format -msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu." +msgid "" +"First you will be given the opportunity to automatically partition either an " +"entire drive, or available free space on a drive. This is also called " +"<quote>guided</quote> partitioning. If you do not want to autopartition, " +"choose <guimenuitem>Manual</guimenuitem> from the menu." msgstr "" #. Tag: title @@ -716,49 +1046,89 @@ msgstr "" #. Tag: para #: using-d-i.xml:881 #, no-c-format -msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>." +msgid "" +"If you choose guided partitioning, you may have three options: to create " +"partitions directly on the hard disk (classic method), or to create them " +"using Logical Volume Management (LVM), or to create them using encrypted " +"LVM<footnote> <para> The installer will encrypt the LVM volume group using a " +"256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> " +"support. </para> </footnote>." msgstr "" #. Tag: para #: using-d-i.xml:896 #, no-c-format -msgid "The option to use (encrypted) LVM may not be available on all architectures." +msgid "" +"The option to use (encrypted) LVM may not be available on all architectures." msgstr "" #. Tag: para #: using-d-i.xml:901 #, no-c-format -msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data." +msgid "" +"When using LVM or encrypted LVM, the installer will create most partitions " +"inside one big partition; the advantage of this method is that partitions " +"inside this big partition can be resized relatively easily later. In the " +"case of encrypted LVM the big partition will not be readable without knowing " +"a special key phrase, thus providing extra security of your (personal) data." msgstr "" #. Tag: para #: using-d-i.xml:910 #, no-c-format -msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk." +msgid "" +"When using encrypted LVM, the installer will also automatically erase the " +"disk by writing random data to it. This further improves security (as it " +"makes it impossible to tell which parts of the disk are in use and also " +"makes sure that any traces of previous installations are erased), but may " +"take some time depending on the size of your disk." msgstr "" #. Tag: para #: using-d-i.xml:919 #, no-c-format -msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk." +msgid "" +"If you choose guided partitioning using LVM or encrypted LVM, some changes " +"in the partition table will need to be written to the selected disk while " +"LVM is being set up. These changes effectively erase all data that is " +"currently on the selected hard disk and you will not be able to undo them " +"later. However, the installer will ask you to confirm these changes before " +"they are written to disk." msgstr "" #. Tag: para #: using-d-i.xml:929 #, no-c-format -msgid "If you choose guided partitioning (either classic or using (encrypted) LVM) for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them." +msgid "" +"If you choose guided partitioning (either classic or using (encrypted) LVM) " +"for a whole disk, you will first be asked to select the disk you want to " +"use. Check that all your disks are listed and, if you have several disks, " +"make sure you select the correct one. The order they are listed in may " +"differ from what you are used to. The size of the disks may help to identify " +"them." msgstr "" #. Tag: para #: using-d-i.xml:938 #, no-c-format -msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible." +msgid "" +"Any data on the disk you select will eventually be lost, but you will always " +"be asked to confirm any changes before they are written to the disk. If you " +"have selected the classic method of partitioning, you will be able to undo " +"any changes right until the end; when using (encrypted) LVM this is not " +"possible." msgstr "" #. Tag: para #: using-d-i.xml:946 #, no-c-format -msgid "Next, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail." +msgid "" +"Next, you will be able to choose from the schemes listed in the table below. " +"All schemes have their pros and cons, some of which are discussed in <xref " +"linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in " +"mind that guided partitioning needs a certain minimal amount of free space " +"to operate with. If you don't give it at least about 1GB of space (depends " +"on chosen scheme), guided partitioning will fail." msgstr "" #. Tag: entry @@ -830,60 +1200,88 @@ msgstr "" #. Tag: entry #: using-d-i.xml:982 #, no-c-format -msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap" +msgid "" +"<filename>/</filename>, <filename>/home</filename>, <filename>/usr</" +"filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap" msgstr "" #. Tag: para #: using-d-i.xml:991 #, no-c-format -msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, including the swap partition, will be created inside the LVM partition." +msgid "" +"If you choose guided partitioning using (encrypted) LVM, the installer will " +"also create a separate <filename>/boot</filename> partition. The other " +"partitions, including the swap partition, will be created inside the LVM " +"partition." msgstr "" #. Tag: para #: using-d-i.xml:997 #, no-c-format -msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition." +msgid "" +"If you choose guided partitioning for your IA-64 system, there will be an " +"additional partition, formatted as a FAT16 bootable filesystem, for the EFI " +"boot loader. There is also an additional menu item in the formatting menu to " +"manually set up a partition as an EFI boot partition." msgstr "" #. Tag: para #: using-d-i.xml:1005 #, no-c-format -msgid "If you choose guided partitioning for your Alpha system, an additional, unformatted partition will be allocated at the beginning of your disk to reserve this space for the aboot boot loader." +msgid "" +"If you choose guided partitioning for your Alpha system, an additional, " +"unformatted partition will be allocated at the beginning of your disk to " +"reserve this space for the aboot boot loader." msgstr "" #. Tag: para #: using-d-i.xml:1011 #, no-c-format -msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted." +msgid "" +"After selecting a scheme, the next screen will show your new partition " +"table, including information on whether and how partitions will be formatted " +"and where they will be mounted." msgstr "" #. Tag: para #: using-d-i.xml:1017 #, no-c-format msgid "" - "The list of partitions might look like this: <informalexample><screen>\n" - " IDE1 master (hda) - 6.4 GB WDC AC36400L\n" - " #1 primary 16.4 MB B f ext2 /boot\n" - " #2 primary 551.0 MB swap swap\n" - " #3 primary 5.8 GB ntfs\n" - " pri/log 8.2 MB FREE SPACE\n" - "\n" - " IDE1 slave (hdb) - 80.0 GB ST380021A\n" - " #1 primary 15.9 MB ext3\n" - " #2 primary 996.0 MB fat16\n" - " #3 primary 3.9 GB xfs /home\n" - " #5 logical 6.0 GB f ext3 /\n" - " #6 logical 1.0 GB f ext3 /var\n" - " #7 logical 498.8 MB ext3\n" - " #8 logical 551.5 MB swap swap\n" - " #9 logical 65.8 GB ext2\n" - "</screen></informalexample> This example shows two IDE harddrives divided into several partitions; the first disk has some free space. Each partition line consists of the partition number, its type, size, optional flags, file system, and mountpoint (if any). Note: this particular setup cannot be created using guided partitioning but it does show possible variation that can be achieved using manual partitioning." +"The list of partitions might look like this: <informalexample><screen>\n" +" IDE1 master (hda) - 6.4 GB WDC AC36400L\n" +" #1 primary 16.4 MB B f ext2 /boot\n" +" #2 primary 551.0 MB swap swap\n" +" #3 primary 5.8 GB ntfs\n" +" pri/log 8.2 MB FREE SPACE\n" +"\n" +" IDE1 slave (hdb) - 80.0 GB ST380021A\n" +" #1 primary 15.9 MB ext3\n" +" #2 primary 996.0 MB fat16\n" +" #3 primary 3.9 GB xfs /home\n" +" #5 logical 6.0 GB f ext3 /\n" +" #6 logical 1.0 GB f ext3 /var\n" +" #7 logical 498.8 MB ext3\n" +" #8 logical 551.5 MB swap swap\n" +" #9 logical 65.8 GB ext2\n" +"</screen></informalexample> This example shows two IDE harddrives divided " +"into several partitions; the first disk has some free space. Each partition " +"line consists of the partition number, its type, size, optional flags, file " +"system, and mountpoint (if any). Note: this particular setup cannot be " +"created using guided partitioning but it does show possible variation that " +"can be achieved using manual partitioning." msgstr "" #. Tag: para #: using-d-i.xml:1030 #, no-c-format -msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning." +msgid "" +"This concludes the guided partitioning. If you are satisfied with the " +"generated partition table, you can choose <guimenuitem>Finish partitioning " +"and write changes to disk</guimenuitem> from the menu to implement the new " +"partition table (as described at the end of this section). If you are not " +"happy, you can choose to <guimenuitem>Undo changes to partitions</" +"guimenuitem> and run guided partitioning again, or modify the proposed " +"changes as described below for manual partitioning." msgstr "" #. Tag: title @@ -895,49 +1293,100 @@ msgstr "" #. Tag: para #: using-d-i.xml:1045 #, no-c-format -msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually setup your partition table and the usage of partitions by your new Debian system will be covered in the remainder of this section." +msgid "" +"A similar screen to the one shown just above will be displayed if you choose " +"manual partitioning except that your existing partition table will be shown " +"and without the mount points. How to manually setup your partition table and " +"the usage of partitions by your new Debian system will be covered in the " +"remainder of this section." msgstr "" #. Tag: para #: using-d-i.xml:1053 #, no-c-format -msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk." +msgid "" +"If you select a pristine disk which has neither partitions nor free space on " +"it, you will be asked if a new partition table should be created (this is " +"needed so you can create new partitions). After this, a new line entitled " +"<quote>FREE SPACE</quote> should appear in the table under the selected disk." msgstr "" #. Tag: para #: using-d-i.xml:1061 #, no-c-format -msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap, software RAID, LVM, an encrypted file system, or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem for this partition, including options to use the partition for swap, software RAID, LVM, or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen." +msgid "" +"If you select some free space, you will have the opportunity to create a new " +"partition. You will have to answer a quick series of questions about its " +"size, type (primary or logical), and location (beginning or end of the free " +"space). After this, you will be presented with a detailed overview of your " +"new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which " +"determines if the partition will have a file system on it, or be used for " +"swap, software RAID, LVM, an encrypted file system, or not be used at all. " +"Other settings include mountpoint, mount options, and bootable flag; which " +"settings are shown depends on how the partition is to be used. If you don't " +"like the preselected defaults, feel free to change them to your liking. E.g. " +"by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose a " +"different filesystem for this partition, including options to use the " +"partition for swap, software RAID, LVM, or not use it at all. Another nice " +"feature is the ability to copy data from an existing partition onto this " +"one. When you are satisfied with your new partition, select " +"<guimenuitem>Done setting up the partition</guimenuitem> and you will return " +"to <command>partman</command>'s main screen." msgstr "" #. Tag: para #: using-d-i.xml:1083 #, no-c-format -msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen as is used when creating a new partition, so you can change the same settings. One thing that may not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition." +msgid "" +"If you decide you want to change something about your partition, simply " +"select the partition, which will bring you to the partition configuration " +"menu. This is the same screen as is used when creating a new partition, so " +"you can change the same settings. One thing that may not be very obvious at " +"a first glance is that you can resize the partition by selecting the item " +"displaying the size of the partition. Filesystems known to work are at least " +"fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a " +"partition." msgstr "" #. Tag: para #: using-d-i.xml:1094 #, no-c-format -msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue." +msgid "" +"Be sure to create at least two partitions: one for the <emphasis>root</" +"emphasis> filesystem (which must be mounted as <filename>/</filename>) and " +"one for <emphasis>swap</emphasis>. If you forget to mount the root " +"filesystem, <command>partman</command> won't let you continue until you " +"correct this issue." msgstr "" #. Tag: para #: using-d-i.xml:1102 #, no-c-format -msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one." +msgid "" +"If you forget to select and format an EFI boot partition, <command>partman</" +"command> will detect this and will not let you continue until you allocate " +"one." msgstr "" #. Tag: para #: using-d-i.xml:1108 #, no-c-format -msgid "Capabilities of <command>partman</command> can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)." +msgid "" +"Capabilities of <command>partman</command> can be extended with installer " +"modules, but are dependent on your system's architecture. So if you can't " +"see all promised goodies, check if you have loaded all required modules (e." +"g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or " +"<filename>partman-lvm</filename>)." msgstr "" #. Tag: para #: using-d-i.xml:1116 #, no-c-format -msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested." +msgid "" +"After you are satisfied with partitioning, select <guimenuitem>Finish " +"partitioning and write changes to disk</guimenuitem> from the partitioning " +"menu. You will be presented with a summary of changes made to the disks and " +"asked to confirm that the filesystems should be created as requested." msgstr "" #. Tag: title @@ -949,19 +1398,66 @@ msgstr "" #. Tag: para #: using-d-i.xml:1145 #, no-c-format -msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct MD device even from partitions residing on single physical drive, but that won't bring you anything useful. </para></footnote> in your computer, you can use <command>mdcfg</command> to setup your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)." +msgid "" +"If you have more than one harddrive<footnote><para> To be honest, you can " +"construct MD device even from partitions residing on single physical drive, " +"but that won't bring you anything useful. </para></footnote> in your " +"computer, you can use <command>mdcfg</command> to setup your drives for " +"increased performance and/or better reliability of your data. The result is " +"called <firstterm>Multidisk Device</firstterm> (or after its most famous " +"variant <firstterm>software RAID</firstterm>)." msgstr "" #. Tag: para #: using-d-i.xml:1159 #, no-c-format -msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)." +msgid "" +"MD is basically a bunch of partitions located on different disks and " +"combined together to form a <emphasis>logical</emphasis> device. This device " +"can then be used like an ordinary partition (i.e. in <command>partman</" +"command> you can format it, assign a mountpoint, etc.)." msgstr "" #. Tag: para #: using-d-i.xml:1167 #, no-c-format -msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> </variablelist> To sum it up:" +msgid "" +"What benefits this brings depends on the type of MD device you are creating. " +"Currently supported are: <variablelist> <varlistentry> <term>RAID0</" +"term><listitem><para> Is mainly aimed at performance. RAID0 splits all " +"incoming data into <firstterm>stripes</firstterm> and distributes them " +"equally over each disk in the array. This can increase the speed of read/" +"write operations, but when one of the disks fails, you will lose " +"<emphasis>everything</emphasis> (part of the information is still on the " +"healthy disk(s), the other part <emphasis>was</emphasis> on the failed " +"disk). </para><para> The typical use for RAID0 is a partition for video " +"editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</" +"term><listitem><para> Is suitable for setups where reliability is the first " +"concern. It consists of several (usually two) equally-sized partitions where " +"every partition contains exactly the same data. This essentially means three " +"things. First, if one of your disks fails, you still have the data mirrored " +"on the remaining disks. Second, you can use only a fraction of the available " +"capacity (more precisely, it is the size of the smallest partition in the " +"RAID). Third, file-reads are load-balanced among the disks, which can " +"improve performance on a server, such as a file server, that tends to be " +"loaded with more disk reads than writes. </para><para> Optionally you can " +"have a spare disk in the array which will take the place of the failed disk " +"in the case of failure. </para></listitem> </varlistentry> <varlistentry> " +"<term>RAID5</term><listitem><para> Is a good compromise between speed, " +"reliability and data redundancy. RAID5 splits all incoming data into stripes " +"and distributes them equally on all but one disk (similar to RAID0). Unlike " +"RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which " +"gets written on the remaining disk. The parity disk is not static (that " +"would be called RAID4), but is changing periodically, so the parity " +"information is distributed equally on all disks. When one of the disks " +"fails, the missing part of information can be computed from remaining data " +"and its parity. RAID5 must consist of at least three active partitions. " +"Optionally you can have a spare disk in the array which will take the place " +"of the failed disk in the case of failure. </para><para> As you can see, " +"RAID5 has a similar degree of reliability to RAID1 while achieving less " +"redundancy. On the other hand, it might be a bit slower on write operations " +"than RAID0 due to computation of parity information. </para></listitem> </" +"varlistentry> </variablelist> To sum it up:" msgstr "" #. Tag: entry @@ -1057,67 +1553,119 @@ msgstr "" #. Tag: entry #: using-d-i.xml:1275 #, no-c-format -msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)" +msgid "" +"Size of the smallest partition multiplied by (number of devices in RAID " +"minus one)" msgstr "" #. Tag: para #: using-d-i.xml:1283 #, no-c-format -msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>." +msgid "" +"If you want to know more about Software RAID, have a look at <ulink url=" +"\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>." msgstr "" #. Tag: para #: using-d-i.xml:1288 #, no-c-format -msgid "To create a MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)" +msgid "" +"To create a MD device, you need to have the desired partitions it should " +"consist of marked for use in a RAID. (This is done in <command>partman</" +"command> in the <guimenu>Partition settings</guimenu> menu where you should " +"select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume " +"for RAID</guimenuitem> </menuchoice>.)" msgstr "" #. Tag: para #: using-d-i.xml:1297 #, no-c-format -msgid "Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for <filename>/boot</filename> when using RAID for the root (<filename>/</filename>) file system. Most boot loaders <phrase arch=\"x86\">(including lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</filename> can be an option." +msgid "" +"Make sure that the system can be booted with the partitioning scheme you are " +"planning. In general it will be necessary to create a separate file system " +"for <filename>/boot</filename> when using RAID for the root (<filename>/</" +"filename>) file system. Most boot loaders <phrase arch=\"x86\">(including " +"lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using " +"for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</" +"filename> can be an option." msgstr "" #. Tag: para #: using-d-i.xml:1309 #, no-c-format -msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) file system. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell." +msgid "" +"Support for MD is a relatively new addition to the installer. You may " +"experience problems for some RAID levels and in combination with some " +"bootloaders if you try to use MD for the root (<filename>/</filename>) file " +"system. For experienced users, it may be possible to work around some of " +"these problems by executing some configuration or installation steps " +"manually from a shell." msgstr "" #. Tag: para #: using-d-i.xml:1318 #, no-c-format -msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected." +msgid "" +"Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> " +"from the main <command>partman</command> menu. (The menu will only appear " +"after you mark at least one partition for use as <guimenuitem>physical " +"volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</" +"command> simply select <guimenuitem>Create MD device</guimenuitem>. You will " +"be presented with a list of supported types of MD devices, from which you " +"should choose one (e.g. RAID1). What follows depends on the type of MD you " +"selected." msgstr "" #. Tag: para #: using-d-i.xml:1331 #, no-c-format -msgid "RAID0 is simple — you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD." +msgid "" +"RAID0 is simple — you will be issued with the list of available RAID " +"partitions and your only task is to select the partitions which will form " +"the MD." msgstr "" #. Tag: para #: using-d-i.xml:1338 #, no-c-format -msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided few seconds ago. Don't worry. If you make a mistake and select different number of partitions, the &d-i; won't let you continue until you correct the issue." +msgid "" +"RAID1 is a bit more tricky. First, you will be asked to enter the number of " +"active devices and the number of spare devices which will form the MD. Next, " +"you need to select from the list of available RAID partitions those that " +"will be active and then those that will be spare. The count of selected " +"partitions must be equal to the number provided few seconds ago. Don't " +"worry. If you make a mistake and select different number of partitions, the " +"&d-i; won't let you continue until you correct the issue." msgstr "" #. Tag: para #: using-d-i.xml:1350 #, no-c-format -msgid "RAID5 has a similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions." +msgid "" +"RAID5 has a similar setup procedure as RAID1 with the exception that you " +"need to use at least <emphasis>three</emphasis> active partitions." msgstr "" #. Tag: para #: using-d-i.xml:1358 #, no-c-format -msgid "It is perfectly possible to have several types of MD at once. For example, if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine the first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)." +msgid "" +"It is perfectly possible to have several types of MD at once. For example, " +"if you have three 200 GB hard drives dedicated to MD, each containing two " +"100 GB partitions, you can combine the first partitions on all three disks " +"into the RAID0 (fast 300 GB video editing partition) and use the other three " +"partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition " +"for <filename>/home</filename>)." msgstr "" #. Tag: para #: using-d-i.xml:1367 #, no-c-format -msgid "After you setup MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints." +msgid "" +"After you setup MD devices to your liking, you can <guimenuitem>Finish</" +"guimenuitem> <command>mdcfg</command> to return back to the " +"<command>partman</command> to create filesystems on your new MD devices and " +"assign them the usual attributes like mountpoints." msgstr "" #. Tag: title @@ -1129,37 +1677,70 @@ msgstr "" #. Tag: para #: using-d-i.xml:1383 #, no-c-format -msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation with moving stuff around, symlinking, etc." +msgid "" +"If you are working with computers at the level of system administrator or " +"<quote>advanced</quote> user, you have surely seen the situation where some " +"disk partition (usually the most important one) was short on space, while " +"some other partition was grossly underused and you had to manage this " +"situation with moving stuff around, symlinking, etc." msgstr "" #. Tag: para #: using-d-i.xml:1391 #, no-c-format -msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disk (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks." +msgid "" +"To avoid the described situation you can use Logical Volume Manager (LVM). " +"Simply said, with LVM you can combine your partitions (<firstterm>physical " +"volumes</firstterm> in LVM lingo) to form a virtual disk (so called " +"<firstterm>volume group</firstterm>), which can then be divided into virtual " +"partitions (<firstterm>logical volumes</firstterm>). The point is that " +"logical volumes (and of course underlying volume groups) can span across " +"several physical disks." msgstr "" #. Tag: para #: using-d-i.xml:1401 #, no-c-format -msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk to the computer, join it with your existing volume group and then resize the logical volume which holds your <filename>/home</filename> filesystem and voila — your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>." +msgid "" +"Now when you realize you need more space for your old 160GB <filename>/home</" +"filename> partition, you can simply add a new 300GB disk to the computer, " +"join it with your existing volume group and then resize the logical volume " +"which holds your <filename>/home</filename> filesystem and voila — " +"your users have some room again on their renewed 460GB partition. This " +"example is of course a bit oversimplified. If you haven't read it yet, you " +"should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>." msgstr "" #. Tag: para #: using-d-i.xml:1412 #, no-c-format -msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>." +msgid "" +"LVM setup in &d-i; is quite simple and completely supported inside " +"<command>partman</command>. First, you have to mark the partition(s) to be " +"used as physical volumes for LVM. This is done in the <guimenu>Partition " +"settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:" +"</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>." msgstr "" #. Tag: para #: using-d-i.xml:1421 #, no-c-format -msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:" +msgid "" +"When you return to the main <command>partman</command> screen, you will see " +"a new option <guimenuitem>Configure the Logical Volume Manager</" +"guimenuitem>. When you select that, you will first be asked to confirm " +"pending changes to the partition table (if any) and after that the LVM " +"configuration menu will be shown. Above the menu a summary of the LVM " +"configuration is shown. The menu itself is context sensitive and only shows " +"valid actions. The possible actions are:" msgstr "" #. Tag: para #: using-d-i.xml:1432 #, no-c-format -msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more" +msgid "" +"<guimenuitem>Display configuration details</guimenuitem>: shows LVM device " +"structure, names and sizes of logical volumes and more" msgstr "" #. Tag: guimenuitem @@ -1201,19 +1782,26 @@ msgstr "" #. Tag: para #: using-d-i.xml:1454 #, no-c-format -msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen" +msgid "" +"<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</" +"command> screen" msgstr "" #. Tag: para #: using-d-i.xml:1460 #, no-c-format -msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it." +msgid "" +"Use the options in that menu to first create a volume group and then create " +"your logical volumes inside it." msgstr "" #. Tag: para #: using-d-i.xml:1465 #, no-c-format -msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)." +msgid "" +"After you return to the main <command>partman</command> screen, any created " +"logical volumes will be displayed in the same way as ordinary partitions " +"(and you should treat them as such)." msgstr "" #. Tag: title @@ -1225,37 +1813,76 @@ msgstr "" #. Tag: para #: using-d-i.xml:1480 #, no-c-format -msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters." +msgid "" +"&d-i; allows you to set up encrypted partitions. Every file you write to " +"such a partition is immediately saved to the device in encrypted form. " +"Access to the encrypted data is granted only after entering the " +"<firstterm>passphrase</firstterm> used when the encrypted partition was " +"originally created. This feature is useful to protect sensitive data in case " +"your laptop or hard drive gets stolen. The thief might get physical access " +"to the hard drive, but without knowing the right passphrase, the data on the " +"hard drive will look like random characters." msgstr "" #. Tag: para #: using-d-i.xml:1492 #, no-c-format -msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition." +msgid "" +"The two most important partitions to encrypt are: the home partition, where " +"your private data resides, and the swap partition, where sensitive data " +"might be stored temporarily during operation. Of course, nothing prevents " +"you from encrypting any other partitions that might be of interest. For " +"example <filename>/var</filename> where database servers, mail servers or " +"print servers store their data, or <filename>/tmp</filename> which is used " +"by various programs to store potentially interesting temporary files. Some " +"people may even want to encrypt their whole system. The only exception is " +"the <filename>/boot</filename> partition which must remain unencrypted, " +"because currently there is no way to load the kernel from an encrypted " +"partition." msgstr "" #. Tag: para #: using-d-i.xml:1507 #, no-c-format -msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length." +msgid "" +"Please note that the performance of encrypted partitions will be less than " +"that of unencrypted ones because the data needs to be decrypted or encrypted " +"for every read or write. The performance impact depends on your CPU speed, " +"chosen cipher and a key length." msgstr "" #. Tag: para #: using-d-i.xml:1514 #, no-c-format -msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition." +msgid "" +"To use encryption, you have to create a new partition by selecting some free " +"space in the main partitioning menu. Another option is to choose an existing " +"partition (e.g. a regular partition, an LVM logical volume or a RAID " +"volume). In the <guimenu>Partition settings</guimenu> menu, you need to " +"select <guimenuitem>physical volume for encryption</guimenuitem> at the " +"<menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will " +"then change to include several cryptographic options for the partition." msgstr "" #. Tag: para #: using-d-i.xml:1525 #, no-c-format -msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default." +msgid "" +"&d-i; supports several encryption methods. The default method is " +"<firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to " +"host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> " +"(older, maintained separately from the Linux kernel tree). Unless you have " +"compelling reasons to do otherwise, it is recommended to use the default." msgstr "" #. Tag: para #: using-d-i.xml:1537 #, no-c-format -msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind." +msgid "" +"First, let's have a look at the options available when you select " +"<userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As " +"always: when in doubt, use the defaults, because they have been carefully " +"chosen with security in mind." msgstr "" #. Tag: term @@ -1267,7 +1894,17 @@ msgstr "" #. Tag: para #: using-d-i.xml:1549 #, no-c-format -msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century." +msgid "" +"This option lets you select the encryption algorithm (<firstterm>cipher</" +"firstterm>) which will be used to encrypt the data on the partition. &d-i; " +"currently supports the following block ciphers: <firstterm>aes</firstterm>, " +"<firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and " +"<firstterm>twofish</firstterm>. It is beyond the scope of this document to " +"discuss the qualities of these different algorithms, however, it might help " +"your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by " +"the American National Institute of Standards and Technology as the standard " +"encryption algorithm for protecting sensitive information in the 21st " +"century." msgstr "" #. Tag: term @@ -1279,7 +1916,11 @@ msgstr "" #. Tag: para #: using-d-i.xml:1569 #, no-c-format -msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher." +msgid "" +"Here you can specify the length of the encryption key. With a larger key " +"size, the strength of the encryption is generally improved. On the other " +"hand, increasing the length of the key usually has a negative impact on " +"performance. Available key sizes vary depending on the cipher." msgstr "" #. Tag: term @@ -1291,13 +1932,23 @@ msgstr "" #. Tag: para #: using-d-i.xml:1583 #, no-c-format -msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data." +msgid "" +"The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</" +"firstterm> algorithm is used in cryptography to ensure that applying the " +"cipher on the same <firstterm>clear text</firstterm> data with the same key " +"always produces a unique <firstterm>cipher text</firstterm>. The idea is to " +"prevent the attacker from deducing information from repeated patterns in the " +"encrypted data." msgstr "" #. Tag: para #: using-d-i.xml:1593 #, no-c-format -msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms." +msgid "" +"From the provided alternatives, the default <userinput>cbc-essiv:sha256</" +"userinput> is currently the least vulnerable to known attacks. Use the other " +"alternatives only when you need to ensure compatibility with some previously " +"installed system that is not able to use newer algorithms." msgstr "" #. Tag: term @@ -1321,7 +1972,11 @@ msgstr "" #. Tag: para #: using-d-i.xml:1614 #, no-c-format -msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process." +msgid "" +"The encryption key will be computed<footnote> <para> Using a passphrase as " +"the key currently means that the partition will be set up using <ulink url=" +"\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase " +"which you will be able to enter later in the process." msgstr "" #. Tag: term @@ -1333,13 +1988,26 @@ msgstr "" #. Tag: para #: using-d-i.xml:1630 #, no-c-format -msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)" +msgid "" +"A new encryption key will be generated from random data each time you try to " +"bring up the encrypted partition. In other words: on every shutdown the " +"content of the partition will be lost as the key is deleted from memory. (Of " +"course, you could try to guess the key with a brute force attack, but unless " +"there is an unknown weakness in the cipher algorithm, it is not achievable " +"in our lifetime.)" msgstr "" #. Tag: para #: using-d-i.xml:1639 #, no-c-format -msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition." +msgid "" +"Random keys are useful for swap partitions because you do not need to bother " +"yourself with remembering the passphrase or wiping sensitive information " +"from the swap partition before shutting down your computer. However, it also " +"means that you will <emphasis>not</emphasis> be able to use the " +"<quote>suspend-to-disk</quote> functionality offered by newer Linux kernels " +"as it will be impossible (during a subsequent boot) to recover the suspended " +"data written to the swap partition." msgstr "" #. Tag: term @@ -1351,13 +2019,24 @@ msgstr "" #. Tag: para #: using-d-i.xml:1660 #, no-c-format -msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>." +msgid "" +"Determines whether the content of this partition should be overwritten with " +"random data before setting up the encryption. This is recommended because it " +"might otherwise be possible for an attacker to discern which parts of the " +"partition are in use and which are not. In addition, this will make it " +"harder to recover any leftover data from previous " +"installations<footnote><para> It is believed that the guys from three-letter " +"agencies can restore the data even after several rewrites of the " +"magnetooptical media, though. </para></footnote>." msgstr "" #. Tag: para #: using-d-i.xml:1680 #, no-c-format -msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:" +msgid "" +"If you select <menuchoice> <guimenu>Encryption method:</guimenu> " +"<guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu " +"changes to provide the following options:" msgstr "" #. Tag: term @@ -1369,7 +2048,10 @@ msgstr "" #. Tag: para #: using-d-i.xml:1691 #, no-c-format -msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information." +msgid "" +"For loop-AES, unlike dm-crypt, the options for cipher and key size are " +"combined, so you can select both at the same time. Please see the above " +"sections on ciphers and key sizes for further information." msgstr "" #. Tag: term @@ -1393,7 +2075,11 @@ msgstr "" #. Tag: para #: using-d-i.xml:1710 #, no-c-format -msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)." +msgid "" +"The encryption key will be generated from random data during the " +"installation. Moreover this key will be encrypted with <application>GnuPG</" +"application>, so to use it, you will need to enter the proper passphrase " +"(you will be asked to provide one later in the process)." msgstr "" #. Tag: para @@ -1409,1054 +2095,1638 @@ msgid "Please see the the section on erasing data above." msgstr "" #. Tag: para -#: using-d-i.xml:1747 +#: using-d-i.xml:1746 #, no-c-format -msgid "Please note that the <emphasis>graphical</emphasis> version of the installer still has some limitations when compared to the textual one. For cryptography it means you can set up only volumes using a <emphasis>passphrase</emphasis> as the encryption key." +msgid "" +"After you have selected the desired parameters for your encrypted " +"partitions, return back to the main partitioning menu. There should now be a " +"new menu item called <guimenu>Configure encrypted volumes</guimenu>. After " +"you select it, you will be asked to confirm the deletion of data on " +"partitions marked to be erased and possibly other actions such as writing a " +"new partition table. For large partitions this might take some time." msgstr "" #. Tag: para -#: using-d-i.xml:1755 +#: using-d-i.xml:1756 #, no-c-format -msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time." +msgid "" +"Next you will be asked to enter a passphrase for partitions configured to " +"use one. Good passphrases should be longer than 8 characters, should be a " +"mixture of letters, numbers and other characters and should not contain " +"common dictionary words or information easily associable with you (such as " +"birthdates, hobbies, pet names, names of family members or relatives, etc.)." msgstr "" #. Tag: para #: using-d-i.xml:1765 #, no-c-format -msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1774 -#, no-c-format -msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system." +msgid "" +"Before you input any passphrases, you should have made sure that your " +"keyboard is configured correctly and generates the expected characters. If " +"you are unsure, you can switch to the second virtual console and type some " +"text at the prompt. This ensures that you won't be surprised later, e.g. by " +"trying to input a passphrase using a qwerty keyboard layout when you used an " +"azerty layout during the installation. This situation can have several " +"causes. Maybe you switched to another keyboard layout during the " +"installation, or the selected keyboard layout might not have been set up yet " +"when entering the passphrase for the root file system." msgstr "" #. Tag: para -#: using-d-i.xml:1787 +#: using-d-i.xml:1778 #, no-c-format -msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted." +msgid "" +"If you selected to use methods other than a passphrase to create encryption " +"keys, they will be generated now. Because the kernel may not have gathered a " +"sufficient amount of entropy at this early stage of the installation, the " +"process may take a long time. You can help speed up the process by " +"generating entropy: e.g. by pressing random keys, or by switching to the " +"shell on the second virtual console and generating some network and disk " +"traffic (downloading some files, feeding big files into <filename>/dev/null</" +"filename>, etc.). This will be repeated for each partition to be encrypted." msgstr "" #. Tag: para -#: using-d-i.xml:1803 +#: using-d-i.xml:1794 #, no-c-format msgid "" - "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n" - "Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux device-mapper\n" - " #1 115.1 GB F ext3\n" - "\n" - "Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile\n" - " #1 515.2 MB F ext3\n" - "</screen></informalexample> Now is the time to assign mount points to the volumes and optionally change the file system types if the defaults do not suit you." +"After returning to the main partitioning menu, you will see all encrypted " +"volumes as additional partitions which can be configured in the same way as " +"ordinary partitions. The following example shows two different volumes. The " +"first one is encrypted via dm-crypt, the second one via loop-AES. " +"<informalexample><screen>\n" +"Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux " +"device-mapper\n" +" #1 115.1 GB F ext3\n" +"\n" +"Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile\n" +" #1 515.2 MB F ext3\n" +"</screen></informalexample> Now is the time to assign mount points to the " +"volumes and optionally change the file system types if the defaults do not " +"suit you." msgstr "" #. Tag: para -#: using-d-i.xml:1816 +#: using-d-i.xml:1807 #, no-c-format -msgid "One thing to note here are the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between ordinary boot process and boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>." +msgid "" +"One thing to note here are the identifiers in parentheses " +"(<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> " +"in this case) and the mount points you assigned to each encrypted volume. " +"You will need this information later when booting the new system. The " +"differences between ordinary boot process and boot process with encryption " +"involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/" +">." msgstr "" #. Tag: para -#: using-d-i.xml:1826 +#: using-d-i.xml:1817 #, no-c-format -msgid "Once you are satisfied with the partitioning scheme, continue with the installation." +msgid "" +"Once you are satisfied with the partitioning scheme, continue with the " +"installation." msgstr "" #. Tag: title -#: using-d-i.xml:1837 +#: using-d-i.xml:1828 #, no-c-format msgid "Installing the Base System" msgstr "" #. Tag: para -#: using-d-i.xml:1838 +#: using-d-i.xml:1829 #, no-c-format -msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time." +msgid "" +"Although this stage is the least problematic, it consumes a significant " +"fraction of the install because it downloads, verifies and unpacks the whole " +"base system. If you have a slow computer or network connection, this could " +"take some time." msgstr "" #. Tag: para -#: using-d-i.xml:1851 +#: using-d-i.xml:1842 #, no-c-format -msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>." +msgid "" +"During installation of the base system, package unpacking and setup messages " +"are redirected to <userinput>tty4</userinput>. You can access this terminal " +"by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></" +"keycombo>; get back to the main installer process with " +"<keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>." msgstr "" #. Tag: para -#: using-d-i.xml:1860 +#: using-d-i.xml:1851 #, no-c-format -msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console." +msgid "" +"The unpack/setup messages generated during this phase are also saved in " +"<filename>/var/log/syslog</filename>. You can check them there if the " +"installation is performed over a serial console." msgstr "" #. Tag: para -#: using-d-i.xml:1866 +#: using-d-i.xml:1857 #, no-c-format -msgid "As part of the installation, a Linux kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels." +msgid "" +"As part of the installation, a Linux kernel will be installed. At the " +"default priority, the installer will choose one for you that best matches " +"your hardware. In lower priority modes, you will be able to choose from a " +"list of available kernels." msgstr "" #. Tag: title -#: using-d-i.xml:1878 +#: using-d-i.xml:1869 #, no-c-format msgid "Setting Up Users And Passwords" msgstr "" #. Tag: para -#: using-d-i.xml:1879 +#: using-d-i.xml:1870 #, no-c-format -msgid "After the base system has been installed, the installer will allow you to set up the <quote>root</quote> account and/or an account for the first user. Other user accounts can be created after the installation has been completed." +msgid "" +"After the base system has been installed, the installer will allow you to " +"set up the <quote>root</quote> account and/or an account for the first user. " +"Other user accounts can be created after the installation has been completed." msgstr "" #. Tag: title -#: using-d-i.xml:1893 +#: using-d-i.xml:1884 #, no-c-format msgid "Set the Root Password" msgstr "" #. Tag: para -#: using-d-i.xml:1897 +#: using-d-i.xml:1888 #, no-c-format -msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible." +msgid "" +"The <emphasis>root</emphasis> account is also called the <emphasis>super-" +"user</emphasis>; it is a login that bypasses all security protection on your " +"system. The root account should only be used to perform system " +"administration, and only used for as short a time as possible." msgstr "" #. Tag: para -#: using-d-i.xml:1905 +#: using-d-i.xml:1896 #, no-c-format -msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed." +msgid "" +"Any password you create should contain at least 6 characters, and should " +"contain both upper- and lower-case characters, as well as punctuation " +"characters. Take extra care when setting your root password, since it is " +"such a powerful account. Avoid dictionary words or use of any personal " +"information which could be guessed." msgstr "" #. Tag: para -#: using-d-i.xml:1913 +#: using-d-i.xml:1904 #, no-c-format -msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator." +msgid "" +"If anyone ever tells you they need your root password, be extremely wary. " +"You should normally never give your root password out, unless you are " +"administering a machine with more than one system administrator." msgstr "" #. Tag: title -#: using-d-i.xml:1923 +#: using-d-i.xml:1914 #, no-c-format msgid "Create an Ordinary User" msgstr "" #. Tag: para -#: using-d-i.xml:1925 +#: using-d-i.xml:1916 #, no-c-format -msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login." +msgid "" +"The system will ask you whether you wish to create an ordinary user account " +"at this point. This account should be your main personal log-in. You should " +"<emphasis>not</emphasis> use the root account for daily use or as your " +"personal login." msgstr "" #. Tag: para -#: using-d-i.xml:1934 +#: using-d-i.xml:1925 #, no-c-format -msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program — that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail — consider reading one if it is new to you." +msgid "" +"Why not? Well, one reason to avoid using root's privileges is that it is " +"very easy to do irreparable damage as root. Another reason is that you might " +"be tricked into running a <emphasis>Trojan-horse</emphasis> program — " +"that is a program that takes advantage of your super-user powers to " +"compromise the security of your system behind your back. Any good book on " +"Unix system administration will cover this topic in more detail — " +"consider reading one if it is new to you." msgstr "" #. Tag: para -#: using-d-i.xml:1944 +#: using-d-i.xml:1935 #, no-c-format -msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account." +msgid "" +"You will first be prompted for the user's full name. Then you'll be asked " +"for a name for the user account; generally your first name or something " +"similar will suffice and indeed will be the default. Finally, you will be " +"prompted for a password for this account." msgstr "" #. Tag: para -#: using-d-i.xml:1951 +#: using-d-i.xml:1942 #, no-c-format -msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command." +msgid "" +"If at any point after installation you would like to create another account, " +"use the <command>adduser</command> command." msgstr "" #. Tag: title -#: using-d-i.xml:1962 +#: using-d-i.xml:1953 #, no-c-format msgid "Installing Additional Software" msgstr "" #. Tag: para -#: using-d-i.xml:1963 +#: using-d-i.xml:1954 #, no-c-format -msgid "At this point you have a usable but limited system. Most users will want to install additional software on the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network connection." +msgid "" +"At this point you have a usable but limited system. Most users will want to " +"install additional software on the system to tune it to their needs, and the " +"installer allows you do so. This step can take even longer than installing " +"the base system if you have a slow computer or network connection." msgstr "" #. Tag: title -#: using-d-i.xml:1978 +#: using-d-i.xml:1969 #, no-c-format msgid "Configuring apt" msgstr "" #. Tag: para -#: using-d-i.xml:1980 +#: using-d-i.xml:1971 #, no-c-format -msgid "One of the tools used to install packages on a &debian; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management." -msgstr "" - -#. Tag: para -#: using-d-i.xml:2004 +msgid "" +"One of the tools used to install packages on a &debian; system is a program " +"called <command>apt-get</command>, from the <classname>apt</classname> " +"package<footnote> <para> Note that the program which actually installs the " +"packages is called <command>dpkg</command>. However, this program is more of " +"a low-level tool. <command>apt-get</command> is a higher-level tool, which " +"will invoke <command>dpkg</command> as appropriate. It knows how to retrieve " +"packages from your CD, the network, or wherever. It is also able to " +"automatically install other packages which are required to make the package " +"you're trying to install work correctly. </para> </footnote>. Other front-" +"ends for package management, like <command>aptitude</command> and " +"<command>synaptic</command>, are also in use. These front-ends are " +"recommended for new users, since they integrate some additional features " +"(package searching and status checks) in a nice user interface. In fact, " +"<command>aptitude</command> is now the recommended utility for package " +"management." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1995 #, no-c-format -msgid "<command>apt</command> must be configured so that it knows from where to retrieve packages. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>. You can examine and edit this file to your liking after the installation is complete." +msgid "" +"<command>apt</command> must be configured so that it knows from where to " +"retrieve packages. The results of this configuration are written to the file " +"<filename>/etc/apt/sources.list</filename>. You can examine and edit this " +"file to your liking after the installation is complete." msgstr "" #. Tag: para -#: using-d-i.xml:2011 +#: using-d-i.xml:2002 #, no-c-format -msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>volatile</quote> update service." +msgid "" +"If you are installing at default priority, the installer will largely take " +"care of the configuration automatically, based on the installation method " +"you are using and possibly using choices made earlier in the installation. " +"In most cases the installer will automatically add a security mirror and, if " +"you are installing the stable distribution, a mirror for the " +"<quote>volatile</quote> update service." msgstr "" #. Tag: para -#: using-d-i.xml:2020 +#: using-d-i.xml:2011 #, no-c-format -msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or volatile update services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive." +msgid "" +"If you are installing at a lower priority (e.g. in expert mode), you will be " +"able to make more decisions yourself. You can choose whether or not to use " +"the security and/or volatile update services, and you can choose to add " +"packages from the <quote>contrib</quote> and <quote>non-free</quote> " +"sections of the archive." msgstr "" #. Tag: title -#: using-d-i.xml:2031 +#: using-d-i.xml:2022 #, no-c-format msgid "Installing from more than one CD or DVD" msgstr "" #. Tag: para -#: using-d-i.xml:2033 +#: using-d-i.xml:2024 #, no-c-format -msgid "If you are installing from a CD or a DVD that is part of a larger set, the installer will ask if you want to scan additional CDs or DVDs. If you have additional CDs or DVDs available, you probably want to do this so the installer can use the packages included on them." +msgid "" +"If you are installing from a CD or a DVD that is part of a larger set, the " +"installer will ask if you want to scan additional CDs or DVDs. If you have " +"additional CDs or DVDs available, you probably want to do this so the " +"installer can use the packages included on them." msgstr "" #. Tag: para -#: using-d-i.xml:2040 +#: using-d-i.xml:2031 #, no-c-format -msgid "If you do not have any additional CDs or DVDs, that is no problem: using them is not required. If you also do not use a network mirror (as explained in the next section), it can mean that not all packages belonging to the tasks you select in the next step of the installation can be installed." +msgid "" +"If you do not have any additional CDs or DVDs, that is no problem: using " +"them is not required. If you also do not use a network mirror (as explained " +"in the next section), it can mean that not all packages belonging to the " +"tasks you select in the next step of the installation can be installed." msgstr "" #. Tag: para -#: using-d-i.xml:2048 +#: using-d-i.xml:2039 #, no-c-format -msgid "Packages are included on CDs (and DVDs) in the order of their popularity. This means that for most uses only the first CDs in a set are needed and that only very few people actually use any of the packages included on the last CDs in a set." +msgid "" +"Packages are included on CDs (and DVDs) in the order of their popularity. " +"This means that for most uses only the first CDs in a set are needed and " +"that only very few people actually use any of the packages included on the " +"last CDs in a set." msgstr "" #. Tag: para -#: using-d-i.xml:2055 +#: using-d-i.xml:2046 #, no-c-format -msgid "It also means that buying or downloading and burning a full CD set is just a waste of money as you'll never use most of them. In most cases you are better off getting only the first 3 to 8 CDs and installing any additional packages you may need from the Internet by using a mirror. The same goes for DVD sets: the first DVD, or maybe the first two DVDs will cover most needs." +msgid "" +"It also means that buying or downloading and burning a full CD set is just a " +"waste of money as you'll never use most of them. In most cases you are " +"better off getting only the first 3 to 8 CDs and installing any additional " +"packages you may need from the Internet by using a mirror. The same goes for " +"DVD sets: the first DVD, or maybe the first two DVDs will cover most needs." msgstr "" #. Tag: para -#: using-d-i.xml:2064 +#: using-d-i.xml:2055 #, no-c-format -msgid "A good rule of thumb is that for a regular desktop installation (using the GNOME desktop environment) only the first three CDs are needed. For the alternative desktop environments (KDE or Xfce), additional CDs are needed. The first DVD easily covers all three desktop environments." +msgid "" +"A good rule of thumb is that for a regular desktop installation (using the " +"GNOME desktop environment) only the first three CDs are needed. For the " +"alternative desktop environments (KDE or Xfce), additional CDs are needed. " +"The first DVD easily covers all three desktop environments." msgstr "" #. Tag: para -#: using-d-i.xml:2072 +#: using-d-i.xml:2063 #, no-c-format -msgid "If you do scan multiple CDs or DVDs, the installer will prompt you to exchange them when it needs packages from another CD/DVD than the one currently in the drive. Note that only CDs or DVDs that belong to the same set should be scanned. The order in which they are scanned does not really matter, but scanning them in ascending order will reduce the chance of mistakes." +msgid "" +"If you do scan multiple CDs or DVDs, the installer will prompt you to " +"exchange them when it needs packages from another CD/DVD than the one " +"currently in the drive. Note that only CDs or DVDs that belong to the same " +"set should be scanned. The order in which they are scanned does not really " +"matter, but scanning them in ascending order will reduce the chance of " +"mistakes." msgstr "" #. Tag: title -#: using-d-i.xml:2085 +#: using-d-i.xml:2076 #, no-c-format msgid "Using a network mirror" msgstr "" #. Tag: para -#: using-d-i.xml:2087 +#: using-d-i.xml:2078 #, no-c-format -msgid "One question that will be asked during most installs is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions." +msgid "" +"One question that will be asked during most installs is whether or not to " +"use a network mirror as a source for packages. In most cases the default " +"answer should be fine, but there are some exceptions." msgstr "" #. Tag: para -#: using-d-i.xml:2093 +#: using-d-i.xml:2084 #, no-c-format -msgid "If you are <emphasis>not</emphasis> installing from a full CD or DVD or using a full CD/DVD image, you really should use a network mirror as otherwise you will end up with only a very minimal system. However, if you have a limited Internet connection it is best <emphasis>not</emphasis> to select the <literal>desktop</literal> task in the next step of the installation." +msgid "" +"If you are <emphasis>not</emphasis> installing from a full CD or DVD or " +"using a full CD/DVD image, you really should use a network mirror as " +"otherwise you will end up with only a very minimal system. However, if you " +"have a limited Internet connection it is best <emphasis>not</emphasis> to " +"select the <literal>desktop</literal> task in the next step of the " +"installation." msgstr "" #. Tag: para -#: using-d-i.xml:2102 +#: using-d-i.xml:2093 #, no-c-format -msgid "If you are installing from a single full CD or using a full CD image, using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. If you have a limited Internet connection it may still be best to <emphasis>not</emphasis> select a network mirror here, but to finish the installation using only what's available on the CD and selectively install additional packages after the installation (i.e. after you have rebooted into the new system)." +msgid "" +"If you are installing from a single full CD or using a full CD image, using " +"a network mirror is not required, but is still strongly recommended because " +"a single CD contains only a fairly limited number of packages. If you have a " +"limited Internet connection it may still be best to <emphasis>not</emphasis> " +"select a network mirror here, but to finish the installation using only " +"what's available on the CD and selectively install additional packages after " +"the installation (i.e. after you have rebooted into the new system)." msgstr "" #. Tag: para -#: using-d-i.xml:2113 +#: using-d-i.xml:2104 #, no-c-format -msgid "If you are installing from a DVD or using a DVD image, any packages needed during the installation should be present on the first DVD. The same is true if you have scanned multiple CDs as explained in the previous section. Use of a network mirror is optional." +msgid "" +"If you are installing from a DVD or using a DVD image, any packages needed " +"during the installation should be present on the first DVD. The same is true " +"if you have scanned multiple CDs as explained in the previous section. Use " +"of a network mirror is optional." msgstr "" #. Tag: para -#: using-d-i.xml:2120 +#: using-d-i.xml:2111 #, no-c-format -msgid "One advantage of adding a network mirror is that updates that have occurred since the CD/DVD set was created and have been included in a point release, will become available for installation, thus extending the life of your CD/DVD set without compromising the security or stability of the installed system." +msgid "" +"One advantage of adding a network mirror is that updates that have occurred " +"since the CD/DVD set was created and have been included in a point release, " +"will become available for installation, thus extending the life of your CD/" +"DVD set without compromising the security or stability of the installed " +"system." msgstr "" #. Tag: para -#: using-d-i.xml:2127 +#: using-d-i.xml:2118 #, no-c-format -msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available from CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on" +msgid "" +"In summary: selecting a network mirror is generally a good idea, except if " +"you do not have a good Internet connection. If the current version of a " +"package is available from CD/DVD, the installer will always use that. The " +"amount of data that will be downloaded if you do select a mirror thus " +"depends on" msgstr "" #. Tag: para -#: using-d-i.xml:2136 +#: using-d-i.xml:2127 #, no-c-format msgid "the tasks you select in the next step of the installation," msgstr "" #. Tag: para -#: using-d-i.xml:2141 +#: using-d-i.xml:2132 #, no-c-format msgid "which packages are needed for those tasks," msgstr "" #. Tag: para -#: using-d-i.xml:2146 +#: using-d-i.xml:2137 #, no-c-format -msgid "which of those packages are present on the CDs or DVDs you have scanned, and" +msgid "" +"which of those packages are present on the CDs or DVDs you have scanned, and" msgstr "" #. Tag: para -#: using-d-i.xml:2151 +#: using-d-i.xml:2142 #, no-c-format -msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or volatile updates)." +msgid "" +"whether any updated versions of packages included on the CDs or DVDs are " +"available from a mirror (either a regular package mirror, or a mirror for " +"security or volatile updates)." msgstr "" #. Tag: para -#: using-d-i.xml:2160 +#: using-d-i.xml:2151 #, no-c-format -msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or volatile update available for them and those services have been configured." +msgid "" +"Note that the last point means that, even if you choose not to use a network " +"mirror, some packages may still be downloaded from the Internet if there is " +"a security or volatile update available for them and those services have " +"been configured." msgstr "" #. Tag: title -#: using-d-i.xml:2176 +#: using-d-i.xml:2167 #, no-c-format msgid "Selecting and Installing Software" msgstr "" #. Tag: para -#: using-d-i.xml:2178 +#: using-d-i.xml:2169 #, no-c-format -msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks." +msgid "" +"During the installation process, you are given the opportunity to select " +"additional software to install. Rather than picking individual software " +"packages from the &num-of-distrib-pkgs; available packages, this stage of " +"the installation process focuses on selecting and installing predefined " +"collections of software to quickly set up your computer to perform various " +"tasks." msgstr "" #. Tag: para -#: using-d-i.xml:2187 +#: using-d-i.xml:2178 #, no-c-format -msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks." +msgid "" +"So, you have the ability to choose <emphasis>tasks</emphasis> first, and " +"then add on more individual packages later. These tasks loosely represent a " +"number of different jobs or things you want to do with your computer, such " +"as <quote>Desktop environment</quote>, <quote>Web server</quote>, or " +"<quote>Print server</quote><footnote> <para> You should know that to present " +"this list, the installer is merely invoking the <command>tasksel</command> " +"program. It can be run at any time after installation to install more " +"packages (or remove them), or you can use a more fine-grained tool such as " +"<command>aptitude</command>. If you are looking for a specific single " +"package, after installation is complete, simply run <userinput>aptitude " +"install <replaceable>package</replaceable></userinput>, where " +"<replaceable>package</replaceable> is the name of the package you are " +"looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> " +"lists the space requirements for the available tasks." msgstr "" #. Tag: para -#: using-d-i.xml:2214 +#: using-d-i.xml:2205 #, no-c-format -msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can deselect them. You can even opt to install no tasks at all at this point." +msgid "" +"Some tasks may be pre-selected based on the characteristics of the computer " +"you are installing. If you disagree with these selections you can deselect " +"them. You can even opt to install no tasks at all at this point." msgstr "" #. Tag: para -#: using-d-i.xml:2221 +#: using-d-i.xml:2212 #, no-c-format -msgid "Unless you are using the special KDE or Xfce CDs, the <quote>Desktop environment</quote> task will install the GNOME desktop environment." +msgid "" +"Unless you are using the special KDE or Xfce CDs, the <quote>Desktop " +"environment</quote> task will install the GNOME desktop environment." msgstr "" #. Tag: para -#: using-d-i.xml:2228 +#: using-d-i.xml:2219 #, no-c-format -msgid "It is not possible to interactively select a different desktop during the installation. However, it <emphasis>is</emphasis> possible to get &d-i; to install a KDE desktop environment instead of GNOME by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter <literal>desktop=kde</literal> at the boot prompt when starting the installer. Alternatively the more lightweight Xfce desktop environment can be selected by using <literal>desktop=xfce</literal>." +msgid "" +"It is not possible to interactively select a different desktop during the " +"installation. However, it <emphasis>is</emphasis> possible to get &d-i; to " +"install a KDE desktop environment instead of GNOME by using preseeding (see " +"<xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter " +"<literal>desktop=kde</literal> at the boot prompt when starting the " +"installer. Alternatively the more lightweight Xfce desktop environment can " +"be selected by using <literal>desktop=xfce</literal>." msgstr "" #. Tag: para -#: using-d-i.xml:2238 +#: using-d-i.xml:2229 #, no-c-format -msgid "Note that this will only work if the packages needed for KDE or Xfce are actually available. If you are installing using a single full CD image, they will need to be downloaded from a mirror as most needed packages are only included on later CDs; installing KDE or Xfce this way should work fine if you are using a DVD image or any other installation method." +msgid "" +"Note that this will only work if the packages needed for KDE or Xfce are " +"actually available. If you are installing using a single full CD image, they " +"will need to be downloaded from a mirror as most needed packages are only " +"included on later CDs; installing KDE or Xfce this way should work fine if " +"you are using a DVD image or any other installation method." msgstr "" #. Tag: para -#: using-d-i.xml:2246 +#: using-d-i.xml:2237 #, no-c-format -msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache</classname>." +msgid "" +"The various server tasks will install software roughly as follows. DNS " +"server: <classname>bind9</classname>; File server: <classname>samba</" +"classname>, <classname>nfs</classname>; Mail server: <classname>exim4</" +"classname>, <classname>spamassassin</classname>, <classname>uw-imap</" +"classname>; Print server: <classname>cups</classname>; SQL database: " +"<classname>postgresql</classname>; Web server: <classname>apache</classname>." msgstr "" #. Tag: para -#: using-d-i.xml:2258 +#: using-d-i.xml:2249 #, no-c-format -msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the tasks you've selected." +msgid "" +"Once you've selected your tasks, select &BTN-CONT;. At this point, " +"<command>aptitude</command> will install the packages that are part of the " +"tasks you've selected." msgstr "" #. Tag: para -#: using-d-i.xml:2265 +#: using-d-i.xml:2256 #, no-c-format -msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task." +msgid "" +"In the standard user interface of the installer, you can use the space bar " +"to toggle selection of a task." msgstr "" #. Tag: para -#: using-d-i.xml:2271 +#: using-d-i.xml:2262 #, no-c-format -msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started." +msgid "" +"You should be aware that especially the Desktop task is very large. " +"Especially when installing from a normal CD-ROM in combination with a mirror " +"for packages not on the CD-ROM, the installer may want to retrieve a lot of " +"packages over the network. If you have a relatively slow Internet " +"connection, this can take a long time. There is no option to cancel the " +"installation of packages once it has started." msgstr "" #. Tag: para -#: using-d-i.xml:2280 +#: using-d-i.xml:2271 #, no-c-format -msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image." +msgid "" +"Even when packages are included on the CD-ROM, the installer may still " +"retrieve them from the mirror if the version available on the mirror is more " +"recent than the one included on the CD-ROM. If you are installing the stable " +"distribution, this can happen after a point release (an update of the " +"original stable release); if you are installing the testing distribution " +"this will happen if you are using an older image." msgstr "" #. Tag: para -#: using-d-i.xml:2289 +#: using-d-i.xml:2280 #, no-c-format -msgid "Each package you selected with <command>tasksel</command> is downloaded, unpacked and then installed in turn by the <command>apt-get</command> and <command>dpkg</command> programs. If a particular program needs more information from the user, it will prompt you during this process." +msgid "" +"Each package you selected with <command>tasksel</command> is downloaded, " +"unpacked and then installed in turn by the <command>apt-get</command> and " +"<command>dpkg</command> programs. If a particular program needs more " +"information from the user, it will prompt you during this process." msgstr "" #. Tag: title -#: using-d-i.xml:2302 +#: using-d-i.xml:2293 #, no-c-format msgid "Making Your System Bootable" msgstr "" #. Tag: para -#: using-d-i.xml:2304 +#: using-d-i.xml:2295 #, no-c-format -msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>" +msgid "" +"If you are installing a diskless workstation, obviously, booting off the " +"local disk isn't a meaningful option, and this step will be skipped. <phrase " +"arch=\"sparc\">You may wish to set OpenBoot to boot from the network by " +"default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>" msgstr "" #. Tag: title -#: using-d-i.xml:2319 +#: using-d-i.xml:2310 #, no-c-format msgid "Detecting other operating systems" msgstr "" #. Tag: para -#: using-d-i.xml:2321 +#: using-d-i.xml:2312 #, no-c-format -msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to Debian." +msgid "" +"Before a boot loader is installed, the installer will attempt to probe for " +"other operating systems which are installed on the machine. If it finds a " +"supported operating system, you will be informed of this during the boot " +"loader installation step, and the computer will be configured to boot this " +"other operating system in addition to Debian." msgstr "" #. Tag: para -#: using-d-i.xml:2329 +#: using-d-i.xml:2320 #, no-c-format -msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information." +msgid "" +"Note that multiple operating systems booting on a single machine is still " +"something of a black art. The automatic support for detecting and setting up " +"boot loaders to boot other operating systems varies by architecture and even " +"by subarchitecture. If it does not work you should consult your boot " +"manager's documentation for more information." msgstr "" #. Tag: title -#: using-d-i.xml:2347 +#: using-d-i.xml:2338 #, no-c-format msgid "Install <command>aboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2348 +#: using-d-i.xml:2339 #, no-c-format -msgid "If you have booted from SRM and you select this option, the installer will write <command>aboot</command> to the first sector of the disk on which you installed Debian. Be <emphasis>very</emphasis> careful — it is <emphasis>not</emphasis> possible to boot multiple operating systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a different operating system installed on the disk where you have installed Debian, you will have to boot GNU/Linux from a floppy instead." +msgid "" +"If you have booted from SRM and you select this option, the installer will " +"write <command>aboot</command> to the first sector of the disk on which you " +"installed Debian. Be <emphasis>very</emphasis> careful — it is " +"<emphasis>not</emphasis> possible to boot multiple operating systems (e.g. " +"GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k.a. Tru64 Unix, or " +"OpenVMS) from the same disk. If you also have a different operating system " +"installed on the disk where you have installed Debian, you will have to boot " +"GNU/Linux from a floppy instead." msgstr "" #. Tag: title -#: using-d-i.xml:2368 +#: using-d-i.xml:2359 #, no-c-format msgid "<command>palo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2369 +#: using-d-i.xml:2360 #, no-c-format -msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions." +msgid "" +"The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is " +"similar in configuration and usage to <command>LILO</command>, with a few " +"exceptions. First of all, <command>PALO</command> allows you to boot any " +"kernel image on your boot partition. This is because <command>PALO</command> " +"can actually read Linux partitions." msgstr "" #. Tag: para -#: using-d-i.xml:2378 +#: using-d-i.xml:2369 #, no-c-format msgid "hppa FIXME ( need more info )" msgstr "" #. Tag: title -#: using-d-i.xml:2390 +#: using-d-i.xml:2381 #, no-c-format msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2392 +#: using-d-i.xml:2383 #, no-c-format -msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for new users and old hands alike." +msgid "" +"The main &architecture; boot loader is called <quote>grub</quote>. Grub is a " +"flexible and robust boot loader and a good default choice for new users and " +"old hands alike." msgstr "" #. Tag: para -#: using-d-i.xml:2398 +#: using-d-i.xml:2389 #, no-c-format -msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information." +msgid "" +"By default, grub will be installed into the Master Boot Record (MBR), where " +"it will take over complete control of the boot process. If you prefer, you " +"can install it elsewhere. See the grub manual for complete information." msgstr "" #. Tag: para -#: using-d-i.xml:2404 +#: using-d-i.xml:2395 #, no-c-format -msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use." +msgid "" +"If you do not want to install grub, use the &BTN-GOBACK; button to get to " +"the main menu, and from there select whatever bootloader you would like to " +"use." msgstr "" #. Tag: title -#: using-d-i.xml:2417 +#: using-d-i.xml:2408 #, no-c-format msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2419 +#: using-d-i.xml:2410 #, no-c-format -msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>." +msgid "" +"The second &architecture; boot loader is called <quote>LILO</quote>. It is " +"an old complex program which offers lots of functionality, including DOS, " +"Windows, and OS/2 boot management. Please carefully read the instructions in " +"the directory <filename>/usr/share/doc/lilo/</filename> if you have special " +"needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>." msgstr "" #. Tag: para -#: using-d-i.xml:2429 +#: using-d-i.xml:2420 #, no-c-format -msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation." +msgid "" +"Currently the LILO installation will only create menu entries for other " +"operating systems if these can be <firstterm>chainloaded</firstterm>. This " +"means you may have to manually add a menu entry for operating systems like " +"GNU/Linux and GNU/Hurd after the installation." msgstr "" #. Tag: para -#: using-d-i.xml:2437 +#: using-d-i.xml:2428 #, no-c-format -msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:" +msgid "" +"&d-i; offers you three choices on where to install the <command>LILO</" +"command> boot loader:" msgstr "" #. Tag: term -#: using-d-i.xml:2444 +#: using-d-i.xml:2435 #, no-c-format msgid "Master Boot Record (MBR)" msgstr "" #. Tag: para -#: using-d-i.xml:2444 +#: using-d-i.xml:2435 #, no-c-format -msgid "This way the <command>LILO</command> will take complete control of the boot process." +msgid "" +"This way the <command>LILO</command> will take complete control of the boot " +"process." msgstr "" #. Tag: term -#: using-d-i.xml:2451 +#: using-d-i.xml:2442 #, no-c-format msgid "new Debian partition" msgstr "" #. Tag: para -#: using-d-i.xml:2451 +#: using-d-i.xml:2442 #, no-c-format -msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new Debian partition and it will serve as a secondary boot loader." +msgid "" +"Choose this if you want to use another boot manager. <command>LILO</command> " +"will install itself at the beginning of the new Debian partition and it will " +"serve as a secondary boot loader." msgstr "" #. Tag: term -#: using-d-i.xml:2460 +#: using-d-i.xml:2451 #, no-c-format msgid "Other choice" msgstr "" #. Tag: para -#: using-d-i.xml:2460 +#: using-d-i.xml:2451 #, no-c-format -msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use traditional device names such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>." +msgid "" +"Useful for advanced users who want to install <command>LILO</command> " +"somewhere else. In this case you will be asked for desired location. You can " +"use traditional device names such as <filename>/dev/hda</filename> or " +"<filename>/dev/sda</filename>." msgstr "" #. Tag: para -#: using-d-i.xml:2470 +#: using-d-i.xml:2461 #, no-c-format -msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record — however, this means that you'll need to use some other way to get back into Debian!" +msgid "" +"If you can no longer boot into Windows 9x (or DOS) after this step, you'll " +"need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /" +"mbr</userinput> command to reinstall the MS-DOS master boot record — " +"however, this means that you'll need to use some other way to get back into " +"Debian!" msgstr "" #. Tag: title -#: using-d-i.xml:2486 +#: using-d-i.xml:2477 #, no-c-format msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2488 +#: using-d-i.xml:2479 #, no-c-format -msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to do the actual work of loading and starting the Linux kernel." +msgid "" +"The &architecture; boot loader is called <quote>elilo</quote>. It is modeled " +"on the <quote>lilo</quote> boot loader for the x86 architecture and uses a " +"similar configuration file. However, instead of writing an MBR or partition " +"boot record to the disk, it copies the necessary files to a separate FAT " +"formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</" +"guimenuitem> menu in the firmware to point to the files in the EFI " +"partition. The <command>elilo</command> boot loader is really in two parts. " +"The <filename>/usr/sbin/elilo</filename> command manages the partition and " +"copies files into it. The <filename>elilo.efi</filename> program is copied " +"into the EFI partition and then run by the <quote>EFI Boot Manager</quote> " +"to do the actual work of loading and starting the Linux kernel." msgstr "" #. Tag: para -#: using-d-i.xml:2504 +#: using-d-i.xml:2495 #, no-c-format -msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem." +msgid "" +"The <quote>elilo</quote> configuration and installation is done as the last " +"step of installing the packages of the base installation. &d-i; will present " +"you with a list of potential disk partitions that it has found suitable for " +"an EFI partition. Select the partition you set up earlier in the " +"installation, typically a partition on the same disk that contains your " +"<emphasis>root</emphasis> filesystem." msgstr "" #. Tag: title -#: using-d-i.xml:2516 +#: using-d-i.xml:2507 #, no-c-format msgid "Choose the correct partition!" msgstr "" #. Tag: para -#: using-d-i.xml:2518 +#: using-d-i.xml:2509 #, no-c-format -msgid "The criteria for selecting a partition is that it is FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!" +msgid "" +"The criteria for selecting a partition is that it is FAT format filesystem " +"with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices " +"depending on what it finds from scanning all of the disks of the system " +"including EFI partitions of other system disks and EFI diagnostic " +"partitions. Remember, <command>elilo</command> may format the partition " +"during the installation, erasing any previous contents!" msgstr "" #. Tag: title -#: using-d-i.xml:2533 +#: using-d-i.xml:2524 #, no-c-format msgid "EFI Partition Contents" msgstr "" #. Tag: para -#: using-d-i.xml:2535 +#: using-d-i.xml:2526 #, no-c-format -msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured." +msgid "" +"The EFI partition is a FAT filesystem format partition on one of the hard " +"disks of the system, usually the same disk that contains the <emphasis>root</" +"emphasis> filesystem. It is normally not mounted on a running system as it " +"is only needed by the <quote>EFI Boot Manager</quote> to load the system and " +"the installer part of the <command>elilo</command> writes to the filesystem " +"directly. The <command>/usr/sbin/elilo</command> utility writes the " +"following files into the <filename>efi/debian</filename> directory of the " +"EFI partition during the installation. Note that the <quote>EFI Boot " +"Manager</quote> would find these files using the path " +"<filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may " +"be other files in this filesystem as well over time as the system is updated " +"or re-configured." msgstr "" #. Tag: filename -#: using-d-i.xml:2557 +#: using-d-i.xml:2548 #, no-c-format msgid "elilo.conf" msgstr "" #. Tag: para -#: using-d-i.xml:2558 +#: using-d-i.xml:2549 #, no-c-format -msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition." +msgid "" +"This is the configuration file read by the boot loader when it starts. It is " +"a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-" +"written to refer to files in the EFI partition." msgstr "" #. Tag: filename -#: using-d-i.xml:2567 +#: using-d-i.xml:2558 #, no-c-format msgid "elilo.efi" msgstr "" #. Tag: para -#: using-d-i.xml:2568 +#: using-d-i.xml:2559 #, no-c-format -msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>Debian GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu." +msgid "" +"This is the boot loader program that the <quote>EFI Boot Manager</quote> " +"runs to boot the system. It is the program behind the <guimenuitem>Debian " +"GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> " +"command menu." msgstr "" #. Tag: filename -#: using-d-i.xml:2578 +#: using-d-i.xml:2569 #, no-c-format msgid "initrd.img" msgstr "" #. Tag: para -#: using-d-i.xml:2579 +#: using-d-i.xml:2570 #, no-c-format -msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>." +msgid "" +"This is the initial root filesystem used to boot the kernel. It is a copy of " +"the file referenced in the <filename>/etc/elilo.conf</filename>. In a " +"standard Debian installation it would be the file in <filename>/boot</" +"filename> pointed to by the symbolic link <filename>/initrd.img</filename>." msgstr "" #. Tag: filename -#: using-d-i.xml:2591 +#: using-d-i.xml:2582 #, no-c-format msgid "readme.txt" msgstr "" #. Tag: para -#: using-d-i.xml:2592 +#: using-d-i.xml:2583 #, no-c-format -msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run." +msgid "" +"This is a small text file warning you that the contents of the directory are " +"managed by the <command>elilo</command> and that any local changes would be " +"lost at the next time <filename>/usr/sbin/elilo</filename> is run." msgstr "" #. Tag: filename -#: using-d-i.xml:2602 +#: using-d-i.xml:2593 #, no-c-format msgid "vmlinuz" msgstr "" #. Tag: para -#: using-d-i.xml:2603 +#: using-d-i.xml:2594 #, no-c-format -msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>." +msgid "" +"This is the compressed kernel itself. It is a copy of the file referenced in " +"the <filename>/etc/elilo.conf</filename>. In a standard Debian installation " +"it would be the file in <filename>/boot</filename> pointed to by the " +"symbolic link <filename>/vmlinuz</filename>." msgstr "" #. Tag: title -#: using-d-i.xml:2623 +#: using-d-i.xml:2614 #, no-c-format msgid "<command>arcboot</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2624 +#: using-d-i.xml:2615 #, no-c-format msgid "" - "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n" - "<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>\n" - "<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</replaceable>)</userinput>\n" - "<userinput> setenv OSLoader arcboot</userinput>\n" - "<userinput> setenv OSLoadFilename <replaceable>config</replaceable></userinput>\n" - "<userinput> setenv AutoLoad yes</userinput>\n" - "</screen></informalexample> on the firmware prompt, and then typing <command>boot</command>." +"The boot loader on SGI machines is <command>arcboot</command>. It has to be " +"installed on the same hard disk as the kernel (this is done automatically by " +"the installer). Arcboot supports different configurations which are set up " +"in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique " +"name, the default setup as created by the installer is <quote>linux</quote>. " +"After arcboot has been installed, the system can be booted from hard disk by " +"setting some firmware environment variables entering " +"<informalexample><screen>\n" +"<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk" +"(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>\n" +"<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk" +"(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</" +"replaceable>)</userinput>\n" +"<userinput> setenv OSLoader arcboot</userinput>\n" +"<userinput> setenv OSLoadFilename <replaceable>config</replaceable></" +"userinput>\n" +"<userinput> setenv AutoLoad yes</userinput>\n" +"</screen></informalexample> on the firmware prompt, and then typing " +"<command>boot</command>." msgstr "" #. Tag: replaceable -#: using-d-i.xml:2643 +#: using-d-i.xml:2634 #, no-c-format msgid "scsi" msgstr "" #. Tag: para -#: using-d-i.xml:2644 +#: using-d-i.xml:2635 #, no-c-format -msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers" +msgid "" +"is the SCSI bus to be booted from, this is <userinput>0</userinput> for the " +"onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2652 +#: using-d-i.xml:2643 #, no-c-format msgid "disk" msgstr "" #. Tag: para -#: using-d-i.xml:2653 +#: using-d-i.xml:2644 #, no-c-format -msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed" +msgid "" +"is the SCSI ID of the hard disk on which <command>arcboot</command> is " +"installed" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2661 using-d-i.xml:2730 +#: using-d-i.xml:2652 using-d-i.xml:2721 #, no-c-format msgid "partnr" msgstr "" #. Tag: para -#: using-d-i.xml:2662 +#: using-d-i.xml:2653 #, no-c-format -msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides" +msgid "" +"is the number of the partition on which <filename>/etc/arcboot.conf</" +"filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2670 +#: using-d-i.xml:2661 #, no-c-format msgid "config" msgstr "" #. Tag: para -#: using-d-i.xml:2671 +#: using-d-i.xml:2662 #, no-c-format -msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default." +msgid "" +"is the name of the configuration entry in <filename>/etc/arcboot.conf</" +"filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: title -#: using-d-i.xml:2692 +#: using-d-i.xml:2683 #, no-c-format msgid "<command>delo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2693 +#: using-d-i.xml:2684 #, no-c-format msgid "" - "The boot loader on DECstations is <command>DELO</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). DELO supports different configurations which are set up in <filename>/etc/delo.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After DELO has been installed, the system can be booted from hard disk by entering <informalexample><screen>\n" - "<userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> <replaceable>partnr</replaceable>/<replaceable>name</replaceable></userinput>\n" - "</screen></informalexample> on the firmware prompt." +"The boot loader on DECstations is <command>DELO</command>. It has to be " +"installed on the same hard disk as the kernel (this is done automatically by " +"the installer). DELO supports different configurations which are set up in " +"<filename>/etc/delo.conf</filename>. Each configuration has a unique name, " +"the default setup as created by the installer is <quote>linux</quote>. After " +"DELO has been installed, the system can be booted from hard disk by entering " +"<informalexample><screen>\n" +"<userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> " +"<replaceable>partnr</replaceable>/<replaceable>name</replaceable></" +"userinput>\n" +"</screen></informalexample> on the firmware prompt." msgstr "" #. Tag: replaceable -#: using-d-i.xml:2712 +#: using-d-i.xml:2703 #, no-c-format msgid "<replaceable>#</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2713 +#: using-d-i.xml:2704 #, no-c-format -msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers" +msgid "" +"is the TurboChannel device to be booted from, on most DECstations this is " +"<userinput>3</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2721 +#: using-d-i.xml:2712 #, no-c-format msgid "<replaceable>id</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2722 +#: using-d-i.xml:2713 #, no-c-format -msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed" +msgid "" +"is the SCSI ID of the hard disk on which <command>DELO</command> is installed" msgstr "" #. Tag: para -#: using-d-i.xml:2731 +#: using-d-i.xml:2722 #, no-c-format -msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides" +msgid "" +"is the number of the partition on which <filename>/etc/delo.conf</filename> " +"resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2739 +#: using-d-i.xml:2730 #, no-c-format msgid "name" msgstr "" #. Tag: para -#: using-d-i.xml:2740 +#: using-d-i.xml:2731 #, no-c-format -msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default." +msgid "" +"is the name of the configuration entry in <filename>/etc/delo.conf</" +"filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: para -#: using-d-i.xml:2750 +#: using-d-i.xml:2741 #, no-c-format -msgid "In case <filename>/etc/delo.conf</filename> is on the first partition on the disk and the default configuration shall be booted, it is sufficient to use" +msgid "" +"In case <filename>/etc/delo.conf</filename> is on the first partition on the " +"disk and the default configuration shall be booted, it is sufficient to use" msgstr "" #. Tag: screen -#: using-d-i.xml:2756 +#: using-d-i.xml:2747 #, no-c-format msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>" msgstr "" #. Tag: title -#: using-d-i.xml:2766 +#: using-d-i.xml:2757 #, no-c-format msgid "Install <command>Yaboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2767 +#: using-d-i.xml:2758 #, no-c-format -msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian;." +msgid "" +"Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their " +"boot loader. The installer will set up <command>yaboot</command> " +"automatically, so all you need is a small 820k partition named " +"<quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> " +"created back in the partitioning component. If this step completes " +"successfully then your disk should now be bootable and OpenFirmware will be " +"set to boot &debian;." msgstr "" #. Tag: title -#: using-d-i.xml:2785 +#: using-d-i.xml:2776 #, no-c-format msgid "Install <command>Quik</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2786 +#: using-d-i.xml:2777 #, no-c-format -msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones." +msgid "" +"The boot loader for OldWorld Power Macintosh machines is <command>quik</" +"command>. You can also use it on CHRP. The installer will attempt to set up " +"<command>quik</command> automatically. The setup has been known to work on " +"7200, 7300, and 7600 Powermacs, and on some Power Computing clones." msgstr "" #. Tag: title -#: using-d-i.xml:2802 +#: using-d-i.xml:2793 #, no-c-format msgid "<command>zipl</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2803 +#: using-d-i.xml:2794 #, no-c-format -msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>." +msgid "" +"The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</" +"command> is similar in configuration and usage to <command>LILO</command>, " +"with a few exceptions. Please take a look at <quote>LINUX for &arch-title; " +"Device Drivers and Installation Commands</quote> from IBM's developerWorks " +"web site if you want to know more about <command>ZIPL</command>." msgstr "" #. Tag: title -#: using-d-i.xml:2820 +#: using-d-i.xml:2811 #, no-c-format msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2822 +#: using-d-i.xml:2813 #, no-c-format -msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install." +msgid "" +"The standard &architecture; boot loader is called <quote>silo</quote>. It is " +"documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</" +"command> is similar in configuration and usage to <command>LILO</command>, " +"with a few exceptions. First of all, <command>SILO</command> allows you to " +"boot any kernel image on your drive, even if it is not listed in <filename>/" +"etc/silo.conf</filename>. This is because <command>SILO</command> can " +"actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is " +"read at boot time, so there is no need to rerun <command>silo</command> " +"after installing a new kernel like you would with <command>LILO</command>. " +"<command>SILO</command> can also read UFS partitions, which means it can " +"boot SunOS/Solaris partitions as well. This is useful if you want to install " +"GNU/Linux alongside an existing SunOS/Solaris install." msgstr "" #. Tag: title -#: using-d-i.xml:2847 +#: using-d-i.xml:2838 #, no-c-format msgid "Continue Without Boot Loader" msgstr "" #. Tag: para -#: using-d-i.xml:2849 +#: using-d-i.xml:2840 #, no-c-format -msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader). <phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, and Amiga systems, where the original operating system must be maintained on the box and used to boot GNU/Linux.</phrase>" +msgid "" +"This option can be used to complete the installation even when no boot " +"loader is to be installed, either because the arch/subarch doesn't provide " +"one, or because none is desired (e.g. you will use existing boot loader). " +"<phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, " +"and Amiga systems, where the original operating system must be maintained on " +"the box and used to boot GNU/Linux.</phrase>" msgstr "" #. Tag: para -#: using-d-i.xml:2858 +#: using-d-i.xml:2849 #, no-c-format -msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem." +msgid "" +"If you plan to manually configure your bootloader, you should check the name " +"of the installed kernel in <filename>/target/boot</filename>. You should " +"also check that directory for the presence of an <firstterm>initrd</" +"firstterm>; if one is present, you will probably have to instruct your " +"bootloader to use it. Other information you will need are the disk and " +"partition you selected for your <filename>/</filename> filesystem and, if " +"you chose to install <filename>/boot</filename> on a separate partition, " +"also your <filename>/boot</filename> filesystem." msgstr "" #. Tag: title -#: using-d-i.xml:2875 +#: using-d-i.xml:2866 #, no-c-format msgid "Finishing the Installation" msgstr "" #. Tag: para -#: using-d-i.xml:2876 +#: using-d-i.xml:2867 #, no-c-format -msgid "This is the last step in the Debian installation process during which the installer will do any last minute tasks. It mostly consists of tidying up after the &d-i;." +msgid "" +"This is the last step in the Debian installation process during which the " +"installer will do any last minute tasks. It mostly consists of tidying up " +"after the &d-i;." msgstr "" #. Tag: title -#: using-d-i.xml:2889 +#: using-d-i.xml:2880 #, no-c-format msgid "Setting the System Clock" msgstr "" #. Tag: para -#: using-d-i.xml:2891 +#: using-d-i.xml:2882 #, no-c-format -msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed." +msgid "" +"The installer may ask you if the computer's clock is set to UTC. Normally " +"this question is avoided if possible and the installer tries to work out " +"whether the clock is set to UTC based on things like what other operating " +"systems are installed." msgstr "" #. Tag: para -#: using-d-i.xml:2898 +#: using-d-i.xml:2889 #, no-c-format -msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"m68k;powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase> <phrase arch=\"x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase>" +msgid "" +"In expert mode you will always be able to choose whether or not the clock is " +"set to UTC. <phrase arch=\"m68k;powerpc\">Macintosh hardware clocks are " +"normally set to local time. If you want to dual-boot, select local time " +"instead of UTC.</phrase> <phrase arch=\"x86\">Systems that (also) run Dos or " +"Windows are normally set to local time. If you want to dual-boot, select " +"local time instead of UTC.</phrase>" msgstr "" #. Tag: para -#: using-d-i.xml:2909 +#: using-d-i.xml:2900 #, no-c-format -msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made." +msgid "" +"At this point &d-i; will also attempt to save the current time to the " +"system's hardware clock. This will be done either in UTC or local time, " +"depending on the selection that was just made." msgstr "" #. Tag: title -#: using-d-i.xml:2924 +#: using-d-i.xml:2915 #, no-c-format msgid "Reboot the System" msgstr "" #. Tag: para -#: using-d-i.xml:2926 +#: using-d-i.xml:2917 #, no-c-format -msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new Debian system." +msgid "" +"You will be prompted to remove the boot media (CD, floppy, etc) that you " +"used to boot the installer. After that the system will be rebooted into your " +"new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2932 +#: using-d-i.xml:2923 #, no-c-format -msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian; from the DASD which you selected for the root filesystem during the first steps of the installation." +msgid "" +"After a final prompt the system will be halted because rebooting is not " +"supported on &arch-title;. You then need to IPL &debian; from the DASD which " +"you selected for the root filesystem during the first steps of the " +"installation." msgstr "" #. Tag: title -#: using-d-i.xml:2945 +#: using-d-i.xml:2936 #, no-c-format msgid "Miscellaneous" msgstr "" #. Tag: para -#: using-d-i.xml:2946 +#: using-d-i.xml:2937 #, no-c-format -msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong." +msgid "" +"The components listed in this section are usually not involved in the " +"installation process, but are waiting in the background to help the user in " +"case something goes wrong." msgstr "" #. Tag: title -#: using-d-i.xml:2959 +#: using-d-i.xml:2950 #, no-c-format msgid "Saving the installation logs" msgstr "" #. Tag: para -#: using-d-i.xml:2961 +#: using-d-i.xml:2952 #, no-c-format -msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new Debian system." +msgid "" +"If the installation is successful, the logfiles created during the " +"installation process will be automatically saved to <filename>/var/log/" +"installer/</filename> on your new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2968 +#: using-d-i.xml:2959 #, no-c-format -msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report." +msgid "" +"Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu " +"allows you to save the log files to a floppy disk, network, hard disk, or " +"other media. This can be useful if you encounter fatal problems during the " +"installation and wish to study the logs on another system or attach them to " +"an installation report." msgstr "" #. Tag: title -#: using-d-i.xml:2988 +#: using-d-i.xml:2979 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "" #. Tag: para -#: using-d-i.xml:2990 +#: using-d-i.xml:2981 #, no-c-format -msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to installer itself." +msgid "" +"There are several methods you can use to get a shell while running an " +"installation. On most systems, and if you are not installing over serial " +"console, the easiest method is to switch to the second <emphasis>virtual " +"console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> " +"<keycap>F2</keycap></keycombo><footnote> <para> That is: press the " +"<keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</" +"keycap> and the <keycap>F2</keycap> function key at the same time. </para> </" +"footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</" +"keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</" +"keycap></keycombo> to switch back to installer itself." msgstr "" #. Tag: para -#: using-d-i.xml:3008 +#: using-d-i.xml:2999 #, no-c-format msgid "For the graphical installer see also <xref linkend=\"gtk-using\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:3012 +#: using-d-i.xml:3003 #, no-c-format -msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer." +msgid "" +"If you cannot switch consoles, there is also an <guimenuitem>Execute a " +"Shell</guimenuitem> item on the main menu that can be used to start a shell. " +"You can get to the main menu from most dialogs by using the &BTN-GOBACK; " +"button one or more times. Type <userinput>exit</userinput> to close the " +"shell and return to the installer." msgstr "" #. Tag: para -#: using-d-i.xml:3020 +#: using-d-i.xml:3011 #, no-c-format -msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history." +msgid "" +"At this point you are booted from the RAM disk, and there is a limited set " +"of Unix utilities available for your use. You can see what programs are " +"available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</" +"command> and by typing <command>help</command>. The shell is a Bourne shell " +"clone called <command>ash</command> and has some nice features like " +"autocompletion and history." msgstr "" #. Tag: para -#: using-d-i.xml:3029 +#: using-d-i.xml:3020 #, no-c-format -msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory." +msgid "" +"To edit and view files, use the text editor <command>nano</command>. Log " +"files for the installation system can be found in the <filename>/var/log</" +"filename> directory." msgstr "" #. Tag: para -#: using-d-i.xml:3036 +#: using-d-i.xml:3027 #, no-c-format -msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging." +msgid "" +"Although you can do basically anything in a shell that the available " +"commands allow you to do, the option to use a shell is really only there in " +"case something goes wrong and for debugging." msgstr "" #. Tag: para -#: using-d-i.xml:3042 +#: using-d-i.xml:3033 #, no-c-format -msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell." +msgid "" +"Doing things manually from the shell may interfere with the installation " +"process and result in errors or an incomplete installation. In particular, " +"you should always use let the installer activate your swap partition and not " +"do this yourself from a shell." msgstr "" #. Tag: title -#: using-d-i.xml:3057 +#: using-d-i.xml:3048 #, no-c-format msgid "Installation Over the Network" msgstr "" #. Tag: para -#: using-d-i.xml:3059 +#: using-d-i.xml:3050 #, no-c-format -msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)" +msgid "" +"One of the more interesting components is <firstterm>network-console</" +"firstterm>. It allows you to do a large part of the installation over the " +"network via SSH. The use of the network implies you will have to perform the " +"first steps of the installation from the console, at least to the point of " +"setting up the networking. (Although you can automate that part with <xref " +"linkend=\"automatic-install\"/>.)" msgstr "" #. Tag: para -#: using-d-i.xml:3069 +#: using-d-i.xml:3060 #, no-c-format -msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>." +msgid "" +"This component is not loaded into the main installation menu by default, so " +"you have to explicitly ask for it. If you are installing from CD, you need " +"to boot with medium priority or otherwise invoke the main installation menu " +"and choose <guimenuitem>Load installer components from CD</guimenuitem> and " +"from the list of additional components select <guimenuitem>network-console: " +"Continue installation remotely using SSH</guimenuitem>. Successful load is " +"indicated by a new menu entry called <guimenuitem>Continue installation " +"remotely using SSH</guimenuitem>." msgstr "" #. Tag: para -#: using-d-i.xml:3082 +#: using-d-i.xml:3073 #, no-c-format -msgid "For installations on &arch-title;, this is the default method after setting up the network." +msgid "" +"For installations on &arch-title;, this is the default method after setting " +"up the network." msgstr "" #. Tag: para -#: using-d-i.xml:3087 +#: using-d-i.xml:3078 #, no-c-format -msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the <quote>person who will continue the installation remotely</quote>." +msgid "" +"<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> " +"<phrase arch=\"s390\">You</phrase> will be asked for a new password to be " +"used for connecting to the installation system and for its confirmation. " +"That's all. Now you should see a screen which instructs you to login " +"remotely as the user <emphasis>installer</emphasis> with the password you " +"just provided. Another important detail to notice on this screen is the " +"fingerprint of this system. You need to transfer the fingerprint securely to " +"the <quote>person who will continue the installation remotely</quote>." msgstr "" #. Tag: para -#: using-d-i.xml:3099 +#: using-d-i.xml:3090 #, no-c-format -msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component." +msgid "" +"Should you decide to continue with the installation locally, you can always " +"press &enterkey;, which will bring you back to the main menu, where you can " +"select another component." msgstr "" #. Tag: para -#: using-d-i.xml:3105 +#: using-d-i.xml:3096 #, no-c-format msgid "" - "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n" - "<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</replaceable></userinput>\n" - "</screen></informalexample> Where <replaceable>install_host</replaceable> is either the name or IP address of the computer being installed. Before the actual login the fingerprint of the remote system will be displayed and you will have to confirm that it is correct." +"Now let's switch to the other side of the wire. As a prerequisite, you need " +"to configure your terminal for UTF-8 encoding, because that is what the " +"installation system uses. If you do not, remote installation will be still " +"possible, but you may encounter strange display artefacts like destroyed " +"dialog borders or unreadable non-ascii characters. Establishing a connection " +"with the installation system is as simple as typing: " +"<informalexample><screen>\n" +"<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</" +"replaceable></userinput>\n" +"</screen></informalexample> Where <replaceable>install_host</replaceable> is " +"either the name or IP address of the computer being installed. Before the " +"actual login the fingerprint of the remote system will be displayed and you " +"will have to confirm that it is correct." msgstr "" #. Tag: para -#: using-d-i.xml:3122 +#: using-d-i.xml:3113 #, no-c-format -msgid "The <command>ssh</command> server in the installer uses a default configuration that does not send keep-alive packets. In principle, a connection to the system being installed should be kept open indefinitely. However, in some situations — depending on your local network setup — the connection may be lost after some period of inactivity. One common case where this can happen is when there is some form of Network Address Translation (NAT) somewhere between the client and the system being installed. Depending on at which point of the installation the connection was lost, you may or may not be able to resume the installation after reconnecting." +msgid "" +"The <command>ssh</command> server in the installer uses a default " +"configuration that does not send keep-alive packets. In principle, a " +"connection to the system being installed should be kept open indefinitely. " +"However, in some situations — depending on your local network setup " +"— the connection may be lost after some period of inactivity. One " +"common case where this can happen is when there is some form of Network " +"Address Translation (NAT) somewhere between the client and the system being " +"installed. Depending on at which point of the installation the connection " +"was lost, you may or may not be able to resume the installation after " +"reconnecting." msgstr "" #. Tag: para -#: using-d-i.xml:3135 +#: using-d-i.xml:3126 #, no-c-format -msgid "You may be able to avoid the connection being dropped by adding the option <userinput>-o ServerAliveInterval=<replaceable>value</replaceable></userinput> when starting the <command>ssh</command> connection, or by adding that option in your <command>ssh</command> configuration file. Note however that in some cases adding this option may also <emphasis>cause</emphasis> a connection to be dropped (for example if keep-alive packets are sent during a brief network outage, from which <command>ssh</command> would otherwise have recovered), so it should only be used when needed." +msgid "" +"You may be able to avoid the connection being dropped by adding the option " +"<userinput>-o ServerAliveInterval=<replaceable>value</replaceable></" +"userinput> when starting the <command>ssh</command> connection, or by adding " +"that option in your <command>ssh</command> configuration file. Note however " +"that in some cases adding this option may also <emphasis>cause</emphasis> a " +"connection to be dropped (for example if keep-alive packets are sent during " +"a brief network outage, from which <command>ssh</command> would otherwise " +"have recovered), so it should only be used when needed." msgstr "" #. Tag: para -#: using-d-i.xml:3148 +#: using-d-i.xml:3139 #, no-c-format -msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename><footnote> <para> The following command will remove an existing entry for a host: <command>ssh-keygen -R <<replaceable>hostname</replaceable>|<replaceable>IP address</replaceable>></command>. </para> </footnote> and try again." +msgid "" +"If you install several computers in turn and they happen to have the same IP " +"address or hostname, <command>ssh</command> will refuse to connect to such " +"host. The reason is that it will have different fingerprint, which is " +"usually a sign of a spoofing attack. If you are sure this is not the case, " +"you will need to delete the relevant line from <filename>~/.ssh/known_hosts</" +"filename><footnote> <para> The following command will remove an existing " +"entry for a host: <command>ssh-keygen -R <<replaceable>hostname</" +"replaceable>|<replaceable>IP address</replaceable>></command>. </" +"para> </footnote> and try again." msgstr "" #. Tag: para -#: using-d-i.xml:3164 +#: using-d-i.xml:3155 #, no-c-format -msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells." +msgid "" +"After the login you will be presented with an initial screen where you have " +"two possibilities called <guimenuitem>Start menu</guimenuitem> and " +"<guimenuitem>Start shell</guimenuitem>. The former brings you to the main " +"installer menu, where you can continue with the installation as usual. The " +"latter starts a shell from which you can examine and possibly fix the remote " +"system. You should only start one SSH session for the installation menu, but " +"may start multiple sessions for shells." msgstr "" #. Tag: para -#: using-d-i.xml:3174 +#: using-d-i.xml:3165 #, no-c-format -msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system." +msgid "" +"After you have started the installation remotely over SSH, you should not go " +"back to the installation session running on the local console. Doing so may " +"corrupt the database that holds the configuration of the new system. This in " +"turn may result in a failed installation or problems with the installed " +"system." msgstr "" #. Tag: para -#: using-d-i.xml:3182 +#: using-d-i.xml:3173 #, no-c-format -msgid "Also, if you are running the SSH session from an X terminal, you should not resize the window as that will result in the connection being terminated." +msgid "" +"Also, if you are running the SSH session from an X terminal, you should not " +"resize the window as that will result in the connection being terminated." msgstr "" - |