diff options
| author | Frans Pop <elendil@planet.nl> | 2006-09-12 22:41:26 +0000 |
|---|---|---|
| committer | Frans Pop <elendil@planet.nl> | 2006-09-12 22:41:26 +0000 |
| commit | dcff138fb58196e279c83915d329d4742f43e831 (patch) | |
| tree | 3fa57b143e6a5702eb96260cf03ae0c7306cb8da /po/hu | |
| parent | 3417984309d96aab7129092321bae3fb50203f4b (diff) | |
| download | installation-guide-dcff138fb58196e279c83915d329d4742f43e831.zip | |
Update of POT and PO files for the manual
Diffstat (limited to 'po/hu')
| -rw-r--r-- | po/hu/boot-installer.po | 1726 | ||||
| -rw-r--r-- | po/hu/install-methods.po | 911 |
2 files changed, 2125 insertions, 512 deletions
diff --git a/po/hu/boot-installer.po b/po/hu/boot-installer.po index 32c528313..2e5dd8fdb 100644 --- a/po/hu/boot-installer.po +++ b/po/hu/boot-installer.po @@ -4,12 +4,13 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: \n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2006-09-08 22:58+0000\n" "PO-Revision-Date: 2006-09-12 23:27+0100\n" "Last-Translator: SZERVÁC Attila <sas@321.hu>\n" "Language-Team: Hungarian\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Poedit-Language: Hungarian\n" @@ -36,55 +37,101 @@ msgstr "" #. Tag: para #: boot-installer.xml:21 #, 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:31 #, 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." -msgstr "Az Alpha konzol alrendszer specifikációra épülő <emphasis>SRM konzol</emphasis> egy OpenVMS, Tru64 UNIX és GNU/Linux operációs rendszerre való kezelő-környezetet ad." +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 "" +"Az Alpha konzol alrendszer specifikációra épülő <emphasis>SRM konzol</" +"emphasis> egy OpenVMS, Tru64 UNIX és GNU/Linux operációs rendszerre való " +"kezelő-környezetet ad." #. Tag: para #: boot-installer.xml:38 #, 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." -msgstr "Az Az Advanced RISC Computing (ARC) specifikációra épülő <emphasis>ARC, AlphaBIOS és ARCSBIOS konzol</emphasis> egy Windows NT-hez készült kezelő-környezetet ad." +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 "" +"Az Az Advanced RISC Computing (ARC) specifikációra épülő <emphasis>ARC, " +"AlphaBIOS és ARCSBIOS konzol</emphasis> egy Windows NT-hez készült kezelő-" +"környezetet ad." #. Tag: para #: boot-installer.xml:47 #, 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:54 #, 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:63 #, 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:76 #, 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:87 #, 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:95 #, 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 @@ -106,20 +153,11 @@ msgid "alcor" msgstr "" #. Tag: entry -#: boot-installer.xml:115 -#: boot-installer.xml:118 -#: boot-installer.xml:124 -#: boot-installer.xml:130 -#: boot-installer.xml:133 -#: boot-installer.xml:136 -#: boot-installer.xml:139 -#: boot-installer.xml:145 -#: boot-installer.xml:148 -#: boot-installer.xml:151 -#: boot-installer.xml:160 -#: boot-installer.xml:169 -#: boot-installer.xml:184 -#: boot-installer.xml:187 +#: boot-installer.xml:115 boot-installer.xml:118 boot-installer.xml:124 +#: boot-installer.xml:130 boot-installer.xml:133 boot-installer.xml:136 +#: boot-installer.xml:139 boot-installer.xml:145 boot-installer.xml:148 +#: boot-installer.xml:151 boot-installer.xml:160 boot-installer.xml:169 +#: boot-installer.xml:184 boot-installer.xml:187 #, no-c-format msgid "ARC or SRM" msgstr "" @@ -137,15 +175,9 @@ msgid "book1" msgstr "" #. Tag: entry -#: boot-installer.xml:121 -#: boot-installer.xml:127 -#: boot-installer.xml:142 -#: boot-installer.xml:154 -#: boot-installer.xml:163 -#: boot-installer.xml:166 -#: boot-installer.xml:172 -#: boot-installer.xml:178 -#: boot-installer.xml:181 +#: boot-installer.xml:121 boot-installer.xml:127 boot-installer.xml:142 +#: boot-installer.xml:154 boot-installer.xml:163 boot-installer.xml:166 +#: boot-installer.xml:172 boot-installer.xml:178 boot-installer.xml:181 #, no-c-format msgid "SRM only" msgstr "" @@ -265,9 +297,7 @@ msgid "ruffian" msgstr "" #. Tag: entry -#: boot-installer.xml:175 -#: boot-installer.xml:190 -#: boot-installer.xml:193 +#: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193 #, no-c-format msgid "ARC only" msgstr "" @@ -311,65 +341,102 @@ msgstr "" #. Tag: para #: boot-installer.xml:200 #, 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:209 #, 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:215 #, 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:221 #, 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:231 #, 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:238 #, 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" +"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." +"</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:253 #, 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:264 #, 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:283 -#: boot-installer.xml:998 -#: boot-installer.xml:1489 -#: boot-installer.xml:1984 -#: boot-installer.xml:2066 -#: boot-installer.xml:2155 -#: boot-installer.xml:2499 -#: boot-installer.xml:2595 +#: boot-installer.xml:283 boot-installer.xml:998 boot-installer.xml:1489 +#: boot-installer.xml:1984 boot-installer.xml:2066 boot-installer.xml:2155 +#: boot-installer.xml:2499 boot-installer.xml:2595 #, no-c-format msgid "Booting with TFTP" msgstr "" @@ -378,37 +445,54 @@ msgstr "" #: boot-installer.xml:284 #, 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" +"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" +"</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" +"</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>." +"</screen></informalexample> You can get a listing of valid modes with " +"<userinput>>>>set ewa0_mode</userinput>." msgstr "" #. Tag: para #: boot-installer.xml:302 #, no-c-format msgid "" -"Then, to boot from the first Ethernet interface, you would type: <informalexample><screen>\n" +"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." +"</screen></informalexample> This will boot using the default kernel " +"parameters as included in the netboot image." msgstr "" #. Tag: para #: boot-installer.xml:311 #, 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:323 #, 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 @@ -423,7 +507,8 @@ msgstr "" msgid "" "Type <informalexample><screen>\n" ">>> boot xxxx -flags 0\n" -"</screen></informalexample> where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation." +"</screen></informalexample> where <replaceable>xxxx</replaceable> is your CD-" +"ROM drive in SRM notation." msgstr "" #. Tag: title @@ -435,7 +520,14 @@ msgstr "" #. Tag: para #: boot-installer.xml:342 #, 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 @@ -448,26 +540,41 @@ msgstr "" #: boot-installer.xml:359 #, no-c-format msgid "" -"At the SRM prompt (<prompt>>>></prompt>), issue the following command: <informalexample><screen>\n" +"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" +"</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." +"</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:376 #, 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:388 #, 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 @@ -479,7 +586,10 @@ msgstr "" #. Tag: para #: boot-installer.xml:400 #, 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 @@ -491,16 +601,24 @@ msgstr "" #. Tag: para #: boot-installer.xml:410 #, 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:416 #, 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" +"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." +"</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 @@ -510,36 +628,30 @@ msgid "Booting from TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:441 -#: boot-installer.xml:1004 -#: boot-installer.xml:1507 -#: boot-installer.xml:1990 -#: boot-installer.xml:2505 -#: boot-installer.xml:2601 +#: boot-installer.xml:441 boot-installer.xml:1004 boot-installer.xml:1507 +#: boot-installer.xml:1990 boot-installer.xml:2505 boot-installer.xml:2601 #, 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:446 -#: boot-installer.xml:1009 -#: boot-installer.xml:1512 -#: boot-installer.xml:1995 -#: boot-installer.xml:2510 -#: boot-installer.xml:2606 +#: boot-installer.xml:446 boot-installer.xml:1009 boot-installer.xml:1512 +#: boot-installer.xml:1995 boot-installer.xml:2510 boot-installer.xml:2606 #, 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:451 -#: boot-installer.xml:1014 -#: boot-installer.xml:1517 -#: boot-installer.xml:2000 -#: boot-installer.xml:2515 -#: boot-installer.xml:2611 +#: boot-installer.xml:451 boot-installer.xml:1014 boot-installer.xml:1517 +#: boot-installer.xml:2000 boot-installer.xml:2515 boot-installer.xml:2611 #, 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 @@ -551,40 +663,66 @@ msgstr "" #. Tag: para #: boot-installer.xml:460 #, 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:469 #, 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:477 #, 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" +"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" +"</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" +"</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" +"</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" +"</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" +"</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" +"</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." +"</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 @@ -596,7 +734,9 @@ msgstr "" #. Tag: para #: boot-installer.xml:530 #, 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 @@ -606,53 +746,55 @@ msgid "Booting from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:546 -#: boot-installer.xml:716 -#: boot-installer.xml:1126 -#: boot-installer.xml:1947 -#: boot-installer.xml:2287 -#: boot-installer.xml:2641 +#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1126 +#: boot-installer.xml:1947 boot-installer.xml:2287 boot-installer.xml:2641 #, 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:557 -#: boot-installer.xml:727 -#: boot-installer.xml:1137 -#: boot-installer.xml:1958 -#: boot-installer.xml:2298 -#: boot-installer.xml:2652 +#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1137 +#: boot-installer.xml:1958 boot-installer.xml:2298 boot-installer.xml:2652 #, 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:565 -#: boot-installer.xml:735 -#: boot-installer.xml:1145 -#: boot-installer.xml:1966 -#: boot-installer.xml:2306 -#: boot-installer.xml:2660 +#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1145 +#: boot-installer.xml:1966 boot-installer.xml:2306 boot-installer.xml:2660 #, 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:573 -#: boot-installer.xml:743 -#: boot-installer.xml:1153 -#: boot-installer.xml:1974 -#: boot-installer.xml:2314 -#: boot-installer.xml:2668 +#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1153 +#: boot-installer.xml:1974 boot-installer.xml:2314 boot-installer.xml:2668 #, 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:580 #, 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 @@ -664,13 +806,20 @@ msgstr "" #. Tag: para #: boot-installer.xml:595 #, 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:601 #, 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 @@ -694,7 +843,12 @@ msgstr "" #. Tag: para #: boot-installer.xml:620 #, 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 @@ -707,9 +861,29 @@ msgstr "" #: boot-installer.xml:632 #, 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" +"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." +"</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 @@ -721,15 +895,15 @@ msgstr "" #. Tag: para #: boot-installer.xml:694 #, 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:710 -#: boot-installer.xml:1120 -#: boot-installer.xml:1935 -#: boot-installer.xml:2281 -#: boot-installer.xml:2635 +#: boot-installer.xml:710 boot-installer.xml:1120 boot-installer.xml:1935 +#: boot-installer.xml:2281 boot-installer.xml:2635 #, no-c-format msgid "Booting from a CD-ROM" msgstr "" @@ -737,31 +911,51 @@ msgstr "" #. Tag: title #: boot-installer.xml:848 #, 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:851 #, 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:856 #, 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/i386/initrd.gz</filename> file and its corresponding kernel. 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/i386/initrd.gz</filename> file and its corresponding " +"kernel. 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:864 #, 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:873 #, 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 @@ -778,14 +972,22 @@ msgstr "" #. Tag: para #: boot-installer.xml:894 #, 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:903 #, 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" +"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 root=/dev/ram0 ramdisk_size=12000\n" "initrd (hd0,0)/boot/newinstall/initrd.gz\n" @@ -795,7 +997,10 @@ msgstr "" #. Tag: para #: boot-installer.xml:914 #, 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 @@ -807,59 +1012,89 @@ msgstr "" #. Tag: para #: boot-installer.xml:926 #, 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:939 -#: boot-installer.xml:2047 -#: boot-installer.xml:2541 +#: boot-installer.xml:939 boot-installer.xml:2047 boot-installer.xml:2541 #: boot-installer.xml:2689 #, no-c-format msgid "Booting from Floppies" msgstr "" #. Tag: para -#: boot-installer.xml:940 -#: boot-installer.xml:2549 +#: boot-installer.xml:940 boot-installer.xml:2549 #, 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:947 #, 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:953 #, 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>linux root=/dev/hdc</userinput> at the boot prompt. Installation from LS-120 is only supported by 2.4 and later kernels." +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>linux root=/dev/hdc</userinput> at the boot prompt. Installation " +"from LS-120 is only supported by 2.4 and later kernels." msgstr "" #. Tag: para #: boot-installer.xml:964 #, 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:973 #, 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:979 #, 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:988 #, 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 @@ -877,7 +1112,11 @@ msgstr "" #. Tag: para #: boot-installer.xml:1029 #, 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 @@ -889,13 +1128,17 @@ msgstr "" #. Tag: para #: boot-installer.xml:1041 #, 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:1046 #, 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 @@ -907,7 +1150,9 @@ msgstr "" #. Tag: para #: boot-installer.xml:1055 #, 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 @@ -920,21 +1165,45 @@ msgstr "" #: boot-installer.xml:1065 #, 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" +"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." +"</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." msgstr "" #. Tag: para #: boot-installer.xml:1077 #, 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>linux</userinput>) and a space before the first parameter (e.g., <userinput>linux fb=false</userinput>)." +msgid "" +"Information on available boot methods and on boot parameters which might be " +"useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</" +"keycap>. If you add any parameters to the boot command line, be sure to type " +"the boot method (the default is <userinput>linux</userinput>) and a space " +"before the first parameter (e.g., <userinput>linux fb=false</userinput>)." msgstr "" #. Tag: para #: boot-installer.xml:1086 #, 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 "" +"If you are installing the system via a remote management device that " +"provides a text interface to the VGA console, you may not be able to see the " +"initial graphical splash screen upon booting the installer; you may even not " +"see the boot prompt. Examples of these devices include the text console of " +"Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's " +"<quote>Integrated Remote Assistant</quote> (IRA). You can blindly press " +"F1<footnote> <para> In some cases these devices will require special escape " +"sequences to enact this keypress, for example the IRA uses <keycombo> " +"<keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</" +"keycap>. </para> </footnote> to bypass this screen and view the help text. " +"Once you are past the splash screen and at the help text your keystrokes " +"will be echoed at the prompt as expected. To prevent the installer from " +"using the framebuffer for the rest of the installation, you will also want " +"to add <userinput>fb=false</userinput> to the boot prompt, as described in " +"the help text." msgstr "" #. Tag: title @@ -946,31 +1215,72 @@ msgstr "" #. Tag: para #: boot-installer.xml:1163 #, 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:1179 #, 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:1195 #, 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:1204 #, 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:1216 #, 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 @@ -982,7 +1292,14 @@ msgstr "" #. Tag: para #: boot-installer.xml:1236 #, 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 @@ -994,37 +1311,62 @@ msgstr "" #. Tag: para #: boot-installer.xml:1255 #, 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:1261 #, 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:1267 #, 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:1278 #, 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:1289 #, 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:1301 #, 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 @@ -1036,43 +1378,73 @@ msgstr "" #. Tag: para #: boot-installer.xml:1312 #, 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:1323 #, 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:1329 #, 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:1343 #, 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:1350 #, 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:1357 #, 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:1364 #, 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 @@ -1084,31 +1456,57 @@ msgstr "" #. Tag: para #: boot-installer.xml:1380 #, 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:1391 #, 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:1398 #, 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:1409 #, 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:1418 #, 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 @@ -1120,49 +1518,85 @@ msgstr "" #. Tag: para #: boot-installer.xml:1429 #, 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:1441 #, 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:1459 #, 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:1464 #, 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:1471 #, 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:1480 #, 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:1491 #, no-c-format -msgid "Booting an IA64 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 thru 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 IA64 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 " +"thru 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:1525 #, no-c-format -msgid "Network booting an ia64 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 ia64 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 @@ -1175,19 +1609,26 @@ msgstr "" #: boot-installer.xml:1537 #, no-c-format msgid "" -"A suitable TFTP entry for network booting an ia64 system looks something like this: <informalexample><screen>\n" +"A suitable TFTP entry for network booting an ia64 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." +"</screen></informalexample> Note that the goal is to get <command>elilo.efi</" +"command> running on the client." msgstr "" #. Tag: para #: boot-installer.xml:1547 #, 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 @@ -1205,7 +1646,15 @@ msgstr "" #. Tag: para #: boot-installer.xml:1557 #, 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 @@ -1217,19 +1666,38 @@ msgstr "" #. Tag: para #: boot-installer.xml:1575 #, 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:1607 #, 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: para #: boot-installer.xml:1616 #, no-c-format -msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and the disk partitions." +msgid "" +"Proceed to the next chapter to continue the installation where you will set " +"up the language locale, network, and the disk partitions." msgstr "" #. Tag: title @@ -1241,25 +1709,36 @@ msgstr "" #. Tag: para #: boot-installer.xml:1631 #, 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:1639 #, 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:1644 #, 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:1649 #, 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 @@ -1271,13 +1750,18 @@ msgstr "" #. Tag: para #: boot-installer.xml:1667 #, 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:1673 #, 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 @@ -1289,13 +1773,18 @@ msgstr "" #. Tag: para #: boot-installer.xml:1683 #, 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:1690 #, 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 @@ -1307,7 +1796,10 @@ msgstr "" #. Tag: para #: boot-installer.xml:1700 #, 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 @@ -1319,13 +1811,24 @@ msgstr "" #. Tag: para #: boot-installer.xml:1711 #, 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:1718 #, 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 @@ -1337,7 +1840,11 @@ msgstr "" #. Tag: para #: boot-installer.xml:1734 #, 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 @@ -1349,7 +1856,10 @@ msgstr "" #. Tag: para #: boot-installer.xml:1745 #, 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 @@ -1359,29 +1869,43 @@ msgid "Booting from a Hard Disk" msgstr "" #. Tag: para -#: boot-installer.xml:1762 -#: boot-installer.xml:2360 +#: boot-installer.xml:1762 boot-installer.xml:2360 #, 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:1768 -#: boot-installer.xml:2366 +#: boot-installer.xml:1768 boot-installer.xml:2366 #, 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:1777 #, 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:1785 #, 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 @@ -1393,13 +1917,24 @@ msgstr "" #. Tag: para #: boot-installer.xml:1807 #, 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:1813 #, 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 @@ -1411,13 +1946,24 @@ msgstr "" #. Tag: para #: boot-installer.xml:1829 #, 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:1836 #, 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 @@ -1429,37 +1975,73 @@ msgstr "" #. Tag: para #: boot-installer.xml:1852 #, 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:1863 #, no-c-format -msgid "Macs require the <command>Penguin</command> bootloader. If you do not have the tools to handle a <command>Stuffit</command> archive, &penguin19.hfs; is an hfs disk image with <command>Penguin</command> unpacked. <xref linkend=\"create-floppy\"/> describes how to copy this image to a floppy." +msgid "" +"Macs require the <command>Penguin</command> bootloader. If you do not have " +"the tools to handle a <command>Stuffit</command> archive, &penguin19.hfs; is " +"an hfs disk image with <command>Penguin</command> unpacked. <xref linkend=" +"\"create-floppy\"/> describes how to copy this image to a floppy." msgstr "" #. Tag: para #: boot-installer.xml:1872 #, 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:1887 #, 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:1896 #, 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:1903 #, 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 @@ -1477,19 +2059,27 @@ msgstr "" #. Tag: para #: boot-installer.xml:1924 #, 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:1936 #, 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:2008 #, 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 @@ -1513,24 +2103,29 @@ msgstr "" #. Tag: para #: boot-installer.xml:2036 #, 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:2048 #, 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:2053 #, 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:2069 -#: boot-installer.xml:2116 +#: boot-installer.xml:2069 boot-installer.xml:2116 #, no-c-format msgid "SGI TFTP Booting" msgstr "" @@ -1541,36 +2136,42 @@ msgstr "" 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" +"</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:2089 -#: boot-installer.xml:2138 -#: boot-installer.xml:2193 +#: boot-installer.xml:2089 boot-installer.xml:2138 boot-installer.xml:2193 #: boot-installer.xml:2232 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:2090 -#: boot-installer.xml:2194 +#: boot-installer.xml:2090 boot-installer.xml:2194 #, 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" +"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" +"</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." +"</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:2113 -#: boot-installer.xml:2217 -#: boot-installer.xml:2740 +#: boot-installer.xml:2113 boot-installer.xml:2217 boot-installer.xml:2740 #, no-c-format msgid "Boot Parameters" msgstr "" @@ -1578,16 +2179,21 @@ msgstr "" #. Tag: para #: boot-installer.xml:2117 #, 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:2122 #, 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" +"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>:" +"</screen></informalexample> Further kernel parameters can be passed via " +"<command>append</command>:" msgstr "" #. Tag: screen @@ -1597,15 +2203,17 @@ msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: para -#: boot-installer.xml:2139 -#: boot-installer.xml:2233 +#: boot-installer.xml:2139 boot-installer.xml:2233 #, 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:2158 -#: boot-installer.xml:2220 +#: boot-installer.xml:2158 boot-installer.xml:2220 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "" @@ -1613,25 +2221,43 @@ msgstr "" #. Tag: para #: boot-installer.xml:2159 #, 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:2169 #, 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:2178 #, 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:2221 #, 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 @@ -1643,13 +2269,18 @@ msgstr "" #. Tag: para #: boot-installer.xml:2250 #, 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:2255 #, 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 a 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 a ssh session which will launch the standard installation system." msgstr "" #. Tag: title @@ -1661,25 +2292,44 @@ msgstr "" #. Tag: para #: boot-installer.xml:2267 #, 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. Please read <ulink url=\"&url-s390-devices;\">Device Drivers and Installation Commands</ulink> for more information about S/390-specific boot parameters." +msgid "" +"On S/390 you can append boot parameters in the parm file. This file can " +"either be in ASCII or EBCDIC format. Please read <ulink url=\"&url-s390-" +"devices;\">Device Drivers and Installation Commands</ulink> for more " +"information about S/390-specific boot parameters." msgstr "" #. Tag: para #: boot-installer.xml:2321 #, no-c-format -msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP 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 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:2330 #, 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:2339 #, 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 @@ -1715,7 +2365,15 @@ msgstr "" #. Tag: para #: boot-installer.xml:2385 #, 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 @@ -1728,11 +2386,27 @@ msgstr "" #: boot-installer.xml:2404 #, 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" +"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" +"</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." +"</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 @@ -1750,34 +2424,62 @@ msgstr "" #. Tag: para #: boot-installer.xml:2446 #, 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:2458 #, 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:2470 #, 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:2484 #, 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:2490 #, 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 @@ -1789,31 +2491,51 @@ msgstr "" #. Tag: para #: boot-installer.xml:2527 #, 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 <replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>." +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 " +"<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>," +"<replaceable>client_ipaddr</replaceable></userinput>." msgstr "" #. Tag: para #: boot-installer.xml:2542 #, 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:2554 #, 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:2560 #, 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:2567 #, 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 @@ -1825,19 +2547,37 @@ msgstr "" #. Tag: para #: boot-installer.xml:2579 #, 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:2619 #, 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. Some older OpenBoot revisions require using the device name, such as <userinput>boot le()</userinput>; these probably don't support BOOTP nor DHCP." +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. Some older " +"OpenBoot revisions require using the device name, such as <userinput>boot le" +"()</userinput>; these probably don't support BOOTP nor DHCP." msgstr "" #. Tag: para #: boot-installer.xml:2675 #, 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). You may have to use the actual device name for older OpenBoot versions that don't support this special command. Note that some problems have been reported on Sun4m (e.g., Sparc 10s and Sparc 20s) systems booting from CD-ROM." +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). You may have to use the actual " +"device name for older OpenBoot versions that don't support this special " +"command. Note that some problems have been reported on Sun4m (e.g., Sparc " +"10s and Sparc 20s) systems booting from CD-ROM." msgstr "" #. Tag: para @@ -1846,23 +2586,34 @@ msgstr "" msgid "" "To boot from floppy on a Sparc, use <informalexample><screen>\n" "Stop-A -> OpenBoot: \"boot floppy\"\n" -"</screen></informalexample> Be warned that the newer Sun4u (ultra) architecture does not support floppy booting. A typical error message is <computeroutput>Bad magic number in disk label - Can't open disk label package</computeroutput>. Furthermore, a number of Sun4c models (such as the IPX) do not support the compressed images found on the disks, so also are not supported." +"</screen></informalexample> Be warned that the newer Sun4u (ultra) " +"architecture does not support floppy booting. A typical error message is " +"<computeroutput>Bad magic number in disk label - Can't open disk label " +"package</computeroutput>. Furthermore, a number of Sun4c models (such as the " +"IPX) do not support the compressed images found on the disks, so also are " +"not supported." msgstr "" #. Tag: para #: boot-installer.xml:2702 #, no-c-format -msgid "Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from booting (instead of not supporting booting at all). The appropriate OBP update can be downloaded as product ID 106121 from <ulink url=\"http://sunsolve.sun.com\"></ulink>." +msgid "" +"Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from " +"booting (instead of not supporting booting at all). The appropriate OBP " +"update can be downloaded as product ID 106121 from <ulink url=\"http://" +"sunsolve.sun.com\"></ulink>." msgstr "" #. Tag: para #: boot-installer.xml:2709 #, no-c-format msgid "" -"If you are booting from the floppy, and you see messages such as <informalexample><screen>\n" +"If you are booting from the floppy, and you see messages such as " +"<informalexample><screen>\n" "Fatal error: Cannot read partition\n" "Illegal or malformed device name\n" -"</screen></informalexample> then it is possible that floppy booting is simply not supported on your machine." +"</screen></informalexample> then it is possible that floppy booting is " +"simply not supported on your machine." msgstr "" #. Tag: title @@ -1874,25 +2625,43 @@ msgstr "" #. Tag: para #: boot-installer.xml:2722 #, 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:2741 #, 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:2748 #, 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:2755 #, 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 @@ -1900,20 +2669,39 @@ msgstr "" #, 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." +"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:2780 #, 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:2793 #, 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 @@ -1925,7 +2713,14 @@ msgstr "" #. Tag: para #: boot-installer.xml:2805 #, no-c-format -msgid "The installation system recognizes a few additional boot parameters<footnote> <para> Note that the 2.4 kernel accepts a maximum of 8 command line options and 8 environment options (including any options added by default for the installer). If these numbers are exceeded, 2.4 kernels will drop any excess options. With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options. </para> </footnote> which may be useful." +msgid "" +"The installation system recognizes a few additional boot " +"parameters<footnote> <para> Note that the 2.4 kernel accepts a maximum of 8 " +"command line options and 8 environment options (including any options added " +"by default for the installer). If these numbers are exceeded, 2.4 kernels " +"will drop any excess options. With kernel 2.6.9 or newer, you can use 32 " +"command line options and 32 environment options. </para> </footnote> which " +"may be useful." msgstr "" #. Tag: term @@ -1937,19 +2732,32 @@ msgstr "" #. Tag: para #: boot-installer.xml:2826 #, no-c-format -msgid "This parameter sets the lowest priority of messages to be displayed. Short form: <userinput>priority</userinput>" +msgid "" +"This parameter sets the lowest priority of messages to be displayed. Short " +"form: <userinput>priority</userinput>" msgstr "" #. Tag: para #: boot-installer.xml:2831 #, 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:2838 #, 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 @@ -1961,7 +2769,24 @@ msgstr "" #. Tag: para #: boot-installer.xml:2853 #, no-c-format -msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=slang</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=ncurses</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=corba</userinput></para> </listitem> </itemizedlist> The default front end is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally only the <userinput>newt</userinput> frontend is available on default install media, so this is not very useful right now." +msgid "" +"This boot parameter controls the type of user interface used for the " +"installer. The current possible parameter settings are: <itemizedlist> " +"<listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></" +"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</" +"userinput></para> </listitem><listitem> " +"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </" +"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=slang</userinput></" +"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=ncurses</" +"userinput></para> </listitem><listitem> " +"<para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> </" +"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> " +"</listitem><listitem> <para><userinput>DEBIAN_FRONTEND=corba</userinput></" +"para> </listitem> </itemizedlist> The default front end is " +"<userinput>DEBIAN_FRONTEND=newt</userinput>. " +"<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial " +"console installs. Generally only the <userinput>newt</userinput> frontend is " +"available on default install media, so this is not very useful right now." msgstr "" #. Tag: term @@ -1973,7 +2798,11 @@ msgstr "" #. Tag: para #: boot-installer.xml:2890 #, 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 @@ -2021,7 +2850,9 @@ msgstr "" #. Tag: para #: boot-installer.xml:2915 #, 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 @@ -2033,13 +2864,18 @@ msgstr "" #. Tag: para #: boot-installer.xml:2930 #, 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:2936 #, 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 @@ -2051,13 +2887,22 @@ msgstr "" #. Tag: para #: boot-installer.xml:2947 #, no-c-format -msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature by the parameter <userinput>debian-installer/framebuffer=false</userinput>, or <userinput>fb=false</userinput> for short. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install." +msgid "" +"Some architectures use the kernel framebuffer to offer installation in a " +"number of languages. If framebuffer causes a problem on your system you can " +"disable the feature by the parameter <userinput>debian-installer/" +"framebuffer=false</userinput>, or <userinput>fb=false</userinput> for short. " +"Problem symptoms are error messages about bterm or bogl, a blank screen, or " +"a freeze within a few minutes after starting the install." msgstr "" #. Tag: para #: boot-installer.xml:2957 #, 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 @@ -2075,7 +2920,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:2971 #, 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 @@ -2087,7 +2938,9 @@ msgstr "" #. Tag: para #: boot-installer.xml:2986 #, no-c-format -msgid "Set to <userinput>false</userinput> to prevent probing for USB on boot, if that causes problems." +msgid "" +"Set to <userinput>false</userinput> to prevent probing for USB on boot, if " +"that causes problems." msgstr "" #. Tag: term @@ -2099,13 +2952,21 @@ msgstr "" #. Tag: para #: boot-installer.xml:2996 #, 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:3003 #, 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 @@ -2117,7 +2978,9 @@ msgstr "" #. Tag: para #: boot-installer.xml:3015 #, 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 @@ -2129,7 +2992,10 @@ msgstr "" #. Tag: para #: boot-installer.xml:3026 #, no-c-format -msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>url</userinput>" +msgid "" +"Specify the url to a preconfiguration file to download and use in automating " +"the install. See <xref linkend=\"automatic-install\"/>. Short form: " +"<userinput>url</userinput>" msgstr "" #. Tag: term @@ -2141,7 +3007,10 @@ msgstr "" #. Tag: para #: boot-installer.xml:3037 #, no-c-format -msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>file</userinput>" +msgid "" +"Specify the path to a preconfiguration file to load to automating the " +"install. See <xref linkend=\"automatic-install\"/>. Short form: " +"<userinput>file</userinput>" msgstr "" #. Tag: term @@ -2153,13 +3022,22 @@ msgstr "" #. Tag: para #: boot-installer.xml:3048 #, 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:3057 #, 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 @@ -2183,7 +3061,9 @@ msgstr "" #. Tag: para #: boot-installer.xml:3078 #, 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 @@ -2201,31 +3081,51 @@ msgstr "" #. Tag: para #: boot-installer.xml:3103 #, 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:3108 #, 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:3117 #, no-c-format -msgid "If you are having the installation stall at a particular floppy, the first thing you should do is re-download the floppy disk image and write it to a <emphasis>different</emphasis> floppy. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system." +msgid "" +"If you are having the installation stall at a particular floppy, the first " +"thing you should do is re-download the floppy disk image and write it to a " +"<emphasis>different</emphasis> floppy. Simply reformatting the old floppy " +"may not be sufficient, even if it appears that the floppy was reformatted " +"and written with no errors. It is sometimes useful to try writing the floppy " +"on a different system." msgstr "" #. Tag: para #: boot-installer.xml:3127 #, 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:3133 #, 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 @@ -2237,25 +3137,39 @@ msgstr "" #. Tag: para #: boot-installer.xml:3144 #, 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:3151 #, no-c-format -msgid "If you are booting with your own kernel instead of the one supplied with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>." +msgid "" +"If you are booting with your own kernel instead of the one supplied with the " +"installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your " +"kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>." msgstr "" #. Tag: para #: boot-installer.xml:3158 #, 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:3164 #, 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 @@ -2267,31 +3181,54 @@ msgstr "" #. Tag: para #: boot-installer.xml:3176 #, 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:3181 #, 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:3187 #, 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:3196 #, 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:3203 #, no-c-format -msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false video=vga16:off</userinput> to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." +msgid "" +"If your screen begins to show a weird picture while the kernel boots, eg. " +"pure white, pure black or colored pixel garbage, your system may contain a " +"problematic video card which does not switch to the framebuffer mode " +"properly. Then you can use the boot parameter <userinput>fb=false " +"video=vga16:off</userinput> to disable the framebuffer console. Only the " +"English language will be available during the installation due to limited " +"console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" #. Tag: title @@ -2303,13 +3240,28 @@ msgstr "" #. Tag: para #: boot-installer.xml:3218 #, 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:3228 #, 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 @@ -2321,7 +3273,14 @@ msgstr "" #. Tag: para #: boot-installer.xml:3246 #, no-c-format -msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter at the boot prompt, which will prevent the modules from being loaded." +msgid "" +"The kernel normally tries to install USB modules and the USB keyboard driver " +"in order to support some non-standard USB keyboards. However, there are some " +"broken USB systems where the driver hangs on loading. A possible workaround " +"may be disabling the USB controller in your mainboard BIOS setup. Another " +"option is passing the <userinput>debian-installer/probe/usb=false</" +"userinput> parameter at the boot prompt, which will prevent the modules from " +"being loaded." msgstr "" #. Tag: title @@ -2333,7 +3292,22 @@ msgstr "" #. Tag: para #: boot-installer.xml:3262 #, 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 @@ -2345,13 +3319,22 @@ msgstr "" #. Tag: para #: boot-installer.xml:3288 #, no-c-format -msgid "If you get through the initial boot phase but cannot complete the install, the bug reporter menu choice may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them in a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report you may want to attach this information to the bug report." +msgid "" +"If you get through the initial boot phase but cannot complete the install, " +"the bug reporter menu choice may be helpful. It lets you store system error " +"logs and configuration information from the installer to a floppy, or " +"download them in a web browser. This information may provide clues as to " +"what went wrong and how to fix it. If you are submitting a bug report you " +"may want to attach this information to the bug report." msgstr "" #. Tag: para #: boot-installer.xml:3299 #, 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 @@ -2363,20 +3346,31 @@ msgstr "" #. Tag: para #: boot-installer.xml:3311 #, 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:3318 #, no-c-format -msgid "If you have a working Debian system, the easiest way to send an installation report is to install the installation-report and reportbug packages (<command>apt-get install installation-report reportbug</command>) and run the command <command>reportbug installation-report</command>." +msgid "" +"If you have a working Debian system, the easiest way to send an installation " +"report is to install the installation-report and reportbug packages " +"(<command>apt-get install installation-report reportbug</command>) and run " +"the command <command>reportbug installation-report</command>." msgstr "" #. Tag: para #: boot-installer.xml:3325 #, no-c-format msgid "" -"Please use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n" +"Please use this template when filling out installation reports, and file the " +"report as a bug report against the <classname>installation-reports</" +"classname> pseudo package, by sending it to <email>submit@bugs.debian.org</" +"email>. <informalexample><screen>\n" "Package: installation-reports\n" "\n" "Boot method: <How did you boot the installer? CD? floppy? network?>\n" @@ -2410,6 +3404,8 @@ msgid "" "\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." +"</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/hu/install-methods.po b/po/hu/install-methods.po index b71fbd01f..cb7096cd8 100644 --- a/po/hu/install-methods.po +++ b/po/hu/install-methods.po @@ -4,12 +4,13 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: \n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2006-08-18 17:32+0000\n" "PO-Revision-Date: 2006-09-12 23:57+0100\n" "Last-Translator: SZERVÁC Attila <sas@321.hu>\n" "Language-Team: Hungarian <debian-l10n-hungarian@lists.debian>\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Poedit-Language: Hungarian\n" @@ -30,26 +31,79 @@ msgstr "Hivatalos &debian; CD-ROM készletek" #. Tag: para #: install-methods.xml:13 #, no-c-format -msgid "By far the easiest way to install &debian; is from an Official Debian CD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD-ROM images from a Debian mirror and make your own set, if you have a fast network connection and a CD burner (see the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink> for detailed instructions). If you have a Debian CD set and CDs are bootable on your machine, you can skip right to <xref linkend=\"boot-installer\"/>; much effort has been expended to ensure the files most people need are there on the CD. Although a full set of binary packages requires several CDs, it is unlikely you will need packages on the third CD and above. You may also consider using the DVD version, which saves a lot of space on your shelf and you avoid the CD shuffling marathon." -msgstr "A &debian; legegyszerűbb telepítése a Hivatalos Debian CD-ROM Készlet segítségével lehetséges. Ez boltban is megvásárolható (lásd a <ulink url=\"&url-debian-cd-vendors;\">CD-forgalmazók oldala</ulink>) lapot. A CD-ROM képek letölthetők egy Debian tükörről is, így egy közepes hálózati kapcsolattal és egy CD-íróval a CD-ROM készlet egyénileg is elkészíthető." +msgid "" +"By far the easiest way to install &debian; is from an Official Debian CD-ROM " +"Set. You can buy a set from a vendor (see the <ulink url=\"&url-debian-cd-" +"vendors;\">CD vendors page</ulink>). You may also download the CD-ROM images " +"from a Debian mirror and make your own set, if you have a fast network " +"connection and a CD burner (see the <ulink url=\"&url-debian-cd;\">Debian CD " +"page</ulink> for detailed instructions). If you have a Debian CD set and CDs " +"are bootable on your machine, you can skip right to <xref linkend=\"boot-" +"installer\"/>; much effort has been expended to ensure the files most people " +"need are there on the CD. Although a full set of binary packages requires " +"several CDs, it is unlikely you will need packages on the third CD and " +"above. You may also consider using the DVD version, which saves a lot of " +"space on your shelf and you avoid the CD shuffling marathon." +msgstr "" +"A &debian; legegyszerűbb telepítése a Hivatalos Debian CD-ROM Készlet " +"segítségével lehetséges. Ez boltban is megvásárolható (lásd a <ulink url=" +"\"&url-debian-cd-vendors;\">CD-forgalmazók oldala</ulink>) lapot. A CD-ROM " +"képek letölthetők egy Debian tükörről is, így egy közepes hálózati " +"kapcsolattal és egy CD-íróval a CD-ROM készlet egyénileg is elkészíthető." #. Tag: para #: install-methods.xml:30 #, no-c-format -msgid "If your machine doesn't support CD booting, but you do have a CD set, you can use an alternative strategy such as <phrase condition=\"supports-floppy-boot\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net boot,</phrase> or manually loading the kernel from the CD to initially boot the system installer. The files you need for booting by another means are also on the CD; the Debian network archive and CD folder organization are identical. So when archive file paths are given below for particular files you need for booting, look for those files in the same directories and subdirectories on your CD." -msgstr "Ha a géped nem támogatja a CD lemezről indítást, noha van CD készleted, más módszerek is léteznek például: <phrase condition=\"supports-floppy-boot\">flopi lemez,</phrase> <phrase arch=\"s390\">szalag, emulált szalag,</phrase> <phrase condition=\"bootable-disk\">merevlemez,</phrase> <phrase condition=\"bootable-usb\">usb tár,</phrase> <phrase condition=\"supports-tftp\">hálózati indítás,</phrase> vagy a kernel kézi betöltése a CD lemezről a rendszer telepítő indításához. A más módszerű indításhoz szükséges fájlok is rajta vannak a CD lemezen; a Debian hálózati archívum és a CD mappa-szervezése egyezik. Így, mikor alább az indításhoz szükséges archívum fájl ösvényeket látod, e fájlok a CD egyező könyvtáraiban és alkönyvtáraiban vannak." +msgid "" +"If your machine doesn't support CD booting, but you do have a CD set, you " +"can use an alternative strategy such as <phrase condition=\"supports-floppy-" +"boot\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</" +"phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase " +"condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-" +"tftp\">net boot,</phrase> or manually loading the kernel from the CD to " +"initially boot the system installer. The files you need for booting by " +"another means are also on the CD; the Debian network archive and CD folder " +"organization are identical. So when archive file paths are given below for " +"particular files you need for booting, look for those files in the same " +"directories and subdirectories on your CD." +msgstr "" +"Ha a géped nem támogatja a CD lemezről indítást, noha van CD készleted, más " +"módszerek is léteznek például: <phrase condition=\"supports-floppy-boot" +"\">flopi lemez,</phrase> <phrase arch=\"s390\">szalag, emulált szalag,</" +"phrase> <phrase condition=\"bootable-disk\">merevlemez,</phrase> <phrase " +"condition=\"bootable-usb\">usb tár,</phrase> <phrase condition=\"supports-" +"tftp\">hálózati indítás,</phrase> vagy a kernel kézi betöltése a CD lemezről " +"a rendszer telepítő indításához. A más módszerű indításhoz szükséges fájlok " +"is rajta vannak a CD lemezen; a Debian hálózati archívum és a CD mappa-" +"szervezése egyezik. Így, mikor alább az indításhoz szükséges archívum fájl " +"ösvényeket látod, e fájlok a CD egyező könyvtáraiban és alkönyvtáraiban " +"vannak." #. Tag: para #: install-methods.xml:52 #, no-c-format -msgid "Once the installer is booted, it will be able to obtain all the other files it needs from the CD." +msgid "" +"Once the installer is booted, it will be able to obtain all the other files " +"it needs from the CD." msgstr "Mihelyst a telepítő elindult, minden fájlt megtalál a CD lemezen." #. Tag: para #: install-methods.xml:57 #, no-c-format -msgid "If you don't have a CD set, then you will need to download the installer system files and place them on the <phrase arch=\"s390\">installation tape</phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> <phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition=\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a connected computer</phrase> so they can be used to boot the installer." -msgstr "Ha nincs CD-készleted, le kell töltened a telepítő rendszer fájlokat és elhelyezni őket <phrase arch=\"s390\">a telepítő szalagon</phrase> <phrase condition=\"supports-floppy-boot\">flopi lemezen vagy</phrase> <phrase condition=\"bootable-disk\">merevlemezen vagy</phrase> <phrase condition=\"bootable-usb\">usb táron vagy</phrase> <phrase condition=\"supports-tftp\">egy kapcsolódó gépen</phrase> így erről indítható a telepítő." +msgid "" +"If you don't have a CD set, then you will need to download the installer " +"system files and place them on the <phrase arch=\"s390\">installation tape</" +"phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> " +"<phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition=" +"\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a " +"connected computer</phrase> so they can be used to boot the installer." +msgstr "" +"Ha nincs CD-készleted, le kell töltened a telepítő rendszer fájlokat és " +"elhelyezni őket <phrase arch=\"s390\">a telepítő szalagon</phrase> <phrase " +"condition=\"supports-floppy-boot\">flopi lemezen vagy</phrase> <phrase " +"condition=\"bootable-disk\">merevlemezen vagy</phrase> <phrase condition=" +"\"bootable-usb\">usb táron vagy</phrase> <phrase condition=\"supports-tftp" +"\">egy kapcsolódó gépen</phrase> így erről indítható a telepítő." #. Tag: title #: install-methods.xml:83 @@ -60,14 +114,22 @@ msgstr "Fájlok letöltése a Debian Tükrökről" #. Tag: para #: install-methods.xml:85 #, no-c-format -msgid "To find the nearest (and thus probably the fastest) mirror, see the <ulink url=\"&url-debian-mirrors;\">list of Debian mirrors</ulink>." -msgstr "A legközelebbi (és alighanem leggyorsabb) tükör megtalálásához lásd a <ulink url=\"&url-debian-mirrors;\">Debian tükrök</ulink> listáját." +msgid "" +"To find the nearest (and thus probably the fastest) mirror, see the <ulink " +"url=\"&url-debian-mirrors;\">list of Debian mirrors</ulink>." +msgstr "" +"A legközelebbi (és alighanem leggyorsabb) tükör megtalálásához lásd a <ulink " +"url=\"&url-debian-mirrors;\">Debian tükrök</ulink> listáját." #. Tag: para #: install-methods.xml:90 #, no-c-format -msgid "When downloading files from a Debian mirror, be sure to download the files in <emphasis>binary</emphasis> mode, not text or automatic mode." -msgstr "Fájlok letöltésekor egy Debian tükörről azokat mindig <emphasis>bináris</emphasis> módban töltsd, ne szöveges vagy automata módban." +msgid "" +"When downloading files from a Debian mirror, be sure to download the files " +"in <emphasis>binary</emphasis> mode, not text or automatic mode." +msgstr "" +"Fájlok letöltésekor egy Debian tükörről azokat mindig <emphasis>bináris</" +"emphasis> módban töltsd, ne szöveges vagy automata módban." #. Tag: title #: install-methods.xml:99 @@ -78,8 +140,18 @@ msgstr "A telepítő képek fellelése" #. Tag: para #: install-methods.xml:101 #, no-c-format -msgid "The installation images are located on each Debian mirror in the directory <ulink url=\"&url-debian-installer;/images\">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> — the <ulink url=\"&url-debian-installer;/images/MANIFEST\">MANIFEST</ulink> lists each image and its purpose." -msgstr "A telepítő képek minden Debian tükrön a <ulink url=\"&url-debian-installer;/images\">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> könyvtárban vannak — a <ulink url=\"&url-debian-installer;/images/MANIFEST\">MANIFEST</ulink> fájl felsorolja őket és céljaikat." +msgid "" +"The installation images are located on each Debian mirror in the directory " +"<ulink url=\"&url-debian-installer;/images\">debian/dists/&releasename;/main/" +"installer-&architecture;/current/images/</ulink> — the <ulink url=" +"\"&url-debian-installer;/images/MANIFEST\">MANIFEST</ulink> lists each image " +"and its purpose." +msgstr "" +"A telepítő képek minden Debian tükrön a <ulink url=\"&url-debian-installer;/" +"images\">debian/dists/&releasename;/main/installer-&architecture;/current/" +"images/</ulink> könyvtárban vannak — a <ulink url=\"&url-debian-" +"installer;/images/MANIFEST\">MANIFEST</ulink> fájl felsorolja őket és " +"céljaikat." #. Tag: title #: install-methods.xml:113 @@ -90,19 +162,37 @@ msgstr "" #. Tag: para #: install-methods.xml:114 #, no-c-format -msgid "If you choose to boot from ARC console firmware using <command>MILO</command>, you will also need to prepare a disk containing <command>MILO</command> and <command>LINLOAD.EXE</command> from the provided disk images. See <xref linkend=\"alpha-firmware\"/> for more information on Alpha firmware and boot loaders. The floppy images can be found in the <filename>MILO</filename> directory as <filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>." +msgid "" +"If you choose to boot from ARC console firmware using <command>MILO</" +"command>, you will also need to prepare a disk containing <command>MILO</" +"command> and <command>LINLOAD.EXE</command> from the provided disk images. " +"See <xref linkend=\"alpha-firmware\"/> for more information on Alpha " +"firmware and boot loaders. The floppy images can be found in the " +"<filename>MILO</filename> directory as " +"<filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>." msgstr "" #. Tag: para #: install-methods.xml:125 #, no-c-format -msgid "Unfortunately, these <command>MILO</command> images could not be tested and might not work for all subarchitectures. If you find it doesn't work for you, try copying the appropriate <command>MILO</command> binary onto the floppy (<ulink url=\"&disturlftp;main/disks-alpha/current/MILO/\"></ulink>). Note that those <command>MILO</command>s don't support ext2 <quote>sparse superblocks</quote>, so you can't use them to load kernels from newly generated ext2 file systems. As a workaround, you can put your kernel onto the FAT partition next to the <command>MILO</command>." +msgid "" +"Unfortunately, these <command>MILO</command> images could not be tested and " +"might not work for all subarchitectures. If you find it doesn't work for " +"you, try copying the appropriate <command>MILO</command> binary onto the " +"floppy (<ulink url=\"&disturlftp;main/disks-alpha/current/MILO/\"></ulink>). " +"Note that those <command>MILO</command>s don't support ext2 <quote>sparse " +"superblocks</quote>, so you can't use them to load kernels from newly " +"generated ext2 file systems. As a workaround, you can put your kernel onto " +"the FAT partition next to the <command>MILO</command>." msgstr "" #. Tag: para #: install-methods.xml:137 #, no-c-format -msgid "<command>MILO</command> binaries are platform-specific. See <xref linkend=\"alpha-cpus\"/> to determine the appropriate <command>MILO</command> image for your Alpha platform." +msgid "" +"<command>MILO</command> binaries are platform-specific. See <xref linkend=" +"\"alpha-cpus\"/> to determine the appropriate <command>MILO</command> image " +"for your Alpha platform." msgstr "" #. Tag: title @@ -114,7 +204,11 @@ msgstr "" #. Tag: para #: install-methods.xml:153 #, no-c-format -msgid "The RiscPC installer is booted initially from RISC OS. All the necessary files are provided in one Zip archive, &rpc-install-kit;. Download this file onto the RISC OS machine, copy the <filename>linloader.!Boot</filename> components into place, and run <filename>!dInstall</filename>." +msgid "" +"The RiscPC installer is booted initially from RISC OS. All the necessary " +"files are provided in one Zip archive, &rpc-install-kit;. Download this file " +"onto the RISC OS machine, copy the <filename>linloader.!Boot</filename> " +"components into place, and run <filename>!dInstall</filename>." msgstr "" #. Tag: title @@ -126,7 +220,9 @@ msgstr "" #. Tag: para #: install-methods.xml:166 #, no-c-format -msgid "The easiest way to boot a Netwinder is over the network, using the supplied TFTP image &netwinder-boot-img;." +msgid "" +"The easiest way to boot a Netwinder is over the network, using the supplied " +"TFTP image &netwinder-boot-img;." msgstr "" #. Tag: title @@ -138,7 +234,9 @@ msgstr "" #. Tag: para #: install-methods.xml:176 #, no-c-format -msgid "CATS can be booted either via the network or from CD-ROM. The kernel and initrd can be obtained from &cats-boot-img;." +msgid "" +"CATS can be booted either via the network or from CD-ROM. The kernel and " +"initrd can be obtained from &cats-boot-img;." msgstr "" #. Tag: title @@ -150,7 +248,10 @@ msgstr "" #. Tag: para #: install-methods.xml:186 #, no-c-format -msgid "A firmware image is provided for the Linksys NSLU2 which will automatically boot <classname>debian-installer</classname>. This firmware image can be obtained from &nslu2-firmware-img;." +msgid "" +"A firmware image is provided for the Linksys NSLU2 which will automatically " +"boot <classname>debian-installer</classname>. This firmware image can be " +"obtained from &nslu2-firmware-img;." msgstr "" #. Tag: title @@ -162,13 +263,20 @@ msgstr "" #. Tag: para #: install-methods.xml:234 #, no-c-format -msgid "Some m68k subarchs have a choice of kernels to install. In general we recommend trying the most recent version first. If your subarch or machine needs to use a 2.2.x kernel, make sure you choose one of the images that supports 2.2.x kernels (see the <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink>)." +msgid "" +"Some m68k subarchs have a choice of kernels to install. In general we " +"recommend trying the most recent version first. If your subarch or machine " +"needs to use a 2.2.x kernel, make sure you choose one of the images that " +"supports 2.2.x kernels (see the <ulink url=\"&disturl;/main/installer-" +"&architecture;/current/images/MANIFEST\">MANIFEST</ulink>)." msgstr "" #. Tag: para #: install-methods.xml:243 #, no-c-format -msgid "All of the m68k images for use with 2.2.x kernels, require the kernel parameter &ramdisksize;." +msgid "" +"All of the m68k images for use with 2.2.x kernels, require the kernel " +"parameter &ramdisksize;." msgstr "" #. Tag: title @@ -180,7 +288,15 @@ msgstr "" #. Tag: para #: install-methods.xml:263 #, no-c-format -msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>." +msgid "" +"If you can't boot (IPL) from the CD-ROM and you are not using VM you need to " +"create an IPL tape first. This is described in section 3.4.3 in the <ulink " +"url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux " +"for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files " +"you need to write to the tape are (in this order): <filename>kernel.debian</" +"filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</" +"filename>. The files can be downloaded from the <filename>tape</filename> " +"sub-directory, see <xref linkend=\"where-files\"/>." msgstr "" #. Tag: title @@ -192,37 +308,56 @@ msgstr "" #. Tag: para #: install-methods.xml:288 #, no-c-format -msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means." +msgid "" +"Bootable floppy disks are generally used as a last resort to boot the " +"installer on hardware that cannot boot from CD or by other means." msgstr "" #. Tag: para #: install-methods.xml:293 #, no-c-format -msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives." +msgid "" +"Booting the installer from floppy disk reportedly fails on Mac USB floppy " +"drives." msgstr "" #. Tag: para #: install-methods.xml:298 #, no-c-format -msgid "Booting the installer from floppy disk is not supported on Amigas or 68k Macs." +msgid "" +"Booting the installer from floppy disk is not supported on Amigas or 68k " +"Macs." msgstr "" #. Tag: para #: install-methods.xml:303 #, no-c-format -msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy." +msgid "" +"Disk images are files containing the complete contents of a floppy disk in " +"<emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</" +"filename>, cannot simply be copied to floppy drives. A special program is " +"used to write the image files to floppy disk in <emphasis>raw</emphasis> " +"mode. This is required because these images are raw representations of the " +"disk; it is required to do a <emphasis>sector copy</emphasis> of the data " +"from the file onto the floppy." msgstr "" #. Tag: para #: install-methods.xml:314 #, no-c-format -msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms." +msgid "" +"There are different techniques for creating floppies from disk images. This " +"section describes how to create floppies from disk images on different " +"platforms." msgstr "" #. Tag: para #: install-methods.xml:320 #, no-c-format -msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally." +msgid "" +"No matter which method you use to create your floppies, you should remember " +"to flip the write-protect tab on the floppies once you have written them, to " +"ensure they are not damaged unintentionally." msgstr "" #. Tag: title @@ -235,21 +370,52 @@ msgstr "" #: install-methods.xml:329 #, no-c-format msgid "" -"To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n" -"$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync\n" -"</screen></informalexample> where <replaceable>filename</replaceable> is one of the floppy disk image files (see <xref linkend=\"downloading-files\"/> for what <replaceable>filename</replaceable> should be). <filename>/dev/fd0</filename> is a commonly used name of the floppy disk device, it may be different on your workstation <phrase arch=\"sparc\">(on Solaris, it is <filename>/dev/fd/0</filename>)</phrase>. The command may return to the prompt before Unix has finished writing the floppy disk, so look for the disk-in-use light on the floppy drive and be sure that the light is out and the disk has stopped revolving before you remove it from the drive. On some systems, you'll have to run a command to eject the floppy from the drive <phrase arch=\"sparc\">(on Solaris, use <command>eject</command>, see the manual page)</phrase>." +"To write the floppy disk image files to the floppy disks, you will probably " +"need root access to the system. Place a good, blank floppy in the floppy " +"drive. Next, use the command <informalexample><screen>\n" +"$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; " +"sync\n" +"</screen></informalexample> where <replaceable>filename</replaceable> is one " +"of the floppy disk image files (see <xref linkend=\"downloading-files\"/> " +"for what <replaceable>filename</replaceable> should be). <filename>/dev/fd0</" +"filename> is a commonly used name of the floppy disk device, it may be " +"different on your workstation <phrase arch=\"sparc\">(on Solaris, it is " +"<filename>/dev/fd/0</filename>)</phrase>. The command may return to the " +"prompt before Unix has finished writing the floppy disk, so look for the " +"disk-in-use light on the floppy drive and be sure that the light is out and " +"the disk has stopped revolving before you remove it from the drive. On some " +"systems, you'll have to run a command to eject the floppy from the drive " +"<phrase arch=\"sparc\">(on Solaris, use <command>eject</command>, see the " +"manual page)</phrase>." msgstr "" #. Tag: para #: install-methods.xml:353 #, no-c-format -msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>" +msgid "" +"Some systems attempt to automatically mount a floppy disk when you place it " +"in the drive. You might have to disable this feature before the workstation " +"will allow you to write a floppy in <emphasis>raw mode</emphasis>. " +"Unfortunately, how to accomplish this will vary based on your operating " +"system. <phrase arch=\"sparc\"> On Solaris, you can work around volume " +"management to get raw access to the floppy. First, make sure that the floppy " +"is auto-mounted (using <command>volcheck</command> or the equivalent command " +"in the file manager). Then use a <command>dd</command> command of the form " +"given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/" +"rdsk/<replaceable>floppy_name</replaceable></filename>, where " +"<replaceable>floppy_name</replaceable> is the name the floppy disk was given " +"when it was formatted (unnamed floppies default to the name " +"<filename>unnamed_floppy</filename>). On other systems, ask your system " +"administrator. </phrase>" msgstr "" #. Tag: para #: install-methods.xml:374 #, no-c-format -msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it." +msgid "" +"If writing a floppy on powerpc Linux, you will need to eject it. The " +"<command>eject</command> program handles this nicely; you might need to " +"install it." msgstr "" #. Tag: title @@ -261,25 +427,37 @@ msgstr "" #. Tag: para #: install-methods.xml:394 #, no-c-format -msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies." +msgid "" +"If you have access to an i386 or amd64 machine, you can use one of the " +"following programs to copy images to floppies." msgstr "" #. Tag: para #: install-methods.xml:399 #, no-c-format -msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work." +msgid "" +"The <command>rawrite1</command> and <command>rawrite2</command> programs can " +"be used under MS-DOS. To use these programs, first make sure that you are " +"booted into DOS. Trying to use these programs from within a DOS box in " +"Windows, or double-clicking on these programs from the Windows Explorer is " +"<emphasis>not</emphasis> expected to work." msgstr "" #. Tag: para #: install-methods.xml:407 #, no-c-format -msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory." +msgid "" +"The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, " +"ME, XP and probably later versions. To use it you will need to unpack diskio." +"dll in the same directory." msgstr "" #. Tag: para #: install-methods.xml:413 #, no-c-format -msgid "These tools can be found on the Official Debian CD-ROMs under the <filename>/tools</filename> directory." +msgid "" +"These tools can be found on the Official Debian CD-ROMs under the <filename>/" +"tools</filename> directory." msgstr "" #. Tag: title @@ -291,7 +469,11 @@ msgstr "" #. Tag: para #: install-methods.xml:427 #, no-c-format -msgid "You'll find the &rawwrite.ttp; program in the same directory as the floppy disk images. Start the program by double clicking on the program icon, and type in the name of the floppy image file you want written to the floppy at the TOS program command line dialog box." +msgid "" +"You'll find the &rawwrite.ttp; program in the same directory as the floppy " +"disk images. Start the program by double clicking on the program icon, and " +"type in the name of the floppy image file you want written to the floppy at " +"the TOS program command line dialog box." msgstr "" #. Tag: title @@ -303,7 +485,12 @@ msgstr "" #. Tag: para #: install-methods.xml:439 #, no-c-format -msgid "There is no MacOS application to write images to floppy disks (and there would be no point in doing this as you can't use these floppies to boot the installation system or install kernel and modules from on Macintosh). However, these files are needed for the installation of the operating system and modules, later in the process." +msgid "" +"There is no MacOS application to write images to floppy disks (and there " +"would be no point in doing this as you can't use these floppies to boot the " +"installation system or install kernel and modules from on Macintosh). " +"However, these files are needed for the installation of the operating system " +"and modules, later in the process." msgstr "" #. Tag: title @@ -315,13 +502,25 @@ msgstr "" #. Tag: para #: install-methods.xml:458 #, no-c-format -msgid "An AppleScript, <application>Make Debian Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it." +msgid "" +"An AppleScript, <application>Make Debian Floppy</application>, is available " +"for burning floppies from the provided disk image files. It can be " +"downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/" +"debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on " +"your desktop, and then drag any floppy image file to it. You must have " +"Applescript installed and enabled in your extensions manager. Disk Copy will " +"ask you to confirm that you wish to erase the floppy and proceed to write " +"the file image to it." msgstr "" #. Tag: para #: install-methods.xml:469 #, no-c-format -msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities." +msgid "" +"You can also use the MacOS utility <command>Disk Copy</command> directly, or " +"the freeware utility <command>suntar</command>. The <filename>root.bin</" +"filename> file is an example of a floppy image. Use one of the following " +"methods to create a floppy from the floppy image with these utilities." msgstr "" #. Tag: title @@ -333,37 +532,59 @@ msgstr "" #. Tag: para #: install-methods.xml:481 #, no-c-format -msgid "If you are creating the floppy image from files which were originally on the official &debian; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a Debian mirror." +msgid "" +"If you are creating the floppy image from files which were originally on the " +"official &debian; CD, then the Type and Creator are already set correctly. " +"The following <command>Creator-Changer</command> steps are only necessary if " +"you downloaded the image files from a Debian mirror." msgstr "" #. Tag: para #: install-methods.xml:490 #, no-c-format -msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file." +msgid "" +"Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> " +"and use it to open the <filename>root.bin</filename> file." msgstr "" #. Tag: para #: install-methods.xml:497 #, no-c-format -msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields." +msgid "" +"Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type " +"to <userinput>DDim</userinput> (binary floppy image). The case is sensitive " +"for these fields." msgstr "" #. Tag: para #: install-methods.xml:504 #, no-c-format -msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted." +msgid "" +"<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</" +"userinput> to display the Finder information about the floppy image, and " +"<quote>X</quote> the <userinput>File Locked</userinput> check box so that " +"MacOS will be unable to remove the boot blocks if the image is accidentally " +"mounted." msgstr "" #. Tag: para #: install-methods.xml:513 #, no-c-format -msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>." +msgid "" +"Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it " +"will very likely be there already, otherwise try <ulink url=\"&url-powerpc-" +"diskcopy;\"></ulink>." msgstr "" #. Tag: para #: install-methods.xml:520 #, no-c-format -msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy." +msgid "" +"Run <command>Disk Copy</command>, and select <menuchoice> " +"<guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </" +"menuchoice>, then select the <emphasis>locked</emphasis> image file from the " +"resulting dialog. It will ask you to insert a floppy, then ask if you really " +"want to erase it. When done it should eject the floppy." msgstr "" #. Tag: title @@ -375,31 +596,44 @@ msgstr "" #. Tag: para #: install-methods.xml:539 #, no-c-format -msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu." +msgid "" +"Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </" +"ulink>. Start the <command>suntar</command> program and select " +"<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> " +"menu." msgstr "" #. Tag: para #: install-methods.xml:547 #, no-c-format -msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)." +msgid "" +"Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)." msgstr "" #. Tag: para #: install-methods.xml:553 #, no-c-format -msgid "Select the <filename>root.bin</filename> file in the file-opening dialog." +msgid "" +"Select the <filename>root.bin</filename> file in the file-opening dialog." msgstr "" #. Tag: para #: install-methods.xml:558 #, no-c-format -msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another." +msgid "" +"After the floppy has been created successfully, select <menuchoice> " +"<guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If " +"there are any errors writing the floppy, simply toss that floppy and try " +"another." msgstr "" #. Tag: para #: install-methods.xml:566 #, no-c-format -msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it." +msgid "" +"Before using the floppy you created, <emphasis>set the write protect tab</" +"emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will " +"helpfully ruin it." msgstr "" #. Tag: title @@ -411,13 +645,21 @@ msgstr "" #. Tag: para #: install-methods.xml:587 #, no-c-format -msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. You should ensure that the usb-storage kernel module is loaded (<userinput>modprobe usb-storage</userinput>) and try to find out which SCSI device the USB stick has been mapped to (in this example <filename>/dev/sda</filename> is used). To write to your stick, you may have to turn off its write protection switch." +msgid "" +"To prepare the USB stick, you will need a system where GNU/Linux is already " +"running and where USB is supported. You should ensure that the usb-storage " +"kernel module is loaded (<userinput>modprobe usb-storage</userinput>) and " +"try to find out which SCSI device the USB stick has been mapped to (in this " +"example <filename>/dev/sda</filename> is used). To write to your stick, you " +"may have to turn off its write protection switch." msgstr "" #. Tag: para #: install-methods.xml:597 #, no-c-format -msgid "Note that the USB stick should be at least 256 MB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)." +msgid "" +"Note that the USB stick should be at least 256 MB in size (smaller setups " +"are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)." msgstr "" #. Tag: title @@ -429,7 +671,11 @@ msgstr "" #. Tag: para #: install-methods.xml:606 #, no-c-format -msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) as well as <command>SYSLINUX</command> and its configuration file. You only have to extract it directly to your USB stick:" +msgid "" +"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which " +"contains all the installer files (including the kernel) as well as " +"<command>SYSLINUX</command> and its configuration file. You only have to " +"extract it directly to your USB stick:" msgstr "" #. Tag: screen @@ -441,7 +687,13 @@ msgstr "" #. Tag: para #: install-methods.xml:615 #, no-c-format -msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) as well as <command>yaboot</command> and its configuration file. Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:" +msgid "" +"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which " +"contains all the installer files (including the kernel) as well as " +"<command>yaboot</command> and its configuration file. Create a partition of " +"type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</" +"command>'s <userinput>C</userinput> command and extract the image directly " +"to that:" msgstr "" #. Tag: screen @@ -453,13 +705,22 @@ msgstr "" #. Tag: para #: install-methods.xml:627 #, no-c-format -msgid "Using this method will destroy anything already on the device. Make sure that you use the correct device name for your USB stick." +msgid "" +"Using this method will destroy anything already on the device. Make sure " +"that you use the correct device name for your USB stick." msgstr "" #. Tag: para #: install-methods.xml:633 #, no-c-format -msgid "After that, mount the USB memory stick (<userinput>mount <replaceable arch=\"x86\">/dev/sda</replaceable> <replaceable arch=\"powerpc\">/dev/sda2</replaceable> /mnt</userinput>), which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a Debian netinst or businesscard ISO image to it. Please note that the file name must end in <filename>.iso</filename>. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done." +msgid "" +"After that, mount the USB memory stick (<userinput>mount <replaceable arch=" +"\"x86\">/dev/sda</replaceable> <replaceable arch=\"powerpc\">/dev/sda2</" +"replaceable> /mnt</userinput>), which will now have <phrase arch=\"x86\">a " +"FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> " +"on it, and copy a Debian netinst or businesscard ISO image to it. Please " +"note that the file name must end in <filename>.iso</filename>. Unmount the " +"stick (<userinput>umount /mnt</userinput>) and you are done." msgstr "" #. Tag: title @@ -471,12 +732,13 @@ msgstr "" #. Tag: para #: install-methods.xml:650 #, no-c-format -msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick." +msgid "" +"If you like more flexibility or just want to know what's going on, you " +"should use the following method to put the files on your stick." msgstr "" #. Tag: title -#: install-methods.xml:662 -#: install-methods.xml:754 +#: install-methods.xml:662 install-methods.xml:754 #, no-c-format msgid "USB stick partitioning on &arch-title;" msgstr "" @@ -484,81 +746,136 @@ msgstr "" #. Tag: para #: install-methods.xml:663 #, no-c-format -msgid "We will show how to setup the memory stick to use the first partition, instead of the entire device." +msgid "" +"We will show how to setup the memory stick to use the first partition, " +"instead of the entire device." msgstr "" #. Tag: para #: install-methods.xml:668 #, no-c-format msgid "" -"Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition, and then create the filesystem using: <informalexample><screen>\n" +"Since most USB sticks come pre-configured with a single FAT16 partition, you " +"probably won't have to repartition or reformat the stick. If you have to do " +"that anyway, use <command>cfdisk</command> or any other partitioning tool to " +"create a FAT16 partition, and then create the filesystem using: " +"<informalexample><screen>\n" "# mkdosfs /dev/<replaceable>sda1</replaceable>\n" -"</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>mkdosfs</command> command is contained in the <classname>dosfstools</classname> Debian package." +"</screen></informalexample> Take care that you use the correct device name " +"for your USB stick. The <command>mkdosfs</command> command is contained in " +"the <classname>dosfstools</classname> Debian package." msgstr "" #. Tag: para #: install-methods.xml:682 #, no-c-format -msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <command>LILO</command>) should work, it's convenient to use <command>SYSLINUX</command>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader." +msgid "" +"In order to start the kernel after booting from the USB stick, we will put a " +"boot loader on the stick. Although any boot loader (e.g. <command>LILO</" +"command>) should work, it's convenient to use <command>SYSLINUX</command>, " +"since it uses a FAT16 partition and can be reconfigured by just editing a " +"text file. Any operating system which supports the FAT file system can be " +"used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para #: install-methods.xml:692 #, no-c-format msgid "" -"To put <command>SYSLINUX</command> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n" +"To put <command>SYSLINUX</command> on the FAT16 partition on your USB stick, " +"install the <classname>syslinux</classname> and <classname>mtools</" +"classname> packages on your system, and do: <informalexample><screen>\n" "# syslinux /dev/<replaceable>sda1</replaceable>\n" -"</screen></informalexample> Again, take care that you use the correct device name. The partition must not be mounted when starting <command>SYSLINUX</command>. This procedure writes a boot sector to the partition and creates the file <filename>ldlinux.sys</filename> which contains the boot loader code." +"</screen></informalexample> Again, take care that you use the correct device " +"name. The partition must not be mounted when starting <command>SYSLINUX</" +"command>. This procedure writes a boot sector to the partition and creates " +"the file <filename>ldlinux.sys</filename> which contains the boot loader " +"code." msgstr "" #. Tag: para #: install-methods.xml:705 #, no-c-format -msgid "Mount the partition (<userinput>mount /dev/sda1 /mnt</userinput>) and copy the following files from the Debian archives to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> <listitem><para> <filename>syslinux.cfg</filename> (SYSLINUX configuration file) </para></listitem> <listitem><para> Optional kernel modules </para></listitem> </itemizedlist> If you want to rename the files, please note that <command>SYSLINUX</command> can only process DOS (8.3) file names." +msgid "" +"Mount the partition (<userinput>mount /dev/sda1 /mnt</userinput>) and copy " +"the following files from the Debian archives to the stick: <itemizedlist> " +"<listitem><para> <filename>vmlinuz</filename> (kernel binary) </para></" +"listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk " +"image) </para></listitem> <listitem><para> <filename>syslinux.cfg</filename> " +"(SYSLINUX configuration file) </para></listitem> <listitem><para> Optional " +"kernel modules </para></listitem> </itemizedlist> If you want to rename the " +"files, please note that <command>SYSLINUX</command> can only process DOS " +"(8.3) file names." msgstr "" #. Tag: para #: install-methods.xml:736 #, no-c-format msgid "" -"The <filename>syslinux.cfg</filename> configuration file should contain the following two lines: <informalexample><screen>\n" +"The <filename>syslinux.cfg</filename> configuration file should contain the " +"following two lines: <informalexample><screen>\n" "default vmlinuz\n" "append initrd=initrd.gz ramdisk_size=12000 root=/dev/ram rw\n" -"</screen></informalexample> Please note that the <userinput>ramdisk_size</userinput> parameter may need to be increased, depending on the image you are booting." +"</screen></informalexample> Please note that the <userinput>ramdisk_size</" +"userinput> parameter may need to be increased, depending on the image you " +"are booting." msgstr "" #. Tag: para #: install-methods.xml:755 #, no-c-format msgid "" -"Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/sda</userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n" +"Most USB sticks do not come pre-configured in such a way that Open Firmware " +"can boot from them, so you will need to repartition the stick. On Mac " +"systems, run <userinput>mac-fdisk /dev/sda</userinput>, initialise a new " +"partition map using the <userinput>i</userinput> command, and create a new " +"partition of type Apple_Bootstrap using the <userinput>C</userinput> " +"command. (Note that the first \"partition\" will always be the partition map " +"itself.) Then type <informalexample><screen>\n" "$ hformat /dev/<replaceable>sda2</replaceable>\n" -"</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>hformat</command> command is contained in the <classname>hfsutils</classname> Debian package." +"</screen></informalexample> Take care that you use the correct device name " +"for your USB stick. The <command>hformat</command> command is contained in " +"the <classname>hfsutils</classname> Debian package." msgstr "" #. Tag: para #: install-methods.xml:771 #, no-c-format -msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader." +msgid "" +"In order to start the kernel after booting from the USB stick, we will put a " +"boot loader on the stick. The <command>yaboot</command> boot loader can be " +"installed on an HFS filesystem and can be reconfigured by just editing a " +"text file. Any operating system which supports the HFS file system can be " +"used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para #: install-methods.xml:780 #, no-c-format msgid "" -"The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n" +"The normal <command>ybin</command> tool that comes with <command>yaboot</" +"command> does not yet understand USB storage devices, so you will have to " +"install <command>yaboot</command> by hand using the <classname>hfsutils</" +"classname> tools. Type <informalexample><screen>\n" "$ hmount /dev/sda2\n" "$ hcopy -r /usr/lib/yaboot/yaboot :\n" "$ hattrib -c UNIX -t tbxi :yaboot\n" "$ hattrib -b :\n" "$ humount\n" -"</screen></informalexample> Again, take care that you use the correct device name. The partition must not be otherwise mounted during this procedure. This procedure writes the boot loader to the partition, and uses the HFS utilities to mark it in such a way that Open Firmware will boot it. Having done this, the rest of the USB stick may be prepared using the normal Unix utilities." +"</screen></informalexample> Again, take care that you use the correct device " +"name. The partition must not be otherwise mounted during this procedure. " +"This procedure writes the boot loader to the partition, and uses the HFS " +"utilities to mark it in such a way that Open Firmware will boot it. Having " +"done this, the rest of the USB stick may be prepared using the normal Unix " +"utilities." msgstr "" #. Tag: para #: install-methods.xml:796 #, no-c-format -msgid "Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and copy the following files from the Debian archives to the stick:" +msgid "" +"Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and copy " +"the following files from the Debian archives to the stick:" msgstr "" #. Tag: para @@ -595,7 +912,8 @@ msgstr "" #: install-methods.xml:829 #, no-c-format msgid "" -"The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n" +"The <filename>yaboot.conf</filename> configuration file should contain the " +"following lines: <informalexample><screen>\n" "default=install\n" "root=/dev/ram\n" "\n" @@ -606,7 +924,9 @@ msgid "" " initrd=/initrd.gz\n" " initrd-size=10000\n" " read-only\n" -"</screen></informalexample> Please note that the <userinput>initrd-size</userinput> parameter may need to be increased, depending on the image you are booting." +"</screen></informalexample> Please note that the <userinput>initrd-size</" +"userinput> parameter may need to be increased, depending on the image you " +"are booting." msgstr "" #. Tag: title @@ -618,19 +938,31 @@ msgstr "" #. Tag: para #: install-methods.xml:846 #, no-c-format -msgid "The installer will look for a Debian ISO image on the stick as its source for additional data needed for the installation. So your next step is to copy a Debian ISO image (businesscard, netinst or even a full CD image) onto your stick (be sure to select one that fits). The file name of the image must end in <filename>.iso</filename>." +msgid "" +"The installer will look for a Debian ISO image on the stick as its source " +"for additional data needed for the installation. So your next step is to " +"copy a Debian ISO image (businesscard, netinst or even a full CD image) onto " +"your stick (be sure to select one that fits). The file name of the image " +"must end in <filename>.iso</filename>." msgstr "" #. Tag: para #: install-methods.xml:854 #, no-c-format -msgid "If you want to install over the network, without using an ISO image, you will of course skip the previous step. Moreover you will have to use the initial ramdisk from the <filename>netboot</filename> directory instead of the one from <filename>hd-media</filename>, because <filename>hd-media/initrd.gz</filename> does not have network support." +msgid "" +"If you want to install over the network, without using an ISO image, you " +"will of course skip the previous step. Moreover you will have to use the " +"initial ramdisk from the <filename>netboot</filename> directory instead of " +"the one from <filename>hd-media</filename>, because <filename>hd-media/" +"initrd.gz</filename> does not have network support." msgstr "" #. Tag: para #: install-methods.xml:863 #, no-c-format -msgid "When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>) and activate its write protection switch." +msgid "" +"When you are done, unmount the USB memory stick (<userinput>umount /mnt</" +"userinput>) and activate its write protection switch." msgstr "" #. Tag: title @@ -642,7 +974,10 @@ msgstr "" #. Tag: para #: install-methods.xml:874 #, no-c-format -msgid "If your system refuses to boot from the memory stick, the stick may contain an invalid master boot record (MBR). To fix this, use the <command>install-mbr</command> command from the package <classname>mbr</classname>:" +msgid "" +"If your system refuses to boot from the memory stick, the stick may contain " +"an invalid master boot record (MBR). To fix this, use the <command>install-" +"mbr</command> command from the package <classname>mbr</classname>:" msgstr "" #. Tag: screen @@ -660,13 +995,20 @@ msgstr "" #. Tag: para #: install-methods.xml:893 #, no-c-format -msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS." +msgid "" +"The installer may be booted using boot files placed on an existing hard " +"drive partition, either launched from another operating system or by " +"invoking a boot loader directly from the BIOS." msgstr "" #. Tag: para #: install-methods.xml:899 #, no-c-format -msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks." +msgid "" +"A full, <quote>pure network</quote> installation can be achieved using this " +"technique. This avoids all hassles of removable media, like finding and " +"burning CD images or struggling with too numerous and unreliable floppy " +"disks." msgstr "" #. Tag: para @@ -678,37 +1020,57 @@ msgstr "" #. Tag: para #: install-methods.xml:910 #, no-c-format -msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download." +msgid "" +"The installer cannot boot from files on an HFS+ file system. MacOS System " +"8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To " +"determine whether your existing file system is HFS+, select <userinput>Get " +"Info</userinput> for the volume in question. HFS file systems appear as " +"<userinput>Mac OS Standard</userinput>, while HFS+ file systems say " +"<userinput>Mac OS Extended</userinput>. You must have an HFS partition in " +"order to exchange files between MacOS and Linux, in particular the " +"installation files you download." msgstr "" #. Tag: para #: install-methods.xml:921 #, no-c-format -msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model." +msgid "" +"Different programs are used for hard disk installation system booting, " +"depending on whether the system is a <quote>NewWorld</quote> or an " +"<quote>OldWorld</quote> model." msgstr "" #. Tag: title #: install-methods.xml:930 #, no-c-format -msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>" +msgid "" +"Hard disk installer booting using <command>LILO</command> or <command>GRUB</" +"command>" msgstr "" #. Tag: para #: install-methods.xml:932 #, no-c-format -msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>." +msgid "" +"This section explains how to add to or even replace an existing linux " +"installation using either <command>LILO</command> or <command>GRUB</command>." msgstr "" #. Tag: para #: install-methods.xml:938 #, no-c-format -msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel." +msgid "" +"At boot time, both bootloaders support loading in memory not only the " +"kernel, but also a disk image. This RAM disk can be used as the root file-" +"system by the kernel." msgstr "" #. Tag: para #: install-methods.xml:944 #, no-c-format -msgid "Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>." +msgid "" +"Copy the following files from the Debian archives to a convenient location " +"on your hard drive, for instance to <filename>/boot/newinstall/</filename>." msgstr "" #. Tag: para @@ -726,7 +1088,9 @@ msgstr "" #. Tag: para #: install-methods.xml:963 #, no-c-format -msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>." +msgid "" +"Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd" +"\"/>." msgstr "" #. Tag: title @@ -738,13 +1102,33 @@ msgstr "" #. Tag: para #: install-methods.xml:974 #, no-c-format -msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your Debian installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model." +msgid "" +"The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</" +"application> to launch Linux installation, but <application>miBoot</" +"application> cannot easily be used for hard disk booting. " +"<application>BootX</application>, launched from MacOS, supports booting from " +"files placed on the hard disk. <application>BootX</application> can also be " +"used to dual-boot MacOS and Linux after your Debian installation is " +"complete. For the Performa 6360, it appears that <command>quik</command> " +"cannot make the hard disk bootable. So <application>BootX</application> is " +"required on that model." msgstr "" #. Tag: para #: install-methods.xml:987 #, no-c-format -msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on Debian http/ftp mirrors and official Debian CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder." +msgid "" +"Download and unstuff the <application>BootX</application> distribution, " +"available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the " +"<filename>dists/woody/main/disks-powerpc/current/powermac</filename> " +"directory on Debian http/ftp mirrors and official Debian CDs. Use " +"<application>Stuffit Expander</application> to extract it from its archive. " +"Within the package, there is an empty folder called <filename>Linux Kernels</" +"filename>. Download <filename>linux.bin</filename> and <filename>ramdisk." +"image.gz</filename> from the <filename>disks-powerpc/current/powermac</" +"filename> folder, and place them in the <filename>Linux Kernels</filename> " +"folder. Then place the <filename>Linux Kernels</filename> folder in the " +"active System Folder." msgstr "" #. Tag: title @@ -756,13 +1140,24 @@ msgstr "" #. Tag: para #: install-methods.xml:1008 #, no-c-format -msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs." +msgid "" +"NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as " +"well as loading ELF binaries directly from the hard disk. These machines " +"will boot Linux directly via <command>yaboot</command>, which supports " +"loading a kernel and RAMdisk directly from an ext2 partition, as well as " +"dual-booting with MacOS. Hard disk booting of the installer is particularly " +"appropriate for newer machines without floppy drives. <command>BootX</" +"command> is not supported and must not be used on NewWorld PowerMacs." msgstr "" #. Tag: para #: install-methods.xml:1019 #, no-c-format -msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the Debian archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)." +msgid "" +"<emphasis>Copy</emphasis> (not move) the following four files which you " +"downloaded earlier from the Debian archives, onto the root level of your " +"hard drive (this can be accomplished by <keycap>option</keycap>-dragging " +"each file to the hard drive icon)." msgstr "" #. Tag: filename @@ -792,7 +1187,12 @@ msgstr "" #. Tag: para #: install-methods.xml:1049 #, no-c-format -msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer." +msgid "" +"Make a note of the partition number of the MacOS partition where you place " +"these files. If you have the MacOS <command>pdisk</command> program, you can " +"use the <command>L</command> command to check for the partition number. You " +"will need this partition number for the command you type at the Open " +"Firmware prompt when you boot the installer." msgstr "" #. Tag: para @@ -810,49 +1210,89 @@ msgstr "" #. Tag: para #: install-methods.xml:1071 #, no-c-format -msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine." +msgid "" +"If your machine is connected to a local area network, you may be able to " +"boot it over the network from another machine, using TFTP. If you intend to " +"boot the installation system from another machine, the boot files will need " +"to be placed in specific locations on that machine, and the machine " +"configured to support booting of your specific machine." msgstr "" #. Tag: para #: install-methods.xml:1079 #, no-c-format -msgid "You need to setup a TFTP server, and for many machines, a BOOTP server <phrase condition=\"supports-rarp\">, or RARP server</phrase> <phrase condition=\"supports-dhcp\">, or DHCP server</phrase>." +msgid "" +"You need to setup a TFTP server, and for many machines, a BOOTP server " +"<phrase condition=\"supports-rarp\">, or RARP server</phrase> <phrase " +"condition=\"supports-dhcp\">, or DHCP server</phrase>." msgstr "" #. Tag: para #: install-methods.xml:1085 #, no-c-format -msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol. </phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image. </phrase> <phrase arch=\"m68k\"> Yet another alternative exists on VMEbus systems: the IP address can be manually configured in boot ROM. </phrase> <phrase condition=\"supports-dhcp\">The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP. </phrase>" +msgid "" +"<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol " +"(RARP) is one way to tell your client what IP address to use for itself. " +"Another way is to use the BOOTP protocol. </phrase> <phrase condition=" +"\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP " +"address and where on the network to obtain a boot image. </phrase> <phrase " +"arch=\"m68k\"> Yet another alternative exists on VMEbus systems: the IP " +"address can be manually configured in boot ROM. </phrase> <phrase condition=" +"\"supports-dhcp\">The DHCP (Dynamic Host Configuration Protocol) is a more " +"flexible, backwards-compatible extension of BOOTP. Some systems can only be " +"configured via DHCP. </phrase>" msgstr "" #. Tag: para #: install-methods.xml:1102 #, no-c-format -msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP." +msgid "" +"For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good " +"idea to use DHCP instead of BOOTP. Some of the latest machines are unable to " +"boot using BOOTP." msgstr "" #. Tag: para #: install-methods.xml:1108 #, no-c-format -msgid "Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM console will <emphasis>not</emphasis> use RARP to obtain its IP address, and therefore you must use BOOTP for net booting your Alpha<footnote> <para> Alpha systems can also be net-booted using the DECNet MOP (Maintenance Operations Protocol), but this is not covered here. Presumably, your local OpenVMS operator will be happy to assist you should you have some burning need to use MOP to boot Linux on your Alpha. </para> </footnote>. You can also enter the IP configuration for network interfaces directly in the SRM console." +msgid "" +"Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM " +"console will <emphasis>not</emphasis> use RARP to obtain its IP address, and " +"therefore you must use BOOTP for net booting your Alpha<footnote> <para> " +"Alpha systems can also be net-booted using the DECNet MOP (Maintenance " +"Operations Protocol), but this is not covered here. Presumably, your local " +"OpenVMS operator will be happy to assist you should you have some burning " +"need to use MOP to boot Linux on your Alpha. </para> </footnote>. You can " +"also enter the IP configuration for network interfaces directly in the SRM " +"console." msgstr "" #. Tag: para #: install-methods.xml:1125 #, no-c-format -msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in Debian." +msgid "" +"Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There " +"is an <classname>rbootd</classname> package available in Debian." msgstr "" #. Tag: para #: install-methods.xml:1130 #, no-c-format -msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux." +msgid "" +"The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to " +"the client. Theoretically, any server, on any platform, which implements " +"these protocols, may be used. In the examples in this section, we shall " +"provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux." msgstr "" #. Tag: para #: install-methods.xml:1138 #, no-c-format -msgid "To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> support. On a &debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</classname> packages qualify; we recommend <classname>tftpd-hpa</classname>." +msgid "" +"To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you " +"will need a TFTP server with <userinput>tsize</userinput> support. On a " +"&debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</" +"classname> packages qualify; we recommend <classname>tftpd-hpa</classname>." msgstr "" #. Tag: title @@ -864,13 +1304,29 @@ msgstr "" #. Tag: para #: install-methods.xml:1157 #, no-c-format -msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>." +msgid "" +"To set up RARP, you need to know the Ethernet address (a.k.a. the MAC " +"address) of the client computers to be installed. If you don't know this " +"information, you can <phrase arch=\"sparc\"> pick it off the initial " +"OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> " +"command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the " +"rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</" +"userinput>." msgstr "" #. Tag: para #: install-methods.xml:1169 #, no-c-format -msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)." +msgid "" +"On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, " +"you use the <command>rarpd</command> program. You need to ensure that the " +"Ethernet hardware address for the client is listed in the <quote>ethers</" +"quote> database (either in the <filename>/etc/ethers</filename> file, or via " +"NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start " +"the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</" +"userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/" +"sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/" +"etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)." msgstr "" #. Tag: title @@ -882,16 +1338,33 @@ msgstr "" #. Tag: para #: install-methods.xml:1192 #, no-c-format -msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian; these are contained in the <classname>bootp</classname> and <classname>dhcp</classname> packages respectively." +msgid "" +"There are two BOOTP servers available for GNU/Linux. The first is CMU " +"<command>bootpd</command>. The other is actually a DHCP server: ISC " +"<command>dhcpd</command>. In &debian; these are contained in the " +"<classname>bootp</classname> and <classname>dhcp</classname> packages " +"respectively." msgstr "" #. Tag: para #: install-methods.xml:1200 #, no-c-format msgid "" -"To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run Debian, the line in question should look like: <informalexample><screen>\n" +"To use CMU <command>bootpd</command>, you must first uncomment (or add) the " +"relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can " +"run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/" +"etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server " +"does not run Debian, the line in question should look like: " +"<informalexample><screen>\n" "bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120\n" -"</screen></informalexample> Now, you must create an <filename>/etc/bootptab</filename> file. This has the same sort of familiar and cryptic format as the good old BSD <filename>printcap</filename>, <filename>termcap</filename>, and <filename>disktab</filename> files. See the <filename>bootptab</filename> manual page for more information. For CMU <command>bootpd</command>, you will need to know the hardware (MAC) address of the client. Here is an example <filename>/etc/bootptab</filename>: <informalexample><screen>\n" +"</screen></informalexample> Now, you must create an <filename>/etc/bootptab</" +"filename> file. This has the same sort of familiar and cryptic format as the " +"good old BSD <filename>printcap</filename>, <filename>termcap</filename>, " +"and <filename>disktab</filename> files. See the <filename>bootptab</" +"filename> manual page for more information. For CMU <command>bootpd</" +"command>, you will need to know the hardware (MAC) address of the client. " +"Here is an example <filename>/etc/bootptab</filename>: " +"<informalexample><screen>\n" "client:\\\n" " hd=/tftpboot:\\\n" " bf=tftpboot.img:\\\n" @@ -899,13 +1372,27 @@ msgid "" " sm=255.255.255.0:\\\n" " sa=192.168.1.1:\\\n" " ha=0123456789AB:\n" -"</screen></informalexample> You will need to change at least the <quote>ha</quote> option, which specifies the hardware address of the client. The <quote>bf</quote> option specifies the file a client should retrieve via TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI machines you can just enter the command monitor and type <userinput>printenv</userinput>. The value of the <userinput>eaddr</userinput> variable is the machine's MAC address. </phrase>" +"</screen></informalexample> You will need to change at least the <quote>ha</" +"quote> option, which specifies the hardware address of the client. The " +"<quote>bf</quote> option specifies the file a client should retrieve via " +"TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=" +"\"mips\"> On SGI machines you can just enter the command monitor and type " +"<userinput>printenv</userinput>. The value of the <userinput>eaddr</" +"userinput> variable is the machine's MAC address. </phrase>" msgstr "" #. Tag: para #: install-methods.xml:1233 #, no-c-format -msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise, you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd restart</userinput>." +msgid "" +"By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really " +"easy, because it treats BOOTP clients as a moderately special case of DHCP " +"clients. Some architectures require a complex configuration for booting " +"clients via BOOTP. If yours is one of those, read the section <xref linkend=" +"\"dhcpd\"/>. Otherwise, you will probably be able to get away with simply " +"adding the <userinput>allow bootp</userinput> directive to the configuration " +"block for the subnet containing the client, and restart <command>dhcpd</" +"command> with <userinput>/etc/init.d/dhcpd restart</userinput>." msgstr "" #. Tag: title @@ -918,7 +1405,10 @@ msgstr "" #: install-methods.xml:1255 #, no-c-format msgid "" -"One free software DHCP server is ISC <command>dhcpd</command>. In &debian;, this is available in the <classname>dhcp</classname> package. Here is a sample configuration file for it (usually <filename>/etc/dhcpd.conf</filename>): <informalexample><screen>\n" +"One free software DHCP server is ISC <command>dhcpd</command>. In &debian;, " +"this is available in the <classname>dhcp</classname> package. Here is a " +"sample configuration file for it (usually <filename>/etc/dhcpd.conf</" +"filename>): <informalexample><screen>\n" "option domain-name \"example.com\";\n" "option domain-name-servers ns1.example.com;\n" "option subnet-mask 255.255.255.0;\n" @@ -938,19 +1428,28 @@ msgid "" " hardware ethernet 01:23:45:67:89:AB;\n" " fixed-address 192.168.1.90;\n" "}\n" -"</screen></informalexample> Note: the new (and preferred) <classname>dhcp3</classname> package uses <filename>/etc/dhcp3/dhcpd.conf</filename>." +"</screen></informalexample> Note: the new (and preferred) <classname>dhcp3</" +"classname> package uses <filename>/etc/dhcp3/dhcpd.conf</filename>." msgstr "" #. Tag: para #: install-methods.xml:1267 #, no-c-format -msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP." +msgid "" +"In this example, there is one server <replaceable>servername</replaceable> " +"which performs all of the work of DHCP server, TFTP server, and network " +"gateway. You will almost certainly need to change the domain-name options, " +"as well as the server name and client hardware address. The " +"<replaceable>filename</replaceable> option should be the name of the file " +"which will be retrieved via TFTP." msgstr "" #. Tag: para #: install-methods.xml:1277 #, no-c-format -msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd restart</userinput>." +msgid "" +"After you have edited the <command>dhcpd</command> configuration file, " +"restart it with <userinput>/etc/init.d/dhcpd restart</userinput>." msgstr "" #. Tag: title @@ -963,7 +1462,8 @@ msgstr "" #: install-methods.xml:1286 #, no-c-format msgid "" -"Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n" +"Here is another example for a <filename>dhcp.conf</filename> using the Pre-" +"boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n" "option domain-name \"example.com\";\n" "\n" "default-lease-time 600;\n" @@ -991,7 +1491,9 @@ msgid "" " filename \"/tftpboot/pxelinux.0\";\n" " }\n" "}\n" -"</screen></informalexample> Note that for PXE booting, the client filename <filename>pxelinux.0</filename> is a boot loader, not a kernel image (see <xref linkend=\"tftp-images\"/> below)." +"</screen></informalexample> Note that for PXE booting, the client filename " +"<filename>pxelinux.0</filename> is a boot loader, not a kernel image (see " +"<xref linkend=\"tftp-images\"/> below)." msgstr "" #. Tag: title @@ -1004,26 +1506,47 @@ msgstr "" #: install-methods.xml:1303 #, no-c-format msgid "" -"To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled. This is usually enabled by having something like the following line in <filename>/etc/inetd.conf</filename>: <informalexample><screen>\n" +"To get the TFTP server ready to go, you should first make sure that " +"<command>tftpd</command> is enabled. This is usually enabled by having " +"something like the following line in <filename>/etc/inetd.conf</filename>: " +"<informalexample><screen>\n" "tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd /tftpboot\n" -"</screen></informalexample> Debian packages will in general set this up correctly by default when they are installed." +"</screen></informalexample> Debian packages will in general set this up " +"correctly by default when they are installed." msgstr "" #. Tag: para #: install-methods.xml:1314 #, no-c-format -msgid "Look in that file and remember the directory which is used as the argument of <command>in.tftpd</command>; you'll need that below. The <userinput>-l</userinput> argument enables some versions of <command>in.tftpd</command> to log all requests to the system logs; this is useful for diagnosing boot errors. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>." +msgid "" +"Look in that file and remember the directory which is used as the argument " +"of <command>in.tftpd</command>; you'll need that below. The <userinput>-l</" +"userinput> argument enables some versions of <command>in.tftpd</command> to " +"log all requests to the system logs; this is useful for diagnosing boot " +"errors. If you've had to change <filename>/etc/inetd.conf</filename>, you'll " +"have to notify the running <command>inetd</command> process that the file " +"has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</" +"userinput>; on other machines, find out the process ID for <command>inetd</" +"command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></" +"userinput>." msgstr "" #. Tag: para #: install-methods.xml:1328 #, no-c-format msgid "" -"If you intend to install Debian on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n" +"If you intend to install Debian on an SGI machine and your TFTP server is a " +"GNU/Linux box running Linux 2.4, you'll need to set the following on your " +"server: <informalexample><screen>\n" "# echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc\n" -"</screen></informalexample> to turn off Path MTU discovery, otherwise the SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets are sent from a source port no greater than 32767, or the download will stall after the first packet. Again, it's Linux 2.4.X tripping this bug in the PROM, and you can avoid it by setting <informalexample><screen>\n" +"</screen></informalexample> to turn off Path MTU discovery, otherwise the " +"SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets " +"are sent from a source port no greater than 32767, or the download will " +"stall after the first packet. Again, it's Linux 2.4.X tripping this bug in " +"the PROM, and you can avoid it by setting <informalexample><screen>\n" "# echo \"2048 32767\" > /proc/sys/net/ipv4/ip_local_port_range\n" -"</screen></informalexample> to adjust the range of source ports the Linux TFTP server uses." +"</screen></informalexample> to adjust the range of source ports the Linux " +"TFTP server uses." msgstr "" #. Tag: title @@ -1035,25 +1558,47 @@ msgstr "" #. Tag: para #: install-methods.xml:1351 #, no-c-format -msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. Generally, this directory will be <filename>/tftpboot</filename>. You'll have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards." +msgid "" +"Next, place the TFTP boot image you need, as found in <xref linkend=\"where-" +"files\"/>, in the <command>tftpd</command> boot image directory. Generally, " +"this directory will be <filename>/tftpboot</filename>. You'll have to make a " +"link from that file to the file which <command>tftpd</command> will use for " +"booting a particular client. Unfortunately, the file name is determined by " +"the TFTP client, and there are no strong standards." msgstr "" #. Tag: para #: install-methods.xml:1361 #, no-c-format -msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP directory." +msgid "" +"On NewWorld Power Macintosh machines, you will need to set up the " +"<command>yaboot</command> boot loader as the TFTP boot image. " +"<command>Yaboot</command> will then retrieve the kernel and RAMdisk images " +"via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</" +"filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP " +"directory." msgstr "" #. Tag: para #: install-methods.xml:1370 #, no-c-format -msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/pxelinux.0</filename> to <command>tftpd</command> as the filename to boot." +msgid "" +"For PXE booting, everything you should need is set up in the " +"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this " +"tarball into the <command>tftpd</command> boot image directory. Make sure " +"your dhcp server is configured to pass <filename>/pxelinux.0</filename> to " +"<command>tftpd</command> as the filename to boot." msgstr "" #. Tag: para #: install-methods.xml:1378 #, no-c-format -msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot." +msgid "" +"For PXE booting, everything you should need is set up in the " +"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this " +"tarball into the <command>tftpd</command> boot image directory. Make sure " +"your dhcp server is configured to pass <filename>/debian-installer/ia64/" +"elilo.efi</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: title @@ -1065,13 +1610,25 @@ msgstr "" #. Tag: para #: install-methods.xml:1391 #, no-c-format -msgid "For DECstations, there are tftpimage files for each subarchitecture, which contain both kernel and installer in one file. The naming convention is <filename><replaceable>subarchitecture</replaceable>/netboot-boot.img</filename>. Copy the tftpimage file you would like to use to <userinput>/tftpboot/tftpboot.img</userinput> if you work with the example BOOTP/DHCP setups described above." +msgid "" +"For DECstations, there are tftpimage files for each subarchitecture, which " +"contain both kernel and installer in one file. The naming convention is " +"<filename><replaceable>subarchitecture</replaceable>/netboot-boot.img</" +"filename>. Copy the tftpimage file you would like to use to <userinput>/" +"tftpboot/tftpboot.img</userinput> if you work with the example BOOTP/DHCP " +"setups described above." msgstr "" #. Tag: para #: install-methods.xml:1401 #, no-c-format -msgid "The DECstation firmware boots by TFTP with the command <userinput>boot <replaceable>#</replaceable>/tftp</userinput>, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot. On most DECstations this is <quote>3</quote>. If the BOOTP/DHCP server does not supply the filename or you need to pass additional parameters, they can optionally be appended with the following syntax:" +msgid "" +"The DECstation firmware boots by TFTP with the command <userinput>boot " +"<replaceable>#</replaceable>/tftp</userinput>, where <replaceable>#</" +"replaceable> is the number of the TurboChannel device from which to boot. On " +"most DECstations this is <quote>3</quote>. If the BOOTP/DHCP server does not " +"supply the filename or you need to pass additional parameters, they can " +"optionally be appended with the following syntax:" msgstr "" #. Tag: userinput @@ -1083,7 +1640,23 @@ msgstr "" #. Tag: para #: install-methods.xml:1415 #, no-c-format -msgid "Several DECstation firmware revisions show a problem with regard to net booting: the transfer starts, but after some time it stops with an <computeroutput>a.out err</computeroutput>. This can have several reasons: <orderedlist> <listitem><para> The firmware does not respond to ARP requests during a TFTP transfer. This leads to an ARP timeout and the transfer stops. The solution is to add the MAC address of the Ethernet card in the DECstation statically to the ARP table of the TFTP server. This is done by running <userinput>arp -s <replaceable>IP-address</replaceable> <replaceable>MAC-address</replaceable></userinput> as root on the machine acting as TFTP server. The MAC-address of the DECstation can be read out by entering <command>cnfg</command> at the DECstation firmware prompt. </para></listitem> <listitem><para> The firmware has a size limit on the files that can be booted by TFTP. </para></listitem> </orderedlist> There are also firmware revisions that cannot boot via TFTP at all. An overview about the different firmware revisions can be found at the NetBSD web pages: <ulink url=\"http://www.netbsd.org/Ports/pmax/board-list.html#proms\"></ulink>." +msgid "" +"Several DECstation firmware revisions show a problem with regard to net " +"booting: the transfer starts, but after some time it stops with an " +"<computeroutput>a.out err</computeroutput>. This can have several reasons: " +"<orderedlist> <listitem><para> The firmware does not respond to ARP requests " +"during a TFTP transfer. This leads to an ARP timeout and the transfer stops. " +"The solution is to add the MAC address of the Ethernet card in the " +"DECstation statically to the ARP table of the TFTP server. This is done by " +"running <userinput>arp -s <replaceable>IP-address</replaceable> " +"<replaceable>MAC-address</replaceable></userinput> as root on the machine " +"acting as TFTP server. The MAC-address of the DECstation can be read out by " +"entering <command>cnfg</command> at the DECstation firmware prompt. </para></" +"listitem> <listitem><para> The firmware has a size limit on the files that " +"can be booted by TFTP. </para></listitem> </orderedlist> There are also " +"firmware revisions that cannot boot via TFTP at all. An overview about the " +"different firmware revisions can be found at the NetBSD web pages: <ulink " +"url=\"http://www.netbsd.org/Ports/pmax/board-list.html#proms\"></ulink>." msgstr "" #. Tag: title @@ -1095,7 +1668,15 @@ msgstr "" #. Tag: para #: install-methods.xml:1454 #, no-c-format -msgid "On Alpha, you must specify the filename (as a relative path to the boot image directory) using the <userinput>-file</userinput> argument to the SRM <userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</userinput> environment variable. Alternatively, the filename can be given via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</userinput> directive). Unlike Open Firmware, there is <emphasis>no default filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a filename by either one of these methods." +msgid "" +"On Alpha, you must specify the filename (as a relative path to the boot " +"image directory) using the <userinput>-file</userinput> argument to the SRM " +"<userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</" +"userinput> environment variable. Alternatively, the filename can be given " +"via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</" +"userinput> directive). Unlike Open Firmware, there is <emphasis>no default " +"filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a " +"filename by either one of these methods." msgstr "" #. Tag: title @@ -1108,16 +1689,29 @@ msgstr "" #: install-methods.xml:1470 #, no-c-format msgid "" -"Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n" -"$ printf '%.2x%.2x%.2x%.2x\\n" -"' 10 0 0 4\n" -"</screen></informalexample> To get to the correct filename, you will need to change all letters to uppercase and if necessary append the subarchitecture name." +"Some SPARC architectures add the subarchitecture names, such as " +"<quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your " +"system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename " +"would be <filename>C0A80103.SUN4C</filename>. However, there are also " +"subarchitectures where the file the client looks for is just " +"<filename>client-ip-in-hex</filename>. An easy way to determine the " +"hexadecimal code for the IP address is to enter the following command in a " +"shell (assuming the machine's intended IP is 10.0.0.4). " +"<informalexample><screen>\n" +"$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n" +"</screen></informalexample> To get to the correct filename, you will need to " +"change all letters to uppercase and if necessary append the subarchitecture " +"name." msgstr "" #. Tag: para #: install-methods.xml:1486 #, no-c-format -msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in." +msgid "" +"You can also force some sparc systems to look for a specific file name by " +"adding it to the end of the OpenPROM boot command, such as <userinput>boot " +"net my-sparc.image</userinput>. This must still reside in the directory that " +"the TFTP server looks in." msgstr "" #. Tag: title @@ -1129,13 +1723,20 @@ msgstr "" #. Tag: para #: install-methods.xml:1498 #, no-c-format -msgid "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to <filename>/tftpboot/</filename>." +msgid "" +"For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to " +"<filename>/tftpboot/</filename>." msgstr "" #. Tag: para #: install-methods.xml:1503 #, no-c-format -msgid "Next, configure your boot ROMs or BOOTP server to initially load the <filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> files from the TFTP server. Refer to the <filename>tftplilo.txt</filename> file for your subarchitecture for additional system-specific configuration information." +msgid "" +"Next, configure your boot ROMs or BOOTP server to initially load the " +"<filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> " +"files from the TFTP server. Refer to the <filename>tftplilo.txt</filename> " +"file for your subarchitecture for additional system-specific configuration " +"information." msgstr "" #. Tag: title @@ -1147,7 +1748,11 @@ msgstr "" #. Tag: para #: install-methods.xml:1516 #, no-c-format -msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>." +msgid "" +"On SGI machines you can rely on the <command>bootpd</command> to supply the " +"name of the TFTP file. It is given either as the <userinput>bf=</userinput> " +"in <filename>/etc/bootptab</filename> or as the <userinput>filename=</" +"userinput> option in <filename>/etc/dhcpd.conf</filename>." msgstr "" #. Tag: title @@ -1159,7 +1764,9 @@ msgstr "" #. Tag: para #: install-methods.xml:1529 #, no-c-format -msgid "You don't have to configure DHCP in a special way because you'll pass the full path of the file to be loaded to CFE." +msgid "" +"You don't have to configure DHCP in a special way because you'll pass the " +"full path of the file to be loaded to CFE." msgstr "" #. Tag: title @@ -1171,7 +1778,12 @@ msgstr "" #. Tag: para #: install-methods.xml:1635 #, no-c-format -msgid "For installing on multiple computers it's possible to do fully automatic installations. Debian packages intended for this include <classname>fai</classname> (which uses an install server), <classname>replicator</classname>, <classname>systemimager</classname>, <classname>autoinstall</classname>, and the Debian Installer itself." +msgid "" +"For installing on multiple computers it's possible to do fully automatic " +"installations. Debian packages intended for this include <classname>fai</" +"classname> (which uses an install server), <classname>replicator</" +"classname>, <classname>systemimager</classname>, <classname>autoinstall</" +"classname>, and the Debian Installer itself." msgstr "" #. Tag: title @@ -1183,12 +1795,17 @@ msgstr "" #. Tag: para #: install-methods.xml:1649 #, no-c-format -msgid "The Debian Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process." +msgid "" +"The Debian Installer supports automating installs via preconfiguration " +"files. A preconfiguration file can be loaded from the network or from " +"removable media, and used to fill in answers to questions asked during the " +"installation process." msgstr "" #. Tag: para #: install-methods.xml:1656 #, no-c-format -msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>." +msgid "" +"Full documentation on preseeding including a working example that you can " +"edit is in <xref linkend=\"appendix-preseed\"/>." msgstr "" - |