Update of POT and PO files for the manual

4 files changed, 1686 insertions, 496 deletions

diff --git a/po/sv/administrivia.po b/po/sv/administrivia.po
index 666889295..8e7632dcd 100755
--- a/po/sv/administrivia.po
+++ b/po/sv/administrivia.po
@@ -10,7 +10,7 @@ msgstr ""
 "Last-Translator: Daniel Nylander <po@danielnylander.se>\n"
 "Language-Team: Swedish <sv@li.org>\n"
 "MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=iso-8859-1\n"
+"Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
 #. Tag: title
@@ -28,19 +28,36 @@ msgstr "Om detta dokument"
 #. Tag: para
 #: administrivia.xml:11
 #, no-c-format
-msgid "This manual was created for Sarge's debian-installer, based on the Woody installation manual for boot-floppies, which was based on earlier Debian installation manuals, and on the Progeny distribution manual which was released under GPL in 2003."
-msgstr "Denna manual skapades för Sarges debian-installer och baserades på installationsmanualen för Woody för uppstartsdisketter som var baserad på tidigare installationsmanualer för Debian och på Progeny-utgåvans manual som utgavs under GPL år 2003."
+msgid ""
+"This manual was created for Sarge's debian-installer, based on the Woody "
+"installation manual for boot-floppies, which was based on earlier Debian "
+"installation manuals, and on the Progeny distribution manual which was "
+"released under GPL in 2003."
+msgstr ""
+"Denna manual skapades för Sarges debian-installer och baserades på "
+"installationsmanualen för Woody för uppstartsdisketter som var baserad på "
+"tidigare installationsmanualer för Debian och på Progeny-utgåvans manual som "
+"utgavs under GPL år 2003."
 
 #. Tag: para
 #: administrivia.xml:18
 #, no-c-format
-msgid "This document is written in DocBook XML. Output formats are generated by various programs using information from the <classname>docbook-xml</classname> and <classname>docbook-xsl</classname> packages."
+msgid ""
+"This document is written in DocBook XML. Output formats are generated by "
+"various programs using information from the <classname>docbook-xml</"
+"classname> and <classname>docbook-xsl</classname> packages."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:25
 #, no-c-format
-msgid "In order to increase the maintainability of this document, we use a number of XML features, such as entities and profiling attributes. These play a role akin to variables and conditionals in programming languages. The XML source to this document contains information for each different architecture &mdash; profiling attributes are used to isolate certain bits of text as architecture-specific."
+msgid ""
+"In order to increase the maintainability of this document, we use a number "
+"of XML features, such as entities and profiling attributes. These play a "
+"role akin to variables and conditionals in programming languages. The XML "
+"source to this document contains information for each different architecture "
+"&mdash; profiling attributes are used to isolate certain bits of text as "
+"architecture-specific."
 msgstr ""
 
 #. Tag: title
@@ -52,19 +69,46 @@ msgstr "Bidrag till detta dokument"
 #. Tag: para
 #: administrivia.xml:54
 #, no-c-format
-msgid "If you have problems or suggestions regarding this document, you should probably submit them as a bug report against the package <classname>debian-installer-manual</classname>. See the <classname>reportbug</classname> package or read the online documentation of the <ulink url=\"&url-bts;\">Debian Bug Tracking System</ulink>. It would be nice if you could check the <ulink url=\"&url-bts;debian-installer-manual\">open bugs against debian-installer-manual</ulink> to see whether your problem has already been reported. If so, you can supply additional corroboration or helpful information to <email><replaceable>XXXX</replaceable>@bugs.debian.org</email>, where <replaceable>XXXX</replaceable> is the number for the already-reported bug."
+msgid ""
+"If you have problems or suggestions regarding this document, you should "
+"probably submit them as a bug report against the package <classname>debian-"
+"installer-manual</classname>. See the <classname>reportbug</classname> "
+"package or read the online documentation of the <ulink url=\"&url-bts;"
+"\">Debian Bug Tracking System</ulink>. It would be nice if you could check "
+"the <ulink url=\"&url-bts;debian-installer-manual\">open bugs against debian-"
+"installer-manual</ulink> to see whether your problem has already been "
+"reported. If so, you can supply additional corroboration or helpful "
+"information to <email><replaceable>XXXX</replaceable>@bugs.debian.org</"
+"email>, where <replaceable>XXXX</replaceable> is the number for the already-"
+"reported bug."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:70
 #, no-c-format
-msgid "Better yet, get a copy of the DocBook source for this document, and produce patches against it. The DocBook source can be found at the <ulink url=\"&url-d-i-websvn;\">debian-installer WebSVN</ulink>. If you're not familiar with DocBook, don't worry: there is a simple cheatsheet in the manuals directory that will get you started. It's like html, but oriented towards the meaning of the text rather than the presentation. Patches submitted to the debian-boot mailing list (see below) are welcomed. For instructions on how to check out the sources via SVN, see <ulink url=\"&url-d-i-readme;\">README</ulink> from the source root directory."
+msgid ""
+"Better yet, get a copy of the DocBook source for this document, and produce "
+"patches against it. The DocBook source can be found at the <ulink url=\"&url-"
+"d-i-websvn;\">debian-installer WebSVN</ulink>. If you're not familiar with "
+"DocBook, don't worry: there is a simple cheatsheet in the manuals directory "
+"that will get you started. It's like html, but oriented towards the meaning "
+"of the text rather than the presentation. Patches submitted to the debian-"
+"boot mailing list (see below) are welcomed. For instructions on how to check "
+"out the sources via SVN, see <ulink url=\"&url-d-i-readme;\">README</ulink> "
+"from the source root directory."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:84
 #, no-c-format
-msgid "Please do <emphasis>not</emphasis> contact the authors of this document directly. There is also a discussion list for &d-i;, which includes discussions of this manual. The mailing list is <email>debian-boot@lists.debian.org</email>. Instructions for subscribing to this list can be found at the <ulink url=\"&url-debian-lists-subscribe;\">Debian Mailing List Subscription</ulink> page; or you can browse the <ulink url=\"&url-debian-list-archives;\">Debian Mailing List Archives</ulink> online."
+msgid ""
+"Please do <emphasis>not</emphasis> contact the authors of this document "
+"directly. There is also a discussion list for &d-i;, which includes "
+"discussions of this manual. The mailing list is <email>debian-boot@lists."
+"debian.org</email>. Instructions for subscribing to this list can be found "
+"at the <ulink url=\"&url-debian-lists-subscribe;\">Debian Mailing List "
+"Subscription</ulink> page; or you can browse the <ulink url=\"&url-debian-"
+"list-archives;\">Debian Mailing List Archives</ulink> online."
 msgstr ""
 
 #. Tag: title
@@ -75,27 +119,65 @@ msgstr "Stora bidragare"
 
 #. Tag: para
 #: administrivia.xml:103
-#, no-c-format
-msgid "This document was originally written by Bruce Perens, Sven Rudolph, Igor Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the Installation Howto. Many, many Debian users and developers contributed to this document. Particular note must be made of Michael Schmitz (m68k support), Frank Neumann (original author of the <ulink url=\"&url-m68k-old-amiga-install;\">Amiga install manual</ulink>), Arto Astala, Eric Delaunay/Ben Collins (SPARC information), Tapio Lehtonen, and Stéphane Bortzmeyer for numerous edits and text. We have to thank Pascal Le Bail for useful information about booting from USB memory sticks. Miroslav Kuře has documented a lot of the new functionality in Sarge's debian-installer."
-msgstr "Detta dokument blev från början skrivet av Bruce Perens, Sven Rudolph, Igor Grobman, James Treacy och Adam Di Carlo. Sebastian Ley skrev Installations Howto. Många, många Debian-användare och utvecklare har bidragit till detta dokument. Speciellt tack måste ges till Michael Schmitz (m68k-stöd), Frank Neumann (originalförfattare av <ulink url=\"&url-m68k-old-amiga-install;\">installationsmanualen för Amiga</ulink>), Arto Astala, Eric Delaunay/Ben Collins (SPARC-information), Tapio Lehtonen och Stephane Bortzmeyer för ett flertal redigeringar och text. Vi måste tacka Pascal Le Bail för användbar information om uppstart från USB-minnen. Miroslav Kure har dokumenterat en hel del av den nya funktionaliteten i Sarges debian-installer."
+#, fuzzy, no-c-format
+msgid ""
+"This document was originally written by Bruce Perens, Sven Rudolph, Igor "
+"Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the "
+"Installation Howto. Many, many Debian users and developers contributed to "
+"this document. Particular note must be made of Michael Schmitz (m68k "
+"support), Frank Neumann (original author of the <ulink url=\"&url-m68k-old-"
+"amiga-install;\">Amiga install manual</ulink>), Arto Astala, Eric Delaunay/"
+"Ben Collins (SPARC information), Tapio Lehtonen, and Stéphane Bortzmeyer for "
+"numerous edits and text. We have to thank Pascal Le Bail for useful "
+"information about booting from USB memory sticks. Miroslav Kuře has "
+"documented a lot of the new functionality in Sarge's debian-installer."
+msgstr ""
+"Detta dokument blev från början skrivet av Bruce Perens, Sven Rudolph, Igor "
+"Grobman, James Treacy och Adam Di Carlo. Sebastian Ley skrev Installations "
+"Howto. Många, många Debian-användare och utvecklare har bidragit till detta "
+"dokument. Speciellt tack måste ges till Michael Schmitz (m68k-stöd), Frank "
+"Neumann (originalförfattare av <ulink url=\"&url-m68k-old-amiga-install;"
+"\">installationsmanualen för Amiga</ulink>), Arto Astala, Eric Delaunay/Ben "
+"Collins (SPARC-information), Tapio Lehtonen och Stephane Bortzmeyer för ett "
+"flertal redigeringar och text. Vi måste tacka Pascal Le Bail för användbar "
+"information om uppstart från USB-minnen. Miroslav Kure har dokumenterat en "
+"hel del av den nya funktionaliteten i Sarges debian-installer."
 
 #. Tag: para
 #: administrivia.xml:118
 #, no-c-format
-msgid "Extremely helpful text and information was found in Jim Mintha's HOWTO for network booting (no URL available), the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>, the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink>, the <ulink url=\"&url-alpha-faq;\">Linux/Alpha FAQ</ulink>, amongst others. The maintainers of these freely available and rich sources of information must be recognized."
+msgid ""
+"Extremely helpful text and information was found in Jim Mintha's HOWTO for "
+"network booting (no URL available), the <ulink url=\"&url-debian-faq;"
+"\">Debian FAQ</ulink>, the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</"
+"ulink>, the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors "
+"FAQ</ulink>, the <ulink url=\"&url-alpha-faq;\">Linux/Alpha FAQ</ulink>, "
+"amongst others. The maintainers of these freely available and rich sources "
+"of information must be recognized."
 msgstr ""
 
 #. Tag: para
 #: administrivia.xml:130
 #, no-c-format
-msgid "The section on chrooted installations in this manual (<xref linkend=\"linux-upgrade\"/>) was derived in part from documents copyright Karsten M. Self."
-msgstr "Sektionen om chrootade installationer i denna manual (<xref linkend=\"linux-upgrade\"/>) blev framtagen ur delar från dokument som är copyright Karsten M. Self."
+msgid ""
+"The section on chrooted installations in this manual (<xref linkend=\"linux-"
+"upgrade\"/>) was derived in part from documents copyright Karsten M. Self."
+msgstr ""
+"Sektionen om chrootade installationer i denna manual (<xref linkend=\"linux-"
+"upgrade\"/>) blev framtagen ur delar från dokument som är copyright Karsten "
+"M. Self."
 
 #. Tag: para
 #: administrivia.xml:136
 #, no-c-format
-msgid "The section on installations over plip in this manual (<xref linkend=\"plip\"/>) was based on the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> by Gilles Lamiral."
-msgstr "Sektionen för installationer över plip i denna manual (<xref linkend=\"plip\"/>) var baserade på <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> av Gilles Lamiral."
+msgid ""
+"The section on installations over plip in this manual (<xref linkend=\"plip"
+"\"/>) was based on the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-"
+"HOWTO</ulink> by Gilles Lamiral."
+msgstr ""
+"Sektionen för installationer över plip i denna manual (<xref linkend=\"plip"
+"\"/>) var baserade på <ulink url=\"&url-plip-install-howto;\">PLIP-Install-"
+"HOWTO</ulink> av Gilles Lamiral."
 
 #. Tag: title
 #: administrivia.xml:147
@@ -108,4 +190,3 @@ msgstr ""
 #, no-c-format
 msgid "All trademarks are property of their respective trademark owners."
 msgstr ""
-
diff --git a/po/sv/install-methods.po b/po/sv/install-methods.po
index 2def52be3..d2cd23974 100755
--- a/po/sv/install-methods.po
+++ b/po/sv/install-methods.po
@@ -10,43 +10,74 @@ msgstr ""
 "Last-Translator: Daniel Nylander <po@danielnylander.se>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
 "MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=iso-8859-1\n"
+"Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
 #. Tag: title
 #: install-methods.xml:5
 #, fuzzy, no-c-format
 msgid "Obtaining System Installation Media"
-msgstr "Installationsfel för grundsystemet"
+msgstr "Installationsfel för grundsystemet"
 
 #. Tag: title
 #: install-methods.xml:12
 #, fuzzy, no-c-format
 msgid "Official &debian; CD-ROM Sets"
-msgstr "Inte en giltig cd-skiva för Debian"
+msgstr "Inte en giltig cd-skiva för Debian"
 
 #. Tag: para
 #: install-methods.xml:13
 #, no-c-format
-msgid "By far the easiest way to install &debian; is from an Official Debian CD-ROM Set. You can buy a set from a vendor (see the <ulink url=\"&url-debian-cd-vendors;\">CD vendors page</ulink>). You may also download the CD-ROM images from a Debian mirror and make your own set, if you have a fast network connection and a CD burner (see the <ulink url=\"&url-debian-cd;\">Debian CD page</ulink> for detailed instructions). If you have a Debian CD set and CDs are bootable on your machine, you can skip right to <xref linkend=\"boot-installer\"/>; much effort has been expended to ensure the files most people need are there on the CD. Although a full set of binary packages requires several CDs, it is unlikely you will need packages on the third CD and above. You may also consider using the DVD version, which saves a lot of space on your shelf and you avoid the CD shuffling marathon."
+msgid ""
+"By far the easiest way to install &debian; is from an Official Debian CD-ROM "
+"Set. You can buy a set from a vendor (see the <ulink url=\"&url-debian-cd-"
+"vendors;\">CD vendors page</ulink>). You may also download the CD-ROM images "
+"from a Debian mirror and make your own set, if you have a fast network "
+"connection and a CD burner (see the <ulink url=\"&url-debian-cd;\">Debian CD "
+"page</ulink> for detailed instructions). If you have a Debian CD set and CDs "
+"are bootable on your machine, you can skip right to <xref linkend=\"boot-"
+"installer\"/>; much effort has been expended to ensure the files most people "
+"need are there on the CD. Although a full set of binary packages requires "
+"several CDs, it is unlikely you will need packages on the third CD and "
+"above. You may also consider using the DVD version, which saves a lot of "
+"space on your shelf and you avoid the CD shuffling marathon."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:30
 #, no-c-format
-msgid "If your machine doesn't support CD booting, but you do have a CD set, you can use an alternative strategy such as <phrase condition=\"supports-floppy-boot\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net boot,</phrase> or manually loading the kernel from the CD to initially boot the system installer. The files you need for booting by another means are also on the CD; the Debian network archive and CD folder organization 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 CD."
+msgid ""
+"If your machine doesn't support CD booting, but you do have a CD set, you "
+"can use an alternative strategy such as <phrase condition=\"supports-floppy-"
+"boot\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</"
+"phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase "
+"condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-"
+"tftp\">net boot,</phrase> or manually loading the kernel from the CD to "
+"initially boot the system installer. The files you need for booting by "
+"another means are also on the CD; the Debian network archive and CD folder "
+"organization 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 CD."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:52
 #, no-c-format
-msgid "Once the installer is booted, it will be able to obtain all the other files it needs from the CD."
+msgid ""
+"Once the installer is booted, it will be able to obtain all the other files "
+"it needs from the CD."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:57
 #, no-c-format
-msgid "If you don't have a CD set, then you will need to download the installer system files and place them on the <phrase arch=\"s390\">installation tape</phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> <phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition=\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a connected computer</phrase> so they can be used to boot the installer."
+msgid ""
+"If you don't have a CD set, then you will need to download the installer "
+"system files and place them on the <phrase arch=\"s390\">installation tape</"
+"phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> "
+"<phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition="
+"\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a "
+"connected computer</phrase> so they can be used to boot the installer."
 msgstr ""
 
 #. Tag: title
@@ -58,13 +89,17 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:85
 #, no-c-format
-msgid "To find the nearest (and thus probably the fastest) mirror, see the <ulink url=\"&url-debian-mirrors;\">list of Debian mirrors</ulink>."
+msgid ""
+"To find the nearest (and thus probably the fastest) mirror, see the <ulink "
+"url=\"&url-debian-mirrors;\">list of Debian mirrors</ulink>."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:90
 #, no-c-format
-msgid "When downloading files from a Debian mirror, be sure to download the files in <emphasis>binary</emphasis> mode, not text or automatic mode."
+msgid ""
+"When downloading files from a Debian mirror, be sure to download the files "
+"in <emphasis>binary</emphasis> mode, not text or automatic mode."
 msgstr ""
 
 #. Tag: title
@@ -76,85 +111,124 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:101
 #, no-c-format
-msgid "The installation images are located on each Debian mirror in the directory <ulink url=\"&url-debian-installer;/images\">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> &mdash; the <ulink url=\"&url-debian-installer;/images/MANIFEST\">MANIFEST</ulink> lists each image and its purpose."
+msgid ""
+"The installation images are located on each Debian mirror in the directory "
+"<ulink url=\"&url-debian-installer;/images\">debian/dists/&releasename;/main/"
+"installer-&architecture;/current/images/</ulink> &mdash; the <ulink url="
+"\"&url-debian-installer;/images/MANIFEST\">MANIFEST</ulink> lists each image "
+"and its purpose."
 msgstr ""
 
 #. Tag: title
 #: install-methods.xml:113
 #, fuzzy, no-c-format
 msgid "Alpha Installation Files"
-msgstr "/tmp - temporära filer"
+msgstr "/tmp - temporära filer"
 
 #. Tag: para
 #: install-methods.xml:114
 #, no-c-format
-msgid "If you choose to boot from ARC console firmware using <command>MILO</command>, you will also need to prepare a disk containing <command>MILO</command> and <command>LINLOAD.EXE</command> from the provided disk images. See <xref linkend=\"alpha-firmware\"/> for more information on Alpha firmware and boot loaders. The floppy images can be found in the <filename>MILO</filename> directory as <filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>."
+msgid ""
+"If you choose to boot from ARC console firmware using <command>MILO</"
+"command>, you will also need to prepare a disk containing <command>MILO</"
+"command> and <command>LINLOAD.EXE</command> from the provided disk images. "
+"See <xref linkend=\"alpha-firmware\"/> for more information on Alpha "
+"firmware and boot loaders. The floppy images can be found in the "
+"<filename>MILO</filename> directory as "
+"<filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:125
 #, no-c-format
-msgid "Unfortunately, these <command>MILO</command> images could not be tested and might not work for all subarchitectures. If you find it doesn't work for you, try copying the appropriate <command>MILO</command> binary onto the floppy (<ulink url=\"&disturlftp;main/disks-alpha/current/MILO/\"></ulink>). Note that those <command>MILO</command>s don't support ext2 <quote>sparse superblocks</quote>, so you can't use them to load kernels from newly generated ext2 file systems. As a workaround, you can put your kernel onto the FAT partition next to the <command>MILO</command>."
+msgid ""
+"Unfortunately, these <command>MILO</command> images could not be tested and "
+"might not work for all subarchitectures. If you find it doesn't work for "
+"you, try copying the appropriate <command>MILO</command> binary onto the "
+"floppy (<ulink url=\"&disturlftp;main/disks-alpha/current/MILO/\"></ulink>). "
+"Note that those <command>MILO</command>s don't support ext2 <quote>sparse "
+"superblocks</quote>, so you can't use them to load kernels from newly "
+"generated ext2 file systems. As a workaround, you can put your kernel onto "
+"the FAT partition next to the <command>MILO</command>."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:137
 #, no-c-format
-msgid "<command>MILO</command> binaries are platform-specific. See <xref linkend=\"alpha-cpus\"/> to determine the appropriate <command>MILO</command> image for your Alpha platform."
+msgid ""
+"<command>MILO</command> binaries are platform-specific. See <xref linkend="
+"\"alpha-cpus\"/> to determine the appropriate <command>MILO</command> image "
+"for your Alpha platform."
 msgstr ""
 
 #. Tag: title
 #: install-methods.xml:152
 #, fuzzy, no-c-format
 msgid "RiscPC Installation Files"
-msgstr "/tmp - temporära filer"
+msgstr "/tmp - temporära filer"
 
 #. Tag: para
 #: install-methods.xml:153
 #, no-c-format
-msgid "The RiscPC installer is booted initially from RISC OS. All the necessary files are provided in one Zip archive, &rpc-install-kit;. Download this file onto the RISC OS machine, copy the <filename>linloader.!Boot</filename> components into place, and run <filename>!dInstall</filename>."
+msgid ""
+"The RiscPC installer is booted initially from RISC OS. All the necessary "
+"files are provided in one Zip archive, &rpc-install-kit;. Download this file "
+"onto the RISC OS machine, copy the <filename>linloader.!Boot</filename> "
+"components into place, and run <filename>!dInstall</filename>."
 msgstr ""
 
 #. Tag: title
 #: install-methods.xml:165
 #, fuzzy, no-c-format
 msgid "NetWinder Installation Files"
-msgstr "/tmp - temporära filer"
+msgstr "/tmp - temporära filer"
 
 #. Tag: para
 #: install-methods.xml:166
 #, no-c-format
-msgid "The easiest way to boot a NetWinder is over the network, using the supplied TFTP image &netwinder-boot-img;."
+msgid ""
+"The easiest way to boot a NetWinder is over the network, using the supplied "
+"TFTP image &netwinder-boot-img;."
 msgstr ""
 
 #. Tag: title
 #: install-methods.xml:175
 #, fuzzy, no-c-format
 msgid "CATS Installation Files"
-msgstr "/tmp - temporära filer"
+msgstr "/tmp - temporära filer"
 
 #. Tag: para
 #: install-methods.xml:176
 #, no-c-format
-msgid "The only supported boot method for CATS is to use the combined image &cats-boot-img;. This can be loaded from any device accessible to the Cyclone bootloader."
+msgid ""
+"The only supported boot method for CATS is to use the combined image &cats-"
+"boot-img;. This can be loaded from any device accessible to the Cyclone "
+"bootloader."
 msgstr ""
 
 #. Tag: title
 #: install-methods.xml:221
 #, no-c-format
 msgid "Choosing a Kernel"
-msgstr "Välja en kärna"
+msgstr "Välja en kärna"
 
 #. Tag: para
 #: install-methods.xml:223
 #, no-c-format
-msgid "Some m68k subarchs have a choice of kernels to install. In general we recommend trying the most recent version first. If your subarch or machine needs to use a 2.2.x kernel, make sure you choose one of the images that supports 2.2.x kernels (see the <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink>)."
+msgid ""
+"Some m68k subarchs have a choice of kernels to install. In general we "
+"recommend trying the most recent version first. If your subarch or machine "
+"needs to use a 2.2.x kernel, make sure you choose one of the images that "
+"supports 2.2.x kernels (see the <ulink url=\"&disturl;/main/installer-"
+"&architecture;/current/images/MANIFEST\">MANIFEST</ulink>)."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:232
 #, no-c-format
-msgid "All of the m68k images for use with 2.2.x kernels, require the kernel parameter &ramdisksize;."
+msgid ""
+"All of the m68k images for use with 2.2.x kernels, require the kernel "
+"parameter &ramdisksize;."
 msgstr ""
 
 #. Tag: title
@@ -166,7 +240,15 @@ msgstr "Skapar enhetsfiler..."
 #. Tag: para
 #: install-methods.xml:252
 #, no-c-format
-msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>,"
+msgid ""
+"If you can't boot (IPL) from the CD-ROM and you are not using VM you need to "
+"create an IPL tape first. This is described in section 3.4.3 in the <ulink "
+"url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux "
+"for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files "
+"you need to write to the tape are (in this order): <filename>kernel.debian</"
+"filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</"
+"filename>. The files can be downloaded from the <filename>tape</filename> "
+"sub-directory, see <xref linkend=\"where-files\"/>,"
 msgstr ""
 
 #. Tag: title
@@ -178,7 +260,9 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:277
 #, no-c-format
-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."
+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 ""
 
 #. Tag: para
@@ -196,19 +280,32 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:291
 #, no-c-format
-msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy."
+msgid ""
+"Disk images are files containing the complete contents of a floppy disk in "
+"<emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</"
+"filename>, cannot simply be copied to floppy drives. A special program is "
+"used to write the image files to floppy disk in <emphasis>raw</emphasis> "
+"mode. This is required because these images are raw representations of the "
+"disk; it is required to do a <emphasis>sector copy</emphasis> of the data "
+"from the file onto the floppy."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:302
 #, no-c-format
-msgid "There are different techniques for creating floppies from disk images, which depend on your platform. This section describes how to create floppies from disk images on different platforms."
+msgid ""
+"There are different techniques for creating floppies from disk images, which "
+"depend on your platform. This section describes how to create floppies from "
+"disk images on different platforms."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:308
 #, no-c-format
-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."
+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 ""
 
 #. Tag: title
@@ -221,21 +318,52 @@ msgstr ""
 #: install-methods.xml:317
 #, no-c-format
 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 <informalexample><screen>\n"
-"$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync\n"
-"</screen></informalexample> where <replaceable>filename</replaceable> is one of the floppy disk image files (see <xref linkend=\"downloading-files\"/> for what <replaceable>filename</replaceable> should be). <filename>/dev/fd0</filename> is a commonly used name of the floppy disk device, it may be different on your workstation <phrase arch=\"sparc\">(on Solaris, it is <filename>/dev/fd/0</filename>)</phrase>. 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 <phrase arch=\"sparc\">(on Solaris, use <command>eject</command>, see the manual page)</phrase>."
+"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 <informalexample><screen>\n"
+"$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; "
+"sync\n"
+"</screen></informalexample> where <replaceable>filename</replaceable> is one "
+"of the floppy disk image files (see <xref linkend=\"downloading-files\"/> "
+"for what <replaceable>filename</replaceable> should be). <filename>/dev/fd0</"
+"filename> is a commonly used name of the floppy disk device, it may be "
+"different on your workstation <phrase arch=\"sparc\">(on Solaris, it is "
+"<filename>/dev/fd/0</filename>)</phrase>. 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 "
+"<phrase arch=\"sparc\">(on Solaris, use <command>eject</command>, see the "
+"manual page)</phrase>."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:341
 #, no-c-format
-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 <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> 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 <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>"
+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 <emphasis>raw mode</emphasis>. "
+"Unfortunately, how to accomplish this will vary based on your operating "
+"system. <phrase arch=\"sparc\"> 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 <command>volcheck</command> or the equivalent command "
+"in the file manager). Then use a <command>dd</command> command of the form "
+"given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/"
+"rdsk/<replaceable>floppy_name</replaceable></filename>, where "
+"<replaceable>floppy_name</replaceable> is the name the floppy disk was given "
+"when it was formatted (unnamed floppies default to the name "
+"<filename>unnamed_floppy</filename>). On other systems, ask your system "
+"administrator. </phrase>"
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:362
 #, no-c-format
-msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it."
+msgid ""
+"If writing a floppy on powerpc Linux, you will need to eject it. The "
+"<command>eject</command> program handles this nicely; you might need to "
+"install it."
 msgstr ""
 
 #. Tag: title
@@ -247,25 +375,37 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:382
 #, no-c-format
-msgid "If you have access to an i386 machine, you can use one of the following programs to copy images to floppies."
+msgid ""
+"If you have access to an i386 machine, you can use one of the following "
+"programs to copy images to floppies."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:387
 #, no-c-format
-msgid "The <command>rawrite1</command> and <command>rawrite2</command> 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 <emphasis>not</emphasis> expected to work."
+msgid ""
+"The <command>rawrite1</command> and <command>rawrite2</command> 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 "
+"<emphasis>not</emphasis> expected to work."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:395
 #, no-c-format
-msgid "The <command>rwwrtwin</command> 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."
+msgid ""
+"The <command>rwwrtwin</command> 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 ""
 
 #. Tag: para
 #: install-methods.xml:401
 #, no-c-format
-msgid "These tools can be found on the Official Debian CD-ROMs under the <filename>/tools</filename> directory."
+msgid ""
+"These tools can be found on the Official Debian CD-ROMs under the <filename>/"
+"tools</filename> directory."
 msgstr ""
 
 #. Tag: title
@@ -277,7 +417,11 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:415
 #, no-c-format
-msgid "You'll find the &rawwrite.ttp; program in the same directory as the floppy disk images. Start the program by double clicking on the program icon, and type in the name of the floppy image file you want written to the floppy at the TOS program command line dialog box."
+msgid ""
+"You'll find the &rawwrite.ttp; program in the same directory as the floppy "
+"disk images. Start the program by double clicking on the program icon, and "
+"type in the name of the floppy image file you want written to the floppy at "
+"the TOS program command line dialog box."
 msgstr ""
 
 #. Tag: title
@@ -289,7 +433,12 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:427
 #, no-c-format
-msgid "There is no MacOS application to write images to floppy disks (and there would be no point in doing this as you can't use these floppies to boot the installation system or install kernel and modules from on Macintosh). However, these files are needed for the installation of the operating system and modules, later in the process."
+msgid ""
+"There is no MacOS application to write images to floppy disks (and there "
+"would be no point in doing this as you can't use these floppies to boot the "
+"installation system or install kernel and modules from on Macintosh). "
+"However, these files are needed for the installation of the operating system "
+"and modules, later in the process."
 msgstr ""
 
 #. Tag: title
@@ -301,13 +450,25 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:446
 #, no-c-format
-msgid "An AppleScript, <application>Make Debian Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. 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."
+msgid ""
+"An AppleScript, <application>Make Debian Floppy</application>, is available "
+"for burning floppies from the provided disk image files. It can be "
+"downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/"
+"debian-imac/MakeDebianFloppy.sit\"></ulink>. 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 ""
 
 #. Tag: para
 #: install-methods.xml:457
 #, no-c-format
-msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> 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."
+msgid ""
+"You can also use the MacOS utility <command>Disk Copy</command> directly, or "
+"the freeware utility <command>suntar</command>. The <filename>root.bin</"
+"filename> 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 ""
 
 #. Tag: title
@@ -319,37 +480,59 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:469
 #, no-c-format
-msgid "If you are creating the floppy image from files which were originally on the official &debian; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a Debian mirror."
+msgid ""
+"If you are creating the floppy image from files which were originally on the "
+"official &debian; CD, then the Type and Creator are already set correctly. "
+"The following <command>Creator-Changer</command> steps are only necessary if "
+"you downloaded the image files from a Debian mirror."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:478
 #, no-c-format
-msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file."
+msgid ""
+"Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> "
+"and use it to open the <filename>root.bin</filename> file."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:485
 #, no-c-format
-msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields."
+msgid ""
+"Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type "
+"to <userinput>DDim</userinput> (binary floppy image). The case is sensitive "
+"for these fields."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:492
 #, no-c-format
-msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted."
+msgid ""
+"<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</"
+"userinput> to display the Finder information about the floppy image, and "
+"<quote>X</quote> the <userinput>File Locked</userinput> check box so that "
+"MacOS will be unable to remove the boot blocks if the image is accidentally "
+"mounted."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:501
 #, no-c-format
-msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>."
+msgid ""
+"Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it "
+"will very likely be there already, otherwise try <ulink url=\"&url-powerpc-"
+"diskcopy;\"></ulink>."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:508
 #, no-c-format
-msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> 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."
+msgid ""
+"Run <command>Disk Copy</command>, and select <menuchoice> "
+"<guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </"
+"menuchoice>, then select the <emphasis>locked</emphasis> 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 ""
 
 #. Tag: title
@@ -361,31 +544,44 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:527
 #, no-c-format
-msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu."
+msgid ""
+"Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </"
+"ulink>. Start the <command>suntar</command> program and select "
+"<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> "
+"menu."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:535
 #, no-c-format
-msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
+msgid ""
+"Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:541
 #, no-c-format
-msgid "Select the <filename>root.bin</filename> file in the file-opening dialog."
+msgid ""
+"Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:546
 #, no-c-format
-msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another."
+msgid ""
+"After the floppy has been created successfully, select <menuchoice> "
+"<guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If "
+"there are any errors writing the floppy, simply toss that floppy and try "
+"another."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:554
 #, no-c-format
-msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it."
+msgid ""
+"Before using the floppy you created, <emphasis>set the write protect tab</"
+"emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will "
+"helpfully ruin it."
 msgstr ""
 
 #. Tag: title
@@ -397,13 +593,22 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:575
 #, no-c-format
-msgid "For preparing the USB stick you will need a system where GNU/Linux is already running and where USB is supported. You should ensure that the usb-storage kernel module is loaded (<userinput>modprobe usb-storage</userinput>) and try to find out which SCSI device the USB stick has been mapped to (in this example <filename>/dev/sda</filename> is used). To write to your stick, you will probably have to turn off its write protection switch."
+msgid ""
+"For preparing the USB stick you will need a system where GNU/Linux is "
+"already running and where USB is supported. You should ensure that the usb-"
+"storage kernel module is loaded (<userinput>modprobe usb-storage</"
+"userinput>) and try to find out which SCSI device the USB stick has been "
+"mapped to (in this example <filename>/dev/sda</filename> is used). To write "
+"to your stick, you will probably have to turn off its write protection "
+"switch."
 msgstr ""
 
 #. Tag: para
 #: install-methods.xml:585
 #, no-c-format
-msgid "Note, that the USB stick should be at least 128 MB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)."
+msgid ""
+"Note, that the USB stick should be at least 128 MB in size (smaller setups "
+"are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)."
 msgstr ""
 
 #. Tag: title
@@ -416,160 +621,250 @@ msgstr ""
 #: install-methods.xml:594
 #, no-c-format
 msgid ""
-"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) as well as <command>SYSLINUX</command> and its configuration file. You only have to extract it directly to your USB stick: <informalexample><screen>\n"
-"# zcat boot.img.gz &gt; /dev/<replaceable>sda</replaceable>\n"
-"</screen></informalexample> Of course this will destroy anything already on the device, so take care that you use the correct device name for your USB stick."
+"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
+"contains all the installer files (including the kernel) as well as "
+"<command>SYSLINUX</command> and its configuration file. You only have to "
+"extract it directly to your USB stick:"
+msgstr ""
+
+#. Tag: screen
+#: install-methods.xml:601
+#, no-c-format
+msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sda</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:606
+#: install-methods.xml:603
 #, no-c-format
 msgid ""
-"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) as well as <command>yaboot</command> and its configuration file. Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that: <informalexample><screen>\n"
-"# zcat boot.img.gz &gt; /dev/<replaceable>sda2</replaceable>\n"
-"</screen></informalexample> Of course this will destroy anything already on the device, so take care that you use the correct device name for your USB stick."
+"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which "
+"contains all the installer files (including the kernel) as well as "
+"<command>yaboot</command> and its configuration file. Create a partition of "
+"type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</"
+"command>'s <userinput>C</userinput> command and extract the image directly "
+"to that:"
+msgstr ""
+
+#. Tag: screen
+#: install-methods.xml:612
+#, no-c-format
+msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sda2</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:620
+#: install-methods.xml:615
 #, no-c-format
-msgid "After that, mount the USB memory stick (<userinput>mount <replaceable arch=\"i386\">/dev/sda</replaceable> <replaceable arch=\"powerpc\">/dev/sda2</replaceable> /mnt</userinput>), which will now have <phrase arch=\"i386\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a Debian netinst or businesscard ISO image to it. Please note that the file name must end in <filename>.iso</filename>. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done."
+msgid ""
+"Using this method will destroy anything already on the device. Make sure "
+"that you use the correct device name for your USB stick."
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:621
+#, no-c-format
+msgid ""
+"After that, mount the USB memory stick (<userinput>mount <replaceable arch="
+"\"i386\">/dev/sda</replaceable> <replaceable arch=\"powerpc\">/dev/sda2</"
+"replaceable> /mnt</userinput>), which will now have <phrase arch=\"i386\">a "
+"FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> "
+"on it, and copy a Debian netinst or businesscard ISO image to it. Please "
+"note that the file name must end in <filename>.iso</filename>. Unmount the "
+"stick (<userinput>umount /mnt</userinput>) and you are done."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:636
+#: install-methods.xml:637
 #, no-c-format
 msgid "Copying the files &mdash; the flexible way"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:637
+#: install-methods.xml:638
 #, no-c-format
-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."
+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."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:649
-#: install-methods.xml:745
+#: install-methods.xml:650 install-methods.xml:746
 #, no-c-format
 msgid "USB stick partitioning on &arch-title;"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:650
+#: install-methods.xml:651
 #, no-c-format
-msgid "We will show how to setup the memory stick to use the first partition, instead of the entire device."
+msgid ""
+"We will show how to setup the memory stick to use the first partition, "
+"instead of the entire device."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:655
+#: install-methods.xml:656
 #, no-c-format
 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 <command>cfdisk</command> or any other partitioning tool for creating a FAT16 partition and then create the filesystem using: <informalexample><screen>\n"
+"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 <command>cfdisk</command> or any other partitioning tool "
+"for creating a FAT16 partition and then create the filesystem using: "
+"<informalexample><screen>\n"
 "# mkdosfs /dev/<replaceable>sda1</replaceable>\n"
-"</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>mkdosfs</command> command is contained in the <classname>dosfstools</classname> Debian package."
+"</screen></informalexample> Take care that you use the correct device name "
+"for your USB stick. The <command>mkdosfs</command> command is contained in "
+"the <classname>dosfstools</classname> Debian package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:669
+#: install-methods.xml:670
 #, no-c-format
-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 (e.g. <command>LILO</command>) should work, it's convenient to use <command>SYSLINUX</command>, 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."
+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 (e.g. <command>LILO</"
+"command>) should work, it's convenient to use <command>SYSLINUX</command>, "
+"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 ""
 
 #. Tag: para
-#: install-methods.xml:679
+#: install-methods.xml:680
 #, no-c-format
 msgid ""
-"To put <command>SYSLINUX</command> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n"
+"To put <command>SYSLINUX</command> on the FAT16 partition on your USB stick, "
+"install the <classname>syslinux</classname> and <classname>mtools</"
+"classname> packages on your system, and do: <informalexample><screen>\n"
 "# syslinux /dev/<replaceable>sda1</replaceable>\n"
-"</screen></informalexample> Again, take care that you use the correct device name. The partition must not be mounted when starting <command>SYSLINUX</command>. This procedure writes a boot sector to the partition and creates the file <filename>ldlinux.sys</filename> which contains the boot loader code."
+"</screen></informalexample> Again, take care that you use the correct device "
+"name. The partition must not be mounted when starting <command>SYSLINUX</"
+"command>. This procedure writes a boot sector to the partition and creates "
+"the file <filename>ldlinux.sys</filename> which contains the boot loader "
+"code."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:692
+#: install-methods.xml:693
 #, no-c-format
-msgid "Mount the partition (<userinput>mount /dev/sda1 /mnt</userinput>) and copy the following files from the Debian archives to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> <listitem><para> <filename>syslinux.cfg</filename> (SYSLINUX configuration file) </para></listitem> <listitem><para> Optional kernel modules </para></listitem> </itemizedlist> If you want to rename the files, please note that <command>SYSLINUX</command> can only process DOS (8.3) file names."
+msgid ""
+"Mount the partition (<userinput>mount /dev/sda1 /mnt</userinput>) and copy "
+"the following files from the Debian archives to the stick: <itemizedlist> "
+"<listitem><para> <filename>vmlinuz</filename> (kernel binary) </para></"
+"listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk "
+"image) </para></listitem> <listitem><para> <filename>syslinux.cfg</filename> "
+"(SYSLINUX configuration file) </para></listitem> <listitem><para> Optional "
+"kernel modules </para></listitem> </itemizedlist> If you want to rename the "
+"files, please note that <command>SYSLINUX</command> can only process DOS "
+"(8.3) file names."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:723
+#: install-methods.xml:724
 #, no-c-format
 msgid ""
-"The <filename>syslinux.cfg</filename> configuration file should contain the following two lines: <informalexample><screen>\n"
+"The <filename>syslinux.cfg</filename> configuration file should contain the "
+"following two lines: <informalexample><screen>\n"
 "default vmlinuz\n"
-"append initrd=initrd.gz ramdisk_size=12000 root=/dev/rd/0 init=/linuxrc rw\n"
-"</screen></informalexample> Please note that the <userinput>ramdisk_size</userinput> parameter may need to be increased, depending on the image you are booting. <phrase condition=\"sarge\"> If the boot fails, you can try adding <userinput>devfs=mount,dall</userinput> to the <quote>append</quote> line. </phrase>"
+"append initrd=initrd.gz ramdisk_size=12000 root=/dev/ram rw\n"
+"</screen></informalexample> Please note that the <userinput>ramdisk_size</"
+"userinput> parameter may need to be increased, depending on the image you "
+"are booting. <phrase condition=\"sarge\"> If the boot fails, you can try "
+"adding <userinput>devfs=mount,dall</userinput> to the <quote>append</quote> "
+"line. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:746
+#: install-methods.xml:747
 #, no-c-format
 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 <userinput>mac-fdisk /dev/sda</userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n"
+"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 <userinput>mac-fdisk /dev/sda</userinput>, initialise a new "
+"partition map using the <userinput>i</userinput> command, and create a new "
+"partition of type Apple_Bootstrap using the <userinput>C</userinput> "
+"command. (Note that the first \"partition\" will always be the partition map "
+"itself.) Then type <informalexample><screen>\n"
 "$ hformat /dev/<replaceable>sda2</replaceable>\n"
-"</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>hformat</command> command is contained in the <classname>hfsutils</classname> Debian package."
+"</screen></informalexample> Take care that you use the correct device name "
+"for your USB stick. The <command>hformat</command> command is contained in "
+"the <classname>hfsutils</classname> Debian package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:762
+#: install-methods.xml:763
 #, no-c-format
-msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> 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."
+msgid ""
+"In order to start the kernel after booting from the USB stick, we will put a "
+"boot loader on the stick. The <command>yaboot</command> 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 ""
 
 #. Tag: para
-#: install-methods.xml:771
+#: install-methods.xml:772
 #, no-c-format
 msgid ""
-"The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n"
+"The normal <command>ybin</command> tool that comes with <command>yaboot</"
+"command> does not yet understand USB storage devices, so you will have to "
+"install <command>yaboot</command> by hand using the <classname>hfsutils</"
+"classname> tools. Type <informalexample><screen>\n"
 "$ hmount /dev/sda2\n"
 "$ hcopy -r /usr/lib/yaboot/yaboot :\n"
 "$ hattrib -c UNIX -t tbxi :yaboot\n"
 "$ hattrib -b :\n"
 "$ humount\n"
-"</screen></informalexample> 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."
+"</screen></informalexample> 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 ""
 
 #. Tag: para
-#: install-methods.xml:787
+#: install-methods.xml:788
 #, no-c-format
-msgid "Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and copy the following files from the Debian archives to the stick:"
+msgid ""
+"Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and copy "
+"the following files from the Debian archives to the stick:"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:793
+#: install-methods.xml:794
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:798
+#: install-methods.xml:799
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:803
+#: install-methods.xml:804
 #, fuzzy, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
-msgstr "Skapandet av huvudkonfigurationsfilen för yaboot misslyckades."
+msgstr "Skapandet av huvudkonfigurationsfilen för yaboot misslyckades."
 
 #. Tag: para
-#: install-methods.xml:808
+#: install-methods.xml:809
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:813
+#: install-methods.xml:814
 #, fuzzy, no-c-format
 msgid "Optional kernel modules"
 msgstr "Moduler som ska laddas:"
 
 #. Tag: para
-#: install-methods.xml:820
+#: install-methods.xml:821
 #, no-c-format
 msgid ""
-"The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n"
+"The <filename>yaboot.conf</filename> configuration file should contain the "
+"following lines: <informalexample><screen>\n"
 "default=install\n"
 "root=/dev/ram\n"
 "\n"
@@ -581,272 +876,401 @@ msgid ""
 "        initrd-size=10000<phrase condition=\"sarge\">\n"
 "        append=\"devfs=mount,dall --\"</phrase>\n"
 "        read-only\n"
-"</screen></informalexample> Please note that the <userinput>initrd-size</userinput> parameter may need to be increased, depending on the image you are booting."
+"</screen></informalexample> Please note that the <userinput>initrd-size</"
+"userinput> parameter may need to be increased, depending on the image you "
+"are booting."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:835
+#: install-methods.xml:836
 #, fuzzy, no-c-format
 msgid "Adding an ISO image"
 msgstr "Hittade ingen installations-ISO-avbild"
 
 #. Tag: para
-#: install-methods.xml:836
+#: install-methods.xml:837
 #, no-c-format
-msgid "Now you should put any Debian ISO image (businesscard, netinst or even a full one) onto your stick (if it fits). The file name of such an image must end in <filename>.iso</filename>."
+msgid ""
+"Now you should put any Debian ISO image (businesscard, netinst or even a "
+"full one) onto your stick (if it fits). The file name of such an image must "
+"end in <filename>.iso</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:842
+#: install-methods.xml:843
 #, no-c-format
-msgid "If you want to install over the network, without using an ISO image, you will of course skip the previous step. Moreover you will have to use the initial ramdisk from the <filename>netboot</filename> directory instead of the one from <filename>hd-media</filename>, because <filename>hd-media/initrd.gz</filename> does not have network support."
+msgid ""
+"If you want to install over the network, without using an ISO image, you "
+"will of course skip the previous step. Moreover you will have to use the "
+"initial ramdisk from the <filename>netboot</filename> directory instead of "
+"the one from <filename>hd-media</filename>, because <filename>hd-media/"
+"initrd.gz</filename> does not have network support."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:851
+#: install-methods.xml:852
 #, no-c-format
-msgid "When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>) and activate its write protection switch."
+msgid ""
+"When you are done, unmount the USB memory stick (<userinput>umount /mnt</"
+"userinput>) and activate its write protection switch."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:861
+#: install-methods.xml:862
 #, no-c-format
 msgid "Booting the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:862
+#: install-methods.xml:863
 #, no-c-format
-msgid "If your system refuses to boot from the memory stick, the stick may contain an invalid master boot record (MBR). To fix this, use the <command>install-mbr</command> command from the package <classname>mbr</classname>:"
+msgid ""
+"If your system refuses to boot from the memory stick, the stick may contain "
+"an invalid master boot record (MBR). To fix this, use the <command>install-"
+"mbr</command> command from the package <classname>mbr</classname>:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:869
+#: install-methods.xml:870
 #, no-c-format
 msgid "# install-mbr /dev/<replaceable>sda</replaceable>"
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:881
+#: install-methods.xml:882
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:882
+#: install-methods.xml:883
 #, 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."
+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."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:888
+#: install-methods.xml:889
 #, no-c-format
-msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks."
+msgid ""
+"A full, <quote>pure network</quote> installation can be achieved using this "
+"technique. This avoids all hassles of removable media, like finding and "
+"burning CD images or struggling with too numerous and unreliable floppy "
+"disks."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:895
+#: install-methods.xml:896
 #, no-c-format
 msgid "The installer cannot boot from files on an NTFS file system."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:899
+#: install-methods.xml:900
 #, no-c-format
-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 <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download."
+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 <userinput>Get "
+"Info</userinput> for the volume in question. HFS file systems appear as "
+"<userinput>Mac OS Standard</userinput>, while HFS+ file systems say "
+"<userinput>Mac OS Extended</userinput>. You must have an HFS partition in "
+"order to exchange files between MacOS and Linux, in particular the "
+"installation files you download."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:910
+#: install-methods.xml:911
 #, no-c-format
-msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model."
+msgid ""
+"Different programs are used for hard disk installation system booting, "
+"depending on whether the system is a <quote>NewWorld</quote> or an "
+"<quote>OldWorld</quote> model."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:919
+#: install-methods.xml:920
 #, no-c-format
-msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>"
+msgid ""
+"Hard disk installer booting using <command>LILO</command> or <command>GRUB</"
+"command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:921
+#: install-methods.xml:922
 #, no-c-format
-msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>."
+msgid ""
+"This section explains how to add to or even replace an existing linux "
+"installation using either <command>LILO</command> or <command>GRUB</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:927
+#: install-methods.xml:928
 #, no-c-format
-msgid "At boot time, both bootloaders support 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."
+msgid ""
+"At boot time, both bootloaders support 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:933
+#: install-methods.xml:934
 #, no-c-format
-msgid "Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>."
+msgid ""
+"Copy the following files from the Debian archives to a convenient location "
+"on your hard drive, for instance to <filename>/boot/newinstall/</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:940
+#: install-methods.xml:941
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:945
+#: install-methods.xml:946
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:952
+#: install-methods.xml:953
 #, no-c-format
-msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."
+msgid ""
+"Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd"
+"\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:962
+#: install-methods.xml:963
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:963
+#: install-methods.xml:964
 #, no-c-format
-msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your Debian installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model."
+msgid ""
+"The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</"
+"application> to launch Linux installation, but <application>miBoot</"
+"application> cannot easily be used for hard disk booting. "
+"<application>BootX</application>, launched from MacOS, supports booting from "
+"files placed on the hard disk. <application>BootX</application> can also be "
+"used to dual-boot MacOS and Linux after your Debian installation is "
+"complete. For the Performa 6360, it appears that <command>quik</command> "
+"cannot make the hard disk bootable. So <application>BootX</application> is "
+"required on that model."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:976
+#: install-methods.xml:977
 #, no-c-format
-msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on Debian http/ftp mirrors and official Debian CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder."
+msgid ""
+"Download and unstuff the <application>BootX</application> distribution, "
+"available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the "
+"<filename>dists/woody/main/disks-powerpc/current/powermac</filename> "
+"directory on Debian http/ftp mirrors and official Debian CDs. Use "
+"<application>Stuffit Expander</application> to extract it from its archive. "
+"Within the package, there is an empty folder called <filename>Linux Kernels</"
+"filename>. Download <filename>linux.bin</filename> and <filename>ramdisk."
+"image.gz</filename> from the <filename>disks-powerpc/current/powermac</"
+"filename> folder, and place them in the <filename>Linux Kernels</filename> "
+"folder. Then place the <filename>Linux Kernels</filename> folder in the "
+"active System Folder."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:996
+#: install-methods.xml:997
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:997
+#: install-methods.xml:998
 #, no-c-format
-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 <command>yaboot</command>, 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. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs."
+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 <command>yaboot</command>, 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. <command>BootX</"
+"command> is not supported and must not be used on NewWorld PowerMacs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1008
+#: install-methods.xml:1009
 #, no-c-format
-msgid "<emphasis>Copy</emphasis> (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 <keycap>option</keycap>-dragging each file to the hard drive icon)."
+msgid ""
+"<emphasis>Copy</emphasis> (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 <keycap>option</keycap>-dragging "
+"each file to the hard drive icon)."
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1018
+#: install-methods.xml:1019
 #, no-c-format
 msgid "vmlinux"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1023
+#: install-methods.xml:1024
 #, no-c-format
 msgid "initrd.gz"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1028
+#: install-methods.xml:1029
 #, no-c-format
 msgid "yaboot"
 msgstr "yaboot"
 
 #. Tag: filename
-#: install-methods.xml:1033
+#: install-methods.xml:1034
 #, no-c-format
 msgid "yaboot.conf"
 msgstr "yaboot.conf"
 
 #. Tag: para
-#: install-methods.xml:1038
+#: install-methods.xml:1039
 #, no-c-format
-msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the L command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer."
+msgid ""
+"Make a note of the partition number of the MacOS partition where you place "
+"these files. If you have the MacOS <command>pdisk</command> program, you can "
+"use the L command to check for the partition number. You will need this "
+"partition number for the command you type at the Open Firmware prompt when "
+"you boot the installer."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1046
+#: install-methods.xml:1047
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1059
+#: install-methods.xml:1060
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1060
+#: install-methods.xml:1061
 #, 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."
+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:1068
+#: install-methods.xml:1069
 #, no-c-format
-msgid "You need to setup a TFTP server, and for many machines, a BOOTP server <phrase condition=\"supports-rarp\">, or RARP server</phrase> <phrase condition=\"supports-dhcp\">, or DHCP server</phrase>."
+msgid ""
+"You need to setup a TFTP server, and for many machines, a BOOTP server "
+"<phrase condition=\"supports-rarp\">, or RARP server</phrase> <phrase "
+"condition=\"supports-dhcp\">, or DHCP server</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1074
+#: install-methods.xml:1075
 #, no-c-format
-msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol. </phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image. </phrase> <phrase arch=\"m68k\"> Yet another alternative exists on VMEbus systems: the IP address can be manually configured in boot ROM. </phrase> <phrase condition=\"supports-dhcp\">The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP. </phrase>"
+msgid ""
+"<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol "
+"(RARP) is one way to tell your client what IP address to use for itself. "
+"Another way is to use the BOOTP protocol. </phrase> <phrase condition="
+"\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP "
+"address and where on the network to obtain a boot image. </phrase> <phrase "
+"arch=\"m68k\"> Yet another alternative exists on VMEbus systems: the IP "
+"address can be manually configured in boot ROM. </phrase> <phrase condition="
+"\"supports-dhcp\">The DHCP (Dynamic Host Configuration Protocol) is a more "
+"flexible, backwards-compatible extension of BOOTP. Some systems can only be "
+"configured via DHCP. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1091
+#: install-methods.xml:1092
 #, no-c-format
-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."
+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 ""
 
 #. Tag: para
-#: install-methods.xml:1097
+#: install-methods.xml:1098
 #, no-c-format
-msgid "Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM console will <emphasis>not</emphasis> use RARP to obtain its IP address, and therefore you must use BOOTP for net booting your Alpha<footnote> <para> Alpha systems can also be net-booted using the DECNet MOP (Maintenance Operations Protocol), but this is not covered here. Presumably, your local OpenVMS operator will be happy to assist you should you have some burning need to use MOP to boot Linux on your Alpha. </para> </footnote>. You can also enter the IP configuration for network interfaces directly in the SRM console."
+msgid ""
+"Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM "
+"console will <emphasis>not</emphasis> use RARP to obtain its IP address, and "
+"therefore you must use BOOTP for net booting your Alpha<footnote> <para> "
+"Alpha systems can also be net-booted using the DECNet MOP (Maintenance "
+"Operations Protocol), but this is not covered here. Presumably, your local "
+"OpenVMS operator will be happy to assist you should you have some burning "
+"need to use MOP to boot Linux on your Alpha. </para> </footnote>. You can "
+"also enter the IP configuration for network interfaces directly in the SRM "
+"console."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1114
+#: install-methods.xml:1115
 #, no-c-format
-msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in Debian."
+msgid ""
+"Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There "
+"is an <classname>rbootd</classname> package available in Debian."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1119
+#: install-methods.xml:1120
 #, 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."
+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:1127
+#: install-methods.xml:1128
 #, no-c-format
-msgid "To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> support. On a &debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</classname> packages qualify; we recommend <classname>tftpd-hpa</classname>."
+msgid ""
+"To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you "
+"will need a TFTP server with <userinput>tsize</userinput> support. On a "
+"&debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</"
+"classname> packages qualify; we recommend <classname>tftpd-hpa</classname>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1145
+#: install-methods.xml:1146
 #, fuzzy, no-c-format
 msgid "Setting up RARP server"
 msgstr "Klar med partitionen"
 
 #. Tag: para
-#: install-methods.xml:1146
+#: install-methods.xml:1147
 #, no-c-format
-msgid "To setup 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 <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>."
+msgid ""
+"To setup 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 <phrase arch=\"sparc\"> pick it off the initial "
+"OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> "
+"command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the "
+"rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</"
+"userinput>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1158
+#: install-methods.xml:1159
 #, no-c-format
 msgid ""
-"On a RARP server system using a Linux 2.2.x kernel, you need to populate the kernel's RARP table. To do this, run the following commands: <informalexample><screen>\n"
+"On a RARP server system using a Linux 2.2.x kernel, you need to populate the "
+"kernel's RARP table. To do this, run the following commands: "
+"<informalexample><screen>\n"
 "# <userinput>/sbin/rarp -s\n"
 "<replaceable>client-hostname</replaceable>\n"
 "<replaceable>client-enet-addr</replaceable></userinput>\n"
@@ -856,40 +1280,66 @@ msgid ""
 "<replaceable>client-enet-addr</replaceable></userinput>\n"
 "</screen></informalexample> If you get <informalexample><screen>\n"
 "SIOCSRARP: Invalid argument\n"
-"</screen></informalexample> you probably need to load the RARP kernel module or else recompile the kernel to support RARP. Try <userinput>modprobe rarp</userinput> and then try the <command>rarp</command> command again."
+"</screen></informalexample> you probably need to load the RARP kernel module "
+"or else recompile the kernel to support RARP. Try <userinput>modprobe rarp</"
+"userinput> and then try the <command>rarp</command> command again."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1174
+#: install-methods.xml:1175
 #, no-c-format
-msgid "On a RARP server system using a Linux 2.4.x kernel, there is no RARP module, and you should instead use the <command>rarpd</command> program. The procedure is similar to that used under SunOS in the following paragraph."
+msgid ""
+"On a RARP server system using a Linux 2.4.x kernel, there is no RARP module, "
+"and you should instead use the <command>rarpd</command> program. The "
+"procedure is similar to that used under SunOS in the following paragraph."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1182
+#: install-methods.xml:1183
 #, no-c-format
-msgid "Under SunOS, you need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. In SunOS 4, issue the command (as root): <userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use <userinput>/usr/sbin/rarpd -a</userinput>."
+msgid ""
+"Under SunOS, you need to ensure that the Ethernet hardware address for the "
+"client is listed in the <quote>ethers</quote> database (either in the "
+"<filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the "
+"<quote>hosts</quote> database. Then you need to start the RARP daemon. In "
+"SunOS 4, issue the command (as root): <userinput>/usr/etc/rarpd -a</"
+"userinput>; in SunOS 5, use <userinput>/usr/sbin/rarpd -a</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1201
+#: install-methods.xml:1202
 #, fuzzy, no-c-format
 msgid "Setting up BOOTP server"
 msgstr "Klar med partitionen"
 
 #. Tag: para
-#: install-methods.xml:1202
+#: install-methods.xml:1203
 #, no-c-format
-msgid "There are two BOOTP servers available for GNU/Linux, the CMU <command>bootpd</command> and the other is actually a DHCP server, ISC <command>dhcpd</command>, which are contained in the <classname>bootp</classname> and <classname>dhcp</classname> packages in &debian;."
+msgid ""
+"There are two BOOTP servers available for GNU/Linux, the CMU "
+"<command>bootpd</command> and the other is actually a DHCP server, ISC "
+"<command>dhcpd</command>, which are contained in the <classname>bootp</"
+"classname> and <classname>dhcp</classname> packages in &debian;."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1210
+#: install-methods.xml:1211
 #, no-c-format
 msgid ""
-"To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Elsewhere, the line in question should look like: <informalexample><screen>\n"
+"To use CMU <command>bootpd</command>, you must first uncomment (or add) the "
+"relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can "
+"run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/"
+"etc/init.d/inetd reload</userinput> to do so. Elsewhere, the line in "
+"question should look like: <informalexample><screen>\n"
 "bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120\n"
-"</screen></informalexample> Now, you must create an <filename>/etc/bootptab</filename> file. This has the same sort of familiar and cryptic format as the good old BSD <filename>printcap</filename>, <filename>termcap</filename>, and <filename>disktab</filename> files. See the <filename>bootptab</filename> manual page for more information. For CMU <command>bootpd</command>, you will need to know the hardware (MAC) address of the client. Here is an example <filename>/etc/bootptab</filename>: <informalexample><screen>\n"
+"</screen></informalexample> Now, you must create an <filename>/etc/bootptab</"
+"filename> file. This has the same sort of familiar and cryptic format as the "
+"good old BSD <filename>printcap</filename>, <filename>termcap</filename>, "
+"and <filename>disktab</filename> files. See the <filename>bootptab</"
+"filename> manual page for more information. For CMU <command>bootpd</"
+"command>, you will need to know the hardware (MAC) address of the client. "
+"Here is an example <filename>/etc/bootptab</filename>: "
+"<informalexample><screen>\n"
 "client:\\\n"
 "  hd=/tftpboot:\\\n"
 "  bf=tftpboot.img:\\\n"
@@ -897,26 +1347,43 @@ msgid ""
 "  sm=255.255.255.0:\\\n"
 "  sa=192.168.1.1:\\\n"
 "  ha=0123456789AB:\n"
-"</screen></informalexample> You will need to change at least the <quote>ha</quote> option, which specifies the hardware address of the client. The <quote>bf</quote> option specifies the file a client should retrieve via TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI Indys you can just enter the command monitor and type <userinput>printenv</userinput>. The value of the <userinput>eaddr</userinput> variable is the machine's MAC address. </phrase>"
+"</screen></informalexample> You will need to change at least the <quote>ha</"
+"quote> option, which specifies the hardware address of the client. The "
+"<quote>bf</quote> option specifies the file a client should retrieve via "
+"TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch="
+"\"mips\"> On SGI Indys you can just enter the command monitor and type "
+"<userinput>printenv</userinput>. The value of the <userinput>eaddr</"
+"userinput> variable is the machine's MAC address. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1243
+#: install-methods.xml:1244
 #, no-c-format
-msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise, you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd restart</userinput>."
+msgid ""
+"By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really "
+"easy, because it treats BOOTP clients as a moderately special case of DHCP "
+"clients. Some architectures require a complex configuration for booting "
+"clients via BOOTP. If yours is one of those, read the section <xref linkend="
+"\"dhcpd\"/>. Otherwise, you will probably be able to get away with simply "
+"adding the <userinput>allow bootp</userinput> directive to the configuration "
+"block for the subnet containing the client, and restart <command>dhcpd</"
+"command> with <userinput>/etc/init.d/dhcpd restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1264
+#: install-methods.xml:1265
 #, fuzzy, no-c-format
 msgid "Setting up a DHCP server"
 msgstr "Klar med partitionen"
 
 #. Tag: para
-#: install-methods.xml:1265
+#: install-methods.xml:1266
 #, no-c-format
 msgid ""
-"One free software DHCP server is ISC <command>dhcpd</command>. In &debian;, this is available in the <classname>dhcp</classname> package. Here is a sample configuration file for it (usually <filename>/etc/dhcpd.conf</filename>): <informalexample><screen>\n"
+"One free software DHCP server is ISC <command>dhcpd</command>. In &debian;, "
+"this is available in the <classname>dhcp</classname> package. Here is a "
+"sample configuration file for it (usually <filename>/etc/dhcpd.conf</"
+"filename>): <informalexample><screen>\n"
 "option domain-name \"example.com\";\n"
 "option domain-name-servers ns1.example.com;\n"
 "option subnet-mask 255.255.255.0;\n"
@@ -936,32 +1403,42 @@ msgid ""
 "  hardware ethernet 01:23:45:67:89:AB;\n"
 "  fixed-address 192.168.1.90;\n"
 "}\n"
-"</screen></informalexample> Note: the new (and preferred) <classname>dhcp3</classname> package uses <filename>/etc/dhcp3/dhcpd.conf</filename>."
+"</screen></informalexample> Note: the new (and preferred) <classname>dhcp3</"
+"classname> package uses <filename>/etc/dhcp3/dhcpd.conf</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1277
+#: install-methods.xml:1278
 #, no-c-format
-msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP."
+msgid ""
+"In this example, there is one server <replaceable>servername</replaceable> "
+"which performs all of the work of DHCP server, TFTP server, and network "
+"gateway. You will almost certainly need to change the domain-name options, "
+"as well as the server name and client hardware address. The "
+"<replaceable>filename</replaceable> option should be the name of the file "
+"which will be retrieved via TFTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1287
+#: install-methods.xml:1288
 #, no-c-format
-msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd restart</userinput>."
+msgid ""
+"After you have edited the <command>dhcpd</command> configuration file, "
+"restart it with <userinput>/etc/init.d/dhcpd restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1295
+#: install-methods.xml:1296
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1296
+#: install-methods.xml:1297
 #, no-c-format
 msgid ""
-"Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
+"Here is another example for a <filename>dhcp.conf</filename> using the Pre-"
+"boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
 "option domain-name \"example.com\";\n"
 "\n"
 "default-lease-time 600;\n"
@@ -989,264 +1466,417 @@ msgid ""
 "  filename \"/tftpboot/pxelinux.0\";\n"
 " }\n"
 "}\n"
-"</screen></informalexample> Note that for PXE booting, the client filename <filename>pxelinux.0</filename> is a boot loader, not a kernel image (see <xref linkend=\"tftp-images\"/> below)."
+"</screen></informalexample> Note that for PXE booting, the client filename "
+"<filename>pxelinux.0</filename> is a boot loader, not a kernel image (see "
+"<xref linkend=\"tftp-images\"/> below)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1312
+#: install-methods.xml:1313
 #, fuzzy, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr "Diskussionsgruppsserver"
 
 #. Tag: para
-#: install-methods.xml:1313
+#: install-methods.xml:1314
 #, no-c-format
 msgid ""
-"To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled. This is usually enabled by having something like the following line in <filename>/etc/inetd.conf</filename>: <informalexample><screen>\n"
+"To get the TFTP server ready to go, you should first make sure that "
+"<command>tftpd</command> is enabled. This is usually enabled by having "
+"something like the following line in <filename>/etc/inetd.conf</filename>: "
+"<informalexample><screen>\n"
 "tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd /tftpboot\n"
-"</screen></informalexample> Debian packages will in general set this up correctly by default when they are installed."
+"</screen></informalexample> Debian packages will in general set this up "
+"correctly by default when they are installed."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1324
+#: install-methods.xml:1325
 #, no-c-format
-msgid "Look in that file and remember the directory which is used as the argument of <command>in.tftpd</command>; you'll need that below. The <userinput>-l</userinput> argument enables some versions of <command>in.tftpd</command> to log all requests to the system logs; this is useful for diagnosing boot errors. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>."
+msgid ""
+"Look in that file and remember the directory which is used as the argument "
+"of <command>in.tftpd</command>; you'll need that below. The <userinput>-l</"
+"userinput> argument enables some versions of <command>in.tftpd</command> to "
+"log all requests to the system logs; this is useful for diagnosing boot "
+"errors. If you've had to change <filename>/etc/inetd.conf</filename>, you'll "
+"have to notify the running <command>inetd</command> process that the file "
+"has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</"
+"userinput>; on other machines, find out the process ID for <command>inetd</"
+"command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></"
+"userinput>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1339
 #, no-c-format
 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: <informalexample><screen>\n"
+"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: <informalexample><screen>\n"
 "# echo 1 &gt; /proc/sys/net/ipv4/ip_no_pmtu_disc\n"
-"</screen></informalexample> to turn off Path MTU discovery, otherwise the Indy'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 <informalexample><screen>\n"
+"</screen></informalexample> to turn off Path MTU discovery, otherwise the "
+"Indy'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 <informalexample><screen>\n"
 "# echo \"2048 32767\" &gt; /proc/sys/net/ipv4/ip_local_port_range\n"
-"</screen></informalexample> to adjust the range of source ports the Linux TFTP server uses."
+"</screen></informalexample> to adjust the range of source ports the Linux "
+"TFTP server uses."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1360
+#: install-methods.xml:1361
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1361
+#: install-methods.xml:1362
 #, no-c-format
-msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. Generally, this directory will be <filename>/tftpboot</filename>. You'll have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards."
+msgid ""
+"Next, place the TFTP boot image you need, as found in <xref linkend=\"where-"
+"files\"/>, in the <command>tftpd</command> boot image directory. Generally, "
+"this directory will be <filename>/tftpboot</filename>. You'll have to make a "
+"link from that file to the file which <command>tftpd</command> will use for "
+"booting a particular client. Unfortunately, the file name is determined by "
+"the TFTP client, and there are no strong standards."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1371
+#: install-methods.xml:1372
 #, no-c-format
-msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP directory."
+msgid ""
+"On NewWorld Power Macintosh machines, you will need to set up the "
+"<command>yaboot</command> boot loader as the TFTP boot image. "
+"<command>Yaboot</command> will then retrieve the kernel and RAMdisk images "
+"via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</"
+"filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP "
+"directory."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1380
+#: install-methods.xml:1381
 #, no-c-format
-msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/pxelinux.0</filename> to <command>tftpd</command> as the filename to boot."
+msgid ""
+"For PXE booting, everything you should need is set up in the "
+"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
+"tarball into the <command>tftpd</command> boot image directory. Make sure "
+"your dhcp server is configured to pass <filename>/pxelinux.0</filename> to "
+"<command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1388
+#: install-methods.xml:1389
 #, no-c-format
-msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
+msgid ""
+"For PXE booting, everything you should need is set up in the "
+"<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this "
+"tarball into the <command>tftpd</command> boot image directory. Make sure "
+"your dhcp server is configured to pass <filename>/debian-installer/ia64/"
+"elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1400
+#: install-methods.xml:1401
 #, fuzzy, no-c-format
 msgid "DECstation TFTP Images"
 msgstr "Visa knappbilder"
 
 #. Tag: para
-#: install-methods.xml:1401
+#: install-methods.xml:1402
 #, no-c-format
-msgid "For DECstations, there are tftpimage files for each subarchitecture, which contain both kernel and installer in one file. The naming convention is <replaceable>subarchitecture</replaceable>/netboot-boot.img. Copy the tftpimage file you would like to use to <userinput>/tftpboot/tftpboot.img</userinput> if you work with the example BOOTP/DHCP setups described above."
+msgid ""
+"For DECstations, there are tftpimage files for each subarchitecture, which "
+"contain both kernel and installer in one file. The naming convention is "
+"<replaceable>subarchitecture</replaceable>/netboot-boot.img. Copy the "
+"tftpimage file you would like to use to <userinput>/tftpboot/tftpboot.img</"
+"userinput> if you work with the example BOOTP/DHCP setups described above."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1410
+#: install-methods.xml:1411
 #, no-c-format
-msgid "The DECstation firmware boots by TFTP with the command <userinput>boot <replaceable>#</replaceable>/tftp</userinput>, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot. On most DECstations this is <quote>3</quote>. If the BOOTP/DHCP server does not supply the filename or you need to pass additional parameters, they can optionally be appended with the following syntax:"
+msgid ""
+"The DECstation firmware boots by TFTP with the command <userinput>boot "
+"<replaceable>#</replaceable>/tftp</userinput>, where <replaceable>#</"
+"replaceable> is the number of the TurboChannel device from which to boot. On "
+"most DECstations this is <quote>3</quote>. If the BOOTP/DHCP server does not "
+"supply the filename or you need to pass additional parameters, they can "
+"optionally be appended with the following syntax:"
 msgstr ""
 
 #. Tag: userinput
-#: install-methods.xml:1422
+#: install-methods.xml:1423
 #, no-c-format
 msgid "boot #/tftp/filename param1=value1 param2=value2 ..."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1424
+#: install-methods.xml:1425
 #, no-c-format
-msgid "Several DECstation firmware revisions show a problem with regard to net booting: the transfer starts, but after some time it stops with an <computeroutput>a.out err</computeroutput>. This can have several reasons: <orderedlist> <listitem><para> The firmware does not respond to ARP requests during a TFTP transfer. This leads to an ARP timeout and the transfer stops. The solution is to add the MAC address of the Ethernet card in the DECstation statically to the ARP table of the TFTP server. This is done by running <userinput>arp -s <replaceable>IP-address</replaceable> <replaceable>MAC-address</replaceable></userinput> as root on the machine acting as TFTP server. The MAC-address of the DECstation can be read out by entering <command>cnfg</command> at the DECstation firmware prompt. </para></listitem> <listitem><para> The firmware has a size limit on the files that can be booted by TFTP. </para></listitem> </orderedlist> There are also firmware revisions that cannot boot via TFTP at all. An overview about the different firmware revisions can be found at the NetBSD web pages: <ulink url=\"http://www.netbsd.org/Ports/pmax/board-list.html#proms\"></ulink>."
+msgid ""
+"Several DECstation firmware revisions show a problem with regard to net "
+"booting: the transfer starts, but after some time it stops with an "
+"<computeroutput>a.out err</computeroutput>. This can have several reasons: "
+"<orderedlist> <listitem><para> The firmware does not respond to ARP requests "
+"during a TFTP transfer. This leads to an ARP timeout and the transfer stops. "
+"The solution is to add the MAC address of the Ethernet card in the "
+"DECstation statically to the ARP table of the TFTP server. This is done by "
+"running <userinput>arp -s <replaceable>IP-address</replaceable> "
+"<replaceable>MAC-address</replaceable></userinput> as root on the machine "
+"acting as TFTP server. The MAC-address of the DECstation can be read out by "
+"entering <command>cnfg</command> at the DECstation firmware prompt. </para></"
+"listitem> <listitem><para> The firmware has a size limit on the files that "
+"can be booted by TFTP. </para></listitem> </orderedlist> There are also "
+"firmware revisions that cannot boot via TFTP at all. An overview about the "
+"different firmware revisions can be found at the NetBSD web pages: <ulink "
+"url=\"http://www.netbsd.org/Ports/pmax/board-list.html#proms\"></ulink>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1462
+#: install-methods.xml:1463
 #, fuzzy, no-c-format
 msgid "Alpha TFTP Booting"
-msgstr "Alfavärde för markeringsrutan"
+msgstr "Alfavärde för markeringsrutan"
 
 #. Tag: para
-#: install-methods.xml:1463
+#: install-methods.xml:1464
 #, no-c-format
-msgid "On Alpha, you must specify the filename (as a relative path to the boot image directory) using the <userinput>-file</userinput> argument to the SRM <userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</userinput> environment variable. Alternatively, the filename can be given via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</userinput> directive). Unlike Open Firmware, there is <emphasis>no default filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a filename by either one of these methods."
+msgid ""
+"On Alpha, you must specify the filename (as a relative path to the boot "
+"image directory) using the <userinput>-file</userinput> argument to the SRM "
+"<userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</"
+"userinput> environment variable. Alternatively, the filename can be given "
+"via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</"
+"userinput> directive). Unlike Open Firmware, there is <emphasis>no default "
+"filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a "
+"filename by either one of these methods."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1478
+#: install-methods.xml:1479
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1479
+#: install-methods.xml:1480
 #, no-c-format
 msgid ""
-"SPARC architectures for instance use the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>; in some cases, the architecture is left blank, so the file the client looks for is just <filename>client-ip-in-hex</filename>. Thus, if your system subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. An easy way to determine this is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n"
-"$ printf '%.2x%.2x%.2x%.2x\\n"
-"' 10 0 0 4\n"
-"</screen></informalexample> This will spit out the IP in hexadecimal; to get to the correct filename, you will need to change all letters to uppercase and if necessary append the subarchitecture name."
+"SPARC architectures for instance use the subarchitecture names, such as "
+"<quote>SUN4M</quote> or <quote>SUN4C</quote>; in some cases, the "
+"architecture is left blank, so the file the client looks for is just "
+"<filename>client-ip-in-hex</filename>. Thus, if your system subarchitecture "
+"is a SUN4C, and its IP is 192.168.1.3, the filename would be "
+"<filename>C0A80103.SUN4C</filename>. An easy way to determine this is to "
+"enter the following command in a shell (assuming the machine's intended IP "
+"is 10.0.0.4). <informalexample><screen>\n"
+"$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n"
+"</screen></informalexample> This will spit out the IP in hexadecimal; to get "
+"to the correct filename, you will need to change all letters to uppercase "
+"and if necessary append the subarchitecture name."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1496
+#: install-methods.xml:1497
 #, no-c-format
-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 <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in."
+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 <userinput>boot "
+"net my-sparc.image</userinput>. This must still reside in the directory that "
+"the TFTP server looks in."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1507
+#: install-methods.xml:1508
 #, no-c-format
 msgid "BVM/Motorola TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1508
+#: install-methods.xml:1509
 #, no-c-format
-msgid "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to <filename>/tftpboot/</filename>."
+msgid ""
+"For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to "
+"<filename>/tftpboot/</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1513
+#: install-methods.xml:1514
 #, no-c-format
-msgid "Next, configure your boot ROMs or BOOTP server to initially load the <filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> files from the TFTP server. Refer to the <filename>tftplilo.txt</filename> file for your subarchitecture for additional system-specific configuration information."
+msgid ""
+"Next, configure your boot ROMs or BOOTP server to initially load the "
+"<filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> "
+"files from the TFTP server. Refer to the <filename>tftplilo.txt</filename> "
+"file for your subarchitecture for additional system-specific configuration "
+"information."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1525
+#: install-methods.xml:1526
 #, no-c-format
 msgid "SGI Indys TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1526
+#: install-methods.xml:1527
 #, no-c-format
-msgid "On SGI Indys you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>."
+msgid ""
+"On SGI Indys you can rely on the <command>bootpd</command> to supply the "
+"name of the TFTP file. It is given either as the <userinput>bf=</userinput> "
+"in <filename>/etc/bootptab</filename> or as the <userinput>filename=</"
+"userinput> option in <filename>/etc/dhcpd.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1538
+#: install-methods.xml:1539
 #, no-c-format
 msgid "Broadcom BCM91250A TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1539
+#: install-methods.xml:1540
 #, no-c-format
-msgid "You don't have to configure DHCP in a special way because you'll pass the full path of the file to the loaded to CFE."
+msgid ""
+"You don't have to configure DHCP in a special way because you'll pass the "
+"full path of the file to the loaded to CFE."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1644
+#: install-methods.xml:1645
 #, no-c-format
 msgid "Automatic Installation"
 msgstr "Automatisk installation"
 
 #. Tag: para
-#: install-methods.xml:1645
+#: install-methods.xml:1646
 #, no-c-format
-msgid "For installing on multiple computers it's possible to do fully automatic installations. Debian packages intended for this include <classname>fai</classname> (which uses an install server), <classname>replicator</classname>, <classname>systemimager</classname>, <classname>autoinstall</classname>, and the Debian Installer itself."
+msgid ""
+"For installing on multiple computers it's possible to do fully automatic "
+"installations. Debian packages intended for this include <classname>fai</"
+"classname> (which uses an install server), <classname>replicator</"
+"classname>, <classname>systemimager</classname>, <classname>autoinstall</"
+"classname>, and the Debian Installer itself."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1658
+#: install-methods.xml:1659
 #, no-c-format
 msgid "Automatic Installation Using the Debian Installer"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1659
+#: install-methods.xml:1660
 #, 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 question asked during the installation process."
+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 question asked during the "
+"installation process."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1666
+#: install-methods.xml:1667
 #, no-c-format
-msgid "Although most dialogs used by &d-i; can be preseeded using this method, there are some notable exceptions. You can (re)partition an entire disk or use available free space on a disk; it is not possible to use existing partitions. You currently cannot use preseeding to set up RAID and LVM. <phrase condition=\"sarge\">Also, with the exception of network driver modules, it is not possible to preconfigure kernel module parameters.</phrase>"
+msgid ""
+"Although most dialogs used by &d-i; can be preseeded using this method, "
+"there are some notable exceptions. You can (re)partition an entire disk or "
+"use available free space on a disk; it is not possible to use existing "
+"partitions. You currently cannot use preseeding to set up RAID and LVM. "
+"<phrase condition=\"sarge\">Also, with the exception of network driver "
+"modules, it is not possible to preconfigure kernel module parameters.</"
+"phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1675
+#: install-methods.xml:1676
 #, no-c-format
-msgid "The preconfiguration file is in the format used by the debconf-set-selections command. A well documented and working example that you can edit is in <xref linkend=\"example-preseed\"/>."
+msgid ""
+"The preconfiguration file is in the format used by the debconf-set-"
+"selections command. A well documented and working example that you can edit "
+"is in <xref linkend=\"example-preseed\"/>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1681
+#: install-methods.xml:1682
 #, no-c-format
 msgid ""
-"Alternatively, one way to get a complete file listing all the values that can be preseeded is to do a manual install, and then use <filename>debconf-get-selections</filename>, from the <classname>debconf-utils</classname> package, to dump both the debconf database and the cdebconf database in /var/log/debian-installer/cdebconf to a single file: <informalexample><screen>\n"
+"Alternatively, one way to get a complete file listing all the values that "
+"can be preseeded is to do a manual install, and then use <filename>debconf-"
+"get-selections</filename>, from the <classname>debconf-utils</classname> "
+"package, to dump both the debconf database and the cdebconf database in /var/"
+"log/debian-installer/cdebconf to a single file: <informalexample><screen>\n"
 "$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
 "$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>\n"
-"</screen></informalexample> However, a file generated in this manner will have some items that should not be preseeded, and the file in <xref linkend=\"example-preseed\"/> is a better starting place for most users."
+"</screen></informalexample> However, a file generated in this manner will "
+"have some items that should not be preseeded, and the file in <xref linkend="
+"\"example-preseed\"/> is a better starting place for most users."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1696
+#: install-methods.xml:1697
 #, no-c-format
-msgid "Once you have a preconfiguration file, you can edit it if necessary, and place it on a web server, or copy it onto the installer's boot media. Wherever you place the file, you need to pass a parameter to the installer at boot time to tell it to use the file."
+msgid ""
+"Once you have a preconfiguration file, you can edit it if necessary, and "
+"place it on a web server, or copy it onto the installer's boot media. "
+"Wherever you place the file, you need to pass a parameter to the installer "
+"at boot time to tell it to use the file."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1703
+#: install-methods.xml:1704
 #, no-c-format
-msgid "To make the installer use a preconfiguration file downloaded from the network, add preseed/url=http://url/to/preseed.cfg to the kernel boot parameters. Of course the preconfiguration will not take effect until the installer manages to set up the network to download the file, so this is most useful if the installer can set up the network via DHCP without asking any questions. You may want to set the installation priority to critical to avoid any questions while the network is being configured. See <xref linkend=\"installer-args\"/>."
+msgid ""
+"To make the installer use a preconfiguration file downloaded from the "
+"network, add preseed/url=http://url/to/preseed.cfg to the kernel boot "
+"parameters. Of course the preconfiguration will not take effect until the "
+"installer manages to set up the network to download the file, so this is "
+"most useful if the installer can set up the network via DHCP without asking "
+"any questions. You may want to set the installation priority to critical to "
+"avoid any questions while the network is being configured. See <xref linkend="
+"\"installer-args\"/>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1714
+#: install-methods.xml:1715
 #, no-c-format
-msgid "To place a preconfiguration file on a CD, you would need to remaster the ISO image to include your preconfiguration file. See the manual page for mkisofs for details. Alternatively, put the preseed file on a floppy, and use preseed/file=/floppy/preseed.cfg"
+msgid ""
+"To place a preconfiguration file on a CD, you would need to remaster the ISO "
+"image to include your preconfiguration file. See the manual page for mkisofs "
+"for details. Alternatively, put the preseed file on a floppy, and use "
+"preseed/file=/floppy/preseed.cfg"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1721
+#: install-methods.xml:1722
 #, no-c-format
-msgid "If you'll be booting from a USB memory stick, then you can simply copy your preconfiguration file onto the memory stick's filesystem, and edit the syslinux.cfg file to add preseed/file=/hd-media/preseed.cfg to the kernel boot parameters."
+msgid ""
+"If you'll be booting from a USB memory stick, then you can simply copy your "
+"preconfiguration file onto the memory stick's filesystem, and edit the "
+"syslinux.cfg file to add preseed/file=/hd-media/preseed.cfg to the kernel "
+"boot parameters."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1731
+#: install-methods.xml:1732
 #, no-c-format
 msgid "Using Preseeding to Change Default Values"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1732
+#: install-methods.xml:1733
 #, no-c-format
-msgid "It is also possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a template."
+msgid ""
+"It is also possible to use preseeding to change the default answer for a "
+"question, but still have the question asked. To do this the <firstterm>seen</"
+"firstterm> flag must be reset to <quote>false</quote> after setting the "
+"value for a template."
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:1739
+#: install-methods.xml:1740
 #, no-c-format
 msgid ""
 "d-i foo/bar string value\n"
 "d-i foo/bar seen false"
 msgstr ""
-
diff --git a/po/sv/post-install.po b/po/sv/post-install.po
index 3d39db45f..5eac2a7dd 100755
--- a/po/sv/post-install.po
+++ b/po/sv/post-install.po
@@ -10,7 +10,7 @@ msgstr ""
 "Last-Translator: Daniel Nylander <po@danielnylander.se>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
 "MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=iso-8859-1\n"
+"Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
 #. Tag: title
@@ -23,30 +23,49 @@ msgstr ""
 #: post-install.xml:13
 #, no-c-format
 msgid "If You Are New to Unix"
-msgstr "Om du är nybörjare i Unix"
+msgstr "Om du är nybörjare i Unix"
 
 #. Tag: para
 #: post-install.xml:14
 #, no-c-format
-msgid "If you are new to Unix, you probably should go out and buy some books and do some reading. A lot of valuable information can also be found in the <ulink url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url=\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet documents which provide a nice historical reference."
+msgid ""
+"If you are new to Unix, you probably should go out and buy some books and do "
+"some reading. A lot of valuable information can also be found in the <ulink "
+"url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url="
+"\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet "
+"documents which provide a nice historical reference."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:22
 #, no-c-format
-msgid "Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux Documentation Project (LDP)</ulink> collects a number of HOWTOs and online books relating to Linux. Most of these documents can be installed locally; just install the <classname>doc-linux-html</classname> package (HTML versions) or the <classname>doc-linux-text</classname> package (ASCII versions), then look in <filename>/usr/share/doc/HOWTO</filename>. International versions of the LDP HOWTOs are also available as Debian packages."
+msgid ""
+"Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux "
+"Documentation Project (LDP)</ulink> collects a number of HOWTOs and online "
+"books relating to Linux. Most of these documents can be installed locally; "
+"just install the <classname>doc-linux-html</classname> package (HTML "
+"versions) or the <classname>doc-linux-text</classname> package (ASCII "
+"versions), then look in <filename>/usr/share/doc/HOWTO</filename>. "
+"International versions of the LDP HOWTOs are also available as Debian "
+"packages."
 msgstr ""
 
 #. Tag: title
 #: post-install.xml:43
 #, fuzzy, no-c-format
 msgid "Orienting Yourself to Debian"
-msgstr "Debianutgåva som ska användas:"
+msgstr "Debianutgåva som ska användas:"
 
 #. Tag: para
 #: post-install.xml:44
 #, no-c-format
-msgid "Debian is a little different from other distributions. Even if you're familiar with Linux in other distributions, there are things you should know about Debian to help you to keep your system in a good, clean state. This chapter contains material to help you get oriented; it is not intended to be a tutorial for how to use Debian, but just a very brief glimpse of the system for the very rushed."
+msgid ""
+"Debian is a little different from other distributions. Even if you're "
+"familiar with Linux in other distributions, there are things you should know "
+"about Debian to help you to keep your system in a good, clean state. This "
+"chapter contains material to help you get oriented; it is not intended to be "
+"a tutorial for how to use Debian, but just a very brief glimpse of the "
+"system for the very rushed."
 msgstr ""
 
 #. Tag: title
@@ -58,49 +77,86 @@ msgstr "Konfiguration av grundsystemet"
 #. Tag: para
 #: post-install.xml:56
 #, no-c-format
-msgid "The most important concept to grasp is the Debian packaging system. In essence, large parts of your system should be considered under the control of the packaging system. These include: <itemizedlist> <listitem><para> <filename>/usr</filename> (excluding <filename>/usr/local</filename>) </para></listitem> <listitem><para> <filename>/var</filename> (you could make <filename>/var/local</filename> and be safe in there) </para></listitem> <listitem><para> <filename>/bin</filename> </para></listitem> <listitem><para> <filename>/sbin</filename> </para></listitem> <listitem><para> <filename>/lib</filename> </para></listitem> </itemizedlist> For instance, if you replace <filename>/usr/bin/perl</filename>, that will work, but then if you upgrade your <classname>perl</classname> package, the file you put there will be replaced. Experts can get around this by putting packages on <quote>hold</quote> in <command>aptitude</command>."
+msgid ""
+"The most important concept to grasp is the Debian packaging system. In "
+"essence, large parts of your system should be considered under the control "
+"of the packaging system. These include: <itemizedlist> <listitem><para> "
+"<filename>/usr</filename> (excluding <filename>/usr/local</filename>) </"
+"para></listitem> <listitem><para> <filename>/var</filename> (you could make "
+"<filename>/var/local</filename> and be safe in there) </para></listitem> "
+"<listitem><para> <filename>/bin</filename> </para></listitem> "
+"<listitem><para> <filename>/sbin</filename> </para></listitem> "
+"<listitem><para> <filename>/lib</filename> </para></listitem> </"
+"itemizedlist> For instance, if you replace <filename>/usr/bin/perl</"
+"filename>, that will work, but then if you upgrade your <classname>perl</"
+"classname> package, the file you put there will be replaced. Experts can get "
+"around this by putting packages on <quote>hold</quote> in <command>aptitude</"
+"command>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:97
 #, no-c-format
-msgid "One of the best installation methods is apt. You can use the command line version <command>apt-get</command> or full-screen text version <application>aptitude</application>. Note apt will also let you merge main, contrib, and non-free so you can have export-restricted packages as well as standard versions."
+msgid ""
+"One of the best installation methods is apt. You can use the command line "
+"version <command>apt-get</command> or full-screen text version "
+"<application>aptitude</application>. Note apt will also let you merge main, "
+"contrib, and non-free so you can have export-restricted packages as well as "
+"standard versions."
 msgstr ""
 
 #. Tag: title
 #: post-install.xml:108
 #, fuzzy, no-c-format
 msgid "Application Version Management"
-msgstr "Stadsförvaltning"
+msgstr "Stadsförvaltning"
 
 #. Tag: para
 #: post-install.xml:109
 #, no-c-format
-msgid "Alternative versions of applications are managed by update-alternatives. If you are maintaining multiple versions of your applications, read the update-alternatives man page."
+msgid ""
+"Alternative versions of applications are managed by update-alternatives. If "
+"you are maintaining multiple versions of your applications, read the update-"
+"alternatives man page."
 msgstr ""
 
 #. Tag: title
 #: post-install.xml:119
 #, fuzzy, no-c-format
 msgid "Cron Job Management"
-msgstr "Stadsförvaltning"
+msgstr "Stadsförvaltning"
 
 #. Tag: para
 #: post-install.xml:120
 #, no-c-format
-msgid "Any jobs under the purview of the system administrator should be in <filename>/etc</filename>, since they are configuration files. If you have a root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/etc/crontab</filename>, and will run in alphabetic order, which serializes them."
+msgid ""
+"Any jobs under the purview of the system administrator should be in "
+"<filename>/etc</filename>, since they are configuration files. If you have a "
+"root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/"
+"cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/"
+"etc/crontab</filename>, and will run in alphabetic order, which serializes "
+"them."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:129
 #, no-c-format
-msgid "On the other hand, if you have a cron job that (a) needs to run as a special user, or (b) needs to run at a special time or frequency, you can use either <filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/whatever</filename>. These particular files also have an extra field that allows you to stipulate the user under which the cron job runs."
+msgid ""
+"On the other hand, if you have a cron job that (a) needs to run as a special "
+"user, or (b) needs to run at a special time or frequency, you can use either "
+"<filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/"
+"whatever</filename>. These particular files also have an extra field that "
+"allows you to stipulate the user under which the cron job runs."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:138
 #, no-c-format
-msgid "In either case, you just edit the files and cron will notice them automatically. There is no need to run a special command. For more information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/README.Debian</filename>."
+msgid ""
+"In either case, you just edit the files and cron will notice them "
+"automatically. There is no need to run a special command. For more "
+"information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/"
+"README.Debian</filename>."
 msgstr ""
 
 #. Tag: title
@@ -112,100 +168,172 @@ msgstr "Windows/DOS OEM (CP 437)"
 #. Tag: para
 #: post-install.xml:156
 #, no-c-format
-msgid "After installing the base system and writing to the <emphasis>Master Boot Record</emphasis>, you will be able to boot Linux, but probably nothing else. This depends what you have chosen during the installation. This chapter will describe how you can reactivate your old systems so that you can also boot your DOS or Windows again."
+msgid ""
+"After installing the base system and writing to the <emphasis>Master Boot "
+"Record</emphasis>, you will be able to boot Linux, but probably nothing "
+"else. This depends what you have chosen during the installation. This "
+"chapter will describe how you can reactivate your old systems so that you "
+"can also boot your DOS or Windows again."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:164
 #, no-c-format
-msgid "<command>LILO</command> is a boot manager with which you can also boot other operating systems than Linux, which complies to PC conventions. The boot manager is configured via <filename>/etc/lilo.conf</filename> file. Whenever you edited this file you have to run <command>lilo</command> afterwards. The reason for this is that the changes will take place only when you call the program."
+msgid ""
+"<command>LILO</command> is a boot manager with which you can also boot other "
+"operating systems than Linux, which complies to PC conventions. The boot "
+"manager is configured via <filename>/etc/lilo.conf</filename> file. Whenever "
+"you edited this file you have to run <command>lilo</command> afterwards. The "
+"reason for this is that the changes will take place only when you call the "
+"program."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:174
 #, no-c-format
-msgid "Important parts of the <filename>lilo.conf</filename> file are the lines containing the <userinput>image</userinput> and <userinput>other</userinput> keywords, as well as the lines following those. They can be used to describe a system which can be booted by <command>LILO</command>. Such a system can include a kernel (<userinput>image</userinput>), a root partition, additional kernel parameters, etc. as well as a configuration to boot another, non-Linux (<userinput>other</userinput>) operating system. These keywords can also be used more than once. The ordering of these systems within the configuration file is important because it determines which system will be booted automatically after, for instance, a timeout (<userinput>delay</userinput>) presuming <command>LILO</command> wasn't stopped by pressing the <keycap>shift</keycap> key."
+msgid ""
+"Important parts of the <filename>lilo.conf</filename> file are the lines "
+"containing the <userinput>image</userinput> and <userinput>other</userinput> "
+"keywords, as well as the lines following those. They can be used to describe "
+"a system which can be booted by <command>LILO</command>. Such a system can "
+"include a kernel (<userinput>image</userinput>), a root partition, "
+"additional kernel parameters, etc. as well as a configuration to boot "
+"another, non-Linux (<userinput>other</userinput>) operating system. These "
+"keywords can also be used more than once. The ordering of these systems "
+"within the configuration file is important because it determines which "
+"system will be booted automatically after, for instance, a timeout "
+"(<userinput>delay</userinput>) presuming <command>LILO</command> wasn't "
+"stopped by pressing the <keycap>shift</keycap> key."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:190
 #, no-c-format
 msgid ""
-"After a fresh install of Debian, just the current system is configured for booting with <command>LILO</command>. If you want to boot another Linux kernel, you have to edit the configuration file <filename>/etc/lilo.conf</filename> to add the following lines: <informalexample><screen>\n"
+"After a fresh install of Debian, just the current system is configured for "
+"booting with <command>LILO</command>. If you want to boot another Linux "
+"kernel, you have to edit the configuration file <filename>/etc/lilo.conf</"
+"filename> to add the following lines: <informalexample><screen>\n"
 "&additional-lilo-image;\n"
-"</screen></informalexample> For a basic setup just the first two lines are necessary. If you want to know more about the other two options please have a look at the <command>LILO</command> documentation. This can be found in <filename>/usr/share/doc/lilo/</filename>. The file which should be read is <filename>Manual.txt</filename>. To have a quicker start into the world of booting a system you can also look at the <command>LILO</command> man pages <filename>lilo.conf</filename> for an overview of configuration keywords and <filename>lilo</filename> for description of the installation of the new configuration into the boot sector."
+"</screen></informalexample> For a basic setup just the first two lines are "
+"necessary. If you want to know more about the other two options please have "
+"a look at the <command>LILO</command> documentation. This can be found in "
+"<filename>/usr/share/doc/lilo/</filename>. The file which should be read is "
+"<filename>Manual.txt</filename>. To have a quicker start into the world of "
+"booting a system you can also look at the <command>LILO</command> man pages "
+"<filename>lilo.conf</filename> for an overview of configuration keywords and "
+"<filename>lilo</filename> for description of the installation of the new "
+"configuration into the boot sector."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:210
 #, no-c-format
-msgid "Notice that there are other boot loaders available in &debian;, such as GRUB (in <classname>grub</classname> package), CHOS (in <classname>chos</classname> package), Extended-IPL (in <classname>extipl</classname> package), loadlin (in <classname>loadlin</classname> package) etc."
+msgid ""
+"Notice that there are other boot loaders available in &debian;, such as GRUB "
+"(in <classname>grub</classname> package), CHOS (in <classname>chos</"
+"classname> package), Extended-IPL (in <classname>extipl</classname> "
+"package), loadlin (in <classname>loadlin</classname> package) etc."
 msgstr ""
 
 #. Tag: title
 #: post-install.xml:225
 #, fuzzy, no-c-format
 msgid "Further Reading and Information"
-msgstr "ingen mer information tillgänglig"
+msgstr "ingen mer information tillgänglig"
 
 #. Tag: para
 #: post-install.xml:226
 #, no-c-format
-msgid "If you need information about a particular program, you should first try <userinput>man <replaceable>program</replaceable></userinput>, or <userinput>info <replaceable>program</replaceable></userinput>."
+msgid ""
+"If you need information about a particular program, you should first try "
+"<userinput>man <replaceable>program</replaceable></userinput>, or "
+"<userinput>info <replaceable>program</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:232
 #, no-c-format
-msgid "There is lots of useful documentation in <filename>/usr/share/doc</filename> as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and <filename>/usr/share/doc/FAQ</filename> contain lots of interesting information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</filename>. To read about Debian-specific issues for particular programs, look at <filename>/usr/share/doc/(package name)/README.Debian</filename>."
+msgid ""
+"There is lots of useful documentation in <filename>/usr/share/doc</filename> "
+"as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and "
+"<filename>/usr/share/doc/FAQ</filename> contain lots of interesting "
+"information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</"
+"filename>. To read about Debian-specific issues for particular programs, "
+"look at <filename>/usr/share/doc/(package name)/README.Debian</filename>."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:243
 #, no-c-format
-msgid "The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a large quantity of documentation about Debian. In particular, see the <ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference\">Debian Reference</ulink>. An index of more Debian documentation is available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian Documentation Project</ulink>. The Debian community is self-supporting; to subscribe to one or more of the Debian mailing lists, see the <ulink url=\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/\">Debian Mailing List Archives</ulink> contain a wealth of information on Debian."
+msgid ""
+"The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a "
+"large quantity of documentation about Debian. In particular, see the <ulink "
+"url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> and the "
+"<ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference\">Debian "
+"Reference</ulink>. An index of more Debian documentation is available from "
+"the <ulink url=\"http://www.debian.org/doc/ddp\">Debian Documentation "
+"Project</ulink>. The Debian community is self-supporting; to subscribe to "
+"one or more of the Debian mailing lists, see the <ulink url=\"http://www."
+"debian.org/MailingLists/subscribe\"> Mail List Subscription</ulink> page. "
+"Last, but not least, the <ulink url=\"http://lists.debian.org/\">Debian "
+"Mailing List Archives</ulink> contain a wealth of information on Debian."
 msgstr ""
 
 #. Tag: para
 #: post-install.xml:261
 #, no-c-format
-msgid "A general source of information on GNU/Linux is the <ulink url=\"http://www.tldp.org/\">Linux Documentation Project</ulink>. There you will find the HOWTOs and pointers to other very valuable information on parts of a GNU/Linux system."
+msgid ""
+"A general source of information on GNU/Linux is the <ulink url=\"http://www."
+"tldp.org/\">Linux Documentation Project</ulink>. There you will find the "
+"HOWTOs and pointers to other very valuable information on parts of a GNU/"
+"Linux system."
 msgstr ""
 
 #. Tag: title
 #: post-install.xml:276
 #, fuzzy, no-c-format
 msgid "Compiling a New Kernel"
-msgstr "Egen kärnkompilering"
+msgstr "Egen kärnkompilering"
 
 #. Tag: para
 #: post-install.xml:277
 #, no-c-format
-msgid "Why would someone want to compile a new kernel? It is often not necessary since the default kernel shipped with Debian handles most configurations. However, it is useful to compile a new kernel in order to:"
+msgid ""
+"Why would someone want to compile a new kernel? It is often not necessary "
+"since the default kernel shipped with Debian handles most configurations. "
+"Also, Debian often offers several alternative kernels. So you may want to "
+"check first if there is an alternative kernel image package that better "
+"corresponds to your hardware. However, it can be useful to compile a new "
+"kernel in order to:"
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:285
+#: post-install.xml:287
 #, no-c-format
-msgid "handle special hardware needs, or hardware conflicts with the pre-supplied kernels"
+msgid ""
+"handle special hardware needs, or hardware conflicts with the pre-supplied "
+"kernels"
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:291
+#: post-install.xml:293
 #, no-c-format
-msgid "handle hardware or options not included in the stock kernel, such as APM or SMP"
+msgid ""
+"use options of the kernel which are not supported in the pre-supplied "
+"kernels (such as high memory support)"
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:297
+#: post-install.xml:299
 #, no-c-format
 msgid "optimize the kernel by removing useless drivers to speed up boot time"
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:303
+#: post-install.xml:304
 #, no-c-format
-msgid "use options of the kernel which are not supported by the default kernel (such as high memory support)"
+msgid "create a monolithic instead of a modularized kernel"
 msgstr ""
 
 #. Tag: para
@@ -217,14 +345,14 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:314
 #, no-c-format
-msgid "impress your friends, try new things"
+msgid "learn more about linux kernels"
 msgstr ""
 
 #. Tag: title
 #: post-install.xml:323
 #, fuzzy, no-c-format
 msgid "Kernel Image Management"
-msgstr "Stadsförvaltning"
+msgstr "Stadsförvaltning"
 
 #. Tag: para
 #: post-install.xml:324
@@ -235,120 +363,239 @@ msgstr ""
 #. Tag: para
 #: post-install.xml:328
 #, no-c-format
-msgid "To compile a kernel the Debian way, you need some packages: <classname>kernel-package</classname>, <classname>kernel-source-&kernelversion;</classname> (the most recent version at the time of this writing), <classname>fakeroot</classname> and a few others which are probably already installed (see <filename>/usr/share/doc/kernel-package/README.gz</filename> for the complete list)."
+msgid ""
+"To compile a kernel the Debian way, you need some packages: "
+"<classname>fakeroot</classname>, <classname>kernel-package</classname>, "
+"<phrase condition=\"classic-kpkg\"><classname>kernel-source-&kernelversion;</"
+"classname> (the most recent version at the time of this writing)</phrase> "
+"<phrase condition=\"common-kpkg\"><classname>linux-source-2.6</classname></"
+"phrase> and a few others which are probably already installed (see "
+"<filename>/usr/share/doc/kernel-package/README.gz</filename> for the "
+"complete list)."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:338
+#: post-install.xml:339
 #, no-c-format
-msgid "This method will make a .deb of your kernel source, and, if you have non-standard modules, make a synchronized dependent .deb of those too. It's a better way to manage kernel images; <filename>/boot</filename> will hold the kernel, the System.map, and a log of the active config file for the build."
+msgid ""
+"This method will make a .deb of your kernel source, and, if you have non-"
+"standard modules, make a synchronized dependent .deb of those too. It's a "
+"better way to manage kernel images; <filename>/boot</filename> will hold the "
+"kernel, the System.map, and a log of the active config file for the build."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:346
+#: post-install.xml:347
 #, no-c-format
-msgid "Note that you don't <emphasis>have</emphasis> to compile your kernel the <quote>Debian way</quote>; but we find that using the packaging system to manage your kernel is actually safer and easier. In fact, you can get your kernel sources right from Linus instead of <classname>kernel-source-&kernelversion;</classname>, yet still use the <classname>kernel-package</classname> compilation method."
+msgid ""
+"Note that you don't <emphasis>have</emphasis> to compile your kernel the "
+"<quote>Debian way</quote>; but we find that using the packaging system to "
+"manage your kernel is actually safer and easier. In fact, you can get your "
+"kernel sources right from Linus instead of <phrase condition=\"classic-kpkg"
+"\"><classname>kernel-source-&kernelversion;</classname>,</phrase> <phrase "
+"condition=\"common-kpkg\"><classname>linux-source-2.6</classname>,</phrase> "
+"yet still use the <classname>kernel-package</classname> compilation method."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:355
+#: post-install.xml:357
 #, no-c-format
-msgid "Note that you'll find complete documentation on using <classname>kernel-package</classname> under <filename>/usr/share/doc/kernel-package</filename>. This section just contains a brief tutorial."
+msgid ""
+"Note that you'll find complete documentation on using <classname>kernel-"
+"package</classname> under <filename>/usr/share/doc/kernel-package</"
+"filename>. This section just contains a brief tutorial."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:362
+#: post-install.xml:364
 #, no-c-format
-msgid "Hereafter, we'll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory<footnote> <para> There are other locations where you can extract kernel sources and build your custom kernel, but this is easiest as it does not require special permissions. </para> </footnote>. We'll also assume that your kernel version is &kernelversion;. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using <userinput>tar xjf /usr/src/kernel-source-&kernelversion;.tar.bz2</userinput> and change to the directory <filename>kernel-source-&kernelversion;</filename> that will have been created."
+msgid ""
+"Hereafter, we'll assume you have free rein over your machine and will "
+"extract your kernel source to somewhere in your home directory<footnote> "
+"<para> There are other locations where you can extract kernel sources and "
+"build your custom kernel, but this is easiest as it does not require special "
+"permissions. </para> </footnote>. We'll also assume that your kernel version "
+"is &kernelversion;. Make sure you are in the directory to where you want to "
+"unpack the kernel sources, extract them using <phrase condition=\"classic-"
+"kpkg\"><userinput>tar xjf /usr/src/kernel-source-&kernelversion;.tar.bz2</"
+"userinput></phrase> <phrase condition=\"common-kpkg\"><userinput>tar xjf /"
+"usr/src/linux-source-&kernelversion;.tar.bz2</userinput></phrase> and change "
+"to the directory <phrase condition=\"classic-kpkg\"><filename>kernel-source-"
+"&kernelversion;</filename></phrase> <phrase condition=\"common-kpkg"
+"\"><filename>linux-source-&kernelversion;</filename></phrase> that will have "
+"been created."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:382
+#: post-install.xml:389
 #, no-c-format
-msgid "Now, you can configure your kernel. Run <userinput>make xconfig</userinput> if X11 is installed, configured and being run; run <userinput>make menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</classname> installed). Take the time to read the online help and choose carefully. When in doubt, it is typically better to include the device driver (the software which manages hardware peripherals, such as Ethernet cards, SCSI controllers, and so on) you are unsure about. Be careful: other options, not related to a specific hardware, should be left at the default value if you do not understand them. Do not forget to select <quote>Kernel module loader</quote> in <quote>Loadable module support</quote> (it is not selected by default). If not included, your Debian installation will experience problems."
+msgid ""
+"Now, you can configure your kernel. Run <userinput>make xconfig</userinput> "
+"if X11 is installed, configured and being run; run <userinput>make "
+"menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</"
+"classname> installed). Take the time to read the online help and choose "
+"carefully. When in doubt, it is typically better to include the device "
+"driver (the software which manages hardware peripherals, such as Ethernet "
+"cards, SCSI controllers, and so on) you are unsure about. Be careful: other "
+"options, not related to a specific hardware, should be left at the default "
+"value if you do not understand them. Do not forget to select <quote>Kernel "
+"module loader</quote> in <quote>Loadable module support</quote> (it is not "
+"selected by default). If not included, your Debian installation will "
+"experience problems."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:397
+#: post-install.xml:404
 #, no-c-format
-msgid "Clean the source tree and reset the <classname>kernel-package</classname> parameters. To do that, do <userinput>make-kpkg clean</userinput>."
+msgid ""
+"Clean the source tree and reset the <classname>kernel-package</classname> "
+"parameters. To do that, do <userinput>make-kpkg clean</userinput>."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:402
+#: post-install.xml:409
 #, no-c-format
-msgid "Now, compile the kernel: <userinput>fakeroot make-kpkg --revision=custom.1.0 kernel_image</userinput>. The version number of <quote>1.0</quote> can be changed at will; this is just a version number that you will use to track your kernel builds. Likewise, you can put any word you like in place of <quote>custom</quote> (e.g., a host name). Kernel compilation may take quite a while, depending on the power of your machine."
+msgid ""
+"Now, compile the kernel: <userinput>fakeroot make-kpkg --revision=custom.1.0 "
+"kernel_image</userinput>. The version number of <quote>1.0</quote> can be "
+"changed at will; this is just a version number that you will use to track "
+"your kernel builds. Likewise, you can put any word you like in place of "
+"<quote>custom</quote> (e.g., a host name). Kernel compilation may take quite "
+"a while, depending on the power of your machine."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:412
+#: post-install.xml:419
 #, no-c-format
-msgid "If you require PCMCIA support, you'll also need to install the <classname>pcmcia-source</classname> package. Unpack the gzipped tar file as root in the directory <filename>/usr/src</filename> (it's important that modules are found where they are expected to be found, namely, <filename>/usr/src/modules</filename>). Then, as root, do <userinput>make-kpkg modules_image</userinput>."
+msgid ""
+"If you require PCMCIA support, you'll also need to install the "
+"<classname>pcmcia-source</classname> package. Unpack the gzipped tar file as "
+"root in the directory <filename>/usr/src</filename> (it's important that "
+"modules are found where they are expected to be found, namely, <filename>/"
+"usr/src/modules</filename>). Then, as root, do <userinput>make-kpkg "
+"modules_image</userinput>."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:421
+#: post-install.xml:428
 #, no-c-format
-msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <userinput>dpkg -i ../kernel-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>i586</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i kernel-image...</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new <classname>kernel-image-&kernelversion;</classname> package is also clever enough to automatically use your platform's boot-loader to run an update on the booting, allowing you to boot without re-running the boot loader. If you have created a modules package, e.g., if you have PCMCIA, you'll need to install that package as well."
-msgstr ""
-
-#. Tag: para
-#: post-install.xml:442
+msgid ""
+"Once the compilation is complete, you can install your custom kernel like "
+"any package. As root, do <userinput>dpkg -i ../kernel-image-&kernelversion;-"
+"<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</"
+"userinput>. The <replaceable>subarchitecture</replaceable> part is an "
+"optional sub-architecture, <phrase arch=\"i386\"> such as <quote>i586</"
+"quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -"
+"i kernel-image...</userinput> will install the kernel, along with some other "
+"nice supporting files. For instance, the <filename>System.map</filename> "
+"will be properly installed (helpful for debugging kernel problems), and "
+"<filename>/boot/config-&kernelversion;</filename> will be installed, "
+"containing your current configuration set. Your new <classname>kernel-image-"
+"&kernelversion;</classname> package is also clever enough to automatically "
+"use your platform's boot-loader to run an update on the booting, allowing "
+"you to boot without re-running the boot loader. If you have created a "
+"modules package, e.g., if you have PCMCIA, you'll need to install that "
+"package as well."
+msgstr ""
+
+#. Tag: para
+#: post-install.xml:449
 #, no-c-format
-msgid "It is time to reboot the system: read carefully any warning that the above step may have produced, then <userinput>shutdown -r now</userinput>."
+msgid ""
+"It is time to reboot the system: read carefully any warning that the above "
+"step may have produced, then <userinput>shutdown -r now</userinput>."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:447
+#: post-install.xml:454
 #, no-c-format
-msgid "For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>."
+msgid ""
+"<phrase condition=\"etch\">For more information on Debian kernels and kernel "
+"compilation, see the <ulink url=\"&url-kernel-handbook;\">Debian Linux "
+"Kernel Handbook</ulink>.</phrase> For more information on <classname>kernel-"
+"package</classname>, read the fine documentation in <filename>/usr/share/doc/"
+"kernel-package</filename>."
 msgstr ""
 
 #. Tag: title
-#: post-install.xml:461
+#: post-install.xml:471
 #, fuzzy, no-c-format
 msgid "Recovering a Broken System"
 msgstr "Konfiguration av grundsystemet"
 
 #. Tag: para
-#: post-install.xml:462
+#: post-install.xml:472
 #, no-c-format
-msgid "Sometimes, things go wrong, and the system you've carefully installed is no longer bootable. Perhaps the boot loader configuration broke while trying out a change, or perhaps a new kernel you installed won't boot, or perhaps cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</filename>. Regardless of the cause, you'll need to have a system to work from while you fix it, and rescue mode can be useful for this."
+msgid ""
+"Sometimes, things go wrong, and the system you've carefully installed is no "
+"longer bootable. Perhaps the boot loader configuration broke while trying "
+"out a change, or perhaps a new kernel you installed won't boot, or perhaps "
+"cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</"
+"filename>. Regardless of the cause, you'll need to have a system to work "
+"from while you fix it, and rescue mode can be useful for this."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:472
+#: post-install.xml:482
 #, no-c-format
-msgid "To access rescue mode, type <userinput>rescue</userinput> at the <prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/enable=true</userinput> boot parameter. You'll be shown the first few screens of the installer, with a note in the corner of the display to indicate that this is rescue mode, not a full installation. Don't worry, your system is not about to be overwritten! Rescue mode simply takes advantage of the hardware detection facilities available in the installer to ensure that your disks, network devices, and so on are available to you while repairing your system."
+msgid ""
+"To access rescue mode, type <userinput>rescue</userinput> at the "
+"<prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/"
+"enable=true</userinput> boot parameter. You'll be shown the first few "
+"screens of the installer, with a note in the corner of the display to "
+"indicate that this is rescue mode, not a full installation. Don't worry, "
+"your system is not about to be overwritten! Rescue mode simply takes "
+"advantage of the hardware detection facilities available in the installer to "
+"ensure that your disks, network devices, and so on are available to you "
+"while repairing your system."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:487
+#: post-install.xml:497
 #, no-c-format
-msgid "Instead of the partitioning tool, you should now be presented with a list of the partitions on your system, and asked to select one of them. Normally, you should select the partition containing the root file system that you need to repair. You may select partitions on RAID and LVM devices as well as those created directly on disks."
+msgid ""
+"Instead of the partitioning tool, you should now be presented with a list of "
+"the partitions on your system, and asked to select one of them. Normally, "
+"you should select the partition containing the root file system that you "
+"need to repair. You may select partitions on RAID and LVM devices as well as "
+"those created directly on disks."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:495
+#: post-install.xml:505
 #, no-c-format
-msgid "If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. <phrase arch=\"i386\"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. </phrase>"
+msgid ""
+"If possible, the installer will now present you with a shell prompt in the "
+"file system you selected, which you can use to perform any necessary "
+"repairs. <phrase arch=\"i386\"> For example, if you need to reinstall the "
+"GRUB boot loader into the master boot record of the first hard disk, you "
+"could enter the command <userinput>grub-install '(hd0)'</userinput> to do "
+"so. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:507
+#: post-install.xml:517
 #, no-c-format
-msgid "If the installer cannot run a usable shell in the root file system you selected, perhaps because the file system is corrupt, then it will issue a warning and offer to give you a shell in the installer environment instead. You may not have as many tools available in this environment, but they will often be enough to repair your system anyway. The root file system you selected will be mounted on the <filename>/target</filename> directory."
+msgid ""
+"If the installer cannot run a usable shell in the root file system you "
+"selected, perhaps because the file system is corrupt, then it will issue a "
+"warning and offer to give you a shell in the installer environment instead. "
+"You may not have as many tools available in this environment, but they will "
+"often be enough to repair your system anyway. The root file system you "
+"selected will be mounted on the <filename>/target</filename> directory."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:516
+#: post-install.xml:526
 #, no-c-format
 msgid "In either case, after you exit the shell, the system will reboot."
 msgstr ""
 
 #. Tag: para
-#: post-install.xml:520
+#: post-install.xml:530
 #, no-c-format
-msgid "Finally, note that repairing broken systems can be difficult, and this manual does not attempt to go into all the things that might have gone wrong or how to fix them. If you have problems, consult an expert."
+msgid ""
+"Finally, note that repairing broken systems can be difficult, and this "
+"manual does not attempt to go into all the things that might have gone wrong "
+"or how to fix them. If you have problems, consult an expert."
 msgstr ""
-
diff --git a/po/sv/random-bits.po b/po/sv/random-bits.po
index 4173fa37e..b3f920791 100755
--- a/po/sv/random-bits.po
+++ b/po/sv/random-bits.po
@@ -10,7 +10,7 @@ msgstr ""
 "Last-Translator: Daniel Nylander <po@danielnylander.se>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
 "MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=iso-8859-1\n"
+"Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
 #. Tag: title
@@ -23,24 +23,35 @@ msgstr "_Packa bitar"
 #: random-bits.xml:11
 #, fuzzy, no-c-format
 msgid "Preconfiguration File Example"
-msgstr "Misslyckades med att hämta förkonfigurationsfilen"
+msgstr "Misslyckades med att hämta förkonfigurationsfilen"
 
 #. Tag: para
 #: random-bits.xml:13
 #, no-c-format
-msgid "This is a complete working example of a preconfiguration file for an automated install. Its use is explained in <xref linkend=\"automatic-install\"/>. You may want to uncomment some of the lines before using the file."
+msgid ""
+"This is a complete working example of a preconfiguration file for an "
+"automated install. Its use is explained in <xref linkend=\"automatic-install"
+"\"/>. You may want to uncomment some of the lines before using the file."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:21
 #, no-c-format
-msgid "In order to be able to properly present this example in the manual, we've had to split some lines. This is indicated by the use of the line-continuation-character <quote>\\</quote> and extra indentation in the next line. In a real preconfiguration file, these split lines have to be joined into <emphasis>one single line</emphasis>. If you do not, preconfiguration will fail with unpredictable results."
+msgid ""
+"In order to be able to properly present this example in the manual, we've "
+"had to split some lines. This is indicated by the use of the line-"
+"continuation-character <quote>\\</quote> and extra indentation in the next "
+"line. In a real preconfiguration file, these split lines have to be joined "
+"into <emphasis>one single line</emphasis>. If you do not, preconfiguration "
+"will fail with unpredictable results."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:29
 #, no-c-format
-msgid "A <quote>clean</quote> example file is available from &urlset-example-preseed;."
+msgid ""
+"A <quote>clean</quote> example file is available from &urlset-example-"
+"preseed;."
 msgstr ""
 
 #. Tag: para
@@ -84,7 +95,8 @@ msgid ""
 "#\n"
 "# While you're at it, you may want to throw a debconf/priority=critical in\n"
 "# there, to avoid most questions even if the preseeding below misses some.\n"
-"# And you might set the timeout to 1 in syslinux.cfg to avoid needing to hit\n"
+"# And you might set the timeout to 1 in syslinux.cfg to avoid needing to "
+"hit\n"
 "# enter to boot the installer.\n"
 "#\n"
 "# Note that the kernel accepts a maximum of 8 command line options and\n"
@@ -163,7 +175,8 @@ msgid ""
 "#d-i partman-auto/choose_recipe select Multi-user workstation\n"
 "\n"
 "# Or provide a recipe of your own...\n"
-"# The recipe format is documented in the file devel/partman-auto-recipe.txt.\n"
+"# The recipe format is documented in the file devel/partman-auto-recipe."
+"txt.\n"
 "# If you have a way to get a recipe file into the d-i environment, you can\n"
 "# just point at it.\n"
 "#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
@@ -206,11 +219,13 @@ msgid ""
 "# instead, uncomment this:\n"
 "#d-i grub-installer/skip boolean true\n"
 "\n"
-"# This is fairly safe to set, it makes grub install automatically to the MBR\n"
+"# This is fairly safe to set, it makes grub install automatically to the "
+"MBR\n"
 "# if no other operating system is detected on the machine.\n"
 "d-i grub-installer/only_debian boolean true\n"
 "\n"
-"# This one makes grub-installer install to the MBR if if finds some other OS\n"
+"# This one makes grub-installer install to the MBR if if finds some other "
+"OS\n"
 "# too, which is less safe as it might not be able to boot that other OS.\n"
 "d-i grub-installer/with_other_os boolean true\n"
 "\n"
@@ -261,7 +276,8 @@ msgid ""
 "# Avoid the final message.\n"
 "base-config base-config/login note\n"
 "\n"
-"# If you installed a display manager, but don't want to start it immediately\n"
+"# If you installed a display manager, but don't want to start it "
+"immediately\n"
 "# after base-config finishes.\n"
 "#base-config base-config/start-display-manager boolean false\n"
 "\n"
@@ -379,7 +395,8 @@ msgid ""
 "# Uncomment if you have an LCD display.\n"
 "#xserver-xfree86 xserver-xfree86/config/monitor/lcd boolean true\n"
 "# X has three configuration paths for the monitor. Here's how to preseed\n"
-"# the \"medium\" path, which is always available. The \"simple\" path may not\n"
+"# the \"medium\" path, which is always available. The \"simple\" path may "
+"not\n"
 "# be available, and the \"advanced\" path asks too many questions.\n"
 "xserver-xfree86 xserver-xfree86/config/monitor/selection-method \\\n"
 "    select medium\n"
@@ -406,9 +423,11 @@ msgid ""
 "\n"
 "# More flexibly, this runs a shell command and if it outputs the names of\n"
 "# preseed files, includes those files. For example, to switch configs based\n"
-"# on a particular usb storage device (in this case, a built-in card reader):\n"
+"# on a particular usb storage device (in this case, a built-in card "
+"reader):\n"
 "#d-i preseed/include_command string \\\n"
-"#    if $(grep -q \"GUID: 0aec3050aec305000001a003\" /proc/scsi/usb-storage-*/*); \\\n"
+"#    if $(grep -q \"GUID: 0aec3050aec305000001a003\" /proc/scsi/usb-storage-"
+"*/*); \\\n"
 "#    then echo kraken.cfg; else echo otherusb.cfg; fi\n"
 "\n"
 "# To check the format of your preseed file before performing an install,\n"
@@ -439,7 +458,8 @@ msgid ""
 "# If you feel comfortable modifying the installer's initrd image,\n"
 "# you can also place a preseed file in the root directory of the initrd's\n"
 "# filesystem, named \"preseed.cfg\" -- the installer will always use this\n"
-"# file if it is present. Otherwise, be sure to copy this file to the location\n"
+"# file if it is present. Otherwise, be sure to copy this file to the "
+"location\n"
 "# you specify.\n"
 "#\n"
 "# To make sure the installer gets the right preseed file, you can specify\n"
@@ -463,7 +483,8 @@ msgid ""
 "#\n"
 "# While you're at it, you may want to throw a debconf/priority=critical in\n"
 "# there, to avoid most questions even if the preseeding below misses some.\n"
-"# And you might set the timeout to 1 in syslinux.cfg to avoid needing to hit\n"
+"# And you might set the timeout to 1 in syslinux.cfg to avoid needing to "
+"hit\n"
 "# enter to boot the installer.\n"
 "#\n"
 "# Note that the 2.4 kernel accepts a maximum of 8 command line options and\n"
@@ -547,11 +568,14 @@ msgid ""
 "# You can choose from any of the predefined partitioning recipes:\n"
 "d-i partman-auto/choose_recipe \\\n"
 "       select All files in one partition (recommended for new users)\n"
-"#d-i partman-auto/choose_recipe select Desktop machine\n"
-"#d-i partman-auto/choose_recipe select Multi-user workstation\n"
+"#d-i partman-auto/choose_recipe \\\n"
+"#       select Separate /home partition\n"
+"#d-i partman-auto/choose_recipe \\\n"
+"#       select Separate /home, /usr, /var, and /tmp partitions\n"
 "\n"
 "# Or provide a recipe of your own...\n"
-"# The recipe format is documented in the file devel/partman-auto-recipe.txt.\n"
+"# The recipe format is documented in the file devel/partman-auto-recipe."
+"txt.\n"
 "# If you have a way to get a recipe file into the d-i environment, you can\n"
 "# just point at it.\n"
 "#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
@@ -588,11 +612,13 @@ msgid ""
 "# instead, uncomment this:\n"
 "#d-i grub-installer/skip boolean true\n"
 "\n"
-"# This is fairly safe to set, it makes grub install automatically to the MBR\n"
+"# This is fairly safe to set, it makes grub install automatically to the "
+"MBR\n"
 "# if no other operating system is detected on the machine.\n"
 "d-i grub-installer/only_debian boolean true\n"
 "\n"
-"# This one makes grub-installer install to the MBR if if finds some other OS\n"
+"# This one makes grub-installer install to the MBR if if finds some other "
+"OS\n"
 "# too, which is less safe as it might not be able to boot that other OS.\n"
 "d-i grub-installer/with_other_os boolean true\n"
 "\n"
@@ -647,7 +673,8 @@ msgid ""
 "# Avoid the final message.\n"
 "base-config base-config/login note\n"
 "\n"
-"# If you installed a display manager, but don't want to start it immediately\n"
+"# If you installed a display manager, but don't want to start it "
+"immediately\n"
 "# after base-config finishes.\n"
 "#base-config base-config/start-display-manager boolean false\n"
 "\n"
@@ -749,7 +776,8 @@ msgid ""
 "# Uncomment if you have an LCD display.\n"
 "#xserver-xfree86 xserver-xfree86/config/monitor/lcd boolean true\n"
 "# X has three configuration paths for the monitor. Here's how to preseed\n"
-"# the \"medium\" path, which is always available. The \"simple\" path may not\n"
+"# the \"medium\" path, which is always available. The \"simple\" path may "
+"not\n"
 "# be available, and the \"advanced\" path asks too many questions.\n"
 "xserver-xfree86 xserver-xfree86/config/monitor/selection-method \\\n"
 "       select medium\n"
@@ -798,7 +826,14 @@ msgstr "Inmatningsenheter"
 #. Tag: para
 #: random-bits.xml:63
 #, no-c-format
-msgid "In Linux you have various special files in <filename>/dev</filename>. These files are called device files. In the Unix world accessing hardware is different. There you have a special file which actually runs a driver which in turn accesses the hardware. The device file is an interface to the actual system component. Files under <filename>/dev</filename> also behave differently than ordinary files. Below are the most important device files listed."
+msgid ""
+"In Linux you have various special files in <filename>/dev</filename>. These "
+"files are called device files. In the Unix world accessing hardware is "
+"different. There you have a special file which actually runs a driver which "
+"in turn accesses the hardware. The device file is an interface to the actual "
+"system component. Files under <filename>/dev</filename> also behave "
+"differently than ordinary files. Below are the most important device files "
+"listed."
 msgstr ""
 
 #. Tag: filename
@@ -883,7 +918,7 @@ msgstr ""
 #: random-bits.xml:101
 #, fuzzy, no-c-format
 msgid "First partition of the first IDE hard disk"
-msgstr "Hittade ingen rotpartition på den första disken"
+msgstr "Hittade ingen rotpartition på den första disken"
 
 #. Tag: filename
 #: random-bits.xml:103
@@ -943,7 +978,7 @@ msgstr ""
 #: random-bits.xml:120
 #, fuzzy, no-c-format
 msgid "First partition of the first SCSI hard disk"
-msgstr "Hittade ingen rotpartition på den första disken"
+msgstr "Hittade ingen rotpartition på den första disken"
 
 #. Tag: filename
 #: random-bits.xml:122
@@ -1087,38 +1122,60 @@ msgstr "Klar med partitionen"
 #: random-bits.xml:178
 #, no-c-format
 msgid ""
-"The mouse can be used in both the Linux console (with gpm) and the X window environment. The two uses can be made compatible if the gpm repeater is used to allow the signal to flow to the X server as shown: <informalexample><screen>\n"
-"mouse =&gt; /dev/psaux  =&gt; gpm =&gt; /dev/gpmdata -&gt; /dev/mouse =&gt; X\n"
+"The mouse can be used in both the Linux console (with gpm) and the X window "
+"environment. The two uses can be made compatible if the gpm repeater is used "
+"to allow the signal to flow to the X server as shown: "
+"<informalexample><screen>\n"
+"mouse =&gt; /dev/psaux  =&gt; gpm =&gt; /dev/gpmdata -&gt; /dev/mouse =&gt; "
+"X\n"
 "         /dev/ttyS0             (repeater)        (symlink)\n"
 "         /dev/ttyS1\n"
-"</screen></informalexample> Set the repeater protocol to be raw (in <filename>/etc/gpm.conf</filename>) while setting X to the original mouse protocol in <filename>/etc/X11/XF86Config</filename> or <filename>/etc/X11/XF86Config-4</filename>."
+"</screen></informalexample> Set the repeater protocol to be raw (in "
+"<filename>/etc/gpm.conf</filename>) while setting X to the original mouse "
+"protocol in <filename>/etc/X11/XF86Config</filename> or <filename>/etc/X11/"
+"XF86Config-4</filename>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:190
 #, no-c-format
 msgid ""
-"This approach to use gpm even in X has advantages when the mouse is unplugged inadvertently. Simply restarting gpm with <informalexample><screen>\n"
+"This approach to use gpm even in X has advantages when the mouse is "
+"unplugged inadvertently. Simply restarting gpm with "
+"<informalexample><screen>\n"
 "# /etc/init.d/gpm restart\n"
-"</screen></informalexample> will re-connect the mouse in software without restarting X."
+"</screen></informalexample> will re-connect the mouse in software without "
+"restarting X."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:199
 #, no-c-format
-msgid "If gpm is disabled or not installed with some reason, make sure to set X to read directly from the mouse device such as /dev/psaux. For details, refer to the 3-Button Mouse mini-Howto at <filename>/usr/share/doc/HOWTO/en-txt/mini/3-Button-Mouse.gz</filename>, <userinput>man gpm</userinput>, <filename>/usr/share/doc/gpm/FAQ.gz</filename>, and <ulink url=\"&url-xfree86;current/mouse.html\">README.mouse</ulink>."
+msgid ""
+"If gpm is disabled or not installed with some reason, make sure to set X to "
+"read directly from the mouse device such as /dev/psaux. For details, refer "
+"to the 3-Button Mouse mini-Howto at <filename>/usr/share/doc/HOWTO/en-txt/"
+"mini/3-Button-Mouse.gz</filename>, <userinput>man gpm</userinput>, "
+"<filename>/usr/share/doc/gpm/FAQ.gz</filename>, and <ulink url=\"&url-"
+"xfree86;current/mouse.html\">README.mouse</ulink>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:209
 #, no-c-format
-msgid "For PowerPC, in <filename>/etc/X11/XF86Config</filename> or <filename>/etc/X11/XF86Config-4</filename>, set the mouse device to <userinput>\"/dev/input/mice\"</userinput>."
+msgid ""
+"For PowerPC, in <filename>/etc/X11/XF86Config</filename> or <filename>/etc/"
+"X11/XF86Config-4</filename>, set the mouse device to <userinput>\"/dev/input/"
+"mice\"</userinput>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:215
 #, no-c-format
-msgid "Modern kernels give you the capability to emulate a three-button mouse when your mouse only has one button. Just add the following lines to <filename>/etc/sysctl.conf</filename> file."
+msgid ""
+"Modern kernels give you the capability to emulate a three-button mouse when "
+"your mouse only has one button. Just add the following lines to <filename>/"
+"etc/sysctl.conf</filename> file."
 msgstr ""
 
 #. Tag: screen
@@ -1139,24 +1196,35 @@ msgstr ""
 #: random-bits.xml:228
 #, fuzzy, no-c-format
 msgid "Disk Space Needed for Tasks"
-msgstr "Drivrutinen som behövs för din diskettstation:"
+msgstr "Drivrutinen som behövs för din diskettstation:"
 
 #. Tag: para
 #: random-bits.xml:240
 #, no-c-format
-msgid "The base installation for i386 using the default 2.4 kernel, including all standard packages, requires 573MB of disk space."
+msgid ""
+"The base installation for i386 using the default 2.4 kernel, including all "
+"standard packages, requires 573MB of disk space."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:245
 #, no-c-format
-msgid "The following table lists sizes reported by aptitude for the tasks listed in tasksel. Note that some tasks have overlapping constituents, so the total installed size for two tasks together may be less than the total obtained by adding up the numbers."
+msgid ""
+"The following table lists sizes reported by aptitude for the tasks listed in "
+"tasksel. Note that some tasks have overlapping constituents, so the total "
+"installed size for two tasks together may be less than the total obtained by "
+"adding up the numbers."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:252
 #, no-c-format
-msgid "Note that you will need to add the sizes listed in the table to the size of the base installation when determining the size of partitions. Most of the size listed as <quote>Installed size</quote> will end up in <filename>/usr</filename>; the size listed as <quote>Download size</quote> is (temporarily) required in <filename>/var</filename>."
+msgid ""
+"Note that you will need to add the sizes listed in the table to the size of "
+"the base installation when determining the size of partitions. Most of the "
+"size listed as <quote>Installed size</quote> will end up in <filename>/usr</"
+"filename>; the size listed as <quote>Download size</quote> is (temporarily) "
+"required in <filename>/var</filename>."
 msgstr ""
 
 #. Tag: entry
@@ -1169,13 +1237,13 @@ msgstr "^Funktionsinfo"
 #: random-bits.xml:266
 #, fuzzy, no-c-format
 msgid "Installed size (MB)"
-msgstr "För stor storlek"
+msgstr "För stor storlek"
 
 #. Tag: entry
 #: random-bits.xml:267
 #, fuzzy, no-c-format
 msgid "Download size (MB)"
-msgstr "För stor storlek"
+msgstr "För stor storlek"
 
 #. Tag: entry
 #: random-bits.xml:268
@@ -1199,7 +1267,7 @@ msgstr ""
 #: random-bits.xml:276
 #, fuzzy, no-c-format
 msgid "<entry>460</entry>"
-msgstr "Byt namn på post"
+msgstr "Byt namn på post"
 
 #. Tag: entry
 #: random-bits.xml:277
@@ -1217,19 +1285,19 @@ msgstr "Webbserver"
 #: random-bits.xml:282
 #, fuzzy, no-c-format
 msgid "<entry>36</entry>"
-msgstr "Byt namn på post"
+msgstr "Byt namn på post"
 
 #. Tag: entry
 #: random-bits.xml:283
 #, fuzzy, no-c-format
 msgid "<entry>12</entry>"
-msgstr "Ingång 12"
+msgstr "Ingång 12"
 
 #. Tag: entry
 #: random-bits.xml:284
 #, fuzzy, no-c-format
 msgid "<entry>48</entry>"
-msgstr "Byt namn på post"
+msgstr "Byt namn på post"
 
 #. Tag: entry
 #: random-bits.xml:288
@@ -1241,19 +1309,19 @@ msgstr "Utskriftsserver"
 #: random-bits.xml:289
 #, fuzzy, no-c-format
 msgid "<entry>168</entry>"
-msgstr "Byt namn på post"
+msgstr "Byt namn på post"
 
 #. Tag: entry
 #: random-bits.xml:290
 #, fuzzy, no-c-format
 msgid "<entry>58</entry>"
-msgstr "Byt namn på post"
+msgstr "Byt namn på post"
 
 #. Tag: entry
 #: random-bits.xml:291
 #, fuzzy, no-c-format
 msgid "<entry>226</entry>"
-msgstr "Byt namn på post"
+msgstr "Byt namn på post"
 
 #. Tag: entry
 #: random-bits.xml:295
@@ -1274,8 +1342,7 @@ msgid "<entry>1</entry>"
 msgstr "post"
 
 #. Tag: entry
-#: random-bits.xml:298
-#: random-bits.xml:311
+#: random-bits.xml:298 random-bits.xml:311
 #, fuzzy, no-c-format
 msgid "<entry>3</entry>"
 msgstr "post"
@@ -1290,19 +1357,19 @@ msgstr "Filserver"
 #: random-bits.xml:303
 #, fuzzy, no-c-format
 msgid "<entry>47</entry>"
-msgstr "Byt namn på post"
+msgstr "Byt namn på post"
 
 #. Tag: entry
 #: random-bits.xml:304
 #, fuzzy, no-c-format
 msgid "<entry>24</entry>"
-msgstr "Byt namn på post"
+msgstr "Byt namn på post"
 
 #. Tag: entry
 #: random-bits.xml:305
 #, fuzzy, no-c-format
 msgid "<entry>71</entry>"
-msgstr "Byt namn på post"
+msgstr "Byt namn på post"
 
 #. Tag: entry
 #: random-bits.xml:309
@@ -1314,13 +1381,13 @@ msgstr "E-postserver"
 #: random-bits.xml:310
 #, fuzzy, no-c-format
 msgid "<entry>10</entry>"
-msgstr "Ingång 10"
+msgstr "Ingång 10"
 
 #. Tag: entry
 #: random-bits.xml:312
 #, fuzzy, no-c-format
 msgid "<entry>13</entry>"
-msgstr "Ingång 13"
+msgstr "Ingång 13"
 
 #. Tag: entry
 #: random-bits.xml:316
@@ -1332,30 +1399,36 @@ msgstr "SQL-databas"
 #: random-bits.xml:317
 #, fuzzy, no-c-format
 msgid "<entry>66</entry>"
-msgstr "Byt namn på post"
+msgstr "Byt namn på post"
 
 #. Tag: entry
 #: random-bits.xml:318
 #, fuzzy, no-c-format
 msgid "<entry>21</entry>"
-msgstr "Byt namn på post"
+msgstr "Byt namn på post"
 
 #. Tag: entry
 #: random-bits.xml:319
 #, fuzzy, no-c-format
 msgid "<entry>87</entry>"
-msgstr "Byt namn på post"
+msgstr "Byt namn på post"
 
 #. Tag: para
 #: random-bits.xml:325
 #, no-c-format
-msgid "The <emphasis>Desktop</emphasis> task will install both the Gnome and KDE desktop environments."
+msgid ""
+"The <emphasis>Desktop</emphasis> task will install both the Gnome and KDE "
+"desktop environments."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:332
 #, no-c-format
-msgid "If you install in a language other than English, <command>tasksel</command> may automatically install a <firstterm>localization task</firstterm>, if one is available for your language. Space requirements differ per language; you should allow up to 200MB in total for download and installation."
+msgid ""
+"If you install in a language other than English, <command>tasksel</command> "
+"may automatically install a <firstterm>localization task</firstterm>, if one "
+"is available for your language. Space requirements differ per language; you "
+"should allow up to 200MB in total for download and installation."
 msgstr ""
 
 #. Tag: title
@@ -1367,45 +1440,69 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:349
 #, no-c-format
-msgid "This section explains how to install &debian; from an existing Unix or Linux system, without using the menu-driven installer as explained in the rest of the manual. This <quote>cross-install</quote> HOWTO has been requested by users switching to &debian; from Red Hat, Mandrake, and SUSE. In this section some familiarity with entering *nix commands and navigating the file system is assumed. In this section, <prompt>$</prompt> symbolizes a command to be entered in the user's current system, while <prompt>#</prompt> refers to a command entered in the Debian chroot."
+msgid ""
+"This section explains how to install &debian; from an existing Unix or Linux "
+"system, without using the menu-driven installer as explained in the rest of "
+"the manual. This <quote>cross-install</quote> HOWTO has been requested by "
+"users switching to &debian; from Red Hat, Mandrake, and SUSE. In this "
+"section some familiarity with entering *nix commands and navigating the file "
+"system is assumed. In this section, <prompt>$</prompt> symbolizes a command "
+"to be entered in the user's current system, while <prompt>#</prompt> refers "
+"to a command entered in the Debian chroot."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:361
 #, no-c-format
-msgid "Once you've got the new Debian system configured to your preference, you can migrate your existing user data (if any) to it, and keep on rolling. This is therefore a <quote>zero downtime</quote> &debian; install. It's also a clever way for dealing with hardware that otherwise doesn't play friendly with various boot or installation media."
+msgid ""
+"Once you've got the new Debian system configured to your preference, you can "
+"migrate your existing user data (if any) to it, and keep on rolling. This is "
+"therefore a <quote>zero downtime</quote> &debian; install. It's also a "
+"clever way for dealing with hardware that otherwise doesn't play friendly "
+"with various boot or installation media."
 msgstr ""
 
 #. Tag: title
 #: random-bits.xml:373
 #, fuzzy, no-c-format
 msgid "Getting Started"
-msgstr "Spel påbörjat."
+msgstr "Spel påbörjat."
 
 #. Tag: para
 #: random-bits.xml:374
 #, no-c-format
-msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need at least 150MB of space available for a console only install, or at least 300MB if you plan to install X."
+msgid ""
+"With your current *nix partitioning tools, repartition the hard drive as "
+"needed, creating at least one filesystem plus swap. You need at least 150MB "
+"of space available for a console only install, or at least 300MB if you plan "
+"to install X."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:381
 #, no-c-format
 msgid ""
-"To create file systems on your partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n"
+"To create file systems on your partitions. For example, to create an ext3 "
+"file system on partition <filename>/dev/hda6</filename> (that's our example "
+"root partition): <informalexample><screen>\n"
 "# mke2fs -j /dev/hda6\n"
-"</screen></informalexample> To create an ext2 file system instead, omit <userinput>-j</userinput>."
+"</screen></informalexample> To create an ext2 file system instead, omit "
+"<userinput>-j</userinput>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:391
 #, no-c-format
 msgid ""
-"Initialize and activate swap (substitute the partition number for your intended Debian swap partition): <informalexample><screen>\n"
+"Initialize and activate swap (substitute the partition number for your "
+"intended Debian swap partition): <informalexample><screen>\n"
 "# mkswap /dev/hda5\n"
 "# sync; sync; sync\n"
 "# swapon /dev/hda5\n"
-"</screen></informalexample> Mount one partition as <filename>/mnt/debinst</filename> (the installation point, to be the root (<filename>/</filename>) filesystem on your new system). The mount point name is strictly arbitrary, it is referenced later below."
+"</screen></informalexample> Mount one partition as <filename>/mnt/debinst</"
+"filename> (the installation point, to be the root (<filename>/</filename>) "
+"filesystem on your new system). The mount point name is strictly arbitrary, "
+"it is referenced later below."
 msgstr ""
 
 #. Tag: screen
@@ -1419,35 +1516,53 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:406
 #, no-c-format
-msgid "If you want to have parts of the filesystem (e.g. /usr) mounted on separate partitions, you will need to create and mount these directories manually before proceding with the next stage."
+msgid ""
+"If you want to have parts of the filesystem (e.g. /usr) mounted on separate "
+"partitions, you will need to create and mount these directories manually "
+"before proceding with the next stage."
 msgstr ""
 
 #. Tag: title
 #: random-bits.xml:416
 #, fuzzy, no-c-format
 msgid "Install <command>debootstrap</command>"
-msgstr "Kommandosträngen är tom"
+msgstr "Kommandosträngen är tom"
 
 #. Tag: para
 #: random-bits.xml:417
 #, no-c-format
-msgid "The tool that the Debian installer uses, which is recognized as the official way to install a Debian base system, is <command>debootstrap</command>. It uses <command>wget</command> and <command>ar</command>, but otherwise depends only on <classname>/bin/sh</classname>. Install <command>wget</command> and <command>ar</command> if they aren't already on your current system, then download and install <command>debootstrap</command>."
+msgid ""
+"The tool that the Debian installer uses, which is recognized as the official "
+"way to install a Debian base system, is <command>debootstrap</command>. It "
+"uses <command>wget</command> and <command>ar</command>, but otherwise "
+"depends only on <classname>/bin/sh</classname>. Install <command>wget</"
+"command> and <command>ar</command> if they aren't already on your current "
+"system, then download and install <command>debootstrap</command>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:427
 #, no-c-format
-msgid "If you have an rpm-based system, you can use alien to convert the .deb into .rpm, or download an rpm-ized version at <ulink url=\"http://people.debian.org/~blade/install/debootstrap\"></ulink>"
+msgid ""
+"If you have an rpm-based system, you can use alien to convert the .deb into ."
+"rpm, or download an rpm-ized version at <ulink url=\"http://people.debian."
+"org/~blade/install/debootstrap\"></ulink>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:433
 #, no-c-format
 msgid ""
-"Or, you can use the following procedure to install it manually. Make a work folder for extracting the .deb into: <informalexample><screen>\n"
+"Or, you can use the following procedure to install it manually. Make a work "
+"folder for extracting the .deb into: <informalexample><screen>\n"
 "# mkdir work\n"
 "# cd work\n"
-"</screen></informalexample> The <command>debootstrap</command> binary is located in the Debian archive (be sure to select the proper file for your architecture). Download the <command>debootstrap</command> .deb from the <ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</ulink>, copy the package to the work folder, and extract the binary files from it. You will need to have root privileges to install the binaries."
+"</screen></informalexample> The <command>debootstrap</command> binary is "
+"located in the Debian archive (be sure to select the proper file for your "
+"architecture). Download the <command>debootstrap</command> .deb from the "
+"<ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</"
+"ulink>, copy the package to the work folder, and extract the binary files "
+"from it. You will need to have root privileges to install the binaries."
 msgstr ""
 
 #. Tag: screen
@@ -1462,31 +1577,50 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:450
 #, no-c-format
-msgid "Note that running <command>debootstrap</command> may require you to have a minimal version of <classname>glibc</classname> installed (currently GLIBC_2.3). <command>debootstrap</command> itself is a shell script, but it calls various utilities that require <classname>glibc</classname>."
+msgid ""
+"Note that running <command>debootstrap</command> may require you to have a "
+"minimal version of <classname>glibc</classname> installed (currently "
+"GLIBC_2.3). <command>debootstrap</command> itself is a shell script, but it "
+"calls various utilities that require <classname>glibc</classname>."
 msgstr ""
 
 #. Tag: title
 #: random-bits.xml:461
 #, fuzzy, no-c-format
 msgid "Run <command>debootstrap</command>"
-msgstr "Misslyckades att köra förinställt kommando"
+msgstr "Misslyckades att köra förinställt kommando"
 
 #. Tag: para
 #: random-bits.xml:462
 #, no-c-format
-msgid "<command>debootstrap</command> can download the needed files directly from the archive when you run it. You can substitute any Debian archive mirror for <userinput>http.us.debian.org/debian</userinput> in the command example below, preferably a mirror close to you network-wise. Mirrors are listed at <ulink url=\"http://www.debian.org/misc/README.mirrors\"></ulink>."
+msgid ""
+"<command>debootstrap</command> can download the needed files directly from "
+"the archive when you run it. You can substitute any Debian archive mirror "
+"for <userinput>http.us.debian.org/debian</userinput> in the command example "
+"below, preferably a mirror close to you network-wise. Mirrors are listed at "
+"<ulink url=\"http://www.debian.org/misc/README.mirrors\"></ulink>."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:471
 #, no-c-format
-msgid "If you have a &releasename; &debian; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>"
+msgid ""
+"If you have a &releasename; &debian; CD mounted at <filename>/cdrom</"
+"filename>, you could substitute a file URL instead of the http URL: "
+"<userinput>file:/cdrom/debian/</userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:477
 #, no-c-format
-msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>alpha</userinput>, <userinput>arm</userinput>, <userinput>hppa</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>m68k</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, or <userinput>sparc</userinput>."
+msgid ""
+"Substitute one of the following for <replaceable>ARCH</replaceable> in the "
+"<command>debootstrap</command> command: <userinput>alpha</userinput>, "
+"<userinput>arm</userinput>, <userinput>hppa</userinput>, <userinput>i386</"
+"userinput>, <userinput>ia64</userinput>, <userinput>m68k</userinput>, "
+"<userinput>mips</userinput>, <userinput>mipsel</userinput>, "
+"<userinput>powerpc</userinput>, <userinput>s390</userinput>, or "
+"<userinput>sparc</userinput>."
 msgstr ""
 
 #. Tag: screen
@@ -1506,7 +1640,9 @@ msgstr "Konfigurera grundsystemet innan omstart"
 #. Tag: para
 #: random-bits.xml:501
 #, no-c-format
-msgid "Now you've got a real Debian system, though rather lean, on disk. <command>Chroot</command> into it:"
+msgid ""
+"Now you've got a real Debian system, though rather lean, on disk. "
+"<command>Chroot</command> into it:"
 msgstr ""
 
 #. Tag: screen
@@ -1525,9 +1661,11 @@ msgstr "Konfigurera och montera partitioner"
 #: random-bits.xml:512
 #, no-c-format
 msgid ""
-"You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n"
+"You need to create <filename>/etc/fstab</filename>. "
+"<informalexample><screen>\n"
 "# editor /etc/fstab\n"
-"</screen></informalexample> Here is a sample you can modify to suit: <informalexample><screen>\n"
+"</screen></informalexample> Here is a sample you can modify to suit: "
+"<informalexample><screen>\n"
 "# /etc/fstab: static file system information.\n"
 "#\n"
 "# file system    mount point   type    options                  dump pass\n"
@@ -1544,9 +1682,14 @@ msgid ""
 "/dev/XXX         /var          ext3    rw,nosuid,nodev          0    2\n"
 "/dev/XXX         /usr          ext3    rw,nodev                 0    2\n"
 "/dev/XXX         /home         ext3    rw,nosuid,nodev          0    2\n"
-"</screen></informalexample> Use <userinput>mount -a</userinput> to mount all the file systems you have specified in your <filename>/etc/fstab</filename>, or to mount file systems individually use: <informalexample><screen>\n"
+"</screen></informalexample> Use <userinput>mount -a</userinput> to mount all "
+"the file systems you have specified in your <filename>/etc/fstab</filename>, "
+"or to mount file systems individually use: <informalexample><screen>\n"
 "# mount /path   # e.g.: mount /usr\n"
-"</screen></informalexample> You can mount the proc file system multiple times and to arbitrary locations, though <filename>/proc</filename> is customary. If you didn't use <userinput>mount -a</userinput>, be sure to mount proc before continuing:"
+"</screen></informalexample> You can mount the proc file system multiple "
+"times and to arbitrary locations, though <filename>/proc</filename> is "
+"customary. If you didn't use <userinput>mount -a</userinput>, be sure to "
+"mount proc before continuing:"
 msgstr ""
 
 #. Tag: screen
@@ -1558,7 +1701,10 @@ msgstr "Monteringspunkt:"
 #. Tag: para
 #: random-bits.xml:534
 #, no-c-format
-msgid "The command <userinput>ls /proc</userinput> should now show a non-empty directory. Should this fail, you may be able to mount proc from outside the chroot:"
+msgid ""
+"The command <userinput>ls /proc</userinput> should now show a non-empty "
+"directory. Should this fail, you may be able to mount proc from outside the "
+"chroot:"
 msgstr ""
 
 #. Tag: screen
@@ -1588,7 +1734,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:553
 #, no-c-format
-msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot."
+msgid ""
+"Note that the keyboard cannot be set while in the chroot, but will be "
+"configured for the next reboot."
 msgstr ""
 
 #. Tag: title
@@ -1601,9 +1749,12 @@ msgstr "Konfigurera tangentbordet"
 #: random-bits.xml:563
 #, no-c-format
 msgid ""
-"To configure networking, edit <filename>/etc/network/interfaces</filename>, <filename>/etc/resolv.conf</filename>, and <filename>/etc/hostname</filename>. <informalexample><screen>\n"
+"To configure networking, edit <filename>/etc/network/interfaces</filename>, "
+"<filename>/etc/resolv.conf</filename>, and <filename>/etc/hostname</"
+"filename>. <informalexample><screen>\n"
 "# editor /etc/network/interfaces\n"
-"</screen></informalexample> Here are some simple examples from <filename>/usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n"
+"</screen></informalexample> Here are some simple examples from <filename>/"
+"usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n"
 "######################################################################\n"
 "# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n"
 "# See the interfaces(5) manpage for information on what options are\n"
@@ -1629,15 +1780,21 @@ msgid ""
 "#     netmask 255.255.255.0\n"
 "#     broadcast 192.168.0.255\n"
 "#     gateway 192.168.0.1\n"
-"</screen></informalexample> Enter your nameserver(s) and search directives in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
+"</screen></informalexample> Enter your nameserver(s) and search directives "
+"in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
 "# editor /etc/resolv.conf\n"
-"</screen></informalexample> A simple <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n"
+"</screen></informalexample> A simple <filename>/etc/resolv.conf</filename>: "
+"<informalexample><screen>\n"
 "search hqdom.local\\000\n"
 "nameserver 10.1.1.36\n"
 "nameserver 192.168.9.100\n"
-"</screen></informalexample> Enter your system's host name (2 to 63 characters): <informalexample><screen>\n"
+"</screen></informalexample> Enter your system's host name (2 to 63 "
+"characters): <informalexample><screen>\n"
 "# echo DebianHostName &gt; /etc/hostname\n"
-"</screen></informalexample> If you have multiple network cards, you should arrange the names of driver modules in the <filename>/etc/modules</filename> file into the desired order. Then during boot, each card will be associated with the interface name (eth0, eth1, etc.) that you expect."
+"</screen></informalexample> If you have multiple network cards, you should "
+"arrange the names of driver modules in the <filename>/etc/modules</filename> "
+"file into the desired order. Then during boot, each card will be associated "
+"with the interface name (eth0, eth1, etc.) that you expect."
 msgstr ""
 
 #. Tag: title
@@ -1649,7 +1806,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:600
 #, no-c-format
-msgid "Set your timezone, add a normal user, and choose your <command>apt</command> sources by running"
+msgid ""
+"Set your timezone, add a normal user, and choose your <command>apt</command> "
+"sources by running"
 msgstr ""
 
 #. Tag: screen
@@ -1668,23 +1827,29 @@ msgstr "Konfigurera tangentbordet"
 #: random-bits.xml:612
 #, no-c-format
 msgid ""
-"To configure your locale settings to use a language other than English, install the locales support package and configure it: <informalexample><screen>\n"
+"To configure your locale settings to use a language other than English, "
+"install the locales support package and configure it: "
+"<informalexample><screen>\n"
 "# apt-get install locales\n"
 "# dpkg-reconfigure locales\n"
-"</screen></informalexample> NOTE: Apt must be configured before, ie. during the base-config phase. Before using locales with character sets other than ASCII or latin1, please consult the appropriate localization HOWTO."
+"</screen></informalexample> NOTE: Apt must be configured before, ie. during "
+"the base-config phase. Before using locales with character sets other than "
+"ASCII or latin1, please consult the appropriate localization HOWTO."
 msgstr ""
 
 #. Tag: title
 #: random-bits.xml:628
 #, fuzzy, no-c-format
 msgid "Install a Kernel"
-msgstr "Kärna som ska installeras:"
+msgstr "Kärna som ska installeras:"
 
 #. Tag: para
 #: random-bits.xml:629
 #, no-c-format
 msgid ""
-"If you intend to boot this system, you probably want a Linux kernel and a boot loader. Identify available pre-packaged kernels with <informalexample><screen>\n"
+"If you intend to boot this system, you probably want a Linux kernel and a "
+"boot loader. Identify available pre-packaged kernels with "
+"<informalexample><screen>\n"
 "# apt-cache search kernel-image\n"
 "</screen></informalexample> Then install your choice using its package name."
 msgstr ""
@@ -1692,7 +1857,8 @@ msgstr ""
 #. Tag: screen
 #: random-bits.xml:638
 #, no-c-format
-msgid "# apt-get install kernel-image-<replaceable>2.X.X-arch-etc</replaceable>"
+msgid ""
+"# apt-get install kernel-image-<replaceable>2.X.X-arch-etc</replaceable>"
 msgstr ""
 
 #. Tag: title
@@ -1704,13 +1870,25 @@ msgstr "/boot - startladdarens statiska filer"
 #. Tag: para
 #: random-bits.xml:645
 #, no-c-format
-msgid "To make your &debian; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that debootstrap does not install a boot loader, though you can use apt-get inside your Debian chroot to do so."
+msgid ""
+"To make your &debian; system bootable, set up your boot loader to load the "
+"installed kernel with your new root partition. Note that debootstrap does "
+"not install a boot loader, though you can use apt-get inside your Debian "
+"chroot to do so."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:652
 #, no-c-format
-msgid "Check <userinput>info grub</userinput> or <userinput>man lilo.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing grub <filename>menu.lst</filename> or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call lilo (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)."
+msgid ""
+"Check <userinput>info grub</userinput> or <userinput>man lilo.conf</"
+"userinput> for instructions on setting up the bootloader. If you are keeping "
+"the system you used to install Debian, just add an entry for the Debian "
+"install to your existing grub <filename>menu.lst</filename> or "
+"<filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you "
+"could also copy it to the new system and edit it there. After you are done "
+"editing, call lilo (remember it will use <filename>lilo.conf</filename> "
+"relative to the system you call it from)."
 msgstr ""
 
 #. Tag: para
@@ -1735,14 +1913,21 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:669
 #, no-c-format
-msgid "Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing <filename>yaboot.conf</filename>. You could also copy it to the new system and edit it there. After you are done editing, call ybin (remember it will use <filename>yaboot.conf</filename> relative to the system you call it from)."
+msgid ""
+"Check <userinput>man yaboot.conf</userinput> for instructions on setting up "
+"the bootloader. If you are keeping the system you used to install Debian, "
+"just add an entry for the Debian install to your existing <filename>yaboot."
+"conf</filename>. You could also copy it to the new system and edit it there. "
+"After you are done editing, call ybin (remember it will use <filename>yaboot."
+"conf</filename> relative to the system you call it from)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:679
 #, no-c-format
 msgid ""
-"Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n"
+"Here is a basic <filename>/etc/yaboot.conf</filename> as an example: "
+"<informalexample><screen>\n"
 "boot=/dev/hda2\n"
 "device=hd:\n"
 "partition=6\n"
@@ -1751,7 +1936,8 @@ msgid ""
 "timeout=50\n"
 "image=/vmlinux\n"
 "label=Debian\n"
-"</screen></informalexample> On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>."
+"</screen></informalexample> On some machines, you may need to use "
+"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>."
 msgstr ""
 
 #. Tag: title
@@ -1763,25 +1949,41 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:699
 #, no-c-format
-msgid "This section explains how to install &debian; on a computer without Ethernet card, but with just a remote gateway computer attached via a Null-Modem cable (also called Null-Printer cable). The gateway computer should be connected to a network that has a Debian mirror on it (e.g. to the Internet)."
+msgid ""
+"This section explains how to install &debian; on a computer without Ethernet "
+"card, but with just a remote gateway computer attached via a Null-Modem "
+"cable (also called Null-Printer cable). The gateway computer should be "
+"connected to a network that has a Debian mirror on it (e.g. to the Internet)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:707
 #, no-c-format
-msgid "In the example in this appendix we will set up a PLIP connection using a gateway connected to the Internet over a dial-up connection (ppp0). We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the target system and the source system respectively (these addresses should be unused within your network address space)."
+msgid ""
+"In the example in this appendix we will set up a PLIP connection using a "
+"gateway connected to the Internet over a dial-up connection (ppp0). We will "
+"use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the "
+"target system and the source system respectively (these addresses should be "
+"unused within your network address space)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:715
 #, no-c-format
-msgid "The PLIP connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)."
+msgid ""
+"The PLIP connection set up during the installation will also be available "
+"after the reboot into the installed system (see <xref linkend=\"boot-new\"/"
+">)."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:720
 #, no-c-format
-msgid "Before you start, you will need to check the BIOS configuration (IO base address and IRQ) for the parallel ports of both the source and target systems. The most common values are <literal>io=0x378</literal>, <literal>irq=7</literal>."
+msgid ""
+"Before you start, you will need to check the BIOS configuration (IO base "
+"address and IRQ) for the parallel ports of both the source and target "
+"systems. The most common values are <literal>io=0x378</literal>, "
+"<literal>irq=7</literal>."
 msgstr ""
 
 #. Tag: title
@@ -1793,7 +1995,9 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:733
 #, no-c-format
-msgid "A target computer, called <emphasis>target</emphasis>, where Debian will be installed."
+msgid ""
+"A target computer, called <emphasis>target</emphasis>, where Debian will be "
+"installed."
 msgstr ""
 
 #. Tag: para
@@ -1805,25 +2009,32 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:744
 #, no-c-format
-msgid "Another computer connected to the Internet, called <emphasis>source</emphasis>, that will function as the gateway."
+msgid ""
+"Another computer connected to the Internet, called <emphasis>source</"
+"emphasis>, that will function as the gateway."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:750
 #, no-c-format
-msgid "A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> for more information on this cable and instructions how to make your own."
+msgid ""
+"A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;"
+"\">PLIP-Install-HOWTO</ulink> for more information on this cable and "
+"instructions how to make your own."
 msgstr ""
 
 #. Tag: title
 #: random-bits.xml:762
 #, fuzzy, no-c-format
 msgid "Setting up source"
-msgstr "Ställer in OpenFirmware"
+msgstr "Ställer in OpenFirmware"
 
 #. Tag: para
 #: random-bits.xml:763
 #, no-c-format
-msgid "The following shell script is a simple example of how to configure the source computer as a gateway to the Internet using ppp0."
+msgid ""
+"The following shell script is a simple example of how to configure the "
+"source computer as a gateway to the Internet using ppp0."
 msgstr ""
 
 #. Tag: screen
@@ -1835,15 +2046,18 @@ msgid ""
 "# We remove running modules from kernel to avoid conflicts and to\n"
 "# reconfigure them manually.\n"
 "modprobe -r lp parport_pc\n"
-"modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</replaceable>\n"
+"modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</"
+"replaceable>\n"
 "modprobe plip\n"
 "\n"
 "# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n"
-"ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint <replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n"
+"ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint "
+"<replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n"
 "\n"
 "# Configure gateway\n"
 "modprobe iptable_nat\n"
-"iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j MASQUERADE\n"
+"iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j "
+"MASQUERADE\n"
 "echo 1 > /proc/sys/net/ipv4/ip_forward"
 msgstr ""
 
@@ -1851,12 +2065,15 @@ msgstr ""
 #: random-bits.xml:774
 #, fuzzy, no-c-format
 msgid "Installing target"
-msgstr "M_ålarbetslista:"
+msgstr "M_Ã¥larbetslista:"
 
 #. Tag: para
 #: random-bits.xml:775
 #, no-c-format
-msgid "Boot the installation media. The installation needs to be run in expert mode; enter <userinput>expert</userinput> at the boot prompt. Below are the answers that should be given during various stages of the installation."
+msgid ""
+"Boot the installation media. The installation needs to be run in expert "
+"mode; enter <userinput>expert</userinput> at the boot prompt. Below are the "
+"answers that should be given during various stages of the installation."
 msgstr ""
 
 #. Tag: guimenuitem
@@ -1868,19 +2085,25 @@ msgstr "Installationskomponenter som ska laddas:"
 #. Tag: para
 #: random-bits.xml:789
 #, no-c-format
-msgid "Select the <userinput>plip-modules</userinput> option from the list; this will make the PLIP drivers available to the installation system."
+msgid ""
+"Select the <userinput>plip-modules</userinput> option from the list; this "
+"will make the PLIP drivers available to the installation system."
 msgstr ""
 
 #. Tag: guimenuitem
 #: random-bits.xml:797
 #, fuzzy, no-c-format
 msgid "Detect network hardware"
-msgstr "Identifiera nätverksmaskinvara"
+msgstr "Identifiera nätverksmaskinvara"
 
 #. Tag: para
 #: random-bits.xml:802
 #, no-c-format
-msgid "If target <emphasis>does</emphasis> have a network card, a list of driver modules for detected cards will be shown. If you want to force &d-i; to use plip instead, you have to deselect all listed driver modules. Obviously, if target doesn't have a network card, the installer will not show this list."
+msgid ""
+"If target <emphasis>does</emphasis> have a network card, a list of driver "
+"modules for detected cards will be shown. If you want to force &d-i; to use "
+"plip instead, you have to deselect all listed driver modules. Obviously, if "
+"target doesn't have a network card, the installer will not show this list."
 msgstr ""
 
 #. Tag: para
@@ -1892,13 +2115,18 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:816
 #, no-c-format
-msgid "Because no network card was detected/selected earlier, the installer will ask you to select a network driver module from a list. Select the <userinput>plip</userinput> module."
+msgid ""
+"Because no network card was detected/selected earlier, the installer will "
+"ask you to select a network driver module from a list. Select the "
+"<userinput>plip</userinput> module."
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:823
 #, no-c-format
-msgid "Additional parameters for module parport_pc: <userinput><replaceable>io=0x378 irq=7</replaceable></userinput>"
+msgid ""
+"Additional parameters for module parport_pc: "
+"<userinput><replaceable>io=0x378 irq=7</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
@@ -1911,7 +2139,7 @@ msgstr ""
 #: random-bits.xml:839
 #, no-c-format
 msgid "Configure the network"
-msgstr "Konfigurera nätverket"
+msgstr "Konfigurera nätverket"
 
 #. Tag: para
 #: random-bits.xml:842
@@ -1922,18 +2150,22 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:847
 #, no-c-format
-msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
+msgid ""
+"IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:852
 #, no-c-format
-msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>"
+msgid ""
+"Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></"
+"userinput>"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:858
 #, no-c-format
-msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)"
+msgid ""
+"Name server addresses: you can enter the same addresses used on source (see "
+"<filename>/etc/resolv.conf</filename>)"
 msgstr ""
-