# Danish translation of boot-installer.
# Copyright (C) 2018 Free Software Foundation, Inc.
# Joe Hansen <joedalton2@yahoo.dk>, 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: 2019-06-18 23:08+0000\n"
"PO-Revision-Date: 2018-12-27 20:23+0200\n"
"Last-Translator: Joe Hansen <joedalton2@yahoo.dk>\n"
"Language-Team: Danish <debian-l10n-danish@lists.debian.org>\n"
"Language: da\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\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 <emphasis>before</emphasis> 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 "
"<emphasis>inden</emphasis> 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 <xref linkend="
"\"graphical\"/>."
msgstr ""
"For information om hvordan man starter det grafiske installationsprogram, så "
"se <xref linkend=\"graphical\"/>."

#. 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 (<quote>vmlinuz</quote>) in "
"conjunction with standard Linux initial ramdisks (<quote>initrd.gz</quote>) "
"or b) uImage-format kernels (<quote>uImage</quote>) in conjunction with "
"corresponding initial ramdisks (<quote>uInitrd</quote>)."
msgstr ""
"På ARM-baserede systemer bruges i de fleste tilfælde et af to formater for "
"opstartsaftryk: a) gængse Linux zImage-formatkerner (<quote>vmlinuz</quote>) "
"i samarbejde med gængse  Linux initial-ramdisk (<quote>initrd.gz</quote>) "
"eller b) uImage-formatkerner (<quote>uImage</quote>) i samarbejde med "
"tilsvarende initial ramdisk (<quote>uInitrd</quote>)."

#. 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, <quote>dtb</quote>) 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, "
"<quote>dtb</quote>). 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 (<xref linkend=\"boot-armhf-netboot.tar.gz\"/>), and the "
"installer SD-card images (<xref linkend=\"boot-installer-sd-image\"/>) use "
"the (platform-specific) default console that is defined by U-Boot in the "
"<quote>console</quote> 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 (<xref linkend=\"boot-armhf-netboot.tar.gz\"/>), og "
"installationsaftrykket for SD-kort (<xref linkend=\"boot-installer-sd-image"
"\"/>) bruger standardkonsollen (platformspecifik), som er defineret af U-"
"Boot i variablen <quote>console</quote>. 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 "
"<quote>console</quote> 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 <quote>console</quote> 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 <quote>Booting Linux</quote> 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 <quote>Booting Linux</"
"quote>-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 <userinput>e</userinput> for <quote>Edit Kernel "
"command-line</quote> at the GRUB menu, and change "
"<informalexample><screen>--- quiet</screen></informalexample> to "
"<informalexample><screen>console=&lt;device&gt;,&lt;speed&gt;</screen></"
"informalexample> e.g. <informalexample><screen>console=ttyAMA0,115200n8</"
"screen></informalexample>. When finished hit <keycombo><keycap>Control</"
"keycap> <keycap>x</keycap></keycombo> to continue booting with new setting."
msgstr ""
"Hvis du møder denne problemstilling, så skal du angive en speciel "
"konsolkonfiguration på kernekommandolinjen. Tryk på <userinput>e</userinput> "
"for <quote>Rediger kernekommandolinje</quote> i GRUB-menuen, og ændr "
"<informalexample><screen>--- quiet</screen></informalexample> til "
"<informalexample><screen>console=&lt;device&gt;,&lt;speed&gt;</screen></"
"informalexample> f.eks. <informalexample><screen>console=ttyAMA0,115200n8</"
"screen></informalexample>. Når færdig tryk på <keycombo><keycap>Control</"
"keycap> <keycap>x</keycap></keycombo> 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 <ulink url=\"&url-juno-firmware;\">&url-juno-firmware;</"
"ulink> 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 <ulink url=\"&url-juno-firmware;\">&url-juno-"
"firmware;</ulink> efter marts 2015 er testet o.k. Se Juno-dokumentationen "
"vedrørende firmwareopdatering."

#. Tag: para
#: boot-installer.xml:116
#, no-c-format
msgid ""
"Prepare a standard arm64 CD image on a USB stick. Insert it in one of the "
"USB ports on the back. Plug a serial cable into the upper 9-pin serial port "
"on the back. If you need networking (netboot image) plug the ethernet cable "
"into the socket on the front of the machine."
msgstr ""
"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 <informalexample><screen>console=ttyAMA0,115200n8</screen></"
"informalexample> (as described in <xref linkend=\"arm64-console-setup\"/>). "
"<keycombo><keycap>Control</keycap> <keycap>x</keycap></keycombo> 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 "
"<informalexample><screen>console=ttyAMA0,115200n8</screen></informalexample> "
"som beskrevet i (<xref linkend=\"arm64-console-setup\"/>). "
"<keycombo><keycap>Control</keycap> <keycap>x</keycap></keycombo> 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 (<xref linkend=\"boot-tftp-uboot\"/"
">). 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 (<xref linkend="
"\"boot-tftp-uboot\"/>). 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 <quote>Hit any key to stop autoboot:</quote> "
"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 <quote>Hit any key to stop autoboot:</quote> "
"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:838 boot-installer.xml:1475
#: boot-installer.xml:1605 boot-installer.xml:1926 boot-installer.xml:2074
#, 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:844 boot-installer.xml:1481
#: boot-installer.xml:1611 boot-installer.xml:1932 boot-installer.xml:2080
#, 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:849 boot-installer.xml:1486
#: boot-installer.xml:1616 boot-installer.xml:1937 boot-installer.xml:2085
#, no-c-format
msgid ""
"The server-side setup to support network booting is described in <xref "
"linkend=\"install-tftp\"/>."
msgstr ""
"Opsætningen på serversiden for understøttelse af netværksopstart er "
"beskrevet i <xref linkend=\"install-tftp\"/>."

#. 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 <informalexample><screen>\n"
"setenv autoload no\n"
"dhcp\n"
"</screen></informalexample> or manually by setting several environment "
"variables <informalexample><screen>\n"
"setenv ipaddr &lt;ip address of the client&gt;\n"
"setenv netmask &lt;netmask&gt;\n"
"setenv serverip &lt;ip address of the tftp server&gt;\n"
"setenv dnsip &lt;ip address of the nameserver&gt;\n"
"setenv gatewayip &lt;ip address of the default gateway&gt;\n"
"</screen></informalexample> 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 "
"<informalexample><screen>\n"
"setenv autoload no\n"
"dhcp\n"
"</screen></informalexample> eller manuelt ved at indstille flere "
"miljøparametre <informalexample><screen>\n"
"setenv ipaddr &lt;ip-adresse for klienten&gt;\n"
"setenv netmask &lt;netmaske&gt;\n"
"setenv serverip &lt;ip-adresse for tftp-serveren&gt;\n"
"setenv dnsip &lt;ip-adresse for navneserveren&gt;\n"
"setenv gatewayip &lt;ip-adresse for standardadgangspunktet&gt;\n"
"</screen></informalexample> 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 <informalexample><screen>\n"
"printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n"
"</screen></informalexample> 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 <quote>sun4i</quote> or the Allwinner A20, architecture name "
"<quote>sun7i</quote>), 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 <informalexample><screen>\n"
"printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n"
"</screen></informalexample> 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 <quote>sun4i</quote> eller Allwinner A20, arkitekturnavn "
"<quote>sun7i</quote>), 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} &lt;filename of the kernel image&gt;\n"
"tftpboot ${fdt_addr_r} &lt;filename of the dtb&gt;\n"
"tftpboot ${ramdisk_addr_r} &lt;filename of the initial ramdisk image&gt;"
msgstr ""
"tftpboot ${kernel_addr_r} &lt;filnavn for kerneaftrykket&gt;\n"
"tftpboot ${fdt_addr_r} &lt;filnavn for dtb'en&gt;\n"
"tftpboot ${ramdisk_addr_r} &lt;filnavn for det initielle ramdisk-aftryk&gt;"

#. 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 <quote>bootargs</quote> "
"environment variable as commandline to the kernel, so any parameters for the "
"kernel and the installer - such as the console device (see <xref linkend="
"\"boot-console\"/>) or preseeding options (see <xref linkend=\"installer-args"
"\"/> and <xref linkend=\"appendix-preseed\"/>) - can be set with a command "
"like <informalexample><screen>\n"
"setenv bootargs console=ttyS0,115200 rootwait panic=10\n"
"</screen></informalexample> The exact command to execute the previously "
"loaded code depends on the image format used. With uImage/uInitrd, the "
"command is <informalexample><screen>\n"
"bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}\n"
"</screen></informalexample> 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 <quote>bootargs</quote> som "
"kommandolinje til kernen, så eventuelle parametre for kernen og "
"installationsprogrammet - såsom konsolenheden (se <xref linkend=\"boot-"
"console\"/>) eller forudfyldte indstillinger (se <xref linkend=\"installer-"
"args\"/> og <xref linkend=\"appendix-preseed\"/>) - kan sættes med en "
"kommando som <informalexample><screen>\n"
"setenv bootargs console=ttyS0,115200 rootwait panic=10\n"
"</screen></informalexample> Den præcise kommando til at køre den tidligere "
"indlæste kode afhænger af det anvendte aftryksformat. Med uImage/uInitrd er "
"kommandoen <informalexample><screen>\n"
"bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}\n"
"</screen></informalexample> 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 <phrase arch="
"\"any-x86\"><xref linkend=\"boot-dev-select-x86\"/></phrase><phrase arch="
"\"arm64\"><xref linkend=\"boot-dev-select-arm64\"/></phrase> and <xref "
"linkend=\"boot-usb-files\"/>, 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 "
"<phrase arch=\"any-x86\"><xref linkend=\"boot-dev-select-x86\"/></"
"phrase><phrase arch=\"arm64\"><xref linkend=\"boot-dev-select-arm64\"/></"
"phrase> og <xref linkend=\"boot-usb-files\"/>. 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 <xref linkend=\"where-files\"/>) 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 <xref linkend=\"where-files\"/>) "
"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
#, 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 "
"<quote>run bootcmd_usb0</quote> 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 <quote>run bootcmd_usb0</quote>."

#. 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 <quote>console=ttyS0,115200</quote>), while on other "
"platforms the console variable contains only the device (as in "
"<quote>console=ttyS0</quote>). 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 <quote>run bootcmd_usb0</quote> 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 "
"<quote>console=ttyS0,115200</quote>), mens på andre platforme indeholder "
"konsolvariablen kun enheden (som i <quote>console=ttyS0</quote>). 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 <quote>run bootcmd_usb0</quote>."

#. 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 "
"<quote>firmware.&lt;system-type&gt;.img.gz</quote>, and a system-independent "
"part named <quote>partition.img.gz</quote>."
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 <quote>firmware.&lt;system-type&gt;."
"img.gz</quote>, og en systemuafhængig del navngivet <quote>partition.img.gz</"
"quote>."

#. 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: <informalexample><screen>zcat firmware.&lt;system-type&gt;."
"img.gz partition.img.gz &gt; complete_image.img</screen></informalexample> "
"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 <informalexample><screen>copy /b "
"firmware.&lt;system-type&gt;.img + partition.img complete_image.img</"
"screen></informalexample> in a Windows CMD.exe window."
msgstr ""
"For at oprette et fuldstændigt aftryk fra de dele på Linuxsystemer, så kan "
"du bruge zcat: <informalexample><screen>zcat firmware.&lt;system-type&gt;."
"img.gz partition.img.gz &gt; complete_image.img</screen></informalexample> "
"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 "
"<informalexample><screen>copy /b firmware.&lt;system-type&gt;.img + "
"partition.img complete_image.img</screen></informalexample> 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: <informalexample><screen>cat complete_image.img "
"&gt; /dev/SD_CARD_DEVICE</screen></informalexample> 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: <informalexample><screen>cat complete_image.img &gt; /dev/"
"SD_CARD_DEVICE</screen></informalexample> 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 <xref linkend="
"\"di-partition\"/>), 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 <xref linkend=\"partman-auto\"/>)."
msgstr ""
"Når du kommer til partitioneringstrinet i installationsprogrammet (se <xref "
"linkend=\"di-partition\"/>), 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 <xref linkend="
"\"partman-auto\"/>)."

#. 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 boot-installer.xml:1089 boot-installer.xml:1690
#: boot-installer.xml:2108
#, no-c-format
msgid "Booting from a CD-ROM"
msgstr "Opstart fra en cd-rom"

#. Tag: para
#: boot-installer.xml:579 boot-installer.xml:1095 boot-installer.xml:1696
#: boot-installer.xml:2114
#, no-c-format
msgid ""
"If you have a CD set, and if your machine supports booting directly off the "
"CD, great! Simply <phrase arch=\"x86\"> configure your system for booting "
"off a CD as described in <xref linkend=\"boot-dev-select-x86\"/>, </phrase> "
"insert your CD, 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 <phrase arch=\"x86\"> ved "
"opstart fra en cd som beskrevet i <xref linkend=\"boot-dev-select-x86\"/>, </"
"phrase> indsæt din cd, genstart og fortsæt til næste kapitel."

#. Tag: para
#: boot-installer.xml:589 boot-installer.xml:1105 boot-installer.xml:1706
#: boot-installer.xml:2124
#, no-c-format
msgid ""
"Note that certain CD drives may require special drivers, and thus be "
"inaccessible in the early installation stages. If it turns out the standard "
"way of booting off a CD doesn't work for your hardware, revisit this chapter "
"and read about alternate kernels and installation methods which may work for "
"you."
msgstr ""
"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:1113 boot-installer.xml:1714
#: boot-installer.xml:2132
#, 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."
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:1121 boot-installer.xml:1722
#: boot-installer.xml:2140
#, no-c-format
msgid ""
"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
msgstr ""
"Hvis du har problemer med at starte op, så se <xref linkend=\"boot-"
"troubleshooting\"/>."

#. 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
#, no-c-format
msgid ""
"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
"stick</phrase> installation media as described in <xref linkend=\"official-"
"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
"usb-files\"/></phrase> or"
msgstr ""
"hente cd-rom/dvd-rom-<phrase condition=\"bootable-usb\"> eller USB- </"
"phrase> installationsmedie, som beskrevet i <xref linkend=\"official-cdrom\"/"
"><phrase condition=\"bootable-usb\"> respektiv <xref linkend=\"boot-usb-files"
"\"/></phrase> eller"

#. Tag: para
#: boot-installer.xml:629
#, no-c-format
msgid ""
"download a standalone Windows executable, which is available as <ulink url="
"\"&win32-loader-exe;\">tools/win32-loader/stable/win32-loader.exe</ulink> on "
"the &debian; mirrors."
msgstr ""
"hente en uafhængig kørbar fil for Windows, som er tilgængelig som <ulink url="
"\"&win32-loader-exe;\">tools/win32-loader/stable/win32-loader.exe</ulink> på "
"&debian;-spejlene."

#. Tag: para
#: boot-installer.xml:638
#, 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 <command>setup.exe</"
"command>."
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 "
"<command>setup.exe</command>."

#. Tag: para
#: boot-installer.xml:646
#, 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:656
#, no-c-format
msgid "Booting from DOS using loadlin"
msgstr "Opstart fra DOS med loadlin"

#. Tag: para
#: boot-installer.xml:657
#, 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:662
#, no-c-format
msgid ""
"If you can access the installation CD, change the current drive to the CD-"
"ROM drive, e.g. <informalexample><screen>\n"
"d:\n"
"</screen></informalexample> else make sure you have first prepared your hard "
"disk as explained in <xref linkend=\"files-loadlin\"/>, 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. <informalexample><screen>\n"
"d:\n"
"</screen></informalexample> ellers skal du sikre dig, at du først har "
"forberedt din harddisk som forklaret i<xref linkend=\"files-loadlin\"/>, og "
"ændre det aktuelle drev, hvis det er krævet."

#. Tag: para
#: boot-installer.xml:672
#, no-c-format
msgid ""
"Enter the subdirectory for the flavor you chose, e.g., "
"<informalexample><screen>\n"
"cd \\&x86-install-dir;\n"
"</screen></informalexample> If you prefer using the graphical installer, "
"enter the <filename>gtk</filename> sub-directory. <informalexample><screen>\n"
"cd gtk\n"
"</screen></informalexample> Next, execute <command>install.bat</command>. "
"The kernel will load and launch the installer system."
msgstr ""
"Gå til undermappen for den variant du ønsker, f.eks. "
"<informalexample><screen>\n"
"cd \\&x86-install-dir;\n"
"</screen></informalexample> Hvis du foretrækker det grafiske "
"installationsprogram, så gå til undermappen <filename>gtk</filename>. "
"<informalexample><screen>\n"
"cd gtk\n"
"</screen></informalexample> Kør derefter <command>install.bat</command>. "
"Kernen vil indlæse og igangsætte installationssystemet."

#. Tag: title
#: boot-installer.xml:690
#, no-c-format
msgid ""
"Booting from Linux using <command>LILO</command> or <command>GRUB</command>"
msgstr ""
"Opstart fra Linux med <command>LILO</command> eller <command>GRUB</command>"

#. Tag: para
#: boot-installer.xml:693
#, no-c-format
msgid ""
"To boot the installer from hard disk, you must first download and place the "
"needed files as described in <xref linkend=\"boot-drive-files\"/>."
msgstr ""
"For at starte installationsprogrammet op fra harddisken skal du først hente "
"og placere de nødvendige filer som beskrevet i <xref linkend=\"boot-drive-"
"files\"/>."

#. Tag: para
#: boot-installer.xml:698
#, no-c-format
msgid ""
"If you intend to use the hard drive only for booting and then download "
"everything over the network, you should download the <filename>netboot/"
"debian-installer/&architecture;/initrd.gz</filename> file and its "
"corresponding kernel <filename>netboot/debian-installer/&architecture;/"
"linux</filename>. 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 <filename>netboot/debian-installer/"
"&architecture;/initrd.gz</filename> og dens modsvarende kerne, "
"<filename>netboot/debian-installer/&architecture;/linux</filename>. Dette "
"vil give dig mulighed for at partitionere harddisken, du starter "
"installationsprogrammet op fra, om selvom du bør gøre dette med forsigtighed."

#. Tag: para
#: boot-installer.xml:708
#, no-c-format
msgid ""
"Alternatively, if you intend to keep an existing partition on the hard drive "
"unchanged during the install, you can download the <filename>hd-media/initrd."
"gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the "
"drive (make sure the file is named ending in <literal>.iso</literal>). The "
"installer can then boot from the drive and install from the CD/DVD 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 <filename>hd-"
"media/initrd.gz</filename> og dens kerne, samt kopiere en cd-iso (eller dvd-"
"iso) til drevet (sikr dig at filens navn ender med <literal>.iso</literal>). "
"Installationsprogrammet kan så starte op fra drevet og installere fra cd/dvd-"
"aftrykket, uden at kræve netværket."

#. Tag: para
#: boot-installer.xml:717
#, no-c-format
msgid ""
"For <command>LILO</command>, you will need to configure two essential things "
"in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to "
"load the <filename>initrd.gz</filename> installer at boot time; </para></"
"listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use "
"a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is "
"a <filename>/etc/lilo.conf</filename> example:"
msgstr ""
"For <command>LILO</command> skal du konfigurere to essentielle ting i "
"<filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> for at "
"indlæse installationsprogrammet <filename>initrd.gz</filename> ved "
"opstartstidspunktet; </para></listitem> <listitem><para> lad "
"<filename>vmlinuz</filename>-kernen bruge en RAM-disk som sin rodpartition. "
"</para></listitem> </itemizedlist> Her er et <filename>/etc/lilo.conf</"
"filename>-eksempel:"

#. Tag: screen
#: boot-installer.xml:738
#, no-c-format
msgid ""
"image=/boot/newinstall/vmlinuz\n"
"       label=newinstall\n"
"       initrd=/boot/newinstall/initrd.gz"
msgstr ""
"image=/boot/newinstall/vmlinuz\n"
"       label=newinstall\n"
"       initrd=/boot/newinstall/initrd.gz"

#. Tag: para
#: boot-installer.xml:738
#, no-c-format
msgid ""
"For more details, refer to the <citerefentry><refentrytitle>initrd</"
"refentrytitle> <manvolnum>4</manvolnum></citerefentry> and "
"<citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</"
"manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and "
"reboot."
msgstr ""
"For yderligere detaljer, så se manualsiderne "
"<citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</"
"manvolnum></citerefentry> og <citerefentry><refentrytitle>lilo.conf</"
"refentrytitle> <manvolnum>5</manvolnum></citerefentry>. Kør nu "
"<userinput>lilo</userinput> og genstart."

#. Tag: para
#: boot-installer.xml:747
#, no-c-format
msgid ""
"The procedure for <command>GRUB1</command> is quite similar. Locate your "
"<filename>menu.lst</filename> in the <filename>/boot/grub/</filename> "
"directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an "
"entry for the installer, for example (assuming <filename>/boot</filename> is "
"on the first partition of the first disk in the system):"
msgstr ""
"Proceduren for <command>GRUB1</command> ligner meget. Find din "
"<filename>menu.lst</filename> i mappen <filename>/boot/grub/</filename> "
"(eller undertiden <filename>/boot/boot/grub/</filename>) og tilføj en post "
"for installationsprogrammet, for eksempel (antager at <filename>/boot</"
"filename> er på den første partition på den første disk i systemet):"

#. Tag: screen
#: boot-installer.xml:755
#, no-c-format
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"

#. Tag: para
#: boot-installer.xml:757
#, no-c-format
msgid ""
"The procedure for <command>GRUB2</command> is very similar. The file is "
"named <filename>grub.cfg</filename> instead of <filename>menu.lst</"
"filename>. An entry for the installer would be for instance for example:"
msgstr ""
"Proceduren for <command>GRUB2</command> er meget lignende. Filen hedder "
"<filename>grub.cfg</filename> i stedet for <filename>menu.lst</filename>. En "
"post for installationsprogrammet ville for eksempel være:"

#. Tag: screen
#: boot-installer.xml:763
#, 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: para
#: boot-installer.xml:765
#, no-c-format
msgid ""
"From here on, there should be no difference between <command>GRUB</command> "
"or <command>LILO</command>."
msgstr ""
"Herfra bør der ikke være forskel på <command>GRUB</command> eller "
"<command>LILO</command>."

#. Tag: title
#: boot-installer.xml:774 boot-installer.xml:1976
#, no-c-format
msgid "Booting from Floppies"
msgstr "Opstart fra disketter"

#. Tag: para
#: boot-installer.xml:775 boot-installer.xml:1984
#, no-c-format
msgid ""
"You will have already downloaded the floppy images you needed and created "
"floppies from the images in <xref linkend=\"create-floppy\"/>."
msgstr ""
"Du skal have hentet disketteaftrykkene og oprettet disketter ud fra "
"aftrykkene i <xref linkend=\"create-floppy\"/>."

#. Tag: para
#: boot-installer.xml:782
#, no-c-format
msgid ""
"To boot from the installer boot floppy, place it in the primary floppy "
"drive, shut down the system as you normally would, then turn it back on."
msgstr ""
"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."

#. Tag: para
#: boot-installer.xml:788
#, no-c-format
msgid ""
"For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
"you need to specify the virtual location for the floppy device. This is done "
"with the <emphasis>root=</emphasis> 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 "
"<userinput>install root=/dev/hdc</userinput> 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 <emphasis>root=</emphasis>, 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 <userinput>install root=/dev/hdc</userinput> ved "
"opstartsprompten."

#. Tag: para
#: boot-installer.xml:798
#, no-c-format
msgid ""
"Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
"keycap> <keycap>Delete</keycap></keycombo> does not properly reset the "
"machine, so a <quote>hard</quote> 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 <keycombo><keycap>Control</keycap> "
"<keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> ikke korrekt "
"maskinen, så en <quote>hård</quote> 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."

#. Tag: para
#: boot-installer.xml:807
#, no-c-format
msgid ""
"The floppy disk will be accessed, and you should then see a screen that "
"introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
msgstr ""
"Disketten vil blive tilgået, og du bør se en skærm som introducerer "
"opstartsdisketten og slutter med prompten <prompt>boot:</prompt>."

#. Tag: para
#: boot-installer.xml:813
#, no-c-format
msgid ""
"Once you press &enterkey;, you should see the message "
"<computeroutput>Loading...</computeroutput>, followed by "
"<computeroutput>Uncompressing Linux...</computeroutput>, 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 <xref "
"linkend=\"kernel-msgs\"/>."
msgstr ""
"Når du trykker &enterkey;, bør du se beskeden <computeroutput>Loading...</"
"computeroutput>, efterfulgt af <computeroutput>Uncompressing Linux...</"
"computeroutput>, og så cirka en skærmfuld af information om udstyret i dit "
"system. Yderligere information om denne fase ved opstartsprocessen kan "
"findes nedenfor i <xref linkend=\"kernel-msgs\"/>."

#. Tag: para
#: boot-installer.xml:822
#, no-c-format
msgid ""
"After booting from the boot floppy, the root floppy is requested. Insert the "
"root floppy and press &enterkey;, and the contents are loaded into memory. "
"The installer program <command>debian-installer</command> 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 <command>debian-installer</command> igangsættes "
"automatisk."

#. Tag: title
#: boot-installer.xml:832 boot-installer.xml:1457 boot-installer.xml:1599
#: boot-installer.xml:1920 boot-installer.xml:2068
#, no-c-format
msgid "Booting with TFTP"
msgstr "Opstart med TFTP"

#. Tag: para
#: boot-installer.xml:857
#, 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:863
#, no-c-format
msgid "NIC or Motherboard that support PXE"
msgstr "NIC eller bundkort som understøtter PXE"

#. Tag: para
#: boot-installer.xml:864
#, no-c-format
msgid ""
"It could be that your Network Interface Card or Motherboard provides PXE "
"boot functionality. This is a <trademark class=\"trade\">Intel</trademark> "
"re-implementation of TFTP boot. If so, you may be able to configure your "
"BIOS to boot from the network."
msgstr ""
"Det kan være at dit netværkskort eller bundkort tilbyder en PXE-"
"opstartsfunktion. Dette er en <trademark class=\"trade\">Intel</trademark>-"
"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:875
#, no-c-format
msgid "NIC with Network BootROM"
msgstr "NIC med netværks-BootROM"

#. Tag: para
#: boot-installer.xml:876
#, 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:881
#, no-c-format
msgid ""
"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
"Please refer to this document."
msgstr ""
"Lad os (<email>&email-debian-boot-list;</email>) høre om hvordan du "
"håndterede det. Henvis til dette dokument."

#. Tag: title
#: boot-installer.xml:889
#, no-c-format
msgid "Etherboot"
msgstr "Etherboot"

#. Tag: para
#: boot-installer.xml:890
#, no-c-format
msgid ""
"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
"provides bootdiskettes and even bootroms that do a TFTPboot."
msgstr ""
"<ulink url=\"http://www.etherboot.org\">Etherbootprojektet</ulink> tilbyder "
"opstartsdisketter og endda bootrom'er som udfører en TFTPboot."

#. Tag: title
#: boot-installer.xml:900
#, no-c-format
msgid "The Boot Screen"
msgstr "Opstartsskærmen"

#. Tag: para
#: boot-installer.xml:901
#, 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:906
#, no-c-format
msgid ""
"&debian-gnu; installer boot menu\n"
"\n"
"Graphical install\n"
"Install\n"
"Advanced options             >\n"
"Help\n"
"Install with speech synthesis"
msgstr ""
"&debian-gnu; installer boot menu\n"
"\n"
"Graphical install\n"
"Install\n"
"Advanced options             >\n"
"Help\n"
"Install with speech synthesis"

#. Tag: para
#: boot-installer.xml:910
#, 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:918
#, no-c-format
msgid ""
"Depending on the installation method you are using, the <quote>Graphical "
"install</quote> 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 <quote>Grafisk "
"installation</quote> 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:925
#, no-c-format
msgid ""
"For a normal installation, select either the <quote>Graphical install</"
"quote> or the <quote>Install</quote> entry &mdash; using either the arrow "
"keys on your keyboard or by typing the first (highlighted) letter &mdash; "
"and press &enterkey; to boot the installer. The <quote>Graphical install</"
"quote> entry is already selected by default."
msgstr ""
"For en normal installation, vælg enten punktet <quote>Graphical install</"
"quote> eller <quote>Install</quote> &mdash; med brug af enten piletasterne "
"på dit tastatur eller ved at indtaste det første (fremhævede) bogstav "
"&mdash; og tryk på &enterkey; for at starte installationen. Punktet "
"<quote>Graphical install</quote> er allerede valgt som standard."

#. Tag: para
#: boot-installer.xml:933
#, no-c-format
msgid ""
"The <quote>Advanced options</quote> 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 <quote>Advanced options</quote> 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:939
#, 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:952
#, no-c-format
msgid ""
"Choosing the <quote>Help</quote> 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: <informalexample><screen>\n"
"Press F1 for the help index, or ENTER to boot:\n"
"</screen></informalexample> 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 <userinput>install</userinput>) and a space before "
"the first parameter (e.g., <userinput>install fb=false</userinput>)."
msgstr ""
"Valg af punktet <quote>Help</quote> 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: "
"<informalexample><screen>\n"
"Press F1 for the help index, or ENTER to boot:\n"
"</screen></informalexample> 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 <userinput>install</userinput>) og et "
"mellemrum før den første parameter (f.eks. <userinput>install fb=false</"
"userinput>)."

#. Tag: para
#: boot-installer.xml:970
#, 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 <ulink url=\"&url-us-"
"keymap;\">schema of the US keyboard layout</ulink> 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 <ulink url=\"&url-"
"us-keymap;\">skema for US-tastaturlayout</ulink>, som kan bruges som en "
"reference til at finde de korrekte taster."

#. Tag: para
#: boot-installer.xml:980
#, 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 <quote>integrated Lights Out</quote> "
"(iLO) and HP's <quote>Integrated Remote Assistant</quote> (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  <quote>integrated Lights Out</"
"quote> (iLO) og HP's <quote>Integrated Remote Assistant</quote> (IRA)."

#. Tag: para
#: boot-installer.xml:990
#, 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 <quote>H</quote> "
"followed by &enterkey; to select the <quote>Help</quote> 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 <userinput>vga=normal fb=false</userinput> 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 "
"<quote>H</quote> efterfulgt af &enterkey; for at vælge indstillingen "
"<quote>Help</quote> 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 "
"<userinput>vga=normal fb=false</userinput> til opstartsprompten, som "
"beskrevet i hjælpeteksten."

#. Tag: title
#: boot-installer.xml:1006
#, no-c-format
msgid "The Graphical Installer"
msgstr "Det grafiske installationsprogram"

#. Tag: para
#: boot-installer.xml:1007
#, 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:1015
#, 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 <quote>newt</quote> 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 <quote>newt</quote>-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:1024
#, 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 <quote>Advanced options</quote> menu. The "
"previously used boot methods <userinput>installgui</userinput>, "
"<userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can "
"still be used from the boot prompt which is shown after selecting the "
"<quote>Help</quote> 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 <quote>Advanced options</quote>. De tidligere anvendte "
"opstartsmetoder <userinput>installgui</userinput>, <userinput>expertgui</"
"userinput> og <userinput>rescuegui</userinput> kan stadig bruges fra "
"opstartsprompten, som vises efter valg af indstillingen <quote>Help</quote> "
"i opstartsmenuen."

#. Tag: para
#: boot-installer.xml:1035
#, no-c-format
msgid ""
"There is also a graphical installer image that can be netbooted. And there "
"is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso-x86\"> "
"<para> The mini ISO image can be downloaded from a &debian; mirror as "
"described in <xref linkend=\"downloading-files\"/>. Look for "
"<filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is "
"mainly useful for testing."
msgstr ""
"Der er også et grafisk installationsaftryk, som kan netstartes. Og der er et "
"specielt <quote>mini</quote> ISo-aftryk<footnote id=\"gtk-miniiso-x86\"> "
"<para> Mini-ISO-aftrykket kan hentes fra et &debian;-spejl som beskrevet i "
"<xref linkend=\"downloading-files\"/>. Kig efter <filename>netboot/gtk/mini."
"iso</filename>. </para> </footnote>, som hovedsagelig er nyttig for test."

#. Tag: para
#: boot-installer.xml:1048
#, no-c-format
msgid ""
"For &arch-title;, currently only an experimental <quote>mini</quote> ISO "
"image is available<footnote id=\"gtk-miniiso-powerpc\"> <para> The mini ISO "
"image can be downloaded from a &debian; mirror as described in <xref linkend="
"\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. "
"</para> </footnote>. 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 <quote>mini</quote>-"
"ISO-aftryk tilgængeligt<footnote id=\"gtk-miniiso-powerpc\"> <para> Mini-ISO-"
"aftrykket kan hentes fra et &debian;-spejl som beskrevet i <xref linkend="
"\"downloading-files\"/>. Kig efter <filename>netboot/gtk/mini.iso</"
"filename>. </para> </footnote>. 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:1062
#, 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:1068
#, 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 <quote>newt</"
"quote> 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 <quote>newt</quote> brugerflade."

#. Tag: para
#: boot-installer.xml:1075
#, 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:1129
#, no-c-format
msgid "CD Contents"
msgstr "Cd-indhold"

#. Tag: para
#: boot-installer.xml:1131
#, no-c-format
msgid ""
"There are three basic variations of &debian; Install CDs. The "
"<emphasis>Business Card</emphasis> 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 <emphasis>Network Install</emphasis> 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;. "
"<emphasis>Forretningskort</emphasis>-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. <emphasis>Netværksinstallations</"
"emphasis>-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:1147
#, 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:1163
#, no-c-format
msgid ""
"The &debian; Installer CD contains a small EFI partition where the "
"<command>ELILO</command> 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 "
"<command>ELILO</command>-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:1172
#, no-c-format
msgid ""
"Most of the details of how <command>ELILO</command> 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 <command>ELILO</command> 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 <command>ELILO</command> 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 "
"<command>ELILO</command> 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:1184
#, 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, <command>Boot Option "
"Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. "
"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, "
"<command>Vedligeholdelsesmenu for opstartsindstillinger</command> og "
"<command>EFI-skal (indbygget)</command>. 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:1203
#, no-c-format
msgid "IMPORTANT"
msgstr "VIGTIGT"

#. Tag: para
#: boot-installer.xml:1204
#, 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 <command>exit</command> 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 <command>exit</command> i "
"skalprompten."

#. Tag: title
#: boot-installer.xml:1216
#, 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:1223
#, 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:1229
#, no-c-format
msgid ""
"Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
"keys and press <command>ENTER</command>. This will display a new menu."
msgstr ""
"Vælg <command>Menu for opstartsvedligeholdelse</command> fra menuen med "
"piletasterne og tryk på <command>RETUR</command>. Dette vil vise en ny menu."

#. Tag: para
#: boot-installer.xml:1235
#, no-c-format
msgid ""
"Select <command>Boot From a File</command> from the menu with the arrow keys "
"and press <command>ENTER</command>. This will display a list of devices "
"probed by the firmware. You should see two menu lines containing either the "
"label <command>Debian Inst [Acpi ...</command> or <command>Removable Media "
"Boot</command>. 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 <command>Start op fra en fil</command> fra menuen med piletasterne og "
"tryk på <command>RETUR</command>. Dette vil vise en liste over enheder "
"undersøgt af firmwaren. Du bør se to menulinjer der indeholder enten "
"etiketten <command>Debian Inst [Acpi ...</command> eller <command>Eksternt "
"medieopstart</command>. 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:1246
#, 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 <command>ENTER</command>. If you "
"choose <command>Removable Media Boot</command> the machine will immediately "
"start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</"
"command> 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å <command>RETUR</command>. Hvis du vælger "
"<command>Eksternt medieopstart</command> så vil maskinen igangsætte "
"opstartsindlæsningssekvensen. Hvis du vælger <command>Debian Inst [Acpi ...</"
"command> 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:1257
#, no-c-format
msgid ""
"You will only need this step if you chose <command>Debian Inst [Acpi ...</"
"command>. The directory listing will also show <command>[Treat like "
"Removable Media Boot]</command> on the next to the last line. Select this "
"line with the arrow keys and press <command>ENTER</command>. This will start "
"the boot load sequence."
msgstr ""
"Du skal kun bruge dette trin, hvis du vælger <command>Debian Inst [Acpi ...</"
"command>. Mappevisningen vil også vise <command>[Treat like Removable Media "
"Boot]</command> på den næste til den sidste linje. Vælg denne linje med "
"piletasterne og tryk på <command>RETUR</command>. Dette vil igangsætte "
"opstartssekvensen."

#. Tag: para
#: boot-installer.xml:1269
#, 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:1279
#, no-c-format
msgid "Option 2: Booting from the EFI Shell"
msgstr "Indstilling 2: Opstart fra EFI-skallen"

#. Tag: para
#: boot-installer.xml:1280
#, 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 "
"<command>EFI Shell [Built-in]</command>. 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 <command>EFI Shell [Built-in]</command>. Start &debian;-"
"installations-cd'en med de følgende trin:"

#. Tag: para
#: boot-installer.xml:1291
#, 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:1297
#, no-c-format
msgid ""
"Select <command>EFI Shell</command> from the menu with the arrow keys and "
"press <command>ENTER</command>. 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 <filename>fs<replaceable>n</replaceable>:</filename>. All other "
"recognized partitions will be named <filename>blk<replaceable>n</"
"replaceable>:</filename>. 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 <command>EFI Shell</command> fra menuen med piletastesrne og tryk "
"<command>RETUR</command>. 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å "
"<filename>fs<replaceable>n</replaceable>:</filename>. Alle andre genkendte "
"partitioner vil blive navngivet <filename>blk<replaceable>n</replaceable>:</"
"filename>. 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:1311
#, no-c-format
msgid ""
"Examine the output from the shell looking for the CDROM drive. It is most "
"likely the <filename>fs0:</filename> device although other devices with "
"bootable partitions will also show up as <filename>fs<replaceable>n</"
"replaceable></filename>."
msgstr ""
"Undersøg resultatet fra skallen til du finder cd-rom-drevet. Det er højst "
"sandsynlig enheden <filename>fs0:</filename> selvom andre enheder med "
"opstartspartitioner også vil blive vist som <filename>fs<replaceable>n</"
"replaceable></filename>."

#. Tag: para
#: boot-installer.xml:1318
#, no-c-format
msgid ""
"Enter <command>fs<replaceable>n</replaceable>:</command> and press "
"<command>ENTER</command> to select that device where <replaceable>n</"
"replaceable> is the partition number for the CDROM. The shell will now "
"display the partition number as its prompt."
msgstr ""
"Indtast <command>fs<replaceable>n</replaceable>:</command> og tryk "
"<command>RETUR</command> for at vælge den enhed hvor <replaceable>n</"
"replaceable> er partitionsnummeret for cd'rommen. Skallen vil nu vise "
"partitionsnummeret som sin prompt."

#. Tag: para
#: boot-installer.xml:1325
#, no-c-format
msgid ""
"Enter <command>elilo</command> and press <command>ENTER</command>. This will "
"start the boot load sequence."
msgstr ""
"Indtast <command>elilo</command> og tryk <command>RETUR</command>. Dette vil "
"igangsætte opstartssekvensen."

#. Tag: para
#: boot-installer.xml:1332
#, 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 <command>fs<replaceable>n</replaceable>:elilo</"
"command> 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 "
"<command>fs<replaceable>n</replaceable>:elilo</command> på skalprompten. "
"Fortsæt for at vælge opstartskernen og indstillinger."

#. Tag: title
#: boot-installer.xml:1346
#, no-c-format
msgid "Installing using a Serial Console"
msgstr "Installation med en seriel konsol"

#. Tag: para
#: boot-installer.xml:1348
#, 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 [<replaceable>BAUD</replaceable> baud "
"serial console], where <replaceable>BAUD</replaceable> 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 [<replaceable>BAUD</replaceable> baud serial console], hvor "
"<replaceable>BAUD</replaceable> er hastigheden for din serielle konsol. "
"Menupunkter for de typiske indstillinger for baudhastigheder på ttyS0-"
"enheden er prækonfigurerede."

#. Tag: para
#: boot-installer.xml:1359
#, 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 <command>baud</command> 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 <command>baud</command> via EFI-skallen."

#. Tag: para
#: boot-installer.xml:1366
#, 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 <command>console=ttyS1,57600n8</command> into "
"the <classname>Boot:</classname> 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 "
"<command>console=ttyS1,57600n8</command> i tekstvinduet <classname>Boot:</"
"classname>."

#. Tag: para
#: boot-installer.xml:1377
#, 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 <classname>Params</classname> 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 "
"<classname>Params</classname> for instruktioner på opstart af "
"installationsprogrammet i teksttilstand."

#. Tag: para
#: boot-installer.xml:1386
#, 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:1395
#, no-c-format
msgid "Selecting the Boot Kernel and Options"
msgstr "Valg af opstartskernen og indstillinger"

#. Tag: para
#: boot-installer.xml:1397
#, no-c-format
msgid ""
"The boot loader will display a form with a menu list and a text window with "
"a <classname>Boot:</classname> 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 <classname>General</classname> help screen "
"explains the menu choices and the <classname>Params</classname> screen "
"explains the common command line options."
msgstr ""
"Opstartsindlæseren vil vise en formular med en menuliste og et tekstvindue "
"med en <classname>Boot:</classname>-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 <classname>General</classname> "
"forklarer menuvalgene og vinduet <classname>Params</classname> forklarer de "
"gængse indstillinger for kommandolinjen."

#. Tag: para
#: boot-installer.xml:1409
#, no-c-format
msgid ""
"Consult the <classname>General</classname> help screen for the description "
"of the kernels and install modes most appropriate for your installation. You "
"should also consult <xref linkend=\"boot-parms\"/> below for any additional "
"parameters that you may want to set in the <classname>Boot:</classname> 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 <classname>General</classname> for beskrivelse af kernerne "
"og installationstilstandene som bedst passer for din installation. Du bør "
"også konsultere <xref linkend=\"boot-parms\"/> nedenfor for yderligere "
"parametre, du ønsker at angive i tekstvinduet <classname>Boot:</classname>. "
"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:1427
#, 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:1432
#, 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:1439
#, no-c-format
msgid ""
"Press <command>ENTER</command>. 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 <command>RETUR</command>. 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:1448 boot-installer.xml:1585
#, 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:1459
#, 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:1494
#, 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 "
"<command>elilo</command>. 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 <command>elilo</command>. 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:1505
#, no-c-format
msgid "Configuring the Server"
msgstr "Konfiguration af serveren"

#. Tag: para
#: boot-installer.xml:1506
#, no-c-format
msgid ""
"A suitable TFTP entry for network booting an IA-64 system looks something "
"like this: <informalexample><screen>\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"
"</screen></informalexample> Note that the goal is to get <command>elilo.efi</"
"command> running on the client."
msgstr ""
"Et egnet TFTP-punkt for netværksopstart af et IA-64-system kan se således "
"ud: <informalexample><screen>\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"
"</screen></informalexample> Bemærk at formålet er at få <command>elilo.efi</"
"command> til at køre på klienten."

#. Tag: para
#: boot-installer.xml:1516
#, no-c-format
msgid ""
"Extract the <filename>netboot.tar.gz</filename> file into the directory used "
"as the root for your tftp server. Typical tftp root directories include "
"<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This "
"will create a <filename>debian-installer</filename> directory tree "
"containing the boot files for an IA-64 system."
msgstr ""
"Udtræk filen <filename>netboot.tar.gz</filename> til mappen brugt som root "
"for din tftp-server. Typiske tftp-rootmapper inkluderer <filename>/var/lib/"
"tftp</filename> og <filename>/tftpboot</filename>. Dette vil oprettet et "
"mappetræ for <filename>debian-installer</filename>, der indeholder "
"opstartsfilerne for et IA-64-system."

#. Tag: screen
#: boot-installer.xml:1526
#, 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:1526
#, no-c-format
msgid ""
"The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
"filename> file that should work for most configurations. However, should you "
"need to make changes to this file, you can find it in the <filename>debian-"
"installer/ia64/</filename> 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 <filename>.conf</filename> instead of "
"<filename>elilo.conf</filename>. See documentation provided in the "
"<classname>elilo</classname> package for details."
msgstr ""
"<filename>netboot.tar.gz</filename> indeholder en fil <filename>elilo.conf</"
"filename> som bør virke med de fleste konfigurationer. Har du brug for "
"ændringer i denne fil, så kan du finde den i mappen <filename>debian-"
"installer/ia64/</filename>. Det er muligt at have forskellige "
"konfigurationsfiler for forskellige klienter ved at navngive dem med "
"klientens IP-adresse i hex med filendelsen <filename>.conf</filename> i "
"stedet for <filename>elilo.conf</filename>. Se dokumentationen tilbudt i "
"pakken <classname>elilo</classname> for detaljer."

#. Tag: title
#: boot-installer.xml:1543
#, no-c-format
msgid "Configuring the Client"
msgstr "Konfiguration af klienten"

#. Tag: para
#: boot-installer.xml:1544
#, no-c-format
msgid ""
"To configure the client to support TFTP booting, start by booting to EFI and "
"entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> "
"<listitem><para> Add a boot option. </para></listitem> <listitem><para> You "
"should see one or more lines with the text <guimenuitem>Load File "
"[Acpi()/.../Mac()]</guimenuitem>. 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. </"
"para></listitem> <listitem><para> Name the entry <userinput>Netboot</"
"userinput> or something similar, save, and exit back to the boot options "
"menu. </para></listitem> </itemizedlist> You should see the new boot option "
"you just created, and selecting it should initiate a DHCP query, leading to "
"a TFTP load of <filename>elilo.efi</filename> 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 <guimenu>Boot Option Maintenance Menu</"
"guimenu>. <itemizedlist> <listitem><para> Add a boot option. </para></"
"listitem> <listitem><para> Du bør se en eller flere linjer med teksten "
"<guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. 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. </para></listitem> <listitem><para> Name the entry "
"<userinput>Netboot</userinput> eller noget lignende, gem og afslut tilbage "
"til menuen for opstartsindstillingerne. </para></listitem> </itemizedlist> "
"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 "
"<filename>elilo.efi</filename> fra serveren."

#. Tag: para
#: boot-installer.xml:1576
#, 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:1630
#, no-c-format
msgid "S/390 Limitations"
msgstr "S/390-begrænsninger"

#. Tag: para
#: boot-installer.xml:1631
#, 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:1636
#, 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:1647
#, no-c-format
msgid "S/390 Boot Parameters"
msgstr "S/390-opstartsparametre"

#. Tag: para
#: boot-installer.xml:1648
#, 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 <filename>parmfile.debian</filename> "
"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 <filename>parmfile.debian</"
"filename> 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:1665
#, 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 <quote>cio_ignore</quote> option supports both a blacklist (to "
"only disallow a few devices) and a whitelist (to only allow specific "
"devices): <informalexample role=\"example\"><screen>\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"
"</screen></informalexample> 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 <filename>parmfile.debian</"
"filename>."
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 <quote>cio_ignore</"
"quote> understøtter både en sortliste (for kun at deaktivere nogle få "
"enheder) og en hvidliste (for kun at tillade specifikke enheder): "
"<informalexample role=\"example\"><screen>\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"
"</screen></informalexample> 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 "
"<filename>parmfile.debian</filename>."

#. Tag: para
#: boot-installer.xml:1729
#, no-c-format
msgid ""
"Currently, the only &arch-title; subarchitectures that support CD-ROM "
"booting are PReP/CHRP (though not all systems) and New World PowerMacs. On "
"PowerMacs, hold the <keycap>c</keycap> key, or else the combination of "
"<keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, "
"and <keycap>Delete</keycap> 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 <keycap>c</keycap>, eller kombinationen af "
"<keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Skift</keycap>, "
"og <keycap>slet</keycap> nede samtidig under opstarten for at starte op fra "
"fabriksstandardens cd/dvd-drev."

#. Tag: para
#: boot-installer.xml:1738
#, no-c-format
msgid ""
"To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
"Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then "
"type <informalexample><screen>\n"
"0 &gt; boot fw/node/sbp-2/disk:,\\install\\yaboot\n"
"</screen></informalexample> 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 <xref linkend=\"invoking-"
"openfirmware\"/>), tast så <informalexample><screen>\n"
"0 &gt; boot fw/node/sbp-2/disk:,\\install\\yaboot\n"
"</screen></informalexample> for en alternativ måde at starte op på fra den "
"interne fabriksstandards cd/dvd-drevtype"

#. Tag: screen
#: boot-installer.xml:1749
#, no-c-format
msgid "0 &gt; boot cd:,\\install\\yaboot"
msgstr "0 &gt; boot cd:,\\install\\yaboot"

#. Tag: para
#: boot-installer.xml:1751
#, no-c-format
msgid ""
"OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
"relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-"
"software version of this driver is not available. All OldWorld systems have "
"floppy drives, so use the floppy drive to launch the installer, and then "
"point the installer to the CD for the needed files."
msgstr ""
"OldWorld 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."

#. Tag: para
#: boot-installer.xml:1760
#, no-c-format
msgid ""
"To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> 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 "
"<keycap>Esc</keycap> nede umiddelbart efter at du har trykket på "
"tændknappen, når SmartFirmware-prompten fremkommer, så tast"

#. Tag: screen
#: boot-installer.xml:1766
#, no-c-format
msgid "boot cd install/pegasos"
msgstr "boot cd install/pegasos"

#. Tag: para
#: boot-installer.xml:1768
#, no-c-format
msgid ""
"On YDL Powerstation machine, press <keycap>s</keycap> immediately after "
"<quote>Press 's' to enter Open Firmware</quote> message, when SLOF prompt "
"appears type"
msgstr ""
"På YDL Powerstation-maskiner trykkes <keycap>s</keycap> umiddelbart efter "
"beskeden <quote>Press 's' to enter Open Firmware</quote>, når SLOF-prompten "
"fremkommer"

#. Tag: screen
#: boot-installer.xml:1773
#, no-c-format
msgid "0 &gt; boot cdrom"
msgstr "0 &gt; boot cdrom"

#. Tag: title
#: boot-installer.xml:1779
#, no-c-format
msgid "Booting from Hard Disk"
msgstr "Opstart fra harddisk"

#. Tag: para
#: boot-installer.xml:1785
#, no-c-format
msgid ""
"Booting from an existing operating system is often a convenient option; for "
"some systems it is the only supported method of installation."
msgstr ""
"Opstart fra et eksisterende operativsystem er ofte en nem mulighed; for "
"nogle systemer er det den eneste understøttede installationsmetode."

#. Tag: para
#: boot-installer.xml:1791
#, no-c-format
msgid ""
"To boot the installer from hard disk, you will have already completed "
"downloading and placing the needed files as described in <xref linkend="
"\"boot-drive-files\"/>."
msgstr ""
"For at starte installationsprogrammet op fra harddisken, så skal du allerede "
"have hentet og placeret de krævede filer som beskrevet i <xref linkend="
"\"boot-drive-files\"/>."

#. Tag: title
#: boot-installer.xml:1811
#, no-c-format
msgid "Booting OldWorld PowerMacs from MacOS"
msgstr "Opstart af OldWorld PowerMacs fra MacOS"

#. Tag: para
#: boot-installer.xml:1812
#, no-c-format
msgid ""
"If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
"boot into the installation system. Double click the <guiicon>BootX</guiicon> "
"application icon. Click on the <guibutton>Options</guibutton> button and "
"select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the "
"chance to select the <filename>ramdisk.image.gz</filename> file. You may "
"need to select the <guilabel>No Video Driver</guilabel> checkbox, depending "
"on your hardware. Then click the <guibutton>Linux</guibutton> button to shut "
"down MacOS and launch the installer."
msgstr ""
"Hvis du opsætter BootX i <xref linkend=\"files-oldworld\"/>, så kan du bruge "
"den til at starte op i installationssystemet. Dobbeltklik på programikonet "
"<guiicon>BootX</guiicon>. Klik på knappen <guibutton>Options</guibutton> og "
"vælg <guilabel>Use Specified RAM Disk</guilabel>. Dette vil give dig "
"mulighed for at vælge filen <filename>ramdisk.image.gz</filename>. Du skal "
"måske vælge afkrydsningsboksen <guilabel>No Video Driver</guilabel>, "
"afhængig af dit udstyr. Klik så på knappen <guibutton>Linux</guibutton> for "
"at lukke MacOS ned og igangsæt installationsprogrammet."

#. Tag: title
#: boot-installer.xml:1830
#, no-c-format
msgid "Booting NewWorld Macs from OpenFirmware"
msgstr "Opstart af NewWorld Macs fra OpenFirmware"

#. Tag: para
#: boot-installer.xml:1831
#, no-c-format
msgid ""
"You will have already placed the <filename>vmlinux</filename>, "
"<filename>initrd.gz</filename>, <filename>yaboot</filename>, and "
"<filename>yaboot.conf</filename> files at the root level of your HFS "
"partition in <xref linkend=\"files-newworld\"/>. You will now have to boot "
"into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the "
"prompt, type <informalexample><screen>\n"
"0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
"</screen></informalexample> replacing <replaceable>x</replaceable> 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 "
"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few "
"more seconds you will see a yaboot prompt <informalexample><screen>\n"
"boot:\n"
"</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type "
"either <userinput>install</userinput> or <userinput>install video=ofonly</"
"userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> "
"argument is for maximum compatibility; you can try it if <userinput>install</"
"userinput> doesn't work. The &debian; installation program should start."
msgstr ""
"Du har allerede placeret filerne <filename>vmlinux</filename>, "
"<filename>initrd.gz</filename>, <filename>yaboot</filename> og "
"<filename>yaboot.conf</filename> på rodniveauet på din HFS-partition i <xref "
"linkend=\"files-newworld\"/>. Du skal nu starte op i OpenFirmware (se <xref "
"linkend=\"invoking-openfirmware\"/>). I prompten taster du "
"<informalexample><screen>\n"
"0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
"</screen></informalexample> hvor du erstatter <replaceable>x</replaceable> "
"med partitionsnummret for HFS-partitionen, hvor kernen og yaboot-filerne "
"blev placeret efterfulgt af &enterkey;. På nogle maskiner, skal du måske "
"bruge <userinput>ide0:</userinput> i stedet for <userinput>hd:</userinput>. "
"Efter nogle få yderligere sekunder vil du se en yaboot-prompt "
"<informalexample><screen>\n"
"boot:\n"
"</screen></informalexample> Ved yaboots <prompt>boot:</prompt>-prompt, så "
"tast enten <userinput>install</userinput> eller <userinput>install "
"video=ofonly</userinput> efterfulgt af &enterkey;. Argumentet "
"<userinput>video=ofonly</userinput> er for maksimal kompatibilitet; du kan "
"prøve dette hvis <userinput>install</userinput> ikke fungerer. &debian;-"
"installationsprogrammet bør starte."

#. Tag: title
#: boot-installer.xml:1863
#, no-c-format
msgid "Booting from USB memory stick"
msgstr "Opstart fra USB-hukommelsesdrev"

#. Tag: para
#: boot-installer.xml:1864
#, no-c-format
msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
msgstr "Aktuelt kan NewWorld PowerMac-systemer understøtte USB-opstart."

#. Tag: para
#: boot-installer.xml:1870
#, no-c-format
msgid ""
"Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
">. 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 <xref linkend=\"invoking-openfirmware\"/>."
msgstr ""
"Sikr dig at du har forberedt alt fra <xref linkend=\"boot-usb-files\"/>. 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 <xref linkend=\"invoking-openfirmware\"/>."

# # engelsk fejl?
#. Tag: para
#: boot-installer.xml:1879
#, no-c-format
msgid ""
"You will need to work out where the USB storage device appears in the device "
"tree, since at the moment <command>ofpath</command> cannot work that out "
"automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</"
"userinput> 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 <filename>usb0/disk</filename>, <filename>usb0/hub/disk</"
"filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and "
"<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
msgstr ""
"Du skal undersøge hvor USB-lagerenheden fremgår af enhedstræet, da "
"<command>ofpath</command> i øjeblikket ikke kan udregne dette automatisk. "
"Tast <userinput>dev / ls</userinput> og <userinput>devalias</userinput> 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 <filename>usb0/disk</filename>, <filename>usb0/hub/"
"disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename> og "
"<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename>."

#. Tag: para
#: boot-installer.xml:1891
#, no-c-format
msgid ""
"Having worked out the device path, use a command like this to boot the "
"installer: <informalexample><screen>\n"
"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:"
"tbxi\n"
"</screen></informalexample> The <replaceable>2</replaceable> matches the "
"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image "
"earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open "
"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. "
"<command>yaboot</command>) in the directory previously blessed with "
"<command>hattrib -b</command>."
msgstr ""
"Med enhedsstien fundet, så brug en kommando som denne for at starte "
"installationsprogrammet op: <informalexample><screen>\n"
"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:"
"tbxi\n"
"</screen></informalexample> <replaceable>2</replaceable> matcher partitionen "
"Apple_HFS eller Apple_Bootstrap hvortil du tidligere kopierede "
"opstartsaftrykket og delen <userinput>,\\\\:tbxi</userinput> instruerer Open "
"Firmware i at opstarte fra filen med en HFS-filtype »tbxi« (dvs. "
"<command>yaboot</command>) i mappen tidligere velsignet med <command>hattrib "
"-b</command>."

#. Tag: para
#: boot-installer.xml:1905
#, no-c-format
msgid ""
"The system should now boot up, and you should be presented with the "
"<prompt>boot:</prompt> 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 "
"<prompt>boot:</prompt>. Her kan du indtaste valgfrie opstartsargumenter, "
"eller bare trykke på &enterkey;."

#. Tag: para
#: boot-installer.xml:1911
#, no-c-format
msgid ""
"This boot method is new, and may be difficult to get to work on some "
"NewWorld systems. If you have problems, please file an installation report, "
"as explained in <xref linkend=\"submit-bug\"/>."
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 <xref linkend=\"submit-bug\"/>."

#. Tag: para
#: boot-installer.xml:1945
#, no-c-format
msgid "Currently, PReP and New World PowerMac systems support netbooting."
msgstr "Aktuelt understøtter PReP- og New World PowerMac-systemer netopstart."

#. Tag: para
#: boot-installer.xml:1949
#, no-c-format
msgid ""
"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
"monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command "
"<informalexample><screen>\n"
"0 &gt; boot enet:0\n"
"</screen></informalexample> If this doesn't work, you might have to add the "
"filename like this: <informalexample><screen>\n"
"0 &gt; boot enet:0,yaboot\n"
"</screen></informalexample> PReP and CHRP boxes may have different ways of "
"addressing the network. On a PReP machine, you should try "
"<informalexample><screen>\n"
"boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</"
"replaceable>,<replaceable>client_ipaddr</replaceable>\n"
"</screen></informalexample> On some PReP systems (e.g. Motorola PowerStack "
"machines) the command <userinput>help boot</userinput> 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 <xref linkend=\"invoking-openfirmware\"/>) og brug kommandoen "
"<informalexample><screen>\n"
"0 &gt; boot enet:0\n"
"</screen></informalexample> Hvis dette ikke virker, så skal du måske tilføje "
"filnavnet således: <informalexample><screen>\n"
"0 &gt; boot enet:0,yaboot\n"
"</screen></informalexample> PReP- og CHRP-bokse kan have forskellige måder "
"at adressere netværket på. På en PReP-maskine, kan du prøve "
"<informalexample><screen>\n"
"boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</"
"replaceable>,<replaceable>client_ipaddr</replaceable>\n"
"</screen></informalexample> På nogle PReP-systemer (f.eks. Motorola "
"PowerStack-maskiner) kan kommandoen <userinput>help boot</userinput> levere "
"en beskrivelse af syntaks og tilgængelige indstillinger."

#. Tag: para
#: boot-installer.xml:1977
#, no-c-format
msgid ""
"Booting from floppies is supported for &arch-title;, although it is "
"generally only applicable for OldWorld systems. NewWorld systems are not "
"equipped with floppy drives, and attached USB floppy drives are not "
"supported for booting."
msgstr ""
"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."

#. Tag: para
#: boot-installer.xml:1989
#, no-c-format
msgid ""
"To boot from the <filename>boot-floppy-hfs.img</filename> 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 <filename>boot-floppy-hfs.img</filename>, så "
"placer den i diskettedrevet efter at systemet er lukket ned, og før du "
"trykker på tændknappen."

#. Tag: para
#: boot-installer.xml:1995
#, no-c-format
msgid ""
"For those not familiar with Macintosh floppy operations: a floppy placed in "
"the machine prior to boot will be the first priority for the system to boot "
"from. A floppy without a valid boot system will be ejected, and the machine "
"will then check for bootable hard disk partitions."
msgstr ""
"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."

#. Tag: para
#: boot-installer.xml:2002
#, no-c-format
msgid ""
"After booting, the <filename>root.bin</filename> 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 <filename>root.bin</filename>. Indsæt "
"roddisketten og tryk på &enterkey;. Installationsprogrammet startes "
"automatisk efter at rodsystemet er blevet indlæst i hukommelsen."

#. Tag: title
#: boot-installer.xml:2013
#, no-c-format
msgid "PowerPC Boot Parameters"
msgstr "PowerPC-opstartsparametre"

#. Tag: para
#: boot-installer.xml:2014
#, no-c-format
msgid ""
"Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
"skewed on an older Apple monitor, try appending the boot argument "
"<userinput>video=atyfb:vmode:6</userinput> , which will select that mode for "
"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to "
"<userinput>video=aty128fb:vmode:6</userinput> ."
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 <userinput>video=atyfb:vmode:6</userinput>, som vil "
"vælge den tilstand for det meste Mach64- og Rage-videoudstyr. For Rage 128-"
"udstyr bliver det <userinput>video=aty128fb:vmode:6</userinput> ."

#. Tag: title
#: boot-installer.xml:2026
#, no-c-format
msgid "Booting a ppc64el machine"
msgstr "Opstart af en ppc64el-maskine"

#. Tag: para
#: boot-installer.xml:2027
#, no-c-format
msgid "How to boot a ppc64el machine:"
msgstr "Sådan startes en ppc64el-maskine op:"

#. Tag: title
#: boot-installer.xml:2033
#, no-c-format
msgid "Petitboot"
msgstr "Petitboot"

#. Tag: para
#: boot-installer.xml:2034
#, 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:2042
#, 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:2093
#, no-c-format
msgid ""
"On machines with OpenBoot, simply enter the boot monitor on the machine "
"which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use "
"the command <userinput>boot net</userinput> to boot from a TFTP and RARP "
"server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:"
"dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass "
"extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> "
"command."
msgstr ""
"På maskiner med OpenBoot, så indtast opstartsskærmen for maskinen som der "
"installeres på (se <xref linkend=\"invoking-openboot\"/>). brug kommandoen "
"<userinput>boot net</userinput> til at starte op med fra en TFTP- og RARP-"
"server, eller prøv <userinput>boot net:bootp</userinput> eller "
"<userinput>boot net:dhcp</userinput> til at starte op fra en TFTP- og BOOTP- "
"eller DHCP-server. Du kan sende ekstra opstartsparametre til &d-i; i "
"slutningen af kommandoen <userinput>boot</userinput>."

#. Tag: para
#: boot-installer.xml:2147
#, no-c-format
msgid ""
"Most OpenBoot versions support the <userinput>boot cdrom</userinput> 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 <userinput>boot cdrom</"
"userinput>, 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:2156
#, no-c-format
msgid "IDPROM Messages"
msgstr "IDPROM-beskeder"

#. Tag: para
#: boot-installer.xml:2157
#, no-c-format
msgid ""
"If you cannot boot because you get messages about a problem with "
"<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which "
"holds configuration information for you firmware, has run out. See the "
"<ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more "
"information."
msgstr ""
"Hvis du ikke kan starte op fordi du får beskeder om et problem med "
"<quote>IDPROM</quote>, så er det muligt at dit NVRAM-batteri, som indeholder "
"konfigurationsinformation for din firmware er løbet tør. se <ulink url="
"\"&url-sun-nvram-faq;\">Sun NVRAM OSS</ulink> for yderligere information."

#. Tag: title
#: boot-installer.xml:2176
#, no-c-format
msgid "Accessibility"
msgstr "Tilgængelighed"

#. Tag: para
#: boot-installer.xml:2177
#, no-c-format
msgid ""
"Some users may need specific support because of e.g. some visual impairment. "
"<phrase arch=\"ia64;powerpc;ppc64el;x86\">USB braille displays are detected "
"automatically (not serial displays connected via a serial-to-USB converter), "
"but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;mips64el;sparc"
"\">Most</phrase> accessibility features have to be enabled manually. <phrase "
"arch=\"x86\">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.</phrase> Some boot parameters can <phrase arch="
"\"x86\">then</phrase> be appended to enable accessibility features<phrase "
"arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. 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. <phrase arch=\"ia64;powerpc;ppc64el;x86\">USB-brailleskærme "
"detekteres automatisk (ikke serielle skærme forbundet via en seriel-til-USB-"
"konvertering), men de fleste andre</phrase> <phrase arch=\"arm;hppa;mips;"
"mipsel;mips64el;sparc\"> De fleste</phrase> funktioner for tilgængelighed "
"skal aktiveres manuelt. <phrase arch=\"x86\">På maskiner som understøtter "
"det, så afgiver opstartsmenuen en biplyd når den er klar til at modtage "
"tastaturtryk.</phrase> Nogle opstartsparametre kan <phrase arch=\"x86\">så</"
"phrase> tilføjes for at aktivere tilgængelighedsfunktioner<phrase arch="
"\"x86\"> (se også <xref linkend=\"boot-screen\"/>)</phrase>. Bemærk at på de "
"fleste arkitekturer fortolker opstartsindlæseren dit tastatur som et QERTY-"
"tastatur."

#. Tag: title
#: boot-installer.xml:2197
#, no-c-format
msgid "Installer front-end"
msgstr "Installationsprogrammets brugerflade"

#. Tag: para
#: boot-installer.xml:2198
#, no-c-format
msgid ""
"The &debian; installer supports several front-ends for asking questions, "
"with varying convenience for accessibility: notably, <userinput>text</"
"userinput> uses plain text while <userinput>newt</userinput> uses text-based "
"dialog boxes. The choice can be made at the boot prompt, see the "
"documentation for <userinput>DEBIAN_FRONTEND</userinput> in <xref linkend="
"\"installer-args\"/>."
msgstr ""
"&debian;-installationsprogrammet understøtter flere brugerflader til "
"spørgsmål, med varierende tilgængelighed: <userinput>text</userinput> bruger "
"ren tekst mens <userinput>newt</userinput> bruger tekstbaserede dialogbokse. "
"Valget kan foretages på opstartsprompten, se dokumentationen for "
"<userinput>DEBIAN_FRONTEND</userinput> i <xref linkend=\"installer-args\"/>."

#. Tag: title
#: boot-installer.xml:2210
#, no-c-format
msgid "USB Braille Displays"
msgstr "USB-brailleskærme"

#. Tag: para
#: boot-installer.xml:2211
#, 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 <classname>brltty</"
"classname> is started, you can choose a braille table by entering the "
"preference menu. Documentation on key bindings for braille devices is "
"available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</"
"classname> website</ulink>."
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 <classname>brltty</"
"classname> er startet, så kan du vælge en brailletabel ved at indtaste "
"præferencemenuen. Dokumentation for genvejstaster til brailleenheder er "
"tilgængelige på <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</"
"classname> hjemmesiden</ulink>."

#. Tag: title
#: boot-installer.xml:2226
#, no-c-format
msgid "Serial Braille Displays"
msgstr "Serielle brailleskærme"

#. Tag: para
#: boot-installer.xml:2227
#, 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 "
"<userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</"
"replaceable></userinput> boot parameter to tell <classname>brltty</"
"classname> which driver and port it should use. <replaceable>driver</"
"replaceable> should be replaced by the two-letter driver code for your "
"terminal (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>). "
"<replaceable>port</replaceable> should be replaced by the name of the serial "
"port the display is connected to, <userinput>ttyS0</userinput> is the "
"default, <userinput>ttyUSB0</userinput> 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 <ulink url=\"&url-brltty-"
"manual;\">BRLTTY manual</ulink>); 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 <userinput>protocol=foo</userinput> which is needed for some rare "
"models. Documentation on key bindings for braille devices is available on "
"the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> "
"website</ulink>."
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 "
"<userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</"
"replaceable>,<replaceable>table</replaceable></userinput> for at fortælle "
"<classname>brltty</classname> hvilken driver og port den skal bruge. "
"<replaceable>driver</replaceable> skal erstattes af driverkoden i to "
"bogstaver for din terminal (se <ulink url=\"&url-brltty-manual;\">BRLTTY-"
"manualen</ulink>). <replaceable>port</replaceable> skal erstattes af navnet "
"for den serielle port skærmen er forbundet til, <userinput>ttyS0</userinput> "
"er standarden, <userinput>ttyUSB0</userinput> 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 <ulink url=\"&url-"
"brltty-manual;\">BRLTTY-manualen</ulink>); 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 <userinput>protocol=foo</userinput> hvilket er krævet for nogle "
"sjældne modeller. Dokumentation vedrørende genvejstaster for brailleenheder "
"er tilgængelig på <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</"
"classname>-hjemmesiden</ulink>."

#. Tag: title
#: boot-installer.xml:2254 boot-installer.xml:3309
#, no-c-format
msgid "Software Speech Synthesis"
msgstr "Understøttelse af talesyntese via programmer"

#. Tag: para
#: boot-installer.xml:2255
#, 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 <userinput>s</userinput> &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 <userinput>s</userinput> "
"&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:2264
#, 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:2269
#, 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 "
"<classname>espeak</classname>)."
msgstr ""
"Det første spørgsmål (sprog) stilles på engelsk, resten af installationen "
"udtales med det valgte sprog (hvis tilgængelig i <classname>espeak</"
"classname>)."

#. Tag: para
#: boot-installer.xml:2275
#, no-c-format
msgid ""
"The default speech rate is quite slow. To make it faster, press "
"<keycombo><keycap>CapsLock</keycap><keycap>6</keycap></keycombo>. To make it "
"slower, press <keycombo><keycap>CapsLock</keycap><keycap>5</keycap></"
"keycombo>. The default volume should be medium. To make it louder, press "
"<keycombo><keycap>CapsLock</keycap><keycap>2</keycap></keycombo>. To make it "
"quieter, press <keycombo><keycap>CapsLock</keycap><keycap>1</keycap></"
"keycombo>. To get more details on the browsing shortcuts, see the <ulink url="
"\"&url-speakup-guide;\">Speakup guide</ulink>. To just accept the default "
"answer for a question, simply press <keycap>Enter</keycap> at the prompt. To "
"provide an empty answer for a question, type <userinput>!</userinput> at the "
"prompt. To get back to the previous question, type <userinput>&lt;</"
"userinput> at the prompt."
msgstr ""
"Talehastigheden er som standard ret så langsom. For at gøre den hurtigere "
"trykkes på <keycombo><keycap>CapsLock</keycap><keycap>6</keycap></keycombo>. "
"For at gøre den langsommere <keycombo><keycap>CapsLock</keycap><keycap>5</"
"keycap></keycombo>. Standardlydstyrken bør være mellem. For at gøre den "
"højere <keycombo><keycap>CapsLock</keycap><keycap>2</keycap></keycombo>. For "
"at gøre den lavere <keycombo><keycap>CapsLock</keycap><keycap>1</keycap></"
"keycombo>. for at få flere detaljer om genvejstaster så se <ulink url=\"&url-"
"speakup-guide;\">Opsætningsvejledningen</ulink>. For bare at acceptere "
"standardsvaret for et spørgsmål så tryk på <keycap>Retur</keycap>. For at "
"angive et tomt svar for et spørgsmål tastes <userinput>!</userinput>. For at "
"gå tilbage til det forrige spørgsmål tast <userinput>&lt;</userinput>."

#. Tag: title
#: boot-installer.xml:2303
#, no-c-format
msgid "Hardware Speech Synthesis"
msgstr "Understøttelse af talesyntese via udstyr"

#. Tag: para
#: boot-installer.xml:2304
#, 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 "
"<quote>Graphical install</quote> 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 <quote>Graphical install</quote> i opstartsmenuen."

#. Tag: para
#: boot-installer.xml:2311
#, no-c-format
msgid ""
"Hardware speech synthesis devices cannot be automatically detected. You thus "
"need to append the <userinput>speakup.synth=<replaceable>driver</"
"replaceable></userinput> boot parameter to tell <classname>speakup</"
"classname> which driver it should use. <replaceable>driver</replaceable> "
"should be replaced by the driver code for your device (see <ulink url=\"&url-"
"speakup-guide;\">driver code list</ulink>). 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 <userinput>speakup."
"synth=<replaceable>driver</replaceable></userinput> for at fortælle "
"<classname>speakup</classname> hvilken driver den skal bruge. "
"<replaceable>driver</replaceable> skal erstattes af driverkoden for din "
"enhed (se <ulink url=\"&url-speakup-guide;\">driverkodelisten</ulink>). 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:2326
#, no-c-format
msgid "Board Devices"
msgstr "Bundkortenheder"

#. Tag: para
#: boot-installer.xml:2327
#, 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 <userinput arch="
"\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> 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 <userinput arch=\"x86\">vga=normal</userinput> "
"<userinput>fb=false</userinput>. Dette vil dog reducere antallet af "
"tilgængelige sprog."

#. Tag: para
#: boot-installer.xml:2335
#, no-c-format
msgid ""
"If desired a textual version of the bootloader can be activated before "
"adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
msgstr ""
"Hvis det ønskes kan en tekstversion af opstartsindlæseren aktiveres før "
"tilføjelse af opstartsparameteren ved at indtaste <userinput>h</userinput> "
"&enterkey;."

#. Tag: title
#: boot-installer.xml:2343
#, no-c-format
msgid "High-Contrast Theme"
msgstr "Tema med høj kontrast"

#. Tag: para
#: boot-installer.xml:2344
#, 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 "
#| "<userinput>theme=dark</userinput> 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 <quote>Accessible "
"high contrast</quote> entry from the boot screen with the <userinput>c</"
"userinput> shortcut, or append the <userinput>theme=dark</userinput> 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 "
"<userinput>theme=dark</userinput> til opstartsparameteren."

#. Tag: title
#: boot-installer.xml:2355
#, no-c-format
msgid "Zoom"
msgstr "Zoom"

#. Tag: para
#: boot-installer.xml:2356
#, no-c-format
msgid ""
"For users with low vision, the graphical installer has a very basic zoom "
"support: the <keycombo><keycap>Control</keycap> <keycap>+</keycap></"
"keycombo> and <keycombo><keycap>Control</keycap> <keycap>-</keycap></"
"keycombo> shortcuts increase and decrease the font size."
msgstr ""
"For brugere med begrænset syn, har det grafiske installationsprogram en "
"meget basal zoomunderstøttelse: Genvejstasterne <keycombo><keycap>Control</"
"keycap> <keycap>+</keycap></keycombo> og <keycombo><keycap>Control</keycap> "
"<keycap>-</keycap></keycombo> øger og sænker skriftstørrelsen."

#. Tag: title
#: boot-installer.xml:2366
#, no-c-format
msgid "Expert install, rescue mode, automated install"
msgstr "Ekspertinstallation, redningstilstand, automatiseret installation"

#. Tag: para
#: boot-installer.xml:2367
#, 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 "
"<quote>Advanced options</quote> submenu from the boot menu by typing "
"<userinput>a</userinput>. 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, <userinput>s</userinput> can optionally be pressed "
"(followed again by &enterkey; on BIOS systems but not on UEFI systems). From "
"there, various shortcuts can be used: <userinput>x</userinput> for expert "
"installation, <userinput>r</userinput> for rescue mode, or <userinput>a</"
"userinput> 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 "
"<quote>Advanced options</quote> fra opstartsmenuen ved at taste "
"<userinput>a</userinput>. 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 <userinput>s</userinput> valgfrit "
"trykkes ned (efterfulgt af &enterkey; på BIOS-systemer men ikke på UEFI-"
"systemer). Derfra kan forskellige genveje bruges: <userinput>x</userinput> "
"for ekspertinstallation, <userinput>r</userinput> for redningstilstand, "
"eller <userinput>a</userinput> for automatiseret installation. Når der "
"bruges et BIOS-system, skal hvert af dem efterfølges af &enterkey;."

#. Tag: para
#: boot-installer.xml:2382
#, 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 <xref "
"linkend=\"appendix-preseed\"/>."
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 <xref linkend=\"appendix-preseed\"/>."

#. Tag: title
#: boot-installer.xml:2392
#, no-c-format
msgid "Accessibility of the installed system"
msgstr "Tilgængelighed for det installerede system"

#. Tag: para
#: boot-installer.xml:2393
#, no-c-format
msgid ""
"Documentation on accessibility of the installed system is available on the "
"<ulink url=\"&url-debian-wiki-accessibility;\">Debian Accessibility wiki "
"page</ulink>."
msgstr ""
"Dokumentation vedrørende tilgængelighed for det installerede system er "
"tilgængelig på <ulink url=\"&url-debian-wiki-accessibility;\">Debians "
"wikiside om tilgængelighed</ulink>."

#. Tag: title
#: boot-installer.xml:2407
#, no-c-format
msgid "Boot Parameters"
msgstr "Opstartsparametre"

#. Tag: para
#: boot-installer.xml:2408
#, 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:2415
#, 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:2422
#, no-c-format
msgid ""
"Information on many boot parameters can be found in the <ulink url=\"http://"
"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, "
"including tips for obscure hardware. This section contains only a sketch of "
"the most salient parameters. Some common gotchas are included below in <xref "
"linkend=\"boot-troubleshooting\"/>."
msgstr ""
"Information om mange opstartsparametre kan findes i <ulink url=\"http://www."
"tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, "
"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 <xref linkend=\"boot-troubleshooting\"/>."

#. Tag: title
#: boot-installer.xml:2434
#, no-c-format
msgid "Boot console"
msgstr "Opstartskonsol"

#. Tag: para
#: boot-installer.xml:2436
#, 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 <userinput>console=<replaceable>device</replaceable></"
"userinput> argument to the kernel, where <replaceable>device</replaceable> "
"is your serial device, which is usually something like <filename>ttyS0</"
"filename>."
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 <userinput>console=<replaceable>device</"
"replaceable></userinput> til kernen, hvor <replaceable>device</replaceable> "
"er din seriel enhed, hvilket normalt ligner noget ala <filename>ttyS0</"
"filename>."

#. Tag: para
#: boot-installer.xml:2448
#, no-c-format
msgid ""
"You may need to specify parameters for the serial port, such as speed and "
"parity, for instance <userinput>console=ttyS0,9600n8</userinput>; other "
"typical speeds may be 57600 or 115200. Be sure to specify this option after "
"<quote>---</quote>, 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 <userinput>console=ttyS0,9600n8</"
"userinput>; andre typiske hastigheder kan være 57600 eller 115200. Vær "
"opmærksom på at angive denne indstilling efter <quote>---</quote>, 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:2456
#, no-c-format
msgid ""
"In order to ensure the terminal type used by the installer matches your "
"terminal emulator, the parameter <userinput>TERM=<replaceable>type</"
"replaceable></userinput> can be added. Note that the installer only supports "
"the following terminal types: <literal>linux</literal>, <literal>bterm</"
"literal>, <literal>ansi</literal>, <literal>vt102</literal> and "
"<literal>dumb</literal>. The default for serial console in &d-i; is "
"<userinput>vt102</userinput>. 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 <command>screen</"
"command> session. That will indeed perform translation into the "
"<literal>screen</literal> terminal type, which is very close to "
"<literal>vt102</literal>."
msgstr ""
"For at sikre at terminaltypen brugt af installationsprogrammet matcher din "
"terminalemulator kan parameteren  <userinput>TERM=<replaceable>type</"
"replaceable></userinput> tilføjes. Bemærk at installationsprogrammet kun "
"understøtter de følgende terminaltyper: <literal>linux</literal>, "
"<literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> "
"og <literal>dumb</literal>. Standarden for seriel konsol i &d-i; er "
"<userinput>vt102</userinput>. 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 "
"<command>screen</command>-session. Den vil udføre oversættelse til "
"<literal>screen</literal>-terminaltypen, som er meget tæt på <literal>vt102</"
"literal>."

#. Tag: para
#: boot-installer.xml:2472
#, no-c-format
msgid ""
"For &arch-title; the serial devices are <filename>ttya</filename> or "
"<filename>ttyb</filename>. Alternatively, set the <envar>input-device</"
"envar> and <envar>output-device</envar> OpenPROM variables to "
"<filename>ttya</filename>."
msgstr ""
"For &arch-title; er serielenhederne <filename>ttya</filename> eller "
"<filename>ttyb</filename>. Alternativt sættes OpenPROM-variablerne "
"<envar>input-device</envar> og <envar>output-device</envar> til "
"<filename>ttya</filename>."

#. Tag: title
#: boot-installer.xml:2484
#, no-c-format
msgid "&debian; Installer Parameters"
msgstr "Parametre for &debian;-installationsprogrammet"

#. Tag: para
#: boot-installer.xml:2485
#, no-c-format
msgid ""
"The installation system recognizes a few additional boot "
"parameters<footnote> <para> 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. </para> </footnote> which may be useful."
msgstr ""
"Installationssystemet genkender nogle få yderligere "
"opstartsparametre<footnote> <para> 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. </"
"para> </footnote> hvilket kan være nyttigt."

#. Tag: para
#: boot-installer.xml:2500
#, no-c-format
msgid ""
"A number of parameters have a <quote>short form</quote> 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 <quote>kort form</quote> 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:2512
#, no-c-format
msgid "debconf/priority (priority)"
msgstr "debconf/priority (prioritet)"

#. Tag: para
#: boot-installer.xml:2513
#, 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:2517
#, no-c-format
msgid ""
"The default installation uses <userinput>priority=high</userinput>. 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 <userinput>priority=high</userinput>. 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:2524
#, no-c-format
msgid ""
"If you add <userinput>priority=medium</userinput> as boot parameter, you "
"will be shown the installation menu and gain more control over the "
"installation. When <userinput>priority=low</userinput> is used, all messages "
"are shown (this is equivalent to the <emphasis>expert</emphasis> boot "
"method). With <userinput>priority=critical</userinput>, the installation "
"system will display only critical messages and try to do the right thing "
"without fuss."
msgstr ""
"Hvis du tilføjer <userinput>priority=medium</userinput> som "
"opstartsparameter, vil du få vist installationsmenuen og opnå yderligere "
"kontrol over installationen. Når <userinput>priority=low</userinput> bruges, "
"vises alle beskeder (dette svarer til opstartsmetoden <emphasis>expert</"
"emphasis>. Med <userinput>priority=critical</userinput> 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:2538
#, no-c-format
msgid "DEBIAN_FRONTEND"
msgstr "DEBIAN_FRONTEND"

#. Tag: para
#: boot-installer.xml:2539
#, no-c-format
msgid ""
"This boot parameter controls the type of user interface used for the "
"installer. The current possible parameter settings are: <itemizedlist> "
"<listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></"
"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</"
"userinput></para> </listitem><listitem> "
"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </"
"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> "
"</listitem> </itemizedlist> The default frontend is "
"<userinput>DEBIAN_FRONTEND=newt</userinput>. "
"<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial "
"console installs. Some specialized types of install media may only offer a "
"limited selection of frontends, but the <userinput>newt</userinput> and "
"<userinput>text</userinput> frontends are available on most default install "
"media. On architectures that support it, the graphical installer uses the "
"<userinput>gtk</userinput> frontend."
msgstr ""
"Denne opstartsparameter kontroller typen af brugergrænseflade brugt af "
"installationsprogrammet. De aktuelt mulige parameterindstillinger er: "
"<itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</"
"userinput></para> </listitem><listitem> "
"<para><userinput>DEBIAN_FRONTEND=text</userinput></para> </"
"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> "
"</listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></"
"para> </listitem> </itemizedlist> Standardbrugerfladen er "
"<userinput>DEBIAN_FRONTEND=newt</userinput>. "
"<userinput>DEBIAN_FRONTEND=text</userinput> kan foretrækkes for serielle "
"konsolinstallationer. Nogle specialiserede typer af installationsmedier "
"tilbyder måske kun et begrærset udvalg af brugerflader, men brugerfladerne "
"<userinput>newt</userinput> og <userinput>text</userinput> er tilgængelige "
"på de fleste gængse installationsmedier. På arkitekturer som understøtter "
"det, bruger det grafiske installationsprogram brugerfladen <userinput>gtk</"
"userinput>."

#. Tag: term
#: boot-installer.xml:2570
#, no-c-format
msgid "BOOT_DEBUG"
msgstr "BOOT_DEBUG"

#. Tag: para
#: boot-installer.xml:2571
#, 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:2580
#, no-c-format
msgid "BOOT_DEBUG=0"
msgstr "BOOT_DEBUG=0"

#. Tag: para
#: boot-installer.xml:2581
#, no-c-format
msgid "This is the default."
msgstr "Dette er standarden."

#. Tag: userinput
#: boot-installer.xml:2585
#, no-c-format
msgid "BOOT_DEBUG=1"
msgstr "BOOT_DEBUG=1"

#. Tag: para
#: boot-installer.xml:2586
#, no-c-format
msgid "More verbose than usual."
msgstr "Mere uddybende end normalt."

#. Tag: userinput
#: boot-installer.xml:2590
#, no-c-format
msgid "BOOT_DEBUG=2"
msgstr "BOOT_DEBUG=2"

#. Tag: para
#: boot-installer.xml:2591
#, no-c-format
msgid "Lots of debugging information."
msgstr "Masser af fejlsøgningsinformation."

#. Tag: userinput
#: boot-installer.xml:2595
#, no-c-format
msgid "BOOT_DEBUG=3"
msgstr "BOOT_DEBUG=3"

#. Tag: para
#: boot-installer.xml:2596
#, 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:2610
#, no-c-format
msgid "INSTALL_MEDIA_DEV"
msgstr "INSTALL_MEDIA_DEV"

#. Tag: para
#: boot-installer.xml:2611
#, no-c-format
msgid ""
"The value of the parameter is the path to the device to load the &debian; "
"installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</"
"userinput>"
msgstr ""
"Værdien på denne parameter er stien til enehden hvor &debian;-"
"installationsprogrammet skal indlæses fra. For eksempel, "
"<userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"

#. Tag: para
#: boot-installer.xml:2617
#, no-c-format
msgid ""
"The boot floppy, which normally scans all floppies it can to find the root "
"floppy, can be overridden by this parameter to only look at the one device."
msgstr ""
"Opstartsdisketten, som normalt skanner alle diskettedrev den kan for at "
"finde roddisketten, kan overskrives med denne parameter til kun at kigge "
"efter en enhed."

#. Tag: term
#: boot-installer.xml:2628
#, no-c-format
msgid "log_host"
msgstr "log_host"

#. Tag: term
#: boot-installer.xml:2629
#, no-c-format
msgid "log_port"
msgstr "log_port"

#. Tag: para
#: boot-installer.xml:2630
#, 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:2641
#, no-c-format
msgid "lowmem"
msgstr "lowmem"

#. Tag: para
#: boot-installer.xml:2642
#, 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 <xref linkend=\"lowmem\"/>."
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å <xref linkend=\"lowmem\"/>."

#. Tag: term
#: boot-installer.xml:2652
#, no-c-format
msgid "noshell"
msgstr "noshell"

#. Tag: para
#: boot-installer.xml:2653
#, 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:2662
#, no-c-format
msgid "debian-installer/framebuffer (fb)"
msgstr "debian-installer/framebuffer (fb)"

#. Tag: para
#: boot-installer.xml:2663
#, 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 <userinput arch=\"x86\">vga=normal</"
"userinput> <userinput>fb=false</userinput>. 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 <userinput arch=\"x86\">vga=normal</"
"userinput> <userinput>fb=false</userinput>. 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:2672
#, no-c-format
msgid "Such problems have been reported on hppa."
msgstr "Disse problemer er blevet indrapporteret på hppa."

#. Tag: para
#: boot-installer.xml:2676
#, no-c-format
msgid ""
"Because of display problems on some systems, framebuffer support is "
"<emphasis>disabled by default</emphasis> 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 <userinput>debian-installer/"
"framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
msgstr ""
"På grund af visningsproblemer på nogle systemer, så er understøttelse af "
"framebuffer <emphasis>deaktiveret som standard</emphasis> 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 <userinput>debian-installer/framebuffer=true</userinput> eller "
"<userinput>fb=true</userinput> i kort form."

#. Tag: term
#: boot-installer.xml:2690
#, no-c-format
msgid "debian-installer/theme (theme)"
msgstr "debian-installer/theme (tema)"

#. Tag: para
#: boot-installer.xml:2691
#, 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 <quote>dark</quote> theme that was "
"designed for visually impaired users. Set the theme by booting with "
"<userinput>theme=<replaceable>dark</replaceable></userinput>."
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 "
"<quote>dark</quote>-tema, som blev designet for de visuelt synshæmmede "
"brugere. Angiv temaet ved at starte med <userinput>theme=<replaceable>dark</"
"replaceable></userinput>."

#. Tag: term
#: boot-installer.xml:2703 boot-installer.xml:2936
#, no-c-format
msgid "netcfg/disable_autoconfig"
msgstr "netcfg/disable_autoconfig"

#. Tag: para
#: boot-installer.xml:2704
#, 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:2711
#, 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 <userinput>netcfg/disable_autoconfig=true</userinput> 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 <userinput>netcfg/disable_autoconfig=true</userinput> til at "
"forhindre automatisk konfiguration af netværket (hverken v4 eller v6) og "
"indtaste informationen manuelt."

#. Tag: term
#: boot-installer.xml:2722
#, no-c-format
msgid "hw-detect/start_pcmcia"
msgstr "hw-detect/start_pcmcia"

#. Tag: para
#: boot-installer.xml:2723
#, no-c-format
msgid ""
"Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
"that causes problems. Some laptops are well known for this misbehavior."
msgstr ""
"Sæt til <userinput>false</userinput> 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:2733
#, no-c-format
msgid "disk-detect/dmraid/enable (dmraid)"
msgstr "disk-detect/dmraid/enable (dmraid)"

#. Tag: para
#: boot-installer.xml:2734
#, no-c-format
msgid ""
"Set to <userinput>true</userinput> 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 <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
msgstr ""
"Sæt til <userinput>true</userinput> 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å <ulink url=\"&url-d-i-"
"wiki;\">&debian;-installationsprogrammets wiki</ulink>."

#. Tag: term
#: boot-installer.xml:2745
#, no-c-format
msgid "preseed/url (url)"
msgstr "preseed/url (adresse)"

#. Tag: para
#: boot-installer.xml:2746
#, no-c-format
msgid ""
"Specify the url to a preconfiguration file to download and use for "
"automating the install. See <xref linkend=\"automatic-install\"/>."
msgstr ""
"Angiv adressen for en prækonfigurationsfil for at hente og bruge den for "
"automatisering af installationen. Se <xref linkend=\"automatic-install\"/>."

#. Tag: term
#: boot-installer.xml:2755
#, no-c-format
msgid "preseed/file (file)"
msgstr "preseed/file (fil)"

#. Tag: para
#: boot-installer.xml:2756
#, no-c-format
msgid ""
"Specify the path to a preconfiguration file to load for automating the "
"install. See <xref linkend=\"automatic-install\"/>."
msgstr ""
"Angiv stien til en forhåndskonfigurationsfil til indlæsning for "
"automatisering af installationen. Se <xref linkend=\"automatic-install\"/>."

#. Tag: term
#: boot-installer.xml:2765
#, no-c-format
msgid "preseed/interactive"
msgstr "preseed/interactive"

#. Tag: para
#: boot-installer.xml:2766
#, no-c-format
msgid ""
"Set to <userinput>true</userinput> 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 <xref "
"linkend=\"preseed-seenflag\"/> for details."
msgstr ""
"Sæt til <userinput>true</userinput> 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  <xref linkend=\"preseed-seenflag\"/> for detaljer."

#. Tag: term
#: boot-installer.xml:2778
#, no-c-format
msgid "auto-install/enable (auto)"
msgstr "auto-install/enable (auto)"

#. Tag: para
#: boot-installer.xml:2779
#, no-c-format
msgid ""
"Delay questions that are normally asked before preseeding is possible until "
"after the network is configured. See <xref linkend=\"preseed-auto\"/> 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 <xref linkend=\"preseed-auto\"/> for "
"detaljer om brugen af denne til automatisering af installationer."

#. Tag: term
#: boot-installer.xml:2790
#, no-c-format
msgid "finish-install/keep-consoles"
msgstr "finish-install/keep-consoles"

#. Tag: para
#: boot-installer.xml:2791
#, no-c-format
msgid ""
"During installations from serial or management console, the regular virtual "
"consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</"
"filename>. Set to <userinput>true</userinput> to prevent this."
msgstr ""
"Under installationer fra seriel eller håndteringskonsol er de regulære "
"virtuelle konsoller (VT1 til VT6) normalt deaktiveret i <filename>/etc/"
"inittab</filename>. Sæt til <userinput>true</userinput> for at forhindre "
"dette."

#. Tag: term
#: boot-installer.xml:2802
#, no-c-format
msgid "cdrom-detect/eject"
msgstr "cdrom-detect/eject"

#. Tag: para
#: boot-installer.xml:2803
#, no-c-format
msgid ""
"By default, before rebooting, &d-i; automatically ejects the optical media "
"used during the installation. This can be unnecessary if the system does not "
"automatically boot off the CD. In some cases it may even be undesirable, for "
"example if the optical drive cannot reinsert the media itself and the user "
"is not there to do it manually. Many slot loading, slim-line, and caddy "
"style drives cannot reload media automatically."
msgstr ""
"Som standard, fø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:2812
#, no-c-format
msgid ""
"Set to <userinput>false</userinput> 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 <userinput>false</userinput> 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:2823
#, no-c-format
msgid "base-installer/install-recommends (recommends)"
msgstr "base-installer/install-recommends (anbefalinger)"

#. Tag: para
#: boot-installer.xml:2824
#, no-c-format
msgid ""
"By setting this option to <userinput>false</userinput>, the package "
"management system will be configured to not automatically install "
"<quote>Recommends</quote>, both during the installation and for the "
"installed system. See also <xref linkend=\"di-install-base\"/>."
msgstr ""
"Ved at angive denne indstilling til <userinput>false</userinput>, vil "
"pakkehåndteringssystemet blive konfigureret til ikke automatisk at "
"installere <quote>Recommends (anbefalinger)</quote>, både under "
"installationen og for det installerede system. Se også <xref linkend=\"di-"
"install-base\"/>."

#. Tag: para
#: boot-installer.xml:2831
#, 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:2843
#, no-c-format
msgid "debian-installer/allow_unauthenticated"
msgstr "debian-installer/allow_unauthenticated"

#. Tag: para
#: boot-installer.xml:2844
#, no-c-format
msgid ""
"By default the installer requires that repositories be authenticated using a "
"known gpg key. Set to <userinput>true</userinput> to disable that "
"authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</"
"emphasis>"
msgstr ""
"Som standard kræver installationsprogrammet at arkiver godkendes med en "
"kendt gpg-nøgle. Angiv som <userinput>true (sand)</userinput> for at "
"deaktivere den godkendelse. <emphasis role=\"bold\">Advarsel: usikker, kan "
"ikke anbefales.</emphasis>"

#. Tag: term
#: boot-installer.xml:2855
#, no-c-format
msgid "ramdisk_size"
msgstr "ramdisk_size"

#. Tag: para
#: boot-installer.xml:2856
#, 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:2866
#, no-c-format
msgid "rescue/enable"
msgstr "rescue/enable"

#. Tag: para
#: boot-installer.xml:2867
#, no-c-format
msgid ""
"Set to <userinput>true</userinput> to enter rescue mode rather than "
"performing a normal installation. See <xref linkend=\"rescue\"/>."
msgstr ""
"Angiv til <userinput>true (sand)</userinput> for at gå i redningstilstand "
"fremfor at udføre en normal installation. Se <xref linkend=\"rescue\"/>."

#. Tag: title
#: boot-installer.xml:2880
#, 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:2881
#, 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 <xref linkend="
"\"preseed-bootparms\"/>. 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 <xref linkend=\"preseed-bootparms\"/>. Nogle specifikke eksempler "
"vises nedenfor."

#. Tag: term
#: boot-installer.xml:2893
#, no-c-format
msgid "debian-installer/language (language)"
msgstr "debian-installer/language (sprog)"

#. Tag: term
#: boot-installer.xml:2894
#, no-c-format
msgid "debian-installer/country (country)"
msgstr "debian-installer/country (land)"

#. Tag: term
#: boot-installer.xml:2895
#, no-c-format
msgid "debian-installer/locale (locale)"
msgstr "debian-installer/locale (sted)"

#. Tag: para
#: boot-installer.xml:2896
#, 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:2901
#, no-c-format
msgid ""
"The first and easiest is to pass only the parameter <literal>locale</"
"literal>. Language and country will then be derived from its value. You can "
"for example use <userinput>locale=de_CH</userinput> to select German as "
"language and Switzerland as country (<literal>de_CH.UTF-8</literal> 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 <literal>locale</"
"literal>. Sprog og land vil så blive udledt fra dens værdi. Du kan for "
"eksempel bruge <userinput>locale=de_CH</userinput> til at vælge tysk som "
"sprog og Schweitz som land (<literal>de_CH.UTF-8</literal> 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:2910
#, no-c-format
msgid ""
"The second, more flexible option is to specify <literal>language</literal> "
"and <literal>country</literal> separately. In this case <literal>locale</"
"literal> can optionally be added to specify a specific default locale for "
"the installed system. Example: <userinput>language=en country=DE "
"locale=en_GB.UTF-8</userinput>."
msgstr ""
"Den anden, mere fleksible indstilling er at angive <literal>sprog</literal> "
"og <literal>land</literal> adskilt. I dette tilfælde kan <literal>sted</"
"literal> valgfrit tilføjes for at angive et specifikt standardsted for det "
"installerede system. Eksempel: <userinput>language=en country=DE "
"locale=en_GB.UTF-8</userinput>."

#. Tag: term
#: boot-installer.xml:2922
#, no-c-format
msgid "anna/choose_modules (modules)"
msgstr "anna/choose_modules (moduler)"

#. Tag: para
#: boot-installer.xml:2923
#, 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 "
"<classname>openssh-client-udeb</classname> (so you can use <command>scp</"
"command> during the installation)<phrase arch=\"not-s390\"> and "
"<classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
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 <classname>openssh-client-udeb</classname> (så du kan bruge "
"<command>scp</command> under installationen)<phrase arch=\"not-s390\"> og "
"<classname>ppp-udeb</classname> (se <xref linkend=\"pppoe\"/>)</phrase>."

#. Tag: para
#: boot-installer.xml:2937
#, no-c-format
msgid ""
"Set to <userinput>true</userinput> if you want to disable IPv6 "
"autoconfiguration and DHCP and instead force static network configuration."
msgstr ""
"Angiv som <userinput>true (sand)</userinput> hvis du ønsker at deaktivere "
"automatisk IPv6-konfiguration og DHCP og i stedet for fremtvinge statisk "
"netværkskonfiguration."

#. Tag: term
#: boot-installer.xml:2946
#, no-c-format
msgid "mirror/protocol (protocol)"
msgstr "mirror/protocol (protokol)"

#. Tag: para
#: boot-installer.xml:2947
#, 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 "
"<userinput>ftp</userinput>, 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 "
"<userinput>ftp</userinput>, 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:2960
#, no-c-format
msgid "tasksel:tasksel/first (tasks)"
msgstr "tasksel:tasksel/first (opgaver)"

#. Tag: para
#: boot-installer.xml:2961
#, no-c-format
msgid ""
"Can be used to select tasks that are not available from the interactive task "
"list, such as the <literal>kde-desktop</literal> task. See <xref linkend="
"\"pkgsel\"/> for additional information."
msgstr ""
"Kan bruges til at vælge opgaver, som ikke er tilgængelige fra den "
"interaktive opgaveliste, såsom opgaven <literal>kde-desktop</literal>. Se "
"<xref linkend=\"pkgsel\"/> for yderligere information."

#. Tag: title
#: boot-installer.xml:2975
#, no-c-format
msgid "Passing parameters to kernel modules"
msgstr "Sende parametre til kernemoduler"

#. Tag: para
#: boot-installer.xml:2976
#, 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:2989
#, 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:2996
#, no-c-format
msgid ""
"The syntax to use to set parameters for modules is: "
"<informalexample><screen>\n"
"<replaceable>module_name</replaceable>.<replaceable>parameter_name</"
"replaceable>=<replaceable>value</replaceable>\n"
"</screen></informalexample> 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: <informalexample><screen>\n"
"<replaceable>module_name</replaceable>.<replaceable>parameter_name</"
"replaceable>=<replaceable>value</replaceable>\n"
"</screen></informalexample> 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:3006
#, no-c-format
msgid "3c509.xcvr=3 3c509.irq=10"
msgstr "3c509.xcvr=3 3c509.irq=10"

#. Tag: title
#: boot-installer.xml:3012
#, no-c-format
msgid "Blacklisting kernel modules"
msgstr "Sortliste kernemoduler"

#. Tag: para
#: boot-installer.xml:3013
#, 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:3022
#, no-c-format
msgid ""
"You can blacklist a module using the following syntax: "
"<userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. "
"This will cause the module to be blacklisted in <filename>/etc/modprobe.d/"
"blacklist.local</filename> both during the installation and for the "
"installed system."
msgstr ""
"Du kan sortliste et modul med den følgende syntaks: "
"<userinput><replaceable>modulnavn</replaceable>.blacklist=yes</userinput>. "
"Dette vil gøre, at modulet bliver sortlistet i <filename>/etc/modprobe.d/"
"blacklist.local</filename> både under installationen og for det installerede "
"system."

#. Tag: para
#: boot-installer.xml:3030
#, 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:3046
#, no-c-format
msgid "Troubleshooting the Installation Process"
msgstr "Fejlsøgning af installationsprocessen"

#. Tag: title
#: boot-installer.xml:3051
#, no-c-format
msgid "CD-ROM Reliability"
msgstr "Cd-rom-troværdighed"

#. Tag: para
#: boot-installer.xml:3052
#, 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 &mdash; even after booting "
"successfully from CD-ROM &mdash; fail to recognize the CD-ROM 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å &mdash; "
"selv efter opstart fra cd-rom &mdash; mislykkes i at genkende cd-rommen "
"eller returnere fejl under læsning fra den under installationen."

#. Tag: para
#: boot-installer.xml:3059
#, 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:3065
#, 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:3070
#, no-c-format
msgid ""
"If the CD-ROM 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:3076
#, no-c-format
msgid ""
"If the installer fails to recognize a CD-ROM, try just running the option "
"<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </"
"menuchoice> 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 <menuchoice> <guimenuitem>Detekter og monter cd-rom</"
"guimenuitem> </menuchoice> 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:3086
#, no-c-format
msgid ""
"If this does not work, then try the suggestions in the subsections below. "
"Most, but not all, suggestions discussed there are valid for both CD-ROM and "
"DVD, but we'll use the term CD-ROM for simplicity."
msgstr ""
"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:3092
#, no-c-format
msgid ""
"If you cannot get the installation working from CD-ROM, try one of the other "
"installation methods that are available."
msgstr ""
"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:3100
#, no-c-format
msgid "Common issues"
msgstr "Gængse problemstillinger"

#. Tag: para
#: boot-installer.xml:3103
#, 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:3120
#, no-c-format
msgid ""
"Some very old CD-ROM drives do not work correctly if <quote>direct memory "
"access</quote> (DMA) is enabled for them."
msgstr ""
"Nogle meget gamle cd-rom-drev virker ikke korrekt hvis <quote>direct memory "
"access</quote> (DMA) er aktiveret for dem."

#. Tag: title
#: boot-installer.xml:3131
#, 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:3132
#, no-c-format
msgid "If the CD-ROM 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:3137
#, 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."
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:3144
#, 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 <filename>MD5SUMS</filename> file that "
"should be present in the same location as where you downloaded the image "
"from. <informalexample><screen>\n"
"$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
"a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst."
"iso</replaceable>\n"
"</screen></informalexample> Next, check that the md5sum of the burned CD-ROM "
"matches as well. The following command should work. It uses the size of the "
"image to read the correct number of bytes from the CD-ROM."
msgstr ""
"Hvis du hentede et iso-aftryk, så kontroller at md5summen for det aftryk "
"matcher det viste aftryk i filen <filename>MD5SUMS</filename>, som bør "
"befinde sig samme sted, som du hentede aftrykket fra. "
"<informalexample><screen>\n"
"$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
"a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst."
"iso</replaceable>\n"
"</screen></informalexample> 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:3157
#, no-c-format
msgid ""
"$ dd if=/dev/cdrom | \\\n"
"&gt; head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</"
"replaceable>` | \\\n"
"&gt; 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 ""
"&gt; head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</"
"replaceable>` | \\\n"
"&gt; 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:3162
#, no-c-format
msgid ""
"If, after the installer has been booted successfully, the CD-ROM is not "
"detected, sometimes simply trying again may solve the problem. If you have "
"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If "
"that does not work or if the CD-ROM is recognized but there are errors when "
"reading from it, try the suggestions listed below. Some basic knowledge of "
"&arch-kernel; is required for this. To execute any of the commands, you "
"should first switch to the second virtual console (VT2) and activate the "
"shell there."
msgstr ""
"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:3174
#, no-c-format
msgid ""
"Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
"(use <command>nano</command> as editor) to check for any specific error "
"messages. After that, also check the output of <command>dmesg</command>."
msgstr ""
"Skift til VT4 eller vis indholdet af <filename>/var/log/syslog</filename> "
"(brug <command>nano</command> som redigeringsprogram) til at kontrollere "
"efter specifikke fejlbeskeder. Derefter kontrolleres også resultatet af "
"<command>dmesg</command>."

#. Tag: para
#: boot-installer.xml:3181
#, no-c-format
msgid ""
"Check in the output of <command>dmesg</command> if your CD-ROM drive was "
"recognized. You should see something like (the lines do not necessarily have "
"to be consecutive): <informalexample><screen>\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"
"</screen></informalexample> 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 <command>modprobe</command>."
msgstr ""
"Kontroller i resultatet fra <command>dmesg</command> om dit cd-rom-drev blev "
"genkendt. Du bør se noget ala (linjerne skal ikke nødvendigvis være "
"fortløbende): <informalexample><screen>\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"
"</screen></informalexample> 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 "
"<command>modprobe</command>."

#. Tag: para
#: boot-installer.xml:3195
#, no-c-format
msgid ""
"Check that there is a device node for your CD-ROM drive under <filename>/dev/"
"</filename>. In the example above, this would be <filename>/dev/sr0</"
"filename>. There should also be a <filename>/dev/cdrom</filename>."
msgstr ""
"Kontroller at der er en enhedsknude for dit cd-rom-drev under <filename>/dev/"
"</filename>. I eksemplet ovenfor, skal dette være <filename>/dev/sr0</"
"filename>. Der skal også være et <filename>/dev/cdrom</filename>."

#. Tag: para
#: boot-installer.xml:3203
#, no-c-format
msgid ""
"Use the <command>mount</command> command to check if the CD-ROM is already "
"mounted; if not, try mounting it manually: <informalexample><screen>\n"
"$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
"</screen></informalexample> Check if there are any error messages after that "
"command."
msgstr ""
"Brug kommandoen <command>mount</command> til at kontrollere om cd-rommen "
"allerede er monteret; hvis ikke, så prøv at montere den manuelt: "
"<informalexample><screen>\n"
"$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
"</screen></informalexample> Kontroller hvis der er nogle fejlbeskeder efter "
"den kommando."

#. Tag: para
#: boot-installer.xml:3213
#, no-c-format
msgid ""
"Check if DMA is currently enabled: <informalexample><screen>\n"
"$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
"$ grep using_dma settings\n"
"using_dma      1       0       1       rw\n"
"</screen></informalexample> A <quote>1</quote> in the first column after "
"<literal>using_dma</literal> means it is enabled. If it is, try disabling "
"it: <informalexample><screen>\n"
"$ echo -n \"using_dma:0\" &gt;settings\n"
"</screen></informalexample> Make sure that you are in the directory for the "
"device that corresponds to your CD-ROM drive."
msgstr ""
"Kontroller hvis DMA er aktuelt aktiveret: <informalexample><screen>\n"
"$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
"$ grep using_dma settings\n"
"using_dma      1       0       1       rw\n"
"</screen></informalexample> Et <quote>1</quote> i den første kolonne efter "
"<literal>using_dma</literal> betyder at den er aktiveret. Hvis den er, så "
"prøv at deaktivere den: <informalexample><screen>\n"
"$ echo -n \"using_dma:0\" &gt;settings\n"
"</screen></informalexample> Sikr dig at du er i mappen for enheden som "
"svarer til dit cd-rom-drev."

#. Tag: para
#: boot-installer.xml:3228
#, no-c-format
msgid ""
"If there are any problems during the installation, try checking the "
"integrity of the CD-ROM using the option near the bottom of the installer's "
"main menu. This option can also be used as a general test if the CD-ROM can "
"be read reliably."
msgstr ""
"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:3243
#, no-c-format
msgid "Floppy Disk Reliability"
msgstr "Troværdighed for disketter"

#. Tag: para
#: boot-installer.xml:3245
#, no-c-format
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."

#. Tag: para
#: boot-installer.xml:3250
#, no-c-format
msgid ""
"The boot floppy is the floppy with the worst problems, because it is read by "
"the hardware directly, before Linux boots. Often, the hardware doesn't read "
"as reliably as the Linux floppy disk driver, and may just stop without "
"printing an error message if it reads incorrect data. There can also be "
"failures in the driver floppies, most of which indicate themselves with a "
"flood of messages about disk I/O errors."
msgstr ""
"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."

#. Tag: para
#: boot-installer.xml:3259
#, no-c-format
msgid ""
"If you are having the installation stall at a particular floppy, the first "
"thing you should do is write the image to a <emphasis>different</emphasis> "
"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 <emphasis>anden</emphasis> 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."

#. Tag: para
#: boot-installer.xml:3268
#, no-c-format
msgid ""
"One user reports he had to write the images to floppy <emphasis>three</"
"emphasis> times before one worked, and then everything was fine with the "
"third floppy."
msgstr ""
"En bruger indrapporterede at han skulle skrive aftrykket til disketten "
"<emphasis>tre</emphasis> gange før der var en der virkede, og så var alt "
"okay med den tredje diskette."

#. Tag: para
#: boot-installer.xml:3274
#, no-c-format
msgid ""
"Normally you should not have to download a floppy image again, but if you "
"are experiencing problems it is always useful to verify that the images were "
"downloaded correctly by verifying their md5sums."
msgstr ""
"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."

#. Tag: para
#: boot-installer.xml:3280
#, no-c-format
msgid ""
"Other users have reported that simply rebooting a few times with the same "
"floppy in the floppy drive can lead to a successful boot. This is all due to "
"buggy hardware or firmware floppy drivers."
msgstr ""
"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."

#. Tag: title
#: boot-installer.xml:3289
#, no-c-format
msgid "Boot Configuration"
msgstr "Opstartskonfiguration"

#. Tag: para
#: boot-installer.xml:3291
#, 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 "
"<xref linkend=\"boot-parms\"/>."
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 <xref linkend=\"boot-parms\"/>."

#. Tag: para
#: boot-installer.xml:3300
#, no-c-format
msgid ""
"In some cases, malfunctions can be caused by missing device firmware (see "
"<xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/"
">)."
msgstr ""
"I nogle tilfælde kan fejlsituationer opstå på grund af manglende firmware "
"for udstyr (se <xref linkend=\"hardware-firmware\"/> og <xref linkend="
"\"loading-firmware\"/>)."

#. Tag: para
#: boot-installer.xml:3311
#, 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:3322
#, no-c-format
msgid "dmesg"
msgstr "dmesg"

#. Tag: userinput
#: boot-installer.xml:3324
#, no-c-format
msgid "lspci"
msgstr "lspci"

#. Tag: userinput
#: boot-installer.xml:3326
#, no-c-format
msgid "lsmod"
msgstr "lsmod"

#. Tag: userinput
#: boot-installer.xml:3328
#, no-c-format
msgid "amixer"
msgstr "amixer"

#. Tag: title
#: boot-installer.xml:3336 boot-installer.xml:3447
#, no-c-format
msgid "Common &arch-title; Installation Problems"
msgstr "Gængse &arch-title;-installationsproblemer"

#. Tag: para
#: boot-installer.xml:3337
#, 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:3388
#, 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 <userinput>fb=false</"
"userinput> to disable the framebuffer console. Only a reduced set of "
"languages will be available during the installation due to limited console "
"features. See <xref linkend=\"boot-parms\"/> 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 "
"<userinput>fb=false</userinput> 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 <xref linkend=\"boot-parms\"/> for "
"detaljer."

#. Tag: title
#: boot-installer.xml:3402
#, no-c-format
msgid "System Freeze During the PCMCIA Configuration Phase"
msgstr "Systemfrysning under PCMCIA-konfigurationsfasen"

#. Tag: para
#: boot-installer.xml:3403
#, 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 <userinput>hw-detect/start_pcmcia=false</userinput> 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 <userinput>hw-detect/"
"start_pcmcia=false</userinput>. Du kan så konfigurere PCMCIA efter at "
"installationen er færdig og ekskludere ressourceintervallet, der medfører "
"problemerne."

#. Tag: para
#: boot-installer.xml:3413
#, 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 "
"<userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list "
"of some common resource range options in the <ulink url=\"http://pcmcia-cs."
"sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource "
"settings section of the PCMCIA HOWTO</ulink>. 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 <userinput>exclude port 0x800-0x8ff</userinput>. Der er også en "
"liste over nogle gængse intervalindstillinger for ressourcer i afsnittet for "
"<ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1."
"html#ss1.12\">Systemressourceindstillinger for PCMCIA - hjælp</ulink>. "
"bemærk at du skal undlade kommaerne, hvis nogen, når du indtaster denne "
"værdi i installationsprogrammet."

#. Tag: para
#: boot-installer.xml:3448
#, 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:3454
#, no-c-format
msgid "Misdirected video output"
msgstr "Fejlramt videoresultat"

#. Tag: para
#: boot-installer.xml:3455
#, 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: <informalexample><screen>\n"
"Remapping the kernel... done\n"
"Booting Linux...\n"
"</screen></informalexample> 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 <userinput>video=atyfb:off</userinput>."
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: <informalexample><screen>\n"
"Remapping the kernel... done\n"
"Booting Linux...\n"
"</screen></informalexample> 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 <userinput>video=atyfb:off</userinput>."

#. Tag: para
#: boot-installer.xml:3469
#, no-c-format
msgid ""
"Note that you may also have to manually add this parameter to the silo "
"configuration (edit <filename>/target/etc/silo.conf</filename> before "
"rebooting) and, if you installed X11, modify the video driver in <filename>/"
"etc/X11/xorg.conf</filename>."
msgstr ""
"Bemærk at du måske også manuelt skal tilføje denne paramter til silo-"
"konfigurationen (rediger <filename>/target/etc/silo.conf</filename> før "
"genstart) og, hvis du installerede X11, så ændr videodriveren i <filename>/"
"etc/X11/xorg.conf</filename>."

#. Tag: title
#: boot-installer.xml:3480
#, 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:3481
#, 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:3487
#, 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:3496
#, no-c-format
msgid "Interpreting the Kernel Startup Messages"
msgstr "Fortolker kernens opstartsbeskeder"

#. Tag: para
#: boot-installer.xml:3498
#, no-c-format
msgid ""
"During the boot sequence, you may see many messages in the form "
"<computeroutput>can't find <replaceable>something</replaceable></"
"computeroutput>, or <computeroutput><replaceable>something</replaceable> not "
"present</computeroutput>, <computeroutput>can't initialize "
"<replaceable>something</replaceable></computeroutput>, or even "
"<computeroutput>this driver release depends on <replaceable>something</"
"replaceable></computeroutput>. 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 <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-"
"baking\"/>)</phrase>."
msgstr ""
"Under opstartssekvensen, kan du se beskeder i form af <computeroutput>kan "
"ikke finde <replaceable>et eller andet</replaceable></computeroutput> eller "
"<computeroutput><replaceable>noget</replaceable> er ikke til stede</"
"computeroutput>, <computeroutput>kan ikke initialisere <replaceable>noget</"
"replaceable></computeroutput>, eller endda <computeroutput>denne "
"driverudgivelse afhænger af <replaceable>et eller andet</replaceable></"
"computeroutput>. 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 <phrase arch=\"linux-any\">(see <xref "
"linkend=\"kernel-baking\"/>)</phrase>."

#. Tag: title
#: boot-installer.xml:3523
#, no-c-format
msgid "Reporting Installation Problems"
msgstr "Rapportering af installationsproblemer"

#. Tag: para
#: boot-installer.xml:3524
#, no-c-format
msgid ""
"If you get through the initial boot phase but cannot complete the install, "
"the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. "
"It lets you store system error logs and configuration information from the "
"installer to a floppy, or download them using a web browser. This "
"information may provide clues as to what went wrong and how to fix it. If "
"you are submitting a bug report, you may want to attach this information to "
"the bug report."
msgstr ""
"Hvis du kommer igennem den indledende opstartsfase men ikke kan færdiggøre "
"installationen, så kan menupunktet <guimenuitem>Gem fejlsøgningslog</"
"guimenuitem> 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:3535
#, no-c-format
msgid ""
"Other pertinent installation messages may be found in <filename>/var/log/</"
"filename> during the installation, and <filename>/var/log/installer/</"
"filename> after the computer has been booted into the installed system."
msgstr ""
"Andre relevante installationsbeskeder kan findes i <filename>/var/log/</"
"filename> under installationen og <filename>/var/log/installer/</filename> "
"efter at computeren er blevet startet op i det installerede system."

#. Tag: title
#: boot-installer.xml:3546
#, no-c-format
msgid "Submitting Installation Reports"
msgstr "Indsendelse af installationsrapporter"

#. Tag: para
#: boot-installer.xml:3547
#, 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:3554
#, 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:3560
#, no-c-format
msgid ""
"If you have a working &debian; system, the easiest way to send an "
"installation report is to install the <classname>installation-report</"
"classname> and <classname>reportbug</classname> packages (<command>apt "
"install installation-report reportbug</command>), configure "
"<classname>reportbug</classname> as explained in <xref linkend=\"mail-"
"outgoing\"/>, and run the command <command>reportbug installation-reports</"
"command>."
msgstr ""
"Hvis du har et fungerende &debian;-system, så er den nemmeste måde at sende "
"en installationsrapport at installere pakkerne <classname>installation-"
"report</classname> og <classname>reportbug</classname> (<command>apt install "
"installation-report reportbug</command>), konfigurere <classname>reportbug</"
"classname> som forklaret i <xref linkend=\"mail-outgoing\"/>, og køre "
"kommandoen <command>reportbug installation-reports</command>."

#. Tag: para
#: boot-installer.xml:3570
#, 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 "
"<classname>installation-reports</classname> pseudo package, by sending it to "
"<email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
"Package: installation-reports\n"
"\n"
"Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;\n"
"Image version: &lt;Full URL to image you downloaded is best&gt;\n"
"Date: &lt;Date and time of the install&gt;\n"
"\n"
"Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n"
"Processor:\n"
"Memory:\n"
"Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;\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"
"&lt;Description of the install, in prose, and any thoughts, comments\n"
"      and ideas you had during the initial install.&gt;\n"
"</screen></informalexample> 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 <classname>installation-reports</classname> ved at sende den "
"til <email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
"Pakke: installation-reports\n"
"\n"
"Boot method: &lt;Hvordan igangsatte du installationsprogrammet? cd? "
"diskette? netværk?&gt;\n"
"Image version: &lt;Fuld adresse til aftrykket du hentede er bedst&gt;\n"
"Date: &lt;Dato og tidspunkt for installationen&gt;\n"
"\n"
"Machine: &lt;Beskrivelse af maskine (f.eks. IBM Thinkpad R32)&gt;\n"
"Processor:\n"
"Memory:\n"
"Partitions: &lt;df -Tl er nok; den rå partitionstabel foretrækkes&gt;\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"
"&lt;Beskrivelse af installationen, i tekst, og eventuelle tanker, "
"kommentarer\n"
"      og ideer du havde under den oprindelige installation.&gt;\n"
"</screen></informalexample> 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 "Preseeding"
#~ msgstr "Forhåndsindstilling"

#~ msgid "SGI TFTP Booting"
#~ msgstr "SGI TFTP-opstart"

#~ msgid ""
#~ "After entering the command monitor use <informalexample><screen>\n"
#~ "bootp():\n"
#~ "</screen></informalexample> 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 <envar>netaddr</envar> environment variable. Type "
#~ "<informalexample><screen>\n"
#~ "unsetenv netaddr\n"
#~ "</screen></informalexample> in the command monitor to do this."
#~ msgstr ""
#~ "Efter indtastning så bruger kommandoovervågningen "
#~ "<informalexample><screen>\n"
#~ "bootp():\n"
#~ "</screen></informalexample> 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 "
#~ "<envar>netaddr</envar>. Tast <informalexample><screen>\n"
#~ "unsetenv netaddr\n"
#~ "</screen></informalexample> i kommandoovervågningen for dette."

#~ msgid ""
#~ "On SGI machines you can append boot parameters to the <command>bootp():</"
#~ "command> command in the command monitor."
#~ msgstr ""
#~ "På SGI-maskiner kan du tilføje opstartsparametre til kommandoen "
#~ "<command>bootp():</command> i kommandoskærmen."

#~ msgid ""
#~ "Following the <command>bootp():</command> 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: <informalexample><screen>\n"
#~ "bootp():/boot/tftpboot.img\n"
#~ "</screen></informalexample> Further kernel parameters can be passed via "
#~ "<command>append</command>:"
#~ msgstr ""
#~ "Efter kommandoen <command>bootp():</command> 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: <informalexample><screen>\n"
#~ "bootp():/boot/tftpboot.img\n"
#~ "</screen></informalexample> Yderligere kerneparametre kan sendes via "
#~ "<command>append</command>:"

#~ msgid "bootp(): append=\"root=/dev/sda1\""
#~ msgstr "bootp(): append=\"root=/dev/sda1\""