diff options
| author | Frans Pop <elendil@planet.nl> | 2006-10-29 14:57:26 +0000 |
|---|---|---|
| committer | Frans Pop <elendil@planet.nl> | 2006-10-29 14:57:26 +0000 |
| commit | 2b571a80b713d0766c2649d18987ef9fd0f642b5 (patch) | |
| tree | c1cc60a93ce23882d00fe3c8c685cdd901142a43 /po/hu | |
| parent | 82610af89ed631f0bc1c2a2f35d9232026e05d9e (diff) | |
| download | installation-guide-2b571a80b713d0766c2649d18987ef9fd0f642b5.zip | |
Update of POT and PO files for the manual
Diffstat (limited to 'po/hu')
| -rw-r--r-- | po/hu/boot-installer.po | 2602 | ||||
| -rw-r--r-- | po/hu/installation-howto.po | 484 | ||||
| -rw-r--r-- | po/hu/partitioning.po | 1089 | ||||
| -rw-r--r-- | po/hu/random-bits.po | 277 |
4 files changed, 3492 insertions, 960 deletions
diff --git a/po/hu/boot-installer.po b/po/hu/boot-installer.po index e4d8bb29f..54d93754d 100644 --- a/po/hu/boot-installer.po +++ b/po/hu/boot-installer.po @@ -5,7 +5,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-10-17 08:26+0000\n" +"POT-Creation-Date: 2006-10-29 14:49+0000\n" "PO-Revision-Date: 2006-10-23 20:34+0100\n" "Last-Translator: SZERVÁC Attila <sas@321.hu>\n" "Language-Team: Hungarian\n" @@ -37,56 +37,106 @@ 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." -msgstr "Az alábbi tábla összefoglalja az elérhető és támogatott rendszer-típus/konzol párokat (lásd az <xref linkend=\"alpha-cpus\"/> oldalt a rendszer-típus nevekért). Az <quote>ARC</quote> szó bármely ARC-kompatibilis konzolt jelöli." +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 "" +"Az alábbi tábla összefoglalja az elérhető és támogatott rendszer-típus/" +"konzol párokat (lásd az <xref linkend=\"alpha-cpus\"/> oldalt a rendszer-" +"típus nevekért). Az <quote>ARC</quote> szó bármely ARC-kompatibilis konzolt " +"jelöli." #. Tag: entry #: boot-installer.xml:107 @@ -107,20 +157,11 @@ msgid "alcor" msgstr "alcor" #. 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 "ARC vagy SRM" @@ -138,15 +179,9 @@ msgid "book1" msgstr "book1" #. 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 "csak SRM" @@ -266,9 +301,7 @@ msgid "ruffian" msgstr "ruffian" #. 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 "csak ARC" @@ -312,65 +345,121 @@ msgstr "<entry>xlt</entry>" #. 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>." -msgstr "Általában e konzolok nem indítanak Linuxot, így egy köztes boot betöltő szükséges. Az SRM konzolokhoz az <command>aboot</command>, egy kis, platform-független boot-betöltő használatos. Lásd az (immár sajnos elavult) <ulink url=\"&url-srm-howto;\">SRM HOGYAN</ulink> <command>aboot</command> leírást." +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 "" +"Általában e konzolok nem indítanak Linuxot, így egy köztes boot betöltő " +"szükséges. Az SRM konzolokhoz az <command>aboot</command>, egy kis, platform-" +"független boot-betöltő használatos. Lásd az (immár sajnos elavult) <ulink " +"url=\"&url-srm-howto;\">SRM HOGYAN</ulink> <command>aboot</command> leírást." #. 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." -msgstr "Az alábbi bekezdések a woody telepítő kézikönyvből valók, melyre itt hivatkozunk; hasznosak lesznek később, mikor a Debian ismét támogatja a MILO-alapú telepítést." +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 "" +"Az alábbi bekezdések a woody telepítő kézikönyvből valók, melyre itt " +"hivatkozunk; hasznosak lesznek később, mikor a Debian ismét támogatja a MILO-" +"alapú telepítést." #. 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>." -msgstr "Általában e konzolok nem indítanak Linuxot, így egy köztes boot betöltő szükséges. 2 népszerű van: a <command>MILO</command> és az <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 "" +"Általában e konzolok nem indítanak Linuxot, így egy köztes boot betöltő " +"szükséges. 2 népszerű van: a <command>MILO</command> és az <command>aboot</" +"command>." #. 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>." -msgstr "A <command>MILO</command> maga egy konzol, mely az ARC vagy SRM helyére kerül a memóriában. A <command>MILO</command> ARC és SRM alól is indítható és ARC konzolról csak ezzel indítható a Linux. A <command>MILO</command> platform-függő (külön <command>MILO</command> kell minden rebdszer-típushoz) és csak a fenti táblában ARC-támogatást mutató rendszerekhez van. Lásd a (sajnos elavult) <ulink url=\"&url-milo-howto;\">MILO HOGYAN</ulink>-t is." +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 "" +"A <command>MILO</command> maga egy konzol, mely az ARC vagy SRM helyére " +"kerül a memóriában. A <command>MILO</command> ARC és SRM alól is indítható " +"és ARC konzolról csak ezzel indítható a Linux. A <command>MILO</command> " +"platform-függő (külön <command>MILO</command> kell minden rebdszer-típushoz) " +"és csak a fenti táblában ARC-támogatást mutató rendszerekhez van. Lásd a " +"(sajnos elavult) <ulink url=\"&url-milo-howto;\">MILO HOGYAN</ulink>-t is." #. 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>." -msgstr "Az <command>aboot</command> egy kis, platform-független boot betöltő, mely csak SRM alól fut. Lásd az (immár sajnos elavult) <ulink url=\"&url-srm-howto;\">SRM HOGYAN</ulink> <command>aboot</command> leírást." +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 "" +"Az <command>aboot</command> egy kis, platform-független boot betöltő, mely " +"csak SRM alól fut. Lásd az (immár sajnos elavult) <ulink url=\"&url-srm-" +"howto;\">SRM HOGYAN</ulink> <command>aboot</command> leírást." #. 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:997 -#: boot-installer.xml:1488 -#: boot-installer.xml:1983 -#: boot-installer.xml:2065 -#: boot-installer.xml:2154 -#: boot-installer.xml:2498 -#: boot-installer.xml:2594 +#: boot-installer.xml:283 boot-installer.xml:997 boot-installer.xml:1488 +#: boot-installer.xml:1983 boot-installer.xml:2065 boot-installer.xml:2154 +#: boot-installer.xml:2498 boot-installer.xml:2594 #, no-c-format msgid "Booting with TFTP" msgstr "Indítás TFTP segítségével" @@ -379,51 +468,85 @@ msgstr "Indítás TFTP segítségével" #: 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 "" -"SRM esetén az Ethernet csatolók <userinput>ewa</userinput> előtagot kapnak és a <userinput>show dev</userinput> parancs kiírja őket így (kissé szerkesztve):<informalexample><screen>\n" +"SRM esetén az Ethernet csatolók <userinput>ewa</userinput> előtagot kapnak " +"és a <userinput>show dev</userinput> parancs kiírja őket így (kissé " +"szerkesztve):<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> Először be kell állítani az indító protokollt: <informalexample><screen>\n" +"</screen></informalexample> Először be kell állítani az indító protokollt: " +"<informalexample><screen>\n" ">>> set ewa0_protocols bootp\n" -"</screen></informalexample> Majd ellenőrizni a médium típust:<informalexample><screen>\n" +"</screen></informalexample> Majd ellenőrizni a médium típust:" +"<informalexample><screen>\n" ">>> set ewa0_mode <replaceable>mód</replaceable>\n" -"</screen></informalexample> Az érvényes módok így írhatók ki: <userinput>>>>set ewa0_mode</userinput>." +"</screen></informalexample> Az érvényes módok így írhatók ki: <userinput>>" +">>set ewa0_mode</userinput>." #. 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 "" -"Majd az 1. Ethernet csatolóról való indításhoz ezt kell beírni: <informalexample><screen>\n" +"Majd az 1. Ethernet csatolóról való indításhoz ezt kell beírni: " +"<informalexample><screen>\n" ">>> boot ewa0 -flags \"\"\n" -"</screen></informalexample> Ez netboot képben lévő alap kernel paraméterekkel indít." +"</screen></informalexample> Ez netboot képben lévő alap kernel " +"paraméterekkel indít." #. 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:" -msgstr "Soros konzol esetén át <emphasis>kell</emphasis> adni a <userinput>console=</userinput> paramétert a kernelnek. Ez az SRM <userinput>boot</userinput> parancsnak adott <userinput>-flags</userinput> argumentummal tehető. A soros portok a <userinput>/dev</userinput> könyvtárban lévő megfelelő fájlokkal nevezhetők. További kernel paraméterek megadásakor meg kell ismételni egyes alapértelmezett opciókat, melyek kellenek a &d-i; képekhez. Például az <userinput>ewa0</userinput> eszközről indításhoz az 1. soros port használatakor ezt kell beírni:" +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 "" +"Soros konzol esetén át <emphasis>kell</emphasis> adni a <userinput>console=</" +"userinput> paramétert a kernelnek. Ez az SRM <userinput>boot</userinput> " +"parancsnak adott <userinput>-flags</userinput> argumentummal tehető. A soros " +"portok a <userinput>/dev</userinput> könyvtárban lévő megfelelő fájlokkal " +"nevezhetők. További kernel paraméterek megadásakor meg kell ismételni egyes " +"alapértelmezett opciókat, melyek kellenek a &d-i; képekhez. Például az " +"<userinput>ewa0</userinput> eszközről indításhoz az 1. soros port " +"használatakor ezt kell beírni:" #. Tag: screen #: boot-installer.xml:323 #, no-c-format -msgid ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0"" -msgstr ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0"" +msgid "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" +msgstr "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" #. Tag: title #: boot-installer.xml:328 @@ -437,11 +560,13 @@ msgstr "Indítás CD-ROM lemezről az SRM konzollal" 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 "" "Írd be ezt: <informalexample><screen>\n" ">>> boot xxxx -flags 0\n" -"</screen></informalexample> ahol az <replaceable>xxxx</replaceable> a CD-ROM meghajtó SRM szerint." +"</screen></informalexample> ahol az <replaceable>xxxx</replaceable> a CD-ROM " +"meghajtó SRM szerint." #. Tag: title #: boot-installer.xml:341 @@ -452,8 +577,22 @@ msgstr "Indítás CD-ROM lemezről az ARC vagy AlphaBIOS konzollal" #. 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." -msgstr "Egy CD-ROM indításakor az ARC konzolról, keresd meg az al-architektúra kód nevet (lásd az <xref linkend=\"alpha-cpus\"/> leírást), majd add meg a <filename>\\milo\\linload.exe</filename> fájlt mint boot betöltő és a <filename>\\milo\\<replaceable>subarch</replaceable></filename> fájlt (ahol a <replaceable>subarch</replaceable> a helyes al-architektúra név) mint OS útvonal az `OS Selection Setup' menüben. A Ruffian kivétel: a <filename>\\milo\\ldmilo.exe</filename> fájl kell mint boot betöltő." +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 "" +"Egy CD-ROM indításakor az ARC konzolról, keresd meg az al-architektúra kód " +"nevet (lásd az <xref linkend=\"alpha-cpus\"/> leírást), majd add meg a " +"<filename>\\milo\\linload.exe</filename> fájlt mint boot betöltő és a " +"<filename>\\milo\\<replaceable>subarch</replaceable></filename> fájlt (ahol " +"a <replaceable>subarch</replaceable> a helyes al-architektúra név) mint OS " +"útvonal az `OS Selection Setup' menüben. A Ruffian kivétel: a <filename>" +"\\milo\\ldmilo.exe</filename> fájl kell mint boot betöltő." #. Tag: title #: boot-installer.xml:358 @@ -465,35 +604,64 @@ msgstr "Indítás flopiról az SRM konzollal" #: 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." -msgstr "" -"Az SRM jelnél (<prompt>>>></prompt>) add ki az alábbi parancsot: <informalexample><screen>\n" +"</screen></informalexample> to see the list of devices (e.g., if you want to " +"boot from a CD). Note that if you are booting via MILO, <command>-flags</" +"command> argument is ignored, so you can just type <command>boot dva0</" +"command>. If everything works OK, you will eventually see the Linux kernel " +"boot." +msgstr "" +"Az SRM jelnél (<prompt>>>></prompt>) add ki az alábbi parancsot: " +"<informalexample><screen>\n" ">>> boot dva0 -flags 0\n" -"</screen></informalexample> ha kell cserélve a <filename>dva0</filename>-t az aktuális eszköz nevével. Általában a <filename>dva0</filename> a flopi; a <informalexample><screen>\n" +"</screen></informalexample> ha kell cserélve a <filename>dva0</filename>-t " +"az aktuális eszköz nevével. Általában a <filename>dva0</filename> a flopi; a " +"<informalexample><screen>\n" ">>> show dev\n" -"</screen></informalexample> sorolja fel az eszközöket (például ha CD-lemezről akarsz indítani). A MILO általi indításkor a <command>-flags</command> argumentum nem számít, csak a <command>boot dva0</command> parancs kell. Ha minden jól működik, a Linux kernel azonnal elindul." +"</screen></informalexample> sorolja fel az eszközöket (például ha CD-" +"lemezről akarsz indítani). A MILO általi indításkor a <command>-flags</" +"command> argumentum nem számít, csak a <command>boot dva0</command> parancs " +"kell. Ha minden jól működik, a Linux kernel azonnal elindul." #. 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>." -msgstr "" -"Ha kernel paramétereket akarsz megadni az <command>aboot</command> indításkor, használd az alábbi parancsot:<informalexample><screen>\n" -">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 load_ramdisk=1 arguments\"\n" -"</screen></informalexample> (egy sorban), cseréld, ha kell, a <filename>dva0</filename> aktuális SRM indító eszköz nevet, az <filename>fd0</filename> Linux indító eszköz nevet és az <filename>arguments</filename> kívánt kernel paramétereket." +"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 "" +"Ha kernel paramétereket akarsz megadni az <command>aboot</command> " +"indításkor, használd az alábbi parancsot:<informalexample><screen>\n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +"</screen></informalexample> (egy sorban), cseréld, ha kell, a " +"<filename>dva0</filename> aktuális SRM indító eszköz nevet, az " +"<filename>fd0</filename> Linux indító eszköz nevet és az " +"<filename>arguments</filename> kívánt kernel paramétereket." #. 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\"/>." -msgstr "Ha kernel paramétereket akarsz megadni az <command>MILO</command> indításkor, a MILO betöltőbe lépve egyszer meg kell szakítanod az indítást. Lásd a <xref linkend=\"booting-from-milo\"/> leírást." +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 "" +"Ha kernel paramétereket akarsz megadni az <command>MILO</command> " +"indításkor, a MILO betöltőbe lépve egyszer meg kell szakítanod az indítást. " +"Lásd a <xref linkend=\"booting-from-milo\"/> leírást." #. Tag: title #: boot-installer.xml:398 @@ -504,8 +672,14 @@ msgstr "Indítás flopiról az ARC vagy AlphaBIOS konzollal" #. 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." -msgstr "Az OS Választás menüben állítsd be a <command>linload.exe</command> fájlt boot betöltőként és a <command>milo</command>-t OS útvonalként. Indíts az újonnan létrehozott beállításokkal." +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 "" +"Az OS Választás menüben állítsd be a <command>linload.exe</command> fájlt " +"boot betöltőként és a <command>milo</command>-t OS útvonalként. Indíts az " +"újonnan létrehozott beállításokkal." #. Tag: title #: boot-installer.xml:409 @@ -516,20 +690,33 @@ msgstr "Indítás MILO segítségével" #. 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." -msgstr "AZ indító médián lévő MILO eleve Linux indításra állított. Ha mégis beavatkoznál csak a szóközt kell leütnöd a MILO visszaszámlálás alatt." +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 "" +"AZ indító médián lévő MILO eleve Linux indításra állított. Ha mégis " +"beavatkoznál csak a szóközt kell leütnöd a MILO visszaszámlálás alatt." #. 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 "" -"Ha mindent magad akarsz megadni (például további paramétereket) hasonló parancs használható:<informalexample><screen>\n" +"Ha mindent magad akarsz megadni (például további paramétereket) hasonló " +"parancs használható:<informalexample><screen>\n" "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->\n" -"</screen></informalexample> Ha flopi helyett mást indítsz, cseréld a fenti példa <filename>fd0</filename> nevet a megfelelő eszköz nevére Linux szerint. A <command>help</command> parancs röviden leírja a MILO parancsait." +"</screen></informalexample> Ha flopi helyett mást indítsz, cseréld a fenti " +"példa <filename>fd0</filename> nevet a megfelelő eszköz nevére Linux " +"szerint. A <command>help</command> parancs röviden leírja a MILO parancsait." #. Tag: title #: boot-installer.xml:435 @@ -538,37 +725,37 @@ msgid "Booting from TFTP" msgstr "Indítás TFTP segítségével" #. Tag: para -#: boot-installer.xml:441 -#: boot-installer.xml:1003 -#: boot-installer.xml:1506 -#: boot-installer.xml:1989 -#: boot-installer.xml:2504 -#: boot-installer.xml:2600 +#: boot-installer.xml:441 boot-installer.xml:1003 boot-installer.xml:1506 +#: boot-installer.xml:1989 boot-installer.xml:2504 boot-installer.xml:2600 #, 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)." -msgstr "A hálózati indítás egy hálózati kapcsolatot és egy TFTP hálózati indító kiszolgálót igényel (DHCP, RARP vagy BOOTP)." +msgid "" +"Booting from the network requires that you have a network connection and a " +"TFTP network boot server (DHCP, RARP, or BOOTP)." +msgstr "" +"A hálózati indítás egy hálózati kapcsolatot és egy TFTP hálózati indító " +"kiszolgálót igényel (DHCP, RARP vagy BOOTP)." #. Tag: para -#: boot-installer.xml:446 -#: boot-installer.xml:1008 -#: boot-installer.xml:1511 -#: boot-installer.xml:1994 -#: boot-installer.xml:2509 -#: boot-installer.xml:2605 +#: boot-installer.xml:446 boot-installer.xml:1008 boot-installer.xml:1511 +#: boot-installer.xml:1994 boot-installer.xml:2509 boot-installer.xml:2605 #, no-c-format -msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server." -msgstr "A régebbi rendszerek, például a 715 egy RBOOT kiszolgálót kérhetnek BOOTP helyett." +msgid "" +"Older systems such as the 715 might require the use of an RBOOT server " +"instead of a BOOTP server." +msgstr "" +"A régebbi rendszerek, például a 715 egy RBOOT kiszolgálót kérhetnek BOOTP " +"helyett." #. Tag: para -#: boot-installer.xml:451 -#: boot-installer.xml:1013 -#: boot-installer.xml:1516 -#: boot-installer.xml:1999 -#: boot-installer.xml:2514 -#: boot-installer.xml:2610 +#: boot-installer.xml:451 boot-installer.xml:1013 boot-installer.xml:1516 +#: boot-installer.xml:1999 boot-installer.xml:2514 boot-installer.xml:2610 #, no-c-format -msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>." -msgstr "A hálózati indítást támogató telepítő mód leírása itt található: <xref linkend=\"install-tftp\"/>." +msgid "" +"The installation method to support network booting is described in <xref " +"linkend=\"install-tftp\"/>." +msgstr "" +"A hálózati indítást támogató telepítő mód leírása itt található: <xref " +"linkend=\"install-tftp\"/>." #. Tag: title #: boot-installer.xml:459 @@ -579,40 +766,70 @@ msgstr "TFTP indítás Netwinder gépen" #. 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>)." -msgstr "A Netwinder gépeknek 2 hálózati csatolója van: egy 10Mbps NE2000-kompatibilis kártya (általában <literal>eth0</literal>) és egy 100Mbps Tulip kártya. Utóbbival gondok lehetnek a kép TFTP letöltésekor így ajánlott a 10Mbps csatoló használata (a <literal>10 Base-T</literal> címkéjű)." +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 "" +"A Netwinder gépeknek 2 hálózati csatolója van: egy 10Mbps NE2000-" +"kompatibilis kártya (általában <literal>eth0</literal>) és egy 100Mbps Tulip " +"kártya. Utóbbival gondok lehetnek a kép TFTP letöltésekor így ajánlott a " +"10Mbps csatoló használata (a <literal>10 Base-T</literal> címkéjű)." #. 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 @@ -624,7 +841,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 @@ -634,54 +853,75 @@ msgid "Booting from CD-ROM" msgstr "Indítás CD-ROM lemezről" #. Tag: para -#: boot-installer.xml:546 -#: boot-installer.xml:716 -#: boot-installer.xml:1125 -#: boot-installer.xml:1946 -#: boot-installer.xml:2286 -#: boot-installer.xml:2640 +#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1125 +#: boot-installer.xml:1946 boot-installer.xml:2286 boot-installer.xml:2640 #, 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." -msgstr "A legtöbb felhasználó számára a legegyszerűbb mód a Debian CD-készlet használata. Ha van egy CD-készleted és a géped támogatja a CD-lemezről indítást, akkor minden csodás. Egyszerűen <phrase arch=\"x86\"> állítsd be a gépet, hogy CD-lemezről induljon, ahogy a <xref linkend=\"boot-dev-select\"/> részben is leírjuk, </phrase> tedd be a CD-lemezt, indítsd róla a gépet és végezd el a telepítést, erről a következő fejezet súg." +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 "" +"A legtöbb felhasználó számára a legegyszerűbb mód a Debian CD-készlet " +"használata. Ha van egy CD-készleted és a géped támogatja a CD-lemezről " +"indítást, akkor minden csodás. Egyszerűen <phrase arch=\"x86\"> állítsd be a " +"gépet, hogy CD-lemezről induljon, ahogy a <xref linkend=\"boot-dev-select\"/" +"> részben is leírjuk, </phrase> tedd be a CD-lemezt, indítsd róla a gépet és " +"végezd el a telepítést, erről a következő fejezet súg." #. Tag: para -#: boot-installer.xml:557 -#: boot-installer.xml:727 -#: boot-installer.xml:1136 -#: boot-installer.xml:1957 -#: boot-installer.xml:2297 -#: boot-installer.xml:2651 +#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1136 +#: boot-installer.xml:1957 boot-installer.xml:2297 boot-installer.xml:2651 #, 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." -msgstr "Egyes CD-eszközök különleges meghajtókat igényelnek és elérhetetlenek lehetnek a telepítő első lépéseiben. Ha a CD-lemezről indítás szokásos módja nem működik a gépeden, nézd át újra e fejezetet és olvasd el az eltérő kernelekről és telepítő módokról szóló részeket, mely megoldja ezt." +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 "" +"Egyes CD-eszközök különleges meghajtókat igényelnek és elérhetetlenek " +"lehetnek a telepítő első lépéseiben. Ha a CD-lemezről indítás szokásos módja " +"nem működik a gépeden, nézd át újra e fejezetet és olvasd el az eltérő " +"kernelekről és telepítő módokról szóló részeket, mely megoldja ezt." #. Tag: para -#: boot-installer.xml:565 -#: boot-installer.xml:735 -#: boot-installer.xml:1144 -#: boot-installer.xml:1965 -#: boot-installer.xml:2305 -#: boot-installer.xml:2659 +#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1144 +#: boot-installer.xml:1965 boot-installer.xml:2305 boot-installer.xml:2659 #, 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." -msgstr "Még abban az esetben is, ha nem tudsz CD-ROM lemezről indítani, valószínűleg képes leszel a Debian rendszer összetevőit és a kívánt csomagokat telepíteni ezekről. Egyszerűen indíts más médiumról, például flopiról. Az operációs rendszer, alaprendszer és tetszőleges további csomagok telepítésekor a telepítő rendszert a CD-ROM meghajtóra irányíthatod." +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 "" +"Még abban az esetben is, ha nem tudsz CD-ROM lemezről indítani, valószínűleg " +"képes leszel a Debian rendszer összetevőit és a kívánt csomagokat telepíteni " +"ezekről. Egyszerűen indíts más médiumról, például flopiról. Az operációs " +"rendszer, alaprendszer és tetszőleges további csomagok telepítésekor a " +"telepítő rendszert a CD-ROM meghajtóra irányíthatod." #. Tag: para -#: boot-installer.xml:573 -#: boot-installer.xml:743 -#: boot-installer.xml:1152 -#: boot-installer.xml:1973 -#: boot-installer.xml:2313 -#: boot-installer.xml:2667 +#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1152 +#: boot-installer.xml:1973 boot-installer.xml:2313 boot-installer.xml:2667 #, no-c-format -msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." -msgstr "Ha gondjaid vannak ez indítással, lásd az <xref linkend=\"boot-troubleshooting\"/> részt." +msgid "" +"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." +msgstr "" +"Ha gondjaid vannak ez indítással, lásd az <xref linkend=\"boot-" +"troubleshooting\"/> részt." #. 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>" -msgstr "Egy CD-ROM indításához Cyclone konzol jelről, használd a <command>boot cd0:cats.bin</command> parancsot" +msgid "" +"To boot a CD-ROM from the Cyclone console prompt, use the command " +"<command>boot cd0:cats.bin</command>" +msgstr "" +"Egy CD-ROM indításához Cyclone konzol jelről, használd a <command>boot cd0:" +"cats.bin</command> parancsot" #. Tag: title #: boot-installer.xml:589 @@ -692,13 +932,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 @@ -722,7 +969,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 @@ -735,9 +987,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 @@ -749,15 +1021,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:1119 -#: boot-installer.xml:1934 -#: boot-installer.xml:2280 -#: boot-installer.xml:2634 +#: boot-installer.xml:710 boot-installer.xml:1119 boot-installer.xml:1934 +#: boot-installer.xml:2280 boot-installer.xml:2634 #, no-c-format msgid "Booting from a CD-ROM" msgstr "Indítás egy CD-ROM lemezről" @@ -765,32 +1037,71 @@ msgstr "Indítás egy CD-ROM lemezről" #. Tag: title #: boot-installer.xml:848 #, no-c-format -msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" -msgstr "Indítás Linuxból <command>LILO</command> vagy <command>GRUB</command> használatával" +msgid "" +"Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" +msgstr "" +"Indítás Linuxból <command>LILO</command> vagy <command>GRUB</command> " +"használatával" #. 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\"/>." -msgstr "A telepítő merevlemezről indításához először le kell tölteni és elhelyezni a <xref linkend=\"boot-drive-files\"/> részben írt fájlokat." +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 "" +"A telepítő merevlemezről indításához először le kell tölteni és elhelyezni a " +"<xref linkend=\"boot-drive-files\"/> részben írt fájlokat." #. 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." -msgstr "Ha a merevlemez csak indításra a többi letöltésre pedig a hálózat szolgál, a <filename>netboot/debian-installer/i386/initrd.gz</filename> fájl és a megfelelő kernel letöltése kell. Ezzel átparticionálható a telepítő indítására használt merevlemez, körültekintően." +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 "" +"Ha a merevlemez csak indításra a többi letöltésre pedig a hálózat szolgál, a " +"<filename>netboot/debian-installer/i386/initrd.gz</filename> fájl és a " +"megfelelő kernel letöltése kell. Ezzel átparticionálható a telepítő " +"indítására használt merevlemez, körültekintően." #. 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." -msgstr "Ha egy merevlemez-partíció változatlan marad a telepítés során, lehetőség nyílik a <filename>hd-media/initrd.gz</filename> fájl, hozzávaló kernel és egy CD iso letöltésére (az utóbbi fájl nevének vége maradjon <literal>.iso</literal>). A telepítő indíthat a meghajtóról és képes telepíteni a CD képről hálózat nélkül." +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 "" +"Ha egy merevlemez-partíció változatlan marad a telepítés során, lehetőség " +"nyílik a <filename>hd-media/initrd.gz</filename> fájl, hozzávaló kernel és " +"egy CD iso letöltésére (az utóbbi fájl nevének vége maradjon <literal>.iso</" +"literal>). A telepítő indíthat a meghajtóról és képes telepíteni a CD képről " +"hálózat nélkül." #. 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:" -msgstr "<command>LILO</command> esetén 2 dolgot kell beállítani a <filename>/etc/lilo.conf</filename> fájlban, melyek: <itemizedlist> <listitem><para> az <filename>initrd.gz</filename> telepítő betöltése induláskor; </para></listitem> <listitem><para> a <filename>vmlinuz</filename> kernel egy RAM lemezt használjon gyökér-partícióként. </para></listitem> </itemizedlist> Itt egy példa <filename>/etc/lilo.conf</filename>:" +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 "" +"<command>LILO</command> esetén 2 dolgot kell beállítani a <filename>/etc/" +"lilo.conf</filename> fájlban, melyek: <itemizedlist> <listitem><para> az " +"<filename>initrd.gz</filename> telepítő betöltése induláskor; </para></" +"listitem> <listitem><para> a <filename>vmlinuz</filename> kernel egy RAM " +"lemezt használjon gyökér-partícióként. </para></listitem> </itemizedlist> " +"Itt egy példa <filename>/etc/lilo.conf</filename>:" #. Tag: screen #: boot-installer.xml:894 @@ -811,20 +1122,36 @@ 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." -msgstr "További részletekért lásd az <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> és <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man oldalakat. Futtasd a <userinput>lilo</userinput>-t és indíts újra." +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 "" +"További részletekért lásd az <citerefentry><refentrytitle>initrd</" +"refentrytitle> <manvolnum>4</manvolnum></citerefentry> és " +"<citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</" +"manvolnum></citerefentry> man oldalakat. Futtasd a <userinput>lilo</" +"userinput>-t és indíts újra." #. 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" "</screen></informalexample> and reboot." msgstr "" -"A <command>GRUB</command> hasonló. Menj a <filename>menu.lst</filename> fájlra a <filename>/boot/grub/</filename> (néha a <filename>/boot/boot/grub/</filename>) könyvtárban és add hozzá a következő sorokat: <informalexample><screen>\n" +"A <command>GRUB</command> hasonló. Menj a <filename>menu.lst</filename> " +"fájlra a <filename>/boot/grub/</filename> (néha a <filename>/boot/boot/grub/" +"</filename>) könyvtárban és add hozzá a következő sorokat: " +"<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" @@ -833,8 +1160,14 @@ 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>." -msgstr "A <userinput>ramdisk_size</userinput> értéke természetesen nem lehet kisebb, mint ami az initrd képhez szükséges. Innentől nincs különbség a <command>GRUB</command> vagy <command>LILO</command> között." +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 "" +"A <userinput>ramdisk_size</userinput> értéke természetesen nem lehet kisebb, " +"mint ami az initrd képhez szükséges. Innentől nincs különbség a " +"<command>GRUB</command> vagy <command>LILO</command> között." #. Tag: title #: boot-installer.xml:925 @@ -845,60 +1178,119 @@ msgstr "Indítás USB tárról" #. 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;." -msgstr "A korábbi <xref linkend=\"boot-dev-select\"/> és <xref linkend=\"boot-usb-files\"/> részben írtak elkészültét feltételezzük. Dugd be az USB tárolót egy szabad USB csatlakozóba és indítsd újra a gépet. Ha minden rendben, a rendszer erről fog indulni és erről ad egy <prompt>boot:</prompt> jelet. A 2 lehetőség: további indító argumentumok megadása vagy az &enterkey; leütése." +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 "" +"A korábbi <xref linkend=\"boot-dev-select\"/> és <xref linkend=\"boot-usb-" +"files\"/> részben írtak elkészültét feltételezzük. Dugd be az USB tárolót " +"egy szabad USB csatlakozóba és indítsd újra a gépet. Ha minden rendben, a " +"rendszer erről fog indulni és erről ad egy <prompt>boot:</prompt> jelet. A 2 " +"lehetőség: további indító argumentumok megadása vagy az &enterkey; leütése." #. Tag: title -#: boot-installer.xml:939 -#: boot-installer.xml:2046 -#: boot-installer.xml:2540 +#: boot-installer.xml:939 boot-installer.xml:2046 boot-installer.xml:2540 #: boot-installer.xml:2688 #, no-c-format msgid "Booting from Floppies" msgstr "Indítás flopikról" #. Tag: para -#: boot-installer.xml:940 -#: boot-installer.xml:2548 +#: boot-installer.xml:940 boot-installer.xml:2548 #, 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\"/>." -msgstr "Itt szükség lesz a már letöltött flopi-képekre és a képekből a <xref linkend=\"create-floppy\"/> részben létrehozott flopikra." +msgid "" +"You will have already downloaded the floppy images you needed and created " +"floppies from the images in <xref linkend=\"create-floppy\"/>." +msgstr "" +"Itt szükség lesz a már letöltött flopi-képekre és a képekből a <xref linkend=" +"\"create-floppy\"/> részben létrehozott flopikra." #. 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." -msgstr "A telepítő flopi indításához, tedd az elsődleges flopi meghajtóba, állítsd le a rendszert, ahogy egyébként tennéd és indítsd újra a gépet." +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 "" +"A telepítő flopi indításához, tedd az elsődleges flopi meghajtóba, állítsd " +"le a rendszert, ahogy egyébként tennéd és indítsd újra a gépet." #. 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." -msgstr "Egy LS-120 meghajtóról (ATAPI változat) indításhoz egy flopi-készlettel, meg kell adni a flopi eszköz virtuális helyét. Ez a <emphasis>root=</emphasis> indító argumentummal tehető, megadva az eszközt, melyre az ide-floppy meghajtó helyezze. Például, ha az LS-120 meghajtó az 1. IDE eszköz (mester) a második kábelen, írd be ezt: <userinput>linux root=/dev/hdc</userinput> az indító jelnél." +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." +msgstr "" +"Egy LS-120 meghajtóról (ATAPI változat) indításhoz egy flopi-készlettel, meg " +"kell adni a flopi eszköz virtuális helyét. Ez a <emphasis>root=</emphasis> " +"indító argumentummal tehető, megadva az eszközt, melyre az ide-floppy " +"meghajtó helyezze. Például, ha az LS-120 meghajtó az 1. IDE eszköz (mester) " +"a második kábelen, írd be ezt: <userinput>linux root=/dev/hdc</userinput> az " +"indító jelnél." #. Tag: para #: boot-installer.xml:963 #, 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." -msgstr "Egyes gépeken a <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> nem indítja újra helyesen a gépet, így egy <quote>hideg</quote> újraindítás ajánlott. Ha egy létező rendszerről telepítesz (például DOS alól), nincs választásod. Általában, ha lehet, végezz hidegindítást." +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 "" +"Egyes gépeken a <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> " +"<keycap>Delete</keycap></keycombo> nem indítja újra helyesen a gépet, így " +"egy <quote>hideg</quote> újraindítás ajánlott. Ha egy létező rendszerről " +"telepítesz (például DOS alól), nincs választásod. Általában, ha lehet, " +"végezz hidegindítást." #. Tag: para #: boot-installer.xml:972 #, 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." -msgstr "A flopi lemez elindul és ekkor látnod kell egy képernyőt, mely bemutatja az indító flopit és egy <prompt>boot:</prompt> jellel zárul." +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 "" +"A flopi lemez elindul és ekkor látnod kell egy képernyőt, mely bemutatja az " +"indító flopit és egy <prompt>boot:</prompt> jellel zárul." #. Tag: para #: boot-installer.xml:978 #, 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\"/>." -msgstr "Az &enterkey; lenyomásakor a <computeroutput>Loading...</computeroutput> üzenetnek kell jönnie, ezt követi ez: <computeroutput>Uncompressing Linux...</computeroutput>, majd sok-sok adat a gépben lévő hardverről. A telepítő folyamat e szakaszáról több adat az alábbi: <xref linkend=\"kernel-msgs\"/> részben található." +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 "" +"Az &enterkey; lenyomásakor a <computeroutput>Loading...</computeroutput> " +"üzenetnek kell jönnie, ezt követi ez: <computeroutput>Uncompressing Linux..." +"</computeroutput>, majd sok-sok adat a gépben lévő hardverről. A telepítő " +"folyamat e szakaszáról több adat az alábbi: <xref linkend=\"kernel-msgs\"/> " +"részben található." #. Tag: para #: boot-installer.xml:987 #, 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." -msgstr "Az indító flopi után az a root flopit kéri. Tedd be a root flopit és üsd le az &enterkey;-t, ekkor tartalma a memóriába olvasásra kerül. A <command>debian-installer</command> telepítő program elindul." +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 "" +"Az indító flopi után az a root flopit kéri. Tedd be a root flopit és üsd le " +"az &enterkey;-t, ekkor tartalma a memóriába olvasásra kerül. A " +"<command>debian-installer</command> telepítő program elindul." #. Tag: para #: boot-installer.xml:1021 @@ -915,8 +1307,16 @@ msgstr "PXE-támogató hálózati kártya vagy alaplap" #. Tag: para #: boot-installer.xml:1028 #, 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." -msgstr "Lehet, hogy a hálózati csatoló kártya vagy alaplap PXE indítást is támogat. Ez a TFTP indítás egy <trademark class=\"trade\">Intel</trademark> megvalósítása. Ha így van, lehetőség van a BIOS hálózati indításra állítására." +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 "" +"Lehet, hogy a hálózati csatoló kártya vagy alaplap PXE indítást is támogat. " +"Ez a TFTP indítás egy <trademark class=\"trade\">Intel</trademark> " +"megvalósítása. Ha így van, lehetőség van a BIOS hálózati indításra " +"állítására." #. Tag: title #: boot-installer.xml:1039 @@ -927,14 +1327,20 @@ msgstr "NIC hálózati indító ROM-mal" #. Tag: para #: boot-installer.xml:1040 #, 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 "Lehet, hogy hálózati csatoló kártyád TFTP indítást kínál." #. Tag: para #: boot-installer.xml:1045 #, no-c-format -msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document." -msgstr "Tudasd velünk (<email>&email-debian-boot-list;</email>) hogyan kezelted. Hivatkozz e dokumentumra." +msgid "" +"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. " +"Please refer to this document." +msgstr "" +"Tudasd velünk (<email>&email-debian-boot-list;</email>) hogyan kezelted. " +"Hivatkozz e dokumentumra." #. Tag: title #: boot-installer.xml:1053 @@ -945,8 +1351,12 @@ msgstr "Etherboot" #. Tag: para #: boot-installer.xml:1054 #, no-c-format -msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot." -msgstr "Az <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> TFTP indítást adó indító lemezeket és indító romokat ad." +msgid "" +"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> " +"provides bootdiskettes and even bootroms that do a TFTPboot." +msgstr "" +"Az <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> TFTP " +"indítást adó indító lemezeket és indító romokat ad." #. Tag: title #: boot-installer.xml:1063 @@ -958,25 +1368,69 @@ msgstr "Az indító jel" #: boot-installer.xml:1064 #, 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 "" -"A telepítő indulásakor egy barátságos grafikus képernyőt látsz a Debian logóval és az indító jellel: <informalexample><screen>\n" +"A telepítő indulásakor egy barátságos grafikus képernyőt látsz a Debian " +"logóval és az indító jellel: <informalexample><screen>\n" "Press F1 for help, or ENTER to boot:\n" -"</screen></informalexample> Az indító jelnél leütheted az &enterkey; billentyűt a telepítő alap lehetőségeivel indításhoz vagy beírhatsz egy adott indító módot és, tetszőlegesen, indító paramétereket." +"</screen></informalexample> Az indító jelnél leütheted az &enterkey; " +"billentyűt a telepítő alap lehetőségeivel indításhoz vagy beírhatsz egy " +"adott indító módot és, tetszőlegesen, indító paramétereket." #. Tag: para #: boot-installer.xml:1076 #, 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>)." -msgstr "Az elérhető indító módok és paraméterek, melyek hasznosak lehetnek az <keycap>F2</keycap> és <keycap>F8</keycap> közti billentyűk leütésével érhetők el. Ha paramétert adsz az indító parancs sorhoz, írd be az indító módot (az alap a <userinput>linux</userinput>) és egy szóközt az 1. paraméter előtt (például <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 "" +"Az elérhető indító módok és paraméterek, melyek hasznosak lehetnek az " +"<keycap>F2</keycap> és <keycap>F8</keycap> közti billentyűk leütésével " +"érhetők el. Ha paramétert adsz az indító parancs sorhoz, írd be az indító " +"módot (az alap a <userinput>linux</userinput>) és egy szóközt az 1. " +"paraméter előtt (például <userinput>linux fb=false</userinput>)." #. Tag: para #: boot-installer.xml:1085 #, 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." -msgstr "Ha a rendszert távoli kezelő eszközön át telepíted, mely szöveges felületet ad a VGA konzolhoz, talán nem látod a kezdő grafikus üdvözlő képernyőt a telepítő indításakor és az indító jelet. Ezek közütt van a Compaq's <quote>integrated Lights Out</quote> (iLO) és HP's <quote>Integrated Remote Assistant</quote> (IRA). Vakon nyomd meg az F1 billentyűt <footnote> <para> Néha ehhez különleges escape sor kell, például IRA esetén <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</keycap>. </para> </footnote> a képernyő átugrásával a súgóra lépéshez. Ezután a leütött billentyűk már a várkozásnak megfelelően megjelennek a beviteli jelnél. A framebuffer tiltásához a telepítéskor a <userinput>fb=false</userinput> hozzáadása kell az indító jelnél, ahogy azt a súgó is írja." +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 "" +"Ha a rendszert távoli kezelő eszközön át telepíted, mely szöveges felületet " +"ad a VGA konzolhoz, talán nem látod a kezdő grafikus üdvözlő képernyőt a " +"telepítő indításakor és az indító jelet. Ezek közütt van a Compaq's " +"<quote>integrated Lights Out</quote> (iLO) és HP's <quote>Integrated Remote " +"Assistant</quote> (IRA). Vakon nyomd meg az F1 billentyűt <footnote> <para> " +"Néha ehhez különleges escape sor kell, például IRA esetén <keycombo> " +"<keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</" +"keycap>. </para> </footnote> a képernyő átugrásával a súgóra lépéshez. " +"Ezután a leütött billentyűk már a várkozásnak megfelelően megjelennek a " +"beviteli jelnél. A framebuffer tiltásához a telepítéskor a " +"<userinput>fb=false</userinput> hozzáadása kell az indító jelnél, ahogy azt " +"a súgó is írja." #. Tag: title #: boot-installer.xml:1160 @@ -987,31 +1441,72 @@ msgstr "" #. Tag: para #: boot-installer.xml:1162 #, 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:1178 #, 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:1194 #, 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:1203 #, 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:1215 #, 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 @@ -1023,7 +1518,14 @@ msgstr "" #. Tag: para #: boot-installer.xml:1235 #, 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 @@ -1035,37 +1537,62 @@ msgstr "" #. Tag: para #: boot-installer.xml:1254 #, 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:1260 #, 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:1266 #, 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:1277 #, 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:1288 #, 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:1300 #, 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 @@ -1077,43 +1604,73 @@ msgstr "" #. Tag: para #: boot-installer.xml:1311 #, 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:1322 #, 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:1328 #, 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:1342 #, 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:1349 #, 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:1356 #, 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:1363 #, 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 @@ -1125,31 +1682,57 @@ msgstr "" #. Tag: para #: boot-installer.xml:1379 #, 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:1390 #, 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:1397 #, 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:1408 #, 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:1417 #, 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 @@ -1161,49 +1744,85 @@ msgstr "" #. Tag: para #: boot-installer.xml:1428 #, 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:1440 #, 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:1458 #, 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:1463 #, 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:1470 #, 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:1479 #, 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:1490 #, 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:1524 #, 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 @@ -1216,19 +1835,26 @@ msgstr "" #: boot-installer.xml:1536 #, 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:1546 #, 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 @@ -1246,7 +1872,15 @@ msgstr "" #. Tag: para #: boot-installer.xml:1556 #, 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 @@ -1258,19 +1892,38 @@ msgstr "" #. Tag: para #: boot-installer.xml:1574 #, 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:1606 #, 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:1615 #, 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 @@ -1282,25 +1935,36 @@ msgstr "" #. Tag: para #: boot-installer.xml:1630 #, 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:1638 #, 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:1643 #, 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:1648 #, 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 @@ -1312,13 +1976,18 @@ msgstr "" #. Tag: para #: boot-installer.xml:1666 #, 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:1672 #, 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 @@ -1330,13 +1999,18 @@ msgstr "" #. Tag: para #: boot-installer.xml:1682 #, 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:1689 #, 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 @@ -1348,7 +2022,10 @@ msgstr "" #. Tag: para #: boot-installer.xml:1699 #, 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 @@ -1360,13 +2037,24 @@ msgstr "" #. Tag: para #: boot-installer.xml:1710 #, 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:1717 #, 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 @@ -1378,7 +2066,11 @@ msgstr "" #. Tag: para #: boot-installer.xml:1733 #, 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 @@ -1390,7 +2082,10 @@ msgstr "" #. Tag: para #: boot-installer.xml:1744 #, 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 @@ -1400,29 +2095,43 @@ msgid "Booting from a Hard Disk" msgstr "" #. Tag: para -#: boot-installer.xml:1761 -#: boot-installer.xml:2359 +#: boot-installer.xml:1761 boot-installer.xml:2359 #, 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:1767 -#: boot-installer.xml:2365 +#: boot-installer.xml:1767 boot-installer.xml:2365 #, 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:1776 #, 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:1784 #, 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 @@ -1434,13 +2143,24 @@ msgstr "" #. Tag: para #: boot-installer.xml:1806 #, 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:1812 #, 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 @@ -1452,13 +2172,24 @@ msgstr "" #. Tag: para #: boot-installer.xml:1828 #, 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:1835 #, 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 @@ -1470,37 +2201,73 @@ msgstr "" #. Tag: para #: boot-installer.xml:1851 #, 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:1862 #, 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:1871 #, 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:1886 #, 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:1895 #, 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:1902 #, 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 @@ -1518,19 +2285,27 @@ msgstr "" #. Tag: para #: boot-installer.xml:1923 #, 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:1935 #, 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:2007 #, 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 @@ -1554,24 +2329,29 @@ msgstr "" #. Tag: para #: boot-installer.xml:2035 #, 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:2047 #, 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:2052 #, 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:2068 -#: boot-installer.xml:2115 +#: boot-installer.xml:2068 boot-installer.xml:2115 #, no-c-format msgid "SGI TFTP Booting" msgstr "" @@ -1582,36 +2362,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:2088 -#: boot-installer.xml:2137 -#: boot-installer.xml:2192 +#: boot-installer.xml:2088 boot-installer.xml:2137 boot-installer.xml:2192 #: boot-installer.xml:2231 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:2089 -#: boot-installer.xml:2193 +#: boot-installer.xml:2089 boot-installer.xml:2193 #, 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:2112 -#: boot-installer.xml:2216 -#: boot-installer.xml:2739 +#: boot-installer.xml:2112 boot-installer.xml:2216 boot-installer.xml:2739 #, no-c-format msgid "Boot Parameters" msgstr "" @@ -1619,16 +2405,21 @@ msgstr "" #. Tag: para #: boot-installer.xml:2116 #, 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:2121 #, 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 @@ -1638,15 +2429,17 @@ msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: para -#: boot-installer.xml:2138 -#: boot-installer.xml:2232 +#: boot-installer.xml:2138 boot-installer.xml:2232 #, 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:2157 -#: boot-installer.xml:2219 +#: boot-installer.xml:2157 boot-installer.xml:2219 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "" @@ -1654,25 +2447,43 @@ msgstr "" #. Tag: para #: boot-installer.xml:2158 #, 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:2168 #, 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:2177 #, 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:2220 #, 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 @@ -1684,13 +2495,19 @@ msgstr "" #. Tag: para #: boot-installer.xml:2249 #, 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:2254 #, no-c-format -msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting an ssh session which will launch the standard installation system." +msgid "" +"The booting process starts with a network setup that prompts you for several " +"network parameters. If the setup is successful, you will login to the system " +"by starting an ssh session which will launch the standard installation " +"system." msgstr "" #. Tag: title @@ -1702,25 +2519,44 @@ msgstr "" #. Tag: para #: boot-installer.xml:2266 #, 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:2320 #, 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:2329 #, 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:2338 #, 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 @@ -1756,7 +2592,15 @@ msgstr "" #. Tag: para #: boot-installer.xml:2384 #, 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 @@ -1769,11 +2613,27 @@ msgstr "" #: boot-installer.xml:2403 #, 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 @@ -1791,34 +2651,62 @@ msgstr "" #. Tag: para #: boot-installer.xml:2445 #, 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:2457 #, 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:2469 #, 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:2483 #, 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:2489 #, 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 @@ -1830,31 +2718,51 @@ msgstr "" #. Tag: para #: boot-installer.xml:2526 #, 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:2541 #, 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:2553 #, 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:2559 #, 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:2566 #, 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 @@ -1866,19 +2774,37 @@ msgstr "" #. Tag: para #: boot-installer.xml:2578 #, 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:2618 #, 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:2674 #, 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 @@ -1887,23 +2813,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:2701 #, 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:2708 #, 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 @@ -1915,25 +2852,43 @@ msgstr "" #. Tag: para #: boot-installer.xml:2721 #, 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:2740 #, 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:2747 #, 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:2754 #, 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 @@ -1941,20 +2896,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:2779 #, 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:2792 #, 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 @@ -1966,486 +2940,1012 @@ msgstr "" #. Tag: para #: boot-installer.xml:2804 #, 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> With current kernels (2.6.9 or newer) you can " +"use 32 command line options and 32 environment options. If these numbers are " +"exceeded, the kernel will panic. </para> </footnote> which may be useful." msgstr "" #. Tag: term -#: boot-installer.xml:2824 +#: boot-installer.xml:2821 #, no-c-format msgid "debconf/priority" msgstr "" #. Tag: para -#: boot-installer.xml:2825 +#: boot-installer.xml:2822 #, 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:2830 +#: boot-installer.xml:2827 #, 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:2837 +#: boot-installer.xml:2834 #, no-c-format -msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss." +msgid "" +"If you add <userinput>priority=medium</userinput> as boot parameter, you " +"will be shown the installation menu and gain more control over the " +"installation. When <userinput>priority=low</userinput> is used, all messages " +"are shown (this is equivalent to the <emphasis>expert</emphasis> boot " +"method). With <userinput>priority=critical</userinput>, the installation " +"system will display only critical messages and try to do the right thing " +"without fuss." msgstr "" #. Tag: term -#: boot-installer.xml:2851 +#: boot-installer.xml:2848 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para -#: boot-installer.xml:2852 +#: boot-installer.xml:2849 #, 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 -#: boot-installer.xml:2888 +#: boot-installer.xml:2885 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:2889 +#: boot-installer.xml:2886 #, no-c-format -msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)" +msgid "" +"Setting this boot parameter to 2 will cause the installer's boot process to " +"be verbosely logged. Setting it to 3 makes debug shells available at " +"strategic points in the boot process. (Exit the shells to continue the boot " +"process.)" msgstr "" #. Tag: userinput -#: boot-installer.xml:2898 +#: boot-installer.xml:2895 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:2899 +#: boot-installer.xml:2896 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:2903 +#: boot-installer.xml:2900 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:2904 +#: boot-installer.xml:2901 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:2908 +#: boot-installer.xml:2905 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:2909 +#: boot-installer.xml:2906 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:2913 +#: boot-installer.xml:2910 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:2914 +#: boot-installer.xml:2911 #, no-c-format -msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot." +msgid "" +"Shells are run at various points in the boot process to allow detailed " +"debugging. Exit the shell to continue the boot." msgstr "" #. Tag: term -#: boot-installer.xml:2928 +#: boot-installer.xml:2925 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:2929 +#: boot-installer.xml:2926 #, 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:2935 +#: boot-installer.xml:2932 #, no-c-format -msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device." +msgid "" +"The boot floppy, which normally scans all floppies it can to find the root " +"floppy, can be overridden by this parameter to only look at the one device." msgstr "" #. Tag: term -#: boot-installer.xml:2945 +#: boot-installer.xml:2942 #, no-c-format msgid "debian-installer/framebuffer" msgstr "" #. Tag: para -#: boot-installer.xml:2946 +#: boot-installer.xml:2943 #, 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:2956 +#: boot-installer.xml:2953 #, no-c-format -msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card." +msgid "" +"The <userinput>video=vga16:off</userinput> argument may also be used to " +"disable the kernel's use of the framebuffer. Such problems have been " +"reported on a Dell Inspiron with Mobile Radeon card." msgstr "" #. Tag: para -#: boot-installer.xml:2962 +#: boot-installer.xml:2959 #, no-c-format msgid "Such problems have been reported on the Amiga 1200 and SE/30." msgstr "" #. Tag: para -#: boot-installer.xml:2966 +#: boot-installer.xml:2963 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:2970 +#: boot-installer.xml:2967 #, no-c-format -msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short." +msgid "" +"Because of display problems on some systems, framebuffer support is " +"<emphasis>disabled by default</emphasis> for &arch-title;. This can result " +"in ugly display on systems that do properly support the framebuffer, like " +"those with ATI graphical cards. If you see display problems in the " +"installer, you can try booting with parameter <userinput>debian-installer/" +"framebuffer=true</userinput> or <userinput>fb=true</userinput> for short." msgstr "" #. Tag: term -#: boot-installer.xml:2984 +#: boot-installer.xml:2981 #, no-c-format msgid "debian-installer/theme" msgstr "" #. Tag: para -#: boot-installer.xml:2985 +#: boot-installer.xml:2982 #, no-c-format -msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with parameter <userinput>debian-installer/theme=<replaceable>dark</replaceable></userinput> or <userinput>theme=<replaceable>dark</replaceable></userinput>." +msgid "" +"A theme determines how the user interface of the installer looks (colors, " +"icons, etc.). What themes are available differs per frontend. Currently both " +"the newt and gtk frontends only have a <quote>dark</quote> theme that was " +"designed for visually impaired users. Set the theme by booting with " +"parameter <userinput>debian-installer/theme=<replaceable>dark</replaceable></" +"userinput> or <userinput>theme=<replaceable>dark</replaceable></userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:2998 +#: boot-installer.xml:2995 #, no-c-format msgid "debian-installer/probe/usb" msgstr "" #. Tag: para -#: boot-installer.xml:2999 +#: boot-installer.xml:2996 #, 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 -#: boot-installer.xml:3008 +#: boot-installer.xml:3005 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" #. Tag: para -#: boot-installer.xml:3009 +#: boot-installer.xml:3006 #, 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:3016 +#: boot-installer.xml:3013 #, no-c-format -msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually." +msgid "" +"If you have a DHCP server on your local network, but want to avoid it " +"because e.g. it gives wrong answers, you can use the parameter " +"<userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the " +"network with DHCP and to enter the information manually." msgstr "" #. Tag: term -#: boot-installer.xml:3027 +#: boot-installer.xml:3024 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:3028 +#: boot-installer.xml:3025 #, no-c-format -msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." +msgid "" +"Set to <userinput>false</userinput> to prevent starting PCMCIA services, if " +"that causes problems. Some laptops are well known for this misbehavior." msgstr "" #. Tag: term -#: boot-installer.xml:3038 +#: boot-installer.xml:3035 #, no-c-format msgid "preseed/url" msgstr "" #. Tag: para -#: boot-installer.xml:3039 +#: boot-installer.xml:3036 #, no-c-format -msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>url</userinput>" +msgid "" +"Specify the url to a preconfiguration file to download and use in automating " +"the install. See <xref linkend=\"automatic-install\"/>. Short form: " +"<userinput>url</userinput>" msgstr "" #. Tag: term -#: boot-installer.xml:3049 +#: boot-installer.xml:3046 #, no-c-format msgid "preseed/file" msgstr "" #. Tag: para -#: boot-installer.xml:3050 +#: boot-installer.xml:3047 #, no-c-format -msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>file</userinput>" +msgid "" +"Specify the path to a preconfiguration file to load to automating the " +"install. See <xref linkend=\"automatic-install\"/>. Short form: " +"<userinput>file</userinput>" msgstr "" #. Tag: term -#: boot-installer.xml:3060 +#: boot-installer.xml:3057 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:3061 +#: boot-installer.xml:3058 #, 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:3070 +#: boot-installer.xml:3067 #, no-c-format -msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation." -msgstr "Legyen <userinput>false</userinput> az automata kiadás kikapcsolásához, ekkor magadnak kell biztosítani, hogy a rendszer ne induljon önműködően az optikai meghajtóról a telepítés után." +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 "" +"Legyen <userinput>false</userinput> az automata kiadás kikapcsolásához, " +"ekkor magadnak kell biztosítani, hogy a rendszer ne induljon önműködően az " +"optikai meghajtóról a telepítés után." #. Tag: term -#: boot-installer.xml:3081 +#: boot-installer.xml:3078 #, no-c-format msgid "ramdisk_size" msgstr "ramdisk_size" #. Tag: para -#: boot-installer.xml:3082 +#: boot-installer.xml:3079 #, no-c-format msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." msgstr "2.2.x kernel esetén a &ramdisksize; beállítandó." #. Tag: term -#: boot-installer.xml:3090 +#: boot-installer.xml:3087 #, no-c-format msgid "directfb/hw-accel" msgstr "directfb/hw-accel" #. Tag: para -#: boot-installer.xml:3091 +#: boot-installer.xml:3088 #, no-c-format -msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. To enable it, set this parameter to <userinput>true</userinput> when booting the installer." -msgstr "A gtk felülethez (grafikus telepítő) a directfb hardveres gyorsítás alapból kikapcsolt. Bekapcsolásához, legyen a paraméter <userinput>true</userinput> a telepítő indításakor." +msgid "" +"For the gtk frontend (graphical installer), hardware acceleration in " +"directfb is disabled by default. To enable it, set this parameter to " +"<userinput>true</userinput> when booting the installer." +msgstr "" +"A gtk felülethez (grafikus telepítő) a directfb hardveres gyorsítás alapból " +"kikapcsolt. Bekapcsolásához, legyen a paraméter <userinput>true</userinput> " +"a telepítő indításakor." #. Tag: term -#: boot-installer.xml:3101 +#: boot-installer.xml:3098 #, no-c-format msgid "rescue/enable" msgstr "rescue/enable" #. Tag: para -#: boot-installer.xml:3102 +#: boot-installer.xml:3099 #, no-c-format -msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." -msgstr "Legyen <userinput>true</userinput> a rendes telepítés helyett mentő módba lépéshez. Lásd: <xref linkend=\"rescue\"/>." +msgid "" +"Set to <userinput>true</userinput> to enter rescue mode rather than " +"performing a normal installation. See <xref linkend=\"rescue\"/>." +msgstr "" +"Legyen <userinput>true</userinput> a rendes telepítés helyett mentő módba " +"lépéshez. Lásd: <xref linkend=\"rescue\"/>." #. Tag: title -#: boot-installer.xml:3120 +#: boot-installer.xml:3117 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "Hibák elhárítása a telepítő folyamat során" #. Tag: title -#: boot-installer.xml:3125 +#: boot-installer.xml:3122 +#, fuzzy, no-c-format +msgid "CD-ROM Reliability" +msgstr "Flopi lemezek megbízhatósága" + +#. Tag: para +#: boot-installer.xml:3123 +#, no-c-format +msgid "" +"Sometimes, especially with older CD-ROM drives, the installer may fail to " +"boot from a CD-ROM. The installer may also — even after booting " +"successfully from CD-ROM — fail to recognize the CD-ROM or return " +"errors while reading from it during the installation." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3130 +#, no-c-format +msgid "" +"There are a many different possible causes for these problems. We can only " +"list some common issues and provide general suggestions on how to deal with " +"them. The rest is up to you." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3136 +#, no-c-format +msgid "" +"If you cannot get the installation working from CD-ROM, try one of the other " +"installation methods that are available." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3144 +#, no-c-format +msgid "Common issues" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3147 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not support reading from discs that were burned " +"at high speeds using a modern CD writer." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3153 +#, no-c-format +msgid "" +"If your system boots correctly from the CD-ROM, it does not necessarily mean " +"that Linux also supports the CD-ROM (or, more correctly, the controller that " +"your CD-ROM drive is connected to)." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3160 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not work correctly if <quote>direct memory " +"access</quote> (DMA) is enabled." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3171 +#, no-c-format +msgid "How to investigate and maybe solve issues" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3172 +#, no-c-format +msgid "If the CD-ROM fails to boot, try the suggestions listed below." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3177 +#, no-c-format +msgid "" +"Check that your BIOS actually supports booting from CD-ROM (older systems " +"possibly don't) and that your CD-ROM drive supports the media you are using." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3183 +#, no-c-format +msgid "" +"If you downloaded an iso image, check that the md5sum of that image matches " +"the one listed for the image in the <filename>MD5SUMS</filename> file that " +"should be present in the same location as where you downloaded the image " +"from. <informalexample><screen>\n" +"$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n" +"a20391b12f7ff22ef705cee4059c6b92 <replaceable>debian-testing-i386-netinst." +"iso</replaceable>\n" +"</screen></informalexample> Next, check that the md5sum of the burned CD-ROM " +"matches as well. The following command should work. It uses the size of the " +"image to read the correct number of bytes from the CD-ROM." +msgstr "" + +#. Tag: screen +#: boot-installer.xml:3196 +#, no-c-format +msgid "" +"$ dd if=/dev/cdrom | \\\n" +"> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</" +"replaceable>` | \\\n" +"> md5sum\n" +"a20391b12f7ff22ef705cee4059c6b92 -\n" +"262668+0 records in\n" +"262668+0 records out\n" +"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3201 +#, no-c-format +msgid "" +"If, after the installer has been booted successfully, the CD-ROM is not " +"detected, sometimes simply trying again may solve the problem. If you have " +"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If " +"that does not work or if the CD-ROM is recognized but there are errors when " +"reading from it, try the suggestions listed below. Some basic knowledge of " +"Linux is required for this. To execute any of the commands, you should first " +"switch to the second virtual console (VT2) and activate the shell there." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3213 +#, no-c-format +msgid "" +"Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> " +"(use <command>nano</command> as editor) to check for any specific error " +"messages. After that, also check the output of <command>dmesg</command>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3220 +#, no-c-format +msgid "" +"Check in the output of <command>dmesg</command> if your CD-ROM drive was " +"recognized. You should see something like (the lines do not necessarily have " +"to be consecutive): <informalexample><screen>\n" +"Probing IDE interface ide1...\n" +"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" +"ide1 at 0x170-0x177,0x376 on irq 15\n" +"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" +"Uniform CD-ROM driver Revision: 3.20\n" +"</screen></informalexample> If you don't see something like that, chances " +"are the controller your CD-ROM is connected to was not recognized or may be " +"not supported at all. If you know what driver is needed for the drive, you " +"can try loading it manually using <command>modprobe</command>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3234 +#, no-c-format +msgid "" +"Check that there is a device node for your CD-ROM drive under <filename>/dev/" +"</filename>. In the example above, this would be <filename>/dev/hdc</" +"filename>. There should also be a <filename>/dev/cdroms/cdrom0</filename>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3242 +#, no-c-format +msgid "" +"Use the <command>mount</command> command to check if the CD-ROM is already " +"mounted; if not, try mounting it manually: <informalexample><screen>\n" +"$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n" +"</screen></informalexample> Check if there are any error messages after that " +"command." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3252 +#, no-c-format +msgid "" +"Check if DMA is currently enabled: <informalexample><screen>\n" +"$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n" +"$ grep dma settings\n" +"using_dma 1 0 1 rw\n" +"</screen></informalexample> A <quote>1</quote> means it is enabled. If it " +"is, try disabling it: <informalexample><screen>\n" +"$ echo -n \"using_dma:0\" >settings\n" +"</screen></informalexample> Make sure that you are in the directory for the " +"device that corresponds to your CD-ROM drive." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3266 +#, no-c-format +msgid "" +"If there are any problems during the installation, try checking the " +"integrity of the CD-ROM using the option near the bottom of the installer's " +"main menu. This option can also be used as a general test if the CD-ROM can " +"be read reliably." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3281 #, no-c-format msgid "Floppy Disk Reliability" msgstr "Flopi lemezek megbízhatósága" #. Tag: para -#: boot-installer.xml:3127 +#: boot-installer.xml:3283 #, no-c-format -msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." -msgstr "A Debian rendszert flopiról telepítők számára a legnagyobb gond a flopi megbízhatatlansága." +msgid "" +"The biggest problem for people using floppy disks to install Debian seems to " +"be floppy disk reliability." +msgstr "" +"A Debian rendszert flopiról telepítők számára a legnagyobb gond a flopi " +"megbízhatatlansága." #. Tag: para -#: boot-installer.xml:3132 +#: boot-installer.xml:3288 #, no-c-format -msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the Driver Floppies most of which indicate themselves with a flood of messages about disk I/O errors." -msgstr "Az indító flopival van a legtöbb gond, mert azt a gép közvetlenül olvassa a Linux indítása előtt. A gép maga általában sokkal megbízhatatlanabbul olvassa a flopit, mint a Linux flopi meghajtó és még üzenet nélkül is leállhat hibás adatok olvasásakor. Nagyon rossz az is, mikor a meghajtó flopikkal van gond, melyek ezt tömeges lemez I/O hiba üzenet jelzik." +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 "" +"Az indító flopival van a legtöbb gond, mert azt a gép közvetlenül olvassa a " +"Linux indítása előtt. A gép maga általában sokkal megbízhatatlanabbul " +"olvassa a flopit, mint a Linux flopi meghajtó és még üzenet nélkül is " +"leállhat hibás adatok olvasásakor. Nagyon rossz az is, mikor a meghajtó " +"flopikkal van gond, melyek ezt tömeges lemez I/O hiba üzenet jelzik." + +#. Tag: para +#: boot-installer.xml:3297 +#, fuzzy, no-c-format +msgid "" +"If you are having the installation stall at a particular floppy, the first " +"thing you should 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 "" +"Ha a telepítés elakad egy flopinál, legelőször töltsd le újra a flopi lemez " +"képet és írd egy <emphasis>másik</emphasis> flopira. A régi flopi " +"újraformázása általában akkor sem elég, ha nem írt hibát. Sok esetben csak " +"az oldja meg, ha egy másik gépen írod meg." #. Tag: para -#: boot-installer.xml:3141 +#: boot-installer.xml:3306 #, 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." -msgstr "Ha a telepítés elakad egy flopinál, legelőször töltsd le újra a flopi lemez képet és írd egy <emphasis>másik</emphasis> flopira. A régi flopi újraformázása általában akkor sem elég, ha nem írt hibát. Sok esetben csak az oldja meg, ha egy másik gépen írod meg." +msgid "" +"Normally you should not have download a floppy image again, but if you are " +"experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." +msgstr "" #. Tag: para -#: boot-installer.xml:3151 +#: boot-installer.xml:3312 #, no-c-format -msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy." -msgstr "Többször előfordult, hogy egy felhasználó <emphasis>három</emphasis> teljesen új flopit használt fel, mire az egyik végre hibátlan volt és sikeresen telepített." +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 "" +"Többször előfordult, hogy egy felhasználó <emphasis>három</emphasis> " +"teljesen új flopit használt fel, mire az egyik végre hibátlan volt és " +"sikeresen telepített." #. Tag: para -#: boot-installer.xml:3157 +#: boot-installer.xml:3318 #, no-c-format -msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers." -msgstr "Sokak gépe pedig csak többszöri indítás után tudta pontosan elolvasni a flopit és így ez csak ekkor tudott sikeresen elindulni. Ezt mind hibás hardver vagy firmware flopi meghajtók okozzák." +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 "" +"Sokak gépe pedig csak többszöri indítás után tudta pontosan elolvasni a " +"flopit és így ez csak ekkor tudott sikeresen elindulni. Ezt mind hibás " +"hardver vagy firmware flopi meghajtók okozzák." #. Tag: title -#: boot-installer.xml:3166 +#: boot-installer.xml:3327 #, no-c-format msgid "Boot Configuration" msgstr "Indító beállítás" #. Tag: para -#: boot-installer.xml:3168 +#: boot-installer.xml:3329 #, no-c-format -msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>." -msgstr "Ha kernel megáll az indító folyamat során, nem ismer fel perifériákat vagy meghajtókat helyesen, először az indító paramétereket kell ellenőrizni a korábbi <xref linkend=\"boot-parms\"/> szerint." +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 "" +"Ha kernel megáll az indító folyamat során, nem ismer fel perifériákat vagy " +"meghajtókat helyesen, először az indító paramétereket kell ellenőrizni a " +"korábbi <xref linkend=\"boot-parms\"/> szerint." #. Tag: para -#: boot-installer.xml:3175 +#: boot-installer.xml:3336 #, no-c-format -msgid "If you are booting with your own kernel instead of the one supplied with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>." -msgstr "Ha a telepítő által adott helyett saját kernelt indítasz, fontos, hogy a <userinput>CONFIG_DEVFS</userinput> be legyen állítva a kernelben. A telepítő a <userinput>CONFIG_DEVFS</userinput> meglétét igényli." +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 "" +"Ha a telepítő által adott helyett saját kernelt indítasz, fontos, hogy a " +"<userinput>CONFIG_DEVFS</userinput> be legyen állítva a kernelben. A " +"telepítő a <userinput>CONFIG_DEVFS</userinput> meglétét igényli." #. Tag: para -#: boot-installer.xml:3182 +#: boot-installer.xml:3343 #, no-c-format -msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" -msgstr "Bizonyos gondok gyakran megoldhatók kiegészítők és perifériák eltávolításával és újraindítással. <phrase arch=\"x86\"> Egyes belső modemek, hangkártyák és Plug-n-Play eszközök sok gondot adnak.</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 "" +"Bizonyos gondok gyakran megoldhatók kiegészítők és perifériák " +"eltávolításával és újraindítással. <phrase arch=\"x86\"> Egyes belső " +"modemek, hangkártyák és Plug-n-Play eszközök sok gondot adnak.</phrase>" #. Tag: para -#: boot-installer.xml:3188 +#: boot-installer.xml:3349 #, no-c-format -msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>." -msgstr "Ha több, mint 512M memória van a gépen és a telepítő megáll a kernel indításakor, előfordulhat, hogy egy indító argumentumot kell megadni a kernel által nézett memória korlátozására így: <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 "" +"Ha több, mint 512M memória van a gépen és a telepítő megáll a kernel " +"indításakor, előfordulhat, hogy egy indító argumentumot kell megadni a " +"kernel által nézett memória korlátozására így: <userinput>mem=512m</" +"userinput>." #. Tag: title -#: boot-installer.xml:3199 +#: boot-installer.xml:3360 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "Gyakori &arch-title; telepítő gondok" #. Tag: para -#: boot-installer.xml:3200 +#: boot-installer.xml:3361 #, no-c-format -msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." -msgstr "Van pár gyakori telepítő gond, mely megoldható vagy elkerülhető egyes indító paraméterek átadásával a telepítőnek." +msgid "" +"There are some common installation problems that can be solved or avoided by " +"passing certain boot parameters to the installer." +msgstr "" +"Van pár gyakori telepítő gond, mely megoldható vagy elkerülhető egyes indító " +"paraméterek átadásával a telepítőnek." #. Tag: para -#: boot-installer.xml:3205 +#: boot-installer.xml:3366 #, no-c-format -msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>." -msgstr "Egyes rendszereken <quote>fordított DCL</quote> flopik vannak. Ha hibákat kapsz a flopiról olvasáskor, pedig tudod, hogy a flopi jó, próbáld a <userinput>floppy=thinkpad</userinput> paramétert." +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 "" +"Egyes rendszereken <quote>fordított DCL</quote> flopik vannak. Ha hibákat " +"kapsz a flopiról olvasáskor, pedig tudod, hogy a flopi jó, próbáld a " +"<userinput>floppy=thinkpad</userinput> paramétert." #. Tag: para -#: boot-installer.xml:3211 +#: boot-installer.xml:3372 #, no-c-format -msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>." -msgstr "Egyes rendszereken, ilyen például az IBM PS/1 vagy ValuePoint (melyben ST-506 lemez meghajtók vannak), az IDE meghajtó felismerése hibás lehet. Előbb paraméterek nélkül próbáld, és nézd meg, az IDE meghajtó felismerése helyes-e. Ha nem, ellenőrizd a meghajtó geometriáját (cilinderek, fejek, szektorok) és használd a <userinput>hd=<replaceable>cilinderek</replaceable>,<replaceable>fejek</replaceable>,<replaceable>szektorok</replaceable></userinput> paramétert." +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 "" +"Egyes rendszereken, ilyen például az IBM PS/1 vagy ValuePoint (melyben ST-" +"506 lemez meghajtók vannak), az IDE meghajtó felismerése hibás lehet. Előbb " +"paraméterek nélkül próbáld, és nézd meg, az IDE meghajtó felismerése helyes-" +"e. Ha nem, ellenőrizd a meghajtó geometriáját (cilinderek, fejek, szektorok) " +"és használd a <userinput>hd=<replaceable>cilinderek</replaceable>," +"<replaceable>fejek</replaceable>,<replaceable>szektorok</replaceable></" +"userinput> paramétert." #. Tag: para -#: boot-installer.xml:3220 +#: boot-installer.xml:3381 #, no-c-format -msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test." -msgstr "Nagyon régi gépnél, ha a kernel megáll itt: <computeroutput>Checking 'hlt' instruction...</computeroutput>, próbáld a <userinput>no-hlt</userinput> indító argumentumot, mely kikapcsolja ezt a tesztet." +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 "" +"Nagyon régi gépnél, ha a kernel megáll itt: <computeroutput>Checking 'hlt' " +"instruction...</computeroutput>, próbáld a <userinput>no-hlt</userinput> " +"indító argumentumot, mely kikapcsolja ezt a tesztet." #. Tag: para -#: boot-installer.xml:3227 +#: boot-installer.xml:3388 #, no-c-format -msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false video=vga16:off</userinput> to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." -msgstr "Ha a képernyő fura képet ad a kernel indításakor, például tiszta fehér, tiszta fekete vagy színes kavar, a rendszer problematikus videó kártyát tartalmazhat, mely hibásan vált framebuffer módra. Ekkor használható a <userinput>fb=false video=vga16:off</userinput> ennek kikapcsolására. Ekkor csak az angol nyelv érhető el a telepítés alatt. Lásd ezt: <xref linkend=\"boot-parms\"/> a részletekért." +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 "" +"Ha a képernyő fura képet ad a kernel indításakor, például tiszta fehér, " +"tiszta fekete vagy színes kavar, a rendszer problematikus videó kártyát " +"tartalmazhat, mely hibásan vált framebuffer módra. Ekkor használható a " +"<userinput>fb=false video=vga16:off</userinput> ennek kikapcsolására. Ekkor " +"csak az angol nyelv érhető el a telepítés alatt. Lásd ezt: <xref linkend=" +"\"boot-parms\"/> a részletekért." #. Tag: title -#: boot-installer.xml:3241 +#: boot-installer.xml:3402 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "A rendszer fagyása a PCMCIA beállító szakaszban" #. Tag: para -#: boot-installer.xml:3242 +#: boot-installer.xml:3403 #, no-c-format -msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems." -msgstr "Egyes Dell laptopok összeomlanak, mikor a PCMCIA eszköz-érzékelő megpróbál elérni egyes hardver-címeket. Pár más laptop is haszonló. Ha ilyen gondot tapasztalsz és nincs szükséged PCMCIA támogatásra a telepítéskor, kapcsold ki a <userinput>hw-detect/start_pcmcia=false</userinput> indító paraméterrel. A telepítés után beállíthatod és kizárhatod a gondot adó erőforrás-tartományokat." +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 "" +"Egyes Dell laptopok összeomlanak, mikor a PCMCIA eszköz-érzékelő megpróbál " +"elérni egyes hardver-címeket. Pár más laptop is haszonló. Ha ilyen gondot " +"tapasztalsz és nincs szükséged PCMCIA támogatásra a telepítéskor, kapcsold " +"ki a <userinput>hw-detect/start_pcmcia=false</userinput> indító " +"paraméterrel. A telepítés után beállíthatod és kizárhatod a gondot adó " +"erőforrás-tartományokat." #. Tag: para -#: boot-installer.xml:3252 +#: boot-installer.xml:3413 #, no-c-format -msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer." -msgstr "A telepítő szakértő módban is indítható. Ekkor lehetőség nyílik a hardver igényeinek megfelelő erőforrás-tartományok bevitelére. Például a fenti Dell laptopokon megadható ez: <userinput>exclude port 0x800-0x8ff</userinput>. Van egy lista is néhány általános erőforrás-tartomány lehetőségről itt: <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">PCMCIA HOGYAN rendszer erőforrás-beállítások szakasz</ulink>. A vesszőket el kell hagyni, ha vannak, mikor beírod ezt az értéket a telepítőben." - -#. Tag: title -#: boot-installer.xml:3269 +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 "" +"A telepítő szakértő módban is indítható. Ekkor lehetőség nyílik a hardver " +"igényeinek megfelelő erőforrás-tartományok bevitelére. Például a fenti Dell " +"laptopokon megadható ez: <userinput>exclude port 0x800-0x8ff</userinput>. " +"Van egy lista is néhány általános erőforrás-tartomány lehetőségről itt: " +"<ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1." +"html#ss1.12\">PCMCIA HOGYAN rendszer erőforrás-beállítások szakasz</ulink>. " +"A vesszőket el kell hagyni, ha vannak, mikor beírod ezt az értéket a " +"telepítőben." + +#. Tag: title +#: boot-installer.xml:3430 #, no-c-format msgid "System Freeze while Loading the USB Modules" msgstr "A rendszer fagyása az USB modulok betöltésekor" #. Tag: para -#: boot-installer.xml:3270 +#: boot-installer.xml:3431 #, no-c-format -msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter at the boot prompt, which will prevent the modules from being loaded." -msgstr "A kernel alapban megpróbálja telepíteni az USB modulokat és az USB billentyű meghajtót pár nem-szabványos USB billentyű támogatásához. De van pár hibás USB rendszer, ahol a meghajtó lefagy betöltéskor. Ennek egyik elkerülése az USB vezérlő kikapcsolása a BIOS beállításban. Egy másik lehetőség a <userinput>debian-installer/probe/usb=false</userinput> paraméter átadása az indító jelnél, mely meggátolja e modulok betöltését." +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 "" +"A kernel alapban megpróbálja telepíteni az USB modulokat és az USB billentyű " +"meghajtót pár nem-szabványos USB billentyű támogatásához. De van pár hibás " +"USB rendszer, ahol a meghajtó lefagy betöltéskor. Ennek egyik elkerülése az " +"USB vezérlő kikapcsolása a BIOS beállításban. Egy másik lehetőség a " +"<userinput>debian-installer/probe/usb=false</userinput> paraméter átadása az " +"indító jelnél, mely meggátolja e modulok betöltését." #. Tag: title -#: boot-installer.xml:3284 +#: boot-installer.xml:3445 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "A kernel indító üzenetek értelmezése" #. Tag: para -#: boot-installer.xml:3286 +#: boot-installer.xml:3447 #, no-c-format -msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable> </computeroutput>, or <computeroutput> <replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable> </computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable> </computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." -msgstr "Az indítás alatt, sok ilyen üzenetet láthatsz: <computeroutput>can't find <replaceable>valami</replaceable> </computeroutput>, vagy <computeroutput> <replaceable>valami</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>valami</replaceable> </computeroutput>, vagy akár <computeroutput>this driver release depends on <replaceable>valami</replaceable> </computeroutput>. A legtöbb ilyen nem számít. Azért látod, mert a telepítőben lévő kernel úgy készült, hogy a legkülönbözőbb eszközöket támogassa. Persze egy gépen sincs az összes lehetséges eszköz, és az operációs rendszer jelezheti, ha olyat keres, ami nem található. Ez akkor történik, ha vár egy eszköz válaszára, az adott rendszer pedig nem tartalmaz olyat. Ha ezt túl hosszúnak találod, később egyéni kernelt is készíthetsz (lásd a <xref linkend=\"kernel-baking\"/> részt)." - -#. Tag: title -#: boot-installer.xml:3311 +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 "" +"Az indítás alatt, sok ilyen üzenetet láthatsz: <computeroutput>can't find " +"<replaceable>valami</replaceable> </computeroutput>, vagy <computeroutput> " +"<replaceable>valami</replaceable> not present</computeroutput>, " +"<computeroutput>can't initialize <replaceable>valami</replaceable> </" +"computeroutput>, vagy akár <computeroutput>this driver release depends on " +"<replaceable>valami</replaceable> </computeroutput>. A legtöbb ilyen nem " +"számít. Azért látod, mert a telepítőben lévő kernel úgy készült, hogy a " +"legkülönbözőbb eszközöket támogassa. Persze egy gépen sincs az összes " +"lehetséges eszköz, és az operációs rendszer jelezheti, ha olyat keres, ami " +"nem található. Ez akkor történik, ha vár egy eszköz válaszára, az adott " +"rendszer pedig nem tartalmaz olyat. Ha ezt túl hosszúnak találod, később " +"egyéni kernelt is készíthetsz (lásd a <xref linkend=\"kernel-baking\"/> " +"részt)." + +#. Tag: title +#: boot-installer.xml:3472 #, no-c-format msgid "Bug Reporter" msgstr "HIbajelentő" #. Tag: para -#: boot-installer.xml:3312 +#: boot-installer.xml:3473 #, no-c-format -msgid "If you get through the initial boot phase but cannot complete the install, the bug reporter menu choice may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them in a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report you may want to attach this information to the bug report." -msgstr "Ha túljutottál a kezdő indító szakaszon, de nem futott le teljesen végig a telepítés, a hibajelentő menü segíthet. Eltárolhatod a rendszer hiba naplóit és beállításait a telepítőből egy flopira, vagy letöltheted egy böngészőben. Ezek megadják a felmerült hibákat és javításukat. Ha jelentést küldesz, csatolhatod hozzá ezeket." +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 "" +"Ha túljutottál a kezdő indító szakaszon, de nem futott le teljesen végig a " +"telepítés, a hibajelentő menü segíthet. Eltárolhatod a rendszer hiba naplóit " +"és beállításait a telepítőből egy flopira, vagy letöltheted egy böngészőben. " +"Ezek megadják a felmerült hibákat és javításukat. Ha jelentést küldesz, " +"csatolhatod hozzá ezeket." #. Tag: para -#: boot-installer.xml:3323 +#: boot-installer.xml:3484 #, no-c-format -msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system." -msgstr "További telepítő üzenetek találhatók a <filename>/var/log/</filename> könyvtárban a telepítés során és a <filename>/var/log/installer/</filename> könyvtárban, miután a gép a telepített rendszert elindította." +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 "" +"További telepítő üzenetek találhatók a <filename>/var/log/</filename> " +"könyvtárban a telepítés során és a <filename>/var/log/installer/</filename> " +"könyvtárban, miután a gép a telepített rendszert elindította." #. Tag: title -#: boot-installer.xml:3334 +#: boot-installer.xml:3495 #, no-c-format msgid "Submitting Installation Reports" msgstr "Telepítő jelentések küldése" #. Tag: para -#: boot-installer.xml:3335 +#: boot-installer.xml:3496 #, no-c-format -msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations." -msgstr "Ha még mindig gondjaid vannak, kérjük, küldj telepítő jelentést. Siker esetén és kérünk erre, mert így a lehető legtöbb adatot kapjuk a legtöbb hardver összeállításról." +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 "" +"Ha még mindig gondjaid vannak, kérjük, küldj telepítő jelentést. Siker " +"esetén és kérünk erre, mert így a lehető legtöbb adatot kapjuk a legtöbb " +"hardver összeállításról." #. Tag: para -#: boot-installer.xml:3342 +#: boot-installer.xml:3503 #, no-c-format -msgid "If you have a working Debian system, the easiest way to send an installation report is to install the installation-report and reportbug packages (<command>apt-get install installation-report reportbug</command>) and run the command <command>reportbug installation-report</command>." -msgstr "Működő Debian rendszerből a telepítő jelentés küldésének legkönnyebb módja az installation-report és reportbug csomag telepítése (<command>apt-get install installation-report reportbug</command>) és a <command>reportbug installation-report</command> parancs futtatása." +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 "" +"Működő Debian rendszerből a telepítő jelentés küldésének legkönnyebb módja " +"az installation-report és reportbug csomag telepítése (<command>apt-get " +"install installation-report reportbug</command>) és a <command>reportbug " +"installation-report</command> parancs futtatása." #. Tag: para -#: boot-installer.xml:3349 -#, no-c-format +#: boot-installer.xml:3510 +#, fuzzy, 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" -"Image version: <Fill in date and from where you got the image>\n" +"Image version: <Full URL to image you downloaded is best>\n" "Date: <Date and time of the install>\n" "\n" "Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" @@ -2453,31 +3953,38 @@ msgid "" "Memory:\n" "Partitions: <df -Tl will do; the raw partition table is preferred>\n" "\n" -"Output of lspci and lspci -n:\n" +"Output of lspci -nn and lspci -vnn:\n" "\n" "Base System Installation Checklist:\n" "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" "\n" -"Initial boot worked: [ ]\n" -"Configure network HW: [ ]\n" -"Config network: [ ]\n" +"Initial boot: [ ]\n" +"Detect network card: [ ]\n" +"Configure network: [ ]\n" "Detect CD: [ ]\n" "Load installer modules: [ ]\n" "Detect hard drives: [ ]\n" "Partition hard drives: [ ]\n" -"Create file systems: [ ]\n" -"Mount partitions: [ ]\n" "Install base system: [ ]\n" +"Clock/timezone setup: [ ]\n" +"User/password setup: [ ]\n" +"Install tasks: [ ]\n" "Install boot loader: [ ]\n" -"Reboot: [ ]\n" +"Overall install: [ ]\n" "\n" "Comments/Problems:\n" "\n" "<Description of the install, in prose, and any thoughts, comments\n" " and ideas you had during the initial install.>\n" -"</screen></informalexample> In the bug report, describe what the problem is, including the last visible kernel messages in the event of a kernel hang. Describe the steps that you did which brought the system into the problem state." -msgstr "" -"Használd e sablont a telepítő jelentés kitöltésére, és küldd a jelentést hibajegyként a <classname>installation-reports</classname> ál- csomagra a <email>submit@bugs.debian.org</email> címre küldve angolul. <informalexample><screen>\n" +"</screen></informalexample> In the bug report, describe what the problem is, " +"including the last visible kernel messages in the event of a kernel hang. " +"Describe the steps that you did which brought the system into the problem " +"state." +msgstr "" +"Használd e sablont a telepítő jelentés kitöltésére, és küldd a jelentést " +"hibajegyként a <classname>installation-reports</classname> ál- csomagra a " +"<email>submit@bugs.debian.org</email> címre küldve angolul. " +"<informalexample><screen>\n" "Package: installation-reports\n" "\n" "Boot method: <Mi volt az indító médium? CD? flopi? hálózat?>\n" @@ -2511,5 +4018,6 @@ msgstr "" "\n" "<Telepítés leírása prózaian és bármilyen gondolat, mejegyzés\n" " és ötlet a kezdeti telepítés során.>\n" -"</screen></informalexample> A jelentésben írd le az esetleges hibát, ha a kernel leállna, annak utolsó látható üzeneteit is. Írd le, mely lépések okozták a gondot." - +"</screen></informalexample> A jelentésben írd le az esetleges hibát, ha a " +"kernel leállna, annak utolsó látható üzeneteit is. Írd le, mely lépések " +"okozták a gondot." diff --git a/po/hu/installation-howto.po b/po/hu/installation-howto.po index 034d5dfc0..02739689a 100644 --- a/po/hu/installation-howto.po +++ b/po/hu/installation-howto.po @@ -5,7 +5,7 @@ msgid "" msgstr "" "Project-Id-Version: Debian Installer Manual Installation HOWTO\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-10-19 11:21+0000\n" +"POT-Creation-Date: 2006-10-29 14:49+0000\n" "PO-Revision-Date: 2006-10-19 17:30+0100\n" "Last-Translator: SZERVÁC Attila <sas@321.hu>\n" "Language-Team: Hungarian <debian-l10n-hungarian@lists.debian.org>\n" @@ -25,8 +25,20 @@ msgstr "Telepítő Hogyan" #. Tag: para #: installation-howto.xml:7 #, no-c-format -msgid "This document describes how to install &debian; &releasename; for the &arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a quick walkthrough of the installation process which should contain all the information you will need for most installs. When more information can be useful, we will link to more detailed explanations in the <link linkend=\"debian_installation_guide\">&debian; Installation Guide</link>." -msgstr "E dokumentum leírja a &debian; &releasename; telepítését &arch-title; (<quote>&architecture;</quote>) gépre az új &d-i; eszköz használatával. Ez a telepítés lépéseinek gyors áttekintése, mely tartalmazza a legtöbb telepítéshez szükséges összes adatot. Ahol további részletesebb adatok lehetnek, hivatkozunk a <link linkend=\"debian_installation_guide\">&debian; Telepítő Útmutató</link> részletesebb leírására." +msgid "" +"This document describes how to install &debian; &releasename; for the &arch-" +"title; (<quote>&architecture;</quote>) with the new &d-i;. It is a quick " +"walkthrough of the installation process which should contain all the " +"information you will need for most installs. When more information can be " +"useful, we will link to more detailed explanations in the <link linkend=" +"\"debian_installation_guide\">&debian; Installation Guide</link>." +msgstr "" +"E dokumentum leírja a &debian; &releasename; telepítését &arch-title; " +"(<quote>&architecture;</quote>) gépre az új &d-i; eszköz használatával. Ez a " +"telepítés lépéseinek gyors áttekintése, mely tartalmazza a legtöbb " +"telepítéshez szükséges összes adatot. Ahol további részletesebb adatok " +"lehetnek, hivatkozunk a <link linkend=\"debian_installation_guide\">&debian; " +"Telepítő Útmutató</link> részletesebb leírására." #. Tag: title #: installation-howto.xml:20 @@ -37,8 +49,19 @@ msgstr "Elöljáróban" #. Tag: para #: installation-howto.xml:21 #, no-c-format -msgid "<phrase condition=\"unofficial-build\"> The debian-installer is still in a beta state. </phrase> If you encounter bugs during your install, please refer to <xref linkend=\"submit-bug\"/> for instructions on how to report them. If you have questions which cannot be answered by this document, please direct them to the debian-boot mailing list (&email-debian-boot-list;) or ask on IRC (#debian-boot on the OFTC network)." -msgstr "<phrase condition=\"unofficial-build\"> Ez még mindig a debian-installer béta állapota. </phrase> Ha hibát találsz, nézd meg az alábbi: <xref linkend=\"submit-bug\"/> részt a jelentés módjáról. Ha e dokumentum nem válaszol egy kérdésedre, fordulj a debian-boot listához (&email-debian-boot-list;) vagy tedd fel IRC-n (#debian-boot az OFTC hálózaton)." +msgid "" +"<phrase condition=\"unofficial-build\"> The debian-installer is still in a " +"beta state. </phrase> If you encounter bugs during your install, please " +"refer to <xref linkend=\"submit-bug\"/> for instructions on how to report " +"them. If you have questions which cannot be answered by this document, " +"please direct them to the debian-boot mailing list (&email-debian-boot-" +"list;) or ask on IRC (#debian-boot on the OFTC network)." +msgstr "" +"<phrase condition=\"unofficial-build\"> Ez még mindig a debian-installer " +"béta állapota. </phrase> Ha hibát találsz, nézd meg az alábbi: <xref linkend=" +"\"submit-bug\"/> részt a jelentés módjáról. Ha e dokumentum nem válaszol egy " +"kérdésedre, fordulj a debian-boot listához (&email-debian-boot-list;) vagy " +"tedd fel IRC-n (#debian-boot az OFTC hálózaton)." #. Tag: title #: installation-howto.xml:37 @@ -49,20 +72,42 @@ msgstr "A telepítő indítása" #. Tag: para #: installation-howto.xml:38 #, no-c-format -msgid "<phrase condition=\"unofficial-build\"> For some quick links to CD images, check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </phrase> The debian-cd team provides builds of CD images using &d-i; on the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink>. For more information on where to get CDs, see <xref linkend=\"official-cdrom\"/>." -msgstr "<phrase condition=\"unofficial-build\"> Gyors CD-kép elérésekhez, lásd a <ulink url=\"&url-d-i;\"> &d-i; honlapot</ulink>. </phrase> A debian-cd csapat biztosít &d-i; programot adó CD-képeket a <ulink url=\"&url-debian-cd;\">Debian CD oldalon</ulink>. További adatok a CD-képek letöltéséről: <xref linkend=\"official-cdrom\"/>." +msgid "" +"<phrase condition=\"unofficial-build\"> For some quick links to CD images, " +"check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </phrase> " +"The debian-cd team provides builds of CD images using &d-i; on the <ulink " +"url=\"&url-debian-cd;\">Debian CD page</ulink>. For more information on " +"where to get CDs, see <xref linkend=\"official-cdrom\"/>." +msgstr "" +"<phrase condition=\"unofficial-build\"> Gyors CD-kép elérésekhez, lásd a " +"<ulink url=\"&url-d-i;\"> &d-i; honlapot</ulink>. </phrase> A debian-cd " +"csapat biztosít &d-i; programot adó CD-képeket a <ulink url=\"&url-debian-cd;" +"\">Debian CD oldalon</ulink>. További adatok a CD-képek letöltéséről: <xref " +"linkend=\"official-cdrom\"/>." #. Tag: para #: installation-howto.xml:48 #, no-c-format -msgid "Some installation methods require other images than CD images. <phrase condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; home page</ulink> has links to other images. </phrase> <xref linkend=\"where-files\"/> explains how to find images on Debian mirrors." -msgstr "Egyes telepítő módok a CD-képektől eltérő képeket kívánnak. <phrase condition=\"unofficial-build\"> A <ulink url=\"&url-d-i;\">&d-i; honlap</ulink> hivatkozásokat ad ezekre. A </phrase> <xref linkend=\"where-files\"/> leírás szól a képek eléréséről a Debian tükrökön." +msgid "" +"Some installation methods require other images than CD images. <phrase " +"condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; home " +"page</ulink> has links to other images. </phrase> <xref linkend=\"where-files" +"\"/> explains how to find images on Debian mirrors." +msgstr "" +"Egyes telepítő módok a CD-képektől eltérő képeket kívánnak. <phrase " +"condition=\"unofficial-build\"> A <ulink url=\"&url-d-i;\">&d-i; honlap</" +"ulink> hivatkozásokat ad ezekre. A </phrase> <xref linkend=\"where-files\"/> " +"leírás szól a képek eléréséről a Debian tükrökön." #. Tag: para #: installation-howto.xml:58 #, no-c-format -msgid "The subsections below will give the details about which images you should get for each possible means of installation." -msgstr "Az alábbi alfejezetek leírják, mely képek kellenek az egyes telepítő módokhoz." +msgid "" +"The subsections below will give the details about which images you should " +"get for each possible means of installation." +msgstr "" +"Az alábbi alfejezetek leírják, mely képek kellenek az egyes telepítő " +"módokhoz." #. Tag: title #: installation-howto.xml:66 @@ -73,14 +118,42 @@ msgstr "CDROM" #. Tag: para #: installation-howto.xml:68 #, no-c-format -msgid "There are two different netinst CD images which can be used to install &releasename; with the &d-i;. These images are intended to boot from CD and install additional packages over a network, hence the name 'netinst'. The difference between the two images is that on the full netinst image the base packages are included, whereas you have to download these from the web if you are using the business card image. If you'd rather, you can get a full size CD image which will not need the network to install. You only need the first CD of the set." -msgstr "2 hálózati telepítő CD-kép van, mely a &releasename; telepítésére használható a &d-i; eszközzel. E képek célja a CD-ről való indítás és további csomagok telepítése hálózatról, ezért neve: 'netinst'. A teljes netinst kép tartalmazza az alap csomagokat az úgynevezett 'business card' kép esetében ezeket is a hálózatról kell letölteni. Teljes CD-kép is letölthető, ekkor az alaptelepítéshez nem lesz szükséged hálózatra. A CD készlet első CD-képe elég lehet, de jellemzően a 2.-4. CD-képen még vannak magyar kiegészítők." +msgid "" +"There are two different netinst CD images which can be used to install " +"&releasename; with the &d-i;. These images are intended to boot from CD and " +"install additional packages over a network, hence the name 'netinst'. The " +"difference between the two images is that on the full netinst image the base " +"packages are included, whereas you have to download these from the web if " +"you are using the business card image. If you'd rather, you can get a full " +"size CD image which will not need the network to install. You only need the " +"first CD of the set." +msgstr "" +"2 hálózati telepítő CD-kép van, mely a &releasename; telepítésére " +"használható a &d-i; eszközzel. E képek célja a CD-ről való indítás és " +"további csomagok telepítése hálózatról, ezért neve: 'netinst'. A teljes " +"netinst kép tartalmazza az alap csomagokat az úgynevezett 'business card' " +"kép esetében ezeket is a hálózatról kell letölteni. Teljes CD-kép is " +"letölthető, ekkor az alaptelepítéshez nem lesz szükséged hálózatra. A CD " +"készlet első CD-képe elég lehet, de jellemzően a 2.-4. CD-képen még vannak " +"magyar kiegészítők." #. Tag: para #: installation-howto.xml:79 #, no-c-format -msgid "Download whichever type you prefer and burn it to a CD. <phrase arch=\"x86\">To boot the CD, you may need to change your BIOS configuration, as explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </phrase>" -msgstr "Töltsd le a választott típust és írd ki egy CD lemezre. <phrase arch=\"x86\">A CD indításához, a BIOS beállításaid meg kell feleljenek a <xref linkend=\"bios-setup\"/> részben leírtaknak.</phrase> <phrase arch=\"powerpc\"> Egy PowerMac CD-képről indításához, nyomd le a <keycap>c</keycap> billentyűt indításkor. Lásd a <xref linkend=\"boot-cd\"/> részt a CD-kép indítás módjairól. </phrase>" +msgid "" +"Download whichever type you prefer and burn it to a CD. <phrase arch=\"x86" +"\">To boot the CD, you may need to change your BIOS configuration, as " +"explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc" +"\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while " +"booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </" +"phrase>" +msgstr "" +"Töltsd le a választott típust és írd ki egy CD lemezre. <phrase arch=\"x86" +"\">A CD indításához, a BIOS beállításaid meg kell feleljenek a <xref linkend=" +"\"bios-setup\"/> részben leírtaknak.</phrase> <phrase arch=\"powerpc\"> Egy " +"PowerMac CD-képről indításához, nyomd le a <keycap>c</keycap> billentyűt " +"indításkor. Lásd a <xref linkend=\"boot-cd\"/> részt a CD-kép indítás " +"módjairól. </phrase>" #. Tag: title #: installation-howto.xml:93 @@ -91,32 +164,71 @@ msgstr "Floppi" #. Tag: para #: installation-howto.xml:94 #, no-c-format -msgid "If you can't boot from CD, you can download floppy images to install Debian. You need the <filename>floppy/boot.img</filename>, the <filename>floppy/root.img</filename> and one or more of the driver disks." -msgstr "Ha nem tudsz CD lemezről indítani, akár flopiról is telepítheted a Debian rendszert. Szükség lesz majd a <filename>floppy/boot.img</filename> és <filename>floppy/root.img</filename> fájlra és legalább egy meghajtó lemezre. " +msgid "" +"If you can't boot from CD, you can download floppy images to install Debian. " +"You need the <filename>floppy/boot.img</filename>, the <filename>floppy/root." +"img</filename> and one or more of the driver disks." +msgstr "" +"Ha nem tudsz CD lemezről indítani, akár flopiról is telepítheted a Debian " +"rendszert. Szükség lesz majd a <filename>floppy/boot.img</filename> és " +"<filename>floppy/root.img</filename> fájlra és legalább egy meghajtó " +"lemezre. " #. Tag: para #: installation-howto.xml:100 #, no-c-format -msgid "The boot floppy is the one with <filename>boot.img</filename> on it. This floppy, when booted, will prompt you to insert a second floppy — use the one with <filename>root.img</filename> on it." -msgstr "Az indító floppi a <filename>boot.img</filename> nevű. E floppi indítása után kérni fogja a 2. lemezt — itt használd majd a <filename>root.img</filename> nevűt." +msgid "" +"The boot floppy is the one with <filename>boot.img</filename> on it. This " +"floppy, when booted, will prompt you to insert a second floppy — use " +"the one with <filename>root.img</filename> on it." +msgstr "" +"Az indító floppi a <filename>boot.img</filename> nevű. E floppi indítása " +"után kérni fogja a 2. lemezt — itt használd majd a <filename>root.img</" +"filename> nevűt." #. Tag: para #: installation-howto.xml:106 #, no-c-format -msgid "If you're planning to install over the network, you will usually need the <filename>floppy/net-drivers-1.img</filename>. For PCMCIA or USB networking, and some less common network cards, you will also need a second driver floppy, <filename>floppy/net-drivers-2.img</filename>." -msgstr "Ha hálózati telepítést tervezel, általában a <filename>floppy/net-drivers-1.img</filename> fájl is kell majd. A PCMCIA vagy USB hálózathoz és pár kevésbé általános hálózati kártyához pedig a <filename>floppy/net-drivers-2.img</filename>." +msgid "" +"If you're planning to install over the network, you will usually need the " +"<filename>floppy/net-drivers-1.img</filename>. For PCMCIA or USB networking, " +"and some less common network cards, you will also need a second driver " +"floppy, <filename>floppy/net-drivers-2.img</filename>." +msgstr "" +"Ha hálózati telepítést tervezel, általában a <filename>floppy/net-drivers-1." +"img</filename> fájl is kell majd. A PCMCIA vagy USB hálózathoz és pár " +"kevésbé általános hálózati kártyához pedig a <filename>floppy/net-drivers-2." +"img</filename>." #. Tag: para #: installation-howto.xml:113 #, no-c-format -msgid "If you have a CD, but cannot boot from it, then boot from floppies and use <filename>floppy/cd-drivers.img</filename> on a driver disk to complete the install using the CD." -msgstr "Ha van egy jól megírt CD-lemezed és a CD-eszközöd is jó, de nem tudsz róla indítani, mert különleges programot igényel, akkor indíts a floppikról és használd a <filename>floppy/cd-drivers.img</filename> floppit, hogy onnan már a CD-lemezről telepíthess." +msgid "" +"If you have a CD, but cannot boot from it, then boot from floppies and use " +"<filename>floppy/cd-drivers.img</filename> on a driver disk to complete the " +"install using the CD." +msgstr "" +"Ha van egy jól megírt CD-lemezed és a CD-eszközöd is jó, de nem tudsz róla " +"indítani, mert különleges programot igényel, akkor indíts a floppikról és " +"használd a <filename>floppy/cd-drivers.img</filename> floppit, hogy onnan " +"már a CD-lemezről telepíthess." #. Tag: para #: installation-howto.xml:119 #, no-c-format -msgid "Floppy disks are one of the least reliable media around, so be prepared for lots of bad disks (see <xref linkend=\"unreliable-floppies\"/>). Each <filename>.img</filename> file you downloaded goes on a single floppy; you can use the dd command to write it to /dev/fd0 or some other means (see <xref linkend=\"create-floppy\"/> for details). Since you'll have more than one floppy, it's a good idea to label them." -msgstr "A floppi lemezek a legmegbízhatatlanabb médiumok közé tartoznak, készül fel sok rossz flopira (lásd a <xref linkend=\"unreliable-floppies\"/>) részt. Minden <filename>.img</filename> fájlt külön floppira kell írnod; használatod dd parancsot a /dev/fd0 eszközre íráshoz vagy más módot (lásd a <xref linkend=\"create-floppy\"/> részt a részletekért)." +msgid "" +"Floppy disks are one of the least reliable media around, so be prepared for " +"lots of bad disks (see <xref linkend=\"unreliable-floppies\"/>). Each " +"<filename>.img</filename> file you downloaded goes on a single floppy; you " +"can use the dd command to write it to /dev/fd0 or some other means (see " +"<xref linkend=\"create-floppy\"/> for details). Since you'll have more than " +"one floppy, it's a good idea to label them." +msgstr "" +"A floppi lemezek a legmegbízhatatlanabb médiumok közé tartoznak, készül fel " +"sok rossz flopira (lásd a <xref linkend=\"unreliable-floppies\"/>) részt. " +"Minden <filename>.img</filename> fájlt külön floppira kell írnod; " +"használatod dd parancsot a /dev/fd0 eszközre íráshoz vagy más módot (lásd a " +"<xref linkend=\"create-floppy\"/> részt a részletekért)." #. Tag: title #: installation-howto.xml:132 @@ -127,32 +239,71 @@ msgstr "USB memória meghajtó" #. Tag: para #: installation-howto.xml:133 #, no-c-format -msgid "It's also possible to install from removable USB storage devices. For example a USB keychain can make a handy Debian install medium that you can take with you anywhere." -msgstr "USB tároló eszközökről is telepíthetsz. Például egy USB kulcstartó egy igen barátságos Debian telepítő médium lehet, ami mindig könnyen veled lehet." +msgid "" +"It's also possible to install from removable USB storage devices. For " +"example a USB keychain can make a handy Debian install medium that you can " +"take with you anywhere." +msgstr "" +"USB tároló eszközökről is telepíthetsz. Például egy USB kulcstartó egy igen " +"barátságos Debian telepítő médium lehet, ami mindig könnyen veled lehet." #. Tag: para #: installation-howto.xml:139 #, no-c-format -msgid "The easiest way to prepare your USB memory stick is to download <filename>hd-media/boot.img.gz</filename>, and use gunzip to extract the 256 MB image from that file. Write this image directly to your memory stick, which must be at least 256 mb in size. Of course this will destroy anything already on the memory stick. Then mount the memory stick, which will now have a FAT filesystem on it. Next, download a Debian netinst CD image, and copy that file to the memory stick; any filename is ok as long as it ends in <literal>.iso</literal>." -msgstr "Az USB memória meghajtó felkészítésének legjobb módja, ha letöltöd a <filename>hd-media/boot.img.gz</filename> fájlt, és a gunzip programmal kibontod belőle a 256 MB méretű képet. Írd ki a képet a meghajtón lévő partícióra, mely legalább 256 MB kell legyen. Csatold fel a partíciót, amely FAT fájlrendszert tartalmazzon. Töltsd le a netinst CD képet és másold e fájlt a csatolt partícióra; bármilyen fájlnév megfelel, csak legyen a vége <literal>.iso</literal>." +msgid "" +"The easiest way to prepare your USB memory stick is to download <filename>hd-" +"media/boot.img.gz</filename>, and use gunzip to extract the 256 MB image " +"from that file. Write this image directly to your memory stick, which must " +"be at least 256 mb in size. Of course this will destroy anything already on " +"the memory stick. Then mount the memory stick, which will now have a FAT " +"filesystem on it. Next, download a Debian netinst CD image, and copy that " +"file to the memory stick; any filename is ok as long as it ends in <literal>." +"iso</literal>." +msgstr "" +"Az USB memória meghajtó felkészítésének legjobb módja, ha letöltöd a " +"<filename>hd-media/boot.img.gz</filename> fájlt, és a gunzip programmal " +"kibontod belőle a 256 MB méretű képet. Írd ki a képet a meghajtón lévő " +"partícióra, mely legalább 256 MB kell legyen. Csatold fel a partíciót, amely " +"FAT fájlrendszert tartalmazzon. Töltsd le a netinst CD képet és másold e " +"fájlt a csatolt partícióra; bármilyen fájlnév megfelel, csak legyen a vége " +"<literal>.iso</literal>." #. Tag: para #: installation-howto.xml:150 #, no-c-format -msgid "There are other, more flexible ways to set up a memory stick to use the debian-installer, and it's possible to get it to work with smaller memory sticks. For details, see <xref linkend=\"boot-usb-files\"/>." -msgstr "Más, rugalmasabb módok is vannak egy ilyen memória meghajtó beállításához a Debian Telepítőhöz, és kisebb eszközökkel is működhet. A részletekért lásd a <xref linkend=\"boot-usb-files\"/> részt." +msgid "" +"There are other, more flexible ways to set up a memory stick to use the " +"debian-installer, and it's possible to get it to work with smaller memory " +"sticks. For details, see <xref linkend=\"boot-usb-files\"/>." +msgstr "" +"Más, rugalmasabb módok is vannak egy ilyen memória meghajtó beállításához a " +"Debian Telepítőhöz, és kisebb eszközökkel is működhet. A részletekért lásd a " +"<xref linkend=\"boot-usb-files\"/> részt." #. Tag: para #: installation-howto.xml:156 #, no-c-format -msgid "Some BIOSes can boot USB storage directly, and some cannot. You may need to configure your BIOS to boot from a <quote>removable drive</quote> or even a <quote>USB-ZIP</quote> to get it to boot from the USB device. For helpful hints and details, see <xref linkend=\"usb-boot\"/>." -msgstr "Néhány BIOS tud közvetlenül USB tárolóról indulni, mások nem. Próbáld ki a lehetőségeket, jó lehet a <quote>removable drive</quote>, de akár még a <quote>USB-ZIP</quote> beállítás is. Ennek leírását lásd a <xref linkend=\"usb-boot\"/> részben." +msgid "" +"Some BIOSes can boot USB storage directly, and some cannot. You may need to " +"configure your BIOS to boot from a <quote>removable drive</quote> or even a " +"<quote>USB-ZIP</quote> to get it to boot from the USB device. For helpful " +"hints and details, see <xref linkend=\"usb-boot\"/>." +msgstr "" +"Néhány BIOS tud közvetlenül USB tárolóról indulni, mások nem. Próbáld ki a " +"lehetőségeket, jó lehet a <quote>removable drive</quote>, de akár még a " +"<quote>USB-ZIP</quote> beállítás is. Ennek leírását lásd a <xref linkend=" +"\"usb-boot\"/> részben." #. Tag: para #: installation-howto.xml:163 #, no-c-format -msgid "Booting Macintosh systems from USB storage devices involves manual use of Open Firmware. For directions, see <xref linkend=\"usb-boot\"/>." -msgstr "Macintoshként ismert rendszerek USB tároló eszközökről indítása az Open Firmware kézi használatát igényli. Ennek leírását is megtalálod a <xref linkend=\"usb-boot\"/> részben." +msgid "" +"Booting Macintosh systems from USB storage devices involves manual use of " +"Open Firmware. For directions, see <xref linkend=\"usb-boot\"/>." +msgstr "" +"Macintoshként ismert rendszerek USB tároló eszközökről indítása az Open " +"Firmware kézi használatát igényli. Ennek leírását is megtalálod a <xref " +"linkend=\"usb-boot\"/> részben." #. Tag: title #: installation-howto.xml:172 @@ -163,14 +314,33 @@ msgstr "Indítás hálózatról" #. Tag: para #: installation-howto.xml:173 #, no-c-format -msgid "It's also possible to boot &d-i; completely from the net. The various methods to netboot depend on your architecture and netboot setup. The files in <filename>netboot/</filename> can be used to netboot &d-i;." -msgstr "A &d-i; indítása teljesen hálózatról is végezhető. A hálózati indítás módjai mind a gép és a hálózati indítás beállításaitól függenek. A <filename>netboot/</filename> könyvtárban lévő fájlok használhatók a &d-i; hálózati indításához." +msgid "" +"It's also possible to boot &d-i; completely from the net. The various " +"methods to netboot depend on your architecture and netboot setup. The files " +"in <filename>netboot/</filename> can be used to netboot &d-i;." +msgstr "" +"A &d-i; indítása teljesen hálózatról is végezhető. A hálózati indítás módjai " +"mind a gép és a hálózati indítás beállításaitól függenek. A " +"<filename>netboot/</filename> könyvtárban lévő fájlok használhatók a &d-i; " +"hálózati indításához." #. Tag: para #: installation-howto.xml:179 #, no-c-format -msgid "The easiest thing to set up is probably PXE netbooting. Untar the file <filename>netboot/pxeboot.tar.gz</filename> into <filename>/var/lib/tftpboot</filename> or wherever is appropriate for your tftp server. Set up your DHCP server to pass filename <filename>/pxelinux.0</filename> to clients, and with luck everything will just work. For detailed instructions, see <xref linkend=\"install-tftp\"/>." -msgstr "E hálózati indítás beállításának egyik legkönnyebb módja a PXE. Bontsd ki a <filename>netboot/pxeboot.tar.gz</filename> fájlt a <filename>/var/lib/tftpboot</filename>-ba, vagy ahol tftp-t tartod. Mondd meg a DHCP kiszolgálónak, hogy az ügyfeleknek a <filename>/pxelinux.0</filename> fájlt adja, és ha minden ok, minden menni fog. Bővebben a <xref linkend=\"install-tftp\"/> részben." +msgid "" +"The easiest thing to set up is probably PXE netbooting. Untar the file " +"<filename>netboot/pxeboot.tar.gz</filename> into <filename>/var/lib/" +"tftpboot</filename> or wherever is appropriate for your tftp server. Set up " +"your DHCP server to pass filename <filename>/pxelinux.0</filename> to " +"clients, and with luck everything will just work. For detailed instructions, " +"see <xref linkend=\"install-tftp\"/>." +msgstr "" +"E hálózati indítás beállításának egyik legkönnyebb módja a PXE. Bontsd ki a " +"<filename>netboot/pxeboot.tar.gz</filename> fájlt a <filename>/var/lib/" +"tftpboot</filename>-ba, vagy ahol tftp-t tartod. Mondd meg a DHCP " +"kiszolgálónak, hogy az ügyfeleknek a <filename>/pxelinux.0</filename> fájlt " +"adja, és ha minden ok, minden menni fog. Bővebben a <xref linkend=\"install-" +"tftp\"/> részben." #. Tag: title #: installation-howto.xml:193 @@ -181,8 +351,21 @@ msgstr "Indítás merevlemezről" #. Tag: para #: installation-howto.xml:194 #, no-c-format -msgid "It's possible to boot the installer using no removable media, but just an existing hard disk, which can have a different OS on it. Download <filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</filename>, and a Debian CD image to the top-level directory of the hard disk. Make sure that the CD image has a filename ending in <literal>.iso</literal>. Now it's just a matter of booting linux with the initrd. <phrase arch=\"x86\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </phrase>" -msgstr "Létező merevlemezről is indítható a telepítő, melyen most más OS van. Töltsd le a <filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</filename> és egy Debian CD kép fájlt a gyökérbe. A CD kép nevének vége legyen <literal>.iso</literal>. Ez az initrd indítás. Az <phrase arch=\"x86\"> <xref linkend=\"boot-initrd\"/> leírja a módot. </phrase>" +msgid "" +"It's possible to boot the installer using no removable media, but just an " +"existing hard disk, which can have a different OS on it. Download " +"<filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</" +"filename>, and a Debian CD image to the top-level directory of the hard " +"disk. Make sure that the CD image has a filename ending in <literal>.iso</" +"literal>. Now it's just a matter of booting linux with the initrd. <phrase " +"arch=\"x86\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </" +"phrase>" +msgstr "" +"Létező merevlemezről is indítható a telepítő, melyen most más OS van. Töltsd " +"le a <filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</" +"filename> és egy Debian CD kép fájlt a gyökérbe. A CD kép nevének vége " +"legyen <literal>.iso</literal>. Ez az initrd indítás. Az <phrase arch=\"x86" +"\"> <xref linkend=\"boot-initrd\"/> leírja a módot. </phrase>" #. Tag: title #: installation-howto.xml:211 @@ -192,103 +375,226 @@ msgstr "Telepítés" #. Tag: para #: installation-howto.xml:212 -#, no-c-format -msgid "Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend=\"boot-parms\"/>). <phrase arch=\"i386\"> If you want a 2.4 kernel, type <userinput>install24</userinput> at the <prompt>boot:</prompt> prompt. The 2.6 kernel is the default. </phrase>" -msgstr "A telepítő indítása után egy üdvözlő képernyő fogad. Üsd le az &enterkey; billentyűt az indításhoz vagy olvasd el a lehetőségeket más indítási módokhoz és paraméterekhez (lásd: <xref linkend=\"boot-parms\"/>). <phrase arch=\"i386\"> 2.4-es indításhoz, üsd be az <userinput>install24</userinput> szót a <prompt>boot:</prompt> beviteli sorban. A 2.6 verziójú Linux az alapértelmezett. </phrase>" +#, fuzzy, no-c-format +msgid "" +"Once the installer starts, you will be greeted with an initial screen. Press " +"&enterkey; to boot, or read the instructions for other boot methods and " +"parameters (see <xref linkend=\"boot-parms\"/>)." +msgstr "" +"A telepítő indítása után egy üdvözlő képernyő fogad. Üsd le az &enterkey; " +"billentyűt az indításhoz vagy olvasd el a lehetőségeket más indítási " +"módokhoz és paraméterekhez (lásd: <xref linkend=\"boot-parms\"/>). <phrase " +"arch=\"i386\"> 2.4-es indításhoz, üsd be az <userinput>install24</userinput> " +"szót a <prompt>boot:</prompt> beviteli sorban. A 2.6 verziójú Linux az " +"alapértelmezett. </phrase>" #. Tag: para -#: installation-howto.xml:222 +#: installation-howto.xml:218 #, no-c-format -msgid "After a while you will be asked to select your language. Use the arrow keys to pick a language and press &enterkey; to continue. Next you'll be asked to select your country, with the choices including countries where your language is spoken. If it's not on the short list, a list of all the countries in the world is available." -msgstr "Sikeres indítás esetén egy hosszú, görgethető listát adó nyelv-választó párbeszéd-ablakot kapsz, melyben kiválaszthatod nyelvedet. Használd a fel-le nyíl billentyűket míg saját nyelved lesz kijelölt, és ekkor üsd le az &enterkey; billentyűt a folytatáshoz. Ezután az országodat lehet kiválasztani." +msgid "" +"After a while you will be asked to select your language. Use the arrow keys " +"to pick a language and press &enterkey; to continue. Next you'll be asked to " +"select your country, with the choices including countries where your " +"language is spoken. If it's not on the short list, a list of all the " +"countries in the world is available." +msgstr "" +"Sikeres indítás esetén egy hosszú, görgethető listát adó nyelv-választó " +"párbeszéd-ablakot kapsz, melyben kiválaszthatod nyelvedet. Használd a fel-le " +"nyíl billentyűket míg saját nyelved lesz kijelölt, és ekkor üsd le az " +"&enterkey; billentyűt a folytatáshoz. Ezután az országodat lehet " +"kiválasztani." #. Tag: para -#: installation-howto.xml:230 +#: installation-howto.xml:226 #, no-c-format -msgid "You may be asked to confirm your keyboard layout. Choose the default unless you know better." -msgstr "Ezután a billentyű-kiosztásodat lehet megerősíteni. Szokásos qwertz billentyűnél jó az alap, egyszerűen lépj tovább." +msgid "" +"You may be asked to confirm your keyboard layout. Choose the default unless " +"you know better." +msgstr "" +"Ezután a billentyű-kiosztásodat lehet megerősíteni. Szokásos qwertz " +"billentyűnél jó az alap, egyszerűen lépj tovább." #. Tag: para -#: installation-howto.xml:235 +#: installation-howto.xml:231 #, no-c-format -msgid "Now sit back while debian-installer detects some of your hardware, and loads the rest of itself from CD, floppy, USB, etc." -msgstr "A Debian Telepítő most gyorsan felderíti a legfontosabb eszközeidet, és betölti önmaga hátralévő részét a CD-lemezről, floppiról, vagyis az általad használt eszközről." +msgid "" +"Now sit back while debian-installer detects some of your hardware, and loads " +"the rest of itself from CD, floppy, USB, etc." +msgstr "" +"A Debian Telepítő most gyorsan felderíti a legfontosabb eszközeidet, és " +"betölti önmaga hátralévő részét a CD-lemezről, floppiról, vagyis az általad " +"használt eszközről." #. Tag: para -#: installation-howto.xml:240 +#: installation-howto.xml:236 #, no-c-format -msgid "Next the installer will try to detect your network hardware and set up networking by DHCP. If you are not on a network or do not have DHCP, you will be given the opportunity to configure the network manually." -msgstr "Ezután a telepítő megpróbálja felismerni hálózati eszközödet és beállítani a hálózatot DHCP kiszolgálóval. Ha nem vagy hálózaton, vagy azon nincs DHCP, akkor természetesen lehetőséged nyílik megadnod hálózati adataidat." +msgid "" +"Next the installer will try to detect your network hardware and set up " +"networking by DHCP. If you are not on a network or do not have DHCP, you " +"will be given the opportunity to configure the network manually." +msgstr "" +"Ezután a telepítő megpróbálja felismerni hálózati eszközödet és beállítani a " +"hálózatot DHCP kiszolgálóval. Ha nem vagy hálózaton, vagy azon nincs DHCP, " +"akkor természetesen lehetőséged nyílik megadnod hálózati adataidat." #. Tag: para -#: installation-howto.xml:246 +#: installation-howto.xml:242 #, no-c-format -msgid "Now it is time to partition your disks. First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive (guided partitioning). This is recommended for new users or anyone in a hurry. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu." -msgstr "Most kell a lemezek particionálásáról dönteni. Adott a lehetőség, hogy a telepítő ezt elvégezze automatikusan akár az egész lemezen, akár bármely lemez szabad részén (irányított particionálás). Ez ajánlott az új felhasználóknak vagy bárkinek, akinek kapkodni kell. Ha nem akarsz automata particionálást, a <guimenuitem>Kézi</guimenuitem> beállítást válaszd." +msgid "" +"Now it is time to partition your disks. First you will be given the " +"opportunity to automatically partition either an entire drive, or available " +"free space on a drive (guided partitioning). This is recommended for new " +"users or anyone in a hurry. If you do not want to autopartition, choose " +"<guimenuitem>Manual</guimenuitem> from the menu." +msgstr "" +"Most kell a lemezek particionálásáról dönteni. Adott a lehetőség, hogy a " +"telepítő ezt elvégezze automatikusan akár az egész lemezen, akár bármely " +"lemez szabad részén (irányított particionálás). Ez ajánlott az új " +"felhasználóknak vagy bárkinek, akinek kapkodni kell. Ha nem akarsz automata " +"particionálást, a <guimenuitem>Kézi</guimenuitem> beállítást válaszd." #. Tag: para -#: installation-howto.xml:254 +#: installation-howto.xml:250 #, no-c-format -msgid "If you have an existing DOS or Windows partition that you want to preserve, be very careful with automatic partitioning. If you choose manual partitioning, you can use the installer to resize existing FAT or NTFS partitions to create room for the Debian install: simply select the partition and specify its new size." -msgstr "Ha van egy létező DOS vagy Windows partíciód és valamiért meg akarod tartani, figyelj az automatikus választásnál. Ha a partíciók kézi összeállítását választod és most nincs fenntartott hely a Debian számára, a FAT vagy NTFS partícióidat átméretezheted, hogy létrehozd ezt a helyet: egyszerűen válaszd ki az átméretezendő partíciót és add meg új méretét." +msgid "" +"If you have an existing DOS or Windows partition that you want to preserve, " +"be very careful with automatic partitioning. If you choose manual " +"partitioning, you can use the installer to resize existing FAT or NTFS " +"partitions to create room for the Debian install: simply select the " +"partition and specify its new size." +msgstr "" +"Ha van egy létező DOS vagy Windows partíciód és valamiért meg akarod " +"tartani, figyelj az automatikus választásnál. Ha a partíciók kézi " +"összeállítását választod és most nincs fenntartott hely a Debian számára, a " +"FAT vagy NTFS partícióidat átméretezheted, hogy létrehozd ezt a helyet: " +"egyszerűen válaszd ki az átméretezendő partíciót és add meg új méretét." #. Tag: para -#: installation-howto.xml:261 +#: installation-howto.xml:257 #, no-c-format -msgid "On the next screen you will see your partition table, how the partitions will be formatted, and where they will be mounted. Select a partition to modify or delete it. If you did automatic partitioning, you should just be able to choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to use what it set up. Remember to assign at least one partition for swap space and to mount a partition on <filename>/</filename>. <xref linkend=\"partitioning\"/> has more information about partitioning." -msgstr "A következő képernyőn mutatja, hogy lesznek a partíciók formázva és hova lesznek csatolva. Válassz egy partíciót ha módosítani vagy törölni akarod. Ha a partíciók automatikus beállítását választottad, csak a <guimenuitem>Partícionálás befejezése és változások lemezre írása</guimenuitem> pontra kell térni a menüből a beállítások használatára. Ne felejts legalább 1 partíciót cserehelyként jelölni és egy partíciót megjelölni a <filename>/</filename> könyvtárként csatoláshoz. Aprólékosabb leírást erről <xref linkend=\"partitioning\"/> részben lehet fellelni." +msgid "" +"On the next screen you will see your partition table, how the partitions " +"will be formatted, and where they will be mounted. Select a partition to " +"modify or delete it. If you did automatic partitioning, you should just be " +"able to choose <guimenuitem>Finish partitioning and write changes to disk</" +"guimenuitem> from the menu to use what it set up. Remember to assign at " +"least one partition for swap space and to mount a partition on <filename>/</" +"filename>. <xref linkend=\"partitioning\"/> has more information about " +"partitioning." +msgstr "" +"A következő képernyőn mutatja, hogy lesznek a partíciók formázva és hova " +"lesznek csatolva. Válassz egy partíciót ha módosítani vagy törölni akarod. " +"Ha a partíciók automatikus beállítását választottad, csak a " +"<guimenuitem>Partícionálás befejezése és változások lemezre írása</" +"guimenuitem> pontra kell térni a menüből a beállítások használatára. Ne " +"felejts legalább 1 partíciót cserehelyként jelölni és egy partíciót " +"megjelölni a <filename>/</filename> könyvtárként csatoláshoz. Aprólékosabb " +"leírást erről <xref linkend=\"partitioning\"/> részben lehet fellelni." #. Tag: para -#: installation-howto.xml:271 +#: installation-howto.xml:267 #, no-c-format -msgid "Now &d-i; formats your partitions and starts to install the base system, which can take a while. That is followed by installing a kernel." -msgstr "A &d-i; megformázza a formázásra jelölt új partíciókat és elkezdi az alaprendszer telepítését, mely géptől függően eltarthat egy pár percig. A rendszermagot is e folyamat végén telepíti." +msgid "" +"Now &d-i; formats your partitions and starts to install the base system, " +"which can take a while. That is followed by installing a kernel." +msgstr "" +"A &d-i; megformázza a formázásra jelölt új partíciókat és elkezdi az " +"alaprendszer telepítését, mely géptől függően eltarthat egy pár percig. A " +"rendszermagot is e folyamat végén telepíti." #. Tag: para -#: installation-howto.xml:276 +#: installation-howto.xml:272 #, no-c-format -msgid "The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. <phrase arch=\"x86\">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase>" -msgstr "Utolsó lépésként pedig a boot betöltő telepítését végzi el. Ha a telepítő más rendszert is érzékelt, hozzáadja az indító menühöz és tudatja ezt. <phrase arch=\"x86\">Alapértelmezetten a GRUB betöltő kerül telepítésre, éspedig az 1. merevlemez MBR részébe, mely általában jó választás. E lehetőség felülbírálható és a boot betöltő máshová is telepíthető. </phrase>" +msgid "" +"The last step is to install a boot loader. If the installer detects other " +"operating systems on your computer, it will add them to the boot menu and " +"let you know. <phrase arch=\"x86\">By default GRUB will be installed to the " +"master boot record of the first harddrive, which is generally a good choice. " +"You'll be given the opportunity to override that choice and install it " +"elsewhere. </phrase>" +msgstr "" +"Utolsó lépésként pedig a boot betöltő telepítését végzi el. Ha a telepítő " +"más rendszert is érzékelt, hozzáadja az indító menühöz és tudatja ezt. " +"<phrase arch=\"x86\">Alapértelmezetten a GRUB betöltő kerül telepítésre, " +"éspedig az 1. merevlemez MBR részébe, mely általában jó választás. E " +"lehetőség felülbírálható és a boot betöltő máshová is telepíthető. </phrase>" #. Tag: para -#: installation-howto.xml:286 +#: installation-howto.xml:282 #, no-c-format -msgid "&d-i; will now tell you that the installation has finished. Remove the cdrom or other boot media and hit &enterkey; to reboot your machine. It should boot up into the next stage of the install process, which is explained in <xref linkend=\"boot-new\"/>." -msgstr "A &d-i; most értesít, hogy a telepítés megtörtént. Távolítsd el a CD lemezt vagy a telepítéskor használt indító médiát és üsd le az &enterkey; billentyűt a gép újraindításához. Ez a telepítő folyamat következő lépéhez indítja majd el a rendszert, a most telepített rendszer használatba vételét a <xref linkend=\"boot-new\"/> részben ismertetjük." +msgid "" +"&d-i; will now tell you that the installation has finished. Remove the cdrom " +"or other boot media and hit &enterkey; to reboot your machine. It should " +"boot up into the next stage of the install process, which is explained in " +"<xref linkend=\"boot-new\"/>." +msgstr "" +"A &d-i; most értesít, hogy a telepítés megtörtént. Távolítsd el a CD lemezt " +"vagy a telepítéskor használt indító médiát és üsd le az &enterkey; " +"billentyűt a gép újraindításához. Ez a telepítő folyamat következő lépéhez " +"indítja majd el a rendszert, a most telepített rendszer használatba vételét " +"a <xref linkend=\"boot-new\"/> részben ismertetjük." #. Tag: para -#: installation-howto.xml:293 +#: installation-howto.xml:289 #, no-c-format -msgid "If you need more information on the install process, see <xref linkend=\"d-i-intro\"/>." -msgstr "Ha több adat érdekel a telepítő folyamatról, nézz bele ebbe: <xref linkend=\"d-i-intro\"/>." +msgid "" +"If you need more information on the install process, see <xref linkend=\"d-i-" +"intro\"/>." +msgstr "" +"Ha több adat érdekel a telepítő folyamatról, nézz bele ebbe: <xref linkend=" +"\"d-i-intro\"/>." #. Tag: title -#: installation-howto.xml:302 +#: installation-howto.xml:298 #, no-c-format msgid "Send us an installation report" msgstr "Küldj nekünk telepítési beszámolót" #. Tag: para -#: installation-howto.xml:303 +#: installation-howto.xml:299 #, no-c-format -msgid "If you successfully managed an installation with &d-i;, please take time to provide us with a report. The simplest way to do so is to install the reportbug package (<command>apt-get install reportbug</command>), and run <command>reportbug installation-report</command>." -msgstr "Ha sikerült a telepítés a &d-i; eszközzel, kérjük, szánj rá egy kis időt, hogy ezt jelentsd nekünk. A legegyszerűbb módja ennek a reportbug csomag telepítése (például ezzel a paranccsal: <command>apt-get install reportbug</command>), és e parancs lefuttatása: <command>reportbug installation-report</command>." +msgid "" +"If you successfully managed an installation with &d-i;, please take time to " +"provide us with a report. The simplest way to do so is to install the " +"reportbug package (<command>apt-get install reportbug</command>), and run " +"<command>reportbug installation-report</command>." +msgstr "" +"Ha sikerült a telepítés a &d-i; eszközzel, kérjük, szánj rá egy kis időt, " +"hogy ezt jelentsd nekünk. A legegyszerűbb módja ennek a reportbug csomag " +"telepítése (például ezzel a paranccsal: <command>apt-get install reportbug</" +"command>), és e parancs lefuttatása: <command>reportbug installation-report</" +"command>." #. Tag: para -#: installation-howto.xml:311 +#: installation-howto.xml:307 #, no-c-format -msgid "If you did not complete the install, you probably found a bug in debian-installer. To improve the installer it is necessary that we know about them, so please take the time to report them. You can use an installation report to report problems; if the install completely fails, see <xref linkend=\"problem-report\"/>." -msgstr "Ha a telepítés közben bármikor hiba történt, valószínűleg találtál egy hibát a telepítőben. Hogy a telepítőt folyamatosan egyre jobbá tegyük, tudnunk kell ezekről, ezért kérjük, jelezd e hibát. A fent már ismertetett egyszerű telepítési beszámolóval megteheted ezt; ha a telepítés egyáltalán nem sikerült valamilyen okból, olvasd el most a <xref linkend=\"problem-report\"/> részt." +msgid "" +"If you did not complete the install, you probably found a bug in debian-" +"installer. To improve the installer it is necessary that we know about them, " +"so please take the time to report them. You can use an installation report " +"to report problems; if the install completely fails, see <xref linkend=" +"\"problem-report\"/>." +msgstr "" +"Ha a telepítés közben bármikor hiba történt, valószínűleg találtál egy hibát " +"a telepítőben. Hogy a telepítőt folyamatosan egyre jobbá tegyük, tudnunk " +"kell ezekről, ezért kérjük, jelezd e hibát. A fent már ismertetett egyszerű " +"telepítési beszámolóval megteheted ezt; ha a telepítés egyáltalán nem " +"sikerült valamilyen okból, olvasd el most a <xref linkend=\"problem-report\"/" +"> részt." #. Tag: title -#: installation-howto.xml:323 +#: installation-howto.xml:319 #, no-c-format msgid "And finally.." msgstr "Végül..." #. Tag: para -#: installation-howto.xml:324 +#: installation-howto.xml:320 #, no-c-format -msgid "We hope that your Debian installation is pleasant and that you find Debian useful. You might want to read <xref linkend=\"post-install\"/>." -msgstr "Reméljük, a Debian telepítésed igazán kellemes lett, és használatba véve jónak fogod találni a Debian rendszert. Érdemes elolvasni a <xref linkend=\"post-install\"/> részt." - +msgid "" +"We hope that your Debian installation is pleasant and that you find Debian " +"useful. You might want to read <xref linkend=\"post-install\"/>." +msgstr "" +"Reméljük, a Debian telepítésed igazán kellemes lett, és használatba véve " +"jónak fogod találni a Debian rendszert. Érdemes elolvasni a <xref linkend=" +"\"post-install\"/> részt." diff --git a/po/hu/partitioning.po b/po/hu/partitioning.po index 534b92e78..137a665c1 100644 --- a/po/hu/partitioning.po +++ b/po/hu/partitioning.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-10-26 16:20+0000\n" +"POT-Creation-Date: 2006-10-29 14:49+0000\n" "PO-Revision-Date: 2006-10-27 11:15+0100\n" "Last-Translator: SZERVÁC Attila <sas@321.hu>\n" "Language-Team: Hungarian\n" @@ -27,26 +27,86 @@ msgstr "A Debian partíciók és méretük eldöntése" #. Tag: para #: partitioning.xml:14 #, no-c-format -msgid "At a bare minimum, GNU/Linux needs one partition for itself. You can have a single partition containing the entire operating system, applications, and your personal files. Most people feel that a separate swap partition is also a necessity, although it's not strictly true. <quote>Swap</quote> is scratch space for an operating system, which allows the system to use disk storage as <quote>virtual memory</quote>. By putting swap on a separate partition, Linux can make much more efficient use of it. It is possible to force Linux to use a regular file as swap, but it is not recommended." -msgstr "Mint abszolút minimum, a GNU/Linux számára is legalább 1 partíció szükséges. Ekkor az operációs rendszer egésze, az alkalmazások és a személyes fájlok is egy partíción vannak. A többség szerint feltétlenül kell egy önálló csere (swap) partíció, de ez nem feltétlen igaz. A <quote>swap</quote>, vagyis a cserehely analógiával élve egy firka-hely, ahol a rendszer a lemezt, mint <quote>virtuális memória</quote> használhatja. A swap önálló partícióra helyezésével azt a Linux sokkal hatékonyabban használhatja. Rávehető sima fájl használatára is erre, de nem ajánlott." +msgid "" +"At a bare minimum, GNU/Linux needs one partition for itself. You can have a " +"single partition containing the entire operating system, applications, and " +"your personal files. Most people feel that a separate swap partition is also " +"a necessity, although it's not strictly true. <quote>Swap</quote> is scratch " +"space for an operating system, which allows the system to use disk storage " +"as <quote>virtual memory</quote>. By putting swap on a separate partition, " +"Linux can make much more efficient use of it. It is possible to force Linux " +"to use a regular file as swap, but it is not recommended." +msgstr "" +"Mint abszolút minimum, a GNU/Linux számára is legalább 1 partíció szükséges. " +"Ekkor az operációs rendszer egésze, az alkalmazások és a személyes fájlok is " +"egy partíción vannak. A többség szerint feltétlenül kell egy önálló csere " +"(swap) partíció, de ez nem feltétlen igaz. A <quote>swap</quote>, vagyis a " +"cserehely analógiával élve egy firka-hely, ahol a rendszer a lemezt, mint " +"<quote>virtuális memória</quote> használhatja. A swap önálló partícióra " +"helyezésével azt a Linux sokkal hatékonyabban használhatja. Rávehető sima " +"fájl használatára is erre, de nem ajánlott." #. Tag: para #: partitioning.xml:26 #, no-c-format -msgid "Most people choose to give GNU/Linux more than the minimum number of partitions, however. There are two reasons you might want to break up the file system into a number of smaller partitions. The first is for safety. If something happens to corrupt the file system, generally only one partition is affected. Thus, you only have to replace (from the backups you've been carefully keeping) a portion of your system. At a bare minimum, you should consider creating what is commonly called a <quote>root partition</quote>. This contains the most essential components of the system. If any other partitions get corrupted, you can still boot into GNU/Linux to fix the system. This can save you the trouble of having to reinstall the system from scratch." -msgstr "A legtöbben a GNU/Linuxnak a minimálisnál több partíciót adnak. Több partíció használatára 2 jó ok is van. Ezek közül az első a biztonság. Ha valami fájlrendszer-sérülést okoz, általában csak 1 partíció érintett. Így csak a rendszer egy részét kell visszaállítani (a biztonsági mentésekből, melyeket minden jó felhasználó tart). Egy úgynevezett <quote>gyökér partíció</quote> mindenképpen létrehozásra kerül. Ezen helyezkednek el a rendszer legfontosabb összetevői. Ha más partíció sérül, innen még mindig el tudod indítani a telepített GNU/Linux rendszert és helyreállítani a sérült adatokat. Ez is egy biztosíték arra, hogy a rendszert soha ne kelljen az alapoktól újratelepítened." +msgid "" +"Most people choose to give GNU/Linux more than the minimum number of " +"partitions, however. There are two reasons you might want to break up the " +"file system into a number of smaller partitions. The first is for safety. If " +"something happens to corrupt the file system, generally only one partition " +"is affected. Thus, you only have to replace (from the backups you've been " +"carefully keeping) a portion of your system. At a bare minimum, you should " +"consider creating what is commonly called a <quote>root partition</quote>. " +"This contains the most essential components of the system. If any other " +"partitions get corrupted, you can still boot into GNU/Linux to fix the " +"system. This can save you the trouble of having to reinstall the system from " +"scratch." +msgstr "" +"A legtöbben a GNU/Linuxnak a minimálisnál több partíciót adnak. Több " +"partíció használatára 2 jó ok is van. Ezek közül az első a biztonság. Ha " +"valami fájlrendszer-sérülést okoz, általában csak 1 partíció érintett. Így " +"csak a rendszer egy részét kell visszaállítani (a biztonsági mentésekből, " +"melyeket minden jó felhasználó tart). Egy úgynevezett <quote>gyökér " +"partíció</quote> mindenképpen létrehozásra kerül. Ezen helyezkednek el a " +"rendszer legfontosabb összetevői. Ha más partíció sérül, innen még mindig el " +"tudod indítani a telepített GNU/Linux rendszert és helyreállítani a sérült " +"adatokat. Ez is egy biztosíték arra, hogy a rendszert soha ne kelljen az " +"alapoktól újratelepítened." #. Tag: para #: partitioning.xml:40 #, no-c-format -msgid "The second reason is generally more important in a business setting, but it really depends on your use of the machine. For example, a mail server getting spammed with e-mail can easily fill a partition. If you made <filename>/var/mail</filename> a separate partition on the mail server, most of the system will remain working even if you get spammed." -msgstr "A másik fő ok sűrűbben fordul elő az üzleti életben, de valójában attól függ, mire használod a gépet. Például, ha egy levelező kiszolgálón kívülről is fogadsz leveleket, a levél-szemét könnyen betölthet egy partíciót. Ha a <filename>/var/mail</filename> egy önálló partícióra kerül egy ilyen gépen, a rendszer többi része még ekkor is rendesen működik majd." +msgid "" +"The second reason is generally more important in a business setting, but it " +"really depends on your use of the machine. For example, a mail server " +"getting spammed with e-mail can easily fill a partition. If you made " +"<filename>/var/mail</filename> a separate partition on the mail server, most " +"of the system will remain working even if you get spammed." +msgstr "" +"A másik fő ok sűrűbben fordul elő az üzleti életben, de valójában attól " +"függ, mire használod a gépet. Például, ha egy levelező kiszolgálón kívülről " +"is fogadsz leveleket, a levél-szemét könnyen betölthet egy partíciót. Ha a " +"<filename>/var/mail</filename> egy önálló partícióra kerül egy ilyen gépen, " +"a rendszer többi része még ekkor is rendesen működik majd." #. Tag: para #: partitioning.xml:48 #, no-c-format -msgid "The only real drawback to using more partitions is that it is often difficult to know in advance what your needs will be. If you make a partition too small then you will either have to reinstall the system or you will be constantly moving things around to make room in the undersized partition. On the other hand, if you make the partition too big, you will be wasting space that could be used elsewhere. Disk space is cheap nowadays, but why throw your money away?" -msgstr "Több partíció használatától csak az tarthat vissza, hogy néha nehéz megjósolni, mire lesz szükség. Ha egy partíció egyszer túl kicsi lesz, automatikusan vagy véglegesen át kell rakni tartalmát egy másikra, vagy átméretezni, de néha ilyenkor inkább újratelepít az ember. Ezzel szemben, ha egy partíció túl nagy, esetleg kiesik hely, ami megfelelne másra. A lemezhely olcsó manapság, de miért pazarolnánk?" +msgid "" +"The only real drawback to using more partitions is that it is often " +"difficult to know in advance what your needs will be. If you make a " +"partition too small then you will either have to reinstall the system or you " +"will be constantly moving things around to make room in the undersized " +"partition. On the other hand, if you make the partition too big, you will be " +"wasting space that could be used elsewhere. Disk space is cheap nowadays, " +"but why throw your money away?" +msgstr "" +"Több partíció használatától csak az tarthat vissza, hogy néha nehéz " +"megjósolni, mire lesz szükség. Ha egy partíció egyszer túl kicsi lesz, " +"automatikusan vagy véglegesen át kell rakni tartalmát egy másikra, vagy " +"átméretezni, de néha ilyenkor inkább újratelepít az ember. Ezzel szemben, ha " +"egy partíció túl nagy, esetleg kiesik hely, ami megfelelne másra. A " +"lemezhely olcsó manapság, de miért pazarolnánk?" #. Tag: title #: partitioning.xml:67 @@ -57,8 +117,18 @@ msgstr "A könyvtárfa" #. Tag: para #: partitioning.xml:68 #, no-c-format -msgid "&debian; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> for directory and file naming. This standard allows users and software programs to predict the location of files and directories. The root level directory is represented simply by the slash <filename>/</filename>. At the root level, all Debian systems include these directories:" -msgstr "A &debian; a <ulink url=\"&url-fhs-home;\">Fájlrendszer Hierarchia Szabvány</ulink>-t követi. E szabvánnyal a felhasználók és programok számára megjósolható a fájlok és könyvtárak helye. A gyökér szintű könyvtárat a <filename>/</filename> jelenti. A gyökér szintjén minden Debian rendszer tartalmazza e könyvtárakat:" +msgid "" +"&debian; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy " +"Standard</ulink> for directory and file naming. This standard allows users " +"and software programs to predict the location of files and directories. The " +"root level directory is represented simply by the slash <filename>/</" +"filename>. At the root level, all Debian systems include these directories:" +msgstr "" +"A &debian; a <ulink url=\"&url-fhs-home;\">Fájlrendszer Hierarchia Szabvány</" +"ulink>-t követi. E szabvánnyal a felhasználók és programok számára " +"megjósolható a fájlok és könyvtárak helye. A gyökér szintű könyvtárat a " +"<filename>/</filename> jelenti. A gyökér szintjén minden Debian rendszer " +"tartalmazza e könyvtárakat:" #. Tag: entry #: partitioning.xml:82 @@ -279,38 +349,115 @@ msgstr "Hozzáadott alkalmazás szoftver csomagok" #. Tag: para #: partitioning.xml:142 #, no-c-format -msgid "The following is a list of important considerations regarding directories and partitions. Note that disk usage varies widely given system configuration and specific usage patterns. The recommendations here are general guidelines and provide a starting point for partitioning." -msgstr "Alább a könyvtárakhoz és partíciókhoz kötődő legfontosabb szempontok sora. A lemez használat nagyon eltér az adott rendszer összeállításnál és felhasználói módnál. Az ajánlások itt általános útmutatók és kiindulópontot adnak a particionáláshoz." +msgid "" +"The following is a list of important considerations regarding directories " +"and partitions. Note that disk usage varies widely given system " +"configuration and specific usage patterns. The recommendations here are " +"general guidelines and provide a starting point for partitioning." +msgstr "" +"Alább a könyvtárakhoz és partíciókhoz kötődő legfontosabb szempontok sora. A " +"lemez használat nagyon eltér az adott rendszer összeállításnál és " +"felhasználói módnál. Az ajánlások itt általános útmutatók és kiindulópontot " +"adnak a particionáláshoz." #. Tag: para #: partitioning.xml:152 #, no-c-format -msgid "The root partition <filename>/</filename> must always physically contain <filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</filename>, <filename>/lib</filename> and <filename>/dev</filename>, otherwise you won't be able to boot. Typically 150–250MB is needed for the root partition." -msgstr "A <filename>/</filename> gyökér partíció kötelezően fizikailag tartalmazza a <filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</filename>, <filename>/lib</filename> és <filename>/dev</filename> könyvtárakat, másképp nem indítható. Általában 150–250MB kell erre." +msgid "" +"The root partition <filename>/</filename> must always physically contain " +"<filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</" +"filename>, <filename>/lib</filename> and <filename>/dev</filename>, " +"otherwise you won't be able to boot. Typically 150–250MB is needed for " +"the root partition." +msgstr "" +"A <filename>/</filename> gyökér partíció kötelezően fizikailag tartalmazza a " +"<filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</" +"filename>, <filename>/lib</filename> és <filename>/dev</filename> " +"könyvtárakat, másképp nem indítható. Általában 150–250MB kell erre." #. Tag: para #: partitioning.xml:161 #, no-c-format -msgid "<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</filename>), libraries (<filename>/usr/lib</filename>), documentation (<filename>/usr/share/doc</filename>), etc. This is the part of the file system that generally takes up most space. You should provide at least 500MB of disk space. This amount should be increased depending on the number and type of packages you plan to install. A generous workstation or server installation should allow 4–6GB." -msgstr "<filename>/usr</filename>: az alapvetőkön kívül a felhasználók alábbi fájljait tartalmazza: programok (<filename>/usr/bin</filename>), függvény-könyvtárak (<filename>/usr/lib</filename>), dokumentáció (<filename>/usr/share/doc</filename>), stb. Általában ez a legnagyobb partíció. Legalább 500MB helyet adj neki. Ezt a telepíteni tervezett csomagok száma és típusa növeli. Egy mindent-bele típusú munkaállomáson vagy kiszolgálón akár a 4–6GB méretet is könnyen elérheti." +msgid "" +"<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</" +"filename>), libraries (<filename>/usr/lib</filename>), documentation " +"(<filename>/usr/share/doc</filename>), etc. This is the part of the file " +"system that generally takes up most space. You should provide at least 500MB " +"of disk space. This amount should be increased depending on the number and " +"type of packages you plan to install. A generous workstation or server " +"installation should allow 4–6GB." +msgstr "" +"<filename>/usr</filename>: az alapvetőkön kívül a felhasználók alábbi " +"fájljait tartalmazza: programok (<filename>/usr/bin</filename>), függvény-" +"könyvtárak (<filename>/usr/lib</filename>), dokumentáció (<filename>/usr/" +"share/doc</filename>), stb. Általában ez a legnagyobb partíció. Legalább " +"500MB helyet adj neki. Ezt a telepíteni tervezett csomagok száma és típusa " +"növeli. Egy mindent-bele típusú munkaállomáson vagy kiszolgálón akár a " +"4–6GB méretet is könnyen elérheti." #. Tag: para #: partitioning.xml:174 #, no-c-format -msgid "<filename>/var</filename>: variable data like news articles, e-mails, web sites, databases, the packaging system cache, etc. will be placed under this directory. The size of this directory depends greatly on the usage of your system, but for most people will be dictated by the package management tool's overhead. If you are going to do a full installation of just about everything Debian has to offer, all in one session, setting aside 2 or 3 GB of space for <filename>/var</filename> should be sufficient. If you are going to install in pieces (that is to say, install services and utilities, followed by text stuff, then X, ...), you can get away with 300–500 MB. If hard drive space is at a premium and you don't plan on doing major system updates, you can get by with as little as 30 or 40 MB." -msgstr "<filename>/var</filename>: a változó adatok, mint hírek, email üzenetek, web lapok, adatbázisok, csomagkezelő gyorstár, stb. kerülnek ide. E könyvtár mérete nagyban függ a rendszer használatának módjától, de a legtöbb felhasználó számára a csomagkezelő eszköz használatának módja szabja meg. Ha a Debian nagyon sok csomagját egyben telepíted a <filename>/var</filename> számára még 2 vagy 3 GB hely is szükséges lehet. Ha rendre telepíted a dolgokat (így például előbb a szolgáltatásokat és eszközöket, majd a szövegkezelőket, majd az X rendszert, ...), 300–500 MB elég. Ha a merevlemezen lévő hellyel nagyon spórolni kell és nem tervezel nagy rendszer-frissítéseket, akár még 30 vagy 40 MB méretre is lekicsinyíthető." +msgid "" +"<filename>/var</filename>: variable data like news articles, e-mails, web " +"sites, databases, the packaging system cache, etc. will be placed under this " +"directory. The size of this directory depends greatly on the usage of your " +"system, but for most people will be dictated by the package management " +"tool's overhead. If you are going to do a full installation of just about " +"everything Debian has to offer, all in one session, setting aside 2 or 3 GB " +"of space for <filename>/var</filename> should be sufficient. If you are " +"going to install in pieces (that is to say, install services and utilities, " +"followed by text stuff, then X, ...), you can get away with 300–500 " +"MB. If hard drive space is at a premium and you don't plan on doing major " +"system updates, you can get by with as little as 30 or 40 MB." +msgstr "" +"<filename>/var</filename>: a változó adatok, mint hírek, email üzenetek, web " +"lapok, adatbázisok, csomagkezelő gyorstár, stb. kerülnek ide. E könyvtár " +"mérete nagyban függ a rendszer használatának módjától, de a legtöbb " +"felhasználó számára a csomagkezelő eszköz használatának módja szabja meg. Ha " +"a Debian nagyon sok csomagját egyben telepíted a <filename>/var</filename> " +"számára még 2 vagy 3 GB hely is szükséges lehet. Ha rendre telepíted a " +"dolgokat (így például előbb a szolgáltatásokat és eszközöket, majd a " +"szövegkezelőket, majd az X rendszert, ...), 300–500 MB elég. Ha a " +"merevlemezen lévő hellyel nagyon spórolni kell és nem tervezel nagy rendszer-" +"frissítéseket, akár még 30 vagy 40 MB méretre is lekicsinyíthető." #. Tag: para #: partitioning.xml:190 #, no-c-format -msgid "<filename>/tmp</filename>: temporary data created by programs will most likely go in this directory. 40–100MB should usually be enough. Some applications — including archive manipulators, CD/DVD authoring tools, and multimedia software — may use <filename>/tmp</filename> to temporarily store image files. If you plan to use such applications, you should adjust the space available in <filename>/tmp</filename> accordingly." -msgstr "<filename>/tmp</filename>: a programok által létrehozott átmeneti adatok általában ide kerülnek. 40–100MB általában elég. Egyes alkalmazások — például archívum kezelők, CD/DVD készítők és multimédia szoftverek — a <filename>/tmp</filename> könyvtárat képmás fájlok tárolására használhatják. Ha ilyen alkalmazások használatát tervezed, igazítsd a <filename>/tmp</filename> könyvtárban elérhető helyet ehhez." +msgid "" +"<filename>/tmp</filename>: temporary data created by programs will most " +"likely go in this directory. 40–100MB should usually be enough. Some " +"applications — including archive manipulators, CD/DVD authoring tools, " +"and multimedia software — may use <filename>/tmp</filename> to " +"temporarily store image files. If you plan to use such applications, you " +"should adjust the space available in <filename>/tmp</filename> accordingly." +msgstr "" +"<filename>/tmp</filename>: a programok által létrehozott átmeneti adatok " +"általában ide kerülnek. 40–100MB általában elég. Egyes alkalmazások " +"— például archívum kezelők, CD/DVD készítők és multimédia szoftverek " +"— a <filename>/tmp</filename> könyvtárat képmás fájlok tárolására " +"használhatják. Ha ilyen alkalmazások használatát tervezed, igazítsd a " +"<filename>/tmp</filename> könyvtárban elérhető helyet ehhez." #. Tag: para #: partitioning.xml:201 #, no-c-format -msgid "<filename>/home</filename>: every user will put his personal data into a subdirectory of this directory. Its size depends on how many users will be using the system and what files are to be stored in their directories. Depending on your planned usage you should reserve about 100MB for each user, but adapt this value to your needs. Reserve a lot more space if you plan to save a lot of multimedia files (pictures, MP3, movies) in your home directory." -msgstr "<filename>/home</filename>: a felhasználók személyes adataikat e könyvtár alkönyvtáraiba teszik. Mérete függ számuktól és attól, hogy milyen fájlokat tárolnak e saját könyvtáraikban. A tervezett felhasználástól függően általában jó legalább 100MB helyet fenntartani mindegyiküknek, de igazítsd ezt az értéket igényeidhez. Tarts fent sokkal több helyet, ha sok multimédia fájl (képek, zenék, filmek) mentését tervezed saját könyvtáradba." +msgid "" +"<filename>/home</filename>: every user will put his personal data into a " +"subdirectory of this directory. Its size depends on how many users will be " +"using the system and what files are to be stored in their directories. " +"Depending on your planned usage you should reserve about 100MB for each " +"user, but adapt this value to your needs. Reserve a lot more space if you " +"plan to save a lot of multimedia files (pictures, MP3, movies) in your home " +"directory." +msgstr "" +"<filename>/home</filename>: a felhasználók személyes adataikat e könyvtár " +"alkönyvtáraiba teszik. Mérete függ számuktól és attól, hogy milyen fájlokat " +"tárolnak e saját könyvtáraikban. A tervezett felhasználástól függően " +"általában jó legalább 100MB helyet fenntartani mindegyiküknek, de igazítsd " +"ezt az értéket igényeidhez. Tarts fent sokkal több helyet, ha sok multimédia " +"fájl (képek, zenék, filmek) mentését tervezed saját könyvtáradba." #. Tag: title #: partitioning.xml:222 @@ -321,56 +468,142 @@ msgstr "Ajánlott partíciós séma" #. Tag: para #: partitioning.xml:223 #, no-c-format -msgid "For new users, personal Debian boxes, home systems, and other single-user setups, a single <filename>/</filename> partition (plus swap) is probably the easiest, simplest way to go. However, if your partition is larger than around 6GB, choose ext3 as your partition type. Ext2 partitions need periodic file system integrity checking, and this can cause delays during booting when the partition is large." -msgstr "Új felhasználóknak, személyes Debian gépekre, otthoni rendszerekre és más 1-felhasználós telepítésekre egyetlen <filename>/</filename> partíció (és egy cserehely) a legkönnyebb, legegyszerűbb mód. Ha a partíció nagyobb, mint 6GB, mindenképp válassz ext3 partíció típust. Az ext2 partíciók ismételt fájlrendszer-ellenőrzést igényelnek és ez időnként késleltetheti az indítást, ha egy partíció nagy." +msgid "" +"For new users, personal Debian boxes, home systems, and other single-user " +"setups, a single <filename>/</filename> partition (plus swap) is probably " +"the easiest, simplest way to go. However, if your partition is larger than " +"around 6GB, choose ext3 as your partition type. Ext2 partitions need " +"periodic file system integrity checking, and this can cause delays during " +"booting when the partition is large." +msgstr "" +"Új felhasználóknak, személyes Debian gépekre, otthoni rendszerekre és más 1-" +"felhasználós telepítésekre egyetlen <filename>/</filename> partíció (és egy " +"cserehely) a legkönnyebb, legegyszerűbb mód. Ha a partíció nagyobb, mint " +"6GB, mindenképp válassz ext3 partíció típust. Az ext2 partíciók ismételt " +"fájlrendszer-ellenőrzést igényelnek és ez időnként késleltetheti az " +"indítást, ha egy partíció nagy." #. Tag: para #: partitioning.xml:232 #, no-c-format -msgid "For multi-user systems or systems with lots of disk space, it's best to put <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, and <filename>/home</filename> each on their own partitions separate from the <filename>/</filename> partition." -msgstr "Ha több felhasználó használhatja a rendszert és van hely, a legjobb séma, ha a <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, és <filename>/home</filename> mind saját partícióra kerül a <filename>/</filename> partíciótól külön." +msgid "" +"For multi-user systems or systems with lots of disk space, it's best to put " +"<filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</" +"filename>, and <filename>/home</filename> each on their own partitions " +"separate from the <filename>/</filename> partition." +msgstr "" +"Ha több felhasználó használhatja a rendszert és van hely, a legjobb séma, ha " +"a <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</" +"filename>, és <filename>/home</filename> mind saját partícióra kerül a " +"<filename>/</filename> partíciótól külön." #. Tag: para #: partitioning.xml:240 #, no-c-format -msgid "You might need a separate <filename>/usr/local</filename> partition if you plan to install many programs that are not part of the Debian distribution. If your machine will be a mail server, you might need to make <filename>/var/mail</filename> a separate partition. Often, putting <filename>/tmp</filename> on its own partition, for instance 20–50MB, is a good idea. If you are setting up a server with lots of user accounts, it's generally good to have a separate, large <filename>/home</filename> partition. In general, the partitioning situation varies from computer to computer depending on its uses." -msgstr "Legyen külön <filename>/usr/local</filename> partíció, ha sok program telepítését tervezed forrásból, melyek valószínűleg nem részei a Debian terjesztésnek. Ha a gép egy kívülről és elérhető levelező kiszolgáló, a <filename>/var/mail</filename> legyen külön partíció. A <filename>/tmp</filename> könyvtárat is gyakran külön partícióra teszik, 20–50MB erre jó ötlet lehet. Ha sok valódi felhasználói hozzáférés van, általában jó a <filename>/home</filename> partíciót külön venni. A legjobb partíciós séma gépről gépre eltér felhasználástól függően." +msgid "" +"You might need a separate <filename>/usr/local</filename> partition if you " +"plan to install many programs that are not part of the Debian distribution. " +"If your machine will be a mail server, you might need to make <filename>/var/" +"mail</filename> a separate partition. Often, putting <filename>/tmp</" +"filename> on its own partition, for instance 20–50MB, is a good idea. " +"If you are setting up a server with lots of user accounts, it's generally " +"good to have a separate, large <filename>/home</filename> partition. In " +"general, the partitioning situation varies from computer to computer " +"depending on its uses." +msgstr "" +"Legyen külön <filename>/usr/local</filename> partíció, ha sok program " +"telepítését tervezed forrásból, melyek valószínűleg nem részei a Debian " +"terjesztésnek. Ha a gép egy kívülről és elérhető levelező kiszolgáló, a " +"<filename>/var/mail</filename> legyen külön partíció. A <filename>/tmp</" +"filename> könyvtárat is gyakran külön partícióra teszik, 20–50MB erre " +"jó ötlet lehet. Ha sok valódi felhasználói hozzáférés van, általában jó a " +"<filename>/home</filename> partíciót külön venni. A legjobb partíciós séma " +"gépről gépre eltér felhasználástól függően." #. Tag: para #: partitioning.xml:252 #, no-c-format -msgid "For very complex systems, you should see the <ulink url=\"&url-multidisk-howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, mostly of interest to ISPs and people setting up servers." -msgstr "A nagyon összetett rendszerekhez, lásd a <ulink url=\"&url-multidisk-howto;\"> Több lemez HOGYAN</ulink>címet. Ez mély leírást ad, melyet főleg az internet-szolgáltatók és kiszolgálók üzemeltetői hasznosítanak." +msgid "" +"For very complex systems, you should see the <ulink url=\"&url-multidisk-" +"howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, " +"mostly of interest to ISPs and people setting up servers." +msgstr "" +"A nagyon összetett rendszerekhez, lásd a <ulink url=\"&url-multidisk-howto;" +"\"> Több lemez HOGYAN</ulink>címet. Ez mély leírást ad, melyet főleg az " +"internet-szolgáltatók és kiszolgálók üzemeltetői hasznosítanak." #. Tag: para #: partitioning.xml:259 #, no-c-format -msgid "With respect to the issue of swap partition size, there are many views. One rule of thumb which works well is to use as much swap as you have system memory. It also shouldn't be smaller than 16MB, in most cases. Of course, there are exceptions to these rules. If you are trying to solve 10000 simultaneous equations on a machine with 256MB of memory, you may need a gigabyte (or more) of swap." -msgstr "A csere-partíció méretéről több szempont van. Az egyik, mely jól működik, hogy legyen legalább annyi, mint memória. Általában ne legyen kisebb, mint 16MB. Természetesen van eltérés e szabályoktól. Például, ha 10000 párhuzamos egyenletet oldasz meg 256MB memóriával, 1 GB vagy több cserehely kell." +msgid "" +"With respect to the issue of swap partition size, there are many views. One " +"rule of thumb which works well is to use as much swap as you have system " +"memory. It also shouldn't be smaller than 16MB, in most cases. Of course, " +"there are exceptions to these rules. If you are trying to solve 10000 " +"simultaneous equations on a machine with 256MB of memory, you may need a " +"gigabyte (or more) of swap." +msgstr "" +"A csere-partíció méretéről több szempont van. Az egyik, mely jól működik, " +"hogy legyen legalább annyi, mint memória. Általában ne legyen kisebb, mint " +"16MB. Természetesen van eltérés e szabályoktól. Például, ha 10000 párhuzamos " +"egyenletet oldasz meg 256MB memóriával, 1 GB vagy több cserehely kell." #. Tag: para #: partitioning.xml:268 #, no-c-format -msgid "On the other hand, Atari Falcons and Macs feel pain when swapping, so instead of making a large swap partition, get as much RAM as possible." -msgstr "Az Atari Falcon vagy a Mac gépek nagyon cserehely-kezelése nagyon rossz, itt nincs más, mint annyi memóriát vásárolni, amennyit csak lehetséges." +msgid "" +"On the other hand, Atari Falcons and Macs feel pain when swapping, so " +"instead of making a large swap partition, get as much RAM as possible." +msgstr "" +"Az Atari Falcon vagy a Mac gépek nagyon cserehely-kezelése nagyon rossz, itt " +"nincs más, mint annyi memóriát vásárolni, amennyit csak lehetséges." #. Tag: para #: partitioning.xml:273 #, no-c-format -msgid "On 32-bit architectures (i386, m68k, 32-bit SPARC, and PowerPC), the maximum size of a swap partition is 2GB. That should be enough for nearly any installation. However, if your swap requirements are this high, you should probably try to spread the swap across different disks (also called <quote>spindles</quote>) and, if possible, different SCSI or IDE channels. The kernel will balance swap usage between multiple swap partitions, giving better performance." -msgstr "A 32-bites gépeken (i386, m68k, 32-bites SPARC és PowerPC) a csere-partíció legnagyobb mérete 2GB. Ez még a legkeményebb feladatokra is szinte mindig elég. De ha a csere-igényed ily magas érdemes több lemez (indák) közt elosztani, ha lehet, különböző SCSI vagy IDE csatornákon. A kernel kiegyenlíti a csere-használatot több csere-partíció közt, nagyobb teljesítményt nyújtva." +msgid "" +"On 32-bit architectures (i386, m68k, 32-bit SPARC, and PowerPC), the maximum " +"size of a swap partition is 2GB. That should be enough for nearly any " +"installation. However, if your swap requirements are this high, you should " +"probably try to spread the swap across different disks (also called " +"<quote>spindles</quote>) and, if possible, different SCSI or IDE channels. " +"The kernel will balance swap usage between multiple swap partitions, giving " +"better performance." +msgstr "" +"A 32-bites gépeken (i386, m68k, 32-bites SPARC és PowerPC) a csere-partíció " +"legnagyobb mérete 2GB. Ez még a legkeményebb feladatokra is szinte mindig " +"elég. De ha a csere-igényed ily magas érdemes több lemez (indák) közt " +"elosztani, ha lehet, különböző SCSI vagy IDE csatornákon. A kernel " +"kiegyenlíti a csere-használatot több csere-partíció közt, nagyobb " +"teljesítményt nyújtva." #. Tag: para #: partitioning.xml:283 #, no-c-format -msgid "As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE drive on <filename>/dev/hda</filename>. There might be a 500MB partition for another operating system on <filename>/dev/hda1</filename>, a 32MB swap partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/dev/hda2</filename> as the Linux partition." -msgstr "Íme egy régi otthoni gép 32MB memóriával és 1.7GB IDE meghajtóval a <filename>/dev/hda</filename> címen. Volt rajta egy 500MB méretű, másik operációs rendszert tartalmazó partíció a <filename>/dev/hda1</filename> címen és ezután a <filename>/dev/hda3</filename> címre került egy 32MB csere-partíció, és egy 1.2GB Linux partíció a <filename>/dev/hda2</filename> címre." +msgid "" +"As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE " +"drive on <filename>/dev/hda</filename>. There might be a 500MB partition for " +"another operating system on <filename>/dev/hda1</filename>, a 32MB swap " +"partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/" +"dev/hda2</filename> as the Linux partition." +msgstr "" +"Íme egy régi otthoni gép 32MB memóriával és 1.7GB IDE meghajtóval a " +"<filename>/dev/hda</filename> címen. Volt rajta egy 500MB méretű, másik " +"operációs rendszert tartalmazó partíció a <filename>/dev/hda1</filename> " +"címen és ezután a <filename>/dev/hda3</filename> címre került egy 32MB csere-" +"partíció, és egy 1.2GB Linux partíció a <filename>/dev/hda2</filename> címre." #. Tag: para #: partitioning.xml:292 #, no-c-format -msgid "For an idea of the space taken by tasks you might be interested in adding after your system installation is complete, check <xref linkend=\"tasksel-size-list\"/>." -msgstr "Az egyes feladatok által lefoglalt méretekről, melyek közül egyeseket valószínűleg hozzáadnál a rendszer telepítése után, lásd a <xref linkend=\"tasksel-size-list\"/> részt." +msgid "" +"For an idea of the space taken by tasks you might be interested in adding " +"after your system installation is complete, check <xref linkend=\"tasksel-" +"size-list\"/>." +msgstr "" +"Az egyes feladatok által lefoglalt méretekről, melyek közül egyeseket " +"valószínűleg hozzáadnál a rendszer telepítése után, lásd a <xref linkend=" +"\"tasksel-size-list\"/> részt." #. Tag: title #: partitioning.xml:308 @@ -381,8 +614,14 @@ msgstr "Eszköznevek Linuxban" #. Tag: para #: partitioning.xml:309 #, no-c-format -msgid "Linux disks and partition names may be different from other operating systems. You need to know the names that Linux uses when you create and mount partitions. Here's the basic naming scheme:" -msgstr "A Linuxban is megtalálható lemez és partíció nevek eltérhetnek bizonyos más operációs rendszerekétől. Ismerned kell az itt használt neveket, amikor partíciókat hozol létre és csatolsz. Itt az alap elnevezési rend:" +msgid "" +"Linux disks and partition names may be different from other operating " +"systems. You need to know the names that Linux uses when you create and " +"mount partitions. Here's the basic naming scheme:" +msgstr "" +"A Linuxban is megtalálható lemez és partíció nevek eltérhetnek bizonyos más " +"operációs rendszerekétől. Ismerned kell az itt használt neveket, amikor " +"partíciókat hozol létre és csatolsz. Itt az alap elnevezési rend:" #. Tag: para #: partitioning.xml:317 @@ -399,38 +638,70 @@ msgstr "Az 2. flopi meghajtó neve <filename>/dev/fd1</filename>." #. Tag: para #: partitioning.xml:327 #, no-c-format -msgid "The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</filename>." -msgstr "Az 1. SCSI lemez (SCSI ID cím-szintű) neve <filename>/dev/sda</filename>." +msgid "" +"The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</" +"filename>." +msgstr "" +"Az 1. SCSI lemez (SCSI ID cím-szintű) neve <filename>/dev/sda</filename>." #. Tag: para #: partitioning.xml:333 #, no-c-format -msgid "The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, and so on." -msgstr "Az 2. SCSI lemez (SCSI ID cím-szintű) neve <filename>/dev/sdb</filename> és így tovább." +msgid "" +"The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, " +"and so on." +msgstr "" +"Az 2. SCSI lemez (SCSI ID cím-szintű) neve <filename>/dev/sdb</filename> és " +"így tovább." #. Tag: para #: partitioning.xml:339 #, no-c-format -msgid "The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as <filename>/dev/sr0</filename>." -msgstr "Az 1. SCSI CS-ROM neve <filename>/dev/scd0</filename>, <filename>/dev/sr0</filename> névvel is ismert." +msgid "" +"The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as " +"<filename>/dev/sr0</filename>." +msgstr "" +"Az 1. SCSI CS-ROM neve <filename>/dev/scd0</filename>, <filename>/dev/sr0</" +"filename> névvel is ismert." #. Tag: para #: partitioning.xml:345 #, no-c-format -msgid "The master disk on IDE primary controller is named <filename>/dev/hda</filename>." -msgstr "Az elsődleges IDE vezérlőn lévő mester (master) lemez neve <filename>/dev/hda</filename>." +msgid "" +"The master disk on IDE primary controller is named <filename>/dev/hda</" +"filename>." +msgstr "" +"Az elsődleges IDE vezérlőn lévő mester (master) lemez neve <filename>/dev/" +"hda</filename>." #. Tag: para #: partitioning.xml:351 #, no-c-format -msgid "The slave disk on IDE primary controller is named <filename>/dev/hdb</filename>." -msgstr "Az elsődleges IDE vezérlőn lévő szolga (slave) lemez neve <filename>/dev/hdb</filename>." +msgid "" +"The slave disk on IDE primary controller is named <filename>/dev/hdb</" +"filename>." +msgstr "" +"Az elsődleges IDE vezérlőn lévő szolga (slave) lemez neve <filename>/dev/" +"hdb</filename>." #. Tag: para #: partitioning.xml:357 #, no-c-format -msgid "The master and slave disks of the secondary controller can be called <filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, respectively. Newer IDE controllers can actually have two channels, effectively acting like two controllers. <phrase arch=\"m68k\"> The letters may differ from what shows in the mac program pdisk (i.e. what shows up as <filename>/dev/hdc</filename> on pdisk may show up as <filename>/dev/hda</filename> in Debian). </phrase>" -msgstr "A másodlagos vezérlő mester (master) és szolga (slave) lemezei neve <filename>/dev/hdc</filename> és <filename>/dev/hdd</filename>. Az újabb IDE vezérlők 2 csatornásak, ezek módjára működnek. <phrase arch=\"m68k\"> A betűk eltérhetnek a pdisk által mutatottól (például, amit talán a pdisk mint <filename>/dev/hdc</filename> mutat, a Debian rendszerben <filename>/dev/hda</filename> lehet). </phrase>" +msgid "" +"The master and slave disks of the secondary controller can be called " +"<filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, " +"respectively. Newer IDE controllers can actually have two channels, " +"effectively acting like two controllers. <phrase arch=\"m68k\"> The letters " +"may differ from what shows in the mac program pdisk (i.e. what shows up as " +"<filename>/dev/hdc</filename> on pdisk may show up as <filename>/dev/hda</" +"filename> in Debian). </phrase>" +msgstr "" +"A másodlagos vezérlő mester (master) és szolga (slave) lemezei neve " +"<filename>/dev/hdc</filename> és <filename>/dev/hdd</filename>. Az újabb IDE " +"vezérlők 2 csatornásak, ezek módjára működnek. <phrase arch=\"m68k\"> A " +"betűk eltérhetnek a pdisk által mutatottól (például, amit talán a pdisk mint " +"<filename>/dev/hdc</filename> mutat, a Debian rendszerben <filename>/dev/" +"hda</filename> lehet). </phrase>" #. Tag: para #: partitioning.xml:372 @@ -447,8 +718,12 @@ msgstr "Az 2. XT lemez neve <filename>/dev/xda</filename>." #. Tag: para #: partitioning.xml:382 #, no-c-format -msgid "The first ACSI device is named <filename>/dev/ada</filename>, the second is named <filename>/dev/adb</filename>." -msgstr "Az 1. ACSI eszköz neve <filename>/dev/ada</filename>, a 2. neve <filename>/dev/adb</filename>." +msgid "" +"The first ACSI device is named <filename>/dev/ada</filename>, the second is " +"named <filename>/dev/adb</filename>." +msgstr "" +"Az 1. ACSI eszköz neve <filename>/dev/ada</filename>, a 2. neve <filename>/" +"dev/adb</filename>." #. Tag: para #: partitioning.xml:391 @@ -459,50 +734,114 @@ msgstr "Az 1. DASD eszköz neve <filename>/dev/dasda</filename>." #. Tag: para #: partitioning.xml:397 #, no-c-format -msgid "The second DASD device is named <filename>/dev/dasdb</filename>, and so on." +msgid "" +"The second DASD device is named <filename>/dev/dasdb</filename>, and so on." msgstr "Az 2. DASD eszköz neve <filename>/dev/dasdb</filename> és így tovább." #. Tag: para #: partitioning.xml:405 #, no-c-format -msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>sda1</filename> and <filename>sda2</filename> represent the first and second partitions of the first SCSI disk drive in your system." -msgstr "Az egyes lemezek partíciói egy a lemez nevéhez fűzött tízes számrendszerbeli számmal ábrázoltak: az <filename>sda1</filename> és <filename>sda2</filename> a rendszer 1. SCSI lemez-meghajtója 1. és 2. partícióját adják." +msgid "" +"The partitions on each disk are represented by appending a decimal number to " +"the disk name: <filename>sda1</filename> and <filename>sda2</filename> " +"represent the first and second partitions of the first SCSI disk drive in " +"your system." +msgstr "" +"Az egyes lemezek partíciói egy a lemez nevéhez fűzött tízes számrendszerbeli " +"számmal ábrázoltak: az <filename>sda1</filename> és <filename>sda2</" +"filename> a rendszer 1. SCSI lemez-meghajtója 1. és 2. partícióját adják." #. Tag: para #: partitioning.xml:412 #, no-c-format -msgid "Here is a real-life example. Let's assume you have a system with 2 SCSI disks, one at SCSI address 2 and the other at SCSI address 4. The first disk (at address 2) is then named <filename>sda</filename>, and the second <filename>sdb</filename>. If the <filename>sda</filename> drive has 3 partitions on it, these will be named <filename>sda1</filename>, <filename>sda2</filename>, and <filename>sda3</filename>. The same applies to the <filename>sdb</filename> disk and its partitions." -msgstr "Itt egy valós példa. Tegyük fel, hogy van egy rendszer 2 SCSI lemezzel, az egyik a kettes, a másik a négyes SCSI címen. Az első lemez (a kettes címen) neve <filename>sda</filename>, a másodiké <filename>sdb</filename>. Ha az <filename>sda</filename> meghajtónak 3 partíciója van, neveik <filename>sda1</filename>, <filename>sda2</filename> és <filename>sda3</filename>. Hasonlóan alakul az <filename>sdb</filename> lemez és partíciói." +msgid "" +"Here is a real-life example. Let's assume you have a system with 2 SCSI " +"disks, one at SCSI address 2 and the other at SCSI address 4. The first disk " +"(at address 2) is then named <filename>sda</filename>, and the second " +"<filename>sdb</filename>. If the <filename>sda</filename> drive has 3 " +"partitions on it, these will be named <filename>sda1</filename>, " +"<filename>sda2</filename>, and <filename>sda3</filename>. The same applies " +"to the <filename>sdb</filename> disk and its partitions." +msgstr "" +"Itt egy valós példa. Tegyük fel, hogy van egy rendszer 2 SCSI lemezzel, az " +"egyik a kettes, a másik a négyes SCSI címen. Az első lemez (a kettes címen) " +"neve <filename>sda</filename>, a másodiké <filename>sdb</filename>. Ha az " +"<filename>sda</filename> meghajtónak 3 partíciója van, neveik " +"<filename>sda1</filename>, <filename>sda2</filename> és <filename>sda3</" +"filename>. Hasonlóan alakul az <filename>sdb</filename> lemez és partíciói." #. Tag: para #: partitioning.xml:423 #, no-c-format -msgid "Note that if you have two SCSI host bus adapters (i.e., controllers), the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities." -msgstr "Figyelj, ha 2 SCSI gazda busz adaptered (vezérlőd) van, a meghajtók sorrendje zavarba ejthet. A meghajtók modellje és/vagy kapacitása ismeretében az indító üzenetek mindent elárulnak." +msgid "" +"Note that if you have two SCSI host bus adapters (i.e., controllers), the " +"order of the drives can get confusing. The best solution in this case is to " +"watch the boot messages, assuming you know the drive models and/or " +"capacities." +msgstr "" +"Figyelj, ha 2 SCSI gazda busz adaptered (vezérlőd) van, a meghajtók " +"sorrendje zavarba ejthet. A meghajtók modellje és/vagy kapacitása " +"ismeretében az indító üzenetek mindent elárulnak." #. Tag: para #: partitioning.xml:430 #, no-c-format -msgid "Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are numbered starting at 5, so the first logical partition on that same drive is <filename>/dev/hda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. This applies to SCSI disks as well as IDE disks." -msgstr "A Linux az elsődleges partíciókat a meghajtó nevével és 1 és 4 közti számokkal jelzi. Például az 1. elsődleges partíció az 1. IDE meghajtón a <filename>/dev/hda1</filename>. 5 az indító értéke a logikai partíciók számának, így az 1. logikai partíció e meghajtón a <filename>/dev/hda5</filename>. Ne feledd, a kiterjesztett partíció, a logikai partíciókat tároló elsődleges partíció, nem használható magában. Ez a SCSI és IDE lemezekre is áll." +msgid "" +"Linux represents the primary partitions as the drive name, plus the numbers " +"1 through 4. For example, the first primary partition on the first IDE drive " +"is <filename>/dev/hda1</filename>. The logical partitions are numbered " +"starting at 5, so the first logical partition on that same drive is " +"<filename>/dev/hda5</filename>. Remember that the extended partition, that " +"is, the primary partition holding the logical partitions, is not usable by " +"itself. This applies to SCSI disks as well as IDE disks." +msgstr "" +"A Linux az elsődleges partíciókat a meghajtó nevével és 1 és 4 közti " +"számokkal jelzi. Például az 1. elsődleges partíció az 1. IDE meghajtón a " +"<filename>/dev/hda1</filename>. 5 az indító értéke a logikai partíciók " +"számának, így az 1. logikai partíció e meghajtón a <filename>/dev/hda5</" +"filename>. Ne feledd, a kiterjesztett partíció, a logikai partíciókat tároló " +"elsődleges partíció, nem használható magában. Ez a SCSI és IDE lemezekre is " +"áll." #. Tag: para #: partitioning.xml:441 #, no-c-format -msgid "VMEbus systems using the TEAC FC-1 SCSI floppy drive will see it as normal SCSI disk. To make identification of the drive simpler the installation software will create a symbolic link to the appropriate device and name it <filename>/dev/sfd0</filename>." -msgstr "A TEAC FC-1 SCSI flopi meghajtót használó VMEbus rendszerek azt normál SCSI lemeznek látják. Az egyszerűbb azonosításért a telepítő létrehoz egy jelképes láncot a megfelelő eszközhöz és elnevezi így: <filename>/dev/sfd0</filename>." +msgid "" +"VMEbus systems using the TEAC FC-1 SCSI floppy drive will see it as normal " +"SCSI disk. To make identification of the drive simpler the installation " +"software will create a symbolic link to the appropriate device and name it " +"<filename>/dev/sfd0</filename>." +msgstr "" +"A TEAC FC-1 SCSI flopi meghajtót használó VMEbus rendszerek azt normál SCSI " +"lemeznek látják. Az egyszerűbb azonosításért a telepítő létrehoz egy " +"jelképes láncot a megfelelő eszközhöz és elnevezi így: <filename>/dev/sfd0</" +"filename>." #. Tag: para #: partitioning.xml:448 #, no-c-format -msgid "Sun disk partitions allow for 8 separate partitions (or slices). The third partition is usually (and is preferred to have) the <quote>Whole Disk</quote> partition. This partition references all of the sectors of the disk, and is used by the boot loader (either SILO, or Sun's)." -msgstr "8 Sun lemez-partíció (szelet) lehet. A 3. általában (és ajánlottan) az <quote>Egész lemez</quote> partíció. E partíció a lemez összes szektorára hivatkozik és a boot betöltő használja (akár a SILO akár a Sun-é)." +msgid "" +"Sun disk partitions allow for 8 separate partitions (or slices). The third " +"partition is usually (and is preferred to have) the <quote>Whole Disk</" +"quote> partition. This partition references all of the sectors of the disk, " +"and is used by the boot loader (either SILO, or Sun's)." +msgstr "" +"8 Sun lemez-partíció (szelet) lehet. A 3. általában (és ajánlottan) az " +"<quote>Egész lemez</quote> partíció. E partíció a lemez összes szektorára " +"hivatkozik és a boot betöltő használja (akár a SILO akár a Sun-é)." #. Tag: para #: partitioning.xml:455 #, no-c-format -msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> represent the first and second partitions of the first DASD device in your system." -msgstr "Az egyes lemezek partíciói egy a lemez nevéhez fűzött tízes számrendszerbeli számmal ábrázoltak: a <filename>dasda1</filename> és <filename>dasda2</filename> a rendszer 1. DASD eszköze 1. és 2. partícióját adják." +msgid "" +"The partitions on each disk are represented by appending a decimal number to " +"the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> " +"represent the first and second partitions of the first DASD device in your " +"system." +msgstr "" +"Az egyes lemezek partíciói egy a lemez nevéhez fűzött tízes számrendszerbeli " +"számmal ábrázoltak: a <filename>dasda1</filename> és <filename>dasda2</" +"filename> a rendszer 1. DASD eszköze 1. és 2. partícióját adják." #. Tag: title #: partitioning.xml:470 @@ -513,8 +852,15 @@ msgstr "Debian particionáló programok" #. Tag: para #: partitioning.xml:471 #, no-c-format -msgid "Several varieties of partitioning programs have been adapted by Debian developers to work on various types of hard disks and computer architectures. Following is a list of the program(s) applicable for your architecture." -msgstr "A Debian fejlesztők számos particionáló programot alkalmaztak a különböző merevlemezekhez és számítógép architektúrákhoz. Itt az architektúrádhoz illő programok sora." +msgid "" +"Several varieties of partitioning programs have been adapted by Debian " +"developers to work on various types of hard disks and computer " +"architectures. Following is a list of the program(s) applicable for your " +"architecture." +msgstr "" +"A Debian fejlesztők számos particionáló programot alkalmaztak a különböző " +"merevlemezekhez és számítógép architektúrákhoz. Itt az architektúrádhoz illő " +"programok sora." #. Tag: command #: partitioning.xml:483 @@ -525,8 +871,15 @@ msgstr "partman" #. Tag: para #: partitioning.xml:484 #, no-c-format -msgid "Recommended partitioning tool in Debian. This Swiss army knife can also resize partitions, create filesystems <phrase arch=\"x86\"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints." -msgstr "A Debian rendszer ajánlott particionáló eszköze. Ez a svájci bicska átméretez partíciókat, létrehoz fájlrendszereket <phrase arch=\"x86\"> (<quote>formáz</quote> a windowsos-nyelvűeknél)</phrase> és csatolási pontokhoz rendeli őket." +msgid "" +"Recommended partitioning tool in Debian. This Swiss army knife can also " +"resize partitions, create filesystems <phrase arch=\"x86\"> (<quote>format</" +"quote> in Windows speak)</phrase> and assign them to the mountpoints." +msgstr "" +"A Debian rendszer ajánlott particionáló eszköze. Ez a svájci bicska " +"átméretez partíciókat, létrehoz fájlrendszereket <phrase arch=\"x86\"> " +"(<quote>formáz</quote> a windowsos-nyelvűeknél)</phrase> és csatolási " +"pontokhoz rendeli őket." #. Tag: command #: partitioning.xml:495 @@ -543,8 +896,17 @@ msgstr "Az eredeti Linux lemez-particionáló, tapasztaltaknak könnyű." #. Tag: para #: partitioning.xml:500 #, no-c-format -msgid "Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that <command>fdisk</command> represents them (or not) can make the device names differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</ulink>." -msgstr "Légy óvatos, ha FreeBSD partícióid vannak. A telepítő kernelek támogatják ezeket, de a mód miatt, ahogy az <command>fdisk</command> megjeleníti (vagy nem) ezeket az eszközök nevei eltérhetnek. Lásd a <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOGYAN</ulink> leírást." +msgid "" +"Be careful if you have existing FreeBSD partitions on your machine. The " +"installation kernels include support for these partitions, but the way that " +"<command>fdisk</command> represents them (or not) can make the device names " +"differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</" +"ulink>." +msgstr "" +"Légy óvatos, ha FreeBSD partícióid vannak. A telepítő kernelek támogatják " +"ezeket, de a mód miatt, ahogy az <command>fdisk</command> megjeleníti (vagy " +"nem) ezeket az eszközök nevei eltérhetnek. Lásd a <ulink url=\"&url-linux-" +"freebsd;\">Linux+FreeBSD HOGYAN</ulink> leírást." #. Tag: command #: partitioning.xml:512 @@ -561,8 +923,12 @@ msgstr "Könnyen használható, teljes-képernyős lemez particionáló sokunkna #. Tag: para #: partitioning.xml:517 #, no-c-format -msgid "Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result." -msgstr "Tudni kell, hogy a <command>cfdisk</command> egyáltalán nem érti a FreeBSD partíciókat, és újra, az eszközök nevei eltérhetnek emiatt." +msgid "" +"Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at " +"all, and, again, device names may differ as a result." +msgstr "" +"Tudni kell, hogy a <command>cfdisk</command> egyáltalán nem érti a FreeBSD " +"partíciókat, és újra, az eszközök nevei eltérhetnek emiatt." #. Tag: command #: partitioning.xml:526 @@ -609,8 +975,12 @@ msgstr "pmac-fdisk" #. Tag: para #: partitioning.xml:554 #, no-c-format -msgid "PowerMac-aware version of <command>fdisk</command>, also used by BVM and Motorola VMEbus systems." -msgstr "Az <command>fdisk</command> PowerMac verziója, a BVM és Motorola VMEbus rendszerek is használják." +msgid "" +"PowerMac-aware version of <command>fdisk</command>, also used by BVM and " +"Motorola VMEbus systems." +msgstr "" +"Az <command>fdisk</command> PowerMac verziója, a BVM és Motorola VMEbus " +"rendszerek is használják." #. Tag: command #: partitioning.xml:563 @@ -621,173 +991,370 @@ msgstr "fdasd" #. Tag: para #: partitioning.xml:564 #, no-c-format -msgid "&arch-title; version of <command>fdisk</command>; Please read the fdasd manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and Installation Commands</ulink> for details." -msgstr "Az <command>fdisk</command> &arch-title; verziója; olvasd el az <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf\"> Eszközmeghajtók és telepítő parancsok</ulink> 13. fejezetét vagy az fdasd kézikönyv oldalt a részletekért." +msgid "" +"&arch-title; version of <command>fdisk</command>; Please read the fdasd " +"manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/" +"developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and " +"Installation Commands</ulink> for details." +msgstr "" +"Az <command>fdisk</command> &arch-title; verziója; olvasd el az <ulink url=" +"\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/" +"l390dd08.pdf\"> Eszközmeghajtók és telepítő parancsok</ulink> 13. fejezetét " +"vagy az fdasd kézikönyv oldalt a részletekért." #. Tag: para #: partitioning.xml:575 #, no-c-format -msgid "One of these programs will be run by default when you select <guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible to use a different partitioning tool from the command line on VT2, but this is not recommended." -msgstr "E programok egyike indul a <guimenuitem>Lemezek particionálása</guimenuitem> (vagy hasonló) választásakor. Más particionáló eszköz is használható a VT2 által adott parancssorban, de ez nem ajánlott." +msgid "" +"One of these programs will be run by default when you select " +"<guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible " +"to use a different partitioning tool from the command line on VT2, but this " +"is not recommended." +msgstr "" +"E programok egyike indul a <guimenuitem>Lemezek particionálása</guimenuitem> " +"(vagy hasonló) választásakor. Más particionáló eszköz is használható a VT2 " +"által adott parancssorban, de ez nem ajánlott." #. Tag: para #: partitioning.xml:582 #, no-c-format +msgid "Remember to mark your boot partition as <quote>Bootable</quote>." +msgstr "" + +#. Tag: para +#: partitioning.xml:585 +#, no-c-format msgid "" -"If you will be working with more than 20 partitions on your ide disk, you will need to create devices for partitions 21 and beyond. The next step of initializing the partition will fail unless a proper device is present. As an example, here are commands you can use in <userinput>tty2</userinput> or under <guimenuitem>Execute a shell</guimenuitem> to add a device so the 21st partition can be initialized: <informalexample><screen>\n" -"# cd /dev\n" -"# mknod hda21 b 3 21\n" -"# chgrp disk hda21\n" -"# chmod 660 hda21\n" -"</screen></informalexample> Booting into the new system will fail unless proper devices are present on the target system. After installing the kernel and modules, execute: <informalexample><screen>\n" -"# cd /target/dev\n" -"# mknod hda21 b 3 21\n" -"# chgrp disk hda21\n" -"# chmod 660 hda21\n" -"</screen></informalexample> <phrase arch=\"x86\">Remember to mark your boot partition as <quote>Bootable</quote>.</phrase>" -msgstr "" -"Ha több, mint 20 partícióval dolgozol ide lemezeden, a 21. és további partíciókat létre kell hoznod. A partíciók inicializálásának következő lépése sikertelen lesz, ha a megfelelő eszköz nincs jelen. Példaként íme pár a <userinput>tty2</userinput> vagy a <guimenuitem>Héj futtatása</guimenuitem> alól használható parancs egy eszköz hozzáadásához, mellyel a 21. partíció inicializálható lesz: <informalexample><screen>\n" -"# cd /dev\n" -"# mknod hda21 b 3 21\n" -"# chgrp disk hda21\n" -"# chmod 660 hda21\n" -"</screen></informalexample> Az új rendszer indítása meghiúsul, míg a helyes eszközök nincsenek a cél-rendszeren. A kernel és modulok telepítése után futtasd ezt: <informalexample><screen>\n" -"# cd /target/dev\n" -"# mknod hda21 b 3 21\n" -"# chgrp disk hda21\n" -"# chmod 660 hda21\n" -"</screen></informalexample> <phrase arch=\"x86\">Szüksége lehet az indító partíció megjelölése mint <quote>Indítható/Bootable)</quote>.</phrase>" - -#. Tag: para -#: partitioning.xml:601 -#, no-c-format -msgid "One key point when partitioning for Mac type disks is that the swap partition is identified by its name; it must be named <quote>swap</quote>. All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you should take if you are sharing your disk with MacOS." -msgstr "A Mac típusú lemezek particionálásakor fontos, hogy a csere partíció neve alapján kerül azonosításra; <quote>swap</quote> nevet kell neki adni. Minden Mac linux partíció típusa azonos, Apple_UNIX_SRV2. Olvasd el a kézikönyvet. A <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink> elolvasását is ajánljuk, mely szükséges lépéseket tartalmaz, ha a lemezeden a Debian mellett MacOS is lenne." +"One key point when partitioning for Mac type disks is that the swap " +"partition is identified by its name; it must be named <quote>swap</quote>. " +"All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. " +"Please read the fine manual. We also suggest reading the <ulink url=\"&url-" +"mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you " +"should take if you are sharing your disk with MacOS." +msgstr "" +"A Mac típusú lemezek particionálásakor fontos, hogy a csere partíció neve " +"alapján kerül azonosításra; <quote>swap</quote> nevet kell neki adni. Minden " +"Mac linux partíció típusa azonos, Apple_UNIX_SRV2. Olvasd el a kézikönyvet. " +"A <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink> " +"elolvasását is ajánljuk, mely szükséges lépéseket tartalmaz, ha a lemezeden " +"a Debian mellett MacOS is lenne." #. Tag: title -#: partitioning.xml:617 -#: partitioning.xml:678 -#: partitioning.xml:702 -#: partitioning.xml:799 -#: partitioning.xml:913 -#: partitioning.xml:990 +#: partitioning.xml:601 partitioning.xml:662 partitioning.xml:686 +#: partitioning.xml:783 partitioning.xml:897 partitioning.xml:974 #, no-c-format msgid "Partitioning for &arch-title;" msgstr "Particionálás &arch-title; gépen" #. Tag: para -#: partitioning.xml:618 +#: partitioning.xml:602 #, no-c-format -msgid "Booting Debian from the SRM console (the only disk boot method supported by &releasename;) requires you to have a BSD disk label, not a DOS partition table, on your boot disk. (Remember, the SRM boot block is incompatible with MS-DOS partition tables — see <xref linkend=\"alpha-firmware\"/>.) As a result, <command>partman</command> creates BSD disk labels when running on &architecture;, but if your disk has an existing DOS partition table the existing partitions will need to be deleted before <command>partman</command> can convert it to use a disk label." -msgstr "A Debian SRM konzolról indítása (&releasename; által egyedül támogatott lemezről indító módszer) BSD lemez címkét igényel, nem DOS partíciós táblát az indító lemezen. (Az SRM indító blokk inkompatibilis az MS-DOS partíciós táblával — lásd e leírást: <xref linkend=\"alpha-firmware\"/>.) Ezért a <command>partman</command> BSD lemez címkéket hoz létre &architecture; architektúrán, ha a lemezen DOS partíciós tábla van, a létező partíciókat törölni kell, mielőtt a <command>partman</command> egy lemez címke használatára tudja alakítani." +msgid "" +"Booting Debian from the SRM console (the only disk boot method supported by " +"&releasename;) requires you to have a BSD disk label, not a DOS partition " +"table, on your boot disk. (Remember, the SRM boot block is incompatible with " +"MS-DOS partition tables — see <xref linkend=\"alpha-firmware\"/>.) As " +"a result, <command>partman</command> creates BSD disk labels when running on " +"&architecture;, but if your disk has an existing DOS partition table the " +"existing partitions will need to be deleted before <command>partman</" +"command> can convert it to use a disk label." +msgstr "" +"A Debian SRM konzolról indítása (&releasename; által egyedül támogatott " +"lemezről indító módszer) BSD lemez címkét igényel, nem DOS partíciós táblát " +"az indító lemezen. (Az SRM indító blokk inkompatibilis az MS-DOS partíciós " +"táblával — lásd e leírást: <xref linkend=\"alpha-firmware\"/>.) Ezért " +"a <command>partman</command> BSD lemez címkéket hoz létre &architecture; " +"architektúrán, ha a lemezen DOS partíciós tábla van, a létező partíciókat " +"törölni kell, mielőtt a <command>partman</command> egy lemez címke " +"használatára tudja alakítani." #. Tag: para -#: partitioning.xml:629 +#: partitioning.xml:613 #, no-c-format -msgid "If you have chosen to use <command>fdisk</command> to partition your disk, and the disk that you have selected for partitioning does not already contain a BSD disk label, you must use the <quote>b</quote> command to enter disk label mode." -msgstr "Ha az <command>fdisk</command> segítségével particionálsz és a particionálásra jelölt lemez még nem tartalmaz BSD lemez címkét, a <quote>b</quote> parancsot kell lemez címke módba lépéshez használnod." +msgid "" +"If you have chosen to use <command>fdisk</command> to partition your disk, " +"and the disk that you have selected for partitioning does not already " +"contain a BSD disk label, you must use the <quote>b</quote> command to enter " +"disk label mode." +msgstr "" +"Ha az <command>fdisk</command> segítségével particionálsz és a " +"particionálásra jelölt lemez még nem tartalmaz BSD lemez címkét, a <quote>b</" +"quote> parancsot kell lemez címke módba lépéshez használnod." #. Tag: para -#: partitioning.xml:636 +#: partitioning.xml:620 #, no-c-format -msgid "Unless you wish to use the disk you are partitioning from Tru64 Unix or one of the free 4.4BSD-Lite derived operating systems (FreeBSD, OpenBSD, or NetBSD), you should <emphasis>not</emphasis> create the third partition as a <quote>whole disk</quote> partition (i.e. with start and end sectors to span the whole disk), as this renders the disk incompatible with the tools used to make it bootable with aboot. This means that the disk configured by the installer for use as the Debian boot disk will be inaccessible to the operating systems mentioned earlier." +msgid "" +"Unless you wish to use the disk you are partitioning from Tru64 Unix or one " +"of the free 4.4BSD-Lite derived operating systems (FreeBSD, OpenBSD, or " +"NetBSD), you should <emphasis>not</emphasis> create the third partition as a " +"<quote>whole disk</quote> partition (i.e. with start and end sectors to span " +"the whole disk), as this renders the disk incompatible with the tools used " +"to make it bootable with aboot. This means that the disk configured by the " +"installer for use as the Debian boot disk will be inaccessible to the " +"operating systems mentioned earlier." msgstr "" #. Tag: para -#: partitioning.xml:648 +#: partitioning.xml:632 #, no-c-format -msgid "Also, because <command>aboot</command> is written to the first few sectors of the disk (currently it occupies about 70 kilobytes, or 150 sectors), you <emphasis>must</emphasis> leave enough empty space at the beginning of the disk for it. In the past, it was suggested that you make a small partition at the beginning of the disk, to be left unformatted. For the same reason mentioned above, we now suggest that you do not do this on disks that will only be used by GNU/Linux. When using <command>partman</command>, a small partition will still be created for <command>aboot</command> for convenience reasons." +msgid "" +"Also, because <command>aboot</command> is written to the first few sectors " +"of the disk (currently it occupies about 70 kilobytes, or 150 sectors), you " +"<emphasis>must</emphasis> leave enough empty space at the beginning of the " +"disk for it. In the past, it was suggested that you make a small partition " +"at the beginning of the disk, to be left unformatted. For the same reason " +"mentioned above, we now suggest that you do not do this on disks that will " +"only be used by GNU/Linux. When using <command>partman</command>, a small " +"partition will still be created for <command>aboot</command> for convenience " +"reasons." msgstr "" #. Tag: para -#: partitioning.xml:660 +#: partitioning.xml:644 #, no-c-format -msgid "For ARC installations, you should make a small FAT partition at the beginning of the disk to contain <command>MILO</command> and <command>linload.exe</command> — 5 megabytes should be sufficient, see <xref linkend=\"non-debian-partitioning\"/>. Unfortunately, making FAT file systems from the menu is not yet supported, so you'll have to do it manually from the shell using <command>mkdosfs</command> before attempting to install the boot loader." +msgid "" +"For ARC installations, you should make a small FAT partition at the " +"beginning of the disk to contain <command>MILO</command> and " +"<command>linload.exe</command> — 5 megabytes should be sufficient, see " +"<xref linkend=\"non-debian-partitioning\"/>. Unfortunately, making FAT file " +"systems from the menu is not yet supported, so you'll have to do it manually " +"from the shell using <command>mkdosfs</command> before attempting to install " +"the boot loader." msgstr "" #. Tag: para -#: partitioning.xml:679 +#: partitioning.xml:663 #, no-c-format -msgid "PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere in the first 2GB. This is where the boot loader and an optional kernel and RAMdisk will be stored, so make it big enough for that — at least 4Mb (I like 8–16MB). An additional requirement of the firmware is that the Linux kernel must reside within the first 2GB of the disk. This is typically achieved by making the root ext2 partition fit entirely within the first 2GB of the disk. Alternatively you can create a small ext2 partition near the start of the disk and mount that on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. <filename>/boot</filename> needs to be big enough to hold whatever kernels (and backups) you might wish to load; 25–50MB is generally sufficient." +msgid "" +"PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> " +"somewhere in the first 2GB. This is where the boot loader and an optional " +"kernel and RAMdisk will be stored, so make it big enough for that — at " +"least 4Mb (I like 8–16MB). An additional requirement of the firmware " +"is that the Linux kernel must reside within the first 2GB of the disk. This " +"is typically achieved by making the root ext2 partition fit entirely within " +"the first 2GB of the disk. Alternatively you can create a small ext2 " +"partition near the start of the disk and mount that on <filename>/boot</" +"filename>, since that is the directory where the Linux kernel(s) will be " +"stored. <filename>/boot</filename> needs to be big enough to hold whatever " +"kernels (and backups) you might wish to load; 25–50MB is generally " +"sufficient." msgstr "" #. Tag: para -#: partitioning.xml:703 +#: partitioning.xml:687 #, no-c-format -msgid "If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing Debian, you may need to resize its partition to free up space for the Debian installation. The installer supports resizing of both FAT and NTFS filesystems; when you get to the installer's partitioning step, select the option <guimenuitem>Manual</guimenuitem> and then simply select an existing partition and change its size." -msgstr "Ha van egy létező rendszered, netán DOS vagy Windows és valamiért meg akarnád őrizni őket, miközben már a Debian rendszert telepíted, biztosítanod kell, akár a partíciók átméretezésével a szabad helyet a Debian telepítésének. A telepítő támogatja a FAT és NTFS fájlrendszerek átméretezését is; a telepítő particionálójába lépve válaszd a <guimenuitem>Kézi szerkesztés</guimenuitem> lehetőséget, egyszerűen jelölj ki egy létező partíciót és változtasd meg méretét." +msgid "" +"If you have an existing other operating system such as DOS or Windows and " +"you want to preserve that operating system while installing Debian, you may " +"need to resize its partition to free up space for the Debian installation. " +"The installer supports resizing of both FAT and NTFS filesystems; when you " +"get to the installer's partitioning step, select the option " +"<guimenuitem>Manual</guimenuitem> and then simply select an existing " +"partition and change its size." +msgstr "" +"Ha van egy létező rendszered, netán DOS vagy Windows és valamiért meg " +"akarnád őrizni őket, miközben már a Debian rendszert telepíted, biztosítanod " +"kell, akár a partíciók átméretezésével a szabad helyet a Debian " +"telepítésének. A telepítő támogatja a FAT és NTFS fájlrendszerek " +"átméretezését is; a telepítő particionálójába lépve válaszd a " +"<guimenuitem>Kézi szerkesztés</guimenuitem> lehetőséget, egyszerűen jelölj " +"ki egy létező partíciót és változtasd meg méretét." #. Tag: para -#: partitioning.xml:713 +#: partitioning.xml:697 #, no-c-format -msgid "The PC BIOS generally adds additional constraints for disk partitioning. There is a limit to how many <quote>primary</quote> and <quote>logical</quote> partitions a drive can contain. Additionally, with pre 1994–98 BIOSes, there are limits to where on the drive the BIOS can boot from. More information can be found in the <ulink url=\"&url-partition-howto;\">Linux Partition HOWTO</ulink> and the <ulink url=\"&url-phoenix-bios-faq-large-disk;\">Phoenix BIOS FAQ</ulink>, but this section will include a brief overview to help you plan most situations." -msgstr "A PC BIOS általában további kikötéseket ad a lemez particionáláshoz. Korlátolt, hány <quote>elsődleges</quote> és <quote>logikai</quote> partíció lehet egy meghajtón. Ráadásul az 1994–98 előtti BIOSok esetén, korlátolt, a meghajtó mely részéről tud a BIOS indítani. Több adat a <ulink url=\"&url-partition-howto;\">Linux Partíció HOGYAN</ulink> és <ulink url=\"&url-phoenix-bios-faq-large-disk;\">Phoenix BIOS GYIK</ulink> leírásban, de a szakasz rövid leírásban a legtöbb esetre segíti a tervezést." +msgid "" +"The PC BIOS generally adds additional constraints for disk partitioning. " +"There is a limit to how many <quote>primary</quote> and <quote>logical</" +"quote> partitions a drive can contain. Additionally, with pre 1994–98 " +"BIOSes, there are limits to where on the drive the BIOS can boot from. More " +"information can be found in the <ulink url=\"&url-partition-howto;\">Linux " +"Partition HOWTO</ulink> and the <ulink url=\"&url-phoenix-bios-faq-large-" +"disk;\">Phoenix BIOS FAQ</ulink>, but this section will include a brief " +"overview to help you plan most situations." +msgstr "" +"A PC BIOS általában további kikötéseket ad a lemez particionáláshoz. " +"Korlátolt, hány <quote>elsődleges</quote> és <quote>logikai</quote> partíció " +"lehet egy meghajtón. Ráadásul az 1994–98 előtti BIOSok esetén, " +"korlátolt, a meghajtó mely részéről tud a BIOS indítani. Több adat a <ulink " +"url=\"&url-partition-howto;\">Linux Partíció HOGYAN</ulink> és <ulink url=" +"\"&url-phoenix-bios-faq-large-disk;\">Phoenix BIOS GYIK</ulink> leírásban, " +"de a szakasz rövid leírásban a legtöbb esetre segíti a tervezést." #. Tag: para -#: partitioning.xml:724 +#: partitioning.xml:708 #, no-c-format -msgid "<quote>Primary</quote> partitions are the original partitioning scheme for PC disks. However, there can only be four of them. To get past this limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By setting one of your primary partitions as an extended partition, you can subdivide all the space allocated to that partition into logical partitions. You can create up to 60 logical partitions per extended partition; however, you can only have one extended partition per drive." -msgstr "Az <quote>elsődleges</quote>partíciók a PC lemezek eredeti particionáló sémája. Ebből csak 4 lehet. E korlátok átlépésére születtek a <quote>kiterjesztett</quote> és <quote>logikai</quote> partíciók. Egy elsődleges partíció kiterjesztettre állításával e partícióhoz lefoglalt teljes terület logikai partíciókra osztható. Kiterjesztett partíciónként 60 logikai partíció hozható létre; viszont meghajtónként csak 1 kiterjesztett partíció lehet." +msgid "" +"<quote>Primary</quote> partitions are the original partitioning scheme for " +"PC disks. However, there can only be four of them. To get past this " +"limitation, <quote>extended</quote> and <quote>logical</quote> partitions " +"were invented. By setting one of your primary partitions as an extended " +"partition, you can subdivide all the space allocated to that partition into " +"logical partitions. You can create up to 60 logical partitions per extended " +"partition; however, you can only have one extended partition per drive." +msgstr "" +"Az <quote>elsődleges</quote>partíciók a PC lemezek eredeti particionáló " +"sémája. Ebből csak 4 lehet. E korlátok átlépésére születtek a " +"<quote>kiterjesztett</quote> és <quote>logikai</quote> partíciók. Egy " +"elsődleges partíció kiterjesztettre állításával e partícióhoz lefoglalt " +"teljes terület logikai partíciókra osztható. Kiterjesztett partíciónként 60 " +"logikai partíció hozható létre; viszont meghajtónként csak 1 kiterjesztett " +"partíció lehet." #. Tag: para -#: partitioning.xml:735 +#: partitioning.xml:719 #, no-c-format -msgid "Linux limits the partitions per drive to 15 partitions for SCSI disks (3 usable primary partitions, 12 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions." -msgstr "A Linux a meghajtónként partíciók számát 15 partícióra korlátozza SCSI lemezeknél (3 használható elsődleges és 12 logikai) és 63 partícióra IDE meghajtón (3 használható elsődleges és 60 logikai). De a &debian; rendszer csak 20 eszközt rendel partíciókhoz, így telepítésre 20 partíciót használhatsz míg nem hozol előbb létre eszközöket továbbiakhoz." +msgid "" +"Linux limits the partitions per drive to 15 partitions for SCSI disks (3 " +"usable primary partitions, 12 logical partitions), and 63 partitions on an " +"IDE drive (3 usable primary partitions, 60 logical partitions). However the " +"normal &debian; system provides only 20 devices for partitions, so you may " +"not install on partitions higher than 20 unless you first manually create " +"devices for those partitions." +msgstr "" +"A Linux a meghajtónként partíciók számát 15 partícióra korlátozza SCSI " +"lemezeknél (3 használható elsődleges és 12 logikai) és 63 partícióra IDE " +"meghajtón (3 használható elsődleges és 60 logikai). De a &debian; rendszer " +"csak 20 eszközt rendel partíciókhoz, így telepítésre 20 partíciót " +"használhatsz míg nem hozol előbb létre eszközöket továbbiakhoz." #. Tag: para -#: partitioning.xml:745 +#: partitioning.xml:729 #, no-c-format -msgid "If you have a large IDE disk, and are using neither LBA addressing, nor overlay drivers (sometimes provided by hard disk manufacturers), then the boot partition (the partition containing your kernel image) must be placed within the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation)." -msgstr "Nagy IDE lemez esetén, ha nem használsz sem LBA címzést sem átlapoló meghajtókat (néha merevlemez-gyártók adják), az indító partíció (a kernel képet tartalmazó partíció) a merevlemez 1. 1024 cilinderén kell legyen (általában mintegy 524 MB BIOS általi áthelyezés nélkül)." +msgid "" +"If you have a large IDE disk, and are using neither LBA addressing, nor " +"overlay drivers (sometimes provided by hard disk manufacturers), then the " +"boot partition (the partition containing your kernel image) must be placed " +"within the first 1024 cylinders of your hard drive (usually around 524 " +"megabytes, without BIOS translation)." +msgstr "" +"Nagy IDE lemez esetén, ha nem használsz sem LBA címzést sem átlapoló " +"meghajtókat (néha merevlemez-gyártók adják), az indító partíció (a kernel " +"képet tartalmazó partíció) a merevlemez 1. 1024 cilinderén kell legyen " +"(általában mintegy 524 MB BIOS általi áthelyezés nélkül)." #. Tag: para -#: partitioning.xml:753 +#: partitioning.xml:737 #, no-c-format -msgid "This restriction doesn't apply if you have a BIOS newer than around 1995–98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and Debian's alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once Linux is booted, no matter what BIOS your computer has, these restrictions no longer apply, since Linux does not use the BIOS for disk access." -msgstr "Ezt már meghaladja minden (gyártótól függően) 1995–98 utáni BIOS, mely már támogatja a <quote>Javított lemez meghajtó támogatás specifikáció</quote>-t. A Lilo, a Linux betöltő nevű program és a Debian alatti <command>mbr</command> program számára is szükséges a BIOS használata a kernel a lemezről a RAM-ba olvasásához. Ha a BIOS 0x13 nagy lemez-elérő kiterjesztések elérhetők, ezeket fogják használni. Ha nem, akkor az elavult lemez-elérő felület, mely nem használható az 1023. cilinder felett. A Linux indulása után a BIOS többé nem számít, a Linux nem használja BIOS-t a lemez-eléréshez sem." +msgid "" +"This restriction doesn't apply if you have a BIOS newer than around " +"1995–98 (depending on the manufacturer) that supports the " +"<quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the " +"Linux loader, and Debian's alternative <command>mbr</command> must use the " +"BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large " +"disk access extensions are found to be present, they will be utilized. " +"Otherwise, the legacy disk access interface is used as a fall-back, and it " +"cannot be used to address any location on the disk higher than the 1023rd " +"cylinder. Once Linux is booted, no matter what BIOS your computer has, these " +"restrictions no longer apply, since Linux does not use the BIOS for disk " +"access." +msgstr "" +"Ezt már meghaladja minden (gyártótól függően) 1995–98 utáni BIOS, " +"mely már támogatja a <quote>Javított lemez meghajtó támogatás specifikáció</" +"quote>-t. A Lilo, a Linux betöltő nevű program és a Debian alatti " +"<command>mbr</command> program számára is szükséges a BIOS használata a " +"kernel a lemezről a RAM-ba olvasásához. Ha a BIOS 0x13 nagy lemez-elérő " +"kiterjesztések elérhetők, ezeket fogják használni. Ha nem, akkor az elavult " +"lemez-elérő felület, mely nem használható az 1023. cilinder felett. A Linux " +"indulása után a BIOS többé nem számít, a Linux nem használja BIOS-t a lemez-" +"eléréshez sem." #. Tag: para -#: partitioning.xml:767 +#: partitioning.xml:751 #, no-c-format -msgid "If you have a large disk, you might have to use cylinder translation techniques, which you can set from your BIOS setup program, such as LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). More information about issues with large disks can be found in the <ulink url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a cylinder translation scheme, and the BIOS does not support the large disk access extensions, then your boot partition has to fit within the <emphasis>translated</emphasis> representation of the 1024th cylinder." -msgstr "Nagy lemezekhez cilinder áthelyező technikát kell alkalmazni, mely a BIOS beállításban van, például LBA (logikai blokk címzés) vagy CHS áthelyező mód (<quote>Large</quote>). A nagy lemezekről szóló tudnivalók a <ulink url=\"&url-large-disk-howto;\">Nagy lemezek HOGYAN</ulink> leírásban vannak. Cilinder áthelyező séma esetén, ha a BIOS nem támogatja a nagy lemez-elérés kiterjesztéseket, az indító partíció az 1024. cilinder <emphasis>áthelyezett</emphasis> megfelelőjében kell legyen." +msgid "" +"If you have a large disk, you might have to use cylinder translation " +"techniques, which you can set from your BIOS setup program, such as LBA " +"(Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). " +"More information about issues with large disks can be found in the <ulink " +"url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a " +"cylinder translation scheme, and the BIOS does not support the large disk " +"access extensions, then your boot partition has to fit within the " +"<emphasis>translated</emphasis> representation of the 1024th cylinder." +msgstr "" +"Nagy lemezekhez cilinder áthelyező technikát kell alkalmazni, mely a BIOS " +"beállításban van, például LBA (logikai blokk címzés) vagy CHS áthelyező mód " +"(<quote>Large</quote>). A nagy lemezekről szóló tudnivalók a <ulink url=" +"\"&url-large-disk-howto;\">Nagy lemezek HOGYAN</ulink> leírásban vannak. " +"Cilinder áthelyező séma esetén, ha a BIOS nem támogatja a nagy lemez-elérés " +"kiterjesztéseket, az indító partíció az 1024. cilinder " +"<emphasis>áthelyezett</emphasis> megfelelőjében kell legyen." #. Tag: para -#: partitioning.xml:779 +#: partitioning.xml:763 #, no-c-format -msgid "The recommended way of accomplishing this is to create a small (25–50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions." -msgstr "Ennek teljesítésének ajánlott módja egy kis (25–50MB elég lehet) partíció létrehozása az indító partícióra használt lemez elején és más partíciók létrehozása a fennmaradó területen. Az indító partíciót <emphasis>kötelező</emphasis> a <filename>/boot</filename> könyvtárba csatolni, mivel ez a Linux kernel(ek) helye. Ez esetben az lehet az előny, hogy e konfiguráció a legvégső esetben a legrégebbi rendszereken is működik függetlenül az LBA vagy nagy lemez CHS áthelyezéstől és még attól is, hogy az elavult BIOS támogatja-e a nagy lemez-elérés kiterjesztéseket." +msgid "" +"The recommended way of accomplishing this is to create a small " +"(25–50MB should suffice) partition at the beginning of the disk to be " +"used as the boot partition, and then create whatever other partitions you " +"wish to have, in the remaining area. This boot partition <emphasis>must</" +"emphasis> be mounted on <filename>/boot</filename>, since that is the " +"directory where the Linux kernel(s) will be stored. This configuration will " +"work on any system, regardless of whether LBA or large disk CHS translation " +"is used, and regardless of whether your BIOS supports the large disk access " +"extensions." +msgstr "" +"Ennek teljesítésének ajánlott módja egy kis (25–50MB elég lehet) " +"partíció létrehozása az indító partícióra használt lemez elején és más " +"partíciók létrehozása a fennmaradó területen. Az indító partíciót " +"<emphasis>kötelező</emphasis> a <filename>/boot</filename> könyvtárba " +"csatolni, mivel ez a Linux kernel(ek) helye. Ez esetben az lehet az előny, " +"hogy e konfiguráció a legvégső esetben a legrégebbi rendszereken is működik " +"függetlenül az LBA vagy nagy lemez CHS áthelyezéstől és még attól is, hogy " +"az elavult BIOS támogatja-e a nagy lemez-elérés kiterjesztéseket." #. Tag: para -#: partitioning.xml:800 +#: partitioning.xml:784 #, no-c-format -msgid "The <command>partman</command> disk partitioner is the default partitioning tool for the installer. It manages the set of partitions and their mount points to ensure that the disks and filesystems are properly configured for a successful installation. It actually uses <command>parted</command> to do the on-disk partitioning." +msgid "" +"The <command>partman</command> disk partitioner is the default partitioning " +"tool for the installer. It manages the set of partitions and their mount " +"points to ensure that the disks and filesystems are properly configured for " +"a successful installation. It actually uses <command>parted</command> to do " +"the on-disk partitioning." msgstr "" #. Tag: title -#: partitioning.xml:812 +#: partitioning.xml:796 #, no-c-format msgid "EFI Recognized Formats" msgstr "" #. Tag: para -#: partitioning.xml:813 +#: partitioning.xml:797 #, no-c-format -msgid "The IA64 EFI firmware supports two partition table (or disk label) formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer recommended for IA64 systems. Although the installer also provides <command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly." +msgid "" +"The IA64 EFI firmware supports two partition table (or disk label) formats, " +"GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer " +"recommended for IA64 systems. Although the installer also provides " +"<command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> " +"<command>parted</command></ulink> because only it can manage both GPT and MS-" +"DOS tables correctly." msgstr "" #. Tag: para -#: partitioning.xml:825 +#: partitioning.xml:809 #, no-c-format -msgid "The automatic partitioning recipes for <command>partman</command> allocate an EFI partition as the first partition on the disk. You can also set up the partition under the <guimenuitem>Guided partitioning</guimenuitem> from the main menu in a manner similar to setting up a <emphasis>swap</emphasis> partition." +msgid "" +"The automatic partitioning recipes for <command>partman</command> allocate " +"an EFI partition as the first partition on the disk. You can also set up the " +"partition under the <guimenuitem>Guided partitioning</guimenuitem> from the " +"main menu in a manner similar to setting up a <emphasis>swap</emphasis> " +"partition." msgstr "" #. Tag: para -#: partitioning.xml:833 +#: partitioning.xml:817 #, no-c-format msgid "" -"The <command>partman</command> partitioner will handle most disk layouts. For those rare cases where it is necessary to manually set up a disk, you can use the shell as described above and run the <command>parted</command> utility directly using its command line interface. Assuming that you want to erase your whole disk and create a GPT table and some partitions, then something similar to the following command sequence could be used: <informalexample><screen>\n" +"The <command>partman</command> partitioner will handle most disk layouts. " +"For those rare cases where it is necessary to manually set up a disk, you " +"can use the shell as described above and run the <command>parted</command> " +"utility directly using its command line interface. Assuming that you want to " +"erase your whole disk and create a GPT table and some partitions, then " +"something similar to the following command sequence could be used: " +"<informalexample><screen>\n" " mklabel gpt\n" " mkpartfs primary fat 0 50\n" " mkpartfs primary linux-swap 51 1000\n" @@ -795,102 +1362,228 @@ msgid "" " set 1 boot on\n" " print\n" " quit\n" -"</screen></informalexample> This creates a new partition table, and three partitions to be used as an EFI boot partition, swap space, and a root file system. Finally it sets the boot flag on the EFI partition. Partitions are specified in Megabytes, with start and end offsets from the beginning of the disk. So, for example, above we created a 1999MB ext2 file system starting at offset 1001MB from the start of the disk. Note that formatting swap space with <command>parted</command> can take a few minutes to complete, as it scans the partition for bad blocks." +"</screen></informalexample> This creates a new partition table, and three " +"partitions to be used as an EFI boot partition, swap space, and a root file " +"system. Finally it sets the boot flag on the EFI partition. Partitions are " +"specified in Megabytes, with start and end offsets from the beginning of the " +"disk. So, for example, above we created a 1999MB ext2 file system starting " +"at offset 1001MB from the start of the disk. Note that formatting swap space " +"with <command>parted</command> can take a few minutes to complete, as it " +"scans the partition for bad blocks." msgstr "" #. Tag: title -#: partitioning.xml:858 +#: partitioning.xml:842 #, no-c-format msgid "Boot Loader Partition Requirements" msgstr "" #. Tag: para -#: partitioning.xml:859 +#: partitioning.xml:843 #, no-c-format -msgid "ELILO, the ia64 boot loader, requires a partition containing a FAT file system with the <userinput>boot</userinput> flag set. The partition must be big enough to hold the boot loader and any kernels or RAMdisks you may wish to boot. A minimum size would be about 20MB, but if you expect to run with multiple kernels, then 128MB might be a better size." +msgid "" +"ELILO, the ia64 boot loader, requires a partition containing a FAT file " +"system with the <userinput>boot</userinput> flag set. The partition must be " +"big enough to hold the boot loader and any kernels or RAMdisks you may wish " +"to boot. A minimum size would be about 20MB, but if you expect to run with " +"multiple kernels, then 128MB might be a better size." msgstr "" #. Tag: para -#: partitioning.xml:868 +#: partitioning.xml:852 #, no-c-format -msgid "The EFI Boot Manager and the EFI Shell fully support the GPT table so the boot partition does not necessarily have to be the first partition or even on the same disk. This is convenient if you should forget to allocate the partition and only find out after you have formatted the other partitions on your disk(s). The <command>partman</command> partitioner checks for an EFI partition at the same time it checks for a properly set up <emphasis>root</emphasis> partition. This gives you an opportunity to correct the disk layout before the package install begins. The easiest way to correct this omission is to shrink the last partition of the disk to make enough free space for adding an EFI partition." +msgid "" +"The EFI Boot Manager and the EFI Shell fully support the GPT table so the " +"boot partition does not necessarily have to be the first partition or even " +"on the same disk. This is convenient if you should forget to allocate the " +"partition and only find out after you have formatted the other partitions on " +"your disk(s). The <command>partman</command> partitioner checks for an EFI " +"partition at the same time it checks for a properly set up <emphasis>root</" +"emphasis> partition. This gives you an opportunity to correct the disk " +"layout before the package install begins. The easiest way to correct this " +"omission is to shrink the last partition of the disk to make enough free " +"space for adding an EFI partition." msgstr "" #. Tag: para -#: partitioning.xml:883 +#: partitioning.xml:867 #, no-c-format -msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem." +msgid "" +"It is strongly recommended that you allocate the EFI boot partition on the " +"same disk as the <emphasis>root</emphasis> filesystem." msgstr "" #. Tag: title -#: partitioning.xml:891 +#: partitioning.xml:875 #, no-c-format msgid "EFI Diagnostic Partitions" msgstr "" #. Tag: para -#: partitioning.xml:892 +#: partitioning.xml:876 #, no-c-format -msgid "The EFI firmware is significantly more sophisticated than the usual BIOS seen on most x86 PCs. Some system vendors take advantage of the ability of the EFI to access files and run programs from a hard disk filesystem to store diagnostics and EFI based system management utilities on the hard disk. This is a separate FAT format filesystem on the system disk. Consult the system documentation and accessories that come with the system for details. The easiest time to set up a diagnostics partition is at the same time you set up the EFI boot partition." +msgid "" +"The EFI firmware is significantly more sophisticated than the usual BIOS " +"seen on most x86 PCs. Some system vendors take advantage of the ability of " +"the EFI to access files and run programs from a hard disk filesystem to " +"store diagnostics and EFI based system management utilities on the hard " +"disk. This is a separate FAT format filesystem on the system disk. Consult " +"the system documentation and accessories that come with the system for " +"details. The easiest time to set up a diagnostics partition is at the same " +"time you set up the EFI boot partition." msgstr "" #. Tag: para -#: partitioning.xml:914 +#: partitioning.xml:898 #, no-c-format -msgid "SGI machines require an SGI disk label in order to make the system bootable from hard disk. It can be created in the fdisk expert menu. The thereby created volume header (partition number 9) should be at least 3MB large. If the volume header created is too small, you can simply delete partition number 9 and re-add it with a different size. Note that the volume header must start at sector 0." +msgid "" +"SGI machines require an SGI disk label in order to make the system bootable " +"from hard disk. It can be created in the fdisk expert menu. The thereby " +"created volume header (partition number 9) should be at least 3MB large. If " +"the volume header created is too small, you can simply delete partition " +"number 9 and re-add it with a different size. Note that the volume header " +"must start at sector 0." msgstr "" #. Tag: title -#: partitioning.xml:931 +#: partitioning.xml:915 #, no-c-format msgid "Partitioning Newer PowerMacs" msgstr "" #. Tag: para -#: partitioning.xml:932 +#: partitioning.xml:916 #, no-c-format -msgid "If you are installing onto a NewWorld PowerMac you must create a special bootstrap partition to hold the boot loader. The size of this partition must be 800KB and its partition type must be <emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not created with the <emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made bootable from the hard disk. This partition can easily be created by creating a new partition in <command>partman</command> and telling it to use it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</command> using the <userinput>b</userinput> command." +msgid "" +"If you are installing onto a NewWorld PowerMac you must create a special " +"bootstrap partition to hold the boot loader. The size of this partition must " +"be 800KB and its partition type must be <emphasis>Apple_Bootstrap</" +"emphasis>. If the bootstrap partition is not created with the " +"<emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made " +"bootable from the hard disk. This partition can easily be created by " +"creating a new partition in <command>partman</command> and telling it to use " +"it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</" +"command> using the <userinput>b</userinput> command." msgstr "" #. Tag: para -#: partitioning.xml:945 +#: partitioning.xml:929 #, no-c-format -msgid "The special partition type Apple_Bootstrap is required to prevent MacOS from mounting and damaging the bootstrap partition, as there are special modifications made to it in order for OpenFirmware to boot it automatically." +msgid "" +"The special partition type Apple_Bootstrap is required to prevent MacOS from " +"mounting and damaging the bootstrap partition, as there are special " +"modifications made to it in order for OpenFirmware to boot it automatically." msgstr "" #. Tag: para -#: partitioning.xml:952 +#: partitioning.xml:936 #, no-c-format -msgid "Note that the bootstrap partition is only meant to hold 3 very small files: the <command>yaboot</command> binary, its configuration <filename>yaboot.conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</command>. It need not and must not be mounted on your file system nor have kernels or anything else copied to it. The <command>ybin</command> and <command>mkofboot</command> utilities are used to manipulate this partition." +msgid "" +"Note that the bootstrap partition is only meant to hold 3 very small files: " +"the <command>yaboot</command> binary, its configuration <filename>yaboot." +"conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</" +"command>. It need not and must not be mounted on your file system nor have " +"kernels or anything else copied to it. The <command>ybin</command> and " +"<command>mkofboot</command> utilities are used to manipulate this partition." msgstr "" #. Tag: para -#: partitioning.xml:962 +#: partitioning.xml:946 #, no-c-format -msgid "In order for OpenFirmware to automatically boot &debian; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts." +msgid "" +"In order for OpenFirmware to automatically boot &debian; the bootstrap " +"partition should appear before other boot partitions on the disk, especially " +"MacOS boot partitions. The bootstrap partition should be the first one you " +"create. However, if you add a bootstrap partition later, you can use " +"<command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder " +"the partition map so the bootstrap partition comes right after the map " +"(which is always partition 1). It's the logical map order, not the physical " +"address order, that counts." msgstr "" #. Tag: para -#: partitioning.xml:974 +#: partitioning.xml:958 #, no-c-format -msgid "Apple disks normally have several small driver partitions. If you intend to dual boot your machine with MacOSX, you should retain these partitions and a small HFS partition (800k is the minimum size). That is because MacOSX, on every boot, offers to initialize any disks which do not have active MacOS partitions and driver partitions." +msgid "" +"Apple disks normally have several small driver partitions. If you intend to " +"dual boot your machine with MacOSX, you should retain these partitions and a " +"small HFS partition (800k is the minimum size). That is because MacOSX, on " +"every boot, offers to initialize any disks which do not have active MacOS " +"partitions and driver partitions." msgstr "" #. Tag: para -#: partitioning.xml:991 +#: partitioning.xml:975 #, no-c-format -msgid "Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. The <keycap>s</keycap> key is used in <command>fdisk</command> to create Sun disk labels." +msgid "" +"Make sure you create a <quote>Sun disk label</quote> on your boot disk. This " +"is the only kind of partition scheme that the OpenBoot PROM understands, and " +"so it's the only scheme from which you can boot. The <keycap>s</keycap> key " +"is used in <command>fdisk</command> to create Sun disk labels." msgstr "" #. Tag: para -#: partitioning.xml:999 +#: partitioning.xml:983 #, no-c-format -msgid "Furthermore, on &arch-title; disks, make sure your first partition on your boot disk starts at cylinder 0. While this is required, it also means that the first partition will contain the partition table and the boot block, which are the first two sectors of the disk. You must <emphasis>not</emphasis> put swap on the first partition of the boot drive, since swap partitions do not preserve the first few sectors of the partition. You can put Ext2 or UFS partitions there; these will leave the partition table and the boot block alone." +msgid "" +"Furthermore, on &arch-title; disks, make sure your first partition on your " +"boot disk starts at cylinder 0. While this is required, it also means that " +"the first partition will contain the partition table and the boot block, " +"which are the first two sectors of the disk. You must <emphasis>not</" +"emphasis> put swap on the first partition of the boot drive, since swap " +"partitions do not preserve the first few sectors of the partition. You can " +"put Ext2 or UFS partitions there; these will leave the partition table and " +"the boot block alone." msgstr "" #. Tag: para -#: partitioning.xml:1010 +#: partitioning.xml:994 #, no-c-format -msgid "It is also advised that the third partition should be of type <quote>Whole disk</quote> (type 5), and contain the entire disk (from the first cylinder to the last). This is simply a convention of Sun disk labels, and helps the <command>SILO</command> boot loader keep its bearings." +msgid "" +"It is also advised that the third partition should be of type <quote>Whole " +"disk</quote> (type 5), and contain the entire disk (from the first cylinder " +"to the last). This is simply a convention of Sun disk labels, and helps the " +"<command>SILO</command> boot loader keep its bearings." msgstr "" +#~ msgid "" +#~ "If you will be working with more than 20 partitions on your ide disk, you " +#~ "will need to create devices for partitions 21 and beyond. The next step " +#~ "of initializing the partition will fail unless a proper device is " +#~ "present. As an example, here are commands you can use in <userinput>tty2</" +#~ "userinput> or under <guimenuitem>Execute a shell</guimenuitem> to add a " +#~ "device so the 21st partition can be initialized: " +#~ "<informalexample><screen>\n" +#~ "# cd /dev\n" +#~ "# mknod hda21 b 3 21\n" +#~ "# chgrp disk hda21\n" +#~ "# chmod 660 hda21\n" +#~ "</screen></informalexample> Booting into the new system will fail unless " +#~ "proper devices are present on the target system. After installing the " +#~ "kernel and modules, execute: <informalexample><screen>\n" +#~ "# cd /target/dev\n" +#~ "# mknod hda21 b 3 21\n" +#~ "# chgrp disk hda21\n" +#~ "# chmod 660 hda21\n" +#~ "</screen></informalexample> <phrase arch=\"x86\">Remember to mark your " +#~ "boot partition as <quote>Bootable</quote>.</phrase>" +#~ msgstr "" +#~ "Ha több, mint 20 partícióval dolgozol ide lemezeden, a 21. és további " +#~ "partíciókat létre kell hoznod. A partíciók inicializálásának következő " +#~ "lépése sikertelen lesz, ha a megfelelő eszköz nincs jelen. Példaként íme " +#~ "pár a <userinput>tty2</userinput> vagy a <guimenuitem>Héj futtatása</" +#~ "guimenuitem> alól használható parancs egy eszköz hozzáadásához, mellyel a " +#~ "21. partíció inicializálható lesz: <informalexample><screen>\n" +#~ "# cd /dev\n" +#~ "# mknod hda21 b 3 21\n" +#~ "# chgrp disk hda21\n" +#~ "# chmod 660 hda21\n" +#~ "</screen></informalexample> Az új rendszer indítása meghiúsul, míg a " +#~ "helyes eszközök nincsenek a cél-rendszeren. A kernel és modulok " +#~ "telepítése után futtasd ezt: <informalexample><screen>\n" +#~ "# cd /target/dev\n" +#~ "# mknod hda21 b 3 21\n" +#~ "# chgrp disk hda21\n" +#~ "# chmod 660 hda21\n" +#~ "</screen></informalexample> <phrase arch=\"x86\">Szüksége lehet az indító " +#~ "partíció megjelölése mint <quote>Indítható/Bootable)</quote>.</phrase>" diff --git a/po/hu/random-bits.po b/po/hu/random-bits.po index 863e720b3..111fd2364 100644 --- a/po/hu/random-bits.po +++ b/po/hu/random-bits.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-10-11 02:03+0000\n" +"POT-Creation-Date: 2006-10-29 14:49+0000\n" "PO-Revision-Date: 2006-10-09 11:19+0100\n" "Last-Translator: SZERVÁC Attila <sas@321.hu>\n" "Language-Team: Hungarian\n" @@ -411,12 +411,13 @@ msgstr "" #: random-bits.xml:189 #, no-c-format msgid "" -"The base installation for i386 using the default 2.4 kernel, including all " -"standard packages, requires 573MB of disk space." +"The base installation for i386 using the default 2.6 kernel, including all " +"standard packages, requires 585MB of disk space. A minimal base " +"installation, without the standard task selected, will take 365MB." msgstr "" #. Tag: para -#: random-bits.xml:194 +#: random-bits.xml:196 #, no-c-format msgid "" "The following table lists sizes reported by aptitude for the tasks listed in " @@ -426,7 +427,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:201 +#: random-bits.xml:203 #, no-c-format msgid "" "Note that you will need to add the sizes listed in the table to the size of " @@ -437,201 +438,225 @@ msgid "" msgstr "" #. Tag: entry -#: random-bits.xml:214 +#: random-bits.xml:216 #, no-c-format msgid "Task" msgstr "" #. Tag: entry -#: random-bits.xml:215 +#: random-bits.xml:217 #, no-c-format msgid "Installed size (MB)" msgstr "" #. Tag: entry -#: random-bits.xml:216 +#: random-bits.xml:218 #, no-c-format msgid "Download size (MB)" msgstr "" #. Tag: entry -#: random-bits.xml:217 +#: random-bits.xml:219 #, no-c-format msgid "Space needed to install (MB)" msgstr "" #. Tag: entry -#: random-bits.xml:223 +#: random-bits.xml:225 #, no-c-format msgid "Desktop" msgstr "" #. Tag: entry -#: random-bits.xml:224 +#: random-bits.xml:226 #, no-c-format -msgid "1392" +msgid "1258" msgstr "" #. Tag: entry -#: random-bits.xml:225 +#: random-bits.xml:227 #, no-c-format -msgid "<entry>460</entry>" +msgid "<entry>418</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:226 +#: random-bits.xml:228 #, no-c-format -msgid "1852" +msgid "1676" msgstr "" #. Tag: entry -#: random-bits.xml:230 +#: random-bits.xml:232 #, no-c-format -msgid "Web server" +msgid "Laptop" msgstr "" #. Tag: entry -#: random-bits.xml:231 +#: random-bits.xml:233 random-bits.xml:242 #, no-c-format -msgid "<entry>36</entry>" +msgid "<entry>46</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:232 +#: random-bits.xml:234 #, no-c-format -msgid "<entry>12</entry>" +msgid "<entry>16</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:233 +#: random-bits.xml:235 #, no-c-format -msgid "<entry>48</entry>" +msgid "<entry>62</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:237 +#: random-bits.xml:239 +#, no-c-format +msgid "Web server" +msgstr "" + +#. Tag: entry +#: random-bits.xml:240 +#, no-c-format +msgid "<entry>35</entry>" +msgstr "" + +#. Tag: entry +#: random-bits.xml:241 +#, no-c-format +msgid "<entry>11</entry>" +msgstr "" + +#. Tag: entry +#: random-bits.xml:246 #, no-c-format msgid "Print server" msgstr "" #. Tag: entry -#: random-bits.xml:238 +#: random-bits.xml:247 #, no-c-format -msgid "<entry>168</entry>" +msgid "<entry>326</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:239 +#: random-bits.xml:248 #, no-c-format -msgid "<entry>58</entry>" +msgid "<entry>95</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:240 +#: random-bits.xml:249 #, no-c-format -msgid "<entry>226</entry>" +msgid "<entry>421</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:244 +#: random-bits.xml:253 #, no-c-format msgid "DNS server" msgstr "" #. Tag: entry -#: random-bits.xml:245 +#: random-bits.xml:254 #, no-c-format msgid "<entry>2</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:246 +#: random-bits.xml:255 #, no-c-format msgid "<entry>1</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:247 random-bits.xml:260 +#: random-bits.xml:256 #, no-c-format msgid "<entry>3</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:251 +#: random-bits.xml:260 #, no-c-format msgid "File server" msgstr "" #. Tag: entry -#: random-bits.xml:252 +#: random-bits.xml:261 #, no-c-format -msgid "<entry>47</entry>" +msgid "<entry>50</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:253 +#: random-bits.xml:262 #, no-c-format -msgid "<entry>24</entry>" +msgid "<entry>21</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:254 +#: random-bits.xml:263 #, no-c-format msgid "<entry>71</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:258 +#: random-bits.xml:267 #, no-c-format msgid "Mail server" msgstr "" #. Tag: entry -#: random-bits.xml:259 +#: random-bits.xml:268 +#, no-c-format +msgid "<entry>13</entry>" +msgstr "" + +#. Tag: entry +#: random-bits.xml:269 #, no-c-format -msgid "<entry>10</entry>" +msgid "<entry>5</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:261 +#: random-bits.xml:270 #, no-c-format -msgid "<entry>13</entry>" +msgid "<entry>18</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:265 +#: random-bits.xml:274 #, no-c-format msgid "SQL database" msgstr "" #. Tag: entry -#: random-bits.xml:266 +#: random-bits.xml:275 #, no-c-format -msgid "<entry>66</entry>" +msgid "<entry>24</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:267 +#: random-bits.xml:276 #, no-c-format -msgid "<entry>21</entry>" +msgid "<entry>8</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:268 +#: random-bits.xml:277 #, no-c-format -msgid "<entry>87</entry>" +msgid "<entry>32</entry>" msgstr "" #. Tag: para -#: random-bits.xml:274 +#: random-bits.xml:283 #, no-c-format msgid "" -"The <emphasis>Desktop</emphasis> task will install both the GNOME and KDE " -"desktop environments." +"The <emphasis>Desktop</emphasis> task will install the GNOME desktop " +"environment." msgstr "" #. Tag: para -#: random-bits.xml:281 +#: random-bits.xml:290 #, no-c-format msgid "" "If you install in a language other than English, <command>tasksel</command> " @@ -641,13 +666,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:296 +#: random-bits.xml:305 #, no-c-format msgid "Installing &debian; from a Unix/Linux System" msgstr "" #. Tag: para -#: random-bits.xml:298 +#: random-bits.xml:307 #, no-c-format msgid "" "This section explains how to install &debian; from an existing Unix or Linux " @@ -661,7 +686,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:310 +#: random-bits.xml:319 #, no-c-format msgid "" "Once you've got the new Debian system configured to your preference, you can " @@ -672,13 +697,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:322 +#: random-bits.xml:331 #, no-c-format msgid "Getting Started" msgstr "" #. Tag: para -#: random-bits.xml:323 +#: random-bits.xml:332 #, no-c-format msgid "" "With your current *nix partitioning tools, repartition the hard drive as " @@ -688,7 +713,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:330 +#: random-bits.xml:339 #, no-c-format msgid "" "Create file systems on your partitions. For example, to create an ext3 file " @@ -700,7 +725,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:340 +#: random-bits.xml:349 #, no-c-format msgid "" "Initialize and activate swap (substitute the partition number for your " @@ -715,7 +740,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:352 +#: random-bits.xml:361 #, no-c-format msgid "" "# mkdir /mnt/debinst\n" @@ -723,7 +748,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:355 +#: random-bits.xml:364 #, no-c-format msgid "" "If you want to have parts of the filesystem (e.g. /usr) mounted on separate " @@ -732,13 +757,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:365 +#: random-bits.xml:374 #, no-c-format msgid "Install <command>debootstrap</command>" msgstr "" #. Tag: para -#: random-bits.xml:366 +#: random-bits.xml:375 #, no-c-format msgid "" "The utility used by the Debian installer, and recognized as the official way " @@ -753,7 +778,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:396 +#: random-bits.xml:405 #, no-c-format msgid "" "Or, you can use the following procedure to install it manually. Make a work " @@ -769,7 +794,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:411 +#: random-bits.xml:420 #, no-c-format msgid "" "# ar -x debootstrap_0.X.X_all.deb\n" @@ -778,13 +803,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:417 +#: random-bits.xml:426 #, no-c-format msgid "Run <command>debootstrap</command>" msgstr "" #. Tag: para -#: random-bits.xml:418 +#: random-bits.xml:427 #, no-c-format msgid "" "<command>debootstrap</command> can download the needed files directly from " @@ -795,7 +820,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:427 +#: random-bits.xml:436 #, no-c-format msgid "" "If you have a &releasename; &debian; CD mounted at <filename>/cdrom</" @@ -804,7 +829,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:433 +#: random-bits.xml:442 #, no-c-format msgid "" "Substitute one of the following for <replaceable>ARCH</replaceable> in the " @@ -817,7 +842,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:450 +#: random-bits.xml:459 #, no-c-format msgid "" "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n" @@ -825,13 +850,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:456 +#: random-bits.xml:465 #, no-c-format msgid "Configure The Base System" msgstr "" #. Tag: para -#: random-bits.xml:457 +#: random-bits.xml:466 #, no-c-format msgid "" "Now you've got a real Debian system, though rather lean, on disk. " @@ -839,19 +864,19 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:462 +#: random-bits.xml:471 #, no-c-format msgid "# LANG= chroot /mnt/debinst /bin/bash" msgstr "" #. Tag: title -#: random-bits.xml:467 +#: random-bits.xml:476 #, no-c-format msgid "Mount Partitions" msgstr "" #. Tag: para -#: random-bits.xml:468 +#: random-bits.xml:477 #, no-c-format msgid "" "You need to create <filename>/etc/fstab</filename>. " @@ -886,13 +911,13 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:488 +#: random-bits.xml:497 #, no-c-format msgid "# mount -t proc proc /proc" msgstr "" #. Tag: para -#: random-bits.xml:490 +#: random-bits.xml:499 #, no-c-format msgid "" "The command <userinput>ls /proc</userinput> should now show a non-empty " @@ -901,31 +926,31 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:496 +#: random-bits.xml:505 #, no-c-format msgid "# mount -t proc proc /mnt/debinst/proc" msgstr "" #. Tag: title -#: random-bits.xml:502 +#: random-bits.xml:511 #, no-c-format msgid "Configure Keyboard" msgstr "" #. Tag: para -#: random-bits.xml:503 +#: random-bits.xml:512 #, no-c-format msgid "To configure your keyboard:" msgstr "" #. Tag: screen -#: random-bits.xml:507 +#: random-bits.xml:516 #, no-c-format msgid "# dpkg-reconfigure console-data" msgstr "" #. Tag: para -#: random-bits.xml:509 +#: random-bits.xml:518 #, no-c-format msgid "" "Note that the keyboard cannot be set while in the chroot, but will be " @@ -933,13 +958,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:518 +#: random-bits.xml:527 #, no-c-format msgid "Configure Networking" msgstr "" #. Tag: para -#: random-bits.xml:519 +#: random-bits.xml:528 #, no-c-format msgid "" "To configure networking, edit <filename>/etc/network/interfaces</filename>, " @@ -991,13 +1016,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:556 +#: random-bits.xml:565 #, no-c-format msgid "Configure Locales" msgstr "" #. Tag: para -#: random-bits.xml:557 +#: random-bits.xml:566 #, no-c-format msgid "" "To configure your locale settings to use a language other than English, " @@ -1013,13 +1038,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:575 +#: random-bits.xml:584 #, no-c-format msgid "Install a Kernel" msgstr "" #. Tag: para -#: random-bits.xml:576 +#: random-bits.xml:585 #, no-c-format msgid "" "If you intend to boot this system, you probably want a Linux kernel and a " @@ -1030,7 +1055,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:585 +#: random-bits.xml:594 #, no-c-format msgid "" "# aptitude install linux-image-<replaceable>&kernelversion;-arch-etc</" @@ -1038,13 +1063,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:591 +#: random-bits.xml:600 #, no-c-format msgid "Set up the Boot Loader" msgstr "" #. Tag: para -#: random-bits.xml:592 +#: random-bits.xml:601 #, no-c-format msgid "" "To make your &debian; system bootable, set up your boot loader to load the " @@ -1054,7 +1079,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:599 +#: random-bits.xml:608 #, no-c-format msgid "" "Check <userinput>info grub</userinput> or <userinput>man lilo.conf</" @@ -1068,13 +1093,13 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:610 +#: random-bits.xml:619 #, no-c-format msgid "Here is a basic <filename>/etc/lilo.conf</filename> as an example:" msgstr "" #. Tag: screen -#: random-bits.xml:614 +#: random-bits.xml:623 #, no-c-format msgid "" "boot=/dev/hda6\n" @@ -1087,7 +1112,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:616 +#: random-bits.xml:625 #, no-c-format msgid "" "Check <userinput>man yaboot.conf</userinput> for instructions on setting up " @@ -1099,7 +1124,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:626 +#: random-bits.xml:635 #, no-c-format msgid "" "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: " @@ -1117,13 +1142,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:644 +#: random-bits.xml:653 #, no-c-format msgid "Installing &debian; over Parallel Line IP (PLIP)" msgstr "" #. Tag: para -#: random-bits.xml:646 +#: random-bits.xml:655 #, no-c-format msgid "" "This section explains how to install &debian; on a computer without an " @@ -1133,7 +1158,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:654 +#: random-bits.xml:663 #, no-c-format msgid "" "In the example in this appendix we will set up a PLIP connection using a " @@ -1144,7 +1169,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:662 +#: random-bits.xml:671 #, no-c-format msgid "" "The PLIP connection set up during the installation will also be available " @@ -1153,7 +1178,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:667 +#: random-bits.xml:676 #, no-c-format msgid "" "Before you start, you will need to check the BIOS configuration (IO base " @@ -1163,13 +1188,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:677 +#: random-bits.xml:686 #, no-c-format msgid "Requirements" msgstr "" #. Tag: para -#: random-bits.xml:680 +#: random-bits.xml:689 #, no-c-format msgid "" "A target computer, called <emphasis>target</emphasis>, where Debian will be " @@ -1177,13 +1202,13 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:686 +#: random-bits.xml:695 #, no-c-format msgid "System installation media; see <xref linkend=\"installation-media\"/>." msgstr "" #. Tag: para -#: random-bits.xml:691 +#: random-bits.xml:700 #, no-c-format msgid "" "Another computer connected to the Internet, called <emphasis>source</" @@ -1191,7 +1216,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:697 +#: random-bits.xml:706 #, no-c-format msgid "" "A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;" @@ -1200,13 +1225,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:709 +#: random-bits.xml:718 #, no-c-format msgid "Setting up source" msgstr "" #. Tag: para -#: random-bits.xml:710 +#: random-bits.xml:719 #, no-c-format msgid "" "The following shell script is a simple example of how to configure the " @@ -1214,7 +1239,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:715 +#: random-bits.xml:724 #, no-c-format msgid "" "#!/bin/sh\n" @@ -1238,13 +1263,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:721 +#: random-bits.xml:730 #, no-c-format msgid "Installing target" msgstr "" #. Tag: para -#: random-bits.xml:722 +#: random-bits.xml:731 #, no-c-format msgid "" "Boot the installation media. The installation needs to be run in expert " @@ -1260,13 +1285,13 @@ msgid "" msgstr "" #. Tag: guimenuitem -#: random-bits.xml:741 +#: random-bits.xml:750 #, no-c-format msgid "Load installer components from CD" msgstr "" #. Tag: para -#: random-bits.xml:743 +#: random-bits.xml:752 #, no-c-format msgid "" "Select the <userinput>plip-modules</userinput> option from the list; this " @@ -1274,13 +1299,13 @@ msgid "" msgstr "" #. Tag: guimenuitem -#: random-bits.xml:751 +#: random-bits.xml:760 #, no-c-format msgid "Detect network hardware" msgstr "" #. Tag: para -#: random-bits.xml:756 +#: random-bits.xml:765 #, no-c-format msgid "" "If target <emphasis>does</emphasis> have a network card, a list of driver " @@ -1290,7 +1315,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:765 +#: random-bits.xml:774 #, no-c-format msgid "" "Because no network card was detected/selected earlier, the installer will " @@ -1299,26 +1324,26 @@ msgid "" msgstr "" #. Tag: guimenuitem -#: random-bits.xml:777 +#: random-bits.xml:786 #, no-c-format msgid "Configure the network" msgstr "" #. Tag: para -#: random-bits.xml:780 +#: random-bits.xml:789 #, no-c-format msgid "Auto-configure network with DHCP: No" msgstr "" #. Tag: para -#: random-bits.xml:785 +#: random-bits.xml:794 #, no-c-format msgid "" "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>" msgstr "" #. Tag: para -#: random-bits.xml:790 +#: random-bits.xml:799 #, no-c-format msgid "" "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></" @@ -1326,7 +1351,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:796 +#: random-bits.xml:805 #, no-c-format msgid "" "Name server addresses: you can enter the same addresses used on source (see " |