diff options
| author | SZERVÁC Attila <sas@321.hu> | 2006-10-19 15:38:50 +0000 |
|---|---|---|
| committer | SZERVÁC Attila <sas@321.hu> | 2006-10-19 15:38:50 +0000 |
| commit | 3a305c9a43746b756830cea7d174eedfc9632ca5 (patch) | |
| tree | c432182edfc6b6f2ea17eaebd42c65b45e849726 | |
| parent | a345dfedcc18241ed0be43884615238d5da49993 (diff) | |
| download | installation-guide-3a305c9a43746b756830cea7d174eedfc9632ca5.zip | |
hu trunk: unfuzzies
| -rw-r--r-- | po/hu/boot-installer.po | 2061 | ||||
| -rw-r--r-- | po/hu/hardware.po | 1693 | ||||
| -rw-r--r-- | po/hu/installation-howto.po | 458 |
3 files changed, 941 insertions, 3271 deletions
diff --git a/po/hu/boot-installer.po b/po/hu/boot-installer.po index fd8b1dc5f..756b80cb2 100644 --- a/po/hu/boot-installer.po +++ b/po/hu/boot-installer.po @@ -6,7 +6,7 @@ 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" -"PO-Revision-Date: 2006-10-07 16:52+0100\n" +"PO-Revision-Date: 2006-10-19 17:32+0100\n" "Last-Translator: SZERVÁC Attila <sas@321.hu>\n" "Language-Team: Hungarian\n" "MIME-Version: 1.0\n" @@ -37,106 +37,56 @@ 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 @@ -157,11 +107,20 @@ 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" @@ -179,9 +138,15 @@ 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" @@ -301,7 +266,9 @@ 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" @@ -345,121 +312,65 @@ 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" @@ -468,85 +379,51 @@ 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 @@ -560,13 +437,11 @@ 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 @@ -577,22 +452,8 @@ 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 @@ -604,64 +465,35 @@ 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 @@ -672,14 +504,8 @@ 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 @@ -690,33 +516,20 @@ 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 @@ -725,37 +538,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 @@ -766,70 +579,40 @@ 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 @@ -841,9 +624,7 @@ 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 @@ -853,75 +634,54 @@ 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 @@ -932,20 +692,13 @@ 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 @@ -969,12 +722,7 @@ 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 @@ -987,29 +735,9 @@ 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 @@ -1021,15 +749,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" @@ -1037,71 +765,32 @@ 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 @@ -1122,36 +811,20 @@ 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" @@ -1160,14 +833,8 @@ 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 @@ -1178,120 +845,60 @@ 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 -#, fuzzy, 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. Az LS-120 telepítést csak a 2.4 és későbbi kernelek " -"támogatják." +#, 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." #. 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 @@ -1308,16 +915,8 @@ 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 @@ -1328,17 +927,13 @@ msgstr "" #. 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 "" #. 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." +msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document." msgstr "" #. Tag: title @@ -1350,9 +945,7 @@ msgstr "" #. 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." +msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" #. Tag: title @@ -1365,45 +958,21 @@ msgstr "" #: 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 "" #. 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>)." +msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</keycap>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>linux</userinput>) and a space before the first parameter (e.g., <userinput>linux fb=false</userinput>)." msgstr "" #. Tag: para #: boot-installer.xml: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." +msgid "If you are installing the system via a remote management device that provides a text interface to the VGA console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot prompt. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA). You can blindly press F1<footnote> <para> In some cases these devices will require special escape sequences to enact this keypress, for example the IRA uses <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</keycap>. </para> </footnote> to bypass this screen and view the help text. Once you are past the splash screen and at the help text your keystrokes will be echoed at the prompt as expected. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>fb=false</userinput> to the boot prompt, as described in the help text." msgstr "" #. Tag: title @@ -1415,72 +984,31 @@ 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 @@ -1492,14 +1020,7 @@ 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 @@ -1511,62 +1032,37 @@ 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 @@ -1578,73 +1074,43 @@ 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 @@ -1656,57 +1122,31 @@ 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 @@ -1718,85 +1158,49 @@ 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 @@ -1809,26 +1213,19 @@ 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 @@ -1846,15 +1243,7 @@ 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 @@ -1866,38 +1255,19 @@ 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 @@ -1909,36 +1279,25 @@ 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 @@ -1950,18 +1309,13 @@ 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 @@ -1973,18 +1327,13 @@ 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 @@ -1996,10 +1345,7 @@ 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 @@ -2011,24 +1357,13 @@ 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 @@ -2040,11 +1375,7 @@ 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 @@ -2056,10 +1387,7 @@ 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 @@ -2069,43 +1397,29 @@ 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 @@ -2117,24 +1431,13 @@ 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 @@ -2146,24 +1449,13 @@ 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 @@ -2175,73 +1467,37 @@ 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 @@ -2259,27 +1515,19 @@ 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 @@ -2303,29 +1551,24 @@ 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 "" @@ -2336,42 +1579,36 @@ 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 "" @@ -2379,21 +1616,16 @@ 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 @@ -2403,17 +1635,15 @@ 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 "" @@ -2421,43 +1651,25 @@ 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 @@ -2469,19 +1681,13 @@ 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 @@ -2493,44 +1699,25 @@ 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 @@ -2566,15 +1753,7 @@ 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 @@ -2587,27 +1766,11 @@ 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 @@ -2625,62 +1788,34 @@ 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 @@ -2692,51 +1827,31 @@ 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 @@ -2748,37 +1863,19 @@ 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 @@ -2787,34 +1884,23 @@ 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 @@ -2826,43 +1912,25 @@ 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 @@ -2870,39 +1938,20 @@ 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 @@ -2914,14 +1963,7 @@ 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> Note that the 2.4 kernel accepts a maximum of 8 command line options and 8 environment options (including any options added by default for the installer). If these numbers are exceeded, 2.4 kernels will drop any excess options. With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options. </para> </footnote> which may be useful." msgstr "" #. Tag: term @@ -2933,32 +1975,19 @@ msgstr "" #. Tag: para #: boot-installer.xml:2825 #, 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 #, 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 #, 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 @@ -2970,24 +1999,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2852 #, 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 @@ -2999,11 +2011,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2889 #, 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 @@ -3051,9 +2059,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2914 #, 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 @@ -3065,18 +2071,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:2929 #, 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 #, 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 @@ -3088,22 +2089,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:2946 #, 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 #, 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 @@ -3121,13 +2113,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2970 #, 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 @@ -3139,13 +2125,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2985 #, 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 @@ -3157,9 +2137,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2999 #, 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 @@ -3171,21 +2149,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:3009 #, 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 #, 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 @@ -3197,9 +2167,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:3028 #, 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 @@ -3211,10 +2179,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:3039 #, 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 @@ -3226,10 +2191,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:3050 #, 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 @@ -3241,22 +2203,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:3061 #, 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 #, no-c-format -msgid "" -"Set to <userinput>false</userinput> to disable automatic ejection, and be " -"aware that you may need to ensure that the system does not automatically " -"boot from the optical drive after the initial installation." +msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation." msgstr "" #. Tag: term @@ -3280,10 +2233,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:3091 #, 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." +msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. To enable it, set this parameter to <userinput>true</userinput> when booting the installer." msgstr "" #. Tag: term @@ -3295,9 +2245,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:3102 #, no-c-format -msgid "" -"Set to <userinput>true</userinput> to enter rescue mode rather than " -"performing a normal installation. See <xref linkend=\"rescue\"/>." +msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." msgstr "" #. Tag: title @@ -3315,69 +2263,32 @@ msgstr "Flopi lemezek megbízhatósága" #. Tag: para #: boot-installer.xml:3127 #, 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 #, 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:3141 #, 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 "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." #. Tag: para #: boot-installer.xml:3151 #, 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 #, 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 @@ -3388,39 +2299,25 @@ msgstr "" #. Tag: para #: boot-installer.xml:3168 #, no-c-format -msgid "" -"If you have problems and the kernel hangs during the boot process, doesn't " -"recognize peripherals you actually have, or drives are not recognized " -"properly, the first thing to check is the boot parameters, as discussed in " -"<xref linkend=\"boot-parms\"/>." +msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>." msgstr "" #. Tag: para #: boot-installer.xml:3175 #, no-c-format -msgid "" -"If you are booting with your own kernel instead of the one supplied with the " -"installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your " -"kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>." +msgid "If you are booting with your own kernel instead of the one supplied with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>." msgstr "" #. Tag: para #: boot-installer.xml:3182 #, no-c-format -msgid "" -"Often, problems can be solved by removing add-ons and peripherals, and then " -"trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and " -"Plug-n-Play devices can be especially problematic.</phrase>" +msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" msgstr "" #. Tag: para #: boot-installer.xml:3188 #, no-c-format -msgid "" -"If you have a large amount of memory installed in your machine, more than " -"512M, and the installer hangs when booting the kernel, you may need to " -"include a boot argument to limit the amount of memory the kernel sees, such " -"as <userinput>mem=512m</userinput>." +msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>." msgstr "" #. Tag: title @@ -3432,54 +2329,31 @@ msgstr "" #. Tag: para #: boot-installer.xml:3200 #, no-c-format -msgid "" -"There are some common installation problems that can be solved or avoided by " -"passing certain boot parameters to the installer." +msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." msgstr "" #. Tag: para #: boot-installer.xml:3205 #, no-c-format -msgid "" -"Some systems have floppies with <quote>inverted DCLs</quote>. If you receive " -"errors reading from the floppy, even when you know the floppy is good, try " -"the parameter <userinput>floppy=thinkpad</userinput>." +msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>." msgstr "" #. Tag: para #: boot-installer.xml:3211 #, no-c-format -msgid "" -"On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk " -"drivers), the IDE drive may not be properly recognized. Again, try it first " -"without the parameters and see if the IDE drive is recognized properly. If " -"not, determine your drive geometry (cylinders, heads, and sectors), and use " -"the parameter <userinput>hd=<replaceable>cylinders</replaceable>," -"<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></" -"userinput>." +msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>." msgstr "" #. Tag: para #: boot-installer.xml:3220 #, no-c-format -msgid "" -"If you have a very old machine, and the kernel hangs after saying " -"<computeroutput>Checking 'hlt' instruction...</computeroutput>, then you " -"should try the <userinput>no-hlt</userinput> boot argument, which disables " -"this test." +msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test." msgstr "" #. Tag: para #: boot-installer.xml:3227 #, no-c-format -msgid "" -"If your screen begins to show a weird picture while the kernel boots, eg. " -"pure white, pure black or colored pixel garbage, your system may contain a " -"problematic video card which does not switch to the framebuffer mode " -"properly. Then you can use the boot parameter <userinput>fb=false " -"video=vga16:off</userinput> to disable the framebuffer console. Only the " -"English language will be available during the installation due to limited " -"console features. See <xref linkend=\"boot-parms\"/> for details." +msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false video=vga16:off</userinput> to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" #. Tag: title @@ -3491,28 +2365,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:3242 #, no-c-format -msgid "" -"Some laptop models produced by Dell are known to crash when PCMCIA device " -"detection tries to access some hardware addresses. Other laptops may display " -"similar problems. If you experience such a problem and you don't need PCMCIA " -"support during the installation, you can disable PCMCIA using the " -"<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can " -"then configure PCMCIA after the installation is completed and exclude the " -"resource range causing the problems." +msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems." msgstr "" #. Tag: para #: boot-installer.xml:3252 #, no-c-format -msgid "" -"Alternatively, you can boot the installer in expert mode. You will then be " -"asked to enter the resource range options your hardware needs. For example, " -"if you have one of the Dell laptops mentioned above, you should enter " -"<userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list " -"of some common resource range options in the <ulink url=\"http://pcmcia-cs." -"sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource " -"settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the " -"commas, if any, when you enter this value in the installer." +msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer." msgstr "" #. Tag: title @@ -3524,14 +2383,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:3270 #, no-c-format -msgid "" -"The kernel normally tries to install USB modules and the USB keyboard driver " -"in order to support some non-standard USB keyboards. However, there are some " -"broken USB systems where the driver hangs on loading. A possible workaround " -"may be disabling the USB controller in your mainboard BIOS setup. Another " -"option is passing the <userinput>debian-installer/probe/usb=false</" -"userinput> parameter at the boot prompt, which will prevent the modules from " -"being loaded." +msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter at the boot prompt, which will prevent the modules from being loaded." msgstr "" #. Tag: title @@ -3543,22 +2395,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:3286 #, no-c-format -msgid "" -"During the boot sequence, you may see many messages in the form " -"<computeroutput>can't find <replaceable>something</replaceable> </" -"computeroutput>, or <computeroutput> <replaceable>something</replaceable> " -"not present</computeroutput>, <computeroutput>can't initialize " -"<replaceable>something</replaceable> </computeroutput>, or even " -"<computeroutput>this driver release depends on <replaceable>something</" -"replaceable> </computeroutput>. Most of these messages are harmless. You see " -"them because the kernel for the installation system is built to run on " -"computers with many different peripheral devices. Obviously, no one computer " -"will have every possible peripheral device, so the operating system may emit " -"a few complaints while it looks for peripherals you don't own. You may also " -"see the system pause for a while. This happens when it is waiting for a " -"device to respond, and that device is not present on your system. If you " -"find the time it takes to boot the system unacceptably long, you can create " -"a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." +msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable> </computeroutput>, or <computeroutput> <replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable> </computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable> </computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." msgstr "" #. Tag: title @@ -3570,22 +2407,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:3312 #, no-c-format -msgid "" -"If you get through the initial boot phase but cannot complete the install, " -"the bug reporter menu choice may be helpful. It lets you store system error " -"logs and configuration information from the installer to a floppy, or " -"download them in a web browser. This information may provide clues as to " -"what went wrong and how to fix it. If you are submitting a bug report you " -"may want to attach this information to the bug report." +msgid "If you get through the initial boot phase but cannot complete the install, the bug reporter menu choice may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them in a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report you may want to attach this information to the bug report." msgstr "" #. Tag: para #: boot-installer.xml:3323 #, no-c-format -msgid "" -"Other pertinent installation messages may be found in <filename>/var/log/</" -"filename> during the installation, and <filename>/var/log/installer/</" -"filename> after the computer has been booted into the installed system." +msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system." msgstr "" #. Tag: title @@ -3597,38 +2425,20 @@ msgstr "Telepítő jelentések küldése" #. Tag: para #: boot-installer.xml:3335 #, 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 #, 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 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" @@ -3662,15 +2472,9 @@ msgid "" "\n" "<Description of the install, in prose, and any thoughts, comments\n" " and ideas you had during the initial install.>\n" -"</screen></informalexample> In the bug report, describe what the problem is, " -"including the last visible kernel messages in the event of a kernel hang. " -"Describe the steps that you did which brought the system into the problem " -"state." -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" @@ -3704,6 +2508,5 @@ 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/hardware.po b/po/hu/hardware.po index 07e14d491..b50328519 100644 --- a/po/hu/hardware.po +++ b/po/hu/hardware.po @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2006-10-19 11:20+0000\n" -"PO-Revision-Date: 2006-09-12 23:59+0100\n" +"PO-Revision-Date: 2006-10-19 17:35+0100\n" "Last-Translator: SZERVÁC Attila <sas@321.hu>\n" "Language-Team: Hungarian <debian-l10n-hungarian@lists.debian>\n" "MIME-Version: 1.0\n" @@ -25,14 +25,8 @@ msgstr "Rendszerkövetelmények" #. Tag: para #: hardware.xml:7 #, no-c-format -msgid "" -"This section contains information about what hardware you need to get " -"started with Debian. You will also find links to further information about " -"hardware supported by GNU and Linux." -msgstr "" -"E fejezet leírja a Debian használatához szükséges hardvert. A GNU és Linux " -"által támogatott hardverekről szóló további információkra utaló " -"hivatkozásokat is ad." +msgid "This section contains information about what hardware you need to get started with Debian. You will also find links to further information about hardware supported by GNU and Linux." +msgstr "E fejezet leírja a Debian használatához szükséges hardvert. A GNU és Linux által támogatott hardverekről szóló további információkra utaló hivatkozásokat is ad." #. Tag: title #: hardware.xml:20 @@ -43,32 +37,14 @@ msgstr "Támogatott hardver" #. Tag: para #: hardware.xml:21 #, no-c-format -msgid "" -"Debian does not impose hardware requirements beyond the requirements of the " -"Linux kernel and the GNU tool-sets. Therefore, any architecture or platform " -"to which the Linux kernel, libc, <command>gcc</command>, etc. have been " -"ported, and for which a Debian port exists, can run Debian. Please refer to " -"the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on " -"&arch-title; architecture systems which have been tested with Debian." -msgstr "" -"A Debian nem igényel a Linux és a GNU eszköz-készletek által kívántnál több " -"hardvert. Ezért minden gépen, melyen a Linux kernel, a libc, a <command>gcc</" -"command> és a többi fut, és melyre a Debian portolva van, futtatható a " -"Debian. Lásd a Debian portok oldalát a <ulink url=\"&url-ports;\"></ulink> " -"címen a jelen &arch-title; architektúra rendszerekről, melyek teszteltek a " -"Debian rendszerrel." +msgid "Debian does not impose hardware requirements beyond the requirements of the Linux kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux kernel, libc, <command>gcc</command>, etc. have been ported, and for which a Debian port exists, can run Debian. Please refer to the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on &arch-title; architecture systems which have been tested with Debian." +msgstr "A Debian nem igényel a Linux és a GNU eszköz-készletek által kívántnál több hardvert. Ezért minden gépen, melyen a Linux kernel, a libc, a <command>gcc</command> és a többi fut, és melyre a Debian portolva van, futtatható a Debian. Lásd a Debian portok oldalát a <ulink url=\"&url-ports;\"></ulink> címen a jelen &arch-title; architektúra rendszerekről, melyek teszteltek a Debian rendszerrel." #. Tag: para #: hardware.xml:32 #, no-c-format -msgid "" -"Rather than attempting to describe all the different hardware configurations " -"which are supported for &arch-title;, this section contains general " -"information and pointers to where additional information can be found." -msgstr "" -"A jelen, &arch-title; architektúra által támogatott összes különböző hardver " -"konfiguráció leírásának megkísérlése helyett, e fejezet általános adatokat " -"és még részletesebb adatokra való hivatkozásokat ad." +msgid "Rather than attempting to describe all the different hardware configurations which are supported for &arch-title;, this section contains general information and pointers to where additional information can be found." +msgstr "A jelen, &arch-title; architektúra által támogatott összes különböző hardver konfiguráció leírásának megkísérlése helyett, e fejezet általános adatokat és még részletesebb adatokra való hivatkozásokat ad." #. Tag: title #: hardware.xml:41 @@ -79,13 +55,8 @@ msgstr "Támogatott architektúrák" #. Tag: para #: hardware.xml:42 #, no-c-format -msgid "" -"Debian &release; supports twelve major architectures and several variations " -"of each architecture known as <quote>flavors</quote>." -msgstr "" -"A Debian &release; 12 nagy architektúrát támogat és minden architektúra " -"számos változatát, melyeket <quote>kivitelek</quote> (flavors) néven " -"említünk." +msgid "Debian &release; supports twelve major architectures and several variations of each architecture known as <quote>flavors</quote>." +msgstr "A Debian &release; 12 nagy architektúrát támogat és minden architektúra számos változatát, melyeket <quote>kivitelek</quote> (flavors) néven említünk." #. Tag: entry #: hardware.xml:53 @@ -280,25 +251,29 @@ msgid "r5k-ip32" msgstr "r5k-ip32" #. Tag: entry -#: hardware.xml:119 hardware.xml:137 +#: hardware.xml:119 +#: hardware.xml:137 #, no-c-format msgid "Broadcom BCM91250A (SWARM)" msgstr "Broadcom BCM91250A (SWARM)" #. Tag: entry -#: hardware.xml:120 hardware.xml:138 +#: hardware.xml:120 +#: hardware.xml:138 #, no-c-format msgid "sb1-bcm91250a" msgstr "sb1-bcm91250a" #. Tag: entry -#: hardware.xml:122 hardware.xml:140 +#: hardware.xml:122 +#: hardware.xml:140 #, no-c-format msgid "Broadcom BCM91480B (BigSur)" msgstr "Broadcom BCM91480B (BigSur)" #. Tag: entry -#: hardware.xml:123 hardware.xml:141 +#: hardware.xml:123 +#: hardware.xml:141 #, no-c-format msgid "sb1a-bcm91480b" msgstr "sb1a-bcm91480b" @@ -334,13 +309,19 @@ msgid "DECstation" msgstr "DECstation" #. Tag: entry -#: hardware.xml:133 hardware.xml:1087 hardware.xml:1102 hardware.xml:1112 +#: hardware.xml:133 +#: hardware.xml:1087 +#: hardware.xml:1102 +#: hardware.xml:1112 #, no-c-format msgid "r4k-kn04" msgstr "r4k-kn04" #. Tag: entry -#: hardware.xml:135 hardware.xml:1082 hardware.xml:1092 hardware.xml:1097 +#: hardware.xml:135 +#: hardware.xml:1082 +#: hardware.xml:1092 +#: hardware.xml:1097 #: hardware.xml:1107 #, no-c-format msgid "r3k-kn02" @@ -541,42 +522,26 @@ msgstr "szalag" #. Tag: para #: hardware.xml:201 #, no-c-format -msgid "" -"This document covers installation for the <emphasis>&arch-title;</emphasis> " -"architecture. If you are looking for information on any of the other Debian-" -"supported architectures take a look at the <ulink url=\"http://www.debian." -"org/ports/\">Debian-Ports</ulink> pages." -msgstr "" -"E dokumentum leírja a Debian <emphasis>&arch-title;</emphasis> " -"architektúrára telepítését. Ha más, Debian által támogatott architektúra " -"érdekel, nézd meg a <ulink url=\"http://www.debian.org/ports/\">Debian " -"portok</ulink> oldalt." +msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture. If you are looking for information on any of the other Debian-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">Debian-Ports</ulink> pages." +msgstr "E dokumentum leírja a Debian <emphasis>&arch-title;</emphasis> architektúrára telepítését. Ha más, Debian által támogatott architektúra érdekel, nézd meg a <ulink url=\"http://www.debian.org/ports/\">Debian portok</ulink> oldalt." #. Tag: para #: hardware.xml:209 #, no-c-format -msgid "" -"This is the first official release of &debian; for the &arch-title; " -"architecture. We feel that it has proven itself sufficiently to be released. " -"However, because it has not had the exposure (and hence testing by users) " -"that some other architectures have had, you may encounter a few bugs. Use " -"our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any " -"problems; make sure to mention the fact that the bug is on the &arch-title; " -"platform. It can be necessary to use the <ulink url=\"&url-list-subscribe;" -"\">debian-&arch-listname; mailing list</ulink> as well." -msgstr "" -"Az a &debian; 1. hivatalos &arch-title; kiadása. Tapasztalataink szerint " -"megérett a kiadásra. De mivel még kevesebb felhasználó tesztelte, ezért " -"nagyobb az esély, hogy találsz benne hibát. Kérjük, a <ulink url=\"&url-bts;" -"\">Hibakövető rendszer</ulink> segítségével jelents minden hibát; említsd " -"meg, hogy a hibát &arch-title; platformon lelted. Ilyenkor az " -"architektúrának megfelelő <ulink url=\"&url-list-subscribe;\">debian-&arch-" -"listname; lista</ulink> használata is szükséges lehet." +msgid "This is the first official release of &debian; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well." +msgstr "Az a &debian; 1. hivatalos &arch-title; kiadása. Tapasztalataink szerint megérett a kiadásra. De mivel még kevesebb felhasználó tesztelte, ezért nagyobb az esély, hogy találsz benne hibát. Kérjük, a <ulink url=\"&url-bts;\">Hibakövető rendszer</ulink> segítségével jelents minden hibát; említsd meg, hogy a hibát &arch-title; platformon lelted. Ilyenkor az architektúrának megfelelő <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; lista</ulink> használata is szükséges lehet." #. Tag: title -#: hardware.xml:231 hardware.xml:690 hardware.xml:726 hardware.xml:802 -#: hardware.xml:821 hardware.xml:907 hardware.xml:949 hardware.xml:1017 -#: hardware.xml:1176 hardware.xml:1622 +#: hardware.xml:231 +#: hardware.xml:690 +#: hardware.xml:726 +#: hardware.xml:802 +#: hardware.xml:821 +#: hardware.xml:907 +#: hardware.xml:949 +#: hardware.xml:1017 +#: hardware.xml:1176 +#: hardware.xml:1622 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "CPU, alaplap és videó támogatás" @@ -584,42 +549,20 @@ msgstr "CPU, alaplap és videó támogatás" #. Tag: para #: hardware.xml:232 #, no-c-format -msgid "" -"Complete information regarding supported DEC Alphas can be found at <ulink " -"url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this " -"section is to describe the systems supported by the boot disks." -msgstr "" -"A támogatott DEC Alpha gépekkel kapcsolatos adatok a <ulink url=\"&url-alpha-" -"howto;\">Linux Alpha HOGYAN</ulink> címen találhatók. E szakasz célja az " -"indító lemezek által támogatott rendszerek leírása." +msgid "Complete information regarding supported DEC Alphas can be found at <ulink url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this section is to describe the systems supported by the boot disks." +msgstr "A támogatott DEC Alpha gépekkel kapcsolatos adatok a <ulink url=\"&url-alpha-howto;\">Linux Alpha HOGYAN</ulink> címen találhatók. E szakasz célja az indító lemezek által támogatott rendszerek leírása." #. Tag: para #: hardware.xml:239 #, no-c-format -msgid "" -"Alpha machines are subdivided into different system types because there are " -"a number of generations of motherboard and supporting chipsets. Different " -"systems (<quote>sub-architectures</quote>) often have radically different " -"engineering and capabilities. Therefore, the process of installing and, more " -"to the point, booting, can vary from system to system." -msgstr "" -"Az Alpha gépek 2 eltérő rendszer-típusra oszlanak, mert számos generációt " -"éltek meg. Ezek az alrendszerek (<quote>al-architektúrák</quote>) teljesen " -"eltérő felépítéssel és képességekkel rendelkeznek. Ezért a telepítés, és " -"főleg az indítás rendszerről rendszerre eltér." +msgid "Alpha machines are subdivided into different system types because there are a number of generations of motherboard and supporting chipsets. Different systems (<quote>sub-architectures</quote>) often have radically different engineering and capabilities. Therefore, the process of installing and, more to the point, booting, can vary from system to system." +msgstr "Az Alpha gépek 2 eltérő rendszer-típusra oszlanak, mert számos generációt éltek meg. Ezek az alrendszerek (<quote>al-architektúrák</quote>) teljesen eltérő felépítéssel és képességekkel rendelkeznek. Ezért a telepítés, és főleg az indítás rendszerről rendszerre eltér." #. Tag: para #: hardware.xml:247 #, no-c-format -msgid "" -"The following table lists the system types supported by the Debian " -"installation system. The table also indicates the <emphasis>code name</" -"emphasis> for these system types. You'll need to know this code name when " -"you actually begin the installation process:" -msgstr "" -"Az alábbi táblázat adja a Debian telepítő rendszer által támogatott " -"rendszereket. A táblázat e rendszerek <emphasis>kódnevét</emphasis> is " -"mutatja. A telepítés megkezdéséhez tudnod kell majd ezt:" +msgid "The following table lists the system types supported by the Debian installation system. The table also indicates the <emphasis>code name</emphasis> for these system types. You'll need to know this code name when you actually begin the installation process:" +msgstr "Az alábbi táblázat adja a Debian telepítő rendszer által támogatott rendszereket. A táblázat e rendszerek <emphasis>kódnevét</emphasis> is mutatja. A telepítés megkezdéséhez tudnod kell majd ezt:" #. Tag: entry #: hardware.xml:264 @@ -658,7 +601,9 @@ msgid "Maverick" msgstr "Maverick" #. Tag: entry -#: hardware.xml:274 hardware.xml:278 hardware.xml:282 +#: hardware.xml:274 +#: hardware.xml:278 +#: hardware.xml:282 #, no-c-format msgid "alcor" msgstr "alcor" @@ -748,8 +693,14 @@ msgid "Mustang" msgstr "Mustang" #. Tag: entry -#: hardware.xml:300 hardware.xml:304 hardware.xml:308 hardware.xml:312 -#: hardware.xml:316 hardware.xml:320 hardware.xml:324 hardware.xml:328 +#: hardware.xml:300 +#: hardware.xml:304 +#: hardware.xml:308 +#: hardware.xml:312 +#: hardware.xml:316 +#: hardware.xml:320 +#: hardware.xml:324 +#: hardware.xml:328 #, no-c-format msgid "avanti" msgstr "avanti" @@ -839,7 +790,9 @@ msgid "Avanti" msgstr "Avanti" #. Tag: entry -#: hardware.xml:332 hardware.xml:345 hardware.xml:346 +#: hardware.xml:332 +#: hardware.xml:345 +#: hardware.xml:346 #, no-c-format msgid "EB164" msgstr "EB164" @@ -905,7 +858,9 @@ msgid "eb164" msgstr "eb164" #. Tag: entry -#: hardware.xml:351 hardware.xml:360 hardware.xml:361 +#: hardware.xml:351 +#: hardware.xml:360 +#: hardware.xml:361 #, no-c-format msgid "EB64+" msgstr "EB64+" @@ -917,13 +872,15 @@ msgid "AlphaPC64" msgstr "AlphaPC64" #. Tag: entry -#: hardware.xml:353 hardware.xml:357 +#: hardware.xml:353 +#: hardware.xml:357 #, no-c-format msgid "Cabriolet" msgstr "Cabriolet" #. Tag: entry -#: hardware.xml:354 hardware.xml:358 +#: hardware.xml:354 +#: hardware.xml:358 #, no-c-format msgid "cabriolet" msgstr "cabriolet" @@ -941,7 +898,9 @@ msgid "eb64p" msgstr "eb64p" #. Tag: entry -#: hardware.xml:366 hardware.xml:367 hardware.xml:368 +#: hardware.xml:366 +#: hardware.xml:367 +#: hardware.xml:368 #, no-c-format msgid "EB66" msgstr "EB66" @@ -953,7 +912,8 @@ msgid "eb66" msgstr "eb66" #. Tag: entry -#: hardware.xml:371 hardware.xml:372 +#: hardware.xml:371 +#: hardware.xml:372 #, no-c-format msgid "EB66+" msgstr "EB66+" @@ -977,22 +937,53 @@ msgid "DEC 2000 Model 300(S)" msgstr "DEC 2000 Model 300(S)" #. Tag: entry -#: hardware.xml:379 hardware.xml:387 +#: hardware.xml:379 +#: hardware.xml:387 #, no-c-format msgid "Jensen" msgstr "Jensen" #. Tag: entry -#: hardware.xml:380 hardware.xml:384 hardware.xml:388 hardware.xml:449 -#: hardware.xml:453 hardware.xml:471 hardware.xml:475 hardware.xml:479 -#: hardware.xml:483 hardware.xml:487 hardware.xml:491 hardware.xml:495 -#: hardware.xml:509 hardware.xml:513 hardware.xml:517 hardware.xml:521 -#: hardware.xml:525 hardware.xml:559 hardware.xml:563 hardware.xml:567 -#: hardware.xml:571 hardware.xml:585 hardware.xml:589 hardware.xml:593 -#: hardware.xml:597 hardware.xml:604 hardware.xml:608 hardware.xml:612 -#: hardware.xml:616 hardware.xml:620 hardware.xml:624 hardware.xml:628 -#: hardware.xml:632 hardware.xml:636 hardware.xml:640 hardware.xml:644 -#: hardware.xml:648 hardware.xml:652 hardware.xml:659 hardware.xml:663 +#: hardware.xml:380 +#: hardware.xml:384 +#: hardware.xml:388 +#: hardware.xml:449 +#: hardware.xml:453 +#: hardware.xml:471 +#: hardware.xml:475 +#: hardware.xml:479 +#: hardware.xml:483 +#: hardware.xml:487 +#: hardware.xml:491 +#: hardware.xml:495 +#: hardware.xml:509 +#: hardware.xml:513 +#: hardware.xml:517 +#: hardware.xml:521 +#: hardware.xml:525 +#: hardware.xml:559 +#: hardware.xml:563 +#: hardware.xml:567 +#: hardware.xml:571 +#: hardware.xml:585 +#: hardware.xml:589 +#: hardware.xml:593 +#: hardware.xml:597 +#: hardware.xml:604 +#: hardware.xml:608 +#: hardware.xml:612 +#: hardware.xml:616 +#: hardware.xml:620 +#: hardware.xml:624 +#: hardware.xml:628 +#: hardware.xml:632 +#: hardware.xml:636 +#: hardware.xml:640 +#: hardware.xml:644 +#: hardware.xml:648 +#: hardware.xml:652 +#: hardware.xml:659 +#: hardware.xml:663 #, no-c-format msgid "<entry>N/A</entry>" msgstr "<entry>N/A</entry>" @@ -1028,15 +1019,27 @@ msgid "Personal WorkStation 433a" msgstr "Personal WorkStation 433a" #. Tag: entry -#: hardware.xml:394 hardware.xml:398 hardware.xml:402 hardware.xml:406 -#: hardware.xml:410 hardware.xml:414 hardware.xml:418 hardware.xml:422 +#: hardware.xml:394 +#: hardware.xml:398 +#: hardware.xml:402 +#: hardware.xml:406 +#: hardware.xml:410 +#: hardware.xml:414 +#: hardware.xml:418 +#: hardware.xml:422 #, no-c-format msgid "Miata" msgstr "Miata" #. Tag: entry -#: hardware.xml:395 hardware.xml:399 hardware.xml:403 hardware.xml:407 -#: hardware.xml:411 hardware.xml:415 hardware.xml:419 hardware.xml:423 +#: hardware.xml:395 +#: hardware.xml:399 +#: hardware.xml:403 +#: hardware.xml:407 +#: hardware.xml:411 +#: hardware.xml:415 +#: hardware.xml:419 +#: hardware.xml:423 #, no-c-format msgid "miata" msgstr "miata" @@ -1102,7 +1105,10 @@ msgid "Mikasa" msgstr "Mikasa" #. Tag: entry -#: hardware.xml:430 hardware.xml:434 hardware.xml:438 hardware.xml:442 +#: hardware.xml:430 +#: hardware.xml:434 +#: hardware.xml:438 +#: hardware.xml:442 #, no-c-format msgid "mikasa" msgstr "mikasa" @@ -1120,7 +1126,8 @@ msgid "Mikasa+" msgstr "Mikasa+" #. Tag: entry -#: hardware.xml:436 hardware.xml:440 +#: hardware.xml:436 +#: hardware.xml:440 #, no-c-format msgid "AlphaServer 1000 5/300" msgstr "AlphaServer 1000 5/300" @@ -1186,7 +1193,8 @@ msgid "Noname" msgstr "Névtelen" #. Tag: entry -#: hardware.xml:460 hardware.xml:464 +#: hardware.xml:460 +#: hardware.xml:464 #, no-c-format msgid "noname" msgstr "névtelen" @@ -1252,7 +1260,9 @@ msgid "AlphaServer 800 5/333...500" msgstr "AlphaServer 800 5/333...500" #. Tag: entry -#: hardware.xml:482 hardware.xml:490 hardware.xml:494 +#: hardware.xml:482 +#: hardware.xml:490 +#: hardware.xml:494 #, no-c-format msgid "Corelle" msgstr "Corelle" @@ -1288,7 +1298,8 @@ msgid "PLATFORM 2000" msgstr "PLATFORM 2000" #. Tag: entry -#: hardware.xml:500 hardware.xml:501 +#: hardware.xml:500 +#: hardware.xml:501 #, no-c-format msgid "<entry>P2K</entry>" msgstr "<entry>P2K</entry>" @@ -1312,7 +1323,8 @@ msgid "AlphaServer 1200 5/xxx" msgstr "AlphaServer 1200 5/xxx" #. Tag: entry -#: hardware.xml:508 hardware.xml:520 +#: hardware.xml:508 +#: hardware.xml:520 #, no-c-format msgid "Tincup/DaVinci" msgstr "Tincup/DaVinci" @@ -1336,7 +1348,8 @@ msgid "AlphaServer 4100 5/xxx" msgstr "AlphaServer 4100 5/xxx" #. Tag: entry -#: hardware.xml:516 hardware.xml:524 +#: hardware.xml:516 +#: hardware.xml:524 #, no-c-format msgid "Dodge" msgstr "Dodge" @@ -1366,15 +1379,23 @@ msgid "DeskStation AlphaPC164-UX" msgstr "DeskStation AlphaPC164-UX" #. Tag: entry -#: hardware.xml:531 hardware.xml:535 hardware.xml:539 hardware.xml:543 -#: hardware.xml:547 hardware.xml:551 +#: hardware.xml:531 +#: hardware.xml:535 +#: hardware.xml:539 +#: hardware.xml:543 +#: hardware.xml:547 +#: hardware.xml:551 #, no-c-format msgid "Ruffian" msgstr "Ruffian" #. Tag: entry -#: hardware.xml:532 hardware.xml:536 hardware.xml:540 hardware.xml:544 -#: hardware.xml:548 hardware.xml:552 +#: hardware.xml:532 +#: hardware.xml:536 +#: hardware.xml:540 +#: hardware.xml:544 +#: hardware.xml:548 +#: hardware.xml:552 #, no-c-format msgid "ruffian" msgstr "ruffian" @@ -1530,7 +1551,9 @@ msgid "Privateer" msgstr "Privateer" #. Tag: entry -#: hardware.xml:595 hardware.xml:634 hardware.xml:638 +#: hardware.xml:595 +#: hardware.xml:634 +#: hardware.xml:638 #, no-c-format msgid "UNKNOWN" msgstr "ISMERETLEN" @@ -1554,7 +1577,8 @@ msgid "AlphaServer DS10" msgstr "AlphaServer DS10" #. Tag: entry -#: hardware.xml:603 hardware.xml:651 +#: hardware.xml:603 +#: hardware.xml:651 #, no-c-format msgid "Webbrick" msgstr "Webbrick" @@ -1620,7 +1644,8 @@ msgid "Clipper" msgstr "Clipper" #. Tag: entry -#: hardware.xml:626 hardware.xml:627 +#: hardware.xml:626 +#: hardware.xml:627 #, no-c-format msgid "DP264" msgstr "DP264" @@ -1692,7 +1717,8 @@ msgid "AlphaServer GS160" msgstr "AlphaServer GS160" #. Tag: entry -#: hardware.xml:658 hardware.xml:662 +#: hardware.xml:658 +#: hardware.xml:662 #, no-c-format msgid "Wildfire" msgstr "Wildfire" @@ -1704,7 +1730,8 @@ msgid "AlphaServer GS320" msgstr "AlphaServer GS320" #. Tag: entry -#: hardware.xml:667 hardware.xml:669 +#: hardware.xml:667 +#: hardware.xml:669 #, no-c-format msgid "<entry>XL</entry>" msgstr "<entry>XL</entry>" @@ -1724,27 +1751,20 @@ msgstr "<entry>xl</entry>" #. Tag: para #: hardware.xml:675 #, no-c-format -msgid "" -"It is believed that Debian &releasename; supports installing on all alpha " -"sub-architectures with the exception of the ARC-only Ruffian and XL sub-" -"architectures and the Titan subarchitecture, which requires a change to the " -"kernel compile options." +msgid "It is believed that Debian &releasename; supports installing on all alpha sub-architectures with the exception of the ARC-only Ruffian and XL sub-architectures and the Titan subarchitecture, which requires a change to the kernel compile options." msgstr "" #. Tag: para -#: hardware.xml:691 hardware.xml:822 +#: hardware.xml:691 +#: hardware.xml:822 #, no-c-format -msgid "" -"Complete information concerning supported peripherals can be found at <ulink " -"url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. " -"This section merely outlines the basics." -msgstr "" -"A <ulink url=\"&url-hardware-howto;\">Linux Hardver Kompatibilitás HOGYAN</" -"ulink> leírásban megtalálható a támogatott perifériák listája. Ez a fejezet " -"csak az alapokat emeli ki." +msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics." +msgstr "A <ulink url=\"&url-hardware-howto;\">Linux Hardver Kompatibilitás HOGYAN</ulink> leírásban megtalálható a támogatott perifériák listája. Ez a fejezet csak az alapokat emeli ki." #. Tag: title -#: hardware.xml:699 hardware.xml:830 hardware.xml:990 +#: hardware.xml:699 +#: hardware.xml:830 +#: hardware.xml:990 #, no-c-format msgid "<title>CPU</title>" msgstr "<title>CPU</title>" @@ -1758,20 +1778,13 @@ msgstr "Az AMD64 és Intel EM64t processzorok is támogatottak." #. Tag: para #: hardware.xml:728 #, no-c-format -msgid "" -"Each distinct ARM architecture requires its own kernel. Because of this the " -"standard Debian distribution only supports installation on a number of the " -"most common systems. The Debian userland however may be used by " -"<emphasis>any</emphasis> ARM CPU including xscale." +msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard Debian distribution only supports installation on a number of the most common systems. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU including xscale." msgstr "" #. Tag: para #: hardware.xml:736 #, no-c-format -msgid "" -"Most ARM CPUs may be run in either endian mode (big or little). However, the " -"majority of current system implementation uses little-endian mode. Debian " -"currently only supports little-endian ARM systems." +msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems." msgstr "" #. Tag: para @@ -1789,17 +1802,8 @@ msgstr "Netwinder" #. Tag: para #: hardware.xml:752 #, no-c-format -msgid "" -"This is actually the name for the group of machines based upon the StrongARM " -"110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises " -"of machines like: Netwinder (possibly one of the most common ARM boxes), " -"CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, " -"aka skiff)." -msgstr "" -"Ez a StrongARM 110 CPU és az Intel 21285 Northbridge (vagy Footbridge) " -"hardverekre épülő gépek neve. Többek között: Netwinder (az egyik " -"legelterjedtebb ARM gép), CATS (vagy EB110ATX), EBSA 285 és Compaq personal " -"server (cps más néven skiff)." +msgid "This is actually the name for the group of machines based upon the StrongARM 110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff)." +msgstr "Ez a StrongARM 110 CPU és az Intel 21285 Northbridge (vagy Footbridge) hardverekre épülő gépek neve. Többek között: Netwinder (az egyik legelterjedtebb ARM gép), CATS (vagy EB110ATX), EBSA 285 és Compaq personal server (cps más néven skiff)." #. Tag: term #: hardware.xml:765 @@ -1810,11 +1814,7 @@ msgstr "NSLU2" #. Tag: para #: hardware.xml:766 #, no-c-format -msgid "" -"The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small " -"device which allows you to easily provide storage via the network. It comes " -"with an Ethernet connection and two USB ports to which hard drives can be " -"connected." +msgid "The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected." msgstr "" #. Tag: term @@ -1826,100 +1826,32 @@ msgstr "<term>RiscPC</term>" #. Tag: para #: hardware.xml:778 #, no-c-format -msgid "" -"This machine is the oldest supported hardware: it was released in 1994. It " -"has RISC OS in ROM, Linux can be booted from that OS using linloader. The " -"RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or " -"233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA " -"video, parallel port, single serial port, PS/2 keyboard and proprietary " -"mouse port. The proprietary module expansion bus allows for up to eight " -"expansion cards to be fitted depending on configuration, several of these " -"modules have Linux drivers." -msgstr "" -"Ez a gép a legrégebben támogatott hardver: a megjelenés éve: 1994. A ROM " -"tartalma egy RISC OS, a Linux ebből indítható a linloader programmal. A " -"RiscPC lelke egy moduláris CPU kártya, melyen jellemzően egy 30MHz 610, " -"40MHz 710 vagy 233MHz Strongarm 110 CPU van. Az alaplapon IDE, SVGA, " -"párhuzamos és 1 soros port, PS/2 billentyű és egy egyéni egér port. Az " -"egyéni modul bővítő busz a kiépítéstől függően legfeljebb 8 különféle bővítő " -"kártyát tesz lehetővé, egyesek mennek Linuxszal." +msgid "This machine is the oldest supported hardware: it was released in 1994. It has RISC OS in ROM, Linux can be booted from that OS using linloader. The RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA video, parallel port, single serial port, PS/2 keyboard and proprietary mouse port. The proprietary module expansion bus allows for up to eight expansion cards to be fitted depending on configuration, several of these modules have Linux drivers." +msgstr "Ez a gép a legrégebben támogatott hardver: a megjelenés éve: 1994. A ROM tartalma egy RISC OS, a Linux ebből indítható a linloader programmal. A RiscPC lelke egy moduláris CPU kártya, melyen jellemzően egy 30MHz 610, 40MHz 710 vagy 233MHz Strongarm 110 CPU van. Az alaplapon IDE, SVGA, párhuzamos és 1 soros port, PS/2 billentyű és egy egyéni egér port. Az egyéni modul bővítő busz a kiépítéstől függően legfeljebb 8 különféle bővítő kártyát tesz lehetővé, egyesek mennek Linuxszal." #. Tag: para #: hardware.xml:803 #, no-c-format -msgid "" -"There are two major support <emphasis>&architecture;</emphasis> flavors: PA-" -"RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit " -"processors whereas the 2.0 architecture is targeted to the 64-bit " -"processors. Some systems are able to run either kernel. In both cases, the " -"userland is 32-bit. There is the possibility of a 64-bit userland in the " -"future." +msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future." msgstr "" #. Tag: para #: hardware.xml:831 #, no-c-format -msgid "" -"Nearly all x86-based (IA-32) processors still in use in personal computers " -"are supported, including all varieties of Intel's \"Pentium\" series. This " -"also includes 32-bits AMD and VIA (former Cyrix) processors, and new " -"processors like the Athlon XP and Intel P4 Xeon." -msgstr "" -"Szinte minden, sok személyi számítógépben még ma is használt x86-alapú (IA-" -"32) processzor támogatott, ideértve az Intel néhai \"Pentium\" sorozatát is. " -"Ez a legrégebbi 32-bites AMD és VIA (egykor Cyrix) processzorokat is jelenti " -"és a kevésbé régi Athlon XP és Intel P4 Xeonokat." +msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bits AMD and VIA (former Cyrix) processors, and new processors like the Athlon XP and Intel P4 Xeon." +msgstr "Szinte minden, sok személyi számítógépben még ma is használt x86-alapú (IA-32) processzor támogatott, ideértve az Intel néhai \"Pentium\" sorozatát is. Ez a legrégebbi 32-bites AMD és VIA (egykor Cyrix) processzorokat is jelenti és a kevésbé régi Athlon XP és Intel P4 Xeonokat." #. Tag: para #: hardware.xml:839 #, no-c-format -msgid "" -"If your system has a 64-bits AMD64, Intel EM64t or Intel Core 2 Duo " -"processor, you will probably want to use the installer for the amd64 " -"architecture instead of the installer for the (32-bits) i386 architecture." -msgstr "" -"Ha a rendszeredben egy 64-bites AMD64, Intel EM64t vagy Intel Core 2 Duo " -"processzor van, akkor valószínűleg már az amd64 architektúrát akarod " -"használni a (32-bites) i386 architektúra telepítője helyett." +msgid "If your system has a 64-bits AMD64, Intel EM64t or Intel Core 2 Duo processor, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bits) i386 architecture." +msgstr "Ha a rendszeredben egy 64-bites AMD64, Intel EM64t vagy Intel Core 2 Duo processzor van, akkor valószínűleg már az amd64 architektúrát akarod használni a (32-bites) i386 architektúra telepítője helyett." #. Tag: para #: hardware.xml:846 #, no-c-format -msgid "" -"However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on " -"386 or earlier processors. Despite the architecture name \"i386\", Debian " -"Sarge has <emphasis>dropped support</emphasis> for actual 80386 processors " -"(and their clones), which were supported by earlier releases<footnote> " -"<para> We have long tried to avoid this, but in the end it was necessary due " -"a unfortunate series of issues with the compiler and the kernel, starting " -"with an bug in the C++ ABI provided by GCC. You should still be able to run " -"Debian GNU/Linux on actual 80386 processors if you compile your own kernel " -"and compile all packages from source, but that is beyond the scope of this " -"manual. </para> </footnote>. (No version of Linux has ever supported the 286 " -"or earlier chips in the series.) All i486 and later processors are still " -"supported<footnote> <para> Many Debian packages will actually run slightly " -"faster on modern computers as a positive side effect of dropping support for " -"these old chips. The i486, introduced in 1989, has three opcodes (bswap, " -"cmpxchg, and xadd) which the i386, introduced in 1986, did not have. " -"Previously, these could not be easily used by most Debian packages; now they " -"can. </para> </footnote>." -msgstr "" -"Tudni kell, hogy a Debian GNU/Linux &releasename; immár <emphasis>nem</" -"emphasis> fut 386-os vagy korábbi processzoron. Az \"i386\" architektúra-név " -"ellenére a Debian Sarge óta <emphasis>megszűnt a támogatás</emphasis> a " -"80386 processzorokhoz (és másolataikhoz), melyet a korábbi kiadások " -"támogattak<footnote> <para> Sokáig megpróbáltuk elkerülni ezt, de végül a " -"fordító és a kernel hibáinak egy szerencsétlen sora miatt, amely egy a GCC " -"által szállított C++ ABI hibával kezdődött ez szükséges volt. A Debian GNU/" -"Linux még mindig futtatható 80386-os processzoron, de ehhez magadnak kell " -"lefordítanod a kernelt és az összes használt csomagot, és ez túlmutat e " -"kézikönyv célján. </para> </footnote>. (A Linux nem támogatja a 286-os vagy " -"korábbi x86 processzorokat.) Minden i486 és későbbi processzor " -"támogatott<footnote> <para> A modern gépeken sok Debian csomag így " -"érezhetően gyorsabban fut, ami a régi gépek támogatása elvetésének pozitív " -"oldala. Az i486 (1989) 3 utasításkóddal bír (bswap, cmpxchg, és xadd) " -"mellyel az i386 (1986) nem. Korábban a legtöbb Debian csomagban ezek nemigen " -"voltak használhatók; most igen. </para> </footnote>." +msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", Debian Sarge has <emphasis>dropped support</emphasis> for actual 80386 processors (and their clones), which were supported by earlier releases<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para> </footnote>." +msgstr "Tudni kell, hogy a Debian GNU/Linux &releasename; immár <emphasis>nem</emphasis> fut 386-os vagy korábbi processzoron. Az \"i386\" architektúra-név ellenére a Debian Sarge óta <emphasis>megszűnt a támogatás</emphasis> a 80386 processzorokhoz (és másolataikhoz), melyet a korábbi kiadások támogattak<footnote> <para> Sokáig megpróbáltuk elkerülni ezt, de végül a fordító és a kernel hibáinak egy szerencsétlen sora miatt, amely egy a GCC által szállított C++ ABI hibával kezdődött ez szükséges volt. A Debian GNU/Linux még mindig futtatható 80386-os processzoron, de ehhez magadnak kell lefordítanod a kernelt és az összes használt csomagot, és ez túlmutat e kézikönyv célján. </para> </footnote>. (A Linux nem támogatja a 286-os vagy korábbi x86 processzorokat.) Minden i486 és későbbi processzor támogatott<footnote> <para> A modern gépeken sok Debian csomag így érezhetően gyorsabban fut, ami a régi gépek támogatása elvetésének pozitív oldala. Az i486 (1989) 3 utasításkóddal bír (bswap, cmpxchg, és xadd) mellyel az i386 (1986) nem. Korábban a legtöbb Debian csomagban ezek nemigen voltak használhatók; most igen. </para> </footnote>." #. Tag: title #: hardware.xml:883 @@ -1930,126 +1862,49 @@ msgstr "I/O Busz" #. Tag: para #: hardware.xml:884 #, no-c-format -msgid "" -"The system bus is the part of the motherboard which allows the CPU to " -"communicate with peripherals such as storage devices. Your computer must use " -"the ISA, EISA, PCI, the Microchannel Architecture (MCA, used in IBM's PS/2 " -"line), or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all " -"personal computers sold in recent years use one of these." -msgstr "" -"A rendszerbusz az alaplap része, mellyel a CPU a perifériákkal kommunikál, " -"például a tároló eszközökkel. A gépnek ISA-t, EISA-t, PCI-t, Mikrocsatornás " -"architektúrát (MCA, az IBM PS/2 vonalban használt) vagy VESA Local Bus-t " -"(VLB, néha VL busznak hívják) kell használnia. Gyakorlatilag minden mai " -"személyi számítógép ezek egyikét használja." +msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, the Microchannel Architecture (MCA, used in IBM's PS/2 line), or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these." +msgstr "A rendszerbusz az alaplap része, mellyel a CPU a perifériákkal kommunikál, például a tároló eszközökkel. A gépnek ISA-t, EISA-t, PCI-t, Mikrocsatornás architektúrát (MCA, az IBM PS/2 vonalban használt) vagy VESA Local Bus-t (VLB, néha VL busznak hívják) kell használnia. Gyakorlatilag minden mai személyi számítógép ezek egyikét használja." #. Tag: para #: hardware.xml:908 #, no-c-format -msgid "" -"Complete information concerning supported M68000 based " -"(<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=" -"\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the " -"basics." -msgstr "" -"Az M68000 alapú (<emphasis>&architecture;</emphasis>) támogatott " -"rendszerekről szóló teljes leírás a <ulink url=\"&url-m68k-faq;\">Linux/m68k " -"FAQ</ulink> címen található. E szakasz csak az alapokat írja le." +msgid "Complete information concerning supported M68000 based (<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the basics." +msgstr "Az M68000 alapú (<emphasis>&architecture;</emphasis>) támogatott rendszerekről szóló teljes leírás a <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink> címen található. E szakasz csak az alapokat írja le." #. Tag: para #: hardware.xml:915 #, no-c-format -msgid "" -"The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory " -"Management Unit) and a FPU (floating-point unit). This includes the 68020 " -"with an external 68851 PMMU, the 68030, and better, and excludes the " -"<quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-" -"faq;\">Linux/m68k FAQ</ulink> for complete details." -msgstr "" -"A Linux &architecture; portja minden PMMU (Paged Memory Management Unit) és " -"FPU (floating-point unit) összetevővel rendelkező 680x0 processzoron fut. " -"Ezek: a 68020 és külső 68851 PMMU és a 68030 és újabbak, ezzel szemben nem " -"megfelelőek a 680x0 <quote>EC</quote> generációjú processzorok." +msgid "The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory Management Unit) and a FPU (floating-point unit). This includes the 68020 with an external 68851 PMMU, the 68030, and better, and excludes the <quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink> for complete details." +msgstr "A Linux &architecture; portja minden PMMU (Paged Memory Management Unit) és FPU (floating-point unit) összetevővel rendelkező 680x0 processzoron fut. Ezek: a 68020 és külső 68851 PMMU és a 68030 és újabbak, ezzel szemben nem megfelelőek a 680x0 <quote>EC</quote> generációjú processzorok." #. Tag: para #: hardware.xml:923 #, no-c-format -msgid "" -"There are four major supported <emphasis>&architecture;</emphasis> flavors: " -"Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two " -"systems to which Linux was ported; in keeping, they are also the two most " -"well-supported Debian ports. The Macintosh line is supported incompletely, " -"both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;" -"\">Linux m68k for Macintosh</ulink> for project status and supported " -"hardware. The BVM and Motorola single board VMEbus computers are the most " -"recent addition to the list of machines supported by Debian. Ports to other " -"&architecture; architectures, such as the Sun3 architecture and NeXT black " -"box, are underway but not yet supported by Debian." +msgid "There are four major supported <emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two systems to which Linux was ported; in keeping, they are also the two most well-supported Debian ports. The Macintosh line is supported incompletely, both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> for project status and supported hardware. The BVM and Motorola single board VMEbus computers are the most recent addition to the list of machines supported by Debian. Ports to other &architecture; architectures, such as the Sun3 architecture and NeXT black box, are underway but not yet supported by Debian." msgstr "" #. Tag: para #: hardware.xml:950 #, no-c-format -msgid "" -"Debian on &arch-title; supports the following platforms: <itemizedlist> " -"<listitem><para> SGI IP22: this platform includes the SGI machines Indy, " -"Indigo 2 and Challenge S. Since these machines are very similar, whenever " -"this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant " -"as well. </para></listitem> <listitem><para> SGI IP32: this platform is " -"generally known as SGI O2. </para></listitem> <listitem><para> Broadcom " -"BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom " -"based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> " -"Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board " -"from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </" -"itemizedlist> Complete information regarding supported mips/mipsel machines " -"can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</" -"ulink>. In the following, only the systems supported by the Debian installer " -"will be covered. If you are looking for support for other subarchitectures, " -"please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-" -"listname; mailing list</ulink>." +msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: para #: hardware.xml:991 #, no-c-format -msgid "" -"On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and " -"R5000 processors are supported by the Debian installation system on big " -"endian MIPS. On SGI IP32, currently only systems based on the R5000 are " -"supported. The Broadcom BCM91250A evaluation board comes with an SB1 1250 " -"chip with two cores which are supported in SMP mode by this installer. " -"Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with " -"four cores which are supported in SMP mode." +msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the Debian installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported. The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." msgstr "" #. Tag: para #: hardware.xml:1001 #, no-c-format -msgid "" -"Some MIPS machines can be operated in both big and little endian mode. For " -"little endian MIPS, please read the documentation for the mipsel " -"architecture." +msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture." msgstr "" #. Tag: para #: hardware.xml:1018 #, no-c-format -msgid "" -"Debian on &arch-title; supports the following platforms: <itemizedlist> " -"<listitem><para> DECstation: various models of the DECstation are supported. " -"</para></listitem> <listitem><para> Cobalt Microserver: only MIPS based " -"Cobalt machines are covered here. This includes the Cobalt Qube 2700 " -"(Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></" -"listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form " -"factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </" -"para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an " -"ATX form factor evaluation board from Broadcom based on the quad-core SB1A " -"1480 CPU. </para></listitem> </itemizedlist> Complete information regarding " -"supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-" -"mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems " -"supported by the Debian installer will be covered. If you are looking for " -"support for other subarchitectures, please contact the <ulink url=\"&url-" -"list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." +msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: title @@ -2061,14 +1916,8 @@ msgstr "CPU/Gép típusok" #. Tag: para #: hardware.xml:1060 #, no-c-format -msgid "" -"Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by " -"the Debian installation system on little endian MIPS. The Debian " -"installation system works on the following machines:" -msgstr "" -"A Debian telepítő jelenleg csak az R3000 és R4000/R4400 CPU-s DECstation " -"gépeket támogatja a kis-végű MIPS gépek közül. A Debian telepítő rendszer az " -"alábbi gépeken működik:" +msgid "Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by the Debian installation system on little endian MIPS. The Debian installation system works on the following machines:" +msgstr "A Debian telepítő jelenleg csak az R3000 és R4000/R4400 CPU-s DECstation gépeket támogatja a kis-végű MIPS gépek közül. A Debian telepítő rendszer az alábbi gépeken működik:" #. Tag: entry #: hardware.xml:1072 @@ -2101,13 +1950,17 @@ msgid "DECstation 5000/1xx" msgstr "DECstation 5000/1xx" #. Tag: entry -#: hardware.xml:1080 hardware.xml:1090 hardware.xml:1095 hardware.xml:1105 +#: hardware.xml:1080 +#: hardware.xml:1090 +#: hardware.xml:1095 +#: hardware.xml:1105 #, no-c-format msgid "R3000" msgstr "R3000" #. Tag: entry -#: hardware.xml:1081 hardware.xml:1086 +#: hardware.xml:1081 +#: hardware.xml:1086 #, no-c-format msgid "3MIN" msgstr "3MIN" @@ -2119,7 +1972,8 @@ msgid "DECstation 5000/150" msgstr "DECstation 5000/150" #. Tag: entry -#: hardware.xml:1085 hardware.xml:1110 +#: hardware.xml:1085 +#: hardware.xml:1110 #, no-c-format msgid "R4000" msgstr "R4000" @@ -2143,7 +1997,8 @@ msgid "DECstation 5000/240" msgstr "DECstation 5000/240" #. Tag: entry -#: hardware.xml:1096 hardware.xml:1101 +#: hardware.xml:1096 +#: hardware.xml:1101 #, no-c-format msgid "3MAX+" msgstr "3MAX+" @@ -2167,7 +2022,8 @@ msgid "Personal DECstation 5000/xx" msgstr "Personal DECstation 5000/xx" #. Tag: entry -#: hardware.xml:1106 hardware.xml:1111 +#: hardware.xml:1106 +#: hardware.xml:1111 #, no-c-format msgid "Maxine" msgstr "Maxine" @@ -2181,23 +2037,13 @@ msgstr "Personal DECstation 5000/50" #. Tag: para #: hardware.xml:1116 #, no-c-format -msgid "" -"All Cobalt machines are supported. In the past, only machines with a serial " -"console were supported (that is, all machines except for the Qube 2700, aka " -"Qube1). However, installations are now also possible through SSH." -msgstr "" -"Minden Cobalt gép támogatott. Régen csak a soros konzolos gépek voltak " -"támogatottak (vagyis minden, kivéve a Qube 2700 más nevén Qube1 gépet). De " -"ma már ez is megoldott az SSH lehetőséggel." +msgid "All Cobalt machines are supported. In the past, only machines with a serial console were supported (that is, all machines except for the Qube 2700, aka Qube1). However, installations are now also possible through SSH." +msgstr "Minden Cobalt gép támogatott. Régen csak a soros konzolos gépek voltak támogatottak (vagyis minden, kivéve a Qube 2700 más nevén Qube1 gépet). De ma már ez is megoldott az SSH lehetőséggel." #. Tag: para #: hardware.xml:1123 #, no-c-format -msgid "" -"The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two " -"cores which are supported in SMP mode by this installer. Similarly, the " -"BCM91480B evaluation board contains an SB1A 1480 chip with four cores which " -"are supported in SMP mode." +msgid "The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." msgstr "" #. Tag: title @@ -2209,30 +2055,16 @@ msgstr "" #. Tag: para #: hardware.xml:1134 #, no-c-format -msgid "" -"A serial console is available on all supported DECstations (9600 bps, 8N1). " -"To use the serial console, you have to boot the installer image with the " -"<literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter " -"(with <replaceable>x</replaceable> being the number of the serial port you " -"have your terminal connected to — usually <literal>2</literal>, but " -"<literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ " -"(DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available " -"with the PMAG-BA and the PMAGB-B graphics options." +msgid "A serial console is available on all supported DECstations (9600 bps, 8N1). To use the serial console, you have to boot the installer image with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter (with <replaceable>x</replaceable> being the number of the serial port you have your terminal connected to — usually <literal>2</literal>, but <literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available with the PMAG-BA and the PMAGB-B graphics options." msgstr "" #. Tag: para #: hardware.xml:1145 #, no-c-format msgid "" -"If you have a Linux system to use as serial terminal, an easy way is to run " -"<command>cu</command><footnote> <para> In Woody this command was part of the " -"<classname>uucp</classname> package, but in later releases it is available " -"as a separate package. </para> </footnote> on it. Example: " -"<informalexample><screen>\n" +"If you have a Linux system to use as serial terminal, an easy way is to run <command>cu</command><footnote> <para> In Woody this command was part of the <classname>uucp</classname> package, but in later releases it is available as a separate package. </para> </footnote> on it. Example: <informalexample><screen>\n" "$ cu -l /dev/ttyS1 -s 9600\n" -"</screen></informalexample> where the option <literal>-l</literal> (line) " -"sets the serial port to use and <literal>-s</literal> (speed) sets the speed " -"for the connection (9600 bits per second)." +"</screen></informalexample> where the option <literal>-l</literal> (line) sets the serial port to use and <literal>-s</literal> (speed) sets the speed for the connection (9600 bits per second)." msgstr "" #. Tag: para @@ -2244,21 +2076,13 @@ msgstr "" #. Tag: para #: hardware.xml:1177 #, no-c-format -msgid "" -"There are four major supported <emphasis>&architecture;</emphasis> " -"subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga " -"Power-UP System), and CHRP machines. Each subarchitecture has its own boot " -"methods. In addition, there are four different kernel flavours, supporting " -"different CPU variants." +msgid "There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga Power-UP System), and CHRP machines. Each subarchitecture has its own boot methods. In addition, there are four different kernel flavours, supporting different CPU variants." msgstr "" #. Tag: para #: hardware.xml:1185 #, no-c-format -msgid "" -"Ports to other <emphasis>&architecture;</emphasis> architectures, such as " -"the Be-Box and MBX architecture, are underway but not yet supported by " -"Debian. We may have a 64-bit port in the future." +msgid "Ports to other <emphasis>&architecture;</emphasis> architectures, such as the Be-Box and MBX architecture, are underway but not yet supported by Debian. We may have a 64-bit port in the future." msgstr "" #. Tag: title @@ -2270,9 +2094,7 @@ msgstr "" #. Tag: para #: hardware.xml:1195 #, no-c-format -msgid "" -"There are four flavours of the powerpc kernel in Debian, based on the CPU " -"type:" +msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" #. Tag: term @@ -2284,10 +2106,7 @@ msgstr "" #. Tag: para #: hardware.xml:1203 #, no-c-format -msgid "" -"Most systems use this kernel flavour, which supports the PowerPC 601, 603, " -"604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and " -"including the one marketed as G4 use one of these processors." +msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors." msgstr "" #. Tag: term @@ -2305,26 +2124,19 @@ msgstr "" #. Tag: para #: hardware.xml:1218 #, no-c-format -msgid "" -"The POWER3 processor is used in older IBM 64-bit server systems: known " -"models include the IntelliStation POWER Model 265, the pSeries 610 and 640, " -"and the RS/6000 7044-170, 7043-260, and 7044-270." +msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270." msgstr "" #. Tag: para #: hardware.xml:1224 #, no-c-format -msgid "" -"The POWER4 processor is used in more recent IBM 64-bit server systems: known " -"models include the pSeries 615, 630, 650, 655, 670, and 690." +msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690." msgstr "" #. Tag: para #: hardware.xml:1229 #, no-c-format -msgid "" -"Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 " -"architecture, and use this kernel flavour." +msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour." msgstr "" #. Tag: term @@ -2348,9 +2160,7 @@ msgstr "" #. Tag: para #: hardware.xml:1248 #, no-c-format -msgid "" -"This kernel flavour supports the Amiga Power-UP System, though it is " -"currently disabled." +msgid "This kernel flavour supports the Amiga Power-UP System, though it is currently disabled." msgstr "" #. Tag: title @@ -2362,46 +2172,32 @@ msgstr "" #. Tag: para #: hardware.xml:1263 #, no-c-format -msgid "" -"Apple (and briefly a few other manufacturers — Power Computing, for " -"example) made a series of Macintosh computers based on the PowerPC " -"processor. For purposes of architecture support, they are categorized as " -"NuBus (not supported by Debian), OldWorld, and NewWorld." +msgid "Apple (and briefly a few other manufacturers — Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by Debian), OldWorld, and NewWorld." msgstr "" #. Tag: para #: hardware.xml:1270 #, no-c-format -msgid "" -"OldWorld systems are most Power Macintoshes with a floppy drive and a PCI " -"bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld " -"machines. Those pre-iMac PowerPC models from Apple use a four digit naming " -"scheme, except for the beige colored G3 systems, which are also OldWorld." +msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld." msgstr "" #. Tag: para #: hardware.xml:1278 #, no-c-format -msgid "" -"The so called NewWorld PowerMacs are any PowerMacs in translucent colored " -"plastic cases and later models. That includes all iMacs, iBooks, G4 systems, " -"blue colored G3 systems, and most PowerBooks manufactured in and after 1999. " -"The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</" -"quote> system for MacOS, and were manufactured from mid-1998 onwards." +msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards." msgstr "" #. Tag: para #: hardware.xml:1286 #, no-c-format -msgid "" -"Specifications for Apple hardware are available at <ulink url=\"http://www." -"info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older " -"hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/" -"index.html\">AppleSpec Legacy</ulink>." +msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>." msgstr "" #. Tag: entry -#: hardware.xml:1302 hardware.xml:1437 hardware.xml:1481 hardware.xml:1510 +#: hardware.xml:1302 +#: hardware.xml:1437 +#: hardware.xml:1481 +#: hardware.xml:1510 #, no-c-format msgid "Model Name/Number" msgstr "" @@ -2425,10 +2221,22 @@ msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:1311 hardware.xml:1314 hardware.xml:1317 hardware.xml:1320 -#: hardware.xml:1323 hardware.xml:1326 hardware.xml:1329 hardware.xml:1332 -#: hardware.xml:1335 hardware.xml:1338 hardware.xml:1341 hardware.xml:1344 -#: hardware.xml:1347 hardware.xml:1350 hardware.xml:1353 hardware.xml:1356 +#: hardware.xml:1311 +#: hardware.xml:1314 +#: hardware.xml:1317 +#: hardware.xml:1320 +#: hardware.xml:1323 +#: hardware.xml:1326 +#: hardware.xml:1329 +#: hardware.xml:1332 +#: hardware.xml:1335 +#: hardware.xml:1338 +#: hardware.xml:1341 +#: hardware.xml:1344 +#: hardware.xml:1347 +#: hardware.xml:1350 +#: hardware.xml:1353 +#: hardware.xml:1356 #, no-c-format msgid "NewWorld" msgstr "NewWorld" @@ -2530,10 +2338,22 @@ msgid "Performa 4400, 54xx, 5500" msgstr "Performa 4400, 54xx, 5500" #. Tag: entry -#: hardware.xml:1359 hardware.xml:1362 hardware.xml:1365 hardware.xml:1368 -#: hardware.xml:1371 hardware.xml:1374 hardware.xml:1377 hardware.xml:1380 -#: hardware.xml:1383 hardware.xml:1386 hardware.xml:1389 hardware.xml:1392 -#: hardware.xml:1398 hardware.xml:1401 hardware.xml:1407 hardware.xml:1413 +#: hardware.xml:1359 +#: hardware.xml:1362 +#: hardware.xml:1365 +#: hardware.xml:1368 +#: hardware.xml:1371 +#: hardware.xml:1374 +#: hardware.xml:1377 +#: hardware.xml:1380 +#: hardware.xml:1383 +#: hardware.xml:1386 +#: hardware.xml:1389 +#: hardware.xml:1392 +#: hardware.xml:1398 +#: hardware.xml:1401 +#: hardware.xml:1407 +#: hardware.xml:1413 #: hardware.xml:1419 #, no-c-format msgid "OldWorld" @@ -2648,7 +2468,8 @@ msgid "APS Tech M*Power 604e/2000" msgstr "APS Tech M*Power 604e/2000" #. Tag: entry -#: hardware.xml:1417 hardware.xml:1443 +#: hardware.xml:1417 +#: hardware.xml:1443 #, no-c-format msgid "Motorola" msgstr "Motorola" @@ -2696,7 +2517,8 @@ msgid "MCP(N)750" msgstr "MCP(N)750" #. Tag: entry -#: hardware.xml:1456 hardware.xml:1487 +#: hardware.xml:1456 +#: hardware.xml:1487 #, no-c-format msgid "IBM RS/6000" msgstr "IBM RS/6000" @@ -2776,17 +2598,7 @@ msgstr "Nubus PowerMac al-architektúra (nem-támogatott)" #. Tag: para #: hardware.xml:1527 #, no-c-format -msgid "" -"NuBus systems are not currently supported by Debian/powerpc. The monolithic " -"Linux/PPC kernel architecture does not have support for these machines; " -"instead, one must use the MkLinux Mach microkernel, which Debian does not " -"yet support. These include the following: <itemizedlist> <listitem><para> " -"Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> " -"Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook " -"1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server " -"6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these " -"machines and limited support is available at <ulink url=\"http://nubus-pmac." -"sourceforge.net/\"></ulink>." +msgid "NuBus systems are not currently supported by Debian/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which Debian does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>." msgstr "" #. Tag: title @@ -2798,33 +2610,19 @@ msgstr "" #. Tag: para #: hardware.xml:1566 #, no-c-format -msgid "" -"Macintosh computers using the 680x0 series of processors are <emphasis>not</" -"emphasis> in the PowerPC family but are instead m68k machines. Those models " -"start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> " -"family, then the Centris series, and culminate in the Quadras and Performas. " -"These models usually have a Roman numeral or 3-digit model number such as " -"Mac IIcx, LCIII or Quadra 950." +msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950." msgstr "" #. Tag: para #: hardware.xml:1575 #, no-c-format -msgid "" -"This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, " -"IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, " -"580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra " -"(605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the " -"Performa 200-640CD." +msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD." msgstr "" #. Tag: para #: hardware.xml:1583 #, no-c-format -msgid "" -"In laptops, it started with the Mac Portable, then the PowerBook 100-190cs " -"and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, " -"please see the section above)." +msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)." msgstr "" #. Tag: title @@ -2836,42 +2634,13 @@ msgstr "S/390 és zSeries géptípusok" #. Tag: para #: hardware.xml:1600 #, no-c-format -msgid "" -"Complete information regarding supported S/390 and zSeries machines can be " -"found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/" -"redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: " -"Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128." -"ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the " -"developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries " -"are fully supported; Multiprise 2000, G3 and G4 machines are supported with " -"IEEE floating point emulation and thus degraded performance." -msgstr "" -"A támogatott S/390 és zSeries gépekről szóló teljes információ forrása az " -"IBM vörös könyv <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/" -"sg246264.pdf\"> Linux az IBM eServer zSeries és S/390 gépekre: " -"Disztribúciók</ulink> 2.1 fejezet illetve a <ulink url=\"http://www-128.ibm." -"com/developerworks/linux/linux390/index.html\">zSeries oldal a " -"developerWorks lapon</ulink>. Röviden: a G5, Multiprise 3000, G6 és minden " -"zSeries teljesen támogatott; a Multiprise 2000, G3 és G4 gépek csak IEEE " -"lebegőpontos emulációval, ami csökkenti a teljesítményt." +msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128.ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance." +msgstr "A támogatott S/390 és zSeries gépekről szóló teljes információ forrása az IBM vörös könyv <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux az IBM eServer zSeries és S/390 gépekre: Disztribúciók</ulink> 2.1 fejezet illetve a <ulink url=\"http://www-128.ibm.com/developerworks/linux/linux390/index.html\">zSeries oldal a developerWorks lapon</ulink>. Röviden: a G5, Multiprise 3000, G6 és minden zSeries teljesen támogatott; a Multiprise 2000, G3 és G4 gépek csak IEEE lebegőpontos emulációval, ami csökkenti a teljesítményt." #. Tag: para #: hardware.xml:1623 #, no-c-format -msgid "" -"Currently the <emphasis>&architecture;</emphasis> port supports several " -"types of Sparc systems. The most common identifiers for Sparc systems are " -"sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not support very old " -"sun4 hardware. However, the other systems are supported. Sun4d has been " -"tested the least of these, so expect possible problems with regard to the " -"kernel stability. Sun4c and Sun4m, the most common of the older Sparc " -"hardware, includes such systems as SparcStation 1, 1+, IPC, IPX and the " -"SparcStation LX, 5, 10, and 20, respectively. The UltraSPARC class systems " -"fall under the sun4u identifier, and are supported using the sun4u set of " -"install images. Some systems that fall under these supported identifiers are " -"known to not be supported. Known unsupported systems are the AP1000 " -"multicomputer and the Tadpole Sparcbook 1. See the <ulink url=\"&url-sparc-" -"linux-faq;\">Linux for SPARCProcessors FAQ</ulink> for complete information." +msgid "Currently the <emphasis>&architecture;</emphasis> port supports several types of Sparc systems. The most common identifiers for Sparc systems are sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not support very old sun4 hardware. However, the other systems are supported. Sun4d has been tested the least of these, so expect possible problems with regard to the kernel stability. Sun4c and Sun4m, the most common of the older Sparc hardware, includes such systems as SparcStation 1, 1+, IPC, IPX and the SparcStation LX, 5, 10, and 20, respectively. The UltraSPARC class systems fall under the sun4u identifier, and are supported using the sun4u set of install images. Some systems that fall under these supported identifiers are known to not be supported. Known unsupported systems are the AP1000 multicomputer and the Tadpole Sparcbook 1. See the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARCProcessors FAQ</ulink> for complete information." msgstr "" #. Tag: title @@ -2883,34 +2652,19 @@ msgstr "" #. Tag: para #: hardware.xml:1644 #, no-c-format -msgid "" -"Some older Sun workstations, notably the Sun IPX and Sun IPC have memory " -"banks located at fixed locations in physical memory. Thus if the banks are " -"not filled gaps will exist in the physical memory space. The Linux " -"installation requires a contiguous memory block into which to load the " -"kernel and the initial RAMdisk. If this is not available a <quote>Data " -"Access Exception</quote> will result." +msgid "Some older Sun workstations, notably the Sun IPX and Sun IPC have memory banks located at fixed locations in physical memory. Thus if the banks are not filled gaps will exist in the physical memory space. The Linux installation requires a contiguous memory block into which to load the kernel and the initial RAMdisk. If this is not available a <quote>Data Access Exception</quote> will result." msgstr "" #. Tag: para #: hardware.xml:1653 #, no-c-format -msgid "" -"Thus you must configure the memory so that the lowest memory block is " -"contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks " -"are mapped in at 16Mb boundaries. In effect this means that you must have a " -"sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. In this " -"case 4Mb is <emphasis>not</emphasis> sufficient." +msgid "Thus you must configure the memory so that the lowest memory block is contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks are mapped in at 16Mb boundaries. In effect this means that you must have a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. In this case 4Mb is <emphasis>not</emphasis> sufficient." msgstr "" #. Tag: para #: hardware.xml:1661 #, no-c-format -msgid "" -"Example: In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four " -"SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS " -"connectors]. You must therefore install the 16Mb SIMM in bank 0; it is then " -"recommended to install the 4Mb SIMM in bank 2." +msgid "Example: In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS connectors]. You must therefore install the 16Mb SIMM in bank 0; it is then recommended to install the 4Mb SIMM in bank 2." msgstr "" #. Tag: title @@ -2922,32 +2676,19 @@ msgstr "" #. Tag: para #: hardware.xml:1673 #, no-c-format -msgid "" -"Especially in the case of older Sun workstations, it is very common for " -"there to be an onboard framebuffer which has been superseded (for example " -"the bwtwo on a sun IPC), and an SBUS card containing a later probably " -"accelerated buffer is then plugged in to an SBUS slot. Under Solaris/SunOS " -"this causes no problems because both cards are initialized." +msgid "Especially in the case of older Sun workstations, it is very common for there to be an onboard framebuffer which has been superseded (for example the bwtwo on a sun IPC), and an SBUS card containing a later probably accelerated buffer is then plugged in to an SBUS slot. Under Solaris/SunOS this causes no problems because both cards are initialized." msgstr "" #. Tag: para #: hardware.xml:1682 #, no-c-format -msgid "" -"However with Linux this can cause a problem, in that the boot PROM monitor " -"may display its output on this additional card; however the linux kernel " -"boot messages may then be directed to the original on board framebuffer, " -"leaving <emphasis>no</emphasis> error messages on the screen, with the " -"machine apparently stuck loading the RAMdisk." +msgid "However with Linux this can cause a problem, in that the boot PROM monitor may display its output on this additional card; however the linux kernel boot messages may then be directed to the original on board framebuffer, leaving <emphasis>no</emphasis> error messages on the screen, with the machine apparently stuck loading the RAMdisk." msgstr "" #. Tag: para #: hardware.xml:1690 #, no-c-format -msgid "" -"To avoid this problem, connect the monitor (if required) to the video card " -"in the lowest numbered SBUS slot (on motherboard card counts as below " -"external slots). Alternatively it is possible to use a serial console." +msgid "To avoid this problem, connect the monitor (if required) to the video card in the lowest numbered SBUS slot (on motherboard card counts as below external slots). Alternatively it is possible to use a serial console." msgstr "" #. Tag: title @@ -2959,45 +2700,25 @@ msgstr "" #. Tag: para #: hardware.xml:1703 #, no-c-format -msgid "" -"You should be using a VGA-compatible display interface for the console " -"terminal. Nearly every modern display card is compatible with VGA. Ancient " -"standards such CGA, MDA, or HGA should also work, assuming you do not " -"require X11 support. Note that X11 is not used during the installation " -"process described in this document." +msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document." msgstr "" #. Tag: para #: hardware.xml:1711 #, no-c-format -msgid "" -"Debian's support for graphical interfaces is determined by the underlying " -"support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work " -"under X.Org. Details on supported graphics buses, cards, monitors, and " -"pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian " -"&release; ships with X.Org version &x11ver;." +msgid "Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian &release; ships with X.Org version &x11ver;." msgstr "" #. Tag: para #: hardware.xml:1720 #, no-c-format -msgid "" -"The X.Org X11 window system is only supported on the SGI Indy and the O2. " -"The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v " -"PCI slots and support VGA emulation or Linux framebuffer on a selected range " -"of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility " -"listing</ulink> for Broadcom evaluation boards is available." +msgid "The X.Org X11 window system is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: para #: hardware.xml:1729 #, no-c-format -msgid "" -"The X.Org X11 window system is supported on some DECstation models. The " -"Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI " -"slots and support VGA emulation or Linux framebuffer on a selected range of " -"graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility " -"listing</ulink> for Broadcom evaluation boards is available." +msgid "The X.Org X11 window system is supported on some DECstation models. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: title @@ -3009,18 +2730,14 @@ msgstr "Laptopok" #. Tag: para #: hardware.xml:1741 #, no-c-format -msgid "" -"Laptops are also supported. Laptops are often specialized or contain " -"proprietary hardware. To see if your particular laptop works well with GNU/" -"Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>" -msgstr "" -"A laptopok is támogatottak. Ezek gyakran specializáltak vagy nem-dokumentált " -"hardvereket tartalmaznak. Annak ellenőrzéséért, hogy a laptopod jól működik-" -"e GNU/Linuxszal, lásd a <ulink url=\"&url-x86-laptop;\">Linux Laptop " -"oldalakat</ulink>" +msgid "Laptops are also supported. Laptops are often specialized or contain proprietary hardware. To see if your particular laptop works well with GNU/Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>" +msgstr "A laptopok is támogatottak. Ezek gyakran specializáltak vagy nem-dokumentált hardvereket tartalmaznak. Annak ellenőrzéséért, hogy a laptopod jól működik-e GNU/Linuxszal, lásd a <ulink url=\"&url-x86-laptop;\">Linux Laptop oldalakat</ulink>" #. Tag: title -#: hardware.xml:1752 hardware.xml:1774 hardware.xml:1794 hardware.xml:1817 +#: hardware.xml:1752 +#: hardware.xml:1774 +#: hardware.xml:1794 +#: hardware.xml:1817 #, no-c-format msgid "Multiple Processors" msgstr "Többszörös processzorok" @@ -3028,136 +2745,50 @@ msgstr "Többszörös processzorok" #. Tag: para #: hardware.xml:1753 #, no-c-format -msgid "" -"Multi-processor support — also called <quote>symmetric multi-" -"processing</quote> or SMP — is available for this architecture. The " -"standard Debian &release; kernel image was compiled with SMP support. This " -"should not prevent installation, since the SMP kernel should boot on non-SMP " -"systems; the kernel will simply cause a bit more overhead." -msgstr "" -"A több-processzoros támogatás — melyre az angol <quote>symmetric multi-" -"processing</quote> vagy SMP — néven is hivatkoznak szintén elérhető " -"ezen architektúrához. Az alap Debian &release; kernel-kép SMP támogatással " -"került lefordításra. Ez nem gátolja a telepítést, mert az SMP kernel nem-SMP " -"rendszeren is elindul; egyszerűen csak kicsit túlműködik." +msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with SMP support. This should not prevent installation, since the SMP kernel should boot on non-SMP systems; the kernel will simply cause a bit more overhead." +msgstr "A több-processzoros támogatás — melyre az angol <quote>symmetric multi-processing</quote> vagy SMP — néven is hivatkoznak szintén elérhető ezen architektúrához. Az alap Debian &release; kernel-kép SMP támogatással került lefordításra. Ez nem gátolja a telepítést, mert az SMP kernel nem-SMP rendszeren is elindul; egyszerűen csak kicsit túlműködik." #. Tag: para #: hardware.xml:1761 #, no-c-format -msgid "" -"In order to optimize the kernel for single CPU systems, you'll have to " -"replace the standard Debian kernel. You can find a discussion of how to do " -"this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version " -"&kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-" -"option;</quote> in the <quote>&smp-config-section;</quote> section of the " -"kernel config." -msgstr "" -"A kernel 1-CPUs rendszerekre optimalizálásához le kell cserélned az alap " -"Debian kernelt. Ennek egy kitárgyalását a <xref linkend=\"kernel-baking\"/> " -"részben találod. Jelenleg (kernel version &kernelversion;) az SMP " -"kikapcsolásának módja a kernel konfiguráció <quote>&smp-config-section;</" -"quote> szakasz <quote>&smp-config-option;</quote> lehetőségének " -"kikapcsolásával lehetséges." +msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." +msgstr "A kernel 1-CPUs rendszerekre optimalizálásához le kell cserélned az alap Debian kernelt. Ennek egy kitárgyalását a <xref linkend=\"kernel-baking\"/> részben találod. Jelenleg (kernel version &kernelversion;) az SMP kikapcsolásának módja a kernel konfiguráció <quote>&smp-config-section;</quote> szakasz <quote>&smp-config-option;</quote> lehetőségének kikapcsolásával lehetséges." #. Tag: para #: hardware.xml:1776 #, no-c-format -msgid "" -"Multi-processor support — also called <quote>symmetric multi-" -"processing</quote> or SMP — is available for this architecture. The " -"standard Debian &release; kernel image was compiled with <firstterm>SMP-" -"alternatives</firstterm> support. This means that the kernel will detect the " -"number of processors (or processor cores) and will automatically deactivate " -"SMP on uniprocessor systems." -msgstr "" -"A több-processzoros támogatás — melyre az angol <quote>symmetric multi-" -"processing</quote> vagy SMP — néven is hivatkoznak szintén elérhető " -"ezen architektúrához. Az alap Debian &release; kernel-kép <firstterm>SMP-" -"alternatíva</firstterm> támogatással került lefordításra. Ez azt jelenti, " -"hogy a kernel érzékeli a processzorok (illetve processzor magok) számát és " -"automatikusan kikapcsolja az SMP-t az 1-processzoros rendszereken." +msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems." +msgstr "A több-processzoros támogatás — melyre az angol <quote>symmetric multi-processing</quote> vagy SMP — néven is hivatkoznak szintén elérhető ezen architektúrához. Az alap Debian &release; kernel-kép <firstterm>SMP-alternatíva</firstterm> támogatással került lefordításra. Ez azt jelenti, hogy a kernel érzékeli a processzorok (illetve processzor magok) számát és automatikusan kikapcsolja az SMP-t az 1-processzoros rendszereken." #. Tag: para #: hardware.xml:1785 #, no-c-format -msgid "" -"The 486 flavour of the Debian kernel image packages for &arch-title; is not " -"compiled with SMP support." -msgstr "" -"A Debian kernel-kép csomagok 486 kivitele &arch-title; architektúrához SMP " -"támogatás nélkül fordított." +msgid "The 486 flavour of the Debian kernel image packages for &arch-title; is not compiled with SMP support." +msgstr "A Debian kernel-kép csomagok 486 kivitele &arch-title; architektúrához SMP támogatás nélkül fordított." #. Tag: para #: hardware.xml:1795 #, no-c-format -msgid "" -"Multi-processor support — also called <quote>symmetric multi-" -"processing</quote> or SMP — is available for this architecture. " -"However, the standard Debian &release; kernel image does not support SMP. " -"This should not prevent installation, since the standard, non-SMP kernel " -"should boot on SMP systems; the kernel will simply use the first CPU." -msgstr "" -"A több-processzoros támogatás — melyre az angol <quote>symmetric multi-" -"processing</quote> vagy SMP — néven is hivatkoznak szintén elérhető " -"ezen architektúrához. De az alap Debian &release; kernel-kép nem támogatja " -"az SMP-t. Ez nem gátolja a telepítést, mert az alap nem-SMP kernel elindul " -"SMP-rendszereken; egyszerűen csak az 1. CPU-t használja." +msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. However, the standard Debian &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." +msgstr "A több-processzoros támogatás — melyre az angol <quote>symmetric multi-processing</quote> vagy SMP — néven is hivatkoznak szintén elérhető ezen architektúrához. De az alap Debian &release; kernel-kép nem támogatja az SMP-t. Ez nem gátolja a telepítést, mert az alap nem-SMP kernel elindul SMP-rendszereken; egyszerűen csak az 1. CPU-t használja." #. Tag: para #: hardware.xml:1804 #, no-c-format -msgid "" -"In order to take advantage of multiple processors, you'll have to replace " -"the standard Debian kernel. You can find a discussion of how to do this in " -"<xref linkend=\"kernel-baking\"/>. At this time (kernel version " -"&kernelversion;) the way you enable SMP is to select <quote>&smp-config-" -"option;</quote> in the <quote>&smp-config-section;</quote> section of the " -"kernel config." -msgstr "" -"A többszörös processzor előnyének kihasználásához le kell cserélned az alap " -"Debian kernelt. Ennek egy kitárgyalását a <xref linkend=\"kernel-baking\"/> " -"részben találod. Jelenleg (kernel version &kernelversion;) az SMP " -"kikapcsolásának módja a kernel konfiguráció <quote>&smp-config-section;</" -"quote> szakasz <quote>&smp-config-option;</quote> lehetőségének " -"bekapcsolásával lehetséges." +msgid "In order to take advantage of multiple processors, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." +msgstr "A többszörös processzor előnyének kihasználásához le kell cserélned az alap Debian kernelt. Ennek egy kitárgyalását a <xref linkend=\"kernel-baking\"/> részben találod. Jelenleg (kernel version &kernelversion;) az SMP kikapcsolásának módja a kernel konfiguráció <quote>&smp-config-section;</quote> szakasz <quote>&smp-config-option;</quote> lehetőségének bekapcsolásával lehetséges." #. Tag: para #: hardware.xml:1818 #, no-c-format -msgid "" -"Multi-processor support — also called <quote>symmetric multi-" -"processing</quote> or SMP — is available for this architecture, and is " -"supported by a precompiled Debian kernel image. Depending on your install " -"media, this SMP-capable kernel may or may not be installed by default. This " -"should not prevent installation, since the standard, non-SMP kernel should " -"boot on SMP systems; the kernel will simply use the first CPU." -msgstr "" -"A több-processzoros támogatás — melyre az angol <quote>symmetric multi-" -"processing</quote> vagy SMP — néven is hivatkoznak szintén elérhető " -"ezen architektúrához. A telepítő médiától függően települ vagy sem " -"alapértelmezetten az SMP-képes kernel. Ez nem gátolja a telepítést, mert az " -"alap nem-SMP kernel elindul SMP-rendszereken; egyszerűen csak az 1. CPU-t " -"használja." +msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture, and is supported by a precompiled Debian kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." +msgstr "A több-processzoros támogatás — melyre az angol <quote>symmetric multi-processing</quote> vagy SMP — néven is hivatkoznak szintén elérhető ezen architektúrához. A telepítő médiától függően települ vagy sem alapértelmezetten az SMP-képes kernel. Ez nem gátolja a telepítést, mert az alap nem-SMP kernel elindul SMP-rendszereken; egyszerűen csak az 1. CPU-t használja." #. Tag: para #: hardware.xml:1828 #, no-c-format -msgid "" -"In order to take advantage of multiple processors, you should check to see " -"if a kernel package that supports SMP is installed, and if not, choose an " -"appropriate kernel package. You can also build your own customized kernel to " -"support SMP. You can find a discussion of how to do this in <xref linkend=" -"\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way " -"you enable SMP is to select <quote>&smp-config-option;</quote> in the " -"<quote>&smp-config-section;</quote> section of the kernel config." -msgstr "" -"A többszörös processzor előnyének kihasználásához ellenőrizd, SMP-támogató " -"kernel-csomag települt-e, s ha nem, válassz megfelelőt. Saját SMP-támogató " -"kernelt is építhetsz. Ennek egy kitárgyalását a <xref linkend=\"kernel-baking" -"\"/> részben találod. Jelenleg (kernel version &kernelversion;) az SMP " -"kikapcsolásának módja a kernel konfiguráció <quote>&smp-config-section;</" -"quote> szakasz <quote>&smp-config-option;</quote> lehetőségének " -"bekapcsolásával lehetséges." +msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package. You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." +msgstr "A többszörös processzor előnyének kihasználásához ellenőrizd, SMP-támogató kernel-csomag települt-e, s ha nem, válassz megfelelőt. Saját SMP-támogató kernelt is építhetsz. Ennek egy kitárgyalását a <xref linkend=\"kernel-baking\"/> részben találod. Jelenleg (kernel version &kernelversion;) az SMP kikapcsolásának módja a kernel konfiguráció <quote>&smp-config-section;</quote> szakasz <quote>&smp-config-option;</quote> lehetőségének bekapcsolásával lehetséges." #. Tag: title #: hardware.xml:1849 @@ -3167,20 +2798,9 @@ msgstr "Telepítő média" #. Tag: para #: hardware.xml:1851 -#, fuzzy, no-c-format -msgid "" -"This section will help you determine which different media types you can use " -"to install Debian. For example, if you have a floppy disk drive on your " -"machine, it can be used to install Debian. There is a whole chapter devoted " -"to media, <xref linkend=\"install-methods\"/>, which lists the advantages " -"and disadvantages of each media type. You may want to refer back to this " -"page once you reach that section." -msgstr "" -"E szakasz leírja, milyen média típusokat használhatsz a Debian telepítésére. " -"Például, ha van egy flopi lemez meghajtód a gépen, telepíthető róla a " -"Debian. Van egy egész fejezet, mely erről szól, a <xref linkend=\"install-" -"methods\"/>, mely leírja minden média típus előnyét és hátrányát. Amennyiben " -"odaugrasz, vissza is térhetsz majd ide." +#, no-c-format +msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used to install Debian. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section." +msgstr "E szakasz leírja, milyen média típusokat használhatsz a Debian telepítésére. Például, ha van egy flopi lemez meghajtód a gépen, telepíthető róla a Debian. Van egy egész, médiára szánt fejezet, a <xref linkend=\"install-methods\"/>, mely leírja minden média típus előnyét és hátrányát. Amennyiben odaugrasz, vissza is térhetsz majd ide." #. Tag: title #: hardware.xml:1862 @@ -3191,14 +2811,8 @@ msgstr "Flopik" #. Tag: para #: hardware.xml:1863 #, no-c-format -msgid "" -"In some cases, you'll have to do your first boot from floppy disks. " -"Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch " -"floppy drive." -msgstr "" -"Lehet, hogy semmilyen más lehetőség nem áll rendelkezésedre, mint egy " -"flopiról indítani. Ehhez csak egy nagy-sűrűségű (1440 kilobyte-os) 3,5 " -"hüvelykes flopi meghajtó kell." +msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive." +msgstr "Lehet, hogy semmilyen más lehetőség nem áll rendelkezésedre, mint egy flopiról indítani. Ehhez csak egy nagy-sűrűségű (1440 kilobyte-os) 3,5 hüvelykes flopi meghajtó kell." #. Tag: para #: hardware.xml:1869 @@ -3215,154 +2829,68 @@ msgstr "CD-ROM/DVD-ROM" #. Tag: para #: hardware.xml:1878 #, no-c-format -msgid "" -"Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-" -"ROMs and DVD-ROMs, because both technologies are really the same from the " -"operating system's point of view, except for some very old nonstandard CD-" -"ROM drives which are neither SCSI nor IDE/ATAPI." -msgstr "" -"Ha e kézikönyvben azt látod: <quote>CD-ROM</quote>, az a CD-ROM és DVD-ROM " -"eszközökre egyaránt vonatkozik, mert az operációs rendszer szempontjából ez " -"ugyanaz, kivéve egyes nagyon régi nem-szabványos CD-ROM meghajtókat, melyek " -"nem SCSI vagy IDE/ATAPI elvűek." +msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI." +msgstr "Ha e kézikönyvben azt látod: <quote>CD-ROM</quote>, az a CD-ROM és DVD-ROM eszközökre egyaránt vonatkozik, mert az operációs rendszer szempontjából ez ugyanaz, kivéve egyes nagyon régi nem-szabványos CD-ROM meghajtókat, melyek nem SCSI vagy IDE/ATAPI elvűek." #. Tag: para #: hardware.xml:1885 #, no-c-format -msgid "" -"CD-ROM based installation is supported for some architectures. On machines " -"which support bootable CD-ROMs, you should be able to do a completely " -"<phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-" -"less</phrase> installation. Even if your system doesn't support booting from " -"a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to " -"install your system, once you've booted up by other means; see <xref linkend=" -"\"boot-installer\"/>." -msgstr "" -"A CD-ROM alapú telepítés a legtöbb architektúrán támogatott. Az indítható CD-" -"ROM lemezeket támogató gépeken teljesen <phrase arch=\"not-s390\">flopi-" -"mentes</phrase> <phrase arch=\"s390\">szalag-mentes</phrase> telepítés " -"végezhető. Még ha a rendszer nem is támogatja a CD-ROM lemezről indítást, a " -"CD-ROM más módokkal együtt használható a telepítésre, miután az indítás " -"megtörtént másképpen; lásd a <xref linkend=\"boot-installer\"/> részt." +msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>." +msgstr "A CD-ROM alapú telepítés a legtöbb architektúrán támogatott. Az indítható CD-ROM lemezeket támogató gépeken teljesen <phrase arch=\"not-s390\">flopi-mentes</phrase> <phrase arch=\"s390\">szalag-mentes</phrase> telepítés végezhető. Még ha a rendszer nem is támogatja a CD-ROM lemezről indítást, a CD-ROM más módokkal együtt használható a telepítésre, miután az indítás megtörtént másképpen; lásd a <xref linkend=\"boot-installer\"/> részt." #. Tag: para #: hardware.xml:1897 #, no-c-format -msgid "" -"Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard " -"CD interfaces supported by Linux are supported by the boot disks (such as " -"Mitsumi and Matsushita drives). However, these models might require special " -"boot parameters or other massaging to get them to work, and booting off " -"these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;" -"\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs " -"with Linux." -msgstr "" -"A SCSI és IDE/ATAPI CD-ROM meghajtók egyaránt támogatottak. Ráadásul az " -"indító lemezek a Linux által támogatott nem-szabványos CD felületeket is " -"támogatják (például Mitsumi és Matsushita meghajtók). Fontos tudni, hogy e " -"modellek különleges indító paramétereket vagy más kezeléseket igényelnek, " -"így a róluk való indítás nem túl örömteli. A <ulink url=\"&url-cd-howto;" -"\">Linux CD-ROM HOGYAN</ulink> nagyon mély leírást tartalmaz a CD-ROM " -"használatáról Linuxon." +msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the boot disks (such as Mitsumi and Matsushita drives). However, these models might require special boot parameters or other massaging to get them to work, and booting off these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux." +msgstr "A SCSI és IDE/ATAPI CD-ROM meghajtók egyaránt támogatottak. Ráadásul az indító lemezek a Linux által támogatott nem-szabványos CD felületeket is támogatják (például Mitsumi és Matsushita meghajtók). Fontos tudni, hogy e modellek különleges indító paramétereket vagy más kezeléseket igényelnek, így a róluk való indítás nem túl örömteli. A <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOGYAN</ulink> nagyon mély leírást tartalmaz a CD-ROM használatáról Linuxon." #. Tag: para #: hardware.xml:1907 #, no-c-format -msgid "" -"USB CD-ROM drives are also supported, as are FireWire devices that are " -"supported by the ohci1394 and sbp2 drivers." -msgstr "" -"Az USB CD-ROM és az ohci1394 és sbp2 meghajtók által támogatott FireWire " -"eszközök szintén támogatottak." +msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." +msgstr "Az USB CD-ROM és az ohci1394 és sbp2 meghajtók által támogatott FireWire eszközök szintén támogatottak." #. Tag: para #: hardware.xml:1912 #, no-c-format -msgid "" -"Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as " -"the controller is supported by the SRM console. This rules out many add-on " -"controller cards, but most integrated IDE and SCSI chips and controller " -"cards that were provided by the manufacturer can be expected to work. To " -"find out whether your device is supported from the SRM console, see the " -"<ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>." -msgstr "" -"A SCSI és IDE/ATAPI CD-ROM eszközök is támogatottak &arch-title; " -"architektúrán, ha az SRM konzol támogatja a vezérlőt. Ez kizár több " -"vezérlőkártyát, de a gyártó által nyújtott legtöbb integrált IDE és SCSI " -"csip és vezérlőkártya általában működik. Az SRM konzol által támogatott " -"eszközökről lásd az <ulink url=\"&url-srm-howto;\">SRM HOGYAN</ulink> címet." +msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as the controller is supported by the SRM console. This rules out many add-on controller cards, but most integrated IDE and SCSI chips and controller cards that were provided by the manufacturer can be expected to work. To find out whether your device is supported from the SRM console, see the <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>." +msgstr "A SCSI és IDE/ATAPI CD-ROM eszközök is támogatottak &arch-title; architektúrán, ha az SRM konzol támogatja a vezérlőt. Ez kizár több vezérlőkártyát, de a gyártó által nyújtott legtöbb integrált IDE és SCSI csip és vezérlőkártya általában működik. Az SRM konzol által támogatott eszközökről lásd az <ulink url=\"&url-srm-howto;\">SRM HOGYAN</ulink> címet." #. Tag: para #: hardware.xml:1921 #, no-c-format -msgid "" -"IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-" -"ROMs are also supported." -msgstr "" -"Az IDE/ATAPI CD-ROM eszközöket minden ARM gép támogatja. A RiscPC a SCSI CD-" -"ROM eszközöket is." +msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-ROMs are also supported." +msgstr "Az IDE/ATAPI CD-ROM eszközöket minden ARM gép támogatja. A RiscPC a SCSI CD-ROM eszközöket is." #. Tag: para #: hardware.xml:1926 #, no-c-format -msgid "" -"On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of " -"working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM " -"drives sold on the PC market do not have this capability. If your CD-ROM " -"drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</" -"quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. " -"To start the install, simply choose the <quote>System installation</quote> " -"entry in the firmware. The Broadcom BCM91250A supports standard IDE devices, " -"including CD-ROM drives, but CD images for this platform are currently not " -"provided because the firmware doesn't recognize CD drives. In order to " -"install Debian on an Broadcom BCM91480B evaluation board, you need an PCI " -"IDE, SATA or SCSI card." +msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card." msgstr "" #. Tag: para #: hardware.xml:1941 #, no-c-format -msgid "" -"On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive capable of " -"working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM " -"drives sold on the PC market do not have this capability. If your CD-ROM " -"drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</" -"quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position." +msgid "On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position." msgstr "" #. Tag: para #: hardware.xml:1950 #, no-c-format -msgid "" -"CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-" -"based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal " -"DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the " -"R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal " -"DECstation 5000/50)." +msgid "CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal DECstation 5000/50)." msgstr "" #. Tag: para #: hardware.xml:1959 #, no-c-format -msgid "" -"To boot from CD, issue the command <userinput>boot <replaceable>#</" -"replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware " -"prompt, where <replaceable>#</replaceable> is the number of the TurboChannel " -"device from which to boot (3 on most DECstations) and <replaceable>id</" -"replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass " -"additional parameters, they can optionally be appended with the following " -"syntax:" +msgid "To boot from CD, issue the command <userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware prompt, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot (3 on most DECstations) and <replaceable>id</replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" #. Tag: userinput #: hardware.xml:1971 #, no-c-format -msgid "" -"boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> " -"param1=value1 param2=value2 ..." -msgstr "" -"boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> " -"param1=érték1 param2=érték2 ..." +msgid "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=value1 param2=value2 ..." +msgstr "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=érték1 param2=érték2 ..." #. Tag: title #: hardware.xml:1978 @@ -3373,34 +2901,20 @@ msgstr "Merevlemez" #. Tag: para #: hardware.xml:1980 #, no-c-format -msgid "" -"Booting the installation system directly from a hard disk is another option " -"for many architectures. This will require some other operating system to " -"load the installer onto the hard disk." -msgstr "" -"A telepítő rendszer közvetlen merevlemezről indítása egy újabb lehetőség " -"számos architektúrán. Ez egy másik operációs rendszert igényel a telepítő " -"merevlemezre töltéséhez." +msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk." +msgstr "A telepítő rendszer közvetlen merevlemezről indítása egy újabb lehetőség számos architektúrán. Ez egy másik operációs rendszert igényel a telepítő merevlemezre töltéséhez." #. Tag: para #: hardware.xml:1986 #, no-c-format -msgid "" -"In fact, installation from your local disk is the preferred installation " -"technique for most &architecture; machines." -msgstr "" -"Valójában sok &architecture; gépen a helyi lemezről telepítés a legjobb " -"telepítő technika." +msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines." +msgstr "Valójában sok &architecture; gépen a helyi lemezről telepítés a legjobb telepítő technika." #. Tag: para #: hardware.xml:1991 #, no-c-format -msgid "" -"Although the &arch-title; does not allow booting from SunOS (Solaris), you " -"can install from a SunOS partition (UFS slices)." -msgstr "" -"Bár a &arch-title; nem teszi lehetővé a SunOS (Solaris) rendszerről " -"indítást, telepíthetsz egy SunOS partícióról (UFS szeletek)." +msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)." +msgstr "Bár a &arch-title; nem teszi lehetővé a SunOS (Solaris) rendszerről indítást, telepíthetsz egy SunOS partícióról (UFS szeletek)." #. Tag: title #: hardware.xml:1999 @@ -3411,19 +2925,8 @@ msgstr "USB háttértároló" #. Tag: para #: hardware.xml:2001 #, no-c-format -msgid "" -"Many Debian boxes need their floppy and/or CD-ROM drives only for setting up " -"the system and for rescue purposes. If you operate some servers, you will " -"probably already have thought about omitting those drives and using an USB " -"memory stick for installing and (when necessary) for recovering the system. " -"This is also useful for small systems which have no room for unnecessary " -"drives." -msgstr "" -"Sok Debian gépnél csak a telepítésre vagy mentésre merülne fel flopi és/vagy " -"CD-ROM meghajtók használata. Ha üzemeltetsz pár kiszolgálót, alighanem " -"eszedbe fog jutni e meghajtók elhagyása és USB háttértároló használata a " -"rendszer telepítésére és (ha szükséges) visszaállítására. Ez kis " -"rendszereknél is hasznos, ahol nincs hely felesleges meghajtóknak." +msgid "Many Debian boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives." +msgstr "Sok Debian gépnél csak a telepítésre vagy mentésre merülne fel flopi és/vagy CD-ROM meghajtók használata. Ha üzemeltetsz pár kiszolgálót, alighanem eszedbe fog jutni e meghajtók elhagyása és USB háttértároló használata a rendszer telepítésére és (ha szükséges) visszaállítására. Ez kis rendszereknél is hasznos, ahol nincs hely felesleges meghajtóknak." #. Tag: title #: hardware.xml:2013 @@ -3434,34 +2937,20 @@ msgstr "Hálózat" #. Tag: para #: hardware.xml:2015 #, no-c-format -msgid "" -"You can also <emphasis>boot</emphasis> your system over the network. <phrase " -"arch=\"mips\">This is the preferred installation technique for Mips.</phrase>" -msgstr "" -"A rendszer <emphasis>indítása</emphasis> hálózatról is lehetséges. <phrase " -"arch=\"mips\">Ez a fő telepítő mód Mips gépekhez.</phrase>" +msgid "You can also <emphasis>boot</emphasis> your system over the network. <phrase arch=\"mips\">This is the preferred installation technique for Mips.</phrase>" +msgstr "A rendszer <emphasis>indítása</emphasis> hálózatról is lehetséges. <phrase arch=\"mips\">Ez a fő telepítő mód Mips gépekhez.</phrase>" #. Tag: para #: hardware.xml:2021 #, no-c-format -msgid "" -"Diskless installation, using network booting from a local area network and " -"NFS-mounting of all local filesystems, is another option." -msgstr "" -"A lemez-nélküli telepítés helyi hálózatról indítással és az összes helyi " -"fájlrendszer NFS-csatolásával egy másik lehetőség." +msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." +msgstr "A lemez-nélküli telepítés helyi hálózatról indítással és az összes helyi fájlrendszer NFS-csatolásával egy másik lehetőség." #. Tag: para #: hardware.xml:2026 #, no-c-format -msgid "" -"After the operating system kernel is installed, you can install the rest of " -"your system via any sort of network connection (including PPP after " -"installation of the base system), via FTP or HTTP." -msgstr "" -"Az operációs rendszer magjának telepítése után, a rendszer többi része " -"bármilyen hálózati kapcsolaton át telepíthető (ideértve a PPP-t is az " -"alaprendszer telepítése után) FTP vagy HTTP segítségével." +msgid "After the operating system kernel is installed, you can install the rest of your system via any sort of network connection (including PPP after installation of the base system), via FTP or HTTP." +msgstr "Az operációs rendszer magjának telepítése után, a rendszer többi része bármilyen hálózati kapcsolaton át telepíthető (ideértve a PPP-t is az alaprendszer telepítése után) FTP vagy HTTP segítségével." #. Tag: title #: hardware.xml:2035 @@ -3472,17 +2961,8 @@ msgstr "Un*x vagy GNU rendszer" #. Tag: para #: hardware.xml:2037 #, no-c-format -msgid "" -"If you are running another Unix-like system, you could use it to install " -"&debian; without using the &d-i; described in the rest of the manual. This " -"kind of install may be useful for users with otherwise unsupported hardware " -"or on hosts which can't afford downtime. If you are interested in this " -"technique, skip to the <xref linkend=\"linux-upgrade\"/>." -msgstr "" -"Ha más Unix-szerű rendszert futtatsz, használhatod a Debian telepítésére a " -"&d-i; nélkül e kézikönyvben is leírt módon. Ez hasznos a másképp nem-" -"támogatott hardvert használóknak vagy ha a gépen a telepítéskor nem lehet " -"üzemszünet." +msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of the manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." +msgstr "Ha más Unix-szerű rendszert futtatsz, használhatod a Debian telepítésére a &d-i; nélkül e kézikönyvben is leírt módon. Ez hasznos a másképp nem-támogatott hardvert használóknak vagy ha a gépen a telepítéskor nem lehet üzemszünet." #. Tag: title #: hardware.xml:2049 @@ -3493,150 +2973,62 @@ msgstr "Támogatott tárolók" #. Tag: para #: hardware.xml:2051 #, no-c-format -msgid "" -"The Debian boot disks contain a kernel which is built to maximize the number " -"of systems it runs on. Unfortunately, this makes for a larger kernel, which " -"includes many drivers that won't be used for your machine (see <xref linkend=" -"\"kernel-baking\"/> to learn how to build your own kernel). Support for the " -"widest possible range of devices is desirable in general, to ensure that " -"Debian can be installed on the widest array of hardware." -msgstr "" -"A Debian indító lemezek kernelei úgy készülnek, hogy a lehető legtöbb " -"rendszert támogassák. Természetesen ez nagyobb, több az adott gépen nem-" -"használt meghajtót tartalmazó kernelt ad (lásd a <xref linkend=\"kernel-" -"baking\"/> részt saját kernel készítéséhez). A lehető legtöbb eszköz " -"támogatása általában jó, ez biztosítja a Debian telepíthetőségét a legtöbb " -"hardveren." +msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware." +msgstr "A Debian indító lemezek kernelei úgy készülnek, hogy a lehető legtöbb rendszert támogassák. Természetesen ez nagyobb, több az adott gépen nem-használt meghajtót tartalmazó kernelt ad (lásd a <xref linkend=\"kernel-baking\"/> részt saját kernel készítéséhez). A lehető legtöbb eszköz támogatása általában jó, ez biztosítja a Debian telepíthetőségét a legtöbb hardveren." #. Tag: para #: hardware.xml:2061 #, no-c-format -msgid "" -"Generally, the Debian installation system includes support for floppies, IDE " -"drives, IDE floppies, parallel port IDE devices, SCSI controllers and " -"drives, USB, and FireWire. The supported file systems include FAT, Win-32 " -"FAT extensions (VFAT) and NTFS." -msgstr "" -"Általánosságban a Debian telepítő rendszer támogatja a flopikat, IDE " -"meghajtókat, IDE flopikat, párhuzamos portos IDE eszközöket, SCSI vezérlőket " -"és meghajtókat, USB-t és FireWire-t. A támogatott szabvány fájlrendszerek " -"mellett a FAT, Win-32 FAT bővítés (VFAT) és NTFS is támogatott." +msgid "Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." +msgstr "Általánosságban a Debian telepítő rendszer támogatja a flopikat, IDE meghajtókat, IDE flopikat, párhuzamos portos IDE eszközöket, SCSI vezérlőket és meghajtókat, USB-t és FireWire-t. A támogatott szabvány fájlrendszerek mellett a FAT, Win-32 FAT bővítés (VFAT) és NTFS is támogatott." #. Tag: para #: hardware.xml:2068 #, no-c-format -msgid "" -"Disk interfaces that emulate the <quote>AT</quote> hard disk interface " -"— often called MFM, RLL, IDE, or ATA — are supported. Very old " -"8–bit hard disk controllers used in the IBM XT computer are supported " -"only as a module. SCSI disk controllers from many different manufacturers " -"are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware " -"Compatibility HOWTO</ulink> for more details." -msgstr "" -"Az <quote>AT</quote>-emuláló lemez felületek — nevük gyakran MFM, RLL, " -"IDE, vagy ATA — támogatottak. Az IBM XT számítógépben használt nagyon " -"régi 8–bites merevlemez vezérlők modulként támogatottak. Rengeteg " -"különböző gyártó által szállított SCSI lemez vezérlő támogatott. Lásd a " -"<ulink url=\"&url-hardware-howto;\">Linux Hardver kompatibilitás HOGYAN</" -"ulink> leírást további részletekért." +msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or ATA — are supported. Very old 8–bit hard disk controllers used in the IBM XT computer are supported only as a module. SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." +msgstr "Az <quote>AT</quote>-emuláló lemez felületek — nevük gyakran MFM, RLL, IDE, vagy ATA — támogatottak. Az IBM XT számítógépben használt nagyon régi 8–bites merevlemez vezérlők modulként támogatottak. Rengeteg különböző gyártó által szállított SCSI lemez vezérlő támogatott. Lásd a <ulink url=\"&url-hardware-howto;\">Linux Hardver kompatibilitás HOGYAN</ulink> leírást további részletekért." #. Tag: para #: hardware.xml:2078 #, no-c-format -msgid "" -"Pretty much all storage systems supported by the Linux kernel are supported " -"by the Debian installation system. Note that the current Linux kernel does " -"not support floppies on the Macintosh at all, and the Debian installation " -"system doesn't support floppies for Amigas. Also supported on the Atari is " -"the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) " -"file system. Amigas support the FAT file system, and HFS as a module." -msgstr "" -"A Linux kernel által támogatott tárolókat a Debian telepítő rendszer " -"támogatja. Jó tudni, hogy a jelenlegi Linux kernel nem támogatja a flopikat " -"Macintoshon, és a Debian telepítő rendszer nem támogatja a flopikat Amigán. " -"Az Atarin a Macintosh HFS támogatott, az AFFS modulként. A macek támogatják " -"az Atari (FAT) fájlrendszert. Az Amigák ezt támogatják, a HFS-t modulként." +msgid "Pretty much all storage systems supported by the Linux kernel are supported by the Debian installation system. Note that the current Linux kernel does not support floppies on the Macintosh at all, and the Debian installation system doesn't support floppies for Amigas. Also supported on the Atari is the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) file system. Amigas support the FAT file system, and HFS as a module." +msgstr "A Linux kernel által támogatott tárolókat a Debian telepítő rendszer támogatja. Jó tudni, hogy a jelenlegi Linux kernel nem támogatja a flopikat Macintoshon, és a Debian telepítő rendszer nem támogatja a flopikat Amigán. Az Atarin a Macintosh HFS támogatott, az AFFS modulként. A macek támogatják az Atari (FAT) fájlrendszert. Az Amigák ezt támogatják, a HFS-t modulként." #. Tag: para #: hardware.xml:2088 #, no-c-format -msgid "" -"Any storage system supported by the Linux kernel is also supported by the " -"boot system. The following SCSI drivers are supported in the default kernel: " -"<itemizedlist> <listitem><para> Sparc ESP </para></listitem> " -"<listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec " -"AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></" -"listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also " -"supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC " -"Processors FAQ</ulink> for more information on SPARC hardware supported by " -"the Linux kernel." -msgstr "" -"Minden Linux kernel által támogatott tárolót támogatja az indító rendszer. " -"Az alábbi SCSI meghajtók támogatottak az alapkernelben: <itemizedlist> " -"<listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic," -"ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> " -"<listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> " -"Az IDE rendszerek (mint az UltraSPARC 5) szintén támogatottak. Lásd a <ulink " -"url=\"&url-sparc-linux-faq;\">Linux SPARC Processzorokra GYIK</ulink> " -"leírást a Linux kernel által támogatott valamennyi SPARC hardverért." +msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel." +msgstr "Minden Linux kernel által támogatott tárolót támogatja az indító rendszer. Az alábbi SCSI meghajtók támogatottak az alapkernelben: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> Az IDE rendszerek (mint az UltraSPARC 5) szintén támogatottak. Lásd a <ulink url=\"&url-sparc-linux-faq;\">Linux SPARC Processzorokra GYIK</ulink> leírást a Linux kernel által támogatott valamennyi SPARC hardverért." #. Tag: para #: hardware.xml:2121 #, no-c-format -msgid "" -"Any storage system supported by the Linux kernel is also supported by the " -"boot system. This includes both SCSI and IDE disks. Note, however, that on " -"many systems, the SRM console is unable to boot from IDE drives, and the " -"Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;" -"\"></ulink> for more information on booting the Jensen)" -msgstr "" -"Minden Linux kernel által támogatott tárolót támogatja az indító rendszer. " -"Ez a SCSI és IDE lemezeket is jelenti. Sok rendszeren az SRM konzol nem " -"indul IDE meghajtókról, és a Jensen nem indul flopiról. (lásd a <ulink url=" -"\"&url-jensen-howto;\"></ulink> leírást erről)" +msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This includes both SCSI and IDE disks. Note, however, that on many systems, the SRM console is unable to boot from IDE drives, and the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;\"></ulink> for more information on booting the Jensen)" +msgstr "Minden Linux kernel által támogatott tárolót támogatja az indító rendszer. Ez a SCSI és IDE lemezeket is jelenti. Sok rendszeren az SRM konzol nem indul IDE meghajtókról, és a Jensen nem indul flopiról. (lásd a <ulink url=\"&url-jensen-howto;\"></ulink> leírást erről)" #. Tag: para #: hardware.xml:2130 #, no-c-format -msgid "" -"Any storage system supported by the Linux kernel is also supported by the " -"boot system. Note that the current Linux kernel does not support floppies on " -"CHRP systems at all." -msgstr "" -"Minden Linux kernel által támogatott tárolót támogatja az indító rendszer. A " -"jelenlegi Linux kernel nem támogatja a flopit CHRP rendszereken." +msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all." +msgstr "Minden Linux kernel által támogatott tárolót támogatja az indító rendszer. A jelenlegi Linux kernel nem támogatja a flopit CHRP rendszereken." #. Tag: para #: hardware.xml:2136 #, no-c-format -msgid "" -"Any storage system supported by the Linux kernel is also supported by the " -"boot system. Note that the current Linux kernel does not support the floppy " -"drive." -msgstr "" -"Minden Linux kernel által támogatott tárolót támogatja az indító rendszer. A " -"jelenlegi Linux kernel nem támogatja a flopi meghajtót." +msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive." +msgstr "Minden Linux kernel által támogatott tárolót támogatja az indító rendszer. A jelenlegi Linux kernel nem támogatja a flopi meghajtót." #. Tag: para #: hardware.xml:2142 #, no-c-format -msgid "" -"Any storage system supported by the Linux kernel is also supported by the " -"boot system." -msgstr "" -"Minden Linux kernel által támogatott tárolót támogatja az indító rendszer." +msgid "Any storage system supported by the Linux kernel is also supported by the boot system." +msgstr "Minden Linux kernel által támogatott tárolót támogatja az indító rendszer." #. Tag: para #: hardware.xml:2147 #, no-c-format -msgid "" -"Any storage system supported by the Linux kernel is also supported by the " -"boot system. This means that FBA and ECKD DASDs are supported with the old " -"Linux disk layout (ldl) and the new common S/390 disk layout (cdl)." -msgstr "" -"Minden Linux kernel által támogatott tárolót támogatja az indító rendszer. " -"Ez alapján a régi Linux disk layout (ldl) és az új common S/390 disk layout " -"(cdl) támogatja az FBA-t és az ECKD DASD tárolókat." +msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)." +msgstr "Minden Linux kernel által támogatott tárolót támogatja az indító rendszer. Ez alapján a régi Linux disk layout (ldl) és az új common S/390 disk layout (cdl) támogatja az FBA-t és az ECKD DASD tárolókat." #. Tag: title #: hardware.xml:2164 @@ -3647,66 +3039,37 @@ msgstr "Perifériák és más hardverek" #. Tag: para #: hardware.xml:2165 #, no-c-format -msgid "" -"Linux supports a large variety of hardware devices such as mice, printers, " -"scanners, PCMCIA and USB devices. However, most of these devices are not " -"required while installing the system." -msgstr "" -"A Linux rengeteg hardver eszközt támogat, mint például az egereket, " -"nyomtatókat, szkennereket, PCMCIA és USB eszközöket. Ezek nem kötelezőek a " -"telepítéskor." +msgid "Linux supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system." +msgstr "A Linux rengeteg hardver eszközt támogat, mint például az egereket, nyomtatókat, szkennereket, PCMCIA és USB eszközöket. Ezek nem kötelezőek a telepítéskor." #. Tag: para #: hardware.xml:2171 #, no-c-format -msgid "" -"USB hardware generally works fine, only some USB keyboards may require " -"additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)." -msgstr "" -"Az USB eszközök általában tökéletesen működnek, csak pár USB billentyűzethez " -"kell egyéni beállítás (lásd a <xref linkend=\"usb-keyboard-config\"/> " -"leírást)." +msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)." +msgstr "Az USB eszközök általában tökéletesen működnek, csak pár USB billentyűzethez kell egyéni beállítás (lásd a <xref linkend=\"usb-keyboard-config\"/> leírást)." #. Tag: para #: hardware.xml:2177 #, no-c-format -msgid "" -"Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware " -"Compatibility HOWTO</ulink> to determine whether your specific hardware is " -"supported by Linux." -msgstr "" -"Ismét csak lásd a <ulink url=\"&url-hardware-howto;\">Linux Hardver " -"kompatibilitás HOGYAN</ulink> leírást a Linux által támogatott hardverről." +msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux." +msgstr "Ismét csak lásd a <ulink url=\"&url-hardware-howto;\">Linux Hardver kompatibilitás HOGYAN</ulink> leírást a Linux által támogatott hardverről." #. Tag: para #: hardware.xml:2183 #, no-c-format -msgid "" -"Package installations from XPRAM and tape are not supported by this system. " -"All packages that you want to install need to be available on a DASD or over " -"the network using NFS, HTTP or FTP." -msgstr "" -"A csomagok telepítését XPRAM vagy szalagos egységről e rendszer nem " -"támogatja. A telepíteni kívánt csomagoknak egy DASD tárolóról vagy " -"hálózatról NFS, HTTP vag FTP használatával elérhetőnek kell lennie." +msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP." +msgstr "A csomagok telepítését XPRAM vagy szalagos egységről e rendszer nem támogatja. A telepíteni kívánt csomagoknak egy DASD tárolóról vagy hálózatról NFS, HTTP vag FTP használatával elérhetőnek kell lennie." #. Tag: para #: hardware.xml:2189 #, no-c-format -msgid "" -"The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 " -"bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation " -"board features four 64 bit PCI slots." +msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots." msgstr "" #. Tag: para #: hardware.xml:2195 #, no-c-format -msgid "" -"The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 " -"bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation " -"board features four 64 bit PCI slots. The Cobalt RaQ has no support for " -"additional devices but the Qube has one PCI slot." +msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." msgstr "" #. Tag: title @@ -3718,42 +3081,25 @@ msgstr "" #. Tag: para #: hardware.xml:2207 #, no-c-format -msgid "" -"There are several vendors, who ship systems with Debian or other " -"distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</" -"ulink>. You might pay more for the privilege, but it does buy a level of " -"peace of mind, since you can be sure that the hardware is well-supported by " -"GNU/Linux." +msgid "There are several vendors, who ship systems with Debian or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux." msgstr "" #. Tag: para #: hardware.xml:2215 #, no-c-format -msgid "" -"Unfortunately, it's quite rare to find any vendor shipping new &arch-title; " -"machines at all." +msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all." msgstr "" #. Tag: para #: hardware.xml:2220 #, no-c-format -msgid "" -"If you do have to buy a machine with Windows bundled, carefully read the " -"software license that comes with Windows; you may be able to reject the " -"license and obtain a rebate from your vendor. Searching the Internet for " -"<quote>windows refund</quote> may get you some useful information to help " -"with that." +msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that." msgstr "" #. Tag: para #: hardware.xml:2228 #, no-c-format -msgid "" -"Whether or not you are purchasing a system with Linux bundled, or even a " -"used system, it is still important to check that your hardware is supported " -"by the Linux kernel. Check if your hardware is listed in the references " -"found above. Let your salesperson (if any) know that you're shopping for a " -"Linux system. Support Linux-friendly hardware vendors." +msgid "Whether or not you are purchasing a system with Linux bundled, or even a used system, it is still important to check that your hardware is supported by the Linux kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a Linux system. Support Linux-friendly hardware vendors." msgstr "" #. Tag: title @@ -3765,34 +3111,19 @@ msgstr "" #. Tag: para #: hardware.xml:2240 #, no-c-format -msgid "" -"Some hardware manufacturers simply won't tell us how to write drivers for " -"their hardware. Others won't allow us access to the documentation without a " -"non-disclosure agreement that would prevent us from releasing the Linux " -"source code." +msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the Linux source code." msgstr "" #. Tag: para #: hardware.xml:2247 #, no-c-format -msgid "" -"Another example is the proprietary hardware in the older Macintosh line. In " -"fact, no specifications or documentation have ever been released for any " -"Macintosh hardware, most notably the ADB controller (used by the mouse and " -"keyboard), the floppy controller, and all acceleration and CLUT manipulation " -"of the video hardware (though we do now support CLUT manipulation on nearly " -"all internal video chips). In a nutshell, this explains why the Macintosh " -"Linux port lags behind other Linux ports." +msgid "Another example is the proprietary hardware in the older Macintosh line. In fact, no specifications or documentation have ever been released for any Macintosh hardware, most notably the ADB controller (used by the mouse and keyboard), the floppy controller, and all acceleration and CLUT manipulation of the video hardware (though we do now support CLUT manipulation on nearly all internal video chips). In a nutshell, this explains why the Macintosh Linux port lags behind other Linux ports." msgstr "" #. Tag: para #: hardware.xml:2258 #, no-c-format -msgid "" -"Since we haven't been granted access to the documentation on these devices, " -"they simply won't work under Linux. You can help by asking the manufacturers " -"of such hardware to release the documentation. If enough people ask, they " -"will realize that the free software community is an important market." +msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under Linux. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market." msgstr "" #. Tag: title @@ -3804,50 +3135,19 @@ msgstr "" #. Tag: para #: hardware.xml:2271 #, no-c-format -msgid "" -"A disturbing trend is the proliferation of Windows-specific modems and " -"printers. In some cases these are specially designed to be operated by the " -"Microsoft Windows operating system and bear the legend <quote>WinModem</" -"quote> or <quote>Made especially for Windows-based computers</quote>. This " -"is generally done by removing the embedded processors of the hardware and " -"shifting the work they do over to a Windows driver that is run by your " -"computer's main CPU. This strategy makes the hardware less expensive, but " -"the savings are often <emphasis>not</emphasis> passed on to the user and " -"this hardware may even be more expensive than equivalent devices that retain " -"their embedded intelligence." +msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence." msgstr "" #. Tag: para #: hardware.xml:2284 #, no-c-format -msgid "" -"You should avoid Windows-specific hardware for two reasons. The first is " -"that the manufacturers do not generally make the resources available to " -"write a Linux driver. Generally, the hardware and software interface to the " -"device is proprietary, and documentation is not available without a non-" -"disclosure agreement, if it is available at all. This precludes its being " -"used for free software, since free software writers disclose the source code " -"of their programs. The second reason is that when devices like these have " -"had their embedded processors removed, the operating system must perform the " -"work of the embedded processors, often at <emphasis>real-time</emphasis> " -"priority, and thus the CPU is not available to run your programs while it is " -"driving these devices. Since the typical Windows user does not multi-process " -"as intensively as a Linux user, the manufacturers hope that the Windows user " -"simply won't notice the burden this hardware places on their CPU. However, " -"any multi-processing operating system, even Windows 2000 or XP, suffers from " -"degraded performance when peripheral manufacturers skimp on the embedded " -"processing power of their hardware." +msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes its being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" #. Tag: para #: hardware.xml:2305 #, no-c-format -msgid "" -"You can help improve this situation by encouraging these manufacturers to " -"release the documentation and other resources necessary for us to program " -"their hardware, but the best strategy is simply to avoid this sort of " -"hardware until it is listed as working in the <ulink url=\"&url-hardware-" -"howto;\">Linux Hardware Compatibility HOWTO</ulink>." +msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>." msgstr "" #. Tag: title @@ -3859,38 +3159,20 @@ msgstr "" #. Tag: para #: hardware.xml:2319 #, no-c-format -msgid "" -"If you ask for Parity RAM in a computer store, you'll probably get " -"<emphasis>virtual parity</emphasis> memory modules instead of <emphasis>true " -"parity</emphasis> ones. Virtual parity SIMMs can often (but not always) be " -"distinguished because they only have one more chip than an equivalent non-" -"parity SIMM, and that one extra chip is smaller than all the others. Virtual-" -"parity SIMMs work exactly like non-parity memory. They can't tell you when " -"you have a single-bit RAM error the way true-parity SIMMs do in a " -"motherboard that implements parity. Don't ever pay more for a virtual-parity " -"SIMM than a non-parity one. Do expect to pay a little more for true-parity " -"SIMMs, because you are actually buying one extra bit of memory for every 8 " -"bits." +msgid "If you ask for Parity RAM in a computer store, you'll probably get <emphasis>virtual parity</emphasis> memory modules instead of <emphasis>true parity</emphasis> ones. Virtual parity SIMMs can often (but not always) be distinguished because they only have one more chip than an equivalent non-parity SIMM, and that one extra chip is smaller than all the others. Virtual-parity SIMMs work exactly like non-parity memory. They can't tell you when you have a single-bit RAM error the way true-parity SIMMs do in a motherboard that implements parity. Don't ever pay more for a virtual-parity SIMM than a non-parity one. Do expect to pay a little more for true-parity SIMMs, because you are actually buying one extra bit of memory for every 8 bits." msgstr "" #. Tag: para #: hardware.xml:2334 #, no-c-format -msgid "" -"If you want complete information on &arch-title; RAM issues, and what is the " -"best RAM to buy, see the <ulink url=\"&url-pc-hw-faq;\">PC Hardware FAQ</" -"ulink>." -msgstr "" -"Ha teljes információt akarsz a RAM tudnivalókról &arch-title; architektúrán " -"és arról, hogy melyik a legjobb megvehető RAM, lásd a <ulink url=\"&url-pc-" -"hw-faq;\">PC Hardver GYIK</ulink> leírást." +msgid "If you want complete information on &arch-title; RAM issues, and what is the best RAM to buy, see the <ulink url=\"&url-pc-hw-faq;\">PC Hardware FAQ</ulink>." +msgstr "Ha teljes információt akarsz a RAM tudnivalókról &arch-title; architektúrán és arról, hogy melyik a legjobb megvehető RAM, lásd a <ulink url=\"&url-pc-hw-faq;\">PC Hardver GYIK</ulink> leírást." #. Tag: para #: hardware.xml:2340 #, no-c-format msgid "Most, if not all, Alpha systems require true-parity RAM." -msgstr "" -"Általában, ha nem mindig, az Alpha rendszerek valódi-paritásos RAM igényűek." +msgstr "Általában, ha nem mindig, az Alpha rendszerek valódi-paritásos RAM igényűek." #. Tag: title #: hardware.xml:2355 @@ -3901,63 +3183,26 @@ msgstr "Memória és lemezterület szükséglet" #. Tag: para #: hardware.xml:2357 #, no-c-format -msgid "" -"You must have at least &minimum-memory; of memory and &minimum-fs-size; of " -"hard disk space. For a minimal console-based system (all standard packages), " -"250MB is required. If you want to install a reasonable amount of software, " -"including the X Window System, and some development programs and libraries, " -"you'll need at least 400MB. For a more or less complete desktop system, " -"you'll need a few gigabytes." -msgstr "" -"Legalább &minimum-memory; memória és &minimum-fs-size; merevlemezhely " -"szükséges. Egy alap konzolos rendszerhez (minden szokásos csomaggal) 250 MB. " -"Ha egy kis, X ablakozó rendszert és pár fejlesztői programot és könyvtárat " -"is tartalmazó rendszert szeretnél telepíteni, legalább 400 MB kell. Egy " -"teljes asztali rendszerhez 2-3 GB." +msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. For a minimal console-based system (all standard packages), 250MB is required. If you want to install a reasonable amount of software, including the X Window System, and some development programs and libraries, you'll need at least 400MB. For a more or less complete desktop system, you'll need a few gigabytes." +msgstr "Legalább &minimum-memory; memória és &minimum-fs-size; merevlemezhely szükséges. Egy alap konzolos rendszerhez (minden szokásos csomaggal) 250 MB. Ha egy kis, X ablakozó rendszert és pár fejlesztői programot és könyvtárat is tartalmazó rendszert szeretnél telepíteni, legalább 400 MB kell. Egy teljes asztali rendszerhez 2-3 GB." #. Tag: para #: hardware.xml:2366 #, no-c-format -msgid "" -"On the Amiga the size of FastRAM is relevant towards the total memory " -"requirements. Also, using Zorro cards with 16-bit RAM is not supported; " -"you'll need 32-bit RAM. The <command>amiboot</command> program can be used " -"to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</" -"ulink>. Recent kernels should disable 16-bit RAM automatically." -msgstr "" -"Az Amiga gépeken a FastRAM a teljes memória-igény tekintetében a FastRAM " -"számít. A 16-bites RAM kiépítésű Zorro kártyák nem támogatottak; 32-bites " -"RAM kell. Az <command>amiboot</command> programmal kikapcsolható a 16-bites " -"RAM; lásd a <ulink url=\"&url-m68k-faq;\">Linux/m68k GYIK</ulink> leírást. A " -"jelenlegi kernelek automatikusan el tudják végezni ezt." +msgid "On the Amiga the size of FastRAM is relevant towards the total memory requirements. Also, using Zorro cards with 16-bit RAM is not supported; you'll need 32-bit RAM. The <command>amiboot</command> program can be used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically." +msgstr "Az Amiga gépeken a FastRAM a teljes memória-igény tekintetében a FastRAM számít. A 16-bites RAM kiépítésű Zorro kártyák nem támogatottak; 32-bites RAM kell. Az <command>amiboot</command> programmal kikapcsolható a 16-bites RAM; lásd a <ulink url=\"&url-m68k-faq;\">Linux/m68k GYIK</ulink> leírást. A jelenlegi kernelek automatikusan el tudják végezni ezt." #. Tag: para #: hardware.xml:2375 #, no-c-format -msgid "" -"On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many " -"users have reported problems running the kernel itself in Fast RAM, so the " -"Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for " -"ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM." -msgstr "" -"Az Atari gépeken ST és Fast RAM (TT) is kell. Több felhasználó gondokat " -"észlelt a kernel futtatásakor Fast RAM területen, ezért az Atari bootstrap a " -"kernelt az ST-RAM területre tölti. Legalább 2 MB ST-RAM és további 12 MB TT-" -"RAM szükséges." +msgid "On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many users have reported problems running the kernel itself in Fast RAM, so the Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM." +msgstr "Az Atari gépeken ST és Fast RAM (TT) is kell. Több felhasználó gondokat észlelt a kernel futtatásakor Fast RAM területen, ezért az Atari bootstrap a kernelt az ST-RAM területre tölti. Legalább 2 MB ST-RAM és további 12 MB TT-RAM szükséges." #. Tag: para #: hardware.xml:2383 #, no-c-format -msgid "" -"On the Macintosh, care should be taken on machines with RAM-based video " -"(RBV). The RAM segment at physical address 0 is used as screen memory, " -"making the default load position for the kernel unavailable. The alternate " -"RAM segment used for kernel and RAMdisk must be at least 4 MB." -msgstr "" -"A Macintoshon légy óvatos a RAM-alapú videóval (RBV). A 0 fizikai cím RAM " -"szegmense képernyő-memóriaként használt, így a kernel nem kerülhet az alap " -"betöltési helyére. A kernel és RAMdisk által használt RAM szegmens legalább " -"4 MB méretet igényel." +msgid "On the Macintosh, care should be taken on machines with RAM-based video (RBV). The RAM segment at physical address 0 is used as screen memory, making the default load position for the kernel unavailable. The alternate RAM segment used for kernel and RAMdisk must be at least 4 MB." +msgstr "A Macintoshon légy óvatos a RAM-alapú videóval (RBV). A 0 fizikai cím RAM szegmense képernyő-memóriaként használt, így a kernel nem kerülhet az alap betöltési helyére. A kernel és RAMdisk által használt RAM szegmens legalább 4 MB méretet igényel." #. Tag: emphasis #: hardware.xml:2393 @@ -3974,58 +3219,26 @@ msgstr "Hálózati csatoló hardverek" #. Tag: para #: hardware.xml:2406 #, no-c-format -msgid "" -"Most PCI and many older ISA network cards are supported. Some network " -"interface cards are not supported by most Debian installation disks, such as " -"AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider & Koch " -"G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) " -"network cards are not supported by the standard installation system, but see " -"<ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) " -"instructions. FDDI networks are also not supported by the installation " -"disks, both cards and protocols." -msgstr "" -"A legtöbb PCI és sok régi ISA hálózati kártya támogatott. Pár hálózati " -"csatoló kártyát a legtöbb Debian telepítő lemez nem támogat, például ezeket: " -"AX.25 kártyák és protokollok; NI16510 EtherBlaster kártyák; Schneider & " -"Koch G16 kártyák és Zenith Z-Note beépített hálózati kártya. A " -"mikrocsatornás (MCA) hálózati kártyákat nem támogatja az alap telepítő " -"rendszer, ám lásd a <ulink url=\"&url-linux-mca;\">Linux MCA-n</ulink> címen " -"található leírást pár (régi) javaslatért. A telepítő lemezek nem támogatják " -"az FDDI hálózatokat, a kártyákat és protokollokat sem." +msgid "Most PCI and many older ISA network cards are supported. Some network interface cards are not supported by most Debian installation disks, such as AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider & Koch G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) network cards are not supported by the standard installation system, but see <ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) instructions. FDDI networks are also not supported by the installation disks, both cards and protocols." +msgstr "A legtöbb PCI és sok régi ISA hálózati kártya támogatott. Pár hálózati csatoló kártyát a legtöbb Debian telepítő lemez nem támogat, például ezeket: AX.25 kártyák és protokollok; NI16510 EtherBlaster kártyák; Schneider & Koch G16 kártyák és Zenith Z-Note beépített hálózati kártya. A mikrocsatornás (MCA) hálózati kártyákat nem támogatja az alap telepítő rendszer, ám lásd a <ulink url=\"&url-linux-mca;\">Linux MCA-n</ulink> címen található leírást pár (régi) javaslatért. A telepítő lemezek nem támogatják az FDDI hálózatokat, a kártyákat és protokollokat sem." #. Tag: para #: hardware.xml:2425 #, no-c-format -msgid "" -"As for ISDN, the D-channel protocol for the (old) German 1TR6 is not " -"supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;." -msgstr "" -"ISDN esetén, a (régi) német 1TR6 D-csatorna protokoll nem támogatott; a &d-" -"i; a Spellcaster BRI ISDN eszközöket sem támogatja." +msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;." +msgstr "ISDN esetén, a (régi) német 1TR6 D-csatorna protokoll nem támogatott; a &d-i; a Spellcaster BRI ISDN eszközöket sem támogatja." #. Tag: para #: hardware.xml:2433 #, no-c-format -msgid "" -"Any network interface card (NIC) supported by the Linux kernel should also " -"be supported by the boot disks. You may need to load your network driver as " -"a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete " -"details." -msgstr "" -"Minden Linux kernel által támogatott hálózati csatolót az indító lemezek is " -"támogatnak. Néha előfordulhat, hogy egy bizonyos hálózati meghajtót kézzel " -"kell betölteni. Lásd a <ulink url=\"&url-m68k-faq;\"></ulink> leírást a " -"részletekért." +msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details." +msgstr "Minden Linux kernel által támogatott hálózati csatolót az indító lemezek is támogatnak. Néha előfordulhat, hogy egy bizonyos hálózati meghajtót kézzel kell betölteni. Lásd a <ulink url=\"&url-m68k-faq;\"></ulink> leírást a részletekért." #. Tag: para #: hardware.xml:2442 #, no-c-format -msgid "" -"The following network interface cards (NICs) are supported from the bootable " -"kernel directly:" -msgstr "" -"A betölthető kernel az alábbi hálózati csatoló kártyákat (NIC rövidítéssel " -"is ismertek) támogatja közvetlenül:" +msgid "The following network interface cards (NICs) are supported from the bootable kernel directly:" +msgstr "A betölthető kernel az alábbi hálózati csatoló kártyákat (NIC rövidítéssel is ismertek) támogatja közvetlenül:" #. Tag: para #: hardware.xml:2448 @@ -4042,14 +3255,8 @@ msgstr "Sun Happy Meal" #. Tag: para #: hardware.xml:2462 #, no-c-format -msgid "" -"The following network interface cards are supported as modules. They can be " -"enabled once the drivers are installed during the setup. However, due to the " -"magic of OpenPROM, you still should be able to boot from these devices:" -msgstr "" -"Az alábbi hálózati kártyák modulként támogatottak. Ezek alapértelmezetten a " -"meghajtók telepítése után kapcsolhatók be. Az OpenPROM varázsával a indítani " -"is lehet róluk." +msgid "The following network interface cards are supported as modules. They can be enabled once the drivers are installed during the setup. However, due to the magic of OpenPROM, you still should be able to boot from these devices:" +msgstr "Az alábbi hálózati kártyák modulként támogatottak. Ezek alapértelmezetten a meghajtók telepítése után kapcsolhatók be. Az OpenPROM varázsával a indítani is lehet róluk." #. Tag: para #: hardware.xml:2470 @@ -4070,40 +3277,26 @@ msgid "MyriCOM Gigabit Ethernet" msgstr "MyriCOM Gigabit Ethernet" #. Tag: para -#: hardware.xml:2488 hardware.xml:2494 hardware.xml:2500 hardware.xml:2506 +#: hardware.xml:2488 +#: hardware.xml:2494 +#: hardware.xml:2500 +#: hardware.xml:2506 #: hardware.xml:2512 #, no-c-format -msgid "" -"Any network interface card (NIC) supported by the Linux kernel should also " -"be supported by the boot disks. You may need to load your network driver as " -"a module." -msgstr "" -"Minden Linux kernel által támogatott hálózati csatolót az indító lemezek is " -"támogatnak. Néha előfordulhat, hogy egy bizonyos hálózati meghajtót kézzel " -"kell betölteni." +msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module." +msgstr "Minden Linux kernel által támogatott hálózati csatolót az indító lemezek is támogatnak. Néha előfordulhat, hogy egy bizonyos hálózati meghajtót kézzel kell betölteni." #. Tag: para #: hardware.xml:2518 #, no-c-format -msgid "" -"Due to kernel limitations only the onboard network interfaces on DECstations " -"are supported, TurboChannel option network cards currently do not work." -msgstr "" -"A kernel korlátai miatt DECstation gépeken csak az alaplapi hálózati " -"csatolók támogatottak, a TurboChannel hálózati kártyák jelenleg nem működnek." +msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work." +msgstr "A kernel korlátai miatt DECstation gépeken csak az alaplapi hálózati csatolók támogatottak, a TurboChannel hálózati kártyák jelenleg nem működnek." #. Tag: para #: hardware.xml:2524 #, no-c-format -msgid "" -"Any network interface card (NIC) supported by the Linux kernel is also be " -"supported by the boot disks. All network drivers are compiled as modules so " -"you need to load one first during the initial network setup. The list of " -"supported network devices is:" -msgstr "" -"Minden Linux kernel által támogatott hálózati csatolót az indító lemezek is " -"támogatnak. Minden hálózati meghajtó modulként fordított, tehát egyet be " -"kell tölteni a hálózat beállítása során. A támogatott hálózati eszközök:" +msgid "Any network interface card (NIC) supported by the Linux kernel is also be supported by the boot disks. All network drivers are compiled as modules so you need to load one first during the initial network setup. The list of supported network devices is:" +msgstr "Minden Linux kernel által támogatott hálózati csatolót az indító lemezek is támogatnak. Minden hálózati meghajtó modulként fordított, tehát egyet be kell tölteni a hálózat beállítása során. A támogatott hálózati eszközök:" #. Tag: para #: hardware.xml:2532 @@ -4120,11 +3313,8 @@ msgstr "OSA-2 Token Ring/Ethernet és OSA-Express Fast Ethernet (nem-QDIO)" #. Tag: para #: hardware.xml:2542 #, no-c-format -msgid "" -"Inter-User Communication Vehicle (IUCV) — available for VM guests only" -msgstr "" -"Inter-User Communication Vehicle (IUCV) — csak for VM vendégek számára " -"elérhető" +msgid "Inter-User Communication Vehicle (IUCV) — available for VM guests only" +msgstr "Inter-User Communication Vehicle (IUCV) — csak for VM vendégek számára elérhető" #. Tag: para #: hardware.xml:2547 @@ -4135,12 +3325,8 @@ msgstr "OSA-Express QDIO módban, HiperSockets és Guest-LANs" #. Tag: para #: hardware.xml:2556 #, no-c-format -msgid "" -"The following network interface cards are supported directly by the boot " -"disks on Netwinder and CATS machines:" -msgstr "" -"Az alábbi hálózati csatoló kártyákat az indító lemezek közvetlenül " -"támogatják Netwinder és CATS gépeken:" +msgid "The following network interface cards are supported directly by the boot disks on Netwinder and CATS machines:" +msgstr "Az alábbi hálózati csatoló kártyákat az indító lemezek közvetlenül támogatják Netwinder és CATS gépeken:" #. Tag: para #: hardware.xml:2562 @@ -4157,12 +3343,8 @@ msgstr "DECchip Tulip" #. Tag: para #: hardware.xml:2575 #, no-c-format -msgid "" -"The following network interface cards are supported directly by the boot " -"disks on RiscPCs:" -msgstr "" -"Az alábbi hálózati csatoló kártyákat az indító lemezek közvetlenül " -"támogatják RiscPC gépeken:" +msgid "The following network interface cards are supported directly by the boot disks on RiscPCs:" +msgstr "Az alábbi hálózati csatoló kártyákat az indító lemezek közvetlenül támogatják RiscPC gépeken:" #. Tag: para #: hardware.xml:2581 @@ -4185,19 +3367,12 @@ msgstr "EtherH" #. Tag: para #: hardware.xml:2598 #, no-c-format -msgid "" -"If your card is mentioned in the lists above, the complete installation can " -"be carried out from the network with no need for CD-ROMs or floppy disks." -msgstr "" -"Ha a kártya szerepel a listában, a teljes telepítés elvégezhető hálózatról " -"CD-ROM vagy flopi lemezek nélkül." +msgid "If your card is mentioned in the lists above, the complete installation can be carried out from the network with no need for CD-ROMs or floppy disks." +msgstr "Ha a kártya szerepel a listában, a teljes telepítés elvégezhető hálózatról CD-ROM vagy flopi lemezek nélkül." #. Tag: para #: hardware.xml:2604 #, no-c-format -msgid "" -"Any other network interface card (NIC) supported by the Linux kernel should " -"also be supported by the boot disks. You may need to load your network " -"driver as a module; this means that you will have to install the operating " -"system kernel and modules using some other media." +msgid "Any other network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module; this means that you will have to install the operating system kernel and modules using some other media." msgstr "" + diff --git a/po/hu/installation-howto.po b/po/hu/installation-howto.po index 1ac975d96..034d5dfc0 100644 --- a/po/hu/installation-howto.po +++ b/po/hu/installation-howto.po @@ -6,7 +6,7 @@ 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" -"PO-Revision-Date: 2006-10-12 20:30+0100\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" "MIME-Version: 1.0\n" @@ -25,20 +25,8 @@ 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 @@ -49,19 +37,8 @@ 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 @@ -72,42 +49,20 @@ 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 @@ -118,42 +73,14 @@ 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 @@ -163,71 +90,33 @@ msgstr "Floppi" #. Tag: para #: installation-howto.xml:94 -#, fuzzy, 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 a " -"<filename>floppy/root.img</filename> fájlra és vélhetően az eszköz-vezérlő " -"programokat tartalmazó lemezek egyikére. " +#, 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. " #. 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 -#, fuzzy, 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 majd a <filename>floppy/net-" -"drivers.img</filename> nevű floppira is szükséged lesz, mely hálózati " -"kártyák sokaságát és a PCMCIA eszközöket is támogatja." +#, 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>." #. 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 @@ -238,71 +127,32 @@ 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 @@ -313,33 +163,14 @@ 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 @@ -350,21 +181,8 @@ 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 @@ -374,177 +192,75 @@ msgstr "Telepítés" #. Tag: para #: installation-howto.xml:212 -#, 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\"/>). <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. <footnote><para> A 2.6 " -"verziójú Linux az alapértelmezett e legtöbb indítási módnál, de floppinál " -"nem elérhető. </para></footnote> </phrase>" +#, 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>" #. Tag: para #: installation-howto.xml:222 #, 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 #, 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 #, 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 #, 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 #, 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 #, 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 #, 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 #, 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 #, 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 #, 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 #, 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 @@ -555,34 +271,14 @@ msgstr "Küldj nekünk telepítési beszámolót" #. Tag: para #: installation-howto.xml:303 #, 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 #, 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 @@ -593,10 +289,6 @@ msgstr "Végül..." #. Tag: para #: installation-howto.xml:324 #, 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." + |