# Danish translation of boot-installer. # Copyright (C) 2018 Free Software Foundation, Inc. # Joe Hansen , 2012, 2014, 2015, 2016, 2017, 2018. # # 32-bit processorer (er anvendt selv om 32-bit-processorer er den korrekte brug) # cipher -> krypteringsalgoritme # howto -> manual # language -> sprog # locale -> sted (lokalitet andet?) # locales -> steder (sprogområder) # scheme -> plan # stateful -> tilstandebærende # stateless -> tilstandsfri # volume -> diskenhed # msgid "" msgstr "" "Project-Id-Version: boot-installer\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2021-04-14 23:02+0000\n" "PO-Revision-Date: 2021-06-07 19:32+0000\n" "Last-Translator: Joe Hansen \n" "Language-Team: Danish \n" "Language: da\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Generator: Weblate 4.7-dev\n" #. Tag: title #: boot-installer.xml:4 #, no-c-format msgid "Booting the Installation System" msgstr "Opstart af installationssystemet" #. Tag: title #: boot-installer.xml:9 #, no-c-format msgid "Booting the Installer on &arch-title;" msgstr "Opstart af installationsprogrammet på &arch-title;" #. Tag: para #: boot-installer.xml:15 #, no-c-format msgid "" "If you have any other operating systems on your system that you wish to keep " "(dual boot setup), you should make sure that they have been properly shut " "down before you boot the installer. Installing an " "operating system while another operating system is in hibernation (has been " "suspended to disk) could result in loss of, or damage to the state of the " "suspended operating system which could cause problems when it is rebooted." msgstr "" "Hvis du har andre operativsystemer på din computer, som du ønsker at beholde " "(via en opstartsmenu), bør du sikre dig, at de er lukket ned på korrekt måde " "inden du starter installationsprogrammet. Installation " "af et operativsystem mens et andet operativsystem er i dvale (er blevet " "suspenderet til disk) kan medføre tab af, eller skade på tilstanden af " "operativsystemet i dvale, hvilket kan medføre problemer når det bliver " "genstartet." #. Tag: para #: boot-installer.xml:26 #, no-c-format msgid "" "For information on how to boot the graphical installer, see ." msgstr "" "For information om hvordan man starter det grafiske installationsprogram, så " "se ." #. Tag: title #: boot-installer.xml:39 #, no-c-format msgid "Boot image formats" msgstr "Formater for opstartsaftryk" #. Tag: para #: boot-installer.xml:40 #, no-c-format msgid "" "On ARM-based systems in most cases one of two formats for boot images is " "used: a) standard Linux zImage-format kernels (vmlinuz) in " "conjunction with standard Linux initial ramdisks (initrd.gz) " "or b) uImage-format kernels (uImage) in conjunction with " "corresponding initial ramdisks (uInitrd)." msgstr "" "På ARM-baserede systemer bruges i de fleste tilfælde et af to formater for " "opstartsaftryk: a) gængse Linux zImage-formatkerner (vmlinuz) " "i samarbejde med gængse Linux initial-ramdisk (initrd.gz) " "eller b) uImage-formatkerner (uImage) i samarbejde med " "tilsvarende initial ramdisk (uInitrd)." #. Tag: para #: boot-installer.xml:48 #, no-c-format msgid "" "uImage/uInitrd are image formats designed for the U-Boot firmware that is " "used on many ARM-based systems (mostly 32-bit ones). Older U-Boot versions " "can only boot files in uImage/uInitrd format, so these are often used on " "older armel systems. Newer U-Boot versions can - besides booting uImages/" "uInitrds - also boot standard Linux kernels and ramdisk images, but the " "command syntax to do that is slightly different from that for booting " "uImages." msgstr "" "uImage/uInitrd er aftryksformater designet for firmwaren U-Boot, som bruges " "på mange ARM-baserede systemer (hovedsagelig 32-bit). Ældre versioner af U-" "Boot kan kun opstarte filer i uImage/uInitrd-formatet, så de bruges ofte på " "ældre armel-systemer. Nyere versioner af U-Boot kan - udover opstarte " "uImages/uInitrds - også opstarte standardkerner med Linux og ramdisk-aftryk, " "men kommandosyntaksen til dette er en smule anderledes end at starte fra " "uImages." #. Tag: para #: boot-installer.xml:57 #, no-c-format msgid "" "For systems using a multiplatform kernel, besides kernel and initial ramdisk " "a so-called device-tree file (or device-tree blob, dtb) is " "needed. It is specific to each supported system and contains a description " "of the particular hardware. The dtb should be supplied on the device by the " "firmware, but in practice a newer one often needs to be loaded." msgstr "" "For systemer der bruger en kerne for flere platforme, udover kerne og " "initiel ramdisk, er en såkaldt enhedstræfil krævet (eller enhedstræ blob, " "dtb). Den er specifik for hvert understøttet system og " "indeholder en beskrivelse af det specifikke udstyr. Dtb'en skal angives på " "enheden af firmwaren, men i praksis skal en ny ofte indlæses." #. Tag: title #: boot-installer.xml:68 boot-installer.xml:86 #, no-c-format msgid "Console configuration" msgstr "Konsolkonfiguration" #. Tag: para #: boot-installer.xml:69 #, no-c-format msgid "" "The netboot tarball (), and the " "installer SD-card images () use " "the (platform-specific) default console that is defined by U-Boot in the " "console variable. In most cases that is a serial console, so " "on those platforms you by default need a serial console cable to use the " "installer." msgstr "" "Netboot tarball (), og " "installationsaftrykket for SD-kort () bruger standardkonsollen (platformspecifik), som er defineret af U-" "Boot i variablen console. I de fleste tilfælde er det en " "seriel konsol, så på de fleste platforme skal du som standard brug et " "serielt konsolkabel for at bruge installationsprogrammet." #. Tag: para #: boot-installer.xml:78 #, no-c-format msgid "" "On platforms which also support a video console, you can modify the U-Boot " "console variable accordingly if you would like the installer " "to start on the video console." msgstr "" "På platforme som også understøtter en videokonsol, så kan du ændre U-Boot " "variablen console tilsvarende, hvis du ønsker, at " "installationsprogrammet skal starte på videokonsollen." #. Tag: para #: boot-installer.xml:87 #, no-c-format msgid "" "The graphical installer is not enabled on the arm64 &d-i; images for stretch " "so the serial console is used. The console device should be detected " "automatically from the firmware, but if it is not then after you boot linux " "from the GRUB menu you will see a Booting Linux message, then " "nothing more." msgstr "" "Det grafiske installationsprogram er ikke aktiveret på arm64 &d-i;-aftryk " "for stretch så den serielle konsol anvendes. Konsolenheden bør blive " "registreret automatisk fra firmwaren, men hvis den ikke gør det så vil du " "efter, at du starter op i Linux fra GRUB-menuen se en Booting Linux-besked, og så intet andet." #. Tag: para #: boot-installer.xml:94 #, no-c-format msgid "" "If you hit this issue you will need to set a specific console config on the " "kernel command line. Hit e for Edit Kernel " "command-line at the GRUB menu, and change " "--- quiet to " "console=<device>,<speed> e.g. console=ttyAMA0,115200n8. When finished hit Control x to continue booting with new setting." msgstr "" "Hvis du møder denne problemstilling, så skal du angive en speciel " "konsolkonfiguration på kernekommandolinjen. Tryk på e " "for Rediger kernekommandolinje i GRUB-menuen, og ændr " "--- quiet til " "console=<device>,<speed> f.eks. console=ttyAMA0,115200n8. Når færdig tryk på Control x for at forsætte opstart med den nye " "indstilling." #. Tag: title #: boot-installer.xml:108 #, no-c-format msgid "Juno Installation" msgstr "Juno-installation" #. Tag: para #: boot-installer.xml:109 #, no-c-format msgid "" "Juno has UEFI so the install is straightforward. The most practical method " "is installing from USB stick. You need up to date firmware for USB-booting " "to work. Builds from &url-juno-firmware; after March 2015 tested OK. Consult Juno documentation on firmware " "updating." msgstr "" "Juno har UEFI så installationen er ligefrem. Den mest praktiske metode er " "installation fra USB-drev. Du skal bruge en opdateret firmware for at USB-" "opstart fungerer. Bygninger fra &url-juno-" "firmware; efter marts 2015 er testet o.k. Se Juno-dokumentationen " "vedrørende firmwareopdatering." #. Tag: para #: boot-installer.xml:116 #, fuzzy, no-c-format #| msgid "" #| "Prepare a standard arm64 CD image on a USB stick. Insert it in one of the " #| "USB ports on the back. Plug a serial cable into the upper 9-pin serial " #| "port on the back. If you need networking (netboot image) plug the " #| "ethernet cable into the socket on the front of the machine." msgid "" "Prepare a standard arm64 CD/DVD image on a USB stick. Insert it in one of " "the USB ports on the back. Plug a serial cable into the upper 9-pin serial " "port on the back. If you need networking (netboot image) plug the ethernet " "cable into the socket on the front of the machine." msgstr "" "Forbered et standardaftryk fra en arm64-cd på et USB-drev. Indsæt det i en " "af USB-portene på bagsiden. Indsæt et serielt kabel i den øvre 9-stik " "serielle port på bagsiden. Hvis du skal bruge netværk (netboot-aftryk) så " "isæt ethernetkablet i soklen på fronten af maskinen." #. Tag: para #: boot-installer.xml:123 #, no-c-format msgid "" "Run a serial console at 115200, 8bit no parity, and boot the Juno. It should " "boot from the USB stick to a GRUB menu. The console config is not correctly " "detected on Juno so just hitting &enterkey; will show no kernel output. Set " "the console to console=ttyAMA0,115200n8 (as described in ). " "Control x to boot " "should show you the &d-i; screens, and allow you to proceed with a standard " "installation." msgstr "" "Kør en seriel konsol med 115200, 8-bit ingen paritet og opstart Junoen. Den " "bør starte op fra USB-drevet til en GRUB-menu. Konsolkonfigurationen bliver " "ikke korrekt registreret på Juno, så et tryk på retur vil ikke vise " "kerneuddata. Angiv konsollen som " "console=ttyAMA0,115200n8 " "som beskrevet i (). " "Control x for at " "starte op bør vise dig skærmene for &d-i; og give dig mulighed for at " "fortsætte med en standardinstallation." #. Tag: title #: boot-installer.xml:136 #, no-c-format msgid "Applied Micro Mustang Installation" msgstr "Anvendt Micro Mustand-installation" #. Tag: para #: boot-installer.xml:137 #, no-c-format msgid "" "UEFI is available for this machine but it is normally shipped with U-Boot so " "you will need to either install UEFI firmware first then use standard boot/" "install methods, or use U-Boot boot methods. You must use a serial console " "to control the installation because the graphical installer is not enabled " "on the arm64 architecture." msgstr "" "UEFI er tilgængelig for denne maskine, men den leveres normalt med U-Boot, " "så du skal enten installere UEFI-firmware først og så bruge " "standardmetoderne til opstart/installation, eller bruger U-Boot-" "opstartsmetoder. Du skal brug en seriel konsol til at kontrollere " "installationen da det grafiske installationsprogram ikke er aktiveret på " "arm64-arkitekturen." #. Tag: para #: boot-installer.xml:145 #, no-c-format msgid "" "The recommended install method is to copy the &d-i; kernel and initrd onto " "the hard drive, using the openembedded system supplied with the machine, " "then boot from that to run the installer. Alternatively use TFTP to get the " "kernel/dtb/initrd copied over and booted (). After installation, manual changes to boot from the installed image are " "needed." msgstr "" "Den anbefalede installationsmetode er at kopiere kernen for &d-i; og initrd " "på harddisken, via det »openembedded« system leveret med maskinen, og så " "starte op fra det for at afvikle installationsprogrammet. Alternativt brug " "TFTP til at få kernel/dtb/initrd kopieret over og startet op (). Efter installation er manuelle ændringer til " "opstarten fra det installerede aftryk krævet." #. Tag: para #: boot-installer.xml:154 #, no-c-format msgid "" "Run a serial console at 115200, 8bit no parity, and boot the machine. Reboot " "the machine and when you see Hit any key to stop autoboot: " "hit a key to get a Mustang# prompt. Then use U-Boot commands to load and " "boot the kernel, dtb and initrd." msgstr "" "Kør en seriel konsol på 115200, 8-bit ingen parietet og start maskinen op. " "Genstart maskinen og når du ser Hit any key to stop autoboot: " "så tryk på en tast for at hente en Mustang#-prompt. Brug så U-Boot-" "kommandoer til at indlæse og starte kernen, dtb og initrd op." #. Tag: title #: boot-installer.xml:163 #, no-c-format msgid "Booting by TFTP" msgstr "Opstart med TFTP" #. Tag: para #: boot-installer.xml:169 boot-installer.xml:729 boot-installer.xml:1366 #: boot-installer.xml:1496 boot-installer.xml:1889 #, no-c-format msgid "" "Booting from the network requires that you have a network connection and a " "TFTP network boot server (and probably also a DHCP, RARP, or BOOTP server " "for automatic network configuration)." msgstr "" "Opstart fra netværket kræver, at du har en netværksforbindelse og en TFTP-" "netværksopstartsserver (og sandsynligvis også en DHCP-, RARP- eller BOOTP-" "server for automatisk netværkskonfiguration)." #. Tag: para #: boot-installer.xml:175 boot-installer.xml:735 boot-installer.xml:1372 #: boot-installer.xml:1502 boot-installer.xml:1895 #, 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 systemer såsom 715 kan kræve brug af en RBOOT-server i stedet for en " "BOOTP-server." #. Tag: para #: boot-installer.xml:180 boot-installer.xml:740 boot-installer.xml:1377 #: boot-installer.xml:1507 boot-installer.xml:1900 #, no-c-format msgid "" "The server-side setup to support network booting is described in ." msgstr "" "Opsætningen på serversiden for understøttelse af netværksopstart er " "beskrevet i ." #. Tag: title #: boot-installer.xml:189 #, no-c-format msgid "TFTP-booting in U-Boot" msgstr "TFTP-opstart i U-Boot" #. Tag: para #: boot-installer.xml:190 #, no-c-format msgid "" "Network booting on systems using the U-Boot firmware consists of three " "steps: a) configuring the network, b) loading the images (kernel/initial " "ramdisk/dtb) into memory and c) actually executing the previosly loaded code." msgstr "" "Netværksopstart på systemer, der bruger firmwaren U-Boot, består af tre " "trin: a) konfiguration af netværket, b) indlæsning af aftrykket (kerne/" "initiel ramdisk/dtb) i hukommelsen og c) faktisk kørsel af den tidligere " "indlæste kode." #. Tag: para #: boot-installer.xml:196 #, no-c-format msgid "" "First you have to configure the network, either automatically via DHCP by " "running \n" "setenv autoload no\n" "dhcp\n" " or manually by setting several environment " "variables \n" "setenv ipaddr <ip address of the client>\n" "setenv netmask <netmask>\n" "setenv serverip <ip address of the tftp server>\n" "setenv dnsip <ip address of the nameserver>\n" "setenv gatewayip <ip address of the default gateway>\n" " If you prefer, you can make these settings " "permanent by running" msgstr "" "Først skal du konfigurere netværket, enten automatisk via DHCP ved at køre " "\n" "setenv autoload no\n" "dhcp\n" " eller manuelt ved at indstille flere " "miljøparametre \n" "setenv ipaddr <ip-adresse for klienten>\n" "setenv netmask <netmaske>\n" "setenv serverip <ip-adresse for tftp-serveren>\n" "setenv dnsip <ip-adresse for navneserveren>\n" "setenv gatewayip <ip-adresse for standardadgangspunktet>\n" " Hvis du foretrækker det kan du foretage disse " "indstillinger ved at køre" #. Tag: screen #: boot-installer.xml:203 #, no-c-format msgid "saveenv" msgstr "saveenv" #. Tag: para #: boot-installer.xml:205 #, no-c-format msgid "" "Afterwards you need to load the images (kernel/initial ramdisk/dtb) into " "memory. This is done with the tftpboot command, which has to be provided " "with the address at which the image shall be stored in memory. Unfortunately " "the memory map can vary from system to system, so there is no general rule " "which addresses can be used for this." msgstr "" "Efterfølgende skal du indlæse aftrykkene (kerne/intiel ramdisk/dtb) i " "hukommelsen. Dette gøres med kommandoen tftpboot, som skal have adressen " "hvor aftrykket skal lagres i hukommelsen. Desværre kan hukommelseskortet " "variere fra system til system, så der er ingen generel regel om, hvilke " "adresser som kan bruges." #. Tag: para #: boot-installer.xml:213 #, no-c-format msgid "" "On some systems, U-Boot predefines a set of environment variables with " "suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. You " "can check whether they are defined by running \n" "printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n" " If they are not defined, you have to check your " "system's documentation for appropriate values and set them manually. For " "systems based on Allwinner SunXi SOCs (e.g. the Allwinner A10, architecture " "name sun4i or the Allwinner A20, architecture name " "sun7i), you can e.g. use the following values:" msgstr "" "På nogle systemer, prædefinerer U-Boot et sæt af miljøparametre med egnede " "indlæsningsadresser: kernel_addr_r, ramdisk_addr_r og fdt_addr_r. Du kan " "kontrollere om de er defineret ved at køre \n" "printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n" " Hvis de ikke er defineret, så skal du " "kontrollere dit systems dokumentation for passende værdier og angive dem " "manuelt. For systemer baseret på Allwinner SunXi SOC'er (f.eks. Allwinnner " "A10, arkitekturnavn sun4i eller Allwinner A20, arkitekturnavn " "sun7i), du kan f.eks. bruge de følgende værdier:" #. Tag: screen #: boot-installer.xml:224 #, no-c-format msgid "" "setenv kernel_addr_r 0x46000000\n" "setenv fdt_addr_r 0x47000000\n" "setenv ramdisk_addr_r 0x48000000" msgstr "" "setenv kernel_addr_r 0x46000000\n" "setenv fdt_addr_r 0x47000000\n" "setenv ramdisk_addr_r 0x48000000" #. Tag: para #: boot-installer.xml:226 #, no-c-format msgid "" "When the load addresses are defined, you can load the images into memory " "from the previously defined tftp server with" msgstr "" "Når indlæsningsadresserne er defineret, så kan du indlæse aftrykket i " "hukommelsen fra den tidligere definerede tftp-server med" #. Tag: screen #: boot-installer.xml:229 #, no-c-format msgid "" "tftpboot ${kernel_addr_r} <filename of the kernel image>\n" "tftpboot ${fdt_addr_r} <filename of the dtb>\n" "tftpboot ${ramdisk_addr_r} <filename of the initial ramdisk image>" msgstr "" "tftpboot ${kernel_addr_r} <filnavn for kerneaftrykket>\n" "tftpboot ${fdt_addr_r} <filnavn for dtb'en>\n" "tftpboot ${ramdisk_addr_r} <filnavn for det initielle ramdisk-aftryk>" #. Tag: para #: boot-installer.xml:231 #, no-c-format msgid "" "The third part is setting the kernel commandline and actually executing the " "loaded code. U-Boot passes the content of the bootargs " "environment variable as commandline to the kernel, so any parameters for the " "kernel and the installer - such as the console device (see ) or preseeding options (see and ) - can be set with a command " "like \n" "setenv bootargs console=ttyS0,115200 rootwait panic=10\n" " The exact command to execute the previously " "loaded code depends on the image format used. With uImage/uInitrd, the " "command is \n" "bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}\n" " and with native Linux images it is" msgstr "" "Tredjeparten indstiller kernens kommandolinje og kører den indlæste kode. U-" "boot videresender indholdet af miljøvariablen bootargs som " "kommandolinje til kernen, så eventuelle parametre for kernen og " "installationsprogrammet - såsom konsolenheden (se ) eller forudfyldte indstillinger (se og ) - kan sættes med en " "kommando som \n" "setenv bootargs console=ttyS0,115200 rootwait panic=10\n" " Den præcise kommando til at køre den tidligere " "indlæste kode afhænger af det anvendte aftryksformat. Med uImage/uInitrd er " "kommandoen \n" "bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}\n" " og med standardaftryk for Linux er det" #. Tag: screen #: boot-installer.xml:244 #, no-c-format msgid "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}" msgstr "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}" #. Tag: para #: boot-installer.xml:246 #, no-c-format msgid "" "Note: When booting standard linux images, it is important to load the " "initial ramdisk image after the kernel and the dtb as U-Boot sets the " "filesize variable to the size of the last file loaded and the bootz command " "requires the size of the ramdisk image to work correctly. In case of booting " "a platform-specific kernel, i.e. a kernel without device-tree, simply omit " "the ${fdt_addr_r} parameter." msgstr "" "Bemærk: Når der opstartes standardaftryk for Linux, så er det vigtigt at " "indlæse det oprindelige ramdisk-aftryk efter kernen og dtb'en, da U-Boot " "angiver filstørrelsesvariablen til størrelsen på den sidst indlæste fil og " "kommandoen bootz kræver størrelsen af ramdisk-aftrykket for at fungere " "korrekt. I tilfælde hvor der opstartes en platformspecifik kerne, d.v.s. en " "kerne uden enhedstræ, udelades parameteren ${fdt_addr_r}." #. Tag: title #: boot-installer.xml:257 #, no-c-format msgid "Pre-built netboot tarball" msgstr "Forhåndsbygget netboot tarball" #. Tag: para #: boot-installer.xml:258 #, no-c-format msgid "" "&debian; provides a pre-built tarball (&armmp-netboot-tarball;) that can " "simply be unpacked on your tftp server and contains all files necessary for " "netbooting. It also includes a boot script that automates all steps to load " "the installer. Modern U-Boot versions contain a tftp autoboot feature that " "becomes active if there is no bootable local storage device (MMC/SD, USB, " "IDE/SATA/SCSI) and then loads this boot script from the tftp server. " "Prerequisite for using this feature is that you have a dhcp server in your " "network which provides the client with the address of the tftp server." msgstr "" "&debian; tilbyder en forhåndbygget tarball (&armmp-netboot-tarball;) som kan " "pakkes ud på din tftp-server og som indeholder alle filer nødvendige for " "netbooting. Den indeholder også opstartsskript, som automatiserer alle trin " "for at indlæse installationsprogrammet. Moderne U-Boot-versioner indeholder " "en tftp autoboot-funktion som bliver aktiv, hvis der ikke er en lokal " "lagerenhed, der kan starte op fra (MMC/SD, USB, IDE/SATA/SCSI) og som så " "indlæser dette opstartsskript fra tftp-serveren. Det er krævet, at du har en " "dhcp-server i dit netværk, som har en klient med adressen for tftp-serveren." #. Tag: para #: boot-installer.xml:270 #, no-c-format msgid "" "If you would like to trigger the tftp autoboot feature from the U-Boot " "commandline, you can use the follwing command:" msgstr "" "Hvis du ønsker at udløse tftp autoboot-funktionen fra U-Boot-kommandolinjen, " "så kan du bruge den følgende kommando:" #. Tag: screen #: boot-installer.xml:273 #, no-c-format msgid "run bootcmd_dhcp" msgstr "run bootcmd_dhcp" #. Tag: para #: boot-installer.xml:275 #, no-c-format msgid "" "To manually load the bootscript provided by the tarball, you can " "alternatively issue the following commands at the U-Boot prompt:" msgstr "" "For manuelt at indlæse opstartsskriptet leveret med tarball'en, så kan du " "alternativt udstede de følgende kommandoer ved U-Boot-prompten:" #. Tag: screen #: boot-installer.xml:279 #, no-c-format msgid "" "setenv autoload no\n" "dhcp\n" "tftpboot ${scriptaddr} /debian-installer/armhf/tftpboot.scr\n" "source ${scriptaddr}" msgstr "" "setenv autoload no\n" "dhcp\n" "tftpboot ${scriptaddr} /debian-installer/armhf/tftpboot.scr\n" "source ${scriptaddr}" #. Tag: title #: boot-installer.xml:287 #, no-c-format msgid "Booting from USB Memory Stick with UEFI" msgstr "Opstart fra USB-drev med UEFI" #. Tag: para #: boot-installer.xml:293 boot-installer.xml:555 #, no-c-format msgid "" "If your computer will boot from USB, this will probably be the easiest route " "for installation. Assuming you have prepared everything from and , just plug your USB stick into some free USB " "connector and reboot the computer. The system should boot up, and unless you " "have used the flexible way to build the stick and not enabled it, you should " "be presented with a graphical boot menu (on hardware that supports it). Here " "you can select various installer options, or just hit &enterkey;." msgstr "" "Hvis din computer kan starte op fra USB, så vil dette sandsynligvis være den " "letteste vej til installation. Lad os antage, at du har forberedt alt fra " " og . Indsæt dit USB-drev i en " "ledig indgang og genstart computeren. Systemet bør starte op, og med mindre " "du har brugt den fleksible måde til at bygge drevet med og ikke aktiveret " "det, vil du blive præsenteret for en grafisk opstartsmenu (på udstyr som " "understøtter det). Her kan du indtaste valgfrie opstartparametre, eller bare " "trykke på &enterkey;." #. Tag: title #: boot-installer.xml:312 #, no-c-format msgid "Booting from a USB stick in U-Boot" msgstr "Opstart fra et USB-hukommelsesdrev i U-Boot" #. Tag: para #: boot-installer.xml:313 #, no-c-format msgid "" "Many modern U-Boot versions have USB support and allow booting from USB mass " "storage devices such as USB sticks. Unfortunately the exact steps required " "to do that can vary quite a bit from device to device." msgstr "" "Mange moderne U-Boot-versioner har USB-understøttelse og tillader opstart " "fra USB-lagerenheder såsom USB-drev. Desværre er de præcise trin krævet for " "dette forskellige fra enhed til enhed." #. Tag: para #: boot-installer.xml:320 #, no-c-format msgid "" "U-Boot v2014.10 has introduced a common commandline handling and autoboot " "framework. This allows building generic boot images that work on any system " "implementing this framework. The &d-i; supports installation from a USB " "stick on such systems, but unfortunately not all platforms have adopted this " "new framework yet." msgstr "" "U-Boot v2014.10 har introduceret en fælles kommandolinjehåndtering og " "autoboot-ramme. Dette giver mulighed for at bygge generiske opstartsaftryk, " "som fungerer på ethvert system, der implementerer denne ramme. &d-i; " "understøtter installation fra et USB-drev på sådanne systemer, men desværre " "har ikke alle platforme adopteret denne nye ramme endnu." #. Tag: para #: boot-installer.xml:329 #, no-c-format msgid "" "To build a bootable USB stick for installing &debian;, unpack the hd-media " "tarball (see ) onto a USB stick formatted " "with a filesystem supported by the U-Boot version on your device. For modern " "U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / ext4 usually works. " "Then copy the ISO image file of the first &debian; installation CD or DVD " "onto the stick." msgstr "" "For at bygge et USB-drev, der kan startes op fra, til installation af " "&debian; udpakkes hd-media-tarball'en (se ) " "til et USB-drev formateret med et filsystem, der understøtter U-Boot-" "versionen på din enhed. For moderne U-Boot-versioner, fungerer enhver FAT16/" "FAT32/ext2/ext3/ext4 normalt. Kopier så ISO-aftryksfilen fra den første " "&debian;-installations-cd eller dvd til drevet." #. Tag: para #: boot-installer.xml:339 #, fuzzy, no-c-format #| msgid "" #| "The autoboot framework in modern U-Boot versions works similar to the " #| "boot ordering options in a PC BIOS, i.e. it checks a list of possible " #| "boot devices for a valid boot image and starts the first one it finds. If " #| "there is no operating system installed, plugging in the USB stick and " #| "powering up the system should result in starting the installer. You can " #| "also initiate the USB-boot process any time from the U-Boot prompt by " #| "entering the run bootcmd_usb0 command." msgid "" "The autoboot framework in modern U-Boot versions works similar to the boot " "ordering options in a PC BIOS/UEFI, i.e. it checks a list of possible boot " "devices for a valid boot image and starts the first one it finds. If there " "is no operating system installed, plugging in the USB stick and powering up " "the system should result in starting the installer. You can also initiate " "the USB-boot process any time from the U-Boot prompt by entering the " "run bootcmd_usb0 command." msgstr "" "Autoboot-rammen i moderne U-Boot-versioner fungerer på samme måde som " "indstillingerne for opstartsrækkefølgen i en PC BIOS, dvs. den kontrollerer " "en liste over mulige opstartsenheder for et gyldigt opstartsaftryk og starer " "den første den finder. Hvis der ikke er et operativsystem installeret, vil " "indsættelse af USB-drevet og opstart af systemet resultere i en start af " "installationsprogrammet. Du kan også igangsætte USB-opstartsprocessen fra u-" "boot-prompten ved at indtaste kommandoen run bootcmd_usb0." #. Tag: para #: boot-installer.xml:349 #, no-c-format msgid "" "One problem that can come up when booting from a USB stick while using a " "serial console can be a console baudrate mismatch. If a console variable is " "defined in U-Boot, the &d-i; boot script automatically passes it to the " "kernel to set the primary console device and, if applicable, the console " "baudrate. Unfortunately the handling of the console variable varies from " "platform to platform - on some platforms, the console variable includes the " "baudrate (as in console=ttyS0,115200), while on other " "platforms the console variable contains only the device (as in " "console=ttyS0). The latter case leads to a garbled console " "output when the default baudrate differs between U-Boot and the kernel. " "Modern U-Boot versions often use 115200 baud while the kernel still defaults " "to the traditional 9600 baud. If this happens, you should manually set the " "console variable to contain the correct baudrate for your system and then " "start the installer with the run bootcmd_usb0 command." msgstr "" "Et problem som kan fremkomme, når der startes op fra et USB-drev, mens der " "anvendes en seriel konsol er en konsols baudhastighedsforskel. Hvis en " "konsolvariabel er defineret i U-Boot, sender &d-i;-opstartskriptet " "automatisk den til kernen for at sætte den primære konsolenhed og, hvis " "anvendelig, konsollens baudhastighed. Desværre varierer håndteringen af " "konsollens variabler fra platform til platform - på nogle platforme " "inkluderer konsolvariablen baudhastigheden (som i " "console=ttyS0,115200), mens på andre platforme indeholder " "konsolvariablen kun enheden (som i console=ttyS0). Det sidste " "tilfælde fører til et forvansket konsolresultat, når standardbauthastigheden " "er forskellig mellem U-Boot og kernen. Moderen U-Boot-versioner bruger ofte " "115200 baud mens kernen stadig har en standard å de traditionelle 9600 baud. " "Hvis dette opstår, så skal du manuelt sætte konsolvariablen til at indeholde " "den korrekte baudhastighed for dit system og så starte " "installationsprogrammet med kommandoen run bootcmd_usb0." #. Tag: title #: boot-installer.xml:370 #, no-c-format msgid "Using pre-built SD-card images with the installer" msgstr "Brug af forhåndsbyggede SD-kortaftryk med installationsprogrammet" #. Tag: para #: boot-installer.xml:371 #, no-c-format msgid "" "For a number of systems, Debian provides SD card images that contain both U-" "Boot and the &d-i;. These images are provided in two variants - one for " "downloading the software packages over the network (available at &armmp-" "netboot-sd-img;) and one for offline installations using a Debian CD/DVD " "(available at &armmp-hd-media-sd-img;). To save space and network bandwidth, " "the images consist of two parts - a system-dependent part named " "firmware.<system-type>.img.gz, and a system-independent " "part named partition.img.gz." msgstr "" "For et antal af systemer tilbyder Debian SD-kortaftryk, som indeholder både " "U-Boot og &d-i;. Disse aftryk tilbydes i to varianter - et for overførsel af " "programpakker over netværket (tilgængelig som &armmp-netboot-sd-img;) og et " "for lokale installationer via en Debian cd/dvd (tilgængelig som &armmp-hd-" "media-sd-img;). For at spare på plads og båndbredde består aftrykkene af to " "dele - en systemafhængig del navngivet firmware.<system-type>." "img.gz, og en systemuafhængig del navngivet partition.img.gz." #. Tag: para #: boot-installer.xml:382 #, no-c-format msgid "" "To create a complete image from the two parts on Linux systems, you can use " "zcat as follows: zcat firmware.<system-type>." "img.gz partition.img.gz > complete_image.img " "On Windows systems, you have to first decompress the two parts separately, " "which can be done e.g. by using 7-Zip, and then concatenate the decompressed " "parts together by running the command copy /b " "firmware.<system-type>.img + partition.img complete_image.img in a Windows CMD.exe window." msgstr "" "For at oprette et fuldstændigt aftryk fra de dele på Linuxsystemer, så kan " "du bruge zcat: zcat firmware.<system-type>." "img.gz partition.img.gz > complete_image.img " "På Windowssystemer skal du først udpakke de to dele hver for sig, hvilket " "kan gøres via 7-Zip og så samle de to udpakkede dele ved at køre kommandoen " "copy /b firmware.<system-type>.img + " "partition.img complete_image.img i et Windows CMD." "exe-vindue." #. Tag: para #: boot-installer.xml:396 #, no-c-format msgid "" "Write the resulting image onto an SD card, e.g. by running the following " "command on a Linux system: cat complete_image.img " "> /dev/SD_CARD_DEVICE After plugging the SD " "card into the target system and powering the system up, the installer is " "loaded from the SD card. If you use the hd-media variant for offline " "installations, you must provide the installer with access to the first " "&debian; CD/DVD on a separate medium, which can e.g. be a CD/DVD ISO image " "on a USB stick." msgstr "" "Skriv aftrykket til et SD-kort, f.eks. ved at køre den følgende kommando på " "et Linuxsystem: cat complete_image.img > /dev/" "SD_CARD_DEVICE Tilslut SD-kortet i målsystemet og " "tænd for det. Installationsprogrammet indlæses så fra SD-kortet. Hvis du " "bruger varianten hd-media for lokale installationer, så skal du give " "installationsprogrammet adgang til den første &debian; cd/dvd på et separat " "medie, som f.ek.s kan være et cd/dvd iso-aftryk på et USB-drev." #. Tag: para #: boot-installer.xml:408 #, no-c-format msgid "" "When you come to the partitioning step in the installer (see ), you can delete or replace any previous partitions on " "the card. Once the installer is started, it runs completely in the system's " "main memory and does not need to access the SD card anymore, so you can use " "the full card for installing &debian;. The easiest way to create a proper " "partition layout on the SD card is to let the installer automatically create " "one for you (see )." msgstr "" "Når du kommer til partitioneringstrinet i installationsprogrammet (se ), kan du slette eller erstatte tidligere " "partitioner på kortet. Når installationsprogrammet er startet kører det " "alene i systemets hovedhukommelse og kræver ikke længere adgang til SD-" "kortet, så du kan bruge hele kortet for installation af &debian;. Den " "nemmeste måde at oprette et korrekt partitionslayout på SD-kortet er at lade " "installationsprogrammet automatisk oprette et for dig (se )." #. Tag: title #: boot-installer.xml:549 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "Opstart fra USB-drev" #. Tag: title #: boot-installer.xml:573 #, fuzzy, no-c-format #| msgid "Booting from a CD-ROM" msgid "Booting from optical disc (CD/DVD)" msgstr "Opstart fra en cd-rom" #. Tag: para #: boot-installer.xml:579 boot-installer.xml:986 boot-installer.xml:1929 #, fuzzy, no-c-format #| msgid "" #| "If you have a CD set, and if your machine supports booting directly off " #| "the CD, great! Simply configure your system for " #| "booting off a CD as described in , " #| " insert your CD, reboot, and proceed to the next chapter." msgid "" "If you have a set of optical discs, and your machine supports booting " "directly off those, great! Simply configure your " "system for booting off an optical disc as described in , insert the disc, reboot, and proceed to the " "next chapter." msgstr "" "Hvis du har et cd-sæt og din maskine understøtter opstart direkte fra cd'en " "så er det rigtig godt! Konfigurer dit system for ved " "opstart fra en cd som beskrevet i , indsæt din cd, genstart og fortsæt til næste kapitel." #. Tag: para #: boot-installer.xml:589 boot-installer.xml:996 boot-installer.xml:1939 #, fuzzy, 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." msgid "" "Note that certain optical drives may require special drivers, and thus be " "inaccessible in the early installation stages. If it turns out the standard " "way of booting off an optical disc doesn't work for your hardware, revisit " "this chapter and read about alternate kernels and installation methods which " "may work for you." msgstr "" "Bemærk at visse cd-drev kan kræve specielle drivere og kan derfor være " "utilgænglige i de første trin af installationen. Hvis det viser sig at den " "normale måde at starte op fra en cd ikke fungerer på dit udstyr, så besøg " "det her kapitel igen og læs om alternative kerner og installationsmetoder " "som måske vil fungere for dig." #. Tag: para #: boot-installer.xml:597 boot-installer.xml:1004 boot-installer.xml:1947 #, fuzzy, no-c-format #| msgid "" #| "Even if you cannot boot from CD-ROM, you can probably install the " #| "&debian; system components and any packages you want from CD-ROM. Simply " #| "boot using a different medium and when it's time to install the operating " #| "system, base system, and any additional packages, point the installation " #| "system at the CD-ROM drive." msgid "" "Even if you cannot boot from optical disc, you can probably install the " "&debian; system components and any packages you want from such disc. Simply " "boot using a different medium and when it's time to install the operating " "system, base system, and any additional packages, point the installation " "system at the optical drive." msgstr "" "Selv om du ikke kan starte op fra cd-rom kan du antagelig installere &debian;" "s systemkomponenter og de pakker du ønsker fra cd-rom. Start op på et andet " "medie, og når det er tid at intallere operativsystemet, basissystemet og " "eventuelle ekstra pakker, så peg installationssystemet til cd-rom-drevet." #. Tag: para #: boot-installer.xml:605 boot-installer.xml:1012 boot-installer.xml:1955 #, no-c-format msgid "" "If you have problems booting, see ." msgstr "" "Hvis du har problemer med at starte op, så se ." #. Tag: title #: boot-installer.xml:615 #, no-c-format msgid "Booting from Windows" msgstr "Opstart fra Windows" #. Tag: para #: boot-installer.xml:616 #, no-c-format msgid "To start the installer from Windows, you can either" msgstr "For at starte installationsprogrammet fra Windows kan du enten" #. Tag: para #: boot-installer.xml:621 #, fuzzy, no-c-format #| msgid "" #| "obtain CD-ROM/DVD-ROM or USB memory " #| "stick installation media as described in respective or" msgid "" "obtain installation media as described in or or" msgstr "" "hente cd-rom/dvd-rom- eller USB- installationsmedie, som beskrevet i respektiv eller" #. Tag: para #: boot-installer.xml:628 #, no-c-format msgid "" "download a standalone Windows executable, which is available as tools/win32-loader/stable/win32-loader.exe on " "the &debian; mirrors." msgstr "" "hente en uafhængig kørbar fil for Windows, som er tilgængelig som tools/win32-loader/stable/win32-loader.exe på " "&debian;-spejlene." #. Tag: para #: boot-installer.xml:637 #, fuzzy, no-c-format #| msgid "" #| "If you use an installation CD or DVD, a pre-installation program should " #| "be launched automatically when you insert the disc. In case Windows does " #| "not start it automatically, or if you are using a USB memory stick, you " #| "can run it manually by accessing the device and executing setup." #| "exe." msgid "" "If you use optical installation media, a pre-installation program should be " "launched automatically when you insert the disc. In case Windows does not " "start it automatically, or if you are using a USB memory stick, you can run " "it manually by accessing the device and executing setup.exe." msgstr "" "Hvis du bruger en installations-cd eller -dvd, vil et " "præinstallationsprogram blive startet automatisk når du indsætter disken. I " "tilfælde af, at Windows ikke starter den automatisk, eller hvis du bruger et " "USB-drev, så kan du starte manuelt ved at tilgå enheden og køre " "setup.exe." #. Tag: para #: boot-installer.xml:645 #, no-c-format msgid "" "After the program has been started, a few preliminary questions will be " "asked and the system will be prepared to reboot into the &debian-gnu; " "installer." msgstr "" "Efter at programmet er blevet startet, vil nogle få forhåndsspørgsmål blive " "stillet og systemet vil blive forberedt til at genstarte ind i &debian-gnu;-" "installationsprogrammet." #. Tag: title #: boot-installer.xml:655 #, no-c-format msgid "Booting from DOS using loadlin" msgstr "Opstart fra DOS med loadlin" #. Tag: para #: boot-installer.xml:656 #, no-c-format msgid "" "Boot into DOS (not Windows). To do this, you can for instance boot from a " "recovery or diagnostic disk." msgstr "" "Start op i DOS (ikke Windows). For at gøre dette kan du for eksempel starte " "op fra en gendannelses- eller diagonostikdisk." #. Tag: para #: boot-installer.xml:661 #, no-c-format msgid "" "If you can access the installation CD, change the current drive to the CD-" "ROM drive, e.g. \n" "d:\n" " else make sure you have first prepared your hard " "disk as explained in , and change the " "current drive to it if needed." msgstr "" "Hvis du kan tilgå installations-cd'en, så ændr det aktuelle drev til cd-rom-" "drevet, f.eks. \n" "d:\n" " ellers skal du sikre dig, at du først har " "forberedt din harddisk som forklaret i, og " "ændre det aktuelle drev, hvis det er krævet." #. Tag: para #: boot-installer.xml:671 #, no-c-format msgid "" "Enter the subdirectory for the flavor you chose, e.g., " "\n" "cd \\&x86-install-dir;\n" " If you prefer using the graphical installer, " "enter the gtk sub-directory. \n" "cd gtk\n" " Next, execute install.bat. " "The kernel will load and launch the installer system." msgstr "" "Gå til undermappen for den variant du ønsker, f.eks. " "\n" "cd \\&x86-install-dir;\n" " Hvis du foretrækker det grafiske " "installationsprogram, så gå til undermappen gtk. " "\n" "cd gtk\n" " Kør derefter install.bat. " "Kernen vil indlæse og igangsætte installationssystemet." #. Tag: title #: boot-installer.xml:689 #, fuzzy, no-c-format #| msgid "" #| "Booting from Linux using LILO or GRUB" msgid "Booting from Linux using GRUB" msgstr "" "Opstart fra Linux med LILO eller GRUB" #. Tag: para #: boot-installer.xml:692 #, no-c-format msgid "" "To boot the installer from hard disk, you must first download and place the " "needed files as described in ." msgstr "" "For at starte installationsprogrammet op fra harddisken skal du først hente " "og placere de nødvendige filer som beskrevet i ." #. Tag: para #: boot-installer.xml:697 #, no-c-format msgid "" "For GRUB2, you will need to configure two essential " "things in /boot/grub/grub.cfg:" msgstr "" #. Tag: para #: boot-installer.xml:701 #, no-c-format msgid "to load the initrd.gz installer at boot time;" msgstr "" #. Tag: para #: boot-installer.xml:706 #, no-c-format msgid "" "have the vmlinuz kernel use a RAM disk as its root " "partition." msgstr "" #. Tag: para #: boot-installer.xml:714 #, no-c-format msgid "An entry for the installer would be for example:" msgstr "" #. Tag: screen #: boot-installer.xml:718 #, no-c-format msgid "" "menuentry 'New Install' {\n" "insmod part_msdos\n" "insmod ext2\n" "set root='(hd0,msdos1)'\n" "linux /boot/newinstall/vmlinuz\n" "initrd /boot/newinstall/initrd.gz\n" "}" msgstr "" "menuentry 'New Install' {\n" "insmod part_msdos\n" "insmod ext2\n" "set root='(hd0,msdos1)'\n" "linux /boot/newinstall/vmlinuz\n" "initrd /boot/newinstall/initrd.gz\n" "}" #. Tag: title #: boot-installer.xml:723 boot-installer.xml:1348 boot-installer.xml:1490 #: boot-installer.xml:1883 #, no-c-format msgid "Booting with TFTP" msgstr "Opstart med TFTP" #. Tag: para #: boot-installer.xml:748 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "Der er forskellige måder at udføre en TFTP-opstart på i386." #. Tag: title #: boot-installer.xml:754 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "NIC eller bundkort som understøtter PXE" #. Tag: para #: boot-installer.xml:755 #, fuzzy, 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." 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/UEFI to boot from the network." msgstr "" "Det kan være at dit netværkskort eller bundkort tilbyder en PXE-" "opstartsfunktion. Dette er en Intel-" "reimplementering af TFTP-opstart. Hvis det er tilfældet kan du måske " "konfigurere din BIOS til at starte op fra netværket." #. Tag: title #: boot-installer.xml:766 #, no-c-format msgid "NIC with Network BootROM" msgstr "NIC med netværks-BootROM" #. Tag: para #: boot-installer.xml:767 #, no-c-format msgid "" "It could be that your Network Interface Card provides TFTP boot " "functionality." msgstr "Det kan være at dit netværkskort tilbyder TFTP-opstartfunktionalitet." #. Tag: para #: boot-installer.xml:772 #, no-c-format msgid "" "Let us (&email-debian-boot-list;) know how did you manage it. " "Please refer to this document." msgstr "" "Lad os (&email-debian-boot-list;) høre om hvordan du " "håndterede det. Henvis til dette dokument." #. Tag: title #: boot-installer.xml:780 #, no-c-format msgid "Etherboot" msgstr "Etherboot" #. Tag: para #: boot-installer.xml:781 #, no-c-format msgid "" "The etherboot project " "provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" "Etherbootprojektet tilbyder " "opstartsdisketter og endda bootrom'er som udfører en TFTPboot." #. Tag: title #: boot-installer.xml:791 #, no-c-format msgid "The Boot Screen" msgstr "Opstartsskærmen" #. Tag: para #: boot-installer.xml:792 #, no-c-format msgid "" "When the installer boots, you should be presented with a friendly graphical " "screen showing the &debian; logo and a menu:" msgstr "" "Når installationsprogrammet starter op, så bliver du præsenteret for en " "venlig grafisk skærm, der viser &debian;-logoet og en menu:" #. Tag: screen #: boot-installer.xml:797 #, no-c-format msgid "" "&debian-gnu; installer boot menu\n" "\n" "Graphical install\n" "Install\n" "Advanced options >\n" "Accessible dark contrast installer menu >\n" "Help\n" "Install with speech synthesis" msgstr "" "&debian-gnu; installer boot menu\n" "\n" "Graphical install\n" "Install\n" "Advanced options >\n" "Accessible dark contrast installer menu >\n" "Help\n" "Install with speech synthesis" #. Tag: para #: boot-installer.xml:801 #, no-c-format msgid "" "This graphical screen will look very slightly different depending on how " "your computer has booted (BIOS or UEFI), but the same options will be shown." msgstr "" "Denne grafiske skærm vil se en smule anderledes ud afhængig af hvordan din " "computer er startet op (BIOS eller UEFI), men de samme indstillinger vil " "blive vist." #. Tag: para #: boot-installer.xml:809 #, no-c-format msgid "" "Depending on the installation method you are using, the Graphical " "install option may not be available. Bi-arch images additionally " "have a 64 bit variant for each install option, right below it, thus almost " "doubling the number of options." msgstr "" "Afhængig af den anvendte installationsmetode er valget Grafisk " "installation måske ikke tilgængelig. Aftryk for to arkitekturer har " "derudover en 64-bit variant for hvert installationsvalg, lige nedenunder, og " "fordobler dermed antallet af valg." #. Tag: para #: boot-installer.xml:816 #, no-c-format msgid "" "For a normal installation, select either the Graphical install or the Install entry — using either the arrow " "keys on your keyboard or by typing the first (highlighted) letter — " "and press &enterkey; to boot the installer. The Graphical install entry is already selected by default." msgstr "" "For en normal installation, vælg enten punktet Graphical install eller Install — med brug af enten piletasterne " "på dit tastatur eller ved at indtaste det første (fremhævede) bogstav " "— og tryk på &enterkey; for at starte installationen. Punktet " "Graphical install er allerede valgt som standard." #. Tag: para #: boot-installer.xml:824 #, no-c-format msgid "" "The Advanced options entry gives access to a second menu that " "allows to boot the installer in expert mode, in rescue mode and for " "automated installs." msgstr "" "Punktet Advanced options giver adgang til en anden menu, som " "giver mulighed for at opstarte installationsprogrammet i tilstanden ekspert, " "i redningstilstand og for automatiserede installationer." #. Tag: para #: boot-installer.xml:830 #, no-c-format msgid "" "If you wish or need to add any boot parameters for either the installer or " "the kernel, press &tabkey; (BIOS boot), or &ekey; then &downkey; three times " "then &endkey; (UEFI boot). This will bring the boot command for the selected " "menu entry and allow you to edit it to suit your needs. Note that the " "keyboard layout at this point is still QWERTY. The help screens (see below) " "list some common possible options. Press &enterkey; (BIOS boot) or &f10key; " "(UEFI boot) to boot the installer with your options; pressing &escapekey; " "will return you to the boot menu and undo any changes you made." msgstr "" "Hvis du ønsker eller har brug for at tilføje opstartsparametre for enten " "installationsprogrammet eller kernen, så tryk &tabkey; (BIOS-opstart) eller " "&ekey; så &downkey; tre gange og så &endkey; (UEFI-opstart). Dette vil vise " "opstartskommandoen for det valgte menupunkt og give mulighed for at lave " "tilpasninger efter behov. Bemærk at tastaturlayoutet på dette tidspunkt " "stadig er QERTY. Hjælpeskærmene (se nedenfor) viser nogle gængse " "indstillingsmuligheder. Tryk &enterkey; (BIOS-opstart) eller &f10key; (UEFI-" "opstart) for at starte installationsprogrammet op med dine indstillinger; et " "tryk på &escapekey; vil returnere dig til opstartsmenuen og omgøre " "eventuelle ændringer, du har foretaget." #. Tag: para #: boot-installer.xml:843 #, no-c-format msgid "" "Choosing the Help entry will result in the first help screen " "being displayed which gives an overview of all available help screens. To " "return to the boot menu after the help screens have been displayed, type " "menu at the boot prompt and press &enterkey;. All help " "screens have a boot prompt at which the boot command can be typed: " "\n" "Press F1 for the help index, or ENTER to boot:\n" " At this boot prompt you can either just press " "&enterkey; to boot the installer with default options or enter a specific " "boot command and, optionally, boot parameters. A number of boot parameters " "which might be useful can be found on the various help screens. If you do " "add any parameters to the boot command line, be sure to first type the boot " "method (the default is install) and a space before " "the first parameter (e.g., install fb=false)." msgstr "" "Valg af punktet Help vil resultere i at den første " "hjælpeskærm bliver vist, hvilket giver et overblik over alle tilgængelige " "hjælpeskærme. For at returnere til opstartsmenuen efter at hjælpeskærmene er " "blevet vist, så tast menu ved opstartsprompten og tryk på " "&enterkey;. Alle hjælpeskærme har en opstartsprompt hvor opstartskommandoen " "kan indtastes: \n" "Press F1 for the help index, or ENTER to boot:\n" " Ved denne opstartsprompt kan du enten bare " "trykke &enterkey; for at igangsætte opstartsprogrammet med " "standardindstillinger eller indtaste en specifik opstartskommando og - " "valgfrit - opstartsparametre. Et antal opstartsparametere som kan være " "nyttige kan findes på de forskellige hjælpeskærme. Hvis du tilføjer " "parametre til opstartskommandolinjen, så være sikker på først at indtaste " "opstartsmetoden (standarden er install) og et " "mellemrum før den første parameter (f.eks. install fb=false)." #. Tag: para #: boot-installer.xml:861 #, no-c-format msgid "" "The keyboard is assumed to have a default American English layout at this " "point. This means that if your keyboard has a different (language-specific) " "layout, the characters that appear on the screen may be different from what " "you'd expect when you type parameters. Wikipedia has a schema of the US keyboard layout which can be used as a " "reference to find the correct keys to use." msgstr "" "Tastaturet antages at have det normale amerikansk-engelske layout på dette " "tidspunkt. Dette betyder at hvis dit tastatur har et andet (sprogspecifik) " "layout, kan tegnene som skrives på skærmen være forskellige fra hvad du " "forventer, når du indtaster parametere. Wikipedia har et skema for US-tastaturlayout, som kan bruges som en " "reference til at finde de korrekte taster." #. Tag: para #: boot-installer.xml:871 #, no-c-format msgid "" "If you are using a system that has the BIOS configured to use serial " "console, you may not be able to see the initial graphical splash screen upon " "booting the installer; you may even not see the boot menu. The same can " "happen if you are installing the system via a remote management device that " "provides a text interface to the VGA console. Examples of these devices " "include the text console of Compaq's integrated Lights Out " "(iLO) and HP's Integrated Remote Assistant (IRA)." msgstr "" "Hvis du bruger et sytsem som har BIOS'en konfigureret til at bruge seriel " "konsol, så kan du måske se den grafiske opstartsskærm før " "installationsprogrammet indlæses; du ser måske slet ikke opstartsmenuen. Det " "samme kan ske hvis du installerer systemet via en ekstern håndteringsenhed, " "som tilbyder en tekstgrænseflade til VGA-konsollen. Eksempler på disse " "enheder inkluderer tekstkonsollen for Compaqs integrated Lights Out (iLO) og HP's Integrated Remote Assistant (IRA)." #. Tag: para #: boot-installer.xml:881 #, no-c-format msgid "" "To bypass the graphical boot screen you can either blindly press &escapekey; " "to get a text boot prompt, or (equally blindly) press H " "followed by &enterkey; to select the Help option described " "above. After that your keystrokes should be echoed at the prompt. To prevent " "the installer from using the framebuffer for the rest of the installation, " "you will also want to add vga=normal fb=false to the " "boot prompt, as described in the help text." msgstr "" "For at forbigå den grafiske opstartsskærm kan du enten blindt indtaste " "&escapekey; for at få en tekstopstartsprompt, eller (lige så blindt) taste " "H efterfulgt af &enterkey; for at vælge indstillingen " "Help beskrevet ovenfor. Herefter bør dine tastaturtryk blive " "gengivet på prompten. For at forhindre installationsprogramet i at bruge " "framebufferen i resten af installationen, skal du også tilføje " "vga=normal fb=false til opstartsprompten, som " "beskrevet i hjælpeteksten." #. Tag: title #: boot-installer.xml:897 #, no-c-format msgid "The Graphical Installer" msgstr "Det grafiske installationsprogram" #. Tag: para #: boot-installer.xml:898 #, no-c-format msgid "" "The graphical version of the installer is only available for a limited " "number of architectures, including &arch-title;. The functionality of the " "graphical installer is essentially the same as that of the text-based " "installer as it basically uses the same programs, but with a different " "frontend." msgstr "" "Den grafiske version af installationsprogrammet er kun tilgængelig i et " "begrænset antal arkitekturer, inklusive &arch-title;. Funktionaliteten for " "det grafiske installationsprogram er essentielt den samme som det " "tekstbaserede installationsprogram, da det grundlæggende bruger det samme " "program, men med en anden brugerflade." #. Tag: para #: boot-installer.xml:906 #, no-c-format msgid "" "Although the functionality is identical, the graphical installer still has a " "few significant advantages. The main advantage is that it supports more " "languages, namely those that use a character set that cannot be displayed " "with the text-based newt frontend. It also has a few " "usability advantages such as the option to use a mouse, and in some cases " "several questions can be displayed on a single screen." msgstr "" "Selvom funktionaliteten er identisk, så har det grafiske " "installationsprogram stadig få signifikante fordele. Hovedfordelen er, at " "det understøtter flere sprog, nemlig dem som bruger et tegnsæt, som ikke kan " "vises med den tekstbaserede newt-brugerflade. Den har også " "nogle få brugsfordele såsom muligheden for at bruge en mus, og i nogle " "tilfælde kan flere spørgsmål vises på en enkel skærm." #. Tag: para #: boot-installer.xml:915 #, fuzzy, no-c-format #| msgid "" #| "The graphical installer is available with all CD images and with the hd-" #| "media installation method. To boot the graphical installer simply select " #| "the relevant option from the boot menu. Expert and rescue mode for the " #| "graphical installer can be selected from the Advanced options menu. The previously used boot methods installgui, expertgui and rescuegui can still be used from the boot prompt which is shown after " #| "selecting the Help option in the boot menu." msgid "" "The graphical installer is available with all CD/DVD images and with the hd-" "media installation method. To boot the graphical installer simply select the " "relevant option from the boot menu. Expert and rescue mode for the graphical " "installer can be selected from the Advanced options menu. The " "previously used boot methods installgui, " "expertgui and rescuegui can " "still be used from the boot prompt which is shown after selecting the " "Help option in the boot menu." msgstr "" "Det grafiske installationsprogram er tilgængelig med alle cd-aftryk og med " "hd-medie-installationsmetoden. For at starte det grafiske " "installationsprogram vælges den relevante indstilling fra opstartsmenuen. " "Ekspert- og redningstilstand for det grafiske installationsprogram kan " "vælges fra menuen Advanced options. De tidligere anvendte " "opstartsmetoder installgui, expertgui og rescuegui kan stadig bruges fra " "opstartsprompten, som vises efter valg af indstillingen Help " "i opstartsmenuen." #. Tag: para #: boot-installer.xml:926 #, no-c-format msgid "" "There is also a graphical installer image that can be netbooted. And there " "is a special mini ISO image " " The mini ISO image can be downloaded from a &debian; mirror as " "described in . Look for " "netboot/gtk/mini.iso. , which is " "mainly useful for testing." msgstr "" "Der er også et grafisk installationsaftryk, som kan netstartes. Og der er et " "specielt mini ISo-aftryk " " Mini-ISO-aftrykket kan hentes fra et &debian;-spejl som beskrevet i " ". Kig efter netboot/gtk/mini." "iso. , som hovedsagelig er nyttig for test." #. Tag: para #: boot-installer.xml:939 #, no-c-format msgid "" "For &arch-title;, currently only an experimental mini ISO " "image is available The mini ISO " "image can be downloaded from a &debian; mirror as described in . Look for netboot/gtk/mini.iso. " " . It should work on almost all PowerPC systems that have " "an ATI graphical card, but is unlikely to work on other systems." msgstr "" "For &arch-title;, er i øjeblikket kun et eksperimentelt mini-" "ISO-aftryk tilgængeligt Mini-ISO-" "aftrykket kan hentes fra et &debian;-spejl som beskrevet i . Kig efter netboot/gtk/mini.iso. . Den bør fungere på næsten alle PowerPC-" "systemer, som har et ATI-grafikkort, men vil sandsynligvis ikke fungere på " "andre systemer." #. Tag: para #: boot-installer.xml:953 #, no-c-format msgid "" "Just as with the text-based installer it is possible to add boot parameters " "when starting the graphical installer." msgstr "" "På samme måde som med det tekstbaserede installationsprogram er det muligt " "at tilføje opstartsparametre, når det grafiske installationsprogram startes." #. Tag: para #: boot-installer.xml:959 #, no-c-format msgid "" "The graphical installer requires significantly more memory to run than the " "text-based installer: &minimum-memory-gtk;. If insufficient memory is " "available, it will automatically fall back to the text-based newt frontend." msgstr "" "Det grafiske installationsprogram kræver signifikant mere hukommelse for at " "køre end det tekstbaserede installationsprogram: &minimum-memory-gtk;. Hvis " "utilstrækkelig hukommelse er tilgængelig, vil den automatisk gå tilbage til " "den tekstbaserede newt brugerflade." #. Tag: para #: boot-installer.xml:966 #, no-c-format msgid "" "If the amount of memory in your system is below &minimum-memory;, the " "graphical installer may fail to boot at all while booting the text-based " "installer would still work. Using the text-based installer is recommended " "for systems with little available memory." msgstr "" "Hvis hukommelsesmængden i dit system er under &minimum-memory;, så vil det " "grafiske installationsprogram fejle fuldstændig i at starte, mens opstart " "med det tekstbaserede installationsprogram stadig vil fungere. Brug af det " "tekstbaserede installationsprogram anbefales for systemer med små mængder " "tilgængelig hukommelse." #. Tag: title #: boot-installer.xml:980 boot-installer.xml:1923 #, no-c-format msgid "Booting from a CD-ROM" msgstr "Opstart fra en cd-rom" #. Tag: title #: boot-installer.xml:1020 #, no-c-format msgid "CD Contents" msgstr "Cd-indhold" #. Tag: para #: boot-installer.xml:1022 #, 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 "" "Der er tre grundlæggende variationer af installations-cd'er for &debian;. " "Forretningskort-cd'en har en minimal installation, som " "vil passe på det lille form factor cd-medie. Det kræver et " "netværksforbindelse for at installere resten af det grundlæggende " "installation og få et brugbart system. Netværksinstallations-cd'en har alle pakkerne for en grundlæggende installation men " "kræver en netværksforbindelse til en &debian;-spejlside for at installere " "ekstra pakker der kan udgøre et fuldstændigt system. Sættet af &debian;-" "cd'er kan installere et fuldstændig system fra det brede udvalg af apkker " "uden at kræve adgang til netværket." #. Tag: para #: boot-installer.xml:1038 #, 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 "" "IA-64-arkitekturen bruger den næste generations Extensible Firmware " "Interface (EFI) fra Intel. Til forskel fra den traditionelle x86 BIOS, som " "ikke kender meget til opstartsenheden udover partitionstabellen og Master " "Boot Record (MBR), kan EFI læse og skrive filer fra FAT16 eller FAT32-" "formatterede diskpartitioner. Dette forenkler den ofte omfangsrige proces " "ved at starte et system. Systemets opstartsindlæser og EFI-firmwaren som " "understøtter den har et fuldt filsystem til at gemme de nødvendige filer for " "opstart af maskinen. Dette betyder at systemdisken på et IA-64-system har en " "yderligere diskpartiiton dedikeret til EFI i stedet for den simple MBR eller " "opstartsblok for mere konventionelle systemer." #. Tag: para #: boot-installer.xml:1054 #, 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;-installations-cd'en indeholder en lille EFI-partition hvor " "ELILO-opstartsindlæseren, dens konfigurationsfil, " "installationsprogrammets kerne og det oprindelige filsystem (initrd) er " "placeret. Det kørende system indeholder også en EFI-partition hvor de " "nødvendige filer for opstart af systemet befinder sig. Disse filer er " "læsbare fra EFI-skallen som beskrevet nedenfor." #. Tag: para #: boot-installer.xml:1063 #, 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 fleste detaljer om hvordan ELILO faktisk indlæser og " "starter et system er gennemsigtige for systemets installationsprogram. " "Installationsprogrammet skal dog opsætte en EFI-partition før det " "grundlægende system installeres. Ellers vil installationen af " "ELILO mislykkes, og medføre at systemet ikke kan startes " "op. EFI-partitionen er placeret og formateret i partitioneringstrinet for " "installationen før der indlæses pakker på systemdisken. " "Partitioneringsopgaven verificerer også at en egnet EFI-partition er til " "stede før installationen får lov til at fortsætte." #. Tag: para #: boot-installer.xml:1075 #, 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-opstartshåndteringen præsenteres ved det sidste trin i firmware-" "initialiseringen. Den viser en menuliste hvorfra brugeren kan foretage et " "valg. Afhængig af systemmodellen og hvilke andre programmer der er blevet " "indlæst på systemet, kan denne menu være forskellig fra et system til et " "andet. Der skal være mindst to menupunkter vist, " "Vedligeholdelsesmenu for opstartsindstillinger og " "EFI-skal (indbygget). Brug af den første indstilling " "foretrækkes, hvis denne indstilling ikke er tilgængelig eller cd'en af en " "eller anden grund ikke starter med den, så brug den anden indstilling." #. Tag: title #: boot-installer.xml:1094 #, no-c-format msgid "IMPORTANT" msgstr "VIGTIGT" #. Tag: para #: boot-installer.xml:1095 #, 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-opstartshåndteringen vil vælge en standardhandling for opstarten, typisk " "det første menuvalg, inden for et prædefineret antal sekunder. Dette vises " "med en nedtælling i bunden af skærmen. Når tidsmåleren udløber og systemet " "starter standardhandlingen, skal du måske genstarte maskinene for at " "fortsætte installationen. Hvis standardhandlingen er EFI-skallen, kan du " "returnere til opstartshåndteirngen ved at køre exit i " "skalprompten." #. Tag: title #: boot-installer.xml:1107 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "Valg 1: Opstart fra vedligeholdelsesmenuen for opstartsindstillinger" #. Tag: para #: boot-installer.xml:1114 #, 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 "" "Indsæt cd'en i dvd/cd-drevet og genstart maskinen. Firmwaren vil vise siden " "for EFI-opstartshåndteringen og menuen efter at den færdiggør dets " "systeminitialisering." #. Tag: para #: boot-installer.xml:1120 #, 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ælg Menu for opstartsvedligeholdelse fra menuen med " "piletasterne og tryk på RETUR. Dette vil vise en ny menu." #. Tag: para #: boot-installer.xml:1126 #, 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ælg Start op fra en fil fra menuen med piletasterne og " "tryk på RETUR. Dette vil vise en liste over enheder " "undersøgt af firmwaren. Du bør se to menulinjer der indeholder enten " "etiketten Debian Inst [Acpi ... eller Eksternt " "medieopstart. Hvis du undersøger resten af menulinjen, vil du " "bemærke at enheds- og controllerinformationen bør være ens." #. Tag: para #: boot-installer.xml:1137 #, 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ælge en af punkterne som refererer til cd/dvd-drevet. Foretag dit " "valg med piletasterne og tryk på RETUR. Hvis du vælger " "Eksternt medieopstart så vil maskinen igangsætte " "opstartsindlæsningssekvensen. Hvis du vælger Debian Inst [Acpi ... i stedet for, så vil den vise en mappe over opstartsdelen af cd'en, " "hvor det bliver krævet at du fortsætter til næste (yderligere) trin." #. Tag: para #: boot-installer.xml:1148 #, 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 skal kun bruge dette trin, hvis du vælger Debian Inst [Acpi .... Mappevisningen vil også vise [Treat like Removable Media " "Boot] på den næste til den sidste linje. Vælg denne linje med " "piletasterne og tryk på RETUR. Dette vil igangsætte " "opstartssekvensen." #. Tag: para #: boot-installer.xml:1160 #, 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 "" "Disse trin starter &debian;-opstartsindlæseren, som vil vise en menuside " "hvor du kan vælge en opstartskerne og indstillinger. Fortsæt for at vælge " "opstartskernen og indstillinger." #. Tag: title #: boot-installer.xml:1170 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "Indstilling 2: Opstart fra EFI-skallen" #. Tag: para #: boot-installer.xml:1171 #, 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 "" "Hvis, af en eller anden årsag, indstilling 1 ikke lykkes, så genstart " "maskinen og når skærmen for EFI-opstartshåndteringen vises, bør der være en " "indstilling kaldt EFI Shell [Built-in]. Start &debian;-" "installations-cd'en med de følgende trin:" #. Tag: para #: boot-installer.xml:1182 #, 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 "" "Indsæt cd'en i dvd/cd-drevet og genstart maskinen. Firmwaren vil vise siden " "og menuen for EFI-opstartshåndteringen efter, at den er færdig med " "systeminitialiseringen." #. Tag: para #: boot-installer.xml:1188 #, 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ælg EFI Shell fra menuen med piletastesrne og tryk " "RETUR. EFI-skallen vil skanne alle enheder, der kan " "startes op fra, og vise dem for konsollen før den viser sin kommandoprompt." "De genkendte opstartspartitioner på enheder vi vise et enhedsnavn på " "fsn:. Alle andre genkendte " "partitioner vil blive navngivet blkn:. Hvis du indsættede cd'en lige før du indtastede skallen, så kan " "dette tage nogle få ekstra sekunder, da den initialiserer c-drevet." #. Tag: para #: boot-installer.xml:1202 #, 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øg resultatet fra skallen til du finder cd-rom-drevet. Det er højst " "sandsynlig enheden fs0: selvom andre enheder med " "opstartspartitioner også vil blive vist som fsn." #. Tag: para #: boot-installer.xml:1209 #, 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 "" "Indtast fsn: og tryk " "RETUR for at vælge den enhed hvor n er partitionsnummeret for cd'rommen. Skallen vil nu vise " "partitionsnummeret som sin prompt." #. Tag: para #: boot-installer.xml:1216 #, no-c-format msgid "" "Enter elilo and press ENTER. This will " "start the boot load sequence." msgstr "" "Indtast elilo og tryk RETUR. Dette vil " "igangsætte opstartssekvensen." #. Tag: para #: boot-installer.xml:1223 #, 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 ved indstilling 1, igangsætter disse trin &debian;-opstartsindlæseren, " "som vil vise en menuside, hvor du kan vælge en opstartskerne og " "indstillinger. Du kan også indtaste den kortere kommando " "fsn:elilo på skalprompten. " "Fortsæt for at vælge opstartskernen og indstillinger." #. Tag: title #: boot-installer.xml:1237 #, no-c-format msgid "Installing using a Serial Console" msgstr "Installation med en seriel konsol" #. Tag: para #: boot-installer.xml:1239 #, 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ælge at udføre en installation med en skærm og tastatur eller med " "brug af en seriel forbindelse. For at bruge en opsætning for skærm/tastatur, " "så vælg en indstilling, der indeholder strengen [VGA console]. For at " "installere over en seriel forbindelse, så vælg en instilling der indeholder " "strengen [BAUD baud serial console], hvor " "BAUD er hastigheden for din serielle konsol. " "Menupunkter for de typiske indstillinger for baudhastigheder på ttyS0-" "enheden er prækonfigurerede." #. Tag: para #: boot-installer.xml:1250 #, 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 fleste tilfælde vil du ønske at installationsprogrammet skal bruge den " "samme baudhastighed som din forbindelse til EFI-konsollen. Hvis du ikke er " "sikker på hvad denne indstilling er sat til, så kan du indhente denne " "oplysning med kommandoen baud via EFI-skallen." #. Tag: para #: boot-installer.xml:1257 #, 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 "" "Hvis der ikke er en indstilling tilgængelig, som er konfigureret for den " "serielle enhed eller baudhastighed, du ønsker at bruge, så kan du overskrive " "konsolindstillingen for en af de eksisterende menuindstillinger. For " "eksempel: For at bruge 57600 baud-konsol over ttyS1-enheden så indtast " "console=ttyS1,57600n8 i tekstvinduet Boot:." #. Tag: para #: boot-installer.xml:1268 #, 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 fleste IA-64-bokse leveres med en standardindstilling for konsollen på " "9600 baud. Denne indstilling er ret langsom, og den normale " "installationsproces vil bruge lang tid på at tegne hver skærm. Du bør " "overveje enten at øge baudhastigheden brugt for udførelse af installationen " "eller udføre en installation i teksttilstand. Se hjælpemenuen " "Params for instruktioner på opstart af " "installationsprogrammet i teksttilstand." #. Tag: para #: boot-installer.xml:1277 #, 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 "" "Hvis du vælger den forkerte konsoltype, vil du kunne vælge kernen og " "indtaste parametre, men både skærmen og dine indtastninger vil gå tabt så " "snart at kernen starter, hvilket kræver at du genstarter, før du kan begynde " "installationen." #. Tag: title #: boot-installer.xml:1286 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "Valg af opstartskernen og indstillinger" #. Tag: para #: boot-installer.xml:1288 #, 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 "" "Opstartsindlæseren vil vise en formular med en menuliste og et tekstvindue " "med en Boot:-prompt. Piletasterne vælger et punkt fra " "menuen og eventuel tekst indtastet på tastaturet vil blive vist i " "tekstvinduet. Der er også hjælpevinduer, som kan vises ved at trykke på den " "passende funktionstast. Hjælpevinduet General " "forklarer menuvalgene og vinduet Params forklarer de " "gængse indstillinger for kommandolinjen." #. Tag: para #: boot-installer.xml:1300 #, 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 "" "Se hjælpevinduet General for beskrivelse af kernerne " "og installationstilstandene som bedst passer for din installation. Du bør " "også konsultere nedenfor for yderligere " "parametre, du ønsker at angive i tekstvinduet Boot:. " "Kerneversionen du vælger udvælger kerneversionen som vil blive brugt både " "for installationsprocessen og det installerede system. Hvis du møder " "kerneproblemer med installationen, kan du også have de samme problemer med " "systemet du installerer. De følgende to trin vil vælge og starte " "installationen:" #. Tag: para #: boot-installer.xml:1318 #, no-c-format msgid "" "Select the kernel version and installation mode most appropriate to your " "needs with the arrow keys." msgstr "" "Vælg kerneversion og installationstilstand der bedst passer til dine behov " "med piletasterne." #. Tag: para #: boot-installer.xml:1323 #, 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 "" "Indtast eventuelle opstartsparametre med tastaturet. Teksten vil blive vist " "direkte i tekstvinduet. Det er her at kerneparametre (såsom indstillinger " "for seriel konsol) specificeres." #. Tag: para #: boot-installer.xml:1330 #, 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 "" "Tryk RETUR. Dette vil indlæse og starte kernen. Kernen " "vil vise dets normale initialiseringsbeskeder efterfulgt af den første skærm " "for &debian;-installationsprogrammet." #. Tag: para #: boot-installer.xml:1339 boot-installer.xml:1476 #, 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æt til det næste kapitel for at fortsætte installationen hvor du vil " "opsætte sprogområdet, netværk og diskpartitioner." #. Tag: para #: boot-installer.xml:1350 #, no-c-format msgid "" "Booting an IA-64 system from the network is similar to a CD boot. The only " "difference is how the installation kernel is loaded. The EFI Boot Manager " "can load and start programs from a server on the network. Once the " "installation kernel is loaded and starts, the system install will proceed " "through the same steps as the CD install with the exception that the " "packages of the base install will be loaded from the network rather than the " "CD drive." msgstr "" "Opstart af et IA-64-system fra netværket ligner en cd-opstart. Den eneste " "forskel er hvordan installationskernen indlæses. EFI-opstartshåndteringen " "kan indlæse og starte programmer fra en server på netværket. Når først " "installationskernen er indlæst og starter, vil systeminstallationen " "fortsætte igennem de samme trin som cd-installationen med den undtagelse at " "pakkerne for grundinstallationen vil blive indlæst fra netværket fremfor fra " "cd-drevet." #. Tag: para #: boot-installer.xml:1385 #, no-c-format msgid "" "Network booting an IA-64 system requires two architecture-specific actions. " "On the boot server, DHCP and TFTP must be configured to deliver " "elilo. On the client a new boot option must be defined in " "the EFI boot manager to enable loading over a network." msgstr "" "Netværksopstart af et IA-64-system kræver to arkitekturspecifikke " "handlinger. På opstartsserveren skal DHCP og TFTP være konfigureret til at " "levere elilo. På klienten skal en ny opstartsindstilling " "være defineret i EFI-opstartshåndteringen for at aktivere indlæsning over et " "netværk." #. Tag: title #: boot-installer.xml:1396 #, no-c-format msgid "Configuring the Server" msgstr "Konfiguration af serveren" #. Tag: para #: boot-installer.xml:1397 #, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 system looks something " "like this: \n" "host mcmuffin {\n" " hardware ethernet 00:30:6e:1e:0e:83;\n" " fixed-address 10.0.0.21;\n" " filename \"debian-installer/ia64/elilo.efi\";\n" "}\n" " Note that the goal is to get elilo.efi running on the client." msgstr "" "Et egnet TFTP-punkt for netværksopstart af et IA-64-system kan se således " "ud: \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" " Bemærk at formålet er at få elilo.efi til at køre på klienten." #. Tag: para #: boot-installer.xml:1407 #, 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 "" "Udtræk filen netboot.tar.gz til mappen brugt som root " "for din tftp-server. Typiske tftp-rootmapper inkluderer /var/lib/" "tftp og /tftpboot. Dette vil oprettet et " "mappetræ for debian-installer, der indeholder " "opstartsfilerne for et IA-64-system." #. Tag: screen #: boot-installer.xml:1417 #, no-c-format msgid "" "# cd /var/lib/tftp\n" "# tar xvfz /home/user/netboot.tar.gz\n" "./\n" "./debian-installer/\n" "./debian-installer/ia64/\n" "[...]" msgstr "" "# cd /var/lib/tftp\n" "# tar xvfz /home/user/netboot.tar.gz\n" "./\n" "./debian-installer/\n" "./debian-installer/ia64/\n" "[...]" #. Tag: para #: boot-installer.xml:1417 #, 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 "" "netboot.tar.gz indeholder en fil elilo.conf som bør virke med de fleste konfigurationer. Har du brug for " "ændringer i denne fil, så kan du finde den i mappen debian-" "installer/ia64/. Det er muligt at have forskellige " "konfigurationsfiler for forskellige klienter ved at navngive dem med " "klientens IP-adresse i hex med filendelsen .conf i " "stedet for elilo.conf. Se dokumentationen tilbudt i " "pakken elilo for detaljer." #. Tag: title #: boot-installer.xml:1434 #, no-c-format msgid "Configuring the Client" msgstr "Konfiguration af klienten" #. Tag: para #: boot-installer.xml:1435 #, 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 "" "For at konfigurere klienten til at understøtte TFTP-opstart, så begynd med " "at starte op i EFI og gå ind i Boot Option Maintenance Menu. Add a boot option. Du bør se en eller flere linjer med teksten " "Load File [Acpi()/.../Mac()]. Hvis mere end en af " "disse punkter findes, så vælg den der indeholder MAC-adressen for " "grænsefladen hvorfra du starter op. Brug piletasterne til at fremhæve dit " "valg, tryk retur. Name the entry " "Netboot eller noget lignende, gem og afslut tilbage " "til menuen for opstartsindstillingerne. " "Du bør se den nye opstartsindstilling du netop har oprettet, og valg af den " "bør initiere en DHCP-forespørgsel, der fører til en TFTP-indlæsning af " "elilo.efi fra serveren." #. Tag: para #: boot-installer.xml:1467 #, 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 "" "Opstartsindlæseren vil vise sin prompt efter at den har hentet og behandlet " "dens konfigurationsfil. På dette tidspunkt fortsætter installationen med de " "samme trin som ved en cd-installation. Vælg en opstartsindstilling som i " "ovenstående og når kernen har færddiggjort installation af sig selv fra " "netværket, vil den starte &debian;-installationsprogrammet." #. Tag: title #: boot-installer.xml:1521 #, no-c-format msgid "S/390 Limitations" msgstr "S/390-begrænsninger" #. Tag: para #: boot-installer.xml:1522 #, no-c-format msgid "" "In order to run the installation system a working network setup and ssh " "session is needed on S/390." msgstr "" "For at køre installationssystemet er en fungerende netværksopsætning og ssh-" "session krævet på S/390." #. Tag: para #: boot-installer.xml:1527 #, 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 "" "Opstartsprocessen starter med en netværksopsætning, som anmoder dig om flere " "netværksparametre. Hvis opsætningen er succesfuld, vil du logge ind på " "systemet ved at starte en ssh-session, som vil igangsætte " "standardinstallationssystemet." #. Tag: title #: boot-installer.xml:1538 #, no-c-format msgid "S/390 Boot Parameters" msgstr "S/390-opstartsparametre" #. Tag: para #: boot-installer.xml:1539 #, no-c-format msgid "" "On S/390 you can append boot parameters in the parm file. This file can " "either be in ASCII or EBCDIC format. It needs to be fixed-width with 80 " "characters per line. A sample parm file parmfile.debian " "is provided with the installation images. If a parameter is too long to fit " "into the 80 characters limit it can simply be continued in the first column " "of the next line. All the lines are concatenated without spaces when being " "passed to the kernel." msgstr "" "På S/390 kan du tilføje opstartsparametre i parm-filen. Denne fil kan enten " "være i ASCII- eller EBCDIC-format. Den skal have en fast bredde på 80 tegn " "per linje. Et eksempel på en sådan parm-fil parmfile.debian følger med installationsaftrykket. Hvis en parameter er for lang " "til 80-tegnsbegrænsningen, så kan den fortsættes i den første kolonne på den " "næste linje. Alle linjerne sammenkædes uden mellemrum når de sendes til " "kernen." #. Tag: para #: boot-installer.xml:1556 #, no-c-format msgid "" "If you boot the installer in a logical partition (LPAR) or virtual machine " "(VM) where a lot of devices are visible, you can instruct the kernel to " "restrict the list to a fixed set of devices. This is advised for the " "installer's boot process if a lot of disks are visible, most likely in LPAR " "mode. The cio_ignore option supports both a blacklist (to " "only disallow a few devices) and a whitelist (to only allow specific " "devices): \n" " # blacklist: just ignore the two devices 300 and 301\n" " cio_ignore=0.0.0300-0.0.0301\n" " # whitelist: ignore everything but 1150, FD00, FD01 and FD02\n" " cio_ignore=all,!0.0.1150,!0.0.fd00-0.0.fd02\n" " Please note that all devices numbers' hex digits " "need to be specified in lower case. Furthermore if this boot parameter is " "used all devices need to be listed: this includes at least disks, network " "devices and the console. To be considered during the installer's boot " "process the above option needs to be added to parmfile.debian." msgstr "" "Hvis du igangsætter installationsprogrammet i en logisk partition (LPAR) " "eller virtuel maskine (VM) hvor en masse enheder er synlige, så kan du " "instruere kernen til at begrænse listen til et bestemt sæt af enheder. Dette " "anbefales for installationsprogrammets opstartsproces, hvis en masse diske " "er synlige, højst sandsynlig i LPAR-tilstand. Tilvalget cio_ignore understøtter både en sortliste (for kun at deaktivere nogle få " "enheder) og en hvidliste (for kun at tillade specifikke enheder): " "\n" " # blacklist: ignorer de to enheder 300 og 301\n" " cio_ignore=0.0.0300-0.0.0301\n" " # whitelist: ignorer alt undtagen 1150, FD00, FD01 og FD02\n" " cio_ignore=all,!0.0.1150,!0.0.fd00-0.0.fd02\n" " Bemærk venligst at alle enhedsnumres hex-numre " "skal angives med små bogstaver. Derudover skal alle enheder vises, såfremt " "opstartsparameteren bruges: Dette inkluderer mindst diske, netværksenheder " "og konsollen. For at blive overvejet under installationsprogrammets " "opstartsproces skal den ovenstående indstilling tilføjes til " "parmfile.debian." #. Tag: title #: boot-installer.xml:1841 #, no-c-format msgid "Booting a ppc64el machine" msgstr "Opstart af en ppc64el-maskine" #. Tag: para #: boot-installer.xml:1842 #, no-c-format msgid "How to boot a ppc64el machine:" msgstr "Sådan startes en ppc64el-maskine op:" #. Tag: title #: boot-installer.xml:1848 #, no-c-format msgid "Petitboot" msgstr "Petitboot" #. Tag: para #: boot-installer.xml:1849 #, no-c-format msgid "" "Petitboot is a platform independent bootloader based on the Linux kexec. " "Petitboot supports loading kernel, initrd and device tree files from any " "Linux mountable filesystem, plus can load files from the network using the " "FTP, SFTP, TFTP, NFS, HTTP and HTTPS protocols. Petitboot can boot any " "operating system that includes kexec boot support." msgstr "" "Petitboot er en opstartsindlæser, der er uafhængig af platform, baseret på " "Linux kexec. Petitboot understøtter indlæsning af kerne, initrd og " "enhedstræfiler fra ethvert Linuxmonterbart filsystem, samt kan indlæse filer " "fra netværket via protokollerne FTP, SFTP, TFTP, NFS, HTTP og HTTPS. " "Petitboot kan starte ethvert operativsystem op, som inkluderer kexec-" "opstartsunderstøttelse." #. Tag: para #: boot-installer.xml:1857 #, no-c-format msgid "" "Petitboot looks for bootloader configuration files on mountable devices in " "the system, and can also be configured to use boot information from a DHCP " "server." msgstr "" "Petitboot kigger efter konfigurationsfiler for opstartsindlæseren på " "monterbare enheder i systemet, og kan også konfigureres til at bruge " "opstartsinformation fra en DHCP-server." #. Tag: para #: boot-installer.xml:1908 #, no-c-format msgid "" "On machines with OpenBoot, simply enter the boot monitor on the machine " "which is being installed (see ). Use " "the command boot net to boot from a TFTP and RARP " "server, or try boot net:bootp or boot net:" "dhcp to boot from a TFTP and BOOTP or DHCP server. You can pass " "extra boot parameters to &d-i; at the end of the boot " "command." msgstr "" "På maskiner med OpenBoot, så indtast opstartsskærmen for maskinen som der " "installeres på (se ). brug kommandoen " "boot net til at starte op med fra en TFTP- og RARP-" "server, eller prøv boot net:bootp eller " "boot net:dhcp til at starte op fra en TFTP- og BOOTP- " "eller DHCP-server. Du kan sende ekstra opstartsparametre til &d-i; i " "slutningen af kommandoen boot." #. Tag: para #: boot-installer.xml:1962 #, no-c-format msgid "" "Most OpenBoot versions support the boot cdrom command " "which is simply an alias to boot from the SCSI device on ID 6 (or the " "secondary master for IDE based systems)." msgstr "" "De fleste OpenBoot-versioner understøtter kommandoen boot cdrom, hvilket kun er et alias for at starte fra SCSI-enheden på ID 6 " "(eller den sekundære master for IDE-baserede systemer)." #. Tag: title #: boot-installer.xml:1971 #, no-c-format msgid "IDPROM Messages" msgstr "IDPROM-beskeder" #. Tag: para #: boot-installer.xml:1972 #, 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 "" "Hvis du ikke kan starte op fordi du får beskeder om et problem med " "IDPROM, så er det muligt at dit NVRAM-batteri, som indeholder " "konfigurationsinformation for din firmware er løbet tør. se Sun NVRAM OSS for yderligere information." #. Tag: title #: boot-installer.xml:1991 #, no-c-format msgid "Accessibility" msgstr "Tilgængelighed" #. Tag: para #: boot-installer.xml:1992 #, no-c-format msgid "" "Some users may need specific support because of e.g. some visual impairment. " "USB braille displays are detected " "automatically (not serial displays connected via a serial-to-USB converter), " "but most other Most accessibility features have to be enabled manually. On machines that support it, the boot menu emits beeps when it " "is ready to receive keystrokes. It beeps once on BIOS systems, and beeps " "twice on UEFI systems. Some boot parameters can then be appended to enable accessibility features (see also ). Note that " "on most architectures the boot loader interprets your keyboard as a QWERTY " "keyboard." msgstr "" "Nogle brugere kan have brug for specifik understøtelse, f.eks. på grund af " "en synshæmmelse. USB-brailleskærme " "detekteres automatisk (ikke serielle skærme forbundet via en seriel-til-USB-" "konvertering), men de fleste andre De fleste funktioner for tilgængelighed " "skal aktiveres manuelt. På maskiner som understøtter " "det, så afgiver opstartsmenuen en biplyd når den er klar til at modtage " "tastaturtryk. Nogle opstartsparametre kan tilføjes for at aktivere tilgængelighedsfunktioner (se også ). Bemærk at på de " "fleste arkitekturer fortolker opstartsindlæseren dit tastatur som et QERTY-" "tastatur." #. Tag: title #: boot-installer.xml:2012 #, no-c-format msgid "Installer front-end" msgstr "Installationsprogrammets brugerflade" #. Tag: para #: boot-installer.xml:2013 #, no-c-format msgid "" "The &debian; installer supports several front-ends for asking questions, " "with varying convenience for accessibility: notably, text uses plain text while newt uses text-based " "dialog boxes. The choice can be made at the boot prompt, see the " "documentation for DEBIAN_FRONTEND in ." msgstr "" "&debian;-installationsprogrammet understøtter flere brugerflader til " "spørgsmål, med varierende tilgængelighed: text bruger " "ren tekst mens newt bruger tekstbaserede dialogbokse. " "Valget kan foretages på opstartsprompten, se dokumentationen for " "DEBIAN_FRONTEND i ." #. Tag: title #: boot-installer.xml:2025 #, no-c-format msgid "USB Braille Displays" msgstr "USB-brailleskærme" #. Tag: para #: boot-installer.xml:2026 #, no-c-format msgid "" "USB braille displays should be automatically detected. A textual version of " "the installer will then be automatically selected, and support for the " "braille display will be automatically installed on the target system. You " "can thus just press &enterkey; at the boot menu. Once brltty is started, you can choose a braille table by entering the " "preference menu. Documentation on key bindings for braille devices is " "available on the brltty website." msgstr "" "USB-brailleskærme bør detekteres automatisk. En tekstversion af " "installationsprogrammet vil så blive valgt automatisk og understøttelse for " "brailleskærmen vil automatisk blive installeret på målsystemet. Du kan så " "bare trykke på &enterkey; ved opstartsmenuen. Når brltty er startet, så kan du vælge en brailletabel ved at indtaste " "præferencemenuen. Dokumentation for genvejstaster til brailleenheder er " "tilgængelige på brltty hjemmesiden." #. Tag: title #: boot-installer.xml:2041 #, no-c-format msgid "Serial Braille Displays" msgstr "Serielle brailleskærme" #. Tag: para #: boot-installer.xml:2042 #, no-c-format msgid "" "Serial braille displays cannot safely be automatically detected (since that " "may damage some of them). You thus need to append the " "brltty=driver,port boot parameter to tell brltty which driver and port it should use. driver should be replaced by the two-letter driver code for your " "terminal (see the BRLTTY manual). " "port should be replaced by the name of the serial " "port the display is connected to, ttyS0 is the " "default, ttyUSB0 can be typically used when using a " "serial-to-USB converter. A third parameter can be provided, to choose the " "name of the braille table to be used (see the BRLTTY manual); the English table is the default. Note " "that the table can be changed later by entering the preference menu. A " "fourth parameter can be provided to pass parameters to the braille driver, " "such as protocol=foo which is needed for some rare " "models. Documentation on key bindings for braille devices is available on " "the brltty " "website." msgstr "" "Serielle brailleskærme kan ikke automatisk registreres på en sikker måde (da " "det kan ødelægge nogle af dem). Du skal derfor tilføje opstartsparameteren " "brltty=driver,port,table for at fortælle " "brltty hvilken driver og port den skal bruge. " "driver skal erstattes af driverkoden i to " "bogstaver for din terminal (se BRLTTY-" "manualen). port skal erstattes af navnet " "for den serielle port skærmen er forbundet til, ttyS0 " "er standarden, ttyUSB0 kan typisk bruges når der " "bruges et seriel-til-USB-konverteringsprogram. En tredje paramter kan " "angives, for at vælge navnet for brailletabellen (se BRLTTY-manualen); den engelske tabel er standarden. " "Bemærk at tabellen kan ændres senere ved at indtaste præferencemenuen. En " "fjerde parameter kan angives for at sende parametre til brailledriveren, " "såsom protocol=foo hvilket er krævet for nogle " "sjældne modeller. Dokumentation vedrørende genvejstaster for brailleenheder " "er tilgængelig på brltty-hjemmesiden." #. Tag: title #: boot-installer.xml:2069 boot-installer.xml:3061 #, no-c-format msgid "Software Speech Synthesis" msgstr "Understøttelse af talesyntese via programmer" #. Tag: para #: boot-installer.xml:2070 #, no-c-format msgid "" "Support for software speech synthesis is available on all installer images " "which have the graphical installer, i.e. all netinst, CD and DVD images, and " "the netboot gtk variant. It can be activated by selecting it in the boot " "menu by typing s &enterkey;. The textual version of " "the installer will then be automatically selected, and support for software " "speech synthesis will be automatically installed on the target system." msgstr "" "Understøttelse for talesyntese via et program er tilgængelig på alle " "installationsaftryk, som har det grafiske installationsprogram, dvs. alle " "netinst-, cd- og dvd-aftryk, og netboot gtk-varianten. Den kan aktiveres ved " "at vælge den i opstartsmenuen ved at taste s " "&enterkey;. Den tekstmæssige version af installationsprogrammet vil så blive " "valgt automatisk og understøttelse for talesyntese via et program vil blive " "installeret automatisk på målsystemet." #. Tag: para #: boot-installer.xml:2079 #, no-c-format msgid "" "If several sound cards are detected, you will be prompted to press " "&enterkey; when you hear speech from the desired sound card." msgstr "" #. Tag: para #: boot-installer.xml:2084 #, no-c-format msgid "" "The first question (language) is spoken in english, and the remainder of " "installation is spoken in the selected language (if available in " "espeak)." msgstr "" "Det første spørgsmål (sprog) stilles på engelsk, resten af installationen " "udtales med det valgte sprog (hvis tilgængelig i espeak)." #. Tag: para #: boot-installer.xml:2090 #, no-c-format msgid "" "The default speech rate is quite slow. To make it faster, press " "CapsLock6. To make it " "slower, press CapsLock5. The default volume should be medium. To make it louder, press " "CapsLock2. To make it " "quieter, press CapsLock1. To get more details on the browsing shortcuts, see the Speakup guide. To just accept the default " "answer for a question, simply press Enter at the prompt. To " "provide an empty answer for a question, type ! at the " "prompt. To get back to the previous question, type < at the prompt." msgstr "" "Talehastigheden er som standard ret så langsom. For at gøre den hurtigere " "trykkes på CapsLock6. " "For at gøre den langsommere CapsLock5. Standardlydstyrken bør være mellem. For at gøre den " "højere CapsLock2. For " "at gøre den lavere CapsLock1. for at få flere detaljer om genvejstaster så se Opsætningsvejledningen. For bare at acceptere " "standardsvaret for et spørgsmål så tryk på Retur. For at " "angive et tomt svar for et spørgsmål tastes !. For at " "gå tilbage til det forrige spørgsmål tast <." #. Tag: title #: boot-installer.xml:2118 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "Understøttelse af talesyntese via udstyr" #. Tag: para #: boot-installer.xml:2119 #, no-c-format msgid "" "Support for hardware speech synthesis devices is available on all installer " "images which have the graphical installer, i.e. all netinst, CD and DVD " "images, and the netboot gtk variant. You thus need to select a " "Graphical install entry in the boot menu." msgstr "" "Understøttelse for talesyntese via udstyrsenheder er tilgængelig på alle " "installationsaftryk, som har det grafiske installationsprogram, d.v.s. alle " "netinst, cd- og dvd-aftryk, og netboot gtk-varianten. Du skal derfor vælge " "et punkt med Graphical install i opstartsmenuen." #. Tag: para #: boot-installer.xml:2126 #, no-c-format msgid "" "Hardware speech synthesis devices cannot be automatically detected. You thus " "need to append the speakup.synth=driver boot parameter to tell speakup which driver it should use. driver " "should be replaced by the driver code for your device (see driver code list). The textual version of the " "installer will then be automatically selected, and support for the speech " "synthesis device will be automatically installed on the target system." msgstr "" "Enheder for udstyrstalesyntese kan ikke automatisk detekteres. Du skal " "derfor tilføje opstartsparameteren speakup." "synth=driver for at fortælle " "speakup hvilken driver den skal bruge. " "driver skal erstattes af driverkoden for din " "enhed (se driverkodelisten). Den " "tekstmæssige udgave af installationsprogramemt vil så automatisk blive " "valgt, og understøttelse for talesynteseenheden vil automatisk blive " "installeret på målsystemet." #. Tag: title #: boot-installer.xml:2141 #, no-c-format msgid "Board Devices" msgstr "Bundkortenheder" #. Tag: para #: boot-installer.xml:2142 #, no-c-format msgid "" "Some accessibility devices are actual boards that are plugged inside the " "machine and that read text directly from the video memory. To get them to " "work framebuffer support must be disabled by using the vga=normal fb=false boot " "parameter. This will however reduce the number of available languages." msgstr "" "Nogle tilgængelighedsenheder er fysiske bundkort som er indsat i selve " "maskinen og som læser tekst direkte fra videohukommelsen. For at få dem til " "at virke skal understøttelse af framebuffer være deaktiveret ved at bruge " "opstartsparameteren vga=normal " "fb=false. Dette vil dog reducere antallet af " "tilgængelige sprog." #. Tag: para #: boot-installer.xml:2150 #, no-c-format msgid "" "If desired a textual version of the bootloader can be activated before " "adding the boot parameter by typing h &enterkey;." msgstr "" "Hvis det ønskes kan en tekstversion af opstartsindlæseren aktiveres før " "tilføjelse af opstartsparameteren ved at indtaste h " "&enterkey;." #. Tag: title #: boot-installer.xml:2158 #, no-c-format msgid "High-Contrast Theme" msgstr "Tema med høj kontrast" #. Tag: para #: boot-installer.xml:2159 #, fuzzy, no-c-format #| msgid "" #| "For users with low vision, the installer can use a high-contrast color " #| "theme that makes it more readable. To enable it, append the " #| "theme=dark boot parameter." msgid "" "For users with low vision, the installer can use a high-contrast color theme " "that makes it more readable. To enable it, you can use the Accessible " "high contrast entry from the boot screen with the d shortcut, or append the theme=dark boot " "parameter." msgstr "" "For brugere med nedsat syn, kan installationsprogrammet bruge et farvetema " "med høj kontrast, hvilket gør det nemmere at læse. For at aktivere tilføjes " "theme=dark til opstartsparameteren." #. Tag: title #: boot-installer.xml:2170 #, no-c-format msgid "Zoom" msgstr "Zoom" #. Tag: para #: boot-installer.xml:2171 #, no-c-format msgid "" "For users with low vision, the graphical installer has a very basic zoom " "support: the Control + and Control - shortcuts increase and decrease the font size." msgstr "" "For brugere med begrænset syn, har det grafiske installationsprogram en " "meget basal zoomunderstøttelse: Genvejstasterne Control + og Control " "- øger og sænker skriftstørrelsen." #. Tag: title #: boot-installer.xml:2181 #, no-c-format msgid "Expert install, rescue mode, automated install" msgstr "Ekspertinstallation, redningstilstand, automatiseret installation" #. Tag: para #: boot-installer.xml:2182 #, no-c-format msgid "" "Expert, Rescue, and Automated installation choices are also available with " "accessibility support. To access them, one has to first enter the " "Advanced options submenu from the boot menu by typing " "a. When using a BIOS system (the boot menu will have " "beeped only once), this has to be followed by &enterkey; ; for UEFI systems " "(the boot menu will have beeped twice) that must not be done. Then, to " "enable speech synthesis, s can optionally be pressed " "(followed again by &enterkey; on BIOS systems but not on UEFI systems). From " "there, various shortcuts can be used: x for expert " "installation, r for rescue mode, or a for automated installation. Again these need to be followed by " "&enterkey; when using a BIOS system." msgstr "" "Installationsvalgene for Ekspert, Redning og Automatisk er også tilgængelige " "med talesyntese. For at tilgå dem, skal man først gå til undermenuen " "Advanced options fra opstartsmenuen ved at taste " "a. Og så bruge et BIOS-system (opstartsmenuen vil kun " "have bippet en gang), dette skal efterfølges af &enterkey; ; for UEFI-" "systemer (opstartsmenuen vil have bippet to gange) som ikke skal gøres. " "Derefter, for at aktivere talesyntese, kan s valgfrit " "trykkes ned (efterfulgt af &enterkey; på BIOS-systemer men ikke på UEFI-" "systemer). Derfra kan forskellige genveje bruges: x " "for ekspertinstallation, r for redningstilstand, " "eller a for automatiseret installation. Når der " "bruges et BIOS-system, skal hvert af dem efterfølges af &enterkey;." #. Tag: para #: boot-installer.xml:2197 #, no-c-format msgid "" "The automated install choice allows to install &debian; completely " "automatically by using preseeding, whose source can be entered after " "accessibility features get started. Preseeding itself is documented in ." msgstr "" "Det automatiserede installationsvalg kan installere &debian; fuldstændig " "automatisk ved at bruge forhåndsindstillinger, hvis kilde kan indtastes " "efter tilgængelighedsfunktioner er startet. Forhåndsindstilling er " "dokumenteret i ." #. Tag: title #: boot-installer.xml:2207 #, no-c-format msgid "Accessibility of the installed system" msgstr "Tilgængelighed for det installerede system" #. Tag: para #: boot-installer.xml:2208 #, no-c-format msgid "" "Documentation on accessibility of the installed system is available on the " "Debian Accessibility wiki " "page." msgstr "" "Dokumentation vedrørende tilgængelighed for det installerede system er " "tilgængelig på Debians " "wikiside om tilgængelighed." #. Tag: title #: boot-installer.xml:2222 #, no-c-format msgid "Boot Parameters" msgstr "Opstartsparametre" #. Tag: para #: boot-installer.xml:2223 #, 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 "" "Opstartsparametre er parametre for Linuxkernen, som generelt bruges til at " "sikre at perifære enheder håndteres korrekt. I de fleste tilfælde kan kernen " "automatisk detektere information om dine perifære enheder. Dog skal du i " "nogle tilfælde hjælpe kernen lidt." #. Tag: para #: boot-installer.xml:2230 #, 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 "" "Hvis dette er den første gang du starter systemet op, så prøv " "standardparametrene for opstart (dvs. prøv uden at angive parametre) og se " "om det virker korrekt. Det vil det sikkert. Hvis ikke så kan du genstarte " "senere og kigge efter eventuelle specielle parametre som informerer dit " "system om dit udstyr." #. Tag: para #: boot-installer.xml:2237 #, 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 mange opstartsparametre kan findes i Linux BootPrompt HOWTO, " "inklusive fif for sjældent udstyr. Dette afsnit indeholder kun en skitse med " "de mest indlysende parametre. Nogle gængse problemstillinger er inkluderet " "nedenfor i ." #. Tag: title #: boot-installer.xml:2249 #, no-c-format msgid "Boot console" msgstr "Opstartskonsol" #. Tag: para #: boot-installer.xml:2251 #, fuzzy, no-c-format #| msgid "" #| "If you are booting with a serial console, generally the kernel will " #| "autodetect this. If you have a videocard (framebuffer) and a keyboard " #| "also attached to the computer which you wish to boot via serial console, " #| "you may have to pass the console=device argument to the kernel, where " #| "device is your serial device, which is usually " #| "something like ttyS0." msgid "" "If you are booting with a serial console, generally the kernel will " "autodetect this. If you have a videocard (framebuffer) and a keyboard also " "attached to the computer which you wish to boot via serial console, you may " "have to pass the console=device argument to the kernel, where device " "is a serial device of the target, which is usually something like " "ttyS0." msgstr "" "Hvis du starter op med en seriel konsol, vil kernen generelt detektere dette " "automatisk. Hvis du har et videokort (framebuffer) og et tastatur der også " "er tilsluttet computeren, som du ønsker at starte op via seriel konsol, så " "skal du måske sende argumentet console=device til kernen, hvor device " "er din seriel enhed, hvilket normalt ligner noget ala ttyS0." #. Tag: para #: boot-installer.xml:2263 #, no-c-format msgid "" "You may need to specify parameters for the serial port, such as speed and " "parity, for instance console=ttyS0,9600n8; other " "typical speeds may be 57600 or 115200. Be sure to specify this option after " "---, so that it is copied into the bootloader configuration " "for the installed system (if supported by the installer for the bootloader)." msgstr "" "Det kan være nødvendigt at angive parametre for den serielle port, såsom " "hastighed og paritet, for eksempel console=ttyS0,9600n8; andre typiske hastigheder kan være 57600 eller 115200. Vær " "opmærksom på at angive denne indstilling efter ---, så at den " "kopieres ind i opstartsindlæserens konfiguration for det installerede system " "(hvis understøttet af installationsprogrammet for opstartsindlæseren)." #. Tag: para #: boot-installer.xml:2271 #, no-c-format msgid "" "In order to ensure the terminal type used by the installer matches your " "terminal emulator, the parameter TERM=type can be added. Note that the installer only supports " "the following terminal types: linux, bterm, ansi, vt102 and " "dumb. The default for serial console in &d-i; is " "vt102. If you are using an IPMI console, or a " "virtualization tool which does not provide conversion into such terminals " "types itself, e.g. QEMU/KVM, you can start it inside a screen session. That will indeed perform translation into the " "screen terminal type, which is very close to " "vt102." msgstr "" "For at sikre at terminaltypen brugt af installationsprogrammet matcher din " "terminalemulator kan parameteren TERM=type tilføjes. Bemærk at installationsprogrammet kun " "understøtter de følgende terminaltyper: linux, " "bterm, ansi, vt102 " "og dumb. Standarden for seriel konsol i &d-i; er " "vt102. Hvis du bruger en IPMI-konsol eller et " "virtualiseringsværktøj, som ikke selv tilbyder konvertering til sådanne " "terminaltyper, f.eks. QEMU/KVM, så kan du starte den inden i en " "screen-session. Den vil udføre oversættelse til " "screen-terminaltypen, som er meget tæt på vt102." #. Tag: para #: boot-installer.xml:2287 #, 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 "" "For &arch-title; er serielenhederne ttya eller " "ttyb. Alternativt sættes OpenPROM-variablerne " "input-device og output-device til " "ttya." #. Tag: title #: boot-installer.xml:2299 #, no-c-format msgid "&debian; Installer Parameters" msgstr "Parametre for &debian;-installationsprogrammet" #. Tag: para #: boot-installer.xml:2300 #, 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. Also there is a limit of 255 characters for " "the whole kernel command line, everything above this limit may be silently " "truncated. which may be useful." msgstr "" "Installationssystemet genkender nogle få yderligere " "opstartsparametre med aktuelle kerner (2.6.9 eller nyere) " "kan du bruge 32 kommandolinjeindstillinger og 32 miljøindstillinger. Hvis " "disse tal overskrides går kernen i panik. Der er også en grænse på 255 tegn " "for hele kernekommandolinjen, alt over denne grænse kan blive afkortet. hvilket kan være nyttigt." #. Tag: para #: boot-installer.xml:2315 #, no-c-format msgid "" "A number of parameters have a short form that helps avoid the " "limitations of the kernel command line options and makes entering the " "parameters easier. If a parameter has a short form, it will be listed in " "brackets behind the (normal) long form. Examples in this manual will " "normally use the short form too." msgstr "" "Et antal parametre har en kort form som hjælper med at undgå " "begrænsningerne i kernens indstillinger for kommandolinjen og gør " "indtastning af parametre nemmere. Hvis en parameter har en kort form, så vil " "den blive vist i parenteser bag den (normale) lange form. Eksempler i denne " "manual vil normalt også bruge den korte form." #. Tag: term #: boot-installer.xml:2327 #, no-c-format msgid "debconf/priority (priority)" msgstr "debconf/priority (prioritet)" #. Tag: para #: boot-installer.xml:2328 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" "Denne parameter angiver den laveste prioritet beskeder kan have for at blive " "vist." #. Tag: para #: boot-installer.xml:2332 #, 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 bruger priority=high. Dette " "betyder at beskeder med både høj og kritisk prioritet bliver vist, mens " "beskeder med mellem og lav prioritet udelades. Hvis der opstår problemer, " "justerer installationsprogrammet prioriteten efter behov." #. Tag: para #: boot-installer.xml:2339 #, 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 "" "Hvis du tilføjer priority=medium som " "opstartsparameter, vil du få vist installationsmenuen og opnå yderligere " "kontrol over installationen. Når priority=low bruges, " "vises alle beskeder (dette svarer til opstartsmetoden expert. Med priority=critical vil " "installationssystemet kun vise kritiske beskeder og forsøge at udføre " "tingene korrekt uden hensyn til unødvendige detaljer." #. Tag: term #: boot-installer.xml:2353 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "DEBIAN_FRONTEND" #. Tag: para #: boot-installer.xml:2354 #, no-c-format msgid "" "This boot parameter controls the type of user interface used for the " "installer. The current possible parameter settings are: " " DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " "DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk " " The default frontend is " "DEBIAN_FRONTEND=newt. " "DEBIAN_FRONTEND=text may be preferable for serial " "console installs. Some specialized types of install media may only offer a " "limited selection of frontends, but the newt and " "text frontends are available on most default install " "media. On architectures that support it, the graphical installer uses the " "gtk frontend." msgstr "" "Denne opstartsparameter kontroller typen af brugergrænseflade brugt af " "installationsprogrammet. De aktuelt mulige parameterindstillinger er: " " DEBIAN_FRONTEND=noninteractive " "DEBIAN_FRONTEND=text DEBIAN_FRONTEND=newt " " DEBIAN_FRONTEND=gtk Standardbrugerfladen er " "DEBIAN_FRONTEND=newt. " "DEBIAN_FRONTEND=text kan foretrækkes for serielle " "konsolinstallationer. Nogle specialiserede typer af installationsmedier " "tilbyder måske kun et begrærset udvalg af brugerflader, men brugerfladerne " "newt og text er tilgængelige " "på de fleste gængse installationsmedier. På arkitekturer som understøtter " "det, bruger det grafiske installationsprogram brugerfladen gtk." #. Tag: term #: boot-installer.xml:2385 #, no-c-format msgid "BOOT_DEBUG" msgstr "BOOT_DEBUG" #. Tag: para #: boot-installer.xml:2386 #, 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 "" "Angivelse af denne opstartsparameter til 2 vil medføre at " "installationsprogrammets opstartsprogram bliver udførligt logget. " "Indstilligen 3 vil gøre fejlsøgningsskaller tilgængelige på strategiske " "steder i opstartsprocessen. (Afslut skallerne for at fortsætte " "opstartsprocessen.)" #. Tag: userinput #: boot-installer.xml:2395 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "BOOT_DEBUG=0" #. Tag: para #: boot-installer.xml:2396 #, no-c-format msgid "This is the default." msgstr "Dette er standarden." #. Tag: userinput #: boot-installer.xml:2400 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "BOOT_DEBUG=1" #. Tag: para #: boot-installer.xml:2401 #, no-c-format msgid "More verbose than usual." msgstr "Mere uddybende end normalt." #. Tag: userinput #: boot-installer.xml:2405 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "BOOT_DEBUG=2" #. Tag: para #: boot-installer.xml:2406 #, no-c-format msgid "Lots of debugging information." msgstr "Masser af fejlsøgningsinformation." #. Tag: userinput #: boot-installer.xml:2410 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "BOOT_DEBUG=3" #. Tag: para #: boot-installer.xml:2411 #, 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 "" "Skaller køres på forskellige steder i opstartsprocessen for at tillade " "detaljeret fejlsøgning. Afslut skallen for at fortsætte opstarten." #. Tag: term #: boot-installer.xml:2425 #, no-c-format msgid "log_host" msgstr "log_host" #. Tag: term #: boot-installer.xml:2426 #, no-c-format msgid "log_port" msgstr "log_port" #. Tag: para #: boot-installer.xml:2427 #, no-c-format msgid "" "Causes the installer to send log messages to a remote syslog on the " "specified host and port as well as to a local file. If not specified, the " "port defaults to the standard syslog port 514." msgstr "" "Får installationsprogrammet til at sende logbeskeder til en ekstern " "systemlog på den angivne vært og port samt til en lokal fil. Hvis ikke " "angivet, er portstandarden systemloggens standardport 514." #. Tag: term #: boot-installer.xml:2438 #, no-c-format msgid "lowmem" msgstr "lowmem" #. Tag: para #: boot-installer.xml:2439 #, no-c-format msgid "" "Can be used to force the installer to a lowmem level higher than the one the " "installer sets by default based on available memory. Possible values are 1 " "and 2. See also ." msgstr "" "Kan bruges til at tvinge installationsprogrammet til et lowmen-niveau højere " "end det installationsprogrammet sætter som standard baseret på tilgængelig " "hukommelse. Mulige værdier er 1 og 2. Se også ." #. Tag: term #: boot-installer.xml:2449 #, no-c-format msgid "noshell" msgstr "noshell" #. Tag: para #: boot-installer.xml:2450 #, no-c-format msgid "" "Prevents the installer from offering interactive shells on tty2 and tty3. " "Useful for unattended installations where physical security is limited." msgstr "" "Forhindrer installationsprogrammet i at tilbyder interaktive skaller på tty2 " "og tty3. Nyttig for installationer der ikke overvåges og hvor fysisk " "sikkerhed er begrænset." #. Tag: term #: boot-installer.xml:2459 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "debian-installer/framebuffer (fb)" #. Tag: para #: boot-installer.xml:2460 #, 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 using the parameter vga=normal fb=false. Problem symptoms are error " "messages about bterm or bogl, a blank screen, or a freeze within a few " "minutes after starting the install." msgstr "" "Nogle arkitekturer bruger kerneframebufferen til at tilbyder installation i " "et antal sprog. Hvis framebuffer medfører et problem på dit system, så kan " "du deaktivere funktionen med parameteren vga=normal fb=false. Symptomer på problemer er " "fejlbeskeder om bterm eller bogl, en blank skærm eller at installationen " "fryser efter et par minutter." #. Tag: para #: boot-installer.xml:2469 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "Disse problemer er blevet indrapporteret på hppa." #. Tag: para #: boot-installer.xml:2473 #, 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 af visningsproblemer på nogle systemer, så er understøttelse af " "framebuffer deaktiveret som standard for &arch-title;. " "Dette kan medføre visninger, der ikke er så kønne, på systemer som ikke " "korrekt understøtter framebufferen, såsom med ATI-grafikkort. Hvis du ser " "problemer i installationsprogrammet, så kan du prøve at starte med " "parameteren debian-installer/framebuffer=true eller " "fb=true i kort form." #. Tag: term #: boot-installer.xml:2487 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "debian-installer/theme (tema)" #. Tag: para #: boot-installer.xml:2488 #, fuzzy, no-c-format #| msgid "" #| "A theme determines how the user interface of the installer looks (colors, " #| "icons, etc.). What themes are available differs per frontend. Currently " #| "both the newt and gtk frontends only have a dark theme " #| "that was designed for visually impaired users. Set the theme by booting " #| "with theme=dark." msgid "" "A theme determines how the user interface of the installer looks (colors, " "icons, etc.). Which themes are available may differ per frontend. Currently " "both the newt and gtk frontend have (apart from the default look) only one " "additional theme named dark theme, which was designed for " "visually impaired users. Set this theme by booting with " "theme=dark (there is also " "the keyboard shortcut d for this in the boot menu)." msgstr "" "Et tema bestemmer hvordan brugergrænsefladen for installationsprogrammet ser " "ud (farver, ikoner etc.). Hvilke temaer der er tilgængelige afviger per " "brugerflade. Aktuelt har både newt- og gtk-brugerfladerne kun et " "dark-tema, som blev designet for de visuelt synshæmmede " "brugere. Angiv temaet ved at starte med theme=dark." #. Tag: term #: boot-installer.xml:2503 boot-installer.xml:2736 #, no-c-format msgid "netcfg/disable_autoconfig" msgstr "netcfg/disable_autoconfig" #. Tag: para #: boot-installer.xml:2504 #, no-c-format msgid "" "By default, the &d-i; automatically probes for network configuration via " "IPv6 autoconfiguration and DHCP. If the probe succeeds, you won't have a " "chance to review and change the obtained settings. You can get to the manual " "network setup only in case the automatic configuration fails." msgstr "" "Som standard vil &d-i; automatisk søge efter netværkskonfiguration via " "automatisk IPv6-konfiguration og DHCP. Hvis søgningen lykkes, vil du ikke få " "mulighed for at gennemse eller ændre de indhentede indstillinger. Du kan kun " "komme til manuel netværksopsætning den automatiske konfiguration mislykkes." #. Tag: para #: boot-installer.xml:2511 #, no-c-format msgid "" "If you have an IPv6 router or a DHCP server on your local network, but want " "to avoid them because e.g. they give wrong answers, you can use the " "parameter netcfg/disable_autoconfig=true to prevent " "any automatic configuration of the network (neither v4 nor v6) and to enter " "the information manually." msgstr "" "Hvis du har en IPv6-router eller en DHCP-server på dit lokale netværk, men " "ønsker at undgå den fordi den f.eks. giver forkerte svar, så kan du bruge " "parameteren netcfg/disable_autoconfig=true til at " "forhindre automatisk konfiguration af netværket (hverken v4 eller v6) og " "indtaste informationen manuelt." #. Tag: term #: boot-installer.xml:2522 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "hw-detect/start_pcmcia" #. Tag: para #: boot-installer.xml:2523 #, 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 "" "Sæt til false for at forhindre opstart af PCMCIA-" "tjenester, hvis dette medfører problemer. Nogle bærbare er kendt for denne " "opførsel." #. Tag: term #: boot-installer.xml:2533 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "disk-detect/dmraid/enable (dmraid)" #. Tag: para #: boot-installer.xml:2534 #, no-c-format msgid "" "Set to true to enable support for Serial ATA RAID " "(also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note " "that this support is currently experimental. Additional information can be " "found on the &debian; Installer Wiki." msgstr "" "Sæt til true for aktivere understøttelse for Serial " "ATA RAID-diske (også kaldt ATA RAID, BIOS RAID eller falsk RAID) i " "installationsprogrammet. Bemærk at denne understøttelse kun er " "eksperimentel. Yderligere information kan findes på &debian;-installationsprogrammets wiki." #. Tag: term #: boot-installer.xml:2545 #, no-c-format msgid "preseed/url (url)" msgstr "preseed/url (adresse)" #. Tag: para #: boot-installer.xml:2546 #, no-c-format msgid "" "Specify the url to a preconfiguration file to download and use for " "automating the install. See ." msgstr "" "Angiv adressen for en prækonfigurationsfil for at hente og bruge den for " "automatisering af installationen. Se ." #. Tag: term #: boot-installer.xml:2555 #, no-c-format msgid "preseed/file (file)" msgstr "preseed/file (fil)" #. Tag: para #: boot-installer.xml:2556 #, no-c-format msgid "" "Specify the path to a preconfiguration file to load for automating the " "install. See ." msgstr "" "Angiv stien til en forhåndskonfigurationsfil til indlæsning for " "automatisering af installationen. Se ." #. Tag: term #: boot-installer.xml:2565 #, no-c-format msgid "preseed/interactive" msgstr "preseed/interactive" #. Tag: para #: boot-installer.xml:2566 #, no-c-format msgid "" "Set to true to display questions even if they have " "been preseeded. Can be useful for testing or debugging a preconfiguration " "file. Note that this will have no effect on parameters that are passed as " "boot parameters, but for those a special syntax can be used. See for details." msgstr "" "Sæt til true for at vise spørgsmål selv hvis de er " "blevet forudfyldt. Kan være nyttig for test eller fejlsøgning af en " "forhåndskonfigureret fil. Bemærk at dette ikke vil have effekt på parametre " "som sendes som opstartsparametre, men for disse kan en speciel syntaks " "bruges. Se for detaljer." #. Tag: term #: boot-installer.xml:2578 #, no-c-format msgid "auto-install/enable (auto)" msgstr "auto-install/enable (auto)" #. Tag: para #: boot-installer.xml:2579 #, no-c-format msgid "" "Delay questions that are normally asked before preseeding is possible until " "after the network is configured. See for " "details about using this to automate installs." msgstr "" "Forsink spørgsmål som der normalt stilles før forudfyldning er muligt indtil " "efter at netværket er konfigureret. Se for " "detaljer om brugen af denne til automatisering af installationer." #. Tag: term #: boot-installer.xml:2590 #, no-c-format msgid "finish-install/keep-consoles" msgstr "finish-install/keep-consoles" #. Tag: para #: boot-installer.xml:2591 #, no-c-format msgid "" "During installations from serial or management console, the regular virtual " "consoles (VT1 to VT6) are normally disabled in /etc/inittab. Set to true to prevent this." msgstr "" "Under installationer fra seriel eller håndteringskonsol er de regulære " "virtuelle konsoller (VT1 til VT6) normalt deaktiveret i /etc/" "inittab. Sæt til true for at forhindre " "dette." #. Tag: term #: boot-installer.xml:2602 #, no-c-format msgid "cdrom-detect/eject" msgstr "cdrom-detect/eject" #. Tag: para #: boot-installer.xml:2603 #, fuzzy, 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." 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 such media. 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ør genstart, så skubber &d-i; automatisk det optiske medie " "ud, som blev brugt under installationen. Dette kan være unødvendigt, hvis " "systemet ikke automatisk starter op fra cd'en. I nogle tilfælde kan det " "endda være uønsket, for eksempel hvis det optiske drev ikke kan genindsætte " "mediet selv og hvis brugeren ikke er der til at gøre det manuelt. Mange slot-" "indlæsende og tynde drev samt drev i caddy-stil kan ikke genindlæse mediet " "automatisk." #. Tag: para #: boot-installer.xml:2612 #, 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 "" "Sæt til false for at deaktivere automatisk skub ud, " "og vær opmærksom på at du skal sikre at systemet ikke automtatisk starter op " "fra det optiske drev efter den oprindelige installation." #. Tag: term #: boot-installer.xml:2623 #, no-c-format msgid "base-installer/install-recommends (recommends)" msgstr "base-installer/install-recommends (anbefalinger)" #. Tag: para #: boot-installer.xml:2624 #, no-c-format msgid "" "By setting this option to false, the package " "management system will be configured to not automatically install " "Recommends, both during the installation and for the " "installed system. See also ." msgstr "" "Ved at angive denne indstilling til false, vil " "pakkehåndteringssystemet blive konfigureret til ikke automatisk at " "installere Recommends (anbefalinger), både under " "installationen og for det installerede system. Se også ." #. Tag: para #: boot-installer.xml:2631 #, no-c-format msgid "" "Note that this option allows to have a leaner system, but can also result in " "features being missing that you might normally expect to be available. You " "may have to manually install some of the recommended packages to obtain the " "full functionality you want. This option should therefore only be used by " "very experienced users." msgstr "" "Bemærk at denne indstilling giver et mindre omfattende system, men kan også " "resultere i at funktioner mangler, som du ellers normalt ville forvente var " "tilgængelige. Du skal måske installere nogle af de anbefalede pakker for at " "få den fulde funktionalitet. Denne indstilling bør derfor kun bruges af " "meget erfarne brugere." #. Tag: term #: boot-installer.xml:2643 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "debian-installer/allow_unauthenticated" #. Tag: para #: boot-installer.xml:2644 #, no-c-format msgid "" "By default the installer requires that repositories be authenticated using a " "known gpg key. Set to true to disable that " "authentication. Warning: insecure, not recommended." msgstr "" "Som standard kræver installationsprogrammet at arkiver godkendes med en " "kendt gpg-nøgle. Angiv som true (sand) for at " "deaktivere den godkendelse. Advarsel: usikker, kan " "ikke anbefales." #. Tag: term #: boot-installer.xml:2655 #, no-c-format msgid "ramdisk_size" msgstr "ramdisk_size" #. Tag: para #: boot-installer.xml:2656 #, no-c-format msgid "" "This parameter should already be set to a correct value where needed; set it " "only it you see errors during the boot that indicate the ramdisk could not " "be loaded completely. The value is in kB." msgstr "" "Denne parameter bør allerede være angivet til en korrekt værdi hvor krævet; " "angiv den kun hvis du ser fejl under opstarten som indikerer at ramdisk ikke " "kunne indlæses fuldt ud. Værdien er i kB." #. Tag: term #: boot-installer.xml:2666 #, no-c-format msgid "rescue/enable" msgstr "rescue/enable" #. Tag: para #: boot-installer.xml:2667 #, no-c-format msgid "" "Set to true to enter rescue mode rather than " "performing a normal installation. See ." msgstr "" "Angiv til true (sand) for at gå i redningstilstand " "fremfor at udføre en normal installation. Se ." #. Tag: title #: boot-installer.xml:2680 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "Brug af opstartsparametre til at besvare spørgsmål" #. Tag: para #: boot-installer.xml:2681 #, no-c-format msgid "" "With some exceptions, a value can be set at the boot prompt for any question " "asked during the installation, though this is only really useful in specific " "cases. General instructions how to do this can be found in . Some specific examples are listed below." msgstr "" "Med nogle undtagelser, kan en værdi angives ved opstartsprompten for " "spørgsmål stillet under installationen, dog er dette kun virkelig nyttigt i " "specifikke tilfælde. Generelle instruktioner om hvordan dette udføres kan " "findes i . Nogle specifikke eksempler " "vises nedenfor." #. Tag: term #: boot-installer.xml:2693 #, no-c-format msgid "debian-installer/language (language)" msgstr "debian-installer/language (sprog)" #. Tag: term #: boot-installer.xml:2694 #, no-c-format msgid "debian-installer/country (country)" msgstr "debian-installer/country (land)" #. Tag: term #: boot-installer.xml:2695 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "debian-installer/locale (sted)" #. Tag: para #: boot-installer.xml:2696 #, no-c-format msgid "" "There are two ways to specify the language, country and locale to use for " "the installation and the installed system." msgstr "" "Der er to måder at angive sproget på, land og sted at bruge for " "installationen og det installerede system." #. Tag: para #: boot-installer.xml:2701 #, no-c-format msgid "" "The first and easiest is to pass only the parameter locale. Language and country will then be derived from its value. You can " "for example use locale=de_CH to select German as " "language and Switzerland as country (de_CH.UTF-8 will be " "set as default locale for the installed system). Limitation is that not all " "possible combinations of language, country and locale can be achieved this " "way." msgstr "" "Den første og nemmeste måde er kun at sende parameteren locale. Sprog og land vil så blive udledt fra dens værdi. Du kan for " "eksempel bruge locale=de_CH til at vælge tysk som " "sprog og Schweitz som land (de_CH.UTF-8 vil blive angivet " "som standardsted for det installerede system). Begrænsningen er at ikke alle " "mulige kombinationer af sprog, land og sted kan opnås på denne måde." #. Tag: para #: boot-installer.xml:2710 #, no-c-format msgid "" "The second, more flexible option is to specify language " "and country separately. In this case locale can optionally be added to specify a specific default locale for " "the installed system. Example: language=en country=DE " "locale=en_GB.UTF-8." msgstr "" "Den anden, mere fleksible indstilling er at angive sprog " "og land adskilt. I dette tilfælde kan sted valgfrit tilføjes for at angive et specifikt standardsted for det " "installerede system. Eksempel: language=en country=DE " "locale=en_GB.UTF-8." #. Tag: term #: boot-installer.xml:2722 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "anna/choose_modules (moduler)" #. Tag: para #: boot-installer.xml:2723 #, no-c-format msgid "" "Can be used to automatically load installer components that are not loaded " "by default. Examples of optional components that may be useful are " "openssh-client-udeb (so you can use scp during the installation) and " "ppp-udeb (see )." msgstr "" "Kan bruges til automatisk at indlæse installationskomponenter, som ikke " "indlæses som standard. Eksempler på valgfrie komponenter, som kan være " "nyttige er openssh-client-udeb (så du kan bruge " "scp under installationen) og " "ppp-udeb (se )." #. Tag: para #: boot-installer.xml:2737 #, no-c-format msgid "" "Set to true if you want to disable IPv6 " "autoconfiguration and DHCP and instead force static network configuration." msgstr "" "Angiv som true (sand) hvis du ønsker at deaktivere " "automatisk IPv6-konfiguration og DHCP og i stedet for fremtvinge statisk " "netværkskonfiguration." #. Tag: term #: boot-installer.xml:2746 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "mirror/protocol (protokol)" #. Tag: para #: boot-installer.xml:2747 #, no-c-format msgid "" "By default the installer will use the http protocol to download files from " "&debian; mirrors and changing that to ftp is not possible during " "installations at normal priority. By setting this parameter to " "ftp, you can force the installer to use that protocol " "instead. Note that you cannot select an ftp mirror from a list, you have to " "enter the hostname manually." msgstr "" "Som standard vil installationsprogrammet bruge http-protokollen til at hente " "filer fra &debian;-spejle og ændring af dette til ftp er ikke muligt under " "installationer med normal prioritet. Ved at angive denne parameter til " "ftp, så kan du tvinge installationsprogrammet til at " "bruge den protokol i stedet for. Bemærk at du ikke kan vælge et ftp-spejl " "fra en liste, du skal indtaste værtsnavnet manuelt." #. Tag: term #: boot-installer.xml:2760 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "tasksel:tasksel/first (opgaver)" #. Tag: para #: boot-installer.xml:2761 #, no-c-format msgid "" "Can be used to select tasks that are not available from the interactive task " "list, such as the kde-desktop task. See for additional information." msgstr "" "Kan bruges til at vælge opgaver, som ikke er tilgængelige fra den " "interaktive opgaveliste, såsom opgaven kde-desktop. Se " " for yderligere information." #. Tag: title #: boot-installer.xml:2775 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "Sende parametre til kernemoduler" #. Tag: para #: boot-installer.xml:2776 #, 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 "" "Hvis drivere er kompileret ind i kernen, så kan du sende parametre til dem " "som beskrevet i kernedokumentationen. Dog er det ikke muligt at sende " "parametre til moduler, som du normalt ville gøre, hvis drivere er kompileret " "som moduler og fordi kernemoduler indlæses en smule anderledes under " "installation end under opstart fra et installeret system. I stedet skal du " "bruge en speciel syntaks der genkendes af installationsprogrammet, som så " "vil sikre at parametrene er gemt i de korrekte konfigurationsfiler og vil " "derfor blive brugt når modulerne rent faktisk indlæses. Parametrene vil også " "automatisk blive videregivet til konfigurationen for det installerede system." #. Tag: para #: boot-installer.xml:2789 #, 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 "" "Bemærk at det er ret sjældent at parametere skal sendes til moduler. I de " "fleste tilfælde vil kernen kunne finde frem til udstyret i et system og " "angive gode standarder via denne metode. I nogle situationer kan det dog " "være nødvendigt at angive parametre manuelt." #. Tag: para #: boot-installer.xml:2796 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: " "\n" "module_name.parameter_name=value\n" " If you need to pass multiple parameters to the " "same or different modules, just repeat this. For example, to set an old 3Com " "network interface card to use the BNC (coax) connector and IRQ 10, you would " "pass:" msgstr "" "Syntaksen for brug af modulparametre er: \n" "module_name.parameter_name=value\n" " Hvis du skal sende flere parametre til den samme " "eller forskellige moduler, så gentag bare dette. For eksmepel, for at angive " "at et gammelt 3Com-netværksgrænsefladekort skal bruge BNC-forbindelsen " "(coax) og IRQ 10, skal du skrive:" #. Tag: screen #: boot-installer.xml:2806 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "3c509.xcvr=3 3c509.irq=10" #. Tag: title #: boot-installer.xml:2812 #, no-c-format msgid "Blacklisting kernel modules" msgstr "Sortliste kernemoduler" #. Tag: para #: boot-installer.xml:2813 #, no-c-format msgid "" "Sometimes it may be necessary to blacklist a module to prevent it from being " "loaded automatically by the kernel and udev. One reason could be that a " "particular module causes problems with your hardware. The kernel also " "sometimes lists two different drivers for the same device. This can cause " "the device to not work correctly if the drivers conflict or if the wrong " "driver is loaded first." msgstr "" "Undertiden kan det være nødvendigt at sortliste et modul for at forhindre " "det i at blive indlæst automatisk af kernen og udev. En årsag kunne være at " "et specifik modul medfører problemer med dit udstyr. Kernen viser også " "undertiden to forskellige drivere for den samme enhed. Dette kan medføre at " "enheden ikke fungerer korrekt, hvis driverne er i konflikt eller hvis den " "forkerte driver indlæses først." #. Tag: para #: boot-installer.xml:2822 #, no-c-format msgid "" "You can blacklist a module using the following syntax: " "module_name.blacklist=yes. " "This will cause the module to be blacklisted in /etc/modprobe.d/" "blacklist.local both during the installation and for the " "installed system." msgstr "" "Du kan sortliste et modul med den følgende syntaks: " "modulnavn.blacklist=yes. " "Dette vil gøre, at modulet bliver sortlistet i /etc/modprobe.d/" "blacklist.local både under installationen og for det installerede " "system." #. Tag: para #: boot-installer.xml:2830 #, no-c-format msgid "" "Note that a module may still be loaded by the installation system itself. " "You can prevent that from happening by running the installation in expert " "mode and unselecting the module from the list of modules displayed during " "the hardware detection phases." msgstr "" "Bemærk at et modul stadig kan blive indlæst af selve installationssystemet. " "Du kan forhindre dette i at ske ved at køre installationen i eksperttilstand " "og fravælge modulet fra listen over moduler vist under detektionsfaserne for " "udstyret." #. Tag: title #: boot-installer.xml:2846 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "Fejlsøgning af installationsprocessen" #. Tag: title #: boot-installer.xml:2851 #, no-c-format msgid "Reliability of optical media" msgstr "" #. Tag: para #: boot-installer.xml:2852 #, fuzzy, 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." msgid "" "Sometimes, especially with older drives, the installer may fail to boot from " "an optical disc. The installer may also — even after booting " "successfully from such disc — fail to recognize the disc or return " "errors while reading from it during the installation." msgstr "" "Undertiden, specielt med ældre cd-rom-drev, vil installationsprogrammet " "fejle i at starte op fra en cd-rom. Installationsprogrammet kan også — " "selv efter opstart fra cd-rom — mislykkes i at genkende cd-rommen " "eller returnere fejl under læsning fra den under installationen." #. Tag: para #: boot-installer.xml:2859 #, no-c-format msgid "" "There are many different possible causes for these problems. We can only " "list some common issues and provide general suggestions on how to deal with " "them. The rest is up to you." msgstr "" "Der er mangle forskellige mulige årsager for disse problemer. Vi kan kun " "vise nogle gængse problemstillinger og tilbyde generelle forslag til hvordan " "du håndterer dem. Resten er op til dig." #. Tag: para #: boot-installer.xml:2865 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "Der er to meget simple metoder, du bør prøve først." #. Tag: para #: boot-installer.xml:2870 #, fuzzy, no-c-format #| msgid "" #| "If the CD-ROM does not boot, check that it was inserted correctly and " #| "that it is not dirty." msgid "" "If the disc does not boot, check that it was inserted correctly and that it " "is not dirty." msgstr "" "Hvis cd-rommen ikke starter op, så kontroller at disken er korrekt indsat og " "at den ikke er ridset eller beskidt." #. Tag: para #: boot-installer.xml:2876 #, fuzzy, no-c-format #| msgid "" #| "If the installer fails to recognize a CD-ROM, try just running the option " #| " Detect and mount CD-ROM a second time. Some DMA related issues with very old CD-ROM " #| "drives are known to be resolved in this way." msgid "" "If the installer fails to recognize the disc, try just running the option " " Detect and mount installation media " " a second time. Some DMA related issues with very old CD-ROM " "drives are known to be resolved in this way." msgstr "" "Hvis installationsprogrammet ikke kan genkende en cd-rom, så prøv at køre " "indstillingen Detekter og monter cd-rom endnu en gang. Nogle DMA-relaterede " "problemstillinger med meget gamle cd-rom-drev kan løses på denne måde." #. Tag: para #: boot-installer.xml:2886 #, fuzzy, 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." msgid "" "If this does not work, then try the suggestions in the subsections below. " "Most, but not all, suggestions discussed there are valid for CD-ROM and DVD." msgstr "" "Hvis dette ikke virker, så prøv forslagene i underafsnittene nedenfor. De " "fleste - men ikke alle - forslag diskuteret her er gyldige for både cd-rom " "og dvd, men vi bruger alene udtrykket cd-rom." #. Tag: para #: boot-installer.xml:2891 #, fuzzy, no-c-format #| msgid "" #| "If you cannot get the installation working from CD-ROM, try one of the " #| "other installation methods that are available." msgid "" "If you cannot get the installation working from optical disc, try one of the " "other installation methods that are available." msgstr "" "Hvis du ikke kan få installationen til at virke fra cd-rom, så prøv en af de " "andre tilgængelige installationsmetoder." #. Tag: title #: boot-installer.xml:2899 #, no-c-format msgid "Common issues" msgstr "Gængse problemstillinger" #. Tag: para #: boot-installer.xml:2902 #, 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 "" "Nogle ældre cd-rom-drev understøtter ikke læsning fra diske som blev brændt " "med høje hastigheder via et moderne cd-rom-drev." #. Tag: para #: boot-installer.xml:2919 #, no-c-format msgid "" "Some very old CD-ROM drives do not work correctly if direct memory " "access (DMA) is enabled for them." msgstr "" "Nogle meget gamle cd-rom-drev virker ikke korrekt hvis direct memory " "access (DMA) er aktiveret for dem." #. Tag: title #: boot-installer.xml:2930 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "Hvordan kan der undersøges og måske løses problemstillinger" #. Tag: para #: boot-installer.xml:2931 #, fuzzy, no-c-format #| msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgid "If the optical disc fails to boot, try the suggestions listed below." msgstr "" "Hvis cd-rom'en ikke starter op, så prøv anbefalingerne på listen nedenfor." #. Tag: para #: boot-installer.xml:2936 #, fuzzy, no-c-format #| msgid "" #| "Check that your BIOS actually supports booting from CD-ROM (only an issue " #| "for very old systems) and that CD booting is enabled in the BIOS." msgid "" "Check that your BIOS/UEFI actually supports booting from optical disc (only " "an issue for very old systems) and that booting from such media is enabled " "in the BIOS/UEFI." msgstr "" "Kontroller at din BIOS rent faktisk understøtter opstart fra cd-rom (kun en " "problemstilling for meget gamle systemer) og at cd-opstart er aktiveret i " "BIOS'en." #. Tag: para #: boot-installer.xml:2943 #, fuzzy, no-c-format #| msgid "" #| "If you downloaded an iso image, check that the md5sum of that image " #| "matches the one listed for the image in the MD5SUMS " #| "file that should be present in the same location as where you downloaded " #| "the image from. \n" #| "$ md5sum debian-testing-i386-netinst.iso\n" #| "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-" #| "netinst.iso\n" #| " Next, check that the md5sum of the burned CD-" #| "ROM matches as well. The following command should work. It uses the size " #| "of the image to read the correct number of bytes from the CD-ROM." msgid "" "If you downloaded an iso image, check that the md5sum of that image matches " "the one listed for the image in the MD5SUMS file that " "should be present in the same location as where you downloaded the image " "from. \n" "$ md5sum debian-testing-i386-netinst.iso\n" "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." "iso\n" " Next, check that the md5sum of the burned disc " "matches as well. The following command should work. It uses the size of the " "image to read the correct number of bytes from the disc." msgstr "" "Hvis du hentede et iso-aftryk, så kontroller at md5summen for det aftryk " "matcher det viste aftryk i filen MD5SUMS, som bør " "befinde sig samme sted, som du hentede aftrykket fra. " "\n" "$ md5sum debian-testing-i386-netinst.iso\n" "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." "iso\n" " Derefter kontrollerer du at md5summen for den " "brændte cd-rom også matcher. Den følgende kommando bør virke. Den bruger " "størrelsen for aftrykket til at læse det korrekte antal byte fra cd-rommen." #. Tag: screen #: boot-installer.xml:2956 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" "> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" "> md5sum\n" "a20391b12f7ff22ef705cee4059c6b92 -\n" "262668+0 records in\n" "262668+0 records out\n" "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" msgstr "" "> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" "> md5sum\n" "a20391b12f7ff22ef705cee4059c6b92 -\n" "262668+0 poster ind\n" "262668+0 poster ud\n" "134486016 byte (134 MB) kopieret, 97,474 sekunder, 1,4 MB/s" #. Tag: para #: boot-installer.xml:2961 #, fuzzy, no-c-format #| msgid "" #| "If, after the installer has been booted successfully, the CD-ROM is not " #| "detected, sometimes simply trying again may solve the problem. If you " #| "have more than one CD-ROM drive, try changing the CD-ROM to the other " #| "drive. If that does not work or if the CD-ROM is recognized but there are " #| "errors when reading from it, try the suggestions listed below. Some basic " #| "knowledge of &arch-kernel; is required for this. To execute any of the " #| "commands, you should first switch to the second virtual console (VT2) and " #| "activate the shell there." msgid "" "If, after the installer has been booted successfully, the disc is not " "detected, sometimes simply trying again may solve the problem. If you have " "more than one optical drive, try changing the disc to the other drive. If " "that does not work or if the disc is recognized but there are errors when " "reading from it, try the suggestions listed below. Some basic knowledge of " "&arch-kernel; is required for this. To execute any of the commands, you " "should first switch to the second virtual console (VT2) and activate the " "shell there." msgstr "" "Hvis, efter at installationsprogrammet er blevet korrekt startet, cd-rommen " "ikke detekteres, så kan det bare at prøve igen nogle gange løse problemet. " "Hvis du har mere end et cd-rom-drev, så prøv at indsætte disken i det andet " "drev. Hvis det ikke virker eller hvis diske genkendes men har fejl under " "læsning, så prøv forslagene nedenfor. Lidt grundlæggende viden om &arch-" "kernel; er krævet for dette. For at køre disse kommandoer, så skal du først " "skifte til den anden virtuelle konsol (VT2) og aktivere skallen der." #. Tag: para #: boot-installer.xml:2973 #, 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 "" "Skift til VT4 eller vis indholdet af /var/log/syslog " "(brug nano som redigeringsprogram) til at kontrollere " "efter specifikke fejlbeskeder. Derefter kontrolleres også resultatet af " "dmesg." #. Tag: para #: boot-installer.xml:2980 #, fuzzy, 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" #| "ata1.00: ATAPI: MATSHITADVD-RAM UJ-822S, 1.61, max UDMA/33\n" #| "ata1.00: configured for UDMA/33\n" #| "scsi 0:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-822S 1.61 PQ: 0 " #| "ANSI: 5\n" #| "sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray\n" #| "cdrom: Uniform CD-ROM driver Revision: 3.20\n" #| " If you don't see something like that, chances " #| "are the controller your CD-ROM is connected to was not recognized or may " #| "be not supported at all. If you know what driver is needed for the " #| "controller, you can try loading it manually using modprobe." msgid "" "Check in the output of dmesg if your optical drive was " "recognized. You should see something like (the lines do not necessarily have " "to be consecutive): \n" "ata1.00: ATAPI: MATSHITADVD-RAM UJ-822S, 1.61, max UDMA/33\n" "ata1.00: configured for UDMA/33\n" "scsi 0:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-822S 1.61 PQ: 0 ANSI: " "5\n" "sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray\n" "cdrom: Uniform CD-ROM driver Revision: 3.20\n" " If you don't see something like that, chances " "are the controller your drive is connected to was not recognized or may be " "not supported at all. If you know what driver is needed for the controller, " "you can try loading it manually using modprobe." msgstr "" "Kontroller i resultatet fra dmesg om dit cd-rom-drev blev " "genkendt. Du bør se noget ala (linjerne skal ikke nødvendigvis være " "fortløbende): \n" "ata1.00: ATAPI: MATSHITADVD-RAM UJ-822S, 1.61, max UDMA/33\n" "ata1.00: configured for UDMA/33\n" "scsi 0:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-822S 1.61 PQ: 0 ANSI: " "5\n" "sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray\n" "cdrom: Uniform CD-ROM driver Revision: 3.20\n" " Hvis du ikke ser noget der ligner eksemplet, er " "der en risiko for, at controlleren som dit cd-rom-drev er forbundet med ikke " "blev genkendt eller slet ikke er understøttet. Hvis du ved hvilken driver, " "der er krævet for controlleren, så kan du forsøge at indlæse den manuelt med " "modprobe." #. Tag: para #: boot-installer.xml:2994 #, fuzzy, 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/sr0. There should also be a /dev/cdrom." msgid "" "Check that there is a device node for your optical drive under /" "dev/. In the example above, this would be /dev/sr0. There should also be a /dev/cdrom." msgstr "" "Kontroller at der er en enhedsknude for dit cd-rom-drev under /dev/" ". I eksemplet ovenfor, skal dette være /dev/sr0. Der skal også være et /dev/cdrom." #. Tag: para #: boot-installer.xml:3002 #, fuzzy, no-c-format #| msgid "" #| "Use the mount command to check if the CD-ROM is " #| "already mounted; if not, try mounting it manually: " #| "\n" #| "$ mount /dev/hdc /cdrom\n" #| " Check if there are any error messages after " #| "that command." msgid "" "Use the mount command to check if the optical disc is " "already mounted; if not, try mounting it manually: " "\n" "$ mount /dev/hdc /cdrom\n" " Check if there are any error messages after that " "command." msgstr "" "Brug kommandoen mount til at kontrollere om cd-rommen " "allerede er monteret; hvis ikke, så prøv at montere den manuelt: " "\n" "$ mount /dev/hdc /cdrom\n" " Kontroller hvis der er nogle fejlbeskeder efter " "den kommando." #. Tag: para #: boot-installer.xml:3012 #, fuzzy, no-c-format #| msgid "" #| "Check if DMA is currently enabled: \n" #| "$ cd /proc/ide/hdc\n" #| "$ grep using_dma settings\n" #| "using_dma 1 0 1 rw\n" #| " A 1 in the first column after " #| "using_dma means it is enabled. If it is, try disabling " #| "it: \n" #| "$ echo -n \"using_dma:0\" >settings\n" #| " Make sure that you are in the directory for " #| "the device that corresponds to your CD-ROM drive." msgid "" "Check if DMA is currently enabled: \n" "$ cd /proc/ide/hdc\n" "$ grep using_dma settings\n" "using_dma 1 0 1 rw\n" " A 1 in the first column after " "using_dma means it is enabled. If it is, try disabling " "it: \n" "$ echo -n \"using_dma:0\" >settings\n" " Make sure that you are in the directory for the " "device that corresponds to your optical drive." msgstr "" "Kontroller hvis DMA er aktuelt aktiveret: \n" "$ cd /proc/ide/hdc\n" "$ grep using_dma settings\n" "using_dma 1 0 1 rw\n" " Et 1 i den første kolonne efter " "using_dma betyder at den er aktiveret. Hvis den er, så " "prøv at deaktivere den: \n" "$ echo -n \"using_dma:0\" >settings\n" " Sikr dig at du er i mappen for enheden som " "svarer til dit cd-rom-drev." #. Tag: para #: boot-installer.xml:3027 #, fuzzy, 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." msgid "" "If there are any problems during the installation, try checking the " "integrity of the installation media using the option near the bottom of the " "installer's main menu. This option can also be used as a general test if the " "disc can be read reliably." msgstr "" "Hvis der er problemer under installationen, så prøv at kontrollere " "integriteten for cd-rommen med indstillingen nær bunden af " "installationsprogrammets hovedmenu. Denne indstilling kan også bruges som en " "generel test af, om cd-rommen kan læses troværdigt." #. Tag: title #: boot-installer.xml:3041 #, no-c-format msgid "Boot Configuration" msgstr "Opstartskonfiguration" #. Tag: para #: boot-installer.xml:3043 #, 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 "" "Hvis du har problemer og kernen hænger under opstartsprocessen, ikke " "genkender perifære enheder du rent faktisk har, eller driverne ikke bliver " "genkendt korrekt, så er den første ting du skal gøre er at kontrollere " "opstartsparametrene, som omtalt i ." #. Tag: para #: boot-installer.xml:3052 #, no-c-format msgid "" "In some cases, malfunctions can be caused by missing device firmware (see " " and )." msgstr "" "I nogle tilfælde kan fejlsituationer opstå på grund af manglende firmware " "for udstyr (se og )." #. Tag: para #: boot-installer.xml:3063 #, no-c-format msgid "" "If software speech synthesis does not work, there is most probably an issue " "with your sound board, usually because either the driver for it is not " "included in the installer, or because it has unusual mixer level names which " "are set to muted by default. You should thus submit a bug report which " "includes the output of the following commands, run on the same machine from " "a Linux system which is known to have sound working (e.g., a live CD)." msgstr "" "Hvis talesyntese for programmer ikke virker, så er der sandsynligvis et " "problem med dit lydkort, normalt på grund af at enten drivere for den ikke " "er inkluderet i installationsprogrammet, eller fordi den har et unormalt " "navn for mikserniveauet som er sat til slukket som standard. Du skal derfor " "indsende en fejlraport som inkluderer resultatet fra de følgende kommandoer, " "kørt på den samme maskine fra et Linuxsystem som vides at have lyd virkende " "(dvs. en live-cd)." #. Tag: userinput #: boot-installer.xml:3074 #, no-c-format msgid "dmesg" msgstr "dmesg" #. Tag: userinput #: boot-installer.xml:3076 #, no-c-format msgid "lspci" msgstr "lspci" #. Tag: userinput #: boot-installer.xml:3078 #, no-c-format msgid "lsmod" msgstr "lsmod" #. Tag: userinput #: boot-installer.xml:3080 #, no-c-format msgid "amixer" msgstr "amixer" #. Tag: title #: boot-installer.xml:3088 boot-installer.xml:3193 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "Gængse &arch-title;-installationsproblemer" #. Tag: para #: boot-installer.xml:3089 #, 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 "" "Der er nogle gængse installationsproblemer, som kan løses eller undgås ved " "at sende bestemte opstartsparametre til installationsprogrammet." #. Tag: para #: boot-installer.xml:3134 #, 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 to disable the framebuffer console. Only a reduced set of " "languages will be available during the installation due to limited console " "features. See for details." msgstr "" "Hvis din skærm begynder at vise et underligt billede når kernen starter op, " "f.eks. ren hvid, ren sort eller usammenhængende farvede billedpunkter, så " "kan dit system indeholde et problematisk videokort, som ikke skifter til " "tilstanden for framebuffer korrekt. Så kan du bruge opstartsparameteren " "fb=false til at deaktivere framebuffer-konsollen. Kun " "et reduceret sæt af sprog vil være tilgængelige under installationen på " "grund af begrænsede konsolfunktioner. Se for " "detaljer." #. Tag: title #: boot-installer.xml:3148 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "Systemfrysning under PCMCIA-konfigurationsfasen" #. Tag: para #: boot-installer.xml:3149 #, no-c-format msgid "" "Some very old laptop models produced by Dell are known to crash when PCMCIA " "device detection tries to access some hardware addresses. Other laptops may " "display similar problems. If you experience such a problem and you don't " "need PCMCIA support during the installation, you can disable PCMCIA using " "the hw-detect/start_pcmcia=false boot parameter. You " "can then configure PCMCIA after the installation is completed and exclude " "the resource range causing the problems." msgstr "" "Nogle meget gamle bærbare modeller fremstillet af Dell vides at bryde ned " "når PCMCIA-enhedsdetektering forsøger at tilgå udvalgte udstyrsadresser. " "Andre bærbare kan have lignende problemer. Hvis du oplever et sådant problem " "har du ikke brug for PCMCIA-understøttelse under installationen, så kan du " "deaktivere PCMCIA via opstartsparameteren hw-detect/" "start_pcmcia=false. Du kan så konfigurere PCMCIA efter at " "installationen er færdig og ekskludere ressourceintervallet, der medfører " "problemerne." #. Tag: para #: boot-installer.xml:3159 #, 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 starte installationsprogrammet op i eksperttilstand. Du " "vil så blive spurgt om at indtaste ressourceintervallet som dit udstyr " "kræver. For eksempel, hvis du har en af Dells bærbare nævnt ovenfor, skal du " "indtaste exclude port 0x800-0x8ff. Der er også en " "liste over nogle gængse intervalindstillinger for ressourcer i afsnittet for " "Systemressourceindstillinger for PCMCIA - hjælp. " "bemærk at du skal undlade kommaerne, hvis nogen, når du indtaster denne " "værdi i installationsprogrammet." #. Tag: para #: boot-installer.xml:3194 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "Der er nogle gængse installationsproblemer som det er værd at nævne." #. Tag: title #: boot-installer.xml:3200 #, no-c-format msgid "Misdirected video output" msgstr "Fejlramt videoresultat" #. Tag: para #: boot-installer.xml:3201 #, no-c-format msgid "" "It is fairly common for &arch-title; to have two video cards in one machine, " "for example an ATI card and a Sun Creator 3D. In some cases, this may result " "in the video output getting misdirected soon after the system boots. In " "typical cases, the display will only show: \n" "Remapping the kernel... done\n" "Booting Linux...\n" " To work around this, you can either pull out one " "of the video cards, or disable the one not used during the OpenProm boot " "phase using a kernel parameter. For example, to disable an ATI card, you " "should boot the installer with video=atyfb:off." msgstr "" "Det er ret ofte at &arch-title; har to videokort i en maskine, for eksempel " "et ATI-kort og et Sun Creator 3D. I nogle tilfælde, kan dette resultere i at " "videoresultatet bliver fejlramt efter at systemet starter op. i typiske " "tilfælde vil skærmen kun vise: \n" "Remapping the kernel... done\n" "Booting Linux...\n" " For at omgå dete kan du enten fjerne et af " "videokortene eller deaktivere et af dem under OpenProm-opstartsfasen med en " "kerneparameter. For eksempel, for at deaktivere et ATI-kort, skal du starter " "installationsprogrammet op med video=atyfb:off." #. Tag: para #: boot-installer.xml:3215 #, no-c-format msgid "" "Note that you may also have to manually add this parameter to the silo " "configuration (edit /target/etc/silo.conf before " "rebooting) and, if you installed X11, modify the video driver in /" "etc/X11/xorg.conf." msgstr "" "Bemærk at du måske også manuelt skal tilføje denne paramter til silo-" "konfigurationen (rediger /target/etc/silo.conf før " "genstart) og, hvis du installerede X11, så ændr videodriveren i /" "etc/X11/xorg.conf." #. Tag: title #: boot-installer.xml:3226 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "Fejl ved opstart eller installation fra cd-rom" #. Tag: para #: boot-installer.xml:3227 #, no-c-format msgid "" "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if " "they do boot, there may be inexplicable failures during the installation. " "Most problems have been reported with SunBlade systems." msgstr "" "Nogle Sparc-systemer er notorisk svære at starte fra cd-rom og selv om de " "starter op, kan der være fejl der ikke kan forklare under installationen. De " "fleste problemer er blevet indrapporteret med SunBlade-systemer." #. Tag: para #: boot-installer.xml:3233 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" "Vi anbefaler at installere sådanne systemer ved at netopstarte " "installationsprogrammet." #. Tag: title #: boot-installer.xml:3242 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "Fortolker kernens opstartsbeskeder" #. Tag: para #: boot-installer.xml:3244 #, 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 opstartssekvensen, kan du se beskeder i form af kan " "ikke finde et eller andet eller " "noget er ikke til stede, kan ikke initialisere noget, eller endda denne " "driverudgivelse afhænger af et eller andet. De fleste af disse beskeder er harmløse. Du ser dem fordi " "kernen for installationssystemet er bygget til at køre på computere med " "mange forskellige perifære enheder. Det er indlysende at ikke alle computere " "har hver eneste perifære enhed, så operativsystemet kan give nogle få " "beklagelser, når det leder efter perifære enheder, du ikke har. Du kan også " "se at systemet kan gå i pause i et øjeblik. Dette sker når systemet venter " "på at en enhed svarer, og denne enhed ikke er tilgængelig på dit system. " "Hvis du synes at tiden systemet er om at starte op er for lang, så kan du " "oprette en tilpasset kerne senere (see )." #. Tag: title #: boot-installer.xml:3269 #, no-c-format msgid "Reporting Installation Problems" msgstr "Rapportering af installationsproblemer" #. Tag: para #: boot-installer.xml:3270 #, fuzzy, no-c-format #| msgid "" #| "If you get through the initial boot phase but cannot complete the " #| "install, the menu option Save debug logs may " #| "be helpful. It lets you store system error logs and configuration " #| "information from the installer to a floppy, or download them using a web " #| "browser. This information may provide clues as to what went wrong and how " #| "to fix it. If you are submitting a bug report, you may want to attach " #| "this information to the bug report." msgid "" "If you get through the initial boot phase but cannot complete the install, " "the menu option Save debug logs may be helpful. " "It lets you store system error logs and configuration information from the " "installer on a storage medium, or download them using a web browser. This " "information may provide clues as to what went wrong and how to fix it. If " "you are submitting a bug report, you may want to attach this information to " "the bug report." msgstr "" "Hvis du kommer igennem den indledende opstartsfase men ikke kan færdiggøre " "installationen, så kan menupunktet Gem fejlsøgningslog være nyttig. Punktet lader dig gemme fejllog fra systemet og " "konfigurationsinformation fra installationsprogrammet til en diskette eller " "hente dem med en internetbrowser. Denne information kan give ideer til hvad " "der gik galt og hvordan det rettes. Hvis du indsender en fejlrapport, så kan " "du vedhæfte denne information til fejlrapporten." #. Tag: para #: boot-installer.xml:3281 #, 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 "" "Andre relevante installationsbeskeder kan findes i /var/log/ under installationen og /var/log/installer/ " "efter at computeren er blevet startet op i det installerede system." #. Tag: title #: boot-installer.xml:3292 #, no-c-format msgid "Submitting Installation Reports" msgstr "Indsendelse af installationsrapporter" #. Tag: para #: boot-installer.xml:3293 #, 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 "" "Hvis du stadig har problemer, så indsend en installationsrapport. Vi " "opmuntrer også til, at installationsrapporter indsendes selvom " "installationen lykkes, så vi kan få så meget information som muligt om det " "største antal udstyrskonfigurationer." #. Tag: para #: boot-installer.xml:3300 #, no-c-format msgid "" "Note that your installation report will be published in the Debian Bug " "Tracking System (BTS) and forwarded to a public mailing list. Make sure that " "you use an e-mail address that you do not mind being made public." msgstr "" "Bemærk at din installationsrapport vil blive vist i Debians " "fejlsøgningssystem (BTS) og videresendt til en offentlig postliste. Sikr dig " "at du bruger en e-post-adresse, som du ikke har problemer med er offentlig." #. Tag: para #: boot-installer.xml:3306 #, 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 " "install installation-report reportbug), configure " "reportbug as explained in , and run the command reportbug installation-reports." msgstr "" "Hvis du har et fungerende &debian;-system, så er den nemmeste måde at sende " "en installationsrapport at installere pakkerne installation-" "report og reportbug (apt install " "installation-report reportbug), konfigurere reportbug som forklaret i , og køre " "kommandoen reportbug installation-reports." #. Tag: para #: boot-installer.xml:3316 #, fuzzy, no-c-format #| msgid "" #| "Alternatively you can use this template when filling out installation " #| "reports, and file the report as a bug report against the " #| "installation-reports pseudo package, by sending it " #| "to submit@bugs.debian.org. \n" #| "Package: installation-reports\n" #| "\n" #| "Boot method: <How did you boot the installer? CD? floppy? network?" #| ">\n" #| "Image version: <Full URL to image you downloaded is best>\n" #| "Date: <Date and time of the install>\n" #| "\n" #| "Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" #| "Processor:\n" #| "Memory:\n" #| "Partitions: <df -Tl will do; the raw partition table is preferred>\n" #| "\n" #| "Output of lspci -knn (or lspci -nn):\n" #| "\n" #| "Base System Installation Checklist:\n" #| "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" #| "\n" #| "Initial boot: [ ]\n" #| "Detect network card: [ ]\n" #| "Configure network: [ ]\n" #| "Detect CD: [ ]\n" #| "Load installer modules: [ ]\n" #| "Detect hard drives: [ ]\n" #| "Partition hard drives: [ ]\n" #| "Install base system: [ ]\n" #| "Clock/timezone setup: [ ]\n" #| "User/password setup: [ ]\n" #| "Install tasks: [ ]\n" #| "Install boot loader: [ ]\n" #| "Overall install: [ ]\n" #| "\n" #| "Comments/Problems:\n" #| "\n" #| "<Description of the install, in prose, and any thoughts, comments\n" #| " and ideas you had during the initial install.>\n" #| " In the bug report, describe what the problem " #| "is, including the last visible kernel messages in the event of a kernel " #| "hang. Describe the steps that you did which brought the system into the " #| "problem state." msgid "" "Alternatively you can use this template when filling out installation " "reports, and file the report as a bug report against the " "installation-reports pseudo package, by sending it to " "submit@bugs.debian.org. \n" "Package: installation-reports\n" "\n" "Boot method: <How did you boot the installer? CD/DVD? USB stick? Network?" ">\n" "Image version: <Full URL to image you downloaded is best>\n" "Date: <Date and time of the install>\n" "\n" "Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" "Processor:\n" "Memory:\n" "Partitions: <df -Tl will do; the raw partition table is preferred>\n" "\n" "Output of lspci -knn (or lspci -nn):\n" "\n" "Base System Installation Checklist:\n" "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" "\n" "Initial boot: [ ]\n" "Detect network card: [ ]\n" "Configure network: [ ]\n" "Detect media: [ ]\n" "Load installer modules: [ ]\n" "Detect hard drives: [ ]\n" "Partition hard drives: [ ]\n" "Install base system: [ ]\n" "Clock/timezone setup: [ ]\n" "User/password setup: [ ]\n" "Install tasks: [ ]\n" "Install boot loader: [ ]\n" "Overall install: [ ]\n" "\n" "Comments/Problems:\n" "\n" "<Description of the install, in prose, and any thoughts, comments\n" " and ideas you had during the initial install.>\n" " In the bug report, describe what the problem is, " "including the last visible kernel messages in the event of a kernel hang. " "Describe the steps that you did which brought the system into the problem " "state." msgstr "" "Alternativt kan du bruge denne skabelon når du udfylder " "installationsrapporter, og indsende rapporten som en fejlrapport mod " "pseudopakken installation-reports ved at sende den " "til submit@bugs.debian.org. \n" "Pakke: installation-reports\n" "\n" "Boot method: <Hvordan igangsatte du installationsprogrammet? cd? " "diskette? netværk?>\n" "Image version: <Fuld adresse til aftrykket du hentede er bedst>\n" "Date: <Dato og tidspunkt for installationen>\n" "\n" "Machine: <Beskrivelse af maskine (f.eks. IBM Thinkpad R32)>\n" "Processor:\n" "Memory:\n" "Partitions: <df -Tl er nok; den rå partitionstabel foretrækkes>\n" "\n" "Resultat af lspci -knn (eller lspci -nn):\n" "\n" "Afkrydsningsliste for installation af basissystemet:\n" "[O] = O.k., [E] = Fejl (uddyb venligst nedenfor), [ ] = prøvede det ikke\n" "\n" "Initial boot: [ ]\n" "Detect network card: [ ]\n" "Configure network: [ ]\n" "Detect CD: [ ]\n" "Load installer modules: [ ]\n" "Detect hard drives: [ ]\n" "Partition hard drives: [ ]\n" "Install base system: [ ]\n" "Clock/timezone setup: [ ]\n" "User/password setup: [ ]\n" "Install tasks: [ ]\n" "Install boot loader: [ ]\n" "Overall install: [ ]\n" "\n" "Comments/Problems:\n" "\n" "<Beskrivelse af installationen, i tekst, og eventuelle tanker, " "kommentarer\n" " og ideer du havde under den oprindelige installation.>\n" " I fejlrapporten beskriver du hvad problemet er, " "inklusiv den sidst synlige kernebesked i tilfælde af at kernen hænger. " "Beskriv handlingerne, du foretog dig, som førte til systemets fejltilstand." #~ msgid "" #~ "If you intend to use the hard drive only for booting and then download " #~ "everything over the network, you should download the netboot/" #~ "debian-installer/&architecture;/initrd.gz file and its " #~ "corresponding kernel netboot/debian-installer/&architecture;/" #~ "linux. This will allow you to repartition the hard disk from " #~ "which you boot the installer, although you should do so with care." #~ msgstr "" #~ "Hvis du har tænkt dig kun at bruge harddisken for opstart og så hente alt " #~ "over netværket, så skal du hente filen netboot/debian-installer/" #~ "&architecture;/initrd.gz og dens modsvarende kerne, " #~ "netboot/debian-installer/&architecture;/linux. Dette " #~ "vil give dig mulighed for at partitionere harddisken, du starter " #~ "installationsprogrammet op fra, om selvom du bør gøre dette med " #~ "forsigtighed." #, fuzzy #~| msgid "" #~| "Alternatively, if you intend to keep an existing partition on the hard " #~| "drive unchanged during the install, you can download the hd-" #~| "media/initrd.gz file and its kernel, as well as copy a CD (or " #~| "DVD) iso to the drive (make sure the file is named ending in ." #~| "iso). The installer can then boot from the drive and install " #~| "from the CD/DVD image, without needing the network." #~ 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 an " #~ "installation image to the hard drive (make sure the file is named ending " #~ "in .iso). The installer can then boot from the hard " #~ "drive and install from the installation image, without needing the " #~ "network." #~ msgstr "" #~ "Alternativt, hvis du forventer at bevare en eksisterende partition på " #~ "harddisken uændret under installationen, så kan du hente filen " #~ "hd-media/initrd.gz og dens kerne, samt kopiere en cd-" #~ "iso (eller dvd-iso) til drevet (sikr dig at filens navn ender med " #~ ".iso). Installationsprogrammet kan så starte op fra " #~ "drevet og installere fra cd/dvd-aftrykket, uden at kræve netværket." #~ 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 "" #~ "For LILO skal du konfigurere to essentielle ting i " #~ "/etc/lilo.conf: for " #~ "at indlæse installationsprogrammet initrd.gz ved " #~ "opstartstidspunktet; lad " #~ "vmlinuz-kernen bruge en RAM-disk som sin " #~ "rodpartition. Her er et /etc/" #~ "lilo.conf-eksempel:" #~ msgid "" #~ "image=/boot/newinstall/vmlinuz\n" #~ " label=newinstall\n" #~ " initrd=/boot/newinstall/initrd.gz" #~ msgstr "" #~ "image=/boot/newinstall/vmlinuz\n" #~ " label=newinstall\n" #~ " initrd=/boot/newinstall/initrd.gz" #~ msgid "" #~ "For more details, refer to the initrd 4 and " #~ "lilo.conf 5 man pages. Now run lilo " #~ "and reboot." #~ msgstr "" #~ "For yderligere detaljer, så se manualsiderne " #~ "initrd 4 og lilo.conf 5. Kør nu " #~ "lilo og genstart." #~ msgid "" #~ "The procedure for GRUB1 is quite similar. Locate your " #~ "menu.lst in the /boot/grub/ " #~ "directory (or sometimes /boot/boot/grub/) and add an " #~ "entry for the installer, for example (assuming /boot " #~ "is on the first partition of the first disk in the system):" #~ msgstr "" #~ "Proceduren for GRUB1 ligner meget. Find din " #~ "menu.lst i mappen /boot/grub/ " #~ "(eller undertiden /boot/boot/grub/) og tilføj en " #~ "post for installationsprogrammet, for eksempel (antager at /" #~ "boot er på den første partition på den første disk i systemet):" #~ msgid "" #~ "title New Install\n" #~ "root (hd0,0)\n" #~ "kernel /boot/newinstall/vmlinuz\n" #~ "initrd /boot/newinstall/initrd.gz" #~ msgstr "" #~ "title New Install\n" #~ "root (hd0,0)\n" #~ "kernel /boot/newinstall/vmlinuz\n" #~ "initrd /boot/newinstall/initrd.gz" #~ msgid "" #~ "The procedure for GRUB2 is very similar. The file is " #~ "named grub.cfg instead of menu.lst. An entry for the installer would be for instance for example:" #~ msgstr "" #~ "Proceduren for GRUB2 er meget lignende. Filen hedder " #~ "grub.cfg i stedet for menu.lst. " #~ "En post for installationsprogrammet ville for eksempel være:" #~ msgid "" #~ "From here on, there should be no difference between GRUB or LILO." #~ msgstr "" #~ "Herfra bør der ikke være forskel på GRUB eller " #~ "LILO." #~ msgid "CD-ROM Reliability" #~ msgstr "Cd-rom-troværdighed" #~ msgid "Booting from Floppies" #~ msgstr "Opstart fra disketter" #~ msgid "" #~ "You will have already downloaded the floppy images you needed and created " #~ "floppies from the images in ." #~ msgstr "" #~ "Du skal have hentet disketteaftrykkene og oprettet disketter ud fra " #~ "aftrykkene i ." #~ 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 "" #~ "For at starte op fra installationsdisketten, så placer den i det primære " #~ "diskettedrev, luk systemet ned som normalt, og tænd det så igen." #~ msgid "" #~ "For installing from an LS-120 drive (ATAPI version) with a set of " #~ "floppies, you need to specify the virtual location for the floppy device. " #~ "This is done with the root= boot argument, giving " #~ "the device that the ide-floppy driver maps the device to. For example, if " #~ "your LS-120 drive is connected as the first IDE device (master) on the " #~ "second cable, you enter install root=/dev/hdc at " #~ "the boot prompt." #~ msgstr "" #~ "For at installere fra et LS-120-drev (ATAPI-version) med et sæt " #~ "disketter, så skal du angive den virtuelle placering for diskettedrevet. " #~ "Dette gøres med opstartsargumentet root=, der skal " #~ "have enheden som ide-floppy-enheden placerer enheden på. For eksempel, " #~ "hvis dit LS-120-drev er forbundet som den første IDE-enhed (master) på " #~ "det andet kabel, så indtaster du install root=/dev/hdc ved opstartsprompten." #~ 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 "" #~ "Bemærk at på nogle maskiner nulstiller Control " #~ "Alt Delete ikke korrekt " #~ "maskinen, så en hård genstart anbefales. Hvis du " #~ "installerer fra et eksisterende operativsystem (f.eks. fra en DOS-boks) " #~ "så har du ikke en valgmulighed. Ellers udfør en hård genstart ved opstart." #~ 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 vil blive tilgået, og du bør se en skærm som introducerer " #~ "opstartsdisketten og slutter med prompten boot:." #~ 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 trykker &enterkey;, bør du se beskeden Loading..., efterfulgt af Uncompressing Linux..., og så cirka en skærmfuld af information om udstyret i " #~ "dit system. Yderligere information om denne fase ved opstartsprocessen " #~ "kan findes nedenfor i ." #~ 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 opstart fra disketten, bliver du anmodt om root-diskken. Indsæt " #~ "root-disketten og tryk &enterkey;, og indholdet læses ind i hukommelsen. " #~ "Installationsprogrammet debian-installer igangsættes " #~ "automatisk." #~ msgid "" #~ "Currently, the only &arch-title; subarchitectures that support CD-ROM " #~ "booting are PReP/CHRP (though not all systems) and New World PowerMacs. " #~ "On PowerMacs, hold the c key, or else the combination of " #~ "Command, Option, Shift, and Delete keys together while booting to boot " #~ "from the factory default CD/DVD drive." #~ msgstr "" #~ "Aktuelt er de eneste &arch-title;-underarkitekturer, som understøtter cd-" #~ "rom-opstart, PReP/CHRP (dog ikke alle systemer) og New World PowerMacs. " #~ "På PowerMacs, hold tasten c, eller kombinationen af " #~ "Command, Option, Skift, og slet nede samtidig under opstarten for at " #~ "starte op fra fabriksstandardens cd/dvd-drev." #~ msgid "" #~ "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open " #~ "Firmware prompt first (see ), " #~ "then type \n" #~ "0 > boot fw/node/sbp-2/disk:,\\install\\yaboot\n" #~ " for an alternative way to boot from the " #~ "internal factory default CD/DVD drive type" #~ msgstr "" #~ "For at starte fra en PowerMac fra et eksternt Firewire cd/dvd-drev så " #~ "igangsæt først Open Firmware-prompten (se ), tast så \n" #~ "0 > boot fw/node/sbp-2/disk:,\\install\\yaboot\n" #~ " for en alternativ måde at starte op på fra " #~ "den interne fabriksstandards cd/dvd-drevtype" #~ msgid "0 > boot cd:,\\install\\yaboot" #~ msgstr "0 > boot cd:,\\install\\yaboot" #~ 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 PowerMacs vil ikke starte op med en &debian;-cd, da OldWorld-" #~ "computere afhang af at en Mac OS ROM CD-opstartsdriver var til stede på " #~ "cd'en, og en fri programversion af denne driver er ikke tilgængelig. Alle " #~ "OldWorld-systemer har diskettedrev, så brug diskettedrevet til at " #~ "igangsætte installationsprogrammet, og peg så installationsprogrammet til " #~ "cd'en for de krævede filer." #~ msgid "" #~ "To boot &debian; CD/DVD on Pegasos II machine, hold Esc " #~ "key immediately after pressing the power-on button, when SmartFirmware " #~ "prompt appears, type" #~ msgstr "" #~ "For at starte &debian;-cd eller -dvd på Pegasos II-maskiner, så hold " #~ "tasten Esc nede umiddelbart efter at du har trykket på " #~ "tændknappen, når SmartFirmware-prompten fremkommer, så tast" #~ msgid "boot cd install/pegasos" #~ msgstr "boot cd install/pegasos" #~ msgid "" #~ "On YDL Powerstation machine, press s immediately after " #~ "Press 's' to enter Open Firmware message, when SLOF prompt " #~ "appears type" #~ msgstr "" #~ "På YDL Powerstation-maskiner trykkes s umiddelbart efter " #~ "beskeden Press 's' to enter Open Firmware, når SLOF-" #~ "prompten fremkommer" #~ msgid "0 > boot cdrom" #~ msgstr "0 > boot cdrom" #~ msgid "Booting from Hard Disk" #~ msgstr "Opstart fra harddisk" #~ msgid "" #~ "Booting from an existing operating system is often a convenient option; " #~ "for some systems it is the only supported method of installation." #~ msgstr "" #~ "Opstart fra et eksisterende operativsystem er ofte en nem mulighed; for " #~ "nogle systemer er det den eneste understøttede installationsmetode." #~ msgid "" #~ "To boot the installer from hard disk, you will have already completed " #~ "downloading and placing the needed files as described in ." #~ msgstr "" #~ "For at starte installationsprogrammet op fra harddisken, så skal du " #~ "allerede have hentet og placeret de krævede filer som beskrevet i ." #~ msgid "Booting OldWorld PowerMacs from MacOS" #~ msgstr "Opstart af OldWorld PowerMacs fra MacOS" #~ 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 "" #~ "Hvis du opsætter BootX i , så kan du " #~ "bruge den til at starte op i installationssystemet. Dobbeltklik på " #~ "programikonet BootX. Klik på knappen " #~ "Options og vælg Use Specified RAM Disk. Dette vil give dig mulighed for at vælge filen " #~ "ramdisk.image.gz. Du skal måske vælge " #~ "afkrydsningsboksen No Video Driver, afhængig af dit " #~ "udstyr. Klik så på knappen Linux for at lukke " #~ "MacOS ned og igangsæt installationsprogrammet." #~ msgid "Booting NewWorld Macs from OpenFirmware" #~ msgstr "Opstart af NewWorld Macs fra OpenFirmware" #~ msgid "" #~ "You will have already placed the vmlinux, " #~ "initrd.gz, yaboot, and " #~ "yaboot.conf files at the root level of your HFS " #~ "partition in . You will now have to " #~ "boot into OpenFirmware (see ). " #~ "At the prompt, type \n" #~ "0 > boot hd:x,yaboot\n" #~ " replacing x with " #~ "the partition number of the HFS partition where the kernel and yaboot " #~ "files were placed, followed by a &enterkey;. On some machines, you may " #~ "need to use ide0: instead of hd:. In a few more seconds you will see a yaboot prompt " #~ "\n" #~ "boot:\n" #~ " At yaboot's boot: prompt, " #~ "type either install or install " #~ "video=ofonly followed by a &enterkey;. The " #~ "video=ofonly argument is for maximum " #~ "compatibility; you can try it if install doesn't " #~ "work. The &debian; installation program should start." #~ msgstr "" #~ "Du har allerede placeret filerne vmlinux, " #~ "initrd.gz, yaboot og " #~ "yaboot.conf på rodniveauet på din HFS-partition i " #~ ". Du skal nu starte op i OpenFirmware " #~ "(se ). I prompten taster du " #~ "\n" #~ "0 > boot hd:x,yaboot\n" #~ " hvor du erstatter x med partitionsnummret for HFS-partitionen, hvor kernen og " #~ "yaboot-filerne blev placeret efterfulgt af &enterkey;. På nogle maskiner, " #~ "skal du måske bruge ide0: i stedet for " #~ "hd:. Efter nogle få yderligere sekunder vil du se " #~ "en yaboot-prompt \n" #~ "boot:\n" #~ " Ved yaboots boot:-prompt, så " #~ "tast enten install eller install " #~ "video=ofonly efterfulgt af &enterkey;. Argumentet " #~ "video=ofonly er for maksimal kompatibilitet; du " #~ "kan prøve dette hvis install ikke fungerer. " #~ "&debian;-installationsprogrammet bør starte." #~ msgid "Booting from USB memory stick" #~ msgstr "Opstart fra USB-hukommelsesdrev" #~ msgid "" #~ "Currently, NewWorld PowerMac systems are known to support USB booting." #~ msgstr "Aktuelt kan NewWorld PowerMac-systemer understøtte USB-opstart." #~ msgid "" #~ "Make sure you have prepared everything from . To boot a Macintosh system from a USB stick, you will need to use " #~ "the Open Firmware prompt, since Open Firmware does not search USB storage " #~ "devices by default. See ." #~ msgstr "" #~ "Sikr dig at du har forberedt alt fra . " #~ "For at starte et Macintosh-system op fra et USB-drev, så skal du bruge " #~ "Open Firmware-prompten, da Open Firmware ikke søger på USB-lagerenheder " #~ "som standard. Se ." # # engelsk fejl? #~ 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 skal undersøge hvor USB-lagerenheden fremgår af enhedstræet, da " #~ "ofpath i øjeblikket ikke kan udregne dette automatisk. " #~ "Tast dev / ls og devalias i " #~ "Open Firmware-prompten for at få en liste over alle kendte enheder og " #~ "enhedsaliasser. På forfatterens system med forskellige typer af USB-drev, " #~ "ser stierne således ud usb0/disk, usb0/hub/" #~ "disk, /pci@f2000000/usb@1b,1/disk@1 og " #~ "/pci@f2000000/usb@1b,1/hub@1/disk@1." #~ msgid "" #~ "Having worked out the device path, use a command like this to boot the " #~ "installer: \n" #~ "boot usb0/disk:2,\\" #~ "\\:tbxi\n" #~ " The 2 matches the " #~ "Apple_HFS or Apple_Bootstrap partition onto which you copied the boot " #~ "image earlier, and the ,\\\\:tbxi part instructs " #~ "Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i." #~ "e. yaboot) in the directory previously blessed with " #~ "hattrib -b." #~ msgstr "" #~ "Med enhedsstien fundet, så brug en kommando som denne for at starte " #~ "installationsprogrammet op: \n" #~ "boot usb0/disk:2,\\" #~ "\\:tbxi\n" #~ " 2 matcher " #~ "partitionen Apple_HFS eller Apple_Bootstrap hvortil du tidligere " #~ "kopierede opstartsaftrykket og delen ,\\\\:tbxi " #~ "instruerer Open Firmware i at opstarte fra filen med en HFS-filtype " #~ "»tbxi« (dvs. yaboot) i mappen tidligere velsignet med " #~ "hattrib -b." #~ 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 skal nu starte op, og du bør blive præsenteret for prompten " #~ "boot:. Her kan du indtaste valgfrie opstartsargumenter, " #~ "eller bare trykke på &enterkey;." #~ 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 "" #~ "Opstartsmetoden er ny, og kan være svær at få til at fungere på nogle " #~ "NewWorld-systemer. Hvis du har problemer, så indsend venligst en " #~ "installationsrapport, som forklaret i ." #~ msgid "Currently, PReP and New World PowerMac systems support netbooting." #~ msgstr "" #~ "Aktuelt understøtter PReP- og New World PowerMac-systemer netopstart." #~ msgid "" #~ "On machines with Open Firmware, such as NewWorld Power Macs, enter the " #~ "boot monitor (see ) and use the " #~ "command \n" #~ "0 > boot enet:0\n" #~ " If this doesn't work, you might have to add " #~ "the filename like this: \n" #~ "0 > boot enet:0,yaboot\n" #~ " PReP and CHRP boxes may have different ways " #~ "of addressing the network. On a PReP machine, you should try " #~ "\n" #~ "boot net:server_ipaddr,file,client_ipaddr\n" #~ " On some PReP systems (e.g. Motorola " #~ "PowerStack machines) the command help boot may " #~ "give a description of syntax and available options." #~ msgstr "" #~ "På maskiner med Open Firmware, såsom NewWorld Power Macs, går du i boot-" #~ "monitoren (se ) og brug " #~ "kommandoen \n" #~ "0 > boot enet:0\n" #~ " Hvis dette ikke virker, så skal du måske " #~ "tilføje filnavnet således: \n" #~ "0 > boot enet:0,yaboot\n" #~ " PReP- og CHRP-bokse kan have forskellige " #~ "måder at adressere netværket på. På en PReP-maskine, kan du prøve " #~ "\n" #~ "boot net:server_ipaddr,file,client_ipaddr\n" #~ " På nogle PReP-systemer (f.eks. Motorola " #~ "PowerStack-maskiner) kan kommandoen help boot " #~ "levere en beskrivelse af syntaks og tilgængelige indstillinger." #~ 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 "" #~ "Opstart fra diskettedrev er understøttet for &arch-title;, selvom det " #~ "generelt kun er gældende for OldWorld-systemer. NewWorld-systemer er ikke " #~ "udstyret med diskettedrev, og tilsluttede USB-drev er ikke understøttet " #~ "for opstart." #~ 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 "" #~ "For at starte op fra disketten boot-floppy-hfs.img, " #~ "så placer den i diskettedrevet efter at systemet er lukket ned, og før du " #~ "trykker på tændknappen." #~ 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 "" #~ "For dem der ikke er bekendt med Macintosh-diskettedrevhandlinger: En " #~ "diskette placeret i maskinen før opstart vil få første prioritet som " #~ "opstart. En diskette uden et gyldigt opstartssystem vil blive skubbte ud, " #~ "og maskinen vil så kigge efter harddiskpartitioner, der kan startes op " #~ "fra." #~ 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 opstart anmodes der om disketten root.bin. " #~ "Indsæt roddisketten og tryk på &enterkey;. Installationsprogrammet " #~ "startes automatisk efter at rodsystemet er blevet indlæst i hukommelsen." #~ msgid "PowerPC Boot Parameters" #~ msgstr "PowerPC-opstartsparametre" #~ 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 "" #~ "Mange ældre Appleskærme brugte en 640x480 67 Hz-tilstand. Hvis dit " #~ "billede fremstår forskudt på en ældre Appleskærm, så prøv at tilføje " #~ "opstartsparameteren video=atyfb:vmode:6, som vil " #~ "vælge den tilstand for det meste Mach64- og Rage-videoudstyr. For Rage " #~ "128-udstyr bliver det video=aty128fb:vmode:6 ." #~ msgid "INSTALL_MEDIA_DEV" #~ msgstr "INSTALL_MEDIA_DEV" #~ 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ærdien på denne parameter er stien til enehden hvor &debian;-" #~ "installationsprogrammet skal indlæses fra. For eksempel, " #~ "INSTALL_MEDIA_DEV=/dev/floppy/0" #~ 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 "" #~ "Opstartsdisketten, som normalt skanner alle diskettedrev den kan for at " #~ "finde roddisketten, kan overskrives med denne parameter til kun at kigge " #~ "efter en enhed." #~ msgid "Floppy Disk Reliability" #~ msgstr "Troværdighed for disketter" #~ msgid "" #~ "The biggest problem for people using floppy disks to install &debian; " #~ "seems to be floppy disk reliability." #~ msgstr "" #~ "Det største problem for folk der bruger disketter til at installere " #~ "&debian; ser ud til at være disketternes troværdighed." #~ 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 "" #~ "Opstartsdisketten er disketten med de største problemer, da den læses af " #~ "udstyret direkte, før Linux starter op. Ofte læser udstyret ikke lige så " #~ "troværdigt som diskettedriveren for Linux, og kan bare stoppe uden at " #~ "vise en fejlbesked, hvis den læser ukorrekte data. Der kan også være fejl " #~ "i driverdisketterne, hvor de fleste fejl viser sig som en stor mængde af " #~ "I/O-fejl." #~ 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 "" #~ "Hvis installationen stopper med en specifik diskette, er den første ting " #~ "du skal gøre at skrive aftrykket til en anden " #~ "diskette og se om dette løser problemet. En formatering af den gamle " #~ "diskette er måske ikke nok, også selv om det ser ud til at disketten blev " #~ "formateret og skrevet uden fejl. Det er undertiden nyttigt at prøve at " #~ "skrive disketten på et andet system." #~ 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 bruger indrapporterede at han skulle skrive aftrykket til disketten " #~ "tre gange før der var en der virkede, og så var alt " #~ "okay med den tredje diskette." #~ 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 "" #~ "Normalt skal du ikke hente en disketteaftryk igen, men hvis du oplever " #~ "problemer er det altid nyttigt at verificere at aftrykkene blev hentet " #~ "korrekt ved at verificere deres md5summer." #~ 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 "" #~ "Andre brugere har indrapporteret at simple genstarter over et par gange " #~ "med den samme diskette i drevet kan føre til en succesfuld opstart. Dette " #~ "skyldes fejlramt udstyr eller firmware i diskettedrevene." #~ msgid "Preseeding" #~ msgstr "Forhåndsindstilling" #~ msgid "SGI TFTP Booting" #~ msgstr "SGI TFTP-opstart" #~ msgid "" #~ "After entering the command monitor use \n" #~ "bootp():\n" #~ " on SGI machines to boot linux and to begin " #~ "installation of the &debian; Software. In order to make this work you may " #~ "have to unset the netaddr environment variable. Type " #~ "\n" #~ "unsetenv netaddr\n" #~ " in the command monitor to do this." #~ msgstr "" #~ "Efter indtastning så bruger kommandoovervågningen " #~ "\n" #~ "bootp():\n" #~ " på SGI-maskiner til at starte Linux op og til " #~ "at begynde installationen af &debian;-programmet. For at dette skal " #~ "virke, så skal du måske ændre indstilling på miljøvariablen " #~ "netaddr. Tast \n" #~ "unsetenv netaddr\n" #~ " i kommandoovervågningen for dette." #~ msgid "" #~ "On SGI machines you can append boot parameters to the bootp(): command in the command monitor." #~ msgstr "" #~ "På SGI-maskiner kan du tilføje opstartsparametre til kommandoen " #~ "bootp(): i kommandoskærmen." #~ msgid "" #~ "Following the bootp(): command you can give the path " #~ "and name of the file to boot if you did not give an explicit name via " #~ "your bootp/dhcp server. Example: \n" #~ "bootp():/boot/tftpboot.img\n" #~ " Further kernel parameters can be passed via " #~ "append:" #~ msgstr "" #~ "Efter kommandoen bootp(): kan du angive stien og " #~ "navnet på filen der skal igangsættes, hvis du ikke angav et eksplicit " #~ "navn via din bootp/dhcp-server. Eksempel: \n" #~ "bootp():/boot/tftpboot.img\n" #~ " Yderligere kerneparametre kan sendes via " #~ "append:" #~ msgid "bootp(): append=\"root=/dev/sda1\"" #~ msgstr "bootp(): append=\"root=/dev/sda1\""