# SOME DESCRIPTIVE TITLE. # FIRST AUTHOR , YEAR. # 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-08-30 23:04+0000\n" "PO-Revision-Date: 2016-04-08 20:25+0000\n" "Last-Translator: NAME \n" "Language-Team: Norwegian nynorsk \n" "Language: nn\n" "MIME-Version: 1.0\n" "Content-Type: application/x-xml2pot; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #: install-methods.xml:5 #, no-c-format msgid "Obtaining System Installation Media" msgstr "" #. Tag: title #: install-methods.xml:12 #, no-c-format msgid "Official &debian-gnu; installation images" msgstr "" #. Tag: para #: install-methods.xml:13 #, 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." msgstr "" #. Tag: para #: install-methods.xml:30 #, 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 "" #. Tag: para #: install-methods.xml:38 #, 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 "" #. Tag: para #: install-methods.xml:46 #, 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." msgstr "" #. Tag: para #: install-methods.xml:67 #, 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 "" #. Tag: para #: install-methods.xml:72 #, 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 "" #. Tag: title #: install-methods.xml:96 #, no-c-format msgid "Downloading Files from &debian; Mirrors" msgstr "" #. Tag: para #: install-methods.xml:98 #, no-c-format msgid "" "To find the nearest (and thus probably the fastest) mirror, see the list of &debian; mirrors." msgstr "" #. Tag: title #: install-methods.xml:106 #, no-c-format msgid "Where to Find Installation Files" msgstr "" #. Tag: para #: install-methods.xml:108 #, 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 "" #. Tag: title #: install-methods.xml:120 #, no-c-format msgid "Kurobox Pro Installation Files" msgstr "" #. Tag: para #: install-methods.xml:121 #, 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 "" #. Tag: title #: install-methods.xml:131 #, no-c-format msgid "HP mv2120 Installation Files" msgstr "" #. Tag: para #: install-methods.xml:132 #, 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 "" #. Tag: title #: install-methods.xml:144 #, no-c-format msgid "QNAP Turbo Station Installation Files" msgstr "" #. Tag: para #: install-methods.xml:145 #, 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 "" #. Tag: title #: install-methods.xml:156 #, no-c-format msgid "Plug Computer and OpenRD Installation Files" msgstr "" #. Tag: para #: install-methods.xml:157 #, 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 "" #. Tag: title #: install-methods.xml:167 #, no-c-format msgid "LaCie NASes Installation Files" msgstr "" #. Tag: para #: install-methods.xml:168 #, 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 "" #. Tag: title #: install-methods.xml:179 #, no-c-format msgid "Armhf Multiplatform Installation Files" msgstr "" #. Tag: para #: install-methods.xml:180 #, 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 "" #. Tag: para #: install-methods.xml:192 #, no-c-format msgid "" "U-boot images for various armhf platforms are available at &armmp-uboot-img;." msgstr "" #. Tag: title #: install-methods.xml:238 #, no-c-format msgid "Preparing Files for USB Memory Stick Booting" msgstr "" #. Tag: para #: install-methods.xml:240 #, 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 "" #. Tag: para #: install-methods.xml:255 #, 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 "" #. Tag: title #: install-methods.xml:265 #, no-c-format msgid "Preparing a USB stick using a hybrid CD/DVD image" msgstr "" #. Tag: para #: install-methods.xml:266 #, 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." msgstr "" #. Tag: para #: install-methods.xml:276 #, 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" " Simply writing the installation image to USB " "like this should work fine for most users. For special needs there is this " "wiki " "page." msgstr "" #. Tag: para #: install-methods.xml:289 #, no-c-format msgid "" "Information about how to do this on other operating systems can be found in " "the Debian CD FAQ." msgstr "" #. Tag: para #: install-methods.xml:294 #, 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 "" #. Tag: title #: install-methods.xml:311 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "" #. Tag: para #: install-methods.xml:312 #, 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 "" #. Tag: para #: install-methods.xml:320 #, 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 "" #. Tag: title #: install-methods.xml:350 #, no-c-format msgid "Hard disk installer booting from Linux using GRUB" msgstr "" #. Tag: para #: install-methods.xml:352 #, no-c-format msgid "" "This section explains how to add to or even replace an existing linux " "installation using GRUB." msgstr "" #. Tag: para #: install-methods.xml:358 #, 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 "" #. Tag: para #: install-methods.xml:364 #, 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 "" #. Tag: para #: install-methods.xml:371 #, no-c-format msgid "vmlinuz (kernel binary)" msgstr "" #. Tag: para #: install-methods.xml:376 #, no-c-format msgid "initrd.gz (ramdisk image)" msgstr "" #. Tag: para #: install-methods.xml:383 #, 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 "" #. Tag: para #: install-methods.xml:392 #, 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 "" #. Tag: para #: install-methods.xml:400 #, no-c-format msgid "" "Finally, to configure the bootloader proceed to ." msgstr "" #. Tag: title #: install-methods.xml:415 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "" #. Tag: para #: install-methods.xml:416 #, 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 "" #. Tag: para #: install-methods.xml:424 #, 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 "" #. Tag: para #: install-methods.xml:431 #, 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 "" #. Tag: para #: install-methods.xml:457 #, 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 "" #. Tag: para #: install-methods.xml:465 #, 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 "" #. Tag: title #: install-methods.xml:481 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para #: install-methods.xml:482 #, 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 "" #. Tag: para #: install-methods.xml:491 #, 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 "" #. Tag: title #: install-methods.xml:512 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para #: install-methods.xml:513 #, 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 "" #. Tag: screen #: install-methods.xml:520 #, 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 "" #. Tag: para #: install-methods.xml:522 #, 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 "" #. Tag: para #: install-methods.xml:532 #, no-c-format msgid "" "After you have edited the dhcpd configuration file, " "restart it with /etc/init.d/isc-dhcp-server restart." msgstr "" #. Tag: title #: install-methods.xml:540 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para #: install-methods.xml:541 #, 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 "" #. Tag: para #: install-methods.xml:551 #, 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 "" #. Tag: screen #: install-methods.xml:555 #, 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 "" #. Tag: title #: install-methods.xml:568 #, no-c-format msgid "Setting up a BOOTP server" msgstr "" #. Tag: para #: install-methods.xml:569 #, 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 "" #. Tag: para #: install-methods.xml:577 #, 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 "" #. Tag: para #: install-methods.xml:604 #, 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 "" #. Tag: title #: install-methods.xml:623 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para #: install-methods.xml:624 #, no-c-format msgid "" "To get the TFTP server ready to go, you should first make sure that " "tftpd is enabled." msgstr "" #. Tag: para #: install-methods.xml:629 #, 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 "" #. Tag: para #: install-methods.xml:638 #, 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 "" #. Tag: para #: install-methods.xml:648 #, 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 "" #. Tag: title #: install-methods.xml:660 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para #: install-methods.xml:661 #, 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 "" #. Tag: para #: install-methods.xml:712 #, 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 "" #. Tag: title #: install-methods.xml:731 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para #: install-methods.xml:732 #, 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 (have a look at the " "FAI home page for detailed " "information) and the &debian; Installer itself." msgstr "" #. Tag: title #: install-methods.xml:744 #, no-c-format msgid "Automatic Installation Using the &debian; Installer" msgstr "" #. Tag: para #: install-methods.xml:745 #, 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 "" #. Tag: para #: install-methods.xml:752 #, no-c-format msgid "" "Full documentation on preseeding including a working example that you can " "edit is in ." msgstr "" #. Tag: title #: install-methods.xml:766 #, no-c-format msgid "Verifying the integrity of installation files" msgstr "" #. Tag: para #: install-methods.xml:768 #, 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 "" #. Tag: para #: install-methods.xml:779 #, no-c-format msgid "" "checksum files for CD images," msgstr "" #. Tag: para #: install-methods.xml:785 #, no-c-format msgid "" "checksum files for DVD images," msgstr "" #. Tag: para #: install-methods.xml:791 #, no-c-format msgid "" "checksum files for BD images," msgstr "" #. Tag: para #: install-methods.xml:797 #, no-c-format msgid "" "checksum files for other " "installation files." msgstr "" #. Tag: para #: install-methods.xml:805 #, 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 "" #. Tag: para #: install-methods.xml:818 #, 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 ""