d-i-manual_install-methods - en to da translation catalogue (80 entries)

note: Tag: title
en: Obtaining System Installation Media
da: Find systeminstallationsmedie

note: Tag: title
en: Official &debian-gnu; installation images
da: Officielle &debian-gnu; installationsaftryk

note: Tag: para
en: Also, keep in mind: if the installation media you are using don't contain some packages you need, you can always install those packages afterwards from your running new Debian system (after the installation has finished). If you need to know on which installation image to find a specific package, visit <ulink url="https://cdimage-search.debian.org/">https://cdimage-search.debian.org/</ulink>.
da: Husk også: Hvis installationsmediet, du bruger, ikke indeholder de pakker, du skal bruge, så kan du altid installere disse pakker efterfølgende fra dit nye kørende Debiansystem (efter installationen er færdig). hvis du har brug for at finde en specifik pakke, så besøg <ulink url="https://cdimage-search.debian.org/">https://cdimage-search.debian.org/</ulink>.

note: Tag: para
en: Once the installer is booted, it will be able to obtain all the other files it needs from the disc.
da: Når installationsprogrammet er startet op, så vil det hente alle de andre nødvendige filer fra disken.

note: Tag: para
en: If you don't have an installation media set, then you will need to download the installer system files and place them on the <phrase arch="s390">VM minidisk</phrase> <phrase condition="bootable-disk">hard disk or</phrase> <phrase condition="bootable-usb">usb stick or</phrase> <phrase condition="supports-tftp">a connected computer</phrase> so they can be used to boot the installer.
da: Hvis du ikke har et installationsmediesæt, så skal du hente installationsprogrammets systemfiler og placere dem på <phrase arch="s390">VM-minidisk</phrase> <phrase condition="bootable-disk">harddisk eller</phrase> <phrase condition="bootable-usb">usb-drev eller</phrase> <phrase condition="supports-tftp">en forbundet computer</phrase> så de kan brugs til at starte installationsprogrammet op.

note: Tag: title
en: Downloading Files from &debian; Mirrors
da: Hentning af filer fra &debian;-spejl

note: Tag: para
en: To find the nearest (and thus probably the fastest) mirror, see the <ulink url="&url-debian-mirrors;">list of &debian; mirrors</ulink>.
da: For at finde det nærmeste (og dermed sandsynligvis det hurtigste) spejl, så se <ulink url="&url-debian-mirrors;">liste over &debian;-spejle</ulink>.

note: Tag: title
en: Where to Find Installation Files
da: Her kan du finde installationsfiler

note: Tag: para
en: Various installation files can be found on each &debian; mirror in the directory <ulink url="&url-debian-installer;images">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> &mdash; the <ulink url="&url-debian-installer;images/MANIFEST">MANIFEST</ulink> lists each image and its purpose.
da: Diverse installationsfiler kan findes på hvert &debian;-spejl i mappen <ulink url="&url-debian-installer;images">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> &mdash; <ulink url="&url-debian-installer;images/MANIFEST">MANIFESTET</ulink> viser hvert aftryk og dets formål.

note: Tag: title
en: Kurobox Pro Installation Files
da: Kurobox Pro-installationsfiler

note: Tag: para
en: The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the disk on which you intend to install &debian;. These images can be obtained from &kuroboxpro-firmware-img;.
da: Kurobox Pro kræver en kerne og ramdisk på en ext2-partition på disken du forventer at installere &debian;. Disse aftryk kan indhentes fra &kuroboxpro-firmware-img;.

note: Tag: title
en: HP mv2120 Installation Files
da: HP mv2120-installationsfiler

note: Tag: para
en: A firmware image is provided for the HP mv2120 which will automatically boot <classname>debian-installer</classname>. This image can be installed with uphpmvault on Linux and other systems and with the HP Media Vault Firmware Recovery Utility on Windows. The firmware image can be obtained from &mv2120-firmware-img;.
da: Et firmware-aftryk tilbydes for HP mv2120 som automatisk vil starte <classname>Debians installationsprogram</classname> op. Dette aftryk kan installeres med uphpmvault på Linux og andre systemer og med HP Media Vault Firmware Recovery Utility på Windows. Firmware-aftrykket kan hentes fra &mv2120-firmware-img;.

note: Tag: title
en: QNAP Turbo Station Installation Files
da: QNAP Turbo Station-installationsfiler

note: Tag: para
en: The installation files for the QNAP Turbo Station consist of a kernel and ramdisk as well as a script to write these images to flash. You can obtain the installation files for QNAP TS-11x/TS-12x, HS-210, TS-21x/TS-22x and TS-41x/TS-42x models from &qnap-kirkwood-firmware-img;.
da: Installationsfilerne for QNAP Turbo Station består af en kerne og en ramdisk samt et skript til at skrive disse aftryk til flash. Du kan hente installationsfilerne for QNAP TS-11x/TS-12x, HS-210, TS-21x/TS-22x og TS-41x/TS-42x fra &qnap-kirkwood-firmware-img;.

note: Tag: title
en: Plug Computer and OpenRD Installation Files
da: Plug Computer og OpenRD-installationsfiler

note: Tag: para
en: The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can obtain these files from &kirkwood-marvell-firmware-img;.
da: Installationsfilerne for plug-computere (SheevaPlug, GuruPlug, DreamPlug etc.) og OpenRD-enheder består af en kerne og initrd for U-Boot. Du kan hente disse filer fra &kirkwood-marvell-firmware-img;.

note: Tag: title
en: LaCie NASes Installation Files
da: LaCie NASes-installationsfiler

note: Tag: para
en: The installation files for LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) consist of a kernel and initrd for U-Boot. You can obtain these files from &lacie-kirkwood-firmware-img;.
da: Installationsfilerne for LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 og 5Big Network v2) består af en kerne og initrd for U-Boot. Du kan hente disse filer fra &lacie-kirkwood-firmware-img;.

note: Tag: title
en: Armhf Multiplatform Installation Files
da: Armhf Multiplatform-installationsfiler

note: Tag: para
en: The installation files for systems supported by the armhf multiplatform kernel (see <xref linkend="armhf-armmp-supported-platforms"/>) consist of a standard Linux kernel image, a standard Linux initial ramdisk image and a system-specific device-tree blob. The kernel and the initial ramdisk image for tftp-booting can be obtained from &armmp-firmware-img; and the device-tree blob can be obtained from &armmp-dtb-img;. The tar archive for creating a bootable USB stick with the installer can be obtained from &armmp-hd-media-tarball;.
da: Installationsfilerne for systemer understøttet af armhf multiplatform-kernen (se <xref linkend="armhf-armmp-supported-platforms"/>) består af et standardaftryk for Linuxkernen, et standardaftryk for Linux initial ramdisk og en systemspecifik enhedstræ-blob. Kernen og initial ramdisk-aftrykket kan hentes fra &armmp-firmware-img; og enhedstræ-blob'en kan hentes fra &armmp-dtb-img;. Tar-arkivet til oprettelse af et USB-drev, der kan startes op fra, med installationsprogrammet kan hentes fra &armmp-hd-media-tarball;.

note: Tag: para
en: U-boot images for various armhf platforms are available at &armmp-uboot-img;.
da: U-boot-aftryk for diverse armhf-platforme er tilgængelige på &armmp-uboot-img;.

note: Tag: title
en: Preparing Files for USB Memory Stick Booting
da: Forberedning af filer for opstart via USB-hukommelsesdrev

note: Tag: para
en: To prepare the USB stick, we recommend to use a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>lsblk</command> before and after inserting it. (The output of <command>dmesg</command> (as root) is another possible method for that.) To write to your stick, you may have to turn off its write protection switch.
da: For at forberede USB-drevet, så skal du bruge et system hvor GNU/Linux allerede er installeret og hvor USB er understøttet. Med nuværende GNU/Linux-systemer vil USB-drevet automatisk blive genkendt, når det indsættes. Hvis ikke bør du kontrollere om usb-storage-kernemodulet er indlæst. Når USB-drevet indsættes, så vil det blive lagt på en enhed navngivet <filename>/dev/sdX</filename>, hvor <quote>X</quote> er et bogstav i intervallet a-z. Du bør kunne se hvilken enhed USB-drevet blev lagt på ved at køre kommandoen <command>lsblk</command> før og efter indsættelse. (Resultatet af <command>dmesg</command> (som root) er en anden mulig metode til dette). For at skrive til dit drev skal du måske stille på skrivebeskyttelsesknappen.

note: Tag: para
en: The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on, for example, a hard disk is lost.
da: Procedurerne beskrevet i dette afsnit vil fjerne alt på enheden! Vær sikker på, at du bruger det korrekte enhedsnavn for dit USB-drev. Hvis du bruger den forkerte enhed kan resultatet være at hele informationen på for eksempel en harddisk mistes.

note: Tag: title
en: Preparing a USB stick using a hybrid CD/DVD image
da: Forberedning af et USB-drev via et hybrid cd/dvd-aftryk

note: Tag: para
en: Information about how to do this on other operating systems can be found in the <ulink url="&url-debian-cd-faq-write-usb;">Debian CD FAQ</ulink>.
da: Information om hvordan dette gøres på andre operativsystemer kan findes i <ulink url="&url-debian-cd-faq-write-usb;">Debians OSS for cd</ulink>.

note: Tag: para
en: The image must be written to the whole-disk device and not a partition, e.g. /dev/sdb and not /dev/sdb1. Do not use tools like <command>unetbootin</command> which alter the image.
da: Aftrykket skal skrives til whole-disk-enheden og ikke en partition, f.eks. /dev/sdb og ikke /dev/sdb1. Brug ikke værktøjer såsom <command>unetbootin</command> som ændrer aftrykket.

note: Tag: title
en: Preparing Files for Hard Disk Booting
da: Forberedelse af filer for harddiskopstart

note: Tag: para
en: The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS. On modern UEFI systems, the kernel may be booted directly from the UEFI partition without the need of a boot loader.
da: Installationsprogrammet kan startes ved at bruges opstartsfiler placeret på en eksisterende harddiskpartition, enten startet fra et andet operativsystem eller ved at igangsætte en opstartsindlæser direkte fra BIOS'en. På moderne UEFI-systemer kan kernen måske startes direkte fra UEFI-partitionen uden behov for en opstartsindlæser.

note: Tag: para
en: A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD/DVD images.
da: En fuld, <quote>ren netværksinstallation</quote> kan opnås via denne teknik. Dette undgår alle problemerne forbundet med eksterne medier, såsom af finde og brænde cd/dvd-aftryk.

note: Tag: title
en: Hard disk installer booting from Linux using <command>GRUB</command>
da: Harddiskinstallationsprogrammet med opstart fra Linux via <command>GRUB</command>

note: Tag: para
en: This section explains how to add to or even replace an existing linux installation using <command>GRUB</command>.
da: Dette afsnit forklarer hvordan du tilføjer eller erstatter en eksisterende Linux-installation via <command>GRUB</command>.

note: Tag: para
en: At boot time, <command>GRUB</command> supports loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel.
da: Ved opstart, understøtter <command>GRUB</command> indlæsning i hukommelse ikke kun af kernen, men også af et diskaftryk. Denne RAM-disk kan bruges som rodfilsystem af kernen.

note: Tag: para
en: Copy the following files from the &debian; archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>.
da: Kopier de følgende filer fra &debian;-arkiverne til en passende placering på din harddisk, for eksempel <filename>/boot/newinstall/</filename>.

note: Tag: para
en: <filename>vmlinuz</filename> (kernel binary)
da: <filename>vmlinuz</filename> (kernens binære fil)

note: Tag: para
en: <filename>initrd.gz</filename> (ramdisk image)
da: <filename>initrd.gz</filename> (ramdisk-aftryk)

note: Tag: para
en: If you intend to use the hard drive only for booting and then download everything over the network, you should download the &x86-netboot-initrd; file and its corresponding kernel &x86-netboot-linux;. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care.
da: Hvis du har tænkt dig kun at bruge harddisken for opstart og så hente alt over netværket, så skal du hente filen &x86-netboot-initrd; og dens modsvarende kerne, &x86-netboot-linux;. Dette vil give dig mulighed for at partitionere harddisken, du starter installationsprogrammet op fra, om selvom du bør gøre dette med forsigtighed.

note: Tag: para
en: Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the &x86-hdmedia-initrd; file and its kernel &x86-hdmedia-vmlinuz;, as well as copy an installation image to the hard drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the hard drive and install from the installation image, without needing the network.
da: Alternativt, hvis du forventer at bevare en eksisterende partition på harddisken uændret under installationen, så kan du hente filen &x86-hdmedia-initrd; og dens kerne, samt kopiere et installationsaftryk til drevet (sikr dig at filens navn ender med <literal>.iso</literal>). Installationsprogrammet kan så starte op fra drevet og installere fra installationsaftrykket, uden at kræve netværket.

note: Tag: para
en: Finally, to configure the bootloader proceed to <xref linkend="boot-initrd"/>.
da: Endelig, for at konfigure opstartsindllæseren fortsættes til <xref linkend="boot-initrd"/>.

note: Tag: title
en: Preparing Files for TFTP Net Booting
da: Forberedelse af filer for TFTP-netopstart

note: Tag: para
en: If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine.
da: Hvis din maskine er forbundet på et lokalt områdenetværk, så kan du måske starte den op over netværket fra en anden maskine, via TFTP. Hvis du har tænkt dig at starte installationssystemet op fra en anden maskine, så vil opstartsfilerne skulle placeres på specifikke placeringer på den maskine, og maskinen skal konfigureres til at understøtte opstart fra din specfikke maskine.

note: Tag: para
en: You need to set up a TFTP server, and for many machines a DHCP server<phrase condition="supports-rarp">, or RARP server</phrase><phrase condition="supports-bootp">, or BOOTP server</phrase>.
da: Du skal opsætte en TFTP-server, og for mange maskiner en DHCP-server<phrase condition="supports-rarp">, eller RARP-server</phrase><phrase condition="supports-bootp">, eller BOOTP-server</phrase>.

note: Tag: para
en: <phrase condition="supports-rarp">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition="supports-bootp">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP.
da: <phrase condition="supports-rarp">The Reverse Address Resolution Protocol (RARP) er en måde at fortælle din klient, hvilken IP-adresse der skal bruges internt. En anden måde er at bruge BOOTP-protokollen.</phrase> <phrase condition="supports-bootp">BOOTP er en IP-protokol, som informerer en computer om dens IP-adresse og hvor på netværket du kan finde et opstartsaftryk.</phrase> DHcP'en (Dynamic Host Configuration Protocol) er en mere fleksibel, bagud kompatibel udvidelse af BOOTP. Nogle systemer kan kun konfigureres via DHCP.

note: Tag: para
en: The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux.
da: Trivial File Transfer Protocol (TFTP) bruges til at levere opstartsaftrykket til klienten. Teoretisk kan enhver server på enhver platform, som implementerer disse protokoller, anvendes. I eksemplerne i dette afsnit angiver vi kommandoer for SunOS 4.x, SunOS 5.x (a.k.a. Solaris) og GNU/Linux.

note: Tag: para
en: For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. It's written by the same author as the <classname>syslinux</classname> bootloader and is therefore least likely to cause issues. A good alternative is <classname>atftpd</classname>.
da: For en &debian-gnu;-server anbefaler vi <classname>tftpd-hpa</classname>. Den er skrevet af den samme forfatter som opstartsindlæseren <classname>syslinux</classname> og er derfor den mindst sandsynlige årsag til problemstillinger. Et godt alternativ er <classname>atftpd</classname>.

note: Tag: title
en: Setting up RARP server
da: Opsætning af en RARP-server

note: Tag: para
en: To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can boot into <quote>Rescue</quote> mode and use the command <userinput>ip addr show dev eth0</userinput>.
da: For at opsætte RARP, så skal ud kende Ethernet-adressen (a.k.a. MAC-adressen) på klientcomputerne der skal installeres på. Hvis du ikke kender denne information, så kan du starte op i <quote>Redningstilstand</quote> og bruge kommandoen <userinput>ip addr show dev eth0</userinput>.

note: Tag: para
en: On a RARP server system using a Linux kernel or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1).
da: På et RARP-serversystem der bruger Linux-kernen eller Solaris/SunOS, skal du bruge programmet <command>rarpd</command>. Du skal sikre dig, at Ethernettets udstyrsadresse for klienten vises i databasen <quote>ethers</quote> (enten i filen <filename>/etc/ethers</filename>, eller via NIS/NIS+) og i databasen <quote>hosts</quote>. Så skal du starte RARP-dæmonen. Udsted kommandoen (som root): <userinput>/usr/sbin/rarpd -a</userinput> på de fleste Linux-systemer og SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> på nogle andre Linux-systemer, eller <userinput>/usr/etc/rarpd -a</userinput> i SunOS 4 (Solaris 1).

note: Tag: title
en: Setting up a DHCP server
da: Opsætning af en DHCP-server

note: Tag: para
en: One free software DHCP server is ISC <command>dhcpd</command>. For &debian-gnu;, the <classname>isc-dhcp-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp/dhcpd.conf</filename>):
da: En fri DHCP-server er ISC <command>dhcpd</command>. For &debian-gnu; anbefales pakken <classname>isc-dhcp-server</classname>. Her er et eksempel på en konfigurationsfil for den (se <filename>/etc/dhcp/dhcpd.conf</filename>):

note: Tag: para
en: In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP.
da: I dette eksempel er der en server <replaceable>servername</replaceable> som udfører al arbejdet på DHCP-serveren, TFTP-serveren og netværksadgangspunktet. Du har med stor sandsynlighed behov for at ændre indstillinger for domænenavnet samt servernavnet og klientens udstyrsadresse. Indstillingen <replaceable>filename</replaceable> skal være navnet på filen, som hentes via TFTP.

note: Tag: para
en: After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/isc-dhcp-server restart</userinput>.
da: Efter du har redigeret konfigurationsfilen <command>dhcpd</command>, så genstart den med <userinput>/etc/init.d/isc-dhcp-server restart</userinput>.

note: Tag: title
en: Enabling PXE Booting in the DHCP configuration
da: Aktivering af PXE-opstart i DHCP-konfigurationen

note: Tag: para
en: Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>
    option domain-name "example.com";
    
    default-lease-time 600;
    max-lease-time 7200;
    
    allow booting;
    allow bootp;
    
    # The next paragraph needs to be modified to fit your case
    subnet 192.168.1.0 netmask 255.255.255.0 {
      range 192.168.1.200 192.168.1.253;
      option broadcast-address 192.168.1.255;
    # the gateway address which can be different
    # (access to the internet for instance)
      option routers 192.168.1.1;
    # indicate the dns you want to use
      option domain-name-servers 192.168.1.3;
    }
    
    group {
      next-server 192.168.1.3;
      host tftpclient {
    # tftp client hardware address
      hardware ethernet  00:10:DC:27:6C:15;
      filename "pxelinux.0";
     }
    }
    </screen></informalexample> Note that for PXE booting, the client filename <filename>pxelinux.0</filename> is a boot loader, not a kernel image (see <xref linkend="tftp-images"/> below).
da: Her er et andet eksempel for <filename>dhcp.conf</filename>, der rbuger Pre-boot Execution Environment (PXE)-metoden for TFTP. <informalexample><screen>
    option domain-name "example.com";
    
    default-lease-time 600;
    max-lease-time 7200;
    
    allow booting;
    allow bootp;
    
    # The next paragraph needs to be modified to fit your case
    subnet 192.168.1.0 netmask 255.255.255.0 {
      range 192.168.1.200 192.168.1.253;
      option broadcast-address 192.168.1.255;
    # the gateway address which can be different
    # (access to the internet for instance)
      option routers 192.168.1.1;
    # indicate the dns you want to use
      option domain-name-servers 192.168.1.3;
    }
    
    group {
      next-server 192.168.1.3;
      host tftpclient {
    # tftp client hardware address
      hardware ethernet  00:10:DC:27:6C:15;
      filename "pxelinux.0";
     }
    }
    </screen></informalexample> Bemærk at for PXE-opstart, er klientfilnavnet <filename>pxelinux.0</filename> en opstartsindlæser, ikke et kerneaftryk (se <xref linkend="tftp-images"/> below).

note: Tag: para
en: If your machine uses UEFI to boot, you will have to specify a boot loader appropriate for UEFI machines, for example
da: Hvis din maskine bruger UEFI til opstart, så skal du angive en opstartsindlæser passende for UEFI-maskiner, for eksempel

note: Tag: title
en: Setting up a BOOTP server
da: Opsætning af en BOOTP-server

note: Tag: para
en: There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian-gnu; these are contained in the <classname>bootp</classname> and <classname>isc-dhcp-server</classname> packages respectively.
da: Der er to BOOTP-servere tilgængelige for GNU/Linux. Den første er CMU <command>bootpd</command>. Den anden er faktisk en DHCP-server: ISC <command>dhcpd</command>. I &debian-gnu; er disse indeholdt i pakkerne <classname>bootp</classname> og <classname>isc-dhcp-server</classname> respektivt.

note: Tag: para
en: To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run &debian;, the line in question should look like: <informalexample><screen>
    bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120
    </screen></informalexample> Now, you must create an <filename>/etc/bootptab</filename> file. This has the same sort of familiar and cryptic format as the good old BSD <filename>printcap</filename>, <filename>termcap</filename>, and <filename>disktab</filename> files. See the <filename>bootptab</filename> manual page for more information. For CMU <command>bootpd</command>, you will need to know the hardware (MAC) address of the client. Here is an example <filename>/etc/bootptab</filename>: <informalexample><screen>
    client:\
      hd=/tftpboot:\
      bf=tftpboot.img:\
      ip=192.168.1.90:\
      sm=255.255.255.0:\
      sa=192.168.1.1:\
      ha=0123456789AB:
    </screen></informalexample> You will need to change at least the <quote>ha</quote> option, which specifies the hardware address of the client. The <quote>bf</quote> option specifies the file a client should retrieve via TFTP; see <xref linkend="tftp-images"/> for more details.
da: For at bruge CMU <command>bootpd</command>, skal du først aktivere (eller tilføje) de relevante linjer i <filename>/etc/inetd.conf</filename>. På &debian-gnu; kan du køre <userinput>update-inetd --enable bootps</userinput>, og så <userinput>/etc/init.d/inetd reload</userinput> for at gøre det. Bare i tilfælde af, at din BOOTP-server ikke kører &debian;, skal den omtalte linje se således ud:<informalexample><screen>
    bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120
    </screen></informalexample> Nu skal du oprette en <filename>/etc/bootptab</filename>-fil. Den har samme slags kendte og kryptiske format som det gode gamle BSD <filename>printcap</filename>-, <filename>termcap</filename>-, og <filename>disktab</filename>-filer. Se manualsiden <filename>bootptab</filename> for yderligere information. For CMU <command>bootpd</command>, skal du bruge udstyrsadressen (MAC) for klienten. Her er en eksempel <filename>/etc/bootptab</filename>: <informalexample><screen>
    client:\
      hd=/tftpboot:\
      bf=tftpboot.img:\
      ip=192.168.1.90:\
      sm=255.255.255.0:\
      sa=192.168.1.1:\
      ha=0123456789AB:
    </screen></informalexample> Du skal mindst ændre <quote>ha</quote>-tilvalget, som angiver udstyrsadressen for klienten. Tilvalget <quote>bf</quote> specificerer filen en klient skal hente via TFTP; se <xref linkend="tftp-images"/> for yderligere detaljer.

note: Tag: para
en: By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend="dhcpd"/>. Otherwise you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client in <filename>/etc/dhcp/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/isc-dhcp-server restart</userinput>.
da: Som kontrast er opsætning af BOOTP med ISC <command>dhcpd</command> virkelig nemt, da det opfatter BOOTP-klienter som et moderat specieltilfælde for DHCP-klienter. Nogle arkitekturer kræver en kompleks konfiguration for opstart af klienter via BOOTP. Hvis din er en af disse, så læs afsnittet <xref linkend="dhcpd"/>. Ellers vil du sandsynligvis kunne slippe af sted med at tilføje <userinput>allow bootp</userinput> direkte til konfigurationsblokken for undernettet, der indeholder klienten i <filename>/etc/dhcp/dhcpd.conf</filename>, og genstarte <command>dhcpd</command> med <userinput>/etc/init.d/isc-dhcp-server restart</userinput>.

note: Tag: title
en: Enabling the TFTP Server
da: Aktivering af TFTP-serveren

note: Tag: para
en: To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled.
da: For at få TFTP-serveren klar, skal du først sikre dig, at <command>tftpd</command> er aktiveret.

note: Tag: para
en: In the case of <classname>tftpd-hpa</classname> there are two ways the service can be run. It can be started on demand by the system's <classname>inetd</classname> daemon, or it can be set up to run as an independent daemon. Which of these methods is used is selected when the package is installed and can be changed by reconfiguring the package.
da: I tilfældet <classname>tftpd-hpa</classname> er der to måder at tjenesten kan køres. Den kan startes efter behov af systemets dæmon <classname>inetd</classname>, eller den kan opsættes til at blive kørt som en uafhængig dæmon. Hvilken af disse metoder der bruges vælges når pakke installeres og kan ændres ved at rekonfigurere pakken.

note: Tag: para
en: Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian-gnu; packages may use other directories to comply with the <ulink url="&url-fhs-home;">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/srv/tftp</filename>. You may have to adjust the configuration examples in this section accordingly.
da: Historisk brugte TFTP-servere <filename>/tftpboot</filename> som mappe til at betjene aftryk fra. Pakkerne &debian-gnu; kan bruge andre mapper til at overholde <ulink url="&url-fhs-home;">Filesystem Hierarchy Standard</ulink>. For eksempel bruger <classname>tftpd-hpa</classname> som standard <filename>/srv/tftp</filename>. Du skal måske justere konfigurationseksemplerne i dette afsnit jævnfør dette.

note: Tag: para
en: All <command>in.tftpd</command> alternatives available in &debian; should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors.
da: Alle <command>in.tftpd</command> alternativer tilgængelige i &debian; bør logge TFTP-forespørgsler til systemets logge som standard. Nogle af dem understøtter et <userinput>-v</userinput> argument for at øge uddybningen. Det anbefales at kontrollere disse logbeskeder i tilfælde at opstartsproblemer, da de er et godt udgangspunkt for diagnosticering af fejltilfælde.

note: Tag: title
en: Move TFTP Images Into Place
da: Flyt TFTP-aftryk på plads

note: Tag: para
en: Next, place the TFTP boot image you need, as found in <xref linkend="where-files"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards.
da: Placer så TFTP-opstartsaftrykket du skal bruge som set i <xref linkend="where-files"/>, i opstartsaftryksmappen <command>tftpd</command>. Du skal måske lave en henvisning fra den fil til filen som <command>tftpd</command> vil bruge til opstart af en bestemt klient. Desværre bestemmes filnavnet af TFTP-klienten, og der er ingen udbredte standarder.

note: Tag: para
en: For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot. For UEFI machines, you will need to pass an appropriate EFI boot image name (such as <filename>/debian-installer/amd64/bootnetx64.efi</filename>).
da: For PXE-opstart befinder alt du bør sætte op sig i tarball'en <filename>netboot/netboot.tar.gz</filename>. Udpak denne tarbal i mappen for opstartsaftrykket <command>tftpd</command>. Sikr dig at din dhcp-server er konfigureret til at sende <filename>pxelinux.0</filename> til <command>tftpd</command> som filnavnet at starte op. For UEFI-maskiner skal du sende et passende EFI-opstartsaftryksnavn (såsom <filename>/debian-installer/amd64/bootnetx64.efi</filename>).

note: Tag: title
en: Automatic Installation
da: Automatisk installation

note: Tag: title
en: Automatic Installation Using the &debian; Installer
da: Automatisk installation med &debian;-installationsprogrammet

note: Tag: para
en: The &debian; Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process.
da: &debian;-installationsprogrammet understøtter automatiske installationer via prækonfigurationsfiler. En prækonfigurationsfil kan indlæses fra netværket eller fra et eksternt medie, og bruges til at udfylde svar på spørgsmål stillet under installationsprocessen.

note: Tag: para
en: Full documentation on preseeding including a working example that you can edit is in <xref linkend="appendix-preseed"/>.
da: Fuld dokumentation vedrørende preseeding inklusiv et arbejdseksempel, som du kan redigere er i <xref linkend="appendix-preseed"/>.

note: Tag: title
en: Verifying the integrity of installation files
da: Verifikation af integreiteten for installationsfiler

note: Tag: para
en: You can verify the integrity of downloaded files against checksums provided in <filename>SHA256SUMS</filename> or <filename>SHA512SUMS</filename> files on Debian mirrors. You can find them in the same places as the installation images itself. Visit the following locations:
da: Du kan verificere integriteten for hentede filer mod kontrolsummer vist i filerne <filename>SHA256SUMS</filename> eller <filename>SHA512SUMS</filename> på Debianspejle. Du kan finde dem på samme sted som selve installationsaftrykkene. Besøg de følgende steder:

note: Tag: para
en: <ulink url="https://cdimage.debian.org/debian-cd/current/&architecture;/iso-cd/">checksum files for CD images</ulink>,
da: <ulink url="https://cdimage.debian.org/debian-cd/current/&architecture;/iso-cd/">kontrolsumfiler for cd-aftryk</ulink>,

note: Tag: para
en: <ulink url="https://cdimage.debian.org/debian-cd/current/&architecture;/iso-dvd/">checksum files for DVD images</ulink>,
da: <ulink url="https://cdimage.debian.org/debian-cd/current/&architecture;/iso-dvd/">kontrolsumfiler for dvd-aftryk</ulink>,

note: Tag: para
en: <ulink url="https://cdimage.debian.org/debian-cd/current/&architecture;/iso-bd/">checksum files for BD images</ulink>,
da: <ulink url="https://cdimage.debian.org/debian-cd/current/&architecture;/iso-bd/">kontrolsumfiler for BD-aftryk</ulink>,

note: Tag: para
en: <ulink url="http://&archive-mirror;/debian/dists/&releasename;/main/installer-&architecture;/current/images/">checksum files for other installation files</ulink>.
da: <ulink url="http://&archive-mirror;/debian/dists/&releasename;/main/installer-&architecture;/current/images/">kontrolsumfiler for andre installationsfiler</ulink>.

note: Tag: para
en: To compute the checksum of a downloaded installation file, use <informalexample><screen>
    sha256sum filename.iso
    </screen></informalexample> respective <informalexample><screen>
    sha512sum filename.iso
    </screen></informalexample> and then compare the shown checksum against the corresponding one in the <filename>SHA256SUMS</filename> respective <filename>SHA512SUMS</filename> file.
da: For at beregne kontrolsummen for et hentet installationsmedie, brug <informalexample><screen>
    sha256sum filename.iso
    </screen></informalexample> respektiv <informalexample><screen>
    sha512sum filename.iso
    </screen></informalexample> og sammenlign så den viste kontrolsum mod den tilsvarende i <filename>SHA256SUMS</filename>-filen respektiv <filename>SHA512SUMS</filename>-filen.

note: Tag: para
en: The <ulink url="&url-debian-cd-faq;">Debian CD FAQ</ulink> has <ulink url="https://www.debian.org/CD/faq/index.en.html#verify">more useful information</ulink> on this topic (such as the script <filename>check_debian_iso</filename>, to semi-automate above procedure), as well as instructions, how to verify the integrity of the above checksum files themselves.
da: <ulink url="&url-debian-cd-faq;">Debians OSS for cd</ulink> har <ulink url="https://www.debian.org/CD/faq/index.en.html#verify">mere nyttig information</ulink> om dette emne (såsom skriptet <filename>check_debian_iso</filename>, til en semiautomatiseirng af ovenstående procedure), samt instruktioner om hvordan integriteten for de ovenstående kontrolsummer verificeres.
