# Hungarian translation of Debian Installation Guide boot-installer # SZERVÁC Attila , 2006. # NAGY Zoltán , 2007. # msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2016-11-25 19:03+0000\n" "PO-Revision-Date: 2007-03-18 16:39+0100\n" "Last-Translator: SZERVÁC Attila \n" "Language-Team: Hungarian \n" "Language: hu\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Poedit-Country: HUNGARY\n" "X-Poedit-Language: Hungarian\n" #. Tag: title #: boot-installer.xml:4 #, no-c-format msgid "Booting the Installation System" msgstr "A telepítő rendszer indítása" #. Tag: title #: boot-installer.xml:9 #, no-c-format msgid "Booting the Installer on &arch-title;" msgstr "A telepítő indítása &arch-title; architektúrán" #. Tag: para #: boot-installer.xml:15 #, no-c-format msgid "" "If you have any other operating systems on your system that you wish to keep " "(dual boot setup), you should make sure that they have been properly shut " "down before you boot the installer. Installing an " "operating system while another operating system is in hibernation (has been " "suspended to disk) could result in loss of, or damage to the state of the " "suspended operating system which could cause problems when it is rebooted." msgstr "" #. Tag: para #: boot-installer.xml:26 #, no-c-format msgid "" "For information on how to boot the graphical installer, see ." msgstr "" "A grafikus telepítő indításáról lásd az alábbit: ." #. Tag: title #: boot-installer.xml:39 #, fuzzy, no-c-format #| msgid "Booting from Firmware" msgid "Boot image formats" msgstr "Indítás firmware-ből" #. Tag: para #: boot-installer.xml:40 #, no-c-format msgid "" "On ARM-based systems in most cases one of two formats for boot images is " "used: a) standard Linux zImage-format kernels (vmlinuz) in " "conjunction with standard Linux initial ramdisks (initrd.gz) " "or b) uImage-format kernels (uImage) in conjunction with " "corresponding initial ramdisks (uInitrd)." msgstr "" #. Tag: para #: boot-installer.xml:48 #, no-c-format msgid "" "uImage/uInitrd are image formats designed for the U-Boot firmware that is " "used on many ARM-based systems (mostly 32-bit ones). Older U-Boot versions " "can only boot files in uImage/uInitrd format, so these are often used on " "older armel systems. Newer U-Boot versions can - besides booting uImages/" "uInitrds - also boot standard Linux kernels and ramdisk images, but the " "command syntax to do that is slightly different from that for booting " "uImages." msgstr "" #. Tag: para #: boot-installer.xml:57 #, no-c-format msgid "" "For systems using a multiplatform kernel, besides kernel and initial ramdisk " "a so-called device-tree file (or device-tree blob, dtb) is " "needed. It is specific to each supported system and contains a description " "of the particular hardware. The dtb should be supplied on the device by the " "firmware, but in practice a newer one often needs to be loaded." msgstr "" #. Tag: title #: boot-installer.xml:68 boot-installer.xml:86 #, fuzzy, no-c-format #| msgid "Boot Configuration" msgid "Console configuration" msgstr "Indító beállítás" #. Tag: para #: boot-installer.xml:69 #, no-c-format msgid "" "The netboot tarball (), and the " "installer SD-card images () use " "the (platform-specific) default console that is defined by U-Boot in the " "console variable. In most cases that is a serial console, so " "on those platforms you by default need a serial console cable to use the " "installer." msgstr "" #. Tag: para #: boot-installer.xml:78 #, no-c-format msgid "" "On platforms which also support a video console, you can modify the U-Boot " "console variable accordingly if you would like the installer " "to start on the video console." msgstr "" #. Tag: para #: boot-installer.xml:87 #, no-c-format msgid "" "The graphical installer is not enabled on the arm64 &d-i; images for jessie " "so the serial console is used. The console device should be detected " "automatically from the firmware, but if it is not then after you boot linux " "from the GRUB menu you will see a Booting Linux message, then " "nothing more." msgstr "" #. Tag: para #: boot-installer.xml:94 #, no-c-format msgid "" "If you hit this issue you will need to set a specific console config on the " "kernel command line. Hit e for Edit Kernel " "command-line at the GRUB menu, and change " "--- quiet to " "console=<device>,<speed> e.g. console=ttyAMA0,115200n8. When finished hit Control x to continue booting with new setting." msgstr "" #. Tag: title #: boot-installer.xml:108 #, fuzzy, no-c-format #| msgid "Submitting Installation Reports" msgid "Juno Installation" msgstr "Telepítő jelentések küldése" #. Tag: para #: boot-installer.xml:109 #, no-c-format msgid "" "Juno has UEFI so the install is straightforward. The most practical method " "is installing from USB stick. You need up to date firmware for USB-booting " "to work. Builds from &url-juno-firmware; after March 2015 tested OK. Consult Juno documentation on firmware " "updating." msgstr "" #. Tag: para #: boot-installer.xml:116 #, no-c-format msgid "" "Prepare a standard arm64 CD image on a USB stick. Insert it in one of the " "USB ports on the back. Plug a serial cable into the upper 9-pin serial port " "on the back. If you need networking (netboot image) plug the ethernet cable " "into the socket on the front of the machine." msgstr "" #. Tag: para #: boot-installer.xml:123 #, no-c-format msgid "" "Run a serial console at 115200, 8bit no parity, and boot the Juno. It should " "boot from the USB stick to a GRUB menu. The console config is not correctly " "detected on Juno so just hitting &enterkey; will show no kernel output. Set " "the console to console=ttyAMA0,115200n8 (as described in ). " "Control x to boot " "should show you the &d-i; screens, and allow you to proceed with a standard " "installation." msgstr "" #. Tag: title #: boot-installer.xml:136 #, no-c-format msgid "Applied Micro Mustang Installation" msgstr "" #. Tag: para #: boot-installer.xml:137 #, no-c-format msgid "" "UEFI is available for this machine but it is normally shipped with U-Boot so " "you will need to either install UEFI firmware first then use standard boot/" "install methods, or use U-Boot boot methods. Also USB is not supported in " "the jessie kernel so installing from a USB stick does not work. You must use " "a serial console to control the installation because the graphical installer " "is not enabled on the arm64 architecture." msgstr "" #. Tag: para #: boot-installer.xml:146 #, no-c-format msgid "" "The recommended install method is to copy the &d-i; kernel and initrd onto " "the hard drive, using the openembedded system supplied with the machine, " "then boot from that to run the installer. Alternatively use TFTP to get the " "kernel/dtb/initrd copied over and booted (). After installation, manual changes to boot from the installed image are " "needed." msgstr "" #. Tag: para #: boot-installer.xml:155 #, no-c-format msgid "" "Run a serial console at 115200, 8bit no parity, and boot the machine. Reboot " "the machine and when you see Hit any key to stop autoboot: " "hit a key to get a Mustang# prompt. Then use U-Boot commands to load and " "boot the kernel, dtb and initrd." msgstr "" #. Tag: title #: boot-installer.xml:164 #, no-c-format msgid "Booting by TFTP" msgstr "Indítás TFTP segítségével" #. Tag: para #: boot-installer.xml:170 boot-installer.xml:832 boot-installer.xml:1468 #: boot-installer.xml:1652 boot-installer.xml:1974 boot-installer.xml:2122 #, fuzzy, no-c-format #| msgid "" #| "Booting from the network requires that you have a network connection and " #| "a TFTP network boot server (DHCP, RARP, or BOOTP)." msgid "" "Booting from the network requires that you have a network connection and a " "TFTP network boot server (and probably also a DHCP, RARP, or BOOTP server " "for automatic network configuration)." msgstr "" "A hálózati indítás egy hálózati kapcsolatot és egy TFTP hálózati indító " "kiszolgálót igényel (DHCP, RARP vagy BOOTP)." #. Tag: para #: boot-installer.xml:176 boot-installer.xml:838 boot-installer.xml:1474 #: boot-installer.xml:1658 boot-installer.xml:1980 boot-installer.xml:2128 #, no-c-format msgid "" "Older systems such as the 715 might require the use of an RBOOT server " "instead of a BOOTP server." msgstr "" "A régebbi rendszerek, például a 715 egy RBOOT kiszolgálót kérhetnek BOOTP " "helyett." #. Tag: para #: boot-installer.xml:181 boot-installer.xml:843 boot-installer.xml:1479 #: boot-installer.xml:1663 boot-installer.xml:1985 boot-installer.xml:2133 #, fuzzy, no-c-format #| msgid "" #| "The installation method to support network booting is described in ." msgid "" "The server-side setup to support network booting is described in ." msgstr "" "A hálózati indítást támogató telepítő mód leírása itt található: ." #. Tag: title #: boot-installer.xml:190 #, no-c-format msgid "TFTP-booting in U-Boot" msgstr "" #. Tag: para #: boot-installer.xml:191 #, no-c-format msgid "" "Network booting on systems using the U-Boot firmware consists of three " "steps: a) configuring the network, b) loading the images (kernel/initial " "ramdisk/dtb) into memory and c) actually executing the previosly loaded code." msgstr "" #. Tag: para #: boot-installer.xml:197 #, no-c-format msgid "" "First you have to configure the network, either automatically via DHCP by " "running \n" "setenv autoload no\n" "dhcp\n" " or manually by setting several environment " "variables \n" "setenv ipaddr <ip address of the client>\n" "setenv netmask <netmask>\n" "setenv serverip <ip address of the tftp server>\n" "setenv dnsip <ip address of the nameserver>\n" "setenv gatewayip <ip address of the default gateway>\n" " If you prefer, you can make these settings " "permanent by running" msgstr "" #. Tag: screen #: boot-installer.xml:204 #, no-c-format msgid "saveenv" msgstr "" #. Tag: para #: boot-installer.xml:206 #, no-c-format msgid "" "Afterwards you need to load the images (kernel/initial ramdisk/dtb) into " "memory. This is done with the tftpboot command, which has to be provided " "with the address at which the image shall be stored in memory. Unfortunately " "the memory map can vary from system to system, so there is no general rule " "which addresses can be used for this." msgstr "" #. Tag: para #: boot-installer.xml:214 #, no-c-format msgid "" "On some systems, U-Boot predefines a set of environment variables with " "suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. You " "can check whether they are defined by running \n" "printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n" " If they are not defined, you have to check your " "system's documentation for appropriate values and set them manually. For " "systems based on Allwinner SunXi SOCs (e.g. the Allwinner A10, architecture " "name sun4i or the Allwinner A20, architecture name " "sun7i), you can e.g. use the following values:" msgstr "" #. Tag: screen #: boot-installer.xml:225 #, no-c-format msgid "" "setenv kernel_addr_r 0x46000000\n" "setenv fdt_addr_r 0x47000000\n" "setenv ramdisk_addr_r 0x48000000" msgstr "" #. Tag: para #: boot-installer.xml:227 #, no-c-format msgid "" "When the load addresses are defined, you can load the images into memory " "from the previously defined tftp server with" msgstr "" #. Tag: screen #: boot-installer.xml:230 #, no-c-format msgid "" "tftpboot ${kernel_addr_r} <filename of the kernel image>\n" "tftpboot ${fdt_addr_r} <filename of the dtb>\n" "tftpboot ${ramdisk_addr_r} <filename of the initial ramdisk image>" msgstr "" #. Tag: para #: boot-installer.xml:232 #, no-c-format msgid "" "The third part is setting the kernel commandline and actually executing the " "loaded code. U-Boot passes the content of the bootargs " "environment variable as commandline to the kernel, so any parameters for the " "kernel and the installer - such as the console device (see ) or preseeding options (see and ) - can be set with a command " "like \n" "setenv bootargs console=ttyS0,115200 rootwait panic=10\n" " The exact command to execute the previously " "loaded code depends on the image format used. With uImage/uInitrd, the " "command is \n" "bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}\n" " and with native Linux images it is" msgstr "" #. Tag: screen #: boot-installer.xml:245 #, no-c-format msgid "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}" msgstr "" #. Tag: para #: boot-installer.xml:247 #, no-c-format msgid "" "Note: When booting standard linux images, it is important to load the " "initial ramdisk image after the kernel and the dtb as U-Boot sets the " "filesize variable to the size of the last file loaded and the bootz command " "requires the size of the ramdisk image to work correctly. In case of booting " "a platform-specific kernel, i.e. a kernel without device-tree, simply omit " "the ${fdt_addr_r} parameter." msgstr "" #. Tag: title #: boot-installer.xml:258 #, no-c-format msgid "Pre-built netboot tarball" msgstr "" #. Tag: para #: boot-installer.xml:259 #, no-c-format msgid "" "&debian; provides a pre-built tarball (&armmp-netboot-tarball;) that can " "simply be unpacked on your tftp server and contains all files necessary for " "netbooting. It also includes a boot script that automates all steps to load " "the installer. Modern U-Boot versions contain a tftp autoboot feature that " "becomes active if there is no bootable local storage device (MMC/SD, USB, " "IDE/SATA/SCSI) and then loads this boot script from the tftp server. " "Prerequisite for using this feature is that you have a dhcp server in your " "network which provides the client with the address of the tftp server." msgstr "" #. Tag: para #: boot-installer.xml:271 #, no-c-format msgid "" "If you would like to trigger the tftp autoboot feature from the U-Boot " "commandline, you can use the follwing command:" msgstr "" #. Tag: screen #: boot-installer.xml:274 #, no-c-format msgid "run bootcmd_dhcp" msgstr "" #. Tag: para #: boot-installer.xml:276 #, no-c-format msgid "" "To manually load the bootscript provided by the tarball, you can " "alternatively issue the following commands at the U-Boot prompt:" msgstr "" #. Tag: screen #: boot-installer.xml:280 #, no-c-format msgid "" "setenv autoload no\n" "dhcp\n" "tftpboot ${scriptaddr} /debian-installer/armhf/tftpboot.scr\n" "source ${scriptaddr}" msgstr "" #. Tag: title #: boot-installer.xml:288 #, fuzzy, no-c-format #| msgid "Booting from USB Memory Stick" msgid "Booting from USB Memory Stick with UEFI" msgstr "Indítás USB tárról" #. Tag: para #: boot-installer.xml:294 boot-installer.xml:553 #, fuzzy, no-c-format #| msgid "" #| "Let's assume you have prepared everything from and . Now just plug your USB " #| "stick into some free USB connector and reboot the computer. The system " #| "should boot up, and you should be presented with the boot: prompt. Here you can enter optional boot arguments, or just hit " #| "&enterkey;." msgid "" "If your computer will boot from USB, this will probably be the easiest route " "for installation. Assuming you have prepared everything from and , just plug your " "USB stick into some free USB connector and reboot the computer. The system " "should boot up, and unless you have used the flexible way to build the stick " "and not enabled it, you should be presented with a graphical boot menu (on " "hardware that supports it). Here you can select various installer options, " "or just hit &enterkey;." msgstr "" "A korábbi és részben írtak elkészültét feltételezzük. Dugd be az USB tárolót " "egy szabad USB csatlakozóba és indítsd újra a gépet. Ha minden rendben, a " "rendszer erről fog indulni és erről ad egy boot: jelet. A 2 " "lehetőség: további indító argumentumok megadása vagy az &enterkey; leütése." #. Tag: title #: boot-installer.xml:310 #, fuzzy, no-c-format #| msgid "Booting from USB memory stick" msgid "Booting from a USB stick in U-Boot" msgstr "Indítás USB memóriáról" #. Tag: para #: boot-installer.xml:311 #, no-c-format msgid "" "Many modern U-Boot versions have USB support and allow booting from USB mass " "storage devices such as USB sticks. Unfortunately the exact steps required " "to do that can vary quite a bit from device to device." msgstr "" #. Tag: para #: boot-installer.xml:318 #, no-c-format msgid "" "U-Boot v2014.10 has introduced a common commandline handling and autoboot " "framework. This allows building generic boot images that work on any system " "implementing this framework. The &d-i; supports installation from a USB " "stick on such systems, but unfortunately not all platforms have adopted this " "new framework yet." msgstr "" #. Tag: para #: boot-installer.xml:327 #, no-c-format msgid "" "To build a bootable USB stick for installing &debian;, unpack the hd-media " "tarball (see ) onto a USB stick formatted " "with a filesystem supported by the U-Boot version on your device. For modern " "U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / ext4 usually works. " "Then copy the ISO image file of the first &debian; installation CD or DVD " "onto the stick." msgstr "" #. Tag: para #: boot-installer.xml:337 #, no-c-format msgid "" "The autoboot framework in modern U-Boot versions works similar to the boot " "ordering options in a PC BIOS, i.e. it checks a list of possible boot " "devices for a valid boot image and starts the first one it finds. If there " "is no operating system installed, plugging in the USB stick and powering up " "the system should result in starting the installer. You can also initiate " "the USB-boot process any time from the U-Boot prompt by entering the " "run bootcmd_usb0 command." msgstr "" #. Tag: para #: boot-installer.xml:347 #, no-c-format msgid "" "One problem that can come up when booting from a USB stick while using a " "serial console can be a console baudrate mismatch. If a console variable is " "defined in U-Boot, the &d-i; boot script automatically passes it to the " "kernel to set the primary console device and, if applicable, the console " "baudrate. Unfortunately the handling of the console variable varies from " "platform to platform - on some platforms, the console variable includes the " "baudrate (as in console=ttyS0,115200), while on other " "platforms the console variable contains only the device (as in " "console=ttyS0). The latter case leads to a garbled console " "output when the default baudrate differs between U-Boot and the kernel. " "Modern U-Boot versions often use 115200 baud while the kernel still defaults " "to the traditional 9600 baud. If this happens, you should manually set the " "console variable to contain the correct baudrate for your system and then " "start the installer with the run bootcmd_usb0 command." msgstr "" #. Tag: title #: boot-installer.xml:368 #, no-c-format msgid "Using pre-built SD-card images with the installer" msgstr "" #. Tag: para #: boot-installer.xml:369 #, no-c-format msgid "" "For a number of systems, Debian provides SD card images that contain both U-" "Boot and the &d-i;. These images are provided in two variants - one for " "downloading the software packages over the network (available at &armmp-" "netboot-sd-img;) and one for offline installations using a Debian CD/DVD " "(available at &armmp-hd-media-sd-img;). To save space and network bandwidth, " "the images consist of two parts - a system-dependent part named " "firmware.<system-type>.img.gz, and a system-independent " "part named partition.img.gz." msgstr "" #. Tag: para #: boot-installer.xml:380 #, no-c-format msgid "" "To create a complete image from the two parts on Linux systems, you can use " "zcat as follows: zcat firmware.<system-type>." "img.gz partition.img.gz > complete_image.img On " "Windows systems, you have to first decompress the two parts separately, " "which can be done e.g. by using 7-Zip, and then concatenate the decompressed " "parts together by running the command copy /b " "firmware.<system-type>.img + partition.img complete_image.img in a Windows CMD.exe window." msgstr "" #. Tag: para #: boot-installer.xml:394 #, no-c-format msgid "" "Write the resulting image onto an SD card, e.g. by running the following " "command on a Linux system: cat complete_image.img " "> /dev/SD_CARD_DEVICE After plugging the SD card " "into the target system and powering the system up, the installer is loaded " "from the SD card. If you use the hd-media variant for offline installations, " "you must provide the installer with access to the first &debian; CD/DVD on a " "separate medium, which can e.g. be a CD/DVD ISO image on a USB stick." msgstr "" #. Tag: para #: boot-installer.xml:406 #, no-c-format msgid "" "When you come to the partitioning step in the installer (see ), you can delete or replace any previous partitions on " "the card. Once the installer is started, it runs completely in the system's " "main memory and does not need to access the SD card anymore, so you can use " "the full card for installing &debian;. The easiest way to create a proper " "partition layout on the SD card is to let the installer automatically create " "one for you (see )." msgstr "" #. Tag: title #: boot-installer.xml:547 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "Indítás USB tárról" #. Tag: title #: boot-installer.xml:568 boot-installer.xml:1082 boot-installer.xml:1738 #: boot-installer.xml:2156 #, no-c-format msgid "Booting from a CD-ROM" msgstr "Indítás egy CD-ROM lemezről" #. Tag: para #: boot-installer.xml:574 boot-installer.xml:1088 boot-installer.xml:1744 #: boot-installer.xml:2162 #, no-c-format msgid "" "If you have a CD set, and if your machine supports booting directly off the " "CD, great! Simply configure your system for booting " "off a CD as described in , " "insert your CD, reboot, and proceed to the next chapter." msgstr "" "Ha van egy CD-készleted és a géped támogatja a CD-lemezről indítást, akkor " "minden csodás. Egyszerűen állítsd be a gépet, hogy CD-" "lemezről induljon, ahogy a részben is " "leírjuk, tedd be a CD-lemezt, indítsd róla a gépet és végezd el a " "telepítést, erről a következő fejezet súg." #. Tag: para #: boot-installer.xml:584 boot-installer.xml:1098 boot-installer.xml:1754 #: boot-installer.xml:2172 #, no-c-format msgid "" "Note that certain CD drives may require special drivers, and thus be " "inaccessible in the early installation stages. If it turns out the standard " "way of booting off a CD doesn't work for your hardware, revisit this chapter " "and read about alternate kernels and installation methods which may work for " "you." msgstr "" "Egyes CD-eszközök különleges meghajtókat igényelnek és elérhetetlenek " "lehetnek a telepítő első lépéseiben. Ha a CD-lemezről indítás szokásos módja " "nem működik a gépeden, nézd át újra e fejezetet és olvasd el az eltérő " "kernelekről és telepítő módokról szóló részeket, mely megoldja ezt." #. Tag: para #: boot-installer.xml:592 boot-installer.xml:1106 boot-installer.xml:1762 #: boot-installer.xml:2180 #, fuzzy, no-c-format #| msgid "" #| "Even if you cannot boot from CD-ROM, you can probably install the " #| "&debian; system components and any packages you want from CD-ROM. Simply " #| "boot using a different media, such as floppies. When it's time to install " #| "the operating system, base system, and any additional packages, point the " #| "installation system at the CD-ROM drive." msgid "" "Even if you cannot boot from CD-ROM, you can probably install the &debian; " "system components and any packages you want from CD-ROM. Simply boot using a " "different medium and when it's time to install the operating system, base " "system, and any additional packages, point the installation system at the CD-" "ROM drive." msgstr "" "Még abban az esetben is, ha nem tudsz CD-ROM lemezről indítani, valószínűleg " "képes leszel a &debian; rendszer összetevőit és a kívánt csomagokat " "telepíteni ezekről. Egyszerűen indíts más médiumról, például flopiról. Az " "operációs rendszer, alaprendszer és tetszőleges további csomagok " "telepítésekor a telepítő rendszert a CD-ROM meghajtóra irányíthatod." #. Tag: para #: boot-installer.xml:600 boot-installer.xml:1114 boot-installer.xml:1770 #: boot-installer.xml:2188 #, no-c-format msgid "" "If you have problems booting, see ." msgstr "" "Ha gondjaid vannak ez indítással, lásd az részt." #. Tag: title #: boot-installer.xml:610 #, fuzzy, no-c-format #| msgid "Booting from Firmware" msgid "Booting from Windows" msgstr "Indítás firmware-ből" #. Tag: para #: boot-installer.xml:611 #, no-c-format msgid "To start the installer from Windows, you can either" msgstr "" #. Tag: para #: boot-installer.xml:616 #, fuzzy, no-c-format #| msgid "" #| "To boot the installer from hard disk, you must first download and place " #| "the needed files as described in ." msgid "" "obtain CD-ROM/DVD-ROM or USB memory " "stick installation media as described in respective or" msgstr "" "A telepítő merevlemezről indításához először le kell tölteni és elhelyezni a " " részben írt fájlokat." #. Tag: para #: boot-installer.xml:624 #, no-c-format msgid "" "download a standalone Windows executable, which is available as tools/win32-" "loader/stable/win32-loader.exe on the &debian; mirrors." msgstr "" #. Tag: para #: boot-installer.xml:632 #, no-c-format msgid "" "If you use an installation CD or DVD, a pre-installation program should be " "launched automatically when you insert the disc. In case Windows does not " "start it automatically, or if you are using a USB memory stick, you can run " "it manually by accessing the device and executing setup.exe." msgstr "" #. Tag: para #: boot-installer.xml:640 #, no-c-format msgid "" "After the program has been started, a few preliminary questions will be " "asked and the system will be prepared to reboot into the &debian-gnu; " "installer." msgstr "" #. Tag: title #: boot-installer.xml:650 #, fuzzy, no-c-format #| msgid "Booting from MacOS" msgid "Booting from DOS using loadlin" msgstr "Indítás MacOS alól" #. Tag: para #: boot-installer.xml:651 #, no-c-format msgid "" "Boot into DOS (not Windows). To do this, you can for instance boot from a " "recovery or diagnostic disk." msgstr "" #. Tag: para #: boot-installer.xml:656 #, no-c-format msgid "" "If you can access the installation CD, change the current drive to the CD-" "ROM drive, e.g. \n" "d:\n" " else make sure you have first prepared your hard " "disk as explained in , and change the " "current drive to it if needed." msgstr "" #. Tag: para #: boot-installer.xml:666 #, no-c-format msgid "" "Enter the subdirectory for the flavor you chose, e.g., " "\n" "cd \\&x86-install-dir;\n" " If you prefer using the graphical installer, " "enter the gtk sub-directory. \n" "cd gtk\n" " Next, execute install.bat. " "The kernel will load and launch the installer system." msgstr "" #. Tag: title #: boot-installer.xml:684 #, no-c-format msgid "" "Booting from Linux using LILO or GRUB" msgstr "" "Indítás Linuxból LILO vagy GRUB " "használatával" #. Tag: para #: boot-installer.xml:687 #, no-c-format msgid "" "To boot the installer from hard disk, you must first download and place the " "needed files as described in ." msgstr "" "A telepítő merevlemezről indításához először le kell tölteni és elhelyezni a " " részben írt fájlokat." #. Tag: para #: boot-installer.xml:692 #, no-c-format msgid "" "If you intend to use the hard drive only for booting and then download " "everything over the network, you should download the netboot/" "debian-installer/&architecture;/initrd.gz file and its " "corresponding kernel netboot/debian-installer/&architecture;/" "linux. This will allow you to repartition the hard disk from " "which you boot the installer, although you should do so with care." msgstr "" "Ha a merevlemez csak indításra a többi letöltésre pedig a hálózat szolgál, a " "netboot/debian-installer/&architecture;/initrd.gz fájl " "és a megfelelő netboot/debian-installer/&architecture;/linux kernel letöltése kell. Ezzel átparticionálható a telepítő " "indítására használt merevlemez, körültekintően." #. Tag: para #: boot-installer.xml:702 #, fuzzy, no-c-format #| msgid "" #| "Alternatively, if you intend to keep an existing partition on the hard " #| "drive unchanged during the install, you can download the hd-" #| "media/initrd.gz file and its kernel, as well as copy a CD iso " #| "to the drive (make sure the file is named ending in .iso). The installer can then boot from the drive and install from " #| "the CD image, without needing the network." msgid "" "Alternatively, if you intend to keep an existing partition on the hard drive " "unchanged during the install, you can download the hd-media/initrd." "gz file and its kernel, as well as copy a CD (or DVD) iso to the " "drive (make sure the file is named ending in .iso). The " "installer can then boot from the drive and install from the CD/DVD image, " "without needing the network." msgstr "" "Ha egy merevlemez-partíció változatlan marad a telepítés során, lehetőség " "nyílik a hd-media/initrd.gz fájl, hozzávaló kernel és " "egy CD iso letöltésére (az utóbbi fájl nevének vége maradjon .iso). A telepítő indíthat a meghajtóról és képes telepíteni a CD képről " "hálózat nélkül." #. Tag: para #: boot-installer.xml:711 #, no-c-format msgid "" "For LILO, you will need to configure two essential things " "in /etc/lilo.conf: to " "load the initrd.gz installer at boot time; have the vmlinuz kernel use " "a RAM disk as its root partition. Here is " "a /etc/lilo.conf example:" msgstr "" "LILO esetén 2 dolgot kell beállítani a /etc/" "lilo.conf fájlban, melyek: az " "initrd.gz telepítő betöltése induláskor; a vmlinuz kernel egy RAM " "lemezt használjon gyökér-partícióként. " "Itt egy példa /etc/lilo.conf:" #. Tag: screen #: boot-installer.xml:732 #, no-c-format msgid "" "image=/boot/newinstall/vmlinuz\n" " label=newinstall\n" " initrd=/boot/newinstall/initrd.gz" msgstr "" "image=/boot/newinstall/vmlinuz\n" " label=newinstall\n" " initrd=/boot/newinstall/initrd.gz" #. Tag: para #: boot-installer.xml:732 #, no-c-format msgid "" "For more details, refer to the initrd 4 and " "lilo.conf 5 man pages. Now run lilo and " "reboot." msgstr "" "További részletekért lásd az initrd 4 és " "lilo.conf 5 man oldalakat. Futtasd a lilo-t és indíts újra." #. Tag: para #: boot-installer.xml:741 #, fuzzy, no-c-format #| msgid "" #| "The procedure for GRUB is quite similar. Locate your " #| "menu.lst in the /boot/grub/ " #| "directory (sometimes in the /boot/boot/grub/), add " #| "the following lines: \n" #| "title New Install\n" #| "kernel (hd0,0)/boot/newinstall/vmlinuz\n" #| "initrd (hd0,0)/boot/newinstall/initrd.gz\n" #| " and reboot." msgid "" "The procedure for GRUB1 is quite similar. Locate your " "menu.lst in the /boot/grub/ " "directory (or sometimes /boot/boot/grub/) and add an " "entry for the installer, for example (assuming /boot is " "on the first partition of the first disk in the system):" msgstr "" "A GRUB hasonló. Menj a menu.lst " "fájlra a /boot/grub/ (néha a /boot/boot/grub/" ") könyvtárban, add hozzá a következő sorokat: " "\n" "title New Install\n" "kernel (hd0,0)/boot/newinstall/vmlinuz\n" "initrd (hd0,0)/boot/newinstall/initrd.gz\n" " és indíts újra." #. Tag: screen #: boot-installer.xml:749 #, fuzzy, no-c-format #| msgid "" #| "image=/boot/newinstall/vmlinuz\n" #| " label=newinstall\n" #| " initrd=/boot/newinstall/initrd.gz" msgid "" "title New Install\n" "root (hd0,0)\n" "kernel /boot/newinstall/vmlinuz\n" "initrd /boot/newinstall/initrd.gz" msgstr "" "image=/boot/newinstall/vmlinuz\n" " label=newinstall\n" " initrd=/boot/newinstall/initrd.gz" #. Tag: para #: boot-installer.xml:751 #, fuzzy, no-c-format #| msgid "" #| "The procedure for GRUB is quite similar. Locate your " #| "menu.lst in the /boot/grub/ " #| "directory (sometimes in the /boot/boot/grub/), add " #| "the following lines: \n" #| "title New Install\n" #| "kernel (hd0,0)/boot/newinstall/vmlinuz\n" #| "initrd (hd0,0)/boot/newinstall/initrd.gz\n" #| " and reboot." msgid "" "The procedure for GRUB2 is very similar. The file is " "named grub.cfg instead of menu.lst. An entry for the installer would be for instance for example:" msgstr "" "A GRUB hasonló. Menj a menu.lst " "fájlra a /boot/grub/ (néha a /boot/boot/grub/" ") könyvtárban, add hozzá a következő sorokat: " "\n" "title New Install\n" "kernel (hd0,0)/boot/newinstall/vmlinuz\n" "initrd (hd0,0)/boot/newinstall/initrd.gz\n" " és indíts újra." #. Tag: screen #: boot-installer.xml:757 #, fuzzy, no-c-format #| msgid "" #| "image=/boot/newinstall/vmlinuz\n" #| " label=newinstall\n" #| " initrd=/boot/newinstall/initrd.gz" msgid "" "menuentry 'New Install' {\n" "insmod part_msdos\n" "insmod ext2\n" "set root='(hd0,msdos1)'\n" "linux /boot/newinstall/vmlinuz\n" "initrd /boot/newinstall/initrd.gz\n" "}" msgstr "" "image=/boot/newinstall/vmlinuz\n" " label=newinstall\n" " initrd=/boot/newinstall/initrd.gz" #. Tag: para #: boot-installer.xml:759 #, no-c-format msgid "" "From here on, there should be no difference between GRUB " "or LILO." msgstr "" "Innentől nincs különbség a GRUB vagy LILO között." #. Tag: title #: boot-installer.xml:768 boot-installer.xml:2024 #, no-c-format msgid "Booting from Floppies" msgstr "Indítás flopikról" #. Tag: para #: boot-installer.xml:769 boot-installer.xml:2032 #, no-c-format msgid "" "You will have already downloaded the floppy images you needed and created " "floppies from the images in ." msgstr "" "Itt szükség lesz a már letöltött flopi-képekre és a képekből a részben létrehozott flopikra." #. Tag: para #: boot-installer.xml:776 #, no-c-format msgid "" "To boot from the installer boot floppy, place it in the primary floppy " "drive, shut down the system as you normally would, then turn it back on." msgstr "" "A telepítő flopi indításához, tedd az elsődleges flopi meghajtóba, állítsd " "le a rendszert, ahogy egyébként tennéd és indítsd újra a gépet." #. Tag: para #: boot-installer.xml:782 #, no-c-format msgid "" "For installing from an LS-120 drive (ATAPI version) with a set of floppies, " "you need to specify the virtual location for the floppy device. This is done " "with the root= boot argument, giving the device that " "the ide-floppy driver maps the device to. For example, if your LS-120 drive " "is connected as the first IDE device (master) on the second cable, you enter " "install root=/dev/hdc at the boot prompt." msgstr "" "Egy LS-120 meghajtóról (ATAPI változat) telepítéshez egy flopi-készlettel, " "meg kell adni a flopi eszköz virtuális helyét. Ez a root= indító argumentummal tehető, megadva az eszközt, melyre az ide-" "floppy meghajtó helyezze. Például, ha az LS-120 meghajtó az 1. IDE eszköz " "(mester) a második kábelen, írd be ezt: install root=/dev/hdc az indító jelnél." #. Tag: para #: boot-installer.xml:792 #, no-c-format msgid "" "Note that on some machines, Control Alt Delete does not properly reset the " "machine, so a hard reboot is recommended. If you are " "installing from an existing operating system (e.g., from a DOS box) you " "don't have a choice. Otherwise, please do a hard reboot when booting." msgstr "" "Egyes gépeken a Control Alt " "Delete nem indítja újra helyesen a gépet, így " "egy hideg újraindítás ajánlott. Ha egy létező rendszerről " "telepítesz (például DOS alól), nincs választásod. Általában, ha lehet, " "végezz hidegindítást." #. Tag: para #: boot-installer.xml:801 #, no-c-format msgid "" "The floppy disk will be accessed, and you should then see a screen that " "introduces the boot floppy and ends with the boot: prompt." msgstr "" "A flopi lemez elindul és ekkor látnod kell egy képernyőt, mely bemutatja az " "indító flopit és egy boot: jellel zárul." #. Tag: para #: boot-installer.xml:807 #, no-c-format msgid "" "Once you press &enterkey;, you should see the message " "Loading..., followed by " "Uncompressing Linux..., and then a " "screenfull or so of information about the hardware in your system. More " "information on this phase of the boot process can be found below in ." msgstr "" "Az &enterkey; lenyomásakor a Loading... " "üzenetnek kell jönnie, ezt követi ez: Uncompressing Linux..." ", majd sok-sok adat a gépben lévő hardverről. A telepítő " "folyamat e szakaszáról több adat az alábbi: " "részben található." #. Tag: para #: boot-installer.xml:816 #, no-c-format msgid "" "After booting from the boot floppy, the root floppy is requested. Insert the " "root floppy and press &enterkey;, and the contents are loaded into memory. " "The installer program debian-installer is automatically " "launched." msgstr "" "Az indító flopi után az a root flopit kéri. Tedd be a root flopit és üsd le " "az &enterkey;-t, ekkor tartalma a memóriába olvasásra kerül. A " "debian-installer telepítő program elindul." #. Tag: title #: boot-installer.xml:826 boot-installer.xml:1450 boot-installer.xml:1592 #: boot-installer.xml:1646 boot-installer.xml:1968 boot-installer.xml:2116 #, no-c-format msgid "Booting with TFTP" msgstr "Indítás TFTP segítségével" #. Tag: para #: boot-installer.xml:851 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "i386 gépen több mód van a TFTP indításra." #. Tag: title #: boot-installer.xml:857 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "PXE-támogató hálózati kártya vagy alaplap" #. Tag: para #: boot-installer.xml:858 #, no-c-format msgid "" "It could be that your Network Interface Card or Motherboard provides PXE " "boot functionality. This is a Intel " "re-implementation of TFTP boot. If so, you may be able to configure your " "BIOS to boot from the network." msgstr "" "Lehet, hogy a hálózati csatoló kártya vagy alaplap PXE indítást is támogat. " "Ez a TFTP indítás egy Intel " "megvalósítása. Ha így van, lehetőség van a BIOS hálózati indításra " "állítására." #. Tag: title #: boot-installer.xml:869 #, no-c-format msgid "NIC with Network BootROM" msgstr "NIC hálózati indító ROM-mal" #. Tag: para #: boot-installer.xml:870 #, no-c-format msgid "" "It could be that your Network Interface Card provides TFTP boot " "functionality." msgstr "Lehet, hogy hálózati csatoló kártyád TFTP indítást kínál." #. Tag: para #: boot-installer.xml:875 #, no-c-format msgid "" "Let us (&email-debian-boot-list;) know how did you manage it. " "Please refer to this document." msgstr "" "Tudasd velünk (&email-debian-boot-list;) hogyan kezelted. " "Hivatkozz e dokumentumra." #. Tag: title #: boot-installer.xml:883 #, no-c-format msgid "Etherboot" msgstr "Etherboot" #. Tag: para #: boot-installer.xml:884 #, no-c-format msgid "" "The etherboot project " "provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" "Az etherboot project TFTP " "indítást adó indító lemezeket és indító romokat ad." #. Tag: title #: boot-installer.xml:894 #, fuzzy, no-c-format #| msgid "The Boot Prompt" msgid "The Boot Screen" msgstr "Az indító jel" #. Tag: para #: boot-installer.xml:895 #, no-c-format msgid "" "When the installer boots, you should be presented with a friendly graphical " "screen showing the &debian; logo and a menu:" msgstr "" #. Tag: screen #: boot-installer.xml:900 #, no-c-format msgid "" "&debian-gnu; installer boot menu\n" "\n" "Graphical install\n" "Install\n" "Advanced options >\n" "Help\n" "Install with speech synthesis" msgstr "" #. Tag: para #: boot-installer.xml:904 #, no-c-format msgid "" "This graphical screen will look very slightly different depending on how " "your computer has booted (BIOS or UEFI), but the same options will be shown." msgstr "" #. Tag: para #: boot-installer.xml:912 #, no-c-format msgid "" "Depending on the installation method you are using, the Graphical " "install option may not be available. Bi-arch images additionally " "have a 64 bit variant for each install option, right below it, thus almost " "doubling the number of options." msgstr "" #. Tag: para #: boot-installer.xml:919 #, no-c-format msgid "" "For a normal installation, select either the Graphical install or the Install entry — using either the arrow " "keys on your keyboard or by typing the first (highlighted) letter — " "and press &enterkey; to boot the installer. The Graphical install entry is already selected by default." msgstr "" #. Tag: para #: boot-installer.xml:927 #, no-c-format msgid "" "The Advanced options entry gives access to a second menu that " "allows to boot the installer in expert mode, in rescue mode and for " "automated installs." msgstr "" #. Tag: para #: boot-installer.xml:933 #, no-c-format msgid "" "If you wish or need to add any boot parameters for either the installer or " "the kernel, press &tabkey; (BIOS boot), or &ekey; then &downkey; three times " "then &endkey; (UEFI boot). This will bring the boot command for the selected " "menu entry and allow you to edit it to suit your needs. The help screens " "(see below) list some common possible options. Press &enterkey; (BIOS boot) " "or &f10key; (UEFI boot) to boot the installer with your options; pressing " "&escapekey; will return you to the boot menu and undo any changes you made." msgstr "" #. Tag: para #: boot-installer.xml:945 #, no-c-format msgid "" "Choosing the Help entry will result in the first help screen " "being displayed which gives an overview of all available help screens. To " "return to the boot menu after the help screens have been displayed, type " "'menu' at the boot prompt and press &enterkey;. All help screens have a boot " "prompt at which the boot command can be typed: \n" "Press F1 for the help index, or ENTER to boot:\n" " At this boot prompt you can either just press " "&enterkey; to boot the installer with default options or enter a specific " "boot command and, optionally, boot parameters. A number of boot parameters " "which might be useful can be found on the various help screens. If you do " "add any parameters to the boot command line, be sure to first type the boot " "method (the default is install) and a space before " "the first parameter (e.g., install fb=false)." msgstr "" #. Tag: para #: boot-installer.xml:963 #, no-c-format msgid "" "The keyboard is assumed to have a default American English layout at this " "point. This means that if your keyboard has a different (language-specific) " "layout, the characters that appear on the screen may be different from what " "you'd expect when you type parameters. Wikipedia has a schema of the US keyboard layout which can be used as a " "reference to find the correct keys to use." msgstr "" #. Tag: para #: boot-installer.xml:973 #, no-c-format msgid "" "If you are using a system that has the BIOS configured to use serial " "console, you may not be able to see the initial graphical splash screen upon " "booting the installer; you may even not see the boot menu. The same can " "happen if you are installing the system via a remote management device that " "provides a text interface to the VGA console. Examples of these devices " "include the text console of Compaq's integrated Lights Out " "(iLO) and HP's Integrated Remote Assistant (IRA)." msgstr "" #. Tag: para #: boot-installer.xml:983 #, no-c-format msgid "" "To bypass the graphical boot screen you can either blindly press &escapekey; " "to get a text boot prompt, or (equally blindly) press H " "followed by &enterkey; to select the Help option described " "above. After that your keystrokes should be echoed at the prompt. To prevent " "the installer from using the framebuffer for the rest of the installation, " "you will also want to add vga=normal fb=false to the " "boot prompt, as described in the help text." msgstr "" #. Tag: title #: boot-installer.xml:999 #, no-c-format msgid "The Graphical Installer" msgstr "" #. Tag: para #: boot-installer.xml:1000 #, no-c-format msgid "" "The graphical version of the installer is only available for a limited " "number of architectures, including &arch-title;. The functionality of the " "graphical installer is essentially the same as that of the text-based " "installer as it basically uses the same programs, but with a different " "frontend." msgstr "" #. Tag: para #: boot-installer.xml:1008 #, no-c-format msgid "" "Although the functionality is identical, the graphical installer still has a " "few significant advantages. The main advantage is that it supports more " "languages, namely those that use a character set that cannot be displayed " "with the text-based newt frontend. It also has a few " "usability advantages such as the option to use a mouse, and in some cases " "several questions can be displayed on a single screen." msgstr "" #. Tag: para #: boot-installer.xml:1017 #, no-c-format msgid "" "The graphical installer is available with all CD images and with the hd-" "media installation method. To boot the graphical installer simply select the " "relevant option from the boot menu. Expert and rescue mode for the graphical " "installer can be selected from the Advanced options menu. The " "previously used boot methods installgui, " "expertgui and rescuegui can " "still be used from the boot prompt which is shown after selecting the " "Help option in the boot menu." msgstr "" #. Tag: para #: boot-installer.xml:1028 #, no-c-format msgid "" "There is also a graphical installer image that can be netbooted. And there " "is a special mini ISO image " " The mini ISO image can be downloaded from a &debian; mirror as " "described in . Look for " "netboot/gtk/mini.iso. , which is " "mainly useful for testing." msgstr "" #. Tag: para #: boot-installer.xml:1041 #, no-c-format msgid "" "For &arch-title;, currently only an experimental mini ISO " "image is available The mini ISO image " "can be downloaded from a &debian; mirror as described in . Look for netboot/gtk/mini.iso. " " . It should work on almost all PowerPC systems that have " "an ATI graphical card, but is unlikely to work on other systems." msgstr "" #. Tag: para #: boot-installer.xml:1055 #, no-c-format msgid "" "Just as with the text-based installer it is possible to add boot parameters " "when starting the graphical installer." msgstr "" #. Tag: para #: boot-installer.xml:1061 #, no-c-format msgid "" "The graphical installer requires significantly more memory to run than the " "text-based installer: &minimum-memory-gtk;. If insufficient memory is " "available, it will automatically fall back to the text-based newt frontend." msgstr "" #. Tag: para #: boot-installer.xml:1068 #, no-c-format msgid "" "If the amount of memory in your system is below &minimum-memory;, the " "graphical installer may fail to boot at all while booting the text-based " "installer would still work. Using the text-based installer is recommended " "for systems with little available memory." msgstr "" #. Tag: title #: boot-installer.xml:1122 #, no-c-format msgid "CD Contents" msgstr "" #. Tag: para #: boot-installer.xml:1124 #, no-c-format msgid "" "There are three basic variations of &debian; Install CDs. The " "Business Card CD has a minimal installation that will " "fit on the small form factor CD media. It requires a network connection in " "order to install the rest of the base installation and make a usable system. " "The Network Install CD has all of the packages for a " "base install but requires a network connection to a &debian; mirror site in " "order to install the extra packages one would want for a complete system . " "The set of &debian; CDs can install a complete system from the wide range of " "packages without needing access to the network." msgstr "" #. Tag: para #: boot-installer.xml:1140 #, no-c-format msgid "" "The IA-64 architecture uses the next generation Extensible Firmware " "Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows " "little about the boot device other than the partition table and Master Boot " "Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted " "disk partitions. This simplifies the often arcane process of starting a " "system. The system boot loader and the EFI firmware that supports it have a " "full filesystem to store the files necessary for booting the machine. This " "means that the system disk on an IA-64 system has an additional disk " "partition dedicated to EFI instead of the simple MBR or boot block on more " "conventional systems." msgstr "" #. Tag: para #: boot-installer.xml:1156 #, no-c-format msgid "" "The &debian; Installer CD contains a small EFI partition where the " "ELILO bootloader, its configuration file, the installer's " "kernel, and initial filesystem (initrd) are located. The running system also " "contains an EFI partition where the necessary files for booting the system " "reside. These files are readable from the EFI Shell as described below." msgstr "" #. Tag: para #: boot-installer.xml:1165 #, no-c-format msgid "" "Most of the details of how ELILO actually loads and " "starts a system are transparent to the system installer. However, the " "installer must set up an EFI partition prior to installing the base system. " "Otherwise, the installation of ELILO will fail, rendering " "the system un-bootable. The EFI partition is allocated and formatted in the " "partitioning step of the installation prior to loading any packages on the " "system disk. The partitioning task also verifies that a suitable EFI " "partition is present before allowing the installation to proceed." msgstr "" #. Tag: para #: boot-installer.xml:1177 #, no-c-format msgid "" "The EFI Boot Manager is presented as the last step of the firmware " "initialization. It displays a menu list from which the user can select an " "option. Depending on the model of system and what other software has been " "loaded on the system, this menu may be different from one system to another. " "There should be at least two menu items displayed, Boot Option " "Maintenance Menu and EFI Shell (Built-in). " "Using the first option is preferred, however, if that option is not " "available or the CD for some reason does not boot with it, use the second " "option." msgstr "" #. Tag: title #: boot-installer.xml:1196 #, no-c-format msgid "IMPORTANT" msgstr "" #. Tag: para #: boot-installer.xml:1197 #, no-c-format msgid "" "The EFI Boot Manager will select a default boot action, typically the first " "menu choice, within a pre-set number of seconds. This is indicated by a " "countdown at the bottom of the screen. Once the timer expires and the " "systems starts the default action, you may have to reboot the machine in " "order to continue the installation. If the default action is the EFI Shell, " "you can return to the Boot Manager by running exit at the " "shell prompt." msgstr "" #. Tag: title #: boot-installer.xml:1209 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "" #. Tag: para #: boot-installer.xml:1216 #, no-c-format msgid "" "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " "display the EFI Boot Manager page and menu after it completes its system " "initialization." msgstr "" #. Tag: para #: boot-installer.xml:1222 #, no-c-format msgid "" "Select Boot Maintenance Menu from the menu with the arrow " "keys and press ENTER. This will display a new menu." msgstr "" #. Tag: para #: boot-installer.xml:1228 #, no-c-format msgid "" "Select Boot From a File from the menu with the arrow keys " "and press ENTER. This will display a list of devices " "probed by the firmware. You should see two menu lines containing either the " "label Debian Inst [Acpi ... or Removable Media " "Boot. If you examine the rest of the menu line, you will notice " "that the device and controller information should be the same." msgstr "" #. Tag: para #: boot-installer.xml:1239 #, no-c-format msgid "" "You can choose either of the entries that refer to the CD/DVD drive. Select " "your choice with the arrow keys and press ENTER. If you " "choose Removable Media Boot the machine will immediately " "start the boot load sequence. If you choose Debian Inst [Acpi ... instead, it will display a directory listing of the bootable " "portion of the CD, requiring you to proceed to the next (additional) step." msgstr "" #. Tag: para #: boot-installer.xml:1250 #, no-c-format msgid "" "You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " "Removable Media Boot] on the next to the last line. Select this " "line with the arrow keys and press ENTER. This will start " "the boot load sequence." msgstr "" #. Tag: para #: boot-installer.xml:1262 #, no-c-format msgid "" "These steps start the &debian; boot loader which will display a menu page " "for you to select a boot kernel and options. Proceed to selecting the boot " "kernel and options." msgstr "" #. Tag: title #: boot-installer.xml:1272 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "" #. Tag: para #: boot-installer.xml:1273 #, no-c-format msgid "" "If, for some reason, option 1 is not successful, reboot the machine and when " "the EFI Boot Manager screen appears there should be one option called " "EFI Shell [Built-in]. Boot the &debian; Installer CD with " "the following steps:" msgstr "" #. Tag: para #: boot-installer.xml:1284 #, no-c-format msgid "" "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " "display the EFI Boot Manager page and menu after it completes system " "initialization." msgstr "" #. Tag: para #: boot-installer.xml:1290 #, no-c-format msgid "" "Select EFI Shell from the menu with the arrow keys and " "press ENTER. The EFI Shell will scan all of the bootable " "devices and display them to the console before displaying its command " "prompt. The recognized bootable partitions on devices will show a device " "name of fsn:. All other " "recognized partitions will be named blkn:. If you inserted the CD just before entering the " "shell, this may take a few extra seconds as it initializes the CD drive." msgstr "" #. Tag: para #: boot-installer.xml:1304 #, no-c-format msgid "" "Examine the output from the shell looking for the CDROM drive. It is most " "likely the fs0: device although other devices with " "bootable partitions will also show up as fsn." msgstr "" #. Tag: para #: boot-installer.xml:1311 #, no-c-format msgid "" "Enter fsn: and press " "ENTER to select that device where n is the partition number for the CDROM. The shell will now " "display the partition number as its prompt." msgstr "" #. Tag: para #: boot-installer.xml:1318 #, no-c-format msgid "" "Enter elilo and press ENTER. This will " "start the boot load sequence." msgstr "" #. Tag: para #: boot-installer.xml:1325 #, no-c-format msgid "" "As with option 1, these steps start the &debian; boot loader which will " "display a menu page for you to select a boot kernel and options. You can " "also enter the shorter fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel " "and options." msgstr "" #. Tag: title #: boot-installer.xml:1339 #, no-c-format msgid "Installing using a Serial Console" msgstr "" #. Tag: para #: boot-installer.xml:1341 #, no-c-format msgid "" "You may choose to perform an install using a monitor and keyboard or using a " "serial connection. To use a monitor/keyboard setup, select an option " "containing the string [VGA console]. To install over a serial connection, " "choose an option containing the string [BAUD baud " "serial console], where BAUD is the speed of your " "serial console. Menu items for the most typical baud rate settings on the " "ttyS0 device are preconfigured." msgstr "" #. Tag: para #: boot-installer.xml:1352 #, no-c-format msgid "" "In most circumstances, you will want the installer to use the same baud rate " "as your connection to the EFI console. If you aren't sure what this setting " "is, you can obtain it using the command baud at the EFI " "shell." msgstr "" #. Tag: para #: boot-installer.xml:1359 #, no-c-format msgid "" "If there is not an option available that is configured for the serial device " "or baud rate you would like to use, you may override the console setting for " "one of the existing menu options. For example, to use a 57600 baud console " "over the ttyS1 device, enter console=ttyS1,57600n8 into " "the Boot: text window." msgstr "" #. Tag: para #: boot-installer.xml:1370 #, no-c-format msgid "" "Most IA-64 boxes ship with a default console setting of 9600 baud. This " "setting is rather slow, and the normal installation process will take a " "significant time to draw each screen. You should consider either increasing " "the baud rate used for performing the installation, or performing a Text " "Mode installation. See the Params help menu for " "instructions on starting the installer in Text Mode." msgstr "" #. Tag: para #: boot-installer.xml:1379 #, no-c-format msgid "" "If you select the wrong console type, you will be able to select the kernel " "and enter parameters but both the display and your input will go dead as " "soon as the kernel starts, requiring you to reboot before you can begin the " "installation." msgstr "" #. Tag: title #: boot-installer.xml:1388 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "" #. Tag: para #: boot-installer.xml:1390 #, no-c-format msgid "" "The boot loader will display a form with a menu list and a text window with " "a Boot: prompt. The arrow keys select an item from " "the menu and any text typed at the keyboard will appear in the text window. " "There are also help screens which can be displayed by pressing the " "appropriate function key. The General help screen " "explains the menu choices and the Params screen " "explains the common command line options." msgstr "" #. Tag: para #: boot-installer.xml:1402 #, no-c-format msgid "" "Consult the General help screen for the description " "of the kernels and install modes most appropriate for your installation. You " "should also consult below for any additional " "parameters that you may want to set in the Boot: text " "window. The kernel version you choose selects the kernel version that will " "be used for both the installation process and the installed system. If you " "encounter kernel problems with the installation, you may also have those " "same problems with the system you install. The following two steps will " "select and start the install:" msgstr "" #. Tag: para #: boot-installer.xml:1420 #, no-c-format msgid "" "Select the kernel version and installation mode most appropriate to your " "needs with the arrow keys." msgstr "" #. Tag: para #: boot-installer.xml:1425 #, no-c-format msgid "" "Enter any boot parameters by typing at the keyboard. The text will be " "displayed directly in the text window. This is where kernel parameters (such " "as serial console settings) are specified." msgstr "" #. Tag: para #: boot-installer.xml:1432 #, no-c-format msgid "" "Press ENTER. This will load and start the kernel. The " "kernel will display its usual initialization messages followed by the first " "screen of the &debian; Installer." msgstr "" #. Tag: para #: boot-installer.xml:1441 boot-installer.xml:1578 #, no-c-format msgid "" "Proceed to the next chapter to continue the installation where you will set " "up the language locale, network, and disk partitions." msgstr "" #. Tag: para #: boot-installer.xml:1452 #, no-c-format msgid "" "Booting an IA-64 system from the network is similar to a CD boot. The only " "difference is how the installation kernel is loaded. The EFI Boot Manager " "can load and start programs from a server on the network. Once the " "installation kernel is loaded and starts, the system install will proceed " "through the same steps as the CD install with the exception that the " "packages of the base install will be loaded from the network rather than the " "CD drive." msgstr "" #. Tag: para #: boot-installer.xml:1487 #, no-c-format msgid "" "Network booting an IA-64 system requires two architecture-specific actions. " "On the boot server, DHCP and TFTP must be configured to deliver " "elilo. On the client a new boot option must be defined in " "the EFI boot manager to enable loading over a network." msgstr "" #. Tag: title #: boot-installer.xml:1498 #, no-c-format msgid "Configuring the Server" msgstr "" #. Tag: para #: boot-installer.xml:1499 #, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 system looks something " "like this: \n" "host mcmuffin {\n" " hardware ethernet 00:30:6e:1e:0e:83;\n" " fixed-address 10.0.0.21;\n" " filename \"debian-installer/ia64/elilo.efi\";\n" "}\n" " Note that the goal is to get elilo.efi running on the client." msgstr "" #. Tag: para #: boot-installer.xml:1509 #, no-c-format msgid "" "Extract the netboot.tar.gz file into the directory used " "as the root for your tftp server. Typical tftp root directories include " "/var/lib/tftp and /tftpboot. This " "will create a debian-installer directory tree " "containing the boot files for an IA-64 system." msgstr "" #. Tag: screen #: boot-installer.xml:1519 #, no-c-format msgid "" "# cd /var/lib/tftp\n" "# tar xvfz /home/user/netboot.tar.gz\n" "./\n" "./debian-installer/\n" "./debian-installer/ia64/\n" "[...]" msgstr "" #. Tag: para #: boot-installer.xml:1519 #, no-c-format msgid "" "The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should you " "need to make changes to this file, you can find it in the debian-" "installer/ia64/ directory. It is possible to have different " "config files for different clients by naming them using the client's IP " "address in hex with the suffix .conf instead of " "elilo.conf. See documentation provided in the " "elilo package for details." msgstr "" #. Tag: title #: boot-installer.xml:1536 #, no-c-format msgid "Configuring the Client" msgstr "" #. Tag: para #: boot-installer.xml:1537 #, no-c-format msgid "" "To configure the client to support TFTP booting, start by booting to EFI and " "entering the Boot Option Maintenance Menu. " " Add a boot option. You " "should see one or more lines with the text Load File " "[Acpi()/.../Mac()]. If more than one of these entries exist, " "choose the one containing the MAC address of the interface from which you'll " "be booting. Use the arrow keys to highlight your choice, then press enter. Name the entry Netboot or something similar, save, and exit back to the boot options " "menu. You should see the new boot option " "you just created, and selecting it should initiate a DHCP query, leading to " "a TFTP load of elilo.efi from the server." msgstr "" #. Tag: para #: boot-installer.xml:1569 #, no-c-format msgid "" "The boot loader will display its prompt after it has downloaded and " "processed its configuration file. At this point, the installation proceeds " "with the same steps as a CD install. Select a boot option as in above and " "when the kernel has completed installing itself from the network, it will " "start the &debian; Installer." msgstr "" #. Tag: title #: boot-installer.xml:1595 boot-installer.xml:1619 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para #: boot-installer.xml:1596 #, no-c-format msgid "" "After entering the command monitor use \n" "bootp():\n" " on SGI machines to boot linux and to begin " "installation of the &debian; Software. In order to make this work you may " "have to unset the netaddr environment variable. Type " "\n" "unsetenv netaddr\n" " in the command monitor to do this." msgstr "" #. Tag: title #: boot-installer.xml:1616 boot-installer.xml:2432 #, no-c-format msgid "Boot Parameters" msgstr "Indító paraméterek" #. Tag: para #: boot-installer.xml:1620 #, no-c-format msgid "" "On SGI machines you can append boot parameters to the bootp(): command in the command monitor." msgstr "" #. Tag: para #: boot-installer.xml:1625 #, no-c-format msgid "" "Following the bootp(): command you can give the path and " "name of the file to boot if you did not give an explicit name via your bootp/" "dhcp server. Example: \n" "bootp():/boot/tftpboot.img\n" " Further kernel parameters can be passed via " "append:" msgstr "" #. Tag: screen #: boot-installer.xml:1635 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: title #: boot-installer.xml:1678 #, no-c-format msgid "s390 Limitations" msgstr "" #. Tag: para #: boot-installer.xml:1679 #, no-c-format msgid "" "In order to run the installation system a working network setup and ssh " "session is needed on S/390." msgstr "" #. Tag: para #: boot-installer.xml:1684 #, no-c-format msgid "" "The booting process starts with a network setup that prompts you for several " "network parameters. If the setup is successful, you will login to the system " "by starting an ssh session which will launch the standard installation " "system." msgstr "" #. Tag: title #: boot-installer.xml:1695 #, no-c-format msgid "s390 Boot Parameters" msgstr "s390 indító paraméterek" #. Tag: para #: boot-installer.xml:1696 #, no-c-format msgid "" "On S/390 you can append boot parameters in the parm file. This file can " "either be in ASCII or EBCDIC format. It needs to be fixed-width with 80 " "characters per line. A sample parm file parmfile.debian " "is provided with the installation images. If a parameter is too long to fit " "into the 80 characters limit it can simply be continued in the first column " "of the next line. All the lines are concatenated without spaces when being " "passed to the kernel." msgstr "" #. Tag: para #: boot-installer.xml:1713 #, no-c-format msgid "" "If you boot the installer in a logical partition (LPAR) or virtual machine " "(VM) where a lot of devices are visible, you can instruct the kernel to " "restrict the list to a fixed set of devices. This is advised for the " "installer's boot process if a lot of disks are visible, most likely in LPAR " "mode. The cio_ignore option supports both a blacklist (to " "only disallow a few devices) and a whitelist (to only allow specific " "devices): \n" " # blacklist: just ignore the two devices 300 and 301\n" " cio_ignore=0.0.0300-0.0.0301\n" " # whitelist: ignore everything but 1150, FD00, FD01 and FD02\n" " cio_ignore=all,!0.0.1150,!0.0.fd00-0.0.fd02\n" " Please note that all devices numbers' hex digits " "need to be specified in lower case. Furthermore if this boot parameter is " "used all devices need to be listed: this includes at least disks, network " "devices and the console. To be considered during the installer's boot " "process the above option needs to be added to parmfile.debian." msgstr "" #. Tag: para #: boot-installer.xml:1777 #, no-c-format msgid "" "Currently, the only &arch-title; subarchitectures that support CD-ROM " "booting are PReP/CHRP (though not all systems) and New World PowerMacs. On " "PowerMacs, hold the c key, or else the combination of " "Command, Option, Shift, " "and Delete keys together while booting to boot from the " "factory default CD/DVD drive." msgstr "" #. Tag: para #: boot-installer.xml:1786 #, no-c-format msgid "" "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open " "Firmware prompt first (see ), then " "type \n" "0 > boot fw/node/sbp-2/disk:,\\install\\yaboot\n" " for an alternative way to boot from the internal " "factory default CD/DVD drive type" msgstr "" #. Tag: screen #: boot-installer.xml:1797 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "" #. Tag: para #: boot-installer.xml:1799 #, no-c-format msgid "" "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers " "relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-" "software version of this driver is not available. All OldWorld systems have " "floppy drives, so use the floppy drive to launch the installer, and then " "point the installer to the CD for the needed files." msgstr "" #. Tag: para #: boot-installer.xml:1808 #, no-c-format msgid "" "To boot &debian; CD/DVD on Pegasos II machine, hold Esc key " "immediately after pressing the power-on button, when SmartFirmware prompt " "appears, type" msgstr "" #. Tag: screen #: boot-installer.xml:1814 #, no-c-format msgid "boot cd install/pegasos" msgstr "" #. Tag: para #: boot-installer.xml:1816 #, no-c-format msgid "" "On YDL Powerstation machine, pres s immediately after " "Press 's' to enter Open Firmware message, when SLOF prompt " "appears type" msgstr "" #. Tag: screen #: boot-installer.xml:1821 #, no-c-format msgid "0 > boot cdrom" msgstr "" #. Tag: title #: boot-installer.xml:1827 #, no-c-format msgid "Booting from Hard Disk" msgstr "Indítás merevlemezről" #. Tag: para #: boot-installer.xml:1833 #, no-c-format msgid "" "Booting from an existing operating system is often a convenient option; for " "some systems it is the only supported method of installation." msgstr "" #. Tag: para #: boot-installer.xml:1839 #, fuzzy, no-c-format #| msgid "" #| "To boot the installer from hard disk, you will have already completed " #| "downloading and placing the needed files in ." msgid "" "To boot the installer from hard disk, you will have already completed " "downloading and placing the needed files as described in ." msgstr "" "A telepítő merevlemezről indításához először le kell tölteni és elhelyezni a " " részben írt fájlokat." #. Tag: title #: boot-installer.xml:1859 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" #. Tag: para #: boot-installer.xml:1860 #, no-c-format msgid "" "If you set up BootX in , you can use it to " "boot into the installation system. Double click the BootX " "application icon. Click on the Options button and " "select Use Specified RAM Disk. This will give you the " "chance to select the ramdisk.image.gz file. You may " "need to select the No Video Driver checkbox, depending " "on your hardware. Then click the Linux button to shut " "down MacOS and launch the installer." msgstr "" #. Tag: title #: boot-installer.xml:1878 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" #. Tag: para #: boot-installer.xml:1879 #, no-c-format msgid "" "You will have already placed the vmlinux, " "initrd.gz, yaboot, and " "yaboot.conf files at the root level of your HFS " "partition in . You will now have to boot " "into OpenFirmware (see ). At the " "prompt, type \n" "0 > boot hd:x,yaboot\n" " replacing x with the " "partition number of the HFS partition where the kernel and yaboot files were " "placed, followed by a &enterkey;. On some machines, you may need to use " "ide0: instead of hd:. In a few " "more seconds you will see a yaboot prompt \n" "boot:\n" " At yaboot's boot: prompt, type " "either install or install video=ofonly followed by a &enterkey;. The video=ofonly " "argument is for maximum compatibility; you can try it if install doesn't work. The &debian; installation program should start." msgstr "" #. Tag: title #: boot-installer.xml:1911 #, no-c-format msgid "Booting from USB memory stick" msgstr "Indítás USB memóriáról" #. Tag: para #: boot-installer.xml:1912 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" #. Tag: para #: boot-installer.xml:1918 #, no-c-format msgid "" "Make sure you have prepared everything from . To boot a Macintosh system from a USB stick, you will need to use the " "Open Firmware prompt, since Open Firmware does not search USB storage " "devices by default. See ." msgstr "" #. Tag: para #: boot-installer.xml:1927 #, no-c-format msgid "" "You will need to work out where the USB storage device appears in the device " "tree, since at the moment ofpath cannot work that out " "automatically. Type dev / ls and devalias at the Open Firmware prompt to get a list of all known devices " "and device aliases. On the author's system with various types of USB stick, " "paths such as usb0/disk, usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1, and " "/pci@f2000000/usb@1b,1/hub@1/disk@1 work." msgstr "" #. Tag: para #: boot-installer.xml:1939 #, no-c-format msgid "" "Having worked out the device path, use a command like this to boot the " "installer: \n" "boot usb0/disk:2,\\\\:" "tbxi\n" " The 2 matches the " "Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image " "earlier, and the ,\\\\:tbxi part instructs Open " "Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. " "yaboot) in the directory previously blessed with " "hattrib -b." msgstr "" #. Tag: para #: boot-installer.xml:1953 #, no-c-format msgid "" "The system should now boot up, and you should be presented with the " "boot: prompt. Here you can enter optional boot arguments, " "or just hit &enterkey;." msgstr "" "A rendszer elindul és erről ad egy boot: jelet. A 2 " "lehetőség: további indító argumentumok megadása vagy az &enterkey; leütése." #. Tag: para #: boot-installer.xml:1959 #, no-c-format msgid "" "This boot method is new, and may be difficult to get to work on some " "NewWorld systems. If you have problems, please file an installation report, " "as explained in ." msgstr "" #. Tag: para #: boot-installer.xml:1993 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" #. Tag: para #: boot-installer.xml:1997 #, no-c-format msgid "" "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " "monitor (see ) and use the command " "\n" "0 > boot enet:0\n" " If this doesn't work, you might have to add the " "filename like this: \n" "0 > boot enet:0,yaboot\n" " PReP and CHRP boxes may have different ways of " "addressing the network. On a PReP machine, you should try " "\n" "boot net:server_ipaddr,file,client_ipaddr\n" " On some PReP systems (e.g. Motorola PowerStack " "machines) the command help boot may give a " "description of syntax and available options." msgstr "" #. Tag: para #: boot-installer.xml:2025 #, no-c-format msgid "" "Booting from floppies is supported for &arch-title;, although it is " "generally only applicable for OldWorld systems. NewWorld systems are not " "equipped with floppy drives, and attached USB floppy drives are not " "supported for booting." msgstr "" #. Tag: para #: boot-installer.xml:2037 #, no-c-format msgid "" "To boot from the boot-floppy-hfs.img floppy, place it " "in floppy drive after shutting the system down, and before pressing the " "power-on button." msgstr "" "A boot-floppy-hfs.img flopi indításához, tedd a flopi " "meghajtóba a rendszer leállítása után, a bekapcsoló megnyomása előtt." #. Tag: para #: boot-installer.xml:2043 #, no-c-format msgid "" "For those not familiar with Macintosh floppy operations: a floppy placed in " "the machine prior to boot will be the first priority for the system to boot " "from. A floppy without a valid boot system will be ejected, and the machine " "will then check for bootable hard disk partitions." msgstr "" #. Tag: para #: boot-installer.xml:2050 #, no-c-format msgid "" "After booting, the root.bin floppy is requested. Insert " "the root floppy and press &enterkey;. The installer program is automatically " "launched after the root system has been loaded into memory." msgstr "" "Indítás után a root.bin flopi kell. Tedd be a root " "flopit és üsd le az &enterkey;-t. A telepítő program elindul a gyökér " "rendszer memóriába töltése után." #. Tag: title #: boot-installer.xml:2061 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "PowerPC indító paraméterek" #. Tag: para #: boot-installer.xml:2062 #, no-c-format msgid "" "Many older Apple monitors used a 640x480 67Hz mode. If your video appears " "skewed on an older Apple monitor, try appending the boot argument " "video=atyfb:vmode:6 , which will select that mode for " "most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to " "video=aty128fb:vmode:6 ." msgstr "" #. Tag: title #: boot-installer.xml:2074 #, no-c-format msgid "Booting a ppc64el machine" msgstr "" #. Tag: para #: boot-installer.xml:2075 #, no-c-format msgid "How to boot a ppc64el machine:" msgstr "" #. Tag: title #: boot-installer.xml:2081 #, no-c-format msgid "Petitboot" msgstr "" #. Tag: para #: boot-installer.xml:2082 #, no-c-format msgid "" "Petitboot is a platform independent bootloader based on the Linux kexec. " "Petitboot supports loading kernel, initrd and device tree files from any " "Linux mountable filesystem, plus can load files from the network using the " "FTP, SFTP, TFTP, NFS, HTTP and HTTPS protocols. Petitboot can boot any " "operating system that includes kexec boot support." msgstr "" #. Tag: para #: boot-installer.xml:2090 #, no-c-format msgid "" "Petitboot looks for bootloader configuration files on mountable devices in " "the system, and can also be configured to use boot information from a DHCP " "server." msgstr "" #. Tag: para #: boot-installer.xml:2141 #, no-c-format msgid "" "On machines with OpenBoot, simply enter the boot monitor on the machine " "which is being installed (see ). Use " "the command boot net to boot from a TFTP and RARP " "server, or try boot net:bootp or boot net:" "dhcp to boot from a TFTP and BOOTP or DHCP server. You can pass " "extra boot parameters to &d-i; at the end of the boot " "command." msgstr "" #. Tag: para #: boot-installer.xml:2195 #, no-c-format msgid "" "Most OpenBoot versions support the boot cdrom command " "which is simply an alias to boot from the SCSI device on ID 6 (or the " "secondary master for IDE based systems)." msgstr "" #. Tag: title #: boot-installer.xml:2204 #, no-c-format msgid "IDPROM Messages" msgstr "IDPROM üzenetek" #. Tag: para #: boot-installer.xml:2205 #, no-c-format msgid "" "If you cannot boot because you get messages about a problem with " "IDPROM, then it's possible that your NVRAM battery, which " "holds configuration information for you firmware, has run out. See the " "Sun NVRAM FAQ for more " "information." msgstr "" "Ha IDPROM gondokról szóló üzenetek miatt nem tudsz indítani, " "lehet, hogy az NVRAM elem, mely a firmware beállításait tartalmazza, " "lemerült. Lásd a Sun NVRAM GYIK " "címet több adatért." #. Tag: title #: boot-installer.xml:2224 #, no-c-format msgid "Accessibility" msgstr "" #. Tag: para #: boot-installer.xml:2225 #, no-c-format msgid "" "Some users may need specific support because of e.g. some visual impairment. " "USB braille displays are detected " "automatically (not serial displays connected via a serial-to-USB converter), " "but most other Most accessibility features have to be enabled manually. On machines that support it, the boot menu emits beeps when it " "is ready to receive keystrokes. It beeps once on BIOS systems, and beeps " "twice on UEFI systems. Some boot parameters can then be appended to enable accessibility features (see also ). Note that " "on most architectures the boot loader interprets your keyboard as a QWERTY " "keyboard." msgstr "" #. Tag: title #: boot-installer.xml:2246 #, no-c-format msgid "Installer front-end" msgstr "" #. Tag: para #: boot-installer.xml:2247 #, no-c-format msgid "" "The &debian; installer supports several front-ends for asking questions, " "with varying convenience for accessibility: notably, text uses plain text while newt uses text-based " "dialog boxes. The choice can be made at the boot prompt, see the " "documentation for DEBIAN_FRONTEND in ." msgstr "" #. Tag: title #: boot-installer.xml:2259 #, no-c-format msgid "USB Braille Displays" msgstr "" #. Tag: para #: boot-installer.xml:2260 #, no-c-format msgid "" "USB braille displays should be automatically detected. A textual version of " "the installer will then be automatically selected, and support for the " "braille display will be automatically installed on the target system. You " "can thus just press &enterkey; at the boot menu. Once brltty is started, you can choose a braille table by entering the " "preference menu. Documentation on key bindings for braille devices is " "available on the brltty website." msgstr "" #. Tag: title #: boot-installer.xml:2275 #, no-c-format msgid "Serial Braille Displays" msgstr "" #. Tag: para #: boot-installer.xml:2276 #, no-c-format msgid "" "Serial braille displays cannot safely be automatically detected (since that " "may damage some of them). You thus need to append the " "brltty=driver,port boot parameter to tell brltty which driver and port it should use. driver should be replaced by the two-letter driver code for your " "terminal (see the BRLTTY manual). " "port should be replaced by the name of the serial " "port the display is connected to, ttyS0 is the " "default, ttyUSB0 can be typically used when using a " "serial-to-USB converter. A third parameter can be provided, to choose the " "name of the braille table to be used (see the BRLTTY manual); the English table is the default. Note " "that the table can be changed later by entering the preference menu. A " "fourth parameter can be provided to pass parameters to the braille driver, " "such as protocol=foo which is needed for some rare " "models. Documentation on key bindings for braille devices is available on " "the brltty " "website." msgstr "" #. Tag: title #: boot-installer.xml:2303 boot-installer.xml:3332 #, no-c-format msgid "Software Speech Synthesis" msgstr "" #. Tag: para #: boot-installer.xml:2304 #, no-c-format msgid "" "Support for software speech synthesis is available on all installer images " "which have the graphical installer, i.e. all netinst, CD and DVD images, and " "the netboot gtk variant. It can be activated by selecting it in the boot " "menu by typing s &enterkey;. The textual version of " "the installer will then be automatically selected, and support for software " "speech synthesis will be automatically installed on the target system." msgstr "" #. Tag: para #: boot-installer.xml:2313 #, no-c-format msgid "" "The first question (language) is spoken in english, and the remainder of " "installation is spoken in the selected language (if available in " "espeak)." msgstr "" #. Tag: para #: boot-installer.xml:2319 #, no-c-format msgid "" "The default speech rate is quite slow. To make it faster, press " "CapsLock6. To make it " "slower, press CapsLock5. The default volume should be medium. To make it louder, press " "CapsLock2. To make it " "quieter, press CapsLock1. To get more details on the browsing shortcuts, see the Speakup guide. To just accept the default " "answer for a question, simply press Enter at the prompt. To " "provide an empty answer for a question, type ! at the " "prompt. To get back to the previous question, type < at the prompt." msgstr "" #. Tag: title #: boot-installer.xml:2347 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para #: boot-installer.xml:2348 #, no-c-format msgid "" "Support for hardware speech synthesis devices is available on all installer " "images which have the graphical installer, i.e. all netinst, CD and DVD " "images, and the netboot gtk variant. You thus need to select a " "Graphical install entry in the boot menu." msgstr "" #. Tag: para #: boot-installer.xml:2355 #, no-c-format msgid "" "Hardware speech synthesis devices cannot be automatically detected. You thus " "need to append the speakup.synth=driver boot parameter to tell speakup which driver it should use. driver " "should be replaced by the driver code for your device (see driver code list). The textual version of the " "installer will then be automatically selected, and support for the speech " "synthesis device will be automatically installed on the target system." msgstr "" #. Tag: title #: boot-installer.xml:2370 #, no-c-format msgid "Board Devices" msgstr "" #. Tag: para #: boot-installer.xml:2371 #, no-c-format msgid "" "Some accessibility devices are actual boards that are plugged inside the " "machine and that read text directly from the video memory. To get them to " "work framebuffer support must be disabled by using the vga=normal fb=false boot " "parameter. This will however reduce the number of available languages." msgstr "" #. Tag: para #: boot-installer.xml:2379 #, no-c-format msgid "" "If desired a textual version of the bootloader can be activated before " "adding the boot parameter by typing h &enterkey;." msgstr "" #. Tag: title #: boot-installer.xml:2387 #, no-c-format msgid "High-Contrast Theme" msgstr "" #. Tag: para #: boot-installer.xml:2388 #, no-c-format msgid "" "For users with low vision, the installer can use a high-contrast color theme " "that makes it more readable. To enable it, append the theme=dark boot parameter." msgstr "" #. Tag: title #: boot-installer.xml:2397 #, no-c-format msgid "Zoom" msgstr "" #. Tag: para #: boot-installer.xml:2398 #, no-c-format msgid "" "For users with low vision, the graphical installer has a very basic zoom " "support: the Control + and Control - shortcuts increase and decrease the font size." msgstr "" #. Tag: title #: boot-installer.xml:2408 #, no-c-format msgid "Preseeding" msgstr "" #. Tag: para #: boot-installer.xml:2409 #, no-c-format msgid "" "Alternatively, &debian; can be installed completely automatically by using " "preseeding. This is documented in ." msgstr "" #. Tag: title #: boot-installer.xml:2417 #, no-c-format msgid "Accessibility of the installed system" msgstr "" #. Tag: para #: boot-installer.xml:2418 #, no-c-format msgid "" "Documentation on accessibility of the installed system is available on the " "Debian Accessibility wiki " "page." msgstr "" #. Tag: para #: boot-installer.xml:2433 #, no-c-format msgid "" "Boot parameters are Linux kernel parameters which are generally used to make " "sure that peripherals are dealt with properly. For the most part, the kernel " "can auto-detect information about your peripherals. However, in some cases " "you'll have to help the kernel a bit." msgstr "" "Az indító paraméterek Linux kernel paraméterek, melyek általában a " "perifériák helyes használatára szolgálnak. A kernel általában képes ezek " "adatainak automatikus érzékelésére. Egyes esetekben azonban egy kis segítség " "szükséges." #. Tag: para #: boot-installer.xml:2440 #, no-c-format msgid "" "If this is the first time you're booting the system, try the default boot " "parameters (i.e., don't try setting parameters) and see if it works " "correctly. It probably will. If not, you can reboot later and look for any " "special parameters that inform the system about your hardware." msgstr "" "A rendszert 1. ízben az alap paraméterekkel jó indítani (vagyis továbbiak " "megadása nélkül) és meggyőződni arról, működése helyes-e. Ha nem, egy " "későbbi újraindításkor megadhatók különleges paraméterek, melyek a rendszert " "kisegítik egyes adatokkal a hardverről." #. Tag: para #: boot-installer.xml:2447 #, no-c-format msgid "" "Information on many boot parameters can be found in the Linux BootPrompt HOWTO, " "including tips for obscure hardware. This section contains only a sketch of " "the most salient parameters. Some common gotchas are included below in ." msgstr "" "Sok indító paraméterről szóló adat van a Linux BootPrompt HOGYAN leírásban, " "benne kétes hardverekről szólók is. Ez csak egy vázlatos szakasz a " "legáltalánosabb paraméterekről. Néhány szokásos találat megtalálható az " "alábbi: részben." #. Tag: title #: boot-installer.xml:2459 #, no-c-format msgid "Boot console" msgstr "" #. Tag: para #: boot-installer.xml:2461 #, fuzzy, no-c-format #| msgid "" #| "If you are booting with a serial console, generally the kernel will " #| "autodetect this (although not on DECstations). If you have a videocard (framebuffer) and a keyboard also " #| "attached to the computer which you wish to boot via serial console, you " #| "may have to pass the console=device argument to the kernel, where " #| "device is your serial device, which is usually " #| "something like ttyS0." msgid "" "If you are booting with a serial console, generally the kernel will " "autodetect this. If you have a videocard (framebuffer) and a keyboard also " "attached to the computer which you wish to boot via serial console, you may " "have to pass the console=device argument to the kernel, where device " "is your serial device, which is usually something like ttyS0." msgstr "" "Soros konzollal indításkor a kernel általában automatikusan felismeri " "ezt (DECstation esetén nem). Ha van videó " "kártya (framebuffer) és billentyűzet a soros konzol által indítandó gépen, " "át kell adni a console=eszköz argumentumot a kernelnek, ahol az eszköz a soros eszköz, mely általában valami ilyesmi: ttyS0." #. Tag: para #: boot-installer.xml:2473 #, no-c-format msgid "" "You may need to specify parameters for the serial port, such as speed and " "parity, for instance console=ttyS0,9600n8; other " "typical speeds may be 57600 or 115200. Be sure to specify this option after " "---, so that it is copied into the bootloader configuration " "for the installed system (if supported by the installer for the bootloader)." msgstr "" #. Tag: para #: boot-installer.xml:2481 #, fuzzy, no-c-format #| msgid "" #| "If you are booting with a serial console, generally the kernel will " #| "autodetect this (although not on DECstations). If you have a videocard (framebuffer) and a keyboard also " #| "attached to the computer which you wish to boot via serial console, you " #| "may have to pass the console=device argument to the kernel, where " #| "device is your serial device, which is usually " #| "something like ttyS0." msgid "" "In order to ensure the terminal type used by the installer matches your " "terminal emulator, the parameter TERM=type can be added. Note that the installer only supports " "the following terminal types: linux, bterm, ansi, vt102 and " "dumb. The default for serial console in &d-i; is " "vt102. If you are using a virtualization tool which " "does not provide conversion into such terminals types itself, e.g. QEMU/KVM, " "you can start it inside a screen session. That will " "indeed perform translation into the screen terminal type, " "which is very close to vt102." msgstr "" "Soros konzollal indításkor a kernel általában automatikusan felismeri " "ezt (DECstation esetén nem). Ha van videó " "kártya (framebuffer) és billentyűzet a soros konzol által indítandó gépen, " "át kell adni a console=eszköz argumentumot a kernelnek, ahol az eszköz a soros eszköz, mely általában valami ilyesmi: ttyS0." #. Tag: para #: boot-installer.xml:2497 #, no-c-format msgid "" "For &arch-title; the serial devices are ttya or " "ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " "ttya." msgstr "" "&arch-title; architektúrán a soros eszközök neve ttya " "vagy ttyb. Vagy állítsd be, hogy az input-" "device és output-device OpenPROM változók értéke " "legyen ttya." #. Tag: title #: boot-installer.xml:2509 #, no-c-format msgid "&debian; Installer Parameters" msgstr "&debian; Telepítő paraméterek" #. Tag: para #: boot-installer.xml:2510 #, no-c-format msgid "" "The installation system recognizes a few additional boot " "parameters With current kernels (2.6.9 or newer) you can " "use 32 command line options and 32 environment options. If these numbers are " "exceeded, the kernel will panic. which may be useful." msgstr "" "A telepítő rendszer pár további indító paramétert is ismer " "A jelenlegi kernelekkel (2.6.9 vagy újabb) 32 parancssori opció és 32 " "környezeti opció használható. Ennek túllépése kernel pánikot okoz. mely hasznos lehet." #. Tag: para #: boot-installer.xml:2523 #, no-c-format msgid "" "A number of parameters have a short form that helps avoid the " "limitations of the kernel command line options and makes entering the " "parameters easier. If a parameter has a short form, it will be listed in " "brackets behind the (normal) long form. Examples in this manual will " "normally use the short form too." msgstr "" "Sok paraméterhez van egy rövid forma, mely segít elkerülni a " "kernel parancs-sori opciók korlátját és könnyebbé teszi a paraméterek " "megadását. Ha egy paraméternek van rövid formája, zárójelben írjuk a " "(rendes) hosszú forma után. A példák is a rövid formát használják." #. Tag: term #: boot-installer.xml:2535 #, no-c-format msgid "debconf/priority (priority)" msgstr "debconf/priority (elsőbbség)" #. Tag: para #: boot-installer.xml:2536 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "E paraméter adja meg a megjelenítendő üzenetek legkisebb elsőbbségét." #. Tag: para #: boot-installer.xml:2540 #, no-c-format msgid "" "The default installation uses priority=high. This " "means that both high and critical priority messages are shown, but medium " "and low priority messages are skipped. If problems are encountered, the " "installer adjusts the priority as needed." msgstr "" "Az alap telepítés a priority=high értéket használja. " "Ekkor a kritikus és magas elsőbbségű üzenetek jelennek meg, a közepes és " "alacsony elsőbbségű üzenetek nem. Hibák esetén a telepítő a szükséges " "szintre állítja ezt." #. Tag: para #: boot-installer.xml:2547 #, no-c-format msgid "" "If you add priority=medium as boot parameter, you " "will be shown the installation menu and gain more control over the " "installation. When priority=low is used, all messages " "are shown (this is equivalent to the expert boot " "method). With priority=critical, the installation " "system will display only critical messages and try to do the right thing " "without fuss." msgstr "" "A priority=medium részletesebb irányítást ad a " "telepítéshez. A priority=low mindent kérdez (ez " "ugyanaz, mint az expert indítás mód). A " "priority=critical esetén a rendszer csak a kritikus " "üzeneteket jeleníti meg és ha minden rendben, nem kérdez." #. Tag: term #: boot-installer.xml:2561 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "DEBIAN_FRONTEND" #. Tag: para #: boot-installer.xml:2562 #, fuzzy, no-c-format #| msgid "" #| "This boot parameter controls the type of user interface used for the " #| "installer. The current possible parameter settings are: " #| " DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " #| "DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk The default frontend is " #| "DEBIAN_FRONTEND=newt. " #| "DEBIAN_FRONTEND=text may be preferable for serial " #| "console installs. Generally, only the newt " #| "frontend is available on default install media. On architectures that " #| "support it, the graphical installer uses the gtk " #| "frontend." msgid "" "This boot parameter controls the type of user interface used for the " "installer. The current possible parameter settings are: " " DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " "DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk " " The default frontend is " "DEBIAN_FRONTEND=newt. " "DEBIAN_FRONTEND=text may be preferable for serial " "console installs. Some specialized types of install media may only offer a " "limited selection of frontends, but the newt and " "text frontends are available on most default install " "media. On architectures that support it, the graphical installer uses the " "gtk frontend." msgstr "" "Ez szabja meg a telepítő által használt felhasználó felületet. A jelenlegi " "lehetséges paraméter beállítások: " "DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " " DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk Az alapfelület a " "DEBIAN_FRONTEND=newt. A " "DEBIAN_FRONTEND=text soros konzolos telepítésekhez " "jó. Általában csak a newt felület elérhető az alap " "telepítő médián. A támogató architektúrákon a grafikus telepítő a " "gtk felületet használja." #. Tag: term #: boot-installer.xml:2593 #, no-c-format msgid "BOOT_DEBUG" msgstr "BOOT_DEBUG" #. Tag: para #: boot-installer.xml:2594 #, no-c-format msgid "" "Setting this boot parameter to 2 will cause the installer's boot process to " "be verbosely logged. Setting it to 3 makes debug shells available at " "strategic points in the boot process. (Exit the shells to continue the boot " "process.)" msgstr "" "Ha e paraméter értéke 2, a telepítő indító folyamat részletesebb naplózásra " "kerül. Ha 3, hibakereső héjakat tesz elérhetővé az indító folyamat fő " "pontjain. (Lépj ki a héjakból az indító folyamat folytatásához.)" #. Tag: userinput #: boot-installer.xml:2603 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "BOOT_DEBUG=0" #. Tag: para #: boot-installer.xml:2604 #, no-c-format msgid "This is the default." msgstr "Ez az alap." #. Tag: userinput #: boot-installer.xml:2608 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "BOOT_DEBUG=1" #. Tag: para #: boot-installer.xml:2609 #, no-c-format msgid "More verbose than usual." msgstr "Átlagnál bővebb." #. Tag: userinput #: boot-installer.xml:2613 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "BOOT_DEBUG=2" #. Tag: para #: boot-installer.xml:2614 #, no-c-format msgid "Lots of debugging information." msgstr "Sok hibakereső adat." #. Tag: userinput #: boot-installer.xml:2618 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "BOOT_DEBUG=3" #. Tag: para #: boot-installer.xml:2619 #, no-c-format msgid "" "Shells are run at various points in the boot process to allow detailed " "debugging. Exit the shell to continue the boot." msgstr "" "A héjak az indító folyamat különböző pontjain futnak részletes hibák " "visszaadásához. Lépj ki a héjból az indítás folytatásához." #. Tag: term #: boot-installer.xml:2633 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "INSTALL_MEDIA_DEV" #. Tag: para #: boot-installer.xml:2634 #, no-c-format msgid "" "The value of the parameter is the path to the device to load the &debian; " "installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" msgstr "" "E paraméter értéke a &debian; telepítőt betöltő eszköz útvonala. Például " "INSTALL_MEDIA_DEV=/dev/floppy/0" #. Tag: para #: boot-installer.xml:2640 #, no-c-format msgid "" "The boot floppy, which normally scans all floppies it can to find the root " "floppy, can be overridden by this parameter to only look at the one device." msgstr "" "Az indító flopi, ami alapban végignézi az összes flopit a gyökér flopi " "megtalálásához felülírható e paraméterrel, hogy csak 1 eszközt nézzen." #. Tag: term #: boot-installer.xml:2651 #, no-c-format msgid "log_host" msgstr "" #. Tag: term #: boot-installer.xml:2652 #, no-c-format msgid "log_port" msgstr "" #. Tag: para #: boot-installer.xml:2653 #, no-c-format msgid "" "Causes the installer to send log messages to a remote syslog on the " "specified host and port as well as to a local file. If not specified, the " "port defaults to the standard syslog port 514." msgstr "" #. Tag: term #: boot-installer.xml:2664 #, no-c-format msgid "lowmem" msgstr "" #. Tag: para #: boot-installer.xml:2665 #, no-c-format msgid "" "Can be used to force the installer to a lowmem level higher than the one the " "installer sets by default based on available memory. Possible values are 1 " "and 2. See also ." msgstr "" #. Tag: term #: boot-installer.xml:2675 #, no-c-format msgid "noshell" msgstr "" #. Tag: para #: boot-installer.xml:2676 #, no-c-format msgid "" "Prevents the installer from offering interactive shells on tty2 and tty3. " "Useful for unattended installations where physical security is limited." msgstr "" #. Tag: term #: boot-installer.xml:2685 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "debian-installer/framebuffer (fb)" #. Tag: para #: boot-installer.xml:2686 #, fuzzy, no-c-format #| msgid "" #| "Some architectures use the kernel framebuffer to offer installation in a " #| "number of languages. If framebuffer causes a problem on your system you " #| "can disable the feature by the parameter fb=false. " #| "Problem symptoms are error messages about bterm or bogl, a blank screen, " #| "or a freeze within a few minutes after starting the install." msgid "" "Some architectures use the kernel framebuffer to offer installation in a " "number of languages. If framebuffer causes a problem on your system you can " "disable the feature using the parameter vga=normal fb=false. Problem symptoms are error " "messages about bterm or bogl, a blank screen, or a freeze within a few " "minutes after starting the install." msgstr "" "Egyes architektúrák használják a kernel framebuffert a telepítő több-nyelvű " "támogatásához. Ha ez gondot okoz, kikapcsolható az fb=false paraméterrel. A szokásos gondok hibaüzenetek a bterm és bogl " "körül, üres képernyő vagy fagyás a telepítés indítása után pár perccel." #. Tag: para #: boot-installer.xml:2695 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "Hasonló problémákról érkezett jelentés egyes hppa gépeken." #. Tag: para #: boot-installer.xml:2699 #, no-c-format msgid "" "Because of display problems on some systems, framebuffer support is " "disabled by default for &arch-title;. This can result " "in ugly display on systems that do properly support the framebuffer, like " "those with ATI graphical cards. If you see display problems in the " "installer, you can try booting with parameter debian-installer/" "framebuffer=true or fb=true for short." msgstr "" "Egyes rendszerek kijelző-gondjai miatt a framebuffer támogatás " "alapból kikapcsolt &arch-title; architektúránál. Ez " "kissé csúf megjelenést okozhat ott, ahol a támogatás amúgy működne, például " "ATI kártyák esetén. A kijelző problémákat látsz a telepítőben, indíthatsz a " "debian-installer/framebuffer=true vagy röviden " "fb=true paraméterrel." #. Tag: term #: boot-installer.xml:2713 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "debian-installer/theme (téma)" #. Tag: para #: boot-installer.xml:2714 #, no-c-format msgid "" "A theme determines how the user interface of the installer looks (colors, " "icons, etc.). What themes are available differs per frontend. Currently both " "the newt and gtk frontends only have a dark theme that was " "designed for visually impaired users. Set the theme by booting with " "theme=dark." msgstr "" "Egy téma meghatározza, hogyan nézzen ki a telepítő felhasználói felülete " "(színek, ikonok, stb.). Az elérhető témák a felülettől függenek. A newt és " "gtk felületek is támogatják a dark témát, mely gyengén " "látóknak is megfelelő. A téma így állítható be: " "theme=dark." #. Tag: term #: boot-installer.xml:2726 boot-installer.xml:2959 #, no-c-format msgid "netcfg/disable_autoconfig" msgstr "netcfg/disable_autoconfig" #. Tag: para #: boot-installer.xml:2727 #, fuzzy, no-c-format #| msgid "" #| "By default, the &d-i; automatically probes for network configuration via " #| "DHCP. If the probe succeeds, you won't have a chance to review and change " #| "the obtained settings. You can get to the manual network setup only in " #| "case the DHCP probe fails." msgid "" "By default, the &d-i; automatically probes for network configuration via " "IPv6 autoconfiguration and DHCP. If the probe succeeds, you won't have a " "chance to review and change the obtained settings. You can get to the manual " "network setup only in case the automatic configuration fails." msgstr "" "Alapértelmezetten a &d-i; önműködően megpróbálja a hálózatot beállítani DHCP-" "n át. Ha sikerül, valószínűleg nem lesz esély a kapott beállítások " "módosítására. A hálózat kézi beállítása csak a DHCP meghiúsulásakor " "lehetséges." #. Tag: para #: boot-installer.xml:2734 #, fuzzy, no-c-format #| msgid "" #| "If you have a DHCP server on your local network, but want to avoid it " #| "because e.g. it gives wrong answers, you can use the parameter " #| "netcfg/disable_autoconfig=true to prevent " #| "configuring the network with DHCP and to enter the information manually." msgid "" "If you have an IPv6 router or a DHCP server on your local network, but want " "to avoid them because e.g. they give wrong answers, you can use the " "parameter netcfg/disable_autoconfig=true to prevent " "any automatic configuration of the network (neither v4 nor v6) and to enter " "the information manually." msgstr "" "Ha van egy DHCP kiszolgáló a helyi hálózaton, de nem akarod használni, mert " "például rossz választ ad, használhatod a netcfg/" "disable_autoconfig=true paramétert a hálózati DHCP-beállítás " "tiltására és megadhatod az adatokat kézzel." #. Tag: term #: boot-installer.xml:2745 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "hw-detect/start_pcmcia" #. Tag: para #: boot-installer.xml:2746 #, no-c-format msgid "" "Set to false to prevent starting PCMCIA services, if " "that causes problems. Some laptops are well known for this misbehavior." msgstr "" "A false tiltja a PCMCIA szolgáltatások indítását, ha " "gondot okoznak. Egyes laptopok híresek erről." #. Tag: term #: boot-installer.xml:2756 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "" #. Tag: para #: boot-installer.xml:2757 #, no-c-format msgid "" "Set to true to enable support for Serial ATA RAID " "(also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note " "that this support is currently experimental. Additional information can be " "found on the &debian; Installer Wiki." msgstr "" #. Tag: term #: boot-installer.xml:2768 #, no-c-format msgid "preseed/url (url)" msgstr "preseed/url (url)" #. Tag: para #: boot-installer.xml:2769 #, no-c-format msgid "" "Specify the url to a preconfiguration file to download and use for " "automating the install. See ." msgstr "" "Megadja az automata telepítéshez letöltendő és használandó elő-beállító " "fájlra mutató url-t. Lásd a részt." #. Tag: term #: boot-installer.xml:2778 #, no-c-format msgid "preseed/file (file)" msgstr "preseed/file (fájl)" #. Tag: para #: boot-installer.xml:2779 #, no-c-format msgid "" "Specify the path to a preconfiguration file to load for automating the " "install. See ." msgstr "" "Megadja az automata telepítéshez betöltendő elő-beállító fájl útvonalát. " "Lásd a részt." #. Tag: term #: boot-installer.xml:2788 #, no-c-format msgid "preseed/interactive" msgstr "preseed/interactive" #. Tag: para #: boot-installer.xml:2789 #, no-c-format msgid "" "Set to true to display questions even if they have " "been preseeded. Can be useful for testing or debugging a preconfiguration " "file. Note that this will have no effect on parameters that are passed as " "boot parameters, but for those a special syntax can be used. See for details." msgstr "" "Legyen true az előírt kérdések feltevéséhez is. Egy " "előíró fájl próbájára vagy javítására jó. Ez nem hat az átadott indító " "paraméterekre, ezek esetén különleges nyelvtan kell. Lásd itt: ." #. Tag: term #: boot-installer.xml:2801 #, no-c-format msgid "auto-install/enable (auto)" msgstr "auto-install/enable (auto)" #. Tag: para #: boot-installer.xml:2802 #, no-c-format msgid "" "Delay questions that are normally asked before preseeding is possible until " "after the network is configured. See for " "details about using this to automate installs." msgstr "" "Az elő-beállítások végrehajtása előtt felteendő kérdések megválaszolása " "elhalasztható a hálózat beállításáig. Lásd a részt ennek használatához az automata telepítésben." #. Tag: term #: boot-installer.xml:2813 #, no-c-format msgid "finish-install/keep-consoles" msgstr "" #. Tag: para #: boot-installer.xml:2814 #, no-c-format msgid "" "During installations from serial or management console, the regular virtual " "consoles (VT1 to VT6) are normally disabled in /etc/inittab. Set to true to prevent this." msgstr "" #. Tag: term #: boot-installer.xml:2825 #, no-c-format msgid "cdrom-detect/eject" msgstr "cdrom-detect/eject" #. Tag: para #: boot-installer.xml:2826 #, no-c-format msgid "" "By default, before rebooting, &d-i; automatically ejects the optical media " "used during the installation. This can be unnecessary if the system does not " "automatically boot off the CD. In some cases it may even be undesirable, for " "example if the optical drive cannot reinsert the media itself and the user " "is not there to do it manually. Many slot loading, slim-line, and caddy " "style drives cannot reload media automatically." msgstr "" "Alapban az újraindítás előtt a &d-i; önműködően kiadja a telepítés alatt " "használt optikai médiát. Ez szükségtelen, ha a rendszer nem indul önműködően " "a CD-lemezről. Néha kimondottan rossz, például, ha az optikai meghajtó nem " "teszi be újra a médiát és a felhasználó nincs ott. Sok rés-töltős, karcsú és " "fentről-töltős stílusú meghajtó nem tudja automatikusan újratölteni a médiát." #. Tag: para #: boot-installer.xml:2835 #, no-c-format msgid "" "Set to false to disable automatic ejection, and be " "aware that you may need to ensure that the system does not automatically " "boot from the optical drive after the initial installation." msgstr "" "Legyen false az automata kiadás kikapcsolásához, " "ekkor magadnak kell biztosítani, hogy a rendszer ne induljon önműködően az " "optikai meghajtóról a telepítés után." #. Tag: term #: boot-installer.xml:2846 #, fuzzy, no-c-format #| msgid "debian-installer/theme (theme)" msgid "base-installer/install-recommends (recommends)" msgstr "debian-installer/theme (téma)" #. Tag: para #: boot-installer.xml:2847 #, no-c-format msgid "" "By setting this option to false, the package " "management system will be configured to not automatically install " "Recommends, both during the installation and for the " "installed system. See also ." msgstr "" #. Tag: para #: boot-installer.xml:2854 #, no-c-format msgid "" "Note that this option allows to have a leaner system, but can also result in " "features being missing that you might normally expect to be available. You " "may have to manually install some of the recommended packages to obtain the " "full functionality you want. This option should therefore only be used by " "very experienced users." msgstr "" #. Tag: term #: boot-installer.xml:2866 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "debian-installer/allow_unauthenticated" #. Tag: para #: boot-installer.xml:2867 #, no-c-format msgid "" "By default the installer requires that repositories be authenticated using a " "known gpg key. Set to true to disable that " "authentication. Warning: insecure, not recommended." msgstr "" "Alapban a telepítő ismert gpg kulcs által hitelesített tárat igényel. " "Állítsd true értékre a hitelesítés kikapcsolásához. " "Figyelem: nem biztonságos, nem ajánlott." #. Tag: term #: boot-installer.xml:2878 #, no-c-format msgid "ramdisk_size" msgstr "ramdisk_size" #. Tag: para #: boot-installer.xml:2879 #, no-c-format msgid "" "This parameter should already be set to a correct value where needed; set it " "only it you see errors during the boot that indicate the ramdisk could not " "be loaded completely. The value is in kB." msgstr "" "E paraméter alapban már helyes, ha szükséges volt; csak akkor állítsd, ha " "hibát látsz a telepítés során, ami azt jelzi, hogy a ram-lemez nem került " "teljesen betöltésre. A mértékegység: kB." #. Tag: term #: boot-installer.xml:2889 #, no-c-format msgid "rescue/enable" msgstr "rescue/enable" #. Tag: para #: boot-installer.xml:2890 #, no-c-format msgid "" "Set to true to enter rescue mode rather than " "performing a normal installation. See ." msgstr "" "Legyen true a rendes telepítés helyett mentő módba " "lépéshez. Lásd: ." #. Tag: title #: boot-installer.xml:2903 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "Indító paraméterek használata kérdések megválaszolására" #. Tag: para #: boot-installer.xml:2904 #, no-c-format msgid "" "With some exceptions, a value can be set at the boot prompt for any question " "asked during the installation, though this is only really useful in specific " "cases. General instructions how to do this can be found in . Some specific examples are listed below." msgstr "" "Pár kivétellel az indító jelnél bármely telepítés alatt feltett kérdés " "értéke beállítható, ez csak egyes esetekben igazán hasznos. Általános leírás " "erről a részben. Íme pár példa." #. Tag: term #: boot-installer.xml:2916 #, fuzzy, no-c-format #| msgid "debian-installer/locale (locale)" msgid "debian-installer/language (language)" msgstr "debian-installer/locale (honosítás)" #. Tag: term #: boot-installer.xml:2917 #, fuzzy, no-c-format #| msgid "debian-installer/theme (theme)" msgid "debian-installer/country (country)" msgstr "debian-installer/theme (téma)" #. Tag: term #: boot-installer.xml:2918 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "debian-installer/locale (honosítás)" #. Tag: para #: boot-installer.xml:2919 #, no-c-format msgid "" "There are two ways to specify the language, country and locale to use for " "the installation and the installed system." msgstr "" #. Tag: para #: boot-installer.xml:2924 #, no-c-format msgid "" "The first and easiest is to pass only the parameter locale. Language and country will then be derived from its value. You can " "for example use locale=de_CH to select German as " "language and Switzerland as country (de_CH.UTF-8 will be " "set as default locale for the installed system). Limitation is that not all " "possible combinations of language, country and locale can be achieved this " "way." msgstr "" #. Tag: para #: boot-installer.xml:2933 #, no-c-format msgid "" "The second, more flexible option is to specify language " "and country separately. In this case locale can optionally be added to specify a specific default locale for " "the installed system. Example: language=en country=DE " "locale=en_GB.UTF-8." msgstr "" #. Tag: term #: boot-installer.xml:2945 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "anna/choose_modules (modules)" #. Tag: para #: boot-installer.xml:2946 #, no-c-format msgid "" "Can be used to automatically load installer components that are not loaded " "by default. Examples of optional components that may be useful are " "openssh-client-udeb (so you can use scp during the installation) and " "ppp-udeb (see )." msgstr "" "Az alapban nem betöltött telepítő összetevők automata betöltésére " "használható. Példa lehetséges hasznos összetevőre az openssh-" "client-udeb (így használhatod az scp másolót " "a telepítés alatt) és a ppp-udeb (lásd itt: )." #. Tag: para #: boot-installer.xml:2960 #, fuzzy, no-c-format #| msgid "" #| "Set to true if you want to disable DHCP and " #| "instead force static network configuration." msgid "" "Set to true if you want to disable IPv6 " "autoconfiguration and DHCP and instead force static network configuration." msgstr "" "Állítsd true értékre a DHCP kikapcsolásához és " "helyette statikus hálózati beállítás kikényszerítéséhez." #. Tag: term #: boot-installer.xml:2969 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "mirror/protocol (protocol)" #. Tag: para #: boot-installer.xml:2970 #, no-c-format msgid "" "By default the installer will use the http protocol to download files from " "&debian; mirrors and changing that to ftp is not possible during " "installations at normal priority. By setting this parameter to " "ftp, you can force the installer to use that protocol " "instead. Note that you cannot select an ftp mirror from a list, you have to " "enter the hostname manually." msgstr "" "Alapban a telepítő http protokollt használ fájlok letöltésére &debian; " "tükrökről és ftp protkollra cserélésre nincs mód telepítéskor normál " "elsőbbségnél. A paraméter beállítása ftp protokollra " "a telepítőt ennek használatára bírja. Fontos tudni, hogy a listából nem " "választható ftp tükör, ezt kézzel kell majd megadni." #. Tag: term #: boot-installer.xml:2983 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "tasksel:tasksel/first (feladatok)" #. Tag: para #: boot-installer.xml:2984 #, no-c-format msgid "" "Can be used to select tasks that are not available from the interactive task " "list, such as the kde-desktop task. See for additional information." msgstr "" "Az interaktív listából el nem érhető feladatok kiválasztására használható, " "fontos például a hungarian-desktop használata. Lásd a " " részt további adatokért." #. Tag: title #: boot-installer.xml:2998 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "Paraméterek átadása kernel moduloknak" #. Tag: para #: boot-installer.xml:2999 #, no-c-format msgid "" "If drivers are compiled into the kernel, you can pass parameters to them as " "described in the kernel documentation. However, if drivers are compiled as " "modules and because kernel modules are loaded a bit differently during an " "installation than when booting an installed system, it is not possible to " "pass parameters to modules as you would normally do. Instead, you need to " "use a special syntax recognized by the installer which will then make sure " "that the parameters are saved in the proper configuration files and will " "thus be used when the modules are actually loaded. The parameters will also " "be propagated automatically to the configuration for the installed system." msgstr "" "Kernelbe fordított meghajtók számára lehetséges a kernel dokumentációja " "szerinti paraméterek átadása. Ám akkor, ha modulokként fordítottak, mivel " "ezek kissé másképp töltődnek be a telepítéskor, mint a telepített " "rendszeren, nem adhatók át úgy paraméterek, mint rendesen. A telepítő által " "ismert különleges szintaxist kell használni, így ezek a helyes beállító " "fájlba kerülnek és felhasználásra kerülnek a modulok tényleges betöltésekor. " "E paraméterek átkerülnek a telepített rendszerbe is." #. Tag: para #: boot-installer.xml:3012 #, no-c-format msgid "" "Note that it is now quite rare that parameters need to be passed to modules. " "In most cases the kernel will be able to probe the hardware present in a " "system and set good defaults that way. However, in some situations it may " "still be needed to set parameters manually." msgstr "" "Erre ritkán van szükség. A kernel szinte mindig képes a rendszeren lévő " "hardvert kipróbálni és jó alapértelmezett értékeket beállítani. De egyes " "esetekben jól jöhet paraméterek kézi beállítása." #. Tag: para #: boot-installer.xml:3019 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: " "\n" "module_name.parameter_name=value\n" " If you need to pass multiple parameters to the " "same or different modules, just repeat this. For example, to set an old 3Com " "network interface card to use the BNC (coax) connector and IRQ 10, you would " "pass:" msgstr "" "A modulokhoz beállítandó paraméterek nyelvtana:\n" "modul_név.paraméter_név=érték\n" " Ha több paramétert akarsz átadni egy vagy több " "modulhoz, csak ismételd ezt. Például egy régi 3Com hálózati csatoló kártya " "beállítása a BNC (koax) csatlakozó és IRQ 10 használatához:" #. Tag: screen #: boot-installer.xml:3029 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "3c509.xcvr=3 3c509.irq=10" #. Tag: title #: boot-installer.xml:3035 #, no-c-format msgid "Blacklisting kernel modules" msgstr "Kernel modulok feketelistája" #. Tag: para #: boot-installer.xml:3036 #, no-c-format msgid "" "Sometimes it may be necessary to blacklist a module to prevent it from being " "loaded automatically by the kernel and udev. One reason could be that a " "particular module causes problems with your hardware. The kernel also " "sometimes lists two different drivers for the same device. This can cause " "the device to not work correctly if the drivers conflict or if the wrong " "driver is loaded first." msgstr "" "Néha egy modult feketelistára kell tenni, hogy a kernel és udev ne töltse " "be. Például, ha gondot ad egy adott hardverrel. A kernel néha 2 eltérő " "modult ad egy eszközhöz. Ez problémás működést okozhat, e meghajtók ütközése " "vagy előbb rossz meghajtó betöltése esetén." #. Tag: para #: boot-installer.xml:3045 #, no-c-format msgid "" "You can blacklist a module using the following syntax: " "module_name.blacklist=yes. " "This will cause the module to be blacklisted in /etc/modprobe.d/" "blacklist.local both during the installation and for the " "installed system." msgstr "" "Egy modul így tehető feketelistára: module_name.blacklist=yes. Így a modul feketelistára kerül a " "/etc/modprobe.d/blacklist.local fájlban a telepítés és " "a telepített rendszer alatt is." #. Tag: para #: boot-installer.xml:3053 #, no-c-format msgid "" "Note that a module may still be loaded by the installation system itself. " "You can prevent that from happening by running the installation in expert " "mode and unselecting the module from the list of modules displayed during " "the hardware detection phases." msgstr "" "Lehet, hogy a modult a telepítő rendszer tölti be. Ez megakadályozható a " "telepítő szakértő módú futtatásával a modul kijelölt volta törlésével a " "hardver felismerő szakaszokban." #. Tag: title #: boot-installer.xml:3069 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "Hibák elhárítása a telepítő folyamat során" #. Tag: title #: boot-installer.xml:3074 #, no-c-format msgid "CD-ROM Reliability" msgstr "CD-ROM megbízhatóság" #. Tag: para #: boot-installer.xml:3075 #, no-c-format msgid "" "Sometimes, especially with older CD-ROM drives, the installer may fail to " "boot from a CD-ROM. The installer may also — even after booting " "successfully from CD-ROM — fail to recognize the CD-ROM or return " "errors while reading from it during the installation." msgstr "" "Néha, főleg régi CD-ROM meghajtókkal, a telepítő CD-ROM lemezről indítása " "meghiúsulhat. A telepítő — akár a CD-ROM lemezről való sikeres indítás " "után — talán nem ismeri fel a CD-ROM eszközt vagy hibákat ad a " "telepítés alatti olvasásakor." #. Tag: para #: boot-installer.xml:3082 #, no-c-format msgid "" "There are many different possible causes for these problems. We can only " "list some common issues and provide general suggestions on how to deal with " "them. The rest is up to you." msgstr "" "Ennek sok eltérő oka lehet. Csak néhány szokásos hibát és kezelésükről szóló " "általános tanácsot írunk le. A többi tőled függ." #. Tag: para #: boot-installer.xml:3088 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "Először 2 egyszerű dolgot érdemes kipróbálni." #. Tag: para #: boot-installer.xml:3093 #, no-c-format msgid "" "If the CD-ROM does not boot, check that it was inserted correctly and that " "it is not dirty." msgstr "" "Ha a CD-ROM nem indul, ellenőrizd, helyesen van-e betéve és nem piszkos-e." #. Tag: para #: boot-installer.xml:3099 #, fuzzy, no-c-format #| msgid "" #| "If the installer fails to recognize a CD-ROM, try just running the option " #| " Detect and mount CD-ROM a second time. Some DMA related issues with older CD-ROM " #| "drives are known to be resolved in this way." msgid "" "If the installer fails to recognize a CD-ROM, try just running the option " " Detect and mount CD-ROM a second time. Some DMA related issues with very old CD-ROM " "drives are known to be resolved in this way." msgstr "" "Ha a telepítő nem ismeri fel a CD-ROM meghajtót, először próbáld meg a " " CD-ROM felismerése és csatolása pont futtatását másodszor. Több régi CD-ROM meghajtónál ismert " "DMA hiba megoldható így." #. Tag: para #: boot-installer.xml:3109 #, no-c-format msgid "" "If this does not work, then try the suggestions in the subsections below. " "Most, but not all, suggestions discussed there are valid for both CD-ROM and " "DVD, but we'll use the term CD-ROM for simplicity." msgstr "" "Ha ez nem megy, próbáld az alábbi javaslatokat. Általában az ott tárgyalt " "javaslatok a CD-ROM és DVD eszközökre egyaránt érvényesek, de az egyszerűség " "kedvéért mindig a CD-ROM szót használjuk." #. Tag: para #: boot-installer.xml:3115 #, no-c-format msgid "" "If you cannot get the installation working from CD-ROM, try one of the other " "installation methods that are available." msgstr "" "Ha a telepítés semmiképp nem megy a CD-ROM eszközről, próbálj egy másik " "elérhető telepítő módot." #. Tag: title #: boot-installer.xml:3123 #, no-c-format msgid "Common issues" msgstr "Általános hibák" #. Tag: para #: boot-installer.xml:3126 #, no-c-format msgid "" "Some older CD-ROM drives do not support reading from discs that were burned " "at high speeds using a modern CD writer." msgstr "" "Néhány régi CD-ROM meghajtó nem támogatja a korszerű CD-írók használatával " "nagy sebességgel írt lemezek olvasását." #. Tag: para #: boot-installer.xml:3143 #, fuzzy, no-c-format #| msgid "" #| "Some older CD-ROM drives do not work correctly if direct memory " #| "access (DMA) is enabled." msgid "" "Some very old CD-ROM drives do not work correctly if direct memory " "access (DMA) is enabled for them." msgstr "" "Pár régi CD-ROM meghajtó nem működik rendesen a direkt memória " "elérés (DMA) bekapcsolt volta esetén." #. Tag: title #: boot-installer.xml:3154 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "Hogyan vizsgálj ki és oldj meg gondokat" #. Tag: para #: boot-installer.xml:3155 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" "Ha a CD-ROM eszköz indítása sikertelen, próbáld ki az alább adott " "javaslatokat." #. Tag: para #: boot-installer.xml:3160 #, fuzzy, no-c-format #| msgid "" #| "Check that your BIOS actually supports booting from CD-ROM (older systems " #| "possibly don't) and that your CD-ROM drive supports the media you are " #| "using." msgid "" "Check that your BIOS actually supports booting from CD-ROM (only an issue " "for very old systems) and that CD booting is enabled in the BIOS." msgstr "" "Ellenőrizd, hogy a BIOS támogatja a CD-ROM indítást (a régebbiek nem) és " "hogy a CD-rom meghajtó támogatja a használt médiát." #. Tag: para #: boot-installer.xml:3167 #, no-c-format msgid "" "If you downloaded an iso image, check that the md5sum of that image matches " "the one listed for the image in the MD5SUMS file that " "should be present in the same location as where you downloaded the image " "from. \n" "$ md5sum debian-testing-i386-netinst.iso\n" "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." "iso\n" " Next, check that the md5sum of the burned CD-ROM " "matches as well. The following command should work. It uses the size of the " "image to read the correct number of bytes from the CD-ROM." msgstr "" "Ha letöltöttél egy iso képet, ellenőrizd, hogy az md5sum egyezik az " "MD5SUMS fájlban lévővel, mely ugyanott van, ahonnan " "letöltötted. \n" "$ md5sum debian-testing-i386-netinst.iso\n" "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." "iso\n" " Ezután ellenőrizd, hogy a megírt CD-ROM is " "egyezik. Az alábbi parancs kiváló. Használja a kép méretét helyes számú bájt " "olvasására a CD-ROM lemezről." #. Tag: screen #: boot-installer.xml:3180 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" "> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" "> md5sum\n" "a20391b12f7ff22ef705cee4059c6b92 -\n" "262668+0 records in\n" "262668+0 records out\n" "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" msgstr "" "$ dd if=/dev/cdrom | \\\n" "> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" "> md5sum\n" "a20391b12f7ff22ef705cee4059c6b92 -\n" "262668+0 rekord beolvasva\n" "262668+0 rekord kiírva\n" "134486016 bájt (134 MB) másolva, 97.474 másodperc, 1.4 MB/s" #. Tag: para #: boot-installer.xml:3185 #, no-c-format msgid "" "If, after the installer has been booted successfully, the CD-ROM is not " "detected, sometimes simply trying again may solve the problem. If you have " "more than one CD-ROM drive, try changing the CD-ROM to the other drive. If " "that does not work or if the CD-ROM is recognized but there are errors when " "reading from it, try the suggestions listed below. Some basic knowledge of " "&arch-kernel; is required for this. To execute any of the commands, you " "should first switch to the second virtual console (VT2) and activate the " "shell there." msgstr "" "Ha a telepítő indulása után a CD-ROM érzékelése sikertelen, sokszor az " "ismételt kísérlet sikerül. Ha egynél több CD-ROM meghajtód van, tedd a " "lemezt a másikba. Ha ez sem válik be vagy a CD-ROM felismerésre kerül de " "hibák történnek az olvasáskor, próbáld a lenti javaslatokat. Ehhez kis &arch-" "kernel;-ismeret kell. Parancsok használatához előbb válts a második " "virtuális terminálra (VT2), melyen aktiváld a héjat." #. Tag: para #: boot-installer.xml:3197 #, no-c-format msgid "" "Switch to VT4 or view the contents of /var/log/syslog " "(use nano as editor) to check for any specific error " "messages. After that, also check the output of dmesg." msgstr "" "Válts a VT4 terminálra vagy nézd meg a /var/log/syslog " "tartalmát (használd a nano-t szerkesztőként) a hibák " "ellenőrzéséhez. Ezután ellenőrizd a dmesg kimenetét is." #. Tag: para #: boot-installer.xml:3204 #, no-c-format msgid "" "Check in the output of dmesg if your CD-ROM drive was " "recognized. You should see something like (the lines do not necessarily have " "to be consecutive): \n" "Probing IDE interface ide1...\n" "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" "ide1 at 0x170-0x177,0x376 on irq 15\n" "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" "Uniform CD-ROM driver Revision: 3.20\n" " If you don't see something like that, chances " "are the controller your CD-ROM is connected to was not recognized or may be " "not supported at all. If you know what driver is needed for the controller, " "you can try loading it manually using modprobe." msgstr "" "Ellenőrizd a dmesg kimenetét, sikerült-e a CD-ROM " "meghajtó felismerése. Ilyesmit kell látnod benne (a sorok nem feltétlenül " "egymás utániak): \n" "Probing IDE interface ide1...\n" "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" "ide1 at 0x170-0x177,0x376 on irq 15\n" "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" "Uniform CD-ROM driver Revision: 3.20\n" " Ha nincs ilyesmi, lehet, hogy a vezérlő " "felismerése nem sikerült vagy egyáltalán nem támogatott. Ha tudod, milyen " "meghajtót igényel az adott, kézzel is betöltheted a modprobe paranccsal." #. Tag: para #: boot-installer.xml:3218 #, no-c-format msgid "" "Check that there is a device node for your CD-ROM drive under /dev/" ". In the example above, this would be /dev/hdc. There should also be a /dev/cdrom." msgstr "" "Ellenőrizd, van-e megfelelő eszköz-leíró fájl a CD-ROM meghajtóhoz a " "/dev/ könyvtárban. A fenti példában ez a /dev/" "hdc. Lehet ez is: /dev/cdrom." #. Tag: para #: boot-installer.xml:3226 #, no-c-format msgid "" "Use the mount command to check if the CD-ROM is already " "mounted; if not, try mounting it manually: \n" "$ mount /dev/hdc /cdrom\n" " Check if there are any error messages after that " "command." msgstr "" "Használd a mount parancsot a CD-ROM csatolt voltának " "ellenőrzésére; ha nincs, próbáld kézzel csatolni: \n" "$ mount /dev/hdc /cdrom\n" " Ellenőrizd, ír-e hibát." #. Tag: para #: boot-installer.xml:3236 #, no-c-format msgid "" "Check if DMA is currently enabled: \n" "$ cd /proc/ide/hdc\n" "$ grep using_dma settings\n" "using_dma 1 0 1 rw\n" " A 1 in the first column after " "using_dma means it is enabled. If it is, try disabling " "it: \n" "$ echo -n \"using_dma:0\" >settings\n" " Make sure that you are in the directory for the " "device that corresponds to your CD-ROM drive." msgstr "" "Ellenőrizd a DMA állapotát: \n" "$ cd /proc/ide/hdc\n" "$ grep dma settings\n" "using_dma 1 0 1 rw\n" " Az 1 az 1. oszlopban a " "using_dma után azt jelenti: bekapcsolva. Ha így van, " "próbáld kikapcsolni: \n" "$ echo -n \"using_dma:0\" >settings\n" " Győződj meg, hogy a CD-ROM meghajtónak megfelelő " "könyvtárban vagy." #. Tag: para #: boot-installer.xml:3251 #, no-c-format msgid "" "If there are any problems during the installation, try checking the " "integrity of the CD-ROM using the option near the bottom of the installer's " "main menu. This option can also be used as a general test if the CD-ROM can " "be read reliably." msgstr "" "Ha gond támad a telepítés alatt, próbáld ki a CD-ROM épségének ellenőrzését " "a telepítő fő-menü vége felé található lehetőséggel. E lehetőség a CD-ROM " "eszközről való olvasás megbízhatóságának általános ellenőrzésére is " "használható." #. Tag: title #: boot-installer.xml:3266 #, no-c-format msgid "Floppy Disk Reliability" msgstr "Flopi lemezek megbízhatósága" #. Tag: para #: boot-installer.xml:3268 #, no-c-format msgid "" "The biggest problem for people using floppy disks to install &debian; seems " "to be floppy disk reliability." msgstr "" "A &debian; rendszert flopiról telepítők számára a legnagyobb gond a flopi " "megbízhatatlansága." #. Tag: para #: boot-installer.xml:3273 #, no-c-format msgid "" "The boot floppy is the floppy with the worst problems, because it is read by " "the hardware directly, before Linux boots. Often, the hardware doesn't read " "as reliably as the Linux floppy disk driver, and may just stop without " "printing an error message if it reads incorrect data. There can also be " "failures in the driver floppies, most of which indicate themselves with a " "flood of messages about disk I/O errors." msgstr "" "Az indító flopival van a legtöbb gond, mert azt a gép közvetlenül olvassa a " "Linux indítása előtt. Ez pedig általában nem olvassa olyan megbízhatóan, " "mint a Linux flopi meghajtó és még üzenet nélkül is leállhat hibás adatok " "olvasásakor. Nagyon rossz az is, mikor a meghajtó flopikkal van gond, melyek " "ezt tömeges lemez I/O hiba üzenettel jelzik." #. Tag: para #: boot-installer.xml:3282 #, no-c-format msgid "" "If you are having the installation stall at a particular floppy, the first " "thing you should do is write the image to a different " "floppy and see if that solves the problem. Simply reformatting the old " "floppy may not be sufficient, even if it appears that the floppy was " "reformatted and written with no errors. It is sometimes useful to try " "writing the floppy on a different system." msgstr "" "Ha a telepítés elakad egy flopinál, legelőször írd a képet egy " "másik flopira, és nézd meg, ez megoldja-e a gondot. A " "régi flopi újraformázása általában akkor sem elég, ha nem írt hibát. Sok " "esetben csak az oldja meg, ha egy másik gépen írod meg." #. Tag: para #: boot-installer.xml:3291 #, no-c-format msgid "" "One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the " "third floppy." msgstr "" "Többször előfordult, hogy egy felhasználó három " "teljesen új flopit használt fel, mire az egyik végre hibátlan volt és " "sikeresen telepített." #. Tag: para #: boot-installer.xml:3297 #, no-c-format msgid "" "Normally you should not have to download a floppy image again, but if you " "are experiencing problems it is always useful to verify that the images were " "downloaded correctly by verifying their md5sums." msgstr "" "Általában nem kell újra letöltened a flopi képet, de ha gondokat észlelsz, " "mindig hasznos ellenőrizni a képek helyesen letöltött voltát md5-összegük " "ellenőrzésével." #. Tag: para #: boot-installer.xml:3303 #, no-c-format msgid "" "Other users have reported that simply rebooting a few times with the same " "floppy in the floppy drive can lead to a successful boot. This is all due to " "buggy hardware or firmware floppy drivers." msgstr "" "Sokak gépe pedig csak többszöri indítás után tudta pontosan elolvasni a " "flopit és így ez csak ekkor tudott sikeresen elindulni. Ezt mind hibás " "hardver vagy firmware flopi meghajtók okozzák." #. Tag: title #: boot-installer.xml:3312 #, no-c-format msgid "Boot Configuration" msgstr "Indító beállítás" #. Tag: para #: boot-installer.xml:3314 #, no-c-format msgid "" "If you have problems and the kernel hangs during the boot process, doesn't " "recognize peripherals you actually have, or drives are not recognized " "properly, the first thing to check is the boot parameters, as discussed in " "." msgstr "" "Ha a kernel megáll az indító folyamat során, nem ismer fel perifériákat vagy " "meghajtókat helyesen, először az indító paramétereket kell ellenőrizni a " "korábbi szerint." #. Tag: para #: boot-installer.xml:3323 #, no-c-format msgid "" "In some cases, malfunctions can be caused by missing device firmware (see " " and )." msgstr "" #. Tag: para #: boot-installer.xml:3334 #, no-c-format msgid "" "If software speech synthesis does not work, there is most probably an issue " "with your sound board, usually because either the driver for it is not " "included in the installer, or because it has unusual mixer level names which " "are set to muted by default. You should thus submit a bug report which " "includes the output of the following commands, run on the same machine from " "a Linux system which is known to have sound working (e.g., a live CD)." msgstr "" #. Tag: userinput #: boot-installer.xml:3345 #, no-c-format msgid "dmesg" msgstr "" #. Tag: userinput #: boot-installer.xml:3347 #, no-c-format msgid "lspci" msgstr "" #. Tag: userinput #: boot-installer.xml:3349 #, no-c-format msgid "lsmod" msgstr "" #. Tag: userinput #: boot-installer.xml:3351 #, no-c-format msgid "amixer" msgstr "" #. Tag: title #: boot-installer.xml:3359 boot-installer.xml:3470 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "Gyakori &arch-title; telepítő gondok" #. Tag: para #: boot-installer.xml:3360 #, no-c-format msgid "" "There are some common installation problems that can be solved or avoided by " "passing certain boot parameters to the installer." msgstr "" "Van pár gyakori telepítő gond, mely megoldható vagy elkerülhető egyes indító " "paraméterek átadásával a telepítőnek." #. Tag: para #: boot-installer.xml:3411 #, fuzzy, no-c-format #| msgid "" #| "If your screen begins to show a weird picture while the kernel boots, eg. " #| "pure white, pure black or colored pixel garbage, your system may contain " #| "a problematic video card which does not switch to the framebuffer mode " #| "properly. Then you can use the boot parameter fb=false " #| "video=vga16:off to disable the framebuffer console. Only a " #| "reduced set of languages will be available during the installation due to " #| "limited console features. See for details." msgid "" "If your screen begins to show a weird picture while the kernel boots, eg. " "pure white, pure black or colored pixel garbage, your system may contain a " "problematic video card which does not switch to the framebuffer mode " "properly. Then you can use the boot parameter fb=false to disable the framebuffer console. Only a reduced set of " "languages will be available during the installation due to limited console " "features. See for details." msgstr "" "Ha a képernyő fura képet ad a kernel indításakor, például tiszta fehér, " "tiszta fekete vagy színes kavar, a rendszer problematikus videó kártyát " "tartalmazhat, mely hibásan vált framebuffer módra. Ekkor használható az " "fb=false video=vga16:off indító paraméter ennek " "kikapcsolására. Ekkor kevesebb nyelv érhető el a telepítés alatt a konzol " "korlátozott képességei miatt. Lásd ezt: a " "részletekért." #. Tag: title #: boot-installer.xml:3425 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "A rendszer fagyása a PCMCIA beállító szakaszban" #. Tag: para #: boot-installer.xml:3426 #, fuzzy, no-c-format #| msgid "" #| "Some laptop models produced by Dell are known to crash when PCMCIA device " #| "detection tries to access some hardware addresses. Other laptops may " #| "display similar problems. If you experience such a problem and you don't " #| "need PCMCIA support during the installation, you can disable PCMCIA using " #| "the hw-detect/start_pcmcia=false boot parameter. " #| "You can then configure PCMCIA after the installation is completed and " #| "exclude the resource range causing the problems." msgid "" "Some very old laptop models produced by Dell are known to crash when PCMCIA " "device detection tries to access some hardware addresses. Other laptops may " "display similar problems. If you experience such a problem and you don't " "need PCMCIA support during the installation, you can disable PCMCIA using " "the hw-detect/start_pcmcia=false boot parameter. You " "can then configure PCMCIA after the installation is completed and exclude " "the resource range causing the problems." msgstr "" "Egyes Dell laptopok összeomlanak, mikor a PCMCIA eszköz-érzékelő megpróbál " "elérni egyes hardver-címeket. Pár más laptop is hasonló. Ha ilyen gondot " "tapasztalsz és nincs szükséged PCMCIA támogatásra a telepítéskor, kapcsold " "ki a hw-detect/start_pcmcia=false indító " "paraméterrel. A telepítés után beállíthatod és kizárhatod a gondot adó " "erőforrás-tartományokat." #. Tag: para #: boot-installer.xml:3436 #, no-c-format msgid "" "Alternatively, you can boot the installer in expert mode. You will then be " "asked to enter the resource range options your hardware needs. For example, " "if you have one of the Dell laptops mentioned above, you should enter " "exclude port 0x800-0x8ff here. There is also a list " "of some common resource range options in the System resource " "settings section of the PCMCIA HOWTO. Note that you have to omit the " "commas, if any, when you enter this value in the installer." msgstr "" "A telepítő szakértő módban is indítható. Ekkor lehetőség nyílik a hardver " "igényeinek megfelelő erőforrás-tartományok bevitelére. Például a fenti Dell " "laptopokon megadható ez: exclude port 0x800-0x8ff. " "Van egy lista is néhány általános erőforrás-tartomány lehetőségről itt: " "PCMCIA HOGYAN rendszer erőforrás-beállítások szakasz. " "A vesszőket el kell hagyni, ha vannak, mikor beírod ezt az értéket a " "telepítőben." #. Tag: para #: boot-installer.xml:3471 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "Van pár fel-felbukkanó telepítő gond, melyet érdemes megemlíteni." #. Tag: title #: boot-installer.xml:3477 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para #: boot-installer.xml:3478 #, no-c-format msgid "" "It is fairly common for &arch-title; to have two video cards in one machine, " "for example an ATI card and a Sun Creator 3D. In some cases, this may result " "in the video output getting misdirected soon after the system boots. In " "typical cases, the display will only show: \n" "Remapping the kernel... done\n" "Booting Linux...\n" " To work around this, you can either pull out one " "of the video cards, or disable the one not used during the OpenProm boot " "phase using a kernel parameter. For example, to disable an ATI card, you " "should boot the installer with video=atyfb:off." msgstr "" #. Tag: para #: boot-installer.xml:3492 #, no-c-format msgid "" "Note that you may also have to manually add this parameter to the silo " "configuration (edit /target/etc/silo.conf before " "rebooting) and, if you installed X11, modify the video driver in /" "etc/X11/xorg.conf." msgstr "" "Add e paramétert a silo beállításhoz (szerkeszd a /target/etc/silo." "conf fájlt újraindítás előtt) és X11 esetén módosítsd a videó " "meghajtót a /etc/X11/xorg.conf fájlban." #. Tag: title #: boot-installer.xml:3503 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "Hibás indítás vagy telepítés CD-ROM lemezről" #. Tag: para #: boot-installer.xml:3504 #, no-c-format msgid "" "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if " "they do boot, there may be inexplicable failures during the installation. " "Most problems have been reported with SunBlade systems." msgstr "" "Bizonyos Sparc rendszerekkel állandó CD-ROM indítás gondok vannak, és ha " "indulnak is, hibákat adnak a telepítéskor. A legtöbb gond a SunBlade " "rendszereknél fordult elő." #. Tag: para #: boot-installer.xml:3510 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "Az ilyen rendszerekhez hálózati telepítést ajánlunk." #. Tag: title #: boot-installer.xml:3519 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "A kernel indító üzenetek értelmezése" #. Tag: para #: boot-installer.xml:3521 #, no-c-format msgid "" "During the boot sequence, you may see many messages in the form " "can't find something, or something not " "present, can't initialize " "something, or even " "this driver release depends on something. Most of these messages are harmless. You see " "them because the kernel for the installation system is built to run on " "computers with many different peripheral devices. Obviously, no one computer " "will have every possible peripheral device, so the operating system may emit " "a few complaints while it looks for peripherals you don't own. You may also " "see the system pause for a while. This happens when it is waiting for a " "device to respond, and that device is not present on your system. If you " "find the time it takes to boot the system unacceptably long, you can create " "a custom kernel later (see )." msgstr "" "Az indítás alatt, sok ilyen üzenetet láthatsz: can't find " "valami, vagy " "valami not present, " "can't initialize valami, vagy akár this driver release depends on " "valami. A legtöbb ilyen nem " "számít. Azért látod, mert a telepítőben lévő kernel úgy készült, hogy a " "legkülönbözőbb eszközöket támogassa. Persze egy gépen sincs az összes " "lehetséges eszköz, és az operációs rendszer jelezheti, ha olyat keres, ami " "nem található. Néha azt is láthatod, hogy a rendszer egy picit megáll. Ez " "akkor történik, ha vár egy eszköz válaszára, az adott rendszer pedig nem " "tartalmaz olyat. Ha ezt túl hosszúnak találod, később egyéni kernelt is " "készíthetsz (lásd a részt)." #. Tag: title #: boot-installer.xml:3546 #, no-c-format msgid "Reporting Installation Problems" msgstr "Telepítő gondok jelentése" #. Tag: para #: boot-installer.xml:3547 #, no-c-format msgid "" "If you get through the initial boot phase but cannot complete the install, " "the menu option Save debug logs may be helpful. " "It lets you store system error logs and configuration information from the " "installer to a floppy, or download them using a web browser. This " "information may provide clues as to what went wrong and how to fix it. If " "you are submitting a bug report, you may want to attach this information to " "the bug report." msgstr "" "Ha túljutottál a kezdő indító szakaszon, de nem futott le teljesen végig a " "telepítés, a Hibanaplók mentése menüpont " "segíthet. Eltárolhatod a rendszer hiba naplóit és beállításait a telepítőből " "egy flopira, vagy letöltheted egy böngészőben. Ezek megadják a felmerült " "hibákat és javításukat. Ha jelentést küldesz, csatolhatod hozzá ezeket." #. Tag: para #: boot-installer.xml:3558 #, no-c-format msgid "" "Other pertinent installation messages may be found in /var/log/ during the installation, and /var/log/installer/ after the computer has been booted into the installed system." msgstr "" "További telepítő üzenetek találhatók a /var/log/ " "könyvtárban a telepítés során és a /var/log/installer/ " "könyvtárban, miután a gép a telepített rendszert elindította." #. Tag: title #: boot-installer.xml:3569 #, no-c-format msgid "Submitting Installation Reports" msgstr "Telepítő jelentések küldése" #. Tag: para #: boot-installer.xml:3570 #, no-c-format msgid "" "If you still have problems, please submit an installation report. We also " "encourage installation reports to be sent even if the installation is " "successful, so that we can get as much information as possible on the " "largest number of hardware configurations." msgstr "" "Ha még mindig gondjaid vannak, kérjük, küldj telepítő jelentést. Siker " "esetén is kérünk erre, mert így a lehető legtöbb adatot kapjuk a legtöbb " "hardver összeállításról." #. Tag: para #: boot-installer.xml:3577 #, no-c-format msgid "" "Note that your installation report will be published in the Debian Bug " "Tracking System (BTS) and forwarded to a public mailing list. Make sure that " "you use an e-mail address that you do not mind being made public." msgstr "" "A telepítő jelentés közzé kerül a Debian hibajelentő rendszerben (BTS) és " "nyilvános listára kerül. Gondold át, melyik email címedet használod." #. Tag: para #: boot-installer.xml:3583 #, fuzzy, no-c-format #| msgid "" #| "If you have a working &debian; system, the easiest way to send an " #| "installation report is to install the installation-report and reportbug packages " #| "(aptitude install installation-report reportbug), " #| "configure reportbug as explained in , and run the command reportbug installation-" #| "reports." msgid "" "If you have a working &debian; system, the easiest way to send an " "installation report is to install the installation-report and reportbug packages (apt " "install installation-report reportbug), configure " "reportbug as explained in , and run the command reportbug installation-reports." msgstr "" "Működő &debian; rendszerből a telepítő jelentés küldésének legkönnyebb módja " "az installation-report és reportbug csomag telepítése (aptitude install installation-report " "reportbug), állítsd be a reportbug csomagot " "a résznek megfelelően és futtasd a " "reportbug installation-reports parancsot." #. Tag: para #: boot-installer.xml:3593 #, fuzzy, no-c-format #| msgid "" #| "Alternatively you can use this template when filling out installation " #| "reports, and file the report as a bug report against the " #| "installation-reports pseudo package, by sending it " #| "to submit@bugs.debian.org. \n" #| "Package: installation-reports\n" #| "\n" #| "Boot method: <How did you boot the installer? CD? floppy? network?" #| ">\n" #| "Image version: <Full URL to image you downloaded is best>\n" #| "Date: <Date and time of the install>\n" #| "\n" #| "Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" #| "Processor:\n" #| "Memory:\n" #| "Partitions: <df -Tl will do; the raw partition table is preferred>\n" #| "\n" #| "Output of lspci -nn and lspci -vnn:\n" #| "\n" #| "Base System Installation Checklist:\n" #| "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" #| "\n" #| "Initial boot: [ ]\n" #| "Detect network card: [ ]\n" #| "Configure network: [ ]\n" #| "Detect CD: [ ]\n" #| "Load installer modules: [ ]\n" #| "Detect hard drives: [ ]\n" #| "Partition hard drives: [ ]\n" #| "Install base system: [ ]\n" #| "Clock/timezone setup: [ ]\n" #| "User/password setup: [ ]\n" #| "Install tasks: [ ]\n" #| "Install boot loader: [ ]\n" #| "Overall install: [ ]\n" #| "\n" #| "Comments/Problems:\n" #| "\n" #| "<Description of the install, in prose, and any thoughts, comments\n" #| " and ideas you had during the initial install.>\n" #| " In the bug report, describe what the problem " #| "is, including the last visible kernel messages in the event of a kernel " #| "hang. Describe the steps that you did which brought the system into the " #| "problem state." msgid "" "Alternatively you can use this template when filling out installation " "reports, and file the report as a bug report against the " "installation-reports pseudo package, by sending it to " "submit@bugs.debian.org. \n" "Package: installation-reports\n" "\n" "Boot method: <How did you boot the installer? CD? floppy? network?>\n" "Image version: <Full URL to image you downloaded is best>\n" "Date: <Date and time of the install>\n" "\n" "Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" "Processor:\n" "Memory:\n" "Partitions: <df -Tl will do; the raw partition table is preferred>\n" "\n" "Output of lspci -knn (or lspci -nn):\n" "\n" "Base System Installation Checklist:\n" "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" "\n" "Initial boot: [ ]\n" "Detect network card: [ ]\n" "Configure network: [ ]\n" "Detect CD: [ ]\n" "Load installer modules: [ ]\n" "Detect hard drives: [ ]\n" "Partition hard drives: [ ]\n" "Install base system: [ ]\n" "Clock/timezone setup: [ ]\n" "User/password setup: [ ]\n" "Install tasks: [ ]\n" "Install boot loader: [ ]\n" "Overall install: [ ]\n" "\n" "Comments/Problems:\n" "\n" "<Description of the install, in prose, and any thoughts, comments\n" " and ideas you had during the initial install.>\n" " In the bug report, describe what the problem is, " "including the last visible kernel messages in the event of a kernel hang. " "Describe the steps that you did which brought the system into the problem " "state." msgstr "" "Vagy pedig használhatod e sablont a telepítő jelentés kitöltésére és " "elküldésére hibajegyként az installation-reports ál- " "csomagra a submit@bugs.debian.org címre küldve angolul. " "\n" "Package: installation-reports\n" "\n" "Boot method: <Mi volt az indító médium? CD? flopi? hálózat?>\n" "Image version: <A letöltött kép teljes URL-e a legjobb>\n" "Date: <Telepítés időpontja>\n" "\n" "Machine: <Gép leírása (például IBM Thinkpad R32)>\n" "Processor:\n" "Memory:\n" "Partitions: <a df -Tl kiírja; a sima partíciós tábla ajánlott>\n" "\n" "Az lspci -nn és lspci -vnn kimenete:\n" "\n" "Az alaprendszer telepítésekor:\n" "[O] = OK, [E] = Hiba (a végén írd le), [ ] = nem próbált\n" "\n" "Initial boot: [ ]\n" "Detect network card: [ ]\n" "Configure network: [ ]\n" "Detect CD: [ ]\n" "Load installer modules: [ ]\n" "Detect hard drives: [ ]\n" "Partition hard drives: [ ]\n" "Install base system: [ ]\n" "Clock/timezone setup: [ ]\n" "User/password setup: [ ]\n" "Install tasks: [ ]\n" "Install boot loader: [ ]\n" "Overall install: [ ]\n" "\n" "Comments/Problems:\n" "\n" "<Telepítés leírása prózaian és bármilyen gondolat, megjegyzés\n" " és ötlet a kezdeti telepítés során.>\n" " A jelentésben írd le az esetleges hibát, ha a " "kernel leállna, annak utolsó látható üzeneteit is. Írd le, mely lépések " "okozták a gondot." #, fuzzy #~| msgid "" #~| "When the installer boots, you should be presented with a friendly " #~| "graphical screen showing the Debian logo and the boot prompt: " #~| "\n" #~| "Press F1 for help, or ENTER to boot:\n" #~| " At the boot prompt you can either just press " #~| "&enterkey; to boot the installer with default options or enter a " #~| "specific boot method and, optionally, boot parameters." #~ msgid "" #~ "When the installer boots, you should be presented with a friendly " #~ "graphical screen showing the &debian; logo and a menu: " #~ "\n" #~ "Installer boot menu\n" #~ "\n" #~ "Install\n" #~ "Graphical install\n" #~ "Advanced options >\n" #~ "Help\n" #~ "Install with speech synthesis\n" #~ "\n" #~ "Press ENTER to boot or TAB to edit a menu entry\n" #~ " Depending on the installation method you are " #~ "using, the Graphical install option may not be available. " #~ "Bi-arch images additionally have a 64 bit variant for each install " #~ "option, right below it, thus almost doubling the number of options." #~ msgstr "" #~ "A telepítő indulásakor egy barátságos grafikus képernyőt látsz a &debian; " #~ "logóval és az indító jellel: \n" #~ "Press F1 for help, or ENTER to boot:\n" #~ " Az indító jelnél leütheted az &enterkey; " #~ "billentyűt a telepítő alap lehetőségeivel indításhoz vagy beírhatsz egy " #~ "adott indító módot és, tetszőlegesen, indító paramétereket." #~ msgid "Booting from CD-ROM" #~ msgstr "Indítás CD-ROM lemezről" #~ msgid "" #~ "There is an increasing number of consumer devices that directly boot from " #~ "a flash chip on the device. The installer can be written to flash so it " #~ "will automatically start when you reboot your machines." #~ msgstr "" #~ "Egyre több olyan fogyasztói termék van, amely közvetlenül az eszköz flash " #~ "csipjéről indul. A telepítő ide írható, így a készülék újraindítása után " #~ "automatikusan el fog indulni." #~ msgid "" #~ "In many cases, changing the firmware of an embedded device voids your " #~ "warranty. Sometimes you are also not able to recover your device if there " #~ "are problems during the flashing process. Therefore, please take care and " #~ "follow the steps precisely." #~ msgstr "" #~ "Gyakori, hogy egy beágyazott rendszerben lévő firmware megváltoztatása a " #~ "garancia elvesztésével jár. Előfordulhat, hogy nincs lehetőség az eszköz " #~ "helyreállítására, ha a flash írása során hiba lépett fel. Ezért légy " #~ "figyelmes és pontosan kövesd a leírást." #, fuzzy #~| msgid "Booting the NSLU2" #~ msgid "Booting the SS4000-E" #~ msgstr "Az NLSU2 indítása" #~ msgid "" #~ "When the kernel boots, a message \n" #~ "Memory:availk/totalk available\n" #~ " should be emitted early in the process. " #~ "total should match the total amount of RAM, in " #~ "kilobytes. If this doesn't match the actual amount of RAM you have " #~ "installed, you need to use the mem=ram parameter, where ram " #~ "is set to the amount of memory, suffixed with k for " #~ "kilobytes, or m for megabytes. For example, both " #~ "mem=65536k and mem=64m mean " #~ "64MB of RAM." #~ msgstr "" #~ "A kernel indulásakor egy \n" #~ "Memory:availk/totalk available\n" #~ " üzenet látható a folyamat elején. A " #~ "total a RAM teljes méretét adja kilobájtban. " #~ "Ha nem pontos, a mem=ram paraméter használandó, ahol a ram a " #~ "memória mérete, melyet k követ kilobájtokhoz, vagy " #~ "m megabájtokhoz. Például a mem=65536k és mem=64m jelentése egyaránt 64MB RAM." #~ msgid "" #~ "If your system boots correctly from the CD-ROM, it does not necessarily " #~ "mean that &arch-kernel; also supports the CD-ROM (or, more correctly, the " #~ "controller that your CD-ROM drive is connected to)." #~ msgstr "" #~ "Ha a rendszer elindul a CD-ROM eszközről, ez nem feltétlenül jelenti, " #~ "hogy a &arch-kernel; is támogatja azt (vagy, pontosabban a vezérlőt, " #~ "melyre a CD-ROM meghajtó kötve van)." #~ msgid "" #~ "Often, problems can be solved by removing add-ons and peripherals, and " #~ "then trying booting again. Internal modems, " #~ "sound cards, and Plug-n-Play devices can be especially problematic." #~ msgstr "" #~ "Bizonyos gondok gyakran megoldhatók kiegészítők és perifériák " #~ "eltávolításával és újraindítással. Egyes belső " #~ "modemek, hangkártyák és Plug-n-Play eszközök sok gondot adnak." #~ msgid "" #~ "If you have a large amount of memory installed in your machine, more than " #~ "512M, and the installer hangs when booting the kernel, you may need to " #~ "include a boot argument to limit the amount of memory the kernel sees, " #~ "such as mem=512m." #~ msgstr "" #~ "Ha több, mint 512M memória van a gépen és a telepítő megáll a kernel " #~ "indításakor, előfordulhat, hogy egy indító argumentumot kell megadni a " #~ "kernel által nézett memória korlátozására így: mem=512m." #~ msgid "" #~ "Some systems have floppies with inverted DCLs. If you " #~ "receive errors reading from the floppy, even when you know the floppy is " #~ "good, try the parameter floppy=thinkpad." #~ msgstr "" #~ "Egyes rendszereken fordított DCL flopik vannak. Ha hibákat " #~ "kapsz a flopiról olvasáskor, pedig tudod, hogy a flopi jó, próbáld a " #~ "floppy=thinkpad paramétert." #~ msgid "" #~ "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 " #~ "disk drivers), the IDE drive may not be properly recognized. Again, try " #~ "it first without the parameters and see if the IDE drive is recognized " #~ "properly. If not, determine your drive geometry (cylinders, heads, and " #~ "sectors), and use the parameter hd=cylinders,heads,sectors." #~ msgstr "" #~ "Egyes rendszereken, ilyen például az IBM PS/1 vagy ValuePoint (melyben " #~ "ST-506 lemez meghajtók vannak), az IDE meghajtó felismerése hibás lehet. " #~ "Előbb paraméterek nélkül próbáld, és nézd meg, az IDE meghajtó " #~ "felismerése helyes-e. Ha nem, ellenőrizd a meghajtó geometriáját " #~ "(cilinderek, fejek, szektorok) és használd a " #~ "hd=cilinderek,fejek,szektorok paramétert." #~ msgid "" #~ "If you have a very old machine, and the kernel hangs after saying " #~ "Checking 'hlt' instruction..., then you " #~ "should try the no-hlt boot argument, which " #~ "disables this test." #~ msgstr "" #~ "Nagyon régi gépnél, ha a kernel megáll itt: Checking " #~ "'hlt' instruction..., próbáld a no-hlt indító argumentumot, mely kikapcsolja ezt a tesztet." #~ msgid "System Freeze while Loading USB Modules" #~ msgstr "A rendszer fagyása az USB modulok betöltésekor" #, fuzzy #~ msgid "" #~ "The kernel normally tries to install USB modules and the USB keyboard " #~ "driver in order to support some non-standard USB keyboards. However, " #~ "there are some broken USB systems where the driver hangs on loading. A " #~ "possible workaround may be disabling the USB controller in your mainboard " #~ "BIOS setup. Another option is passing the nousb " #~ "parameter at the boot prompt." #~ msgstr "" #~ "A kernel alapban megpróbálja telepíteni az USB modulokat és az USB " #~ "billentyű meghajtót pár nem-szabványos USB billentyű támogatásához. De " #~ "van pár hibás USB rendszer, ahol a meghajtó lefagy betöltéskor. Ennek " #~ "egyik elkerülése az USB vezérlő kikapcsolása a BIOS beállításban. Egy " #~ "másik lehetőség a debian-installer/probe/usb=false " #~ "paraméter átadása az indító jelnél, mely meggátolja e modulok betöltését." #~ msgid "Booting the NSLU2" #~ msgstr "Az NLSU2 indítása" #~ msgid "There are three ways how to put the installer firmware into flash:" #~ msgstr "3 mód van a telepítő firmware flashbe töltéséhez:" #~ msgid "Using the NSLU2 web interface" #~ msgstr "Az NSLU2 webes felületének használatával" #~ msgid "" #~ "Go to the administration section and choose the menu item " #~ "Upgrade. You can then browse your disk for the " #~ "installer image you have previously downloaded. Then press the " #~ "Start Upgrade button, confirm, wait for a few minutes " #~ "and confirm again. The system will then boot straight into the installer." #~ msgstr "" #~ "Menj az adminisztrációs részhez és válaszd az Upgrade " #~ "menüpontot. Ezután keresd meg a lemezeden a letöltött telepítő képfájlt. " #~ "Majd nyomd meg a Start Upgrade gombot, hagyd jóvá, " #~ "várj néhány percet majd ismét hagyd jóvá. A rendszer egyből a telepítővel " #~ "indul majd." #~ msgid "Via the network using Linux/Unix" #~ msgstr "Hálózaton Linux/Unix használatával" #~ msgid "" #~ "You can use upslug2 from any Linux or Unix machine to " #~ "upgrade the machine via the network. This software is packaged for " #~ "&debian;. First, you have to put your NSLU2 in upgrade mode: " #~ " Disconnect any disks and/or devices from " #~ "the USB ports. Power off the NSLU2 Press and hold the reset button " #~ "(accessible through the small hole on the back just above the power " #~ "input). Press and release the power " #~ "button to power on the NSLU2. Wait " #~ "for 10 seconds watching the ready/status LED. After 10 seconds it will " #~ "change from amber to red. Immediately release the reset button. The NSLU2 ready/status LED will flash " #~ "alternately red/green (there is a 1 second delay before the first green). " #~ "The NSLU2 is now in upgrade mode. See " #~ "the NSLU2-Linux pages if you have problems with this. Once your " #~ "NSLU2 is in upgrade mode, you can flash the new image: " #~ "\n" #~ "sudo upslug2 -i di-nslu2.bin\n" #~ " Note that the tool also shows the MAC address " #~ "of your NSLU2, which may come in handy to configure your DHCP server. " #~ "After the whole image has been written and verified, the system will " #~ "automatically reboot. Make sure you connect your USB disk again now, " #~ "otherwise the installer won't be able to find it." #~ msgstr "" #~ "Bármely Linuxos vagy Unixos gépről használhatod az upslug2 parancsot a készülék hálózaton keresztüli frissítéséhez. Ez a " #~ "szoftver csomagként elérhető a &debian;. Először upgrade módba kell " #~ "helyezned az NSLU2-t: Távolíts el minden " #~ "lemezt és eszközt az USB portokról. " #~ "Kapcsold ki az NSLU2-t Nyomd meg és " #~ "tartsd benyomva a reset gombot (a hátlapon közvetlenül a tápcsatlakozó " #~ "felett található kis lyukon keresztül érhető el). " #~ " Az NSLU2 bekapcsolásához nyomd meg és engedd el a " #~ "bekapcsoló gombot. A ready/status LED-" #~ "et figyelve várj 10 másodpercet. 10 másodperc múlva sárgáról pirosra fog " #~ "váltani. Azonnal engedd el a reset gombot. " #~ " Az NSLU2 ready/status LED-je váltakozva piros és zöld " #~ "színnel fog világítani (az első zöld előtt van 1 másodperc késleltetés). " #~ "Az NSLU2 most már upgrade módban van. " #~ "Ha gondod van ezzel, nézd meg az NSLU2-Linux oldalakat. Mihelyt az " #~ "NSLU2 upgrade módban van, már írhatod is be az új képfjált a flashbe: " #~ "\n" #~ "sudo upslug2 -i di-nslu2.bin\n" #~ " Figyeld meg, hogy ez az eszköz az NSLU2 MAC " #~ "címét is megmutatja, ami még jól jöhet a DHCP szervered konfigurálásakor. " #~ "Miután a teljes képfájlt kiírása és ellenőrzése megtörtént a rendszer " #~ "automatikusan újra fog indulni. Ne felejtsd el most az USB-s lemezt " #~ "újracsatlakoztatni, különben a telepítő nem fogja megtalálni." #~ msgid "Via the network using Windows" #~ msgstr "Hálózaton Windowsos gépnél" #~ msgid "" #~ "There is a tool for Windows to upgrade " #~ "the firmware via the network." #~ msgstr "" #~ "Van egy eszköz Windowshoz a firmware " #~ "hálózati frissítéséhez." #, fuzzy #~| msgid "mouse/left" #~ msgid "mouse/device" #~ msgstr "mouse/left" #~ msgid "mouse/left" #~ msgstr "mouse/left" #~ msgid "" #~ "For the gtk frontend (graphical installer), users can switch the mouse to " #~ "left-handed operation by setting this parameter to true." #~ msgstr "" #~ "A gtk felülethez (grafikus telepítő) a felhasználók az egeret bal-kezesre " #~ "válthatják e paraméter true értékre állításával." #~ msgid "directfb/hw-accel" #~ msgstr "directfb/hw-accel" #, fuzzy #~ msgid "" #~ "For the gtk frontend (graphical installer), hardware acceleration in " #~ "directfb is disabled by default. Set this parameter to true to enable it." #~ msgstr "" #~ "A gtk felülethez (grafikus telepítő) a directfb hardveres gyorsítás " #~ "alapból kikapcsolt. Bekapcsolásához, legyen a paraméter true a telepítő indításakor." #~ msgid "" #~ "The video=vga16:off argument may also be used to " #~ "disable the kernel's use of the framebuffer. Such problems have been " #~ "reported on a Dell Inspiron with Mobile Radeon card." #~ msgstr "" #~ "A video=vga16:off argumentum szintén használható a " #~ "kernel framebuffer kikapcsolására. Ilyen gondok vannak a Dell Inspiron " #~ "gépeken Mobil Radeon kártya esetén." #~ msgid "" #~ "Can be used to set both the language and country for the installation. " #~ "This will only work if the locale is supported in Debian. For example, " #~ "use locale=de_CH to select German as language and " #~ "Switzerland as country." #~ msgstr "" #~ "A nyelv és ország beállítására használható. Minden Debian által " #~ "támogatott helyi beállításra működik. Például a locale=de_CH német nyelvet választ, országnak pedig Svájcot." #~ msgid "" #~ "SRM console, based on the Alpha Console Subsystem " #~ "specification, which provides an operating environment for OpenVMS, Tru64 " #~ "UNIX, and Linux operating systems." #~ msgstr "" #~ "Az Alpha konzol alrendszer specifikációra épülő SRM konzol egy OpenVMS, Tru64 UNIX és GNU/Linux operációs rendszerre való " #~ "kezelő-környezetet ad." #~ msgid "" #~ "ARC, AlphaBIOS, or ARCSBIOS console, based on the " #~ "Advanced RISC Computing (ARC) specification, which provides an operating " #~ "environment for Windows NT." #~ msgstr "" #~ "Az Advanced RISC Computing (ARC) specifikációra épülő ARC, " #~ "AlphaBIOS és ARCSBIOS konzol egy Windows NT-hez készült kezelő-" #~ "környezetet ad." #~ msgid "" #~ "The following table summarizes available and supported system type/" #~ "console combinations (see for the system " #~ "type names). The word ARC below denotes any of the ARC-" #~ "compliant consoles." #~ msgstr "" #~ "Az alábbi tábla összefoglalja az elérhető és támogatott rendszer-típus/" #~ "konzol párokat (lásd az oldalt a rendszer-" #~ "típus nevekért). Az ARC szó bármely ARC-kompatibilis " #~ "konzolt jelöli." #~ msgid "System Type" #~ msgstr "Rendszer típus" #~ msgid "Console Type Supported" #~ msgstr "Támogatott konzol típus" #~ msgid "alcor" #~ msgstr "alcor" #~ msgid "ARC or SRM" #~ msgstr "ARC vagy SRM" #~ msgid "avanti" #~ msgstr "avanti" #~ msgid "book1" #~ msgstr "book1" #~ msgid "SRM only" #~ msgstr "csak SRM" #~ msgid "cabriolet" #~ msgstr "cabriolet" #~ msgid "dp264" #~ msgstr "dp264" #~ msgid "eb164" #~ msgstr "eb164" #~ msgid "eb64p" #~ msgstr "eb64p" #~ msgid "eb66" #~ msgstr "eb66" #~ msgid "eb66p" #~ msgstr "eb66p" #~ msgid "jensen" #~ msgstr "jensen" #~ msgid "lx164" #~ msgstr "lx164" #~ msgid "miata" #~ msgstr "miata" #~ msgid "mikasa" #~ msgstr "mikasa" #~ msgid "mikasa-p" #~ msgstr "mikasa-p" #~ msgid "nautilus" #~ msgstr "nautilus" #~ msgid "ARC (see motherboard manual) or SRM" #~ msgstr "ARC (lásd az alaplap kézikönyvet) vagy SRM" #~ msgid "noname" #~ msgstr "névtelen" #~ msgid "noritake" #~ msgstr "noritake" #~ msgid "noritake-p" #~ msgstr "noritake-p" #~ msgid "pc164" #~ msgstr "pc164" #~ msgid "rawhide" #~ msgstr "rawhide" #~ msgid "ruffian" #~ msgstr "ruffian" #~ msgid "ARC only" #~ msgstr "csak ARC" #~ msgid "sable" #~ msgstr "sable" #~ msgid "sable-g" #~ msgstr "sable-g" #~ msgid "sx164" #~ msgstr "sx164" #~ msgid "takara" #~ msgstr "takara" #~ msgid "xl" #~ msgstr "xl" #~ msgid "xlt" #~ msgstr "xlt" #~ msgid "" #~ "Generally, none of these consoles can boot Linux directly, so the " #~ "assistance of an intermediary bootloader is required. For the SRM " #~ "console, aboot, a small, platform-independent " #~ "bootloader, is used. See the (unfortunately outdated) SRM HOWTO for more information on aboot." #~ msgstr "" #~ "Általában e konzolok nem indítanak Linuxot, így egy köztes boot betöltő " #~ "szükséges. Az SRM konzolokhoz az aboot, egy kis, " #~ "platform-független boot-betöltő használatos. Lásd az (immár sajnos " #~ "elavult) SRM HOGYAN " #~ "aboot leírást." #~ msgid "" #~ "The following paragraphs are from the woody install manual, and are " #~ "included here for reference; they may be useful to someone at a later " #~ "date when Debian supports MILO-based installs again." #~ msgstr "" #~ "Az alábbi bekezdések a woody telepítő kézikönyvből valók, melyre itt " #~ "hivatkozunk; hasznosak lesznek később, mikor a Debian ismét támogatja a " #~ "MILO-alapú telepítést." #~ msgid "" #~ "Generally, none of these consoles can boot Linux directly, so the " #~ "assistance of an intermediary bootloader is required. There are two " #~ "mainstream Linux loaders: MILO and aboot." #~ msgstr "" #~ "Általában e konzolok nem indítanak Linuxot, így egy köztes boot betöltő " #~ "szükséges. 2 népszerű van: a MILO és az " #~ "aboot." #~ msgid "" #~ "MILO is itself a console, which replaces ARC or SRM in " #~ "memory. MILO can be booted from both ARC and SRM and " #~ "is the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO is " #~ "needed for each system type) and exist only for those systems, for which " #~ "ARC support is shown in the table above. See also the (unfortunately " #~ "outdated) MILO HOWTO." #~ msgstr "" #~ "A MILO maga egy konzol, mely az ARC vagy SRM helyére " #~ "kerül a memóriában. A MILO ARC és SRM alól is " #~ "indítható és ARC konzolról csak ezzel indítható a Linux. A MILO platform-függő (külön MILO kell minden " #~ "rebdszer-típushoz) és csak a fenti táblában ARC-támogatást mutató " #~ "rendszerekhez van. Lásd a (sajnos elavult) MILO HOGYAN-t is." #~ msgid "" #~ "aboot is a small, platform-independent bootloader, " #~ "which runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on " #~ "aboot." #~ msgstr "" #~ "Az aboot egy kis, platform-független boot betöltő, " #~ "mely csak SRM alól fut. Lásd az (immár sajnos elavult) SRM HOGYAN aboot leírást." #~ msgid "" #~ "In SRM, Ethernet interfaces are named with the ewa " #~ "prefix, and will be listed in the output of the show dev command, like this (edited slightly): " #~ "\n" #~ ">>> show dev\n" #~ "ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65\n" #~ "ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54\n" #~ "ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0\n" #~ " You first need to set the boot protocol: " #~ "\n" #~ ">>> set ewa0_protocols bootp\n" #~ " Then check the medium type is correct: " #~ "\n" #~ ">>> set ewa0_mode mode\n" #~ " You can get a listing of valid modes with " #~ ">>>set ewa0_mode." #~ msgstr "" #~ "SRM esetén az Ethernet csatolók ewa előtagot " #~ "kapnak és a show dev parancs kiírja őket így " #~ "(kissé szerkesztve):\n" #~ ">>> show dev\n" #~ "ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65\n" #~ "ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54\n" #~ "ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0\n" #~ " Először be kell állítani az indító " #~ "protokollt: \n" #~ ">>> set ewa0_protocols bootp\n" #~ " Majd ellenőrizni a médium típust:" #~ "\n" #~ ">>> set ewa0_mode mód\n" #~ " Az érvényes módok így írhatók ki: " #~ ">>>set ewa0_mode." #~ msgid "" #~ "Then, to boot from the first Ethernet interface, you would type: " #~ "\n" #~ ">>> boot ewa0 -flags \"\"\n" #~ " This will boot using the default kernel " #~ "parameters as included in the netboot image." #~ msgstr "" #~ "Majd az 1. Ethernet csatolóról való indításhoz ezt kell beírni: " #~ "\n" #~ ">>> boot ewa0 -flags \"\"\n" #~ " Ez netboot képben lévő alap kernel " #~ "paraméterekkel indít." #~ msgid "" #~ "If you wish to use a serial console, you must pass " #~ "the console= parameter to the kernel. This can be " #~ "done using the -flags argument to the SRM " #~ "boot command. The serial ports are named the same " #~ "as their corresponding files in /dev. Also, when " #~ "specifying additional kernel parameters, you must repeat certain default " #~ "options that are needed by the &d-i; images. For example, to boot from " #~ "ewa0 and use a console on the first serial port, " #~ "you would type:" #~ msgstr "" #~ "Soros konzol esetén át kell adni a " #~ "console= paramétert a kernelnek. Ez az SRM " #~ "boot parancsnak adott -flags argumentummal tehető. A soros portok a /dev könyvtárban lévő megfelelő fájlokkal nevezhetők. További " #~ "kernel paraméterek megadásakor meg kell ismételni egyes alapértelmezett " #~ "opciókat, melyek kellenek a &d-i; képekhez. Például az ewa0 eszközről indításhoz az 1. soros port használatakor ezt kell " #~ "beírni:" #~ msgid "" #~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " #~ "console=ttyS0"" #~ msgstr "" #~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " #~ "console=ttyS0"" #~ msgid "Booting from CD-ROM with the SRM Console" #~ msgstr "Indítás CD-ROM lemezről az SRM konzollal" #~ msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" #~ msgstr "Indítás CD-ROM lemezről az ARC vagy AlphaBIOS konzollal" #~ msgid "" #~ "To boot a CD-ROM from the ARC console, find your sub-architecture code " #~ "name (see ), then enter \\milo" #~ "\\linload.exe as the boot loader and \\milo" #~ "\\subarch (where " #~ "subarch is the proper subarchitecture name) as " #~ "the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: " #~ "You need to use \\milo\\ldmilo.exe as boot loader." #~ msgstr "" #~ "Egy CD-ROM indításakor az ARC konzolról, keresd meg az al-architektúra " #~ "kód nevet (lásd az leírást), majd add meg " #~ "a \\milo\\linload.exe fájlt mint boot betöltő és a " #~ "\\milo\\subarch fájlt " #~ "(ahol a subarch a helyes al-architektúra név) " #~ "mint OS útvonal az `OS Selection Setup' menüben. A Ruffian kivétel: a " #~ "\\milo\\ldmilo.exe fájl kell mint boot betöltő." #~ msgid "Booting from Floppies with the SRM Console" #~ msgstr "Indítás flopiról az SRM konzollal" #~ msgid "" #~ "At the SRM prompt (>>>), issue the following " #~ "command: \n" #~ ">>> boot dva0 -flags 0\n" #~ " possibly replacing dva0 " #~ "with the actual device name. Usually, dva0 is the " #~ "floppy; type \n" #~ ">>> show dev\n" #~ " to see the list of devices (e.g., if you want " #~ "to boot from a CD). Note that if you are booting via MILO, -" #~ "flags argument is ignored, so you can just type boot " #~ "dva0. If everything works OK, you will eventually see the Linux " #~ "kernel boot." #~ msgstr "" #~ "Az SRM jelnél (>>>) add ki az alábbi parancsot: " #~ "\n" #~ ">>> boot dva0 -flags 0\n" #~ " ha kell cserélve a dva0-" #~ "t az aktuális eszköz nevével. Általában a dva0 a " #~ "flopi; a \n" #~ ">>> show dev\n" #~ " sorolja fel az eszközöket (például ha CD-" #~ "lemezről akarsz indítani). A MILO általi indításkor a -flags argumentum nem számít, csak a boot dva0 " #~ "parancs kell. Ha minden jól működik, a Linux kernel azonnal elindul." #~ msgid "" #~ "If you want to specify kernel parameters when booting via aboot, use the following command: \n" #~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " #~ "load_ramdisk=1 arguments\"\n" #~ " (typed on one line), substituting, if " #~ "necessary, the actual SRM boot device name for dva0, " #~ "the Linux boot device name for fd0, and the desired " #~ "kernel parameters for arguments." #~ msgstr "" #~ "Ha kernel paramétereket akarsz megadni az aboot " #~ "indításkor, használd az alábbi parancsot:\n" #~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " #~ "load_ramdisk=1 arguments\"\n" #~ " (egy sorban), cseréld, ha kell, a " #~ "dva0 aktuális SRM indító eszköz nevet, az " #~ "fd0 Linux indító eszköz nevet és az " #~ "arguments kívánt kernel paramétereket." #~ msgid "" #~ "If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. " #~ "See ." #~ msgstr "" #~ "Ha kernel paramétereket akarsz megadni az MILO " #~ "indításkor, a MILO betöltőbe lépve egyszer meg kell szakítanod az " #~ "indítást. Lásd a leírást." #~ msgid "Booting from Floppies with the ARC or AlphaBIOS Console" #~ msgstr "Indítás flopiról az ARC vagy AlphaBIOS konzollal" #~ msgid "" #~ "In the OS Selection menu, set linload.exe as the boot " #~ "loader, and milo as the OS Path. Bootstrap using the " #~ "newly created entry." #~ msgstr "" #~ "Az OS Választás menüben állítsd be a linload.exe fájlt " #~ "boot betöltőként és a milo-t OS útvonalként. Indíts az " #~ "újonnan létrehozott beállításokkal." #~ msgid "Booting with MILO" #~ msgstr "Indítás MILO segítségével" #~ msgid "" #~ "MILO contained on the bootstrap media is configured to proceed straight " #~ "to Linux automatically. Should you wish to intervene, all you need is to " #~ "press space during MILO countdown." #~ msgstr "" #~ "AZ indító médián lévő MILO eleve Linux indításra állított. Ha mégis " #~ "beavatkoznál csak a szóközt kell leütnöd a MILO visszaszámlálás alatt." #~ msgid "" #~ "If you want to specify all the bits explicitly (for example, to supply " #~ "additional parameters), you can use a command like this: " #~ "\n" #~ "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1