# Danish translation of administrivia. # Copyright (C) 2022 Free Software Foundation, Inc. # Joe Hansen , 2014, 2015, 2016, 2018, 2022. # # nb skal preseeding oversættes? # msgid "" msgstr "" "Project-Id-Version: d-i-manual_install-methods\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2023-12-17 23:04+0000\n" "PO-Revision-Date: 2022-07-08 19:32+0000\n" "Last-Translator: Joe Hansen \n" "Language-Team: Danish \n" "Language: da\n" "MIME-Version: 1.0\n" "Content-Type: application/x-xml2pot; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Generator: Weblate 4.7-dev\n" #. Tag: title #: install-methods.xml:5 #, no-c-format msgid "Obtaining System Installation Media" msgstr "Find systeminstallationsmedie" #. Tag: title #: install-methods.xml:12 #, no-c-format msgid "Official &debian-gnu; installation images" msgstr "Officielle &debian-gnu; installationsaftryk" #. Tag: para #: install-methods.xml:13 #, fuzzy, no-c-format #| msgid "" #| "By far the easiest way to install &debian-gnu; is from a set of official " #| "&debian; installation images. You can buy a set of CDs/DVDs from a vendor " #| "(see the CD vendors page). " #| "You may also download the installation images from a &debian; mirror and " #| "make your own set, if you have a fast network connection and a CD/DVD " #| "burner (see the Debian CD/DVD page " #| "and Debian CD FAQ for detailed " #| "instructions). If you have such optical installation media, and they are " #| "bootable on your machine, which is the case on all " #| "modern PCs, you can skip right to . Much effort has been expended to ensure the most-used files are on " #| "the first CD and DVD image, so that a basic desktop installation can be " #| "done with only the first DVD or - to a limited extent - even with only " #| "the first CD image." msgid "" "By far the easiest way to install &debian-gnu; is from a set of official " "&debian; installation images. You can buy a set of CDs/DVDs from a vendor " "(see the CD vendors page). " "You may also download the installation images from a &debian; mirror and " "make your own set, if you have a fast network connection and a CD/DVD burner " "(see the Debian CD/DVD page and " "Debian CD FAQ for detailed " "instructions). If you have such optical installation media, and they are " "bootable on your machine, which is the case on all " "modern PCs, you can skip right to . Much effort has been expended to ensure the most-used files are on the " "first DVD image, so that a basic desktop installation can be done with only " "the first DVD." msgstr "" "Den bedste måde at installere &debian-gnu; er fra det officielle &debian;-" "installationsaftryk. Du kan købe et sæt af cd'er/dvd'er fra en leverandør " "(se cd-leverandørsiden). Du " "kan også hente installationsaftrykket fra et &debian;-spejl og lave dit eget " "sæt, hvis du har en hurtig netværksforbindelse og en cd/dvd-brænder (se " "Debians cd/dvd-side og Debians OSS for cd for detaljerede " "instruktioner). Hvis du har et optisk installationsmedie og det startes op " "på din maskine , hvilket er tilfældet for alle moderne " "pc'er, så kan du gå direkte til . " "Der er brugt en stor indsats for at sikre at de mest anvendte filer er på " "den første cd eller dvd, så en installation af basissystemet kan udføres kun " "med den første dvd eller - i begrænset omfang - selv med den første cd." #. Tag: para #: install-methods.xml:29 #, no-c-format msgid "" "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 https://cdimage-" "search.debian.org/." msgstr "" "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 https://cdimage-search.debian.org/." #. Tag: para #: install-methods.xml:37 #, fuzzy, no-c-format #| msgid "" #| "If your machine doesn't support booting from optical media (only relevant on very old PC systems), but you do have " #| "a set of CD/DVD, you can use an alternative strategy such as VM reader, hard " #| "disk, usb stick, " #| "net boot, or manually " #| "loading the kernel from the disc to initially boot the system installer. " #| "The files you need for booting by another means are also on the disc; the " #| "&debian; network archive and folder organization on the disc are " #| "identical. So when archive file paths are given below for particular " #| "files you need for booting, look for those files in the same directories " #| "and subdirectories on your installation media." msgid "" "If your machine doesn't support booting from optical media (only relevant on very old PC systems), but you do have a " "set of DVD, you can use an alternative strategy such as VM reader, hard disk, usb stick, net boot, or manually loading the " "kernel from the disc to initially boot the system installer. The files you " "need for booting by another means are also on the disc; the &debian; network " "archive and folder organization on the disc are identical. So when archive " "file paths are given below for particular files you need for booting, look " "for those files in the same directories and subdirectories on your " "installation media." msgstr "" "Hvis din maskine ikke understøtter opstart fra et optisk medie (kun relevant på meget gamle pc-systemer), men du har et " "cd/dvd-sæt, så kan du bruge en alternativ strategi såsom VM-læser, harddisk, usb-drev, net boot eller manuelt indlæse kernen " "fra disken for her i starten at få gang i systeminstallationsprogrammet. " "Filerne du skal bruge til at starte op med andre metoder er også på disken; " "&debian;-netværksarkivet og mappeorganisationen på disken er identisk. Så " "når arkivfilstier angives nedenfor for bestemte filer du skal bruge til at " "starte op, så skal du kigge efter disse filer i de samme mapper og " "undermapper på dit installationsmedie." #. Tag: para #: install-methods.xml:58 #, no-c-format msgid "" "Once the installer is booted, it will be able to obtain all the other files " "it needs from the disc." msgstr "" "Når installationsprogrammet er startet op, så vil det hente alle de andre " "nødvendige filer fra disken." #. Tag: para #: install-methods.xml:63 #, no-c-format msgid "" "If you don't have an installation media set, then you will need to download " "the installer system files and place them on the VM " "minidisk hard disk or " "usb stick or a connected computer so they can be used to boot " "the installer." msgstr "" "Hvis du ikke har et installationsmediesæt, så skal du hente " "installationsprogrammets systemfiler og placere dem på VM-minidisk harddisk " "eller usb-drev eller " "en forbundet computer så de kan " "brugs til at starte installationsprogrammet op." #. Tag: title #: install-methods.xml:87 #, no-c-format msgid "Downloading Files from &debian; Mirrors" msgstr "Hentning af filer fra &debian;-spejl" #. Tag: para #: install-methods.xml:89 #, no-c-format msgid "" "To find the nearest (and thus probably the fastest) mirror, see the list of &debian; mirrors." msgstr "" "For at finde det nærmeste (og dermed sandsynligvis det hurtigste) spejl, så " "se liste over &debian;-spejle." #. Tag: title #: install-methods.xml:97 #, no-c-format msgid "Where to Find Installation Files" msgstr "Her kan du finde installationsfiler" #. Tag: para #: install-methods.xml:99 #, no-c-format msgid "" "Various installation files can be found on each &debian; mirror in the " "directory debian/dists/" "&releasename;/main/installer-&architecture;/current/images/ — " "the MANIFEST " "lists each image and its purpose." msgstr "" "Diverse installationsfiler kan findes på hvert &debian;-spejl i mappen " "debian/dists/&releasename;/main/" "installer-&architecture;/current/images/MANIFESTET viser hvert aftryk og " "dets formål." #. Tag: title #: install-methods.xml:111 #, no-c-format msgid "Kurobox Pro Installation Files" msgstr "Kurobox Pro-installationsfiler" #. Tag: para #: install-methods.xml:112 #, no-c-format msgid "" "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;." msgstr "" "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;." #. Tag: title #: install-methods.xml:122 #, no-c-format msgid "HP mv2120 Installation Files" msgstr "HP mv2120-installationsfiler" #. Tag: para #: install-methods.xml:123 #, no-c-format msgid "" "A firmware image is provided for the HP mv2120 which will automatically boot " "debian-installer. 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;." msgstr "" "Et firmware-aftryk tilbydes for HP mv2120 som automatisk vil starte " "Debians installationsprogram 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;." #. Tag: title #: install-methods.xml:135 #, no-c-format msgid "QNAP Turbo Station Installation Files" msgstr "QNAP Turbo Station-installationsfiler" #. Tag: para #: install-methods.xml:136 #, no-c-format msgid "" "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;." msgstr "" "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;." #. Tag: title #: install-methods.xml:147 #, no-c-format msgid "Plug Computer and OpenRD Installation Files" msgstr "Plug Computer og OpenRD-installationsfiler" #. Tag: para #: install-methods.xml:148 #, no-c-format msgid "" "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;." msgstr "" "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;." #. Tag: title #: install-methods.xml:158 #, no-c-format msgid "LaCie NASes Installation Files" msgstr "LaCie NASes-installationsfiler" #. Tag: para #: install-methods.xml:159 #, no-c-format msgid "" "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;." msgstr "" "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;." #. Tag: title #: install-methods.xml:170 #, no-c-format msgid "Armhf Multiplatform Installation Files" msgstr "Armhf Multiplatform-installationsfiler" #. Tag: para #: install-methods.xml:171 #, no-c-format msgid "" "The installation files for systems supported by the armhf multiplatform " "kernel (see ) 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;." msgstr "" "Installationsfilerne for systemer understøttet af armhf multiplatform-kernen " "(se ) 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;." #. Tag: para #: install-methods.xml:183 #, no-c-format msgid "" "U-boot images for various armhf platforms are available at &armmp-uboot-img;." msgstr "" "U-boot-aftryk for diverse armhf-platforme er tilgængelige på &armmp-uboot-" "img;." #. Tag: title #: install-methods.xml:229 #, no-c-format msgid "Preparing Files for USB Memory Stick Booting" msgstr "Forberedning af filer for opstart via USB-hukommelsesdrev" #. Tag: para #: install-methods.xml:231 #, no-c-format msgid "" "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 /" "dev/sdX, where the X 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 lsblk before and after inserting it. " "(The output of dmesg (as root) is another possible method " "for that.) To write to your stick, you may have to turn off its write " "protection switch." msgstr "" "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 /dev/" "sdX, hvor X er et bogstav i intervallet a-z. Du " "bør kunne se hvilken enhed USB-drevet blev lagt på ved at køre kommandoen " "lsblk før og efter indsættelse. (Resultatet af " "dmesg (som root) er en anden mulig metode til dette). For " "at skrive til dit drev skal du måske stille på skrivebeskyttelsesknappen." #. Tag: para #: install-methods.xml:246 #, no-c-format msgid "" "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." msgstr "" "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." #. Tag: title #: install-methods.xml:256 #, no-c-format msgid "Preparing a USB stick using a hybrid CD/DVD image" msgstr "Forberedning af et USB-drev via et hybrid cd/dvd-aftryk" #. Tag: para #: install-methods.xml:257 #, fuzzy, no-c-format #| msgid "" #| "Debian installation images for this architecture are created using the " #| "isohybrid technology; that means they can be written " #| "directly to a USB stick, which is a very easy way to make an installation " #| "media. Simply choose an image (such as the netinst, CD or DVD-1) that " #| "will fit on your USB stick. See to get " #| "an installation image." msgid "" "Debian installation images for this architecture are created using the " "isohybrid technology; that means they can be written " "directly to a USB stick, which is a very easy way to make an installation " "media. Simply choose an image (such as the netinst or DVD-1) that will fit " "on your USB stick. See to get an " "installation image." msgstr "" "Debian installationsaftryk for denne arkitektur oprettes med " "isohybrid-teknologien; dette betyder at de kan skrives " "direkte på et USB-drev, hvilket er en meget nem måde at lave et " "installationsmedie. Vælg et aftryk (såsom netinst, CD eller DVD-1), som vil " "passe på dit USB-drev. Se for hvordan du " "får fat i et installationsaftryk." #. Tag: para #: install-methods.xml:267 #, fuzzy, no-c-format #| msgid "" #| "The installation image you choose should be written directly to the USB " #| "stick, overwriting its current contents. For example, when using an " #| "existing GNU/Linux system, the image file can be written to a USB stick " #| "as follows, after having made sure that the stick is unmounted: " #| "\n" #| "# cp debian.iso /" #| "dev/sdX\n" #| "# sync\n" #| " Information about how to do this on other " #| "operating systems can be found in the Debian CD FAQ." msgid "" "The installation image you choose should be written directly to the USB " "stick, overwriting its current contents. For example, when using an existing " "GNU/Linux system, the image file can be written to a USB stick as follows, " "after having made sure that the stick is unmounted: " "\n" "# cp debian.iso /dev/" "sdX\n" "# sync\n" " Simply writing the installation image to USB " "like this should work fine for most users. For special needs there is this " "wiki " "page." msgstr "" "Installationsaftrykket, du vælger, skal skrives direkte til USB-drevet, og " "overskrive dets nuværende indhold. For eksempel kan du med et eksisterende " "GNU/Linux-system skrive aftrykket til et USB-drev som i det følgende, efter " "at du har sikret dig, at drevet er afmonteret:\n" "# cp debian.iso /dev/" "sdX\n" "# sync\n" " En simpel skrivning af installationsaftrykket " "til USB bør fungere fint for de fleste brugere." #. Tag: para #: install-methods.xml:280 #, no-c-format msgid "" "Information about how to do this on other operating systems can be found in " "the Debian CD FAQ." msgstr "" "Information om hvordan dette gøres på andre operativsystemer kan findes i " "Debians OSS for cd." #. Tag: para #: install-methods.xml:285 #, no-c-format msgid "" "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 unetbootin which alter the image." msgstr "" "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 unetbootin som ændrer aftrykket." #. Tag: title #: install-methods.xml:302 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "Forberedelse af filer for harddiskopstart" #. Tag: para #: install-methods.xml:303 #, no-c-format msgid "" "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." msgstr "" "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." #. Tag: para #: install-methods.xml:311 #, no-c-format msgid "" "A full, pure network installation can be achieved using this " "technique. This avoids all hassles of removable media, like finding and " "burning CD/DVD images." msgstr "" "En fuld, ren netværksinstallation 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." #. Tag: title #: install-methods.xml:341 #, no-c-format msgid "Hard disk installer booting from Linux using GRUB" msgstr "" "Harddiskinstallationsprogrammet med opstart fra Linux via GRUB" #. Tag: para #: install-methods.xml:343 #, no-c-format msgid "" "This section explains how to add to or even replace an existing linux " "installation using GRUB." msgstr "" "Dette afsnit forklarer hvordan du tilføjer eller erstatter en eksisterende " "Linux-installation via GRUB." #. Tag: para #: install-methods.xml:349 #, no-c-format msgid "" "At boot time, GRUB 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." msgstr "" "Ved opstart, understøtter GRUB indlæsning i hukommelse " "ikke kun af kernen, men også af et diskaftryk. Denne RAM-disk kan bruges som " "rodfilsystem af kernen." #. Tag: para #: install-methods.xml:355 #, no-c-format msgid "" "Copy the following files from the &debian; archives to a convenient location " "on your hard drive, for instance to /boot/newinstall/." msgstr "" "Kopier de følgende filer fra &debian;-arkiverne til en passende placering på " "din harddisk, for eksempel /boot/newinstall/." #. Tag: para #: install-methods.xml:362 #, no-c-format msgid "vmlinuz (kernel binary)" msgstr "vmlinuz (kernens binære fil)" #. Tag: para #: install-methods.xml:367 #, no-c-format msgid "initrd.gz (ramdisk image)" msgstr "initrd.gz (ramdisk-aftryk)" #. Tag: para #: install-methods.xml:374 #, 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 &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." 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 &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." #. Tag: para #: install-methods.xml:383 #, 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 &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 .iso). The installer can then boot from the hard drive and install from " "the installation image, without needing the network." msgstr "" "Alternativt, hvis du forventer at bevare en eksisterende partition på " "harddisken uændret under installationen, så kan du hente filen &x86-hdmedia-" "initrd; og dens kerne, samt kopiere et installationsaftryk til drevet (sikr " "dig at filens navn ender med .iso). " "Installationsprogrammet kan så starte op fra drevet og installere fra " "installationsaftrykket, uden at kræve netværket." #. Tag: para #: install-methods.xml:391 #, no-c-format msgid "" "Finally, to configure the bootloader proceed to ." msgstr "" "Endelig, for at konfigure opstartsindllæseren fortsættes til ." #. Tag: title #: install-methods.xml:406 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "Forberedelse af filer for TFTP-netopstart" #. Tag: para #: install-methods.xml:407 #, no-c-format msgid "" "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." msgstr "" "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." #. Tag: para #: install-methods.xml:415 #, no-c-format msgid "" "You need to set up a TFTP server, and for many machines a DHCP server, or RARP server, or BOOTP server." msgstr "" "Du skal opsætte en TFTP-server, og for mange maskiner en DHCP-server, eller RARP-server, eller BOOTP-server." #. Tag: para #: install-methods.xml:422 #, no-c-format msgid "" "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. BOOTP is an IP protocol that informs a computer of its IP " "address and where on the network to obtain a boot image. The DHCP " "(Dynamic Host Configuration Protocol) is a more flexible, backwards-" "compatible extension of BOOTP. Some systems can only be configured via DHCP." msgstr "" "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. BOOTP er en IP-protokol, som informerer en " "computer om dens IP-adresse og hvor på netværket du kan finde et " "opstartsaftryk. DHcP'en (Dynamic Host Configuration Protocol) er en " "mere fleksibel, bagud kompatibel udvidelse af BOOTP. Nogle systemer kan kun " "konfigureres via DHCP." #. Tag: para #: install-methods.xml:448 #, no-c-format msgid "" "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." msgstr "" "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." #. Tag: para #: install-methods.xml:456 #, no-c-format msgid "" "For a &debian-gnu; server we recommend tftpd-hpa. " "It's written by the same author as the syslinux " "bootloader and is therefore least likely to cause issues. A good alternative " "is atftpd." msgstr "" "For en &debian-gnu;-server anbefaler vi tftpd-hpa. " "Den er skrevet af den samme forfatter som opstartsindlæseren " "syslinux og er derfor den mindst sandsynlige årsag " "til problemstillinger. Et godt alternativ er atftpd." #. Tag: title #: install-methods.xml:472 #, no-c-format msgid "Setting up RARP server" msgstr "Opsætning af en RARP-server" #. Tag: para #: install-methods.xml:473 #, no-c-format msgid "" "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 Rescue mode and use the " "command ip addr show dev eth0." msgstr "" "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 Redningstilstand og " "bruge kommandoen ip addr show dev eth0." #. Tag: para #: install-methods.xml:482 #, no-c-format msgid "" "On a RARP server system using a Linux kernel or Solaris/SunOS, you use the " "rarpd program. You need to ensure that the Ethernet " "hardware address for the client is listed in the ethers " "database (either in the /etc/ethers file, or via NIS/NIS" "+) and in the hosts database. Then you need to start the RARP " "daemon. Issue the command (as root): /usr/sbin/rarpd -a on most Linux systems and SunOS 5 (Solaris 2), /usr/" "sbin/in.rarpd -a on some other Linux systems, or /usr/" "etc/rarpd -a in SunOS 4 (Solaris 1)." msgstr "" "På et RARP-serversystem der bruger Linux-kernen eller Solaris/SunOS, skal du " "bruge programmet rarpd. Du skal sikre dig, at " "Ethernettets udstyrsadresse for klienten vises i databasen ethers (enten i filen /etc/ethers, eller via NIS/NIS+) " "og i databasen hosts. Så skal du starte RARP-dæmonen. Udsted " "kommandoen (som root): /usr/sbin/rarpd -a på de " "fleste Linux-systemer og SunOS 5 (Solaris 2), /usr/sbin/in.rarpd -" "a på nogle andre Linux-systemer, eller /usr/etc/rarpd " "-a i SunOS 4 (Solaris 1)." #. Tag: title #: install-methods.xml:503 #, no-c-format msgid "Setting up a DHCP server" msgstr "Opsætning af en DHCP-server" #. Tag: para #: install-methods.xml:504 #, no-c-format msgid "" "One free software DHCP server is ISC dhcpd. For &debian-" "gnu;, the isc-dhcp-server package is recommended. " "Here is a sample configuration file for it (see /etc/dhcp/dhcpd." "conf):" msgstr "" "En fri DHCP-server er ISC dhcpd. For &debian-gnu; " "anbefales pakken isc-dhcp-server. Her er et eksempel " "på en konfigurationsfil for den (se /etc/dhcp/dhcpd.conf):" #. Tag: screen #: install-methods.xml:511 #, no-c-format msgid "" "option domain-name \"example.com\";\n" "option domain-name-servers ns1.example.com;\n" "option subnet-mask 255.255.255.0;\n" "default-lease-time 600;\n" "max-lease-time 7200;\n" "server-name \"servername\";\n" "\n" "subnet 192.168.1.0 netmask 255.255.255.0 {\n" " range 192.168.1.200 192.168.1.253;\n" " option routers 192.168.1.1;\n" "}\n" "\n" "host clientname {\n" " filename \"/tftpboot.img\";\n" " server-name \"servername\";\n" " next-server servername;\n" " hardware ethernet 01:23:45:67:89:AB;\n" " fixed-address 192.168.1.90;\n" "}" msgstr "" "option domain-name \"example.com\";\n" "option domain-name-servers ns1.example.com;\n" "option subnet-mask 255.255.255.0;\n" "default-lease-time 600;\n" "max-lease-time 7200;\n" "server-name \"servername\";\n" "\n" "subnet 192.168.1.0 netmask 255.255.255.0 {\n" " range 192.168.1.200 192.168.1.253;\n" " option routers 192.168.1.1;\n" "}\n" "\n" "host clientname {\n" " filename \"/tftpboot.img\";\n" " server-name \"servername\";\n" " next-server servername;\n" " hardware ethernet 01:23:45:67:89:AB;\n" " fixed-address 192.168.1.90;\n" "}" #. Tag: para #: install-methods.xml:513 #, no-c-format msgid "" "In this example, there is one server servername " "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 " "filename option should be the name of the file " "which will be retrieved via TFTP." msgstr "" "I dette eksempel er der en server servername 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 filename skal være " "navnet på filen, som hentes via TFTP." #. Tag: para #: install-methods.xml:523 #, no-c-format msgid "" "After you have edited the dhcpd configuration file, " "restart it with /etc/init.d/isc-dhcp-server restart." msgstr "" "Efter du har redigeret konfigurationsfilen dhcpd, så " "genstart den med /etc/init.d/isc-dhcp-server restart." #. Tag: title #: install-methods.xml:531 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "Aktivering af PXE-opstart i DHCP-konfigurationen" #. Tag: para #: install-methods.xml:532 #, no-c-format msgid "" "Here is another example for a dhcp.conf using the Pre-" "boot Execution Environment (PXE) method of TFTP. \n" "option domain-name \"example.com\";\n" "\n" "default-lease-time 600;\n" "max-lease-time 7200;\n" "\n" "allow booting;\n" "allow bootp;\n" "\n" "# The next paragraph needs to be modified to fit your case\n" "subnet 192.168.1.0 netmask 255.255.255.0 {\n" " range 192.168.1.200 192.168.1.253;\n" " option broadcast-address 192.168.1.255;\n" "# the gateway address which can be different\n" "# (access to the internet for instance)\n" " option routers 192.168.1.1;\n" "# indicate the dns you want to use\n" " option domain-name-servers 192.168.1.3;\n" "}\n" "\n" "group {\n" " next-server 192.168.1.3;\n" " host tftpclient {\n" "# tftp client hardware address\n" " hardware ethernet 00:10:DC:27:6C:15;\n" " filename \"pxelinux.0\";\n" " }\n" "}\n" " Note that for PXE booting, the client filename " "pxelinux.0 is a boot loader, not a kernel image (see " " below)." msgstr "" "Her er et andet eksempel for dhcp.conf, der rbuger Pre-" "boot Execution Environment (PXE)-metoden for TFTP. " "\n" "option domain-name \"example.com\";\n" "\n" "default-lease-time 600;\n" "max-lease-time 7200;\n" "\n" "allow booting;\n" "allow bootp;\n" "\n" "# The next paragraph needs to be modified to fit your case\n" "subnet 192.168.1.0 netmask 255.255.255.0 {\n" " range 192.168.1.200 192.168.1.253;\n" " option broadcast-address 192.168.1.255;\n" "# the gateway address which can be different\n" "# (access to the internet for instance)\n" " option routers 192.168.1.1;\n" "# indicate the dns you want to use\n" " option domain-name-servers 192.168.1.3;\n" "}\n" "\n" "group {\n" " next-server 192.168.1.3;\n" " host tftpclient {\n" "# tftp client hardware address\n" " hardware ethernet 00:10:DC:27:6C:15;\n" " filename \"pxelinux.0\";\n" " }\n" "}\n" " Bemærk at for PXE-opstart, er klientfilnavnet " "pxelinux.0 en opstartsindlæser, ikke et kerneaftryk (se " " below)." #. Tag: para #: install-methods.xml:542 #, no-c-format msgid "" "If your machine uses UEFI to boot, you will have to specify a boot loader " "appropriate for UEFI machines, for example" msgstr "" "Hvis din maskine bruger UEFI til opstart, så skal du angive en " "opstartsindlæser passende for UEFI-maskiner, for eksempel" #. Tag: screen #: install-methods.xml:546 #, no-c-format msgid "" "group {\n" " next-server 192.168.1.3;\n" " host tftpclient {\n" "# tftp client hardware address\n" " hardware ethernet 00:10:DC:27:6C:15;\n" " filename \"debian-installer/amd64/bootnetx64.efi\";\n" " }\n" "}" msgstr "" "group {\n" " next-server 192.168.1.3;\n" " host tftpclient {\n" "# tftp client hardware address\n" " hardware ethernet 00:10:DC:27:6C:15;\n" " filename \"debian-installer/amd64/bootnetx64.efi\";\n" " }\n" "}" #. Tag: title #: install-methods.xml:559 #, no-c-format msgid "Setting up a BOOTP server" msgstr "Opsætning af en BOOTP-server" #. Tag: para #: install-methods.xml:560 #, no-c-format msgid "" "There are two BOOTP servers available for GNU/Linux. The first is CMU " "bootpd. The other is actually a DHCP server: ISC " "dhcpd. In &debian-gnu; these are contained in the " "bootp and isc-dhcp-server " "packages respectively." msgstr "" "Der er to BOOTP-servere tilgængelige for GNU/Linux. Den første er CMU " "bootpd. Den anden er faktisk en DHCP-server: ISC " "dhcpd. I &debian-gnu; er disse indeholdt i pakkerne " "bootp og isc-dhcp-server " "respektivt." #. Tag: para #: install-methods.xml:568 #, no-c-format msgid "" "To use CMU bootpd, you must first uncomment (or add) the " "relevant line in /etc/inetd.conf. On &debian-gnu;, you " "can run update-inetd --enable bootps, then " "/etc/init.d/inetd reload to do so. Just in case your " "BOOTP server does not run &debian;, the line in question should look like: " "\n" "bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120\n" " Now, you must create an /etc/bootptab file. This has the same sort of familiar and cryptic format as the " "good old BSD printcap, termcap, " "and disktab files. See the bootptab manual page for more information. For CMU bootpd, you will need to know the hardware (MAC) address of the client. " "Here is an example /etc/bootptab: " "\n" "client:\\\n" " hd=/tftpboot:\\\n" " bf=tftpboot.img:\\\n" " ip=192.168.1.90:\\\n" " sm=255.255.255.0:\\\n" " sa=192.168.1.1:\\\n" " ha=0123456789AB:\n" " You will need to change at least the ha option, which specifies the hardware address of the client. The " "bf option specifies the file a client should retrieve via " "TFTP; see for more details." msgstr "" "For at bruge CMU bootpd, skal du først aktivere (eller " "tilføje) de relevante linjer i /etc/inetd.conf. På " "&debian-gnu; kan du køre update-inetd --enable bootps, og så /etc/init.d/inetd reload 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:\n" "bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120\n" " Nu skal du oprette en /etc/bootptab-fil. Den har samme slags kendte og kryptiske format som det gode " "gamle BSD printcap-, termcap-, og " "disktab-filer. Se manualsiden bootptab for yderligere information. For CMU bootpd, " "skal du bruge udstyrsadressen (MAC) for klienten. Her er en eksempel " "/etc/bootptab: \n" "client:\\\n" " hd=/tftpboot:\\\n" " bf=tftpboot.img:\\\n" " ip=192.168.1.90:\\\n" " sm=255.255.255.0:\\\n" " sa=192.168.1.1:\\\n" " ha=0123456789AB:\n" " Du skal mindst ændre ha-" "tilvalget, som angiver udstyrsadressen for klienten. Tilvalget bf specificerer filen en klient skal hente via TFTP; se for yderligere detaljer." #. Tag: para #: install-methods.xml:595 #, no-c-format msgid "" "By contrast, setting up BOOTP with ISC dhcpd 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 . Otherwise you will probably be able to get away with simply " "adding the allow bootp directive to the configuration " "block for the subnet containing the client in /etc/dhcp/dhcpd." "conf, and restart dhcpd with /etc/" "init.d/isc-dhcp-server restart." msgstr "" "Som kontrast er opsætning af BOOTP med ISC dhcpd 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 . Ellers vil du sandsynligvis kunne slippe af sted med at tilføje " "allow bootp direkte til konfigurationsblokken for " "undernettet, der indeholder klienten i /etc/dhcp/dhcpd.conf, og genstarte dhcpd med /etc/init.d/" "isc-dhcp-server restart." #. Tag: title #: install-methods.xml:614 #, no-c-format msgid "Enabling the TFTP Server" msgstr "Aktivering af TFTP-serveren" #. Tag: para #: install-methods.xml:615 #, no-c-format msgid "" "To get the TFTP server ready to go, you should first make sure that " "tftpd is enabled." msgstr "" "For at få TFTP-serveren klar, skal du først sikre dig, at tftpd er aktiveret." #. Tag: para #: install-methods.xml:620 #, no-c-format msgid "" "In the case of tftpd-hpa there are two ways the " "service can be run. It can be started on demand by the system's " "inetd 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." msgstr "" "I tilfældet tftpd-hpa er der to måder at tjenesten " "kan køres. Den kan startes efter behov af systemets dæmon inetd, 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." #. Tag: para #: install-methods.xml:629 #, no-c-format msgid "" "Historically, TFTP servers used /tftpboot as directory " "to serve images from. However, &debian-gnu; packages may use other " "directories to comply with the Filesystem " "Hierarchy Standard. For example, tftpd-hpa by " "default uses /srv/tftp. You may have to adjust the " "configuration examples in this section accordingly." msgstr "" "Historisk brugte TFTP-servere /tftpboot som mappe til " "at betjene aftryk fra. Pakkerne &debian-gnu; kan bruge andre mapper til at " "overholde Filesystem Hierarchy Standard. For eksempel bruger tftpd-hpa som standard " "/srv/tftp. Du skal måske justere " "konfigurationseksemplerne i dette afsnit jævnfør dette." #. Tag: para #: install-methods.xml:639 #, no-c-format msgid "" "All in.tftpd alternatives available in &debian; should " "log TFTP requests to the system logs by default. Some of them support a " "-v 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." msgstr "" "Alle in.tftpd alternativer tilgængelige i &debian; bør " "logge TFTP-forespørgsler til systemets logge som standard. Nogle af dem " "understøtter et -v 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." #. Tag: title #: install-methods.xml:651 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "Flyt TFTP-aftryk på plads" #. Tag: para #: install-methods.xml:652 #, no-c-format msgid "" "Next, place the TFTP boot image you need, as found in , in the tftpd boot image directory. You may " "have to make a link from that file to the file which tftpd will use for booting a particular client. Unfortunately, the file " "name is determined by the TFTP client, and there are no strong standards." msgstr "" "Placer så TFTP-opstartsaftrykket du skal bruge som set i , i opstartsaftryksmappen tftpd. Du skal " "måske lave en henvisning fra den fil til filen som tftpd " "vil bruge til opstart af en bestemt klient. Desværre bestemmes filnavnet af " "TFTP-klienten, og der er ingen udbredte standarder." #. Tag: para #: install-methods.xml:703 #, no-c-format msgid "" "For PXE booting, everything you should need is set up in the " "netboot/netboot.tar.gz tarball. Simply extract this " "tarball into the tftpd boot image directory. Make sure " "your dhcp server is configured to pass pxelinux.0 to " "tftpd as the filename to boot. For UEFI machines, you " "will need to pass an appropriate EFI boot image name (such as /" "debian-installer/amd64/bootnetx64.efi)." msgstr "" "For PXE-opstart befinder alt du bør sætte op sig i tarball'en " "netboot/netboot.tar.gz. Udpak denne tarbal i mappen for " "opstartsaftrykket tftpd. Sikr dig at din dhcp-server er " "konfigureret til at sende pxelinux.0 til " "tftpd som filnavnet at starte op. For UEFI-maskiner skal " "du sende et passende EFI-opstartsaftryksnavn (såsom /debian-" "installer/amd64/bootnetx64.efi)." #. Tag: title #: install-methods.xml:722 #, no-c-format msgid "Automatic Installation" msgstr "Automatisk installation" #. Tag: para #: install-methods.xml:723 #, fuzzy, no-c-format #| msgid "" #| "For installing on multiple computers it's possible to do fully automatic " #| "installations. &debian; packages intended for this include fai-" #| "quickstart (which can use an install server) and the &debian; " #| "Installer itself. Have a look at the FAI home page for detailed information." msgid "" "For installing on multiple computers it's possible to do fully automatic " "installations. &debian; packages intended for this include fai-" "quickstart, which can use an install server (have a look at the " "FAI home page for detailed " "information) and the &debian; Installer itself." msgstr "" "For installation på flere computere er det muligt at udføre helt automatiske " "installationer. &debian;-pakker til dette formål inkluderer fai-" "quickstart (som kan bruge en installationsserver) og selve " "&debian;-installationsprogrammet. Kig på FAI's hjemmeside for detaljeret information." #. Tag: title #: install-methods.xml:735 #, no-c-format msgid "Automatic Installation Using the &debian; Installer" msgstr "Automatisk installation med &debian;-installationsprogrammet" #. Tag: para #: install-methods.xml:736 #, no-c-format msgid "" "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." msgstr "" "&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." #. Tag: para #: install-methods.xml:743 #, no-c-format msgid "" "Full documentation on preseeding including a working example that you can " "edit is in ." msgstr "" "Fuld dokumentation vedrørende preseeding inklusiv et arbejdseksempel, som du " "kan redigere er i ." #. Tag: title #: install-methods.xml:757 #, no-c-format msgid "Verifying the integrity of installation files" msgstr "Verifikation af integreiteten for installationsfiler" #. Tag: para #: install-methods.xml:759 #, no-c-format msgid "" "You can verify the integrity of downloaded files against checksums provided " "in SHA256SUMS or SHA512SUMS files " "on Debian mirrors. You can find them in the same places as the installation " "images itself. Visit the following locations:" msgstr "" "Du kan verificere integriteten for hentede filer mod kontrolsummer vist i " "filerne SHA256SUMS eller SHA512SUMS på Debianspejle. Du kan finde dem på samme sted som selve " "installationsaftrykkene. Besøg de følgende steder:" #. Tag: para #: install-methods.xml:770 #, no-c-format msgid "" "checksum files for CD images," msgstr "" "kontrolsumfiler for cd-aftryk," #. Tag: para #: install-methods.xml:776 #, no-c-format msgid "" "checksum files for DVD images," msgstr "" "kontrolsumfiler for dvd-aftryk," #. Tag: para #: install-methods.xml:782 #, no-c-format msgid "" "checksum files for BD images," msgstr "" "kontrolsumfiler for BD-aftryk," #. Tag: para #: install-methods.xml:788 #, no-c-format msgid "" "checksum files for other " "installation files." msgstr "" "kontrolsumfiler for andre " "installationsfiler." #. Tag: para #: install-methods.xml:796 #, no-c-format msgid "" "To compute the checksum of a downloaded installation file, use " "\n" "sha256sum filename.iso\n" " respective \n" "sha512sum filename.iso\n" " and then compare the shown checksum against the " "corresponding one in the SHA256SUMS respective " "SHA512SUMS file." msgstr "" "For at beregne kontrolsummen for et hentet installationsmedie, brug " "\n" "sha256sum filename.iso\n" " respektiv \n" "sha512sum filename.iso\n" " og sammenlign så den viste kontrolsum mod den " "tilsvarende i SHA256SUMS-filen respektiv " "SHA512SUMS-filen." #. Tag: para #: install-methods.xml:809 #, no-c-format msgid "" "The Debian CD FAQ has more useful " "information on this topic (such as the script " "check_debian_iso, to semi-automate above procedure), as " "well as instructions, how to verify the integrity of the above checksum " "files themselves." msgstr "" "Debians OSS for cd har mere nyttig " "information om dette emne (såsom skriptet " "check_debian_iso, til en semiautomatiseirng af " "ovenstående procedure), samt instruktioner om hvordan integriteten for de " "ovenstående kontrolsummer verificeres." #, no-c-format #~ msgid "" #~ "As CDs have a rather limited capacity by today's standards, not all " #~ "graphical desktop environments are installable with only the first CD; " #~ "for some desktop environments a CD installation requires either network " #~ "connectivity during the installation to download the remaining files or " #~ "additional CDs." #~ msgstr "" #~ "Da cd'er har en ret så begrænset kapacitet efter nutidens standarder, kan " #~ "ikke alle grafiske skrivebordsmiljøet installeres kun med den første cd; " #~ "for nogle skrivebordsmiljøet kræver en cd-installation enten " #~ "netværksforbindelse under installationen for at hente de resternede filer " #~ "eller yderligere cd'er." #~ msgid "" #~ "Alternatively, for very small USB sticks, only a few megabytes in size, " #~ "you can download the &netboot-mini-iso; image from the netboot directory (at the location mentioned in )." #~ msgstr "" #~ "Alternativt kan du for meget små USB-drev på kun nogle få megabyte hente " #~ "aftrykket &netboot-mini-iso; fra mappen netboot (på " #~ "placeringen nævnt i )." #~ msgid "" #~ "Simply writing the installation image to USB like this should work fine " #~ "for most users. The other options below are more complex, mainly for " #~ "people with specialised needs." #~ msgstr "" #~ "En simpel skrivning af installationsaftrykket til USB bør fungere fint " #~ "for de fleste brugere. De andre muligheder er mere komplekse og " #~ "hovedsagelig for folk med specielle behov." #~ msgid "" #~ "The hybrid image on the stick does not occupy all the storage space, so " #~ "it may be worth considering using the free space to hold firmware files " #~ "or packages or any other files of your choice. This could be useful if " #~ "you have only one stick or just want to keep everything you need on one " #~ "device." #~ msgstr "" #~ "Hybridaftrykket på drevet bruger ikke al lagerplads, så kan være en " #~ "overvejelse værd at bruge den ledige plads til firmware-filer eller " #~ "pakker eller andre filer efter dit eget valg. Dette kan være nyttigt, " #~ "hvis du kun har et drev eller bare ønsker at have alt på en enhed." #~ msgid "" #~ "To do so, use cfdisk or any other partitioning tool to create an " #~ "additional partition on the stick. Then create a (FAT) filesystem on the " #~ "partition, mount it and copy or unpack the firmware onto it, for example " #~ "with: \n" #~ "# mkdosfs -n FIRMWARE /dev/sdX3\n" #~ "# mount /dev/sdX3 /mnt\n" #~ "# cd /mnt\n" #~ "# tar zxvf /path/to/firmware.tar.gz\n" #~ "# cd /\n" #~ "# umount /mnt\n" #~ " Take care that you use the correct device " #~ "name for your USB stick. The mkdosfs command is " #~ "contained in the dosfstools &debian; package." #~ msgstr "" #~ "For dette, brug cfdisk eller et andet partitioneringsværktøj til at " #~ "oprette en yderligere partition på drevet. Opret så et (FAT) filsystem på " #~ "partitionen, monter den og kopier eller udpak firmwaren på den, for " #~ "eksempel med: \n" #~ "# mkdosfs -n FIRMWARE /dev/sdX3\n" #~ "# mount /dev/sdX3 /mnt\n" #~ "# cd /mnt\n" #~ "# tar zxvf /sti/til/firmware.tar.gz\n" #~ "# cd /\n" #~ "# umount /mnt\n" #~ " Husk at bruge det korrekte enhedsnavn for dit " #~ "USB-drev. Kommandoen mkdosfs er indeholdt i &debian;" #~ "pakken dosfstools." #~ msgid "" #~ "If you have chosen the mini.iso to be written to the " #~ "USB stick, the second partition doesn't have to be created, as - very " #~ "nicely - it will already be present. Unplugging and replugging the USB " #~ "stick should make the two partitions visible." #~ msgstr "" #~ "Hvis du har valg at mini.iso skal skrives til USB-" #~ "drevet, så skal den anden partition ikke oprettes, da den - meget " #~ "passende - allerede vil være til stede. Fjernelse og isættelse af USB-" #~ "drevet bør gøre de to partitioner synlige." #~ msgid "Manually copying files to the USB stick" #~ msgstr "Manuelt kopiere filer til USB-drevet" #~ msgid "" #~ "Prior to isohybrid technology being used for &debian; installation " #~ "images, the methods documented in the chapters below were used to prepare " #~ "media for booting from USB devices. These have been superseded by the " #~ "technique in , but have been left " #~ "here for educational and historical purposes and in case they are useful " #~ "to some user." #~ msgstr "" #~ "Før teknologien isohybrid blev brugt til &debian;-installationsaftryk, " #~ "blev metoderne dokumenteret i afsnittene nedenfor brugt til at forberede " #~ "medier for opstart fra USB-enheder. Disse er blevet afløst af teknikken i " #~ ", men er blevet bevaret her af " #~ "undervisningsmæssige og historiske formål, og i tilfælde af, at de skulle " #~ "være nyttig for nogle brugere." #~ msgid "" #~ "An alternative to the method described in is to manually copy the installer files, and also an " #~ "installation image to the stick. Note that the USB stick should be at " #~ "least 1 GB in size (smaller setups are possible using the files from " #~ "netboot, following )." #~ msgstr "" #~ "En alternativ måde til metoderne beskrevet i er manuelt at kopiere installationsfilerne, og et " #~ "installationsaftryk til drevet. Bemærk at USB-drevet bør være på mindst 1 " #~ "GB (mindre opsætninger er mulige, hvis du bruger filerne fra netboot, " #~ "efter )." #~ msgid "" #~ "There is an all-in-one file &hdmedia-boot-img; which contains all the " #~ "installer files (including the kernel) as well as " #~ "syslinux and its configuration file." #~ msgstr "" #~ "Der er en alt i en-fil &hdmedia-boot-img; som indeholder alle " #~ "installationsprogrammets filer (inklusive the kernen) samt syslinux og dets konfigurationsfil." #~ msgid "" #~ "Note that, although convenient, this method does have one major " #~ "disadvantage: the logical size of the device will be limited to 1 GB, " #~ "even if the capacity of the USB stick is larger. You will need to " #~ "repartition the USB stick and create new file systems to get its full " #~ "capacity back if you ever want to use it for some different purpose." #~ msgstr "" #~ "Bemærk dog, selvom det er nemt, at denne metode har en stor ulempe: Den " #~ "logiske størrelse på enheden vil være begrænset til 1 GB, selv hvis " #~ "kapaciteten på USB-drevet er større. Du skal partitionere USB-drevet igen " #~ "og oprette nye filsystemer for at få den fulde kapacitet tilbage, hvis du " #~ "ønsker at bruge den til andre formål." #~ msgid "Simply extract this image directly to your USB stick:" #~ msgstr "Udtræk dette aftryk direkte til dit USB-drev:" #~ msgid "# zcat boot.img.gz > /dev/sdX" #~ msgstr "# zcat boot.img.gz > /dev/sdX" #~ msgid "" #~ "After that, mount the USB memory stick (mount /dev/sdX /mnt), (mount /dev/" #~ "sdX2 /mnt), which will " #~ "now have a FAT filesystem an HFS filesystem on it, and copy a &debian; ISO " #~ "image (netinst or full CD; see ) to it. " #~ "Unmount the stick (umount /mnt) and you are done." #~ msgstr "" #~ "Derefter monteres USB-hukommelsesdrevet (mount /dev/sdX /mnt), (mount /dev/" #~ "sdX2 /mnt), som nu vil " #~ "have et FAT-filsystem et HFS-filsystem på sig og kopier et &debian; ISO-aftryk " #~ "(netinst eller fuld cd; se ) til den. " #~ "Afmonter drevet (umount /mnt) og du er færdig." #~ msgid "Manually copying files to the USB stick — the flexible way" #~ msgstr "Manuelt kopiere filer til USB-drevet — den fleksible måde" #~ msgid "" #~ "If you like more flexibility or just want to know what's going on, you " #~ "should use the following method to put the files on your stick. One " #~ "advantage of using this method is that — if the capacity of your " #~ "USB stick is large enough — you have the option of copying any ISO " #~ "image, even a DVD image, to it." #~ msgstr "" #~ "Hvis du ønsker højere fleksibilitet eller bare ønsker at vide, hvad der " #~ "foregår, så kan du bruge en af de følgende metoder til at placere filerne " #~ "på dit drev. En af fordelene ved denne metode er at — hvis " #~ "kapaciteten på dit USB-drev er stor nok — så kan du kopiere ethvert " #~ "ISO-aftryk eller endda et dvd-aftryk til drevet." #~ msgid "Partitioning and adding a boot loader" #~ msgstr "Partitionering og tilføjelse af en opstartsindlæser" #~ msgid "" #~ "We will show how to set up the memory stick to use the first partition, " #~ "instead of the entire device." #~ msgstr "" #~ "Vi vil vise hvordan hukommelsesdrevet opsættes til at bruge den første " #~ "partition, i stedet for hele enheden." #~ msgid "" #~ "In order to start the kernel after booting from the USB stick, we will " #~ "put a boot loader on the stick. Although any boot loader should work, " #~ "it's convenient to use syslinux, since it uses a " #~ "FAT16 partition and can be reconfigured by just editing a text file. Any " #~ "operating system which supports the FAT file system can be used to make " #~ "changes to the configuration of the boot loader." #~ msgstr "" #~ "For at starte kernen efter opstart fra USB-drevet, vil vi placere en " #~ "opstartsindlæser på drevet. Selvom enhver opstartsindlæser bør fungere, " #~ "er det praktisk at bruge syslinux, da den bruger " #~ "en FAT16-partition og kan konfigureres om ved bare at redigere en " #~ "tekstfil. Ethvert operativsystem som understøtter FAT-filsystemet kan " #~ "bruges til at lave ændringer til konfigurationen af opstartsindlæseren." #~ msgid "" #~ "First, you need to install the syslinux and " #~ "mtools packages on your system." #~ msgstr "" #~ "Først skal du installere pakkerne syslinux og " #~ "mtools på dit system." #~ msgid "" #~ "Since most USB sticks come pre-configured with a single FAT16 partition, " #~ "you probably won't have to repartition or reformat the stick. If you have " #~ "to do that anyway, use cfdisk or any other " #~ "partitioning tool to create a FAT16 partition now Don't " #~ "forget to activate the bootable flag. , " #~ "and then install an MBR using: \n" #~ "# cat /usr/lib/syslinux/mbr/mbr.bin >/dev/sdX\n" #~ " Now create the filesystem using: " #~ "\n" #~ "# mkdosfs /dev/sdX1\n" #~ " Take care that you use the correct device " #~ "name for your USB stick. The mkdosfs command is " #~ "contained in the dosfstools &debian; package." #~ msgstr "" #~ "Da de fleste USB-drev kommer prækonfigurede med en enkel FAT16-partition, " #~ "så skal du sandsynligvis ikke partitioner eller formatere drevet igen. " #~ "Hvis du alligevel skal gøre dette, så brug cfdisk " #~ "eller et andet partitioneringsværktøj til at oprette en FAT16-" #~ "partition Glem ikke at angive opstartsflaget " #~ "bootable. , installer en MBR via: " #~ "\n" #~ "# cat /usr/lib/syslinux/mbr/mbr.bin >/dev/sdX\n" #~ " Now create the filesystem using: " #~ "\n" #~ "# mkdosfs /dev/sdX1\n" #~ " Vær opmærksom på at bruge det korrekte " #~ "enhedsnavn for dit USB-drev. Kommandoen mkdosfs er " #~ "indeholdt i &debian;-pakken dosfstools." #~ msgid "" #~ "Having a correctly partitioned USB stick (now), you need to put " #~ "syslinux on the FAT16 partition with: " #~ "\n" #~ "# syslinux /dev/sdX1\n" #~ " Again, take care that you use the correct " #~ "device name. The partition must not be mounted when starting " #~ "syslinux. This procedure writes a boot sector to the " #~ "partition and creates the file ldlinux.sys which " #~ "contains the boot loader code." #~ msgstr "" #~ "For at få et korrekt partitioneret USB-drev (nu), skal du placere " #~ "syslinux på FAT16-partionen med: " #~ "\n" #~ "# syslinux /dev/sdX1\n" #~ " Igen husk at sikre dig, at du bruger det " #~ "korrekte enhedsnavn. Partitionen må ikke være monteret når " #~ "syslinux startes. Denne procedure skriver en " #~ "opstartssektor til partionen og opretter filen ldlinux.sys, som indeholder koden for opstartsindlæseren." #~ msgid "Adding the installer files" #~ msgstr "Tilføjelse af installationsfilerne" #~ msgid "" #~ "There are two different installation variants to choose here: The hd-" #~ "media variant needs an installation ISO file on the stick, to load " #~ "installer modules and the base system from. The netboot installer however " #~ "will load all that from a &debian; mirror." #~ msgstr "" #~ "Der er to forskellige installationsvarianter at vælge fra: varianten hd-" #~ "media skal bruge en ISO-installationsfil på drevet, for at indlæse " #~ "installationsmodulerne og basissystemet. Installationsprogrammet netboot " #~ "vil dog indlæse alt det fra et &debian;-spejl." #~ msgid "" #~ "According to your choice, you have to download some installer files from " #~ "the hd-media or netboot subdirectory of debian/dists/&releasename;/main/installer-" #~ "&architecture;/current/images/ on any &debian; mirror: " #~ " vmlinuz or " #~ "linux (kernel binary) " #~ " initrd.gz (initial ramdisk image) You can choose between either the text-" #~ "based version of the installer (the files can be found directly in hd-" #~ "media or netboot) or the graphical version (look in the respective " #~ "gtk subdirectories)." #~ msgstr "" #~ "Jævnfør dit valg, så skal du hente nogle installationsfiler fra " #~ "undermappen hd-media eller netboot i debian/dists/&releasename;/main/installer-&architecture;/current/" #~ "images/ på ethvert &debian;-spejl: " #~ " vmlinuz eller linux (binær fil for kernen) " #~ "initrd.gz (oprindelig ramdisk-aftryk) Du kan vælge mellem enten den tekstbaserede " #~ "version af installationsprogrammet (filerne kan findes direkte i hd-media " #~ "eller netboot) eller den grafiske version se i de respektive " #~ "gtk-undermapper)." #~ msgid "" #~ "Then mount the partition (mount /dev/sdX1 /mnt) and copy the downloaded files to the root " #~ "directory of the stick." #~ msgstr "" #~ "Monter partitionen (mount /dev/sdX1 /mnt) og kopier de hentede filer til rodmappen " #~ "på drevet." #~ msgid "" #~ "Next you should create a text file named syslinux.cfg in the root directory of the stick as configuration file for " #~ "syslinux, which at a bare minimum should contain the following line: " #~ "\n" #~ "default vmlinuz initrd=initrd.gz\n" #~ " Change the name of the kernel binary to " #~ "linux if you used files from " #~ "netboot." #~ msgstr "" #~ "Derefter bør du oprette en tekstfil navngivet syslinux.cfg i rodmappen på drevet som konfigurationsfil for syslinux, der " #~ "som et absolut minimum skal indeholde den følgende linje: " #~ "\n" #~ "default vmlinuz initrd=initrd.gz\n" #~ " Ændr navnet for kernens binære fil til " #~ "linux hvis du anvendte filer fra " #~ "netboot." #~ msgid "" #~ "For the graphical installer (from gtk) you should " #~ "add vga=788 at the end of the line. Other " #~ "parameters can be appended as desired." #~ msgstr "" #~ "For det grafiske installationsprogram (fra gtk) bør " #~ "du tilføje vga=788 til den anden linje. Andre " #~ "parametre kan tilføjes som ønsket." #~ msgid "" #~ "To enable the boot prompt to permit further parameter appending, add a " #~ "prompt 1 line." #~ msgstr "" #~ "For at aktivere opstartsprompten til at acceptere yderligere " #~ "parametertilføjelse, tilføjes en linje prompt 1." #~ msgid "" #~ "If you used files from hd-media, you should now copy " #~ "the ISO file of a &debian; installation image onto the stick. (For the " #~ "netboot variant this is not needed.)" #~ msgstr "" #~ "Hvis du anvendte filer fra hd-media, så bør du nu " #~ "kopiere ISO-filen for et &debian;-installationsaftryk ned på drevet. (For " #~ "varianten netboot er dette ikke krævet)." #~ msgid "" #~ "You can use either a netinst or a full CD/DVD image (see ). Be sure to select one that fits on your stick. " #~ "Note that the netboot mini.iso image " #~ "is not usable for this purpose." #~ msgstr "" #~ "Du kan bruge enten en netinst eller et fuld cd/dvd-aftryk (se ). Vær sikker på at vælge et som passer. " #~ "Bemærk at netboot mini.iso-aftrykket " #~ "ikke er brugbar til dette formål." #~ msgid "" #~ "When you are done, unmount the USB memory stick (umount /mnt)." #~ msgstr "" #~ "Når du er færdig, afmonter USB-drevet (umount /mnt)." #~ msgid "" #~ "Hard disk installer booting from DOS using loadlin" #~ msgstr "" #~ "Harddiskinstallationen starter op fra DOS med loadlin" #~ msgid "" #~ "This section explains how to prepare your hard drive for booting the " #~ "installer from DOS using loadlin." #~ msgstr "" #~ "Dette afsnit forklarer hvordan du forbereder din harddisk til at starte " #~ "installationsprogrammet op fra DOS med loadlin." #~ msgid "" #~ "Copy the following directories from a &debian; installation image to " #~ "c:\\." #~ msgstr "" #~ "Kopier de følgende mapper fra et &debian;-installationsaftryk til " #~ "c:\\." #~ msgid "" #~ "/&x86-install-dir; (kernel binary and ramdisk image)" #~ msgstr "" #~ "/&x86-install-dir; (kernens binære fil og " #~ "ramdiskaftryk)" #~ msgid "/tools (loadlin tool)" #~ msgstr "/tools (loadlin-værktøj)" #~ msgid "" #~ "Create a partition of type \"Apple_Bootstrap\" on your USB stick using " #~ "mac-fdisk's C command and " #~ "extract the image directly to that:" #~ msgstr "" #~ "Opret en partition af typen »Apple_Bootstrap« på dit USB-drev via " #~ "mac-fdisks C-kommando og udtræk " #~ "aftrykket direkte til denne:" #~ msgid "# zcat boot.img.gz > /dev/sdX2" #~ msgstr "# zcat boot.img.gz > /dev/sdX2" #~ msgid "Partitioning the USB stick" #~ msgstr "Partitionering af USB-drevet" #~ msgid "" #~ "Most USB sticks do not come pre-configured in such a way that Open " #~ "Firmware can boot from them, so you will need to repartition the stick. " #~ "On Mac systems, run mac-fdisk /dev/sdX, initialise a new partition map using the " #~ "i command, and create a new partition of type " #~ "Apple_Bootstrap using the C command. (Note that " #~ "the first \"partition\" will always be the partition map itself.) Then " #~ "type \n" #~ "$ hformat /dev/sdX2\n" #~ " Take care that you use the correct device " #~ "name for your USB stick. The hformat command is " #~ "contained in the hfsutils &debian; package." #~ msgstr "" #~ "De fleste USB-drev er ikke prækonfigurerede på en sådan måde at Open " #~ "Firmware kan starte op fra dem, så du skal partitionere drevet om. På Mac-" #~ "systemer, kør mac-fdisk /dev/sdX, initialiser et nyt partitionskort via kommandoen " #~ "i, og opret en ny partition af typen " #~ "Apple_Bootstrap via kommandoen C. (Bemærk at den " #~ "første »partition« altid vil være selve partitionskortet). Tast så " #~ "\n" #~ "$ hformat /dev/sdX2\n" #~ " Sikr dig, at du bruger det korrekte " #~ "enhedsnavn på dit USB-drev. Kommandoen hformat er " #~ "indeholdt i &debian;-pakken hfsutils." #~ msgid "" #~ "In order to start the kernel after booting from the USB stick, we will " #~ "put a boot loader on the stick. The yaboot boot loader " #~ "can be installed on an HFS filesystem and can be reconfigured by just " #~ "editing a text file. Any operating system which supports the HFS file " #~ "system can be used to make changes to the configuration of the boot " #~ "loader." #~ msgstr "" #~ "For at starte kernen efter opstart fra USB-drevet, vil vi placere en " #~ "opstartsindlæser på drevet. Opstartsindlæseren yaboot " #~ "kan installeres på et HFS-filsystem og kan konfigureres om ved bare at " #~ "redigere en tekstfil. Alle operativsystemer som understøtter HFS-" #~ "filsystemet kan bruges til at udføre ændringer til konfigurationen af " #~ "opstartsindlæseren." #~ msgid "" #~ "The normal ybin tool that comes with yaboot does not yet understand USB storage devices, so you will have to " #~ "install yaboot by hand using the hfsutils tools. Type \n" #~ "$ hmount /dev/sdX2\n" #~ "$ hcopy -r /usr/lib/yaboot/yaboot :\n" #~ "$ hattrib -c UNIX -t tbxi :yaboot\n" #~ "$ hattrib -b :\n" #~ "$ humount\n" #~ " Again, take care that you use the correct " #~ "device name. The partition must not be otherwise mounted during this " #~ "procedure. This procedure writes the boot loader to the partition, and " #~ "uses the HFS utilities to mark it in such a way that Open Firmware will " #~ "boot it. Having done this, the rest of the USB stick may be prepared " #~ "using the normal Unix utilities." #~ msgstr "" #~ "Det normale værktøj ybin, som følger med " #~ "yaboot forstår endnu ikke USB-lagerenheder, så du skal " #~ "installere yaboot manuelt via hfsutils-værktøjerne. Tast \n" #~ "$ hmount /dev/sdX2\n" #~ "$ hcopy -r /usr/lib/yaboot/yaboot :\n" #~ "$ hattrib -c UNIX -t tbxi :yaboot\n" #~ "$ hattrib -b :\n" #~ "$ humount\n" #~ " Sikr dig, at du bruger det korrekte " #~ "enhedsnavn. Partitionen må ikke på anden vis monteres under denne " #~ "procedure. Denne procedure skriver opstartsindlæseren til partitionen, og " #~ "bruger HFS-redskaberne til at markere den på en måde så at Open Firmware " #~ "vil starte den op. Når dette er gjort kan resten af USB-drevet forberedes " #~ "med normale UNIX-redskaber." #~ msgid "Adding the installer image" #~ msgstr "Tilføjelse af installationsprogrammets aftryk" #~ msgid "" #~ "Mount the partition (mount /dev/sdX2 /mnt) and copy the following installer image " #~ "files to the stick:" #~ msgstr "" #~ "Monter partitionen (mount /dev/sdX2 /mnt) og kopier de følgende " #~ "installationsaftryksfiler til drevet:" #~ msgid "vmlinux (kernel binary)" #~ msgstr "vmlinux (kernens binære fil)" #~ msgid "initrd.gz (initial ramdisk image)" #~ msgstr "initrd.gz (oprindelig ramdisk-aftryk)" #~ msgid "yaboot.conf (yaboot configuration file)" #~ msgstr "yaboot.conf (yaboot-konfigurationsfil)" #~ msgid "boot.msg (optional boot message)" #~ msgstr "boot.msg (valgfri opstartsbesked)" #~ msgid "" #~ "The yaboot.conf configuration file should contain " #~ "the following lines: \n" #~ "default=install\n" #~ "root=/dev/ram\n" #~ "\n" #~ "message=/boot.msg\n" #~ "\n" #~ "image=/vmlinux\n" #~ " label=install\n" #~ " initrd=/initrd.gz\n" #~ " initrd-size=10000\n" #~ " read-only\n" #~ " Please note that the initrd-size parameter may need to be increased, depending on the image you " #~ "are booting." #~ msgstr "" #~ "Konfigurationsfilen yaboot.conf bør indeholder de " #~ "følgende linjer: \n" #~ "default=install\n" #~ "root=/dev/ram\n" #~ "\n" #~ "message=/boot.msg\n" #~ "\n" #~ "image=/vmlinux\n" #~ " label=install\n" #~ " initrd=/initrd.gz\n" #~ " initrd-size=10000\n" #~ " read-only\n" #~ " Bemærk venligst at parameteren " #~ "initrd-size måske skal øges, afhængig af aftrykket " #~ "du indlæser." #~ msgid "" #~ "If you used an hd-media image, you should now copy " #~ "the ISO file of a &debian; ISO image You can use either " #~ "a netinst or a full CD image (see ). Be " #~ "sure to select one that fits. Note that the netboot mini." #~ "iso image is not usable for this purpose. onto the stick. When you are done, unmount the USB memory stick " #~ "(umount /mnt)." #~ msgstr "" #~ "Hvis du anvendte et hd-media-aftryk, så bør du " #~ "kopiere ISO-filen for et &debian;-ISO-aftryk Du kan " #~ "bruge enten en netinst eller et fuld cd-aftryk (se ). Vær sikker på at vælge et som passer. Bemærk at " #~ "netboot mini.iso-aftrykket ikke er " #~ "brugbar til dette formål. ned på drevet. Når du er " #~ "færdig, afmonter USB-drevet (umount /mnt)." #~ msgid "" #~ "The installer cannot boot from files on an HFS+ file system. MacOS System " #~ "8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. " #~ "To determine whether your existing file system is HFS+, select " #~ "Get Info for the volume in question. HFS file " #~ "systems appear as Mac OS Standard, while HFS+ file " #~ "systems say Mac OS Extended. You must have an HFS " #~ "partition in order to exchange files between MacOS and Linux, in " #~ "particular the installation files you download." #~ msgstr "" #~ "Installationsprogrammet kan ikke starte op fra filer på et HFS+-" #~ "filsystem. MacOS System 8.1 og senere kan bruge HFS+-filsystemer; " #~ "NewWorld PowerMacs bruger alle HFS+. For at bestemme om dit eksisterende " #~ "filsystem er HFS+, vælges Hent information for " #~ "diskenheden. HFS-filsystemet fremstår som Mac OS Standard, mens HFS+-filsystemet er Mac OS Extended. Du skal have en HFS-partition for at udtrække filer mellem " #~ "MacOS og Linux, specielt installationsfilerne du hentede." #~ msgid "" #~ "Different programs are used for hard disk installation system booting, " #~ "depending on whether the system is a NewWorld or an " #~ "OldWorld model." #~ msgstr "" #~ "Forskellige programmer bruges til systemopstart af installationen fra " #~ "harddisk afhængig af om systemet er NewWorld eller " #~ "OldWorld." #~ msgid "" #~ "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good " #~ "idea to use DHCP instead of BOOTP. Some of the latest machines are unable " #~ "to boot using BOOTP." #~ msgstr "" #~ "For PowerPC, hvis du har en NewWorld Power Macintosh-maskine, er det en " #~ "god ide at bruge DHCP i stedet for BOOTP. Nogle af de seneste maskiner " #~ "kan ikke starte op via BOOTP." #~ msgid "" #~ "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. " #~ "There is an rbootd package available in &debian;." #~ msgstr "" #~ "Nogle ældre HPPA-maskiner (f.eks. 715/75) bruger RBOOTD frem for BOOTP. " #~ "Der er en rbootd-pakke tilgængelig i &debian;." #~ msgid "" #~ "If you intend to install &debian; on an SGI machine and your TFTP server " #~ "is a GNU/Linux box running Linux 2.4, you'll need to set the following on " #~ "your server: \n" #~ "# echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc\n" #~ " to turn off Path MTU discovery, otherwise the " #~ "SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets " #~ "are sent from a source port no greater than 32767, or the download will " #~ "stall after the first packet. Again, it's Linux 2.4.X tripping this bug " #~ "in the PROM, and you can avoid it by setting \n" #~ "# echo \"2048 32767\" > /proc/sys/net/ipv4/ip_local_port_range\n" #~ " to adjust the range of source ports the Linux " #~ "TFTP server uses." #~ msgstr "" #~ "Hvis du planlægger at installere &debian; på en SGI-maskine og din TFTP-" #~ "server er en GNU/Linux-boks, der kører Linux 2.4, så skal du angive det " #~ "følgende på din server: nux box running Linux 2.4, you'll need to set the " #~ "following on your server: \n" #~ "# echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc\n" #~ " for at deaktivere Path MTU-registrering, " #~ "ellers kan SGI's PROM ikke hente kernen. Derudover skal du sikre dig, at " #~ "TFTP-pakker sendes fra en kildeport, der ikke er højere end 32767, ellers " #~ "vil overførslen stoppe efter den første pakke. Igen det er Linux 2.4.x " #~ "der udløser denne fejl i PROM'en, og du kan undgå den ved at angive " #~ "\n" #~ "# echo \"2048 32767\" > /proc/sys/net/ipv4/ip_local_port_range\n" #~ " for at justere intervallet af kildeporte som " #~ "Linux TFTP-serveren bruger." #~ msgid "" #~ "On NewWorld Power Macintosh machines, you will need to set up the " #~ "yaboot boot loader as the TFTP boot image. " #~ "Yaboot will then retrieve the kernel and RAMdisk " #~ "images via TFTP itself. You will need to download the following files " #~ "from the netboot/ directory:" #~ msgstr "" #~ "På NewWorld Power Macintosh-maskiner skal du opsætte opstartsindlæseren " #~ "yaboot som TFTP-opstartsaftryk. Yaboot vil selv hente kernen og RAMdisk-aftryk via TFTP. Du skal hente " #~ "de følgende filer fra mappen netboot/:" #~ msgid "vmlinux" #~ msgstr "vmlinux" #~ msgid "initrd.gz" #~ msgstr "initrd.gz" #~ msgid "yaboot" #~ msgstr "yaboot" #~ msgid "yaboot.conf" #~ msgstr "yaboot.conf" #~ msgid "boot.msg" #~ msgstr "boot.msg" #~ msgid "" #~ "For PXE booting, everything you should need is set up in the " #~ "netboot/netboot.tar.gz tarball. Simply extract this " #~ "tarball into the tftpd boot image directory. Make sure " #~ "your dhcp server is configured to pass /debian-installer/ia64/" #~ "elilo.efi to tftpd as the filename to boot." #~ msgstr "" #~ "For PXE-opstart befinder alt du bør sætte op sig i tarball'en " #~ "netboot/netboot.tar.gz. Udpak denne tarbal i mappen " #~ "for opstartsaftrykket tftpd. Sikr dig at din dhcp-" #~ "server er konfigureret til at sende /debian-installer/ia64/" #~ "elilo.efi til tftpd som filnavnet at starte " #~ "op." #~ msgid "SPARC TFTP Booting" #~ msgstr "SPARC TFTP-opstart" #~ msgid "" #~ "Some SPARC architectures add the subarchitecture names, such as " #~ "SUN4M or SUN4C, to the filename. Thus, if " #~ "your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the " #~ "filename would be C0A80103.SUN4C. However, there are " #~ "also subarchitectures where the file the client looks for is just " #~ "client-ip-in-hex. An easy way to determine the " #~ "hexadecimal code for the IP address is to enter the following command in " #~ "a shell (assuming the machine's intended IP is 10.0.0.4). " #~ "\n" #~ "$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n" #~ " To get to the correct filename, you will need " #~ "to change all letters to uppercase and if necessary append the " #~ "subarchitecture name." #~ msgstr "" #~ "Nogle SPARC-arkitekturer tilføjer underarkitekturnavne, såsom " #~ "SUN4M eller SUN4C, til filnavnet. Hvis dit " #~ "systems underarkitektur er en SUN4c, og dets IP er 192.168.1.3, vil " #~ "filnavnet være C0A80103.SUN4C. Men der er også " #~ "underarkitekturer hvor filen klienten kigger efter kun er " #~ "client-ip-in-hex. En nem måde at bestemme den " #~ "hexadecimale kode for IP-adressen er at indtaste den følgende kommando i " #~ "en skal (under antagelse af at maskinens forventede IP er 10.0.0.4). " #~ "\n" #~ "$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n" #~ " For at hente det korrekte filnavn, så skal du " #~ "ændre alle bogstaverne til store bogstaver og om nødvendigt tilføje " #~ "underarkitekturnavnet." #~ msgid "" #~ "If you've done all this correctly, giving the command boot " #~ "net from the OpenPROM should load the image. If the image " #~ "cannot be found, try checking the logs on your tftp server to see which " #~ "image name is being requested." #~ msgstr "" #~ "Hvis du har gjort alt dette korrekt, vil kommandoen boot net fra OpenPROM indlæse aftrykket. Hvis aftrykket ikke kan " #~ "findes, så prøv at kontrollere loggene på din tftp-server for at se " #~ "hvilket aftryksnavn der anmodes om." #~ msgid "" #~ "You can also force some sparc systems to look for a specific file name by " #~ "adding it to the end of the OpenPROM boot command, such as " #~ "boot net my-sparc.image. This must still reside in " #~ "the directory that the TFTP server looks in." #~ msgstr "" #~ "Du kan også fremtvinge nogle sparc-systemer til at kigge efter et " #~ "specifikt filnavn ved at tilføjet det til slutningen af OpenPROM-" #~ "opstartskommandoen, såsom boot net my-sparc.image. " #~ "Dette skal stadig befinde sig i mappen som TFTP-serveren kigger i." #~ msgid "SGI TFTP Booting" #~ msgstr "SGI TFTP-opstart" #~ msgid "" #~ "On SGI machines you can rely on the bootpd to supply " #~ "the name of the TFTP file. It is given either as the bf= in /etc/bootptab or as the " #~ "filename= option in /etc/dhcpd.conf." #~ msgstr "" #~ "På SGI-maskiner kan du stole på bootpd for at levere " #~ "navnet på TFTP-filen. Den angives enten som bf= i " #~ "/etc/bootptab eller som filename=-tlvalget i /etc/dhcpd.conf." #~ msgid "" #~ "Create a second, FAT partition on the stick, mount the partition and copy " #~ "or unpack the firmware onto it. For example:" #~ msgstr "" #~ "Opret endnu en FAT-partition på drevet, monter partitionen og kopier " #~ "eller udpak firmwaren til den. For eksempel:" #~ msgid "" #~ "# mount /dev/sdX2 /mnt\n" #~ "# cd /mnt\n" #~ "# tar zxvf /path/to/firmware.tar.gz\n" #~ "# cd /\n" #~ "# umount /mnt" #~ msgstr "" #~ "# mount /dev/sdX2 /mnt\n" #~ "# cd /mnt\n" #~ "# tar zxvf /path/to/firmware.tar.gz\n" #~ "# cd /\n" #~ "# umount /mnt" #~ msgid "" #~ "Hard disk installer booting from Linux using LILO or " #~ "GRUB" #~ msgstr "" #~ "Installationsprogrammets opstart fra harddisk fra Linux med brug af " #~ "LILO eller GRUB" #~ msgid "Creating Floppies from Disk Images" #~ msgstr "Oprette disketter fra diskaftryk" #~ msgid "" #~ "Bootable floppy disks are generally used as a last resort to boot the " #~ "installer on hardware that cannot boot from CD or by other means." #~ msgstr "" #~ "Opstartsbare disketter bruges generelt som en sidste mulighed til at " #~ "starte installationsprogrammet op, på udstyr som ikke kan starte fra cd " #~ "eller ved andre metoder." #~ msgid "" #~ "Booting the installer from floppy disk reportedly fails on Mac USB floppy " #~ "drives." #~ msgstr "" #~ "Opstart af installationsprogrammet fra diskettedrev fejler på Mac USB-" #~ "diskettedrev." #~ msgid "" #~ "Disk images are files containing the complete contents of a floppy disk " #~ "in raw form. Disk images, such as boot." #~ "img, cannot simply be copied to floppy drives. A special " #~ "program is used to write the image files to floppy disk in raw mode. This is required because these images are raw " #~ "representations of the disk; it is required to do a sector " #~ "copy of the data from the file onto the floppy." #~ msgstr "" #~ "Diskaftryk er filer, der indeholder hele indholdet af en diskette i " #~ " form. Diskaftryk, såsom boot.img, kan ikke bare kopieres til diskettedrev. Et speciel program " #~ "bruges til at skrive aftryksfilerne til diskettedrev i tilstand. Dette er krævet da disse aftryk er rå " #~ "repræsentationer af disken; det er krævet, at der udføres en " #~ "sektorkopiering af dataene fra filen til disketten." #~ msgid "" #~ "There are different techniques for creating floppies from disk images. " #~ "This section describes how to create floppies from disk images on " #~ "different platforms." #~ msgstr "" #~ "Der er forskellige teknikker for oprettelse af disketter fra diskaftryk. " #~ "Dette afsnit beskriver hvordan der oprettes disketter fra diskaftryk på " #~ "forskellige platforme." #~ msgid "" #~ "Before you can create the floppies, you will first need to download them " #~ "from one of the &debian; mirrors, as explained in . If you already have an " #~ "installation CD-ROM or DVD, the floppy images may also be included on the " #~ "CD/DVD." #~ msgstr "" #~ "Før du kan oprette disketterne, så skal du først hente dem fra en af " #~ "&debian;-spejlene, som forklaret i . " #~ "Hvis du allerede har en installations-cd-rom eller " #~ "dvd, så an disketteaftrykken også være inkluderet på cd'en eller dvd'en." #~ msgid "" #~ "No matter which method you use to create your floppies, you should " #~ "remember to flip the write-protect tab on the floppies once you have " #~ "written them, to ensure they are not damaged unintentionally." #~ msgstr "" #~ "Uanset hvilken metode du ønsker at bruge til at oprette disketterne med, " #~ "så bør du huske at indstille skrivebeskyttelsesknappen på disketterne, " #~ "når du har skrevet til dem, så de ikke uagtsomt bliver beskadiget." #~ msgid "Writing Disk Images From a Linux or Unix System" #~ msgstr "Skrivning af diskaftryk fra et Linux- eller Unix-system" #~ msgid "" #~ "To write the floppy disk image files to the floppy disks, you will " #~ "probably need root access to the system. Place a good, blank floppy in " #~ "the floppy drive. Next, use the command \n" #~ "$ dd if=filename of=/dev/fd0 bs=1024 " #~ "conv=sync ; sync\n" #~ " where filename is " #~ "one of the floppy disk image files. /dev/fd0 is a " #~ "commonly used name of the floppy disk device, it may be different on your " #~ "workstation (on Solaris, it is /dev/" #~ "fd/0). The command may return to the prompt before " #~ "Unix has finished writing the floppy disk, so look for the disk-in-use " #~ "light on the floppy drive and be sure that the light is out and the disk " #~ "has stopped revolving before you remove it from the drive. On some " #~ "systems, you'll have to run a command to eject the floppy from the drive " #~ " (on Solaris, use eject, see " #~ "the manual page)." #~ msgstr "" #~ "For at skrive disketteaftryksfiler til disketter, så skal du " #~ "sandsynligvis have administratoradgang til systemet. Placer en god, tom " #~ "diskette i diskettedrevet. Brug kommandoen \n" #~ "$ dd if=filename of=/dev/fd0 bs=1024 " #~ "conv=sync ; sync\n" #~ " hvor filnavn er et " #~ "af disketteaftryksfilerne. /dev/fd0 er et ofte " #~ "anvendt navn for diskettedrevet, det kan være anderledes på din " #~ "arbejdsstation (på Solaris, er det /dev/" #~ "fd/0). Kommandoen kan returnere til prompten før Unix " #~ "er færdig med at skrive til disketten, så kig efter lyset for disketten " #~ "er i brug på diskettedrevet og vær sikker på, at det er slukket og " #~ "disketten er stoppet med at rotere før du fjerner den fra drevet. På " #~ "nogle systemer, skal du køre en kommando for at skubbe disketten ud fra " #~ "drevet (på Solaris, brug eject, se manualsiden)." #~ msgid "" #~ "Some systems attempt to automatically mount a floppy disk when you place " #~ "it in the drive. You might have to disable this feature before the " #~ "workstation will allow you to write a floppy in raw mode. Unfortunately, how to accomplish this will vary based on your " #~ "operating system. On Solaris, you can work around " #~ "volume management to get raw access to the floppy. First, make sure that " #~ "the floppy is auto-mounted (using volcheck or the " #~ "equivalent command in the file manager). Then use a dd " #~ "command of the form given above, just replace /dev/fd0 with /vol/rdsk/floppy_name, where floppy_name is " #~ "the name the floppy disk was given when it was formatted (unnamed " #~ "floppies default to the name unnamed_floppy). On " #~ "other systems, ask your system administrator. " #~ msgstr "" #~ "Nogle systemer forsøger automatisk at montere et diskettedrev, når du " #~ "placerer den i drevet. Du skal måske deaktivere denne funktion, før " #~ "arbejdsstationen vil give dig rettighed til at skrive en diskette i " #~ "rå tilstand. Desværre vil metoden til at opnå dette " #~ "variere med dit operativsystem. På Solaris kan du " #~ "arbejde dig omkring diskenhedshåndtering for at få rå adgang til " #~ "disketten. Først skal du sikre dig, at disketten er automatisk monteret " #~ "(via volcheck eller den tilsvarende kommando i " #~ "filhåndteringen). Brug så kommandoen dd i formen " #~ "angivet ovenfor, bare erstat /dev/fd0 med /" #~ "vol/rdsk/diskettenavn, hvor " #~ "diskettenavn er navnet som disketten fik, da " #~ "den blev formateret (unavngivne disketter får navnet " #~ "unnamed_floppy). På andre systemer, skal du spørge " #~ "din systemadministrator. " #~ msgid "" #~ "If writing a floppy on powerpc Linux, you will need to eject it. The " #~ "eject program handles this nicely; you might need to " #~ "install it." #~ msgstr "" #~ "Hvis du skriver til en diskette på powerpc-linux, så skal du skubbe den " #~ "ud. Programmet eject håndterer dette pænt; du skal " #~ "måske installere det." #~ msgid "Writing Disk Images From DOS, Windows, or OS/2" #~ msgstr "Skrivning af diskaftryk fra DOS, Windwos eller OS/2" #~ msgid "" #~ "If you have access to an i386 or amd64 machine, you can use one of the " #~ "following programs to copy images to floppies." #~ msgstr "" #~ "Hvis du adgang til en i386- eller amd64-maskine, så kan du bruge en af de " #~ "følgende programmer til at kopiere aftryk til disketter." #~ msgid "" #~ "The rawrite1 and rawrite2 programs " #~ "can be used under MS-DOS. To use these programs, first make sure that you " #~ "are booted into DOS. Trying to use these programs from within a DOS box " #~ "in Windows, or double-clicking on these programs from the Windows " #~ "Explorer is not expected to work." #~ msgstr "" #~ "Programmerne rawrite1 og rawrite2 " #~ "kan bruges under MS-DOS. For at bruge disse programmer skal du først " #~ "sikre dig, at du er startet i DOS. At bruge disse programmer inden fra en " #~ "DOS-boks i Windows, eller dobbeltklik på disse programmer fra Windows " #~ "Explorer kan ikke forventes at fungere." #~ msgid "" #~ "The rwwrtwin program runs on Windows 95, NT, 98, 2000, " #~ "ME, XP and probably later versions. To use it you will need to unpack " #~ "diskio.dll in the same directory." #~ msgstr "" #~ "Programmet rwwrtwin kører på Windows 95, NT, 98, 2000, " #~ "ME, XP og sandsynligvis senere versioner. For at bruge programmet skal du " #~ "udpakke diskio.dll i den samme mappe." #~ msgid "" #~ "These tools can be found on the Official &debian; CD-ROMs under the " #~ "/tools directory." #~ msgstr "" #~ "Disse værktøjer kan findes på de officielle &debian;-cd-rom'er under " #~ "mappen /tools." #~ msgid "Writing Disk Images From MacOS" #~ msgstr "Skrivning af diskaftryk fra MacOS" #~ msgid "" #~ "An AppleScript, Make &debian; Floppy, is " #~ "available for burning floppies from the provided disk image files. It can " #~ "be downloaded from . To use it, " #~ "just unstuff it on your desktop, and then drag any floppy image file to " #~ "it. You must have Applescript installed and enabled in your extensions " #~ "manager. Disk Copy will ask you to confirm that you wish to erase the " #~ "floppy and proceed to write the file image to it." #~ msgstr "" #~ "Et Applescript, Make &debian; Floppy, er " #~ "tilgængelig for brænding af disketteaftryk fra de tilbudte " #~ "diskaftryksfiler. Det kan hentes fra . For " #~ "at bruge det, så »unstuff« det på dit skrivebord, og træk så " #~ "disketteaftryksfilen til det. Du skal have Applescript installeret og " #~ "aktiveret i din udvidelseshåndtering. Disk Copy vil bede dig om at " #~ "bekræfte, at du ønsker at slette disketten og fortsætte med at skrive " #~ "filaftrykket." #~ msgid "" #~ "You can also use the MacOS utility Disk Copy directly, " #~ "or the freeware utility suntar. The root." #~ "bin file is an example of a floppy image. Use one of the " #~ "following methods to create a floppy from the floppy image with these " #~ "utilities." #~ msgstr "" #~ "Du kan også bruge MacOS-redskabet Disk Copy direkte, " #~ "eller freeware-redskabet suntar. Filen root." #~ "bin er et eksempel på et disketteaftryk. Brug en af de " #~ "følgende metoder til at oprette en diskette fra disketteaftrykket med " #~ "disse redskaber." #~ msgid "Writing Disk Images with Disk Copy" #~ msgstr "Skrivning af diskaftryk med Disk Copy" #~ msgid "" #~ "If you are creating the floppy image from files which were originally on " #~ "the official &debian-gnu; CD, then the Type and Creator are already set " #~ "correctly. The following Creator-Changer steps are " #~ "only necessary if you downloaded the image files from a &debian; mirror." #~ msgstr "" #~ "Hvis du opretter diskaftrykket fra filer, som oprindelig befandt sig på " #~ "den officielle &debian-gnu;-cd, så er Type og Creator allerede angivet " #~ "korrekt. De følgende Creator-Changer-trin er kun " #~ "nødvendige hvis du hentede aftryksfilerne fra et &debian;-spejl." #~ msgid "" #~ "Obtain Creator-Changer and use it to open the root.bin file." #~ msgstr "" #~ "Hent Creator-Changer " #~ "og brug den til at åbne filen root.bin." #~ msgid "" #~ "Change the Creator to ddsk (Disk Copy), and the " #~ "Type to DDim (binary floppy image). The case is " #~ "sensitive for these fields." #~ msgstr "" #~ "Ændr Creator til ddsk (Disk Copy), og Type til " #~ "DDim (binært disketteaftryk). Der er forskel på " #~ "små og store bogstaver for disse felter." #~ msgid "" #~ "Important: In the Finder, use Get Info to display the Finder information about the floppy image, and " #~ "X the File Locked check box so that " #~ "MacOS will be unable to remove the boot blocks if the image is " #~ "accidentally mounted." #~ msgstr "" #~ "Vigtigt: I Finder, brug Get Info for at vise Finder-informationen om disketteaftrykket, og " #~ "afkryds X File Locked-" #~ "afkrydsningsboksen så at MacOS ikke kan fjerne opstartsblokken hvis " #~ "aftrykket ved en fejl monteres." #~ msgid "" #~ "Obtain Disk Copy; if you have a MacOS system or CD it " #~ "will very likely be there already, otherwise try ." #~ msgstr "" #~ "Hent Disk Copy; hvis du har et MacOS-system eller cd " #~ "så vil programmet højst sandsynlig allerede være installeret, ellers prøv " #~ "." #~ msgid "" #~ "Run Disk Copy, and select " #~ "Utilities Make a Floppy , then select the locked image file from " #~ "the resulting dialog. It will ask you to insert a floppy, then ask if you " #~ "really want to erase it. When done it should eject the floppy." #~ msgstr "" #~ "Kør Disk Copy, og vælg " #~ "Utilities Make a Floppy , vælg så den låste billedfil fra " #~ "resultatdialogen. Den vil bede dig om at indsætte en diskette og om du er " #~ "sikker på at du ønsker at slette den. Når færdig bør disketten blive " #~ "skubbet ud." #~ msgid "Writing Disk Images with suntar" #~ msgstr "Skrivning af diskaftryk med suntar" #~ msgid "" #~ "Obtain suntar from . Start the suntar program and select " #~ "Overwrite Sectors... from the Special menu." #~ msgstr "" #~ "Hent suntar fra . Start programmet suntar og vælg " #~ "Overskriv sektorer ... fra menuen Special." #~ msgid "" #~ "Insert the floppy disk as requested, then hit &enterkey; (start at sector " #~ "0)." #~ msgstr "" #~ "Indsæt diskettedisken som anmodt om og tryk på &enterkey; (start ved " #~ "sektor 0)." #~ msgid "" #~ "Select the root.bin file in the file-opening dialog." #~ msgstr "Vælg filen root.bin i filåbningsdialogen." #~ msgid "" #~ "After the floppy has been created successfully, select " #~ "File Eject . " #~ "If there are any errors writing the floppy, simply toss that floppy and " #~ "try another." #~ msgstr "" #~ "Efter disketten er blevet oprettet vælges Fil Skub ud . Hvis der " #~ "opstod fejl ved skrivning af disketten, så smid den ud og prøv på en " #~ "anden." #~ msgid "" #~ "Before using the floppy you created, set the write protect tab! Otherwise if you accidentally mount it in MacOS, MacOS will " #~ "helpfully ruin it." #~ msgstr "" #~ "Før du bruger disketten du oprettede, så husk at slå " #~ "skrivebeskyttelsen til! Ellers vil MacOS, hvis du ved en " #~ "fejltagelse monterer den, gøre disketten ubrugelig til sit formål." #~ msgid "Hard Disk Installer Booting for OldWorld Macs" #~ msgstr "Harddiskinstallation med opstart fra OldWorld Macs" #~ msgid "" #~ "The boot-floppy-hfs floppy uses miBoot to launch Linux installation, but miBoot cannot easily be used for hard disk booting. " #~ "BootX, launched from MacOS, supports booting " #~ "from files placed on the hard disk. BootX can " #~ "also be used to dual-boot MacOS and Linux after your &debian; " #~ "installation is complete. For the Performa 6360, it appears that " #~ "quik cannot make the hard disk bootable. So " #~ "BootX is required on that model." #~ msgstr "" #~ "Disketten boot-floppy-hfs bruger " #~ "miBoot til at starte Linux-installation, men " #~ "miBoot kan ikke nemt bruges for " #~ "harddiskopstart. BootX, startet fra MacOS, " #~ "understøtter opstart fra filer placeret på harddisken. " #~ "BootX kan også bruges til dual-boot af MacOS " #~ "og Linux efter din &debian;-installation er færdig. For Performa 6360 " #~ "virker det som om, at quik ikke kan gøre harddisken " #~ "opstartbar. Så BootX er krævet på den model." #~ msgid "" #~ "Download and unstuff the BootX distribution, " #~ "available from , or in the " #~ "dists/woody/main/disks-powerpc/current/powermac " #~ "directory on &debian; http/ftp mirrors and official &debian; CDs. Use " #~ "Stuffit Expander to extract it from its " #~ "archive. Within the package, there is an empty folder called " #~ "Linux Kernels. Download linux.bin and ramdisk.image.gz from the " #~ "disks-powerpc/current/powermac folder, and place " #~ "them in the Linux Kernels folder. Then place the " #~ "Linux Kernels folder in the active System Folder." #~ msgstr "" #~ "Hent og pak BootX-distributionen ud, som er " #~ "tilgængelig fra , eller i " #~ "mappen dists/woody/main/disks-powerpc/current/powermacpå &debian; http/ftp-spejl og officielle &debian;-cd'er. Brug " #~ "Stuffit Expander til at udtrække den fra dens " #~ "arkiv. Inden i pakken er der en tom mappe kaldt Linux Kernels. Hent linux.bin og ramdisk.image." #~ "gz fra mappen disks-powerpc/current/powermac og placer dem i mappen Linux Kernels. " #~ "Placer så mappen Linux Kernels i den aktive " #~ "systemmappe." #~ msgid "Hard Disk Installer Booting for NewWorld Macs" #~ msgstr "Harddiskinstallation med opstart fra NewWorld Macs" #~ msgid "" #~ "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, " #~ "as well as loading ELF binaries directly from the hard disk. These " #~ "machines will boot Linux directly via yaboot, which " #~ "supports loading a kernel and RAMdisk directly from an ext2 partition, as " #~ "well as dual-booting with MacOS. Hard disk booting of the installer is " #~ "particularly appropriate for newer machines without floppy drives. " #~ "BootX is not supported and must not be used on " #~ "NewWorld PowerMacs." #~ msgstr "" #~ "NewWorld PowerMacs understøtter opstart fra et netværk eller en ISO9660-" #~ "cd-rom, samt indlæsning af ELF's binære filer direkte fra harddisken. " #~ "Disse maskiner vil starte Linux direkte via yaboot, " #~ "som understøtter indlæsning af en kerne og RAMdisk direkte fra en ext2-" #~ "partition, samt som dual-booting med MacOS. Harddiskopstart af " #~ "installationsprogrammet er specielt passende for nyere maskiner uden " #~ "diskettedrev. BootX er ikke understøttet og må ikke " #~ "bruges på NewWorld PowerMacs." #~ msgid "" #~ "Copy (not move) the following four files which you " #~ "downloaded earlier from the &debian; archives, onto the root level of " #~ "your hard drive (this can be accomplished by option-" #~ "dragging each file to the hard drive icon)." #~ msgstr "" #~ "Kopier (flyt ikke) de følgende fire filer, som du " #~ "hentede fra &debian;-arkiverne, til rodniveauet for din harddisk (dette " #~ "kan opnås ved option-trækning af hver fil til " #~ "harddiskikonet)."