path: root/po/da/boot-new.po

# Danish translation of boot-new.
# Copyright (C) 2012 Free Software Foundation, Inc.
# Joe Hansen <joedalton2@yahoo.dk>, 2012.
#
msgid ""
msgstr ""
"Project-Id-Version: boot-new\n"
"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
"POT-Creation-Date: 2012-06-16 09:12+0000\n"
"PO-Revision-Date: 2012-11-25 21:25+0100\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-new.xml:5
#, no-c-format
msgid "Booting Into Your New &debian; System"
msgstr "Start op i dit nye &debian;-system"

#. Tag: title
#: boot-new.xml:7
#, no-c-format
msgid "The Moment of Truth"
msgstr "Sandhedens øjeblik"

#. Tag: para
#: boot-new.xml:8
#, no-c-format
msgid "Your system's first boot on its own power is what electrical engineers call the <quote>smoke test</quote>."
msgstr ""
"Dit systems første opstart på egen hånd er hvad teknikerne kalder for <quote>den endelige test (»smoke test«)</quote>."

#. Tag: para
#: boot-new.xml:13
#, no-c-format
msgid "If you did a default installation, the first thing you should see when you boot the system is the menu of the <classname>grub</classname><phrase arch=\"x86\"> or possibly the <classname>lilo</classname> bootloader</phrase>. The first choices in the menu will be for your new &debian; system. If you had any other operating systems on your computer (like Windows) that were detected by the installation system, those will be listed lower down in the menu."
msgstr ""
"Hvis du udførte en standardinstallation, så bør den første ting du ser ved opstart af systemet være menuen for <classname>grub</classname><phrase arch=\"x86\"> eller muligvis opstartsindlæseren <classname>lilo</classname></phrase>. Det første valg i menuen vil være for dit nye &debian;-system. Hvis du havde andre operativsystemer på din computer (såsom Windows), som blev deteketeret af installationssystemet, så vil disse blive vist længere nede i menuen."

#. Tag: para
#: boot-new.xml:23
#, no-c-format
msgid "If the system fails to start up correctly, don't panic. If the installation was successful, chances are good that there is only a relatively minor problem that is preventing the system from booting &debian;. In most cases such problems can be fixed without having to repeat the installation. One available option to fix boot problems is to use the installer's built-in rescue mode (see <xref linkend=\"rescue\"/>)."
msgstr ""
"Hvis systemet ikke starter korrekt op, så gå ikke i panik. Hvis installationen lykkedes, er der gode chancer for, at det kun er et mindre problem, som forhindrer systemet i at starte &debian; op. I de fleste tilfælde kan sådanne problemer rettes uden at skulle gentage installationen. En mulig måde at rette opstartsproblemer på er at bruge installationsprogrammets indbyggede redningstilstand (se <xref linkend=\"rescue\"/>)."

#. Tag: para
#: boot-new.xml:32
#, no-c-format
msgid "If you are new to &debian; and &arch-kernel;, you may need some help from more experienced users. <phrase arch=\"x86\">For direct on-line help you can try the IRC channels #debian or #debian-boot on the OFTC network. Alternatively you can contact the <ulink url=\"&url-list-subscribe;\">debian-user mailing list</ulink>.</phrase> <phrase arch=\"not-x86\">For less common architectures like &arch-title;, your best option is to ask on the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink>.</phrase> You can also file an installation report as described in <xref linkend=\"submit-bug\"/>. Please make sure that you describe your problem clearly and include any messages that are displayed and may help others to diagnose the issue."
msgstr ""
"Hvis du er ny til &debian; og &arch-kernel;, så har du måske brug for lidt hjælp fra mere erfarne brugere. <phrase arch=\"x86\">For direkte hjælp via internettet kan du prøve i IRC-kanalerne #debian eller #debian-boot på OFTC-netværket. Alternativt kan du kontakte <ulink url=\"&url-list-subscribe;\">postlisten for debianbrugere</ulink>.</phrase> <phrase arch=\"not-x86\">For mindre udbredte arkitekturer såsom  &arch-title;, dit bedste valg er at spørge på <ulink url=\"&url-list-subscribe;\">debian-&arch-listname;-postlisten</ulink>.</phrase> Du kan også indsende en installationsrapport som beskrevet i <xref linkend=\"submit-bug\"/>. Vær sikker på at du beskriver dit problem tydeligt og inkludere alle beskeder som vises og som kan hjælpe andre med at diagnosticere problemet."

#. Tag: para
#: boot-new.xml:48
#, no-c-format
msgid "If you had any other operating systems on your computer that were not detected or not detected correctly, please file an installation report."
msgstr ""
"Hvis du havde et andet operativsystem på din computer, som ikke blev detekteret eller ikke detekteret korrekt, så indsend venligst en installationsrapport."

#. Tag: title
#: boot-new.xml:56
#, no-c-format
msgid "OldWorld PowerMacs"
msgstr "OldWorld PowerMacs"

#. Tag: para
#: boot-new.xml:57
#, no-c-format
msgid "If the machine fails to boot after completing the installation, and stops with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</userinput> followed by &enterkey;. (The default boot configuration in <filename>quik.conf</filename> is labeled Linux). The labels defined in <filename>quik.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also try booting back into the installer, and editing the <filename>/target/etc/quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>."
msgstr ""
"Hvis maskinen ikke kan starte op efter at installationen er færdig og stopper med en <prompt>boot:</prompt>-prompt, så prøv at indtaste <userinput>Linux</userinput> efterfulgt af &enterkey;. (Standardopstartskonfigurationen i <filename>quik.conf</filename> har etiketten Linux). Etiketterne defineret i <filename>quik.conf</filename> vil blive vist hvis du trykker på tasten <keycap>Tab</keycap> ved <prompt>boot:</prompt>-prompten. Du kan også forsøge at starte op igen i installationsprogrammet og redigere <filename>/target/etc/quik.conf</filename> placeret der af trinnet <guimenuitem>Installer Quik på en harddisk</guimenuitem>. Ideer til håndtering af <command>quik</command> er tilgængelige på <ulink url=\"&url-powerpc-quik-faq;\"></ulink>."

#. Tag: para
#: boot-new.xml:71
#, no-c-format
msgid "To boot back into MacOS without resetting the nvram, type <userinput>bye</userinput> at the OpenFirmware prompt (assuming MacOS has not been removed from the machine). To obtain an OpenFirmware prompt, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. If you need to reset the OpenFirmware nvram changes to the MacOS default in order to boot back to MacOS, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine."
msgstr ""
"For at starte op i MacOS uden at nulstille nvram, så tast <userinput>bye</userinput> ved OpenFirmware-prompten (antager at MacOS ikke er blevet fjernet fra maskinen). For at få en OpenFirmware-prompt, så hold tasterne <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</keycap> <keycap>f</keycap> </keycombo> nede mens du koldstarter maskinen. Hvis du skal nulstille OpenFirmware nvram-ændringerne til MacOS-standarden for at starte op i MacOS, så hold tasterne <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> nede, mens du koldstarter maskinen."

#. Tag: para
#: boot-new.xml:84
#, no-c-format
msgid "If you use <command>BootX</command> to boot into the installed system, just select your desired kernel in the <filename>Linux Kernels</filename> folder, un-choose the ramdisk option, and add a root device corresponding to your installation; e.g. <userinput>/dev/hda8</userinput>."
msgstr ""
"Hvis du bruger <command>BootX</command> til at starte op i det installerede system, så vælg din ønskede kerne i mappen <filename>Linux Kernels</filename>, fravælg indstillingen ramdisk og tilføj en rodenhed der svarer til din installation; f.eks. <userinput>/dev/hda8</userinput>."

#. Tag: title
#: boot-new.xml:96
#, no-c-format
msgid "NewWorld PowerMacs"
msgstr "NewWorld PowerMacs"

#. Tag: para
#: boot-new.xml:97
#, no-c-format
msgid "On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key and get a graphical screen with a button for each bootable OS, &debian-gnu; will be a button with a small penguin icon."
msgstr ""
"På G4-maskiner og iBooks, kan du holde tasten <keycap>option</keycap> nede og få en grafisk skærm med en knap for hvert operativsystem der kan startes op, &debian-gnu; vil være en knap med et lille pingvinikon."

#. Tag: para
#: boot-new.xml:104
#, no-c-format
msgid "If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-device</envar> variable you should reset OpenFirmware to its default configuration. To do this hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine."
msgstr ""
"Hvis du beholdt MacOS og det på et tidspunkt ændrer OpenFirmware <envar>boot-device</envar>-variablen, så skal du nulstille OpenFirmware til sin standardkonfiguration. For at gøre dette holder du tasterne <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> nede mens du koldstarter maskinen."

#. Tag: para
#: boot-new.xml:112
#, no-c-format
msgid "The labels defined in <filename>yaboot.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt."
msgstr ""
"Etiketterne defineret i <filename>yaboot.conf</filename> vil blive vist hvis du trykker tasten <keycap>Tab</keycap> ned ved <prompt>boot:</prompt>-prompten."

#. Tag: para
#: boot-new.xml:118
#, no-c-format
msgid "Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian-gnu; by default (if you correctly partitioned and placed the Apple_Bootstrap partition first). If you have &debian-gnu; on a SCSI disk and MacOS on an IDE disk this may not work and you will have to enter OpenFirmware and set the <envar>boot-device</envar> variable, <command>ybin</command> normally does this automatically."
msgstr ""
"Nulstilling af OpenFirmware på G3- eller G4-udstyr vil få den til at starte &debian-gnu; som standard (hvis du korrekt partitionerede og placerede Apple_Bootstrap-partitionen først."

#. Tag: para
#: boot-new.xml:127
#, no-c-format
msgid "After you boot &debian-gnu; for the first time you can add any additional options you desire (such as dual boot options) to <filename>/etc/yaboot.conf</filename> and run <command>ybin</command> to update your boot partition with the changed configuration. Please read the <ulink url=\"&url-powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information."
msgstr ""
"Efter at du har startet &debian-gnu; op første gang kan du tilføje yderligere ønskede indstillinger (såsom indstillinger for dualboot) til <filename>/etc/yaboot.conf</filename> og køre <command>ybin</command> for at opdatere din opstartspartition med den ændrede konfiguration. Læs venligst <ulink url=\"&url-powerpc-yaboot-faq;\">yaboot-hjælpen</ulink> for yderligere information."

#. Tag: title
#: boot-new.xml:145
#, no-c-format
msgid "Mounting encrypted volumes"
msgstr "Montering af krypterede diskenheder"

#. Tag: para
#: boot-new.xml:147
#, no-c-format
msgid "If you created encrypted volumes during the installation and assigned them mount points, you will be asked to enter the passphrase for each of these volumes during the boot. The actual procedure differs slightly between dm-crypt and loop-AES."
msgstr ""
"Hvis du oprettede krypterede diskenheder under installationen og tildelte dem monteringspunkter, så vil du blive anmodt om en adgangsfrase for hver af disse diskenheder under opstarten. Den aktuelle procedure er en smule anderledes mellem dm-crypt og loop-AES."

#. Tag: title
#: boot-new.xml:157
#, no-c-format
msgid "dm-crypt"
msgstr "dm-crypt"

#. Tag: para
#: boot-new.xml:159
#, no-c-format
msgid ""
"For partitions encrypted using dm-crypt you will be shown the following prompt during the boot: <informalexample><screen>\n"
"Starting early crypto disks... <replaceable>part</replaceable>_crypt(starting)\n"
"Enter LUKS passphrase:\n"
"</screen></informalexample> In the first line of the prompt, <replaceable>part</replaceable> is the name of the underlying partition, e.g. sda2 or md0. You are now probably wondering <emphasis>for which volume</emphasis> you are actually entering the passphrase. Does it relate to your <filename>/home</filename>? Or to <filename>/var</filename>? Of course, if you have just one encrypted volume, this is easy and you can just enter the passphrase you used when setting up this volume. If you set up more than one encrypted volume during the installation, the notes you wrote down as the last step in <xref linkend=\"partman-crypto\"/> come in handy. If you did not make a note of the mapping between <filename><replaceable>part</replaceable>_crypt</filename> and the mount points before, you can still find it in <filename>/etc/crypttab</filename> and <filename>/etc/fstab</filename> of your new system."
msgstr ""
"For partitioner krypteret med dm-crypt får du vist den følgende prompt under opstarten: <informalexample><screen>\n"
"Starting early crypto disks... <replaceable>part</replaceable>_crypt(starting)\n"
"Enter LUKS passphrase:\n"
"</screen></informalexample> I den første linje af prompten, er <replaceable>part</replaceable> navnet på den underliggende partition, f.eks. sda2 eller md0. Du undrer dig nu sikkert over <emphasis>hvilken diskenhed</emphasis> du reelt indtaster adgangsfrasen for. Drejer det sig om din <filename>/home</filename>? Eller til <filename>/var</filename>? Hvis du kun har en krypteret diskenhed er dette selvfølgelig nemt og du kan bare indtaste adgangsfrasen du brugte ved opsætning af denne diskenhed. Hvis du har opsat mere end en krypteret diskenhed under installationen, så er noterne du skrev ned som det sidste trin i <xref linkend=\"partman-crypto\"/> rigtig gode nu. Hvis du ikke skrev opsætningen mellem <filename><replaceable>part</replaceable>_crypt</filename> og monteringspunkter før ned, så kan du stadig finde den i <filename>/etc/crypttab</filename> og <filename>/etc/fstab</filename> i dit nye system."

#. Tag: para
#: boot-new.xml:182
#, no-c-format
msgid "The prompt may look somewhat different when an encrypted root file system is mounted. This depends on which initramfs generator was used to generate the initrd used to boot the system. The example below is for an initrd generated using <classname>initramfs-tools</classname>:"
msgstr ""
"Prompten kan se noget anderledes ud når et krypteret rod-filsystem er monteret. Dette afhænger af hvilke initramfs-generatorer der blev brugt til at oprette initrd'en brugt til at starte systemet op med. Eksemplet nedenfor er for en initrd oprettet med <classname>initramfs-tools</classname>:"

#. Tag: screen
#: boot-new.xml:189
#, no-c-format
msgid ""
"Begin: Mounting <emphasis>root file system</emphasis>... ...\n"
"Begin: Running /scripts/local-top ...\n"
"Enter LUKS passphrase:"
msgstr ""
"Begin: Mounting <emphasis>root file system</emphasis>... ...\n"
"Begin: Running /scripts/local-top ...\n"
"Enter LUKS passphrase:"

#. Tag: para
#: boot-new.xml:191 boot-new.xml:216
#, no-c-format
msgid "No characters (even asterisks) will be shown while entering the passphrase. If you enter the wrong passphrase, you have two more tries to correct it. After the third try the boot process will skip this volume and continue to mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting\"/> for further information."
msgstr ""
"Ingen tegn (heller ikke stjerner) vil blive vist mens du indtaster adgangsfrasen. Hvis du indtaster forkert adgangsfrase, så har du to yderligere forsøg. Efter det tredje forsøg vil opstartsprocessen springe denne diskenhed over og fortsætte med at montere det næste filsystem. Se venligst <xref linkend=\"crypto-troubleshooting\"/> for yderligere information."

#. Tag: para
#: boot-new.xml:199 boot-new.xml:224
#, no-c-format
msgid "After entering all passphrases the boot should continue as usual."
msgstr ""
"Efter indtastning af alle adgangsfraser bør opstarten fortsætte som normalt."

#. Tag: title
#: boot-new.xml:207
#, no-c-format
msgid "loop-AES"
msgstr "loop-AES"

#. Tag: para
#: boot-new.xml:209
#, no-c-format
msgid "For partitions encrypted using loop-AES you will be shown the following prompt during the boot:"
msgstr ""
"For partitioner krypteret med loop-AES vil du blive vist den følgende prompt under opstarten:"

#. Tag: screen
#: boot-new.xml:214
#, no-c-format
msgid ""
"Checking loop-encrypted file systems.\n"
"Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</replaceable>)\n"
"Password:"
msgstr ""
"Checking loop-encrypted file systems.\n"
"Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</replaceable>)\n"
"Password:"

#. Tag: title
#: boot-new.xml:232
#, no-c-format
msgid "Troubleshooting"
msgstr "Fejlsøgning"

#. Tag: para
#: boot-new.xml:234
#, no-c-format
msgid "If some of the encrypted volumes could not be mounted because a wrong passphrase was entered, you will have to mount them manually after the boot. There are several cases."
msgstr ""
"Hvis nogle af de krypterede diskenheder ikke kunne monteres på grund af en forkert adgangsfrase, så skal du montere dem manuelt efter opstarten. Der er flere tilfælde."

#. Tag: para
#: boot-new.xml:243
#, no-c-format
msgid "The first case concerns the root partition. When it is not mounted correctly, the boot process will halt and you will have to reboot the computer to try again."
msgstr ""
"Det første tilfælde vedrører rodpartitionen. Når den ikke er monteret korrekt, så vil opstartsprocessen stoppe og du vil skulle genstarte computeren for at forsøge igen."

#. Tag: para
#: boot-new.xml:250
#, no-c-format
msgid ""
"The easiest case is for encrypted volumes holding data like <filename>/home</filename> or <filename>/srv</filename>. You can simply mount them manually after the boot. For loop-AES this is a one-step operation: <informalexample><screen>\n"
"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>\n"
"<prompt>Password:</prompt>\n"
"</screen></informalexample> where <replaceable>/mount_point</replaceable> should be replaced by the particular directory (e.g. <filename>/home</filename>). The only difference from an ordinary mount is that you will be asked to enter the passphrase for this volume."
msgstr ""
"Det nemmeste tilfælde er for krypterede diskenheder, der indeholder data såsom <filename>/home</filename> eller <filename>/srv</filename>. Du kan montere dem manuelt efter opstarten. For loop-AES er dette en et-trins operation: <informalexample><screen>\n"
"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>\n"
"<prompt>Adgangskode:</prompt>\n"
"</screen></informalexample> hvor <replaceable>/mount_point</replaceable> skal erstattes med den specifikke mappe (f.eks. <filename>/home</filename>). Den eneste forskel fra en normal montering er at du vil blive anmodt om at indtaste adgangsfrasen for denne diskenhed."

#. Tag: para
#: boot-new.xml:264
#, no-c-format
msgid ""
"For dm-crypt this is a bit trickier. First you need to register the volumes with <application>device mapper</application> by running: <informalexample><screen>\n"
"<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
"</screen></informalexample> This will scan all volumes mentioned in <filename>/etc/crypttab</filename> and will create appropriate devices under the <filename>/dev</filename> directory after entering the correct passphrases. (Already registered volumes will be skipped, so you can repeat this command several times without worrying.) After successful registration you can simply mount the volumes the usual way:"
msgstr ""
"For dm-crypt er det en smule sværere. Først skal du registrere diskenhederne med <application>device mapper</application> ved at køre: <informalexample><screen>\n"
"<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
"</screen></informalexample> Dette vil skanne alle diskenheder nævnt i <filename>/etc/crypttab</filename> og vil oprette passende enheder under mappen <filename>/dev</filename> efter indtastning af korrekt adgangsfrase. (Allerede registrerede diskenheder vil blive sprunget over, så du kan gentage denne kommando flere gange uden problemer). Efter succesfuld registrering kan du montere diskenhederne på den normale måde:"

#. Tag: screen
#: boot-new.xml:279
#, no-c-format
msgid "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>"
msgstr ""
"<prompt>#</prompt> <userinput>mount <replaceable>/monteringspunkt</replaceable></userinput>"

#. Tag: para
#: boot-new.xml:282
#, no-c-format
msgid ""
"If any volume holding noncritical system files could not be mounted (<filename>/usr</filename> or <filename>/var</filename>), the system should still boot and you should be able to mount the volumes manually like in the previous case. However, you will also need to (re)start any services usually running in your default runlevel because it is very likely that they were not started. The easiest way to achieve this is by switching to the first runlevel and back by entering <informalexample><screen>\n"
"<prompt>#</prompt> <userinput>init 1</userinput>\n"
"</screen></informalexample> at the shell prompt and pressing <keycombo> <keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the root password."
msgstr ""
"Hvis en diskenhed indeholdende ikkekritiske systemfiler ikke kunne monteres (<filename>/usr</filename> eller <filename>/var</filename>), bør systemet stadig kunne montere diskenhederne manuelt ligesom i det forrige tilfælde. Du skal dog også (gen)starte alle tjenester der normalt kører i dit normale kørselsniveau, da det er meget sandsynligt, at de ikke blev startet. Den nemmeste måde at opnå dette på er at skifte til det første kørselsniveau og tilbage igen ved at taste <informalexample><screen>\n"
"<prompt>#</prompt> <userinput>init 1</userinput>\n"
"</screen></informalexample> ved skalprompten og trykke på <keycombo> <keycap>Control</keycap> <keycap>D</keycap> </keycombo> når du bliver anmodt om root-adgangskoden."

#. Tag: title
#: boot-new.xml:305
#, no-c-format
msgid "Log In"
msgstr "Log ind"

#. Tag: para
#: boot-new.xml:307
#, no-c-format
msgid "Once your system boots, you'll be presented with the login prompt. Log in using the personal login and password you selected during the installation process. Your system is now ready for use."
msgstr ""
"Når dit system starter op, vil du blive præsenteret for logind-prompten. Log ind med dit personlige logind og adgangskode, du valgte under installationsprocessen. Dit system er nu klar til brug."

#. Tag: para
#: boot-new.xml:313
#, no-c-format
msgid "If you are a new user, you may want to explore the documentation which is already installed on your system as you start to use it. There are currently several documentation systems, work is proceeding on integrating the different types of documentation. Here are a few starting points."
msgstr ""
"Hvis du er en ny bruger, så kan du kigge i dokumentationen, som allerede er installeret på dit system, når du begynder at bruge det. Der er i øjeblikket flere dokumentationssystemer, arbejde er i gang med at integrere de forskellige typer af dokumentation. Her er nogle få udgangspunkter."

#. Tag: para
#: boot-new.xml:321
#, no-c-format
msgid "Documentation accompanying programs you have installed can be found in <filename>/usr/share/doc/</filename>, under a subdirectory named after the program (or, more precise, the &debian; package that contains the program). However, more extensive documentation is often packaged separately in special documentation packages that are mostly not installed by default. For example, documentation about the package management tool <command>apt</command> can be found in the packages <classname>apt-doc</classname> or <classname>apt-howto</classname>."
msgstr ""
"Dokumentation for programmer du har installeret kan findes i <filename>/usr/share/doc/</filename> i en undermappe navngivet efter programmet (eller mere præcist, &debian;-pakken som indeholder programmet). Mere omfattende dokumentation er ofte pakket for sig selv i specielle dokumentationspakker som normalt ikke installeres som standard. For eksempel kan dokumentationen for pakkehåndteringsværktøjet <command>apt</command> findes i pakkerne <classname>apt-doc</classname> eller <classname>apt-howto</classname>."

#. Tag: para
#: boot-new.xml:332
#, no-c-format
msgid "In addition, there are some special folders within the <filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</emphasis> (compressed) format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. After installing <classname>dhelp</classname>, you will find a browsable index of documentation in <filename>/usr/share/doc/HTML/index.html</filename>."
msgstr ""
"Derudover er der nogle specielle mapper i hierarkiet <filename>/usr/share/doc/</filename>. Linux-hjælp installeres i formatet <emphasis>.gz</emphasis> (komprimeret), i <filename>/usr/share/doc/HOWTO/en-txt/</filename>. Efter installation af <classname>dhelp</classname>, vil du kunne se et indeks for dokumentationen i <filename>/usr/share/doc/HTML/index.html</filename>."

#. Tag: para
#: boot-new.xml:341
#, no-c-format
msgid ""
"One easy way to view these documents using a text based browser is to enter the following commands: <informalexample><screen>\n"
"$ cd /usr/share/doc/\n"
"$ w3m .\n"
"</screen></informalexample> The dot after the <command>w3m</command> command tells it to show the contents of the current directory."
msgstr ""
"En nem måde at vise disse dokumenter med en tekstbaseret browser er at indtaste de følgende kommandoer: <informalexample><screen>\n"
"$ cd /usr/share/doc/\n"
"$ w3m .\n"
"</screen></informalexample> Punktummet efter kommandoen <command>w3m</command> viser indholdet af den aktuelle mappe."

#. Tag: para
#: boot-new.xml:351
#, no-c-format
msgid "If you have a graphical desktop environment installed, you can also use its web browser. Start the web browser from the application menu and enter <userinput>/usr/share/doc/</userinput> in the address bar."
msgstr ""
"Hvis du har et grafisk skrivebordsmiljø installeret, så kan du også bruge dets internetbrowser. Start internetbrowseren fra programmenuen og indtast <userinput>/usr/share/doc/</userinput> i adresse adressefeltet."

#. Tag: para
#: boot-new.xml:357
#, no-c-format
msgid "You can also type <userinput>info <replaceable>command</replaceable></userinput> or <userinput>man <replaceable>command</replaceable></userinput> to see documentation on most commands available at the command prompt. Typing <userinput>help</userinput> will display help on shell commands. And typing a command followed by <userinput>--help</userinput> will usually display a short summary of the command's usage. If a command's results scroll past the top of the screen, type <userinput>|&nbsp;more</userinput> after the command to cause the results to pause before scrolling past the top of the screen. To see a list of all commands available which begin with a certain letter, type the letter and then two tabs."
msgstr ""
"Du kan også indtaste <userinput>info <replaceable>command</replaceable></userinput> eller <userinput>man <replaceable>command</replaceable></userinput> for at se dokumentationen for de fleste kommandoer tilgængelige på kommandoprompten. Tast <userinput>help</userinput> for at se hjælpeteksten for skalkommandoer. Og indtastning af en kommando efterfulgt af <userinput>--help</userinput> vil normalt vise et kort referat af kommandoens brug. Hvis resultatet for en kommando ruller forbi skærmen, så tast <userinput>|&nbsp;more</userinput> efter kommanden for at få resultatet til at stoppe før der rulles forbi skærmen. For at se en liste over alle tilgængelige kommandoer, som begynder med et bestemt bogstav, så tast bogstavet efterfulgt af to indryk (tabs)."