From 69a3d267a0cb4d2b49fd6e6d0547450e01c54aa2 Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Fri, 10 Nov 2006 03:20:49 +0000 Subject: Update of POT and PO files for the manual --- po/el/boot-installer.po | 33 +- po/fi/boot-installer.po | 1628 ++++++++++++++++---- po/hu/boot-installer.po | 2654 ++++++++++++++++++++++++------- po/ko/boot-installer.po | 31 +- po/pot/boot-installer.pot | 10 +- po/pt/boot-installer.po | 62 +- po/ru/boot-installer.po | 123 +- po/sv/boot-installer.po | 3682 +++++++++++++++++++++++++++++++++++--------- po/vi/boot-installer.po | 33 +- po/zh_CN/boot-installer.po | 39 +- po/zh_TW/boot-installer.po | 31 +- 11 files changed, 6628 insertions(+), 1698 deletions(-) (limited to 'po') diff --git a/po/el/boot-installer.po b/po/el/boot-installer.po index 63fcffdd0..acc04d1c5 100644 --- a/po/el/boot-installer.po +++ b/po/el/boot-installer.po @@ -16,7 +16,7 @@ msgid "" msgstr "" "Project-Id-Version: boot-installer\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-11-04 17:26+0000\n" +"POT-Creation-Date: 2006-11-10 03:17+0000\n" "PO-Revision-Date: 2006-10-16 16:14+0300\n" "Last-Translator: QUAD-nrg.net \n" "Language-Team: Greek \n" @@ -4680,13 +4680,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:3363 -#, no-c-format +#, fuzzy, 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 " +"failures in the driver floppies, most of which indicate themselves with a " "flood of messages about disk I/O errors." msgstr "" "Η δισκέτα εκκίνησης είναι η δισκέτα που παρουσιάζει τα χειρότερα προβλήματα, " @@ -4703,10 +4703,11 @@ msgstr "" #, fuzzy, no-c-format msgid "" "If you are having the installation stall at a particular floppy, the first " -"thing you should 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." +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. Simply reformatting the old " +"floppy may not be sufficient, even if it appears that the floppy was " +"reformatted and written with no errors. It is sometimes useful to try " +"writing the floppy on a different system." msgstr "" "Εάν βρεθείτε αντιμέτωποι με σταμάτημα της εγκατάστασης σε μια συγκεκριμένη " "δισκέτα, το πρώτο πράγμα που πρέπει να κάνετε είναι να κατεβάσετε ξανά το " @@ -4720,15 +4721,6 @@ msgstr "" #: boot-installer.xml:3381 #, no-c-format msgid "" -"Normally you should not have download a floppy image again, but if you are " -"experiencing problems it is always useful to verify that the images were " -"downloaded correctly by verifying their md5sums." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3387 -#, 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." @@ -4737,6 +4729,15 @@ msgstr "" "τρεις φορες πριν να λειτουργησει καποια απ'αυτες , και " "επειτα ολα προχωρησαν κανονικα με την τριτη δισκετα." +#. Tag: para +#: boot-installer.xml:3387 +#, no-c-format +msgid "" +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." +msgstr "" + #. Tag: para #: boot-installer.xml:3393 #, no-c-format diff --git a/po/fi/boot-installer.po b/po/fi/boot-installer.po index ee6df4218..5ff93f686 100644 --- a/po/fi/boot-installer.po +++ b/po/fi/boot-installer.po @@ -5,7 +5,7 @@ msgid "" msgstr "" "Project-Id-Version: Debian Installer boot-installer\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-11-04 17:26+0000\n" +"POT-Creation-Date: 2006-11-10 03:17+0000\n" "PO-Revision-Date: 2006-11-09 16:42+0200\n" "Last-Translator: Tapio Lehtonen \n" "Language-Team: Finnish \n" @@ -126,7 +126,16 @@ msgid "" "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 "GNU/Linux on Alphan ainoa käyttöjärjestelmä joka voidaan käynnistää molemmista konsolityypeistä, mutta &debian; &release; tukee käynnistämistä vain SRM:ään pohjautuvilla järjestelmillä. Jos käytössä on Alpha johon ei ole saatavilla mitään SRM:n versiota, jos halutaan kaksoiskäynnistää Windows NT:n kanssa, tai jos käynnistyslaite vaatii ARC-konsolin tukea BIOS:n alkuarvojen asettamiseen, ei &debian; &release;:n asenninta voi käyttää. &debian; &release;:aa voidaan silti ajaa noilla järjestelmillä käyttämällä muuta asennustaltiota; esimerkiksi voidaan asentaa Debian Woody MILO:lla ja päivittää." +msgstr "" +"GNU/Linux on Alphan ainoa käyttöjärjestelmä joka voidaan käynnistää " +"molemmista konsolityypeistä, mutta &debian; &release; tukee käynnistämistä " +"vain SRM:ään pohjautuvilla järjestelmillä. Jos käytössä on Alpha johon ei " +"ole saatavilla mitään SRM:n versiota, jos halutaan kaksoiskäynnistää Windows " +"NT:n kanssa, tai jos käynnistyslaite vaatii ARC-konsolin tukea BIOS:n " +"alkuarvojen asettamiseen, ei &debian; &release;:n asenninta voi käyttää. " +"&debian; &release;:aa voidaan silti ajaa noilla järjestelmillä käyttämällä " +"muuta asennustaltiota; esimerkiksi voidaan asentaa Debian Woody MILO:lla ja " +"päivittää." #. Tag: para #: boot-installer.xml:87 @@ -635,7 +644,15 @@ msgid "" "replaceable> 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 "ARC-konsolilta käynnistetään rompulta etsimällä suoritinarkkitehtuurin koodinimi (katso ), määrittämällä käynnistyslataimeksi \\milo\\linload.exe ja OS Path:in arvoksi \"OS Selection Setup\"-valikossa \\milo\\subarch (missä subarch on asiaankuuluva suoritinarkkitehtuurin nimi). Ruffianit ovat poikkeus: käynnistyslataimena on käytettävä \\milo\\ldmilo.exe." +msgstr "" +"ARC-konsolilta käynnistetään rompulta etsimällä suoritinarkkitehtuurin " +"koodinimi (katso ), määrittämällä " +"käynnistyslataimeksi \\milo\\linload.exe ja OS Path:in " +"arvoksi \"OS Selection Setup\"-valikossa \\milo" +"\\subarch (missä subarch on asiaankuuluva suoritinarkkitehtuurin nimi). Ruffianit ovat " +"poikkeus: käynnistyslataimena on käytettävä \\milo\\ldmilo.exe." #. Tag: title #: boot-installer.xml:358 @@ -660,11 +677,18 @@ msgid "" "command>. If everything works OK, you will eventually see the Linux kernel " "boot." msgstr "" -"Kirjoita SRM-kehotteeseen (>>>) seuraava komento:\n" +"Kirjoita SRM-kehotteeseen (>>>) seuraava komento:" +"\n" ">>> boot dva0 -flags 0\n" -" mahdollisesti korvaten dva0 oikealla laitenimellä. Tavallisesti dva0 on levyke; kirjoittamalla \n" +" mahdollisesti korvaten dva0 " +"oikealla laitenimellä. Tavallisesti dva0 on levyke; " +"kirjoittamalla \n" ">>> show dev\n" -" näkee laiteluettelon (esim. jos halutaan käynnistää rompulta). Huomaa, että käynnistettäessä MILO:n avulla, parametri -flags ohitetaan joten voidaan kirjoittaa vain boot dva0. Jos kaikki toimii kuten pitää, käynnistyy Linux-ydin hetken kuluttua." +" näkee laiteluettelon (esim. jos halutaan " +"käynnistää rompulta). Huomaa, että käynnistettäessä MILO:n avulla, parametri " +"-flags ohitetaan joten voidaan kirjoittaa vain " +"boot dva0. Jos kaikki toimii kuten pitää, käynnistyy " +"Linux-ydin hetken kuluttua." #. Tag: para #: boot-installer.xml:376 @@ -679,9 +703,14 @@ msgid "" "boot device name for fd0, and the desired kernel " "parameters for arguments." msgstr "" -"Jos käynnistettäessä halutaan antaa ytimen parametreja aboot:n kautta, käytetään seuraavaa komentoa:\n" -">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 load_ramdisk=1 arguments\"\n" -" (kaikki kirjoitetaan samalle riville), korvaten, jos tarpeen, dva0:n tilalle oikea SRM:n laitenimi, fd0:n tilalle Linuxin käynnistyslaite ja arguments:in tilalle halutut ytimen parametrit." +"Jos käynnistettäessä halutaan antaa ytimen parametreja aboot:n kautta, käytetään seuraavaa komentoa:\n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +" (kaikki kirjoitetaan samalle riville), korvaten, " +"jos tarpeen, dva0:n tilalle oikea SRM:n laitenimi, " +"fd0:n tilalle Linuxin käynnistyslaite ja " +"arguments:in tilalle halutut ytimen parametrit." #. Tag: para #: boot-installer.xml:388 @@ -690,7 +719,10 @@ 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 "Jos MILO:n avulla käynnistettäessä halutaan antaa ytimen parametreja, on käynnistys keskeytettävä kun on päästy MILO:on. Katso ." +msgstr "" +"Jos MILO:n avulla käynnistettäessä halutaan antaa ytimen " +"parametreja, on käynnistys keskeytettävä kun on päästy MILO:on. Katso ." #. Tag: title #: boot-installer.xml:398 @@ -705,7 +737,10 @@ 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 "OS Selection -valikossa, aseta käynnistyslataimeksi linload.exe ja \"OS Path\" arvoon milo. Käynnistä tällä uudella valikon kohdalla." +msgstr "" +"OS Selection -valikossa, aseta käynnistyslataimeksi linload.exe ja \"OS Path\" arvoon milo. Käynnistä tällä " +"uudella valikon kohdalla." #. Tag: title #: boot-installer.xml:409 @@ -720,7 +755,10 @@ 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 "Käynnistystaltiolla olevan MILO:n asetukset on tehty jatkamaan suoraan Linuxiin automaattisesti. Jos tätä ei haluta, riittää painaa välilyöntiä MILO:n lähtölaskennan aikana." +msgstr "" +"Käynnistystaltiolla olevan MILO:n asetukset on tehty jatkamaan suoraan " +"Linuxiin automaattisesti. Jos tätä ei haluta, riittää painaa välilyöntiä " +"MILO:n lähtölaskennan aikana." #. Tag: para #: boot-installer.xml:416 @@ -735,9 +773,15 @@ msgid "" "appropriate device name in Linux notation. The help " "command would give you a brief MILO command reference." msgstr "" -"Haluttaessa määrittää kaikki yksityiskohdat tarkkaan (esimerkiksi antaa lisäparametreja), voidaan käyttää tämän tapaista komentoa: \n" -"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" -" Jos käynnistetään muulta laitteelta kuin levyke, kirjoita yllä olevassa esimerkissä fd0:n tilalle oikean laitteen nimi Linuxin merkintätavalla. Komennolla help näkee lyhyen MILO:n komentojen luettelon." +"Haluttaessa määrittää kaikki yksityiskohdat tarkkaan (esimerkiksi antaa " +"lisäparametreja), voidaan käyttää tämän tapaista komentoa: " +"\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." +" 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" +"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." +" 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 @@ -538,37 +725,37 @@ msgid "Booting from TFTP" msgstr "Indítás TFTP segítségével" #. Tag: para -#: boot-installer.xml:441 -#: boot-installer.xml:1003 -#: boot-installer.xml:1506 -#: boot-installer.xml:1989 -#: boot-installer.xml:2504 -#: boot-installer.xml:2600 +#: boot-installer.xml:441 boot-installer.xml:1003 boot-installer.xml:1506 +#: boot-installer.xml:1989 boot-installer.xml:2504 boot-installer.xml:2600 #, no-c-format -msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)." -msgstr "A hálózati indítás egy hálózati kapcsolatot és egy TFTP hálózati indító kiszolgálót igényel (DHCP, RARP vagy BOOTP)." +msgid "" +"Booting from the network requires that you have a network connection and a " +"TFTP network boot server (DHCP, RARP, or BOOTP)." +msgstr "" +"A hálózati indítás egy hálózati kapcsolatot és egy TFTP hálózati indító " +"kiszolgálót igényel (DHCP, RARP vagy BOOTP)." #. Tag: para -#: boot-installer.xml:446 -#: boot-installer.xml:1008 -#: boot-installer.xml:1511 -#: boot-installer.xml:1994 -#: boot-installer.xml:2509 -#: boot-installer.xml:2605 +#: boot-installer.xml:446 boot-installer.xml:1008 boot-installer.xml:1511 +#: boot-installer.xml:1994 boot-installer.xml:2509 boot-installer.xml:2605 #, no-c-format -msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server." -msgstr "A régebbi rendszerek, például a 715 egy RBOOT kiszolgálót kérhetnek BOOTP helyett." +msgid "" +"Older systems such as the 715 might require the use of an RBOOT server " +"instead of a BOOTP server." +msgstr "" +"A régebbi rendszerek, például a 715 egy RBOOT kiszolgálót kérhetnek BOOTP " +"helyett." #. Tag: para -#: boot-installer.xml:451 -#: boot-installer.xml:1013 -#: boot-installer.xml:1516 -#: boot-installer.xml:1999 -#: boot-installer.xml:2514 -#: boot-installer.xml:2610 +#: boot-installer.xml:451 boot-installer.xml:1013 boot-installer.xml:1516 +#: boot-installer.xml:1999 boot-installer.xml:2514 boot-installer.xml:2610 #, no-c-format -msgid "The installation method to support network booting is described in ." -msgstr "A hálózati indítást támogató telepítő mód leírása itt található: ." +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 @@ -579,40 +766,70 @@ 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ű)." +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 ." +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" +"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" +" 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" +" 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" +" 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" +" 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" +" 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" +" 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." +" In case you run into any problems, a detailed HOWTO is available." msgstr "" #. Tag: title @@ -624,7 +841,9 @@ msgstr "" #. Tag: para #: boot-installer.xml:530 #, no-c-format -msgid "On CATS machines, use boot de0: or similar at the Cyclone prompt." +msgid "" +"On CATS machines, use boot de0: or similar at the Cyclone " +"prompt." msgstr "" #. Tag: title @@ -634,54 +853,75 @@ msgid "Booting from CD-ROM" msgstr "Indítás CD-ROM lemezről" #. Tag: para -#: boot-installer.xml:546 -#: boot-installer.xml:716 -#: boot-installer.xml:1125 -#: boot-installer.xml:1946 -#: boot-installer.xml:2286 -#: boot-installer.xml:2640 +#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1125 +#: boot-installer.xml:1946 boot-installer.xml:2286 boot-installer.xml:2640 #, no-c-format -msgid "The easiest route for most people will be to use a set of Debian CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply 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." +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 +#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1136 +#: boot-installer.xml:1957 boot-installer.xml:2297 boot-installer.xml:2651 #, no-c-format -msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you." -msgstr "Egyes CD-eszközök különleges meghajtókat igényelnek és elérhetetlenek lehetnek a telepítő első lépéseiben. Ha a CD-lemezről indítás szokásos módja nem működik a gépeden, nézd át újra e fejezetet és olvasd el az eltérő kernelekről és telepítő módokról szóló részeket, mely megoldja ezt." +msgid "" +"Note that certain CD drives may require special drivers, and thus be " +"inaccessible in the early installation stages. If it turns out the standard " +"way of booting off a CD doesn't work for your hardware, revisit this chapter " +"and read about alternate kernels and installation methods which may work for " +"you." +msgstr "" +"Egyes CD-eszközök különleges meghajtókat igényelnek és elérhetetlenek " +"lehetnek a telepítő első lépéseiben. Ha a CD-lemezről indítás szokásos módja " +"nem működik a gépeden, nézd át újra e fejezetet és olvasd el az eltérő " +"kernelekről és telepítő módokról szóló részeket, mely megoldja ezt." #. Tag: para -#: boot-installer.xml:565 -#: boot-installer.xml:735 -#: boot-installer.xml:1144 -#: boot-installer.xml:1965 -#: boot-installer.xml:2305 -#: boot-installer.xml:2659 +#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1144 +#: boot-installer.xml:1965 boot-installer.xml:2305 boot-installer.xml:2659 #, no-c-format -msgid "Even if you cannot boot from CD-ROM, you can probably install the Debian system components and any packages you want from CD-ROM. Simply boot using a different media, such as floppies. When it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive." -msgstr "Még abban az esetben is, ha nem tudsz CD-ROM lemezről indítani, valószínűleg képes leszel a Debian rendszer összetevőit és a kívánt csomagokat telepíteni ezekről. Egyszerűen indíts más médiumról, például flopiról. Az operációs rendszer, alaprendszer és tetszőleges további csomagok telepítésekor a telepítő rendszert a CD-ROM meghajtóra irányíthatod." +msgid "" +"Even if you cannot boot from CD-ROM, you can probably install the Debian " +"system components and any packages you want from CD-ROM. Simply boot using a " +"different media, such as floppies. When it's time to install the operating " +"system, base system, and any additional packages, point the installation " +"system at the CD-ROM drive." +msgstr "" +"Még abban az esetben is, ha nem tudsz CD-ROM lemezről indítani, valószínűleg " +"képes leszel a Debian rendszer összetevőit és a kívánt csomagokat telepíteni " +"ezekről. Egyszerűen indíts más médiumról, például flopiról. Az operációs " +"rendszer, alaprendszer és tetszőleges további csomagok telepítésekor a " +"telepítő rendszert a CD-ROM meghajtóra irányíthatod." #. Tag: para -#: boot-installer.xml:573 -#: boot-installer.xml:743 -#: boot-installer.xml:1152 -#: boot-installer.xml:1973 -#: boot-installer.xml:2313 -#: boot-installer.xml:2667 +#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1152 +#: boot-installer.xml:1973 boot-installer.xml:2313 boot-installer.xml:2667 #, no-c-format -msgid "If you have problems booting, see ." -msgstr "Ha gondjaid vannak ez indítással, lásd az részt." +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" +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 @@ -692,13 +932,20 @@ msgstr "" #. Tag: para #: boot-installer.xml:595 #, no-c-format -msgid "There is an increasing number of consumer devices that directly boot from a flash chip on the device. The installer can be written to flash so it will automatically start when you reboot your machines." +msgid "" +"There is an increasing number of consumer devices that directly boot from a " +"flash chip on the device. The installer can be written to flash so it will " +"automatically start when you reboot your machines." msgstr "" #. Tag: para #: boot-installer.xml:601 #, no-c-format -msgid "In many cases, changing the firmware of an embedded device voids your warranty. Sometimes you are also not able to recover your device if there are problems during the flashing process. Therefore, please take care and follow the steps precisely." +msgid "" +"In many cases, changing the firmware of an embedded device voids your " +"warranty. Sometimes you are also not able to recover your device if there " +"are problems during the flashing process. Therefore, please take care and " +"follow the steps precisely." msgstr "" #. Tag: title @@ -722,7 +969,12 @@ 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." +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 @@ -735,9 +987,29 @@ msgstr "" #: 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" +"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." +" 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 @@ -749,15 +1021,15 @@ msgstr "" #. Tag: para #: boot-installer.xml:694 #, no-c-format -msgid "There is a tool for Windows to upgrade the firmware via the network." +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 +#: 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" @@ -765,32 +1037,71 @@ 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" +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." +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." +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." +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:" +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 @@ -811,20 +1122,36 @@ msgstr "" #. 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." +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" +"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" +"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" @@ -833,8 +1160,14 @@ msgstr "" #. 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." +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 @@ -845,60 +1178,119 @@ 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." +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:939 boot-installer.xml:2046 boot-installer.xml:2540 #: boot-installer.xml:2688 #, no-c-format msgid "Booting from Floppies" msgstr "Indítás flopikról" #. Tag: para -#: boot-installer.xml:940 -#: boot-installer.xml:2548 +#: boot-installer.xml:940 boot-installer.xml:2548 #, no-c-format -msgid "You will have already downloaded the floppy images you needed and created floppies from the images in ." -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." +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." +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 #, 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." +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." #. 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." +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." +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ó." +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." +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 @@ -915,8 +1307,16 @@ 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." +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 @@ -927,14 +1327,20 @@ msgstr "NIC hálózati indító ROM-mal" #. Tag: para #: boot-installer.xml:1040 #, no-c-format -msgid "It could be that your Network Interface Card provides TFTP boot functionality." +msgid "" +"It could be that your Network Interface Card provides TFTP boot " +"functionality." msgstr "Lehet, hogy hálózati csatoló kártyád TFTP indítást kínál." #. 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 "Tudasd velünk (&email-debian-boot-list;) hogyan kezelted. Hivatkozz e dokumentumra." +msgid "" +"Let us (&email-debian-boot-list;) know how did you manage it. " +"Please refer to this document." +msgstr "" +"Tudasd velünk (&email-debian-boot-list;) hogyan kezelted. " +"Hivatkozz e dokumentumra." #. Tag: title #: boot-installer.xml:1053 @@ -945,8 +1351,12 @@ msgstr "Etherboot" #. Tag: para #: boot-installer.xml:1054 #, no-c-format -msgid "The etherboot project provides bootdiskettes and even bootroms that do a TFTPboot." -msgstr "Az etherboot project TFTP indítást adó indító lemezeket és indító romokat ad." +msgid "" +"The etherboot project " +"provides bootdiskettes and even bootroms that do a TFTPboot." +msgstr "" +"Az etherboot project TFTP " +"indítást adó indító lemezeket és indító romokat ad." #. Tag: title #: boot-installer.xml:1063 @@ -958,25 +1368,69 @@ msgstr "Az indító jel" #: 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" +"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." +" At the boot prompt you can either just press " +"&enterkey; to boot the installer with default options or enter a specific " +"boot method and, optionally, boot parameters." msgstr "" -"A telepítő indulásakor egy barátságos grafikus képernyőt látsz a Debian logóval és az indító jellel: \n" +"A telepítő indulásakor egy barátságos grafikus képernyőt látsz a Debian " +"logóval és az indító jellel: \n" "Press F1 for help, or ENTER to boot:\n" -" Az indító jelnél leütheted az &enterkey; billentyűt a telepítő alap lehetőségeivel indításhoz vagy beírhatsz egy adott indító módot és, tetszőlegesen, indító paramétereket." +" Az indító jelnél leütheted az &enterkey; " +"billentyűt a telepítő alap lehetőségeivel indításhoz vagy beírhatsz egy " +"adott indító módot és, tetszőlegesen, indító paramétereket." #. Tag: para #: boot-installer.xml: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 "Az elérhető indító módok és paraméterek, melyek hasznosak lehetnek az F2 és F8 közti billentyűk leütésével érhetők el. Ha paramétert adsz az indító parancs sorhoz, írd be az indító módot (az alap a linux) és egy szóközt az 1. paraméter előtt (például linux fb=false)." +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 "" +"Az elérhető indító módok és paraméterek, melyek hasznosak lehetnek az " +"F2 és F8 közti billentyűk leütésével " +"érhetők el. Ha paramétert adsz az indító parancs sorhoz, írd be az indító " +"módot (az alap a linux) és egy szóközt az 1. " +"paraméter előtt (például linux fb=false)." #. 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 "Ha a rendszert távoli kezelő eszközön át telepíted, mely szöveges felületet ad a VGA konzolhoz, talán nem látod a kezdő grafikus üdvözlő képernyőt a telepítő indításakor és az indító jelet. Ezek közütt van a Compaq's integrated Lights Out (iLO) és HP's Integrated Remote Assistant (IRA). Vakon nyomd meg az F1 billentyűt Néha ehhez különleges escape sor kell, például IRA esetén Ctrl F , 1. a képernyő átugrásával a súgóra lépéshez. Ezután a leütött billentyűk már a várkozásnak megfelelően megjelennek a beviteli jelnél. A framebuffer tiltásához a telepítéskor a fb=false hozzáadása kell az indító jelnél, ahogy azt a súgó is írja." +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 "" +"Ha a rendszert távoli kezelő eszközön át telepíted, mely szöveges felületet " +"ad a VGA konzolhoz, talán nem látod a kezdő grafikus üdvözlő képernyőt a " +"telepítő indításakor és az indító jelet. Ezek közütt van a Compaq's " +"integrated Lights Out (iLO) és HP's Integrated Remote " +"Assistant (IRA). Vakon nyomd meg az F1 billentyűt " +"Néha ehhez különleges escape sor kell, például IRA esetén " +"Ctrl F , 1. a képernyő átugrásával a súgóra lépéshez. " +"Ezután a leütött billentyűk már a várkozásnak megfelelően megjelennek a " +"beviteli jelnél. A framebuffer tiltásához a telepítéskor a " +"fb=false hozzáadása kell az indító jelnél, ahogy azt " +"a súgó is írja." #. Tag: title #: boot-installer.xml:1160 @@ -987,31 +1441,72 @@ 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." +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." +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." +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." +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." +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 @@ -1023,7 +1518,14 @@ 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." +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 @@ -1035,37 +1537,62 @@ msgstr "" #. Tag: para #: boot-installer.xml:1254 #, no-c-format -msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes its system initialization." +msgid "" +"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " +"display the EFI Boot Manager page and menu after it completes its system " +"initialization." msgstr "" #. Tag: para #: boot-installer.xml:1260 #, no-c-format -msgid "Select Boot Maintenance Menu from the menu with the arrow keys and press ENTER. This will display a new menu." +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." +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." +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." +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." +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 @@ -1077,43 +1604,73 @@ 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:" +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." +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." +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." +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." +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." +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." +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 @@ -1125,31 +1682,57 @@ 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." +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." +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." +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." +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." +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 @@ -1161,49 +1744,85 @@ 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." +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:" +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." +msgid "" +"Select the kernel version and installation mode most appropriate to your " +"needs with the arrow keys." msgstr "" #. Tag: para #: boot-installer.xml:1463 #, no-c-format -msgid "Enter any boot parameters by typing at the keyboard. The text will be displayed directly in the text window. This is where kernel parameters (such as serial console settings) are specified." +msgid "" +"Enter any boot parameters by typing at the keyboard. The text will be " +"displayed directly in the text window. This is where kernel parameters (such " +"as serial console settings) are specified." msgstr "" #. Tag: para #: boot-installer.xml:1470 #, no-c-format -msgid "Press 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." +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." +msgid "" +"Proceed to the next chapter to continue the installation where you will set " +"up the language locale, network, and disk partitions." msgstr "" #. Tag: para #: boot-installer.xml:1490 #, no-c-format -msgid "Booting an IA64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed thru the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive." +msgid "" +"Booting an IA64 system from the network is similar to a CD boot. The only " +"difference is how the installation kernel is loaded. The EFI Boot Manager " +"can load and start programs from a server on the network. Once the " +"installation kernel is loaded and starts, the system install will proceed " +"thru the same steps as the CD install with the exception that the packages " +"of the base install will be loaded from the network rather than the CD drive." msgstr "" #. Tag: para #: boot-installer.xml:1524 #, no-c-format -msgid "Network booting an ia64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver elilo. On the client a new boot option must be defined in the EFI boot manager to enable loading over a network." +msgid "" +"Network booting an ia64 system requires two architecture-specific actions. " +"On the boot server, DHCP and TFTP must be configured to deliver " +"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 @@ -1216,19 +1835,26 @@ msgstr "" #: boot-installer.xml:1536 #, no-c-format msgid "" -"A suitable TFTP entry for network booting an ia64 system looks something like this: \n" +"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." +" 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." +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 @@ -1246,7 +1872,15 @@ 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." +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 @@ -1258,19 +1892,38 @@ 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." +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." +msgid "" +"The boot loader will display its prompt after it has downloaded and " +"processed its configuration file. At this point, the installation proceeds " +"with the same steps as a CD install. Select a boot option as in above and " +"when the kernel has completed installing itself from the network, it will " +"start the Debian Installer." msgstr "" #. Tag: para #: boot-installer.xml:1615 #, no-c-format -msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and the disk partitions." +msgid "" +"Proceed to the next chapter to continue the installation where you will set " +"up the language locale, network, and the disk partitions." msgstr "" #. Tag: title @@ -1282,25 +1935,36 @@ msgstr "" #. Tag: para #: boot-installer.xml:1630 #, no-c-format -msgid "Some &arch-title; subarchs have the option of booting using either a 2.4.x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux kernel. The installer should also require less memory when using a 2.4.x linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses tmpfs." +msgid "" +"Some &arch-title; subarchs have the option of booting using either a 2.4.x " +"or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux " +"kernel. The installer should also require less memory when using a 2.4.x " +"linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses " +"tmpfs." msgstr "" #. Tag: para #: boot-installer.xml:1638 #, no-c-format -msgid "If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; kernel parameter." +msgid "" +"If you are using a 2.2.x linux kernel, then you need to use the " +"&ramdisksize; kernel parameter." msgstr "" #. Tag: para #: boot-installer.xml:1643 #, no-c-format -msgid "Make sure root=/dev/ram is one of your kernel parameters." +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." +msgid "" +"If you're having trouble, check cts's " +"&arch-title; debian-installer FAQ." msgstr "" #. Tag: title @@ -1312,13 +1976,18 @@ 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." +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." +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 @@ -1330,13 +1999,18 @@ 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." +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." +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 @@ -1348,7 +2022,10 @@ 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 )." +msgid "" +"The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." msgstr "" #. Tag: title @@ -1360,13 +2037,24 @@ 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." +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." +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 @@ -1378,7 +2066,11 @@ 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." +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 @@ -1390,7 +2082,10 @@ 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." +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 @@ -1400,29 +2095,43 @@ msgid "Booting from a Hard Disk" msgstr "" #. Tag: para -#: boot-installer.xml:1761 -#: boot-installer.xml:2359 +#: boot-installer.xml:1761 boot-installer.xml:2359 #, no-c-format -msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation." +msgid "" +"Booting from an existing operating system is often a convenient option; for " +"some systems it is the only supported method of installation." msgstr "" #. Tag: para -#: boot-installer.xml:1767 -#: boot-installer.xml:2365 +#: boot-installer.xml:1767 boot-installer.xml:2365 #, no-c-format -msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files in ." +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)." +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." +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 @@ -1434,13 +2143,24 @@ 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." +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 ." +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 @@ -1452,13 +2172,24 @@ 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." +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 ." +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 @@ -1470,37 +2201,73 @@ 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." +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." +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." +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." +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." +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 ." +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 @@ -1518,19 +2285,27 @@ msgstr "" #. Tag: para #: boot-installer.xml:1923 #, no-c-format -msgid "The installation program should start automatically, so you can continue below at ." +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." +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:" +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 @@ -1554,24 +2329,29 @@ 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;." +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." +msgid "" +"For most &arch-title; architectures, booting from a local filesystem is the " +"recommended method." msgstr "" #. Tag: para #: boot-installer.xml:2052 #, no-c-format -msgid "Booting from the boot floppy is supported only for Atari and VME (with a SCSI floppy drive on VME) at this time." +msgid "" +"Booting from the boot floppy is supported only for Atari and VME (with a " +"SCSI floppy drive on VME) at this time." msgstr "" #. Tag: title -#: boot-installer.xml:2068 -#: boot-installer.xml:2115 +#: boot-installer.xml:2068 boot-installer.xml:2115 #, no-c-format msgid "SGI TFTP Booting" msgstr "" @@ -1582,36 +2362,42 @@ msgstr "" 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" +" 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:2088 boot-installer.xml:2137 boot-installer.xml:2192 #: boot-installer.xml:2231 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:2089 -#: boot-installer.xml:2193 +#: boot-installer.xml:2089 boot-installer.xml:2193 #, no-c-format msgid "" -"On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load the SiByl boot loader via TFTP which will then load and start the Debian installer. In most cases, you will first obtain an IP address via DHCP but it is also possible to configure a static address. In order to use DHCP, you can enter the following command on the CFE prompt: \n" +"On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load " +"the SiByl boot loader via TFTP which will then load and start the Debian " +"installer. In most cases, you will first obtain an IP address via DHCP but " +"it is also possible to configure a static address. In order to use DHCP, you " +"can enter the following command on the CFE prompt: " +"\n" "ifconfig eth0 -auto\n" -" Once you have obtained an IP address, you can load SiByl with the following command: \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." +" You need to substitute the IP address listed in " +"this example with either the name or the IP address of your TFTP server. " +"Once you issue this command, the installer will be loaded automatically." msgstr "" #. Tag: title -#: boot-installer.xml:2112 -#: boot-installer.xml:2216 -#: boot-installer.xml:2739 +#: boot-installer.xml:2112 boot-installer.xml:2216 boot-installer.xml:2739 #, no-c-format msgid "Boot Parameters" msgstr "Indító paraméterek" @@ -1619,16 +2405,21 @@ msgstr "Indító paraméterek" #. 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." +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" +"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:" +" Further kernel parameters can be passed via " +"append:" msgstr "" #. Tag: screen @@ -1638,15 +2429,17 @@ msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: para -#: boot-installer.xml:2138 -#: boot-installer.xml:2232 +#: boot-installer.xml:2138 boot-installer.xml:2232 #, no-c-format -msgid "You cannot pass any boot parameters directly from the CFE prompt. Instead, you have to edit the /boot/sibyl.conf file on the TFTP server and add your parameters to the extra_args variable." +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 +#: boot-installer.xml:2157 boot-installer.xml:2219 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "" @@ -1654,25 +2447,43 @@ 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:" +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." +msgid "" +"Via SSH (default): In this case, the installer will configure the network " +"via DHCP and start an SSH server. It will then display a random password and " +"other login information (such as the IP address) on the Cobalt LCD. When you " +"connect to the machine with an SSH client you can start with the " +"installation." msgstr "" #. Tag: para #: boot-installer.xml:2177 #, no-c-format -msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way. This option is not available on Qube 2700 (Qube1) machines since they have no serial port." +msgid "" +"Via serial console: Using a null modem cable, you can connect to the serial " +"port of your Cobalt machine (using 115200 bps) and perform the installation " +"this way. This option is not available on Qube 2700 (Qube1) machines since " +"they have no serial port." msgstr "" #. Tag: para #: boot-installer.xml:2220 #, no-c-format -msgid "You cannot pass any boot parameters directly. Instead, you have to edit the /nfsroot/default.colo file on the NFS server and add your parameters to the args variable." +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 @@ -1684,13 +2495,19 @@ msgstr "" #. Tag: para #: boot-installer.xml:2249 #, no-c-format -msgid "In order to run the installation system a working network setup and ssh session is needed on S/390." +msgid "" +"In order to run the installation system a working network setup and ssh " +"session is needed on S/390." msgstr "" #. Tag: para #: boot-installer.xml:2254 #, no-c-format -msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting an ssh session which will launch the standard installation system." +msgid "" +"The booting process starts with a network setup that prompts you for several " +"network parameters. If the setup is successful, you will login to the system " +"by starting an ssh session which will launch the standard installation " +"system." msgstr "" #. Tag: title @@ -1702,25 +2519,44 @@ 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." +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." +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." +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" +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 @@ -1756,7 +2592,15 @@ 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." +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 @@ -1769,11 +2613,27 @@ msgstr "" #: 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" +"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" +" 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." +" 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 @@ -1791,34 +2651,62 @@ 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 )." +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." +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." +"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;." +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 ." +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 @@ -1830,31 +2718,51 @@ 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." +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." +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." +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." +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." +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 @@ -1866,19 +2774,37 @@ 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 ." +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." +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." +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 @@ -1887,23 +2813,34 @@ msgstr "" 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." +" 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 ." +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" +"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." +" then it is possible that floppy booting is " +"simply not supported on your machine." msgstr "" #. Tag: title @@ -1915,49 +2852,113 @@ 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." +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 "Az indító paraméterek Linux kernel paraméterek, melyek általában a perifériák helyes használatára szolgálnak. A kernel általában képes ezek adatainak automatikus érzékelésére. Egyes esetekben azonban egy kis segítség szükséges." +msgid "" +"Boot parameters are Linux kernel parameters which are generally used to make " +"sure that peripherals are dealt with properly. For the most part, the kernel " +"can auto-detect information about your peripherals. However, in some cases " +"you'll have to help the kernel a bit." +msgstr "" +"Az indító paraméterek Linux kernel paraméterek, melyek általában a " +"perifériák helyes használatára szolgálnak. A kernel általában képes ezek " +"adatainak automatikus érzékelésére. Egyes esetekben azonban egy kis segítség " +"szükséges." #. Tag: para #: boot-installer.xml: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 "A rendszert 1. ízben az alap paraméterekkel jó indítani (vagyis továbbiak megadása nélkül) és meggyőződni arról, működése helyes-e. Ha nem, egy későbbi újraindításkor megadhatók különleges paraméterek, melyek a rendszert kisegítik egyes adatokkal a hardverről." +msgid "" +"If this is the first time you're booting the system, try the default boot " +"parameters (i.e., don't try setting parameters) and see if it works " +"correctly. It probably will. If not, you can reboot later and look for any " +"special parameters that inform the system about your hardware." +msgstr "" +"A rendszert 1. ízben az alap paraméterekkel jó indítani (vagyis továbbiak " +"megadása nélkül) és meggyőződni arról, működése helyes-e. Ha nem, egy " +"későbbi újraindításkor megadhatók különleges paraméterek, melyek a rendszert " +"kisegítik egyes adatokkal a hardverről." #. Tag: para #: boot-installer.xml: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 "Sok indító paraméterről szóló adat van a Linux BootPrompt HOGYAN leírásban, benne kétes hardverekről szólók is. Ez csak egy vázlatos szakasz a legáltalánosabb paraméterekről. Néhány szokásos találat megtalálható az alábbi: részben." +msgid "" +"Information on many boot parameters can be found in the Linux BootPrompt HOWTO, " +"including tips for obscure hardware. This section contains only a sketch of " +"the most salient parameters. Some common gotchas are included below in ." +msgstr "" +"Sok indító paraméterről szóló adat van a Linux BootPrompt HOGYAN leírásban, " +"benne kétes hardverekről szólók is. Ez csak egy vázlatos szakasz a " +"legáltalánosabb paraméterekről. Néhány szokásos találat megtalálható az " +"alábbi: részben." #. Tag: 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." +"Memory:availk/totalk " +"available\n" +" should be emitted early in the process. " +"total should match the total amount of RAM, in " +"kilobytes. If this doesn't match the actual amount of RAM you have " +"installed, you need to use the mem=ram parameter, where ram is " +"set to the amount of memory, suffixed with k for kilobytes, " +"or m for megabytes. For example, both mem=65536k and mem=64m mean 64MB of RAM." msgstr "" "A kernel indulásakor egy \n" -"Memory:availk/totalk available\n" -" üzenet látható a folyamat elején. A total a RAM teljes méretét adja kilobájtban. Ha nem pontos, a mem=ram paraméter használandó, ahol a ram a memória mérete, melyet k követ kilobájtokhoz, vagy m megabájtokhoz. Például a mem=65536k és mem=64m jelentése egyaránt 64MB RAM." +"Memory:availk/totalk " +"available\n" +" üzenet látható a folyamat elején. A " +"total a RAM teljes méretét adja kilobájtban. Ha " +"nem pontos, a mem=ram " +"paraméter használandó, ahol a ram a memória " +"mérete, melyet k követ kilobájtokhoz, vagy m " +"megabájtokhoz. Például a mem=65536k és " +"mem=64m jelentése egyaránt 64MB RAM." #. 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 "Soros konzollal indításkor a kernel általában automatikusan felismeri ezt (DECstation esetén nem). Ha van videó kártya (framebuffer) és billentyűzet a soros konzol által indítandó gépen, át kell adni a console=eszköz argumentumot a kernelnek, ahol az eszköz a soros eszköz, mely általában valami ilyesmi: ttyS0." +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 "" +"Soros konzollal indításkor a kernel általában automatikusan felismeri " +"ezt (DECstation esetén nem). Ha van videó " +"kártya (framebuffer) és billentyűzet a soros konzol által indítandó gépen, " +"át kell adni a console=eszköz argumentumot a kernelnek, ahol az eszköz a soros eszköz, mely általában valami ilyesmi: ttyS0." #. Tag: para #: boot-installer.xml: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." +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 @@ -1969,8 +2970,16 @@ msgstr "Debian Telepítő paraméterek" #. Tag: para #: boot-installer.xml:2804 #, no-c-format -msgid "The installation system recognizes a few additional boot parameters With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. which may be useful." -msgstr "A telepítő rendszer pár további indító paramétert is ismer A jelenlegi kernelekkel (2.6.9 vagy újabb) 32 parancssori opció és 32 környezeti opció használható. Ennek túllépése kernel pánikot okoz. mely hasznos lehet." +msgid "" +"The installation system recognizes a few additional boot " +"parameters With current kernels (2.6.9 or newer) you can " +"use 32 command line options and 32 environment options. If these numbers are " +"exceeded, the kernel will panic. which may be useful." +msgstr "" +"A telepítő rendszer pár további indító paramétert is ismer " +"A jelenlegi kernelekkel (2.6.9 vagy újabb) 32 parancssori opció és 32 " +"környezeti opció használható. Ennek túllépése kernel pánikot okoz. mely hasznos lehet." #. Tag: term #: boot-installer.xml:2821 @@ -1981,20 +2990,44 @@ msgstr "debconf/priority" #. Tag: para #: boot-installer.xml:2822 #, no-c-format -msgid "This parameter sets the lowest priority of messages to be displayed. Short form: priority" -msgstr "E paraméter adja meg a megjelenítendő üzenetek legkisebb elsőbbségét. Rövid forma: priority" +msgid "" +"This parameter sets the lowest priority of messages to be displayed. Short " +"form: priority" +msgstr "" +"E paraméter adja meg a megjelenítendő üzenetek legkisebb elsőbbségét. Rövid " +"forma: priority" #. Tag: para #: boot-installer.xml:2827 #, no-c-format -msgid "The default installation uses priority=high. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed." -msgstr "Az alap telepítés a priority=high. érteket használja. Ekkor a kritikus és magas elsőbbségű üzenetek jelennek meg, a közepes és alacsony elsőbbségű üzenetek nem. Hibák esetén a telepítő a szükséges szintre állítja ezt." +msgid "" +"The default installation uses priority=high. This " +"means that both high and critical priority messages are shown, but medium " +"and low priority messages are skipped. If problems are encountered, the " +"installer adjusts the priority as needed." +msgstr "" +"Az alap telepítés a priority=high. érteket használja. " +"Ekkor a kritikus és magas elsőbbségű üzenetek jelennek meg, a közepes és " +"alacsony elsőbbségű üzenetek nem. Hibák esetén a telepítő a szükséges " +"szintre állítja ezt." #. Tag: para #: boot-installer.xml:2834 #, no-c-format -msgid "If you add priority=medium as boot parameter, you will be shown the installation menu and gain more control over the installation. When priority=low is used, all messages are shown (this is equivalent to the expert boot method). With priority=critical, the installation system will display only critical messages and try to do the right thing without fuss." -msgstr "A priority=medium részletesebb irányítást ad a telepítéshez. A priority=low mindent kérdez (ez ugyanaz, mint az expert indítás mód). A priority=critical esetén a rendszer csak a kritikus üzeneteket jeleníti meg és ha minden rendben, nem kérdez." +msgid "" +"If you add priority=medium as boot parameter, you " +"will be shown the installation menu and gain more control over the " +"installation. When priority=low is used, all messages " +"are shown (this is equivalent to the expert boot " +"method). With priority=critical, the installation " +"system will display only critical messages and try to do the right thing " +"without fuss." +msgstr "" +"A priority=medium részletesebb irányítást ad a " +"telepítéshez. A priority=low mindent kérdez (ez " +"ugyanaz, mint az expert indítás mód). A " +"priority=critical esetén a rendszer csak a kritikus " +"üzeneteket jeleníti meg és ha minden rendben, nem kérdez." #. Tag: term #: boot-installer.xml:2848 @@ -2005,8 +3038,41 @@ msgstr "DEBIAN_FRONTEND" #. Tag: para #: boot-installer.xml:2849 #, 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 "Ez szabja meg a telepítő által használt felhasználó felületet. A jelenlegi lehetséges paraméter beállítások: DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=slang DEBIAN_FRONTEND=ncurses DEBIAN_FRONTEND=bogl DEBIAN_FRONTEND=gtk DEBIAN_FRONTEND=corba Az alapfelület a DEBIAN_FRONTEND=newt. A DEBIAN_FRONTEND=text soros konzolos telepítésekhez jó. Általában csak a newt felület elérhető az alap telepítő médián, így ez nem túl hasznos még." +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 "" +"Ez szabja meg a telepítő által használt felhasználó felületet. A jelenlegi " +"lehetséges paraméter beállítások: " +"DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " +" DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=slang " +"DEBIAN_FRONTEND=ncurses DEBIAN_FRONTEND=bogl " +" DEBIAN_FRONTEND=gtk DEBIAN_FRONTEND=corba Az alapfelület a " +"DEBIAN_FRONTEND=newt. A " +"DEBIAN_FRONTEND=text soros konzolos telepítésekhez " +"jó. Általában csak a newt felület elérhető az alap " +"telepítő médián, így ez nem túl hasznos még." #. Tag: term #: boot-installer.xml:2885 @@ -2017,8 +3083,15 @@ msgstr "BOOT_DEBUG" #. Tag: para #: boot-installer.xml:2886 #, no-c-format -msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)" -msgstr "Ha e paraméter értéke 2, a telepítő indító folyamat részletesebb naplózásra kerül. Ha 3, hibakereső héjakat tesz elérhetővé az indító folyamat fő pontjain. (Lépj ki a héjakból az indító folyamat folytatásához.)" +msgid "" +"Setting this boot parameter to 2 will cause the installer's boot process to " +"be verbosely logged. Setting it to 3 makes debug shells available at " +"strategic points in the boot process. (Exit the shells to continue the boot " +"process.)" +msgstr "" +"Ha e paraméter értéke 2, a telepítő indító folyamat részletesebb naplózásra " +"kerül. Ha 3, hibakereső héjakat tesz elérhetővé az indító folyamat fő " +"pontjain. (Lépj ki a héjakból az indító folyamat folytatásához.)" #. Tag: userinput #: boot-installer.xml:2895 @@ -2065,8 +3138,12 @@ msgstr "BOOT_DEBUG=3" #. Tag: para #: boot-installer.xml:2911 #, no-c-format -msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot." -msgstr "A héjak az indító folyamat különböző pontjain futnak részletes hibák visszaadásához. Lépj ki a héjból az indítás folytatásához." +msgid "" +"Shells are run at various points in the boot process to allow detailed " +"debugging. Exit the shell to continue the boot." +msgstr "" +"A héjak az indító folyamat különböző pontjain futnak részletes hibák " +"visszaadásához. Lépj ki a héjból az indítás folytatásához." #. Tag: term #: boot-installer.xml:2925 @@ -2077,14 +3154,23 @@ msgstr "INSTALL_MEDIA_DEV" #. Tag: para #: boot-installer.xml:2926 #, no-c-format -msgid "The value of the parameter is the path to the device to load the Debian installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" -msgstr "E paraméter értéke a Debian telepítőt betöltő eszköz útvonala. Például INSTALL_MEDIA_DEV=/dev/floppy/0" +msgid "" +"The value of the parameter is the path to the device to load the Debian " +"installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" +msgstr "" +"E paraméter értéke a Debian telepítőt betöltő eszköz útvonala. Például " +"INSTALL_MEDIA_DEV=/dev/floppy/0" #. Tag: para #: boot-installer.xml:2932 #, no-c-format -msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device." -msgstr "Az indító flopi, ami alapban végignézi az összes flopit a gyökér flopi megtalálásához felülírható e paraméterrel, hogy csak 1 eszközt nézzen." +msgid "" +"The boot floppy, which normally scans all floppies it can to find the root " +"floppy, can be overridden by this parameter to only look at the one device." +msgstr "" +"Az indító flopi, ami alapban végignézi az összes flopit a gyökér flopi " +"megtalálásához felülírható e paraméterrel, hogy csak 1 eszközt nézzen." #. Tag: term #: boot-installer.xml:2942 @@ -2095,14 +3181,31 @@ msgstr "debian-installer/framebuffer" #. Tag: para #: boot-installer.xml:2943 #, 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 "Egyes architektúrák használják a kernel framebuffert a telepítő több-nyelvű támogatásához. Ha ez gondot okoz, kikapcsolható a debian-installer/framebuffer=false vagy röviden fb=false paraméterrel. A szokásos gondok hibaüzenetek a bterm és bogl körül, üres képernyő vagy fagyás a telepítés indítása után pár perccel." +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 "" +"Egyes architektúrák használják a kernel framebuffert a telepítő több-nyelvű " +"támogatásához. Ha ez gondot okoz, kikapcsolható a debian-" +"installer/framebuffer=false vagy röviden fb=false paraméterrel. A szokásos gondok hibaüzenetek a bterm és bogl " +"körül, üres képernyő vagy fagyás a telepítés indítása után pár perccel." #. Tag: para #: boot-installer.xml:2953 #, 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 "A video=vga16:off argumentum szintén használható a kernel framebuffer kikapcsolására. Ilyen gondok vannak a Dell Inspiron gépeken Mobil Radeon kártya esetén." +msgid "" +"The video=vga16:off argument may also be used to " +"disable the kernel's use of the framebuffer. Such problems have been " +"reported on a Dell Inspiron with Mobile Radeon card." +msgstr "" +"A video=vga16:off argumentum szintén használható a " +"kernel framebuffer kikapcsolására. Ilyen gondok vannak a Dell Inspiron " +"gépeken Mobil Radeon kártya esetén." #. Tag: para #: boot-installer.xml:2959 @@ -2119,7 +3222,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:2967 #, 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." +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 @@ -2131,8 +3240,20 @@ msgstr "debian-installer/theme" #. Tag: para #: boot-installer.xml:2982 #, 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 "Egy téma meghatározza, hogyan nézzen ki a telepítő felhasználói felülete (színek, ikonok, stb.). Az elérhető témák a felülettől függenek. A newt és gtk felületek is támogatják a dark témát, mely gyengén látóknak is megfelelő. A téma így állítható be: debian-installer/theme=dark vagy theme=dark." +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 "" +"Egy téma meghatározza, hogyan nézzen ki a telepítő felhasználói felülete " +"(színek, ikonok, stb.). Az elérhető témák a felülettől függenek. A newt és " +"gtk felületek is támogatják a dark témát, mely gyengén " +"látóknak is megfelelő. A téma így állítható be: debian-installer/" +"theme=dark vagy " +"theme=dark." #. Tag: term #: boot-installer.xml:2995 @@ -2143,7 +3264,9 @@ msgstr "debian-installer/probe/usb" #. Tag: para #: boot-installer.xml:2996 #, no-c-format -msgid "Set to false to prevent probing for USB on boot, if that causes problems." +msgid "" +"Set to false to prevent probing for USB on boot, if " +"that causes problems." msgstr "A false tiltja az USB indítást, ha gondot okoz." #. Tag: term @@ -2155,14 +3278,30 @@ msgstr "netcfg/disable_dhcp" #. Tag: para #: boot-installer.xml:3006 #, no-c-format -msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails." -msgstr "Alapértelmezetten a &d-i; önműködően megpróbálja a hálózatot beállítani DHCP-n át. Ha sikerül, valószínűleg nem lesz esély a kapott beállítások módosítására. A hálózat kézi beállítása csak a DHCP meghiúsulásakor lehetséges." +msgid "" +"By default, the &d-i; automatically probes for network configuration via " +"DHCP. If the probe succeeds, you won't have a chance to review and change " +"the obtained settings. You can get to the manual network setup only in case " +"the DHCP probe fails." +msgstr "" +"Alapértelmezetten a &d-i; önműködően megpróbálja a hálózatot beállítani DHCP-" +"n át. Ha sikerül, valószínűleg nem lesz esély a kapott beállítások " +"módosítására. A hálózat kézi beállítása csak a DHCP meghiúsulásakor " +"lehetséges." #. Tag: para #: boot-installer.xml:3013 #, 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 "Ha van egy DHCP kiszolgáló a helyi hálózaton, de nem akarod használni, mert például rossz választ ad, használhatod a netcfg/disable_dhcp=true paramétert a hálózati DHCP-beállítás tiltására és megadhatod az adatokat kézzel." +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 "" +"Ha van egy DHCP kiszolgáló a helyi hálózaton, de nem akarod használni, mert " +"például rossz választ ad, használhatod a netcfg/" +"disable_dhcp=true paramétert a hálózati DHCP-beállítás tiltására " +"és megadhatod az adatokat kézzel." #. Tag: term #: boot-installer.xml:3024 @@ -2173,8 +3312,12 @@ msgstr "hw-detect/start_pcmcia" #. Tag: para #: boot-installer.xml:3025 #, no-c-format -msgid "Set to false to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." -msgstr "A false tiltja a PCMCIA szolgáltatások indítását, ha gondot okoznak. Egyes laptopok híresek erről." +msgid "" +"Set to false to prevent starting PCMCIA services, if " +"that causes problems. Some laptops are well known for this misbehavior." +msgstr "" +"A false tiltja a PCMCIA szolgáltatások indítását, ha " +"gondot okoznak. Egyes laptopok híresek erről." #. Tag: term #: boot-installer.xml:3035 @@ -2185,8 +3328,14 @@ msgstr "preseed/url" #. Tag: para #: boot-installer.xml:3036 #, no-c-format -msgid "Specify the url to a preconfiguration file to download and use in automating the install. See . Short form: url" -msgstr "Megadja az automata telepítéshez letöltendő és használandó elő-beállító fájlra mutató url-t. Lásd a részt. Rövid forma: url" +msgid "" +"Specify the url to a preconfiguration file to download and use in automating " +"the install. See . Short form: " +"url" +msgstr "" +"Megadja az automata telepítéshez letöltendő és használandó elő-beállító " +"fájlra mutató url-t. Lásd a részt. " +"Rövid forma: url" #. Tag: term #: boot-installer.xml:3046 @@ -2197,8 +3346,14 @@ msgstr "preseed/file" #. Tag: para #: boot-installer.xml:3047 #, no-c-format -msgid "Specify the path to a preconfiguration file to load to automating the install. See . Short form: file" -msgstr "Megadja az automata telepítéshez betöltendő elő-beállító fájl útvonalát. Lásd a részt. Rövid forma: fájl" +msgid "" +"Specify the path to a preconfiguration file to load to automating the " +"install. See . Short form: " +"file" +msgstr "" +"Megadja az automata telepítéshez betöltendő elő-beállító fájl útvonalát. " +"Lásd a részt. Rövid forma: " +"fájl" #. Tag: term #: boot-installer.xml:3057 @@ -2209,8 +3364,16 @@ msgstr "auto-install/enabled" #. Tag: para #: boot-installer.xml:3058 #, no-c-format -msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. Short form: auto=true See for details about using this to automate installs." -msgstr "Az elő-beállítások végrehajtása előtt felteendő kérdések megválaszolása elhalasztható a hálózat beállításáig. Rövid forma: auto=true Lásd a részt ennek használatához az automata telepítésben." +msgid "" +"Delay questions that are normally asked before preseeding is possible until " +"after the network is configured. Short form: auto=true See for details about using this " +"to automate installs." +msgstr "" +"Az elő-beállítások végrehajtása előtt felteendő kérdések megválaszolása " +"elhalasztható a hálózat beállításáig. Rövid forma: auto=true Lásd a részt ennek használatához " +"az automata telepítésben." #. Tag: term #: boot-installer.xml:3069 @@ -2221,14 +3384,31 @@ msgstr "cdrom-detect/eject" #. Tag: para #: boot-installer.xml:3070 #, no-c-format -msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically." -msgstr "Alapban az újraindítás előtt a &d-i; önműködően kiadja a telepítés alatt használt optikai médiát. Ez szükségtelen, ha a rendszer nem indul önműködően a CD-lemezről. Néha kimondottan rossz, például, ha az optikai meghajtó nem teszi be újra a médiát és a felhasználó nincs ott. Sok rés-töltős, karcsú és fentről-töltős stílusú meghajtó nem tudja automatikusan újratölteni a médiát." +msgid "" +"By default, before rebooting, &d-i; automatically ejects the optical media " +"used during the installation. This can be unnecessary if the system does not " +"automatically boot off the CD. In some cases it may even be undesirable, for " +"example if the optical drive cannot reinsert the media itself and the user " +"is not there to do it manually. Many slot loading, slim-line, and caddy " +"style drives cannot reload media automatically." +msgstr "" +"Alapban az újraindítás előtt a &d-i; önműködően kiadja a telepítés alatt " +"használt optikai médiát. Ez szükségtelen, ha a rendszer nem indul önműködően " +"a CD-lemezről. Néha kimondottan rossz, például, ha az optikai meghajtó nem " +"teszi be újra a médiát és a felhasználó nincs ott. Sok rés-töltős, karcsú és " +"fentről-töltős stílusú meghajtó nem tudja automatikusan újratölteni a médiát." #. Tag: para #: boot-installer.xml:3079 #, no-c-format -msgid "Set to false to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation." -msgstr "Legyen false az automata kiadás kikapcsolásához, ekkor magadnak kell biztosítani, hogy a rendszer ne induljon önműködően az optikai meghajtóról a telepítés után." +msgid "" +"Set to false to disable automatic ejection, and be " +"aware that you may need to ensure that the system does not automatically " +"boot from the optical drive after the initial installation." +msgstr "" +"Legyen false az automata kiadás kikapcsolásához, " +"ekkor magadnak kell biztosítani, hogy a rendszer ne induljon önműködően az " +"optikai meghajtóról a telepítés után." #. Tag: term #: boot-installer.xml:3090 @@ -2251,8 +3431,14 @@ msgstr "directfb/hw-accel" #. Tag: para #: boot-installer.xml:3100 #, 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 "A gtk felülethez (grafikus telepítő) a directfb hardveres gyorsítás alapból kikapcsolt. Bekapcsolásához, legyen a paraméter true a telepítő indításakor." +msgid "" +"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 "" +"A gtk felülethez (grafikus telepítő) a directfb hardveres gyorsítás alapból " +"kikapcsolt. Bekapcsolásához, legyen a paraméter true " +"a telepítő indításakor." #. Tag: term #: boot-installer.xml:3110 @@ -2263,8 +3449,12 @@ msgstr "rescue/enable" #. Tag: para #: boot-installer.xml:3111 #, no-c-format -msgid "Set to true to enter rescue mode rather than performing a normal installation. See ." -msgstr "Legyen true a rendes telepítés helyett mentő módba lépéshez. Lásd: ." +msgid "" +"Set to true to enter rescue mode rather than " +"performing a normal installation. See ." +msgstr "" +"Legyen true a rendes telepítés helyett mentő módba " +"lépéshez. Lásd: ." #. Tag: title #: boot-installer.xml:3122 @@ -2275,26 +3465,57 @@ msgstr "Paraméterek átadása kernel moduloknak" #. Tag: para #: boot-installer.xml:3123 #, no-c-format -msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system." -msgstr "Kernelbe fordított meghajtók számára lehetséges a kernel dokumentációja szerinti paraméterek átadása. Ám akkor, ha modulokként fordítottak, mivel ezek kissé másképp töltődnek be a telepítéskor, mint a telepített rendszeren, nem adhatók át úgy paraméterek, mint rendesen. A telepítő által ismert különleges szintaxist kell használni, így ezek a helyes beállító fájlba kerülnek és felhasználásra kerülnek a modulok tényleges betöltésekor. E paraméterek átkerülnek a telepített rendszerbe is." +msgid "" +"If drivers are compiled into the kernel, you can pass parameters to them as " +"described in the kernel documentation. However, if drivers are compiled as " +"modules and because kernel modules are loaded a bit differently during an " +"installation than when booting an installed system, it is not possible to " +"pass parameters to modules as you would normally do. Instead, you need to " +"use a special syntax recognized by the installer which will then make sure " +"that the parameters are saved in the proper configuration files and will " +"thus be used when the modules are actually loaded. The parameters will also " +"be propagated automatically to the configuration for the installed system." +msgstr "" +"Kernelbe fordított meghajtók számára lehetséges a kernel dokumentációja " +"szerinti paraméterek átadása. Ám akkor, ha modulokként fordítottak, mivel " +"ezek kissé másképp töltődnek be a telepítéskor, mint a telepített " +"rendszeren, nem adhatók át úgy paraméterek, mint rendesen. A telepítő által " +"ismert különleges szintaxist kell használni, így ezek a helyes beállító " +"fájlba kerülnek és felhasználásra kerülnek a modulok tényleges betöltésekor. " +"E paraméterek átkerülnek a telepített rendszerbe is." #. Tag: para #: boot-installer.xml:3136 #, no-c-format -msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually." -msgstr "Erre ritkán van szükség. A kernel szinte mindig képes a rendszeren lévő hardvert kipróbálni és jó alapértelmezett értékeket beállítani. De egyes esetekben jól jöhet paraméterek kézi beállítása." +msgid "" +"Note that it is now quite rare that parameters need to be passed to modules. " +"In most cases the kernel will be able to probe the hardware present in a " +"system and set good defaults that way. However, in some situations it may " +"still be needed to set parameters manually." +msgstr "" +"Erre ritkán van szükség. A kernel szinte mindig képes a rendszeren lévő " +"hardvert kipróbálni és jó alapértelmezett értékeket beállítani. De egyes " +"esetekben jól jöhet paraméterek kézi beállítása." #. Tag: para #: boot-installer.xml:3143 #, no-c-format msgid "" -"The syntax to use to set parameters for modules is: \n" -"module_name.parameter_name=value\n" -" If you need to pass multiple parameters to the same or different modules, just repeat this. For example, to set an old 3Com network interface card to use the BNC (coax) connector and IRQ 10, you would pass:" +"The syntax to use to set parameters for modules is: " +"\n" +"module_name.parameter_name=value\n" +" If you need to pass multiple parameters to the " +"same or different modules, just repeat this. For example, to set an old 3Com " +"network interface card to use the BNC (coax) connector and IRQ 10, you would " +"pass:" msgstr "" "A modulokhoz beállítandó paraméterek nyelvtana:\n" -"modul_név.paraméter_név=érték\n" -" Ha több paramétert akarsz átadni egy vagy több modulhoz, csak ismételd ezt. Például egy régi 3Com hálózati csatoló kártya beállítása a BNC (koax) csatlakozó és IRQ 10 használatához:" +"modul_név.paraméter_név=érték\n" +" Ha több paramétert akarsz átadni egy vagy több " +"modulhoz, csak ismételd ezt. Például egy régi 3Com hálózati csatoló kártya " +"beállítása a BNC (koax) csatlakozó és IRQ 10 használatához:" #. Tag: screen #: boot-installer.xml:3153 @@ -2317,14 +3538,27 @@ msgstr "CD-ROM megbízhatóság" #. Tag: para #: boot-installer.xml:3171 #, no-c-format -msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also — even after booting successfully from CD-ROM — fail to recognize the CD-ROM or return errors while reading from it during the installation." -msgstr "Néha, főleg régi CD-ROM meghajtókkal, a telepítő CD-ROM lemezről indítása meghiúsulhat. A telepítő — akár a CD-ROM lemezről való sikeres indítás után — talán nem ismeri fel a CD-ROM eszközt vagy hibákat ad a telepítés alatti olvasásakor." +msgid "" +"Sometimes, especially with older CD-ROM drives, the installer may fail to " +"boot from a CD-ROM. The installer may also — even after booting " +"successfully from CD-ROM — fail to recognize the CD-ROM or return " +"errors while reading from it during the installation." +msgstr "" +"Néha, főleg régi CD-ROM meghajtókkal, a telepítő CD-ROM lemezről indítása " +"meghiúsulhat. A telepítő — akár a CD-ROM lemezről való sikeres indítás " +"után — talán nem ismeri fel a CD-ROM eszközt vagy hibákat ad a " +"telepítés alatti olvasásakor." #. Tag: para #: boot-installer.xml:3178 #, no-c-format -msgid "There are a many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you." -msgstr "Ennek sok eltérő oka lehet. Csak néhány szokásos hibát és kezelésükről szóló általános tanácsokat írunk le. A többi tőled függ." +msgid "" +"There are a many different possible causes for these problems. We can only " +"list some common issues and provide general suggestions on how to deal with " +"them. The rest is up to you." +msgstr "" +"Ennek sok eltérő oka lehet. Csak néhány szokásos hibát és kezelésükről szóló " +"általános tanácsokat írunk le. A többi tőled függ." #. Tag: para #: boot-installer.xml:3184 @@ -2335,26 +3569,47 @@ msgstr "Először 2 egyszerű dolgot érdemes kipróbálni." #. Tag: para #: boot-installer.xml:3189 #, no-c-format -msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty." -msgstr "Ha a CD-ROM nem indul, ellenőrizd, helyesen van-e betéve és nem piszkos-e." +msgid "" +"If the CD-ROM does not boot, check that it was inserted correctly and that " +"it is not dirty." +msgstr "" +"Ha a CD-ROM nem indul, ellenőrizd, helyesen van-e betéve és nem piszkos-e." #. Tag: para #: boot-installer.xml:3195 #, no-c-format -msgid "If the installer fails to recognize a CD-ROM, try just running the option Detect and mount CD-ROM a second time. Some DMA related isses with older CD-ROM drives are known to be resolved in this way." -msgstr "Ha a telepítő nem ismeri fel a CD-ROM meghajtót, először próbáld meg a CD-ROM felismerése és csatolása pont futtatását másodszor. Több régi CD-ROM meghajtónál ismert DMA hiba megoldható így." +msgid "" +"If the installer fails to recognize a CD-ROM, try just running the option " +" Detect and mount CD-ROM a second time. Some DMA related isses with older CD-ROM drives " +"are known to be resolved in this way." +msgstr "" +"Ha a telepítő nem ismeri fel a CD-ROM meghajtót, először próbáld meg a " +" CD-ROM felismerése és csatolása pont futtatását másodszor. Több régi CD-ROM meghajtónál ismert " +"DMA hiba megoldható így." #. Tag: para #: boot-installer.xml:3205 #, no-c-format -msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity." -msgstr "Ha ez nem megy, próbáld az alábbi javaslatokat. Általában az ott tárgyalt javaslatok a CD-ROM és DVD eszközökre egyaránt érvényesek, de az egyszerűség kedvéért mindig a CD-ROM szót használjuk." +msgid "" +"If this does not work, then try the suggestions in the subsections below. " +"Most, but not all, suggestions discussed there are valid for both CD-ROM and " +"DVD, but we'll use the term CD-ROM for simplicity." +msgstr "" +"Ha ez nem megy, próbáld az alábbi javaslatokat. Általában az ott tárgyalt " +"javaslatok a CD-ROM és DVD eszközökre egyaránt érvényesek, de az egyszerűség " +"kedvéért mindig a CD-ROM szót használjuk." #. Tag: para #: boot-installer.xml:3211 #, no-c-format -msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available." -msgstr "Ha a telepítés semmiképp nem megy a CD-ROM eszközről, próbálj egy másik elérhető telepítő módot." +msgid "" +"If you cannot get the installation working from CD-ROM, try one of the other " +"installation methods that are available." +msgstr "" +"Ha a telepítés semmiképp nem megy a CD-ROM eszközről, próbálj egy másik " +"elérhető telepítő módot." #. Tag: title #: boot-installer.xml:3219 @@ -2365,20 +3620,34 @@ msgstr "Általános hibák" #. Tag: para #: boot-installer.xml:3222 #, no-c-format -msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer." -msgstr "Néhány régi CD-ROM meghajtó nem támogatja a korszerű CD-írók használatával nagy sebességgel írt lemezek olvasását." +msgid "" +"Some older CD-ROM drives do not support reading from discs that were burned " +"at high speeds using a modern CD writer." +msgstr "" +"Néhány régi CD-ROM meghajtó nem támogatja a korszerű CD-írók használatával " +"nagy sebességgel írt lemezek olvasását." #. Tag: para #: boot-installer.xml:3228 #, no-c-format -msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)." -msgstr "Ha a rendszer elindul a CD-ROM eszközről, ez nem feltétlenül jelenti azt, hogy a Linux is támogatja azt (vagy, pontosabban a vezérlőt, melyre a CD-ROM meghajtó kötve van)." +msgid "" +"If your system boots correctly from the CD-ROM, it does not necessarily mean " +"that Linux also supports the CD-ROM (or, more correctly, the controller that " +"your CD-ROM drive is connected to)." +msgstr "" +"Ha a rendszer elindul a CD-ROM eszközről, ez nem feltétlenül jelenti azt, " +"hogy a Linux is támogatja azt (vagy, pontosabban a vezérlőt, melyre a CD-ROM " +"meghajtó kötve van)." #. Tag: para #: boot-installer.xml:3235 #, no-c-format -msgid "Some older CD-ROM drives do not work correctly if direct memory access (DMA) is enabled." -msgstr "Pár régi CD-ROM meghajtó nem működik rendesen a direkt memória elérés (DMA) bekapcsolt volta esetén." +msgid "" +"Some older CD-ROM drives do not work correctly if direct memory " +"access (DMA) is enabled." +msgstr "" +"Pár régi CD-ROM meghajtó nem működik rendesen a direkt memória " +"elérés (DMA) bekapcsolt volta esetén." #. Tag: title #: boot-installer.xml:3246 @@ -2390,34 +3659,52 @@ msgstr "Hogyan vizsgálj ki és oldj meg gondokat" #: boot-installer.xml:3247 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." -msgstr "Ha a CD-ROM eszköz indítása sikertelen, próbáld ki az alább adott javaslatokat." +msgstr "" +"Ha a CD-ROM eszköz indítása sikertelen, próbáld ki az alább adott " +"javaslatokat." #. Tag: para #: boot-installer.xml:3252 #, no-c-format -msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using." -msgstr "Ellenőrizd, hogy a BIOS támogatja a CD-ROM indítást (a régebbiek nem) és hogy a CD-rom meghajtó támogatja a használt médiát." +msgid "" +"Check that your BIOS actually supports booting from CD-ROM (older systems " +"possibly don't) and that your CD-ROM drive supports the media you are using." +msgstr "" +"Ellenőrizd, hogy a BIOS támogatja a CD-ROM indítást (a régebbiek nem) és " +"hogy a CD-rom meghajtó támogatja a használt médiát." #. Tag: para #: boot-installer.xml:3258 #, no-c-format msgid "" -"If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the MD5SUMS file that should be present in the same location as where you downloaded the image from. \n" +"If you downloaded an iso image, check that the md5sum of that image matches " +"the one listed for the image in the MD5SUMS file that " +"should be present in the same location as where you downloaded the image " +"from. \n" "$ md5sum debian-testing-i386-netinst.iso\n" -"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst.iso\n" -" Next, check that the md5sum of the burned CD-ROM matches as well. The following command should work. It uses the size of the image to read the correct number of bytes from the CD-ROM." -msgstr "" -"Ha letöltöttél egy iso képet, ellenőrizd, hogy az md5sum egyezik az MD5SUMS fájlban lévővel, mely ugyanott van, ahonnan letöltötted. \n" +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Next, check that the md5sum of the burned CD-ROM " +"matches as well. The following command should work. It uses the size of the " +"image to read the correct number of bytes from the CD-ROM." +msgstr "" +"Ha letöltöttél egy iso képet, ellenőrizd, hogy az md5sum egyezik az " +"MD5SUMS fájlban lévővel, mely ugyanott van, ahonnan " +"letöltötted. \n" "$ md5sum debian-testing-i386-netinst.iso\n" -"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst.iso\n" -" Ezután ellenőrizd, hogy megírt CD-ROM is egyezik. Az alábbi parancs kiváló. Használja a kép méretét helyes számú bájt olvasására a CD-ROM lemezről." +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Ezután ellenőrizd, hogy megírt CD-ROM is " +"egyezik. Az alábbi parancs kiváló. Használja a kép méretét helyes számú bájt " +"olvasására a CD-ROM lemezről." #. Tag: screen #: boot-installer.xml:3271 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" -"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" "> md5sum\n" "a20391b12f7ff22ef705cee4059c6b92 -\n" "262668+0 records in\n" @@ -2425,7 +3712,8 @@ msgid "" "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" msgstr "" "$ dd if=/dev/cdrom | \\\n" -"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" "> md5sum\n" "a20391b12f7ff22ef705cee4059c6b92 -\n" "262668+0 rekord beolvasva\n" @@ -2435,50 +3723,88 @@ msgstr "" #. Tag: para #: boot-installer.xml:3276 #, no-c-format -msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there." -msgstr "Ha a telepítő indulása után a CD-ROM érzékelése sikertelen, sokszor az ismételt kísérlet sikerül. Ha egynél több CD-ROM meghajtód van, tedd a lemezt a másikba. Ha ez sem válik be vagy a CD-ROM felismerésre kerül de hibák történnek az olvasáskor, próbáld a lenti javaslatokat. Ehhez kis Linux-ismeret kell. Parancsok használatához előbb válts a második virtuális terminálra (VT2), melyen aktiváld a héjat." +msgid "" +"If, after the installer has been booted successfully, the CD-ROM is not " +"detected, sometimes simply trying again may solve the problem. If you have " +"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If " +"that does not work or if the CD-ROM is recognized but there are errors when " +"reading from it, try the suggestions listed below. Some basic knowledge of " +"Linux is required for this. To execute any of the commands, you should first " +"switch to the second virtual console (VT2) and activate the shell there." +msgstr "" +"Ha a telepítő indulása után a CD-ROM érzékelése sikertelen, sokszor az " +"ismételt kísérlet sikerül. Ha egynél több CD-ROM meghajtód van, tedd a " +"lemezt a másikba. Ha ez sem válik be vagy a CD-ROM felismerésre kerül de " +"hibák történnek az olvasáskor, próbáld a lenti javaslatokat. Ehhez kis Linux-" +"ismeret kell. Parancsok használatához előbb válts a második virtuális " +"terminálra (VT2), melyen aktiváld a héjat." #. Tag: para #: boot-installer.xml:3288 #, no-c-format -msgid "Switch to VT4 or view the contents of /var/log/syslog (use nano as editor) to check for any specific error messages. After that, also check the output of dmesg." -msgstr "Válts a VT4 terminálra vagy nézd meg a /var/log/syslog tartalmát (használd a nano-t szerkesztőként) a hibák ellenőrzéséhez. Ezután ellenőrizd a dmesg kimenetét is." +msgid "" +"Switch to VT4 or view the contents of /var/log/syslog " +"(use nano as editor) to check for any specific error " +"messages. After that, also check the output of dmesg." +msgstr "" +"Válts a VT4 terminálra vagy nézd meg a /var/log/syslog " +"tartalmát (használd a nano-t szerkesztőként) a hibák " +"ellenőrzéséhez. Ezután ellenőrizd a dmesg kimenetét is." #. Tag: para #: boot-installer.xml:3295 #, no-c-format msgid "" -"Check in the output of dmesg if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): \n" +"Check in the output of dmesg if your CD-ROM drive was " +"recognized. You should see something like (the lines do not necessarily have " +"to be consecutive): \n" "Probing IDE interface ide1...\n" "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" "ide1 at 0x170-0x177,0x376 on irq 15\n" "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" "Uniform CD-ROM driver Revision: 3.20\n" -" If you don't see something like that, chances are the controller your CD-ROM is connected to was not recognized or may be not supported at all. If you know what driver is needed for the drive, you can try loading it manually using modprobe." -msgstr "" -"Ellenőrizd a dmesg kimenetét, ha a CD-ROM meghajtó felismerése sikerült. Ilyesmit kell látnod benne (a sorok nem feltétlenül egymás utániak): \n" +" If you don't see something like that, chances " +"are the controller your CD-ROM is connected to was not recognized or may be " +"not supported at all. If you know what driver is needed for the drive, you " +"can try loading it manually using modprobe." +msgstr "" +"Ellenőrizd a dmesg kimenetét, ha a CD-ROM meghajtó " +"felismerése sikerült. Ilyesmit kell látnod benne (a sorok nem feltétlenül " +"egymás utániak): \n" "Probing IDE interface ide1...\n" "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" "ide1 at 0x170-0x177,0x376 on irq 15\n" "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" "Uniform CD-ROM driver Revision: 3.20\n" -" Ha nincs ilyesmi, lehet, hogy a vezérlő felismerése nem sikerült vagy egyáltalán nem támogatott. Ha tudod, milyen meghajtót igényel, kézzel is betöltheted a modprobe paranccsal." +" Ha nincs ilyesmi, lehet, hogy a vezérlő " +"felismerése nem sikerült vagy egyáltalán nem támogatott. Ha tudod, milyen " +"meghajtót igényel, kézzel is betöltheted a modprobe " +"paranccsal." #. Tag: para #: boot-installer.xml:3309 #, no-c-format -msgid "Check that there is a device node for your CD-ROM drive under /dev/. In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." -msgstr "Ellenőrizd, van-e megfelelő eszköz-leíró fájl a CD-ROM meghajtóhoz a /dev/ könyvtárban. A fenti példában ez a /dev/hdc. Lehet ez is: /dev/cdroms/cdrom0." +msgid "" +"Check that there is a device node for your CD-ROM drive under /dev/" +". In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." +msgstr "" +"Ellenőrizd, van-e megfelelő eszköz-leíró fájl a CD-ROM meghajtóhoz a " +"/dev/ könyvtárban. A fenti példában ez a /dev/" +"hdc. Lehet ez is: /dev/cdroms/cdrom0." #. Tag: para #: boot-installer.xml:3317 #, no-c-format msgid "" -"Use the mount command to check if the CD-ROM is already mounted; if not, try mounting it manually: \n" +"Use the mount command to check if the CD-ROM is already " +"mounted; if not, try mounting it manually: \n" "$ mount /dev/hdc /cdrom\n" -" Check if there are any error messages after that command." +" Check if there are any error messages after that " +"command." msgstr "" -"Használd a mount parancsot a CD-ROM csatolt voltának ellenőrzésére; ha nincs, próbáld kézzel csatolni: \n" +"Használd a mount parancsot a CD-ROM csatolt voltának " +"ellenőrzésére; ha nincs, próbáld kézzel csatolni: \n" "$ mount /dev/hdc /cdrom\n" " Ellenőrizd, ír-e hibát." @@ -2490,23 +3816,35 @@ msgid "" "$ cd /proc/ide/hdc\n" "$ grep dma settings\n" "using_dma 1 0 1 rw\n" -" A 1 means it is enabled. If it is, try disabling it: \n" +" A 1 means it is enabled. If it " +"is, try disabling it: \n" "$ echo -n \"using_dma:0\" >settings\n" -" Make sure that you are in the directory for the device that corresponds to your CD-ROM drive." +" Make sure that you are in the directory for the " +"device that corresponds to your CD-ROM drive." msgstr "" "Ellenőrizd a DMA állapotát: \n" "$ cd /proc/ide/hdc\n" "$ grep dma settings\n" "using_dma 1 0 1 rw\n" -" Az 1 az jelenti: bekapcsolva. Ha így van, próbáld kikapcsolni: \n" +" Az 1 az jelenti: bekapcsolva. Ha " +"így van, próbáld kikapcsolni: \n" "$ echo -n \"using_dma:0\" >settings\n" -" Győződj meg, hogy a CD-ROM meghajtónak megfelelő könyvtárban vagy." +" Győződj meg, hogy a CD-ROM meghajtónak megfelelő " +"könyvtárban vagy." #. Tag: para #: boot-installer.xml:3341 #, no-c-format -msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably." -msgstr "Ha gond támad a telepítés alatt, próbáld ki a CD-ROM épségének ellenőrzését a telepítő fő-menü vége felé található lehetőséggel. E lehetőség a CD-ROM eszközről való olvasás megbízhatóságának általános ellenőrzésére is használható." +msgid "" +"If there are any problems during the installation, try checking the " +"integrity of the CD-ROM using the option near the bottom of the installer's " +"main menu. This option can also be used as a general test if the CD-ROM can " +"be read reliably." +msgstr "" +"Ha gond támad a telepítés alatt, próbáld ki a CD-ROM épségének ellenőrzését " +"a telepítő fő-menü vége felé található lehetőséggel. E lehetőség a CD-ROM " +"eszközről való olvasás megbízhatóságának általános ellenőrzésére is " +"használható." #. Tag: title #: boot-installer.xml:3356 @@ -2517,38 +3855,81 @@ msgstr "Flopi lemezek megbízhatósága" #. Tag: para #: boot-installer.xml:3358 #, no-c-format -msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." -msgstr "A Debian rendszert flopiról telepítők számára a legnagyobb gond a flopi megbízhatatlansága." +msgid "" +"The biggest problem for people using floppy disks to install Debian seems to " +"be floppy disk reliability." +msgstr "" +"A Debian rendszert flopiról telepítők számára a legnagyobb gond a flopi " +"megbízhatatlansága." #. Tag: para #: boot-installer.xml:3363 -#, 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." +#, fuzzy, 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:3372 -#, no-c-format -msgid "If you are having the installation stall at a particular floppy, the first thing you should 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." +#, fuzzy, no-c-format +msgid "" +"If you are having the installation stall at a particular floppy, the first " +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. Simply reformatting the old " +"floppy may not be sufficient, even if it appears that the floppy was " +"reformatted and written with no errors. It is sometimes useful to try " +"writing the floppy on a different system." +msgstr "" +"Ha a telepítés elakad egy flopinál, legelőször 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:3381 #, no-c-format -msgid "Normally you should not have download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums." -msgstr "Általában nem kell újra letöltened a flopi képet, de ha gondokat észlelsz mindig hasznos ellenőrizni a képek helyesen letöltött voltát md5-összegük ellenőrzésével." +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:3387 -#, 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." +#, fuzzy, no-c-format +msgid "" +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." +msgstr "" +"Általában nem kell újra letöltened a flopi képet, de ha gondokat észlelsz " +"mindig hasznos ellenőrizni a képek helyesen letöltött voltát md5-összegük " +"ellenőrzésével." #. Tag: para #: boot-installer.xml:3393 #, no-c-format -msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers." -msgstr "Sokak gépe pedig csak többszöri indítás után tudta pontosan elolvasni a flopit és így ez csak ekkor tudott sikeresen elindulni. Ezt mind hibás hardver vagy firmware flopi meghajtók okozzák." +msgid "" +"Other users have reported that simply rebooting a few times with the same " +"floppy in the floppy drive can lead to a successful boot. This is all due to " +"buggy hardware or firmware floppy drivers." +msgstr "" +"Sokak gépe pedig csak többszöri indítás után tudta pontosan elolvasni a " +"flopit és így ez csak ekkor tudott sikeresen elindulni. Ezt mind hibás " +"hardver vagy firmware flopi meghajtók okozzák." #. Tag: title #: boot-installer.xml:3402 @@ -2559,26 +3940,53 @@ msgstr "Indító beállítás" #. Tag: para #: boot-installer.xml:3404 #, no-c-format -msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in ." -msgstr "Ha kernel megáll az indító folyamat során, nem ismer fel perifériákat vagy meghajtókat helyesen, először az indító paramétereket kell ellenőrizni a korábbi szerint." +msgid "" +"If you have problems and the kernel hangs during the boot process, doesn't " +"recognize peripherals you actually have, or drives are not recognized " +"properly, the first thing to check is the boot parameters, as discussed in " +"." +msgstr "" +"Ha kernel megáll az indító folyamat során, nem ismer fel perifériákat vagy " +"meghajtókat helyesen, először az indító paramétereket kell ellenőrizni a " +"korábbi szerint." #. Tag: para #: boot-installer.xml:3411 #, 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 "Ha a telepítő által adott helyett saját kernelt indítasz, fontos, hogy a CONFIG_DEVFS be legyen állítva a kernelben. A telepítő a CONFIG_DEVFS meglétét igényli." +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 "" +"Ha a telepítő által adott helyett saját kernelt indítasz, fontos, hogy a " +"CONFIG_DEVFS be legyen állítva a kernelben. A " +"telepítő a CONFIG_DEVFS meglétét igényli." #. Tag: para #: boot-installer.xml:3418 #, 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 "Bizonyos gondok gyakran megoldhatók kiegészítők és perifériák eltávolításával és újraindítással. Egyes belső modemek, hangkártyák és Plug-n-Play eszközök sok gondot adnak." +msgid "" +"Often, problems can be solved by removing add-ons and peripherals, and then " +"trying booting again. Internal modems, sound cards, and " +"Plug-n-Play devices can be especially problematic." +msgstr "" +"Bizonyos gondok gyakran megoldhatók kiegészítők és perifériák " +"eltávolításával és újraindítással. Egyes belső " +"modemek, hangkártyák és Plug-n-Play eszközök sok gondot adnak." #. Tag: para #: boot-installer.xml:3424 #, 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 "Ha több, mint 512M memória van a gépen és a telepítő megáll a kernel indításakor, előfordulhat, hogy egy indító argumentumot kell megadni a kernel által nézett memória korlátozására így: mem=512m." +msgid "" +"If you have a large amount of memory installed in your machine, more than " +"512M, and the installer hangs when booting the kernel, you may need to " +"include a boot argument to limit the amount of memory the kernel sees, such " +"as mem=512m." +msgstr "" +"Ha több, mint 512M memória van a gépen és a telepítő megáll a kernel " +"indításakor, előfordulhat, hogy egy indító argumentumot kell megadni a " +"kernel által nézett memória korlátozására így: mem=512m." #. Tag: title #: boot-installer.xml:3435 @@ -2589,32 +3997,76 @@ msgstr "Gyakori &arch-title; telepítő gondok" #. Tag: para #: boot-installer.xml:3436 #, no-c-format -msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." -msgstr "Van pár gyakori telepítő gond, mely megoldható vagy elkerülhető egyes indító paraméterek átadásával a telepítőnek." +msgid "" +"There are some common installation problems that can be solved or avoided by " +"passing certain boot parameters to the installer." +msgstr "" +"Van pár gyakori telepítő gond, mely megoldható vagy elkerülhető egyes indító " +"paraméterek átadásával a telepítőnek." #. Tag: para #: boot-installer.xml:3441 #, 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 "Egyes rendszereken fordított DCL flopik vannak. Ha hibákat kapsz a flopiról olvasáskor, pedig tudod, hogy a flopi jó, próbáld a floppy=thinkpad paramétert." +msgid "" +"Some systems have floppies with inverted DCLs. If you receive " +"errors reading from the floppy, even when you know the floppy is good, try " +"the parameter floppy=thinkpad." +msgstr "" +"Egyes rendszereken fordított DCL flopik vannak. Ha hibákat " +"kapsz a flopiról olvasáskor, pedig tudod, hogy a flopi jó, próbáld a " +"floppy=thinkpad paramétert." #. Tag: para #: boot-installer.xml:3447 #, 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 "Egyes rendszereken, ilyen például az IBM PS/1 vagy ValuePoint (melyben ST-506 lemez meghajtók vannak), az IDE meghajtó felismerése hibás lehet. Előbb paraméterek nélkül próbáld, és nézd meg, az IDE meghajtó felismerése helyes-e. Ha nem, ellenőrizd a meghajtó geometriáját (cilinderek, fejek, szektorok) és használd a hd=cilinderek,fejek,szektorok paramétert." +msgid "" +"On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk " +"drivers), the IDE drive may not be properly recognized. Again, try it first " +"without the parameters and see if the IDE drive is recognized properly. If " +"not, determine your drive geometry (cylinders, heads, and sectors), and use " +"the parameter hd=cylinders," +"heads,sectors." +msgstr "" +"Egyes rendszereken, ilyen például az IBM PS/1 vagy ValuePoint (melyben ST-" +"506 lemez meghajtók vannak), az IDE meghajtó felismerése hibás lehet. Előbb " +"paraméterek nélkül próbáld, és nézd meg, az IDE meghajtó felismerése helyes-" +"e. Ha nem, ellenőrizd a meghajtó geometriáját (cilinderek, fejek, szektorok) " +"és használd a hd=cilinderek," +"fejek,szektorok paramétert." #. Tag: para #: boot-installer.xml:3456 #, 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 "Nagyon régi gépnél, ha a kernel megáll itt: Checking 'hlt' instruction..., próbáld a no-hlt indító argumentumot, mely kikapcsolja ezt a tesztet." +msgid "" +"If you have a very old machine, and the kernel hangs after saying " +"Checking 'hlt' instruction..., then you " +"should try the no-hlt boot argument, which disables " +"this test." +msgstr "" +"Nagyon régi gépnél, ha a kernel megáll itt: Checking 'hlt' " +"instruction..., próbáld a no-hlt " +"indító argumentumot, mely kikapcsolja ezt a tesztet." #. Tag: para #: boot-installer.xml:3463 #, 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 "Ha a képernyő fura képet ad a kernel indításakor, például tiszta fehér, tiszta fekete vagy színes kavar, a rendszer problematikus videó kártyát tartalmazhat, mely hibásan vált framebuffer módra. Ekkor használható a fb=false video=vga16:off ennek kikapcsolására. Ekkor csak az angol nyelv érhető el a telepítés alatt. Lásd ezt: a részletekért." +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 "" +"Ha a képernyő fura képet ad a kernel indításakor, például tiszta fehér, " +"tiszta fekete vagy színes kavar, a rendszer problematikus videó kártyát " +"tartalmazhat, mely hibásan vált framebuffer módra. Ekkor használható a " +"fb=false video=vga16:off ennek kikapcsolására. Ekkor " +"csak az angol nyelv érhető el a telepítés alatt. Lásd ezt: a részletekért." #. Tag: title #: boot-installer.xml:3477 @@ -2625,14 +4077,43 @@ msgstr "A rendszer fagyása a PCMCIA beállító szakaszban" #. Tag: para #: boot-installer.xml:3478 #, 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 "Egyes Dell laptopok összeomlanak, mikor a PCMCIA eszköz-érzékelő megpróbál elérni egyes hardver-címeket. Pár más laptop is haszonló. Ha ilyen gondot tapasztalsz és nincs szükséged PCMCIA támogatásra a telepítéskor, kapcsold ki a hw-detect/start_pcmcia=false indító paraméterrel. A telepítés után beállíthatod és kizárhatod a gondot adó erőforrás-tartományokat." +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 "" +"Egyes Dell laptopok összeomlanak, mikor a PCMCIA eszköz-érzékelő megpróbál " +"elérni egyes hardver-címeket. Pár más laptop is haszonló. Ha ilyen gondot " +"tapasztalsz és nincs szükséged PCMCIA támogatásra a telepítéskor, kapcsold " +"ki a hw-detect/start_pcmcia=false indító " +"paraméterrel. A telepítés után beállíthatod és kizárhatod a gondot adó " +"erőforrás-tartományokat." #. Tag: para #: boot-installer.xml:3488 #, no-c-format -msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter exclude port 0x800-0x8ff here. There is also a list of some common resource range options in the System resource settings section of the PCMCIA HOWTO. Note that you have to omit the commas, if any, when you enter this value in the installer." -msgstr "A telepítő szakértő módban is indítható. Ekkor lehetőség nyílik a hardver igényeinek megfelelő erőforrás-tartományok bevitelére. Például a fenti Dell laptopokon megadható ez: exclude port 0x800-0x8ff. Van egy lista is néhány általános erőforrás-tartomány lehetőségről itt: PCMCIA HOGYAN rendszer erőforrás-beállítások szakasz. A vesszőket el kell hagyni, ha vannak, mikor beírod ezt az értéket a telepítőben." +msgid "" +"Alternatively, you can boot the installer in expert mode. You will then be " +"asked to enter the resource range options your hardware needs. For example, " +"if you have one of the Dell laptops mentioned above, you should enter " +"exclude port 0x800-0x8ff here. There is also a list " +"of some common resource range options in the System resource " +"settings section of the PCMCIA HOWTO. Note that you have to omit the " +"commas, if any, when you enter this value in the installer." +msgstr "" +"A telepítő szakértő módban is indítható. Ekkor lehetőség nyílik a hardver " +"igényeinek megfelelő erőforrás-tartományok bevitelére. Például a fenti Dell " +"laptopokon megadható ez: exclude port 0x800-0x8ff. " +"Van egy lista is néhány általános erőforrás-tartomány lehetőségről itt: " +"PCMCIA HOGYAN rendszer erőforrás-beállítások szakasz. " +"A vesszőket el kell hagyni, ha vannak, mikor beírod ezt az értéket a " +"telepítőben." #. Tag: title #: boot-installer.xml:3505 @@ -2643,8 +4124,21 @@ msgstr "A rendszer fagyása az USB modulok betöltésekor" #. Tag: para #: boot-installer.xml:3506 #, 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 "A kernel alapban megpróbálja telepíteni az USB modulokat és az USB billentyű meghajtót pár nem-szabványos USB billentyű támogatásához. De van pár hibás USB rendszer, ahol a meghajtó lefagy betöltéskor. Ennek egyik elkerülése az USB vezérlő kikapcsolása a BIOS beállításban. Egy másik lehetőség a debian-installer/probe/usb=false paraméter átadása az indító jelnél, mely meggátolja e modulok betöltését." +msgid "" +"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 "" +"A kernel alapban megpróbálja telepíteni az USB modulokat és az USB billentyű " +"meghajtót pár nem-szabványos USB billentyű támogatásához. De van pár hibás " +"USB rendszer, ahol a meghajtó lefagy betöltéskor. Ennek egyik elkerülése az " +"USB vezérlő kikapcsolása a BIOS beállításban. Egy másik lehetőség a " +"debian-installer/probe/usb=false paraméter átadása az " +"indító jelnél, mely meggátolja e modulok betöltését." #. Tag: title #: boot-installer.xml:3520 @@ -2655,8 +4149,36 @@ msgstr "A kernel indító üzenetek értelmezése" #. Tag: para #: boot-installer.xml:3522 #, no-c-format -msgid "During the boot sequence, you may see many messages in the form can't find something , or something not present, can't initialize something , or even this driver release depends on something . Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see )." -msgstr "Az indítás alatt, sok ilyen üzenetet láthatsz: can't find valami , vagy valami not present, can't initialize valami , vagy akár this driver release depends on valami . A legtöbb ilyen nem számít. Azért látod, mert a telepítőben lévő kernel úgy készült, hogy a legkülönbözőbb eszközöket támogassa. Persze egy gépen sincs az összes lehetséges eszköz, és az operációs rendszer jelezheti, ha olyat keres, ami nem található. Ez akkor történik, ha vár egy eszköz válaszára, az adott rendszer pedig nem tartalmaz olyat. Ha ezt túl hosszúnak találod, később egyéni kernelt is készíthetsz (lásd a részt)." +msgid "" +"During the boot sequence, you may see many messages in the form " +"can't find something , or something " +"not present, can't initialize " +"something , or even " +"this driver release depends on something . Most of these messages are harmless. You see " +"them because the kernel for the installation system is built to run on " +"computers with many different peripheral devices. Obviously, no one computer " +"will have every possible peripheral device, so the operating system may emit " +"a few complaints while it looks for peripherals you don't own. You may also " +"see the system pause for a while. This happens when it is waiting for a " +"device to respond, and that device is not present on your system. If you " +"find the time it takes to boot the system unacceptably long, you can create " +"a custom kernel later (see )." +msgstr "" +"Az indítás alatt, sok ilyen üzenetet láthatsz: can't find " +"valami , vagy " +"valami not present, " +"can't initialize valami , vagy akár this driver release depends on " +"valami . A legtöbb ilyen nem " +"számít. Azért látod, mert a telepítőben lévő kernel úgy készült, hogy a " +"legkülönbözőbb eszközöket támogassa. Persze egy gépen sincs az összes " +"lehetséges eszköz, és az operációs rendszer jelezheti, ha olyat keres, ami " +"nem található. Ez akkor történik, ha vár egy eszköz válaszára, az adott " +"rendszer pedig nem tartalmaz olyat. Ha ezt túl hosszúnak találod, később " +"egyéni kernelt is készíthetsz (lásd a " +"részt)." #. Tag: title #: boot-installer.xml:3547 @@ -2667,14 +4189,31 @@ msgstr "Hibajelentő" #. Tag: para #: boot-installer.xml:3548 #, 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 "Ha túljutottál a kezdő indító szakaszon, de nem futott le teljesen végig a telepítés, a hibajelentő menü segíthet. Eltárolhatod a rendszer hiba naplóit és beállításait a telepítőből egy flopira, vagy letöltheted egy böngészőben. Ezek megadják a felmerült hibákat és javításukat. Ha jelentést küldesz, csatolhatod hozzá ezeket." +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 "" +"Ha túljutottál a kezdő indító szakaszon, de nem futott le teljesen végig a " +"telepítés, a hibajelentő menü segíthet. Eltárolhatod a rendszer hiba naplóit " +"és beállításait a telepítőből egy flopira, vagy letöltheted egy böngészőben. " +"Ezek megadják a felmerült hibákat és javításukat. Ha jelentést küldesz, " +"csatolhatod hozzá ezeket." #. Tag: para #: boot-installer.xml:3559 #, no-c-format -msgid "Other pertinent installation messages may be found in /var/log/ during the installation, and /var/log/installer/ after the computer has been booted into the installed system." -msgstr "További telepítő üzenetek találhatók a /var/log/ könyvtárban a telepítés során és a /var/log/installer/ könyvtárban, miután a gép a telepített rendszert elindította." +msgid "" +"Other pertinent installation messages may be found in /var/log/ during the installation, and /var/log/installer/ after the computer has been booted into the installed system." +msgstr "" +"További telepítő üzenetek találhatók a /var/log/ " +"könyvtárban a telepítés során és a /var/log/installer/ " +"könyvtárban, miután a gép a telepített rendszert elindította." #. Tag: title #: boot-installer.xml:3570 @@ -2685,20 +4224,38 @@ msgstr "Telepítő jelentések küldése" #. Tag: para #: boot-installer.xml:3571 #, no-c-format -msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations." -msgstr "Ha még mindig gondjaid vannak, kérjük, küldj telepítő jelentést. Siker esetén és kérünk erre, mert így a lehető legtöbb adatot kapjuk a legtöbb hardver összeállításról." +msgid "" +"If you still have problems, please submit an installation report. We also " +"encourage installation reports to be sent even if the installation is " +"successful, so that we can get as much information as possible on the " +"largest number of hardware configurations." +msgstr "" +"Ha még mindig gondjaid vannak, kérjük, küldj telepítő jelentést. Siker " +"esetén és kérünk erre, mert így a lehető legtöbb adatot kapjuk a legtöbb " +"hardver összeállításról." #. Tag: para #: boot-installer.xml:3578 #, 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." +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:3585 #, 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" +"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" @@ -2733,9 +4290,15 @@ msgid "" "\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" +" 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" @@ -2770,5 +4333,6 @@ msgstr "" "\n" "<Telepítés leírása prózaian és bármilyen gondolat, megjegyzés\n" " és ötlet a kezdeti telepítés során.>\n" -" A jelentésben írd le az esetleges hibát, ha a kernel leállna, annak utolsó látható üzeneteit is. Írd le, mely lépések okozták a gondot." - +" A jelentésben írd le az esetleges hibát, ha a " +"kernel leállna, annak utolsó látható üzeneteit is. Írd le, mely lépések " +"okozták a gondot." diff --git a/po/ko/boot-installer.po b/po/ko/boot-installer.po index bbd314e3f..9173f95bd 100644 --- a/po/ko/boot-installer.po +++ b/po/ko/boot-installer.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: boot-installer.xml\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-11-04 17:26+0000\n" +"POT-Creation-Date: 2006-11-10 03:17+0000\n" "PO-Revision-Date: 2006-10-07 17:00+0900\n" "Last-Translator: Seok-moon Jang \n" "Language-Team: Korean \n" @@ -4364,13 +4364,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:3363 -#, no-c-format +#, fuzzy, 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 " +"failures in the driver floppies, most of which indicate themselves with a " "flood of messages about disk I/O errors." msgstr "" "부트 플로피가 가장 문제가 많은 플로피입니다. 부트 플로피는 리눅스가 아니라 하" @@ -4384,10 +4384,11 @@ msgstr "" #, fuzzy, no-c-format msgid "" "If you are having the installation stall at a particular floppy, the first " -"thing you should 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." +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. Simply reformatting the old " +"floppy may not be sufficient, even if it appears that the floppy was " +"reformatted and written with no errors. It is sometimes useful to try " +"writing the floppy on a different system." msgstr "" "설치 도중에 특정 플로피에서 멈추는 현상이 발생하면, 가장 먼저 할 일은 플로피 " "디스크 이미지를 다시 받아서 다른 플로피에 만들어 보는 것" @@ -4398,21 +4399,21 @@ msgstr "" #: boot-installer.xml:3381 #, no-c-format msgid "" -"Normally you should not have download a floppy image again, but if you are " -"experiencing problems it is always useful to verify that the images were " -"downloaded correctly by verifying their md5sums." +"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 "" +"어떤 사용자는 플로피가 제대로 동작할 때까지 이미지를 무려 세 번 써야 했다고 하고, 세 번째 플로피에서 제대로 동작했다고 합니다." #. Tag: para #: boot-installer.xml:3387 #, 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." +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." msgstr "" -"어떤 사용자는 플로피가 제대로 동작할 때까지 이미지를 무려 세 번 써야 했다고 하고, 세 번째 플로피에서 제대로 동작했다고 합니다." #. Tag: para #: boot-installer.xml:3393 diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index a04bb250a..cc684a7cf 100644 --- a/po/pot/boot-installer.pot +++ b/po/pot/boot-installer.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-11-04 17:26+0000\n" +"POT-Creation-Date: 2006-11-10 03:17+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -2363,25 +2363,25 @@ msgstr "" #. Tag: para #: boot-installer.xml:3363 #, 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." +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 "" #. Tag: para #: boot-installer.xml:3372 #, no-c-format -msgid "If you are having the installation stall at a particular floppy, the first thing you should 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." +msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a different floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system." msgstr "" #. Tag: para #: boot-installer.xml:3381 #, no-c-format -msgid "Normally you should not have download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums." +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 "" #. Tag: para #: boot-installer.xml:3387 #, 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." +msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums." msgstr "" #. Tag: para diff --git a/po/pt/boot-installer.po b/po/pt/boot-installer.po index 09f93f3dc..bc2b7f5f6 100644 --- a/po/pt/boot-installer.po +++ b/po/pt/boot-installer.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: boot-installer\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-11-04 17:26+0000\n" +"POT-Creation-Date: 2006-11-10 03:17+0000\n" "PO-Revision-Date: 2006-11-04 18:57+0000\n" "Last-Translator: Miguel Figueiredo \n" "Language-Team: Portuguese \n" @@ -4155,7 +4155,10 @@ msgid "" "userinput> See for details about using this " "to automate installs." msgstr "" -"Perguntas retardadas são normalmente perguntadas antes de ser possível de fazer preseed até depois da rede estar configurada. Forma abreviada: auto=true Para detalhes acerca de como utilizar isto para auomatizar instalações veja ." +"Perguntas retardadas são normalmente perguntadas antes de ser possível de " +"fazer preseed até depois da rede estar configurada. Forma abreviada: " +"auto=true Para detalhes acerca de como utilizar isto " +"para auomatizar instalações veja ." #. Tag: term #: boot-installer.xml:3069 @@ -4316,7 +4319,6 @@ msgstr "" msgid "3c509.xcvr=3 3c509.irq=10" msgstr "3c509.xcvr=3 3c509.irq=10" - #. Tag: title #: boot-installer.xml:3165 #, no-c-format @@ -4369,7 +4371,8 @@ msgid "" "If the CD-ROM does not boot, check that it was inserted correctly and that " "it is not dirty." msgstr "" -"Se o CD-ROM não arrancar, verifique se foi inserido correctamente e se não está sujo." +"Se o CD-ROM não arrancar, verifique se foi inserido correctamente e se não " +"está sujo." #. Tag: para #: boot-installer.xml:3195 @@ -4380,9 +4383,10 @@ msgid "" "menuchoice> a second time. Some DMA related isses with older CD-ROM drives " "are known to be resolved in this way." msgstr "" -"Se o instalador falhar o reconhecimento de um CD-ROM, tente apenas correr a opção " -" Detectar e montar o CD-ROM uma segunda vez. É conhecido que alguns problemas relacionados com DMA em leitores de CD-ROM antigos se resolvem desta forma." +"Se o instalador falhar o reconhecimento de um CD-ROM, tente apenas correr a " +"opção Detectar e montar o CD-ROM uma segunda vez. É conhecido que alguns problemas relacionados " +"com DMA em leitores de CD-ROM antigos se resolvem desta forma." #. Tag: para #: boot-installer.xml:3205 @@ -4392,8 +4396,9 @@ msgid "" "Most, but not all, suggestions discussed there are valid for both CD-ROM and " "DVD, but we'll use the term CD-ROM for simplicity." msgstr "" -"Se isto não funcionar, então tente as sugestões nas sub-secções abaixo. " -"A maioria, mas não todas, as sugestões discutidas são válidas quer para CD-ROM quer para DVD, mas utilizaremos o termo CD-ROM pela simplicidade." +"Se isto não funcionar, então tente as sugestões nas sub-secções abaixo. A " +"maioria, mas não todas, as sugestões discutidas são válidas quer para CD-ROM " +"quer para DVD, mas utilizaremos o termo CD-ROM pela simplicidade." #. Tag: para #: boot-installer.xml:3211 @@ -4663,13 +4668,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:3363 -#, no-c-format +#, fuzzy, 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 " +"failures in the driver floppies, most of which indicate themselves with a " "flood of messages about disk I/O errors." msgstr "" "A disquete de arranque é a disquete com os piores problemas, porque é lida " @@ -4681,13 +4686,14 @@ msgstr "" #. Tag: para #: boot-installer.xml:3372 -#, no-c-format +#, fuzzy, no-c-format msgid "" "If you are having the installation stall at a particular floppy, the first " -"thing you should 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." +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. Simply reformatting the old " +"floppy may not be sufficient, even if it appears that the floppy was " +"reformatted and written with no errors. It is sometimes useful to try " +"writing the floppy on a different system." msgstr "" "Se está a enfrentar paragens da instalação numa disquete em particular, a " "primeira coisa que deve fazer é gravá-la para uma disquete " @@ -4700,18 +4706,6 @@ msgstr "" #: boot-installer.xml:3381 #, no-c-format msgid "" -"Normally you should not have download a floppy image again, but if you are " -"experiencing problems it is always useful to verify that the images were " -"downloaded correctly by verifying their md5sums." -msgstr "" -"Normalmente deve fazer novamente o download da imagem da disquete, mas se " -"está a ter problemas é sempre útil verificar que foi feito correctamente o " -"download das imagens verificando o seu md5sum." - -#. Tag: para -#: boot-installer.xml:3387 -#, 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." @@ -4720,6 +4714,18 @@ msgstr "" "três vezes antes de funcionar, e após isso tudo ficou " "bem com a terceira disquete." +#. Tag: para +#: boot-installer.xml:3387 +#, fuzzy, no-c-format +msgid "" +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." +msgstr "" +"Normalmente deve fazer novamente o download da imagem da disquete, mas se " +"está a ter problemas é sempre útil verificar que foi feito correctamente o " +"download das imagens verificando o seu md5sum." + #. Tag: para #: boot-installer.xml:3393 #, no-c-format diff --git a/po/ru/boot-installer.po b/po/ru/boot-installer.po index 0a64a5281..07a89d4bf 100644 --- a/po/ru/boot-installer.po +++ b/po/ru/boot-installer.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: boot-installer\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-11-04 17:26+0000\n" +"POT-Creation-Date: 2006-11-10 03:17+0000\n" "PO-Revision-Date: 2006-11-05 10:46+0300\n" "Last-Translator: Yuri Kozlov \n" "Language-Team: Russian \n" @@ -14,7 +14,8 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: KBabel 1.11.2\n" -"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%" +"10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" #. Tag: title #: boot-installer.xml:4 @@ -1031,7 +1032,8 @@ msgstr "" #: 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 ." +msgid "" +"If you have problems booting, see ." msgstr "" "При возникновении проблем с загрузкой смотрите ." @@ -1202,7 +1204,8 @@ msgstr "Загрузка с CD-ROM" #. Tag: title #: boot-installer.xml:848 #, no-c-format -msgid "Booting from Linux Using LILO or GRUB" +msgid "" +"Booting from Linux Using LILO or GRUB" msgstr "" "Загрузка из Linux с помощью LILO или GRUB" @@ -1504,7 +1507,8 @@ msgstr "Сетевая карта с сетевым BootROM" msgid "" "It could be that your Network Interface Card provides TFTP boot " "functionality." -msgstr "Возможно, что сетевая карта (NIC) предоставляет возможность загрузки по TFTP." +msgstr "" +"Возможно, что сетевая карта (NIC) предоставляет возможность загрузки по TFTP." #. Tag: para #: boot-installer.xml:1045 @@ -3286,7 +3290,8 @@ msgstr "Загрузка с карты памяти USB" #: boot-installer.xml:2439 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." -msgstr "В настоящий момент системы NewWorld PowerMac можно загружать с USB устройств." +msgstr "" +"В настоящий момент системы NewWorld PowerMac можно загружать с USB устройств." #. Tag: para #: boot-installer.xml:2445 @@ -4135,11 +4140,10 @@ msgid "" "userinput> See for details about using this " "to automate installs." msgstr "" -"Отложить вопросы, которые обычно задаются перед автоматической " -"установкой, которые можно задать после настройки сети. " -"Сокращённая форма: auto=true " -"Подробней об автоматизации установки смотрите " -"в ." +"Отложить вопросы, которые обычно задаются перед автоматической установкой, " +"которые можно задать после настройки сети. Сокращённая форма: " +"auto=true Подробней об автоматизации установки " +"смотрите в ." #. Tag: term #: boot-installer.xml:3069 @@ -4188,7 +4192,8 @@ msgstr "ramdisk_size" #: boot-installer.xml:3091 #, no-c-format msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." -msgstr "Если вы используете ядро 2.2.x, может потребоваться установить &ramdisksize;." +msgstr "" +"Если вы используете ядро 2.2.x, может потребоваться установить &ramdisksize;." #. Tag: term #: boot-installer.xml:3099 @@ -4244,15 +4249,14 @@ msgid "" "thus be used when the modules are actually loaded. The parameters will also " "be propagated automatically to the configuration for the installed system." msgstr "" -"Если драйверы встроены в ядро, вы можете передать им параметры как " -"это описано в документации к ядру. Если же драйверы собраны как " -"модули и так как модули ядра загружаются немного по-другому чем " -"при загрузке установленной системы, невозможно передать " -"параметры модулям обычным способом. Вместо этого вам нужно " -"использовать специальный синтаксис, распознаваемый программой " -"установки, которая сохраняет эти параметры в нужные конфигурационные " -"файлы, для того чтобы использовать их при загрузке модуля. Параметры " -"также будут автоматически включены в конфигурацию установленной " +"Если драйверы встроены в ядро, вы можете передать им параметры как это " +"описано в документации к ядру. Если же драйверы собраны как модули и так как " +"модули ядра загружаются немного по-другому чем при загрузке установленной " +"системы, невозможно передать параметры модулям обычным способом. Вместо " +"этого вам нужно использовать специальный синтаксис, распознаваемый " +"программой установки, которая сохраняет эти параметры в нужные " +"конфигурационные файлы, для того чтобы использовать их при загрузке модуля. " +"Параметры также будут автоматически включены в конфигурацию установленной " "системы." #. Tag: para @@ -4264,10 +4268,10 @@ msgid "" "system and set good defaults that way. However, in some situations it may " "still be needed to set parameters manually." msgstr "" -"Заметим, что теперь редко требуется указывать параметры модулям. " -"В большинстве случаев ядро способно само определить имеющееся " -"оборудование в системе и настроить его правильно. Однако иногда " -"всё ещё может потребоваться установка параметров вручную." +"Заметим, что теперь редко требуется указывать параметры модулям. В " +"большинстве случаев ядро способно само определить имеющееся оборудование в " +"системе и настроить его правильно. Однако иногда всё ещё может потребоваться " +"установка параметров вручную." #. Tag: para #: boot-installer.xml:3143 @@ -4282,8 +4286,7 @@ msgid "" "network interface card to use the BNC (coax) connector and IRQ 10, you would " "pass:" msgstr "" -"Синтаксис установки параметров модулей: " -"\n" +"Синтаксис установки параметров модулей: \n" "имя_модуля.имя_параметра=значение\n" " Если требуется передать несколько параметров " @@ -4339,8 +4342,8 @@ msgstr "" #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" -"Есть несколько простых вещей, которые вы можете попробовать сделать " -"в первую очередь." +"Есть несколько простых вещей, которые вы можете попробовать сделать в первую " +"очередь." #. Tag: para #: boot-installer.xml:3189 @@ -4349,8 +4352,8 @@ msgid "" "If the CD-ROM does not boot, check that it was inserted correctly and that " "it is not dirty." msgstr "" -"Если с CD-ROM не получается загрузиться, проверьте, что он вставлен правильно " -"и что диск не грязный." +"Если с CD-ROM не получается загрузиться, проверьте, что он вставлен " +"правильно и что диск не грязный." #. Tag: para #: boot-installer.xml:3195 @@ -4361,11 +4364,10 @@ msgid "" "menuchoice> a second time. Some DMA related isses with older CD-ROM drives " "are known to be resolved in this way." msgstr "" -"Если программа установки не смогла определить CD-ROM, попробуйте " -"выполнить пункт меню " -" Поиск и монтирование CD-ROM второй раз. Некоторые проблемы с DMA на старых приводах CD-ROM " -"решаются таким способом." +"Если программа установки не смогла определить CD-ROM, попробуйте выполнить " +"пункт меню Поиск и монтирование CD-ROM второй раз. Некоторые проблемы с DMA на старых " +"приводах CD-ROM решаются таким способом." #. Tag: para #: boot-installer.xml:3205 @@ -4375,9 +4377,9 @@ msgid "" "Most, but not all, suggestions discussed there are valid for both CD-ROM and " "DVD, but we'll use the term CD-ROM for simplicity." msgstr "" -"Если это не сработало, попробуйте советы данные ниже. " -"Хотя большинство, но не все, описываемые предложения работают и " -"для CD-ROM и для DVD, для простоты мы будем использовать термин CD-ROM." +"Если это не сработало, попробуйте советы данные ниже. Хотя большинство, но " +"не все, описываемые предложения работают и для CD-ROM и для DVD, для " +"простоты мы будем использовать термин CD-ROM." #. Tag: para #: boot-installer.xml:3211 @@ -4437,7 +4439,8 @@ msgstr "Как изучать и может быть решить проблем #: boot-installer.xml:3247 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." -msgstr "Если с CD-ROM не удаётся загрузиться, попробуйте способы указанные ниже." +msgstr "" +"Если с CD-ROM не удаётся загрузиться, попробуйте способы указанные ниже." #. Tag: para #: boot-installer.xml:3252 @@ -4646,13 +4649,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:3363 -#, no-c-format +#, fuzzy, 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 " +"failures in the driver floppies, most of which indicate themselves with a " "flood of messages about disk I/O errors." msgstr "" "Загрузочная дискета — это самая проблемная дискета, потому что она " @@ -4664,13 +4667,14 @@ msgstr "" #. Tag: para #: boot-installer.xml:3372 -#, no-c-format +#, fuzzy, no-c-format msgid "" "If you are having the installation stall at a particular floppy, the first " -"thing you should 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." +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. Simply reformatting the old " +"floppy may not be sufficient, even if it appears that the floppy was " +"reformatted and written with no errors. It is sometimes useful to try " +"writing the floppy on a different system." msgstr "" "Если установка замирает на какой-то дискете, сперва попробуйте записать " "образ на другую дискету. Простого переформатирования " @@ -4682,18 +4686,6 @@ msgstr "" #: boot-installer.xml:3381 #, no-c-format msgid "" -"Normally you should not have download a floppy image again, but if you are " -"experiencing problems it is always useful to verify that the images were " -"downloaded correctly by verifying their md5sums." -msgstr "" -"Обычно не нужно скачивать образ дискет ещё раз, но если вы испытываете " -"проблемы, всегда полезно проверить корректность загруженных образов с " -"помощью md5sums." - -#. Tag: para -#: boot-installer.xml:3387 -#, 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." @@ -4701,6 +4693,18 @@ msgstr "" "Один пользователь сообщил, что он записывал образ на дискету три раза, прежде чем она заработала, и затем всё пошло нормально." +#. Tag: para +#: boot-installer.xml:3387 +#, fuzzy, no-c-format +msgid "" +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." +msgstr "" +"Обычно не нужно скачивать образ дискет ещё раз, но если вы испытываете " +"проблемы, всегда полезно проверить корректность загруженных образов с " +"помощью md5sums." + #. Tag: para #: boot-installer.xml:3393 #, no-c-format @@ -5135,4 +5139,3 @@ msgstr "" "проблема, включая последние увиденные сообщения ядра в случае повисания " "ядра. Опишите шаги, которые вы делали, чтобы привести систему в проблемное " "состояние." - diff --git a/po/sv/boot-installer.po b/po/sv/boot-installer.po index a65256b71..7332b21b1 100644 --- a/po/sv/boot-installer.po +++ b/po/sv/boot-installer.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: installation-guide 20051025 boot-installer\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-11-04 17:26+0000\n" +"POT-Creation-Date: 2006-11-10 03:17+0000\n" "PO-Revision-Date: 2006-11-04 21:10+0100\n" "Last-Translator: Daniel Nylander \n" "Language-Team: Swedish \n" @@ -35,56 +35,139 @@ msgstr "Konsollfirmware för Alpha" #. 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 "Konsollfirmware lagras i ett flash-rom och startas när ett Alpha-system slås på eller startas om. Det finns två olika konsollspecifikationer som används på Alpha-system och därav finns det två klasser av konsollfirmware tillgängliga:" +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 "" +"Konsollfirmware lagras i ett flash-rom och startas när ett Alpha-system slås " +"på eller startas om. Det finns två olika konsollspecifikationer som används " +"på Alpha-system och därav finns det två klasser av konsollfirmware " +"tillgängliga:" #. 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 "SRM-konsoll, baserad på specifikationen Alpha Console Subsystem, som tillhandahåller ett operativmiljö för operativsystemen OpenVMS, Tru64 UNIX och Linux." +msgid "" +"SRM console, based on the Alpha Console Subsystem " +"specification, which provides an operating environment for OpenVMS, Tru64 " +"UNIX, and Linux operating systems." +msgstr "" +"SRM-konsoll, baserad på specifikationen Alpha Console " +"Subsystem, som tillhandahåller ett operativmiljö för operativsystemen " +"OpenVMS, Tru64 UNIX och Linux." #. 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 "ARC, AlphaBIOS eller ARCSBIOS-konsoll, baserad på specifikationen Advanced RISC Computing (ARC), som tillhandahåller en operativmiljö för Windows NT." +msgid "" +"ARC, AlphaBIOS, or ARCSBIOS console, based on the " +"Advanced RISC Computing (ARC) specification, which provides an operating " +"environment for Windows NT." +msgstr "" +"ARC, AlphaBIOS eller ARCSBIOS-konsoll, baserad på " +"specifikationen Advanced RISC Computing (ARC), som tillhandahåller en " +"operativmiljö för Windows NT." #. 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 "Från användarens perspektiv är den mest viktiga skillnaden mellan SRM och ARC den att valet av konsoll begränsar den möjliga diskpartitionsplanen för hårddisken som du önskar starta upp från." +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 "" +"Från användarens perspektiv är den mest viktiga skillnaden mellan SRM och " +"ARC den att valet av konsoll begränsar den möjliga diskpartitionsplanen för " +"hårddisken som du önskar starta upp från." #. 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 "ARC kräver att du använder en MS-DOS-partitionstabell (som skapas av cfdisk) för uppstartsdisken. Därför är MS-DOS-partitionstabeller det ursprungliga partitionsformatet vid uppstarter från ARC. Faktum är att eftersom AlphaBIOS innehåller ett diskpartitioneringsverktyg kanske du föredrar att partitionera dina diskar från firmwaremenyerna före installation av Linux." +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 "" +"ARC kräver att du använder en MS-DOS-partitionstabell (som skapas av " +"cfdisk) för uppstartsdisken. Därför är MS-DOS-" +"partitionstabeller det ursprungliga partitionsformatet vid " +"uppstarter från ARC. Faktum är att eftersom AlphaBIOS innehåller ett " +"diskpartitioneringsverktyg kanske du föredrar att partitionera dina diskar " +"från firmwaremenyerna före installation av Linux." #. 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 "Motsatt är SRM inkompatibel Specifikt är formatet på uppstartssektorn som krävs av Console Subsystem Specification i konflikt med placeringen av DOS-partitionstabellen. med MS-DOS-partitionstabeller. Eftersom Tru64 Unix använder formatet för BSD-disketiketter, är det här det ursprungliga (native) partitionsformatet för SRM-installationer." +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 "" +"Motsatt är SRM inkompatibel Specifikt " +"är formatet på uppstartssektorn som krävs av Console Subsystem Specification " +"i konflikt med placeringen av DOS-partitionstabellen. " +"med MS-DOS-partitionstabeller. Eftersom Tru64 Unix använder formatet för BSD-" +"disketiketter, är det här det ursprungliga (native) " +"partitionsformatet för SRM-installationer." #. 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 "GNU/Linux är det enda operativsystemet på Alpha som kan startas upp från båda konsolltyperna, men &debian; &release; har endast stöd för uppstart på SRM-baserade system. Om du har en Alpha som det inte finns någon SRM-version tillgänglig för, om du vill använda dubbel-uppstart tillsammans med Windows NT, eller om din uppstartsenhet kräver stöd för ARC-konsoll för initiering av BIOS kommer du inte kunna använda installeraren för &debian; &release;. Du kan fortfarande köra &debian; &release; på sådana system genom att använda andra installationsmedia, till exempel kan du installera Debian woody med MILO och uppgradera." +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 "" +"GNU/Linux är det enda operativsystemet på Alpha som kan startas upp från " +"båda konsolltyperna, men &debian; &release; har endast stöd för uppstart på " +"SRM-baserade system. Om du har en Alpha som det inte finns någon SRM-version " +"tillgänglig för, om du vill använda dubbel-uppstart tillsammans med Windows " +"NT, eller om din uppstartsenhet kräver stöd för ARC-konsoll för initiering " +"av BIOS kommer du inte kunna använda installeraren för &debian; &release;. " +"Du kan fortfarande köra &debian; &release; på sådana system genom att " +"använda andra installationsmedia, till exempel kan du installera Debian " +"woody med MILO och uppgradera." #. 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 "På grund av att MILO inte finns tillgänglig för någon av Alpha-systemen för tillfället i produktion (i februari 2000), och på grund att det inte längre är nödvändigt att köra en licens för OpenVMS eller Tru64 Unix för att få SRM-firmware på din äldre Alpha, rekommenderas det att du använder SRM om möjligt." +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 "" +"På grund av att MILO inte finns tillgänglig för någon av " +"Alpha-systemen för tillfället i produktion (i februari 2000), och på grund " +"att det inte längre är nödvändigt att köra en licens för OpenVMS eller Tru64 " +"Unix för att få SRM-firmware på din äldre Alpha, rekommenderas det att du " +"använder SRM om möjligt." #. 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 "Följande tabell sammanställer tillgängliga och systemtyper/konsollkombinationer som stöds (se för namnen på systemtyperna). Ordet ARC nedan below indikerar någon av de ARC-godkända konsollerna." +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 "" +"Följande tabell sammanställer tillgängliga och systemtyper/" +"konsollkombinationer som stöds (se för namnen " +"på systemtyperna). Ordet ARC nedan below indikerar någon av " +"de ARC-godkända konsollerna." #. Tag: entry #: boot-installer.xml:107 @@ -105,20 +188,11 @@ msgid "alcor" msgstr "alcor" #. Tag: entry -#: boot-installer.xml:115 -#: boot-installer.xml:118 -#: boot-installer.xml:124 -#: boot-installer.xml:130 -#: boot-installer.xml:133 -#: boot-installer.xml:136 -#: boot-installer.xml:139 -#: boot-installer.xml:145 -#: boot-installer.xml:148 -#: boot-installer.xml:151 -#: boot-installer.xml:160 -#: boot-installer.xml:169 -#: boot-installer.xml:184 -#: boot-installer.xml:187 +#: boot-installer.xml:115 boot-installer.xml:118 boot-installer.xml:124 +#: boot-installer.xml:130 boot-installer.xml:133 boot-installer.xml:136 +#: boot-installer.xml:139 boot-installer.xml:145 boot-installer.xml:148 +#: boot-installer.xml:151 boot-installer.xml:160 boot-installer.xml:169 +#: boot-installer.xml:184 boot-installer.xml:187 #, no-c-format msgid "ARC or SRM" msgstr "ARC eller SRM" @@ -136,15 +210,9 @@ msgid "book1" msgstr "book1" #. Tag: entry -#: boot-installer.xml:121 -#: boot-installer.xml:127 -#: boot-installer.xml:142 -#: boot-installer.xml:154 -#: boot-installer.xml:163 -#: boot-installer.xml:166 -#: boot-installer.xml:172 -#: boot-installer.xml:178 -#: boot-installer.xml:181 +#: boot-installer.xml:121 boot-installer.xml:127 boot-installer.xml:142 +#: boot-installer.xml:154 boot-installer.xml:163 boot-installer.xml:166 +#: boot-installer.xml:172 boot-installer.xml:178 boot-installer.xml:181 #, no-c-format msgid "SRM only" msgstr "Endast SRM" @@ -264,9 +332,7 @@ msgid "ruffian" msgstr "ruffian" #. Tag: entry -#: boot-installer.xml:175 -#: boot-installer.xml:190 -#: boot-installer.xml:193 +#: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193 #, no-c-format msgid "ARC only" msgstr "Endast ARC" @@ -310,70 +376,151 @@ 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 "Generellt sett kan ingen av dessa konsoller starta upp Linux direkt, så behovet av en mellanliggande starthanterare finns. För SRM-konsollen används aboot, en liten, plattformsoberoende starthanterare. Se (tyvärr föråldrad) SRM HOWTO för mer information om aboot." +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 "" +"Generellt sett kan ingen av dessa konsoller starta upp Linux direkt, så " +"behovet av en mellanliggande starthanterare finns. För SRM-konsollen används " +"aboot, en liten, plattformsoberoende starthanterare. Se " +"(tyvärr föråldrad) SRM HOWTO för mer " +"information om aboot." #. 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 "Följande paragrafer kommer från installationshandboken för woody och inkluderas här som referens: de kan vara användbara för någon vid ett senare datum när Debian har stöd för MILO-baserade installationer igen." +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 "" +"Följande paragrafer kommer från installationshandboken för woody och " +"inkluderas här som referens: de kan vara användbara för någon vid ett senare " +"datum när Debian har stöd för MILO-baserade installationer igen." #. 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 "Generellt sett kan ingen av dessa konsoller starta upp Linux direkt, så behovet av en mellanliggande starthanterare finns. Det finns två huvudsakliga Linux-inläsare: MILO och aboot." +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 "" +"Generellt sett kan ingen av dessa konsoller starta upp Linux direkt, så " +"behovet av en mellanliggande starthanterare finns. Det finns två " +"huvudsakliga Linux-inläsare: MILO och 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 "MILO är själv en konsoll, som ersätter ARC eller SRM i minnet. MILO kan startas upp från både ARC och SRM och är det enda sättet att bootstrapa Linux från ARC-konsollen. MILO är plattformsspecifik (olika MILO behövs för varje systemtyp) och existerar för de systemen, för vilka ARC-stöd visas i tabellen ovan.. Se även (tyvärr föråldrad) MILO HOWTO." +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 "" +"MILO är själv en konsoll, som ersätter ARC eller SRM i " +"minnet. MILO kan startas upp från både ARC och SRM och är " +"det enda sättet att bootstrapa Linux från ARC-konsollen. MILO är plattformsspecifik (olika MILO behövs för " +"varje systemtyp) och existerar för de systemen, för vilka ARC-stöd visas i " +"tabellen ovan.. Se även (tyvärr föråldrad) MILO HOWTO." #. 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 "aboot är en liten, plattformsoberoende starthanterare, som endast körs från SRM. Se (även den föråldrad) SRM HOWTO för mer information om aboot." +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 "" +"aboot är en liten, plattformsoberoende starthanterare, " +"som endast körs från SRM. Se (även den föråldrad) SRM HOWTO för mer information om aboot." #. 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" +"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." +" 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 "" -"Därav är tre scenarion generellt sett möjliga, beroende på systemets konsollfirmware och huruvida MILO finns tillgänglig eller inte: \n" +"Därav är tre scenarion generellt sett möjliga, beroende på systemets " +"konsollfirmware och huruvida MILO finns tillgänglig eller " +"inte: \n" "SRM -> aboot\n" "SRM -> MILO\n" "ARC -> MILO\n" -" Därför att MILO inte finns tillgänglig för någon av de Alpha-system som för närvarande produceras (från och med februari 2000), och på grund av att det inte längre är nödvändigt att köpa en licens för OpenVMS eller Tru64 Unix för att få SRM-firmware på din äldre Alpha, rekommenderas det att du använder SRM och aboot på nyare installationer av GNU/Linux, om inte du önskar att även starta upp med Windows NT." +" Därför att MILO inte finns " +"tillgänglig för någon av de Alpha-system som för närvarande produceras (från " +"och med februari 2000), och på grund av att det inte längre är nödvändigt " +"att köpa en licens för OpenVMS eller Tru64 Unix för att få SRM-firmware på " +"din äldre Alpha, rekommenderas det att du använder SRM och aboot på nyare installationer av GNU/Linux, om inte du önskar att även " +"starta upp med Windows NT." #. 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 "Majoriteten av de AlphaServer-modeller och alla nuvarande server- och arbetsstationsprodukter innehåller både SRM och AlphaBIOS i sina firmware. För half-flash-maskiner såsom de olika evalueringskorten, är det möjligt att byta från en version till en annan genom att skriva om firmware. När SRM har installerats, är det möjligt att köra ARC/AlphaBIOS från en diskett (med kommandot arc). Med anledningarna nämnda ovan, rekommenderar vi ett byte till SRM före installation av &debian;." +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 "" +"Majoriteten av de AlphaServer-modeller och alla nuvarande server- och " +"arbetsstationsprodukter innehåller både SRM och AlphaBIOS i sina firmware. " +"För half-flash-maskiner såsom de olika evalueringskorten, är " +"det möjligt att byta från en version till en annan genom att skriva om " +"firmware. När SRM har installerats, är det möjligt att köra ARC/AlphaBIOS " +"från en diskett (med kommandot arc). Med anledningarna " +"nämnda ovan, rekommenderar vi ett byte till SRM före installation av " +"&debian;." #. 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 "Som på andra arkitekturer, bör du installera de senaste tillgängliga revisionen av firmware Utom på Jensen, där Linux inte stöds på firmware-versioner senare än 1.7 — se för mer information. före installation av &debian;. För Alpha, uppdateringar av firmware kan hämtas från Alpha Firmware Updates." +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 "" +"Som på andra arkitekturer, bör du installera de senaste tillgängliga " +"revisionen av firmware Utom på Jensen, där Linux inte stöds " +"på firmware-versioner senare än 1.7 — se för mer information. före installation " +"av &debian;. För Alpha, uppdateringar av firmware kan hämtas från Alpha Firmware Updates." #. Tag: title -#: boot-installer.xml:283 -#: boot-installer.xml:997 -#: boot-installer.xml:1488 -#: boot-installer.xml:1983 -#: boot-installer.xml:2065 -#: boot-installer.xml:2154 -#: boot-installer.xml:2498 -#: boot-installer.xml:2594 +#: boot-installer.xml:283 boot-installer.xml:997 boot-installer.xml:1488 +#: boot-installer.xml:1983 boot-installer.xml:2065 boot-installer.xml:2154 +#: boot-installer.xml:2498 boot-installer.xml:2594 #, no-c-format msgid "Booting with TFTP" msgstr "Uppstart via TFTP" @@ -382,51 +529,86 @@ msgstr "Uppstart via TFTP" #: 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" +"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" +" You first need to set the boot protocol: " +"\n" ">>> set ewa0_protocols bootp\n" -" Then check the medium type is correct: \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." +" You can get a listing of valid modes with " +">>>set ewa0_mode." msgstr "" -"I SRM är Ethernet-gränssnitten namngivna med prefixet ewa, och kommer att listas i utskriften från kommandot show dev, som denna (delvis redigerat): \n" +"I SRM är Ethernet-gränssnitten namngivna med prefixet ewa, och kommer att listas i utskriften från kommandot " +"show dev, som denna (delvis redigerat): " +"\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" -" Du behöver först ställa in uppstartsprotokollet: \n" +" Du behöver först ställa in uppstartsprotokollet: " +"\n" ">>> set ewa0_protocol bootp\n" -" Kontrollera sedan att mediatypen är korrekt: \n" +" Kontrollera sedan att mediatypen är korrekt: " +"\n" ">>> set ewa0_mode läge\n" -" Du kan få en lista på giltiga lägen med >>>set ewa0_mode." +" Du kan få en lista på giltiga lägen med " +">>>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" +"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." +" This will boot using the default kernel " +"parameters as included in the netboot image." msgstr "" -"Sedan, för att starta upp från det första Ethernet-gränssnittet, kan du skriva: \n" +"Sedan, för att starta upp från det första Ethernet-gränssnittet, kan du " +"skriva: \n" ">>> boot ewa0 -flags \"\"\n" -" Det här kommer att starta upp med de kärnparametrar som är standard och som inkluderats i netboot-avbilden." +" Det här kommer att starta upp med de " +"kärnparametrar som är standard och som inkluderats i netboot-avbilden." #. 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 "Om du önskar att använda en seriekonsoll, måste du skicka med parametern console= till kärnan. Det kan göras med argumentet -flags till SRM-kommandot boot. Serieportarna har samma namn som sina motsvarande filer i /dev. När ytterligare kärnparametrar anges, måste du upprepa vissa standardalternativ som behövs av &d-i;-avbilderna. Till exempel, för att starta upp från ewa0 och använda en konsoll på första serieporten, skulle du skriva:" +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 "" +"Om du önskar att använda en seriekonsoll, måste du " +"skicka med parametern console= till kärnan. Det kan " +"göras med argumentet -flags till SRM-kommandot " +"boot. Serieportarna har samma namn som sina " +"motsvarande filer i /dev. När ytterligare " +"kärnparametrar anges, måste du upprepa vissa standardalternativ som behövs " +"av &d-i;-avbilderna. Till exempel, för att starta upp från ewa0 och använda en konsoll på första serieporten, skulle du skriva:" #. Tag: screen #: boot-installer.xml:323 #, no-c-format -msgid ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0"" -msgstr ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0"" +msgid "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" +msgstr "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" #. Tag: title #: boot-installer.xml:328 @@ -440,11 +622,13 @@ msgstr "Uppstart från cd-rom med SRM-konsoll" msgid "" "Type \n" ">>> boot xxxx -flags 0\n" -" where xxxx is your CD-ROM drive in SRM notation." +" where xxxx is your CD-" +"ROM drive in SRM notation." msgstr "" "Ange \n" ">>> boot xxxx -flags 0\n" -" där xxxx är din cd-rom-enhet i SRM-notation." +" där xxxx är din cd-" +"rom-enhet i SRM-notation." #. Tag: title #: boot-installer.xml:341 @@ -455,8 +639,23 @@ msgstr "Uppstart från cd-rom med ARC eller AlphaBIOS-konsoll" #. 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 "För att starta upp en cd-rom från ARC-konsollen, ta reda på kodnamnet för din underarkitektur (se ), och ange sedan \\milo\\linload.exe som starthanterare och \\milo\\underarkitektur (där underarkitektur är det korrekta namnet på underarkitekturen) som sökväg till operativsystemet i menyn \"OS Selection Setup\". Ett undantag för ägare av Ruffian-system: De måste använda \\milo\\ldmilo.exe som starthanterare." +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 "" +"För att starta upp en cd-rom från ARC-konsollen, ta reda på kodnamnet för " +"din underarkitektur (se ), och ange sedan " +"\\milo\\linload.exe som starthanterare och " +"\\milo\\underarkitektur (där " +"underarkitektur är det korrekta namnet på " +"underarkitekturen) som sökväg till operativsystemet i menyn \"OS Selection " +"Setup\". Ett undantag för ägare av Ruffian-system: De måste använda " +"\\milo\\ldmilo.exe som starthanterare." #. Tag: title #: boot-installer.xml:358 @@ -468,35 +667,66 @@ msgstr "Uppstart från startdisketter med SRM-konsoll" #: boot-installer.xml:359 #, no-c-format msgid "" -"At the SRM prompt (>>>), issue the following command: \n" +"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" +" 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." +" 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 "" -"På SRM-prompten (>>>), ange följande kommando: \n" +"På SRM-prompten (>>>), ange följande kommando: " +"\n" ">>> boot dva0 -flags 0\n" -" ersätt möjligen dva0 med det faktiska enhetsnamnet. Vanligtvis är dva0 diskettenheten; skriv \n" +" ersätt möjligen dva0 med " +"det faktiska enhetsnamnet. Vanligtvis är dva0 " +"diskettenheten; skriv \n" ">>> show dev\n" -" för att se listan på enheter (alltså, om du vill starta upp från en cd). Observera att om du startar upp via MILO, ignoreras argumentet -flags, så du kan helt enkelt skriva boot dva0. Om allt fungerar som det ska kommer du till slut se Linux-kärnan starta upp." +" för att se listan på enheter (alltså, om du vill " +"starta upp från en cd). Observera att om du startar upp via MILO, ignoreras " +"argumentet -flags, så du kan helt enkelt skriva " +"boot dva0. Om allt fungerar som det ska kommer du till " +"slut se Linux-kärnan starta upp." #. 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." +"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 "" -"Om du vill ange kärnparametrar vid uppstart med aboot, använd följande kommando: \n" -">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 load_ramdisk=1 arguments\"\n" -" (angivet på en rad), som ersätter, om nödvändigt, det faktiska namnet på uppstartsenheten i SRM för dva0, namnet för uppstartsenheten för Linux för fd0, och de önskade kärnparametrarna för arguments." +"Om du vill ange kärnparametrar vid uppstart med aboot, " +"använd följande kommando: \n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +" (angivet på en rad), som ersätter, om " +"nödvändigt, det faktiska namnet på uppstartsenheten i SRM för " +"dva0, namnet för uppstartsenheten för Linux för " +"fd0, och de önskade kärnparametrarna för " +"arguments." #. 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 "Om du vill ange kärnparametrar vid uppstart med MILO, måste du avbryta bootstrap när du kommit in i MILO. Se ." +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 "" +"Om du vill ange kärnparametrar vid uppstart med MILO, " +"måste du avbryta bootstrap när du kommit in i MILO. Se ." #. Tag: title #: boot-installer.xml:398 @@ -507,8 +737,14 @@ msgstr "Uppstart från startdisketter med ARC eller AlphaBIOS-konsoll" #. 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 "I valmenyn för operativsystem, ställ in linload.exe som starthanterare, och milo som \"OS Path\". Kör bootstrap med den nyligen skapade posten." +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 "" +"I valmenyn för operativsystem, ställ in linload.exe som " +"starthanterare, och milo som \"OS Path\". Kör bootstrap " +"med den nyligen skapade posten." #. Tag: title #: boot-installer.xml:409 @@ -519,20 +755,36 @@ msgstr "Uppstart med MILO" #. 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 "MILO som finns på bootstrap-mediumet är konfigurerad att automatiskt fortsätta direkt till Linux. Om du önskar att avbryta är allt du behöver göra att trycka på blanksteg under MILO-nedräkningen." +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 "" +"MILO som finns på bootstrap-mediumet är konfigurerad att automatiskt " +"fortsätta direkt till Linux. Om du önskar att avbryta är allt du behöver " +"göra att trycka på blanksteg under MILO-nedräkningen." #. 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" +"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." +" 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 "" -"Om du vill uttryckligen ange alla bitar (till exempel, för att skicka med ytterligare parametrar), kan du använda ett kommando som denna: \n" +"Om du vill uttryckligen ange alla bitar (till exempel, för att skicka med " +"ytterligare parametrar), kan du använda ett kommando som denna: " +"\n" "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" -" Om du startar upp från något annat än en diskett, ersätt fd0 i exemplet ovan med lämpligt enhetsnamn i Linux-notation. Kommandot help ger dig en kort referens på MILO-kommandon." +" Om du startar upp från något annat än en " +"diskett, ersätt fd0 i exemplet ovan med lämpligt " +"enhetsnamn i Linux-notation. Kommandot help ger dig en " +"kort referens på MILO-kommandon." #. Tag: title #: boot-installer.xml:435 @@ -541,37 +793,37 @@ msgid "Booting from TFTP" msgstr "Uppstart från TFTP" #. Tag: para -#: boot-installer.xml:441 -#: boot-installer.xml:1003 -#: boot-installer.xml:1506 -#: boot-installer.xml:1989 -#: boot-installer.xml:2504 -#: boot-installer.xml:2600 +#: boot-installer.xml:441 boot-installer.xml:1003 boot-installer.xml:1506 +#: boot-installer.xml:1989 boot-installer.xml:2504 boot-installer.xml:2600 #, no-c-format -msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)." -msgstr "Uppstart från nätverket kräver att du har en nätverksanslutning och en TFTP-server konfigurerad för uppstarter (DHCP, RARP eller BOOTP)." +msgid "" +"Booting from the network requires that you have a network connection and a " +"TFTP network boot server (DHCP, RARP, or BOOTP)." +msgstr "" +"Uppstart från nätverket kräver att du har en nätverksanslutning och en TFTP-" +"server konfigurerad för uppstarter (DHCP, RARP eller BOOTP)." #. Tag: para -#: boot-installer.xml:446 -#: boot-installer.xml:1008 -#: boot-installer.xml:1511 -#: boot-installer.xml:1994 -#: boot-installer.xml:2509 -#: boot-installer.xml:2605 +#: boot-installer.xml:446 boot-installer.xml:1008 boot-installer.xml:1511 +#: boot-installer.xml:1994 boot-installer.xml:2509 boot-installer.xml:2605 #, no-c-format -msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server." -msgstr "Äldre system såsom 715 kan kräva att en RBOOT-server används istället för en BOOTP-server." +msgid "" +"Older systems such as the 715 might require the use of an RBOOT server " +"instead of a BOOTP server." +msgstr "" +"Äldre system såsom 715 kan kräva att en RBOOT-server används istället för en " +"BOOTP-server." #. Tag: para -#: boot-installer.xml:451 -#: boot-installer.xml:1013 -#: boot-installer.xml:1516 -#: boot-installer.xml:1999 -#: boot-installer.xml:2514 -#: boot-installer.xml:2610 +#: boot-installer.xml:451 boot-installer.xml:1013 boot-installer.xml:1516 +#: boot-installer.xml:1999 boot-installer.xml:2514 boot-installer.xml:2610 #, no-c-format -msgid "The installation method to support network booting is described in ." -msgstr "Installationsmetoden som har stöd för nätverksuppstart finns beskriven i ." +msgid "" +"The installation method to support network booting is described in ." +msgstr "" +"Installationsmetoden som har stöd för nätverksuppstart finns beskriven i " +"." #. Tag: title #: boot-installer.xml:459 @@ -582,62 +834,117 @@ msgstr "Starta upp NetWinder via TFTP" #. 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 "Netwinder har två nätverksgränssnitt: Ett 10Mbps NE2000-kompatibelt kort (som generellt sett refereras till som eth0) och ett 100Mbps Tulip-kort. Det kan uppstå problem vid inläsning av avbilden via TFTP med 100Mbps-kortet så det rekommenderas att du använder 10Mbps-gränssnittet (det som är märkt som 10 Base-T)." +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 "" +"Netwinder har två nätverksgränssnitt: Ett 10Mbps NE2000-kompatibelt kort " +"(som generellt sett refereras till som eth0) och ett " +"100Mbps Tulip-kort. Det kan uppstå problem vid inläsning av avbilden via " +"TFTP med 100Mbps-kortet så det rekommenderas att du använder 10Mbps-" +"gränssnittet (det som är märkt som 10 Base-T)." #. 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 "Du behöver NeTTrom 2.2.1 eller senare för att starta upp installationssystemet, och version 2.3.3 rekommenderas. Tyvärr finns inte firmwarefilerna tillgängliga för hämtning för tillfället på grund av licensproblem. Om denna situation ändras, kan du hitta nya avbilder på ." +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 "" +"Du behöver NeTTrom 2.2.1 eller senare för att starta upp " +"installationssystemet, och version 2.3.3 rekommenderas. Tyvärr finns inte " +"firmwarefilerna tillgängliga för hämtning för tillfället på grund av " +"licensproblem. Om denna situation ändras, kan du hitta nya avbilder på " +"." #. 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" +"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" +" 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" +" 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" +" 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" +" 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" +" 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" +" 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." +" In case you run into any problems, a detailed HOWTO is available." msgstr "" -"När du startar upp din Netwinder måste du avbryta uppstartsprocessen under nedräkningen. Det här låter dig ställa in ett antal firmwareinställningar som behövs för att kunna starta upp installeraren. Börja först med att läsa in standardinställningarna: \n" +"När du startar upp din Netwinder måste du avbryta uppstartsprocessen under " +"nedräkningen. Det här låter dig ställa in ett antal firmwareinställningar " +"som behövs för att kunna starta upp installeraren. Börja först med att läsa " +"in standardinställningarna: \n" " NeTTrom command-> load-defaults\n" -" Sedan måste du konfigurera nätverket, antingen med en statisk adress: \n" +" Sedan måste du konfigurera nätverket, antingen " +"med en statisk adress: \n" " NeTTrom command-> setenv netconfig_eth0 flash\n" " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" -" där 24 är antalet bitar i nätmasken, eller en dynamisk adress: \n" +" där 24 är antalet bitar i nätmasken, eller en " +"dynamisk adress: \n" " NeTTrom command-> setenv netconfig_eth0 dhcp\n" -" Du kanske även behöver konfigurera inställningen route1 om TFTP-servern inte finns på det lokala subnätet. Om du följer dessa inställningar, måste du ange TFTP-servern och avbildens plats. Du kan sedan lagra dina inställningar till flashminnet. \n" +" Du kanske även behöver konfigurera inställningen " +"route1 om TFTP-servern inte finns på det lokala " +"subnätet. Om du följer dessa inställningar, måste du ange TFTP-servern och " +"avbildens plats. Du kan sedan lagra dina inställningar till flashminnet. " +"\n" " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" " NeTTrom command-> setenv kerntftpfile boot.img\n" " NeTTrom command-> save-all\n" -" Nu måste du berätta för firmware att TFTP-avbilden ska användas för att starta upp: \n" +" Nu måste du berätta för firmware att TFTP-" +"avbilden ska användas för att starta upp: \n" " NeTTrom command-> setenv kernconfig tftp\n" " NeTTrom command-> setenv rootdev /dev/ram\n" -" Om du använder en seriekonsoll för att installera din Netwinder, behöver du lägga till följande inställning: \n" -" NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200\n" -" Alternativt, för installationer med ett tangentbord och skärm måste du ställa in: \n" +" Om du använder en seriekonsoll för att " +"installera din Netwinder, behöver du lägga till följande inställning: " +"\n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +" Alternativt, för installationer med ett " +"tangentbord och skärm måste du ställa in: \n" " NeTTrom command-> setenv cmdappend root=/dev/ram\n" -" Du kan använda kommandot printenv för att granska dina miljöinställningar. Efter att du har validerat att inställningarna är korrekta kan du läsa in avbilden: \n" +" Du kan använda kommandot printenv för att granska dina miljöinställningar. Efter att du har validerat " +"att inställningarna är korrekta kan du läsa in avbilden: " +"\n" " NeTTrom command-> boot\n" -" Om du springer på några problem, finns en detaljerad HOWTO tillgänglig." +" Om du springer på några problem, finns en detaljerad HOWTO tillgänglig." #. Tag: title #: boot-installer.xml:529 @@ -648,8 +955,12 @@ msgstr "Uppstart från TFTP på CATS" #. Tag: para #: boot-installer.xml:530 #, no-c-format -msgid "On CATS machines, use boot de0: or similar at the Cyclone prompt." -msgstr "På CATS-maskiner, använd boot de0: eller liknande på Cyclone-prompten." +msgid "" +"On CATS machines, use boot de0: or similar at the Cyclone " +"prompt." +msgstr "" +"På CATS-maskiner, använd boot de0: eller liknande på " +"Cyclone-prompten." #. Tag: title #: boot-installer.xml:540 @@ -658,54 +969,76 @@ msgid "Booting from CD-ROM" msgstr "Uppstart från cd-rom" #. Tag: para -#: boot-installer.xml:546 -#: boot-installer.xml:716 -#: boot-installer.xml:1125 -#: boot-installer.xml:1946 -#: boot-installer.xml:2286 -#: boot-installer.xml:2640 +#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1125 +#: boot-installer.xml:1946 boot-installer.xml:2286 boot-installer.xml:2640 #, no-c-format -msgid "The easiest route for most people will be to use a set of Debian CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply configure your system for booting off a CD as described in , insert your CD, reboot, and proceed to the next chapter." -msgstr "Den enklaste vägen för de flesta personer är att använda en uppsättning Debian-cd-skivor. Om du har en cd-uppsättning och om din maskin har stöd för att starta upp direkt från cd, bra! Bara att konfigurera ditt system för att starta upp från en cd som beskrivs i , mata in din cd-skiva, starta om och fortsätt till nästa kapitel." +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 "" +"Den enklaste vägen för de flesta personer är att använda en uppsättning " +"Debian-cd-skivor. Om du har en cd-uppsättning och om din maskin har stöd för " +"att starta upp direkt från cd, bra! Bara att " +"konfigurera ditt system för att starta upp från en cd som beskrivs i , mata in din cd-skiva, starta om och " +"fortsätt till nästa kapitel." #. Tag: para -#: boot-installer.xml:557 -#: boot-installer.xml:727 -#: boot-installer.xml:1136 -#: boot-installer.xml:1957 -#: boot-installer.xml:2297 -#: boot-installer.xml:2651 +#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1136 +#: boot-installer.xml:1957 boot-installer.xml:2297 boot-installer.xml:2651 #, no-c-format -msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you." -msgstr "Observera att vissa cd-enheter kan kräver speciella drivrutiner och kan därför vara otillgängliga i de tidiga stegen av installationen. Om det visar sig att det vanliga sättet att starta upp från en cd inte fungerar på din maskinvara, besök det här kapitlet igen och läs om alternativa kärnor och installationsmetoder som kan fungera för dig." +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 "" +"Observera att vissa cd-enheter kan kräver speciella drivrutiner och kan " +"därför vara otillgängliga i de tidiga stegen av installationen. Om det visar " +"sig att det vanliga sättet att starta upp från en cd inte fungerar på din " +"maskinvara, besök det här kapitlet igen och läs om alternativa kärnor och " +"installationsmetoder som kan fungera för dig." #. Tag: para -#: boot-installer.xml:565 -#: boot-installer.xml:735 -#: boot-installer.xml:1144 -#: boot-installer.xml:1965 -#: boot-installer.xml:2305 -#: boot-installer.xml:2659 +#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1144 +#: boot-installer.xml:1965 boot-installer.xml:2305 boot-installer.xml:2659 #, no-c-format -msgid "Even if you cannot boot from CD-ROM, you can probably install the Debian system components and any packages you want from CD-ROM. Simply boot using a different media, such as floppies. When it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive." -msgstr "Även om du inte kan starta upp från cd-rom kan du antagligen installera Debians systemkomponenter och de paket du vill från cd-rom. Starta helt enkelt upp på ett annat media, såsom disketter. När det är dags att installera operativsystemet, grundsystemet och eventuellt andra paket, peka installationssystemet till cd-rom-enheten." +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 "" +"Även om du inte kan starta upp från cd-rom kan du antagligen installera " +"Debians systemkomponenter och de paket du vill från cd-rom. Starta helt " +"enkelt upp på ett annat media, såsom disketter. När det är dags att " +"installera operativsystemet, grundsystemet och eventuellt andra paket, peka " +"installationssystemet till cd-rom-enheten." #. Tag: para -#: boot-installer.xml:573 -#: boot-installer.xml:743 -#: boot-installer.xml:1152 -#: boot-installer.xml:1973 -#: boot-installer.xml:2313 -#: boot-installer.xml:2667 +#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1152 +#: boot-installer.xml:1973 boot-installer.xml:2313 boot-installer.xml:2667 #, no-c-format -msgid "If you have problems booting, see ." -msgstr "Om du har problem att starta upp, se ." +msgid "" +"If you have problems booting, see ." +msgstr "" +"Om du har problem att starta upp, se ." #. 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 "För att starta upp en cd-rom från Cyclones konsollprompt, använd kommandot boot cd0:cats.bin" +msgid "" +"To boot a CD-ROM from the Cyclone console prompt, use the command " +"boot cd0:cats.bin" +msgstr "" +"För att starta upp en cd-rom från Cyclones konsollprompt, använd kommandot " +"boot cd0:cats.bin" #. Tag: title #: boot-installer.xml:589 @@ -716,14 +1049,27 @@ msgstr "Starta upp från firmware" #. 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 "Det finns ett ökande antal konsumentenheter som startar upp direkt från ett flashchip på enheten. Installeraren kan skrivas till flash så att den automatiskt startar upp när du startar om dina maskiner." +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 "" +"Det finns ett ökande antal konsumentenheter som startar upp direkt från ett " +"flashchip på enheten. Installeraren kan skrivas till flash så att den " +"automatiskt startar upp när du startar om dina maskiner." #. 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 "I många fall gäller inte din garanti när firmware i inbäddade enheter ändras. Ibland kan du inte heller återhämta din enhet om det inträffar problem under flashningsprocessen. Var därför försiktig och följ stegen noga." +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 "" +"I många fall gäller inte din garanti när firmware i inbäddade enheter " +"ändras. Ibland kan du inte heller återhämta din enhet om det inträffar " +"problem under flashningsprocessen. Var därför försiktig och följ stegen noga." #. Tag: title #: boot-installer.xml:612 @@ -735,7 +1081,8 @@ msgstr "Starta upp NSLU2" #: boot-installer.xml:613 #, no-c-format msgid "There are three ways how to put the installer firmware into flash:" -msgstr "Det finns tre sätt hur man lägger in installerarens firmware i flash-minnet:" +msgstr "" +"Det finns tre sätt hur man lägger in installerarens firmware i flash-minnet:" #. Tag: title #: boot-installer.xml:619 @@ -746,8 +1093,18 @@ msgstr "Använda webbgränssnittet i NSLU2" #. 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 "Gå till administrationsavsnittet och välj menyposten Upgrade. Du kan sedan bläddra på din disk efter installationsavbilden du tidigare hämtade ner. Tryck sedan på knappen Start Upgrade, bekräfta, vänta ett par minuter och bekräfta igen. Systemet kommer sedan att starta upp direkt in i installeraren." +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 "" +"Gå till administrationsavsnittet och välj menyposten Upgrade. Du kan sedan bläddra på din disk efter installationsavbilden du " +"tidigare hämtade ner. Tryck sedan på knappen Start Upgrade, bekräfta, vänta ett par minuter och bekräfta igen. Systemet kommer " +"sedan att starta upp direkt in i installeraren." #. Tag: title #: boot-installer.xml:631 @@ -759,13 +1116,53 @@ msgstr "Via nätverket med Linux/Unix" #: 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" +"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." +" 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 "" -"Du kan använda upslug2 från valfri Linux- eller Unix-maskin för att uppgradera maskinen via nätverket. Den här programvaran är paketerad för Debian. Först måste du försätta din NSLU2 i uppgraderingsläge: Koppla loss alla diskar och/eller enheter från USB-portarna. Stäng av din NSLU2 Tryck och håll nere omstartsknappen (tillgänglig genom ett litet hål på baksidan ovanför strömanslutningen). Tryck och släpp strömknappen för att starta upp NSLU2. Vänta 10 sekunder och se på ready-/status-lampan. Efter 10 sekunder kommer en att ändra färg från orange till röd. Släpp omedelbart omstartsknappen. Lampan på NSLU2 för ready/status kommer att blinka rött och grönt (det är en sekunds fördröjning före den första gröna). NSLU2 är nu i uppgraderingsläge. Se NSLU2-Linux-sidor om du har problem med det här. När din NSLU2 är i uppgraderingsläge, kan du lägga in den nya flashavbilden: \n" +"Du kan använda upslug2 från valfri Linux- eller Unix-" +"maskin för att uppgradera maskinen via nätverket. Den här programvaran är " +"paketerad för Debian. Först måste du försätta din NSLU2 i uppgraderingsläge: " +" Koppla loss alla diskar och/eller enheter " +"från USB-portarna. Stäng av din NSLU2 Tryck och håll nere omstartsknappen " +"(tillgänglig genom ett litet hål på baksidan ovanför strömanslutningen). Tryck och släpp strömknappen för att " +"starta upp NSLU2. Vänta 10 sekunder och " +"se på ready-/status-lampan. Efter 10 sekunder kommer en att ändra färg från " +"orange till röd. Släpp omedelbart omstartsknappen. " +" Lampan på NSLU2 för ready/status kommer att blinka rött och " +"grönt (det är en sekunds fördröjning före den första gröna). NSLU2 är nu i " +"uppgraderingsläge. Se NSLU2-Linux-sidor " +"om du har problem med det här. När din NSLU2 är i uppgraderingsläge, kan du " +"lägga in den nya flashavbilden: \n" "sudo upslug2 -i di-nslu2.bin\n" -" Observera att verktyget även visar MAC-adressen på din NSLU2, vilket kan vara användbart för att konfigurera din DHCP-server. Efter att hela avbilden har skrivits och validerats kommer systemet att automatiskt starta om. Se till att du ansluter din USB-disk igen nu, annars kommer installeraren inte att kunna hitta den." +" Observera att verktyget även visar MAC-adressen " +"på din NSLU2, vilket kan vara användbart för att konfigurera din DHCP-" +"server. Efter att hela avbilden har skrivits och validerats kommer systemet " +"att automatiskt starta om. Se till att du ansluter din USB-disk igen nu, " +"annars kommer installeraren inte att kunna hitta den." #. Tag: title #: boot-installer.xml:693 @@ -776,15 +1173,18 @@ msgstr "Via nätverket med Windows" #. Tag: para #: boot-installer.xml:694 #, no-c-format -msgid "There is a tool for Windows to upgrade the firmware via the network." -msgstr "Det finns ett verktyg för Windows för att uppgradera firmware via nätverket." +msgid "" +"There is a tool for Windows to upgrade the firmware " +"via the network." +msgstr "" +"Det finns ett verktyg för Windows för att uppgradera " +"firmware via nätverket." #. Tag: title -#: boot-installer.xml:710 -#: boot-installer.xml:1119 -#: boot-installer.xml:1934 -#: boot-installer.xml:2280 -#: boot-installer.xml:2634 +#: boot-installer.xml:710 boot-installer.xml:1119 boot-installer.xml:1934 +#: boot-installer.xml:2280 boot-installer.xml:2634 #, no-c-format msgid "Booting from a CD-ROM" msgstr "Uppstart från en cd-rom" @@ -792,32 +1192,73 @@ msgstr "Uppstart från en cd-rom" #. Tag: title #: boot-installer.xml:848 #, no-c-format -msgid "Booting from Linux Using LILO or GRUB" -msgstr "Uppstart från Linux med LILO eller GRUB" +msgid "" +"Booting from Linux Using LILO or GRUB" +msgstr "" +"Uppstart från Linux med LILO eller GRUB" #. 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 "För att starta upp installeraren från hårddisk måste du första hämta och placera de nödvändiga filerna som beskrivs i ." +msgid "" +"To boot the installer from hard disk, you must first download and place the " +"needed files as described in ." +msgstr "" +"För att starta upp installeraren från hårddisk måste du första hämta och " +"placera de nödvändiga filerna som beskrivs i ." #. 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 "Om du bara tänkte använda hårddisken för att starta upp och sedan hämta allt över nätverket, bör du hämta filen netboot/debian-installer/i386/initrd.gz och dess motsvarande kärna. Den låter dig partionera om hårddisken från vilken du startar upp installeraren, fastän du bör göra det med försiktighet." +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 "" +"Om du bara tänkte använda hårddisken för att starta upp och sedan hämta allt " +"över nätverket, bör du hämta filen netboot/debian-installer/i386/" +"initrd.gz och dess motsvarande kärna. Den låter dig partionera om " +"hårddisken från vilken du startar upp installeraren, fastän du bör göra det " +"med försiktighet." #. 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 "Alternativt, om du tänker behålla en existerande partition på hårddisken i oförändrat skick under installationen, kan du hämta filen hd-media/initrd.gz och dess kärna, såväl som en kopia av en cd-avbild till enheten (se till att filens namn slutar på .iso). Installeraren kan sedan starta upp från enheten och installera från cd-avbilden, utan behov av nätverk." +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 "" +"Alternativt, om du tänker behålla en existerande partition på hårddisken i " +"oförändrat skick under installationen, kan du hämta filen hd-media/" +"initrd.gz och dess kärna, såväl som en kopia av en cd-avbild till " +"enheten (se till att filens namn slutar på .iso). " +"Installeraren kan sedan starta upp från enheten och installera från cd-" +"avbilden, utan behov av nätverk." #. 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 "För LILO, behöver du konfigurera två viktiga saker i /etc/lilo.conf: för att läsa in initrd.gz installeraren vid uppstart; få kärnan vmlinuz att använda en RAM-disk som sin rotpartition. Här är ett exempel på en /etc/lilo.conf:" +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 "" +"För LILO, behöver du konfigurera två viktiga saker i " +"/etc/lilo.conf: för att " +"läsa in initrd.gz installeraren vid uppstart; få kärnan vmlinuz att " +"använda en RAM-disk som sin rotpartition. " +"Här är ett exempel på en /etc/lilo.conf:" #. Tag: screen #: boot-installer.xml:894 @@ -838,20 +1279,36 @@ msgstr "" #. 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 "För fler detaljer, referera till manualsidorna initrd 4 och lilo.conf 5. Kör nu lilo och starta om." +msgid "" +"For more details, refer to the initrd 4 and " +"lilo.conf 5 man pages. Now run lilo and " +"reboot." +msgstr "" +"För fler detaljer, referera till manualsidorna " +"initrd 4 och lilo.conf 5. Kör nu " +"lilo och starta om." #. 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" +"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 "" -"Proceduren för GRUB är ganska lik. Leta upp din menu.lst i katalogen /boot/grub/ (ibland finns den i /boot/boot/grub/), lägg till följande rader: \n" +"Proceduren för GRUB är ganska lik. Leta upp din " +"menu.lst i katalogen /boot/grub/ " +"(ibland finns den i /boot/boot/grub/), lägg till " +"följande rader: \n" "title Ny installation\n" "kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n" "initrd (hd0,0)/boot/newinstall/initrd.gz\n" @@ -860,8 +1317,14 @@ msgstr "" #. 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 "Observera att värden för ramdisk_size kan behöva justeras efter initrd-avbildens storlek. Från och med nu bör det inte vara några skillnader mellan GRUB och LILO." +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 "" +"Observera att värden för ramdisk_size kan behöva " +"justeras efter initrd-avbildens storlek. Från och med nu bör det inte vara " +"några skillnader mellan GRUB och LILO." #. Tag: title #: boot-installer.xml:925 @@ -872,60 +1335,120 @@ msgstr "Uppstart från USB-minne" #. 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 "Låt oss anta att du har förberett allt från och . Anslut ditt USB-minne i någon ledig USB-kontakt och starta om datorn. Systemet bör starta upp och du bör se prompten boot:. Här kan du ange ytterligare uppstartsargument eller bara trycka &enterkey;." +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 "" +"Låt oss anta att du har förberett allt från och . Anslut ditt USB-minne i någon " +"ledig USB-kontakt och starta om datorn. Systemet bör starta upp och du bör " +"se prompten boot:. Här kan du ange ytterligare " +"uppstartsargument eller bara trycka &enterkey;." #. Tag: title -#: boot-installer.xml:939 -#: boot-installer.xml:2046 -#: boot-installer.xml:2540 +#: boot-installer.xml:939 boot-installer.xml:2046 boot-installer.xml:2540 #: boot-installer.xml:2688 #, no-c-format msgid "Booting from Floppies" msgstr "Uppstart från startdisketter" #. Tag: para -#: boot-installer.xml:940 -#: boot-installer.xml:2548 +#: boot-installer.xml:940 boot-installer.xml:2548 #, no-c-format -msgid "You will have already downloaded the floppy images you needed and created floppies from the images in ." -msgstr "Du ska redan ha hämtat diskettavbilderna du behövde och skapat disketterna från avbilderna i ." +msgid "" +"You will have already downloaded the floppy images you needed and created " +"floppies from the images in ." +msgstr "" +"Du ska redan ha hämtat diskettavbilderna du behövde och skapat disketterna " +"från avbilderna i ." #. 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 "För att starta upp från installerarens startdiskett, placera den i primära diskettenheten, stäng ner systemet som vanligt och starta upp det igen." +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 "" +"För att starta upp från installerarens startdiskett, placera den i primära " +"diskettenheten, stäng ner systemet som vanligt och starta upp det igen." #. Tag: para #: boot-installer.xml:953 #, 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 "För att installera från en LS-120-enhet (ATAPI-version) med en uppsättning disketter, behöver du ange den virtuella platsen för diskettenheten. Det här gör man med uppstartsargumentet root=, som anger enheten som drivrutinen kan binda enheten till. Till exempel, om din LS-120-enhet är ansluten som första IDE-enhet (master) på andra kabeln, anger du linux root=/dev/hdc på uppstartsprompten." +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 "" +"För att installera från en LS-120-enhet (ATAPI-version) med en uppsättning " +"disketter, behöver du ange den virtuella platsen för diskettenheten. Det här " +"gör man med uppstartsargumentet root=, som anger " +"enheten som drivrutinen kan binda enheten till. Till exempel, om din LS-120-" +"enhet är ansluten som första IDE-enhet (master) på andra kabeln, anger du " +"linux root=/dev/hdc på uppstartsprompten." #. 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 "Observera att på vissa maskiner, Control Alt Delete återställer inte korrekt maskinen, så en hård omstart rekommenderas. Om du installerar från ett existerande operativsystem (exempelvis från en DOS-burk) har du inget val. Om inte, gör en hård omstart vid uppstart." +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 "" +"Observera att på vissa maskiner, Control " +"Alt Delete återställer inte " +"korrekt maskinen, så en hård omstart rekommenderas. Om du " +"installerar från ett existerande operativsystem (exempelvis från en DOS-" +"burk) har du inget val. Om inte, gör en hård omstart vid uppstart." #. 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 "Disketten kommer att läsas från och du bör sedan se en skärm som introducerar startdisketten och slutar med prompten boot:." +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 "" +"Disketten kommer att läsas från och du bör sedan se en skärm som " +"introducerar startdisketten och slutar med prompten boot:." #. 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 "När du trycker &enterkey;, bör du se meddelandet Loading..., följt av Uncompressing Linux..., och sedan en skärm full av information om maskinvaran i ditt system. Mer information angående den här fasen i uppstartsprocessen kan hittas under i ." +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 "" +"När du trycker &enterkey;, bör du se meddelandet Loading..., följt av Uncompressing Linux..., och sedan en skärm full av information om maskinvaran i " +"ditt system. Mer information angående den här fasen i uppstartsprocessen kan " +"hittas under i ." #. 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 "Efter uppstart från startdisketten kommer rotdisketten att efterfrågas. Mata in rotdisketten och tryck &enterkey;, och dess innehåll kommer att läsas in i minnet. Installeringsprogrammet debian-installer startas automatiskt." +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 "" +"Efter uppstart från startdisketten kommer rotdisketten att efterfrågas. Mata " +"in rotdisketten och tryck &enterkey;, och dess innehåll kommer att läsas in " +"i minnet. Installeringsprogrammet debian-installer " +"startas automatiskt." #. Tag: para #: boot-installer.xml:1021 @@ -942,8 +1465,16 @@ msgstr "Nätverkskort eller moderkort med stöd för PXE" #. 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 "Det kan vara så att ditt nätverkskort eller moderkort erbjuder funktionalitet för uppstart via PXE. Det är en återimplementation av TFTP-uppstart från Intel. Om så är fallet kan du konfigurera ditt BIOS att starta upp från nätverket." +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 "" +"Det kan vara så att ditt nätverkskort eller moderkort erbjuder " +"funktionalitet för uppstart via PXE. Det är en återimplementation av TFTP-" +"uppstart från Intel. Om så är fallet " +"kan du konfigurera ditt BIOS att starta upp från nätverket." #. Tag: title #: boot-installer.xml:1039 @@ -954,14 +1485,22 @@ msgstr "Nätverkskort med Network BootROM" #. Tag: para #: boot-installer.xml:1040 #, no-c-format -msgid "It could be that your Network Interface Card provides TFTP boot functionality." -msgstr "Det kan vara så att ditt nätverkskort erbjuder funktionalitet för att starta upp via TFTP." +msgid "" +"It could be that your Network Interface Card provides TFTP boot " +"functionality." +msgstr "" +"Det kan vara så att ditt nätverkskort erbjuder funktionalitet för att starta " +"upp via TFTP." #. 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 "Låt oss (&email-debian-boot-list;) veta hur du gjorde det. Referera till det här dokumentet." +msgid "" +"Let us (&email-debian-boot-list;) know how did you manage it. " +"Please refer to this document." +msgstr "" +"Låt oss (&email-debian-boot-list;) veta hur du gjorde det. " +"Referera till det här dokumentet." #. Tag: title #: boot-installer.xml:1053 @@ -972,8 +1511,12 @@ msgstr "Etherboot" #. Tag: para #: boot-installer.xml:1054 #, no-c-format -msgid "The etherboot project provides bootdiskettes and even bootroms that do a TFTPboot." -msgstr "Etherboot-projektet erbjuder startdisketter och även ROM-filer som kan göra uppstarter via TFTP." +msgid "" +"The etherboot project " +"provides bootdiskettes and even bootroms that do a TFTPboot." +msgstr "" +"Etherboot-projektet erbjuder " +"startdisketter och även ROM-filer som kan göra uppstarter via TFTP." #. Tag: title #: boot-installer.xml:1063 @@ -985,25 +1528,73 @@ msgstr "Uppstartsprompten" #: 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" +"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." +" 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 "" -"När installeraren startar upp bör du presenteras med en snäll grafisk skärm som visar Debians logotyp och en uppstartsprompt: \n" +"När installeraren startar upp bör du presenteras med en snäll grafisk skärm " +"som visar Debians logotyp och en uppstartsprompt: \n" "Press F1 for help, or ENTER to boot:\n" -" Vid uppstartsprompten kan du antingen bara trycka &enterkey; för att starta upp installeraren med standardalternativ eller ange en specifik uppstartsmetod och, valfritt, uppstartsparametrar." +" Vid uppstartsprompten kan du antingen bara " +"trycka &enterkey; för att starta upp installeraren med standardalternativ " +"eller ange en specifik uppstartsmetod och, valfritt, uppstartsparametrar." #. 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 "Information om tillgängliga uppstartsmetoder och om uppstartsparametrar som kan vara användbara kan hittas genom att trycka F2 till F8. Om du lägger till några parametrar till kommandoraden, tänk på att ange uppstartsmetoden (standard är linux) och ett blanksteg före den första parametern (exempelvis linux fb=false)." +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 "" +"Information om tillgängliga uppstartsmetoder och om uppstartsparametrar som " +"kan vara användbara kan hittas genom att trycka F2 till " +"F8. Om du lägger till några parametrar till kommandoraden, " +"tänk på att ange uppstartsmetoden (standard är linux) " +"och ett blanksteg före den första parametern (exempelvis linux " +"fb=false)." #. 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 "Om du installerar systemet via en fjärrhanteringsenhet som tillhandahåller ett textgränssnitt till VGA-konsollen, kan du inte se den initiala grafiska uppstartsskärmen under uppstarten av installeraren; du kanske inte heller kan se uppstartsprompten. Exempel på de här enheterna inkluderar textkonsollen för Compaqs integrated Lights Out (iLO) och HP:s Integrated Remote Assistant (IRA). Du kan helt blint trycka F1 I vissa fall kräver de här enheterna en speciell tangentsekvens för att göra den här tangenttryckningen, till exempel använder IRA Ctrl F , 1. för att komma förbi den här skärmen och visa hjälptexten. När du har kommit förbi uppstartsskärmen och är vid hjälptexten kommer dina tangenttryckningar att ekas vid prompten som förväntat. För att förhindra att installeraren använder grafikkortet i resten av installationen, kan du också lägga till fb=false till uppstartsprompten, som beskrivs i hjälptexten." +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 "" +"Om du installerar systemet via en fjärrhanteringsenhet som tillhandahåller " +"ett textgränssnitt till VGA-konsollen, kan du inte se den initiala grafiska " +"uppstartsskärmen under uppstarten av installeraren; du kanske inte heller " +"kan se uppstartsprompten. Exempel på de här enheterna inkluderar " +"textkonsollen för Compaqs integrated Lights Out (iLO) och HP:" +"s Integrated Remote Assistant (IRA). Du kan helt blint trycka " +"F1 I vissa fall kräver de här enheterna en speciell " +"tangentsekvens för att göra den här tangenttryckningen, till exempel " +"använder IRA Ctrl F ," +" 1. för att komma förbi den här " +"skärmen och visa hjälptexten. När du har kommit förbi uppstartsskärmen och " +"är vid hjälptexten kommer dina tangenttryckningar att ekas vid prompten som " +"förväntat. För att förhindra att installeraren använder grafikkortet i " +"resten av installationen, kan du också lägga till fb=false till uppstartsprompten, som beskrivs i hjälptexten." #. Tag: title #: boot-installer.xml:1160 @@ -1014,32 +1605,115 @@ msgstr "Cd-innehåll" #. 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 "Det finns tre enkla variationer av Debians installationsskivor. Cd-skivan Visitkort innehåller en minimal installation som passar på ett minimalt cd-media. Den kräver en nätverksanslutning för att installera resten av grundinstallationen och skapa ett användbart system. Cd-skivan Nätinstallation har alla paket för en grundinstallation men kräver en nätverksanslutningen till en Debian-spegel för att installera de extra paket som man vill ha för ett komplett system. Uppsättningen av Debian-cd-skivor kan installera ett komplett system från en mängd olika paket utan behov av tillgång till nätverket." +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 "" +"Det finns tre enkla variationer av Debians installationsskivor. Cd-skivan " +"Visitkort innehåller en minimal installation som passar " +"på ett minimalt cd-media. Den kräver en nätverksanslutning för att " +"installera resten av grundinstallationen och skapa ett användbart system. Cd-" +"skivan Nätinstallation har alla paket för en " +"grundinstallation men kräver en nätverksanslutningen till en Debian-spegel " +"för att installera de extra paket som man vill ha för ett komplett system. " +"Uppsättningen av Debian-cd-skivor kan installera ett komplett system från en " +"mängd olika paket utan behov av tillgång till nätverket." #. 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 "Arkitekturen IA-64 använder nästa generations Extensible Firmware Interface (EFI) från Intel. Olik det traditionella x86 BIOS som inte känner till mer om uppstartsenheten annat än partitionstabellen och huvudstartsektorn (MBR), EFI kan läsa och skriva filer från FAT16- eller FAT32-formaterade diskpartitioner. Det här förenklar den ofta mystiska processen hur ett system startas upp. Starthanteraren och EFI-firmware som har stöd för det har ett helt filsystem att lagra nödvändiga filer för att starta upp maskinen. Det betyder att systemdisken på ett IA-64-system har ytterligare en diskpartition som är dedicerad till EFI istället för den enkla MBR eller uppstartsblock på mer konventionella system." +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 "" +"Arkitekturen IA-64 använder nästa generations Extensible Firmware Interface " +"(EFI) från Intel. Olik det traditionella x86 BIOS som inte känner till mer " +"om uppstartsenheten annat än partitionstabellen och huvudstartsektorn (MBR), " +"EFI kan läsa och skriva filer från FAT16- eller FAT32-formaterade " +"diskpartitioner. Det här förenklar den ofta mystiska processen hur ett " +"system startas upp. Starthanteraren och EFI-firmware som har stöd för det " +"har ett helt filsystem att lagra nödvändiga filer för att starta upp " +"maskinen. Det betyder att systemdisken på ett IA-64-system har ytterligare " +"en diskpartition som är dedicerad till EFI istället för den enkla MBR eller " +"uppstartsblock på mer konventionella system." #. 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 "Debian Installer-cd-skivan innehåller en liten EFI-partition där starthanteraren ELILO, dess konfigurationsfil, installerarens kärna, och initiala filsystem (initrd) finns. Det körande systemet innehåller även en EFI-partition där de nödvändiga filerna för uppstart av systemet finns. De här filerna är läsbara från EFI-skalet som beskrivs nedan." +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 "" +"Debian Installer-cd-skivan innehåller en liten EFI-partition där " +"starthanteraren ELILO, dess konfigurationsfil, " +"installerarens kärna, och initiala filsystem (initrd) finns. Det körande " +"systemet innehåller även en EFI-partition där de nödvändiga filerna för " +"uppstart av systemet finns. De här filerna är läsbara från EFI-skalet som " +"beskrivs nedan." #. 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 "De flesta detaljer för hur ELILO faktiskt läser in och startar ett system är inte synliga för systeminstalleraren. Dock, installeraren måste ställa in en EFI-partition före installation av grundsystemet. Annars kommer installationen av ELILO att misslyckas som resulterar i att systemet inte kan startas upp. EFI-partitionen allokeras och formateras i partitioneringssteget av installationen före inläsningen av paketen på systemdisken. Partitioneringsfunktionen verifierar även att en lämplig EFI-partition finns före den tillåter installationen att fortsätta." +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 "" +"De flesta detaljer för hur ELILO faktiskt läser in och " +"startar ett system är inte synliga för systeminstalleraren. Dock, " +"installeraren måste ställa in en EFI-partition före installation av " +"grundsystemet. Annars kommer installationen av ELILO att " +"misslyckas som resulterar i att systemet inte kan startas upp. EFI-" +"partitionen allokeras och formateras i partitioneringssteget av " +"installationen före inläsningen av paketen på systemdisken. " +"Partitioneringsfunktionen verifierar även att en lämplig EFI-partition finns " +"före den tillåter installationen att fortsätta." #. 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 "EFI Boot Manager visas som sista steget för initiering av firmware. Den visar en menylista från vilken användaren kan välja ett alternativ. Beroende på systemmodellen och vilken annan programvara som har lästs in på systemet kan den här menyn skilja sig från system till system. Det bör finnas åtminstone två menyposter, Boot Option Maintenance Menu och EFI Shell (Built-in). Första alternativet föredras, dock, om det alternativet inte finns tillgängligt eller att cd-skivan av någon anledning inte startar upp med den, använd det andra alternativet." +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 "" +"EFI Boot Manager visas som sista steget för initiering av firmware. Den " +"visar en menylista från vilken användaren kan välja ett alternativ. Beroende " +"på systemmodellen och vilken annan programvara som har lästs in på systemet " +"kan den här menyn skilja sig från system till system. Det bör finnas " +"åtminstone två menyposter, Boot Option Maintenance Menu " +"och EFI Shell (Built-in). Första alternativet föredras, " +"dock, om det alternativet inte finns tillgängligt eller att cd-skivan av " +"någon anledning inte startar upp med den, använd det andra alternativet." #. Tag: title #: boot-installer.xml:1234 @@ -1050,8 +1724,22 @@ msgstr "VIKTIGT" #. 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 "EFI Boot Manager kommer att välja en standardåtgärd för uppstart, vanligtvis det första menyvalet, inom ett förinställt antal sekunder. Det här indikeras av en nedräkning i nedre delen av skärmen. När räknaren har räknat ned och systemet startar standardåtgärden, kanske du måste starta om maskinen för att fortsätta installationen. Om standardåtgärden är EFI-skalet kan du återvända till Boot Manager genom att köra exit vid skalprompten." +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 "" +"EFI Boot Manager kommer att välja en standardåtgärd för uppstart, vanligtvis " +"det första menyvalet, inom ett förinställt antal sekunder. Det här indikeras " +"av en nedräkning i nedre delen av skärmen. När räknaren har räknat ned och " +"systemet startar standardåtgärden, kanske du måste starta om maskinen för " +"att fortsätta installationen. Om standardåtgärden är EFI-skalet kan du " +"återvända till Boot Manager genom att köra exit vid " +"skalprompten." #. Tag: title #: boot-installer.xml:1247 @@ -1062,38 +1750,89 @@ msgstr "Alternativ 1: Starta upp från Boot Option Maintenance Menu" #. 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 "Mata in cd-skivan i dvd/cd-enheten och starta om maskinen. Firmware kommer att visa EFI Boot Manager-sidan och menyn efter den färdigställt sin systeminitiering." +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 "" +"Mata in cd-skivan i dvd/cd-enheten och starta om maskinen. Firmware kommer " +"att visa EFI Boot Manager-sidan och menyn efter den färdigställt sin " +"systeminitiering." #. 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 "Välj Boot Maintenance Menu från menyn med piltangenterna och tryck ENTER. Det här kommer att visa en ny meny." +msgid "" +"Select Boot Maintenance Menu from the menu with the arrow " +"keys and press ENTER. This will display a new menu." +msgstr "" +"Välj Boot Maintenance Menu från menyn med piltangenterna " +"och tryck ENTER. Det här kommer att visa en ny meny." #. 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 "Välj Boot From a File från menyn med piltangenterna och tryck ENTER. Det här kommer att visa en lista på enheter som firmware har sökt efter. Du bör se två menyrader som innehåller antingen etiketten Debian Inst [Acpi ... eller Removable Media Boot. Om du undersöker resten av menyraden kommer du att se att informationen för enheten och kontrollern är samma." +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 "" +"Välj Boot From a File från menyn med piltangenterna och " +"tryck ENTER. Det här kommer att visa en lista på enheter " +"som firmware har sökt efter. Du bör se två menyrader som innehåller antingen " +"etiketten Debian Inst [Acpi ... eller Removable " +"Media Boot. Om du undersöker resten av menyraden kommer du att se " +"att informationen för enheten och kontrollern är samma." #. 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 "Du kan välja någon av posterna som refererar till cd/dvd-enheten. Välj med piltangenterna och tryck sedan ENTER. Om du väljer Removable Media Boot kommer maskinen att omedelbart påbörja uppstartssekvensen. Om du istället väljer Debian Inst [Acpi ..., kommer den att visa en kataloglistning på den startbara delen av cd-skivan, som kräver att du fortsätter till nästa (ytterligare) steg." +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 "" +"Du kan välja någon av posterna som refererar till cd/dvd-enheten. Välj med " +"piltangenterna och tryck sedan ENTER. Om du väljer " +"Removable Media Boot kommer maskinen att omedelbart " +"påbörja uppstartssekvensen. Om du istället väljer Debian Inst " +"[Acpi ..., kommer den att visa en kataloglistning på den startbara " +"delen av cd-skivan, som kräver att du fortsätter till nästa (ytterligare) " +"steg." #. 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 "Du behöver endast det här steget om du valde Debian Inst [Acpi .... Kataloglistningen kommer även att visa [Treat like Removable Media Boot] på den näst sista raden. Välj den raden med piltangenterna och tryck ENTER. Det här kommer att starta inläsningssekvensen för uppstarten." +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 "" +"Du behöver endast det här steget om du valde Debian Inst [Acpi .... Kataloglistningen kommer även att visa [Treat like " +"Removable Media Boot] på den näst sista raden. Välj den raden med " +"piltangenterna och tryck ENTER. Det här kommer att starta " +"inläsningssekvensen för uppstarten." #. 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 "Dessa steg startar Debians starthanterare som kommer att visa en menysida för dig att välja en uppstartskärna och flaggor. Fortsätt till valet av uppstartskärna och flaggor." +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 "" +"Dessa steg startar Debians starthanterare som kommer att visa en menysida " +"för dig att välja en uppstartskärna och flaggor. Fortsätt till valet av " +"uppstartskärna och flaggor." #. Tag: title #: boot-installer.xml:1310 @@ -1104,44 +1843,104 @@ msgstr "Alternativ 2: Starta upp från EFI-skalet" #. 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 "Om, av någon anledning, alternativ 1 inte lyckas, starta om maskinen och när EFI Boot Manager-skärmen visas bör det finnas ett alternativ kallat EFI Shell [Built-in]. Starta upp Debian Installer-skivan med följande steg:" +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 "" +"Om, av någon anledning, alternativ 1 inte lyckas, starta om maskinen och när " +"EFI Boot Manager-skärmen visas bör det finnas ett alternativ kallat " +"EFI Shell [Built-in]. Starta upp Debian Installer-skivan " +"med följande steg:" #. 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 "Mata in cd-skivan i dvd/cd-enheten och starta om maskinen. Firmware kommer att visa EFI Boot Manager-sidan och menyn efter den färdigställer systeminitieringen." +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 "" +"Mata in cd-skivan i dvd/cd-enheten och starta om maskinen. Firmware kommer " +"att visa EFI Boot Manager-sidan och menyn efter den färdigställer " +"systeminitieringen." #. 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 "Välj EFI Shell från menyn med piltangenterna och tryck ENTER. EFI-skalet kommer att söka av alla startbara enheter och visa dem i konsollen före den visar sin kommandoprompt. De kända partitioner som är startbara på enheterna kommer att visa enhetsnamnet fsn:. Alla andra kända partitioner kommer att namnges som blkn:. Om du matade in cd-skivan precis innan du gick in i skalet kommer det ta några extra sekunder när den initierar cd-enheten." +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 "" +"Välj EFI Shell från menyn med piltangenterna och tryck " +"ENTER. EFI-skalet kommer att söka av alla startbara " +"enheter och visa dem i konsollen före den visar sin kommandoprompt. De kända " +"partitioner som är startbara på enheterna kommer att visa enhetsnamnet " +"fsn:. Alla andra kända " +"partitioner kommer att namnges som blkn:" +". Om du matade in cd-skivan precis innan du gick in i skalet " +"kommer det ta några extra sekunder när den initierar cd-enheten." #. 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 "Undersök utskriften från skalet som letar efter cd-rom-enheten. Det är antagligen enheten fs0: även om andra enheter med startbara partitioner också kommer att visas som fsn." +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 "" +"Undersök utskriften från skalet som letar efter cd-rom-enheten. Det är " +"antagligen enheten fs0: även om andra enheter med " +"startbara partitioner också kommer att visas som fsn." #. 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 "Ange fsn: och tryck på ENTER för att välja den enhet där n är partitionsnumret för cd-rom. Skalet kommer nu att visa partitionsnumret som sin prompt." +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 "" +"Ange fsn: och tryck på " +"ENTER för att välja den enhet där n är partitionsnumret för cd-rom. Skalet kommer nu att visa " +"partitionsnumret som sin prompt." #. Tag: para #: boot-installer.xml:1356 #, no-c-format -msgid "Enter elilo and press ENTER. This will start the boot load sequence." -msgstr "Ange elilo och tryck på ENTER. Det kommer att påbörja uppstartssekvensen." +msgid "" +"Enter elilo and press ENTER. This will " +"start the boot load sequence." +msgstr "" +"Ange elilo och tryck på ENTER. Det " +"kommer att påbörja uppstartssekvensen." #. 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 "Som med alternativ 1, de här stegen startar Debians starthanterare som kommer att visa en menysida för dig där du kan välja en uppstartskärna och alternativ. Du kan även ange det kortare kommandot fsn:elilo vid skalprompten. Fortsätt till att välja uppstartskärna och alternativ." +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 "" +"Som med alternativ 1, de här stegen startar Debians starthanterare som " +"kommer att visa en menysida för dig där du kan välja en uppstartskärna och " +"alternativ. Du kan även ange det kortare kommandot " +"fsn:elilo vid skalprompten. " +"Fortsätt till att välja uppstartskärna och alternativ." #. Tag: title #: boot-installer.xml:1377 @@ -1152,32 +1951,86 @@ msgstr "Installation med en seriekonsoll" #. 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 "Du kan välja att genomföra en installation med en skärm och tangentbord eller genom att använda en serieanslutning. För att använda skärm/tangentbord, välj ett alternativ som innehåller strängen [VGA console]. För att installera över en serieanslutning, välj ett alternativ som innehåller strängen [BAUD baud serial console], där BAUD är hastigheten för din seriekonsoll. Menyposter för de mest vanliga hastigheterna för ttyS0-enheten är förkonfigurerade." +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 "" +"Du kan välja att genomföra en installation med en skärm och tangentbord " +"eller genom att använda en serieanslutning. För att använda skärm/" +"tangentbord, välj ett alternativ som innehåller strängen [VGA console]. För " +"att installera över en serieanslutning, välj ett alternativ som innehåller " +"strängen [BAUD baud serial console], där " +"BAUD är hastigheten för din seriekonsoll. " +"Menyposter för de mest vanliga hastigheterna för ttyS0-enheten är " +"förkonfigurerade." #. 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 "I de flesta fall kommer att du vilja att installeraren använder samma bithastighet som din anslutning till EFI-konsollen. Om du inte är säker på vad den här inställningen är inställd till kan du hämta den med kommandot baud i EFI-skalet." +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 "" +"I de flesta fall kommer att du vilja att installeraren använder samma " +"bithastighet som din anslutning till EFI-konsollen. Om du inte är säker på " +"vad den här inställningen är inställd till kan du hämta den med kommandot " +"baud i EFI-skalet." #. 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 "Om det inte finns ett alternativ tillgängligt som är konfigurerad för serieenheten eller den hastighet du vill använda kan du åsidosätta inställningarna för konsollen för en av de existerande menyalternativen. Till exempel för att använda en konsoll på 57600 baud över enheten ttyS1, ange console=ttyS1,57600n8 i textfönstretBoot:." +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 "" +"Om det inte finns ett alternativ tillgängligt som är konfigurerad för " +"serieenheten eller den hastighet du vill använda kan du åsidosätta " +"inställningarna för konsollen för en av de existerande menyalternativen. " +"Till exempel för att använda en konsoll på 57600 baud över enheten ttyS1, " +"ange console=ttyS1,57600n8 i textfönstretBoot:" +"." #. 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 "De flesta IA-64-maskiner skeppas med en standardinställning för konsollen på 9600 baud. Den här inställningen är ganska långsam, och den normala installationsprocessen kommer att ta mycket längre tid att rita upp varje skärm. Du bör tänka på att antingen öka hastigheten som används för att genomföra installationen, eller genomföra en installation i textläget. Se hjälpmenyn Params för instruktioner för hur man startar installeraren i textläge." +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 "" +"De flesta IA-64-maskiner skeppas med en standardinställning för konsollen på " +"9600 baud. Den här inställningen är ganska långsam, och den normala " +"installationsprocessen kommer att ta mycket längre tid att rita upp varje " +"skärm. Du bör tänka på att antingen öka hastigheten som används för att " +"genomföra installationen, eller genomföra en installation i textläget. Se " +"hjälpmenyn Params för instruktioner för hur man " +"startar installeraren i textläge." #. 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 "Om du väljer fel konsolltyp kommer du kunna välja kärna och ange parametrar men både skärmen och din inmatning kommer att försvinna så snart som kärnan startat och kräver att du startar om före du kan påbörjar installationen." +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 "" +"Om du väljer fel konsolltyp kommer du kunna välja kärna och ange parametrar " +"men både skärmen och din inmatning kommer att försvinna så snart som kärnan " +"startat och kräver att du startar om före du kan påbörjar installationen." #. Tag: title #: boot-installer.xml:1426 @@ -1188,50 +2041,125 @@ msgstr "Välj uppstartskärna och inställningar" #. 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 "Starthanteraren kommer att visa ett formulär med en menylista och ett textfönster med en Boot:-prompt. Piltangenterna väljer en post från menyn och all text som skrivs på tangentbordet visas i textfönstret. Det finns även hjälpskärmar som kan visas genom att tryck på lämplig funktionstangent. Hjälpskärmen General förklarar menyvalet och skärmen Params förklarar de vanliga kommandoradsflaggorna." +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 "" +"Starthanteraren kommer att visa ett formulär med en menylista och ett " +"textfönster med en Boot:-prompt. Piltangenterna " +"väljer en post från menyn och all text som skrivs på tangentbordet visas i " +"textfönstret. Det finns även hjälpskärmar som kan visas genom att tryck på " +"lämplig funktionstangent. Hjälpskärmen General " +"förklarar menyvalet och skärmen Params förklarar de " +"vanliga kommandoradsflaggorna." #. 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 "Konsultera hjälpskärmen General för beskrivningen av vilka kärnor och installationslägen som är mest lämpliga för din installation. Du bör även konsultera nedan för ytterligare parametrar som du kanske vill ställa in i textfönstret Boot:. Kärnversionen du väljer kommer att välja den kärnversion som kommer att användas för både installationsprocessen och det installerade systemet. Om du påträffar problem med kärnan under installationen, kommer du även att få de samma problem med systemet du installerar. De följande två stegen kommer att välja och påbörja installationen:" +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 "" +"Konsultera hjälpskärmen General för beskrivningen av " +"vilka kärnor och installationslägen som är mest lämpliga för din " +"installation. Du bör även konsultera nedan " +"för ytterligare parametrar som du kanske vill ställa in i textfönstret " +"Boot:. Kärnversionen du väljer kommer att välja den " +"kärnversion som kommer att användas för både installationsprocessen och det " +"installerade systemet. Om du påträffar problem med kärnan under " +"installationen, kommer du även att få de samma problem med systemet du " +"installerar. De följande två stegen kommer att välja och påbörja " +"installationen:" #. 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 "Välj kärnversionen och installationsläget som är mest lämplig för dina behov med piltangenterna." +msgid "" +"Select the kernel version and installation mode most appropriate to your " +"needs with the arrow keys." +msgstr "" +"Välj kärnversionen och installationsläget som är mest lämplig för dina behov " +"med piltangenterna." #. 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 "Ange valfri uppstartsparameter genom att skriva på tangentbordet. Texten kommer att visas direkt i textfönstret. Det är här som kärnparametrar (såsom inställningar för seriekonsoll) anges." +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 "" +"Ange valfri uppstartsparameter genom att skriva på tangentbordet. Texten " +"kommer att visas direkt i textfönstret. Det är här som kärnparametrar (såsom " +"inställningar för seriekonsoll) anges." #. 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 "Tryck ENTER. Det kommer att läsa in och starta kärnan. Kärnan kommer att visa dess vanliga initieringsmeddelanden följt av första skärmen av Debian Installer." +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 "" +"Tryck ENTER. Det kommer att läsa in och starta kärnan. " +"Kärnan kommer att visa dess vanliga initieringsmeddelanden följt av första " +"skärmen av Debian Installer." #. 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 "Fortsätt till nästa kapitel för att fortsätta installationen där du kommer att ställa in språkanpassning, nätverk och diskpartitioner." +msgid "" +"Proceed to the next chapter to continue the installation where you will set " +"up the language locale, network, and disk partitions." +msgstr "" +"Fortsätt till nästa kapitel för att fortsätta installationen där du kommer " +"att ställa in språkanpassning, nätverk och diskpartitioner." #. 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 "Starta upp ett IA64-system från nätverket är likt en uppstart från cd. Den enda skillnaden är hur installationskärnan läses in. EFI Boot Manager kan läsas in och starta program från en server på nätverket. När installationskärnan är inläst och startar kommer systeminstallationen att fortsätta genom samma steg som för cd-installationen med undantaget av att paketen för grundinstallationen kommer att läsas från nätverket istället för cd-enheten." +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 "" +"Starta upp ett IA64-system från nätverket är likt en uppstart från cd. Den " +"enda skillnaden är hur installationskärnan läses in. EFI Boot Manager kan " +"läsas in och starta program från en server på nätverket. När " +"installationskärnan är inläst och startar kommer systeminstallationen att " +"fortsätta genom samma steg som för cd-installationen med undantaget av att " +"paketen för grundinstallationen kommer att läsas från nätverket istället för " +"cd-enheten." #. 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 "Nätverksuppstart för ia64-system kräver två arkitekturspecifika åtgärder. På uppstartsservern måste DHCP och TFTP konfigureras för att leverera elilo. På klienten måste ett nytt uppstartsalternativ definieras i EFI-uppstartshanteraren för att aktivera inläsning över ett nätverk." +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 "" +"Nätverksuppstart för ia64-system kräver två arkitekturspecifika åtgärder. På " +"uppstartsservern måste DHCP och TFTP konfigureras för att leverera " +"elilo. På klienten måste ett nytt uppstartsalternativ " +"definieras i EFI-uppstartshanteraren för att aktivera inläsning över ett " +"nätverk." #. Tag: title #: boot-installer.xml:1535 @@ -1243,27 +2171,41 @@ msgstr "Konfiguration av servern" #: boot-installer.xml:1536 #, no-c-format msgid "" -"A suitable TFTP entry for network booting an ia64 system looks something like this: \n" +"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." +" Note that the goal is to get elilo.efi running on the client." msgstr "" -"En lämplig TFTP-post för att starta upp via nätverket på ett ia64-system ser ut ungefär som den här: \n" +"En lämplig TFTP-post för att starta upp via nätverket på ett ia64-system ser " +"ut ungefär som den här: \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" -" Observera att målet är att få elilo.efi att köra på klienten." +" Observera att målet är att få elilo." +"efi att köra på klienten." #. 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 "Packa upp filen netboot.tar.gz i katalogen som används som rot för din tftp-server. Vanliga rotkataloger för tftp är /var/lib/tftp och /tftpboot. Det kommer att skapas en debian-installer-katalog som innehåller uppstartsfilerna för ett IA-64-system." +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 "" +"Packa upp filen netboot.tar.gz i katalogen som används " +"som rot för din tftp-server. Vanliga rotkataloger för tftp är /var/" +"lib/tftp och /tftpboot. Det kommer att " +"skapas en debian-installer-katalog som innehåller " +"uppstartsfilerna för ett IA-64-system." #. Tag: screen #: boot-installer.xml:1556 @@ -1286,8 +2228,24 @@ 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 "Filen netboot.tar.gz innehåller en fil kallad elilo.conf som bör fungera för de flesta konfigurationer. Dock, om du behöver göra ändringar i denna fil kan du hitta den i katalogen debian-installer/ia64/. Det är möjligt att ha olika konfigurationsfiler för olika klienter genom att namnge dem med klientens IP-adress hexadecimalt och ändelsen .conf istället för elilo.conf. Se dokumentationen som tillhandahålls av paketet elilo för detaljer." +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 "" +"Filen netboot.tar.gz innehåller en fil kallad " +"elilo.conf som bör fungera för de flesta " +"konfigurationer. Dock, om du behöver göra ändringar i denna fil kan du hitta " +"den i katalogen debian-installer/ia64/. Det är möjligt " +"att ha olika konfigurationsfiler för olika klienter genom att namnge dem med " +"klientens IP-adress hexadecimalt och ändelsen .conf " +"istället för elilo.conf. Se dokumentationen som " +"tillhandahålls av paketet elilo för detaljer." #. Tag: title #: boot-installer.xml:1573 @@ -1298,20 +2256,59 @@ msgstr "Konfiguration av klienten" #. 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 "För att konfigurera stöd för klienten att starta upp via TFTP, börja genom att starta upp till EFI och gå in i Boot Option Maintenance Menu. Lägg till ett uppstartsalternativ. Du bör se en eller flera rader med texten Load File [Acpi()/.../Mac()]. Om fler än en av de här raderna finns, välj den som innehåller MAC-adressen för gränssnittet från vilket du kommer att starta upp. Använd piltangenterna för att markera ditt val, tryck sedan Enter. Namnge posten Netboot eller något liknande, spara, och gå tillbaka till menyn med uppstartsalternativ. Du bör se det nya uppstartsalternativet som du nyss skapade, och att välja det för initiera en DHCP-fråga som leder till en inläsning av elilo.efi från TFTP-servern." +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 "" +"För att konfigurera stöd för klienten att starta upp via TFTP, börja genom " +"att starta upp till EFI och gå in i Boot Option Maintenance Menu. Lägg till ett uppstartsalternativ. " +" Du bör se en eller flera rader med " +"texten Load File [Acpi()/.../Mac()]. Om fler än " +"en av de här raderna finns, välj den som innehåller MAC-adressen för " +"gränssnittet från vilket du kommer att starta upp. Använd piltangenterna för " +"att markera ditt val, tryck sedan Enter. " +"Namnge posten Netboot eller något liknande, spara, " +"och gå tillbaka till menyn med uppstartsalternativ. Du bör se det nya uppstartsalternativet som du nyss skapade, " +"och att välja det för initiera en DHCP-fråga som leder till en inläsning av " +"elilo.efi från TFTP-servern." #. 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 "Starthanteraren kommer att visa sin prompt efter den har hämtat och bearbetat sin konfigurationsfil. Vid denna punkt, fortsätter installationen med samma steg som en cd-installation. Välj ett uppstartsalternativ som ovan och när kärnan har installerat sig själv från nätverket, kommer den att starta Debian Installer." +msgid "" +"The boot loader will display its prompt after it has downloaded and " +"processed its configuration file. At this point, the installation proceeds " +"with the same steps as a CD install. Select a boot option as in above and " +"when the kernel has completed installing itself from the network, it will " +"start the Debian Installer." +msgstr "" +"Starthanteraren kommer att visa sin prompt efter den har hämtat och " +"bearbetat sin konfigurationsfil. Vid denna punkt, fortsätter installationen " +"med samma steg som en cd-installation. Välj ett uppstartsalternativ som ovan " +"och när kärnan har installerat sig själv från nätverket, kommer den att " +"starta Debian Installer." #. 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 "Fortsätt till nästa kapitel för att fortsätta installationen där du kommer att ställa in språkanpassning, nätverk och diskpartitionerna." +msgid "" +"Proceed to the next chapter to continue the installation where you will set " +"up the language locale, network, and the disk partitions." +msgstr "" +"Fortsätt till nästa kapitel för att fortsätta installationen där du kommer " +"att ställa in språkanpassning, nätverk och diskpartitionerna." #. Tag: title #: boot-installer.xml:1628 @@ -1322,26 +2319,48 @@ msgstr "Välja en installationsmetod" #. 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 "Vissa underarkitekturer av &arch-title; har alternativet att starta upp med antingen en Linuxkärna av version 2.4.x eller 2.2.x. När en sådan valmöjlighet finns, prova 2.4.x-kärnan. Installeraren bör även kräva mindre minne när 2.4.x-kärnan används eftersom 2.2.x kräver en fast storlek på ramdisken och 2.4.x använder tmpfs." +msgid "" +"Some &arch-title; subarchs have the option of booting using either a 2.4.x " +"or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux " +"kernel. The installer should also require less memory when using a 2.4.x " +"linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses " +"tmpfs." +msgstr "" +"Vissa underarkitekturer av &arch-title; har alternativet att starta upp med " +"antingen en Linuxkärna av version 2.4.x eller 2.2.x. När en sådan " +"valmöjlighet finns, prova 2.4.x-kärnan. Installeraren bör även kräva mindre " +"minne när 2.4.x-kärnan används eftersom 2.2.x kräver en fast storlek på " +"ramdisken och 2.4.x använder tmpfs." #. 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 "Om du använder en Linux-kärna med version 2.2.x, behöver du använda kärnparametern &ramdisksize;." +msgid "" +"If you are using a 2.2.x linux kernel, then you need to use the " +"&ramdisksize; kernel parameter." +msgstr "" +"Om du använder en Linux-kärna med version 2.2.x, behöver du använda " +"kärnparametern &ramdisksize;." #. Tag: para #: boot-installer.xml:1643 #, no-c-format -msgid "Make sure root=/dev/ram is one of your kernel parameters." -msgstr "Se till att root=/dev/ram är en av dina kärnparametrar." +msgid "" +"Make sure root=/dev/ram is one of your kernel " +"parameters." +msgstr "" +"Se till att root=/dev/ram är en av dina " +"kärnparametrar." #. Tag: para #: boot-installer.xml:1648 #, no-c-format -msgid "If you're having trouble, check cts's &arch-title; debian-installer FAQ." -msgstr "Om du får problem, ta en titt i cts's &arch-title; debian-installer FAQ." +msgid "" +"If you're having trouble, check cts's " +"&arch-title; debian-installer FAQ." +msgstr "" +"Om du får problem, ta en titt i cts's " +"&arch-title; debian-installer FAQ." #. Tag: title #: boot-installer.xml:1665 @@ -1352,14 +2371,24 @@ msgstr "Amiga" #. 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 "Den enda installationsmetoden tillgänglig för amiga är via hårddisken (se ). Med andra ord, cd-skivan är inte startbar." +msgid "" +"The only method of installation available to amiga is the hard drive (see " +"). In other words the cdrom is not " +"bootable." +msgstr "" +"Den enda installationsmetoden tillgänglig för amiga är via hårddisken (se " +"). Med andra ord, cd-skivan är " +"inte startbar." #. 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 "Amiga fungerar för tillfället inte med bogl, så om du ser fel från bogl behöver du inkludera uppstartsparametern fb=false." +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 "" +"Amiga fungerar för tillfället inte med bogl, så om du ser fel från bogl " +"behöver du inkludera uppstartsparametern fb=false." #. Tag: title #: boot-installer.xml:1681 @@ -1370,14 +2399,25 @@ msgstr "Atari" #. 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 "Installeraren för atari kan startas från antingen hårddisken (se ) eller från disketter (se ). Med andra ord, cd-skivan är inte startbar." +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 "" +"Installeraren för atari kan startas från antingen hårddisken (se ) eller från disketter (se ). Med andra ord, cd-skivan är inte startbar." #. 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 "Atari fungerar för närvarande inte med bogl så om du ser fel från bogl behöver du inkludera uppstartsparametern fb=false." +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 "" +"Atari fungerar för närvarande inte med bogl så om du ser fel från bogl " +"behöver du inkludera uppstartsparametern fb=false." #. Tag: title #: boot-installer.xml:1698 @@ -1388,8 +2428,14 @@ msgstr "BVME6000" #. 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 "Installeraren för BVME6000 kan behöva startas från en cd-rom (se ), startdisketter (se ), eller via nätverket (se )." +msgid "" +"The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." +msgstr "" +"Installeraren för BVME6000 kan behöva startas från en cd-rom (se ), startdisketter (se ), eller via nätverket (se )." #. Tag: title #: boot-installer.xml:1709 @@ -1400,14 +2446,36 @@ msgstr "Macintosh" #. 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 "Den enda installationsmetoden som är tillgänglig för mac är från hårddisken (se ). Med andra ord, cd-skivan är inte startbar. Mac har ingen fungerande 2.4.x-kärna." +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 "" +"Den enda installationsmetoden som är tillgänglig för mac är från hårddisken " +"(se ). Med andra ord, cd-skivan är " +"inte startbar. Mac har ingen fungerande 2.4.x-kärna." #. 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 "Om din maskinvara använder en 53c9x-baserad scsi-buss, behöver du kanske inkludera kärnparametern mac53c9x=1,0. Maskinvara med två sådana scsi-bussar, såsom Quadra 950, behöver istället mac53c9x=2,0. Alternativt kan parametern anges som mac53c9x=-1,0 som lämnar automatisk identifiering påslagen, men som inaktiverar SCSI-nedkopplingar. Observera att den här parametern endast behöver anges om du har fler än en hårddisk; i annat fall kommer systemet att köra snabbare än om du inte angav det." +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 "" +"Om din maskinvara använder en 53c9x-baserad scsi-buss, behöver du kanske " +"inkludera kärnparametern mac53c9x=1,0. Maskinvara med " +"två sådana scsi-bussar, såsom Quadra 950, behöver istället " +"mac53c9x=2,0. Alternativt kan parametern anges som " +"mac53c9x=-1,0 som lämnar automatisk identifiering " +"påslagen, men som inaktiverar SCSI-nedkopplingar. Observera att den här " +"parametern endast behöver anges om du har fler än en hårddisk; i annat fall " +"kommer systemet att köra snabbare än om du inte angav det." #. Tag: title #: boot-installer.xml:1732 @@ -1418,8 +2486,16 @@ msgstr "MVME147 och MVME16x" #. 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 "Installeraren för MVME147 och MVME16x kan behöva startas från antingen startdisketter (se ) eller via nätverket (se ). Med andra ord är inte cd-skivan startbar." +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 "" +"Installeraren för MVME147 och MVME16x kan behöva startas från antingen " +"startdisketter (se ) eller via " +"nätverket (se ). Med andra ord är " +"inte cd-skivan startbar." #. Tag: title #: boot-installer.xml:1743 @@ -1430,8 +2506,14 @@ msgstr "Q40/Q60" #. 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 "Den enda installationsmetoden som är tillgänglig för Q40/Q60 är från hårddisken (se ). Med andra ord, cd-skivan är inte startbar." +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 "" +"Den enda installationsmetoden som är tillgänglig för Q40/Q60 är från " +"hårddisken (se ). Med andra ord, " +"cd-skivan är inte startbar." #. Tag: title #: boot-installer.xml:1755 @@ -1440,30 +2522,59 @@ msgid "Booting from a Hard Disk" msgstr "Starta upp från en hårddisk" #. Tag: para -#: boot-installer.xml:1761 -#: boot-installer.xml:2359 +#: boot-installer.xml:1761 boot-installer.xml:2359 #, no-c-format -msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation." -msgstr "Uppstart från ett existerande operativsystem är ofta ett bekvämt alternativ, för vissa system är det den enda installationsmetoden som stöds." +msgid "" +"Booting from an existing operating system is often a convenient option; for " +"some systems it is the only supported method of installation." +msgstr "" +"Uppstart från ett existerande operativsystem är ofta ett bekvämt alternativ, " +"för vissa system är det den enda installationsmetoden som stöds." #. Tag: para -#: boot-installer.xml:1767 -#: boot-installer.xml:2365 +#: boot-installer.xml:1767 boot-installer.xml:2365 #, no-c-format -msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files in ." -msgstr "För att starta upp installeraren från hårddisk måste du redan ha hämtat och placerat de filer som behövs i ." +msgid "" +"To boot the installer from hard disk, you will have already completed " +"downloading and placing the needed files in ." +msgstr "" +"För att starta upp installeraren från hårddisk måste du redan ha hämtat och " +"placerat de filer som behövs i ." #. 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 "Åtminstone sex olika ramdiskar kan användas för att starta upp från hårddisken, tre olika typer vardera med och utan stöd för en Linuxkärna version 2.2.x (se MANIFEST för detaljer)." +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 "" +"Åtminstone sex olika ramdiskar kan användas för att starta upp från " +"hårddisken, tre olika typer vardera med och utan stöd för en Linuxkärna " +"version 2.2.x (se MANIFEST för detaljer)." #. 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 "De tre olika typer av ramdiskar är cdrom, hd-media och nativehd. De här ramdiskarna skiljer sig endast i sin källkod för installationspaketen. Ramdisken cdrom använder en cd-rom för att hämta paket för debian-installer. Ramdisken hd-media använder en iso-avbild av en cd-rom som för närvarande ligger på en hårddisk. Till slut, ramdisken nativehd använder nätet för att installera paket." +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 "" +"De tre olika typer av ramdiskar är cdrom, hd-" +"media och nativehd. De här ramdiskarna " +"skiljer sig endast i sin källkod för installationspaketen. Ramdisken " +"cdrom använder en cd-rom för att hämta paket för debian-" +"installer. Ramdisken hd-media använder en iso-avbild av " +"en cd-rom som för närvarande ligger på en hårddisk. Till slut, ramdisken " +"nativehd använder nätet för att installera paket." #. Tag: title #: boot-installer.xml:1805 @@ -1474,14 +2585,36 @@ msgstr "Starta upp från AmigaOS" #. 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 "I Workbench, start Linux-installationsprocessen genom att dubbelklicka på ikonen StartInstall i katalogen debian." +msgid "" +"In the Workbench, start the Linux installation process by " +"double-clicking on the StartInstall icon in the " +"debian directory." +msgstr "" +"I Workbench, start Linux-installationsprocessen genom att " +"dubbelklicka på ikonen StartInstall i katalogen " +"debian." #. 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 "Du kanske måste trycka på &enterkey;-tangenten två gånger efter att Amiga-installationsprogrammet har skrivit ut viss felsökningsinformation i ett fönster. Efter det här kommer skärmen att bli grå, sedan ett par sekunders fördröjning. Härnäst kommer en svart skärm med vit text att visas, som visar alla sorters felsökningsinformation för kärnan. De här meddelanden kan rulla förbi för snabbt för dig att läsa, men det är OK. Efter ett par sekunder ska installationsprogrammet startas automatiskt, så att du kan fortsätta på ." +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 "" +"Du kanske måste trycka på &enterkey;-tangenten två gånger efter att Amiga-" +"installationsprogrammet har skrivit ut viss felsökningsinformation i ett " +"fönster. Efter det här kommer skärmen att bli grå, sedan ett par sekunders " +"fördröjning. Härnäst kommer en svart skärm med vit text att visas, som visar " +"alla sorters felsökningsinformation för kärnan. De här meddelanden kan rulla " +"förbi för snabbt för dig att läsa, men det är OK. Efter ett par sekunder ska " +"installationsprogrammet startas automatiskt, så att du kan fortsätta på " +"." #. Tag: title #: boot-installer.xml:1827 @@ -1492,14 +2625,37 @@ msgstr "Starta upp från Atari TOS" #. 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 "I skrivbordsmiljön GEM, starta Linux-installationsprocessen genom att dubbelklicka på ikonen bootstra.prg i katalogen debian och klicka Ok i programmets inställningsruta." +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 "" +"I skrivbordsmiljön GEM, starta Linux-installationsprocessen genom att " +"dubbelklicka på ikonen bootstra.prg i katalogen " +"debian och klicka Ok i " +"programmets inställningsruta." #. 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 "Du kanske måste trycka på &enterkey;-tangenten efter att Atari-bootstrapprogrammet har skrivit ut viss felsökningsinformation i ett fönster. Efter det här kommer skärmen att bli grå, sedan ett par sekunders fördröjning. Härnäst kommer en svart skärm med vit text att visas, som visar alla sorters felsökningsinformation för kärnan. De här meddelanden kan rulla förbi för snabbt för dig att läsa, men det är OK. Efter ett par sekunder ska installationsprogrammet startas automatiskt, så att du kan fortsätta på ." +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 "" +"Du kanske måste trycka på &enterkey;-tangenten efter att Atari-" +"bootstrapprogrammet har skrivit ut viss felsökningsinformation i ett " +"fönster. Efter det här kommer skärmen att bli grå, sedan ett par sekunders " +"fördröjning. Härnäst kommer en svart skärm med vit text att visas, som visar " +"alla sorters felsökningsinformation för kärnan. De här meddelanden kan rulla " +"förbi för snabbt för dig att läsa, men det är OK. Efter ett par sekunder ska " +"installationsprogrammet startas automatiskt, så att du kan fortsätta på " +"." #. Tag: title #: boot-installer.xml:1850 @@ -1510,38 +2666,112 @@ msgstr "Starta upp från MacOS" #. 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 "Du måste bibehålla original Mac-systemet och starta upp från det. Det är viktigt att starta upp MacOS för att förbereda en uppstart av starthanteraren Penguin, att du håller ned tangenten shift för att förhindra att utökningar läses in. Om du inte använder MacOS annat än för att läsa in Linux, kan du åstadkomma samma sak genom att ta bort alla utökningar och kontrollpaneler från Macens System-mapp. Annars kan körande utökningar lämnas kvar och orsaka diverse problem för den körande Linux-kärnan." +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 "" +"Du måste bibehålla original Mac-systemet och starta upp från det. Det är " +"viktigt att starta upp MacOS för att förbereda en " +"uppstart av starthanteraren Penguin, att du håller ned tangenten " +"shift för att förhindra att utökningar läses in. Om du inte " +"använder MacOS annat än för att läsa in Linux, kan du åstadkomma samma sak " +"genom att ta bort alla utökningar och kontrollpaneler från Macens System-" +"mapp. Annars kan körande utökningar lämnas kvar och orsaka diverse problem " +"för den körande Linux-kärnan." #. 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 "Mac kräver starthanteraren Penguin. Om du inte har verktygen för att hantera ett Stuffit-arkiv, &penguin19.hfs; är en hfs-diskavbild med en uppackad Penguin. beskriver hur man kopierar den här avbilden till en diskett." +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 "" +"Mac kräver starthanteraren Penguin. Om du inte har " +"verktygen för att hantera ett Stuffit-arkiv, &penguin19." +"hfs; är en hfs-diskavbild med en uppackad Penguin. beskriver hur man kopierar den här avbilden till " +"en diskett." #. 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 "På MacOS-skrivbordet, starta Linux-installationsprocessen genom att dubbelklicka på Penguin Prefs-ikonen i katalogen Penguin. Uppstartaren Penguin kommer att startas upp. Gå till posten Settings i menyn File, klicka på fliken Kernel. Välj kärnavbilden (vmlinuz) och ramdisk (initrd.gz) i katalogen install genom att klicka på motsvarande knappar i övre högra hörnet, och navigera fram till filerna i dialogrutan." +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 "" +"På MacOS-skrivbordet, starta Linux-installationsprocessen genom att " +"dubbelklicka på Penguin Prefs-ikonen i katalogen " +"Penguin. Uppstartaren Penguin kommer " +"att startas upp. Gå till posten Settings i menyn " +"File, klicka på fliken Kernel. Välj " +"kärnavbilden (vmlinuz) och ramdisk (initrd." +"gz) i katalogen install genom att klicka på " +"motsvarande knappar i övre högra hörnet, och navigera fram till filerna i " +"dialogrutan." #. 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 "För att ställa in uppstartsparametrarna i Penguin, välj File -> Settings..., växla sedan till fliken Options. Uppstartsparametrar kan anges i textrutan. Om du alltid vill använda de här inställningarna, välj File -> Save Settings as Default." +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 "" +"För att ställa in uppstartsparametrarna i Penguin, välj File -> Settings..., växla sedan till " +"fliken Options. Uppstartsparametrar kan anges i " +"textrutan. Om du alltid vill använda de här inställningarna, välj " +"File -> Save Settings as Default." #. 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 "Stäng Settings-dialogen, spara inställningarna och starta bootstrap med posten Boot Now i File-menyn." +msgid "" +"Close the Settings dialog, save the settings and start " +"the bootstrap using the Boot Now item in the " +"File menu." +msgstr "" +"Stäng Settings-dialogen, spara inställningarna och " +"starta bootstrap med posten Boot Now i " +"File-menyn." #. 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 "Starthanteraren Penguin kommer att skriva ut viss felsökningsinformation i ett fönster. Efter det här kommer skärmen att bli grå, sedan ett par sekunders fördröjning. Härnäst kommer en svart skärm med vit text att visas, som visar alla sorters felsökningsinformation för kärnan. De här meddelanden kan rulla förbi för snabbt för dig att läsa, men det är OK. Efter ett par sekunder ska installationsprogrammet startas automatiskt, så att du kan fortsätta på ." +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 "" +"Starthanteraren Penguin kommer att skriva ut viss " +"felsökningsinformation i ett fönster. Efter det här kommer skärmen att bli " +"grå, sedan ett par sekunders fördröjning. Härnäst kommer en svart skärm med " +"vit text att visas, som visar alla sorters felsökningsinformation för " +"kärnan. De här meddelanden kan rulla förbi för snabbt för dig att läsa, men " +"det är OK. Efter ett par sekunder ska installationsprogrammet startas " +"automatiskt, så att du kan fortsätta på ." #. Tag: title #: boot-installer.xml:1917 @@ -1558,26 +2788,43 @@ msgstr "FIXME" #. Tag: para #: boot-installer.xml:1923 #, no-c-format -msgid "The installation program should start automatically, so you can continue below at ." -msgstr "Installationsprogrammet ska starta automatiskt, så du kan fortsätta nedan i ." +msgid "" +"The installation program should start automatically, so you can continue " +"below at ." +msgstr "" +"Installationsprogrammet ska starta automatiskt, så du kan fortsätta nedan i " +"." #. 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 "För närvarande, den enda underarkitekturen av &arch-title; som har stöd för uppstart via cd-rom är BVME6000." +msgid "" +"Currently, the only &arch-title; subarchitecture that supports CD-ROM " +"booting is the BVME6000." +msgstr "" +"För närvarande, den enda underarkitekturen av &arch-title; som har stöd för " +"uppstart via cd-rom är BVME6000." #. 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 "Efter uppstarten av VMEbus-systemen kommer du bli presenterad med LILO-prompten Boot:. Vid prompten, ange en av följande för att starta upp Linux och påbörja installationen av Debian-programvaran med terminalemuleringen vt102." +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 "" +"Efter uppstarten av VMEbus-systemen kommer du bli presenterad med LILO-" +"prompten Boot:. Vid prompten, ange en av följande för att " +"starta upp Linux och påbörja installationen av Debian-programvaran med " +"terminalemuleringen vt102." #. Tag: para #: boot-installer.xml:2018 #, no-c-format msgid "type i6000 &enterkey; to install a BVME4000/6000" -msgstr "ange i6000 &enterkey; för att installera en BVME4000/6000" +msgstr "" +"ange i6000 &enterkey; för att installera en BVME4000/6000" #. Tag: para #: boot-installer.xml:2023 @@ -1589,29 +2836,42 @@ msgstr "ange i162 &enterkey; för att installera en MVME162" #: boot-installer.xml:2028 #, no-c-format msgid "type i167 &enterkey; to install an MVME166/167" -msgstr "ange i167 &enterkey; för att installera en MVME166/167" +msgstr "" +"ange i167 &enterkey; för att installera en MVME166/167" #. 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 "Du kan även lägga till strängen TERM=vt100 för att använda terminalemuleringen vt100, exempelvis i6000 TERM=vt100 &enterkey;." +msgid "" +"You may additionally append the string TERM=vt100 to use " +"vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." +msgstr "" +"Du kan även lägga till strängen TERM=vt100 för att använda " +"terminalemuleringen vt100, exempelvis i6000 TERM=vt100 &enterkey;." #. 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 "För de flesta &arch-title;-arkitekturer är uppstart från ett lokalt filsystem den metod som rekommenderas." +msgid "" +"For most &arch-title; architectures, booting from a local filesystem is the " +"recommended method." +msgstr "" +"För de flesta &arch-title;-arkitekturer är uppstart från ett lokalt " +"filsystem den metod som rekommenderas." #. 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 "Uppstart från startdisketten stöds endast på Atari och VME (med en SCSI-diskettenhet på VME) för tillfället." +msgid "" +"Booting from the boot floppy is supported only for Atari and VME (with a " +"SCSI floppy drive on VME) at this time." +msgstr "" +"Uppstart från startdisketten stöds endast på Atari och VME (med en SCSI-" +"diskettenhet på VME) för tillfället." #. Tag: title -#: boot-installer.xml:2068 -#: boot-installer.xml:2115 +#: boot-installer.xml:2068 boot-installer.xml:2115 #, no-c-format msgid "SGI TFTP Booting" msgstr "Uppstart för SGI via TFTP" @@ -1622,46 +2882,63 @@ msgstr "Uppstart för SGI via TFTP" 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" +" 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 "" "Efter man gått in i kommandomonitorn, använd \n" "bootp():\n" -" på SGI-maskiner för att starta upp Linux och påbörja installationen av Debian-programvaran. För att det här ska fungera måste du rensa miljövariabeln netaddr. Ange \n" +" på SGI-maskiner för att starta upp Linux och " +"påbörja installationen av Debian-programvaran. För att det här ska fungera " +"måste du rensa miljövariabeln netaddr. Ange " +"\n" "unsetenv netaddr\n" " i kommandomonitorn för att göra det." #. Tag: title -#: boot-installer.xml:2088 -#: boot-installer.xml:2137 -#: boot-installer.xml:2192 +#: boot-installer.xml:2088 boot-installer.xml:2137 boot-installer.xml:2192 #: boot-installer.xml:2231 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "Uppstart för Broadcom BCM91250A och BCM91480B via TFTP" #. Tag: para -#: boot-installer.xml:2089 -#: boot-installer.xml:2193 +#: boot-installer.xml:2089 boot-installer.xml:2193 #, no-c-format msgid "" -"On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load the SiByl boot loader via TFTP which will then load and start the Debian installer. In most cases, you will first obtain an IP address via DHCP but it is also possible to configure a static address. In order to use DHCP, you can enter the following command on the CFE prompt: \n" +"On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load " +"the SiByl boot loader via TFTP which will then load and start the Debian " +"installer. In most cases, you will first obtain an IP address via DHCP but " +"it is also possible to configure a static address. In order to use DHCP, you " +"can enter the following command on the CFE prompt: " +"\n" "ifconfig eth0 -auto\n" -" Once you have obtained an IP address, you can load SiByl with the following command: \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." +" 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 "" -"På evalueringskorten Broadcom BCM91250A och BCM91480B, måste du läsa in starthanteraren SiByl via TFTP som sedan kommer att läsa in och starta Debian-installer. I de flesta fall kommer du första att ta emot en IP-adress via DHCP men det är även möjligt att konfigurera en statisk adress. För att använda DHCP kan du ange följande kommando på CFE-prompten: \n" +"På evalueringskorten Broadcom BCM91250A och BCM91480B, måste du läsa in " +"starthanteraren SiByl via TFTP som sedan kommer att läsa in och starta " +"Debian-installer. I de flesta fall kommer du första att ta emot en IP-adress " +"via DHCP men det är även möjligt att konfigurera en statisk adress. För att " +"använda DHCP kan du ange följande kommando på CFE-prompten: " +"\n" "ifconfig eth0 -auto\n" -" När du har tagit emot en IP-adress, kan du läsa in SiByl med följande kommando: \n" +" När du har tagit emot en IP-adress, kan du läsa " +"in SiByl med följande kommando: \n" "boot 192.168.1.1:/boot/sibyl\n" -" Du behöver ersätta IP-adressen som listas i exemplet med antingen namnet eller IP-adressen för din TFTP-server. När du kört det här kommandot kommer installeraren att läsas in automatiskt." +" Du behöver ersätta IP-adressen som listas i " +"exemplet med antingen namnet eller IP-adressen för din TFTP-server. När du " +"kört det här kommandot kommer installeraren att läsas in automatiskt." #. Tag: title -#: boot-installer.xml:2112 -#: boot-installer.xml:2216 -#: boot-installer.xml:2739 +#: boot-installer.xml:2112 boot-installer.xml:2216 boot-installer.xml:2739 #, no-c-format msgid "Boot Parameters" msgstr "Uppstartsparametrar" @@ -1669,20 +2946,30 @@ msgstr "Uppstartsparametrar" #. 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 "På SGI-maskiner kan du lägga till uppstartsparametrar till kommandot bootp(): i kommandomonitorn." +msgid "" +"On SGI machines you can append boot parameters to the bootp(): command in the command monitor." +msgstr "" +"På SGI-maskiner kan du lägga till uppstartsparametrar till kommandot " +"bootp(): i kommandomonitorn." #. 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" +"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:" +" Further kernel parameters can be passed via " +"append:" msgstr "" -"Efter kommandot bootp(): kan du ange sökvägen och namnet på filen som ska starta upp om du inte har angivit ett namn via din bootp/dhcpserver. Exempel: \n" +"Efter kommandot bootp(): kan du ange sökvägen och namnet " +"på filen som ska starta upp om du inte har angivit ett namn via din bootp/" +"dhcpserver. Exempel: \n" "bootp():/boot/tftpboot.img\n" -" Ytterligare kärnparametrar kan skickas med via append:" +" Ytterligare kärnparametrar kan skickas med via " +"append:" #. Tag: screen #: boot-installer.xml:2131 @@ -1691,15 +2978,21 @@ msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "bootp(): append=\"root=/dev/sda1\"" #. Tag: para -#: boot-installer.xml:2138 -#: boot-installer.xml:2232 +#: boot-installer.xml:2138 boot-installer.xml:2232 #, no-c-format -msgid "You cannot pass any boot parameters directly from the CFE prompt. Instead, you have to edit the /boot/sibyl.conf file on the TFTP server and add your parameters to the extra_args variable." -msgstr "Du kan inte skicka med några uppstartsparametrar direkt från CFE-prompten. Istället kan du redigera filen /boot/sibyl.conf på TFTP-servern och lägga till din parametrar till variabeln extra_args." +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 "" +"Du kan inte skicka med några uppstartsparametrar direkt från CFE-prompten. " +"Istället kan du redigera filen /boot/sibyl.conf på TFTP-" +"servern och lägga till din parametrar till variabeln " +"extra_args." #. Tag: title -#: boot-installer.xml:2157 -#: boot-installer.xml:2219 +#: boot-installer.xml:2157 boot-installer.xml:2219 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "Starta upp Cobalt via TFTP" @@ -1707,26 +3000,62 @@ msgstr "Starta upp Cobalt via TFTP" #. 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 "Ärligt talat använder Cobalt inte TFTP utan NFS för att starta upp. Du behöver installera en NFS-server och lägga installerarens filer i /nfsroot. När du startar upp din Cobalt måste du trycka ned vänstra och högra piltangenterna samtidigt för att maskinen ska starta upp via nätverket. Den kommer då att visa flera alternativ på skärmen. Det finns följande installationsmetoder:" +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 "" +"Ärligt talat använder Cobalt inte TFTP utan NFS för att starta upp. Du " +"behöver installera en NFS-server och lägga installerarens filer i /" +"nfsroot. När du startar upp din Cobalt måste du trycka ned " +"vänstra och högra piltangenterna samtidigt för att maskinen ska starta upp " +"via nätverket. Den kommer då att visa flera alternativ på skärmen. Det finns " +"följande installationsmetoder:" #. 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 "Via SSH (standard): I det här fallet kommer installeraren att konfigurera nätverket via DHCP och starta en SSH-server. Den kommer sedan att visa ett slumpat lösenord och annan inloggningsinformation (som IP-adress) på Cobalts LCD-skärm. När du ansluter till maskinen med en SSH-klient kan du påbörja installationen." +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 "" +"Via SSH (standard): I det här fallet kommer installeraren att konfigurera " +"nätverket via DHCP och starta en SSH-server. Den kommer sedan att visa ett " +"slumpat lösenord och annan inloggningsinformation (som IP-adress) på Cobalts " +"LCD-skärm. När du ansluter till maskinen med en SSH-klient kan du påbörja " +"installationen." #. 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 "Via seriekonsoll: Med en nollmodem-kabel kan du ansluta till serieporten på din Cobalt-maskin (med 115200 bps) och genomföra installationen på detta sätt. Detta alternativ är inte tillgängligt för Qube 2700-maskiner (Qube1) eftersom de inte har en serieport." +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 "" +"Via seriekonsoll: Med en nollmodem-kabel kan du ansluta till serieporten på " +"din Cobalt-maskin (med 115200 bps) och genomföra installationen på detta " +"sätt. Detta alternativ är inte tillgängligt för Qube 2700-maskiner (Qube1) " +"eftersom de inte har en serieport." #. 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 "Du kan inte skicka med några uppstartsparametrar direkt. Istället ska du redigera filen /nfsroot/default.colo på NFS-servern och lägga till dina parametrar till variabeln args." +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 "" +"Du kan inte skicka med några uppstartsparametrar direkt. Istället ska du " +"redigera filen /nfsroot/default.colo på NFS-servern och " +"lägga till dina parametrar till variabeln args." #. Tag: title #: boot-installer.xml:2248 @@ -1737,14 +3066,26 @@ msgstr "Begränsningar för s390" #. 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 "För att kunna köra installationssystemet på S/390 behövs en fungerande nätverkskonfiguration och en ssh-session." +msgid "" +"In order to run the installation system a working network setup and ssh " +"session is needed on S/390." +msgstr "" +"För att kunna köra installationssystemet på S/390 behövs en fungerande " +"nätverkskonfiguration och en ssh-session." #. 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 "Uppstartsprocessen startar med en nätverkskonfiguration som frågar dig efter flera nätverksparametrar. Om konfigurationen lyckas kommer du kunna logga in på systemet genom att starta en ssh-session som kommer att starta standardinstallationssystemet." +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 "" +"Uppstartsprocessen startar med en nätverkskonfiguration som frågar dig efter " +"flera nätverksparametrar. Om konfigurationen lyckas kommer du kunna logga in " +"på systemet genom att starta en ssh-session som kommer att starta " +"standardinstallationssystemet." #. Tag: title #: boot-installer.xml:2265 @@ -1755,26 +3096,67 @@ msgstr "Uppstartsparametrar för s390" #. 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 "På S/390 kan du lägga till uppstartsparametrar i parm-filen. Denna fil kan antingen vara i ASCII- eller EBCDIC-format. Läs Device Drivers and Installation Commands för mer information om S/390-specifika uppstartsparametrar." +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 "" +"På S/390 kan du lägga till uppstartsparametrar i parm-filen. Denna fil kan " +"antingen vara i ASCII- eller EBCDIC-format. Läs Device Drivers and Installation Commands för mer " +"information om S/390-specifika uppstartsparametrar." #. 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 "För närvarande är PReP och New World PowerMac de enda underarkitekturerna för &arch-title; som har stöd för uppstart från cd-rom. På PowerMac, håll ned c-tangenten, eller annars tangentkombinationen Command, Option, Shift och Delete tillsammans vid uppstart för att starta upp från cd-rom." +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 "" +"För närvarande är PReP och New World PowerMac de enda underarkitekturerna " +"för &arch-title; som har stöd för uppstart från cd-rom. På PowerMac, håll " +"ned c-tangenten, eller annars tangentkombinationen " +"Command, Option, Shift " +"och Delete tillsammans vid uppstart för att starta upp från " +"cd-rom." #. 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 "OldWorld PowerMac kommer inte att starta upp på en Debian-cd på grund av att OldWorld-datorer förlitade sig på att en Mac OS ROM cd-uppstartsdrivrutin skulle finnas på cd-skivan, och en fri version av den här drivrutinen finns inte tillgänglig. Alla OldWorld-system har diskettenheter, så använd diskettenheten för att starta installeraren, och peka sedan installeraren till cd-enheten för de nödvändiga filerna." +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 "" +"OldWorld PowerMac kommer inte att starta upp på en Debian-cd på grund av att " +"OldWorld-datorer förlitade sig på att en Mac OS ROM cd-uppstartsdrivrutin " +"skulle finnas på cd-skivan, och en fri version av den här drivrutinen finns " +"inte tillgänglig. Alla OldWorld-system har diskettenheter, så använd " +"diskettenheten för att starta installeraren, och peka sedan installeraren " +"till cd-enheten för de nödvändiga filerna." #. 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 "Om ditt system inte startar upp direkt från cd-rom, kan du fortfarande använda cd-enheten för att installera systemet. På NewWorld kan du även använde ett OpenFirmware-kommando för att manuellt starta upp från cd-rom. Följ instruktionerna i för att starta upp från hårddisken, använd dock sökvägen till yaboot på cd-skivan vid OF-prompten, såsom" +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 "" +"Om ditt system inte startar upp direkt från cd-rom, kan du fortfarande " +"använda cd-enheten för att installera systemet. På NewWorld kan du även " +"använde ett OpenFirmware-kommando för att manuellt starta upp från cd-rom. " +"Följ instruktionerna i för att starta upp " +"från hårddisken, använd dock sökvägen till yaboot på cd-" +"skivan vid OF-prompten, såsom" #. Tag: screen #: boot-installer.xml:2347 @@ -1809,8 +3191,25 @@ msgstr "Starta upp OldWorld PowerMac från MacOS" #. 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 "Om du ställer in en BootX i , kan du använda den för att starta upp installationssystemet. Dubbelklicka på programikonen BootX. Klicka på knappen Options och välj Use Specified RAM Disk. Det här kommer att ge dig chansen att välja filen ramdisk.image.gz. Du kan behöva att kryssa i rutan No Video Driver, beroende på din maskinvara. Klicka sedan på knappen Linux för att stänga ner MacOS och starta upp installeraren." +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 "" +"Om du ställer in en BootX i , kan du " +"använda den för att starta upp installationssystemet. Dubbelklicka på " +"programikonen BootX. Klicka på knappen " +"Options och välj Use Specified RAM Disk. Det här kommer att ge dig chansen att välja filen " +"ramdisk.image.gz. Du kan behöva att kryssa i rutan " +"No Video Driver, beroende på din maskinvara. Klicka " +"sedan på knappen Linux för att stänga ner MacOS och " +"starta upp installeraren." #. Tag: title #: boot-installer.xml:2402 @@ -1822,17 +3221,49 @@ msgstr "Starta upp NewWorld Mac från OpenFirmware" #: 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" +"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" +" 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." +" 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 "" -"Du har redan placerat filerna vmlinux, initrd.gz, yaboot och yaboot.conf i rotnivån av din HFS-partition i . Starta om datorn, och omedelbart (under klockljudet) håll ned tangenterna Option, Command (klöverblad/Apple), o och f samtidigt. Efter ett par sekunder kommer du att komma till Open Firmware-prompten. Vid prompten, ange \n" +"Du har redan placerat filerna vmlinux, initrd." +"gz, yaboot och yaboot.conf i rotnivån av din HFS-partition i . Starta om datorn, och omedelbart (under klockljudet) håll ned tangenterna " +"Option, Command (klöverblad/Apple), " +"o och f samtidigt. Efter ett par sekunder " +"kommer du att komma till Open Firmware-prompten. Vid prompten, ange " +"\n" "0 > boot hd:x,yaboot\n" -" ersätt x med partitionsnumret för HFS-partitionen där kärnan och yaboot-filerna placerades, följt av &enterkey;. På vissa maskiner kan du behöva använda ide0: istället för hd:. Om ett par sekunder kommer du att se en yaboot-prompt \n" +" ersätt x med " +"partitionsnumret för HFS-partitionen där kärnan och yaboot-filerna " +"placerades, följt av &enterkey;. På vissa maskiner kan du behöva använda " +"ide0: istället för hd:. Om ett " +"par sekunder kommer du att se en yaboot-prompt \n" "boot:\n" -" Vid yaboots boot:-prompt, ange antingen install eller install video=ofonly följt av &enterkey;. Argumentet video=ofonly är för maximal kompatibilitet; du kan prova den om install inte fungerar. Debians installationprogram ska nu starta." +" Vid yaboots boot:-prompt, ange " +"antingen install eller install " +"video=ofonly följt av &enterkey;. Argumentet " +"video=ofonly är för maximal kompatibilitet; du kan " +"prova den om install inte fungerar. Debians " +"installationprogram ska nu starta." #. Tag: title #: boot-installer.xml:2438 @@ -1844,79 +3275,178 @@ msgstr "Starta upp från USB-minne" #: boot-installer.xml:2439 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." -msgstr "För närvarande är NewWorld PowerMac-system kända att ha stöd för uppstart via USB." +msgstr "" +"För närvarande är NewWorld PowerMac-system kända att ha stöd för uppstart " +"via USB." #. 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 "Se till att du har förberett allt från . För att starta upp ett Macintosh-system från ett USB-minne behöver du använda Open Firmware-prompten, eftersom Open Firmware inte söker efter USB-lagringsenheter som standard. För att komma till prompten, håll ned Command Option o f samtidigt vid uppstart (se )." +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 "" +"Se till att du har förberett allt från . " +"För att starta upp ett Macintosh-system från ett USB-minne behöver du " +"använda Open Firmware-prompten, eftersom Open Firmware inte söker efter USB-" +"lagringsenheter som standard. För att komma till prompten, håll ned " +"Command Option o f samtidigt vid uppstart (se )." #. 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 "Du behöver ta reda på var USB-lagringsenheten visas i enhetsträdet, eftersom ofpath för tillfället inte kan ta reda på det automatiskt. Ange dev / ls och devalias vid Open Firmware-prompten för att gå en lista på alla kända enheter och enhetsalias. På upphovsmannens system med olika typer av USB-minnen, fungerar sökvägar såsom usb0/disk, usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1 och /pci@f2000000/usb@1b,1/hub@1/disk@1." +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 "" +"Du behöver ta reda på var USB-lagringsenheten visas i enhetsträdet, eftersom " +"ofpath för tillfället inte kan ta reda på det " +"automatiskt. Ange dev / ls och devalias vid Open Firmware-prompten för att gå en lista på alla kända " +"enheter och enhetsalias. På upphovsmannens system med olika typer av USB-" +"minnen, fungerar sökvägar såsom usb0/disk, " +"usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1 och /pci@f2000000/usb@1b,1/hub@1/disk@1." #. 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." +"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 "" -"Efter att enhetssökvägen har fastställts, använd ett kommando liknande den här för att starta upp installeraren: \n" -"boot usb0/disk:2,\\\\:tbxi\n" -" 2 matchar den Apple_HFS- eller Apple_Bootstrap-partition på vilken du tidigare kopierade in uppstartsavbilden, och delen ,\\\\:tbxi instruerar Open Firmware att starta upp från filen med HFS-filtypen \"tbxi\" (alltså, yaboot) i katalogen som tidigare välsignats med hattrib -b." +"Efter att enhetssökvägen har fastställts, använd ett kommando liknande den " +"här för att starta upp installeraren: \n" +"boot usb0/disk:2,\\\\:" +"tbxi\n" +" 2 matchar den " +"Apple_HFS- eller Apple_Bootstrap-partition på vilken du tidigare kopierade " +"in uppstartsavbilden, och delen ,\\\\:tbxi instruerar " +"Open Firmware att starta upp från filen med HFS-filtypen \"tbxi\" (alltså, " +"yaboot) i katalogen som tidigare välsignats med " +"hattrib -b." #. 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 "Systemet ska nu starta upp, och du ska se en boot:-prompt. Här kan du ange ytterligare uppstartsargument, eller bara trycka &enterkey;." +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 "" +"Systemet ska nu starta upp, och du ska se en boot:-prompt. " +"Här kan du ange ytterligare uppstartsargument, eller bara trycka &enterkey;." #. 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 "Denn uppstartsmetod är ny, och kan vara svårt att få att fungera på vissa NewWorld-system. Om du har problem, skriv en installationsrapport, som förklaras i ." +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 "" +"Denn uppstartsmetod är ny, och kan vara svårt att få att fungera på vissa " +"NewWorld-system. Om du har problem, skriv en installationsrapport, som " +"förklaras i ." #. Tag: para #: boot-installer.xml:2522 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." -msgstr "För närvarande har PReP- och NewWorld PowerMac-systemen stöd för uppstart via nätverk." +msgstr "" +"För närvarande har PReP- och NewWorld PowerMac-systemen stöd för uppstart " +"via nätverk." #. 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 "På maskiner med Open Firmware, såsom NewWorld Power Mac, gå in i uppstartsmonitorn (se ) och använd kommandot boot enet:0. PReP- och CHRP-maskiner kan ha olika sätt att adressera nätverket. På en PReP-maskin bör du prova med boot server_ipadr,fil,klient_ipadr." +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 "" +"På maskiner med Open Firmware, såsom NewWorld Power Mac, gå in i " +"uppstartsmonitorn (se ) och använd " +"kommandot boot enet:0. PReP- och CHRP-maskiner kan ha " +"olika sätt att adressera nätverket. På en PReP-maskin bör du prova med " +"boot server_ipadr,fil,klient_ipadr." #. 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 "Uppstart från disketter stöds för &arch-title;, fast det generellt sett endast gäller för OldWorld-system. NewWorld-system är inte utrustade med diskettenheter, och USB-diskettenheter stöds inte för uppstart." +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 "" +"Uppstart från disketter stöds för &arch-title;, fast det generellt sett " +"endast gäller för OldWorld-system. NewWorld-system är inte utrustade med " +"diskettenheter, och USB-diskettenheter stöds inte för uppstart." #. 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 "För att starta upp från disketten boot-floppy-hfs.img, placera den i diskettenheten efter att systemet har stängts ned, och slå sedan på systemet." +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 "" +"För att starta upp från disketten boot-floppy-hfs.img, " +"placera den i diskettenheten efter att systemet har stängts ned, och slå " +"sedan på systemet." #. 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 "För de som inte känner till hur Macintosh-disketter hanteras: en diskett som placeras i maskinen före uppstart kommer att vara första prioritet för systemet att starta upp från. En diskett utan ett giltigt uppstartssystem kommer att matas ut, och maskinen kommer sedan att leta efter startbara hårddiskpartitioner." +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 "" +"För de som inte känner till hur Macintosh-disketter hanteras: en diskett som " +"placeras i maskinen före uppstart kommer att vara första prioritet för " +"systemet att starta upp från. En diskett utan ett giltigt uppstartssystem " +"kommer att matas ut, och maskinen kommer sedan att leta efter startbara " +"hårddiskpartitioner." #. 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 "Efter uppstart kommer disketten root.bin att begäras. Mata in rotdisketten och tryck &enterkey;. Installeringsprogrammet startas automatiskt efter att rotsystemet har lästs in i minnet." +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 "" +"Efter uppstart kommer disketten root.bin att begäras. " +"Mata in rotdisketten och tryck &enterkey;. Installeringsprogrammet startas " +"automatiskt efter att rotsystemet har lästs in i minnet." #. Tag: title #: boot-installer.xml:2577 @@ -1927,20 +3457,58 @@ msgstr "Uppstartsparametrar för PowerPC" #. 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 "Många äldre Apple-skärmar använde läget 640x480 67Hz. Om din bild verkar vara sned på en äldre Apple-skärm, prova att lägga till uppstartsargumentet video=atyfb:vmode:6 , som kommer att välja det läget för de flesta Mach64- och Rage-grafikmaskinvara. För Rage 128-maskinvara, skall video=aty128fb:vmode:6 användas." +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 "" +"Många äldre Apple-skärmar använde läget 640x480 67Hz. Om din bild verkar " +"vara sned på en äldre Apple-skärm, prova att lägga till uppstartsargumentet " +"video=atyfb:vmode:6 , som kommer att välja det läget " +"för de flesta Mach64- och Rage-grafikmaskinvara. För Rage 128-maskinvara, " +"skall video=aty128fb:vmode:6 användas." #. 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 "På maskiner med OpenBoot, gå helt enkelt in i uppstartsmonitorn på maskinen som ska installeras (ee ). Använd kommandot boot net för att starta upp från en TFTP- och RARP-server, eller prova boot net:bootp eller boot net:dhcp för att starta upp från en TFTP och BOOTP eller DHCP-server. Vissa äldre OpenBoot-revisioner kräver att man använder enhetsnamnet, såsom boot le(); de har antagligen inte stöd för BOOTP eller DHCP." +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 "" +"På maskiner med OpenBoot, gå helt enkelt in i uppstartsmonitorn på maskinen " +"som ska installeras (ee ). Använd " +"kommandot boot net för att starta upp från en TFTP- " +"och RARP-server, eller prova boot net:bootp eller " +"boot net:dhcp för att starta upp från en TFTP och " +"BOOTP eller DHCP-server. Vissa äldre OpenBoot-revisioner kräver att man " +"använder enhetsnamnet, såsom boot le(); de har " +"antagligen inte stöd för BOOTP eller DHCP." #. 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 "De flesta OpenBoot-versioner stöder kommandot boot cdrom som helt enkelt är ett alias för att starta upp från SCSI-enheten på ID 6 (eller sekundär master för IDE-baserade system). Du kanske måste använda det faktiska enhetsnamnet för äldre OpenBoot-versioner som inte har stöd för det här speciella kommandot. Observera att vissa problem har rapporterats på Sun4m-system (alltså Sparc 10 och Sparc 20) vid uppstart från cd-rom." +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 "" +"De flesta OpenBoot-versioner stöder kommandot boot cdrom som helt enkelt är ett alias för att starta upp från SCSI-enheten " +"på ID 6 (eller sekundär master för IDE-baserade system). Du kanske måste " +"använda det faktiska enhetsnamnet för äldre OpenBoot-versioner som inte har " +"stöd för det här speciella kommandot. Observera att vissa problem har " +"rapporterats på Sun4m-system (alltså Sparc 10 och Sparc 20) vid uppstart " +"från cd-rom." #. Tag: para #: boot-installer.xml:2689 @@ -1948,31 +3516,53 @@ msgstr "De flesta OpenBoot-versioner stöder kommandot boot cdrom\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." +" 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 "" -"För att starta upp från en diskett på en Sparc, använd \n" +"För att starta upp från en diskett på en Sparc, använd " +"\n" "Stop-A -> OpenBoot: \"boot floppy\"\n" -" Tänk på att nyare Sun4u-arkitekturen (ultra) inte har stöd för uppstart på diskett. Ett typiskt felmeddelande är Bad magic number in disk label - Can't open disk label package. Vidare stöder inte ett antal Sun4c-modeller (såsom IPX) komprimerade avbilder som finns på disketter." +" Tänk på att nyare Sun4u-arkitekturen (ultra) " +"inte har stöd för uppstart på diskett. Ett typiskt felmeddelande är " +"Bad magic number in disk label - Can't open disk label " +"package. Vidare stöder inte ett antal Sun4c-modeller (såsom " +"IPX) komprimerade avbilder som finns på disketter." #. 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 "Ett flertal Sparc (exempelvis Ultra 10) har ett OBP-fel som förhindrar dem från att starta upp (istället för att inte stöda uppstart alls). Den lämpliga uppdateringen för OBP kan hämtas som produkt-id 106121 från ." +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 "" +"Ett flertal Sparc (exempelvis Ultra 10) har ett OBP-fel som förhindrar dem " +"från att starta upp (istället för att inte stöda uppstart alls). Den " +"lämpliga uppdateringen för OBP kan hämtas som produkt-id 106121 från ." #. Tag: para #: boot-installer.xml:2708 #, no-c-format msgid "" -"If you are booting from the floppy, and you see messages such as \n" +"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." +" then it is possible that floppy booting is " +"simply not supported on your machine." msgstr "" -"Om du startar upp från disketten, och du ser meddelanden såsom \n" +"Om du startar upp från disketten, och du ser meddelanden såsom " +"\n" "Fatal error: Cannot read partition\n" "Illegal or malformed device name\n" -" är det möjligt att uppstart via diskett inte stöds på din maskin." +" är det möjligt att uppstart via diskett inte " +"stöds på din maskin." #. Tag: title #: boot-installer.xml:2720 @@ -1983,50 +3573,125 @@ msgstr "IDPROM-meddelanden" #. 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 "Om du inte kan starta upp på grund av att får meddelanden om ett problem med IDPROM, är det möjligt att ditt NVRAM-batteri, som tillhandahåller konfigurationsinformation för ditt firmware, har slut på ström. Se Sun NVRAM FAQ för mer information." +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 "" +"Om du inte kan starta upp på grund av att får meddelanden om ett problem med " +"IDPROM, är det möjligt att ditt NVRAM-batteri, som " +"tillhandahåller konfigurationsinformation för ditt firmware, har slut på " +"ström. Se Sun NVRAM FAQ för mer " +"information." #. 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 "Uppstartsparametrar är parametrar för Linux-kärnan som generellt sett används för att se till att kringutrustning hanteras korrekt. För det mesta kan kärnan automatiskt identifiera information om din kringutrustning. Dock, i vissa fall, behöver du hjälpa kärnan en bit på vägen." +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 "" +"Uppstartsparametrar är parametrar för Linux-kärnan som generellt sett " +"används för att se till att kringutrustning hanteras korrekt. För det mesta " +"kan kärnan automatiskt identifiera information om din kringutrustning. Dock, " +"i vissa fall, behöver du hjälpa kärnan en bit på vägen." #. 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 "Om det här är första gången du startar upp systemet kan du prova de uppstartsparametrar som är standard (alltså, ställ inte in några parametrar) och se om det fungerar korrekt. Det kommer säkert att göra det. Om inte, kan du starta om senare och leta efter några speciella parametrar som informerar systemet om din maskinvara." +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 "" +"Om det här är första gången du startar upp systemet kan du prova de " +"uppstartsparametrar som är standard (alltså, ställ inte in några parametrar) " +"och se om det fungerar korrekt. Det kommer säkert att göra det. Om inte, kan " +"du starta om senare och leta efter några speciella parametrar som informerar " +"systemet om din maskinvara." #. 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 "Information om många uppstartsparametrar kan hittas i Linux BootPrompt HOWTO, inklusive tips för obskyr maskinvara. Det här avsnittet innehåller endast en del av de mest vanliga parametrarna. Vissa vanliga problem finns beskrivna i ." +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 "" +"Information om många uppstartsparametrar kan hittas i Linux BootPrompt HOWTO, " +"inklusive tips för obskyr maskinvara. Det här avsnittet innehåller endast en " +"del av de mest vanliga parametrarna. Vissa vanliga problem finns beskrivna i " +"." #. 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." +"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 "" "När kärnan startar upp bör meddelandet\n" -"Memory:tillgängligtk/totaltk available\n" -" visas tidigt i processen. totalt bör stämma med totalt RAM-minne i kilobyte. Om det inte stämmer med den faktiska mängden RAM-minne du har installerad behöver du använda parametern mem=ram, där ram är inställd till mängden minne och ändelsen k för kilobyte eller m för megabyte. Till exempel, både mem=65536k och mem=64m betyder 64MB RAM-minne." +"Memory:tillgängligtk/totaltk available\n" +" visas tidigt i processen. totalt bör stämma med totalt RAM-minne i kilobyte. Om det inte stämmer " +"med den faktiska mängden RAM-minne du har installerad behöver du använda " +"parametern mem=ram, där " +"ram är inställd till mängden minne och ändelsen " +"k för kilobyte eller m för megabyte. Till " +"exempel, både mem=65536k och mem=64m betyder 64MB RAM-minne." #. 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 "Om du startar upp på en seriekonsoll kommer generellt sett kärnan att autodetektera det (dock inte på DECstation). Om du har ett grafikkort (framebuffer) och ett tangentbord anslutet till datorn som du önskar starta upp via seriekonsoll, kan du skicka med följande argument console=enhet till kärnan, där enhet är din serieenhet, som vanligtvis är något liknande ttyS0." +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 "" +"Om du startar upp på en seriekonsoll kommer generellt sett kärnan att " +"autodetektera det (dock inte på DECstation). Om du har ett grafikkort (framebuffer) och ett tangentbord anslutet " +"till datorn som du önskar starta upp via seriekonsoll, kan du skicka med " +"följande argument console=enhet till kärnan, där enhet är din " +"serieenhet, som vanligtvis är något liknande ttyS0." #. 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 "För &arch-title; heter serieenheterna ttya eller ttyb. Alternativt, ställ in OpenPROM-variablerna input-device och output-device till ttya." +msgid "" +"For &arch-title; the serial devices are ttya or " +"ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " +"ttya." +msgstr "" +"För &arch-title; heter serieenheterna ttya eller " +"ttyb. Alternativt, ställ in OpenPROM-variablerna " +"input-device och output-device till " +"ttya." #. Tag: title #: boot-installer.xml:2803 @@ -2037,8 +3702,17 @@ msgstr "Parametrar för Debian Installer" #. Tag: para #: boot-installer.xml:2804 #, no-c-format -msgid "The installation system recognizes a few additional boot parameters With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. which may be useful." -msgstr "Installationssystemet känner igen ytterligare ett antal uppstartsparametrar Med aktuella kärnor (2.6.9 eller senare) kan du använda 32 kommandoradsflaggor och 32 miljöflaggor. Om dessa tal överstigs, kommer kärnan att få panik. som kan vara användbara." +msgid "" +"The installation system recognizes a few additional boot " +"parameters With current kernels (2.6.9 or newer) you can " +"use 32 command line options and 32 environment options. If these numbers are " +"exceeded, the kernel will panic. which may be useful." +msgstr "" +"Installationssystemet känner igen ytterligare ett antal " +"uppstartsparametrar Med aktuella kärnor (2.6.9 eller " +"senare) kan du använda 32 kommandoradsflaggor och 32 miljöflaggor. Om dessa " +"tal överstigs, kommer kärnan att få panik. som kan vara " +"användbara." #. Tag: term #: boot-installer.xml:2821 @@ -2049,20 +3723,47 @@ msgstr "debconf/priority" #. Tag: para #: boot-installer.xml:2822 #, no-c-format -msgid "This parameter sets the lowest priority of messages to be displayed. Short form: priority" -msgstr "Den här parametern ställer in så att meddelanden med lägst prioritet visas. Kort form: priority" +msgid "" +"This parameter sets the lowest priority of messages to be displayed. Short " +"form: priority" +msgstr "" +"Den här parametern ställer in så att meddelanden med lägst prioritet visas. " +"Kort form: priority" #. Tag: para #: boot-installer.xml:2827 #, 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 "Standardinstallationen använder priority=high. Det betyder att både meddelanden med prioriteterna hög och kritisk visas, men meddelanden med prioriteterna medium och låg hoppas över. Om problem påträffas justerar installeraren prioriteten efter behov." +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 "" +"Standardinstallationen använder priority=high. Det " +"betyder att både meddelanden med prioriteterna hög och kritisk visas, men " +"meddelanden med prioriteterna medium och låg hoppas över. Om problem " +"påträffas justerar installeraren prioriteten efter behov." #. Tag: para #: boot-installer.xml:2834 #, 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 "Om du lägger till priority=medium som uppstartsparameter kommer du att få se installationsmenyn och få mer kontroll över installationen. När priority=low används kommer alla meddelanden visas (det här är likvärdigt med uppstartsmetoden expert). Med priority=critical kommer installationssystemet endast att visa kritiska meddelanden och försöka göra det rätta utan att krångla till det." +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 "" +"Om du lägger till priority=medium som " +"uppstartsparameter kommer du att få se installationsmenyn och få mer " +"kontroll över installationen. När priority=low " +"används kommer alla meddelanden visas (det här är likvärdigt med " +"uppstartsmetoden expert). Med " +"priority=critical kommer installationssystemet endast " +"att visa kritiska meddelanden och försöka göra det rätta utan att krångla " +"till det." #. Tag: term #: boot-installer.xml:2848 @@ -2073,8 +3774,43 @@ msgstr "DEBIAN_FRONTEND" #. Tag: para #: boot-installer.xml:2849 #, 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 "Den här uppstartsparametern kontrollerar den typ av användargränssnitt som används för installeraren. De för närvarande möjliga parametervärdena är: DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=slang DEBIAN_FRONTEND=ncurses DEBIAN_FRONTEND=bogl DEBIAN_FRONTEND=gtk DEBIAN_FRONTEND=corba Standardgränssnitt är DEBIAN_FRONTEND=newt. DEBIAN_FRONTEND=text kan föredras för installationer via seriekonsoll. Generellt sett är endast gränssnittet newt tillgängligt på standardinstallationsmedia så den här parametern är inte så användbar just nu." +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 "" +"Den här uppstartsparametern kontrollerar den typ av användargränssnitt som " +"används för installeraren. De för närvarande möjliga parametervärdena är: " +" DEBIAN_FRONTEND=noninteractive " +"DEBIAN_FRONTEND=text DEBIAN_FRONTEND=newt " +" DEBIAN_FRONTEND=slang DEBIAN_FRONTEND=ncurses " +"DEBIAN_FRONTEND=bogl DEBIAN_FRONTEND=gtk " +" DEBIAN_FRONTEND=corba Standardgränssnitt är " +"DEBIAN_FRONTEND=newt. " +"DEBIAN_FRONTEND=text kan föredras för installationer " +"via seriekonsoll. Generellt sett är endast gränssnittet newt tillgängligt på standardinstallationsmedia så den här parametern " +"är inte så användbar just nu." #. Tag: term #: boot-installer.xml:2885 @@ -2085,8 +3821,16 @@ msgstr "BOOT_DEBUG" #. Tag: para #: boot-installer.xml:2886 #, 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 "Ställ in den här uppstartsparametern till 2 innebär att installerarens uppstartsprocess kommer att loggas på ett informativt sätt. Ställ in den till 3 och felsökningsloggar blir tillgängliga på strategiska punkter i uppstartsprocessen. (Avsluta skalen för att fortsätta uppstartsprocessen.)" +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 "" +"Ställ in den här uppstartsparametern till 2 innebär att installerarens " +"uppstartsprocess kommer att loggas på ett informativt sätt. Ställ in den " +"till 3 och felsökningsloggar blir tillgängliga på strategiska punkter i " +"uppstartsprocessen. (Avsluta skalen för att fortsätta uppstartsprocessen.)" #. Tag: userinput #: boot-installer.xml:2895 @@ -2133,8 +3877,12 @@ msgstr "BOOT_DEBUG=3" #. Tag: para #: boot-installer.xml:2911 #, 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 "Skal kommer att köras på olika punkter i uppstartsprocessen för detaljerad felsökning. Avsluta skalet för att fortsätta uppstarten." +msgid "" +"Shells are run at various points in the boot process to allow detailed " +"debugging. Exit the shell to continue the boot." +msgstr "" +"Skal kommer att köras på olika punkter i uppstartsprocessen för detaljerad " +"felsökning. Avsluta skalet för att fortsätta uppstarten." #. Tag: term #: boot-installer.xml:2925 @@ -2145,14 +3893,25 @@ msgstr "INSTALL_MEDIA_DEV" #. Tag: para #: boot-installer.xml:2926 #, 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 "Värdet för parametern är sökvägen till enheten som Debian Installer ska läsas in från. Till exempel, INSTALL_MEDIA_DEV=/dev/floppy/0" +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 "" +"Värdet för parametern är sökvägen till enheten som Debian Installer ska " +"läsas in från. Till exempel, INSTALL_MEDIA_DEV=/dev/floppy/0" #. Tag: para #: boot-installer.xml:2932 #, 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 "Startdisketten, som normalt sett söker av alla disketter den kan hitta efter rotdisketten, kan åsidosättas av den här parametern för att endast söka på en enhet." +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 "" +"Startdisketten, som normalt sett söker av alla disketter den kan hitta efter " +"rotdisketten, kan åsidosättas av den här parametern för att endast söka på " +"en enhet." #. Tag: term #: boot-installer.xml:2942 @@ -2164,14 +3923,33 @@ msgstr "debian-installer/framebuffer" #. Tag: para #: boot-installer.xml:2943 #, 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 "Vissa arkitekturer använder kärnans framebuffer för att erbjuda en installation på ett antal olika språk. Om framebuffer orsakar ett problem på ditt system kan du inaktivera funktionen genom parametern debian-installer/framebuffer=false eller fb=false i kort form. Symptom på problemet är felmeddelanden om bterm eller bogl, en blank skärm, eller en frysning inom ett par minuter efter påbörjad installation." +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 "" +"Vissa arkitekturer använder kärnans framebuffer för att erbjuda en " +"installation på ett antal olika språk. Om framebuffer orsakar ett problem på " +"ditt system kan du inaktivera funktionen genom parametern debian-" +"installer/framebuffer=false eller fb=false i kort form. Symptom på problemet är felmeddelanden om bterm " +"eller bogl, en blank skärm, eller en frysning inom ett par minuter efter " +"påbörjad installation." #. Tag: para #: boot-installer.xml:2953 #, 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 "Argumentet video=vga16:off kan också användas för att inaktivera kärnans användning av framebuffer. Sådana problem har rapporterats på en Dell Inspiron med Mobile Radeon-kort." +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 "" +"Argumentet video=vga16:off kan också användas för att " +"inaktivera kärnans användning av framebuffer. Sådana problem har " +"rapporterats på en Dell Inspiron med Mobile Radeon-kort." #. Tag: para #: boot-installer.xml:2959 @@ -2188,8 +3966,20 @@ msgstr "Liknande problem har blivit rapporterats för hppa." #. Tag: para #: boot-installer.xml:2967 #, 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 "På grund av displayproblem på vissa system är stöd för framebuffer inaktiverat som standard för &arch-title;. Det kan resultera i en mindre vacker display på system som korrekt sett har stöd för framebuffer, såsom de med ATI-grafikkort. Om du upplever displayproblem i installeraren kan du försöka att starta upp med parametern debian-installer/framebuffer=true eller fb=true." +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 "" +"På grund av displayproblem på vissa system är stöd för framebuffer " +"inaktiverat som standard för &arch-title;. Det kan " +"resultera i en mindre vacker display på system som korrekt sett har stöd för " +"framebuffer, såsom de med ATI-grafikkort. Om du upplever displayproblem i " +"installeraren kan du försöka att starta upp med parametern debian-" +"installer/framebuffer=true eller fb=true." #. Tag: term #: boot-installer.xml:2981 @@ -2200,8 +3990,21 @@ msgstr "debian-installer/theme" #. Tag: para #: boot-installer.xml:2982 #, 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 "Ett tema bestämmer hur användargränssnittet för installeraren ser ut (färger, ikoner, etc). Vilka teman som finns tillgängliga beror på gränssnittet. För närvarande har endast gränssnitten newt och gtk ett mörkt tema som blev designat för användare med nedsatt syn. Ställ in temat genom att starta upp med parametern debian-installer/theme=dark eller theme=dark." +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 "" +"Ett tema bestämmer hur användargränssnittet för installeraren ser ut " +"(färger, ikoner, etc). Vilka teman som finns tillgängliga beror på " +"gränssnittet. För närvarande har endast gränssnitten newt och gtk ett " +"mörkt tema som blev designat för användare med nedsatt syn. " +"Ställ in temat genom att starta upp med parametern debian-" +"installer/theme=dark eller " +"theme=dark." #. Tag: term #: boot-installer.xml:2995 @@ -2212,8 +4015,12 @@ msgstr "debian-installer/probe/usb" #. Tag: para #: boot-installer.xml:2996 #, no-c-format -msgid "Set to false to prevent probing for USB on boot, if that causes problems." -msgstr "Ställ in till false för att förhindra sökning efter USB vid uppstart, om det orsakar problem." +msgid "" +"Set to false to prevent probing for USB on boot, if " +"that causes problems." +msgstr "" +"Ställ in till false för att förhindra sökning efter " +"USB vid uppstart, om det orsakar problem." #. Tag: term #: boot-installer.xml:3005 @@ -2224,14 +4031,30 @@ msgstr "netcfg/disable_dhcp" #. Tag: para #: boot-installer.xml:3006 #, 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 "Som standard söker &d-i; automatiskt efter nätverkskonfiguration via DHCP. Om sökningen lyckas, har du ingen chans att granska och ändra de mottagna inställningarna. Du kan komma åt de manuellt inställningarna endast om DHCP-sökningen misslyckas." +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 "" +"Som standard söker &d-i; automatiskt efter nätverkskonfiguration via DHCP. " +"Om sökningen lyckas, har du ingen chans att granska och ändra de mottagna " +"inställningarna. Du kan komma åt de manuellt inställningarna endast om DHCP-" +"sökningen misslyckas." #. Tag: para #: boot-installer.xml:3013 #, 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 "Om du har en DHCP-server på ditt lokala nätverk men du vill undvika den på grund av att den, exempelvis ger fel svar, kan du använda parametern netcfg/disable_dhcp=true för att förhindra att nätverket konfigureras med DHCP och att informationen matas in manuellt." +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 "" +"Om du har en DHCP-server på ditt lokala nätverk men du vill undvika den på " +"grund av att den, exempelvis ger fel svar, kan du använda parametern " +"netcfg/disable_dhcp=true för att förhindra att " +"nätverket konfigureras med DHCP och att informationen matas in manuellt." #. Tag: term #: boot-installer.xml:3024 @@ -2242,8 +4065,13 @@ msgstr "hw-detect/start_pcmcia" #. Tag: para #: boot-installer.xml:3025 #, 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 "Ställ in till false för att förhindra att PCMCIA-tjänster startas, om det orsakar problem. Vissa bärbara datorer är kända för det här problemet." +msgid "" +"Set to false to prevent starting PCMCIA services, if " +"that causes problems. Some laptops are well known for this misbehavior." +msgstr "" +"Ställ in till false för att förhindra att PCMCIA-" +"tjänster startas, om det orsakar problem. Vissa bärbara datorer är kända för " +"det här problemet." #. Tag: term #: boot-installer.xml:3035 @@ -2254,8 +4082,14 @@ msgstr "preseed/url" #. Tag: para #: boot-installer.xml:3036 #, no-c-format -msgid "Specify the url to a preconfiguration file to download and use in automating the install. See . Short form: url" -msgstr "Ange URL:en till en förkonfigurationsfil att hämta och användas för att automatisera installationen. Se . Kort form: url" +msgid "" +"Specify the url to a preconfiguration file to download and use in automating " +"the install. See . Short form: " +"url" +msgstr "" +"Ange URL:en till en förkonfigurationsfil att hämta och användas för att " +"automatisera installationen. Se . Kort " +"form: url" #. Tag: term #: boot-installer.xml:3046 @@ -2266,8 +4100,14 @@ msgstr "preseed/file" #. Tag: para #: boot-installer.xml:3047 #, no-c-format -msgid "Specify the path to a preconfiguration file to load to automating the install. See . Short form: file" -msgstr "Ange sökvägen till en förkonfigurationsfil att läsa in för att automatisera installationen. Se . Kort form: file" +msgid "" +"Specify the path to a preconfiguration file to load to automating the " +"install. See . Short form: " +"file" +msgstr "" +"Ange sökvägen till en förkonfigurationsfil att läsa in för att automatisera " +"installationen. Se . Kort form: " +"file" #. Tag: term #: boot-installer.xml:3057 @@ -2278,8 +4118,16 @@ msgstr "auto-install/enabled" #. Tag: para #: boot-installer.xml:3058 #, no-c-format -msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. Short form: auto=true See for details about using this to automate installs." -msgstr "Fördröj frågor som vanligtvis frågas innan förinställning är möjlig efter att nätverket har konfigurerats. Kort form: auto=true Se för detaljer om hur man använder det här för att automatisera installationer." +msgid "" +"Delay questions that are normally asked before preseeding is possible until " +"after the network is configured. Short form: auto=true See for details about using this " +"to automate installs." +msgstr "" +"Fördröj frågor som vanligtvis frågas innan förinställning är möjlig efter " +"att nätverket har konfigurerats. Kort form: auto=true " +"Se för detaljer om hur man använder det här " +"för att automatisera installationer." #. Tag: term #: boot-installer.xml:3069 @@ -2290,14 +4138,32 @@ msgstr "cdrom-detect/eject" #. Tag: para #: boot-installer.xml:3070 #, 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 "Som standard, före omstart, matar &d-i; automatiskt ut det optiska mediat som användes under installationen. Det kan vara onödigt om systemet inte startar upp automatiskt på cd. I vissa fall kan det inte vara önskvärt, till exempel om den optiska enheten inte kan mata in mediat själv om användaren inte finns där för att göra det manuellt. Många cd-läsare kan inte mata in media automatiskt." +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 "" +"Som standard, före omstart, matar &d-i; automatiskt ut det optiska mediat " +"som användes under installationen. Det kan vara onödigt om systemet inte " +"startar upp automatiskt på cd. I vissa fall kan det inte vara önskvärt, till " +"exempel om den optiska enheten inte kan mata in mediat själv om användaren " +"inte finns där för att göra det manuellt. Många cd-läsare kan inte mata in " +"media automatiskt." #. Tag: para #: boot-installer.xml:3079 #, 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 "Ställ in till false för att inaktivera automatisk utmatning och tänk på att du kan behöva se till att systemet inte startar upp automatiskt från den optiska enheten efter den initiala installationen." +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 "" +"Ställ in till false för att inaktivera automatisk " +"utmatning och tänk på att du kan behöva se till att systemet inte startar " +"upp automatiskt från den optiska enheten efter den initiala installationen." #. Tag: term #: boot-installer.xml:3090 @@ -2309,7 +4175,8 @@ msgstr "ramdisk_size" #: boot-installer.xml:3091 #, no-c-format msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." -msgstr "Om du använder en 2.2.x-kärna, kan du behöva att ställa in &ramdisksize;." +msgstr "" +"Om du använder en 2.2.x-kärna, kan du behöva att ställa in &ramdisksize;." #. Tag: term #: boot-installer.xml:3099 @@ -2320,8 +4187,15 @@ msgstr "directfb/hw-accel" #. Tag: para #: boot-installer.xml:3100 #, 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 "Hårdvaruaccelerering för gtk-gränssnittet (grafiska installeraren) i directfb är inaktiverat som standard. Ställ in den här parametern till true när installeraren startar upp för att aktivera det." +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 "" +"Hårdvaruaccelerering för gtk-gränssnittet (grafiska installeraren) i " +"directfb är inaktiverat som standard. Ställ in den här parametern till " +"true när installeraren startar upp för att aktivera " +"det." #. Tag: term #: boot-installer.xml:3110 @@ -2332,8 +4206,13 @@ msgstr "rescue/enable" #. Tag: para #: boot-installer.xml:3111 #, no-c-format -msgid "Set to true to enter rescue mode rather than performing a normal installation. See ." -msgstr "Ställ in till true för att gå in i räddningsläget istället för att genomföra en normal installation. Se ." +msgid "" +"Set to true to enter rescue mode rather than " +"performing a normal installation. See ." +msgstr "" +"Ställ in till true för att gå in i räddningsläget " +"istället för att genomföra en normal installation. Se ." #. Tag: title #: boot-installer.xml:3122 @@ -2344,26 +4223,63 @@ msgstr "Skicka parametrar till kärnmoduler" #. Tag: para #: boot-installer.xml:3123 #, no-c-format -msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system." -msgstr "Om drivrutiner är kompilerade in i kärnan kan du skicka parametrar till dem som beskrivs i dokumentationen för kärnan. Dock om drivrutinerna är byggda som moduler och därför att kärnmoduler läses in lite annorlunda under en installation än vid uppstart av ett installerat system, är det inte möjligt att skicka parametrar till moduler kan samma sätt som du normalt gör. Istället behöver du använda en speciell syntax som känns igen av installeraren som ser till att parametrarna sparas i de korrekta konfigurationsfilerna och på så sätt kommer att användas när modulerna faktiskt läses in. Parametrarna kommer även att propageras automatiskt till konfigurationen för det installerade systemet." +msgid "" +"If drivers are compiled into the kernel, you can pass parameters to them as " +"described in the kernel documentation. However, if drivers are compiled as " +"modules and because kernel modules are loaded a bit differently during an " +"installation than when booting an installed system, it is not possible to " +"pass parameters to modules as you would normally do. Instead, you need to " +"use a special syntax recognized by the installer which will then make sure " +"that the parameters are saved in the proper configuration files and will " +"thus be used when the modules are actually loaded. The parameters will also " +"be propagated automatically to the configuration for the installed system." +msgstr "" +"Om drivrutiner är kompilerade in i kärnan kan du skicka parametrar till dem " +"som beskrivs i dokumentationen för kärnan. Dock om drivrutinerna är byggda " +"som moduler och därför att kärnmoduler läses in lite annorlunda under en " +"installation än vid uppstart av ett installerat system, är det inte möjligt " +"att skicka parametrar till moduler kan samma sätt som du normalt gör. " +"Istället behöver du använda en speciell syntax som känns igen av " +"installeraren som ser till att parametrarna sparas i de korrekta " +"konfigurationsfilerna och på så sätt kommer att användas när modulerna " +"faktiskt läses in. Parametrarna kommer även att propageras automatiskt till " +"konfigurationen för det installerade systemet." #. Tag: para #: boot-installer.xml:3136 #, no-c-format -msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually." -msgstr "Observera att det är nuförtiden ganska ovanligt att parametrar behöver skickas till moduler. I de flesta fall kommer kärnan att söka av befintlig hårdvara i ett system och ställa in bra standardvärden på det sättet. Dock, i vissa fall, kan det fortfarande krävas att parametrar ställs in manuellt." +msgid "" +"Note that it is now quite rare that parameters need to be passed to modules. " +"In most cases the kernel will be able to probe the hardware present in a " +"system and set good defaults that way. However, in some situations it may " +"still be needed to set parameters manually." +msgstr "" +"Observera att det är nuförtiden ganska ovanligt att parametrar behöver " +"skickas till moduler. I de flesta fall kommer kärnan att söka av befintlig " +"hårdvara i ett system och ställa in bra standardvärden på det sättet. Dock, " +"i vissa fall, kan det fortfarande krävas att parametrar ställs in manuellt." #. Tag: para #: boot-installer.xml:3143 #, no-c-format msgid "" -"The syntax to use to set parameters for modules is: \n" -"module_name.parameter_name=value\n" -" If you need to pass multiple parameters to the same or different modules, just repeat this. For example, to set an old 3Com network interface card to use the BNC (coax) connector and IRQ 10, you would pass:" +"The syntax to use to set parameters for modules is: " +"\n" +"module_name.parameter_name=value\n" +" If you need to pass multiple parameters to the " +"same or different modules, just repeat this. For example, to set an old 3Com " +"network interface card to use the BNC (coax) connector and IRQ 10, you would " +"pass:" msgstr "" -"Syntaxen att använda för att ställa in parametrar för moduler är: \n" -"modulnamn.parameternamn=värde\n" -" Om du behöver skicka flera parametrar till samma eller olika moduler är det bara att upprepa detta. Till exempel, för att ställa in ett gammalt 3Com-nätverkskort till att använda BNC-kontakten (coax) och IRQ 10, skulle du skicka:" +"Syntaxen att använda för att ställa in parametrar för moduler är: " +"\n" +"modulnamn.parameternamn=värde\n" +" Om du behöver skicka flera parametrar till samma " +"eller olika moduler är det bara att upprepa detta. Till exempel, för att " +"ställa in ett gammalt 3Com-nätverkskort till att använda BNC-kontakten " +"(coax) och IRQ 10, skulle du skicka:" #. Tag: screen #: boot-installer.xml:3153 @@ -2386,14 +4302,28 @@ msgstr "Tillförlitlighet för cd-rom" #. Tag: para #: boot-installer.xml:3171 #, no-c-format -msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also — even after booting successfully from CD-ROM — fail to recognize the CD-ROM or return errors while reading from it during the installation." -msgstr "Ibland, speciellt med äldre cd-rom-enhet, kan installeraren misslyckas att starta upp från en cd-skiva. Installeraren kan även — även efter en lyckad uppstart från cd-skiva — misslyckas att känna igen cd-rom-enheten eller svara med fel vid läsning från den under installationen." +msgid "" +"Sometimes, especially with older CD-ROM drives, the installer may fail to " +"boot from a CD-ROM. The installer may also — even after booting " +"successfully from CD-ROM — fail to recognize the CD-ROM or return " +"errors while reading from it during the installation." +msgstr "" +"Ibland, speciellt med äldre cd-rom-enhet, kan installeraren misslyckas att " +"starta upp från en cd-skiva. Installeraren kan även — även efter en " +"lyckad uppstart från cd-skiva — misslyckas att känna igen cd-rom-" +"enheten eller svara med fel vid läsning från den under installationen." #. Tag: para #: boot-installer.xml:3178 #, no-c-format -msgid "There are a many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you." -msgstr "Det finns många olika möjliga orsaker till dessa problem. Vi kan endast lista några vanliga problem och tillhandahålla allmänna förslag på hur man hanterar dem. Resten är upp till dig." +msgid "" +"There are a many different possible causes for these problems. We can only " +"list some common issues and provide general suggestions on how to deal with " +"them. The rest is up to you." +msgstr "" +"Det finns många olika möjliga orsaker till dessa problem. Vi kan endast " +"lista några vanliga problem och tillhandahålla allmänna förslag på hur man " +"hanterar dem. Resten är upp till dig." #. Tag: para #: boot-installer.xml:3184 @@ -2404,26 +4334,48 @@ msgstr "Det finns två mycket enkla saker som du bör prova först." #. Tag: para #: boot-installer.xml:3189 #, no-c-format -msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty." -msgstr "Om cd-skivan inte startar upp, kontrollera att den blev inmatad korrekt och att den inte är smutsig." +msgid "" +"If the CD-ROM does not boot, check that it was inserted correctly and that " +"it is not dirty." +msgstr "" +"Om cd-skivan inte startar upp, kontrollera att den blev inmatad korrekt och " +"att den inte är smutsig." #. Tag: para #: boot-installer.xml:3195 #, no-c-format -msgid "If the installer fails to recognize a CD-ROM, try just running the option Detect and mount CD-ROM a second time. Some DMA related isses with older CD-ROM drives are known to be resolved in this way." -msgstr "Om installeraren misslyckas att känna igen en cd-rom, prova att köra alternativet Identifiera och montera cd-rom en andra gång. Vissa DMA-relaterade problem med äldre cd-rom-enheter kan lösas på detta sätt." +msgid "" +"If the installer fails to recognize a CD-ROM, try just running the option " +" Detect and mount CD-ROM a second time. Some DMA related isses with older CD-ROM drives " +"are known to be resolved in this way." +msgstr "" +"Om installeraren misslyckas att känna igen en cd-rom, prova att köra " +"alternativet Identifiera och montera cd-rom en andra gång. Vissa DMA-relaterade problem med " +"äldre cd-rom-enheter kan lösas på detta sätt." #. Tag: para #: boot-installer.xml:3205 #, no-c-format -msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity." -msgstr "Om det inte fungerar, prova nedanstående förslag. De flesta, men inte alla, förslag som diskuteras där gäller för både cd-rom och dvd, men vi använder termen cd-rom för enkelhet." +msgid "" +"If this does not work, then try the suggestions in the subsections below. " +"Most, but not all, suggestions discussed there are valid for both CD-ROM and " +"DVD, but we'll use the term CD-ROM for simplicity." +msgstr "" +"Om det inte fungerar, prova nedanstående förslag. De flesta, men inte alla, " +"förslag som diskuteras där gäller för både cd-rom och dvd, men vi använder " +"termen cd-rom för enkelhet." #. Tag: para #: boot-installer.xml:3211 #, no-c-format -msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available." -msgstr "Om du inte kan få installationen att fungera från cd-rom, prova en av de andra installationsmetoderna som finns tillgängliga." +msgid "" +"If you cannot get the installation working from CD-ROM, try one of the other " +"installation methods that are available." +msgstr "" +"Om du inte kan få installationen att fungera från cd-rom, prova en av de " +"andra installationsmetoderna som finns tillgängliga." #. Tag: title #: boot-installer.xml:3219 @@ -2434,20 +4386,34 @@ msgstr "Vanliga problem" #. Tag: para #: boot-installer.xml:3222 #, no-c-format -msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer." -msgstr "Några äldre cd-rom-enheter saknar stöd för att läsa från skivor som blev brända med höga hastigheter med en modern cd-brännare." +msgid "" +"Some older CD-ROM drives do not support reading from discs that were burned " +"at high speeds using a modern CD writer." +msgstr "" +"Några äldre cd-rom-enheter saknar stöd för att läsa från skivor som blev " +"brända med höga hastigheter med en modern cd-brännare." #. Tag: para #: boot-installer.xml:3228 #, no-c-format -msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)." -msgstr "Om ditt system startar upp korrekt från cd-rom, betyder inte det alltid att Linux även har stöd för cd-enheten (eller, mer korrekt, kontrollern som din cd-rom-enhet är ansluten till)." +msgid "" +"If your system boots correctly from the CD-ROM, it does not necessarily mean " +"that Linux also supports the CD-ROM (or, more correctly, the controller that " +"your CD-ROM drive is connected to)." +msgstr "" +"Om ditt system startar upp korrekt från cd-rom, betyder inte det alltid att " +"Linux även har stöd för cd-enheten (eller, mer korrekt, kontrollern som din " +"cd-rom-enhet är ansluten till)." #. Tag: para #: boot-installer.xml:3235 #, no-c-format -msgid "Some older CD-ROM drives do not work correctly if direct memory access (DMA) is enabled." -msgstr "Några äldre cd-rom-enheter fungerar inte korrekt om direkt minnesåtkomst (DMA) är aktiverat." +msgid "" +"Some older CD-ROM drives do not work correctly if direct memory " +"access (DMA) is enabled." +msgstr "" +"Några äldre cd-rom-enheter fungerar inte korrekt om direkt " +"minnesåtkomst (DMA) är aktiverat." #. Tag: title #: boot-installer.xml:3246 @@ -2459,34 +4425,53 @@ msgstr "Hur man undersöker och kanske även löser problem" #: boot-installer.xml:3247 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." -msgstr "Prova förslagen som listas här nedan om uppstart med cd-rom misslyckas." +msgstr "" +"Prova förslagen som listas här nedan om uppstart med cd-rom misslyckas." #. Tag: para #: boot-installer.xml:3252 #, no-c-format -msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using." -msgstr "Kontrollera att ditt BIOS faktiskt har stöd för uppstart från cd-rom (äldre system har inte alltid det) och att din cd-rom-enhet har stöd för det media som du använder." +msgid "" +"Check that your BIOS actually supports booting from CD-ROM (older systems " +"possibly don't) and that your CD-ROM drive supports the media you are using." +msgstr "" +"Kontrollera att ditt BIOS faktiskt har stöd för uppstart från cd-rom (äldre " +"system har inte alltid det) och att din cd-rom-enhet har stöd för det media " +"som du använder." #. Tag: para #: boot-installer.xml:3258 #, no-c-format msgid "" -"If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the MD5SUMS file that should be present in the same location as where you downloaded the image from. \n" +"If you downloaded an iso image, check that the md5sum of that image matches " +"the one listed for the image in the MD5SUMS file that " +"should be present in the same location as where you downloaded the image " +"from. \n" "$ md5sum debian-testing-i386-netinst.iso\n" -"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst.iso\n" -" Next, check that the md5sum of the burned CD-ROM matches as well. The following command should work. It uses the size of the image to read the correct number of bytes from the CD-ROM." +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Next, check that the md5sum of the burned CD-ROM " +"matches as well. The following command should work. It uses the size of the " +"image to read the correct number of bytes from the CD-ROM." msgstr "" -"Om du hämtat en iso-avbild, kontrollera att md5-kontrollsumman för avbilder matchar den som listas för avbilden i filen MD5SUMS som bör finnas på samma plats som där du hämtade avbilden från. \n" +"Om du hämtat en iso-avbild, kontrollera att md5-kontrollsumman för avbilder " +"matchar den som listas för avbilden i filen MD5SUMS som " +"bör finnas på samma plats som där du hämtade avbilden från. " +"\n" "$ md5sum debian-testing-i386-netinst.iso\n" -"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst.iso\n" -" Kontrollera sedan att md5-kontrollsumman för den brända cd-skivan matchar också. Följande kommando bör fungera. Det använder storleken på avbilden för att läsa det korrekta antalet byte från cd-skivan." +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Kontrollera sedan att md5-kontrollsumman för den " +"brända cd-skivan matchar också. Följande kommando bör fungera. Det använder " +"storleken på avbilden för att läsa det korrekta antalet byte från cd-skivan." #. Tag: screen #: boot-installer.xml:3271 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" -"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" "> md5sum\n" "a20391b12f7ff22ef705cee4059c6b92 -\n" "262668+0 records in\n" @@ -2494,7 +4479,8 @@ msgid "" "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" msgstr "" "$ dd if=/dev/cdrom | \\\n" -"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" "> md5sum\n" "a20391b12f7ff22ef705cee4059c6b92 -\n" "262668+0 poster in\n" @@ -2504,52 +4490,94 @@ msgstr "" #. Tag: para #: boot-installer.xml:3276 #, no-c-format -msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there." -msgstr "Om, efter att installeraren har startat upp korrekt, identifieras inte cd-rom-enheten, kan ibland ett nytt försök lösa problemet. Om du har fler än en cd-rom-enhet, prova att byta cd-rom-enheten till den andra enheten. Om det inte fungerar eller om cd-rom-enheten identifieras men det uppstod fel vid läsningen från den, prova förslagen som listas nedan. Viss grundläggande kunskap om Linux krävs för det här. För att köra något av kommandona, bör du först växla till den andra virtuella konsollen (VT2) och aktivera skalet där." +msgid "" +"If, after the installer has been booted successfully, the CD-ROM is not " +"detected, sometimes simply trying again may solve the problem. If you have " +"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If " +"that does not work or if the CD-ROM is recognized but there are errors when " +"reading from it, try the suggestions listed below. Some basic knowledge of " +"Linux is required for this. To execute any of the commands, you should first " +"switch to the second virtual console (VT2) and activate the shell there." +msgstr "" +"Om, efter att installeraren har startat upp korrekt, identifieras inte cd-" +"rom-enheten, kan ibland ett nytt försök lösa problemet. Om du har fler än en " +"cd-rom-enhet, prova att byta cd-rom-enheten till den andra enheten. Om det " +"inte fungerar eller om cd-rom-enheten identifieras men det uppstod fel vid " +"läsningen från den, prova förslagen som listas nedan. Viss grundläggande " +"kunskap om Linux krävs för det här. För att köra något av kommandona, bör du " +"först växla till den andra virtuella konsollen (VT2) och aktivera skalet där." #. Tag: para #: boot-installer.xml:3288 #, no-c-format -msgid "Switch to VT4 or view the contents of /var/log/syslog (use nano as editor) to check for any specific error messages. After that, also check the output of dmesg." -msgstr "Växla till VT4 eller visa innehållet i /var/log/syslog (använd nano som redigerare) för att leta efter specifika felmeddelenden. Efter det, kontrollera även utskriften för dmesg." +msgid "" +"Switch to VT4 or view the contents of /var/log/syslog " +"(use nano as editor) to check for any specific error " +"messages. After that, also check the output of dmesg." +msgstr "" +"Växla till VT4 eller visa innehållet i /var/log/syslog " +"(använd nano som redigerare) för att leta efter specifika " +"felmeddelenden. Efter det, kontrollera även utskriften för dmesg." #. Tag: para #: boot-installer.xml:3295 #, no-c-format msgid "" -"Check in the output of dmesg if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): \n" +"Check in the output of dmesg if your CD-ROM drive was " +"recognized. You should see something like (the lines do not necessarily have " +"to be consecutive): \n" "Probing IDE interface ide1...\n" "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" "ide1 at 0x170-0x177,0x376 on irq 15\n" "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" "Uniform CD-ROM driver Revision: 3.20\n" -" If you don't see something like that, chances are the controller your CD-ROM is connected to was not recognized or may be not supported at all. If you know what driver is needed for the drive, you can try loading it manually using modprobe." +" If you don't see something like that, chances " +"are the controller your CD-ROM is connected to was not recognized or may be " +"not supported at all. If you know what driver is needed for the drive, you " +"can try loading it manually using modprobe." msgstr "" -"Leta i utskriften från dmesg om din cd-rom-enhet identifierades. Du bör se någonting som liknar (raderna behöver inte nödvändigtvis vara lika): \n" +"Leta i utskriften från dmesg om din cd-rom-enhet " +"identifierades. Du bör se någonting som liknar (raderna behöver inte " +"nödvändigtvis vara lika): \n" "Probing IDE interface ide1...\n" "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" "ide1 at 0x170-0x177,0x376 on irq 15\n" "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" "Uniform CD-ROM driver Revision: 3.20\n" -" Om du inte ser någonting som liknar det här, är chansen att din kontroller, som din cd-rom är ansluten till, inte känns igen eller inte stöds alls. Om du vet vilken drivrutin som behövs för enheten, kan du prova att läsa in den manuellt med modprobe." +" Om du inte ser någonting som liknar det här, är " +"chansen att din kontroller, som din cd-rom är ansluten till, inte känns igen " +"eller inte stöds alls. Om du vet vilken drivrutin som behövs för enheten, " +"kan du prova att läsa in den manuellt med modprobe." #. Tag: para #: boot-installer.xml:3309 #, no-c-format -msgid "Check that there is a device node for your CD-ROM drive under /dev/. In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." -msgstr "Kontrollera att det finns en enhetsnod för din cd-rom-enhet under /dev/. I ovanstående exempel skulle detta vara /dev/hdc. Det bör även finnas en /dev/cdroms/cdrom0." +msgid "" +"Check that there is a device node for your CD-ROM drive under /dev/" +". In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." +msgstr "" +"Kontrollera att det finns en enhetsnod för din cd-rom-enhet under /" +"dev/. I ovanstående exempel skulle detta vara /dev/hdc. Det bör även finnas en /dev/cdroms/cdrom0." #. Tag: para #: boot-installer.xml:3317 #, no-c-format msgid "" -"Use the mount command to check if the CD-ROM is already mounted; if not, try mounting it manually: \n" +"Use the mount command to check if the CD-ROM is already " +"mounted; if not, try mounting it manually: \n" "$ mount /dev/hdc /cdrom\n" -" Check if there are any error messages after that command." +" Check if there are any error messages after that " +"command." msgstr "" -"Använd kommandot mount för att kontrollera att din cd-rom redan är monterad, om inte, försök att montera den manuellt: \n" +"Använd kommandot mount för att kontrollera att din cd-rom " +"redan är monterad, om inte, försök att montera den manuellt: " +"\n" "$ mount /dev/hdc /cdrom\n" -" Kontrollera om det uppstod felmeddelanden efter körning av kommandot." +" Kontrollera om det uppstod felmeddelanden efter " +"körning av kommandot." #. Tag: para #: boot-installer.xml:3327 @@ -2559,23 +4587,35 @@ msgid "" "$ cd /proc/ide/hdc\n" "$ grep dma settings\n" "using_dma 1 0 1 rw\n" -" A 1 means it is enabled. If it is, try disabling it: \n" +" A 1 means it is enabled. If it " +"is, try disabling it: \n" "$ echo -n \"using_dma:0\" >settings\n" -" Make sure that you are in the directory for the device that corresponds to your CD-ROM drive." +" Make sure that you are in the directory for the " +"device that corresponds to your CD-ROM drive." msgstr "" "Kontrollera om DMA för närvarande är aktiverad: \n" "$ cd /proc/ide/hdc\n" "$ grep dma settings\n" "using_dma 1 0 1 rw\n" -" En 1 betyder att det är aktiverat. Om det är, försök att inaktivera det: \n" +" En 1 betyder att det är " +"aktiverat. Om det är, försök att inaktivera det: \n" "$ echo -n \"using_dma:0\" >settings\n" -" Se till att du är i katalogen för enheten som motsvarar din cd-rom-enhet." +" Se till att du är i katalogen för enheten som " +"motsvarar din cd-rom-enhet." #. Tag: para #: boot-installer.xml:3341 #, no-c-format -msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably." -msgstr "Om det uppstår problem under installationen, prova att kontrollera integriteten för cd-skivan med alternativen nära slutet på installerarens huvudmeny. Det här alternativet kan även användas som ett allmänt test för att se om cd-skivan kan läsas tillförlitligt." +msgid "" +"If there are any problems during the installation, try checking the " +"integrity of the CD-ROM using the option near the bottom of the installer's " +"main menu. This option can also be used as a general test if the CD-ROM can " +"be read reliably." +msgstr "" +"Om det uppstår problem under installationen, prova att kontrollera " +"integriteten för cd-skivan med alternativen nära slutet på installerarens " +"huvudmeny. Det här alternativet kan även användas som ett allmänt test för " +"att se om cd-skivan kan läsas tillförlitligt." #. Tag: title #: boot-installer.xml:3356 @@ -2586,38 +4626,84 @@ msgstr "Tillförlitlighet för disketter" #. Tag: para #: boot-installer.xml:3358 #, no-c-format -msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." -msgstr "Det största problemet för personer som använder disketter för att installera Debian verkar vara pålitligheten för disketterna." +msgid "" +"The biggest problem for people using floppy disks to install Debian seems to " +"be floppy disk reliability." +msgstr "" +"Det största problemet för personer som använder disketter för att installera " +"Debian verkar vara pålitligheten för disketterna." #. Tag: para #: boot-installer.xml:3363 -#, 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 "Startdisketten är den diskett med värsta problemen på grund av att den läses av maskinvaran direkt, före Linux startar upp. Ofta läser maskinvaran inte så tillförlitligt som Linux egna drivrutin för diskettenheten och kan bara stoppa upp utan att skriva ut något felmeddelande om den läser felaktig data. Det kan också bli fel i drivrutinsdisketterna som visar sig som massor av meddelanden om disk in/ut-fel." +#, fuzzy, 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 "" +"Startdisketten är den diskett med värsta problemen på grund av att den läses " +"av maskinvaran direkt, före Linux startar upp. Ofta läser maskinvaran inte " +"så tillförlitligt som Linux egna drivrutin för diskettenheten och kan bara " +"stoppa upp utan att skriva ut något felmeddelande om den läser felaktig " +"data. Det kan också bli fel i drivrutinsdisketterna som visar sig som massor " +"av meddelanden om disk in/ut-fel." #. Tag: para #: boot-installer.xml:3372 -#, no-c-format -msgid "If you are having the installation stall at a particular floppy, the first thing you should 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 "Om du får installationen att stanna upp på en speciell diskett, är den första saken du bör göra är att skriva den till en annan diskett. Formatera helt enkelt om en gammal diskett kanske inte räcker, även om det verkar som om disketten var omformaterad och skrevs utan fel. Det kan ibland vara användbart att prova skriva att disketten på ett annat system." +#, fuzzy, no-c-format +msgid "" +"If you are having the installation stall at a particular floppy, the first " +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. Simply reformatting the old " +"floppy may not be sufficient, even if it appears that the floppy was " +"reformatted and written with no errors. It is sometimes useful to try " +"writing the floppy on a different system." +msgstr "" +"Om du får installationen att stanna upp på en speciell diskett, är den " +"första saken du bör göra är att skriva den till en annan diskett. Formatera helt enkelt om en gammal diskett kanske inte " +"räcker, även om det verkar som om disketten var omformaterad och skrevs utan " +"fel. Det kan ibland vara användbart att prova skriva att disketten på ett " +"annat system." #. Tag: para #: boot-installer.xml:3381 #, no-c-format -msgid "Normally you should not have download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums." -msgstr "Vanligtvis behöver du inte hämta ner diskettavbilden igen, men om du upplever problem är det alltid bra att validera att avbilderna som hämtades är korrekta genom att verifiera deras md5-kontrollsummor." +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 "" +"En användare rapporterar att han måste skriva avbilderna till disketten " +"tre gånger före en fungerade och sedan var allt bra med " +"den tredje disketten." #. Tag: para #: boot-installer.xml:3387 -#, 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 "En användare rapporterar att han måste skriva avbilderna till disketten tre gånger före en fungerade och sedan var allt bra med den tredje disketten." +#, fuzzy, no-c-format +msgid "" +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." +msgstr "" +"Vanligtvis behöver du inte hämta ner diskettavbilden igen, men om du " +"upplever problem är det alltid bra att validera att avbilderna som hämtades " +"är korrekta genom att verifiera deras md5-kontrollsummor." #. Tag: para #: boot-installer.xml:3393 #, 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 "Andra användare har rapporterat att helt enkelt starta om ett par gånger med samma diskett i diskettenheten kan leda till en lyckad uppstart. Det är på grund av felaktig maskinvara eller drivrutinen för diskettenheten i firmware." +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 "" +"Andra användare har rapporterat att helt enkelt starta om ett par gånger med " +"samma diskett i diskettenheten kan leda till en lyckad uppstart. Det är på " +"grund av felaktig maskinvara eller drivrutinen för diskettenheten i firmware." #. Tag: title #: boot-installer.xml:3402 @@ -2628,26 +4714,54 @@ msgstr "Uppstartskonfiguration" #. Tag: para #: boot-installer.xml:3404 #, 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 "Om du har problem och kärnan hänger sig under uppstartsprocessen, inte känner igen kringutrustning som du faktiskt har, eller enheter som inte korrekt känns igen är uppstartsparametrarna den första saken att kontrollera, det diskuteras i ." +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 "" +"Om du har problem och kärnan hänger sig under uppstartsprocessen, inte " +"känner igen kringutrustning som du faktiskt har, eller enheter som inte " +"korrekt känns igen är uppstartsparametrarna den första saken att " +"kontrollera, det diskuteras i ." #. Tag: para #: boot-installer.xml:3411 #, 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 "Om du startar upp med din egna kärna istället för den som skickas med installeraren, se till att CONFIG_DEVFS är inställd i din kärna. Installeraren kräver CONFIG_DEVFS." +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 "" +"Om du startar upp med din egna kärna istället för den som skickas med " +"installeraren, se till att CONFIG_DEVFS är inställd i " +"din kärna. Installeraren kräver CONFIG_DEVFS." #. Tag: para #: boot-installer.xml:3418 #, 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 "Ofta kan problemen lösas genom att ta bort tillägg och kringutrustning och sedan försöka starta upp igen. Interna modem, ljudkort och enheter med plug-n-play kan vara speciellt problematiska." +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 "" +"Ofta kan problemen lösas genom att ta bort tillägg och kringutrustning och " +"sedan försöka starta upp igen. Interna modem, ljudkort " +"och enheter med plug-n-play kan vara speciellt problematiska." #. Tag: para #: boot-installer.xml:3424 #, 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 "Om du har en stor mängd minne installerad i din maskin, mer än 512MB, och installeraren hänger sig när kärnan startar upp, kan du behöva inkludera ett uppstartsargument för att begränsa mängden minne som kärnan ser, såsom mem=512m." +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 "" +"Om du har en stor mängd minne installerad i din maskin, mer än 512MB, och " +"installeraren hänger sig när kärnan startar upp, kan du behöva inkludera ett " +"uppstartsargument för att begränsa mängden minne som kärnan ser, såsom " +"mem=512m." #. Tag: title #: boot-installer.xml:3435 @@ -2658,32 +4772,78 @@ msgstr "Vanliga installationsproblem på &arch-title;" #. Tag: para #: boot-installer.xml:3436 #, 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 "Det finns några vanliga installationsproblem som kan lösas eller undvikas genom att skicka med vissa uppstartsparametrar till installeraren." +msgid "" +"There are some common installation problems that can be solved or avoided by " +"passing certain boot parameters to the installer." +msgstr "" +"Det finns några vanliga installationsproblem som kan lösas eller undvikas " +"genom att skicka med vissa uppstartsparametrar till installeraren." #. Tag: para #: boot-installer.xml:3441 #, 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 "Vissa system har disketter med omvänd DCL. Om du upptäcker fel vid inläsning från disketten även om disketten är bra, prova med parametern floppy=thinkpad." +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 "" +"Vissa system har disketter med omvänd DCL. Om du upptäcker " +"fel vid inläsning från disketten även om disketten är bra, prova med " +"parametern floppy=thinkpad." #. Tag: para #: boot-installer.xml:3447 #, 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 "På vissa system, såsom IBM PS/1 eller ValuePoint (som har ST-506-hårddiskar), kanske IDE-disken inte kan identifieras korrekt. Igen, prova den först utan parametrar och se om IDE-disken identifieras korrekt. Om inte, ta reda på geometrin för din hårddisk (cylindrar, huvuden och sektorer), och använd parametern hd=cylindrar,huvuden,sektorer." +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 "" +"På vissa system, såsom IBM PS/1 eller ValuePoint (som har ST-506-" +"hårddiskar), kanske IDE-disken inte kan identifieras korrekt. Igen, prova " +"den först utan parametrar och se om IDE-disken identifieras korrekt. Om " +"inte, ta reda på geometrin för din hårddisk (cylindrar, huvuden och " +"sektorer), och använd parametern hd=cylindrar,huvuden,sektorer." #. Tag: para #: boot-installer.xml:3456 #, 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 "Om du har en mycket gammal maskin, och kärnan hänger sig efter den sagt Checking 'hlt' instruction..., så ska du prova uppstartsargumentet no-hlt, som inaktiverar det här testet." +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 "" +"Om du har en mycket gammal maskin, och kärnan hänger sig efter den sagt " +"Checking 'hlt' instruction..., så ska du " +"prova uppstartsargumentet no-hlt, som inaktiverar det " +"här testet." #. Tag: para #: boot-installer.xml:3463 #, 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 "Om din skärm börjar visa en konstig bild vid uppstart av kärnan, exempelvis vitt, svart eller färgat pixelskräp, kan ditt system innehålla ett problematiskt grafikkort som inte kan byta till framebuffer-läget korrekt. Då kan du använda uppstartsparametern fb=false video=vga16:off för att inaktivera framebuffer-konsollen. Endast det engelska språket kommer att vara tillgängligt under installationen på grund av begränsade konsollfunktioner. Se för detaljer." +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 "" +"Om din skärm börjar visa en konstig bild vid uppstart av kärnan, exempelvis " +"vitt, svart eller färgat pixelskräp, kan ditt system innehålla ett " +"problematiskt grafikkort som inte kan byta till framebuffer-läget korrekt. " +"Då kan du använda uppstartsparametern fb=false video=vga16:off för att inaktivera framebuffer-konsollen. Endast det engelska " +"språket kommer att vara tillgängligt under installationen på grund av " +"begränsade konsollfunktioner. Se för detaljer." #. Tag: title #: boot-installer.xml:3477 @@ -2694,14 +4854,46 @@ msgstr "Systemet fryser under konfigurationsfasen för PCMCIA" #. Tag: para #: boot-installer.xml:3478 #, 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 "Vissa modeller av bärbara datorer producerade av Dell är kända att krascha när identifiering av PCMCIA-enheter försöker komma åt vissa maskinvaruadresser. Andra bärbara kan visa liknande problem. Om du upplever sådana problem och du inte behöver PCMCIA-stöd under installationen kan du inaktivera PCMCIA med uppstartsparametern hw-detect/start_pcmcia=false. Du kan då konfigurera PCMCIA efter installationen är genomförd och undanta resursintervallet som orsakar problemen." +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 "" +"Vissa modeller av bärbara datorer producerade av Dell är kända att krascha " +"när identifiering av PCMCIA-enheter försöker komma åt vissa " +"maskinvaruadresser. Andra bärbara kan visa liknande problem. Om du upplever " +"sådana problem och du inte behöver PCMCIA-stöd under installationen kan du " +"inaktivera PCMCIA med uppstartsparametern hw-detect/" +"start_pcmcia=false. Du kan då konfigurera PCMCIA efter " +"installationen är genomförd och undanta resursintervallet som orsakar " +"problemen." #. Tag: para #: boot-installer.xml:3488 #, 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 "Alternativt kan du starta upp installeraren i expertläget. Du kommer då att bli frågad att ange inställningar för resursintervall som din maskinvara behöver. Till exempel, om du har en av Dells bärbara datorer som nämndes ovan, bör du ange exclude port 0x800-0x8ff här. Det finns också en lista på några vanliga resursintervall i System resource settings section of the PCMCIA HOWTO. Observera att du måste ta bort eventuella kommatecken när du anger det här värdet i installeraren." +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 "" +"Alternativt kan du starta upp installeraren i expertläget. Du kommer då att " +"bli frågad att ange inställningar för resursintervall som din maskinvara " +"behöver. Till exempel, om du har en av Dells bärbara datorer som nämndes " +"ovan, bör du ange exclude port 0x800-0x8ff här. Det " +"finns också en lista på några vanliga resursintervall i System " +"resource settings section of the PCMCIA HOWTO. Observera att du " +"måste ta bort eventuella kommatecken när du anger det här värdet i " +"installeraren." #. Tag: title #: boot-installer.xml:3505 @@ -2712,8 +4904,23 @@ msgstr "Systemet fryser vid inläsning av USB-moduler" #. Tag: para #: boot-installer.xml:3506 #, 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 "Kärnan försöker normalt sett att installera USB-moduler och drivrutinen för USB-tangentbord för att ge stöd för icke-standardiserade USB-tangentbord. Dock, det finns några trasiga USB-system där drivrutinen hänger sig vid inläsning. Ett möjligt sätt att komma runt problemet är att inaktivera USB-kontrollern i BIOS-inställningen på ditt moderkort. Ett annat alternativ är att skicka med parametern debian-installer/probe/usb=false vid uppstartsprompten, som kommer att förhindra att modulerna läses in." +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 "" +"Kärnan försöker normalt sett att installera USB-moduler och drivrutinen för " +"USB-tangentbord för att ge stöd för icke-standardiserade USB-tangentbord. " +"Dock, det finns några trasiga USB-system där drivrutinen hänger sig vid " +"inläsning. Ett möjligt sätt att komma runt problemet är att inaktivera USB-" +"kontrollern i BIOS-inställningen på ditt moderkort. Ett annat alternativ är " +"att skicka med parametern debian-installer/probe/usb=false vid uppstartsprompten, som kommer att förhindra att modulerna " +"läses in." #. Tag: title #: boot-installer.xml:3520 @@ -2724,8 +4931,39 @@ msgstr "Tolkning av kärnans uppstartsmeddelanden" #. Tag: para #: boot-installer.xml:3522 #, 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 "Under uppstartssekvensen kan du se många meddelanden i formen can't find någonting , eller någonting not present, can't initialize någonting , eller till och med this driver release depends on någonting . De flesta av de här meddelandena är harmlösa. Du ser dem för att kärnan för installationssystemet är byggd för att köras på datorer med många olika kringutrustningsenheter. Så klart, ingen dator kommer att ha alla möjliga kringutrustningsenheter, så operativsystemet kan klaga en hel del när den letar efter kringutrustning som du inte har. Du kan också se att systemet pausar en stund. Det händer när det väntar på att en enhet ska svara, och den enheten finns inte på ditt system. Om du tycker att tiden det tar att starta upp systemet är på tok för lång, kan du skapa en anpassad kärna senare (se )." +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 "" +"Under uppstartssekvensen kan du se många meddelanden i formen " +"can't find någonting , eller någonting " +"not present, can't initialize " +"någonting , eller till och med " +"this driver release depends on någonting . De flesta av de här meddelandena är " +"harmlösa. Du ser dem för att kärnan för installationssystemet är byggd för " +"att köras på datorer med många olika kringutrustningsenheter. Så klart, " +"ingen dator kommer att ha alla möjliga kringutrustningsenheter, så " +"operativsystemet kan klaga en hel del när den letar efter kringutrustning " +"som du inte har. Du kan också se att systemet pausar en stund. Det händer " +"när det väntar på att en enhet ska svara, och den enheten finns inte på " +"ditt system. Om du tycker att tiden det tar att starta upp systemet är på " +"tok för lång, kan du skapa en anpassad kärna senare (se )." #. Tag: title #: boot-installer.xml:3547 @@ -2736,14 +4974,33 @@ msgstr "Felrapporterare" #. Tag: para #: boot-installer.xml:3548 #, 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 "Om du kommer igenom den initiala uppstartsfasen men inte kan färdigställa installationen, kan menyvalet för felrapportering vara till hjälp. Den låter dig lagra felloggar från systemet och information om konfigurationen från installeraren till en diskett, eller hämta dem i en webbläsare. Den informationen kan innehålla ledtrådar till vad som gick fel och hur man löser det. Om du skickar in en felrapport kan du bifoga den här informationen i felrapporten." +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 "" +"Om du kommer igenom den initiala uppstartsfasen men inte kan färdigställa " +"installationen, kan menyvalet för felrapportering vara till hjälp. Den låter " +"dig lagra felloggar från systemet och information om konfigurationen från " +"installeraren till en diskett, eller hämta dem i en webbläsare. Den " +"informationen kan innehålla ledtrådar till vad som gick fel och hur man " +"löser det. Om du skickar in en felrapport kan du bifoga den här " +"informationen i felrapporten." #. Tag: para #: boot-installer.xml:3559 #, 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 "Andra relevanta installationsmeddelanden kan hittas i /var/log/ under installationen, och /var/log/installer/ efter datorn har startats om till det nyligen installerade systemet." +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 "" +"Andra relevanta installationsmeddelanden kan hittas i /var/log/ under installationen, och /var/log/installer/ " +"efter datorn har startats om till det nyligen installerade systemet." #. Tag: title #: boot-installer.xml:3570 @@ -2754,20 +5011,39 @@ msgstr "Skicka installationsrapporter" #. Tag: para #: boot-installer.xml:3571 #, 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 "Om du fortfarande har problem, skicka in en installationsrapport. Vi uppmuntrar att installationsrapporter skickas in även om installationen lyckats, så att vi kan få så mycket information som möjligt på flest antal olika maskinvarukonfigurationer." +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 "" +"Om du fortfarande har problem, skicka in en installationsrapport. Vi " +"uppmuntrar att installationsrapporter skickas in även om installationen " +"lyckats, så att vi kan få så mycket information som möjligt på flest antal " +"olika maskinvarukonfigurationer." #. Tag: para #: boot-installer.xml:3578 #, 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 "Om du har ett fungerande Debian-system är det enklaste sättet att skicka in en installationsrapport att installera paketen installation-report och reportbug (apt-get install installation-report reportbug) och kör kommandot reportbug installation-report." +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 "" +"Om du har ett fungerande Debian-system är det enklaste sättet att skicka in " +"en installationsrapport att installera paketen installation-report och " +"reportbug (apt-get install installation-report reportbug) " +"och kör kommandot reportbug installation-report." #. Tag: para #: boot-installer.xml:3585 #, 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" +"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" @@ -2802,12 +5078,19 @@ msgid "" "\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." +" 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 "" -"Använd den här mallen när du fyller i installationsrapporter och skicka sedan rapporten som en felrapport mot pseudopaketet installation-reports, genom att skicka det till submit@bugs.debian.org (skriv på engelska). \n" +"Använd den här mallen när du fyller i installationsrapporter och skicka " +"sedan rapporten som en felrapport mot pseudopaketet installation-" +"reports, genom att skicka det till submit@bugs.debian." +"org (skriv på engelska). \n" "Package: installation-reports\n" "\n" -"Boot method: <Hur startade du upp installeraren? Cd? Diskett? Nätverk?>\n" +"Boot method: <Hur startade du upp installeraren? Cd? Diskett? Nätverk?" +">\n" "Image version: <Fullständig url till avbilden du hämtade är bäst>\n" "Date: <Datum och tid för installationen>\n" "\n" @@ -2837,9 +5120,12 @@ msgstr "" "\n" "Comments/Problems:\n" "\n" -"<Beskrivning av installationen, i prosa, och eventuella tankar, kommentarer\n" +"<Beskrivning av installationen, i prosa, och eventuella tankar, " +"kommentarer\n" " och idéer du hade under installationen.>\n" -" Beskriv i felrapporten vad problemet var, inklusive de sista meddelandena från kärnan om problemet var att kärnan hängde sig. Beskriv de steg du tog som slutade i att systemet fick problem." +" Beskriv i felrapporten vad problemet var, " +"inklusive de sista meddelandena från kärnan om problemet var att kärnan " +"hängde sig. Beskriv de steg du tog som slutade i att systemet fick problem." #~ msgid "" #~ "In case your computer doesn't support booting from USB memory devices, " @@ -2855,10 +5141,12 @@ msgstr "" #~ "; kärnan på startdisketten ska automatiskt " #~ "identifiera ditt USB-minne. När den frågar efter rotdisketten, tryck bara " #~ "&enterkey;. Du bör nu se &d-i; starta." + #~ msgid "nettrom-2.3-3.armv4l.rpm" #~ msgstr "nettrom-2.3-3.armv4l.rpm" + #~ msgid "nettrom-2.3.3.bin" #~ msgstr "nettrom-2.3.3.bin" + #~ msgid "nettrom-2.3.3.bin.md5sum" #~ msgstr "nettrom-2.3.3.bin.md5sum" - diff --git a/po/vi/boot-installer.po b/po/vi/boot-installer.po index b3a786143..c520fb170 100644 --- a/po/vi/boot-installer.po +++ b/po/vi/boot-installer.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: boot-installer\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-11-04 17:26+0000\n" +"POT-Creation-Date: 2006-11-10 03:17+0000\n" "PO-Revision-Date: 2006-10-21 18:05+0930\n" "Last-Translator: Clytie Siddall \n" "Language-Team: Vietnamese \n" @@ -4584,13 +4584,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:3363 -#, no-c-format +#, fuzzy, 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 " +"failures in the driver floppies, most of which indicate themselves with a " "flood of messages about disk I/O errors." msgstr "" "Đĩa mềm khởi động là đĩa mềm có vấn đề nghiêm trọng nhất, vì nó do phần cứng " @@ -4605,10 +4605,11 @@ msgstr "" #, fuzzy, no-c-format msgid "" "If you are having the installation stall at a particular floppy, the first " -"thing you should 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." +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. Simply reformatting the old " +"floppy may not be sufficient, even if it appears that the floppy was " +"reformatted and written with no errors. It is sometimes useful to try " +"writing the floppy on a different system." msgstr "" "Nếu bạn thấy tiến trình cài đặt bị ngừng chạy tại một đĩa mềm riêng, trước " "tiên bạn nên tải về lại ảnh đĩa mềm đó và ghi nó vào một đĩa mềm " @@ -4620,15 +4621,6 @@ msgstr "" #: boot-installer.xml:3381 #, no-c-format msgid "" -"Normally you should not have download a floppy image again, but if you are " -"experiencing problems it is always useful to verify that the images were " -"downloaded correctly by verifying their md5sums." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3387 -#, 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." @@ -4637,6 +4629,15 @@ msgstr "" "mềm ba lần trước khi gặp một đĩa mềm hoạt động được, " "còn sau đó, mọi thứ thì tốt với đĩa mềm thứ ba." +#. Tag: para +#: boot-installer.xml:3387 +#, no-c-format +msgid "" +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." +msgstr "" + #. Tag: para #: boot-installer.xml:3393 #, no-c-format diff --git a/po/zh_CN/boot-installer.po b/po/zh_CN/boot-installer.po index 28a2615a0..5b7f8966d 100644 --- a/po/zh_CN/boot-installer.po +++ b/po/zh_CN/boot-installer.po @@ -3,7 +3,7 @@ msgid "" msgstr "" "Project-Id-Version: d-i-manual\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-11-04 17:26+0000\n" +"POT-Creation-Date: 2006-11-10 03:17+0000\n" "PO-Revision-Date: 2006-11-01 09:46+0800\n" "Last-Translator: Ji YongGang\n" "Language-Team: debian-chinese-gb \n" @@ -4266,13 +4266,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:3363 -#, no-c-format +#, fuzzy, 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 " +"failures in the driver floppies, most of which indicate themselves with a " "flood of messages about disk I/O errors." msgstr "" "问题出现最严重的是糟糕的引导软盘，因为他们由硬件直接读出，然后才进入 Linux 引" @@ -4282,13 +4282,14 @@ msgstr "" #. Tag: para #: boot-installer.xml:3372 -#, no-c-format +#, fuzzy, no-c-format msgid "" "If you are having the installation stall at a particular floppy, the first " -"thing you should 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." +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. Simply reformatting the old " +"floppy may not be sufficient, even if it appears that the floppy was " +"reformatted and written with no errors. It is sometimes useful to try " +"writing the floppy on a different system." msgstr "" "如果您在某个软盘上遇到安装问题，首先要做的，是把它重新写到另外一张软盘上。仅仅只是格式化老的软盘是不够的，即使它在重新格式化以后看" @@ -4298,17 +4299,6 @@ msgstr "" #: boot-installer.xml:3381 #, no-c-format msgid "" -"Normally you should not have download a floppy image again, but if you are " -"experiencing problems it is always useful to verify that the images were " -"downloaded correctly by verifying their md5sums." -msgstr "" -"一般情况下，您不必再下载一次软盘映像，但如果总有问题，可以通过确认 md5sum 来" -"检验下载的映像是否正确。" - -#. Tag: para -#: boot-installer.xml:3387 -#, 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." @@ -4316,6 +4306,17 @@ msgstr "" "一个用户报告过他不得不把映像往软盘写三次，只有最后一次的" "软盘才算工作良好。" +#. Tag: para +#: boot-installer.xml:3387 +#, fuzzy, no-c-format +msgid "" +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." +msgstr "" +"一般情况下，您不必再下载一次软盘映像，但如果总有问题，可以通过确认 md5sum 来" +"检验下载的映像是否正确。" + #. Tag: para #: boot-installer.xml:3393 #, no-c-format diff --git a/po/zh_TW/boot-installer.po b/po/zh_TW/boot-installer.po index f1725518b..5f93c291a 100644 --- a/po/zh_TW/boot-installer.po +++ b/po/zh_TW/boot-installer.po @@ -3,7 +3,7 @@ msgid "" msgstr "" "Project-Id-Version: d-i-manual\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-11-04 17:26+0000\n" +"POT-Creation-Date: 2006-11-10 03:17+0000\n" "PO-Revision-Date: 2005-07-18 14:56+0800\n" "Last-Translator: Jhang, Jia-Wei\n" "Language-Team: debian-chinese-big5 \n" @@ -4134,13 +4134,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:3363 -#, no-c-format +#, fuzzy, 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 " +"failures in the driver floppies, most of which indicate themselves with a " "flood of messages about disk I/O errors." msgstr "" "問題出現最嚴重的是糟糕的開機軟碟，因為他們由硬體直接讀出，然後才進入 Linux 開" @@ -4153,10 +4153,11 @@ msgstr "" #, fuzzy, no-c-format msgid "" "If you are having the installation stall at a particular floppy, the first " -"thing you should 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." +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. Simply reformatting the old " +"floppy may not be sufficient, even if it appears that the floppy was " +"reformatted and written with no errors. It is sometimes useful to try " +"writing the floppy on a different system." msgstr "" "如果您在特定的軟碟上遇到麻煩，第一件要做的事情，是重新下載磁碟映像並且把它寫" "到另外一張軟碟上。僅僅只是格式化老的軟碟是不夠的，有可能" @@ -4166,21 +4167,21 @@ msgstr "" #: boot-installer.xml:3381 #, no-c-format msgid "" -"Normally you should not have download a floppy image again, but if you are " -"experiencing problems it is always useful to verify that the images were " -"downloaded correctly by verifying their md5sums." +"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 "" +"一個使用者曾報告他不得不把映像往軟碟寫了三次，直到第四次" +"軟碟才算工作良好。" #. Tag: para #: boot-installer.xml:3387 #, 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." +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." msgstr "" -"一個使用者曾報告他不得不把映像往軟碟寫了三次，直到第四次" -"軟碟才算工作良好。" #. Tag: para #: boot-installer.xml:3393 -- cgit v1.2.3