# Hungarian translation of Debian Installation Guide boot-installer # SZERVÁC Attila , 2006. # msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2006-10-17 08:26+0000\n" "PO-Revision-Date: 2006-10-07 16:52+0100\n" "Last-Translator: SZERVÁC Attila \n" "Language-Team: Hungarian\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-Language: Hungarian\n" "X-Poedit-Country: HUNGARY\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: title #: boot-installer.xml:20 #, no-c-format msgid "Alpha Console Firmware" msgstr "" #. Tag: para #: boot-installer.xml:21 #, no-c-format msgid "" "Console firmware is stored in a flash ROM and started when an Alpha system " "is powered up or reset. There are two different console specifications used " "on Alpha systems, and hence two classes of console firmware available:" msgstr "" #. Tag: para #: boot-installer.xml:31 #, no-c-format 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." #. Tag: para #: boot-installer.xml:38 #, no-c-format msgid "" "ARC, AlphaBIOS, or ARCSBIOS console, based on the " "Advanced RISC Computing (ARC) specification, which provides an operating " "environment for Windows NT." msgstr "" "Az Az Advanced RISC Computing (ARC) specifikációra épülő ARC, " "AlphaBIOS és ARCSBIOS konzol egy Windows NT-hez készült kezelő-" "környezetet ad." #. Tag: para #: boot-installer.xml:47 #, no-c-format msgid "" "From the user's perspective, the most important difference between SRM and " "ARC is that the choice of console constrains the possible disk-partitioning " "scheme for the hard disk which you wish to boot off of." msgstr "" #. Tag: para #: boot-installer.xml:54 #, no-c-format msgid "" "ARC requires that you use an MS-DOS partition table (as created by " "cfdisk) for the boot disk. Therefore MS-DOS partition " "tables are the native partition format when booting from ARC. " "In fact, since AlphaBIOS contains a disk partitioning utility, you may " "prefer to partition your disks from the firmware menus before installing " "Linux." msgstr "" #. Tag: para #: boot-installer.xml:63 #, no-c-format msgid "" "Conversely, SRM is incompatible " "Specifically, the bootsector format required by the Console Subsystem " "Specification conflicts with the placement of the DOS partition table. with MS-DOS partition tables. Since Tru64 Unix uses the " "BSD disklabel format, this is the native partition format for " "SRM installations." msgstr "" #. Tag: para #: boot-installer.xml:76 #, no-c-format msgid "" "GNU/Linux is the only operating system on Alpha that can be booted from both " "console types, but &debian; &release; only supports booting on SRM-based " "systems. If you have an Alpha for which no version of SRM is available, if " "you will be dual-booting the system with Windows NT, or if your boot device " "requires ARC console support for BIOS initialization, you will not be able " "to use the &debian; &release; installer. You can still run &debian; " "&release; on such systems by using other install media; for instance, you " "can install Debian woody with MILO and upgrade." msgstr "" #. Tag: para #: boot-installer.xml:87 #, no-c-format msgid "" "Because MILO is not available for any of the Alpha " "systems currently in production (as of February 2000), and because it is no " "longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM " "firmware on your older Alpha, it is recommended that you use SRM when " "possible." msgstr "" #. Tag: para #: boot-installer.xml:95 #, no-c-format msgid "" "The following table summarizes available and supported system type/console " "combinations (see 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." #. Tag: entry #: boot-installer.xml:107 #, no-c-format msgid "System Type" msgstr "Rendszer típus" #. Tag: entry #: boot-installer.xml:108 #, no-c-format msgid "Console Type Supported" msgstr "Támogatott konzol típus" #. Tag: entry #: boot-installer.xml:114 #, no-c-format msgid "alcor" msgstr "alcor" #. Tag: entry #: boot-installer.xml:115 boot-installer.xml:118 boot-installer.xml:124 #: boot-installer.xml:130 boot-installer.xml:133 boot-installer.xml:136 #: boot-installer.xml:139 boot-installer.xml:145 boot-installer.xml:148 #: boot-installer.xml:151 boot-installer.xml:160 boot-installer.xml:169 #: boot-installer.xml:184 boot-installer.xml:187 #, no-c-format msgid "ARC or SRM" msgstr "ARC vagy SRM" #. Tag: entry #: boot-installer.xml:117 #, no-c-format msgid "avanti" msgstr "avanti" #. Tag: entry #: boot-installer.xml:120 #, no-c-format msgid "book1" msgstr "book1" #. Tag: entry #: boot-installer.xml:121 boot-installer.xml:127 boot-installer.xml:142 #: boot-installer.xml:154 boot-installer.xml:163 boot-installer.xml:166 #: boot-installer.xml:172 boot-installer.xml:178 boot-installer.xml:181 #, no-c-format msgid "SRM only" msgstr "csak SRM" #. Tag: entry #: boot-installer.xml:123 #, no-c-format msgid "cabriolet" msgstr "cabriolet" #. Tag: entry #: boot-installer.xml:126 #, no-c-format msgid "dp264" msgstr "dp264" #. Tag: entry #: boot-installer.xml:129 #, no-c-format msgid "eb164" msgstr "eb164" #. Tag: entry #: boot-installer.xml:132 #, no-c-format msgid "eb64p" msgstr "eb64p" #. Tag: entry #: boot-installer.xml:135 #, no-c-format msgid "eb66" msgstr "eb66" #. Tag: entry #: boot-installer.xml:138 #, no-c-format msgid "eb66p" msgstr "eb66p" #. Tag: entry #: boot-installer.xml:141 #, no-c-format msgid "jensen" msgstr "jensen" #. Tag: entry #: boot-installer.xml:144 #, no-c-format msgid "lx164" msgstr "lx164" #. Tag: entry #: boot-installer.xml:147 #, no-c-format msgid "miata" msgstr "miata" #. Tag: entry #: boot-installer.xml:150 #, no-c-format msgid "mikasa" msgstr "mikasa" #. Tag: entry #: boot-installer.xml:153 #, no-c-format msgid "mikasa-p" msgstr "mikasa-p" #. Tag: entry #: boot-installer.xml:156 #, no-c-format msgid "nautilus" msgstr "nautilus" #. Tag: entry #: boot-installer.xml:157 #, no-c-format msgid "ARC (see motherboard manual) or SRM" msgstr "ARC (lásd az alaplap kézikönyvet) vagy SRM" #. Tag: entry #: boot-installer.xml:159 #, no-c-format msgid "noname" msgstr "névtelen" #. Tag: entry #: boot-installer.xml:162 #, no-c-format msgid "noritake" msgstr "noritake" #. Tag: entry #: boot-installer.xml:165 #, no-c-format msgid "noritake-p" msgstr "noritake-p" #. Tag: entry #: boot-installer.xml:168 #, no-c-format msgid "pc164" msgstr "pc164" #. Tag: entry #: boot-installer.xml:171 #, no-c-format msgid "rawhide" msgstr "rawhide" #. Tag: entry #: boot-installer.xml:174 #, no-c-format msgid "ruffian" msgstr "ruffian" #. Tag: entry #: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193 #, no-c-format msgid "ARC only" msgstr "csak ARC" #. Tag: entry #: boot-installer.xml:177 #, no-c-format msgid "sable" msgstr "sable" #. Tag: entry #: boot-installer.xml:180 #, no-c-format msgid "sable-g" msgstr "sable-g" #. Tag: entry #: boot-installer.xml:183 #, no-c-format msgid "sx164" msgstr "sx164" #. Tag: entry #: boot-installer.xml:186 #, no-c-format msgid "takara" msgstr "takara" #. Tag: entry #: boot-installer.xml:189 #, no-c-format msgid "xl" msgstr "xl" #. Tag: entry #: boot-installer.xml:192 #, no-c-format msgid "xlt" msgstr "xlt" #. Tag: para #: boot-installer.xml:200 #, no-c-format msgid "" "Generally, none of these consoles can boot Linux directly, so the assistance " "of an intermediary bootloader is required. For the SRM console, " "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." #. Tag: para #: boot-installer.xml:209 #, no-c-format msgid "" "The following paragraphs are from the woody install manual, and are included " "here for reference; they may be useful to someone at a later date when " "Debian supports MILO-based installs again." msgstr "" "Az alábbi bekezdések a woody telepítő kézikönyvből valók, melyre itt " "hivatkozunk; hasznosak lesznek később, mikor a Debian ismét támogatja a MILO-" "alapú telepítést." #. Tag: para #: boot-installer.xml:215 #, no-c-format msgid "" "Generally, none of these consoles can boot Linux directly, so the assistance " "of an intermediary bootloader is required. There are two mainstream Linux " "loaders: 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." #. Tag: para #: boot-installer.xml:221 #, no-c-format 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." #. Tag: para #: boot-installer.xml:231 #, no-c-format 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." #. Tag: para #: boot-installer.xml:238 #, no-c-format msgid "" "Thus, three scenarios are generally possible, depending on the system's " "console firmware and whether or not MILO is available: " "\n" "SRM -> aboot\n" "SRM -> MILO\n" "ARC -> MILO\n" " Because MILO is not available " "for any of the Alpha systems currently in production (as of February 2000), " "and because it is no longer necessary to buy an OpenVMS or Tru64 Unix " "license to have SRM firmware on your older Alpha, it is recommended that you " "use SRM and aboot on new installations of GNU/Linux, " "unless you wish to dual-boot with Windows NT." msgstr "" #. Tag: para #: boot-installer.xml:253 #, no-c-format msgid "" "The majority of AlphaServers and all current server and workstation products " "contain both SRM and AlphaBIOS in their firmware. For half-flash machines such as the various evaluation boards, it is possible to " "switch from one version to another by reflashing the firmware. Also, once " "SRM is installed, it is possible to run ARC/AlphaBIOS from a floppy disk " "(using the arc command). For the reasons mentioned above, " "we recommend switching to SRM before installing &debian;." msgstr "" #. Tag: para #: boot-installer.xml:264 #, no-c-format msgid "" "As on other architectures, you should install the newest available revision " "of the firmware Except on Jensen, where Linux is not " "supported on firmware versions newer than 1.7 — see for more information. before " "installing &debian;. For Alpha, firmware updates can be obtained from Alpha Firmware Updates." msgstr "" #. Tag: title #: boot-installer.xml:283 boot-installer.xml:997 boot-installer.xml:1488 #: boot-installer.xml:1983 boot-installer.xml:2065 boot-installer.xml:2154 #: boot-installer.xml:2498 boot-installer.xml:2594 #, no-c-format msgid "Booting with TFTP" msgstr "Indítás TFTP segítségével" #. Tag: para #: boot-installer.xml:284 #, no-c-format 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." #. Tag: para #: boot-installer.xml:302 #, no-c-format 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." #. Tag: para #: boot-installer.xml:311 #, no-c-format 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:" #. Tag: screen #: boot-installer.xml:323 #, no-c-format msgid "" ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " "console=ttyS0"" msgstr "" ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " "console=ttyS0"" #. Tag: title #: boot-installer.xml:328 #, no-c-format msgid "Booting from CD-ROM with the SRM Console" msgstr "Indítás CD-ROM lemezről az SRM konzollal" #. Tag: para #: boot-installer.xml:329 #, no-c-format msgid "" "Type \n" ">>> boot xxxx -flags 0\n" " where xxxx is your CD-" "ROM drive in SRM notation." msgstr "" "Írd be ezt: \n" ">>> boot xxxx -flags 0\n" " ahol az xxxx a CD-ROM " "meghajtó SRM szerint." #. Tag: title #: boot-installer.xml:341 #, no-c-format msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" msgstr "Indítás CD-ROM lemezről az ARC vagy AlphaBIOS konzollal" #. Tag: para #: boot-installer.xml:342 #, no-c-format 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ő." #. Tag: title #: boot-installer.xml:358 #, no-c-format msgid "Booting from Floppies with the SRM Console" msgstr "Indítás flopiról az SRM konzollal" #. Tag: para #: boot-installer.xml:359 #, no-c-format 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." #. Tag: para #: boot-installer.xml:376 #, no-c-format 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." #. Tag: para #: boot-installer.xml:388 #, no-c-format 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." #. Tag: title #: boot-installer.xml:398 #, no-c-format msgid "Booting from Floppies with the ARC or AlphaBIOS Console" msgstr "Indítás flopiról az ARC vagy AlphaBIOS konzollal" #. Tag: para #: boot-installer.xml:400 #, no-c-format 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." #. Tag: title #: boot-installer.xml:409 #, no-c-format msgid "Booting with MILO" msgstr "Indítás MILO segítségével" #. Tag: para #: boot-installer.xml:410 #, no-c-format msgid "" "MILO contained on the bootstrap media is configured to proceed straight to " "Linux automatically. Should you wish to intervene, all you need is to press " "space during MILO countdown." msgstr "" "AZ indító médián lévő MILO eleve Linux indításra állított. Ha mégis " "beavatkoznál csak a szóközt kell leütnöd a MILO visszaszámlálás alatt." #. Tag: para #: boot-installer.xml:416 #, no-c-format msgid "" "If you want to specify all the bits explicitly (for example, to supply " "additional parameters), you can use a command like this: " "\n" "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" " If you are booting from something other than a " "floppy, substitute fd0 in the above example with the " "appropriate device name in Linux notation. The help " "command would give you a brief MILO command reference." msgstr "" "Ha mindent magad akarsz megadni (például további paramétereket) hasonló " "parancs használható:\n" "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" " Ha flopi helyett mást indítsz, cseréld a fenti " "példa fd0 nevet a megfelelő eszköz nevére Linux " "szerint. A help parancs röviden leírja a MILO parancsait." #. Tag: title #: boot-installer.xml:435 #, no-c-format msgid "Booting from TFTP" msgstr "Indítás TFTP segítségével" #. Tag: para #: boot-installer.xml:441 boot-installer.xml:1003 boot-installer.xml:1506 #: boot-installer.xml:1989 boot-installer.xml:2504 boot-installer.xml:2600 #, no-c-format msgid "" "Booting from the network requires that you have a network connection and a " "TFTP network boot server (DHCP, RARP, or BOOTP)." msgstr "" "A hálózati indítás egy hálózati kapcsolatot és egy TFTP hálózati indító " "kiszolgálót igényel (DHCP, RARP vagy BOOTP)." #. Tag: para #: boot-installer.xml:446 boot-installer.xml:1008 boot-installer.xml:1511 #: boot-installer.xml:1994 boot-installer.xml:2509 boot-installer.xml:2605 #, no-c-format msgid "" "Older systems such as the 715 might require the use of an RBOOT server " "instead of a BOOTP server." msgstr "" "A régebbi rendszerek, például a 715 egy RBOOT kiszolgálót kérhetnek BOOTP " "helyett." #. Tag: para #: boot-installer.xml:451 boot-installer.xml:1013 boot-installer.xml:1516 #: boot-installer.xml:1999 boot-installer.xml:2514 boot-installer.xml:2610 #, no-c-format msgid "" "The installation method 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:459 #, no-c-format msgid "Booting from TFTP on Netwinder" msgstr "TFTP indítás Netwinder gépen" #. Tag: para #: boot-installer.xml:460 #, no-c-format msgid "" "Netwinders have two network interfaces: A 10Mbps NE2000-compatible card " "(which is generally referred to as eth0) and a 100Mbps " "Tulip card. There may be problems loading the image via TFTP using the " "100Mbps card so it is recommended that you use the 10Mbps interface (the one " "labeled with 10 Base-T)." msgstr "" "A Netwinder gépeknek 2 hálózati csatolója van: egy 10Mbps NE2000-" "kompatibilis kártya (általában eth0) és egy 100Mbps Tulip " "kártya. Utóbbival gondok lehetnek a kép TFTP letöltésekor így ajánlott a " "10Mbps csatoló használata (a 10 Base-T címkéjű)." #. Tag: para #: boot-installer.xml:469 #, no-c-format msgid "" "You need NeTTrom 2.2.1 or later to boot the installation system, and version " "2.3.3 is recommended. Unfortunately, firmware files are currently not " "available for download because of license issues. If this situation changes, " "you may find new images at ." msgstr "" #. Tag: para #: boot-installer.xml:477 #, no-c-format msgid "" "When you boot your Netwinder you have to interrupt the boot process during " "the countdown. This allows you to set a number of firmware settings needed " "in order to boot the installer. First of all, start by loading the default " "settings: \n" " NeTTrom command-> load-defaults\n" " Furthermore, you must configure the network, " "either with a static address: \n" " NeTTrom command-> setenv netconfig_eth0 flash\n" " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" " where 24 is the number of set bits in the " "netmask, or a dynamic address: \n" " NeTTrom command-> setenv netconfig_eth0 dhcp\n" " You may also need to configure the " "route1 settings if the TFTP server is not on the " "local subnet. Following these settings, you have to specify the TFTP server " "and the location of the image. You can then store your settings to flash. " "\n" " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" " NeTTrom command-> setenv kerntftpfile boot.img\n" " NeTTrom command-> save-all\n" " Now you have to tell the firmware that the TFTP " "image should be booted: \n" " NeTTrom command-> setenv kernconfig tftp\n" " NeTTrom command-> setenv rootdev /dev/ram\n" " If you use a serial console to install your " "Netwinder, you need to add the following setting: \n" " NeTTrom command-> setenv cmdappend root=/dev/ram " "console=ttyS0,115200\n" " Alternatively, for installations using a " "keyboard and monitor you have to set: \n" " NeTTrom command-> setenv cmdappend root=/dev/ram\n" " You can use the printenv " "command to review your environment settings. After you have verified that " "the settings are correct, you can load the image: \n" " NeTTrom command-> boot\n" " In case you run into any problems, a detailed HOWTO is available." msgstr "" #. Tag: title #: boot-installer.xml:529 #, no-c-format msgid "Booting from TFTP on CATS" msgstr "" #. Tag: para #: boot-installer.xml:530 #, no-c-format msgid "" "On CATS machines, use boot de0: or similar at the Cyclone " "prompt." msgstr "" #. Tag: title #: boot-installer.xml:540 #, no-c-format msgid "Booting from CD-ROM" msgstr "Indítás CD-ROM lemezről" #. Tag: para #: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1125 #: boot-installer.xml:1946 boot-installer.xml:2286 boot-installer.xml:2640 #, no-c-format msgid "" "The easiest route for most people will be to use a set of Debian CDs. If you " "have a CD set, and if your machine supports booting directly off the CD, " "great! Simply configure your system for booting off a " "CD as described in , insert " "your CD, reboot, and proceed to the next chapter." msgstr "" "A legtöbb felhasználó számára a legegyszerűbb mód a Debian CD-készlet " "használata. Ha van egy CD-készleted és a géped támogatja a CD-lemezről " "indítást, akkor minden csodás. Egyszerűen á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:557 boot-installer.xml:727 boot-installer.xml:1136 #: boot-installer.xml:1957 boot-installer.xml:2297 boot-installer.xml:2651 #, no-c-format msgid "" "Note that certain CD drives may require special drivers, and thus be " "inaccessible in the early installation stages. If it turns out the standard " "way of booting off a CD doesn't work for your hardware, revisit this chapter " "and read about alternate kernels and installation methods which may work for " "you." msgstr "" "Egyes CD-eszközök különleges meghajtókat igényelnek és elérhetetlenek " "lehetnek a telepítő első lépéseiben. Ha a CD-lemezről indítás szokásos módja " "nem működik a gépeden, nézd át újra e fejezetet és olvasd el az eltérő " "kernelekről és telepítő módokról szóló részeket, mely megoldja ezt." #. Tag: para #: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1144 #: boot-installer.xml:1965 boot-installer.xml:2305 boot-installer.xml:2659 #, no-c-format msgid "" "Even if you cannot boot from CD-ROM, you can probably install the Debian " "system components and any packages you want from CD-ROM. Simply boot using a " "different media, such as floppies. When it's time to install the operating " "system, base system, and any additional packages, point the installation " "system at the CD-ROM drive." msgstr "" "Még abban az esetben is, ha nem tudsz CD-ROM lemezről indítani, valószínűleg " "képes leszel a Debian rendszer összetevőit és a kívánt csomagokat telepíteni " "ezekről. Egyszerűen indíts más médiumról, például flopiról. Az operációs " "rendszer, alaprendszer és tetszőleges további csomagok telepítésekor a " "telepítő rendszert a CD-ROM meghajtóra irányíthatod." #. Tag: para #: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1152 #: boot-installer.xml:1973 boot-installer.xml:2313 boot-installer.xml:2667 #, no-c-format msgid "" "If you have problems booting, see ." msgstr "" "Ha gondjaid vannak ez indítással, lásd az részt." #. Tag: para #: boot-installer.xml:580 #, no-c-format msgid "" "To boot a CD-ROM from the Cyclone console prompt, use the command " "boot cd0:cats.bin" msgstr "" "Egy CD-ROM indításához Cyclone konzol jelről, használd a boot cd0:" "cats.bin parancsot" #. Tag: title #: boot-installer.xml:589 #, no-c-format msgid "Booting from Firmware" msgstr "" #. Tag: para #: boot-installer.xml:595 #, no-c-format msgid "" "There is an increasing number of consumer devices that directly boot from a " "flash chip on the device. The installer can be written to flash so it will " "automatically start when you reboot your machines." msgstr "" #. Tag: para #: boot-installer.xml:601 #, no-c-format msgid "" "In many cases, changing the firmware of an embedded device voids your " "warranty. Sometimes you are also not able to recover your device if there " "are problems during the flashing process. Therefore, please take care and " "follow the steps precisely." msgstr "" #. Tag: title #: boot-installer.xml:612 #, no-c-format msgid "Booting the NSLU2" msgstr "" #. Tag: para #: boot-installer.xml:613 #, no-c-format msgid "There are three ways how to put the installer firmware into flash:" msgstr "" #. Tag: title #: boot-installer.xml:619 #, no-c-format msgid "Using the NSLU2 web interface" msgstr "" #. Tag: para #: boot-installer.xml:620 #, no-c-format 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 "" #. Tag: title #: boot-installer.xml:631 #, no-c-format msgid "Via the network using Linux/Unix" msgstr "" #. Tag: para #: boot-installer.xml:632 #, no-c-format 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 "" #. Tag: title #: boot-installer.xml:693 #, no-c-format msgid "Via the network using Windows" msgstr "" #. Tag: para #: boot-installer.xml:694 #, no-c-format msgid "" "There is a tool for Windows to upgrade the firmware " "via the network." msgstr "" #. Tag: title #: boot-installer.xml:710 boot-installer.xml:1119 boot-installer.xml:1934 #: boot-installer.xml:2280 boot-installer.xml:2634 #, no-c-format msgid "Booting from a CD-ROM" msgstr "Indítás egy CD-ROM lemezről" #. Tag: title #: boot-installer.xml:848 #, 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:851 #, 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:856 #, no-c-format msgid "" "If you intend to use the hard drive only for booting and then download " "everything over the network, you should download the netboot/" "debian-installer/i386/initrd.gz file and its corresponding " "kernel. This will allow you to repartition the hard disk from which you boot " "the installer, although you should do so with care." msgstr "" "Ha a merevlemez csak indításra a többi letöltésre pedig a hálózat szolgál, a " "netboot/debian-installer/i386/initrd.gz fájl és a " "megfelelő kernel letöltése kell. Ezzel átparticionálható a telepítő " "indítására használt merevlemez, körültekintően." #. Tag: para #: boot-installer.xml:864 #, no-c-format msgid "" "Alternatively, if you intend to keep an existing partition on the hard drive " "unchanged during the install, you can download the 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." 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:873 #, 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:894 #, no-c-format msgid "" "image=/boot/newinstall/vmlinuz\n" " label=newinstall\n" " initrd=/boot/newinstall/initrd.gz\n" " root=/dev/ram0\n" " append=\"ramdisk_size=12000\"" msgstr "" "image=/boot/newinstall/vmlinuz\n" " label=newinstall\n" " initrd=/boot/newinstall/initrd.gz\n" " root=/dev/ram0\n" " append=\"ramdisk_size=12000\"" #. Tag: para #: boot-installer.xml:894 #, 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:903 #, 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 root=/dev/ram0 ramdisk_size=12000\n" "initrd (hd0,0)/boot/newinstall/initrd.gz\n" " and reboot." msgstr "" "A GRUB hasonló. Menj a menu.lst " "fájlra a /boot/grub/ (néha a /boot/boot/grub/" ") könyvtárban és add hozzá a következő sorokat: " "\n" "title New Install\n" "kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n" "initrd (hd0,0)/boot/newinstall/initrd.gz\n" " és indíts újra." #. Tag: para #: boot-installer.xml:914 #, no-c-format msgid "" "Note that the value of the ramdisk_size may need to " "be adjusted for the size of the initrd image. From here on, there should be " "no difference between GRUB or LILO." msgstr "" "A ramdisk_size értéke természetesen nem lehet kisebb, " "mint ami az initrd képhez szükséges. Innentől nincs különbség a " "GRUB vagy LILO között." #. Tag: title #: boot-installer.xml:925 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "Indítás USB tárról" #. Tag: para #: boot-installer.xml:926 #, no-c-format msgid "" "Let's assume you have prepared everything from 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;." 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:939 boot-installer.xml:2046 boot-installer.xml:2540 #: boot-installer.xml:2688 #, no-c-format msgid "Booting from Floppies" msgstr "Indítás flopikról" #. Tag: para #: boot-installer.xml:940 boot-installer.xml:2548 #, 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:947 #, no-c-format msgid "" "To boot from the installer boot floppy, place it in the primary floppy " "drive, shut down the system as you normally would, then turn it back on." msgstr "" "A telepítő flopi indításához, tedd az elsődleges flopi meghajtóba, állítsd " "le a rendszert, ahogy egyébként tennéd és indítsd újra a gépet." #. Tag: para #: boot-installer.xml:953 #, fuzzy, no-c-format msgid "" "For installing from an LS-120 drive (ATAPI version) with a set of floppies, " "you need to specify the virtual location for the floppy device. This is done " "with the 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 " "linux root=/dev/hdc at the boot prompt." msgstr "" "Egy LS-120 meghajtóról (ATAPI változat) indításhoz egy flopi-készlettel, meg " "kell adni a flopi eszköz virtuális helyét. Ez a 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: linux root=/dev/hdc az " "indító jelnél. Az LS-120 telepítést csak a 2.4 és későbbi kernelek " "támogatják." #. Tag: para #: boot-installer.xml:963 #, 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:972 #, no-c-format msgid "" "The floppy disk will be accessed, and you should then see a screen that " "introduces the boot floppy and ends with the 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:978 #, 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:987 #, no-c-format msgid "" "After booting from the boot floppy, the root floppy is requested. Insert the " "root floppy and press &enterkey;, and the contents are loaded into memory. " "The installer program 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: para #: boot-installer.xml:1021 #, 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:1027 #, 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:1028 #, 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:1039 #, no-c-format msgid "NIC with Network BootROM" msgstr "" #. Tag: para #: boot-installer.xml:1040 #, no-c-format msgid "" "It could be that your Network Interface Card provides TFTP boot " "functionality." msgstr "" #. Tag: para #: boot-installer.xml:1045 #, no-c-format msgid "" "Let us (&email-debian-boot-list;) know how did you manage it. " "Please refer to this document." msgstr "" #. Tag: title #: boot-installer.xml:1053 #, no-c-format msgid "Etherboot" msgstr "" #. Tag: para #: boot-installer.xml:1054 #, no-c-format msgid "" "The etherboot project " "provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" #. Tag: title #: boot-installer.xml:1063 #, no-c-format msgid "The Boot Prompt" msgstr "" #. Tag: para #: boot-installer.xml:1064 #, no-c-format msgid "" "When the installer boots, you should be presented with a friendly graphical " "screen showing the Debian logo and the boot prompt: " "\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." msgstr "" #. Tag: para #: boot-installer.xml:1076 #, no-c-format msgid "" "Information on available boot methods and on boot parameters which might be " "useful can be found by pressing F2 through F8. If you add any parameters to the boot command line, be sure to type " "the boot method (the default is linux) and a space " "before the first parameter (e.g., linux fb=false)." msgstr "" #. Tag: para #: boot-installer.xml:1085 #, no-c-format msgid "" "If you are installing the system via a remote management device that " "provides a text interface to the VGA console, you may not be able to see the " "initial graphical splash screen upon booting the installer; you may even not " "see the boot prompt. Examples of these devices include the text console of " "Compaq's integrated Lights Out (iLO) and HP's " "Integrated Remote Assistant (IRA). You can blindly press " "F1 In some cases these devices will require special escape " "sequences to enact this keypress, for example the IRA uses " "Ctrl F 1. to bypass this screen and view the help text. " "Once you are past the splash screen and at the help text your keystrokes " "will be echoed at the prompt as expected. To prevent the installer from " "using the framebuffer for the rest of the installation, you will also want " "to add fb=false to the boot prompt, as described in " "the help text." msgstr "" #. Tag: title #: boot-installer.xml:1160 #, no-c-format msgid "CD Contents" msgstr "" #. Tag: para #: boot-installer.xml:1162 #, 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:1178 #, no-c-format msgid "" "The IA-64 architecture uses the next generation Extensible Firmware " "Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows " "little about the boot device other than the partition table and Master Boot " "Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted " "disk partitions. This simplifies the often arcane process of starting a " "system. The system boot loader and the EFI firmware that supports it have a " "full filesystem to store the files necessary for booting the machine. This " "means that the system disk on an IA-64 system has an additional disk " "partition dedicated to EFI instead of the simple MBR or boot block on more " "conventional systems." msgstr "" #. Tag: para #: boot-installer.xml:1194 #, 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:1203 #, 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:1215 #, no-c-format msgid "" "The EFI Boot Manager is presented as the last step of the firmware " "initialization. It displays a menu list from which the user can select an " "option. Depending on the model of system and what other software has been " "loaded on the system, this menu may be different from one system to another. " "There should be at least two menu items displayed, 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:1234 #, no-c-format msgid "IMPORTANT" msgstr "" #. Tag: para #: boot-installer.xml:1235 #, no-c-format msgid "" "The EFI Boot Manager will select a default boot action, typically the first " "menu choice, within a pre-set number of seconds. This is indicated by a " "countdown at the bottom of the screen. Once the timer expires and the " "systems starts the default action, you may have to reboot the machine in " "order to continue the installation. If the default action is the EFI Shell, " "you can return to the Boot Manager by running exit at the " "shell prompt." msgstr "" #. Tag: title #: boot-installer.xml:1247 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "" #. Tag: para #: boot-installer.xml:1254 #, no-c-format msgid "" "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " "display the EFI Boot Manager page and menu after it completes its system " "initialization." msgstr "" #. Tag: para #: boot-installer.xml:1260 #, 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:1266 #, 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:1277 #, no-c-format msgid "" "You can choose either of the entries that refer to the CD/DVD drive. Select " "your choice with the arrow keys and press 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:1288 #, 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:1300 #, no-c-format msgid "" "These steps start the Debian boot loader which will display a menu page for " "you to select a boot kernel and options. Proceed to selecting the boot " "kernel and options." msgstr "" #. Tag: title #: boot-installer.xml:1310 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "" #. Tag: para #: boot-installer.xml:1311 #, no-c-format msgid "" "If, for some reason, option 1 is not successful, reboot the machine and when " "the EFI Boot Manager screen appears there should be one option called " "EFI Shell [Built-in]. Boot the Debian Installer CD with " "the following steps:" msgstr "" #. Tag: para #: boot-installer.xml:1322 #, no-c-format msgid "" "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " "display the EFI Boot Manager page and menu after it completes system " "initialization." msgstr "" #. Tag: para #: boot-installer.xml:1328 #, 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:1342 #, 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:1349 #, 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:1356 #, no-c-format msgid "" "Enter elilo and press ENTER. This will " "start the boot load sequence." msgstr "" #. Tag: para #: boot-installer.xml:1363 #, no-c-format msgid "" "As with option 1, these steps start the Debian boot loader which will " "display a menu page for you to select a boot kernel and options. You can " "also enter the shorter fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel " "and options." msgstr "" #. Tag: title #: boot-installer.xml:1377 #, no-c-format msgid "Installing using a Serial Console" msgstr "" #. Tag: para #: boot-installer.xml:1379 #, no-c-format msgid "" "You may choose to perform an install using a monitor and keyboard or using a " "serial connection. To use a monitor/keyboard setup, select an option " "containing the string [VGA console]. To install over a serial connection, " "choose an option containing the string [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:1390 #, no-c-format msgid "" "In most circumstances, you will want the installer to use the same baud rate " "as your connection to the EFI console. If you aren't sure what this setting " "is, you can obtain it using the command baud at the EFI " "shell." msgstr "" #. Tag: para #: boot-installer.xml:1397 #, no-c-format msgid "" "If there is not an option available that is configured for the serial device " "or baud rate you would like to use, you may override the console setting for " "one of the existing menu options. For example, to use a 57600 baud console " "over the ttyS1 device, enter console=ttyS1,57600n8 into " "the Boot: text window." msgstr "" #. Tag: para #: boot-installer.xml:1408 #, no-c-format msgid "" "Most IA-64 boxes ship with a default console setting of 9600 baud. This " "setting is rather slow, and the normal installation process will take a " "significant time to draw each screen. You should consider either increasing " "the baud rate used for performing the installation, or performing a Text " "Mode installation. See the Params help menu for " "instructions on starting the installer in Text Mode." msgstr "" #. Tag: para #: boot-installer.xml:1417 #, no-c-format msgid "" "If you select the wrong console type, you will be able to select the kernel " "and enter parameters but both the display and your input will go dead as " "soon as the kernel starts, requiring you to reboot before you can begin the " "installation." msgstr "" #. Tag: title #: boot-installer.xml:1426 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "" #. Tag: para #: boot-installer.xml:1428 #, no-c-format msgid "" "The boot loader will display a form with a menu list and a text window with " "a 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:1440 #, 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:1458 #, 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:1463 #, no-c-format msgid "" "Enter any boot parameters by typing at the keyboard. The text will be " "displayed directly in the text window. This is where kernel parameters (such " "as serial console settings) are specified." msgstr "" #. Tag: para #: boot-installer.xml:1470 #, 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:1479 #, no-c-format msgid "" "Proceed to the next chapter to continue the installation where you will set " "up the language locale, network, and disk partitions." msgstr "" #. Tag: para #: boot-installer.xml:1490 #, no-c-format msgid "" "Booting an IA64 system from the network is similar to a CD boot. The only " "difference is how the installation kernel is loaded. The EFI Boot Manager " "can load and start programs from a server on the network. Once the " "installation kernel is loaded and starts, the system install will proceed " "thru the same steps as the CD install with the exception that the packages " "of the base install will be loaded from the network rather than the CD drive." msgstr "" #. Tag: para #: boot-installer.xml:1524 #, no-c-format msgid "" "Network booting an ia64 system requires two architecture-specific actions. " "On the boot server, DHCP and TFTP must be configured to deliver " "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:1535 #, no-c-format msgid "Configuring the Server" msgstr "" #. Tag: para #: boot-installer.xml:1536 #, no-c-format msgid "" "A suitable TFTP entry for network booting an ia64 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:1546 #, 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:1556 #, 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:1556 #, 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:1573 #, no-c-format msgid "Configuring the Client" msgstr "" #. Tag: para #: boot-installer.xml:1574 #, no-c-format msgid "" "To configure the client to support TFTP booting, start by booting to EFI and " "entering the 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:1606 #, no-c-format msgid "" "The boot loader will display its prompt after it has downloaded and " "processed its configuration file. At this point, the installation proceeds " "with the same steps as a CD install. Select a boot option as in above and " "when the kernel has completed installing itself from the network, it will " "start the Debian Installer." msgstr "" #. Tag: para #: boot-installer.xml:1615 #, no-c-format msgid "" "Proceed to the next chapter to continue the installation where you will set " "up the language locale, network, and the disk partitions." msgstr "" #. Tag: title #: boot-installer.xml:1628 #, no-c-format msgid "Choosing an Installation Method" msgstr "" #. Tag: para #: boot-installer.xml:1630 #, no-c-format msgid "" "Some &arch-title; subarchs have the option of booting using either a 2.4.x " "or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux " "kernel. The installer should also require less memory when using a 2.4.x " "linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses " "tmpfs." msgstr "" #. Tag: para #: boot-installer.xml:1638 #, no-c-format msgid "" "If you are using a 2.2.x linux kernel, then you need to use the " "&ramdisksize; kernel parameter." msgstr "" #. Tag: para #: boot-installer.xml:1643 #, no-c-format msgid "" "Make sure root=/dev/ram is one of your kernel " "parameters." msgstr "" #. Tag: para #: boot-installer.xml:1648 #, no-c-format msgid "" "If you're having trouble, check cts's " "&arch-title; debian-installer FAQ." msgstr "" #. Tag: title #: boot-installer.xml:1665 #, no-c-format msgid "Amiga" msgstr "" #. Tag: para #: boot-installer.xml:1666 #, no-c-format msgid "" "The only method of installation available to amiga is the hard drive (see " "). In other words the cdrom is not " "bootable." msgstr "" #. Tag: para #: boot-installer.xml:1672 #, no-c-format msgid "" "Amiga does not currently work with bogl, so if you are seeing bogl errors, " "you need to include the boot parameter fb=false." msgstr "" #. Tag: title #: boot-installer.xml:1681 #, no-c-format msgid "Atari" msgstr "" #. Tag: para #: boot-installer.xml:1682 #, no-c-format msgid "" "The installer for atari may be started from either the hard drive (see ) or from floppies (see ). In other words the cdrom is not bootable." msgstr "" #. Tag: para #: boot-installer.xml:1689 #, no-c-format msgid "" "Atari does not currently work with bogl, so if you are seeing bogl errors, " "you need to include the boot parameter fb=false." msgstr "" #. Tag: title #: boot-installer.xml:1698 #, no-c-format msgid "BVME6000" msgstr "" #. Tag: para #: boot-installer.xml:1699 #, no-c-format msgid "" "The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." msgstr "" #. Tag: title #: boot-installer.xml:1709 #, no-c-format msgid "Macintosh" msgstr "" #. Tag: para #: boot-installer.xml:1710 #, no-c-format msgid "" "The only method of installation available to mac is from the hard drive (see " "). In other words the cdrom is not " "bootable. Macs do not have a working 2.4.x kernel." msgstr "" #. Tag: para #: boot-installer.xml:1717 #, no-c-format msgid "" "If your hardware uses a 53c9x-based scsi bus, then you may need to include " "the kernel parameter mac53c9x=1,0. Hardware with two " "such scsi buses, such as the Quadra 950, will need mac53c9x=2,0 instead. Alternatively, the parameter can be specified as " "mac53c9x=-1,0 which will leave autodetection on, but " "which will disable SCSI disconnects. Note that specifying this parameter is " "only necessary if you have more than one hard disk; otherwise, the system " "will run faster if you do not specify it." msgstr "" #. Tag: title #: boot-installer.xml:1732 #, no-c-format msgid "MVME147 and MVME16x" msgstr "" #. Tag: para #: boot-installer.xml:1733 #, no-c-format msgid "" "The installer for MVME147 and MVME16x may be started from either floppies " "(see ) or the net (see ). In other words the cdrom is not bootable." msgstr "" #. Tag: title #: boot-installer.xml:1743 #, no-c-format msgid "Q40/Q60" msgstr "" #. Tag: para #: boot-installer.xml:1744 #, no-c-format msgid "" "The only method of installation available to Q40/Q60 is from the hard drive " "(see ). In other words the cdrom " "is not bootable." msgstr "" #. Tag: title #: boot-installer.xml:1755 #, no-c-format msgid "Booting from a Hard Disk" msgstr "" #. Tag: para #: boot-installer.xml:1761 boot-installer.xml:2359 #, no-c-format msgid "" "Booting from an existing operating system is often a convenient option; for " "some systems it is the only supported method of installation." msgstr "" #. Tag: para #: boot-installer.xml:1767 boot-installer.xml:2365 #, no-c-format msgid "" "To boot the installer from hard disk, you will have already completed " "downloading and placing the needed files in ." msgstr "" #. Tag: para #: boot-installer.xml:1776 #, no-c-format msgid "" "At least six different ramdisks may be used to boot from the hard drive, " "three different types each with and without support for a 2.2.x linux kernel " "(see MANIFEST for details)." msgstr "" #. Tag: para #: boot-installer.xml:1784 #, no-c-format msgid "" "The three different types of ramdisks are cdrom, " "hd-media, and nativehd. These " "ramdisks differ only in their source for installation packages. The " "cdrom ramdisk uses a cdrom to get debian-installer " "packages. The hd-media ramdisk uses an iso image file " "of a cdrom currently residing on a hard disk. Finally, the " "nativehd ramdisk uses the net to install packages." msgstr "" #. Tag: title #: boot-installer.xml:1805 #, no-c-format msgid "Booting from AmigaOS" msgstr "" #. Tag: para #: boot-installer.xml:1806 #, no-c-format msgid "" "In the Workbench, start the Linux installation process by " "double-clicking on the StartInstall icon in the " "debian directory." msgstr "" #. Tag: para #: boot-installer.xml:1812 #, no-c-format msgid "" "You may have to press the &enterkey; key twice after the Amiga installer " "program has output some debugging information into a window. After this, the " "screen will go grey, there will be a few seconds' delay. Next, a black " "screen with white text should come up, displaying all kinds of kernel " "debugging information. These messages may scroll by too fast for you to " "read, but that's OK. After a couple of seconds, the installation program " "should start automatically, so you can continue down at ." msgstr "" #. Tag: title #: boot-installer.xml:1827 #, no-c-format msgid "Booting from Atari TOS" msgstr "" #. Tag: para #: boot-installer.xml:1828 #, no-c-format msgid "" "At the GEM desktop, start the Linux installation process by double-clicking " "on the bootstra.prg icon in the debian directory and clicking Ok at the program " "options dialog box." msgstr "" #. Tag: para #: boot-installer.xml:1835 #, no-c-format msgid "" "You may have to press the &enterkey; key after the Atari bootstrap program " "has output some debugging information into a window. After this, the screen " "will go grey, there will be a few seconds' delay. Next, a black screen with " "white text should come up, displaying all kinds of kernel debugging " "information. These messages may scroll by too fast for you to read, but " "that's OK. After a couple of seconds, the installation program should start " "automatically, so you can continue below at ." msgstr "" #. Tag: title #: boot-installer.xml:1850 #, no-c-format msgid "Booting from MacOS" msgstr "" #. Tag: para #: boot-installer.xml:1851 #, no-c-format msgid "" "You must retain the original Mac system and boot from it. It is " "essential that, when booting MacOS in preparation for " "booting the Penguin linux loader, you hold the shift key " "down to prevent extensions from loading. If you don't use MacOS except for " "loading linux, you can accomplish the same thing by removing all extensions " "and control panels from the Mac's System Folder. Otherwise extensions may be " "left running and cause random problems with the running linux kernel." msgstr "" #. Tag: para #: boot-installer.xml:1862 #, no-c-format msgid "" "Macs require the Penguin bootloader. If you do not have " "the tools to handle a Stuffit archive, &penguin19.hfs; is " "an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." msgstr "" #. Tag: para #: boot-installer.xml:1871 #, no-c-format msgid "" "At the MacOS desktop, start the Linux installation process by double-" "clicking on the Penguin Prefs icon in the " "Penguin directory. The Penguin " "booter will start up. Go to the Settings item in " "the File menu, click the Kernel tab. " "Select the kernel (vmlinuz) and ramdisk " "(initrd.gz) images in the install " "directory by clicking on the corresponding buttons in the upper right " "corner, and navigating the file select dialogs to locate the files." msgstr "" #. Tag: para #: boot-installer.xml:1886 #, no-c-format msgid "" "To set the boot parameters in Penguin, choose File -> " "Settings..., then switch to the " "Options tab. Boot parameters may be typed in to the " "text entry area. If you will always want to use these settings, select " "File -> Save Settings as Default." msgstr "" #. Tag: para #: boot-installer.xml:1895 #, no-c-format msgid "" "Close the Settings dialog, save the settings and start " "the bootstrap using the Boot Now item in the " "File menu." msgstr "" #. Tag: para #: boot-installer.xml:1902 #, no-c-format msgid "" "The Penguin booter will output some debugging information " "into a window. After this, the screen will go grey, there will be a few " "seconds' delay. Next, a black screen with white text should come up, " "displaying all kinds of kernel debugging information. These messages may " "scroll by too fast for you to read, but that's OK. After a couple of " "seconds, the installation program should start automatically, so you can " "continue below at ." msgstr "" #. Tag: title #: boot-installer.xml:1917 #, no-c-format msgid "Booting from Q40/Q60" msgstr "" #. Tag: para #: boot-installer.xml:1919 #, no-c-format msgid "FIXME" msgstr "" #. Tag: para #: boot-installer.xml:1923 #, no-c-format msgid "" "The installation program should start automatically, so you can continue " "below at ." msgstr "" #. Tag: para #: boot-installer.xml:1935 #, no-c-format msgid "" "Currently, the only &arch-title; subarchitecture that supports CD-ROM " "booting is the BVME6000." msgstr "" #. Tag: para #: boot-installer.xml:2007 #, no-c-format msgid "" "After booting the VMEbus systems you will be presented with the LILO " "Boot: prompt. At that prompt enter one of the following to " "boot Linux and begin installation proper of the Debian software using vt102 " "terminal emulation:" msgstr "" #. Tag: para #: boot-installer.xml:2018 #, no-c-format msgid "type i6000 &enterkey; to install a BVME4000/6000" msgstr "" #. Tag: para #: boot-installer.xml:2023 #, no-c-format msgid "type i162 &enterkey; to install an MVME162" msgstr "" #. Tag: para #: boot-installer.xml:2028 #, no-c-format msgid "type i167 &enterkey; to install an MVME166/167" msgstr "" #. Tag: para #: boot-installer.xml:2035 #, no-c-format msgid "" "You may additionally append the string TERM=vt100 to use " "vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." msgstr "" #. Tag: para #: boot-installer.xml:2047 #, no-c-format msgid "" "For most &arch-title; architectures, booting from a local filesystem is the " "recommended method." msgstr "" #. Tag: para #: boot-installer.xml:2052 #, no-c-format msgid "" "Booting from the boot floppy is supported only for Atari and VME (with a " "SCSI floppy drive on VME) at this time." msgstr "" #. Tag: title #: boot-installer.xml:2068 boot-installer.xml:2115 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para #: boot-installer.xml:2069 #, 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:2088 boot-installer.xml:2137 boot-installer.xml:2192 #: boot-installer.xml:2231 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para #: boot-installer.xml:2089 boot-installer.xml:2193 #, no-c-format msgid "" "On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load " "the SiByl boot loader via TFTP which will then load and start the Debian " "installer. In most cases, you will first obtain an IP address via DHCP but " "it is also possible to configure a static address. In order to use DHCP, you " "can enter the following command on the CFE prompt: " "\n" "ifconfig eth0 -auto\n" " Once you have obtained an IP address, you can " "load SiByl with the following command: \n" "boot 192.168.1.1:/boot/sibyl\n" " You need to substitute the IP address listed in " "this example with either the name or the IP address of your TFTP server. " "Once you issue this command, the installer will be loaded automatically." msgstr "" #. Tag: title #: boot-installer.xml:2112 boot-installer.xml:2216 boot-installer.xml:2739 #, no-c-format msgid "Boot Parameters" msgstr "" #. Tag: para #: boot-installer.xml:2116 #, 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:2121 #, 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:2131 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: para #: boot-installer.xml:2138 boot-installer.xml:2232 #, no-c-format msgid "" "You cannot pass any boot parameters directly from the CFE prompt. Instead, " "you have to edit the /boot/sibyl.conf file on the TFTP " "server and add your parameters to the extra_args " "variable." msgstr "" #. Tag: title #: boot-installer.xml:2157 boot-installer.xml:2219 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "" #. Tag: para #: boot-installer.xml:2158 #, no-c-format msgid "" "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to " "install an NFS server and put the installer files in /nfsroot. When you boot your Cobalt, you have to press the left and the " "right cursor buttons at the same time and the machine will boot via the " "network from NFS. It will then display several options on the display. There " "are the following two installation methods:" msgstr "" #. Tag: para #: boot-installer.xml:2168 #, no-c-format msgid "" "Via SSH (default): In this case, the installer will configure the network " "via DHCP and start an SSH server. It will then display a random password and " "other login information (such as the IP address) on the Cobalt LCD. When you " "connect to the machine with an SSH client you can start with the " "installation." msgstr "" #. Tag: para #: boot-installer.xml:2177 #, no-c-format msgid "" "Via serial console: Using a null modem cable, you can connect to the serial " "port of your Cobalt machine (using 115200 bps) and perform the installation " "this way. This option is not available on Qube 2700 (Qube1) machines since " "they have no serial port." msgstr "" #. Tag: para #: boot-installer.xml:2220 #, no-c-format msgid "" "You cannot pass any boot parameters directly. Instead, you have to edit the " "/nfsroot/default.colo file on the NFS server and add " "your parameters to the args variable." msgstr "" #. Tag: title #: boot-installer.xml:2248 #, no-c-format msgid "s390 Limitations" msgstr "" #. Tag: para #: boot-installer.xml:2249 #, no-c-format msgid "" "In order to run the installation system a working network setup and ssh " "session is needed on S/390." msgstr "" #. Tag: para #: boot-installer.xml:2254 #, no-c-format msgid "" "The booting process starts with a network setup that prompts you for several " "network parameters. If the setup is successful, you will login to the system " "by starting an ssh session which will launch the standard installation " "system." msgstr "" #. Tag: title #: boot-installer.xml:2265 #, no-c-format msgid "s390 Boot Parameters" msgstr "" #. Tag: para #: boot-installer.xml:2266 #, no-c-format msgid "" "On S/390 you can append boot parameters in the parm file. This file can " "either be in ASCII or EBCDIC format. Please read Device Drivers and Installation Commands for more " "information about S/390-specific boot parameters." msgstr "" #. Tag: para #: boot-installer.xml:2320 #, no-c-format msgid "" "Currently, the only &arch-title; subarchitectures that support CD-ROM " "booting are PReP and New World PowerMacs. On PowerMacs, hold the c key, or else the combination of Command, " "Option, Shift, and Delete " "keys together while booting to boot from the CD-ROM." msgstr "" #. Tag: para #: boot-installer.xml:2329 #, no-c-format msgid "" "OldWorld PowerMacs will not boot a Debian CD, because OldWorld computers " "relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-" "software version of this driver is not available. All OldWorld systems have " "floppy drives, so use the floppy drive to launch the installer, and then " "point the installer to the CD for the needed files." msgstr "" #. Tag: para #: boot-installer.xml:2338 #, no-c-format msgid "" "If your system doesn't boot directly from CD-ROM, you can still use the CD-" "ROM to install the system. On NewWorlds, you can also use an OpenFirmware " "command to boot from the CD-ROM manually. Follow the instructions in for booting from the hard disk, except use the " "path to yaboot on the CD at the OF prompt, such as" msgstr "" #. Tag: screen #: boot-installer.xml:2347 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "" #. Tag: title #: boot-installer.xml:2353 #, no-c-format msgid "Booting from Hard Disk" msgstr "" #. Tag: title #: boot-installer.xml:2374 #, no-c-format msgid "Booting CHRP from OpenFirmware" msgstr "" #. Tag: emphasis #: boot-installer.xml:2378 #, no-c-format msgid "Not yet written." msgstr "" #. Tag: title #: boot-installer.xml:2383 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" #. Tag: para #: boot-installer.xml:2384 #, 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:2402 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" #. Tag: para #: boot-installer.xml:2403 #, 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 . Restart the computer, and " "immediately (during the chime) hold down the Option, " "Command (cloverleaf/Apple), o, and " "f keys all together. After a few seconds you will be " "presented with the Open Firmware prompt. 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:2438 #, no-c-format msgid "Booting from USB memory stick" msgstr "" #. Tag: para #: boot-installer.xml:2439 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" #. Tag: para #: boot-installer.xml:2445 #, 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. To get to the prompt, hold down " "Command Option o f all together while booting (see )." msgstr "" #. Tag: para #: boot-installer.xml:2457 #, no-c-format msgid "" "You will need to work out where the USB storage device appears in the device " "tree, since at the moment 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:2469 #, 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:2483 #, 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 "" #. Tag: para #: boot-installer.xml:2489 #, no-c-format msgid "" "This boot method is new, and may be difficult to get to work on some " "NewWorld systems. If you have problems, please file an installation report, " "as explained in ." msgstr "" #. Tag: para #: boot-installer.xml:2522 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" #. Tag: para #: boot-installer.xml:2526 #, no-c-format msgid "" "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " "monitor (see ) and use the command " "boot enet:0. PReP and CHRP boxes may have different ways " "of addressing the network. On a PReP machine, you should try boot " "server_ipaddr,file," "client_ipaddr." msgstr "" #. Tag: para #: boot-installer.xml:2541 #, no-c-format msgid "" "Booting from floppies is supported for &arch-title;, although it is " "generally only applicable for OldWorld systems. NewWorld systems are not " "equipped with floppy drives, and attached USB floppy drives are not " "supported for booting." msgstr "" #. Tag: para #: boot-installer.xml:2553 #, 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 "" #. Tag: para #: boot-installer.xml:2559 #, no-c-format msgid "" "For those not familiar with Macintosh floppy operations: a floppy placed in " "the machine prior to boot will be the first priority for the system to boot " "from. A floppy without a valid boot system will be ejected, and the machine " "will then check for bootable hard disk partitions." msgstr "" #. Tag: para #: boot-installer.xml:2566 #, 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 "" #. Tag: title #: boot-installer.xml:2577 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "" #. Tag: para #: boot-installer.xml:2578 #, no-c-format msgid "" "Many older Apple monitors used a 640x480 67Hz mode. If your video appears " "skewed on an older Apple monitor, try appending the boot argument " "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: para #: boot-installer.xml:2618 #, no-c-format msgid "" "On machines with OpenBoot, simply enter the boot monitor on the machine " "which is being installed (see ). 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. Some older " "OpenBoot revisions require using the device name, such as boot le" "(); these probably don't support BOOTP nor DHCP." msgstr "" #. Tag: para #: boot-installer.xml:2674 #, 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). You may have to use the actual " "device name for older OpenBoot versions that don't support this special " "command. Note that some problems have been reported on Sun4m (e.g., Sparc " "10s and Sparc 20s) systems booting from CD-ROM." msgstr "" #. Tag: para #: boot-installer.xml:2689 #, no-c-format msgid "" "To boot from floppy on a Sparc, use \n" "Stop-A -> OpenBoot: \"boot floppy\"\n" " Be warned that the newer Sun4u (ultra) " "architecture does not support floppy booting. A typical error message is " "Bad magic number in disk label - Can't open disk label " "package. Furthermore, a number of Sun4c models (such as the " "IPX) do not support the compressed images found on the disks, so also are " "not supported." msgstr "" #. Tag: para #: boot-installer.xml:2701 #, no-c-format msgid "" "Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from " "booting (instead of not supporting booting at all). The appropriate OBP " "update can be downloaded as product ID 106121 from ." msgstr "" #. Tag: para #: boot-installer.xml:2708 #, no-c-format msgid "" "If you are booting from the floppy, and you see messages such as " "\n" "Fatal error: Cannot read partition\n" "Illegal or malformed device name\n" " then it is possible that floppy booting is " "simply not supported on your machine." msgstr "" #. Tag: title #: boot-installer.xml:2720 #, no-c-format msgid "IDPROM Messages" msgstr "" #. Tag: para #: boot-installer.xml:2721 #, 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 "" #. Tag: para #: boot-installer.xml:2740 #, no-c-format msgid "" "Boot parameters are Linux kernel parameters which are generally used to make " "sure that peripherals are dealt with properly. For the most part, the kernel " "can auto-detect information about your peripherals. However, in some cases " "you'll have to help the kernel a bit." msgstr "" #. Tag: para #: boot-installer.xml:2747 #, no-c-format msgid "" "If this is the first time you're booting the system, try the default boot " "parameters (i.e., don't try setting parameters) and see if it works " "correctly. It probably will. If not, you can reboot later and look for any " "special parameters that inform the system about your hardware." msgstr "" #. Tag: para #: boot-installer.xml:2754 #, 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 "" #. Tag: para #: boot-installer.xml:2763 #, no-c-format 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 "" #. Tag: para #: boot-installer.xml:2779 #, 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." msgstr "" #. Tag: para #: boot-installer.xml:2792 #, 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 "" #. Tag: title #: boot-installer.xml:2803 #, no-c-format msgid "Debian Installer Parameters" msgstr "" #. Tag: para #: boot-installer.xml:2804 #, no-c-format msgid "" "The installation system recognizes a few additional boot " "parameters Note that the 2.4 kernel accepts a maximum of 8 " "command line options and 8 environment options (including any options added " "by default for the installer). If these numbers are exceeded, 2.4 kernels " "will drop any excess options. With kernel 2.6.9 or newer, you can use 32 " "command line options and 32 environment options. which " "may be useful." msgstr "" #. Tag: term #: boot-installer.xml:2824 #, no-c-format msgid "debconf/priority" msgstr "" #. Tag: para #: boot-installer.xml:2825 #, no-c-format msgid "" "This parameter sets the lowest priority of messages to be displayed. Short " "form: priority" msgstr "" #. Tag: para #: boot-installer.xml:2830 #, 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 "" #. Tag: para #: boot-installer.xml:2837 #, 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 "" #. Tag: term #: boot-installer.xml:2851 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para #: boot-installer.xml:2852 #, no-c-format msgid "" "This boot parameter controls the type of user interface used for the " "installer. The current possible parameter settings are: " " DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " "DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=slang DEBIAN_FRONTEND=ncurses " "DEBIAN_FRONTEND=bogl DEBIAN_FRONTEND=gtk " " DEBIAN_FRONTEND=corba The default front end 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, so this is not very useful right now." msgstr "" #. Tag: term #: boot-installer.xml:2888 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para #: boot-installer.xml:2889 #, no-c-format msgid "" "Setting this boot parameter to 2 will cause the installer's boot process to " "be verbosely logged. Setting it to 3 makes debug shells available at " "strategic points in the boot process. (Exit the shells to continue the boot " "process.)" msgstr "" #. Tag: userinput #: boot-installer.xml:2898 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para #: boot-installer.xml:2899 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput #: boot-installer.xml:2903 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para #: boot-installer.xml:2904 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput #: boot-installer.xml:2908 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para #: boot-installer.xml:2909 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput #: boot-installer.xml:2913 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para #: boot-installer.xml:2914 #, no-c-format msgid "" "Shells are run at various points in the boot process to allow detailed " "debugging. Exit the shell to continue the boot." msgstr "" #. Tag: term #: boot-installer.xml:2928 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para #: boot-installer.xml:2929 #, no-c-format msgid "" "The value of the parameter is the path to the device to load the Debian " "installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" msgstr "" #. Tag: para #: boot-installer.xml:2935 #, no-c-format msgid "" "The boot floppy, which normally scans all floppies it can to find the root " "floppy, can be overridden by this parameter to only look at the one device." msgstr "" #. Tag: term #: boot-installer.xml:2945 #, no-c-format msgid "debian-installer/framebuffer" msgstr "" #. Tag: para #: boot-installer.xml:2946 #, no-c-format msgid "" "Some architectures use the kernel framebuffer to offer installation in a " "number of languages. If framebuffer causes a problem on your system you can " "disable the feature by the parameter debian-installer/" "framebuffer=false, or fb=false for short. " "Problem symptoms are error messages about bterm or bogl, a blank screen, or " "a freeze within a few minutes after starting the install." msgstr "" #. Tag: para #: boot-installer.xml:2956 #, no-c-format msgid "" "The 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 "" #. Tag: para #: boot-installer.xml:2962 #, no-c-format msgid "Such problems have been reported on the Amiga 1200 and SE/30." msgstr "" #. Tag: para #: boot-installer.xml:2966 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para #: boot-installer.xml:2970 #, 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 "" #. Tag: term #: boot-installer.xml:2984 #, no-c-format msgid "debian-installer/theme" msgstr "" #. Tag: para #: boot-installer.xml:2985 #, no-c-format msgid "" "A theme determines how the user interface of the installer looks (colors, " "icons, etc.). What themes are available differs per frontend. Currently both " "the newt and gtk frontends only have a dark theme that was " "designed for visually impaired users. Set the theme by booting with " "parameter debian-installer/theme=dark or theme=dark." msgstr "" #. Tag: term #: boot-installer.xml:2998 #, no-c-format msgid "debian-installer/probe/usb" msgstr "" #. Tag: para #: boot-installer.xml:2999 #, no-c-format msgid "" "Set to false to prevent probing for USB on boot, if " "that causes problems." msgstr "" #. Tag: term #: boot-installer.xml:3008 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" #. Tag: para #: boot-installer.xml:3009 #, no-c-format msgid "" "By default, the &d-i; automatically probes for network configuration via " "DHCP. If the probe succeeds, you won't have a chance to review and change " "the obtained settings. You can get to the manual network setup only in case " "the DHCP probe fails." msgstr "" #. Tag: para #: boot-installer.xml:3016 #, no-c-format msgid "" "If you have a DHCP server on your local network, but want to avoid it " "because e.g. it gives wrong answers, you can use the parameter " "netcfg/disable_dhcp=true to prevent configuring the " "network with DHCP and to enter the information manually." msgstr "" #. Tag: term #: boot-installer.xml:3027 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para #: boot-installer.xml:3028 #, 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 "" #. Tag: term #: boot-installer.xml:3038 #, no-c-format msgid "preseed/url" msgstr "" #. Tag: para #: boot-installer.xml:3039 #, no-c-format msgid "" "Specify the url to a preconfiguration file to download and use in automating " "the install. See . Short form: " "url" msgstr "" #. Tag: term #: boot-installer.xml:3049 #, no-c-format msgid "preseed/file" msgstr "" #. Tag: para #: boot-installer.xml:3050 #, no-c-format msgid "" "Specify the path to a preconfiguration file to load to automating the " "install. See . Short form: " "file" msgstr "" #. Tag: term #: boot-installer.xml:3060 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para #: boot-installer.xml:3061 #, no-c-format msgid "" "By default, before rebooting, &d-i; automatically ejects the optical media " "used during the installation. This can be unnecessary if the system does not " "automatically boot off the CD. In some cases it may even be undesirable, for " "example if the optical drive cannot reinsert the media itself and the user " "is not there to do it manually. Many slot loading, slim-line, and caddy " "style drives cannot reload media automatically." msgstr "" #. Tag: para #: boot-installer.xml:3070 #, 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 "" #. Tag: term #: boot-installer.xml:3081 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para #: boot-installer.xml:3082 #, no-c-format msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." msgstr "" #. Tag: term #: boot-installer.xml:3090 #, no-c-format msgid "directfb/hw-accel" msgstr "" #. Tag: para #: boot-installer.xml:3091 #, no-c-format msgid "" "For the gtk frontend (graphical installer), hardware acceleration in " "directfb is disabled by default. To enable it, set this parameter to " "true when booting the installer." msgstr "" #. Tag: term #: boot-installer.xml:3101 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para #: boot-installer.xml:3102 #, no-c-format msgid "" "Set to true to enter rescue mode rather than " "performing a normal installation. See ." msgstr "" #. Tag: title #: boot-installer.xml:3120 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "Hibák elhárítása a telepítő folyamat során" #. Tag: title #: boot-installer.xml:3125 #, no-c-format msgid "Floppy Disk Reliability" msgstr "Flopi lemezek megbízhatósága" #. Tag: para #: boot-installer.xml:3127 #, no-c-format msgid "" "The biggest problem for people using floppy disks to install Debian seems to " "be floppy disk reliability." msgstr "" "A Debian rendszert flopiról telepítők számára a legnagyobb gond a flopi " "megbízhatatlansága." #. Tag: para #: boot-installer.xml:3132 #, no-c-format msgid "" "The boot floppy is the floppy with the worst problems, because it is read by " "the hardware directly, before Linux boots. Often, the hardware doesn't read " "as reliably as the Linux floppy disk driver, and may just stop without " "printing an error message if it reads incorrect data. There can also be " "failures in the Driver Floppies most of which indicate themselves with a " "flood of messages about disk I/O errors." msgstr "" "Az indító flopival van a legtöbb gond, mert azt a gép közvetlenül olvassa a " "Linux indítása előtt. A gép maga általában sokkal megbízhatatlanabbul " "olvassa a flopit, mint a Linux flopi meghajtó és még üzenet nélkül is " "leállhat hibás adatok olvasásakor. Nagyon rossz az is, mikor a meghajtó " "flopikkal van gond, melyek ezt tömeges lemez I/O hiba üzenet jelzik." #. Tag: para #: boot-installer.xml:3141 #, no-c-format msgid "" "If you are having the installation stall at a particular floppy, the first " "thing you should do is re-download the floppy disk image and write it to a " "different floppy. Simply reformatting the old floppy " "may not be sufficient, even if it appears that the floppy was reformatted " "and written with no errors. It is sometimes useful to try writing the floppy " "on a different system." msgstr "" "Ha a telepítés elakad egy flopinál, legelőször töltsd le újra a flopi lemez " "képet és írd egy másik flopira. A régi flopi " "újraformázása általában akkor sem elég, ha nem írt hibát. Sok esetben csak " "az oldja meg, ha egy másik gépen írod meg." #. Tag: para #: boot-installer.xml:3151 #, no-c-format msgid "" "One user reports he had to write the images to floppy 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:3157 #, no-c-format msgid "" "Other users have reported that simply rebooting a few times with the same " "floppy in the floppy drive can lead to a successful boot. This is all due to " "buggy hardware or firmware floppy drivers." msgstr "" "Sokak gépe pedig csak többszöri indítás után tudta pontosan elolvasni a " "flopit és így ez csak ekkor tudott sikeresen elindulni. Ezt mind hibás " "hardver vagy firmware flopi meghajtók okozzák." #. Tag: title #: boot-installer.xml:3166 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para #: boot-installer.xml:3168 #, no-c-format msgid "" "If you have problems and the kernel hangs during the boot process, doesn't " "recognize peripherals you actually have, or drives are not recognized " "properly, the first thing to check is the boot parameters, as discussed in " "." msgstr "" #. Tag: para #: boot-installer.xml:3175 #, no-c-format msgid "" "If you are booting with your own kernel instead of the one supplied with the " "installer, be sure that CONFIG_DEVFS is set in your " "kernel. The installer requires CONFIG_DEVFS." msgstr "" #. Tag: para #: boot-installer.xml:3182 #, no-c-format msgid "" "Often, problems can be solved by removing add-ons and peripherals, and then " "trying booting again. Internal modems, sound cards, and " "Plug-n-Play devices can be especially problematic." msgstr "" #. Tag: para #: boot-installer.xml:3188 #, no-c-format msgid "" "If you have a large amount of memory installed in your machine, more than " "512M, and the installer hangs when booting the kernel, you may need to " "include a boot argument to limit the amount of memory the kernel sees, such " "as mem=512m." msgstr "" #. Tag: title #: boot-installer.xml:3199 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para #: boot-installer.xml:3200 #, no-c-format msgid "" "There are some common installation problems that can be solved or avoided by " "passing certain boot parameters to the installer." msgstr "" #. Tag: para #: boot-installer.xml:3205 #, no-c-format 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 "" #. Tag: para #: boot-installer.xml:3211 #, no-c-format msgid "" "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk " "drivers), the IDE drive may not be properly recognized. Again, try it first " "without the parameters and see if the IDE drive is recognized properly. If " "not, determine your drive geometry (cylinders, heads, and sectors), and use " "the parameter hd=cylinders," "heads,sectors." msgstr "" #. Tag: para #: boot-installer.xml:3220 #, no-c-format 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 "" #. Tag: para #: boot-installer.xml:3227 #, no-c-format msgid "" "If your screen begins to show a weird picture while the kernel boots, eg. " "pure white, pure black or colored pixel garbage, your system may contain a " "problematic video card which does not switch to the framebuffer mode " "properly. Then you can use the boot parameter fb=false " "video=vga16:off to disable the framebuffer console. Only the " "English language will be available during the installation due to limited " "console features. See for details." msgstr "" #. Tag: title #: boot-installer.xml:3241 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para #: boot-installer.xml:3242 #, no-c-format msgid "" "Some laptop models produced by Dell are known to crash when PCMCIA device " "detection tries to access some hardware addresses. Other laptops may display " "similar problems. If you experience such a problem and you don't need PCMCIA " "support during the installation, you can disable PCMCIA using the " "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 "" #. Tag: para #: boot-installer.xml:3252 #, no-c-format msgid "" "Alternatively, you can boot the installer in expert mode. You will then be " "asked to enter the resource range options your hardware needs. For example, " "if you have one of the Dell laptops mentioned above, you should enter " "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 "" #. Tag: title #: boot-installer.xml:3269 #, no-c-format msgid "System Freeze while Loading the USB Modules" msgstr "" #. Tag: para #: boot-installer.xml:3270 #, no-c-format msgid "" "The kernel normally tries to install USB modules and the USB keyboard driver " "in order to support some non-standard USB keyboards. However, there are some " "broken USB systems where the driver hangs on loading. A possible workaround " "may be disabling the USB controller in your mainboard BIOS setup. Another " "option is passing the debian-installer/probe/usb=false parameter at the boot prompt, which will prevent the modules from " "being loaded." msgstr "" #. Tag: title #: boot-installer.xml:3284 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para #: boot-installer.xml:3286 #, 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 "" #. Tag: title #: boot-installer.xml:3311 #, no-c-format msgid "Bug Reporter" msgstr "" #. Tag: para #: boot-installer.xml:3312 #, no-c-format msgid "" "If you get through the initial boot phase but cannot complete the install, " "the bug reporter menu choice may be helpful. It lets you store system error " "logs and configuration information from the installer to a floppy, or " "download them in a web browser. This information may provide clues as to " "what went wrong and how to fix it. If you are submitting a bug report you " "may want to attach this information to the bug report." msgstr "" #. Tag: para #: boot-installer.xml:3323 #, 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 "" #. Tag: title #: boot-installer.xml:3334 #, no-c-format msgid "Submitting Installation Reports" msgstr "Telepítő jelentések küldése" #. Tag: para #: boot-installer.xml:3335 #, no-c-format msgid "" "If you still have problems, please submit an installation report. We also " "encourage installation reports to be sent even if the installation is " "successful, so that we can get as much information as possible on the " "largest number of hardware configurations." msgstr "" "Ha még mindig gondjaid vannak, kérjük, küldj telepítő jelentést. Siker " "esetén és kérünk erre, mert így a lehető legtöbb adatot kapjuk a legtöbb " "hardver összeállításról." #. Tag: para #: boot-installer.xml:3342 #, no-c-format msgid "" "If you have a working Debian system, the easiest way to send an installation " "report is to install the installation-report and reportbug packages " "(apt-get install installation-report reportbug) and run " "the command reportbug installation-report." 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 (apt-get " "install installation-report reportbug) és a reportbug " "installation-report parancs futtatása." #. Tag: para #: boot-installer.xml:3349 #, no-c-format msgid "" "Please use this template when filling out installation reports, and file the " "report as a bug report against the 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: <Fill in date and from where you got the image>\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 and lspci -n:\n" "\n" "Base System Installation Checklist:\n" "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" "\n" "Initial boot worked: [ ]\n" "Configure network HW: [ ]\n" "Config network: [ ]\n" "Detect CD: [ ]\n" "Load installer modules: [ ]\n" "Detect hard drives: [ ]\n" "Partition hard drives: [ ]\n" "Create file systems: [ ]\n" "Mount partitions: [ ]\n" "Install base system: [ ]\n" "Install boot loader: [ ]\n" "Reboot: [ ]\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 "" "Használd e sablont a telepítő jelentés kitöltésére, és küldd a jelentést " "hibajegyként a 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: <Kép letöltésének helye és ideje>\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 és lspci -n 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 worked: [ ]\n" "Configure network HW: [ ]\n" "Config network: [ ]\n" "Detect CD: [ ]\n" "Load installer modules: [ ]\n" "Detect hard drives: [ ]\n" "Partition hard drives: [ ]\n" "Create file systems: [ ]\n" "Mount partitions: [ ]\n" "Install base system: [ ]\n" "Install boot loader: [ ]\n" "Reboot: [ ]\n" "\n" "Comments/Problems:\n" "\n" "<Telepítés leírása prózaian és bármilyen gondolat, mejegyzés\n" " és ötlet a kezdeti telepítés során.>\n" " 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."