# Hungarian translation of Debian Installation Guide boot-installer
# SZERVÁC Attila <sas@321.hu>, 2006.
#
msgid ""
msgstr ""
"Project-Id-Version: \n"
"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
"POT-Creation-Date: 2007-02-27 20:31+0000\n"
"PO-Revision-Date: 2007-02-22 21:03+0100\n"
"Last-Translator: SZERVÁC Attila <sas@321.hu>\n"
"Language-Team: Hungarian <debian-l10n-hungarian@lists.debian>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Poedit-Country: HUNGARY\n"
"X-Poedit-Language: Hungarian\n"

#. Tag: title
#: boot-installer.xml:4
#, no-c-format
msgid "Booting the Installation System"
msgstr "A telepítő rendszer indítása"

#. Tag: title
#: boot-installer.xml:9
#, no-c-format
msgid "Booting the Installer on &arch-title;"
msgstr "A telepítő indítása &arch-title; architektúrán"

#. Tag: para
#: boot-installer.xml:15
#, no-c-format
msgid ""
"For information on how to boot the graphical installer, see <xref linkend="
"\"graphical\"/>."
msgstr ""
"A grafikus telepítő indításáról lásd az alábbit: <xref linkend=\"graphical\"/"
">."

#. Tag: title
#: boot-installer.xml:27
#, no-c-format
msgid "Alpha Console Firmware"
msgstr ""

#. Tag: para
#: boot-installer.xml:28
#, 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:"
msgstr ""

#. Tag: para
#: boot-installer.xml:38
#, 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."

#. Tag: para
#: boot-installer.xml:45
#, 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 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:54
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:61
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:70
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:83
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:94
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:102
#, 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."

#. Tag: entry
#: boot-installer.xml:114
#, no-c-format
msgid "System Type"
msgstr "Rendszer típus"

#. Tag: entry
#: boot-installer.xml:115
#, no-c-format
msgid "Console Type Supported"
msgstr "Támogatott konzol típus"

#. Tag: entry
#: boot-installer.xml:121
#, no-c-format
msgid "alcor"
msgstr "alcor"

#. Tag: entry
#: boot-installer.xml:122 boot-installer.xml:125 boot-installer.xml:131
#: boot-installer.xml:137 boot-installer.xml:140 boot-installer.xml:143
#: boot-installer.xml:146 boot-installer.xml:152 boot-installer.xml:155
#: boot-installer.xml:158 boot-installer.xml:167 boot-installer.xml:176
#: boot-installer.xml:191 boot-installer.xml:194
#, no-c-format
msgid "ARC or SRM"
msgstr "ARC vagy SRM"

#. Tag: entry
#: boot-installer.xml:124
#, no-c-format
msgid "avanti"
msgstr "avanti"

#. Tag: entry
#: boot-installer.xml:127
#, no-c-format
msgid "book1"
msgstr "book1"

#. Tag: entry
#: boot-installer.xml:128 boot-installer.xml:134 boot-installer.xml:149
#: boot-installer.xml:161 boot-installer.xml:170 boot-installer.xml:173
#: boot-installer.xml:179 boot-installer.xml:185 boot-installer.xml:188
#, no-c-format
msgid "SRM only"
msgstr "csak SRM"

#. Tag: entry
#: boot-installer.xml:130
#, no-c-format
msgid "cabriolet"
msgstr "cabriolet"

#. Tag: entry
#: boot-installer.xml:133
#, no-c-format
msgid "dp264"
msgstr "dp264"

#. Tag: entry
#: boot-installer.xml:136
#, no-c-format
msgid "eb164"
msgstr "eb164"

#. Tag: entry
#: boot-installer.xml:139
#, no-c-format
msgid "eb64p"
msgstr "eb64p"

#. Tag: entry
#: boot-installer.xml:142
#, no-c-format
msgid "eb66"
msgstr "eb66"

#. Tag: entry
#: boot-installer.xml:145
#, no-c-format
msgid "eb66p"
msgstr "eb66p"

#. Tag: entry
#: boot-installer.xml:148
#, no-c-format
msgid "jensen"
msgstr "jensen"

#. Tag: entry
#: boot-installer.xml:151
#, no-c-format
msgid "lx164"
msgstr "lx164"

#. Tag: entry
#: boot-installer.xml:154
#, no-c-format
msgid "miata"
msgstr "miata"

#. Tag: entry
#: boot-installer.xml:157
#, no-c-format
msgid "mikasa"
msgstr "mikasa"

#. Tag: entry
#: boot-installer.xml:160
#, no-c-format
msgid "mikasa-p"
msgstr "mikasa-p"

#. Tag: entry
#: boot-installer.xml:163
#, no-c-format
msgid "nautilus"
msgstr "nautilus"

#. Tag: entry
#: boot-installer.xml:164
#, no-c-format
msgid "ARC (see motherboard manual) or SRM"
msgstr "ARC (lásd az alaplap kézikönyvet) vagy SRM"

#. Tag: entry
#: boot-installer.xml:166
#, no-c-format
msgid "noname"
msgstr "névtelen"

#. Tag: entry
#: boot-installer.xml:169
#, no-c-format
msgid "noritake"
msgstr "noritake"

#. Tag: entry
#: boot-installer.xml:172
#, no-c-format
msgid "noritake-p"
msgstr "noritake-p"

#. Tag: entry
#: boot-installer.xml:175
#, no-c-format
msgid "pc164"
msgstr "pc164"

#. Tag: entry
#: boot-installer.xml:178
#, no-c-format
msgid "rawhide"
msgstr "rawhide"

#. Tag: entry
#: boot-installer.xml:181
#, no-c-format
msgid "ruffian"
msgstr "ruffian"

#. Tag: entry
#: boot-installer.xml:182 boot-installer.xml:197 boot-installer.xml:200
#, no-c-format
msgid "ARC only"
msgstr "csak ARC"

#. Tag: entry
#: boot-installer.xml:184
#, no-c-format
msgid "sable"
msgstr "sable"

#. Tag: entry
#: boot-installer.xml:187
#, no-c-format
msgid "sable-g"
msgstr "sable-g"

#. Tag: entry
#: boot-installer.xml:190
#, no-c-format
msgid "sx164"
msgstr "sx164"

#. Tag: entry
#: boot-installer.xml:193
#, no-c-format
msgid "takara"
msgstr "takara"

#. Tag: entry
#: boot-installer.xml:196
#, no-c-format
msgid "<entry>xl</entry>"
msgstr "<entry>xl</entry>"

#. Tag: entry
#: boot-installer.xml:199
#, no-c-format
msgid "<entry>xlt</entry>"
msgstr "<entry>xlt</entry>"

#. Tag: para
#: boot-installer.xml:207
#, 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."

#. Tag: para
#: boot-installer.xml:216
#, 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."

#. Tag: para
#: boot-installer.xml:222
#, 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>."

#. Tag: para
#: boot-installer.xml:228
#, 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."

#. Tag: para
#: boot-installer.xml:238
#, 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."

#. Tag: para
#: boot-installer.xml:245
#, no-c-format
msgid ""
"Thus, three scenarios are generally possible, depending on the system's "
"console firmware and whether or not <command>MILO</command> is available: "
"<informalexample><screen>\n"
"SRM -&gt; aboot\n"
"SRM -&gt; MILO\n"
"ARC -&gt; MILO\n"
"</screen></informalexample> Because <command>MILO</command> is not available "
"for any of the Alpha systems currently in production (as of February 2000), "
"and because it is no longer necessary to buy an OpenVMS or Tru64 Unix "
"license to have SRM firmware on your older Alpha, it is recommended that you "
"use SRM and <command>aboot</command> on new installations of GNU/Linux, "
"unless you wish to dual-boot with Windows NT."
msgstr ""

#. Tag: para
#: boot-installer.xml:260
#, 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;."
msgstr ""

#. Tag: para
#: boot-installer.xml:271
#, 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 &mdash; 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:290 boot-installer.xml:1015 boot-installer.xml:1506
#: boot-installer.xml:2003 boot-installer.xml:2085 boot-installer.xml:2174
#: boot-installer.xml:2524 boot-installer.xml:2623
#, no-c-format
msgid "Booting with TFTP"
msgstr "Indítás TFTP segítségével"

#. Tag: para
#: boot-installer.xml:291
#, 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"
"&gt;&gt;&gt; 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"
"&gt;&gt;&gt; set ewa0_protocols bootp\n"
"</screen></informalexample> Then check the medium type is correct: "
"<informalexample><screen>\n"
"&gt;&gt;&gt; set ewa0_mode <replaceable>mode</replaceable>\n"
"</screen></informalexample> You can get a listing of valid modes with "
"<userinput>&gt;&gt;&gt;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"
"&gt;&gt;&gt; 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"
"&gt;&gt;&gt; set ewa0_protocols bootp\n"
"</screen></informalexample> Majd ellenőrizni a médium típust:"
"<informalexample><screen>\n"
"&gt;&gt;&gt; set ewa0_mode <replaceable>mód</replaceable>\n"
"</screen></informalexample> Az érvényes módok így írhatók ki: <userinput>&gt;"
"&gt;&gt;set ewa0_mode</userinput>."

#. Tag: para
#: boot-installer.xml:309
#, no-c-format
msgid ""
"Then, to boot from the first Ethernet interface, you would type: "
"<informalexample><screen>\n"
"&gt;&gt;&gt; boot ewa0 -flags \"\"\n"
"</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"
"&gt;&gt;&gt; boot ewa0 -flags \"\"\n"
"</screen></informalexample> Ez netboot képben lévő alap kernel "
"paraméterekkel indít."

#. Tag: para
#: boot-installer.xml:318
#, 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:"

#. Tag: screen
#: boot-installer.xml:330
#, no-c-format
msgid ""
"&gt;&gt;&gt; boot ewa0 -flags &quot;root=/dev/ram ramdisk_size=16384 "
"console=ttyS0&quot;"
msgstr ""
"&gt;&gt;&gt; boot ewa0 -flags &quot;root=/dev/ram ramdisk_size=16384 "
"console=ttyS0&quot;"

#. Tag: title
#: boot-installer.xml:335
#, no-c-format
msgid "Booting from CD-ROM with the SRM Console"
msgstr "Indítás CD-ROM lemezről az SRM konzollal"

#. Tag: para
#: boot-installer.xml:336
#, no-c-format
msgid ""
"The &debian; install CDs include several preconfigured boot options for VGA "
"and serial consoles. Type <informalexample><screen>\n"
"&gt;&gt;&gt; boot xxxx -flags 0\n"
"</screen></informalexample> to boot using VGA console, where "
"<replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation. To use "
"serial console on the first serial device, type <informalexample><screen>\n"
"&gt;&gt;&gt; boot xxxx -flags 1\n"
"</screen></informalexample> and for console on the second serial port, type"
msgstr ""

#. Tag: screen
#: boot-installer.xml:351
#, no-c-format
msgid "&gt;&gt;&gt; boot xxxx -flags 2"
msgstr ""

#. Tag: title
#: boot-installer.xml:357
#, no-c-format
msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console"
msgstr "Indítás CD-ROM lemezről az ARC vagy AlphaBIOS konzollal"

#. Tag: para
#: boot-installer.xml:358
#, 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ő."

#. Tag: title
#: boot-installer.xml:374
#, no-c-format
msgid "Booting from Floppies with the SRM Console"
msgstr "Indítás flopiról az SRM konzollal"

#. Tag: para
#: boot-installer.xml:375
#, no-c-format
msgid ""
"At the SRM prompt (<prompt>&gt;&gt;&gt;</prompt>), issue the following "
"command: <informalexample><screen>\n"
"&gt;&gt;&gt; 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"
"&gt;&gt;&gt; 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>&gt;&gt;&gt;</prompt>) add ki az alábbi parancsot: "
"<informalexample><screen>\n"
"&gt;&gt;&gt; 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"
"&gt;&gt;&gt; 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."

#. Tag: para
#: boot-installer.xml:392
#, no-c-format
msgid ""
"If you want to specify kernel parameters when booting via <command>aboot</"
"command>, use the following command: <informalexample><screen>\n"
"&gt;&gt;&gt; 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"
"&gt;&gt;&gt; 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:404
#, 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."

#. Tag: title
#: boot-installer.xml:414
#, no-c-format
msgid "Booting from Floppies with the ARC or AlphaBIOS Console"
msgstr "Indítás flopiról az ARC vagy AlphaBIOS konzollal"

#. Tag: para
#: boot-installer.xml:416
#, 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."

#. Tag: title
#: boot-installer.xml:425
#, no-c-format
msgid "Booting with MILO"
msgstr "Indítás MILO segítségével"

#. Tag: para
#: boot-installer.xml:426
#, 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."

#. Tag: para
#: boot-installer.xml:432
#, no-c-format
msgid ""
"If you want to specify all the bits explicitly (for example, to supply "
"additional parameters), you can use a command like this: "
"<informalexample><screen>\n"
"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->\n"
"</screen></informalexample> If you are booting from something other than a "
"floppy, substitute <filename>fd0</filename> in the above example with the "
"appropriate device name in Linux notation. The <command>help</command> "
"command would give you a brief MILO command reference."
msgstr ""
"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."

#. Tag: title
#: boot-installer.xml:451
#, no-c-format
msgid "Booting from TFTP"
msgstr "Indítás TFTP segítségével"

#. Tag: para
#: boot-installer.xml:457 boot-installer.xml:1021 boot-installer.xml:1524
#: boot-installer.xml:2009 boot-installer.xml:2530 boot-installer.xml:2629
#, 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)."

#. Tag: para
#: boot-installer.xml:462 boot-installer.xml:1026 boot-installer.xml:1529
#: boot-installer.xml:2014 boot-installer.xml:2535 boot-installer.xml:2634
#, 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."

#. Tag: para
#: boot-installer.xml:467 boot-installer.xml:1031 boot-installer.xml:1534
#: boot-installer.xml:2019 boot-installer.xml:2540 boot-installer.xml:2639
#, 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\"/>."

#. Tag: title
#: boot-installer.xml:475
#, no-c-format
msgid "Booting from TFTP on Netwinder"
msgstr "TFTP indítás Netwinder gépen"

#. Tag: para
#: boot-installer.xml:476
#, 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ű)."

#. Tag: para
#: boot-installer.xml:485
#, 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>."
msgstr ""

#. Tag: para
#: boot-installer.xml:493
#, no-c-format
msgid ""
"When you boot your Netwinder you have to interrupt the boot process during "
"the countdown. This allows you to set a number of firmware settings needed "
"in order to boot the installer. First of all, start by loading the default "
"settings: <informalexample><screen>\n"
"    NeTTrom command-&gt; load-defaults\n"
"</screen></informalexample> Furthermore, you must configure the network, "
"either with a static address: <informalexample><screen>\n"
"    NeTTrom command-&gt; setenv netconfig_eth0 flash\n"
"    NeTTrom command-&gt; setenv eth0_ip 192.168.0.10/24\n"
"</screen></informalexample> where 24 is the number of set bits in the "
"netmask, or a dynamic address: <informalexample><screen>\n"
"    NeTTrom command-&gt; setenv netconfig_eth0 dhcp\n"
"</screen></informalexample> You may also need to configure the "
"<userinput>route1</userinput> settings if the TFTP server is not on the "
"local subnet. Following these settings, you have to specify the TFTP server "
"and the location of the image. You can then store your settings to flash. "
"<informalexample><screen>\n"
"    NeTTrom command-&gt; setenv kerntftpserver 192.168.0.1\n"
"    NeTTrom command-&gt; setenv kerntftpfile boot.img\n"
"    NeTTrom command-&gt; save-all\n"
"</screen></informalexample> Now you have to tell the firmware that the TFTP "
"image should be booted: <informalexample><screen>\n"
"    NeTTrom command-&gt; setenv kernconfig tftp\n"
"    NeTTrom command-&gt; 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-&gt; 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-&gt; setenv cmdappend root=/dev/ram\n"
"</screen></informalexample> You can use the <command>printenv</command> "
"command to review your environment settings. After you have verified that "
"the settings are correct, you can load the image: <informalexample><screen>\n"
"    NeTTrom command-&gt; boot\n"
"</screen></informalexample> In case you run into any problems, a <ulink url="
"\"http://www.netwinder.org/howto/Firmware-HOWTO.html\">detailed HOWTO</"
"ulink> is available."
msgstr ""

#. Tag: title
#: boot-installer.xml:545
#, no-c-format
msgid "Booting from TFTP on CATS"
msgstr "Indítás TFTP segítségével CATS rendszeren"

#. Tag: para
#: boot-installer.xml:546
#, no-c-format
msgid ""
"On CATS machines, use <command>boot de0:</command> or similar at the Cyclone "
"prompt."
msgstr ""

#. Tag: title
#: boot-installer.xml:556
#, no-c-format
msgid "Booting from CD-ROM"
msgstr "Indítás CD-ROM lemezről"

#. Tag: para
#: boot-installer.xml:562 boot-installer.xml:732 boot-installer.xml:1143
#: boot-installer.xml:1966 boot-installer.xml:2312 boot-installer.xml:2667
#, 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."

#. Tag: para
#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1154
#: boot-installer.xml:1977 boot-installer.xml:2323 boot-installer.xml:2678
#, 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."

#. Tag: para
#: boot-installer.xml:581 boot-installer.xml:751 boot-installer.xml:1162
#: boot-installer.xml:1985 boot-installer.xml:2331 boot-installer.xml:2686
#, 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."

#. Tag: para
#: boot-installer.xml:589 boot-installer.xml:759 boot-installer.xml:1170
#: boot-installer.xml:1993 boot-installer.xml:2339 boot-installer.xml:2694
#, 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."

#. Tag: para
#: boot-installer.xml:596
#, 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"

#. Tag: title
#: boot-installer.xml:605
#, no-c-format
msgid "Booting from Firmware"
msgstr "Indítás firmware-ből"

#. Tag: para
#: boot-installer.xml:611
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:617
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:628
#, no-c-format
msgid "Booting the NSLU2"
msgstr "Az NLSU2 indítása"

#. Tag: para
#: boot-installer.xml:629
#, no-c-format
msgid "There are three ways how to put the installer firmware into flash:"
msgstr ""

#. Tag: title
#: boot-installer.xml:635
#, no-c-format
msgid "Using the NSLU2 web interface"
msgstr ""

#. Tag: para
#: boot-installer.xml:636
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:647
#, no-c-format
msgid "Via the network using Linux/Unix"
msgstr ""

#. Tag: para
#: boot-installer.xml:648
#, no-c-format
msgid ""
"You can use <command>upslug2</command> from any Linux or Unix machine to "
"upgrade the machine via the network. This software is packaged for Debian. "
"First, you have to put your NSLU2 in upgrade mode: <orderedlist> "
"<listitem><para> Disconnect any disks and/or devices from the USB ports. </"
"para></listitem> <listitem><para> Power off the NSLU2 </para></listitem> "
"<listitem><para> Press and hold the reset button (accessible through the "
"small hole on the back just above the power input). </para></listitem> "
"<listitem><para> Press and release the power button to power on the NSLU2. </"
"para></listitem> <listitem><para> Wait for 10 seconds watching the ready/"
"status LED. After 10 seconds it will change from amber to red. Immediately "
"release the reset button. </para></listitem> <listitem><para> The NSLU2 "
"ready/status LED will flash alternately red/green (there is a 1 second delay "
"before the first green). The NSLU2 is now in upgrade mode. </para></"
"listitem> </orderedlist> See the <ulink url=\"http://www.nslu2-linux.org/"
"wiki/OpenSlug/UsingTheBinary\">NSLU2-Linux pages</ulink> if you have "
"problems with this. Once your NSLU2 is in upgrade mode, you can flash the "
"new image: <informalexample><screen>\n"
"sudo upslug2 -i di-nslu2.bin\n"
"</screen></informalexample> Note that the tool also shows the MAC address of "
"your NSLU2, which may come in handy to configure your DHCP server. After the "
"whole image has been written and verified, the system will automatically "
"reboot. Make sure you connect your USB disk again now, otherwise the "
"installer won't be able to find it."
msgstr ""

#. Tag: title
#: boot-installer.xml:709
#, no-c-format
msgid "Via the network using Windows"
msgstr ""

#. Tag: para
#: boot-installer.xml:710
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:726 boot-installer.xml:1137 boot-installer.xml:1954
#: boot-installer.xml:2306 boot-installer.xml:2661
#, no-c-format
msgid "Booting from a CD-ROM"
msgstr "Indítás egy CD-ROM lemezről"

#. Tag: title
#: boot-installer.xml:864
#, 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"

#. Tag: para
#: boot-installer.xml:867
#, 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."

#. Tag: para
#: boot-installer.xml:872
#, no-c-format
msgid ""
"If you intend to use the hard drive only for booting and then download "
"everything over the network, you should download the <filename>netboot/"
"debian-installer/&architecture;/initrd.gz</filename> file and its "
"corresponding kernel <filename>netboot/debian-installer/&architecture;/"
"linux</filename>. This will allow you to repartition the hard disk from "
"which you boot the installer, although you should do so with care."
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/&architecture;/initrd.gz</filename> fájl "
"és a megfelelő <filename>netboot/debian-installer/&architecture;/linux</"
"filename> 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:882
#, 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."

#. Tag: para
#: boot-installer.xml:891
#, 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>:"

#. Tag: screen
#: boot-installer.xml:912
#, no-c-format
msgid ""
"image=/boot/newinstall/vmlinuz\n"
"       label=newinstall\n"
"       initrd=/boot/newinstall/initrd.gz"
msgstr ""
"image=/boot/newinstall/vmlinuz\n"
"       label=newinstall\n"
"       initrd=/boot/newinstall/initrd.gz"

#. Tag: para
#: boot-installer.xml:912
#, 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."

#. Tag: para
#: boot-installer.xml:921
#, no-c-format
msgid ""
"The procedure for <command>GRUB</command> is quite similar. Locate your "
"<filename>menu.lst</filename> in the <filename>/boot/grub/</filename> "
"directory (sometimes in the <filename>/boot/boot/grub/</filename>), add the "
"following lines: <informalexample><screen>\n"
"title  New Install\n"
"kernel (hd0,0)/boot/newinstall/vmlinuz\n"
"initrd (hd0,0)/boot/newinstall/initrd.gz\n"
"</screen></informalexample> and reboot."
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, add hozzá a következő sorokat: "
"<informalexample><screen>\n"
"title  New Install\n"
"kernel (hd0,0)/boot/newinstall/vmlinuz\n"
"initrd (hd0,0)/boot/newinstall/initrd.gz\n"
"</screen></informalexample> és indíts újra."

#. Tag: para
#: boot-installer.xml:932
#, 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."

#. Tag: title
#: boot-installer.xml:943
#, no-c-format
msgid "Booting from USB Memory Stick"
msgstr "Indítás USB tárról"

#. Tag: para
#: boot-installer.xml:944
#, 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."

#. Tag: title
#: boot-installer.xml:957 boot-installer.xml:2066 boot-installer.xml:2569
#: boot-installer.xml:2712
#, no-c-format
msgid "Booting from Floppies"
msgstr "Indítás flopikról"

#. Tag: para
#: boot-installer.xml:958 boot-installer.xml:2577
#, 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."

#. Tag: para
#: boot-installer.xml:965
#, 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."

#. Tag: para
#: boot-installer.xml:971
#, no-c-format
msgid ""
"For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
"you need to specify the virtual location for the floppy device. This is done "
"with the <emphasis>root=</emphasis> boot argument, giving the device that "
"the ide-floppy driver maps the device to. For example, if your LS-120 drive "
"is connected as the first IDE device (master) on the second cable, you enter "
"<userinput>install root=/dev/hdc</userinput> at the boot prompt."
msgstr ""
"Egy LS-120 meghajtóról (ATAPI változat) telepítéshez 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>install root=/dev/hdc</"
"userinput> az indító jelnél."

#. Tag: para
#: boot-installer.xml:981
#, 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."

#. Tag: para
#: boot-installer.xml:990
#, 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."

#. Tag: para
#: boot-installer.xml:996
#, 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ó."

#. Tag: para
#: boot-installer.xml:1005
#, 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."

#. Tag: para
#: boot-installer.xml:1039
#, no-c-format
msgid "There are various ways to do a TFTP boot on i386."
msgstr "i386 gépen több mód van a TFTP indításra."

#. Tag: title
#: boot-installer.xml:1045
#, no-c-format
msgid "NIC or Motherboard that support PXE"
msgstr "PXE-támogató hálózati kártya vagy alaplap"

#. Tag: para
#: boot-installer.xml:1046
#, 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."

#. Tag: title
#: boot-installer.xml:1057
#, no-c-format
msgid "NIC with Network BootROM"
msgstr "NIC hálózati indító ROM-mal"

#. Tag: para
#: boot-installer.xml:1058
#, no-c-format
msgid ""
"It could be that your Network Interface Card provides TFTP boot "
"functionality."
msgstr "Lehet, hogy hálózati csatoló kártyád TFTP indítást kínál."

#. Tag: para
#: boot-installer.xml:1063
#, no-c-format
msgid ""
"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
"Please refer to this document."
msgstr ""
"Tudasd velünk (<email>&email-debian-boot-list;</email>) hogyan kezelted. "
"Hivatkozz e dokumentumra."

#. Tag: title
#: boot-installer.xml:1071
#, no-c-format
msgid "Etherboot"
msgstr "Etherboot"

#. Tag: para
#: boot-installer.xml:1072
#, no-c-format
msgid ""
"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
"provides bootdiskettes and even bootroms that do a TFTPboot."
msgstr ""
"Az <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> TFTP "
"indítást adó indító lemezeket és indító romokat ad."

#. Tag: title
#: boot-installer.xml:1081
#, no-c-format
msgid "The Boot Prompt"
msgstr "Az indító jel"

#. Tag: para
#: boot-installer.xml:1082
#, no-c-format
msgid ""
"When the installer boots, you should be presented with a friendly graphical "
"screen showing the Debian logo and the boot prompt: "
"<informalexample><screen>\n"
"Press F1 for help, or ENTER to boot:\n"
"</screen></informalexample> At the boot prompt you can either just press "
"&enterkey; to boot the installer with default options or enter a specific "
"boot method and, optionally, boot parameters."
msgstr ""
"A telepítő indulásakor egy barátságos grafikus képernyőt látsz a Debian "
"logóval és az indító jellel: <informalexample><screen>\n"
"Press F1 for help, or ENTER to boot:\n"
"</screen></informalexample> Az indító jelnél leütheted az &enterkey; "
"billentyűt a telepítő alap lehetőségeivel indításhoz vagy beírhatsz egy "
"adott indító módot és, tetszőlegesen, indító paramétereket."

#. Tag: para
#: boot-installer.xml:1094
#, no-c-format
msgid ""
"Information on available boot methods and on boot parameters which might be "
"useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</"
"keycap>. If you add any parameters to the boot command line, be sure to type "
"the boot method (the default is <userinput>install</userinput>) and a space "
"before the first parameter (e.g., <userinput>install fb=false</userinput>)."
msgstr ""
"Az elérhető indító módok és paraméterek, melyek hasznosak lehetnek az "
"<keycap>F2</keycap> és <keycap>F8</keycap> közti billentyűk leütésével "
"érhetők el. Ha paramétert adsz az indító parancs sorhoz, írd be az indító "
"módot (az alap az <userinput>install</userinput>) és egy szóközt az 1. "
"paraméter előtt (például <userinput>install fb=false</userinput>)."

#. Tag: para
#: boot-installer.xml:1103
#, 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>,&nbsp;<keycap>1</"
"keycap>. </para> </footnote> to bypass this screen and view the help text. "
"Once you are past the splash screen and at the help text your keystrokes "
"will be echoed at the prompt as expected. To prevent the installer from "
"using the framebuffer for the rest of the installation, you will also want "
"to add <userinput>fb=false</userinput> to the boot prompt, as described in "
"the help text."
msgstr ""
"Ha a rendszert távoli kezelő eszközön át telepíted, mely szöveges felületet "
"ad a VGA konzolhoz, talán nem látod a kezdő grafikus üdvözlő képernyőt a "
"telepítő indításakor és az indító jelet. Ezek között van a Compaq "
"<quote>integrated Lights Out</quote> (iLO) és HP <quote>Integrated Remote "
"Assistant</quote> (IRA). Vakon nyomd meg az F1 billentyűt <footnote> <para> "
"Néha ehhez különleges escape sor kell, például IRA esetén <keycombo> "
"<keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>,&nbsp;<keycap>1</"
"keycap>. </para> </footnote> a képernyő átugrásával a súgóra lépéshez. "
"Ezután a leütött billentyűk már a várakozásnak megfelelően megjelennek a "
"beviteli jelnél. A framebuffer tiltásához a telepítéskor az "
"<userinput>fb=false</userinput> hozzáadása kell az indító jelnél, ahogy azt "
"a súgó is írja."

#. Tag: title
#: boot-installer.xml:1178
#, no-c-format
msgid "CD Contents"
msgstr ""

#. Tag: para
#: boot-installer.xml:1180
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1196
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1212
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1221
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1233
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1252
#, no-c-format
msgid "IMPORTANT"
msgstr ""

#. Tag: para
#: boot-installer.xml:1253
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1265
#, no-c-format
msgid "Option 1: Booting from the Boot Option Maintenance Menu"
msgstr ""

#. Tag: para
#: boot-installer.xml:1272
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1278
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1284
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1295
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1306
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1318
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1328
#, no-c-format
msgid "Option 2: Booting from the EFI Shell"
msgstr ""

#. Tag: para
#: boot-installer.xml:1329
#, 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:"
msgstr ""

#. Tag: para
#: boot-installer.xml:1340
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1346
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1360
#, 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>."
msgstr ""

#. Tag: para
#: boot-installer.xml:1367
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1374
#, no-c-format
msgid ""
"Enter <command>elilo</command> and press <command>ENTER</command>. This will "
"start the boot load sequence."
msgstr ""

#. Tag: para
#: boot-installer.xml:1381
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1395
#, no-c-format
msgid "Installing using a Serial Console"
msgstr ""

#. Tag: para
#: boot-installer.xml:1397
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1408
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1415
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1426
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1435
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1444
#, no-c-format
msgid "Selecting the Boot Kernel and Options"
msgstr ""

#. Tag: para
#: boot-installer.xml:1446
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1458
#, 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:"
msgstr ""

#. Tag: para
#: boot-installer.xml:1476
#, no-c-format
msgid ""
"Select the kernel version and installation mode most appropriate to your "
"needs with the arrow keys."
msgstr ""

#. Tag: para
#: boot-installer.xml:1481
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1488
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1497 boot-installer.xml:1633
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1508
#, no-c-format
msgid ""
"Booting an IA-64 system from the network is similar to a CD boot. The only "
"difference is how the installation kernel is loaded. The EFI Boot Manager "
"can load and start programs from a server on the network. Once the "
"installation kernel is loaded and starts, the system install will proceed "
"through the same steps as the CD install with the exception that the "
"packages of the base install will be loaded from the network rather than the "
"CD drive."
msgstr ""

#. Tag: para
#: boot-installer.xml:1542
#, no-c-format
msgid ""
"Network booting an IA-64 system requires two architecture-specific actions. "
"On the boot server, DHCP and TFTP must be configured to deliver "
"<command>elilo</command>. On the client a new boot option must be defined in "
"the EFI boot manager to enable loading over a network."
msgstr ""

#. Tag: title
#: boot-installer.xml:1553
#, no-c-format
msgid "Configuring the Server"
msgstr ""

#. Tag: para
#: boot-installer.xml:1554
#, no-c-format
msgid ""
"A suitable TFTP entry for network booting an IA-64 system looks something "
"like this: <informalexample><screen>\n"
"host mcmuffin {\n"
"        hardware ethernet 00:30:6e:1e:0e:83;\n"
"        fixed-address 10.0.0.21;\n"
"        filename \"debian-installer/ia64/elilo.efi\";\n"
"}\n"
"</screen></informalexample> Note that the goal is to get <command>elilo.efi</"
"command> running on the client."
msgstr ""

#. Tag: para
#: boot-installer.xml:1564
#, 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."
msgstr ""

#. Tag: screen
#: boot-installer.xml:1574
#, no-c-format
msgid ""
"# cd /var/lib/tftp\n"
"# tar xvfz /home/user/netboot.tar.gz\n"
"./\n"
"./debian-installer/\n"
"./debian-installer/ia64/\n"
"[...]"
msgstr ""

#. Tag: para
#: boot-installer.xml:1574
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1591
#, no-c-format
msgid "Configuring the Client"
msgstr ""

#. Tag: para
#: boot-installer.xml:1592
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1624
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1646
#, no-c-format
msgid "Choosing an Installation Method"
msgstr "Telepítő mód választás"

#. Tag: para
#: boot-installer.xml:1648
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1656
#, no-c-format
msgid ""
"If you are using a 2.2.x linux kernel, then you need to use the "
"&ramdisksize; kernel parameter."
msgstr "2.2.x linux kernel esetén a &ramdisksize; beállítandó."

#. Tag: para
#: boot-installer.xml:1661
#, no-c-format
msgid ""
"Make sure <userinput>root=/dev/ram</userinput> is one of your kernel "
"parameters."
msgstr ""

#. Tag: para
#: boot-installer.xml:1666
#, no-c-format
msgid ""
"If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's "
"&arch-title; debian-installer FAQ</ulink>."
msgstr ""

#. Tag: title
#: boot-installer.xml:1683
#, no-c-format
msgid "Amiga"
msgstr "Amiga"

#. Tag: para
#: boot-installer.xml:1684
#, 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>"
msgstr ""

#. Tag: para
#: boot-installer.xml:1690
#, 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>."
msgstr ""

#. Tag: title
#: boot-installer.xml:1699
#, no-c-format
msgid "Atari"
msgstr ""

#. Tag: para
#: boot-installer.xml:1700
#, 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>"
msgstr ""

#. Tag: para
#: boot-installer.xml:1707
#, 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>."
msgstr ""

#. Tag: title
#: boot-installer.xml:1716
#, no-c-format
msgid "BVME6000"
msgstr ""

#. Tag: para
#: boot-installer.xml:1717
#, 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\"/>)."
msgstr ""

#. Tag: title
#: boot-installer.xml:1727
#, no-c-format
msgid "Macintosh"
msgstr ""

#. Tag: para
#: boot-installer.xml:1728
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1735
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1750
#, no-c-format
msgid "MVME147 and MVME16x"
msgstr ""

#. Tag: para
#: boot-installer.xml:1751
#, 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>"
msgstr ""

#. Tag: title
#: boot-installer.xml:1761
#, no-c-format
msgid "Q40/Q60"
msgstr ""

#. Tag: para
#: boot-installer.xml:1762
#, 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>"
msgstr ""

#. Tag: title
#: boot-installer.xml:1773
#, no-c-format
msgid "Booting from a Hard Disk"
msgstr "Indítás egy merevlemezről"

#. Tag: para
#: boot-installer.xml:1779 boot-installer.xml:2385
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1785 boot-installer.xml:2391
#, 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"
"\"/>."
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:1794
#, 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)."
msgstr ""

#. Tag: para
#: boot-installer.xml:1802
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:1823
#, no-c-format
msgid "Booting from AmigaOS"
msgstr "Indítás AmigaOS alól"

#. Tag: para
#: boot-installer.xml:1824
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1830
#, 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\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:1845
#, no-c-format
msgid "Booting from Atari TOS"
msgstr "Indítás Atari TOS alól"

#. Tag: para
#: boot-installer.xml:1846
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1853
#, 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\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:1868
#, no-c-format
msgid "Booting from MacOS"
msgstr "Indítás MacOS alól"

#. Tag: para
#: boot-installer.xml:1869
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1880
#, no-c-format
msgid ""
"Macs require the <command>Penguin</command> bootloader, which can be "
"downloaded from <ulink url=\"&url-m68k-mac;\">the Linux/mac68k sourceforge."
"net project</ulink>. If you do not have the tools to handle a "
"<command>Stuffit</command> archive, you can put it on a MacOS-formatted "
"floppy using a second GNU/Linux machine of any architecture and the "
"<command>hmount</command>, <command>hcopy</command>, and <command>humount</"
"command> tools from the <classname>hfsutils</classname> suite."
msgstr ""

#. Tag: para
#: boot-installer.xml:1891
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1906
#, no-c-format
msgid ""
"To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -&gt; "
"<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> -&gt; <guimenuitem>Save Settings as Default</"
"guimenuitem>."
msgstr ""

#. Tag: para
#: boot-installer.xml:1915
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:1922
#, 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\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:1937
#, no-c-format
msgid "Booting from Q40/Q60"
msgstr "Indítás Q40/Q60 alól"

#. Tag: para
#: boot-installer.xml:1939
#, no-c-format
msgid "FIXME"
msgstr ""

#. Tag: para
#: boot-installer.xml:1943
#, no-c-format
msgid ""
"The installation program should start automatically, so you can continue "
"below at <xref linkend=\"d-i-intro\"/>."
msgstr ""

#. Tag: para
#: boot-installer.xml:1955
#, no-c-format
msgid ""
"Currently, the only &arch-title; subarchitecture that supports CD-ROM "
"booting is the BVME6000."
msgstr ""

#. Tag: para
#: boot-installer.xml:2027
#, 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:"
msgstr ""

#. Tag: para
#: boot-installer.xml:2038
#, no-c-format
msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000"
msgstr ""

#. Tag: para
#: boot-installer.xml:2043
#, no-c-format
msgid "type <screen>i162 &enterkey;</screen> to install an MVME162"
msgstr ""

#. Tag: para
#: boot-installer.xml:2048
#, no-c-format
msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167"
msgstr ""

#. Tag: para
#: boot-installer.xml:2055
#, 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>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2067
#, no-c-format
msgid ""
"For most &arch-title; architectures, booting from a local filesystem is the "
"recommended method."
msgstr ""

#. Tag: para
#: boot-installer.xml:2072
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:2088 boot-installer.xml:2135
#, no-c-format
msgid "SGI TFTP Booting"
msgstr ""

#. Tag: para
#: boot-installer.xml:2089
#, no-c-format
msgid ""
"After entering the command monitor use <informalexample><screen>\n"
"bootp():\n"
"</screen></informalexample> on SGI machines to boot linux and to begin "
"installation of the Debian Software. In order to make this work you may have "
"to unset the <envar>netaddr</envar> environment variable. Type "
"<informalexample><screen>\n"
"unsetenv netaddr\n"
"</screen></informalexample> in the command monitor to do this."
msgstr ""

#. Tag: title
#: boot-installer.xml:2108 boot-installer.xml:2157 boot-installer.xml:2212
#: boot-installer.xml:2251
#, no-c-format
msgid "Broadcom BCM91250A and BCM91480B TFTP Booting"
msgstr ""

#. Tag: para
#: boot-installer.xml:2109 boot-installer.xml:2213
#, no-c-format
msgid ""
"On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load "
"the SiByl boot loader via TFTP which will then load and start the Debian "
"installer. In most cases, you will first obtain an IP address via DHCP but "
"it is also possible to configure a static address. In order to use DHCP, you "
"can enter the following command on the CFE prompt: "
"<informalexample><screen>\n"
"ifconfig eth0 -auto\n"
"</screen></informalexample> Once you have obtained an IP address, you can "
"load SiByl with the following command: <informalexample><screen>\n"
"boot 192.168.1.1:/boot/sibyl\n"
"</screen></informalexample> You need to substitute the IP address listed in "
"this example with either the name or the IP address of your TFTP server. "
"Once you issue this command, the installer will be loaded automatically."
msgstr ""

#. Tag: title
#: boot-installer.xml:2132 boot-installer.xml:2236 boot-installer.xml:2770
#, no-c-format
msgid "Boot Parameters"
msgstr "Indító paraméterek"

#. Tag: para
#: boot-installer.xml:2136
#, no-c-format
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:2141
#, no-c-format
msgid ""
"Following the <command>bootp():</command> command you can give the path and "
"name of the file to boot if you did not give an explicit name via your bootp/"
"dhcp server. Example: <informalexample><screen>\n"
"bootp():/boot/tftpboot.img\n"
"</screen></informalexample> Further kernel parameters can be passed via "
"<command>append</command>:"
msgstr ""

#. Tag: screen
#: boot-installer.xml:2151
#, no-c-format
msgid "bootp(): append=\"root=/dev/sda1\""
msgstr ""

#. Tag: para
#: boot-installer.xml:2158 boot-installer.xml:2252
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:2177 boot-installer.xml:2239
#, no-c-format
msgid "Cobalt TFTP Booting"
msgstr ""

#. Tag: para
#: boot-installer.xml:2178
#, 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:"
msgstr ""

#. Tag: para
#: boot-installer.xml:2188
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2197
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2240
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:2268
#, no-c-format
msgid "s390 Limitations"
msgstr ""

#. Tag: para
#: boot-installer.xml:2269
#, no-c-format
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:2274
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:2285
#, no-c-format
msgid "s390 Boot Parameters"
msgstr "s390 indító paraméterek"

#. Tag: para
#: boot-installer.xml:2286
#, no-c-format
msgid ""
"On S/390 you can append boot parameters in the parm file. This file can "
"either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile."
"debian</filename> is provided with the installation images."
msgstr ""

#. Tag: para
#: boot-installer.xml:2346
#, no-c-format
msgid ""
"Currently, the only &arch-title; subarchitectures that support CD-ROM "
"booting are PReP (though not all systems) and New World PowerMacs. On "
"PowerMacs, hold the <keycap>c</keycap> key, or else the combination of "
"<keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, "
"and <keycap>Delete</keycap> keys together while booting to boot from the CD-"
"ROM."
msgstr ""

#. Tag: para
#: boot-installer.xml:2355
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2364
#, 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"
msgstr ""

#. Tag: screen
#: boot-installer.xml:2373
#, no-c-format
msgid "0 &gt; boot cd:,\\install\\yaboot"
msgstr ""

#. Tag: title
#: boot-installer.xml:2379
#, no-c-format
msgid "Booting from Hard Disk"
msgstr "Indítás merevlemezről"

#. Tag: title
#: boot-installer.xml:2400
#, no-c-format
msgid "Booting CHRP from OpenFirmware"
msgstr "CHRP Indítása OpenFirmware alól"

#. Tag: emphasis
#: boot-installer.xml:2404
#, no-c-format
msgid "Not yet written."
msgstr ""

#. Tag: title
#: boot-installer.xml:2409
#, no-c-format
msgid "Booting OldWorld PowerMacs from MacOS"
msgstr ""

#. Tag: para
#: boot-installer.xml:2410
#, 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."
msgstr ""

#. Tag: title
#: boot-installer.xml:2428
#, no-c-format
msgid "Booting NewWorld Macs from OpenFirmware"
msgstr ""

#. Tag: para
#: boot-installer.xml:2429
#, no-c-format
msgid ""
"You will have already placed the <filename>vmlinux</filename>, "
"<filename>initrd.gz</filename>, <filename>yaboot</filename>, and "
"<filename>yaboot.conf</filename> files at the root level of your HFS "
"partition in <xref linkend=\"files-newworld\"/>. Restart the computer, and "
"immediately (during the chime) hold down the <keycap>Option</keycap>, "
"<keycap>Command (cloverleaf/Apple)</keycap>, <keycap>o</keycap>, and "
"<keycap>f</keycap> keys all together. After a few seconds you will be "
"presented with the Open Firmware prompt. At the prompt, type "
"<informalexample><screen>\n"
"0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
"</screen></informalexample> replacing <replaceable>x</replaceable> with the "
"partition number of the HFS partition where the kernel and yaboot files were "
"placed, followed by a &enterkey;. On some machines, you may need to use "
"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few "
"more seconds you will see a yaboot prompt <informalexample><screen>\n"
"boot:\n"
"</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type "
"either <userinput>install</userinput> or <userinput>install video=ofonly</"
"userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> "
"argument is for maximum compatibility; you can try it if <userinput>install</"
"userinput> doesn't work. The Debian installation program should start."
msgstr ""

#. Tag: title
#: boot-installer.xml:2464
#, no-c-format
msgid "Booting from USB memory stick"
msgstr "Indítás USB memóriáról"

#. Tag: para
#: boot-installer.xml:2465
#, no-c-format
msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
msgstr ""

#. Tag: para
#: boot-installer.xml:2471
#, 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\"/>)."
msgstr ""

#. Tag: para
#: boot-installer.xml:2483
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2495
#, 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>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2509
#, 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;."
msgstr ""
"A rendszer elindul é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: para
#: boot-installer.xml:2515
#, 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\"/>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2548
#, no-c-format
msgid "Currently, PReP and New World PowerMac systems support netbooting."
msgstr ""

#. Tag: para
#: boot-installer.xml:2552
#, no-c-format
msgid ""
"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
"monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command "
"<command>boot enet:0</command>. PReP and CHRP boxes may have different ways "
"of addressing the network. On a PReP machine, you should try <userinput>boot "
"net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,"
"<replaceable>client_ipaddr</replaceable></userinput>. On some PReP systems "
"(e.g. Motorola PowerStack machines) the command <userinput>help boot</"
"userinput> may give a description of syntax and available options."
msgstr ""

#. Tag: para
#: boot-installer.xml:2570
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2582
#, 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."
msgstr ""
"A <filename>boot-floppy-hfs.img</filename> flopi indításához, tedd a flopi "
"meghajtóba a rendszer leállítása után, a bekapcsoló megnyomása előtt."

#. Tag: para
#: boot-installer.xml:2588
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2595
#, 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."
msgstr ""
"Indítás után a <filename>root.bin</filename> flopi kell. Tedd be a root "
"flopit és üsd le az &enterkey;-t. A telepítő program elindul a gyökér "
"rendszer memóriába töltése után."

#. Tag: title
#: boot-installer.xml:2606
#, no-c-format
msgid "PowerPC Boot Parameters"
msgstr "PowerPC indító paraméterek"

#. Tag: para
#: boot-installer.xml:2607
#, 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> ."
msgstr ""

#. Tag: para
#: boot-installer.xml:2647
#, 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."
msgstr ""

#. Tag: para
#: boot-installer.xml:2701
#, 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)."
msgstr ""

#. Tag: para
#: boot-installer.xml:2713
#, no-c-format
msgid ""
"Floppy images are currently only available for sparc32, but, for technical "
"reasons, not for official releases. (The reason is that they can only be "
"built as root, which is not supported by our build daemons.) Look under "
"<quote>daily built images</quote> on the <ulink url=\"&url-d-i;\">Debian "
"Installer project website</ulink> for links to floppy images for sparc32."
msgstr ""

#. Tag: para
#: boot-installer.xml:2722
#, no-c-format
msgid ""
"To boot from floppy on a Sparc, use <informalexample><screen>\n"
"Stop-A -&gt; 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>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2732
#, 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>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2739
#, no-c-format
msgid ""
"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."
msgstr ""
"Ha flopiról indítanál, de ehhez hasonló üzeneteket kapsz:"
"<informalexample><screen>\n"
"Fatal error: Cannot read partition\n"
"Illegal or malformed device name\n"
"</screen></informalexample> lehet, hogy a flopi indítás egyszerűen nem "
"támogatott e gépen."

#. Tag: title
#: boot-installer.xml:2751
#, no-c-format
msgid "IDPROM Messages"
msgstr "IDPROM üzenetek"

#. Tag: para
#: boot-installer.xml:2752
#, 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."
msgstr ""
"Ha <quote>IDPROM</quote> gondokról szóló üzenetek miatt nem tudsz indítani, "
"lehet, hogy az NVRAM elem, mely a firmware beállításait tartalmazza, "
"lemerült. Lásd a <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM GYIK</ulink> "
"címet több adatért."

#. Tag: para
#: boot-installer.xml:2771
#, 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."
msgstr ""
"Az indító paraméterek Linux kernel paraméterek, melyek általában a "
"perifériák helyes használatára szolgálnak. A kernel általában képes ezek "
"adatainak automatikus érzékelésére. Egyes esetekben azonban egy kis segítség "
"szükséges."

#. Tag: para
#: boot-installer.xml:2778
#, 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."
msgstr ""
"A rendszert 1. ízben az alap paraméterekkel jó indítani (vagyis továbbiak "
"megadása nélkül) és meggyőződni arról, működése helyes-e. Ha nem, egy "
"későbbi újraindításkor megadhatók különleges paraméterek, melyek a rendszert "
"kisegítik egyes adatokkal a hardverről."

#. Tag: para
#: boot-installer.xml:2785
#, 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\"/>."
msgstr ""
"Sok indító paraméterről szóló adat van a <ulink url=\"http://www.tldp.org/"
"HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOGYAN</ulink> leírásban, "
"benne kétes hardverekről szólók is. Ez csak egy vázlatos szakasz a "
"legáltalánosabb paraméterekről. Néhány szokásos találat megtalálható az "
"alábbi: <xref linkend=\"boot-troubleshooting\"/> részben."

#. Tag: para
#: boot-installer.xml:2794
#, 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."
msgstr ""
"A kernel indulásakor egy <informalexample><screen>\n"
"Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k "
"available\n"
"</screen></informalexample> üzenet látható a folyamat elején. A "
"<replaceable>total</replaceable> a RAM teljes méretét adja kilobájtban. Ha "
"nem pontos, a <userinput>mem=<replaceable>ram</replaceable></userinput> "
"paraméter használandó, ahol a <replaceable>ram</replaceable> a memória "
"mérete, melyet <quote>k</quote> követ kilobájtokhoz, vagy <quote>m</quote> "
"megabájtokhoz. Például a <userinput>mem=65536k</userinput> és "
"<userinput>mem=64m</userinput> jelentése egyaránt 64MB RAM."

#. Tag: para
#: boot-installer.xml:2810
#, 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>."
msgstr ""
"Soros konzollal indításkor a kernel általában automatikusan felismeri "
"ezt<phrase arch=\"mipsel\"> (DECstation esetén nem)</phrase>. Ha van videó "
"kártya (framebuffer) és billentyűzet a soros konzol által indítandó gépen, "
"át kell adni a <userinput>console=<replaceable>eszköz</replaceable></"
"userinput> argumentumot a kernelnek, ahol az <replaceable>eszköz</"
"replaceable> a soros eszköz, mely általában valami ilyesmi: <filename>ttyS0</"
"filename>."

#. Tag: para
#: boot-installer.xml:2823
#, 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>."
msgstr ""
"&arch-title; architektúrán a soros eszközök neve <filename>ttya</filename> "
"vagy <filename>ttyb</filename>. Vagy állítsd be, hogy az <envar>input-"
"device</envar> és <envar>output-device</envar> OpenPROM változók értéke "
"legyen <filename>ttya</filename>."

#. Tag: title
#: boot-installer.xml:2834
#, no-c-format
msgid "Debian Installer Parameters"
msgstr "Debian Telepítő paraméterek"

#. Tag: para
#: boot-installer.xml:2835
#, no-c-format
msgid ""
"The installation system recognizes a few additional boot "
"parameters<footnote> <para> With current kernels (2.6.9 or newer) you can "
"use 32 command line options and 32 environment options. If these numbers are "
"exceeded, the kernel will panic. </para> </footnote> which may be useful."
msgstr ""
"A telepítő rendszer pár további indító paramétert is ismer<footnote> <para> "
"A jelenlegi kernelekkel  (2.6.9 vagy újabb) 32 parancssori opció és 32 "
"környezeti opció használható. Ennek túllépése kernel pánikot okoz. </para> </"
"footnote> mely hasznos lehet."

#. Tag: para
#: boot-installer.xml:2848
#, no-c-format
msgid ""
"A number of parameters have a <quote>short form</quote> that helps avoid the "
"limitations of the kernel command line options and makes entering the "
"parameters easier. If a parameter has a short form, it will be listed in "
"brackets behind the (normal) long form. Examples in this manual will "
"normally use the short form too."
msgstr ""
"Sok paraméterhez van egy <quote>rövid forma</quote>, mely segít elkerülni a "
"kernel parancs-sori opciók korlátját és könnyebbé teszi a paraméterek "
"megadását. Ha egy paraméternek van rövid formája, zárójelben írjuk a "
"(rendes) hosszú forma után. A példák is a rövid formát használják."

#. Tag: term
#: boot-installer.xml:2860
#, no-c-format
msgid "debconf/priority (priority)"
msgstr "debconf/priority (elsőbbség)"

#. Tag: para
#: boot-installer.xml:2861
#, no-c-format
msgid "This parameter sets the lowest priority of messages to be displayed."
msgstr "E paraméter adja meg a megjelenítendő üzenetek legkisebb elsőbbségét."

#. Tag: para
#: boot-installer.xml:2865
#, 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."
msgstr ""
"Az alap telepítés a <userinput>priority=high</userinput> értéket használja. "
"Ekkor a kritikus és magas elsőbbségű üzenetek jelennek meg, a közepes és "
"alacsony elsőbbségű üzenetek nem. Hibák esetén a telepítő a szükséges "
"szintre állítja ezt."

#. Tag: para
#: boot-installer.xml:2872
#, 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."
msgstr ""
"A <userinput>priority=medium</userinput> részletesebb irányítást ad a "
"telepítéshez. A <userinput>priority=low</userinput> mindent kérdez (ez "
"ugyanaz, mint az <emphasis>expert</emphasis> indítás mód). A "
"<userinput>priority=critical</userinput> esetén a rendszer csak a kritikus "
"üzeneteket jeleníti meg és ha minden rendben, nem kérdez."

#. Tag: term
#: boot-installer.xml:2886
#, no-c-format
msgid "DEBIAN_FRONTEND"
msgstr "DEBIAN_FRONTEND"

#. Tag: para
#: boot-installer.xml:2887
#, no-c-format
msgid ""
"This boot parameter controls the type of user interface used for the "
"installer. The current possible parameter settings are: <itemizedlist> "
"<listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></"
"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</"
"userinput></para> </listitem><listitem> "
"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </"
"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> "
"</listitem> </itemizedlist> The default frontend is "
"<userinput>DEBIAN_FRONTEND=newt</userinput>. "
"<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial "
"console installs. Generally, only the <userinput>newt</userinput> frontend "
"is available on default install media. On architectures that support it, the "
"graphical installer uses the <userinput>gtk</userinput> frontend."
msgstr ""
"Ez szabja meg a telepítő által használt felhasználó felületet. A jelenlegi "
"lehetséges paraméter beállítások: <itemizedlist> <listitem> "
"<para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </"
"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> "
"</listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></"
"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</"
"userinput></para> </listitem> </itemizedlist> Az alapfelület a "
"<userinput>DEBIAN_FRONTEND=newt</userinput>. A "
"<userinput>DEBIAN_FRONTEND=text</userinput> soros konzolos telepítésekhez "
"jó. Általában csak a <userinput>newt</userinput> felület elérhető az alap "
"telepítő médián. A támogató architektúrákon a grafikus telepítő a "
"<userinput>gtk</userinput> felületet használja."

#. Tag: term
#: boot-installer.xml:2916
#, no-c-format
msgid "BOOT_DEBUG"
msgstr "BOOT_DEBUG"

#. Tag: para
#: boot-installer.xml:2917
#, 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.)"
msgstr ""
"Ha e paraméter értéke 2, a telepítő indító folyamat részletesebb naplózásra "
"kerül. Ha 3, hibakereső héjakat tesz elérhetővé az indító folyamat fő "
"pontjain. (Lépj ki a héjakból az indító folyamat folytatásához.)"

#. Tag: userinput
#: boot-installer.xml:2926
#, no-c-format
msgid "BOOT_DEBUG=0"
msgstr "BOOT_DEBUG=0"

#. Tag: para
#: boot-installer.xml:2927
#, no-c-format
msgid "This is the default."
msgstr "Ez az alap."

#. Tag: userinput
#: boot-installer.xml:2931
#, no-c-format
msgid "BOOT_DEBUG=1"
msgstr "BOOT_DEBUG=1"

#. Tag: para
#: boot-installer.xml:2932
#, no-c-format
msgid "More verbose than usual."
msgstr "Átlagnál bővebb."

#. Tag: userinput
#: boot-installer.xml:2936
#, no-c-format
msgid "BOOT_DEBUG=2"
msgstr "BOOT_DEBUG=2"

#. Tag: para
#: boot-installer.xml:2937
#, no-c-format
msgid "Lots of debugging information."
msgstr "Sok hibakereső adat."

#. Tag: userinput
#: boot-installer.xml:2941
#, no-c-format
msgid "BOOT_DEBUG=3"
msgstr "BOOT_DEBUG=3"

#. Tag: para
#: boot-installer.xml:2942
#, 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."
msgstr ""
"A héjak az indító folyamat különböző pontjain futnak részletes hibák "
"visszaadásához. Lépj ki a héjból az indítás folytatásához."

#. Tag: term
#: boot-installer.xml:2956
#, no-c-format
msgid "INSTALL_MEDIA_DEV"
msgstr "INSTALL_MEDIA_DEV"

#. Tag: para
#: boot-installer.xml:2957
#, 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>"
msgstr ""
"E paraméter értéke a Debian telepítőt betöltő eszköz útvonala. Például "
"<userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"

#. Tag: para
#: boot-installer.xml:2963
#, 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."
msgstr ""
"Az indító flopi, ami alapban végignézi az összes flopit a gyökér flopi "
"megtalálásához felülírható e paraméterrel, hogy csak 1 eszközt nézzen."

#. Tag: term
#: boot-installer.xml:2973
#, no-c-format
msgid "debian-installer/framebuffer (fb)"
msgstr "debian-installer/framebuffer (fb)"

#. Tag: para
#: boot-installer.xml:2974
#, no-c-format
msgid ""
"Some architectures use the kernel framebuffer to offer installation in a "
"number of languages. If framebuffer causes a problem on your system you can "
"disable the feature by the parameter <userinput>fb=false</userinput>. "
"Problem symptoms are error messages about bterm or bogl, a blank screen, or "
"a freeze within a few minutes after starting the install."
msgstr ""
"Egyes architektúrák használják a kernel framebuffert a telepítő több-nyelvű "
"támogatásához. Ha ez gondot okoz, kikapcsolható az <userinput>fb=false</"
"userinput> paraméterrel. A szokásos gondok hibaüzenetek a bterm és bogl "
"körül, üres képernyő vagy fagyás a telepítés indítása után pár perccel."

#. Tag: para
#: boot-installer.xml:2983
#, 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."
msgstr ""
"A <userinput>video=vga16:off</userinput> argumentum szintén használható a "
"kernel framebuffer kikapcsolására. Ilyen gondok vannak a Dell Inspiron "
"gépeken Mobil Radeon kártya esetén."

#. Tag: para
#: boot-installer.xml:2989
#, no-c-format
msgid "Such problems have been reported on the Amiga 1200 and SE/30."
msgstr "Hasonló problémákról érkezett jelentés az Amiga 1200 és SE/30 gépeken."

#. Tag: para
#: boot-installer.xml:2993
#, no-c-format
msgid "Such problems have been reported on hppa."
msgstr "Hasonló problémákról érkezett jelentés egyes hppa gépeken."

#. Tag: para
#: boot-installer.xml:2997
#, 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."
msgstr ""
"Egyes rendszerek kijelző-gondjai miatt a framebuffer támogatás "
"<emphasis>alapból kikapcsolt</emphasis> &arch-title; architektúránál. Ez "
"kissé csúf megjelenést okozhat ott, ahol a támogatás amúgy működne, például "
"ATI kártyák esetén. A kijelző problémákat látsz a telepítőben, indíthatsz a "
"<userinput>debian-installer/framebuffer=true</userinput> vagy röviden "
"<userinput>fb=true</userinput> paraméterrel."

#. Tag: term
#: boot-installer.xml:3011
#, no-c-format
msgid "debian-installer/theme (theme)"
msgstr "debian-installer/theme (téma)"

#. Tag: para
#: boot-installer.xml:3012
#, no-c-format
msgid ""
"A theme determines how the user interface of the installer looks (colors, "
"icons, etc.). What themes are available differs per frontend. Currently both "
"the newt and gtk frontends only have a <quote>dark</quote> theme that was "
"designed for visually impaired users. Set the theme by booting with "
"<userinput>theme=<replaceable>dark</replaceable></userinput>."
msgstr ""
"Egy téma meghatározza, hogyan nézzen ki a telepítő felhasználói felülete "
"(színek, ikonok, stb.). Az elérhető témák a felülettől függenek. A newt és "
"gtk felületek is támogatják a <quote>dark</quote> témát, mely gyengén "
"látóknak is megfelelő. A téma így állítható be: "
"<userinput>theme=<replaceable>dark</replaceable></userinput>."

#. Tag: term
#: boot-installer.xml:3024
#, no-c-format
msgid "debian-installer/probe/usb"
msgstr "debian-installer/probe/usb"

#. Tag: para
#: boot-installer.xml:3025
#, no-c-format
msgid ""
"Set to <userinput>false</userinput> to prevent probing for USB on boot, if "
"that causes problems."
msgstr "A <userinput>false</userinput> tiltja az USB indítást, ha gondot okoz."

#. Tag: term
#: boot-installer.xml:3034 boot-installer.xml:3225
#, no-c-format
msgid "netcfg/disable_dhcp"
msgstr "netcfg/disable_dhcp"

#. Tag: para
#: boot-installer.xml:3035
#, 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."
msgstr ""
"Alapértelmezetten a &d-i; önműködően megpróbálja a hálózatot beállítani DHCP-"
"n át. Ha sikerül, valószínűleg nem lesz esély a kapott beállítások "
"módosítására. A hálózat kézi beállítása csak a DHCP meghiúsulásakor "
"lehetséges."

#. Tag: para
#: boot-installer.xml:3042
#, 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."
msgstr ""
"Ha van egy DHCP kiszolgáló a helyi hálózaton, de nem akarod használni, mert "
"például rossz választ ad, használhatod a <userinput>netcfg/"
"disable_dhcp=true</userinput> paramétert a hálózati DHCP-beállítás tiltására "
"és megadhatod az adatokat kézzel."

#. Tag: term
#: boot-installer.xml:3053
#, no-c-format
msgid "hw-detect/start_pcmcia"
msgstr "hw-detect/start_pcmcia"

#. Tag: para
#: boot-installer.xml:3054
#, 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."
msgstr ""
"A <userinput>false</userinput> tiltja a PCMCIA szolgáltatások indítását, ha "
"gondot okoznak. Egyes laptopok híresek erről."

#. Tag: term
#: boot-installer.xml:3064
#, no-c-format
msgid "preseed/url (url)"
msgstr "preseed/url (url)"

#. Tag: para
#: boot-installer.xml:3065
#, no-c-format
msgid ""
"Specify the url to a preconfiguration file to download and use for "
"automating the install. See <xref linkend=\"automatic-install\"/>."
msgstr ""
"Megadja az automata telepítéshez letöltendő és használandó elő-beállító "
"fájlra mutató url-t. Lásd a <xref linkend=\"automatic-install\"/> részt."

#. Tag: term
#: boot-installer.xml:3074
#, no-c-format
msgid "preseed/file (file)"
msgstr "preseed/file (fájl)"

#. Tag: para
#: boot-installer.xml:3075
#, no-c-format
msgid ""
"Specify the path to a preconfiguration file to load for automating the "
"install. See <xref linkend=\"automatic-install\"/>."
msgstr ""
"Megadja az automata telepítéshez betöltendő elő-beállító fájl útvonalát. "
"Lásd a <xref linkend=\"automatic-install\"/> részt."

#. Tag: term
#: boot-installer.xml:3084
#, no-c-format
msgid "preseed/interactive"
msgstr "preseed/interactive"

#. Tag: para
#: boot-installer.xml:3085
#, no-c-format
msgid ""
"Set to <userinput>true</userinput> to display questions even if they have "
"been preseeded. Can be useful for testing or debugging a preconfiguration "
"file. Note that this will have no effect on parameters that are passed as "
"boot parameters, but for those a special syntax can be used. See <xref "
"linkend=\"preseed-seenflag\"/> for details."
msgstr ""
"Legyen <userinput>true</userinput> az előírt kérdések feltevéséhez is. Egy "
"előíró fájl próbájára vagy javítására jó. Ez nem hat az átadott indító "
"paraméterekre, ezek esetén különleges nyelvtan kell. Lásd itt: <xref linkend="
"\"preseed-seenflag\"/>."

#. Tag: term
#: boot-installer.xml:3097
#, no-c-format
msgid "auto-install/enable (auto)"
msgstr "auto-install/enable (auto)"

#. Tag: para
#: boot-installer.xml:3098
#, no-c-format
msgid ""
"Delay questions that are normally asked before preseeding is possible until "
"after the network is configured. See <xref linkend=\"preseed-auto\"/> for "
"details about using this to automate installs."
msgstr ""
"Az elő-beállítások végrehajtása előtt felteendő kérdések megválaszolása "
"elhalasztható a hálózat beállításáig. Lásd a <xref linkend=\"preseed-auto\"/"
"> részt ennek használatához az automata telepítésben."

#. Tag: term
#: boot-installer.xml:3109
#, no-c-format
msgid "cdrom-detect/eject"
msgstr "cdrom-detect/eject"

#. Tag: para
#: boot-installer.xml:3110
#, 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."
msgstr ""
"Alapban az újraindítás előtt a &d-i; önműködően kiadja a telepítés alatt "
"használt optikai médiát. Ez szükségtelen, ha a rendszer nem indul önműködően "
"a CD-lemezről. Néha kimondottan rossz, például, ha az optikai meghajtó nem "
"teszi be újra a médiát és a felhasználó nincs ott. Sok rés-töltős, karcsú és "
"fentről-töltős stílusú meghajtó nem tudja automatikusan újratölteni a médiát."

#. Tag: para
#: boot-installer.xml:3119
#, no-c-format
msgid ""
"Set to <userinput>false</userinput> to disable automatic ejection, and be "
"aware that you may need to ensure that the system does not automatically "
"boot from the optical drive after the initial installation."
msgstr ""
"Legyen <userinput>false</userinput> az automata kiadás kikapcsolásához, "
"ekkor magadnak kell biztosítani, hogy a rendszer ne induljon önműködően az "
"optikai meghajtóról a telepítés után."

#. Tag: term
#: boot-installer.xml:3130
#, no-c-format
msgid "debian-installer/allow_unauthenticated"
msgstr "debian-installer/allow_unauthenticated"

#. Tag: para
#: boot-installer.xml:3131
#, no-c-format
msgid ""
"By default the installer requires that repositories be authenticated using a "
"known gpg key. Set to <userinput>true</userinput> to disable that "
"authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</"
"emphasis>"
msgstr ""
"Alapban a telepítő ismert gpg kulcs által hitelesített tárat igényel. "
"Állítsd <userinput>true</userinput> értékre a hitelesítés kikapcsolásához. "
"<emphasis role=\"bold\">Figyelem: nem biztonságos, nem ajánlott.</emphasis>"

#. Tag: term
#: boot-installer.xml:3142
#, no-c-format
msgid "ramdisk_size"
msgstr "ramdisk_size"

#. Tag: para
#: boot-installer.xml:3143
#, no-c-format
msgid ""
"This parameter should already be set to a correct value where needed; set it "
"only it you see errors during the boot that indicate the ramdisk could not "
"be loaded completely. The value is in kB."
msgstr ""
"E paraméter alapban már helyes, ha szükséges volt; csak akkor állítsd, ha "
"hibát látsz a telepítés során, ami azt jelzi, hogy a ram-lemez nem került "
"teljesen betöltésre. A mértékegység: kB."

#. Tag: term
#: boot-installer.xml:3153
#, no-c-format
msgid "mouse/left"
msgstr "mouse/left"

#. Tag: para
#: boot-installer.xml:3154
#, no-c-format
msgid ""
"For the gtk frontend (graphical installer), users can switch the mouse to "
"left-handed operation by setting this parameter to <userinput>true</"
"userinput>."
msgstr ""
"A gtk felülethez (grafikus telepítő) a felhasználók az egeret bal-kezesre "
"válthatják e paraméter <userinput>true</userinput> értékre állításával."

#. Tag: term
#: boot-installer.xml:3163
#, no-c-format
msgid "directfb/hw-accel"
msgstr "directfb/hw-accel"

#. Tag: para
#: boot-installer.xml:3164
#, no-c-format
msgid ""
"For the gtk frontend (graphical installer), hardware acceleration in "
"directfb is disabled by default. To enable it, set this parameter to "
"<userinput>true</userinput> when booting the installer."
msgstr ""
"A gtk felülethez (grafikus telepítő) a directfb hardveres gyorsítás alapból "
"kikapcsolt. Bekapcsolásához, legyen a paraméter <userinput>true</userinput> "
"a telepítő indításakor."

#. Tag: term
#: boot-installer.xml:3174
#, no-c-format
msgid "rescue/enable"
msgstr "rescue/enable"

#. Tag: para
#: boot-installer.xml:3175
#, no-c-format
msgid ""
"Set to <userinput>true</userinput> to enter rescue mode rather than "
"performing a normal installation. See <xref linkend=\"rescue\"/>."
msgstr ""
"Legyen <userinput>true</userinput> a rendes telepítés helyett mentő módba "
"lépéshez. Lásd: <xref linkend=\"rescue\"/>."

#. Tag: title
#: boot-installer.xml:3186
#, no-c-format
msgid "Using boot parameters to answer questions"
msgstr "Indító paraméterek használata kérdések megválaszolására"

#. Tag: para
#: boot-installer.xml:3187
#, no-c-format
msgid ""
"With some exceptions, a value can be set at the boot prompt for any question "
"asked during the installation, though this is only really useful in specific "
"cases. General instructions how to do this can be found in <xref linkend="
"\"preseed-bootparms\"/>. Some specific examples are listed below."
msgstr ""
"Pár kivétellel az indító jelnél bármely telepítés alatt feltett kérdés "
"értéke beállítható, ez csak egyes esetekben igazán hasznos. Általános leírás "
"erről a <xref linkend=\"preseed-bootparms\"/> részben. Íme pár példa."

#. Tag: term
#: boot-installer.xml:3199
#, no-c-format
msgid "debian-installer/locale (locale)"
msgstr "debian-installer/locale (honosítás)"

#. Tag: para
#: boot-installer.xml:3200
#, no-c-format
msgid ""
"Can be used to set both the language and country for the installation. This "
"will only work if the locale is supported in Debian. For example, use "
"<userinput>locale=de_CH</userinput> to select German as language and "
"Switzerland as country."
msgstr ""
"A nyelv és ország beállítására használható. Minden Debian által támogatott "
"helyi beállításra működik. Például a <userinput>locale=de_CH</userinput> "
"német nyelvet választ, országnak pedig Svájcot."

#. Tag: term
#: boot-installer.xml:3211
#, no-c-format
msgid "anna/choose_modules (modules)"
msgstr "anna/choose_modules (modules)"

#. Tag: para
#: boot-installer.xml:3212
#, no-c-format
msgid ""
"Can be used to automatically load installer components that are not loaded "
"by default. Examples of optional components that may be useful are "
"<classname>openssh-client-udeb</classname> (so you can use <command>scp</"
"command> during the installation)<phrase arch=\"not-s390\"> and "
"<classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
msgstr ""
"Az alapban nem betöltött telepítő összetevők automata betöltésére "
"használható. Példa lehetséges hasznos összetevőre az <classname>openssh-"
"client-udeb</classname> (így használhatod az <command>scp</command> másolót "
"a telepítés alatt) <phrase arch=\"not-s390\"> és a <classname>ppp-udeb</"
"classname> (lásd itt: <xref linkend=\"pppoe\"/>)</phrase>."

#. Tag: para
#: boot-installer.xml:3226
#, no-c-format
msgid ""
"Set to <userinput>true</userinput> if you want to disable DHCP and instead "
"force static network configuration."
msgstr ""
"Állítsd <userinput>true</userinput> értékre a DHCP kikapcsolásához és "
"helyette statikus hálózati beállítás kikényszerítéséhez."

#. Tag: term
#: boot-installer.xml:3235
#, no-c-format
msgid "mirror/protocol (protocol)"
msgstr "mirror/protocol (protocol)"

#. Tag: para
#: boot-installer.xml:3236
#, no-c-format
msgid ""
"By default the installer will use the http protocol to download files from "
"Debian mirrors and changing that to ftp is not possible during installations "
"at normal priority. By setting this parameter to <userinput>ftp</userinput>, "
"you can force the installer to use that protocol instead. Note that you "
"cannot select an ftp mirror from a list, you have to enter the hostname "
"manually."
msgstr ""
"Alapban a telepítő http protokollt használ fájlok letöltésére Debian "
"tükrökről és ftp protkollra cserélésre nincs mód telepítéskor normál "
"elsőbbségnél. A paraméter beállítása <userinput>ftp</userinput> protokollra "
"a telepítőt ennek használatára bírja. Fontos tudni, hogy a listából nem "
"választható ftp tükör, ezt kézzel kell majd megadni."

#. Tag: term
#: boot-installer.xml:3249
#, no-c-format
msgid "tasksel:tasksel/first (tasks)"
msgstr "tasksel:tasksel/first (feladatok)"

#. Tag: para
#: boot-installer.xml:3250
#, no-c-format
msgid ""
"Can be used to select tasks that are not available from the interactive task "
"list, such as the <literal>kde-desktop</literal> task. See <xref linkend="
"\"pkgsel\"/> for additional information."
msgstr ""
"Az interaktív listából el nem érhető feladatok kiválasztására használható, "
"fontos például a <literal>hungarian-desktop</literal> használata. Lásd a "
"<xref linkend=\"pkgsel\"/> részt további adatokért."

#. Tag: title
#: boot-installer.xml:3264
#, no-c-format
msgid "Passing parameters to kernel modules"
msgstr "Paraméterek átadása kernel moduloknak"

#. Tag: para
#: boot-installer.xml:3265
#, no-c-format
msgid ""
"If drivers are compiled into the kernel, you can pass parameters to them as "
"described in the kernel documentation. However, if drivers are compiled as "
"modules and because kernel modules are loaded a bit differently during an "
"installation than when booting an installed system, it is not possible to "
"pass parameters to modules as you would normally do. Instead, you need to "
"use a special syntax recognized by the installer which will then make sure "
"that the parameters are saved in the proper configuration files and will "
"thus be used when the modules are actually loaded. The parameters will also "
"be propagated automatically to the configuration for the installed system."
msgstr ""
"Kernelbe fordított meghajtók számára lehetséges a kernel dokumentációja "
"szerinti paraméterek átadása. Ám akkor, ha modulokként fordítottak, mivel "
"ezek kissé másképp töltődnek be a telepítéskor, mint a telepített "
"rendszeren, nem adhatók át úgy paraméterek, mint rendesen. A telepítő által "
"ismert különleges szintaxist kell használni, így ezek a helyes beállító "
"fájlba kerülnek és felhasználásra kerülnek a modulok tényleges betöltésekor. "
"E paraméterek átkerülnek a telepített rendszerbe is."

#. Tag: para
#: boot-installer.xml:3278
#, no-c-format
msgid ""
"Note that it is now quite rare that parameters need to be passed to modules. "
"In most cases the kernel will be able to probe the hardware present in a "
"system and set good defaults that way. However, in some situations it may "
"still be needed to set parameters manually."
msgstr ""
"Erre ritkán van szükség. A kernel szinte mindig képes a rendszeren lévő "
"hardvert kipróbálni és jó alapértelmezett értékeket beállítani. De egyes "
"esetekben jól jöhet paraméterek kézi beállítása."

#. Tag: para
#: boot-installer.xml:3285
#, no-c-format
msgid ""
"The syntax to use to set parameters for modules is: "
"<informalexample><screen>\n"
"<replaceable>module_name</replaceable>.<replaceable>parameter_name</"
"replaceable>=<replaceable>value</replaceable>\n"
"</screen></informalexample> If you need to pass multiple parameters to the "
"same or different modules, just repeat this. For example, to set an old 3Com "
"network interface card to use the BNC (coax) connector and IRQ 10, you would "
"pass:"
msgstr ""
"A modulokhoz beállítandó paraméterek nyelvtana:<informalexample><screen>\n"
"<replaceable>modul_név</replaceable>.<replaceable>paraméter_név</"
"replaceable>=<replaceable>érték</replaceable>\n"
"</screen></informalexample> Ha több paramétert akarsz átadni egy vagy több "
"modulhoz, csak ismételd ezt. Például egy régi 3Com hálózati csatoló kártya "
"beállítása a BNC (koax) csatlakozó és IRQ 10 használatához:"

#. Tag: screen
#: boot-installer.xml:3295
#, no-c-format
msgid "3c509.xcvr=3 3c509.irq=10"
msgstr "3c509.xcvr=3 3c509.irq=10"

#. Tag: title
#: boot-installer.xml:3301
#, no-c-format
msgid "Blacklisting kernel modules"
msgstr "Kernel modulok feketelistája"

#. Tag: para
#: boot-installer.xml:3302
#, no-c-format
msgid ""
"Sometimes it may be necessary to blacklist a module to prevent it from being "
"loaded automatically by the kernel and udev. One reason could be that a "
"particular module causes problems with your hardware. The kernel also "
"sometimes lists two different drivers for the same device. This can cause "
"the device to not work correctly if the drivers conflict or if the wrong "
"driver is loaded first."
msgstr ""
"Néha egy modult feketelistára kell tenni, hogy a kernel és udev ne töltse "
"be. Például, ha gondot ad egy adott hardverrel. A kernel néha 2 eltérő "
"modult ad egy eszközhöz. Ez problémás működést okozhat, e meghajtók ütközése "
"vagy előbb rossz meghajtó betöltése esetén."

#. Tag: para
#: boot-installer.xml:3311
#, no-c-format
msgid ""
"You can blacklist a module using the following syntax: "
"<userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. "
"This will cause the module to be blacklisted in <filename>/etc/modprobe.d/"
"blacklist.local</filename> both during the installation and for the "
"installed system."
msgstr ""
"Egy modul így tehető feketelistára: <userinput><replaceable>module_name</"
"replaceable>.blacklist=yes</userinput>. Így a modul feketelistára kerül a "
"<filename>/etc/modprobe.d/blacklist.local</filename> fájlban a telepítés és "
"a telepített rendszer alatt is."

#. Tag: para
#: boot-installer.xml:3319
#, no-c-format
msgid ""
"Note that a module may still be loaded by the installation system itself. "
"You can prevent that from happening by running the installation in expert "
"mode and unselecting the module from the list of modules displayed during "
"the hardware detection phases."
msgstr ""
"Lehet, hogy a modult a telepítő rendszer tölti be. Ez megakadályozható a "
"telepítő szakértő módú futtatásával a modul kijelölt volta törlésével a "
"hardver felismerő szakaszokban."

#. Tag: title
#: boot-installer.xml:3336
#, no-c-format
msgid "Troubleshooting the Installation Process"
msgstr "Hibák elhárítása a telepítő folyamat során"

#. Tag: title
#: boot-installer.xml:3341
#, no-c-format
msgid "CD-ROM Reliability"
msgstr "CD-ROM megbízhatóság"

#. Tag: para
#: boot-installer.xml:3342
#, no-c-format
msgid ""
"Sometimes, especially with older CD-ROM drives, the installer may fail to "
"boot from a CD-ROM. The installer may also &mdash; even after booting "
"successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return "
"errors while reading from it during the installation."
msgstr ""
"Néha, főleg régi CD-ROM meghajtókkal, a telepítő CD-ROM lemezről indítása "
"meghiúsulhat. A telepítő &mdash; akár a CD-ROM lemezről való sikeres indítás "
"után &mdash; talán nem ismeri fel a CD-ROM eszközt vagy hibákat ad a "
"telepítés alatti olvasásakor."

#. Tag: para
#: boot-installer.xml:3349
#, no-c-format
msgid ""
"There are a many different possible causes for these problems. We can only "
"list some common issues and provide general suggestions on how to deal with "
"them. The rest is up to you."
msgstr ""
"Ennek sok eltérő oka lehet. Csak néhány szokásos hibát és kezelésükről szóló "
"általános tanácsot írunk le. A többi tőled függ."

#. Tag: para
#: boot-installer.xml:3355
#, no-c-format
msgid "There are two very simple things that you should try first."
msgstr "Először 2 egyszerű dolgot érdemes kipróbálni."

#. Tag: para
#: boot-installer.xml:3360
#, no-c-format
msgid ""
"If the CD-ROM does not boot, check that it was inserted correctly and that "
"it is not dirty."
msgstr ""
"Ha a CD-ROM nem indul, ellenőrizd, helyesen van-e betéve és nem piszkos-e."

#. Tag: para
#: boot-installer.xml:3366
#, no-c-format
msgid ""
"If the installer fails to recognize a CD-ROM, try just running the option "
"<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </"
"menuchoice> a second time. Some DMA related issues with older CD-ROM drives "
"are known to be resolved in this way."
msgstr ""
"Ha a telepítő nem ismeri fel a CD-ROM meghajtót, először próbáld meg a "
"<menuchoice> <guimenuitem>CD-ROM felismerése és csatolása</guimenuitem> </"
"menuchoice> pont futtatását másodszor. Több régi CD-ROM meghajtónál ismert "
"DMA hiba megoldható így."

#. Tag: para
#: boot-installer.xml:3376
#, no-c-format
msgid ""
"If this does not work, then try the suggestions in the subsections below. "
"Most, but not all, suggestions discussed there are valid for both CD-ROM and "
"DVD, but we'll use the term CD-ROM for simplicity."
msgstr ""
"Ha ez nem megy, próbáld az alábbi javaslatokat. Általában az ott tárgyalt "
"javaslatok a CD-ROM és DVD eszközökre egyaránt érvényesek, de az egyszerűség "
"kedvéért mindig a CD-ROM szót használjuk."

#. Tag: para
#: boot-installer.xml:3382
#, no-c-format
msgid ""
"If you cannot get the installation working from CD-ROM, try one of the other "
"installation methods that are available."
msgstr ""
"Ha a telepítés semmiképp nem megy a CD-ROM eszközről, próbálj egy másik "
"elérhető telepítő módot."

#. Tag: title
#: boot-installer.xml:3390
#, no-c-format
msgid "Common issues"
msgstr "Általános hibák"

#. Tag: para
#: boot-installer.xml:3393
#, no-c-format
msgid ""
"Some older CD-ROM drives do not support reading from discs that were burned "
"at high speeds using a modern CD writer."
msgstr ""
"Néhány régi CD-ROM meghajtó nem támogatja a korszerű CD-írók használatával "
"nagy sebességgel írt lemezek olvasását."

#. Tag: para
#: boot-installer.xml:3399
#, no-c-format
msgid ""
"If your system boots correctly from the CD-ROM, it does not necessarily mean "
"that Linux also supports the CD-ROM (or, more correctly, the controller that "
"your CD-ROM drive is connected to)."
msgstr ""
"Ha a rendszer elindul a CD-ROM eszközről, ez nem feltétlenül jelenti, hogy a "
"Linux is támogatja azt (vagy, pontosabban a vezérlőt, melyre a CD-ROM "
"meghajtó kötve van)."

#. Tag: para
#: boot-installer.xml:3406
#, no-c-format
msgid ""
"Some older CD-ROM drives do not work correctly if <quote>direct memory "
"access</quote> (DMA) is enabled."
msgstr ""
"Pár régi CD-ROM meghajtó nem működik rendesen a <quote>direkt memória "
"elérés</quote> (DMA) bekapcsolt volta esetén."

#. Tag: title
#: boot-installer.xml:3417
#, no-c-format
msgid "How to investigate and maybe solve issues"
msgstr "Hogyan vizsgálj ki és oldj meg gondokat"

#. Tag: para
#: boot-installer.xml:3418
#, no-c-format
msgid "If the CD-ROM fails to boot, try the suggestions listed below."
msgstr ""
"Ha a CD-ROM eszköz indítása sikertelen, próbáld ki az alább adott "
"javaslatokat."

#. Tag: para
#: boot-installer.xml:3423
#, no-c-format
msgid ""
"Check that your BIOS actually supports booting from CD-ROM (older systems "
"possibly don't) and that your CD-ROM drive supports the media you are using."
msgstr ""
"Ellenőrizd, hogy a BIOS támogatja a CD-ROM indítást (a régebbiek nem) és "
"hogy a CD-rom meghajtó támogatja a használt médiát."

#. Tag: para
#: boot-installer.xml:3429
#, no-c-format
msgid ""
"If you downloaded an iso image, check that the md5sum of that image matches "
"the one listed for the image in the <filename>MD5SUMS</filename> file that "
"should be present in the same location as where you downloaded the image "
"from. <informalexample><screen>\n"
"$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
"a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst."
"iso</replaceable>\n"
"</screen></informalexample> Next, check that the md5sum of the burned CD-ROM "
"matches as well. The following command should work. It uses the size of the "
"image to read the correct number of bytes from the CD-ROM."
msgstr ""
"Ha letöltöttél egy iso képet, ellenőrizd, hogy az md5sum egyezik az "
"<filename>MD5SUMS</filename> fájlban lévővel, mely ugyanott van, ahonnan "
"letöltötted. <informalexample><screen>\n"
"$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
"a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst."
"iso</replaceable>\n"
"</screen></informalexample> Ezután ellenőrizd, hogy a megírt CD-ROM is "
"egyezik. Az alábbi parancs kiváló. Használja a kép méretét helyes számú bájt "
"olvasására a CD-ROM lemezről."

#. Tag: screen
#: boot-installer.xml:3442
#, no-c-format
msgid ""
"$ dd if=/dev/cdrom | \\\n"
"> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</"
"replaceable>` | \\\n"
"> md5sum\n"
"a20391b12f7ff22ef705cee4059c6b92  -\n"
"262668+0 records in\n"
"262668+0 records out\n"
"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
msgstr ""
"$ dd if=/dev/cdrom | \\\n"
"> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</"
"replaceable>` | \\\n"
"> md5sum\n"
"a20391b12f7ff22ef705cee4059c6b92  -\n"
"262668+0 rekord beolvasva\n"
"262668+0 rekord kiírva\n"
"134486016 bájt (134 MB) másolva, 97.474 másodperc, 1.4 MB/s"

#. Tag: para
#: boot-installer.xml:3447
#, no-c-format
msgid ""
"If, after the installer has been booted successfully, the CD-ROM is not "
"detected, sometimes simply trying again may solve the problem. If you have "
"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If "
"that does not work or if the CD-ROM is recognized but there are errors when "
"reading from it, try the suggestions listed below. Some basic knowledge of "
"Linux is required for this. To execute any of the commands, you should first "
"switch to the second virtual console (VT2) and activate the shell there."
msgstr ""
"Ha a telepítő indulása után a CD-ROM érzékelése sikertelen, sokszor az "
"ismételt kísérlet sikerül. Ha egynél több CD-ROM meghajtód van, tedd a "
"lemezt a másikba. Ha ez sem válik be vagy a CD-ROM felismerésre kerül de "
"hibák történnek az olvasáskor, próbáld a lenti javaslatokat. Ehhez kis Linux-"
"ismeret kell. Parancsok használatához előbb válts a második virtuális "
"terminálra (VT2), melyen aktiváld a héjat."

#. Tag: para
#: boot-installer.xml:3459
#, no-c-format
msgid ""
"Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
"(use <command>nano</command> as editor) to check for any specific error "
"messages. After that, also check the output of <command>dmesg</command>."
msgstr ""
"Válts a VT4 terminálra vagy nézd meg a <filename>/var/log/syslog</filename> "
"tartalmát (használd a <command>nano</command>-t szerkesztőként) a hibák "
"ellenőrzéséhez. Ezután ellenőrizd a <command>dmesg</command> kimenetét is."

#. Tag: para
#: boot-installer.xml:3466
#, no-c-format
msgid ""
"Check in the output of <command>dmesg</command> if your CD-ROM drive was "
"recognized. You should see something like (the lines do not necessarily have "
"to be consecutive): <informalexample><screen>\n"
"Probing IDE interface ide1...\n"
"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n"
"ide1 at 0x170-0x177,0x376 on irq 15\n"
"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n"
"Uniform CD-ROM driver Revision: 3.20\n"
"</screen></informalexample> If you don't see something like that, chances "
"are the controller your CD-ROM is connected to was not recognized or may be "
"not supported at all. If you know what driver is needed for the controller, "
"you can try loading it manually using <command>modprobe</command>."
msgstr ""
"Ellenőrizd a <command>dmesg</command> kimenetét, sikerült-e a CD-ROM "
"meghajtó felismerése. Ilyesmit kell látnod benne (a sorok nem feltétlenül "
"egymás utániak): <informalexample><screen>\n"
"Probing IDE interface ide1...\n"
"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n"
"ide1 at 0x170-0x177,0x376 on irq 15\n"
"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n"
"Uniform CD-ROM driver Revision: 3.20\n"
"</screen></informalexample> Ha nincs ilyesmi, lehet, hogy a vezérlő "
"felismerése nem sikerült vagy egyáltalán nem támogatott. Ha tudod, milyen "
"meghajtót igényel az adott, kézzel is betöltheted a <command>modprobe</"
"command> paranccsal."

#. Tag: para
#: boot-installer.xml:3480
#, no-c-format
msgid ""
"Check that there is a device node for your CD-ROM drive under <filename>/dev/"
"</filename>. In the example above, this would be <filename>/dev/hdc</"
"filename>. There should also be a <filename>/dev/cdroms/cdrom0</filename>."
msgstr ""
"Ellenőrizd, van-e megfelelő eszköz-leíró fájl a CD-ROM meghajtóhoz a "
"<filename>/dev/</filename> könyvtárban. A fenti példában ez a <filename>/dev/"
"hdc</filename>. Lehet ez is: <filename>/dev/cdroms/cdrom0</filename>."

#. Tag: para
#: boot-installer.xml:3488
#, no-c-format
msgid ""
"Use the <command>mount</command> command to check if the CD-ROM is already "
"mounted; if not, try mounting it manually: <informalexample><screen>\n"
"$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
"</screen></informalexample> Check if there are any error messages after that "
"command."
msgstr ""
"Használd a <command>mount</command> parancsot a CD-ROM csatolt voltának "
"ellenőrzésére; ha nincs, próbáld kézzel csatolni: <informalexample><screen>\n"
"$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
"</screen></informalexample> Ellenőrizd, ír-e hibát."

#. Tag: para
#: boot-installer.xml:3498
#, no-c-format
msgid ""
"Check if DMA is currently enabled: <informalexample><screen>\n"
"$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
"$ grep using_dma settings\n"
"using_dma      1       0       1       rw\n"
"</screen></informalexample> A <quote>1</quote> in the first column after "
"<literal>using_dma</literal> means it is enabled. If it is, try disabling "
"it: <informalexample><screen>\n"
"$ echo -n \"using_dma:0\" >settings\n"
"</screen></informalexample> Make sure that you are in the directory for the "
"device that corresponds to your CD-ROM drive."
msgstr ""
"Ellenőrizd a DMA állapotát: <informalexample><screen>\n"
"$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
"$ grep dma settings\n"
"using_dma      1       0       1       rw\n"
"</screen></informalexample> Az <quote>1</quote> az 1. oszlopban a "
"<literal>using_dma</literal> után azt jelenti: bekapcsolva. Ha így van, "
"próbáld kikapcsolni: <informalexample><screen>\n"
"$ echo -n \"using_dma:0\" >settings\n"
"</screen></informalexample> Győződj meg, hogy a CD-ROM meghajtónak megfelelő "
"könyvtárban vagy."

#. Tag: para
#: boot-installer.xml:3513
#, no-c-format
msgid ""
"If there are any problems during the installation, try checking the "
"integrity of the CD-ROM using the option near the bottom of the installer's "
"main menu. This option can also be used as a general test if the CD-ROM can "
"be read reliably."
msgstr ""
"Ha gond támad a telepítés alatt, próbáld ki a CD-ROM épségének ellenőrzését "
"a telepítő fő-menü vége felé található lehetőséggel. E lehetőség a CD-ROM "
"eszközről való olvasás megbízhatóságának  általános ellenőrzésére is "
"használható."

#. Tag: title
#: boot-installer.xml:3528
#, no-c-format
msgid "Floppy Disk Reliability"
msgstr "Flopi lemezek megbízhatósága"

#. Tag: para
#: boot-installer.xml:3530
#, 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."

#. Tag: para
#: boot-installer.xml:3535
#, 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. Ez pedig általában nem olvassa olyan megbízhatóan, "
"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 üzenettel jelzik."

#. Tag: para
#: boot-installer.xml:3544
#, no-c-format
msgid ""
"If you are having the installation stall at a particular floppy, the first "
"thing you should do is write the image to a <emphasis>different</emphasis> "
"floppy and see if that solves the problem. Simply reformatting the old "
"floppy may not be sufficient, even if it appears that the floppy was "
"reformatted and written with no errors. It is sometimes useful to try "
"writing the floppy on a different system."
msgstr ""
"Ha a telepítés elakad egy flopinál, legelőször írd a képet egy "
"<emphasis>másik</emphasis> flopira, és nézd meg, ez megoldja-e a gondot. 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:3553
#, 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."

#. Tag: para
#: boot-installer.xml:3559
#, no-c-format
msgid ""
"Normally you should not have to download a floppy image again, but if you "
"are experiencing problems it is always useful to verify that the images were "
"downloaded correctly by verifying their md5sums."
msgstr ""
"Általában nem kell újra letöltened a flopi képet, de ha gondokat észlelsz, "
"mindig hasznos ellenőrizni a képek helyesen letöltött voltát md5-összegük "
"ellenőrzésével."

#. Tag: para
#: boot-installer.xml:3565
#, 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."

#. Tag: title
#: boot-installer.xml:3574
#, no-c-format
msgid "Boot Configuration"
msgstr "Indító beállítás"

#. Tag: para
#: boot-installer.xml:3576
#, no-c-format
msgid ""
"If you have problems and the kernel hangs during the boot process, doesn't "
"recognize peripherals you actually have, or drives are not recognized "
"properly, the first thing to check is the boot parameters, as discussed in "
"<xref linkend=\"boot-parms\"/>."
msgstr ""
"Ha a kernel megáll az indító folyamat során, nem ismer fel perifériákat vagy "
"meghajtókat helyesen, először az indító paramétereket kell ellenőrizni a "
"korábbi <xref linkend=\"boot-parms\"/> szerint."

#. Tag: para
#: boot-installer.xml:3583
#, no-c-format
msgid ""
"Often, problems can be solved by removing add-ons and peripherals, and then "
"trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and "
"Plug-n-Play devices can be especially problematic.</phrase>"
msgstr ""
"Bizonyos gondok gyakran megoldhatók kiegészítők és perifériák "
"eltávolításával és újraindítással. <phrase arch=\"x86\"> Egyes belső "
"modemek, hangkártyák és Plug-n-Play eszközök sok gondot adnak.</phrase>"

#. Tag: para
#: boot-installer.xml:3589
#, no-c-format
msgid ""
"If you have a large amount of memory installed in your machine, more than "
"512M, and the installer hangs when booting the kernel, you may need to "
"include a boot argument to limit the amount of memory the kernel sees, such "
"as <userinput>mem=512m</userinput>."
msgstr ""
"Ha több, mint 512M memória van a gépen és a telepítő megáll a kernel "
"indításakor, előfordulhat, hogy egy indító argumentumot kell megadni a "
"kernel által nézett memória korlátozására így: <userinput>mem=512m</"
"userinput>."

#. Tag: title
#: boot-installer.xml:3600 boot-installer.xml:3685
#, no-c-format
msgid "Common &arch-title; Installation Problems"
msgstr "Gyakori &arch-title; telepítő gondok"

#. Tag: para
#: boot-installer.xml:3601
#, no-c-format
msgid ""
"There are some common installation problems that can be solved or avoided by "
"passing certain boot parameters to the installer."
msgstr ""
"Van pár gyakori telepítő gond, mely megoldható vagy elkerülhető egyes indító "
"paraméterek átadásával a telepítőnek."

#. Tag: para
#: boot-installer.xml:3606
#, no-c-format
msgid ""
"Some systems have floppies with <quote>inverted DCLs</quote>. If you receive "
"errors reading from the floppy, even when you know the floppy is good, try "
"the parameter <userinput>floppy=thinkpad</userinput>."
msgstr ""
"Egyes rendszereken <quote>fordított DCL</quote> flopik vannak. Ha hibákat "
"kapsz a flopiról olvasáskor, pedig tudod, hogy a flopi jó, próbáld a  "
"<userinput>floppy=thinkpad</userinput> paramétert."

#. Tag: para
#: boot-installer.xml:3612
#, no-c-format
msgid ""
"On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk "
"drivers), the IDE drive may not be properly recognized. Again, try it first "
"without the parameters and see if the IDE drive is recognized properly. If "
"not, determine your drive geometry (cylinders, heads, and sectors), and use "
"the parameter <userinput>hd=<replaceable>cylinders</replaceable>,"
"<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></"
"userinput>."
msgstr ""
"Egyes rendszereken, ilyen például az IBM PS/1 vagy ValuePoint (melyben ST-"
"506 lemez meghajtók vannak), az IDE meghajtó felismerése hibás lehet. Előbb "
"paraméterek nélkül próbáld, és nézd meg, az IDE meghajtó felismerése helyes-"
"e. Ha nem, ellenőrizd a meghajtó geometriáját (cilinderek, fejek, szektorok) "
"és használd a <userinput>hd=<replaceable>cilinderek</replaceable>,"
"<replaceable>fejek</replaceable>,<replaceable>szektorok</replaceable></"
"userinput> paramétert."

#. Tag: para
#: boot-installer.xml:3621
#, no-c-format
msgid ""
"If you have a very old machine, and the kernel hangs after saying "
"<computeroutput>Checking 'hlt' instruction...</computeroutput>, then you "
"should try the <userinput>no-hlt</userinput> boot argument, which disables "
"this test."
msgstr ""
"Nagyon régi gépnél, ha a kernel megáll itt: <computeroutput>Checking 'hlt' "
"instruction...</computeroutput>, próbáld a <userinput>no-hlt</userinput> "
"indító argumentumot, mely kikapcsolja ezt a tesztet."

#. Tag: para
#: boot-installer.xml:3628
#, no-c-format
msgid ""
"If your screen begins to show a weird picture while the kernel boots, eg. "
"pure white, pure black or colored pixel garbage, your system may contain a "
"problematic video card which does not switch to the framebuffer mode "
"properly. Then you can use the boot parameter <userinput>fb=false "
"video=vga16:off</userinput> to disable the framebuffer console. Only a "
"reduced set of languages will be available during the installation due to "
"limited console features. See <xref linkend=\"boot-parms\"/> for details."
msgstr ""
"Ha a képernyő fura képet ad a kernel indításakor, például tiszta fehér, "
"tiszta fekete vagy színes kavar, a rendszer problematikus videó kártyát "
"tartalmazhat, mely hibásan vált framebuffer módra. Ekkor használható az "
"<userinput>fb=false video=vga16:off</userinput> indító paraméter ennek "
"kikapcsolására. Ekkor kevesebb nyelv érhető el a telepítés alatt a konzol "
"korlátozott képességei miatt. Lásd ezt: <xref linkend=\"boot-parms\"/> a "
"részletekért."

#. Tag: title
#: boot-installer.xml:3642
#, no-c-format
msgid "System Freeze During the PCMCIA Configuration Phase"
msgstr "A rendszer fagyása a PCMCIA beállító szakaszban"

#. Tag: para
#: boot-installer.xml:3643
#, no-c-format
msgid ""
"Some laptop models produced by Dell are known to crash when PCMCIA device "
"detection tries to access some hardware addresses. Other laptops may display "
"similar problems. If you experience such a problem and you don't need PCMCIA "
"support during the installation, you can disable PCMCIA using the "
"<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can "
"then configure PCMCIA after the installation is completed and exclude the "
"resource range causing the problems."
msgstr ""
"Egyes Dell laptopok összeomlanak, mikor a PCMCIA eszköz-érzékelő megpróbál "
"elérni egyes hardver-címeket. Pár más laptop is hasonló. Ha ilyen gondot "
"tapasztalsz és nincs szükséged PCMCIA támogatásra a telepítéskor, kapcsold "
"ki a <userinput>hw-detect/start_pcmcia=false</userinput> indító "
"paraméterrel. A telepítés után beállíthatod és kizárhatod a gondot adó "
"erőforrás-tartományokat."

#. Tag: para
#: boot-installer.xml:3653
#, no-c-format
msgid ""
"Alternatively, you can boot the installer in expert mode. You will then be "
"asked to enter the resource range options your hardware needs. For example, "
"if you have one of the Dell laptops mentioned above, you should enter "
"<userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list "
"of some common resource range options in the <ulink url=\"http://pcmcia-cs."
"sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource "
"settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the "
"commas, if any, when you enter this value in the installer."
msgstr ""
"A telepítő szakértő módban is indítható. Ekkor lehetőség nyílik a hardver "
"igényeinek megfelelő erőforrás-tartományok bevitelére. Például a fenti Dell "
"laptopokon megadható ez: <userinput>exclude port 0x800-0x8ff</userinput>. "
"Van egy lista is néhány általános erőforrás-tartomány lehetőségről itt: "
"<ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1."
"html#ss1.12\">PCMCIA HOGYAN rendszer erőforrás-beállítások szakasz</ulink>. "
"A vesszőket el kell hagyni, ha vannak, mikor beírod ezt az értéket a "
"telepítőben."

#. Tag: title
#: boot-installer.xml:3670
#, no-c-format
msgid "System Freeze while Loading USB Modules"
msgstr "A rendszer fagyása az USB modulok betöltésekor"

#. Tag: para
#: boot-installer.xml:3671
#, no-c-format
msgid ""
"The kernel normally tries to install USB modules and the USB keyboard driver "
"in order to support some non-standard USB keyboards. However, there are some "
"broken USB systems where the driver hangs on loading. A possible workaround "
"may be disabling the USB controller in your mainboard BIOS setup. Another "
"option is passing the <userinput>debian-installer/probe/usb=false</"
"userinput> parameter at the boot prompt, which will prevent the modules from "
"being loaded."
msgstr ""
"A kernel alapban megpróbálja telepíteni az USB modulokat és az USB billentyű "
"meghajtót pár nem-szabványos USB billentyű támogatásához. De van pár hibás "
"USB rendszer, ahol a meghajtó lefagy betöltéskor. Ennek egyik elkerülése az "
"USB vezérlő kikapcsolása a BIOS beállításban. Egy másik lehetőség a "
"<userinput>debian-installer/probe/usb=false</userinput> paraméter átadása az "
"indító jelnél, mely meggátolja e modulok betöltését."

#. Tag: para
#: boot-installer.xml:3686
#, no-c-format
msgid "There are some common installation problems that are worth mentioning."
msgstr "Van pár fel-felbukkanó telepítő gond, melyet érdemes megemlíteni."

#. Tag: title
#: boot-installer.xml:3692
#, no-c-format
msgid "Misdirected video output"
msgstr ""

#. Tag: para
#: boot-installer.xml:3693
#, no-c-format
msgid ""
"It is fairly common for &arch-title; to have two video cards in one machine, "
"for example an ATI card and a Sun Creator 3D. In some cases, this may result "
"in the video output getting misdirected soon after the system boots. In "
"typical cases, the display will only show: <informalexample><screen>\n"
"Remapping the kernel... done\n"
"Booting Linux...\n"
"</screen></informalexample> To work around this, you can either pull out one "
"of the video cards, or disable the one not used during the OpenProm boot "
"phase using a kernel parameter. For example, to disable an ATI card, you "
"should boot the installer with <userinput>video=atyfb:off</userinput>."
msgstr ""

#. Tag: para
#: boot-installer.xml:3707
#, no-c-format
msgid ""
"Note that you may also have to manually add this parameter to the silo "
"configuration (edit <filename>/target/etc/silo.conf</filename> before "
"rebooting) and, if you installed X11, modify the video driver in <filename>/"
"etc/X11/xorg.conf</filename>."
msgstr ""
"Add e paramétert a silo beállításhoz (szerkeszd a <filename>/target/etc/silo."
"conf</filename> fájlt újraindítás előtt) és X11 esetén módosítsd a videó "
"meghajtót a <filename>/etc/X11/xorg.conf</filename> fájlban."

#. Tag: title
#: boot-installer.xml:3718
#, no-c-format
msgid "Failure to Boot or Install from CD-ROM"
msgstr "Hibás indítás vagy telepítés CD-ROM lemezről"

#. Tag: para
#: boot-installer.xml:3719
#, no-c-format
msgid ""
"Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
"they do boot, there may be inexplicable failures during the installation. "
"Most problems have been reported with SunBlade systems."
msgstr ""
"Bizonyos Sparc rendszerekkel állandó CD-ROM indítás gondok vannak, és ha "
"indulnak is, hibákat adnak a telepítéskor. A legtöbb gond a SunBlade "
"rendszereknél fordult elő."

#. Tag: para
#: boot-installer.xml:3725
#, no-c-format
msgid "We recommend to install such systems by netbooting the installer."
msgstr "Az ilyen rendszerekhez hálózati telepítést ajánlunk."

#. Tag: title
#: boot-installer.xml:3734
#, no-c-format
msgid "Interpreting the Kernel Startup Messages"
msgstr "A kernel indító üzenetek értelmezése"

#. Tag: para
#: boot-installer.xml:3736
#, no-c-format
msgid ""
"During the boot sequence, you may see many messages in the form "
"<computeroutput>can't find <replaceable>something</replaceable></"
"computeroutput>, or <computeroutput><replaceable>something</replaceable> not "
"present</computeroutput>, <computeroutput>can't initialize "
"<replaceable>something</replaceable></computeroutput>, or even "
"<computeroutput>this driver release depends on <replaceable>something</"
"replaceable></computeroutput>. Most of these messages are harmless. You see "
"them because the kernel for the installation system is built to run on "
"computers with many different peripheral devices. Obviously, no one computer "
"will have every possible peripheral device, so the operating system may emit "
"a few complaints while it looks for peripherals you don't own. You may also "
"see the system pause for a while. This happens when it is waiting for a "
"device to respond, and that device is not present on your system. If you "
"find the time it takes to boot the system unacceptably long, you can create "
"a custom kernel later (see <xref linkend=\"kernel-baking\"/>)."
msgstr ""
"Az indítás alatt, sok ilyen üzenetet láthatsz: <computeroutput>can't find "
"<replaceable>valami</replaceable></computeroutput>, vagy <computeroutput> "
"<replaceable>valami</replaceable> not present</computeroutput>, "
"<computeroutput>can't initialize <replaceable>valami</replaceable></"
"computeroutput>, vagy akár <computeroutput>this driver release depends on "
"<replaceable>valami</replaceable></computeroutput>. A legtöbb ilyen nem "
"számít. Azért látod, mert a telepítőben lévő kernel úgy készült, hogy a "
"legkülönbözőbb eszközöket támogassa.  Persze egy gépen sincs az összes "
"lehetséges eszköz, és az operációs rendszer jelezheti, ha olyat keres, ami "
"nem található. Néha azt is láthatod, hogy a rendszer egy picit megáll. Ez "
"akkor történik, ha vár egy eszköz válaszára, az adott rendszer pedig nem "
"tartalmaz olyat. Ha ezt túl hosszúnak találod, később egyéni kernelt is "
"készíthetsz (lásd a <xref linkend=\"kernel-baking\"/> részt)."

#. Tag: title
#: boot-installer.xml:3761
#, no-c-format
msgid "Reporting Installation Problems"
msgstr "Telepítő gondok jelentése"

#. Tag: para
#: boot-installer.xml:3762
#, no-c-format
msgid ""
"If you get through the initial boot phase but cannot complete the install, "
"the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. "
"It lets you store system error logs and configuration information from the "
"installer to a floppy, or download them using a web browser. This "
"information may provide clues as to what went wrong and how to fix it. If "
"you are submitting a bug report, you may want to attach this information to "
"the bug report."
msgstr ""
"Ha túljutottál a kezdő indító szakaszon, de nem futott le teljesen végig a "
"telepítés, a <guimenuitem>Hibanaplók mentése</guimenuitem> menüpont "
"segíthet. Eltárolhatod a rendszer hiba naplóit és beállításait a telepítőből "
"egy flopira, vagy letöltheted egy böngészőben. Ezek megadják a felmerült "
"hibákat és javításukat. Ha jelentést küldesz, csatolhatod hozzá ezeket."

#. Tag: para
#: boot-installer.xml:3773
#, no-c-format
msgid ""
"Other pertinent installation messages may be found in <filename>/var/log/</"
"filename> during the installation, and <filename>/var/log/installer/</"
"filename> after the computer has been booted into the installed system."
msgstr ""
"További telepítő üzenetek találhatók a <filename>/var/log/</filename> "
"könyvtárban a telepítés során és a <filename>/var/log/installer/</filename> "
"könyvtárban, miután a gép a telepített rendszert elindította."

#. Tag: title
#: boot-installer.xml:3784
#, no-c-format
msgid "Submitting Installation Reports"
msgstr "Telepítő jelentések küldése"

#. Tag: para
#: boot-installer.xml:3785
#, 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 is 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:3792
#, no-c-format
msgid ""
"Note that your installation report will be published in the Debian Bug "
"Tracking System (BTS) and forwarded to a public mailing list. Make sure that "
"you use an e-mail address that you do not mind being made public."
msgstr ""
"A telepítő jelentés közzé kerül a Debian hibajelentő rendszerben (BTS) és "
"nyilvános listára kerül. Gondold át, melyik email címedet használod."

#. Tag: para
#: boot-installer.xml:3798
#, no-c-format
msgid ""
"If you have a working Debian system, the easiest way to send an installation "
"report is to install the <classname>installation-report</classname> and "
"<classname>reportbug</classname> packages (<command>aptitude install "
"installation-report reportbug</command>), configure <classname>reportbug</"
"classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the "
"command <command>reportbug installation-reports</command>."
msgstr ""
"Működő Debian rendszerből a telepítő jelentés küldésének legkönnyebb módja "
"az <classname>installation-report</classname> és <classname>reportbug</"
"classname> csomag telepítése (<command>aptitude install installation-report "
"reportbug</command>), állítsd be a <classname>reportbug</classname> csomagot "
"a <xref linkend=\"mail-outgoing\"/> résznek megfelelően és futtasd a "
"<command>reportbug installation-reports</command> parancsot."

#. Tag: para
#: boot-installer.xml:3808
#, no-c-format
msgid ""
"Alternatively you can use this template when filling out installation "
"reports, and file the report as a bug report against the "
"<classname>installation-reports</classname> pseudo package, by sending it to "
"<email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
"Package: installation-reports\n"
"\n"
"Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;\n"
"Image version: &lt;Full URL to image you downloaded is best&gt;\n"
"Date: &lt;Date and time of the install&gt;\n"
"\n"
"Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n"
"Processor:\n"
"Memory:\n"
"Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;\n"
"\n"
"Output of lspci -nn and lspci -vnn:\n"
"\n"
"Base System Installation Checklist:\n"
"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n"
"\n"
"Initial boot:           [ ]\n"
"Detect network card:    [ ]\n"
"Configure network:      [ ]\n"
"Detect CD:              [ ]\n"
"Load installer modules: [ ]\n"
"Detect hard drives:     [ ]\n"
"Partition hard drives:  [ ]\n"
"Install base system:    [ ]\n"
"Clock/timezone setup:   [ ]\n"
"User/password setup:    [ ]\n"
"Install tasks:          [ ]\n"
"Install boot loader:    [ ]\n"
"Overall install:        [ ]\n"
"\n"
"Comments/Problems:\n"
"\n"
"&lt;Description of the install, in prose, and any thoughts, comments\n"
"      and ideas you had during the initial install.&gt;\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 ""
"Vagy pedig használhatod e sablont a telepítő jelentés kitöltésére és "
"elküldésére hibajegyként az <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: &lt;Mi volt az indító médium? CD? flopi? hálózat?&gt;\n"
"Image version: &lt;A letöltött kép teljes URL-e a legjobb&gt;\n"
"Date: &lt;Telepítés időpontja&gt;\n"
"\n"
"Machine: &lt;Gép leírása (például IBM Thinkpad R32)&gt;\n"
"Processor:\n"
"Memory:\n"
"Partitions: &lt;a df -Tl kiírja; a sima partíciós tábla ajánlott&gt;\n"
"\n"
"Az lspci -nn és lspci -vnn kimenete:\n"
"\n"
"Az alaprendszer telepítésekor:\n"
"[O] = OK, [E] = Hiba (a végén írd le), [ ] = nem próbált\n"
"\n"
"Initial boot:    [ ]\n"
"Detect network card:    [ ]\n"
"Configure network:   [ ]\n"
"Detect CD:              [ ]\n"
"Load installer modules: [ ]\n"
"Detect hard drives:     [ ]\n"
"Partition hard drives:  [ ]\n"
"Install base system:    [ ]\n"
"Clock/timezone setup:   [ ]\n"
"User/password setup:    [ ]\n"
"Install tasks:          [ ]\n"
"Install boot loader:    [ ]\n"
"Overall install:        [ ]\n"
"\n"
"Comments/Problems:\n"
"\n"
"&lt;Telepítés leírása prózaian és bármilyen gondolat, megjegyzés\n"
"      és ötlet a kezdeti telepítés során.&gt;\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."

#~ msgid ""
#~ "Type <informalexample><screen>\n"
#~ "&gt;&gt;&gt; boot xxxx -flags 0\n"
#~ "</screen></informalexample> where <replaceable>xxxx</replaceable> is your "
#~ "CD-ROM drive in SRM notation."
#~ msgstr ""
#~ "Írd be ezt: <informalexample><screen>\n"
#~ "&gt;&gt;&gt; boot xxxx -flags 0\n"
#~ "</screen></informalexample> ahol az <replaceable>xxxx</replaceable> a CD-"
#~ "ROM meghajtó SRM szerint."

#~ msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;."
#~ msgstr "2.2.x kernel esetén a &ramdisksize; beállítandó."

#~ msgid ""
#~ "If you are booting with your own kernel instead of the one supplied with "
#~ "the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in "
#~ "your kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>."
#~ msgstr ""
#~ "Ha a telepítő által adott helyett saját kernelt indítasz, fontos, hogy a "
#~ "<userinput>CONFIG_DEVFS</userinput> be legyen állítva a kernelben. A "
#~ "telepítő a <userinput>CONFIG_DEVFS</userinput> meglétét igényli."

#~ msgid "Bug Reporter"
#~ msgstr "Hibajelentő"