diff options
Diffstat (limited to 'po/hu')
-rw-r--r-- | po/hu/boot-new.po | 283 | ||||
-rw-r--r-- | po/hu/hardware.po | 1356 | ||||
-rw-r--r-- | po/hu/post-install.po | 672 |
3 files changed, 1799 insertions, 512 deletions
diff --git a/po/hu/boot-new.po b/po/hu/boot-new.po index a7d412315..e200f8a46 100644 --- a/po/hu/boot-new.po +++ b/po/hu/boot-new.po @@ -1,12 +1,13 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: \n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2006-08-05 12:45+0000\n" "PO-Revision-Date: 2006-08-20 12:15+0100\n" "Last-Translator: SZERVÁC Attila <sas@321.hu>\n" "Language-Team: hu\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Poedit-Language: Hungarian\n" @@ -27,14 +28,34 @@ msgstr "Az igazság pillanata" #. Tag: para #: boot-new.xml:8 #, no-c-format -msgid "Your system's first boot on its own power is what electrical engineers call the <quote>smoke test</quote>." -msgstr "A rendszer 1. önálló indítása olyasmi, amit a mérnökök úgy hívnak: <quote>tűzpróba</quote>." +msgid "" +"Your system's first boot on its own power is what electrical engineers call " +"the <quote>smoke test</quote>." +msgstr "" +"A rendszer 1. önálló indítása olyasmi, amit a mérnökök úgy hívnak: " +"<quote>tűzpróba</quote>." #. Tag: para #: boot-new.xml:13 #, no-c-format -msgid "If you are booting directly into Debian, and the system doesn't start up, either use your original installation boot media, or insert the custom boot floppy if you have one, and reset your system. This way, you will probably need to add some boot arguments like <userinput>root=<replaceable>root</replaceable></userinput>, where <replaceable>root</replaceable> is your root partition, such as <filename>/dev/sda1</filename>. Alternatively, see <xref linkend=\"rescue\"/> for instructions on using the installer's built-in rescue mode." -msgstr "Ha kiválasztottad a Debian indítását, és a rendszer mégsem indul, használhatod a telepítő médiát vagy flopit. Ekkor valószínűleg meg kell adnod 1-2 indítási argumentumot, leginkább egy ilyet: <userinput>root=<replaceable>gyökér</replaceable></userinput>, where <replaceable>gyökér</replaceable> a telepített rendszer gyökér-partíciója, például <filename>/dev/sda1</filename>. Módfelett ajánljuk, olvasd el a <xref linkend=\"rescue\"/> részt a telepítő beépített mentő módja lehetőségeinek ismertetéséért." +msgid "" +"If you are booting directly into Debian, and the system doesn't start up, " +"either use your original installation boot media, or insert the custom boot " +"floppy if you have one, and reset your system. This way, you will probably " +"need to add some boot arguments like <userinput>root=<replaceable>root</" +"replaceable></userinput>, where <replaceable>root</replaceable> is your root " +"partition, such as <filename>/dev/sda1</filename>. Alternatively, see <xref " +"linkend=\"rescue\"/> for instructions on using the installer's built-in " +"rescue mode." +msgstr "" +"Ha kiválasztottad a Debian indítását, és a rendszer mégsem indul, " +"használhatod a telepítő médiát vagy flopit. Ekkor valószínűleg meg kell " +"adnod 1-2 indítási argumentumot, leginkább egy ilyet: " +"<userinput>root=<replaceable>gyökér</replaceable></userinput>, where " +"<replaceable>gyökér</replaceable> a telepített rendszer gyökér-partíciója, " +"például <filename>/dev/sda1</filename>. Módfelett ajánljuk, olvasd el a " +"<xref linkend=\"rescue\"/> részt a telepítő beépített mentő módja " +"lehetőségeinek ismertetéséért." #. Tag: title #: boot-new.xml:27 @@ -45,13 +66,18 @@ msgstr "" #. Tag: para #: boot-new.xml:28 #, no-c-format -msgid "If you have just performed a diskless install on a BVM or Motorola VMEbus machine: once the system has loaded the <command>tftplilo</command> program from the TFTP server, from the <prompt>LILO Boot:</prompt> prompt enter one of:" +msgid "" +"If you have just performed a diskless install on a BVM or Motorola VMEbus " +"machine: once the system has loaded the <command>tftplilo</command> program " +"from the TFTP server, from the <prompt>LILO Boot:</prompt> prompt enter one " +"of:" msgstr "" #. Tag: para #: boot-new.xml:36 #, no-c-format -msgid "<userinput>b6000</userinput> followed by &enterkey; to boot a BVME 4000/6000" +msgid "" +"<userinput>b6000</userinput> followed by &enterkey; to boot a BVME 4000/6000" msgstr "" #. Tag: para @@ -63,7 +89,8 @@ msgstr "" #. Tag: para #: boot-new.xml:46 #, no-c-format -msgid "<userinput>b167</userinput> followed by &enterkey; to boot an MVME166/167" +msgid "" +"<userinput>b167</userinput> followed by &enterkey; to boot an MVME166/167" msgstr "" #. Tag: title @@ -75,31 +102,54 @@ msgstr "" #. Tag: para #: boot-new.xml:60 #, no-c-format -msgid "Go to the directory containing the installation files and start up the <command>Penguin</command> booter, holding down the <keycap>command</keycap> key. Go to the <userinput>Settings</userinput> dialogue (<keycombo> <keycap>command</keycap> <keycap>T</keycap> </keycombo>), and locate the kernel options line which should look like <userinput>root=/dev/ram video=font:VGA8x16</userinput> or similar." +msgid "" +"Go to the directory containing the installation files and start up the " +"<command>Penguin</command> booter, holding down the <keycap>command</keycap> " +"key. Go to the <userinput>Settings</userinput> dialogue (<keycombo> " +"<keycap>command</keycap> <keycap>T</keycap> </keycombo>), and locate the " +"kernel options line which should look like <userinput>root=/dev/ram " +"video=font:VGA8x16</userinput> or similar." msgstr "" #. Tag: para #: boot-new.xml:70 #, no-c-format -msgid "You need to change the entry to <userinput>root=/dev/<replaceable>yyyy</replaceable></userinput>. Replace the <replaceable>yyyy</replaceable> with the Linux name of the partition onto which you installed the system (e.g. <filename>/dev/sda1</filename>); you wrote this down earlier. The <userinput>video=font:VGA8x8</userinput> is recommended especially for users with tiny screens. The kernel would pick a prettier (6x11) font but the console driver for this font can hang the machine, so using 8x16 or 8x8 is safer at this stage. You can change this at any time." +msgid "" +"You need to change the entry to <userinput>root=/dev/<replaceable>yyyy</" +"replaceable></userinput>. Replace the <replaceable>yyyy</replaceable> with " +"the Linux name of the partition onto which you installed the system (e.g. " +"<filename>/dev/sda1</filename>); you wrote this down earlier. The " +"<userinput>video=font:VGA8x8</userinput> is recommended especially for users " +"with tiny screens. The kernel would pick a prettier (6x11) font but the " +"console driver for this font can hang the machine, so using 8x16 or 8x8 is " +"safer at this stage. You can change this at any time." msgstr "" #. Tag: para #: boot-new.xml:83 #, no-c-format -msgid "If you don't want to start GNU/Linux immediately each time you start, uncheck the <userinput>Auto Boot</userinput> option. Save your settings in the <filename>Prefs</filename> file using the <userinput>Save Settings As Default</userinput> option." +msgid "" +"If you don't want to start GNU/Linux immediately each time you start, " +"uncheck the <userinput>Auto Boot</userinput> option. Save your settings in " +"the <filename>Prefs</filename> file using the <userinput>Save Settings As " +"Default</userinput> option." msgstr "" #. Tag: para #: boot-new.xml:90 #, no-c-format -msgid "Now select <userinput>Boot Now</userinput> (<keycombo> <keycap>command</keycap> <keycap>B</keycap> </keycombo>) to start your freshly installed GNU/Linux instead of the RAMdisk installer system." +msgid "" +"Now select <userinput>Boot Now</userinput> (<keycombo> <keycap>command</" +"keycap> <keycap>B</keycap> </keycombo>) to start your freshly installed GNU/" +"Linux instead of the RAMdisk installer system." msgstr "" #. Tag: para #: boot-new.xml:96 #, no-c-format -msgid "Debian should boot, and you should see the same messages as when you first booted the installation system, followed by some new messages." +msgid "" +"Debian should boot, and you should see the same messages as when you first " +"booted the installation system, followed by some new messages." msgstr "" #. Tag: title @@ -111,19 +161,42 @@ msgstr "" #. Tag: para #: boot-new.xml:107 #, no-c-format -msgid "If the machine fails to boot after completing the installation, and stops with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</userinput> followed by &enterkey;. (The default boot configuration in <filename>quik.conf</filename> is labeled Linux). The labels defined in <filename>quik.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also try booting back into the installer, and editing the <filename>/target/etc/quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>." +msgid "" +"If the machine fails to boot after completing the installation, and stops " +"with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</" +"userinput> followed by &enterkey;. (The default boot configuration in " +"<filename>quik.conf</filename> is labeled Linux). The labels defined in " +"<filename>quik.conf</filename> will be displayed if you press the " +"<keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also " +"try booting back into the installer, and editing the <filename>/target/etc/" +"quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard " +"Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are " +"available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>." msgstr "" #. Tag: para #: boot-new.xml:121 #, no-c-format -msgid "To boot back into MacOS without resetting the nvram, type <userinput>bye</userinput> at the OpenFirmware prompt (assuming MacOS has not been removed from the machine). To obtain an OpenFirmware prompt, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. If you need to reset the OpenFirmware nvram changes to the MacOS default in order to boot back to MacOS, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine." +msgid "" +"To boot back into MacOS without resetting the nvram, type <userinput>bye</" +"userinput> at the OpenFirmware prompt (assuming MacOS has not been removed " +"from the machine). To obtain an OpenFirmware prompt, hold down the " +"<keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</" +"keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. " +"If you need to reset the OpenFirmware nvram changes to the MacOS default in " +"order to boot back to MacOS, hold down the <keycombo> <keycap>command</" +"keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </" +"keycombo> keys while cold booting the machine." msgstr "" #. Tag: para #: boot-new.xml:134 #, no-c-format -msgid "If you use <command>BootX</command> to boot into the installed system, just select your desired kernel in the <filename>Linux Kernels</filename> folder, un-choose the ramdisk option, and add a root device corresponding to your installation; e.g. <userinput>/dev/hda8</userinput>." +msgid "" +"If you use <command>BootX</command> to boot into the installed system, just " +"select your desired kernel in the <filename>Linux Kernels</filename> folder, " +"un-choose the ramdisk option, and add a root device corresponding to your " +"installation; e.g. <userinput>/dev/hda8</userinput>." msgstr "" #. Tag: title @@ -135,31 +208,52 @@ msgstr "" #. Tag: para #: boot-new.xml:147 #, no-c-format -msgid "On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key and get a graphical screen with a button for each bootable OS, &debian; will be a button with a small penguin icon." +msgid "" +"On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key " +"and get a graphical screen with a button for each bootable OS, &debian; will " +"be a button with a small penguin icon." msgstr "" #. Tag: para #: boot-new.xml:154 #, no-c-format -msgid "If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-device</envar> variable you should reset OpenFirmware to its default configuration. To do this hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine." +msgid "" +"If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-" +"device</envar> variable you should reset OpenFirmware to its default " +"configuration. To do this hold down the <keycombo> <keycap>command</keycap> " +"<keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> " +"keys while cold booting the machine." msgstr "" #. Tag: para #: boot-new.xml:162 #, no-c-format -msgid "The labels defined in <filename>yaboot.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt." +msgid "" +"The labels defined in <filename>yaboot.conf</filename> will be displayed if " +"you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt." msgstr "" #. Tag: para #: boot-new.xml:168 #, no-c-format -msgid "Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian; by default (if you correctly partitioned and placed the Apple_Bootstrap partition first). If you have &debian; on a SCSI disk and MacOS on an IDE disk this may not work and you will have to enter OpenFirmware and set the <envar>boot-device</envar> variable, <command>ybin</command> normally does this automatically." +msgid "" +"Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian; " +"by default (if you correctly partitioned and placed the Apple_Bootstrap " +"partition first). If you have &debian; on a SCSI disk and MacOS on an IDE " +"disk this may not work and you will have to enter OpenFirmware and set the " +"<envar>boot-device</envar> variable, <command>ybin</command> normally does " +"this automatically." msgstr "" #. Tag: para #: boot-new.xml:177 #, no-c-format -msgid "After you boot &debian; for the first time you can add any additional options you desire (such as dual boot options) to <filename>/etc/yaboot.conf</filename> and run <command>ybin</command> to update your boot partition with the changed configuration. Please read the <ulink url=\"&url-powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information." +msgid "" +"After you boot &debian; for the first time you can add any additional " +"options you desire (such as dual boot options) to <filename>/etc/yaboot." +"conf</filename> and run <command>ybin</command> to update your boot " +"partition with the changed configuration. Please read the <ulink url=\"&url-" +"powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information." msgstr "" #. Tag: title @@ -171,7 +265,11 @@ msgstr "" #. Tag: para #: boot-new.xml:193 #, no-c-format -msgid "If you created encrypted volumes during the installation and assigned them mount points, you will be asked to enter the passphrase for each of these volumes during the boot. The actual procedure differs slightly between dm-crypt and loop-AES." +msgid "" +"If you created encrypted volumes during the installation and assigned them " +"mount points, you will be asked to enter the passphrase for each of these " +"volumes during the boot. The actual procedure differs slightly between dm-" +"crypt and loop-AES." msgstr "" #. Tag: title @@ -184,16 +282,32 @@ msgstr "" #: boot-new.xml:205 #, no-c-format msgid "" -"For partitions encrypted using dm-crypt you will be shown the following prompt during the boot: <informalexample><screen>\n" +"For partitions encrypted using dm-crypt you will be shown the following " +"prompt during the boot: <informalexample><screen>\n" "Starting early crypto disks... crypt<replaceable>X</replaceable>(starting)\n" "Enter LUKS passphrase:\n" -"</screen></informalexample> In the first line of the prompt, <replaceable>X</replaceable> is the number of the loop device. You are now probably wondering <emphasis>for which volume</emphasis> you are actually entering the passphrase. Does it relate to your <filename>/home</filename>? Or to <filename>/var</filename>? Of course, if you have just one encrypted volume, this is easy and you can just enter the passphrase you used when setting up this volume. If you set up more than one encrypted volume during the installation, the notes you wrote down as the last step in <xref linkend=\"partman-crypto\"/> come in handy. If you did not make a note of the mapping between <filename>crypt<replaceable>X</replaceable></filename> and the mount points before, you can still find it in <filename>/etc/crypttab</filename> and <filename>/etc/fstab</filename> of your new system." +"</screen></informalexample> In the first line of the prompt, <replaceable>X</" +"replaceable> is the number of the loop device. You are now probably " +"wondering <emphasis>for which volume</emphasis> you are actually entering " +"the passphrase. Does it relate to your <filename>/home</filename>? Or to " +"<filename>/var</filename>? Of course, if you have just one encrypted volume, " +"this is easy and you can just enter the passphrase you used when setting up " +"this volume. If you set up more than one encrypted volume during the " +"installation, the notes you wrote down as the last step in <xref linkend=" +"\"partman-crypto\"/> come in handy. If you did not make a note of the " +"mapping between <filename>crypt<replaceable>X</replaceable></filename> and " +"the mount points before, you can still find it in <filename>/etc/crypttab</" +"filename> and <filename>/etc/fstab</filename> of your new system." msgstr "" #. Tag: para #: boot-new.xml:227 #, no-c-format -msgid "The prompt may look somewhat different when an encrypted root file system is mounted. This depends on which initramfs generator was used to generate the initrd used to boot the system. The example below is for an initrd generated using <classname>initramfs-tools</classname>:" +msgid "" +"The prompt may look somewhat different when an encrypted root file system is " +"mounted. This depends on which initramfs generator was used to generate the " +"initrd used to boot the system. The example below is for an initrd generated " +"using <classname>initramfs-tools</classname>:" msgstr "" #. Tag: screen @@ -206,15 +320,18 @@ msgid "" msgstr "" #. Tag: para -#: boot-new.xml:236 -#: boot-new.xml:261 +#: boot-new.xml:236 boot-new.xml:261 #, no-c-format -msgid "No characters (even asterisks) will be shown while entering the passphrase. If you enter the wrong passphrase, you have two more tries to correct it. After the third try the boot process will skip this volume and continue to mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting\"/> for further information." +msgid "" +"No characters (even asterisks) will be shown while entering the passphrase. " +"If you enter the wrong passphrase, you have two more tries to correct it. " +"After the third try the boot process will skip this volume and continue to " +"mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting" +"\"/> for further information." msgstr "" #. Tag: para -#: boot-new.xml:244 -#: boot-new.xml:269 +#: boot-new.xml:244 boot-new.xml:269 #, no-c-format msgid "After entering all passphrases the boot should continue as usual." msgstr "" @@ -228,7 +345,9 @@ msgstr "" #. Tag: para #: boot-new.xml:254 #, no-c-format -msgid "For partitions encrypted using loop-AES you will be shown the following prompt during the boot:" +msgid "" +"For partitions encrypted using loop-AES you will be shown the following " +"prompt during the boot:" msgstr "" #. Tag: screen @@ -236,7 +355,8 @@ msgstr "" #, no-c-format msgid "" "Checking loop-encrypted file systems.\n" -"Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</replaceable>)\n" +"Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</" +"replaceable>)\n" "Password:" msgstr "" @@ -249,47 +369,77 @@ msgstr "" #. Tag: para #: boot-new.xml:279 #, no-c-format -msgid "If some of the encrypted volumes could not be mounted because a wrong passphrase was entered, you will have to mount them manually after the boot. There are several cases." +msgid "" +"If some of the encrypted volumes could not be mounted because a wrong " +"passphrase was entered, you will have to mount them manually after the boot. " +"There are several cases." msgstr "" #. Tag: para #: boot-new.xml:288 #, no-c-format -msgid "The first case concerns the root partition. When it is not mounted correctly, the boot process will halt and you will have to reboot the computer to try again." +msgid "" +"The first case concerns the root partition. When it is not mounted " +"correctly, the boot process will halt and you will have to reboot the " +"computer to try again." msgstr "" #. Tag: para #: boot-new.xml:295 #, no-c-format msgid "" -"The easiest case is for encrypted volumes holding data like <filename>/home</filename> or <filename>/srv</filename>. You can simply mount them manually after the boot. For loop-AES this is one-step operation: <informalexample><screen>\n" -"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>\n" +"The easiest case is for encrypted volumes holding data like <filename>/home</" +"filename> or <filename>/srv</filename>. You can simply mount them manually " +"after the boot. For loop-AES this is one-step operation: " +"<informalexample><screen>\n" +"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></" +"userinput>\n" "<prompt>Password:</prompt>\n" -"</screen></informalexample> where <replaceable>/mount_point</replaceable> should be replaced by the particular directory (e.g. <filename>/home</filename>). The only difference from an ordinary mount is that you will be asked to enter the passphrase for this volume." +"</screen></informalexample> where <replaceable>/mount_point</replaceable> " +"should be replaced by the particular directory (e.g. <filename>/home</" +"filename>). The only difference from an ordinary mount is that you will be " +"asked to enter the passphrase for this volume." msgstr "" #. Tag: para #: boot-new.xml:309 #, no-c-format msgid "" -"For dm-crypt this is a bit trickier. First you need to register the volumes with <application>device mapper</application> by running: <informalexample><screen>\n" +"For dm-crypt this is a bit trickier. First you need to register the volumes " +"with <application>device mapper</application> by running: " +"<informalexample><screen>\n" "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n" -"</screen></informalexample> This will scan all volumes mentioned in <filename>/etc/crypttab</filename> and will create appropriate devices under the <filename>/dev</filename> directory after entering the correct passphrases. (Already registered volumes will be skipped, so you can repeat this command several times without worrying.) After successful registration you can simply mount the volumes the usual way:" +"</screen></informalexample> This will scan all volumes mentioned in " +"<filename>/etc/crypttab</filename> and will create appropriate devices under " +"the <filename>/dev</filename> directory after entering the correct " +"passphrases. (Already registered volumes will be skipped, so you can repeat " +"this command several times without worrying.) After successful registration " +"you can simply mount the volumes the usual way:" msgstr "" #. Tag: screen #: boot-new.xml:324 #, no-c-format -msgid "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>" +msgid "" +"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></" +"userinput>" msgstr "" #. Tag: para #: boot-new.xml:327 #, no-c-format msgid "" -"If any volume holding noncritical system files could not be mounted (<filename>/usr</filename> or <filename>/var</filename>), the system should still boot and you should be able to mount the volumes manually like in the previous case. However, you will also need to (re)start any services usually running in your default runlevel because it is very likely that they were not started. The easiest way to achieve this is by switching to the first runlevel and back by entering <informalexample><screen>\n" +"If any volume holding noncritical system files could not be mounted " +"(<filename>/usr</filename> or <filename>/var</filename>), the system should " +"still boot and you should be able to mount the volumes manually like in the " +"previous case. However, you will also need to (re)start any services usually " +"running in your default runlevel because it is very likely that they were " +"not started. The easiest way to achieve this is by switching to the first " +"runlevel and back by entering <informalexample><screen>\n" "<prompt>#</prompt> <userinput>init 1</userinput>\n" -"</screen></informalexample> at the shell prompt and pressing <keycombo> <keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the root password." +"</screen></informalexample> at the shell prompt and pressing <keycombo> " +"<keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the " +"root password." msgstr "" #. Tag: title @@ -301,42 +451,73 @@ msgstr "" #. Tag: para #: boot-new.xml:352 #, no-c-format -msgid "Once your system boots, you'll be presented with the login prompt. Log in using the personal login and password you selected during the installation process. Your system is now ready to use." +msgid "" +"Once your system boots, you'll be presented with the login prompt. Log in " +"using the personal login and password you selected during the installation " +"process. Your system is now ready to use." msgstr "" #. Tag: para #: boot-new.xml:358 #, no-c-format -msgid "If you are a new user, you may want to explore the documentation which is already installed on your system as you start to use it. There are currently several documentation systems, work is proceeding on integrating the different types of documentation. Here are a few starting points." +msgid "" +"If you are a new user, you may want to explore the documentation which is " +"already installed on your system as you start to use it. There are currently " +"several documentation systems, work is proceeding on integrating the " +"different types of documentation. Here are a few starting points." msgstr "" #. Tag: para #: boot-new.xml:366 #, no-c-format -msgid "Documentation accompanying programs you have installed is in <filename>/usr/share/doc/</filename>, under a subdirectory named after the program. For example, the APT User's Guide for using <command>apt</command> to install other programs on your system, is located in <filename>/usr/share/doc/apt/guide.html/index.html</filename>." +msgid "" +"Documentation accompanying programs you have installed is in <filename>/usr/" +"share/doc/</filename>, under a subdirectory named after the program. For " +"example, the APT User's Guide for using <command>apt</command> to install " +"other programs on your system, is located in <filename>/usr/share/doc/apt/" +"guide.html/index.html</filename>." msgstr "" #. Tag: para #: boot-new.xml:375 #, no-c-format -msgid "In addition, there are some special folders within the <filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</emphasis> format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. After installing <command>dhelp</command> you will find a browse-able index of documentation in <filename>/usr/share/doc/HTML/index.html</filename>." +msgid "" +"In addition, there are some special folders within the <filename>/usr/share/" +"doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</" +"emphasis> format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. " +"After installing <command>dhelp</command> you will find a browse-able index " +"of documentation in <filename>/usr/share/doc/HTML/index.html</filename>." msgstr "" #. Tag: para #: boot-new.xml:385 #, no-c-format -msgid "One easy way to view these documents is to <userinput>cd /usr/share/doc/</userinput>, and type <userinput>lynx</userinput> followed by a space and a dot (the dot stands for the current directory)." +msgid "" +"One easy way to view these documents is to <userinput>cd /usr/share/doc/</" +"userinput>, and type <userinput>lynx</userinput> followed by a space and a " +"dot (the dot stands for the current directory)." msgstr "" #. Tag: para #: boot-new.xml:392 #, no-c-format -msgid "You can also type <userinput>info <replaceable>command</replaceable></userinput> or <userinput>man <replaceable>command</replaceable></userinput> to see documentation on most commands available at the command prompt. Typing <userinput>help</userinput> will display help on shell commands. And typing a command followed by <userinput>--help</userinput> will usually display a short summary of the command's usage. If a command's results scroll past the top of the screen, type <userinput>| more</userinput> after the command to cause the results to pause before scrolling past the top of the screen. To see a list of all commands available which begin with a certain letter, type the letter and then two tabs." +msgid "" +"You can also type <userinput>info <replaceable>command</replaceable></" +"userinput> or <userinput>man <replaceable>command</replaceable></userinput> " +"to see documentation on most commands available at the command prompt. " +"Typing <userinput>help</userinput> will display help on shell commands. And " +"typing a command followed by <userinput>--help</userinput> will usually " +"display a short summary of the command's usage. If a command's results " +"scroll past the top of the screen, type <userinput>| more</userinput> after " +"the command to cause the results to pause before scrolling past the top of " +"the screen. To see a list of all commands available which begin with a " +"certain letter, type the letter and then two tabs." msgstr "" #. Tag: para #: boot-new.xml:407 #, no-c-format -msgid "For a more complete introduction to Debian and GNU/Linux, see <filename>/usr/share/doc/debian-guide/html/noframes/index.html</filename>." +msgid "" +"For a more complete introduction to Debian and GNU/Linux, see <filename>/usr/" +"share/doc/debian-guide/html/noframes/index.html</filename>." msgstr "" - diff --git a/po/hu/hardware.po b/po/hu/hardware.po index 87b5b5170..f477ad3fa 100644 --- a/po/hu/hardware.po +++ b/po/hu/hardware.po @@ -1,12 +1,13 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: \n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2006-08-18 17:32+0000\n" "PO-Revision-Date: 2006-08-20 17:27+0100\n" "Last-Translator: SZERVÁC Attila <sas@321.hu>\n" "Language-Team: hu\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Poedit-Language: Hungarian\n" @@ -21,8 +22,14 @@ msgstr "Rendszerkövetelmények" #. Tag: para #: hardware.xml:7 #, no-c-format -msgid "This section contains information about what hardware you need to get started with Debian. You will also find links to further information about hardware supported by GNU and Linux." -msgstr "E fejezet leírja a Debian használatához szükséges hardvert. A GNU és Linux által támogatott hardverekről szóló további információkra utaló hivatkozásokat is ad." +msgid "" +"This section contains information about what hardware you need to get " +"started with Debian. You will also find links to further information about " +"hardware supported by GNU and Linux." +msgstr "" +"E fejezet leírja a Debian használatához szükséges hardvert. A GNU és Linux " +"által támogatott hardverekről szóló további információkra utaló " +"hivatkozásokat is ad." #. Tag: title #: hardware.xml:20 @@ -33,14 +40,32 @@ msgstr "Támogatott hardver" #. Tag: para #: hardware.xml:21 #, no-c-format -msgid "Debian does not impose hardware requirements beyond the requirements of the Linux kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux kernel, libc, <command>gcc</command>, etc. have been ported, and for which a Debian port exists, can run Debian. Please refer to the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on &arch-title; architecture systems which have been tested with Debian." -msgstr "A Debian nem igényel a Linux és a GNU eszköz-készletek által kívántnál több hardvert. Ezért minden gépen, melyen a Linux kernel, a libc, a <command>gcc</command> és a többi fut, és melyre a Debian portolva van, futtatható a Debian. Lásd a Debian portok oldalát a <ulink url=\"&url-ports;\"></ulink> címen a jelen &arch-title; architektúra rendszerekről, melyek teszteltek a Debian rendszerrel." +msgid "" +"Debian does not impose hardware requirements beyond the requirements of the " +"Linux kernel and the GNU tool-sets. Therefore, any architecture or platform " +"to which the Linux kernel, libc, <command>gcc</command>, etc. have been " +"ported, and for which a Debian port exists, can run Debian. Please refer to " +"the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on " +"&arch-title; architecture systems which have been tested with Debian." +msgstr "" +"A Debian nem igényel a Linux és a GNU eszköz-készletek által kívántnál több " +"hardvert. Ezért minden gépen, melyen a Linux kernel, a libc, a <command>gcc</" +"command> és a többi fut, és melyre a Debian portolva van, futtatható a " +"Debian. Lásd a Debian portok oldalát a <ulink url=\"&url-ports;\"></ulink> " +"címen a jelen &arch-title; architektúra rendszerekről, melyek teszteltek a " +"Debian rendszerrel." #. Tag: para #: hardware.xml:32 #, no-c-format -msgid "Rather than attempting to describe all the different hardware configurations which are supported for &arch-title;, this section contains general information and pointers to where additional information can be found." -msgstr "A jelen, &arch-title; architektúra által támogatott összes különböző hardver konfiguráció leírásának megkísérlése helyett, e fejezet általános adatokat és hivatkozásokat ad bővebb adatok helyéről." +msgid "" +"Rather than attempting to describe all the different hardware configurations " +"which are supported for &arch-title;, this section contains general " +"information and pointers to where additional information can be found." +msgstr "" +"A jelen, &arch-title; architektúra által támogatott összes különböző hardver " +"konfiguráció leírásának megkísérlése helyett, e fejezet általános adatokat " +"és hivatkozásokat ad bővebb adatok helyéről." #. Tag: title #: hardware.xml:41 @@ -51,7 +76,9 @@ msgstr "Támogatott architektúrák" #. Tag: para #: hardware.xml:42 #, no-c-format -msgid "Debian &release; supports eleven major architectures and several variations of each architecture known as <quote>flavors</quote>." +msgid "" +"Debian &release; supports eleven major architectures and several variations " +"of each architecture known as <quote>flavors</quote>." msgstr "" #. Tag: entry @@ -247,29 +274,25 @@ msgid "r5k-ip32" msgstr "r5k-ip32" #. Tag: entry -#: hardware.xml:119 -#: hardware.xml:137 +#: hardware.xml:119 hardware.xml:137 #, no-c-format msgid "Broadcom BCM91250A (SWARM)" msgstr "Broadcom BCM91250A (SWARM)" #. Tag: entry -#: hardware.xml:120 -#: hardware.xml:138 +#: hardware.xml:120 hardware.xml:138 #, no-c-format msgid "sb1-bcm91250a" msgstr "sb1-bcm91250a" #. Tag: entry -#: hardware.xml:122 -#: hardware.xml:140 +#: hardware.xml:122 hardware.xml:140 #, no-c-format msgid "Broadcom BCM91480B (BigSur)" msgstr "Broadcom BCM91480B (BigSur)" #. Tag: entry -#: hardware.xml:123 -#: hardware.xml:141 +#: hardware.xml:123 hardware.xml:141 #, no-c-format msgid "sb1a-bcm91480b" msgstr "sb1a-bcm91480b" @@ -305,19 +328,13 @@ msgid "DECstation" msgstr "DECstation" #. Tag: entry -#: hardware.xml:133 -#: hardware.xml:1087 -#: hardware.xml:1102 -#: hardware.xml:1112 +#: hardware.xml:133 hardware.xml:1087 hardware.xml:1102 hardware.xml:1112 #, no-c-format msgid "r4k-kn04" msgstr "r4k-kn04" #. Tag: entry -#: hardware.xml:135 -#: hardware.xml:1082 -#: hardware.xml:1092 -#: hardware.xml:1097 +#: hardware.xml:135 hardware.xml:1082 hardware.xml:1092 hardware.xml:1097 #: hardware.xml:1107 #, no-c-format msgid "r3k-kn02" @@ -518,26 +535,42 @@ msgstr "szalag" #. Tag: para #: hardware.xml:201 #, no-c-format -msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture. If you are looking for information on any of the other Debian-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">Debian-Ports</ulink> pages." -msgstr "E dokumentum leírja a Debian <emphasis>&arch-title;</emphasis> architektúrára telepítését. Ha más, Debian által támogatott architektúra érdekel, nézd meg a <ulink url=\"http://www.debian.org/ports/\">Debian portok</ulink> oldalt." +msgid "" +"This document covers installation for the <emphasis>&arch-title;</emphasis> " +"architecture. If you are looking for information on any of the other Debian-" +"supported architectures take a look at the <ulink url=\"http://www.debian." +"org/ports/\">Debian-Ports</ulink> pages." +msgstr "" +"E dokumentum leírja a Debian <emphasis>&arch-title;</emphasis> " +"architektúrára telepítését. Ha más, Debian által támogatott architektúra " +"érdekel, nézd meg a <ulink url=\"http://www.debian.org/ports/\">Debian " +"portok</ulink> oldalt." #. Tag: para #: hardware.xml:209 #, no-c-format -msgid "This is the first official release of &debian; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well." -msgstr "Az a &debian; 1. hivatalos &arch-title; kiadása. Tapasztalataink szerint megérett a kiadásra. De mivel még kevesebb felhasználó tesztelte, ezért nagyobb az esély, hogy találsz benne hibát. Kérjük, a <ulink url=\"&url-bts;\">Hibakövető rendszer</ulink> segítségével jelents minden hibát; említsd meg, hogy a hibát &arch-title; platformon lelted. Ilyenkor az architektúrának megfelelő <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; lista</ulink> használata is szükséges lehet." +msgid "" +"This is the first official release of &debian; for the &arch-title; " +"architecture. We feel that it has proven itself sufficiently to be released. " +"However, because it has not had the exposure (and hence testing by users) " +"that some other architectures have had, you may encounter a few bugs. Use " +"our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any " +"problems; make sure to mention the fact that the bug is on the &arch-title; " +"platform. It can be necessary to use the <ulink url=\"&url-list-subscribe;" +"\">debian-&arch-listname; mailing list</ulink> as well." +msgstr "" +"Az a &debian; 1. hivatalos &arch-title; kiadása. Tapasztalataink szerint " +"megérett a kiadásra. De mivel még kevesebb felhasználó tesztelte, ezért " +"nagyobb az esély, hogy találsz benne hibát. Kérjük, a <ulink url=\"&url-bts;" +"\">Hibakövető rendszer</ulink> segítségével jelents minden hibát; említsd " +"meg, hogy a hibát &arch-title; platformon lelted. Ilyenkor az " +"architektúrának megfelelő <ulink url=\"&url-list-subscribe;\">debian-&arch-" +"listname; lista</ulink> használata is szükséges lehet." #. Tag: title -#: hardware.xml:231 -#: hardware.xml:690 -#: hardware.xml:726 -#: hardware.xml:802 -#: hardware.xml:821 -#: hardware.xml:907 -#: hardware.xml:949 -#: hardware.xml:1017 -#: hardware.xml:1176 -#: hardware.xml:1622 +#: hardware.xml:231 hardware.xml:690 hardware.xml:726 hardware.xml:802 +#: hardware.xml:821 hardware.xml:907 hardware.xml:949 hardware.xml:1017 +#: hardware.xml:1176 hardware.xml:1622 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "CPU, alaplap és videó támogatás" @@ -545,20 +578,42 @@ msgstr "CPU, alaplap és videó támogatás" #. Tag: para #: hardware.xml:232 #, no-c-format -msgid "Complete information regarding supported DEC Alphas can be found at <ulink url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this section is to describe the systems supported by the boot disks." -msgstr "A támogatott DEC Alpha gépekkel kapcsolatos adatok a <ulink url=\"&url-alpha-howto;\">Linux Alpha HOGYAN</ulink> címen találhatók. E szakasz célja az indító lemezek által támogatott rendszerek leírása." +msgid "" +"Complete information regarding supported DEC Alphas can be found at <ulink " +"url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this " +"section is to describe the systems supported by the boot disks." +msgstr "" +"A támogatott DEC Alpha gépekkel kapcsolatos adatok a <ulink url=\"&url-alpha-" +"howto;\">Linux Alpha HOGYAN</ulink> címen találhatók. E szakasz célja az " +"indító lemezek által támogatott rendszerek leírása." #. Tag: para #: hardware.xml:239 #, no-c-format -msgid "Alpha machines are subdivided into different system types because there are a number of generations of motherboard and supporting chipsets. Different systems (<quote>sub-architectures</quote>) often have radically different engineering and capabilities. Therefore, the process of installing and, more to the point, booting, can vary from system to system." -msgstr "Az Alpha gépek 2 eltérő rendszer-típusra oszlanak, mert számos generációt éltek meg. Ezek az alrendszerek (<quote>al-architektúrák</quote>) teljesen eltérő felépítéssel és képességekkel rendelkeznek. Ezért a telepítés, és főleg az indítás rendszerről rendszerre eltér." +msgid "" +"Alpha machines are subdivided into different system types because there are " +"a number of generations of motherboard and supporting chipsets. Different " +"systems (<quote>sub-architectures</quote>) often have radically different " +"engineering and capabilities. Therefore, the process of installing and, more " +"to the point, booting, can vary from system to system." +msgstr "" +"Az Alpha gépek 2 eltérő rendszer-típusra oszlanak, mert számos generációt " +"éltek meg. Ezek az alrendszerek (<quote>al-architektúrák</quote>) teljesen " +"eltérő felépítéssel és képességekkel rendelkeznek. Ezért a telepítés, és " +"főleg az indítás rendszerről rendszerre eltér." #. Tag: para #: hardware.xml:247 #, no-c-format -msgid "The following table lists the system types supported by the Debian installation system. The table also indicates the <emphasis>code name</emphasis> for these system types. You'll need to know this code name when you actually begin the installation process:" -msgstr "Az alábbi táblázat adja a Debian telepítő rendszer által támogatott rendszereket. A táblázat e rendszerek <emphasis>kódnevét</emphasis> is mutatja. A telepítés megkezdéséhez tudnod kell majd ezt:" +msgid "" +"The following table lists the system types supported by the Debian " +"installation system. The table also indicates the <emphasis>code name</" +"emphasis> for these system types. You'll need to know this code name when " +"you actually begin the installation process:" +msgstr "" +"Az alábbi táblázat adja a Debian telepítő rendszer által támogatott " +"rendszereket. A táblázat e rendszerek <emphasis>kódnevét</emphasis> is " +"mutatja. A telepítés megkezdéséhez tudnod kell majd ezt:" #. Tag: entry #: hardware.xml:264 @@ -597,9 +652,7 @@ msgid "Maverick" msgstr "Maverick" #. Tag: entry -#: hardware.xml:274 -#: hardware.xml:278 -#: hardware.xml:282 +#: hardware.xml:274 hardware.xml:278 hardware.xml:282 #, no-c-format msgid "alcor" msgstr "alcor" @@ -689,14 +742,8 @@ msgid "Mustang" msgstr "Mustang" #. Tag: entry -#: hardware.xml:300 -#: hardware.xml:304 -#: hardware.xml:308 -#: hardware.xml:312 -#: hardware.xml:316 -#: hardware.xml:320 -#: hardware.xml:324 -#: hardware.xml:328 +#: hardware.xml:300 hardware.xml:304 hardware.xml:308 hardware.xml:312 +#: hardware.xml:316 hardware.xml:320 hardware.xml:324 hardware.xml:328 #, no-c-format msgid "avanti" msgstr "avanti" @@ -786,9 +833,7 @@ msgid "Avanti" msgstr "Avanti" #. Tag: entry -#: hardware.xml:332 -#: hardware.xml:345 -#: hardware.xml:346 +#: hardware.xml:332 hardware.xml:345 hardware.xml:346 #, no-c-format msgid "EB164" msgstr "EB164" @@ -854,9 +899,7 @@ msgid "eb164" msgstr "eb164" #. Tag: entry -#: hardware.xml:351 -#: hardware.xml:360 -#: hardware.xml:361 +#: hardware.xml:351 hardware.xml:360 hardware.xml:361 #, no-c-format msgid "EB64+" msgstr "EB64+" @@ -868,15 +911,13 @@ msgid "AlphaPC64" msgstr "AlphaPC64" #. Tag: entry -#: hardware.xml:353 -#: hardware.xml:357 +#: hardware.xml:353 hardware.xml:357 #, no-c-format msgid "Cabriolet" msgstr "Cabriolet" #. Tag: entry -#: hardware.xml:354 -#: hardware.xml:358 +#: hardware.xml:354 hardware.xml:358 #, no-c-format msgid "cabriolet" msgstr "cabriolet" @@ -894,9 +935,7 @@ msgid "eb64p" msgstr "eb64p" #. Tag: entry -#: hardware.xml:366 -#: hardware.xml:367 -#: hardware.xml:368 +#: hardware.xml:366 hardware.xml:367 hardware.xml:368 #, no-c-format msgid "EB66" msgstr "EB66" @@ -908,8 +947,7 @@ msgid "eb66" msgstr "eb66" #. Tag: entry -#: hardware.xml:371 -#: hardware.xml:372 +#: hardware.xml:371 hardware.xml:372 #, no-c-format msgid "EB66+" msgstr "EB66+" @@ -933,53 +971,22 @@ msgid "DEC 2000 Model 300(S)" msgstr "DEC 2000 Model 300(S)" #. Tag: entry -#: hardware.xml:379 -#: hardware.xml:387 +#: hardware.xml:379 hardware.xml:387 #, no-c-format msgid "Jensen" msgstr "Jensen" #. Tag: entry -#: hardware.xml:380 -#: hardware.xml:384 -#: hardware.xml:388 -#: hardware.xml:449 -#: hardware.xml:453 -#: hardware.xml:471 -#: hardware.xml:475 -#: hardware.xml:479 -#: hardware.xml:483 -#: hardware.xml:487 -#: hardware.xml:491 -#: hardware.xml:495 -#: hardware.xml:509 -#: hardware.xml:513 -#: hardware.xml:517 -#: hardware.xml:521 -#: hardware.xml:525 -#: hardware.xml:559 -#: hardware.xml:563 -#: hardware.xml:567 -#: hardware.xml:571 -#: hardware.xml:585 -#: hardware.xml:589 -#: hardware.xml:593 -#: hardware.xml:597 -#: hardware.xml:604 -#: hardware.xml:608 -#: hardware.xml:612 -#: hardware.xml:616 -#: hardware.xml:620 -#: hardware.xml:624 -#: hardware.xml:628 -#: hardware.xml:632 -#: hardware.xml:636 -#: hardware.xml:640 -#: hardware.xml:644 -#: hardware.xml:648 -#: hardware.xml:652 -#: hardware.xml:659 -#: hardware.xml:663 +#: hardware.xml:380 hardware.xml:384 hardware.xml:388 hardware.xml:449 +#: hardware.xml:453 hardware.xml:471 hardware.xml:475 hardware.xml:479 +#: hardware.xml:483 hardware.xml:487 hardware.xml:491 hardware.xml:495 +#: hardware.xml:509 hardware.xml:513 hardware.xml:517 hardware.xml:521 +#: hardware.xml:525 hardware.xml:559 hardware.xml:563 hardware.xml:567 +#: hardware.xml:571 hardware.xml:585 hardware.xml:589 hardware.xml:593 +#: hardware.xml:597 hardware.xml:604 hardware.xml:608 hardware.xml:612 +#: hardware.xml:616 hardware.xml:620 hardware.xml:624 hardware.xml:628 +#: hardware.xml:632 hardware.xml:636 hardware.xml:640 hardware.xml:644 +#: hardware.xml:648 hardware.xml:652 hardware.xml:659 hardware.xml:663 #, no-c-format msgid "<entry>N/A</entry>" msgstr "<entry>N/A</entry>" @@ -1015,27 +1022,15 @@ msgid "Personal WorkStation 433a" msgstr "Personal WorkStation 433a" #. Tag: entry -#: hardware.xml:394 -#: hardware.xml:398 -#: hardware.xml:402 -#: hardware.xml:406 -#: hardware.xml:410 -#: hardware.xml:414 -#: hardware.xml:418 -#: hardware.xml:422 +#: hardware.xml:394 hardware.xml:398 hardware.xml:402 hardware.xml:406 +#: hardware.xml:410 hardware.xml:414 hardware.xml:418 hardware.xml:422 #, no-c-format msgid "Miata" msgstr "Miata" #. Tag: entry -#: hardware.xml:395 -#: hardware.xml:399 -#: hardware.xml:403 -#: hardware.xml:407 -#: hardware.xml:411 -#: hardware.xml:415 -#: hardware.xml:419 -#: hardware.xml:423 +#: hardware.xml:395 hardware.xml:399 hardware.xml:403 hardware.xml:407 +#: hardware.xml:411 hardware.xml:415 hardware.xml:419 hardware.xml:423 #, no-c-format msgid "miata" msgstr "miata" @@ -1101,10 +1096,7 @@ msgid "Mikasa" msgstr "Mikasa" #. Tag: entry -#: hardware.xml:430 -#: hardware.xml:434 -#: hardware.xml:438 -#: hardware.xml:442 +#: hardware.xml:430 hardware.xml:434 hardware.xml:438 hardware.xml:442 #, no-c-format msgid "mikasa" msgstr "mikasa" @@ -1122,8 +1114,7 @@ msgid "Mikasa+" msgstr "Mikasa+" #. Tag: entry -#: hardware.xml:436 -#: hardware.xml:440 +#: hardware.xml:436 hardware.xml:440 #, no-c-format msgid "AlphaServer 1000 5/300" msgstr "AlphaServer 1000 5/300" @@ -1189,8 +1180,7 @@ msgid "Noname" msgstr "Névtelen" #. Tag: entry -#: hardware.xml:460 -#: hardware.xml:464 +#: hardware.xml:460 hardware.xml:464 #, no-c-format msgid "noname" msgstr "névtelen" @@ -1256,9 +1246,7 @@ msgid "AlphaServer 800 5/333...500" msgstr "AlphaServer 800 5/333...500" #. Tag: entry -#: hardware.xml:482 -#: hardware.xml:490 -#: hardware.xml:494 +#: hardware.xml:482 hardware.xml:490 hardware.xml:494 #, no-c-format msgid "Corelle" msgstr "Corelle" @@ -1294,8 +1282,7 @@ msgid "PLATFORM 2000" msgstr "PLATFORM 2000" #. Tag: entry -#: hardware.xml:500 -#: hardware.xml:501 +#: hardware.xml:500 hardware.xml:501 #, no-c-format msgid "<entry>P2K</entry>" msgstr "<entry>P2K</entry>" @@ -1319,8 +1306,7 @@ msgid "AlphaServer 1200 5/xxx" msgstr "AlphaServer 1200 5/xxx" #. Tag: entry -#: hardware.xml:508 -#: hardware.xml:520 +#: hardware.xml:508 hardware.xml:520 #, no-c-format msgid "Tincup/DaVinci" msgstr "Tincup/DaVinci" @@ -1344,8 +1330,7 @@ msgid "AlphaServer 4100 5/xxx" msgstr "AlphaServer 4100 5/xxx" #. Tag: entry -#: hardware.xml:516 -#: hardware.xml:524 +#: hardware.xml:516 hardware.xml:524 #, no-c-format msgid "Dodge" msgstr "Dodge" @@ -1375,23 +1360,15 @@ msgid "DeskStation AlphaPC164-UX" msgstr "DeskStation AlphaPC164-UX" #. Tag: entry -#: hardware.xml:531 -#: hardware.xml:535 -#: hardware.xml:539 -#: hardware.xml:543 -#: hardware.xml:547 -#: hardware.xml:551 +#: hardware.xml:531 hardware.xml:535 hardware.xml:539 hardware.xml:543 +#: hardware.xml:547 hardware.xml:551 #, no-c-format msgid "Ruffian" msgstr "Ruffian" #. Tag: entry -#: hardware.xml:532 -#: hardware.xml:536 -#: hardware.xml:540 -#: hardware.xml:544 -#: hardware.xml:548 -#: hardware.xml:552 +#: hardware.xml:532 hardware.xml:536 hardware.xml:540 hardware.xml:544 +#: hardware.xml:548 hardware.xml:552 #, no-c-format msgid "ruffian" msgstr "ruffian" @@ -1547,9 +1524,7 @@ msgid "Privateer" msgstr "Privateer" #. Tag: entry -#: hardware.xml:595 -#: hardware.xml:634 -#: hardware.xml:638 +#: hardware.xml:595 hardware.xml:634 hardware.xml:638 #, no-c-format msgid "UNKNOWN" msgstr "ISMERETLEN" @@ -1573,8 +1548,7 @@ msgid "AlphaServer DS10" msgstr "AlphaServer DS10" #. Tag: entry -#: hardware.xml:603 -#: hardware.xml:651 +#: hardware.xml:603 hardware.xml:651 #, no-c-format msgid "Webbrick" msgstr "Webbrick" @@ -1640,8 +1614,7 @@ msgid "Clipper" msgstr "Clipper" #. Tag: entry -#: hardware.xml:626 -#: hardware.xml:627 +#: hardware.xml:626 hardware.xml:627 #, no-c-format msgid "DP264" msgstr "DP264" @@ -1713,8 +1686,7 @@ msgid "AlphaServer GS160" msgstr "AlphaServer GS160" #. Tag: entry -#: hardware.xml:658 -#: hardware.xml:662 +#: hardware.xml:658 hardware.xml:662 #, no-c-format msgid "Wildfire" msgstr "Wildfire" @@ -1726,8 +1698,7 @@ msgid "AlphaServer GS320" msgstr "AlphaServer GS320" #. Tag: entry -#: hardware.xml:667 -#: hardware.xml:669 +#: hardware.xml:667 hardware.xml:669 #, no-c-format msgid "<entry>XL</entry>" msgstr "<entry>XL</entry>" @@ -1747,20 +1718,27 @@ msgstr "<entry>xl</entry>" #. Tag: para #: hardware.xml:675 #, no-c-format -msgid "It is believed that Debian &releasename; supports installing on all alpha sub-architectures with the exception of the ARC-only Ruffian and XL sub-architectures and the Titan subarchitecture, which requires a change to the kernel compile options." +msgid "" +"It is believed that Debian &releasename; supports installing on all alpha " +"sub-architectures with the exception of the ARC-only Ruffian and XL sub-" +"architectures and the Titan subarchitecture, which requires a change to the " +"kernel compile options." msgstr "" #. Tag: para -#: hardware.xml:691 -#: hardware.xml:822 +#: hardware.xml:691 hardware.xml:822 #, no-c-format -msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics." -msgstr "A <ulink url=\"&url-hardware-howto;\">Linux Hardver Kompatibilitás HOGYAN</ulink> leírásban megtalálható a támogatott perifériák listája. Ez a fejezet csak az alapokat emel ki." +msgid "" +"Complete information concerning supported peripherals can be found at <ulink " +"url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. " +"This section merely outlines the basics." +msgstr "" +"A <ulink url=\"&url-hardware-howto;\">Linux Hardver Kompatibilitás HOGYAN</" +"ulink> leírásban megtalálható a támogatott perifériák listája. Ez a fejezet " +"csak az alapokat emel ki." #. Tag: title -#: hardware.xml:699 -#: hardware.xml:830 -#: hardware.xml:990 +#: hardware.xml:699 hardware.xml:830 hardware.xml:990 #, no-c-format msgid "<title>CPU</title>" msgstr "<title>CPU</title>" @@ -1774,13 +1752,20 @@ msgstr "Az AMD64 és Intel EM64t processzorok is támogatottak." #. Tag: para #: hardware.xml:728 #, no-c-format -msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard Debian distribution only supports installation on a number of the most common systems. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU including xscale." +msgid "" +"Each distinct ARM architecture requires its own kernel. Because of this the " +"standard Debian distribution only supports installation on a number of the " +"most common systems. The Debian userland however may be used by " +"<emphasis>any</emphasis> ARM CPU including xscale." msgstr "" #. Tag: para #: hardware.xml:736 #, no-c-format -msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems." +msgid "" +"Most ARM CPUs may be run in either endian mode (big or little). However, the " +"majority of current system implementation uses little-endian mode. Debian " +"currently only supports little-endian ARM systems." msgstr "" #. Tag: para @@ -1798,8 +1783,17 @@ msgstr "Netwinder" #. Tag: para #: hardware.xml:752 #, no-c-format -msgid "This is actually the name for the group of machines based upon the StrongARM 110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff)." -msgstr "Ez a StrongARM 110 CPU és az Intel 21285 Northbridge (vagy Footbridge) hardverekre épülő gépek neve. Többek között: Netwinder (az egyik legelterjedtebb ARM gép), CATS (vagy EB110ATX), EBSA 285 és Compaq personal server (cps más néven skiff)." +msgid "" +"This is actually the name for the group of machines based upon the StrongARM " +"110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises " +"of machines like: Netwinder (possibly one of the most common ARM boxes), " +"CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, " +"aka skiff)." +msgstr "" +"Ez a StrongARM 110 CPU és az Intel 21285 Northbridge (vagy Footbridge) " +"hardverekre épülő gépek neve. Többek között: Netwinder (az egyik " +"legelterjedtebb ARM gép), CATS (vagy EB110ATX), EBSA 285 és Compaq personal " +"server (cps más néven skiff)." #. Tag: term #: hardware.xml:765 @@ -1810,7 +1804,11 @@ msgstr "NSLU2" #. Tag: para #: hardware.xml:766 #, no-c-format -msgid "The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected." +msgid "" +"The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small " +"device which allows you to easily provide storage via the network. It comes " +"with an Ethernet connection and two USB ports to which hard drives can be " +"connected." msgstr "" #. Tag: term @@ -1822,32 +1820,100 @@ msgstr "<term>RiscPC</term>" #. Tag: para #: hardware.xml:778 #, no-c-format -msgid "This machine is the oldest supported hardware: it was released in 1994. It has RISC OS in ROM, Linux can be booted from that OS using linloader. The RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA video, parallel port, single serial port, PS/2 keyboard and proprietary mouse port. The proprietary module expansion bus allows for up to eight expansion cards to be fitted depending on configuration, several of these modules have Linux drivers." -msgstr "Ez a gép a legrégebben támogatott hardver: a megjelenés éve: 1994. A ROM tartalma egy RISC OS, a Linux ebből indítható a linloader programmal. A RiscPC lelke egy moduláris CPU kártya, melyen jellemzően egy 30MHz 610, 40MHz 710 vagy 233MHz Strongarm 110 CPU van. Az alaplapon IDE, SVGA, párhuzamos és 1 soros port, PS/2 billentyű és egy egyéni egér port. Az egyéni modul bővítő busz a kiépítéstől függően legfeljebb 8 különféle bővítő kártyát tesz lehetővé, egyesek mennek Linuxszal." +msgid "" +"This machine is the oldest supported hardware: it was released in 1994. It " +"has RISC OS in ROM, Linux can be booted from that OS using linloader. The " +"RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or " +"233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA " +"video, parallel port, single serial port, PS/2 keyboard and proprietary " +"mouse port. The proprietary module expansion bus allows for up to eight " +"expansion cards to be fitted depending on configuration, several of these " +"modules have Linux drivers." +msgstr "" +"Ez a gép a legrégebben támogatott hardver: a megjelenés éve: 1994. A ROM " +"tartalma egy RISC OS, a Linux ebből indítható a linloader programmal. A " +"RiscPC lelke egy moduláris CPU kártya, melyen jellemzően egy 30MHz 610, " +"40MHz 710 vagy 233MHz Strongarm 110 CPU van. Az alaplapon IDE, SVGA, " +"párhuzamos és 1 soros port, PS/2 billentyű és egy egyéni egér port. Az " +"egyéni modul bővítő busz a kiépítéstől függően legfeljebb 8 különféle bővítő " +"kártyát tesz lehetővé, egyesek mennek Linuxszal." #. Tag: para #: hardware.xml:803 #, no-c-format -msgid "The are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future." +msgid "" +"The are two major support <emphasis>&architecture;</emphasis> flavors: PA-" +"RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit " +"processors whereas the 2.0 architecture is targeted to the 64-bit " +"processors. Some systems are able to run either kernel. In both cases, the " +"userland is 32-bit. There is the possibility of a 64-bit userland in the " +"future." msgstr "" #. Tag: para #: hardware.xml:831 #, no-c-format -msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bits AMD and VIA (former Cyrix) processors, and new processors like the Athlon XP and Intel P4 Xeon." -msgstr "Szinte minden, sok személyi számítógépben még ma is használt x86-alapú (IA-32) processzor támogatott, ideértve az Intel néhai \"Pentium\" sorozatát is. Ez a legrégebbi 32-bites AMD és VIA (egykor Cyrix) processzorokat is jelenti és a a kevésbé régi Athlon XP és Intel P4 Xeonokat." +msgid "" +"Nearly all x86-based (IA-32) processors still in use in personal computers " +"are supported, including all varieties of Intel's \"Pentium\" series. This " +"also includes 32-bits AMD and VIA (former Cyrix) processors, and new " +"processors like the Athlon XP and Intel P4 Xeon." +msgstr "" +"Szinte minden, sok személyi számítógépben még ma is használt x86-alapú (IA-" +"32) processzor támogatott, ideértve az Intel néhai \"Pentium\" sorozatát is. " +"Ez a legrégebbi 32-bites AMD és VIA (egykor Cyrix) processzorokat is jelenti " +"és a a kevésbé régi Athlon XP és Intel P4 Xeonokat." #. Tag: para #: hardware.xml:839 #, no-c-format -msgid "If your system has a 64-bits AMD64, Intel EM64t or Intel Core 2 Duo processor, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bits) i386 architecture." -msgstr "Ha a rendszeredben egy 64-bites AMD64, Intel EM64t vagy Intel Core 2 Duo processzor van, akkor valószínűleg már az amd64 architektúrát akarod használni a (32-bites) i386 architektúra telepítője helyett." +msgid "" +"If your system has a 64-bits AMD64, Intel EM64t or Intel Core 2 Duo " +"processor, you will probably want to use the installer for the amd64 " +"architecture instead of the installer for the (32-bits) i386 architecture." +msgstr "" +"Ha a rendszeredben egy 64-bites AMD64, Intel EM64t vagy Intel Core 2 Duo " +"processzor van, akkor valószínűleg már az amd64 architektúrát akarod " +"használni a (32-bites) i386 architektúra telepítője helyett." #. Tag: para #: hardware.xml:846 #, no-c-format -msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", Debian Sarge has <emphasis>dropped support</emphasis> for actual 80386 processors (and their clones), which were supported by earlier releases<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para> </footnote>." -msgstr "Tudni kell, hogy a Debian GNU/Linux &releasename; immár <emphasis>nem</emphasis> fut 386-os vagy korábbi processzoron. Az \"i386\" architektúra-név ellenére a Debian Sarge óta <emphasis>megszűnt a támogatás</emphasis> a 80386 processzorokhoz (és másolataikhoz), melyet a korábbi kiadások támogattak<footnote> <para> Sokáig megpróbáltuk elkerülni ezt, de végül a fordító és a kernel hibáinak egy szerencsétlen sora miatt, amely egy a GCC által szállított C++ ABI hibával kezdődött ez szükséges volt. A Debian GNU/Linux még mindig futtatható 80386-os processzoron, de ehhez megadnak kell lefordítanod a kernelt és az összes használt csomagot, és ez túlmutat e kézikönyv célján. </para> </footnote>. (A Linux nem támogatja a 286-os vagy korábbi x86 processzorokat.) Minden i486 és későbbi processzor támogatott<footnote> <para> Sok Debian érezhetően gyorsabban fut modern gépeken, ami a régi gépek támogatása elvetésének pozitív oldala. Az i486 (1989) 3 utasításkóddal bír (bswap, cmpxchg, és xadd) mellyel az i386, (1986) nem. Korábban a legtöbb Debian csomagban ezek nemigen voltak használhatók; most igen. </para> </footnote>." +msgid "" +"However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on " +"386 or earlier processors. Despite the architecture name \"i386\", Debian " +"Sarge has <emphasis>dropped support</emphasis> for actual 80386 processors " +"(and their clones), which were supported by earlier releases<footnote> " +"<para> We have long tried to avoid this, but in the end it was necessary due " +"a unfortunate series of issues with the compiler and the kernel, starting " +"with an bug in the C++ ABI provided by GCC. You should still be able to run " +"Debian GNU/Linux on actual 80386 processors if you compile your own kernel " +"and compile all packages from source, but that is beyond the scope of this " +"manual. </para> </footnote>. (No version of Linux has ever supported the 286 " +"or earlier chips in the series.) All i486 and later processors are still " +"supported<footnote> <para> Many Debian packages will actually run slightly " +"faster on modern computers as a positive side effect of dropping support for " +"these old chips. The i486, introduced in 1989, has three opcodes (bswap, " +"cmpxchg, and xadd) which the i386, introduced in 1986, did not have. " +"Previously, these could not be easily used by most Debian packages; now they " +"can. </para> </footnote>." +msgstr "" +"Tudni kell, hogy a Debian GNU/Linux &releasename; immár <emphasis>nem</" +"emphasis> fut 386-os vagy korábbi processzoron. Az \"i386\" architektúra-név " +"ellenére a Debian Sarge óta <emphasis>megszűnt a támogatás</emphasis> a " +"80386 processzorokhoz (és másolataikhoz), melyet a korábbi kiadások " +"támogattak<footnote> <para> Sokáig megpróbáltuk elkerülni ezt, de végül a " +"fordító és a kernel hibáinak egy szerencsétlen sora miatt, amely egy a GCC " +"által szállított C++ ABI hibával kezdődött ez szükséges volt. A Debian GNU/" +"Linux még mindig futtatható 80386-os processzoron, de ehhez megadnak kell " +"lefordítanod a kernelt és az összes használt csomagot, és ez túlmutat e " +"kézikönyv célján. </para> </footnote>. (A Linux nem támogatja a 286-os vagy " +"korábbi x86 processzorokat.) Minden i486 és későbbi processzor " +"támogatott<footnote> <para> Sok Debian érezhetően gyorsabban fut modern " +"gépeken, ami a régi gépek támogatása elvetésének pozitív oldala. Az i486 " +"(1989) 3 utasításkóddal bír (bswap, cmpxchg, és xadd) mellyel az i386, " +"(1986) nem. Korábban a legtöbb Debian csomagban ezek nemigen voltak " +"használhatók; most igen. </para> </footnote>." #. Tag: title #: hardware.xml:883 @@ -1858,49 +1924,114 @@ msgstr "" #. Tag: para #: hardware.xml:884 #, no-c-format -msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, the Microchannel Architecture (MCA, used in IBM's PS/2 line), or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these." +msgid "" +"The system bus is the part of the motherboard which allows the CPU to " +"communicate with peripherals such as storage devices. Your computer must use " +"the ISA, EISA, PCI, the Microchannel Architecture (MCA, used in IBM's PS/2 " +"line), or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all " +"personal computers sold in recent years use one of these." msgstr "" #. Tag: para #: hardware.xml:908 #, no-c-format -msgid "Complete information concerning supported M68000 based (<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the basics." +msgid "" +"Complete information concerning supported M68000 based " +"(<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=" +"\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the " +"basics." msgstr "" #. Tag: para #: hardware.xml:915 #, no-c-format -msgid "The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory Management Unit) and a FPU (floating-point unit). This includes the 68020 with an external 68851 PMMU, the 68030, and better, and excludes the <quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink> for complete details." +msgid "" +"The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory " +"Management Unit) and a FPU (floating-point unit). This includes the 68020 " +"with an external 68851 PMMU, the 68030, and better, and excludes the " +"<quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-" +"faq;\">Linux/m68k FAQ</ulink> for complete details." msgstr "" #. Tag: para #: hardware.xml:923 #, no-c-format -msgid "There are four major supported <emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two systems to which Linux was ported; in keeping, they are also the two most well-supported Debian ports. The Macintosh line is supported incompletely, both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> for project status and supported hardware. The BVM and Motorola single board VMEbus computers are the most recent addition to the list of machines supported by Debian. Ports to other &architecture; architectures, such as the Sun3 architecture and NeXT black box, are underway but not yet supported by Debian." +msgid "" +"There are four major supported <emphasis>&architecture;</emphasis> flavors: " +"Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two " +"systems to which Linux was ported; in keeping, they are also the two most " +"well-supported Debian ports. The Macintosh line is supported incompletely, " +"both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;" +"\">Linux m68k for Macintosh</ulink> for project status and supported " +"hardware. The BVM and Motorola single board VMEbus computers are the most " +"recent addition to the list of machines supported by Debian. Ports to other " +"&architecture; architectures, such as the Sun3 architecture and NeXT black " +"box, are underway but not yet supported by Debian." msgstr "" #. Tag: para #: hardware.xml:950 #, no-c-format -msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." +msgid "" +"Debian on &arch-title; supports the following platforms: <itemizedlist> " +"<listitem><para> SGI IP22: this platform includes the SGI machines Indy, " +"Indigo 2 and Challenge S. Since these machines are very similar, whenever " +"this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant " +"as well. </para></listitem> <listitem><para> SGI IP32: this platform is " +"generally known as SGI O2. </para></listitem> <listitem><para> Broadcom " +"BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom " +"based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> " +"Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board " +"from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </" +"itemizedlist> Complete information regarding supported mips/mipsel machines " +"can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</" +"ulink>. In the following, only the systems supported by the Debian installer " +"will be covered. If you are looking for support for other subarchitectures, " +"please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-" +"listname; mailing list</ulink>." msgstr "" #. Tag: para #: hardware.xml:991 #, no-c-format -msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the Debian installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported. The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." +msgid "" +"On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and " +"R5000 processors are supported by the Debian installation system on big " +"endian MIPS. On SGI IP32, currently only systems based on the R5000 are " +"supported. The Broadcom BCM91250A evaluation board comes with an SB1 1250 " +"chip with two cores which are supported in SMP mode by this installer. " +"Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with " +"four cores which are supported in SMP mode." msgstr "" #. Tag: para #: hardware.xml:1001 #, no-c-format -msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture." +msgid "" +"Some MIPS machines can be operated in both big and little endian mode. For " +"little endian MIPS, please read the documentation for the mipsel " +"architecture." msgstr "" #. Tag: para #: hardware.xml:1018 #, no-c-format -msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." +msgid "" +"Debian on &arch-title; supports the following platforms: <itemizedlist> " +"<listitem><para> DECstation: various models of the DECstation are supported. " +"</para></listitem> <listitem><para> Cobalt Microserver: only MIPS based " +"Cobalt machines are covered here. This includes the Cobalt Qube 2700 " +"(Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></" +"listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form " +"factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </" +"para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an " +"ATX form factor evaluation board from Broadcom based on the quad-core SB1A " +"1480 CPU. </para></listitem> </itemizedlist> Complete information regarding " +"supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-" +"mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems " +"supported by the Debian installer will be covered. If you are looking for " +"support for other subarchitectures, please contact the <ulink url=\"&url-" +"list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." msgstr "" #. Tag: title @@ -1912,8 +2043,14 @@ msgstr "CPU/Gép típusok" #. Tag: para #: hardware.xml:1060 #, no-c-format -msgid "Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by the Debian installation system on little endian MIPS. The Debian installation system works on the following machines:" -msgstr "A Debian telepítő jelenleg csak az R3000 és R4000/R4400 CPU-s DECstation gépeket támogatja a kis-végű MIPS gépek közül. A Debian telepítő rendszer az alábbi gépeken működik:" +msgid "" +"Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by " +"the Debian installation system on little endian MIPS. The Debian " +"installation system works on the following machines:" +msgstr "" +"A Debian telepítő jelenleg csak az R3000 és R4000/R4400 CPU-s DECstation " +"gépeket támogatja a kis-végű MIPS gépek közül. A Debian telepítő rendszer az " +"alábbi gépeken működik:" #. Tag: entry #: hardware.xml:1072 @@ -1946,17 +2083,13 @@ msgid "DECstation 5000/1xx" msgstr "DECstation 5000/1xx" #. Tag: entry -#: hardware.xml:1080 -#: hardware.xml:1090 -#: hardware.xml:1095 -#: hardware.xml:1105 +#: hardware.xml:1080 hardware.xml:1090 hardware.xml:1095 hardware.xml:1105 #, no-c-format msgid "R3000" msgstr "R3000" #. Tag: entry -#: hardware.xml:1081 -#: hardware.xml:1086 +#: hardware.xml:1081 hardware.xml:1086 #, no-c-format msgid "3MIN" msgstr "3MIN" @@ -1968,8 +2101,7 @@ msgid "DECstation 5000/150" msgstr "DECstation 5000/150" #. Tag: entry -#: hardware.xml:1085 -#: hardware.xml:1110 +#: hardware.xml:1085 hardware.xml:1110 #, no-c-format msgid "R4000" msgstr "R4000" @@ -1993,8 +2125,7 @@ msgid "DECstation 5000/240" msgstr "DECstation 5000/240" #. Tag: entry -#: hardware.xml:1096 -#: hardware.xml:1101 +#: hardware.xml:1096 hardware.xml:1101 #, no-c-format msgid "3MAX+" msgstr "3MAX+" @@ -2018,8 +2149,7 @@ msgid "Personal DECstation 5000/xx" msgstr "Personal DECstation 5000/xx" #. Tag: entry -#: hardware.xml:1106 -#: hardware.xml:1111 +#: hardware.xml:1106 hardware.xml:1111 #, no-c-format msgid "Maxine" msgstr "Maxine" @@ -2033,13 +2163,23 @@ msgstr "Personal DECstation 5000/50" #. Tag: para #: hardware.xml:1116 #, no-c-format -msgid "All Cobalt machines are supported. In the past, only machines with a serial console were supported (that is, all machines except for the Qube 2700, aka Qube1). However, installations are now also possible through SSH." -msgstr "Minden Cobalt gép támogatott. Régen csak a soros konzolos gépek voltak támogatottak (vagyis minden, kivéve a Qube 2700 más nevén Qube1 gépet). De ma már ez is megoldott az SSH lehetőséggel." +msgid "" +"All Cobalt machines are supported. In the past, only machines with a serial " +"console were supported (that is, all machines except for the Qube 2700, aka " +"Qube1). However, installations are now also possible through SSH." +msgstr "" +"Minden Cobalt gép támogatott. Régen csak a soros konzolos gépek voltak " +"támogatottak (vagyis minden, kivéve a Qube 2700 más nevén Qube1 gépet). De " +"ma már ez is megoldott az SSH lehetőséggel." #. Tag: para #: hardware.xml:1123 #, no-c-format -msgid "The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." +msgid "" +"The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two " +"cores which are supported in SMP mode by this installer. Similarly, the " +"BCM91480B evaluation board contains an SB1A 1480 chip with four cores which " +"are supported in SMP mode." msgstr "" #. Tag: title @@ -2051,16 +2191,30 @@ msgstr "" #. Tag: para #: hardware.xml:1134 #, no-c-format -msgid "A serial console is available on all supported DECstations (9600 bps, 8N1). To use the serial console, you have to boot the installer image with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter (with <replaceable>x</replaceable> being the number of the serial port you have your terminal connected to — usually <literal>2</literal>, but <literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available with the PMAG-BA and the PMAGB-B graphics options." +msgid "" +"A serial console is available on all supported DECstations (9600 bps, 8N1). " +"To use the serial console, you have to boot the installer image with the " +"<literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter " +"(with <replaceable>x</replaceable> being the number of the serial port you " +"have your terminal connected to — usually <literal>2</literal>, but " +"<literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ " +"(DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available " +"with the PMAG-BA and the PMAGB-B graphics options." msgstr "" #. Tag: para #: hardware.xml:1145 #, no-c-format msgid "" -"If you have a Linux system to use as serial terminal, an easy way is to run <command>cu</command><footnote> <para> In Woody this command was part of the <classname>uucp</classname> package, but in later releases it is available as a separate package. </para> </footnote> on it. Example: <informalexample><screen>\n" +"If you have a Linux system to use as serial terminal, an easy way is to run " +"<command>cu</command><footnote> <para> In Woody this command was part of the " +"<classname>uucp</classname> package, but in later releases it is available " +"as a separate package. </para> </footnote> on it. Example: " +"<informalexample><screen>\n" "$ cu -l /dev/ttyS1 -s 9600\n" -"</screen></informalexample> where the option <literal>-l</literal> (line) sets the serial port to use and <literal>-s</literal> (speed) sets the speed for the connection (9600 bits per second)." +"</screen></informalexample> where the option <literal>-l</literal> (line) " +"sets the serial port to use and <literal>-s</literal> (speed) sets the speed " +"for the connection (9600 bits per second)." msgstr "" #. Tag: para @@ -2072,13 +2226,21 @@ msgstr "" #. Tag: para #: hardware.xml:1177 #, no-c-format -msgid "There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga Power-UP System), and CHRP machines. Each subarchitecture has its own boot methods. In addition, there are four different kernel flavours, supporting different CPU variants." +msgid "" +"There are four major supported <emphasis>&architecture;</emphasis> " +"subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga " +"Power-UP System), and CHRP machines. Each subarchitecture has its own boot " +"methods. In addition, there are four different kernel flavours, supporting " +"different CPU variants." msgstr "" #. Tag: para #: hardware.xml:1185 #, no-c-format -msgid "Ports to other <emphasis>&architecture;</emphasis> architectures, such as the Be-Box and MBX architecture, are underway but not yet supported by Debian. We may have a 64-bit port in the future." +msgid "" +"Ports to other <emphasis>&architecture;</emphasis> architectures, such as " +"the Be-Box and MBX architecture, are underway but not yet supported by " +"Debian. We may have a 64-bit port in the future." msgstr "" #. Tag: title @@ -2090,7 +2252,9 @@ msgstr "" #. Tag: para #: hardware.xml:1195 #, no-c-format -msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:" +msgid "" +"There are four flavours of the powerpc kernel in Debian, based on the CPU " +"type:" msgstr "" #. Tag: term @@ -2102,7 +2266,10 @@ msgstr "" #. Tag: para #: hardware.xml:1203 #, no-c-format -msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors." +msgid "" +"Most systems use this kernel flavour, which supports the PowerPC 601, 603, " +"604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and " +"including the one marketed as G4 use one of these processors." msgstr "" #. Tag: term @@ -2120,19 +2287,26 @@ msgstr "" #. Tag: para #: hardware.xml:1218 #, no-c-format -msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270." +msgid "" +"The POWER3 processor is used in older IBM 64-bit server systems: known " +"models include the IntelliStation POWER Model 265, the pSeries 610 and 640, " +"and the RS/6000 7044-170, 7043-260, and 7044-270." msgstr "" #. Tag: para #: hardware.xml:1224 #, no-c-format -msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690." +msgid "" +"The POWER4 processor is used in more recent IBM 64-bit server systems: known " +"models include the pSeries 615, 630, 650, 655, 670, and 690." msgstr "" #. Tag: para #: hardware.xml:1229 #, no-c-format -msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour." +msgid "" +"Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 " +"architecture, and use this kernel flavour." msgstr "" #. Tag: term @@ -2156,7 +2330,9 @@ msgstr "" #. Tag: para #: hardware.xml:1248 #, no-c-format -msgid "This kernel flavour supports the Amiga Power-UP System, though it is currently disabled." +msgid "" +"This kernel flavour supports the Amiga Power-UP System, though it is " +"currently disabled." msgstr "" #. Tag: title @@ -2168,32 +2344,46 @@ msgstr "" #. Tag: para #: hardware.xml:1263 #, no-c-format -msgid "Apple (and briefly a few other manufacturers — Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by Debian), OldWorld, and NewWorld." +msgid "" +"Apple (and briefly a few other manufacturers — Power Computing, for " +"example) made a series of Macintosh computers based on the PowerPC " +"processor. For purposes of architecture support, they are categorized as " +"NuBus (not supported by Debian), OldWorld, and NewWorld." msgstr "" #. Tag: para #: hardware.xml:1270 #, no-c-format -msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld." +msgid "" +"OldWorld systems are most Power Macintoshes with a floppy drive and a PCI " +"bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld " +"machines. Those pre-iMac PowerPC models from Apple use a four digit naming " +"scheme, except for the beige colored G3 systems, which are also OldWorld." msgstr "" #. Tag: para #: hardware.xml:1278 #, no-c-format -msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards." +msgid "" +"The so called NewWorld PowerMacs are any PowerMacs in translucent colored " +"plastic cases and later models. That includes all iMacs, iBooks, G4 systems, " +"blue colored G3 systems, and most PowerBooks manufactured in and after 1999. " +"The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</" +"quote> system for MacOS, and were manufactured from mid-1998 onwards." msgstr "" #. Tag: para #: hardware.xml:1286 #, no-c-format -msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>." +msgid "" +"Specifications for Apple hardware are available at <ulink url=\"http://www." +"info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older " +"hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/" +"index.html\">AppleSpec Legacy</ulink>." msgstr "" #. Tag: entry -#: hardware.xml:1302 -#: hardware.xml:1437 -#: hardware.xml:1481 -#: hardware.xml:1510 +#: hardware.xml:1302 hardware.xml:1437 hardware.xml:1481 hardware.xml:1510 #, no-c-format msgid "Model Name/Number" msgstr "" @@ -2217,22 +2407,10 @@ msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:1311 -#: hardware.xml:1314 -#: hardware.xml:1317 -#: hardware.xml:1320 -#: hardware.xml:1323 -#: hardware.xml:1326 -#: hardware.xml:1329 -#: hardware.xml:1332 -#: hardware.xml:1335 -#: hardware.xml:1338 -#: hardware.xml:1341 -#: hardware.xml:1344 -#: hardware.xml:1347 -#: hardware.xml:1350 -#: hardware.xml:1353 -#: hardware.xml:1356 +#: hardware.xml:1311 hardware.xml:1314 hardware.xml:1317 hardware.xml:1320 +#: hardware.xml:1323 hardware.xml:1326 hardware.xml:1329 hardware.xml:1332 +#: hardware.xml:1335 hardware.xml:1338 hardware.xml:1341 hardware.xml:1344 +#: hardware.xml:1347 hardware.xml:1350 hardware.xml:1353 hardware.xml:1356 #, no-c-format msgid "NewWorld" msgstr "NewWorld" @@ -2334,22 +2512,10 @@ msgid "Performa 4400, 54xx, 5500" msgstr "Performa 4400, 54xx, 5500" #. Tag: entry -#: hardware.xml:1359 -#: hardware.xml:1362 -#: hardware.xml:1365 -#: hardware.xml:1368 -#: hardware.xml:1371 -#: hardware.xml:1374 -#: hardware.xml:1377 -#: hardware.xml:1380 -#: hardware.xml:1383 -#: hardware.xml:1386 -#: hardware.xml:1389 -#: hardware.xml:1392 -#: hardware.xml:1398 -#: hardware.xml:1401 -#: hardware.xml:1407 -#: hardware.xml:1413 +#: hardware.xml:1359 hardware.xml:1362 hardware.xml:1365 hardware.xml:1368 +#: hardware.xml:1371 hardware.xml:1374 hardware.xml:1377 hardware.xml:1380 +#: hardware.xml:1383 hardware.xml:1386 hardware.xml:1389 hardware.xml:1392 +#: hardware.xml:1398 hardware.xml:1401 hardware.xml:1407 hardware.xml:1413 #: hardware.xml:1419 #, no-c-format msgid "OldWorld" @@ -2464,8 +2630,7 @@ msgid "APS Tech M*Power 604e/2000" msgstr "APS Tech M*Power 604e/2000" #. Tag: entry -#: hardware.xml:1417 -#: hardware.xml:1443 +#: hardware.xml:1417 hardware.xml:1443 #, no-c-format msgid "Motorola" msgstr "Motorola" @@ -2513,8 +2678,7 @@ msgid "MCP(N)750" msgstr "MCP(N)750" #. Tag: entry -#: hardware.xml:1456 -#: hardware.xml:1487 +#: hardware.xml:1456 hardware.xml:1487 #, no-c-format msgid "IBM RS/6000" msgstr "IBM RS/6000" @@ -2594,7 +2758,17 @@ msgstr "Nubus PowerMac al-architektúra (nem-támogatott)" #. Tag: para #: hardware.xml:1527 #, no-c-format -msgid "NuBus systems are not currently supported by Debian/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which Debian does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>." +msgid "" +"NuBus systems are not currently supported by Debian/powerpc. The monolithic " +"Linux/PPC kernel architecture does not have support for these machines; " +"instead, one must use the MkLinux Mach microkernel, which Debian does not " +"yet support. These include the following: <itemizedlist> <listitem><para> " +"Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> " +"Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook " +"1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server " +"6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these " +"machines and limited support is available at <ulink url=\"http://nubus-pmac." +"sourceforge.net/\"></ulink>." msgstr "" #. Tag: title @@ -2606,19 +2780,33 @@ msgstr "" #. Tag: para #: hardware.xml:1566 #, no-c-format -msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950." +msgid "" +"Macintosh computers using the 680x0 series of processors are <emphasis>not</" +"emphasis> in the PowerPC family but are instead m68k machines. Those models " +"start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> " +"family, then the Centris series, and culminate in the Quadras and Performas. " +"These models usually have a Roman numeral or 3-digit model number such as " +"Mac IIcx, LCIII or Quadra 950." msgstr "" #. Tag: para #: hardware.xml:1575 #, no-c-format -msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD." +msgid "" +"This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, " +"IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, " +"580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra " +"(605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the " +"Performa 200-640CD." msgstr "" #. Tag: para #: hardware.xml:1583 #, no-c-format -msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)." +msgid "" +"In laptops, it started with the Mac Portable, then the PowerBook 100-190cs " +"and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, " +"please see the section above)." msgstr "" #. Tag: title @@ -2630,13 +2818,34 @@ msgstr "" #. Tag: para #: hardware.xml:1600 #, no-c-format -msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128.ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance." +msgid "" +"Complete information regarding supported S/390 and zSeries machines can be " +"found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/" +"redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: " +"Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128." +"ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the " +"developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries " +"are fully supported; Multiprise 2000, G3 and G4 machines are supported with " +"IEEE floating point emulation and thus degraded performance." msgstr "" #. Tag: para #: hardware.xml:1623 #, no-c-format -msgid "Currently the <emphasis>&architecture;</emphasis> port supports several types of Sparc systems. The most common identifiers for Sparc systems are sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not support very old sun4 hardware. However, the other systems are supported. Sun4d has been tested the least of these, so expect possible problems with regard to the kernel stability. Sun4c and Sun4m, the most common of the older Sparc hardware, includes such systems as SparcStation 1, 1+, IPC, IPX and the SparcStation LX, 5, 10, and 20, respectively. The UltraSPARC class systems fall under the sun4u identifier, and are supported using the sun4u set of install images. Some systems that fall under these supported identifiers are known to not be supported. Known unsupported systems are the AP1000 multicomputer and the Tadpole Sparcbook 1. See the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARCProcessors FAQ</ulink> for complete information." +msgid "" +"Currently the <emphasis>&architecture;</emphasis> port supports several " +"types of Sparc systems. The most common identifiers for Sparc systems are " +"sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not support very old " +"sun4 hardware. However, the other systems are supported. Sun4d has been " +"tested the least of these, so expect possible problems with regard to the " +"kernel stability. Sun4c and Sun4m, the most common of the older Sparc " +"hardware, includes such systems as SparcStation 1, 1+, IPC, IPX and the " +"SparcStation LX, 5, 10, and 20, respectively. The UltraSPARC class systems " +"fall under the sun4u identifier, and are supported using the sun4u set of " +"install images. Some systems that fall under these supported identifiers are " +"known to not be supported. Known unsupported systems are the AP1000 " +"multicomputer and the Tadpole Sparcbook 1. See the <ulink url=\"&url-sparc-" +"linux-faq;\">Linux for SPARCProcessors FAQ</ulink> for complete information." msgstr "" #. Tag: title @@ -2648,19 +2857,34 @@ msgstr "" #. Tag: para #: hardware.xml:1644 #, no-c-format -msgid "Some older Sun workstations, notably the Sun IPX and Sun IPC have memory banks located at fixed locations in physical memory. Thus if the banks are not filled gaps will exist in the physical memory space. The Linux installation requires a contiguous memory block into which to load the kernel and the initial RAMdisk. If this is not available a <quote>Data Access Exception</quote> will result." +msgid "" +"Some older Sun workstations, notably the Sun IPX and Sun IPC have memory " +"banks located at fixed locations in physical memory. Thus if the banks are " +"not filled gaps will exist in the physical memory space. The Linux " +"installation requires a contiguous memory block into which to load the " +"kernel and the initial RAMdisk. If this is not available a <quote>Data " +"Access Exception</quote> will result." msgstr "" #. Tag: para #: hardware.xml:1653 #, no-c-format -msgid "Thus you must configure the memory so that the lowest memory block is contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks are mapped in at 16Mb boundaries. In effect this means that you must have a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. In this case 4Mb is <emphasis>not</emphasis> sufficient." +msgid "" +"Thus you must configure the memory so that the lowest memory block is " +"contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks " +"are mapped in at 16Mb boundaries. In effect this means that you must have a " +"sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. In this " +"case 4Mb is <emphasis>not</emphasis> sufficient." msgstr "" #. Tag: para #: hardware.xml:1661 #, no-c-format -msgid "Example: In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS connectors]. You must therefore install the 16Mb SIMM in bank 0; it is then recommended to install the 4Mb SIMM in bank 2." +msgid "" +"Example: In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four " +"SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS " +"connectors]. You must therefore install the 16Mb SIMM in bank 0; it is then " +"recommended to install the 4Mb SIMM in bank 2." msgstr "" #. Tag: title @@ -2672,19 +2896,32 @@ msgstr "" #. Tag: para #: hardware.xml:1673 #, no-c-format -msgid "Especially in the case of older Sun workstations, it is very common for there to be an onboard framebuffer which has been superseded (for example the bwtwo on a sun IPC), and an SBUS card containing a later probably accelerated buffer is then plugged in to an SBUS slot. Under Solaris/SunOS this causes no problems because both cards are initialized." +msgid "" +"Especially in the case of older Sun workstations, it is very common for " +"there to be an onboard framebuffer which has been superseded (for example " +"the bwtwo on a sun IPC), and an SBUS card containing a later probably " +"accelerated buffer is then plugged in to an SBUS slot. Under Solaris/SunOS " +"this causes no problems because both cards are initialized." msgstr "" #. Tag: para #: hardware.xml:1682 #, no-c-format -msgid "However with Linux this can cause a problem, in that the boot PROM monitor may display its output on this additional card; however the linux kernel boot messages may then be directed to the original on board framebuffer, leaving <emphasis>no</emphasis> error messages on the screen, with the machine apparently stuck loading the RAMdisk." +msgid "" +"However with Linux this can cause a problem, in that the boot PROM monitor " +"may display its output on this additional card; however the linux kernel " +"boot messages may then be directed to the original on board framebuffer, " +"leaving <emphasis>no</emphasis> error messages on the screen, with the " +"machine apparently stuck loading the RAMdisk." msgstr "" #. Tag: para #: hardware.xml:1690 #, no-c-format -msgid "To avoid this problem, connect the monitor (if required) to the video card in the lowest numbered SBUS slot (on motherboard card counts as below external slots). Alternatively it is possible to use a serial console." +msgid "" +"To avoid this problem, connect the monitor (if required) to the video card " +"in the lowest numbered SBUS slot (on motherboard card counts as below " +"external slots). Alternatively it is possible to use a serial console." msgstr "" #. Tag: title @@ -2696,25 +2933,45 @@ msgstr "" #. Tag: para #: hardware.xml:1703 #, no-c-format -msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document." +msgid "" +"You should be using a VGA-compatible display interface for the console " +"terminal. Nearly every modern display card is compatible with VGA. Ancient " +"standards such CGA, MDA, or HGA should also work, assuming you do not " +"require X11 support. Note that X11 is not used during the installation " +"process described in this document." msgstr "" #. Tag: para #: hardware.xml:1711 #, no-c-format -msgid "Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian &release; ships with X.Org version &x11ver;." +msgid "" +"Debian's support for graphical interfaces is determined by the underlying " +"support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work " +"under X.Org. Details on supported graphics buses, cards, monitors, and " +"pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian " +"&release; ships with X.Org version &x11ver;." msgstr "" #. Tag: para #: hardware.xml:1720 #, no-c-format -msgid "The X.Org X11 window system is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." +msgid "" +"The X.Org X11 window system is only supported on the SGI Indy and the O2. " +"The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v " +"PCI slots and support VGA emulation or Linux framebuffer on a selected range " +"of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility " +"listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: para #: hardware.xml:1729 #, no-c-format -msgid "The X.Org X11 window system is supported on some DECstation models. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." +msgid "" +"The X.Org X11 window system is supported on some DECstation models. The " +"Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI " +"slots and support VGA emulation or Linux framebuffer on a selected range of " +"graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility " +"listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: title @@ -2726,14 +2983,14 @@ msgstr "" #. Tag: para #: hardware.xml:1741 #, no-c-format -msgid "Laptops are also supported. Laptops are often specialized or contain proprietary hardware. To see if your particular laptop works well with GNU/Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>" +msgid "" +"Laptops are also supported. Laptops are often specialized or contain " +"proprietary hardware. To see if your particular laptop works well with GNU/" +"Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>" msgstr "" #. Tag: title -#: hardware.xml:1752 -#: hardware.xml:1774 -#: hardware.xml:1794 -#: hardware.xml:1817 +#: hardware.xml:1752 hardware.xml:1774 hardware.xml:1794 hardware.xml:1817 #, no-c-format msgid "Multiple Processors" msgstr "" @@ -2741,49 +2998,92 @@ msgstr "" #. Tag: para #: hardware.xml:1753 #, no-c-format -msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with SMP support. This should not prevent installation, since the SMP kernel should boot on non-SMP systems; the kernel will simply cause a bit more overhead." +msgid "" +"Multi-processor support — also called <quote>symmetric multi-" +"processing</quote> or SMP — is available for this architecture. The " +"standard Debian &release; kernel image was compiled with SMP support. This " +"should not prevent installation, since the SMP kernel should boot on non-SMP " +"systems; the kernel will simply cause a bit more overhead." msgstr "" #. Tag: para #: hardware.xml:1761 #, no-c-format -msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." +msgid "" +"In order to optimize the kernel for single CPU systems, you'll have to " +"replace the standard Debian kernel. You can find a discussion of how to do " +"this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version " +"&kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-" +"option;</quote> in the <quote>&smp-config-section;</quote> section of the " +"kernel config." msgstr "" #. Tag: para #: hardware.xml:1776 #, no-c-format -msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems." +msgid "" +"Multi-processor support — also called <quote>symmetric multi-" +"processing</quote> or SMP — is available for this architecture. The " +"standard Debian &release; kernel image was compiled with <firstterm>SMP-" +"alternatives</firstterm> support. This means that the kernel will detect the " +"number of processors (or processor cores) and will automatically deactivate " +"SMP on uniprocessor systems." msgstr "" #. Tag: para #: hardware.xml:1785 #, no-c-format -msgid "The 486 flavour of the Debian kernel image packages for &arch-title; is not compiled with SMP support." +msgid "" +"The 486 flavour of the Debian kernel image packages for &arch-title; is not " +"compiled with SMP support." msgstr "" #. Tag: para #: hardware.xml:1795 #, no-c-format -msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. However, the standard Debian &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." +msgid "" +"Multi-processor support — also called <quote>symmetric multi-" +"processing</quote> or SMP — is available for this architecture. " +"However, the standard Debian &release; kernel image does not support SMP. " +"This should not prevent installation, since the standard, non-SMP kernel " +"should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para #: hardware.xml:1804 #, no-c-format -msgid "In order to take advantage of multiple processors, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." +msgid "" +"In order to take advantage of multiple processors, you'll have to replace " +"the standard Debian kernel. You can find a discussion of how to do this in " +"<xref linkend=\"kernel-baking\"/>. At this time (kernel version " +"&kernelversion;) the way you enable SMP is to select <quote>&smp-config-" +"option;</quote> in the <quote>&smp-config-section;</quote> section of the " +"kernel config." msgstr "" #. Tag: para #: hardware.xml:1818 #, no-c-format -msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture, and is supported by a precompiled Debian kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." +msgid "" +"Multi-processor support — also called <quote>symmetric multi-" +"processing</quote> or SMP — is available for this architecture, and is " +"supported by a precompiled Debian kernel image. Depending on your install " +"media, this SMP-capable kernel may or may not be installed by default. This " +"should not prevent installation, since the standard, non-SMP kernel should " +"boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para #: hardware.xml:1828 #, no-c-format -msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package. You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." +msgid "" +"In order to take advantage of multiple processors, you should check to see " +"if a kernel package that supports SMP is installed, and if not, choose an " +"appropriate kernel package. You can also build your own customized kernel to " +"support SMP. You can find a discussion of how to do this in <xref linkend=" +"\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way " +"you enable SMP is to select <quote>&smp-config-option;</quote> in the " +"<quote>&smp-config-section;</quote> section of the kernel config." msgstr "" #. Tag: title @@ -2795,8 +3095,19 @@ msgstr "Telepítő média" #. Tag: para #: hardware.xml:1851 #, no-c-format -msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used to install Debian. There is a whole chapter devoted media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section." -msgstr "E szakasz leírja, milyen média típusokat használhatsz a Debian telepítésére. Például, ha van egy flopi lemez meghajtód a gépen, telepíthető róla a Debian. Van egy egész fejezet, mely erről szól, a <xref linkend=\"install-methods\"/>, mely leírja minden média típus előnyét és hátrányát. Amennyiben odaugrasz, vissza is térhetsz majd ide." +msgid "" +"This section will help you determine which different media types you can use " +"to install Debian. For example, if you have a floppy disk drive on your " +"machine, it can be used to install Debian. There is a whole chapter devoted " +"media, <xref linkend=\"install-methods\"/>, which lists the advantages and " +"disadvantages of each media type. You may want to refer back to this page " +"once you reach that section." +msgstr "" +"E szakasz leírja, milyen média típusokat használhatsz a Debian telepítésére. " +"Például, ha van egy flopi lemez meghajtód a gépen, telepíthető róla a " +"Debian. Van egy egész fejezet, mely erről szól, a <xref linkend=\"install-" +"methods\"/>, mely leírja minden média típus előnyét és hátrányát. Amennyiben " +"odaugrasz, vissza is térhetsz majd ide." #. Tag: title #: hardware.xml:1862 @@ -2807,8 +3118,14 @@ msgstr "Flopik" #. Tag: para #: hardware.xml:1863 #, no-c-format -msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive." -msgstr "Lehet, hogy semmilyen más lehetőség nem áll rendelkezésedre, mint egy flopiról indítani. Ehhez csak egy nagy-sűrűségű (1440 kilobyte-os) 3,5 hüvelykes flopi meghajtó kell." +msgid "" +"In some cases, you'll have to do your first boot from floppy disks. " +"Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch " +"floppy drive." +msgstr "" +"Lehet, hogy semmilyen más lehetőség nem áll rendelkezésedre, mint egy " +"flopiról indítani. Ehhez csak egy nagy-sűrűségű (1440 kilobyte-os) 3,5 " +"hüvelykes flopi meghajtó kell." #. Tag: para #: hardware.xml:1869 @@ -2825,67 +3142,135 @@ msgstr "CD-ROM/DVD-ROM" #. Tag: para #: hardware.xml:1878 #, no-c-format -msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI." -msgstr "Ha e kézikönyvben azt látod: <quote>CD-ROM</quote>, az a CD-ROM és DVD-ROM eszközökre egyaránt vonatkozik, mert az operációs rendszer szempontjából ez ugyanaz, kivév egyes nagyon régi nem-szabványos CD-ROM meghajtókat, melyek nem SCSI vagy IDE/ATAPI elvűek." +msgid "" +"Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-" +"ROMs and DVD-ROMs, because both technologies are really the same from the " +"operating system's point of view, except for some very old nonstandard CD-" +"ROM drives which are neither SCSI nor IDE/ATAPI." +msgstr "" +"Ha e kézikönyvben azt látod: <quote>CD-ROM</quote>, az a CD-ROM és DVD-ROM " +"eszközökre egyaránt vonatkozik, mert az operációs rendszer szempontjából ez " +"ugyanaz, kivév egyes nagyon régi nem-szabványos CD-ROM meghajtókat, melyek " +"nem SCSI vagy IDE/ATAPI elvűek." #. Tag: para #: hardware.xml:1885 #, no-c-format -msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>." -msgstr "A CD-ROM alapú telepítés a legtöbb architektúrán támogatott. Az indítható CD-ROM lemezeket támogató gépeken teljesen <phrase arch=\"not-s390\">flopi-mentes</phrase> <phrase arch=\"s390\">szalag-mentes</phrase> telepítés végezhető. Még ha a rendszer nem is támogatja a CD-ROM lemezről indítást, a CD-ROM más módokkal együtt használható a telepítésre, miután az indítás megtörtént másképpen; lásd a <xref linkend=\"boot-installer\"/> részt." +msgid "" +"CD-ROM based installation is supported for some architectures. On machines " +"which support bootable CD-ROMs, you should be able to do a completely " +"<phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-" +"less</phrase> installation. Even if your system doesn't support booting from " +"a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to " +"install your system, once you've booted up by other means; see <xref linkend=" +"\"boot-installer\"/>." +msgstr "" +"A CD-ROM alapú telepítés a legtöbb architektúrán támogatott. Az indítható CD-" +"ROM lemezeket támogató gépeken teljesen <phrase arch=\"not-s390\">flopi-" +"mentes</phrase> <phrase arch=\"s390\">szalag-mentes</phrase> telepítés " +"végezhető. Még ha a rendszer nem is támogatja a CD-ROM lemezről indítást, a " +"CD-ROM más módokkal együtt használható a telepítésre, miután az indítás " +"megtörtént másképpen; lásd a <xref linkend=\"boot-installer\"/> részt." #. Tag: para #: hardware.xml:1897 #, no-c-format -msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the boot disks (such as Mitsumi and Matsushita drives). However, these models might require special boot parameters or other massaging to get them to work, and booting off these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux." +msgid "" +"Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard " +"CD interfaces supported by Linux are supported by the boot disks (such as " +"Mitsumi and Matsushita drives). However, these models might require special " +"boot parameters or other massaging to get them to work, and booting off " +"these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;" +"\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs " +"with Linux." msgstr "" #. Tag: para #: hardware.xml:1907 #, no-c-format -msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." +msgid "" +"USB CD-ROM drives are also supported, as are FireWire devices that are " +"supported by the ohci1394 and sbp2 drivers." msgstr "" #. Tag: para #: hardware.xml:1912 #, no-c-format -msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as the controller is supported by the SRM console. This rules out many add-on controller cards, but most integrated IDE and SCSI chips and controller cards that were provided by the manufacturer can be expected to work. To find out whether your device is supported from the SRM console, see the <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>." +msgid "" +"Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as " +"the controller is supported by the SRM console. This rules out many add-on " +"controller cards, but most integrated IDE and SCSI chips and controller " +"cards that were provided by the manufacturer can be expected to work. To " +"find out whether your device is supported from the SRM console, see the " +"<ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>." msgstr "" #. Tag: para #: hardware.xml:1921 #, no-c-format -msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-ROMs are also supported." +msgid "" +"IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-" +"ROMs are also supported." msgstr "" #. Tag: para #: hardware.xml:1926 #, no-c-format -msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card." +msgid "" +"On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of " +"working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM " +"drives sold on the PC market do not have this capability. If your CD-ROM " +"drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</" +"quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. " +"To start the install, simply choose the <quote>System installation</quote> " +"entry in the firmware. The Broadcom BCM91250A supports standard IDE devices, " +"including CD-ROM drives, but CD images for this platform are currently not " +"provided because the firmware doesn't recognize CD drives. In order to " +"install Debian on an Broadcom BCM91480B evaluation board, you need an PCI " +"IDE, SATA or SCSI card." msgstr "" #. Tag: para #: hardware.xml:1941 #, no-c-format -msgid "On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position." +msgid "" +"On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive capable of " +"working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM " +"drives sold on the PC market do not have this capability. If your CD-ROM " +"drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</" +"quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position." msgstr "" #. Tag: para #: hardware.xml:1950 #, no-c-format -msgid "CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal DECstation 5000/50)." +msgid "" +"CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-" +"based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal " +"DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the " +"R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal " +"DECstation 5000/50)." msgstr "" #. Tag: para #: hardware.xml:1959 #, no-c-format -msgid "To boot from CD, issue the command <userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware prompt, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot (3 on most DECstations) and <replaceable>id</replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass additional parameters, they can optionally be appended with the following syntax:" +msgid "" +"To boot from CD, issue the command <userinput>boot <replaceable>#</" +"replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware " +"prompt, where <replaceable>#</replaceable> is the number of the TurboChannel " +"device from which to boot (3 on most DECstations) and <replaceable>id</" +"replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass " +"additional parameters, they can optionally be appended with the following " +"syntax:" msgstr "" #. Tag: userinput #: hardware.xml:1971 #, no-c-format -msgid "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=value1 param2=value2 ..." +msgid "" +"boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> " +"param1=value1 param2=value2 ..." msgstr "" #. Tag: title @@ -2897,19 +3282,26 @@ msgstr "" #. Tag: para #: hardware.xml:1980 #, no-c-format -msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk." +msgid "" +"Booting the installation system directly from a hard disk is another option " +"for many architectures. This will require some other operating system to " +"load the installer onto the hard disk." msgstr "" #. Tag: para #: hardware.xml:1986 #, no-c-format -msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines." +msgid "" +"In fact, installation from your local disk is the preferred installation " +"technique for most &architecture; machines." msgstr "" #. Tag: para #: hardware.xml:1991 #, no-c-format -msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)." +msgid "" +"Although the &arch-title; does not allow booting from SunOS (Solaris), you " +"can install from a SunOS partition (UFS slices)." msgstr "" #. Tag: title @@ -2921,7 +3313,13 @@ msgstr "" #. Tag: para #: hardware.xml:2001 #, no-c-format -msgid "Many Debian boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives." +msgid "" +"Many Debian boxes need their floppy and/or CD-ROM drives only for setting up " +"the system and for rescue purposes. If you operate some servers, you will " +"probably already have thought about omitting those drives and using an USB " +"memory stick for installing and (when necessary) for recovering the system. " +"This is also useful for small systems which have no room for unnecessary " +"drives." msgstr "" #. Tag: title @@ -2933,19 +3331,26 @@ msgstr "" #. Tag: para #: hardware.xml:2015 #, no-c-format -msgid "You can also <emphasis>boot</emphasis> your system over the network. <phrase arch=\"mips\">This is the preferred installation technique for Mips.</phrase>" +msgid "" +"You can also <emphasis>boot</emphasis> your system over the network. <phrase " +"arch=\"mips\">This is the preferred installation technique for Mips.</phrase>" msgstr "" #. Tag: para #: hardware.xml:2021 #, no-c-format -msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." +msgid "" +"Diskless installation, using network booting from a local area network and " +"NFS-mounting of all local filesystems, is another option." msgstr "" #. Tag: para #: hardware.xml:2026 #, no-c-format -msgid "After the operating system kernel is installed, you can install the rest of your system via any sort of network connection (including PPP after installation of the base system), via FTP or HTTP." +msgid "" +"After the operating system kernel is installed, you can install the rest of " +"your system via any sort of network connection (including PPP after " +"installation of the base system), via FTP or HTTP." msgstr "" #. Tag: title @@ -2957,7 +3362,12 @@ msgstr "" #. Tag: para #: hardware.xml:2037 #, no-c-format -msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of the manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." +msgid "" +"If you are running another Unix-like system, you could use it to install " +"&debian; without using the &d-i; described in the rest of the manual. This " +"kind of install may be useful for users with otherwise unsupported hardware " +"or on hosts which can't afford downtime. If you are interested in this " +"technique, skip to the <xref linkend=\"linux-upgrade\"/>." msgstr "" #. Tag: title @@ -2969,61 +3379,108 @@ msgstr "" #. Tag: para #: hardware.xml:2051 #, no-c-format -msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware." +msgid "" +"The Debian boot disks contain a kernel which is built to maximize the number " +"of systems it runs on. Unfortunately, this makes for a larger kernel, which " +"includes many drivers that won't be used for your machine (see <xref linkend=" +"\"kernel-baking\"/> to learn how to build your own kernel). Support for the " +"widest possible range of devices is desirable in general, to ensure that " +"Debian can be installed on the widest array of hardware." msgstr "" #. Tag: para #: hardware.xml:2061 #, no-c-format -msgid "Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." +msgid "" +"Generally, the Debian installation system includes support for floppies, IDE " +"drives, IDE floppies, parallel port IDE devices, SCSI controllers and " +"drives, USB, and FireWire. The supported file systems include FAT, Win-32 " +"FAT extensions (VFAT) and NTFS." msgstr "" #. Tag: para #: hardware.xml:2068 #, no-c-format -msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or ATA — are supported. Very old 8–bit hard disk controllers used in the IBM XT computer are supported only as a module. SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." +msgid "" +"Disk interfaces that emulate the <quote>AT</quote> hard disk interface " +"— often called MFM, RLL, IDE, or ATA — are supported. Very old " +"8–bit hard disk controllers used in the IBM XT computer are supported " +"only as a module. SCSI disk controllers from many different manufacturers " +"are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware " +"Compatibility HOWTO</ulink> for more details." msgstr "" #. Tag: para #: hardware.xml:2078 #, no-c-format -msgid "Pretty much all storage systems supported by the Linux kernel are supported by the Debian installation system. Note that the current Linux kernel does not support floppies on the Macintosh at all, and the Debian installation system doesn't support floppies for Amigas. Also supported on the Atari is the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) file system. Amigas support the FAT file system, and HFS as a module." +msgid "" +"Pretty much all storage systems supported by the Linux kernel are supported " +"by the Debian installation system. Note that the current Linux kernel does " +"not support floppies on the Macintosh at all, and the Debian installation " +"system doesn't support floppies for Amigas. Also supported on the Atari is " +"the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) " +"file system. Amigas support the FAT file system, and HFS as a module." msgstr "" #. Tag: para #: hardware.xml:2088 #, no-c-format -msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel." +msgid "" +"Any storage system supported by the Linux kernel is also supported by the " +"boot system. The following SCSI drivers are supported in the default kernel: " +"<itemizedlist> <listitem><para> Sparc ESP </para></listitem> " +"<listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec " +"AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></" +"listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also " +"supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC " +"Processors FAQ</ulink> for more information on SPARC hardware supported by " +"the Linux kernel." msgstr "" #. Tag: para #: hardware.xml:2121 #, no-c-format -msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This includes both SCSI and IDE disks. Note, however, that on many systems, the SRM console is unable to boot from IDE drives, and the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;\"></ulink> for more information on booting the Jensen)" +msgid "" +"Any storage system supported by the Linux kernel is also supported by the " +"boot system. This includes both SCSI and IDE disks. Note, however, that on " +"many systems, the SRM console is unable to boot from IDE drives, and the " +"Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;" +"\"></ulink> for more information on booting the Jensen)" msgstr "" #. Tag: para #: hardware.xml:2130 #, no-c-format -msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all." +msgid "" +"Any storage system supported by the Linux kernel is also supported by the " +"boot system. Note that the current Linux kernel does not support floppies on " +"CHRP systems at all." msgstr "" #. Tag: para #: hardware.xml:2136 #, no-c-format -msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive." +msgid "" +"Any storage system supported by the Linux kernel is also supported by the " +"boot system. Note that the current Linux kernel does not support the floppy " +"drive." msgstr "" #. Tag: para #: hardware.xml:2142 #, no-c-format -msgid "Any storage system supported by the Linux kernel is also supported by the boot system." +msgid "" +"Any storage system supported by the Linux kernel is also supported by the " +"boot system." msgstr "" #. Tag: para #: hardware.xml:2147 #, no-c-format -msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)." +msgid "" +"Any storage system supported by the Linux kernel is also supported by the " +"boot system. This means that FBA and ECKD DASDs are supported with the old " +"Linux disk layout (ldl) and the new common S/390 disk layout (cdl)." msgstr "" #. Tag: title @@ -3035,37 +3492,55 @@ msgstr "" #. Tag: para #: hardware.xml:2165 #, no-c-format -msgid "Linux supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system." +msgid "" +"Linux supports a large variety of hardware devices such as mice, printers, " +"scanners, PCMCIA and USB devices. However, most of these devices are not " +"required while installing the system." msgstr "" #. Tag: para #: hardware.xml:2171 #, no-c-format -msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)." +msgid "" +"USB hardware generally works fine, only some USB keyboards may require " +"additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)." msgstr "" #. Tag: para #: hardware.xml:2177 #, no-c-format -msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux." +msgid "" +"Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware " +"Compatibility HOWTO</ulink> to determine whether your specific hardware is " +"supported by Linux." msgstr "" #. Tag: para #: hardware.xml:2183 #, no-c-format -msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP." +msgid "" +"Package installations from XPRAM and tape are not supported by this system. " +"All packages that you want to install need to be available on a DASD or over " +"the network using NFS, HTTP or FTP." msgstr "" #. Tag: para #: hardware.xml:2189 #, no-c-format -msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots." +msgid "" +"The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 " +"bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation " +"board features four 64 bit PCI slots." msgstr "" #. Tag: para #: hardware.xml:2195 #, no-c-format -msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." +msgid "" +"The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 " +"bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation " +"board features four 64 bit PCI slots. The Cobalt RaQ has no support for " +"additional devices but the Qube has one PCI slot." msgstr "" #. Tag: title @@ -3077,25 +3552,42 @@ msgstr "" #. Tag: para #: hardware.xml:2207 #, no-c-format -msgid "There are several vendors, who ship systems with Debian or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux." +msgid "" +"There are several vendors, who ship systems with Debian or other " +"distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</" +"ulink>. You might pay more for the privilege, but it does buy a level of " +"peace of mind, since you can be sure that the hardware is well-supported by " +"GNU/Linux." msgstr "" #. Tag: para #: hardware.xml:2215 #, no-c-format -msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all." +msgid "" +"Unfortunately, it's quite rare to find any vendor shipping new &arch-title; " +"machines at all." msgstr "" #. Tag: para #: hardware.xml:2220 #, no-c-format -msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that." +msgid "" +"If you do have to buy a machine with Windows bundled, carefully read the " +"software license that comes with Windows; you may be able to reject the " +"license and obtain a rebate from your vendor. Searching the Internet for " +"<quote>windows refund</quote> may get you some useful information to help " +"with that." msgstr "" #. Tag: para #: hardware.xml:2228 #, no-c-format -msgid "Whether or not you are purchasing a system with Linux bundled, or even a used system, it is still important to check that your hardware is supported by the Linux kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a Linux system. Support Linux-friendly hardware vendors." +msgid "" +"Whether or not you are purchasing a system with Linux bundled, or even a " +"used system, it is still important to check that your hardware is supported " +"by the Linux kernel. Check if your hardware is listed in the references " +"found above. Let your salesperson (if any) know that you're shopping for a " +"Linux system. Support Linux-friendly hardware vendors." msgstr "" #. Tag: title @@ -3107,19 +3599,34 @@ msgstr "" #. Tag: para #: hardware.xml:2240 #, no-c-format -msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the Linux source code." +msgid "" +"Some hardware manufacturers simply won't tell us how to write drivers for " +"their hardware. Others won't allow us access to the documentation without a " +"non-disclosure agreement that would prevent us from releasing the Linux " +"source code." msgstr "" #. Tag: para #: hardware.xml:2247 #, no-c-format -msgid "Another example is the proprietary hardware in the older Macintosh line. In fact, no specifications or documentation have ever been released for any Macintosh hardware, most notably the ADB controller (used by the mouse and keyboard), the floppy controller, and all acceleration and CLUT manipulation of the video hardware (though we do now support CLUT manipulation on nearly all internal video chips). In a nutshell, this explains why the Macintosh Linux port lags behind other Linux ports." +msgid "" +"Another example is the proprietary hardware in the older Macintosh line. In " +"fact, no specifications or documentation have ever been released for any " +"Macintosh hardware, most notably the ADB controller (used by the mouse and " +"keyboard), the floppy controller, and all acceleration and CLUT manipulation " +"of the video hardware (though we do now support CLUT manipulation on nearly " +"all internal video chips). In a nutshell, this explains why the Macintosh " +"Linux port lags behind other Linux ports." msgstr "" #. Tag: para #: hardware.xml:2258 #, no-c-format -msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under Linux. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market." +msgid "" +"Since we haven't been granted access to the documentation on these devices, " +"they simply won't work under Linux. You can help by asking the manufacturers " +"of such hardware to release the documentation. If enough people ask, they " +"will realize that the free software community is an important market." msgstr "" #. Tag: title @@ -3131,19 +3638,50 @@ msgstr "" #. Tag: para #: hardware.xml:2271 #, no-c-format -msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence." +msgid "" +"A disturbing trend is the proliferation of Windows-specific modems and " +"printers. In some cases these are specially designed to be operated by the " +"Microsoft Windows operating system and bear the legend <quote>WinModem</" +"quote> or <quote>Made especially for Windows-based computers</quote>. This " +"is generally done by removing the embedded processors of the hardware and " +"shifting the work they do over to a Windows driver that is run by your " +"computer's main CPU. This strategy makes the hardware less expensive, but " +"the savings are often <emphasis>not</emphasis> passed on to the user and " +"this hardware may even be more expensive than equivalent devices that retain " +"their embedded intelligence." msgstr "" #. Tag: para #: hardware.xml:2284 #, no-c-format -msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes its being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." +msgid "" +"You should avoid Windows-specific hardware for two reasons. The first is " +"that the manufacturers do not generally make the resources available to " +"write a Linux driver. Generally, the hardware and software interface to the " +"device is proprietary, and documentation is not available without a non-" +"disclosure agreement, if it is available at all. This precludes its being " +"used for free software, since free software writers disclose the source code " +"of their programs. The second reason is that when devices like these have " +"had their embedded processors removed, the operating system must perform the " +"work of the embedded processors, often at <emphasis>real-time</emphasis> " +"priority, and thus the CPU is not available to run your programs while it is " +"driving these devices. Since the typical Windows user does not multi-process " +"as intensively as a Linux user, the manufacturers hope that the Windows user " +"simply won't notice the burden this hardware places on their CPU. However, " +"any multi-processing operating system, even Windows 2000 or XP, suffers from " +"degraded performance when peripheral manufacturers skimp on the embedded " +"processing power of their hardware." msgstr "" #. Tag: para #: hardware.xml:2305 #, no-c-format -msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>." +msgid "" +"You can help improve this situation by encouraging these manufacturers to " +"release the documentation and other resources necessary for us to program " +"their hardware, but the best strategy is simply to avoid this sort of " +"hardware until it is listed as working in the <ulink url=\"&url-hardware-" +"howto;\">Linux Hardware Compatibility HOWTO</ulink>." msgstr "" #. Tag: title @@ -3155,13 +3693,27 @@ msgstr "" #. Tag: para #: hardware.xml:2319 #, no-c-format -msgid "If you ask for Parity RAM in a computer store, you'll probably get <emphasis>virtual parity</emphasis> memory modules instead of <emphasis>true parity</emphasis> ones. Virtual parity SIMMs can often (but not always) be distinguished because they only have one more chip than an equivalent non-parity SIMM, and that one extra chip is smaller than all the others. Virtual-parity SIMMs work exactly like non-parity memory. They can't tell you when you have a single-bit RAM error the way true-parity SIMMs do in a motherboard that implements parity. Don't ever pay more for a virtual-parity SIMM than a non-parity one. Do expect to pay a little more for true-parity SIMMs, because you are actually buying one extra bit of memory for every 8 bits." +msgid "" +"If you ask for Parity RAM in a computer store, you'll probably get " +"<emphasis>virtual parity</emphasis> memory modules instead of <emphasis>true " +"parity</emphasis> ones. Virtual parity SIMMs can often (but not always) be " +"distinguished because they only have one more chip than an equivalent non-" +"parity SIMM, and that one extra chip is smaller than all the others. Virtual-" +"parity SIMMs work exactly like non-parity memory. They can't tell you when " +"you have a single-bit RAM error the way true-parity SIMMs do in a " +"motherboard that implements parity. Don't ever pay more for a virtual-parity " +"SIMM than a non-parity one. Do expect to pay a little more for true-parity " +"SIMMs, because you are actually buying one extra bit of memory for every 8 " +"bits." msgstr "" #. Tag: para #: hardware.xml:2334 #, no-c-format -msgid "If you want complete information on &arch-title; RAM issues, and what is the best RAM to buy, see the <ulink url=\"&url-pc-hw-faq;\">PC Hardware FAQ</ulink>." +msgid "" +"If you want complete information on &arch-title; RAM issues, and what is the " +"best RAM to buy, see the <ulink url=\"&url-pc-hw-faq;\">PC Hardware FAQ</" +"ulink>." msgstr "" #. Tag: para @@ -3179,25 +3731,44 @@ msgstr "" #. Tag: para #: hardware.xml:2357 #, no-c-format -msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. For a minimal console-based system (all standard packages), 250MB is required. If you want to install a reasonable amount of software, including the X Window System, and some development programs and libraries, you'll need at least 400MB. For a more or less complete desktop system, you'll need a few gigabytes." +msgid "" +"You must have at least &minimum-memory; of memory and &minimum-fs-size; of " +"hard disk space. For a minimal console-based system (all standard packages), " +"250MB is required. If you want to install a reasonable amount of software, " +"including the X Window System, and some development programs and libraries, " +"you'll need at least 400MB. For a more or less complete desktop system, " +"you'll need a few gigabytes." msgstr "" #. Tag: para #: hardware.xml:2366 #, no-c-format -msgid "On the Amiga the size of FastRAM is relevant towards the total memory requirements. Also, using Zorro cards with 16-bit RAM is not supported; you'll need 32-bit RAM. The <command>amiboot</command> program can be used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically." +msgid "" +"On the Amiga the size of FastRAM is relevant towards the total memory " +"requirements. Also, using Zorro cards with 16-bit RAM is not supported; " +"you'll need 32-bit RAM. The <command>amiboot</command> program can be used " +"to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</" +"ulink>. Recent kernels should disable 16-bit RAM automatically." msgstr "" #. Tag: para #: hardware.xml:2375 #, no-c-format -msgid "On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many users have reported problems running the kernel itself in Fast RAM, so the Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM." +msgid "" +"On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many " +"users have reported problems running the kernel itself in Fast RAM, so the " +"Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for " +"ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM." msgstr "" #. Tag: para #: hardware.xml:2383 #, no-c-format -msgid "On the Macintosh, care should be taken on machines with RAM-based video (RBV). The RAM segment at physical address 0 is used as screen memory, making the default load position for the kernel unavailable. The alternate RAM segment used for kernel and RAMdisk must be at least 4 MB." +msgid "" +"On the Macintosh, care should be taken on machines with RAM-based video " +"(RBV). The RAM segment at physical address 0 is used as screen memory, " +"making the default load position for the kernel unavailable. The alternate " +"RAM segment used for kernel and RAMdisk must be at least 4 MB." msgstr "" #. Tag: emphasis @@ -3215,25 +3786,41 @@ msgstr "" #. Tag: para #: hardware.xml:2406 #, no-c-format -msgid "Most PCI and many older ISA network cards are supported. Some network interface cards are not supported by most Debian installation disks, such as AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider & Koch G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) network cards are not supported by the standard installation system, but see <ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) instructions. FDDI networks are also not supported by the installation disks, both cards and protocols." +msgid "" +"Most PCI and many older ISA network cards are supported. Some network " +"interface cards are not supported by most Debian installation disks, such as " +"AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider & Koch " +"G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) " +"network cards are not supported by the standard installation system, but see " +"<ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) " +"instructions. FDDI networks are also not supported by the installation " +"disks, both cards and protocols." msgstr "" #. Tag: para #: hardware.xml:2425 #, no-c-format -msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;." +msgid "" +"As for ISDN, the D-channel protocol for the (old) German 1TR6 is not " +"supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;." msgstr "" #. Tag: para #: hardware.xml:2433 #, no-c-format -msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details." +msgid "" +"Any network interface card (NIC) supported by the Linux kernel should also " +"be supported by the boot disks. You may need to load your network driver as " +"a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete " +"details." msgstr "" #. Tag: para #: hardware.xml:2442 #, no-c-format -msgid "The following network interface cards (NICs) are supported from the bootable kernel directly:" +msgid "" +"The following network interface cards (NICs) are supported from the bootable " +"kernel directly:" msgstr "" #. Tag: para @@ -3251,7 +3838,10 @@ msgstr "" #. Tag: para #: hardware.xml:2462 #, no-c-format -msgid "The following network interface cards are supported as modules. They can be enabled once the drivers are installed during the setup. However, due to the magic of OpenPROM, you still should be able to boot from these devices:" +msgid "" +"The following network interface cards are supported as modules. They can be " +"enabled once the drivers are installed during the setup. However, due to the " +"magic of OpenPROM, you still should be able to boot from these devices:" msgstr "" #. Tag: para @@ -3273,25 +3863,31 @@ msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:2488 -#: hardware.xml:2494 -#: hardware.xml:2500 -#: hardware.xml:2506 +#: hardware.xml:2488 hardware.xml:2494 hardware.xml:2500 hardware.xml:2506 #: hardware.xml:2512 #, no-c-format -msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module." +msgid "" +"Any network interface card (NIC) supported by the Linux kernel should also " +"be supported by the boot disks. You may need to load your network driver as " +"a module." msgstr "" #. Tag: para #: hardware.xml:2518 #, no-c-format -msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work." +msgid "" +"Due to kernel limitations only the onboard network interfaces on DECstations " +"are supported, TurboChannel option network cards currently do not work." msgstr "" #. Tag: para #: hardware.xml:2524 #, no-c-format -msgid "Any network interface card (NIC) supported by the Linux kernel is also be supported by the boot disks. All network drivers are compiled as modules so you need to load one first during the initial network setup. The list of supported network devices is:" +msgid "" +"Any network interface card (NIC) supported by the Linux kernel is also be " +"supported by the boot disks. All network drivers are compiled as modules so " +"you need to load one first during the initial network setup. The list of " +"supported network devices is:" msgstr "" #. Tag: para @@ -3309,7 +3905,8 @@ msgstr "" #. Tag: para #: hardware.xml:2542 #, no-c-format -msgid "Inter-User Communication Vehicle (IUCV) — available for VM guests only" +msgid "" +"Inter-User Communication Vehicle (IUCV) — available for VM guests only" msgstr "" #. Tag: para @@ -3321,7 +3918,9 @@ msgstr "" #. Tag: para #: hardware.xml:2556 #, no-c-format -msgid "The following network interface cards are supported directly by the boot disks on Netwinder and CATS machines:" +msgid "" +"The following network interface cards are supported directly by the boot " +"disks on Netwinder and CATS machines:" msgstr "" #. Tag: para @@ -3339,7 +3938,9 @@ msgstr "" #. Tag: para #: hardware.xml:2575 #, no-c-format -msgid "The following network interface cards are supported directly by the boot disks on RiscPCs:" +msgid "" +"The following network interface cards are supported directly by the boot " +"disks on RiscPCs:" msgstr "" #. Tag: para @@ -3363,12 +3964,17 @@ msgstr "" #. Tag: para #: hardware.xml:2598 #, no-c-format -msgid "If your card is mentioned in the lists above, the complete installation can be carried out from the network with no need for CD-ROMs or floppy disks." +msgid "" +"If your card is mentioned in the lists above, the complete installation can " +"be carried out from the network with no need for CD-ROMs or floppy disks." msgstr "" #. Tag: para #: hardware.xml:2604 #, no-c-format -msgid "Any other network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module; this means that you will have to install the operating system kernel and modules using some other media." +msgid "" +"Any other network interface card (NIC) supported by the Linux kernel should " +"also be supported by the boot disks. You may need to load your network " +"driver as a module; this means that you will have to install the operating " +"system kernel and modules using some other media." msgstr "" - diff --git a/po/hu/post-install.po b/po/hu/post-install.po index 1545a94be..9ace9c6de 100644 --- a/po/hu/post-install.po +++ b/po/hu/post-install.po @@ -1,12 +1,13 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: \n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2006-08-18 17:32+0000\n" "PO-Revision-Date: 2006-08-20 11:59+0100\n" "Last-Translator: SZERVÁC Attila <sas@321.hu>\n" "Language-Team: hu\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Poedit-Language: Hungarian\n" @@ -27,14 +28,42 @@ msgstr "A rendszer leállítása" #. Tag: para #: post-install.xml:15 #, no-c-format -msgid "To shut down a running Linux system, you must not reboot with the reset switch on the front or back of your computer, or just turn off the computer. Linux should be shut down in a controlled manner, otherwise files might get lost and/or disk damage might occur. If you run a desktop environment, there is usually an option to <quote>log out</quote> available from the application menu that allows you to shutdown (or reboot) the system." -msgstr "Egy futó GNU/Linux rendszer leállításánál szerencsére mellőzhető a gép durva, azonnali áramtalanítása az újraindító vagy kapcsoló gombbal, irányított módon tesszük ezt, így a fájlok vagy a lemez nem sérülhet. Amikor egy asztali környezetet futtatsz, általában megleled a <quote>kijelentkezés</quote> pontot a környezet menüjében, mellyel leállíthatod (vagy újraindíthatod) a rendszert." +msgid "" +"To shut down a running Linux system, you must not reboot with the reset " +"switch on the front or back of your computer, or just turn off the computer. " +"Linux should be shut down in a controlled manner, otherwise files might get " +"lost and/or disk damage might occur. If you run a desktop environment, there " +"is usually an option to <quote>log out</quote> available from the " +"application menu that allows you to shutdown (or reboot) the system." +msgstr "" +"Egy futó GNU/Linux rendszer leállításánál szerencsére mellőzhető a gép " +"durva, azonnali áramtalanítása az újraindító vagy kapcsoló gombbal, " +"irányított módon tesszük ezt, így a fájlok vagy a lemez nem sérülhet. Amikor " +"egy asztali környezetet futtatsz, általában megleled a <quote>kijelentkezés</" +"quote> pontot a környezet menüjében, mellyel leállíthatod (vagy " +"újraindíthatod) a rendszert." #. Tag: para #: post-install.xml:25 #, no-c-format -msgid "Alternatively you can press the key combination <keycombo> <keycap>Ctrl</keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch=\"powerpc;m68k\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> <keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. A last option is to log in as root and type one of the commands <command>poweroff</command>, <command>halt</command> or <command>shutdown -h now</command> if either of the key combinations do not work or you prefer to type commands; use <command>reboot</command> to reboot the system." -msgstr "Más esetben legtöbbször használhatod a <keycombo> <keycap>Ctrl</keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch=\"powerpc;m68k\"> vagy Macintosh rendszereken <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> <keycap>Power</keycap> </keycombo></phrase> billentyűket. Végül rendszergazdaként használhatod a <command>poweroff</command>, <command>halt</command> vagy <command>shutdown -h now</command> parancsokat, ha a gyorsbillentyűk céljaidra nem megfelelők; a <command>reboot</command> parancs újraindít." +msgid "" +"Alternatively you can press the key combination <keycombo> <keycap>Ctrl</" +"keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch=" +"\"powerpc;m68k\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</" +"keycap> <keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. A " +"last option is to log in as root and type one of the commands " +"<command>poweroff</command>, <command>halt</command> or <command>shutdown -h " +"now</command> if either of the key combinations do not work or you prefer to " +"type commands; use <command>reboot</command> to reboot the system." +msgstr "" +"Más esetben legtöbbször használhatod a <keycombo> <keycap>Ctrl</keycap> " +"<keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch=\"powerpc;" +"m68k\"> vagy Macintosh rendszereken <keycombo> <keycap>Control</keycap> " +"<keycap>Shift</keycap> <keycap>Power</keycap> </keycombo></phrase> " +"billentyűket. Végül rendszergazdaként használhatod a <command>poweroff</" +"command>, <command>halt</command> vagy <command>shutdown -h now</command> " +"parancsokat, ha a gyorsbillentyűk céljaidra nem megfelelők; a " +"<command>reboot</command> parancs újraindít." #. Tag: title #: post-install.xml:46 @@ -45,14 +74,38 @@ msgstr "Ha új vagy a Unixban" #. Tag: para #: post-install.xml:47 #, no-c-format -msgid "If you are new to Unix, you probably should go out and buy some books and do some reading. A lot of valuable information can also be found in the <ulink url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url=\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet documents which provide a nice historical reference." -msgstr "Ha még nem ismered a unixos alapokat, hasznos lehet belenézni pár könyvbe. Sok nagyon hasznos információ megtalálható a <ulink url=\"&url-debian-reference;\">Debian Reference</ulink> leírásban. A <ulink url=\"&url-unix-faq;\">Unix FAQ-lista</ulink> jó néhány UseNet dokumentumra hivatkozik." +msgid "" +"If you are new to Unix, you probably should go out and buy some books and do " +"some reading. A lot of valuable information can also be found in the <ulink " +"url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url=" +"\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet " +"documents which provide a nice historical reference." +msgstr "" +"Ha még nem ismered a unixos alapokat, hasznos lehet belenézni pár könyvbe. " +"Sok nagyon hasznos információ megtalálható a <ulink url=\"&url-debian-" +"reference;\">Debian Reference</ulink> leírásban. A <ulink url=\"&url-unix-" +"faq;\">Unix FAQ-lista</ulink> jó néhány UseNet dokumentumra hivatkozik." #. Tag: para #: post-install.xml:55 #, no-c-format -msgid "Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux Documentation Project (LDP)</ulink> collects a number of HOWTOs and online books relating to Linux. Most of these documents can be installed locally; just install the <classname>doc-linux-html</classname> package (HTML versions) or the <classname>doc-linux-text</classname> package (ASCII versions), then look in <filename>/usr/share/doc/HOWTO</filename>. International versions of the LDP HOWTOs are also available as Debian packages." -msgstr "A GNU/Linux alapjaiban egy Unix-szerű rendszer. A <ulink url=\"&url-ldp;\">Linux Dokumentációs Projekt (LDP)</ulink> számos HOGYAN és könyv gyűjteménye. Ezek többsége a Debian rendszerben helyileg is telepíthető; egyszerűen telepítsd a <classname>doc-linux-html</classname> csomagot (HTML verzió) vagy a <classname>doc-linux-text</classname> csomagot (ASCII verzió), és megtalálod a <filename>/usr/share/doc/HOWTO</filename> könyvtárban." +msgid "" +"Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux " +"Documentation Project (LDP)</ulink> collects a number of HOWTOs and online " +"books relating to Linux. Most of these documents can be installed locally; " +"just install the <classname>doc-linux-html</classname> package (HTML " +"versions) or the <classname>doc-linux-text</classname> package (ASCII " +"versions), then look in <filename>/usr/share/doc/HOWTO</filename>. " +"International versions of the LDP HOWTOs are also available as Debian " +"packages." +msgstr "" +"A GNU/Linux alapjaiban egy Unix-szerű rendszer. A <ulink url=\"&url-ldp;" +"\">Linux Dokumentációs Projekt (LDP)</ulink> számos HOGYAN és könyv " +"gyűjteménye. Ezek többsége a Debian rendszerben helyileg is telepíthető; " +"egyszerűen telepítsd a <classname>doc-linux-html</classname> csomagot (HTML " +"verzió) vagy a <classname>doc-linux-text</classname> csomagot (ASCII " +"verzió), és megtalálod a <filename>/usr/share/doc/HOWTO</filename> " +"könyvtárban." #. Tag: title #: post-install.xml:76 @@ -63,8 +116,19 @@ msgstr "Hangolódj a Debian rendszerre" #. Tag: para #: post-install.xml:77 #, no-c-format -msgid "Debian is a little different from other distributions. Even if you're familiar with Linux in other distributions, there are things you should know about Debian to help you to keep your system in a good, clean state. This chapter contains material to help you get oriented; it is not intended to be a tutorial for how to use Debian, but just a very brief glimpse of the system for the very rushed." -msgstr "A Debian természetesen egyedi jellemzőket is tartalmaz. Valószínűleg már dolgoztál hasonló rendszerrel, de még így is van pár hasznos tudnivaló, mellyel Debian rendszeredet jól és rendben tarthatod. Ez a fejezet ezekről szól; természetesen nem egy átfogó Debian oktatóanyag, csak egy pillantás a rendszerre az esetleges legsürgősebb dolgokról." +msgid "" +"Debian is a little different from other distributions. Even if you're " +"familiar with Linux in other distributions, there are things you should know " +"about Debian to help you to keep your system in a good, clean state. This " +"chapter contains material to help you get oriented; it is not intended to be " +"a tutorial for how to use Debian, but just a very brief glimpse of the " +"system for the very rushed." +msgstr "" +"A Debian természetesen egyedi jellemzőket is tartalmaz. Valószínűleg már " +"dolgoztál hasonló rendszerrel, de még így is van pár hasznos tudnivaló, " +"mellyel Debian rendszeredet jól és rendben tarthatod. Ez a fejezet ezekről " +"szól; természetesen nem egy átfogó Debian oktatóanyag, csak egy pillantás a " +"rendszerre az esetleges legsürgősebb dolgokról." #. Tag: title #: post-install.xml:88 @@ -75,14 +139,52 @@ msgstr "A Debian csomagkezelő rendszer" #. Tag: para #: post-install.xml:89 #, no-c-format -msgid "The most important concept to grasp is the Debian packaging system. In essence, large parts of your system should be considered under the control of the packaging system. These include: <itemizedlist> <listitem><para> <filename>/usr</filename> (excluding <filename>/usr/local</filename>) </para></listitem> <listitem><para> <filename>/var</filename> (you could make <filename>/var/local</filename> and be safe in there) </para></listitem> <listitem><para> <filename>/bin</filename> </para></listitem> <listitem><para> <filename>/sbin</filename> </para></listitem> <listitem><para> <filename>/lib</filename> </para></listitem> </itemizedlist> For instance, if you replace <filename>/usr/bin/perl</filename>, that will work, but then if you upgrade your <classname>perl</classname> package, the file you put there will be replaced. Experts can get around this by putting packages on <quote>hold</quote> in <command>aptitude</command>." -msgstr "A legfontosabb, amit meg kell értenünk, a Debian csomagkezelő rendszer. A rendszer legnagyobb részét ez kezeli. Így például: <itemizedlist> <listitem><para> <filename>/usr</filename> (kivéve <filename>/usr/local</filename>) </para></listitem> <listitem><para> <filename>/var</filename> (készíthető egyéni <filename>/var/local</filename> és használható mentésre) </para></listitem> <listitem><para> <filename>/bin</filename> </para></listitem> <listitem><para> <filename>/sbin</filename> </para></listitem> <listitem><para> <filename>/lib</filename> </para></listitem> </itemizedlist>. Például, ha lecseréled a <filename>/usr/bin/perl</filename> fájlt, működni fog, de ha frissül a rendszereden a <classname>perl</classname> csomag, az felülírja majd. Haladó felhasználóként viszont visszafogásba (<quote>hold</quote>) teheted a csomagot például az <command>aptitude</command> paranccsal indítható felület segítségével." +msgid "" +"The most important concept to grasp is the Debian packaging system. In " +"essence, large parts of your system should be considered under the control " +"of the packaging system. These include: <itemizedlist> <listitem><para> " +"<filename>/usr</filename> (excluding <filename>/usr/local</filename>) </" +"para></listitem> <listitem><para> <filename>/var</filename> (you could make " +"<filename>/var/local</filename> and be safe in there) </para></listitem> " +"<listitem><para> <filename>/bin</filename> </para></listitem> " +"<listitem><para> <filename>/sbin</filename> </para></listitem> " +"<listitem><para> <filename>/lib</filename> </para></listitem> </" +"itemizedlist> For instance, if you replace <filename>/usr/bin/perl</" +"filename>, that will work, but then if you upgrade your <classname>perl</" +"classname> package, the file you put there will be replaced. Experts can get " +"around this by putting packages on <quote>hold</quote> in <command>aptitude</" +"command>." +msgstr "" +"A legfontosabb, amit meg kell értenünk, a Debian csomagkezelő rendszer. A " +"rendszer legnagyobb részét ez kezeli. Így például: <itemizedlist> " +"<listitem><para> <filename>/usr</filename> (kivéve <filename>/usr/local</" +"filename>) </para></listitem> <listitem><para> <filename>/var</filename> " +"(készíthető egyéni <filename>/var/local</filename> és használható mentésre) " +"</para></listitem> <listitem><para> <filename>/bin</filename> </para></" +"listitem> <listitem><para> <filename>/sbin</filename> </para></listitem> " +"<listitem><para> <filename>/lib</filename> </para></listitem> </" +"itemizedlist>. Például, ha lecseréled a <filename>/usr/bin/perl</filename> " +"fájlt, működni fog, de ha frissül a rendszereden a <classname>perl</" +"classname> csomag, az felülírja majd. Haladó felhasználóként viszont " +"visszafogásba (<quote>hold</quote>) teheted a csomagot például az " +"<command>aptitude</command> paranccsal indítható felület segítségével." #. Tag: para #: post-install.xml:130 #, no-c-format -msgid "One of the best installation methods is apt. You can use the command line version <command>apt-get</command> or full-screen text version <application>aptitude</application>. Note apt will also let you merge main, contrib, and non-free so you can have export-restricted packages as well as standard versions." -msgstr "A telepítés egyik legjobb módja az apt. Ennek több felülete létezik, például az <command>apt-get</command> parancssoros felület, vagy az <application>aptitude</application> teljes-képernyős szöveges felület. Az apt a fő, vagyis main tárolók mellett a contrib és non-free nevűeket is tudja kezelni, így, ha esetleg ezeket is használnád, korlátozó csomagjaid éppúgy lesznek, mint standard verziójúak." +msgid "" +"One of the best installation methods is apt. You can use the command line " +"version <command>apt-get</command> or full-screen text version " +"<application>aptitude</application>. Note apt will also let you merge main, " +"contrib, and non-free so you can have export-restricted packages as well as " +"standard versions." +msgstr "" +"A telepítés egyik legjobb módja az apt. Ennek több felülete létezik, például " +"az <command>apt-get</command> parancssoros felület, vagy az " +"<application>aptitude</application> teljes-képernyős szöveges felület. Az " +"apt a fő, vagyis main tárolók mellett a contrib és non-free nevűeket is " +"tudja kezelni, így, ha esetleg ezeket is használnád, korlátozó csomagjaid " +"éppúgy lesznek, mint standard verziójúak." #. Tag: title #: post-install.xml:141 @@ -93,8 +195,14 @@ msgstr "Alkalmazás verzió kezelés" #. Tag: para #: post-install.xml:142 #, no-c-format -msgid "Alternative versions of applications are managed by update-alternatives. If you are maintaining multiple versions of your applications, read the update-alternatives man page." -msgstr "Az alkalmazások párhuzamos verzióit az update-alternatives kezeli. Ha egyes alkalmazásaid egyszerre több változatát is karbantartod, olvasd el az update-alternatives kézikönyv oldalát." +msgid "" +"Alternative versions of applications are managed by update-alternatives. If " +"you are maintaining multiple versions of your applications, read the update-" +"alternatives man page." +msgstr "" +"Az alkalmazások párhuzamos verzióit az update-alternatives kezeli. Ha egyes " +"alkalmazásaid egyszerre több változatát is karbantartod, olvasd el az update-" +"alternatives kézikönyv oldalát." #. Tag: title #: post-install.xml:152 @@ -105,20 +213,49 @@ msgstr "Cron feladatok kezelése" #. Tag: para #: post-install.xml:153 #, no-c-format -msgid "Any jobs under the purview of the system administrator should be in <filename>/etc</filename>, since they are configuration files. If you have a root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/etc/crontab</filename>, and will run in alphabetic order, which serializes them." -msgstr "Minden a rendszergazda hatáskörébe tartozó cron feladatnak a <filename>/etc</filename> könyvtárban kell lennie, mivel ezek a cron szempontjából beállítófájlok. Ha van egy napi, heti vagy havi rendszergazdai cron feladatod, tedd a <filename>/etc/cron.{daily,weekly,monthly}</filename> könyvtárba. A <filename>/etc/crontab</filename> meghívja őket, és ABC-rendben futtatja." +msgid "" +"Any jobs under the purview of the system administrator should be in " +"<filename>/etc</filename>, since they are configuration files. If you have a " +"root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/" +"cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/" +"etc/crontab</filename>, and will run in alphabetic order, which serializes " +"them." +msgstr "" +"Minden a rendszergazda hatáskörébe tartozó cron feladatnak a <filename>/etc</" +"filename> könyvtárban kell lennie, mivel ezek a cron szempontjából " +"beállítófájlok. Ha van egy napi, heti vagy havi rendszergazdai cron " +"feladatod, tedd a <filename>/etc/cron.{daily,weekly,monthly}</filename> " +"könyvtárba. A <filename>/etc/crontab</filename> meghívja őket, és ABC-" +"rendben futtatja." #. Tag: para #: post-install.xml:162 #, no-c-format -msgid "On the other hand, if you have a cron job that (a) needs to run as a special user, or (b) needs to run at a special time or frequency, you can use either <filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/whatever</filename>. These particular files also have an extra field that allows you to stipulate the user under which the cron job runs." -msgstr "Illetve, ha van egy cron feladatot, amit speciális (a) felhasználóként (b) időpontban vagy gyakorisággal kell futtatnod, használd a <filename>/etc/crontab</filename> vagy, még jobb, a <filename>/etc/cron.d/amit_akarsz</filename> fájlt. E fájloknak extra mezőik vannak, melyekkel megadhatod e feltételeket." +msgid "" +"On the other hand, if you have a cron job that (a) needs to run as a special " +"user, or (b) needs to run at a special time or frequency, you can use either " +"<filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/" +"whatever</filename>. These particular files also have an extra field that " +"allows you to stipulate the user under which the cron job runs." +msgstr "" +"Illetve, ha van egy cron feladatot, amit speciális (a) felhasználóként (b) " +"időpontban vagy gyakorisággal kell futtatnod, használd a <filename>/etc/" +"crontab</filename> vagy, még jobb, a <filename>/etc/cron.d/amit_akarsz</" +"filename> fájlt. E fájloknak extra mezőik vannak, melyekkel megadhatod e " +"feltételeket." #. Tag: para #: post-install.xml:171 #, no-c-format -msgid "In either case, you just edit the files and cron will notice them automatically. There is no need to run a special command. For more information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/README.Debian</filename>." -msgstr "Csak szerkeszd e fájlokat és a cron magától észreveszi. Nem kell különleges parancsot futtatnod. A további adatokat lásd a cron(8) és crontab(5) lapokon és a <filename>/usr/share/doc/cron/README.Debian</filename> fájlban." +msgid "" +"In either case, you just edit the files and cron will notice them " +"automatically. There is no need to run a special command. For more " +"information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/" +"README.Debian</filename>." +msgstr "" +"Csak szerkeszd e fájlokat és a cron magától észreveszi. Nem kell különleges " +"parancsot futtatnod. A további adatokat lásd a cron(8) és crontab(5) lapokon " +"és a <filename>/usr/share/doc/cron/README.Debian</filename> fájlban." #. Tag: title #: post-install.xml:188 @@ -129,38 +266,111 @@ msgstr "Régi rendszerek és DOS vagy Windows felébresztése" #. Tag: para #: post-install.xml:189 #, no-c-format -msgid "After installing the base system and writing to the <emphasis>Master Boot Record</emphasis>, you will be able to boot Linux, but probably nothing else. This depends what you have chosen during the installation. This chapter will describe how you can reactivate your old systems so that you can also boot your DOS or Windows again." -msgstr "Az alaprendszer telepítése és az <emphasis>MBR</emphasis> módosítása után sikerrel indíthatod a Linuxot, de lehet, hogy ekkor semmi mást. Ez attól is függ, mit választottál a telepítéskor. Ez a rész leírja, hogyan tudsz felébreszteni régi rendszereket (ha voltak ilyenek és ez szükséges) sőt, így akár még egy, a telepítés előtti DOS vagy Windows is ismét indíthatóvá tehető." +msgid "" +"After installing the base system and writing to the <emphasis>Master Boot " +"Record</emphasis>, you will be able to boot Linux, but probably nothing " +"else. This depends what you have chosen during the installation. This " +"chapter will describe how you can reactivate your old systems so that you " +"can also boot your DOS or Windows again." +msgstr "" +"Az alaprendszer telepítése és az <emphasis>MBR</emphasis> módosítása után " +"sikerrel indíthatod a Linuxot, de lehet, hogy ekkor semmi mást. Ez attól is " +"függ, mit választottál a telepítéskor. Ez a rész leírja, hogyan tudsz " +"felébreszteni régi rendszereket (ha voltak ilyenek és ez szükséges) sőt, így " +"akár még egy, a telepítés előtti DOS vagy Windows is ismét indíthatóvá " +"tehető." #. Tag: para #: post-install.xml:197 #, no-c-format -msgid "<command>LILO</command> is a boot manager with which you can also boot other operating systems than Linux, which complies to PC conventions. The boot manager is configured via <filename>/etc/lilo.conf</filename> file. Whenever you edited this file you have to run <command>lilo</command> afterwards. The reason for this is that the changes will take place only when you call the program." -msgstr "A <command>LILO</command> egy boot betöltő, mellyel nem csak GNU/Linux, de más operációs rendszer is indítható, mely PC-ken szokásos. Ez a boot betöltő a <filename>/etc/lilo.conf</filename> fájlban állítható. A fájl minden szerkesztés után futtatni kell a <command>lilo</command> parancsot, mer a módosítások csak e program meghívása után kerülnek helyükre." +msgid "" +"<command>LILO</command> is a boot manager with which you can also boot other " +"operating systems than Linux, which complies to PC conventions. The boot " +"manager is configured via <filename>/etc/lilo.conf</filename> file. Whenever " +"you edited this file you have to run <command>lilo</command> afterwards. The " +"reason for this is that the changes will take place only when you call the " +"program." +msgstr "" +"A <command>LILO</command> egy boot betöltő, mellyel nem csak GNU/Linux, de " +"más operációs rendszer is indítható, mely PC-ken szokásos. Ez a boot betöltő " +"a <filename>/etc/lilo.conf</filename> fájlban állítható. A fájl minden " +"szerkesztés után futtatni kell a <command>lilo</command> parancsot, mer a " +"módosítások csak e program meghívása után kerülnek helyükre." #. Tag: para #: post-install.xml:207 #, no-c-format -msgid "Important parts of the <filename>lilo.conf</filename> file are the lines containing the <userinput>image</userinput> and <userinput>other</userinput> keywords, as well as the lines following those. They can be used to describe a system which can be booted by <command>LILO</command>. Such a system can include a kernel (<userinput>image</userinput>), a root partition, additional kernel parameters, etc. as well as a configuration to boot another, non-Linux (<userinput>other</userinput>) operating system. These keywords can also be used more than once. The ordering of these systems within the configuration file is important because it determines which system will be booted automatically after, for instance, a timeout (<userinput>delay</userinput>) presuming <command>LILO</command> wasn't stopped by pressing the <keycap>shift</keycap> key." -msgstr "A <filename>lilo.conf</filename> fontos részei az <userinput>image</userinput> és <userinput>other</userinput> szavakat tartalmazó és követő sorok. Ezek használhatók egy a <command>LILO</command> által indítható rendszer leírására. A kernel (<userinput>kép</userinput>), gyökér-partíció, további kernel paraméterek, és más beállításokkal bíró rendszerekére is a más, nem-Linux (<userinput>other</userinput>) operációs rendszerek indításának beállítására is. A szavak többször is szerepelhetnek. A rendszerek sorrendje fontos, mert az adja meg, mely rendszer induljon magától, például egy késedelmi idő (<userinput>delay</userinput>) után, ha <command>LILO</command> nem került leállításra a <keycap>shift</keycap> billentyű leütésével." +msgid "" +"Important parts of the <filename>lilo.conf</filename> file are the lines " +"containing the <userinput>image</userinput> and <userinput>other</userinput> " +"keywords, as well as the lines following those. They can be used to describe " +"a system which can be booted by <command>LILO</command>. Such a system can " +"include a kernel (<userinput>image</userinput>), a root partition, " +"additional kernel parameters, etc. as well as a configuration to boot " +"another, non-Linux (<userinput>other</userinput>) operating system. These " +"keywords can also be used more than once. The ordering of these systems " +"within the configuration file is important because it determines which " +"system will be booted automatically after, for instance, a timeout " +"(<userinput>delay</userinput>) presuming <command>LILO</command> wasn't " +"stopped by pressing the <keycap>shift</keycap> key." +msgstr "" +"A <filename>lilo.conf</filename> fontos részei az <userinput>image</" +"userinput> és <userinput>other</userinput> szavakat tartalmazó és követő " +"sorok. Ezek használhatók egy a <command>LILO</command> által indítható " +"rendszer leírására. A kernel (<userinput>kép</userinput>), gyökér-partíció, " +"további kernel paraméterek, és más beállításokkal bíró rendszerekére is a " +"más, nem-Linux (<userinput>other</userinput>) operációs rendszerek " +"indításának beállítására is. A szavak többször is szerepelhetnek. A " +"rendszerek sorrendje fontos, mert az adja meg, mely rendszer induljon " +"magától, például egy késedelmi idő (<userinput>delay</userinput>) után, ha " +"<command>LILO</command> nem került leállításra a <keycap>shift</keycap> " +"billentyű leütésével." #. Tag: para #: post-install.xml:223 #, no-c-format msgid "" -"After a fresh install of Debian, just the current system is configured for booting with <command>LILO</command>. If you want to boot another Linux kernel, you have to edit the configuration file <filename>/etc/lilo.conf</filename> to add the following lines: <informalexample><screen>\n" +"After a fresh install of Debian, just the current system is configured for " +"booting with <command>LILO</command>. If you want to boot another Linux " +"kernel, you have to edit the configuration file <filename>/etc/lilo.conf</" +"filename> to add the following lines: <informalexample><screen>\n" "&additional-lilo-image;\n" -"</screen></informalexample> For a basic setup just the first two lines are necessary. If you want to know more about the other two options please have a look at the <command>LILO</command> documentation. This can be found in <filename>/usr/share/doc/lilo/</filename>. The file which should be read is <filename>Manual.txt</filename>. To have a quicker start into the world of booting a system you can also look at the <command>LILO</command> man pages <filename>lilo.conf</filename> for an overview of configuration keywords and <filename>lilo</filename> for description of the installation of the new configuration into the boot sector." +"</screen></informalexample> For a basic setup just the first two lines are " +"necessary. If you want to know more about the other two options please have " +"a look at the <command>LILO</command> documentation. This can be found in " +"<filename>/usr/share/doc/lilo/</filename>. The file which should be read is " +"<filename>Manual.txt</filename>. To have a quicker start into the world of " +"booting a system you can also look at the <command>LILO</command> man pages " +"<filename>lilo.conf</filename> for an overview of configuration keywords and " +"<filename>lilo</filename> for description of the installation of the new " +"configuration into the boot sector." msgstr "" -"A Debian egy friss telepítése után csak a jelen rendszer indítható, ha a <command>LILO</command> betöltőt használjuk. Ebben az esetben, ha más Linux rendszermagot akarsz indítani, a <filename>/etc/lilo.conf</filename> fájl szerkesztése szükséges, például: <informalexample><screen>\n" +"A Debian egy friss telepítése után csak a jelen rendszer indítható, ha a " +"<command>LILO</command> betöltőt használjuk. Ebben az esetben, ha más Linux " +"rendszermagot akarsz indítani, a <filename>/etc/lilo.conf</filename> fájl " +"szerkesztése szükséges, például: <informalexample><screen>\n" "&additional-lilo-image;\n" -"</screen></informalexample> Egy alap beállításhoz csak az 1. 2 sor szükséges. Több adatért lásd a <command>LILO</command> dokumentációját. Ez a <filename>/usr/share/doc/lilo/</filename> könyvtárban található. A fontos fájl a <filename>Manual.txt</filename>. A <command>LILO</command> kézikönyv-oldalait is átnézheted. A <filename>lilo.conf</filename> tartalmazza a beállításokat, a <filename>lilo</filename> az új beállító fájl telepítésének leírását." +"</screen></informalexample> Egy alap beállításhoz csak az 1. 2 sor " +"szükséges. Több adatért lásd a <command>LILO</command> dokumentációját. Ez a " +"<filename>/usr/share/doc/lilo/</filename> könyvtárban található. A fontos " +"fájl a <filename>Manual.txt</filename>. A <command>LILO</command> kézikönyv-" +"oldalait is átnézheted. A <filename>lilo.conf</filename> tartalmazza a " +"beállításokat, a <filename>lilo</filename> az új beállító fájl telepítésének " +"leírását." #. Tag: para #: post-install.xml:243 #, no-c-format -msgid "Notice that there are other boot loaders available in &debian;, such as GRUB (in <classname>grub</classname> package), CHOS (in <classname>chos</classname> package), Extended-IPL (in <classname>extipl</classname> package), loadlin (in <classname>loadlin</classname> package) etc." -msgstr "Más fontos boot betöltők is vannak a &debian; rendszerben, például a GRUB (a <classname>grub</classname> csomagban), CHOS (a <classname>chos</classname> csomagban), Extended-IPL (az <classname>extipl</classname> csomagban), loadlin (a <classname>loadlin</classname> csomagban) és így tovább." +msgid "" +"Notice that there are other boot loaders available in &debian;, such as GRUB " +"(in <classname>grub</classname> package), CHOS (in <classname>chos</" +"classname> package), Extended-IPL (in <classname>extipl</classname> " +"package), loadlin (in <classname>loadlin</classname> package) etc." +msgstr "" +"Más fontos boot betöltők is vannak a &debian; rendszerben, például a GRUB (a " +"<classname>grub</classname> csomagban), CHOS (a <classname>chos</classname> " +"csomagban), Extended-IPL (az <classname>extipl</classname> csomagban), " +"loadlin (a <classname>loadlin</classname> csomagban) és így tovább." #. Tag: title #: post-install.xml:258 @@ -171,26 +381,75 @@ msgstr "További olvasnivalók és információk" #. Tag: para #: post-install.xml:259 #, no-c-format -msgid "If you need information about a particular program, you should first try <userinput>man <replaceable>program</replaceable></userinput>, or <userinput>info <replaceable>program</replaceable></userinput>." -msgstr "Ha tájékozódni akarsz egy programról, először majdnem mindig érdemes kipróbálni az <userinput>info <replaceable>a_program_neve</replaceable></userinput> vagy a <userinput>man <replaceable>a_program_neve</replaceable></userinput> parancsot." +msgid "" +"If you need information about a particular program, you should first try " +"<userinput>man <replaceable>program</replaceable></userinput>, or " +"<userinput>info <replaceable>program</replaceable></userinput>." +msgstr "" +"Ha tájékozódni akarsz egy programról, először majdnem mindig érdemes " +"kipróbálni az <userinput>info <replaceable>a_program_neve</replaceable></" +"userinput> vagy a <userinput>man <replaceable>a_program_neve</replaceable></" +"userinput> parancsot." #. Tag: para #: post-install.xml:265 #, no-c-format -msgid "There is lots of useful documentation in <filename>/usr/share/doc</filename> as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and <filename>/usr/share/doc/FAQ</filename> contain lots of interesting information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</filename>. To read about Debian-specific issues for particular programs, look at <filename>/usr/share/doc/(package name)/README.Debian</filename>." -msgstr "Számos részletesebb dokumentáció van a <filename>/usr/share/doc</filename> könyvtárban. Például a <filename>/usr/share/doc/HOWTO</filename> és <filename>/usr/share/doc/FAQ</filename> rengeteg hasznos adattal szolgál. HIbajelentéshez lásd ezt: <filename>/usr/share/doc/debian/bug*</filename>. Adott program és a Debian kapcsolatáról olvasd el a <filename>/usr/share/doc/(csomag név)/README.Debian</filename> fájlt." +msgid "" +"There is lots of useful documentation in <filename>/usr/share/doc</filename> " +"as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and " +"<filename>/usr/share/doc/FAQ</filename> contain lots of interesting " +"information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</" +"filename>. To read about Debian-specific issues for particular programs, " +"look at <filename>/usr/share/doc/(package name)/README.Debian</filename>." +msgstr "" +"Számos részletesebb dokumentáció van a <filename>/usr/share/doc</filename> " +"könyvtárban. Például a <filename>/usr/share/doc/HOWTO</filename> és " +"<filename>/usr/share/doc/FAQ</filename> rengeteg hasznos adattal szolgál. " +"HIbajelentéshez lásd ezt: <filename>/usr/share/doc/debian/bug*</filename>. " +"Adott program és a Debian kapcsolatáról olvasd el a <filename>/usr/share/doc/" +"(csomag név)/README.Debian</filename> fájlt." #. Tag: para #: post-install.xml:276 #, no-c-format -msgid "The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a large quantity of documentation about Debian. In particular, see the <ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference\">Debian Reference</ulink>. An index of more Debian documentation is available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian Documentation Project</ulink>. The Debian community is self-supporting; to subscribe to one or more of the Debian mailing lists, see the <ulink url=\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/\">Debian Mailing List Archives</ulink> contain a wealth of information on Debian." -msgstr "A <ulink url=\"http://www.debian.org/\">Debian weblap</ulink> sok dokumentációt tartalmaz a Debian rendszerről. Lásd például a <ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux GYIK</ulink> és <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference\">Debian Reference</ulink> leírást. Több Debian dokumentáció listája a <ulink url=\"http://www.debian.org/doc/ddp\">Debian Dokumentációs Projekt</ulink> címén. A Debian egy támogatói közösség is, 1 vagy több Debian listára iratkozáshoz lásd a <ulink url=\"http://www.debian.org/MailingLists/subscribe\"> Levelező lista feliratkozás</ulink> oldalt. Végül, de nem utolsó sorban a <ulink url=\"http://lists.debian.org/\">Debian levelező lista archívumok</ulink> a Debian információinak egy aranybányája." +msgid "" +"The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a " +"large quantity of documentation about Debian. In particular, see the <ulink " +"url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> and the " +"<ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference\">Debian " +"Reference</ulink>. An index of more Debian documentation is available from " +"the <ulink url=\"http://www.debian.org/doc/ddp\">Debian Documentation " +"Project</ulink>. The Debian community is self-supporting; to subscribe to " +"one or more of the Debian mailing lists, see the <ulink url=\"http://www." +"debian.org/MailingLists/subscribe\"> Mail List Subscription</ulink> page. " +"Last, but not least, the <ulink url=\"http://lists.debian.org/\">Debian " +"Mailing List Archives</ulink> contain a wealth of information on Debian." +msgstr "" +"A <ulink url=\"http://www.debian.org/\">Debian weblap</ulink> sok " +"dokumentációt tartalmaz a Debian rendszerről. Lásd például a <ulink url=" +"\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux GYIK</ulink> és <ulink " +"url=\"http://www.debian.org/doc/user-manuals#quick-reference\">Debian " +"Reference</ulink> leírást. Több Debian dokumentáció listája a <ulink url=" +"\"http://www.debian.org/doc/ddp\">Debian Dokumentációs Projekt</ulink> " +"címén. A Debian egy támogatói közösség is, 1 vagy több Debian listára " +"iratkozáshoz lásd a <ulink url=\"http://www.debian.org/MailingLists/subscribe" +"\"> Levelező lista feliratkozás</ulink> oldalt. Végül, de nem utolsó sorban " +"a <ulink url=\"http://lists.debian.org/\">Debian levelező lista archívumok</" +"ulink> a Debian információinak egy aranybányája." #. Tag: para #: post-install.xml:294 #, no-c-format -msgid "A general source of information on GNU/Linux is the <ulink url=\"http://www.tldp.org/\">Linux Documentation Project</ulink>. There you will find the HOWTOs and pointers to other very valuable information on parts of a GNU/Linux system." -msgstr "A GNU/Linuxról szóló információk egy általános forrása a <ulink url=\"http://www.tldp.org/\">Linux Dokumentációs Projekt</ulink>. Itt a GNU/Linux rendszerről szóló HOGYAN leírásokat és más nagyon hasznos adatokra mutató hivatkozásokat találsz." +msgid "" +"A general source of information on GNU/Linux is the <ulink url=\"http://www." +"tldp.org/\">Linux Documentation Project</ulink>. There you will find the " +"HOWTOs and pointers to other very valuable information on parts of a GNU/" +"Linux system." +msgstr "" +"A GNU/Linuxról szóló információk egy általános forrása a <ulink url=\"http://" +"www.tldp.org/\">Linux Dokumentációs Projekt</ulink>. Itt a GNU/Linux " +"rendszerről szóló HOGYAN leírásokat és más nagyon hasznos adatokra mutató " +"hivatkozásokat találsz." #. Tag: title #: post-install.xml:309 @@ -201,26 +460,48 @@ msgstr "Új rendszermag (kernel) fordítása" #. Tag: para #: post-install.xml:310 #, no-c-format -msgid "Why would someone want to compile a new kernel? It is often not necessary since the default kernel shipped with Debian handles most configurations. Also, Debian often offers several alternative kernels. So you may want to check first if there is an alternative kernel image package that better corresponds to your hardware. However, it can be useful to compile a new kernel in order to:" -msgstr "Miért akarna valaki új kernelt fordítani? Valóban, ez általában nem szükséges, mivel a Debian által alapértelmezetten adott kernel a legtöbb gépet jól kezeli. Ráadásul a Debian más kerneleket is tartalmaz. Sokszor ezek között is találhatsz a gépedhez jobban illő kernelt. Ezzel együtt néha hasznos lehet új kernelt fordítani az alábbi célokra:" +msgid "" +"Why would someone want to compile a new kernel? It is often not necessary " +"since the default kernel shipped with Debian handles most configurations. " +"Also, Debian often offers several alternative kernels. So you may want to " +"check first if there is an alternative kernel image package that better " +"corresponds to your hardware. However, it can be useful to compile a new " +"kernel in order to:" +msgstr "" +"Miért akarna valaki új kernelt fordítani? Valóban, ez általában nem " +"szükséges, mivel a Debian által alapértelmezetten adott kernel a legtöbb " +"gépet jól kezeli. Ráadásul a Debian más kerneleket is tartalmaz. Sokszor " +"ezek között is találhatsz a gépedhez jobban illő kernelt. Ezzel együtt néha " +"hasznos lehet új kernelt fordítani az alábbi célokra:" #. Tag: para #: post-install.xml:320 #, no-c-format -msgid "handle special hardware needs, or hardware conflicts with the pre-supplied kernels" -msgstr "speciális hardver-igények, vagy ezek az előre-szállított kernelekkel való ütközésük kezelésére" +msgid "" +"handle special hardware needs, or hardware conflicts with the pre-supplied " +"kernels" +msgstr "" +"speciális hardver-igények, vagy ezek az előre-szállított kernelekkel való " +"ütközésük kezelésére" #. Tag: para #: post-install.xml:326 #, no-c-format -msgid "use options of the kernel which are not supported in the pre-supplied kernels (such as high memory support)" -msgstr "olyan kernel lehetőségek használatára, melyek nem kerültek bekapcsolásra az előre-szállított kernelekben (például az átlagnál magasabb memória-tartományok támogatása)" +msgid "" +"use options of the kernel which are not supported in the pre-supplied " +"kernels (such as high memory support)" +msgstr "" +"olyan kernel lehetőségek használatára, melyek nem kerültek bekapcsolásra az " +"előre-szállított kernelekben (például az átlagnál magasabb memória-" +"tartományok támogatása)" #. Tag: para #: post-install.xml:332 #, no-c-format msgid "optimize the kernel by removing useless drivers to speed up boot time" -msgstr "a kernel optimalizálása a nem használt meghajtók mellőzésével az indítási idő további gyorsítására" +msgstr "" +"a kernel optimalizálása a nem használt meghajtók mellőzésével az indítási " +"idő további gyorsítására" #. Tag: para #: post-install.xml:337 @@ -255,68 +536,225 @@ msgstr "Próbáld ki bátran a kernel-fordítást. Ez kellemes és ráadásul ha #. Tag: para #: post-install.xml:361 #, no-c-format -msgid "To compile a kernel the Debian way, you need some packages: <classname>fakeroot</classname>, <classname>kernel-package</classname>, <phrase condition=\"classic-kpkg\"><classname>kernel-source-&kernelversion;</classname> (the most recent version at the time of this writing)</phrase> <phrase condition=\"common-kpkg\"><classname>linux-source-2.6</classname></phrase> and a few others which are probably already installed (see <filename>/usr/share/doc/kernel-package/README.gz</filename> for the complete list)." -msgstr "Ha a Debian módszerével fordítanál, szükséged lesz pár csomagra, úgymint: <classname>fakeroot</classname>, <classname>kernel-package</classname>, <phrase condition=\"classic-kpkg\"><classname>kernel-source-&kernelversion;</classname> (a legújabb verzió, mikor ezt írom)</phrase> <phrase condition=\"common-kpkg\"><classname>linux-source-2.6</classname></phrase> és egy pár egyébre, mely már valószínűleg telepítve van (a teljes listát elolvashatod a <filename>/usr/share/doc/kernel-package/README.gz</filename> fájlban)." +msgid "" +"To compile a kernel the Debian way, you need some packages: " +"<classname>fakeroot</classname>, <classname>kernel-package</classname>, " +"<phrase condition=\"classic-kpkg\"><classname>kernel-source-&kernelversion;</" +"classname> (the most recent version at the time of this writing)</phrase> " +"<phrase condition=\"common-kpkg\"><classname>linux-source-2.6</classname></" +"phrase> and a few others which are probably already installed (see " +"<filename>/usr/share/doc/kernel-package/README.gz</filename> for the " +"complete list)." +msgstr "" +"Ha a Debian módszerével fordítanál, szükséged lesz pár csomagra, úgymint: " +"<classname>fakeroot</classname>, <classname>kernel-package</classname>, " +"<phrase condition=\"classic-kpkg\"><classname>kernel-source-&kernelversion;</" +"classname> (a legújabb verzió, mikor ezt írom)</phrase> <phrase condition=" +"\"common-kpkg\"><classname>linux-source-2.6</classname></phrase> és egy pár " +"egyébre, mely már valószínűleg telepítve van (a teljes listát elolvashatod a " +"<filename>/usr/share/doc/kernel-package/README.gz</filename> fájlban)." #. Tag: para #: post-install.xml:372 #, no-c-format -msgid "This method will make a .deb of your kernel source, and, if you have non-standard modules, make a synchronized dependent .deb of those too. It's a better way to manage kernel images; <filename>/boot</filename> will hold the kernel, the System.map, and a log of the active config file for the build." -msgstr "E módszer elkészíti a .deb csomagot a kernel-forrásból, és, ha nem- szabvány moduljaid vannak, azokra is elkészíti a megfelelően függőt. Ez sokkal jobb mód a kernel-képek kezelésére; a <filename>/boot</filename> könyvtár tartalmazza majd a kernelt, a System.map fájlt és az aktív konfigurációs fájl naplóját az elkészítéshez." +msgid "" +"This method will make a .deb of your kernel source, and, if you have non-" +"standard modules, make a synchronized dependent .deb of those too. It's a " +"better way to manage kernel images; <filename>/boot</filename> will hold the " +"kernel, the System.map, and a log of the active config file for the build." +msgstr "" +"E módszer elkészíti a .deb csomagot a kernel-forrásból, és, ha nem- szabvány " +"moduljaid vannak, azokra is elkészíti a megfelelően függőt. Ez sokkal jobb " +"mód a kernel-képek kezelésére; a <filename>/boot</filename> könyvtár " +"tartalmazza majd a kernelt, a System.map fájlt és az aktív konfigurációs " +"fájl naplóját az elkészítéshez." #. Tag: para #: post-install.xml:380 #, no-c-format -msgid "Note that you don't <emphasis>have</emphasis> to compile your kernel the <quote>Debian way</quote>; but we find that using the packaging system to manage your kernel is actually safer and easier. In fact, you can get your kernel sources right from Linus instead of <phrase condition=\"classic-kpkg\"><classname>kernel-source-&kernelversion;</classname>,</phrase> <phrase condition=\"common-kpkg\"><classname>linux-source-2.6</classname>,</phrase> yet still use the <classname>kernel-package</classname> compilation method." -msgstr "Tudd, hogy nem <emphasis>kell</emphasis> a kernelt a <quote>Debian módszer</quote> útján fordítanod; de a kernel csomagoló rendszerrel való kezelése biztosabb és könnyebb. Fontos tudni, hogy a kernel forrásokat Linustól is letöltheted a Debian <phrase condition=\"classic-kpkg\"><classname>kernel-source-&kernelversion;</classname>,</phrase> <phrase condition=\"common-kpkg\"><classname>linux-source-2.6</classname>,</phrase> csomagok használata helyett, és még így is rendelkezésedre áll a <classname>kernel-package</classname> kernel-fordítási módszer használata." +msgid "" +"Note that you don't <emphasis>have</emphasis> to compile your kernel the " +"<quote>Debian way</quote>; but we find that using the packaging system to " +"manage your kernel is actually safer and easier. In fact, you can get your " +"kernel sources right from Linus instead of <phrase condition=\"classic-kpkg" +"\"><classname>kernel-source-&kernelversion;</classname>,</phrase> <phrase " +"condition=\"common-kpkg\"><classname>linux-source-2.6</classname>,</phrase> " +"yet still use the <classname>kernel-package</classname> compilation method." +msgstr "" +"Tudd, hogy nem <emphasis>kell</emphasis> a kernelt a <quote>Debian módszer</" +"quote> útján fordítanod; de a kernel csomagoló rendszerrel való kezelése " +"biztosabb és könnyebb. Fontos tudni, hogy a kernel forrásokat Linustól is " +"letöltheted a Debian <phrase condition=\"classic-kpkg\"><classname>kernel-" +"source-&kernelversion;</classname>,</phrase> <phrase condition=\"common-kpkg" +"\"><classname>linux-source-2.6</classname>,</phrase> csomagok használata " +"helyett, és még így is rendelkezésedre áll a <classname>kernel-package</" +"classname> kernel-fordítási módszer használata." #. Tag: para #: post-install.xml:390 #, no-c-format -msgid "Note that you'll find complete documentation on using <classname>kernel-package</classname> under <filename>/usr/share/doc/kernel-package</filename>. This section just contains a brief tutorial." -msgstr "Jó tudni, hogy a <classname>kernel-package</classname> módról teljes leírás található a <filename>/usr/share/doc/kernel-package</filename> könyvtárban." +msgid "" +"Note that you'll find complete documentation on using <classname>kernel-" +"package</classname> under <filename>/usr/share/doc/kernel-package</" +"filename>. This section just contains a brief tutorial." +msgstr "" +"Jó tudni, hogy a <classname>kernel-package</classname> módról teljes leírás " +"található a <filename>/usr/share/doc/kernel-package</filename> könyvtárban." #. Tag: para #: post-install.xml:397 #, no-c-format -msgid "Hereafter, we'll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory<footnote> <para> There are other locations where you can extract kernel sources and build your custom kernel, but this is easiest as it does not require special permissions. </para> </footnote>. We'll also assume that your kernel version is &kernelversion;. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using <phrase condition=\"classic-kpkg\"><userinput>tar xjf /usr/src/kernel-source-&kernelversion;.tar.bz2</userinput></phrase> <phrase condition=\"common-kpkg\"><userinput>tar xjf /usr/src/linux-source-&kernelversion;.tar.bz2</userinput></phrase> and change to the directory <phrase condition=\"classic-kpkg\"><filename>kernel-source-&kernelversion;</filename></phrase> <phrase condition=\"common-kpkg\"><filename>linux-source-&kernelversion;</filename></phrase> that will have been created." -msgstr "Mostantól azt feltételezzük, hogy szabadon mozogsz a gépen, és a kernel forrását kicsomagolod a saját könyvtáradba<footnote> <para> Vannak más helyek is, ahova kicsomagolhatod és ahol elkészítheted saját kerneledet, de ez a legegyszerűbb és nem igényel különleges jogokat.. </para> </footnote>. A példában azt vesszük, hogy kerneled verziója &kernelversion;. Győződj meg, hogy abban a könyvtárban vagy, ahova ki akarod bontani a kernelforrásokat, csomagold ki őket így: <phrase condition=\"classic-kpkg\"><userinput>tar xjf /usr/src/kernel-source-&kernelversion;.tar.bz2</userinput></phrase> <phrase condition=\"common-kpkg\"><userinput>tar xjf /usr/src/linux-source-&kernelversion;.tar.bz2</userinput></phrase> és lépj a létrejött <phrase condition=\"classic-kpkg\"><filename>kernel-source-&kernelversion;</filename></phrase> <phrase condition=\"common-kpkg\"><filename>linux-source-&kernelversion;</filename></phrase> könyvtárba." +msgid "" +"Hereafter, we'll assume you have free rein over your machine and will " +"extract your kernel source to somewhere in your home directory<footnote> " +"<para> There are other locations where you can extract kernel sources and " +"build your custom kernel, but this is easiest as it does not require special " +"permissions. </para> </footnote>. We'll also assume that your kernel version " +"is &kernelversion;. Make sure you are in the directory to where you want to " +"unpack the kernel sources, extract them using <phrase condition=\"classic-" +"kpkg\"><userinput>tar xjf /usr/src/kernel-source-&kernelversion;.tar.bz2</" +"userinput></phrase> <phrase condition=\"common-kpkg\"><userinput>tar xjf /" +"usr/src/linux-source-&kernelversion;.tar.bz2</userinput></phrase> and change " +"to the directory <phrase condition=\"classic-kpkg\"><filename>kernel-source-" +"&kernelversion;</filename></phrase> <phrase condition=\"common-kpkg" +"\"><filename>linux-source-&kernelversion;</filename></phrase> that will have " +"been created." +msgstr "" +"Mostantól azt feltételezzük, hogy szabadon mozogsz a gépen, és a kernel " +"forrását kicsomagolod a saját könyvtáradba<footnote> <para> Vannak más " +"helyek is, ahova kicsomagolhatod és ahol elkészítheted saját kerneledet, de " +"ez a legegyszerűbb és nem igényel különleges jogokat.. </para> </footnote>. " +"A példában azt vesszük, hogy kerneled verziója &kernelversion;. Győződj meg, " +"hogy abban a könyvtárban vagy, ahova ki akarod bontani a kernelforrásokat, " +"csomagold ki őket így: <phrase condition=\"classic-kpkg\"><userinput>tar " +"xjf /usr/src/kernel-source-&kernelversion;.tar.bz2</userinput></phrase> " +"<phrase condition=\"common-kpkg\"><userinput>tar xjf /usr/src/linux-source-" +"&kernelversion;.tar.bz2</userinput></phrase> és lépj a létrejött <phrase " +"condition=\"classic-kpkg\"><filename>kernel-source-&kernelversion;</" +"filename></phrase> <phrase condition=\"common-kpkg\"><filename>linux-source-" +"&kernelversion;</filename></phrase> könyvtárba." #. Tag: para #: post-install.xml:422 #, no-c-format -msgid "Now, you can configure your kernel. Run <userinput>make xconfig</userinput> if X11 is installed, configured and being run; run <userinput>make menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</classname> installed). Take the time to read the online help and choose carefully. When in doubt, it is typically better to include the device driver (the software which manages hardware peripherals, such as Ethernet cards, SCSI controllers, and so on) you are unsure about. Be careful: other options, not related to a specific hardware, should be left at the default value if you do not understand them. Do not forget to select <quote>Kernel module loader</quote> in <quote>Loadable module support</quote> (it is not selected by default). If not included, your Debian installation will experience problems." -msgstr "Most jöhet a kernel beállítása. Indíts egy <userinput>make xconfig</userinput> parancsot, ha X alatt akarsz dolgozni és erre módod van; vagy futtasd a <userinput>make menuconfig</userinput> parancsot (a <classname>libncurses5-dev</classname> csomag kell). Szánj időt a súgó elolvasására és válassz ésszerűen. Kétség esetén általában jobb kiválasztani egy olyan eszköz-meghajtót (azok a szoftverek, melyek a hardver perifériákat kezelik, például hálózati (ethernet) kártyák, SCSI vezérlők, és így tovább), melyben nem vagy biztos. Légy óvatos: más lehetőségeket, melyek nem adott hardverre vonatkoznak, hagyj a megadott értéken, ha nem érted. Ne feledd kijelölni a <quote>Kernel module loader</quote> lehetőséget a <quote>Loadable module support</quote> menüben (ez nincs alapban kijelölve). Ha nem adod meg, akkor a Debian telepítésed valószínűleg hibákat fog észlelni." +msgid "" +"Now, you can configure your kernel. Run <userinput>make xconfig</userinput> " +"if X11 is installed, configured and being run; run <userinput>make " +"menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</" +"classname> installed). Take the time to read the online help and choose " +"carefully. When in doubt, it is typically better to include the device " +"driver (the software which manages hardware peripherals, such as Ethernet " +"cards, SCSI controllers, and so on) you are unsure about. Be careful: other " +"options, not related to a specific hardware, should be left at the default " +"value if you do not understand them. Do not forget to select <quote>Kernel " +"module loader</quote> in <quote>Loadable module support</quote> (it is not " +"selected by default). If not included, your Debian installation will " +"experience problems." +msgstr "" +"Most jöhet a kernel beállítása. Indíts egy <userinput>make xconfig</" +"userinput> parancsot, ha X alatt akarsz dolgozni és erre módod van; vagy " +"futtasd a <userinput>make menuconfig</userinput> parancsot (a " +"<classname>libncurses5-dev</classname> csomag kell). Szánj időt a súgó " +"elolvasására és válassz ésszerűen. Kétség esetén általában jobb kiválasztani " +"egy olyan eszköz-meghajtót (azok a szoftverek, melyek a hardver perifériákat " +"kezelik, például hálózati (ethernet) kártyák, SCSI vezérlők, és így tovább), " +"melyben nem vagy biztos. Légy óvatos: más lehetőségeket, melyek nem adott " +"hardverre vonatkoznak, hagyj a megadott értéken, ha nem érted. Ne feledd " +"kijelölni a <quote>Kernel module loader</quote> lehetőséget a " +"<quote>Loadable module support</quote> menüben (ez nincs alapban kijelölve). " +"Ha nem adod meg, akkor a Debian telepítésed valószínűleg hibákat fog " +"észlelni." #. Tag: para #: post-install.xml:437 #, no-c-format -msgid "Clean the source tree and reset the <classname>kernel-package</classname> parameters. To do that, do <userinput>make-kpkg clean</userinput>." -msgstr "Tisztítsd a forrást és a <classname>kernel-package</classname> paramétereket. Add ki a <userinput>make-kpkg clean</userinput> parancsot." +msgid "" +"Clean the source tree and reset the <classname>kernel-package</classname> " +"parameters. To do that, do <userinput>make-kpkg clean</userinput>." +msgstr "" +"Tisztítsd a forrást és a <classname>kernel-package</classname> " +"paramétereket. Add ki a <userinput>make-kpkg clean</userinput> parancsot." #. Tag: para #: post-install.xml:442 #, no-c-format -msgid "Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image</userinput>. The version number of <quote>1.0</quote> can be changed at will; this is just a version number that you will use to track your kernel builds. Likewise, you can put any word you like in place of <quote>custom</quote> (e.g., a host name). Kernel compilation may take quite a while, depending on the power of your machine." -msgstr "Most fordítsd le a kernelt: <userinput>fakeroot make-kpkg --initrd --revision=egyedi.1.0 kernel_image</userinput>. Az <quote>1.0</quote> verziószám bármi lehet; ez csak arra jó, hogy többszöri fordítás esetén kövesd ezek sorát. Az <quote>egyedi</quote> szó helyére is bármit tehetsz (például a gép nevét). A kernel fordítás eltarthat egy ideig, attól függ, milyen géped van." +msgid "" +"Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --" +"revision=custom.1.0 kernel_image</userinput>. The version number of " +"<quote>1.0</quote> can be changed at will; this is just a version number " +"that you will use to track your kernel builds. Likewise, you can put any " +"word you like in place of <quote>custom</quote> (e.g., a host name). Kernel " +"compilation may take quite a while, depending on the power of your machine." +msgstr "" +"Most fordítsd le a kernelt: <userinput>fakeroot make-kpkg --initrd --" +"revision=egyedi.1.0 kernel_image</userinput>. Az <quote>1.0</quote> " +"verziószám bármi lehet; ez csak arra jó, hogy többszöri fordítás esetén " +"kövesd ezek sorát. Az <quote>egyedi</quote> szó helyére is bármit tehetsz " +"(például a gép nevét). A kernel fordítás eltarthat egy ideig, attól függ, " +"milyen géped van." #. Tag: para #: post-install.xml:452 #, no-c-format -msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <phrase condition=\"classic-kpkg\"> <userinput>dpkg -i ../kernel-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> <phrase condition=\"common-kpkg\"> <userinput>dpkg -i ../linux-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, <phrase condition=\"classic-kpkg\">e.g., if you have PCMCIA,</phrase> you'll need to install that package as well." -msgstr "A fordítás végeztével más csomaghoz hasonlóan telepítheted az egyedi kernelt. Rendszergazdaként add ki ezt a parancsot: <phrase condition=\"classic-kpkg\"> <userinput>dpkg -i ../kernel-image-&kernelversion;-<replaceable>alarchitektúra</replaceable>_egyedi.1.0_&architecture;.deb</userinput>. </phrase> <phrase condition=\"common-kpkg\"> <userinput>dpkg -i ../linux-image-&kernelversion;-<replaceable>alarchitektúra</replaceable>_egyedi.1.0_&architecture;.deb</userinput>. </phrase> Az <replaceable>alarchitektúra</replaceable> rész egy lehetséges al-architektúra, <phrase arch=\"i386\"> például <quote>686</quote>, </phrase> a beállított kernelopcióktól is függ. A <userinput>dpkg -i</userinput> telepíti a kernelt kiegészítő támogató fájlokkal. Például a <filename>System.map</filename> megfelelően telepítésre kerül (kernelhibák keresését segíti), és a <filename>/boot/config-&kernelversion;</filename> is telepítésre kerül, mely a beállításokat tartalmazza. Az új kernel csomag automatikusak frissíti is a boott betöltőt. Ha modul csomagot is készítettél <phrase condition=\"classic-kpkg\">például PCMCIA esetén,</phrase> azt a csomagot is telepítened kell." +msgid "" +"Once the compilation is complete, you can install your custom kernel like " +"any package. As root, do <phrase condition=\"classic-kpkg\"> <userinput>dpkg " +"-i ../kernel-image-&kernelversion;-<replaceable>subarchitecture</" +"replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> <phrase " +"condition=\"common-kpkg\"> <userinput>dpkg -i ../linux-image-&kernelversion;-" +"<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</" +"userinput>. </phrase> The <replaceable>subarchitecture</replaceable> part is " +"an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>686</" +"quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -" +"i</userinput> will install the kernel, along with some other nice supporting " +"files. For instance, the <filename>System.map</filename> will be properly " +"installed (helpful for debugging kernel problems), and <filename>/boot/" +"config-&kernelversion;</filename> will be installed, containing your current " +"configuration set. Your new kernel package is also clever enough to " +"automatically update your boot loader to use the new kernel. If you have " +"created a modules package, <phrase condition=\"classic-kpkg\">e.g., if you " +"have PCMCIA,</phrase> you'll need to install that package as well." +msgstr "" +"A fordítás végeztével más csomaghoz hasonlóan telepítheted az egyedi " +"kernelt. Rendszergazdaként add ki ezt a parancsot: <phrase condition=" +"\"classic-kpkg\"> <userinput>dpkg -i ../kernel-image-&kernelversion;-" +"<replaceable>alarchitektúra</replaceable>_egyedi.1.0_&architecture;.deb</" +"userinput>. </phrase> <phrase condition=\"common-kpkg\"> <userinput>dpkg -" +"i ../linux-image-&kernelversion;-<replaceable>alarchitektúra</" +"replaceable>_egyedi.1.0_&architecture;.deb</userinput>. </phrase> Az " +"<replaceable>alarchitektúra</replaceable> rész egy lehetséges al-" +"architektúra, <phrase arch=\"i386\"> például <quote>686</quote>, </phrase> a " +"beállított kernelopcióktól is függ. A <userinput>dpkg -i</userinput> " +"telepíti a kernelt kiegészítő támogató fájlokkal. Például a <filename>System." +"map</filename> megfelelően telepítésre kerül (kernelhibák keresését segíti), " +"és a <filename>/boot/config-&kernelversion;</filename> is telepítésre kerül, " +"mely a beállításokat tartalmazza. Az új kernel csomag automatikusak frissíti " +"is a boott betöltőt. Ha modul csomagot is készítettél <phrase condition=" +"\"classic-kpkg\">például PCMCIA esetén,</phrase> azt a csomagot is " +"telepítened kell." #. Tag: para #: post-install.xml:479 #, no-c-format -msgid "It is time to reboot the system: read carefully any warning that the above step may have produced, then <userinput>shutdown -r now</userinput>." -msgstr "Ideje újraindítani a rendszert: olvass el gondosan minden figyelmeztetést, amit a fentiek írtak, és ezután jöhet a <userinput>shutdown -r now</userinput>." +msgid "" +"It is time to reboot the system: read carefully any warning that the above " +"step may have produced, then <userinput>shutdown -r now</userinput>." +msgstr "" +"Ideje újraindítani a rendszert: olvass el gondosan minden figyelmeztetést, " +"amit a fentiek írtak, és ezután jöhet a <userinput>shutdown -r now</" +"userinput>." #. Tag: para #: post-install.xml:484 #, no-c-format -msgid "For more information on Debian kernels and kernel compilation, see the <ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>." -msgstr "További adatokért a Debian kernelekről és kernel-fordításról, lásd a <ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Kézikönyvet</ulink>." +msgid "" +"For more information on Debian kernels and kernel compilation, see the " +"<ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. " +"For more information on <classname>kernel-package</classname>, read the fine " +"documentation in <filename>/usr/share/doc/kernel-package</filename>." +msgstr "" +"További adatokért a Debian kernelekről és kernel-fordításról, lásd a <ulink " +"url=\"&url-kernel-handbook;\">Debian Linux Kernel Kézikönyvet</ulink>." #. Tag: title #: post-install.xml:500 @@ -327,32 +765,89 @@ msgstr "Egy sérült rendszer helyreállítása" #. Tag: para #: post-install.xml:501 #, no-c-format -msgid "Sometimes, things go wrong, and the system you've carefully installed is no longer bootable. Perhaps the boot loader configuration broke while trying out a change, or perhaps a new kernel you installed won't boot, or perhaps cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</filename>. Regardless of the cause, you'll need to have a system to work from while you fix it, and rescue mode can be useful for this." -msgstr "Mint bármi, egy gondosan telepített rendszer is elromolhat. Például egy változtatásnál elállítjuk a boot betöltőt, egy nem megfelelő kernelre váltunk és nem indul, vagy teljesen véletlenül, például a lemezt érő kozmikus háttérsugárzás átbillent egy érzékeny bitet a <filename>/sbin/init</filename> fájlban. Ezért szükséged lesz egy rendszerre, melyről javíthatsz, és erre kiválóan alkalmas lesz például a telepítő mentési módja." +msgid "" +"Sometimes, things go wrong, and the system you've carefully installed is no " +"longer bootable. Perhaps the boot loader configuration broke while trying " +"out a change, or perhaps a new kernel you installed won't boot, or perhaps " +"cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</" +"filename>. Regardless of the cause, you'll need to have a system to work " +"from while you fix it, and rescue mode can be useful for this." +msgstr "" +"Mint bármi, egy gondosan telepített rendszer is elromolhat. Például egy " +"változtatásnál elállítjuk a boot betöltőt, egy nem megfelelő kernelre " +"váltunk és nem indul, vagy teljesen véletlenül, például a lemezt érő " +"kozmikus háttérsugárzás átbillent egy érzékeny bitet a <filename>/sbin/init</" +"filename> fájlban. Ezért szükséged lesz egy rendszerre, melyről javíthatsz, " +"és erre kiválóan alkalmas lesz például a telepítő mentési módja." #. Tag: para #: post-install.xml:511 #, no-c-format -msgid "To access rescue mode, type <userinput>rescue</userinput> at the <prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/enable=true</userinput> boot parameter. You'll be shown the first few screens of the installer, with a note in the corner of the display to indicate that this is rescue mode, not a full installation. Don't worry, your system is not about to be overwritten! Rescue mode simply takes advantage of the hardware detection facilities available in the installer to ensure that your disks, network devices, and so on are available to you while repairing your system." -msgstr "A mentési mód eléréséhez üsd be <userinput>rescue</userinput> szót a <prompt>boot:</prompt> beviteli jelnél, vagy indíts a <userinput>rescue/enable=true</userinput> paraméterrel. A telepítő 1. pár képernyőjét látod a sarokban megjegyezve, hogy ez mentési mód nem egy teljes telepítés. Ne aggódj, a rendszeredet nem fogja felülírni. A mentési mód egyszerűen csak kihasználja a telepítőben lévő hardver-felismerés előnyeit, hogy a javításhoz használni tudd őket." +msgid "" +"To access rescue mode, type <userinput>rescue</userinput> at the " +"<prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/" +"enable=true</userinput> boot parameter. You'll be shown the first few " +"screens of the installer, with a note in the corner of the display to " +"indicate that this is rescue mode, not a full installation. Don't worry, " +"your system is not about to be overwritten! Rescue mode simply takes " +"advantage of the hardware detection facilities available in the installer to " +"ensure that your disks, network devices, and so on are available to you " +"while repairing your system." +msgstr "" +"A mentési mód eléréséhez üsd be <userinput>rescue</userinput> szót a " +"<prompt>boot:</prompt> beviteli jelnél, vagy indíts a <userinput>rescue/" +"enable=true</userinput> paraméterrel. A telepítő 1. pár képernyőjét látod a " +"sarokban megjegyezve, hogy ez mentési mód nem egy teljes telepítés. Ne " +"aggódj, a rendszeredet nem fogja felülírni. A mentési mód egyszerűen csak " +"kihasználja a telepítőben lévő hardver-felismerés előnyeit, hogy a " +"javításhoz használni tudd őket." #. Tag: para #: post-install.xml:526 #, no-c-format -msgid "Instead of the partitioning tool, you should now be presented with a list of the partitions on your system, and asked to select one of them. Normally, you should select the partition containing the root file system that you need to repair. You may select partitions on RAID and LVM devices as well as those created directly on disks." -msgstr "A particionáló eszköz helyett egyszerűen kiválaszthatsz egyet. Itt általában a javítandó rendszer gyökér fájlrendszerét tartalmazó partíciót kell kiválasztanod." +msgid "" +"Instead of the partitioning tool, you should now be presented with a list of " +"the partitions on your system, and asked to select one of them. Normally, " +"you should select the partition containing the root file system that you " +"need to repair. You may select partitions on RAID and LVM devices as well as " +"those created directly on disks." +msgstr "" +"A particionáló eszköz helyett egyszerűen kiválaszthatsz egyet. Itt általában " +"a javítandó rendszer gyökér fájlrendszerét tartalmazó partíciót kell " +"kiválasztanod." #. Tag: para #: post-install.xml:534 #, no-c-format -msgid "If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. <phrase arch=\"x86\"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. </phrase>" -msgstr "Ha lehetséges, a telepítő bead egy héj promptot a kijelölt fájlrendszeren, mellyel bármilyen javítási műveletet végezhetsz. <phrase arch=\"x86\"> Például ha újra kell tenned a GRUB boot betöltőt az 1. merevlemez MBR-jébe, kiadhatod a <userinput>grub-install '(hd0)'</userinput> parancsot. </phrase>" +msgid "" +"If possible, the installer will now present you with a shell prompt in the " +"file system you selected, which you can use to perform any necessary " +"repairs. <phrase arch=\"x86\"> For example, if you need to reinstall the " +"GRUB boot loader into the master boot record of the first hard disk, you " +"could enter the command <userinput>grub-install '(hd0)'</userinput> to do " +"so. </phrase>" +msgstr "" +"Ha lehetséges, a telepítő bead egy héj promptot a kijelölt fájlrendszeren, " +"mellyel bármilyen javítási műveletet végezhetsz. <phrase arch=\"x86\"> " +"Például ha újra kell tenned a GRUB boot betöltőt az 1. merevlemez MBR-jébe, " +"kiadhatod a <userinput>grub-install '(hd0)'</userinput> parancsot. </phrase>" #. Tag: para #: post-install.xml:546 #, no-c-format -msgid "If the installer cannot run a usable shell in the root file system you selected, perhaps because the file system is corrupt, then it will issue a warning and offer to give you a shell in the installer environment instead. You may not have as many tools available in this environment, but they will often be enough to repair your system anyway. The root file system you selected will be mounted on the <filename>/target</filename> directory." -msgstr "Ha a telepítő nem tud használható héjat futtatni a kijelölt gyökér fájlrendszeren, mert az például sérült, figyelmeztet és felajánlja, hogy nyit egy héjat a telepítő környezetén belül. Itt nincs annyi eszközöd, de általában elég a rendszer alapvető megjavításához. A kijelölt gyökér fájlrendszert a <filename>/target</filename> könyvtárba csatolja." +msgid "" +"If the installer cannot run a usable shell in the root file system you " +"selected, perhaps because the file system is corrupt, then it will issue a " +"warning and offer to give you a shell in the installer environment instead. " +"You may not have as many tools available in this environment, but they will " +"often be enough to repair your system anyway. The root file system you " +"selected will be mounted on the <filename>/target</filename> directory." +msgstr "" +"Ha a telepítő nem tud használható héjat futtatni a kijelölt gyökér " +"fájlrendszeren, mert az például sérült, figyelmeztet és felajánlja, hogy " +"nyit egy héjat a telepítő környezetén belül. Itt nincs annyi eszközöd, de " +"általában elég a rendszer alapvető megjavításához. A kijelölt gyökér " +"fájlrendszert a <filename>/target</filename> könyvtárba csatolja." #. Tag: para #: post-install.xml:555 @@ -363,6 +858,11 @@ msgstr "A héjből való kilépés újraindít." #. Tag: para #: post-install.xml:559 #, no-c-format -msgid "Finally, note that repairing broken systems can be difficult, and this manual does not attempt to go into all the things that might have gone wrong or how to fix them. If you have problems, consult an expert." -msgstr "Természetesen egy sérült rendszer javítása ennél jóval nehezebb is lehet és e leírás nem szólhat az összes lehetséges részletről. Ha kérdésed van, bátran kérd a közösség segítségét!" - +msgid "" +"Finally, note that repairing broken systems can be difficult, and this " +"manual does not attempt to go into all the things that might have gone wrong " +"or how to fix them. If you have problems, consult an expert." +msgstr "" +"Természetesen egy sérült rendszer javítása ennél jóval nehezebb is lehet és " +"e leírás nem szólhat az összes lehetséges részletről. Ha kérdésed van, " +"bátran kérd a közösség segítségét!" |