diff options
| author | Daniel Nylander <debian@danielnylander.se> | 2005-11-20 23:18:40 +0000 |
|---|---|---|
| committer | Daniel Nylander <debian@danielnylander.se> | 2005-11-20 23:18:40 +0000 |
| commit | d333212b0dad9d1380e3aa68e1ef7c0d4af3a39e (patch) | |
| tree | 0d705fb1e689a1513054e6ea19bd1b6afedb5447 | |
| parent | 79ce471f20854c1b98a503ee448d31821368641d (diff) | |
| download | installation-guide-d333212b0dad9d1380e3aa68e1ef7c0d4af3a39e.zip | |
Update for swedish manual again
| -rwxr-xr-x | po/sv/administrivia.po | 135 | ||||
| -rwxr-xr-x | po/sv/boot-installer.po | 1719 | ||||
| -rwxr-xr-x | po/sv/install-methods.po | 1032 | ||||
| -rwxr-xr-x | po/sv/preparing.po | 314 | ||||
| -rwxr-xr-x | po/sv/random-bits.po | 729 |
5 files changed, 1031 insertions, 2898 deletions
diff --git a/po/sv/administrivia.po b/po/sv/administrivia.po index 8e7632dcd..366fd2665 100755 --- a/po/sv/administrivia.po +++ b/po/sv/administrivia.po @@ -6,18 +6,20 @@ msgid "" msgstr "" "Project-Id-Version: installation-guide 20051025 administrativa\n" "POT-Creation-Date: 2001-02-09 01:25+0100\n" -"PO-Revision-Date: 2005-11-16 11:44+0100\n" +"PO-Revision-Date: 2005-11-21 00:02+0100\n" "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=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: sv\n" +"X-Poedit-Country: sv\n" #. Tag: title #: administrivia.xml:5 #, no-c-format msgid "Administrivia" -msgstr "" +msgstr "Administrivia" #. Tag: title #: administrivia.xml:9 @@ -28,37 +30,20 @@ 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." -msgstr "" +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 "Detta dokument är skrivet i DocBook XML. Formaten för utdata genereras av olika program med information frÃ¥n paketen <classname>docbook-xml</classname> och <classname>docbook-xsl</classname>." #. 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 " -"— profiling attributes are used to isolate certain bits of text as " -"architecture-specific." -msgstr "" +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 — profiling attributes are used to isolate certain bits of text as architecture-specific." +msgstr "För att förbättra hanteringen av detta dokument använder vi ett antal XML-funktioner sÃ¥som entities och profil-attribut. Dessa spelar en roll som är besläktad med variabler och villkor i programsprÃ¥k. XML-källkoden till detta dokument innehÃ¥ller information om varje arkitektur och profil-attribut används för att isolera vissa delar av texten som är arkitekturspecifik." #. Tag: title #: administrivia.xml:52 @@ -69,47 +54,20 @@ 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." -msgstr "" +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 "Om du har problem eller förslag angÃ¥ende detta dokument bör du antagligen sända in om som en buggrapport mot paketet <classname>debian-installer-manual</classname>. Se paketet <classname>reportbug</classname> eller läs online-dokumentationen för <ulink url=\"&url-bts;\">Debians bugghanteringssystem</ulink>. Det vore trevligt om du kunde kontrollera <ulink url=\"&url-bts;debian-installer-manual\">öppna buggar mot paketet debian-installer-manual</ulink> för att se om ditt problem redan har blivit rapporterat. Om det har gjorts kan du ge ytterligare bekräftelse eller behjälplig information till <email><replaceable>XXXX</replaceable>@bugs.debian.org</email> där <replaceable>XXXX</replaceable> är numret för den redan öppna buggrapporten." #. 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." -msgstr "" +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 "Ännu bättre, skaffa en kopia av DocBook-källan för detta dokument och skapa rättningar mot den. DocBook-källan kan hittas pÃ¥ <ulink url=\"&url-d-i-websvn;\">debian-installer WebSVN</ulink>. Om du inte känner till DocBook, var inte rädd, det finns en enkel lathund i manualkatalogen som gör det lättare att starta. Det liknar html men riktar sig mer mot betydningen av texten hellre än presentationen. Rättningar som skickas till e-postlistan debian-boot (se nedan) välkomnas. För instruktioner om hur man tar ner källan via SVN, se <ulink url=\"&url-d-i-readme;\">README</ulink> frÃ¥n källans rotkatalog." #. 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." -msgstr "" +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 "Vänligen kontakta <emphasis>inte</emphasis> författaren av detta dokument direkt. Det finns även en diskussionslista för &d-i som inkluderar diskussioner om denna manual. E-postlistan är <email>debian-boot@lists.debian.org</email>. Instruktioner för prenumeration av denna lista kan hittas pÃ¥ sidan <ulink url=\"&url-debian-lists-subscribe;\">Debian Mailing List Subscription</ulink> eller sÃ¥ kan du bläddra i <ulink url=\"&url-debian-list-archives;\">Debian Mailing List Archives</ulink> online." #. Tag: title #: administrivia.xml:101 @@ -119,74 +77,37 @@ msgstr "Stora bidragare" #. Tag: para #: administrivia.xml:103 -#, 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." +#, 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 Stéphane Bortzmeyer för ett flertal redigeringar och texter. Vi mÃ¥ste tacka Pascal Le Bail för användbar information om uppstart frÃ¥n USB-minnen. Miroslav KuÅ™e 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." -msgstr "" +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 "Mycket behjälplig text och information hittades i Jim Minthas HOWTO för uppstart via nätverket (ingen URL tillgänglig), <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>, <ulink url=\"&url-sparc-linux-faq;\">Linux för SPARC-processorer FAQ</ulink>, <ulink url=\"&url-alpha-faq;\">Linux/Alpha FAQ</ulink> bland andra. Ansvariga för dessa fritt tillgängliga och rikliga källor av information mÃ¥ste erkännas." #. 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 #, no-c-format msgid "Trademark Acknowledgement" -msgstr "" +msgstr "Varumärken" #. Tag: para #: administrivia.xml:148 #, no-c-format msgid "All trademarks are property of their respective trademark owners." -msgstr "" +msgstr "Alla varumärken tillhör sina respektive ägare." + diff --git a/po/sv/boot-installer.po b/po/sv/boot-installer.po index bd3d5a8c6..4a0b3d209 100755 --- a/po/sv/boot-installer.po +++ b/po/sv/boot-installer.po @@ -6,9 +6,9 @@ msgid "" msgstr "" "Project-Id-Version: installation-guide 20051025 boot-installer\n" "POT-Creation-Date: 2001-02-09 01:25+0100\n" -"PO-Revision-Date: 2005-11-16 22:42+0100\n" +"PO-Revision-Date: 2005-11-21 00:08+0100\n" "Last-Translator: Daniel Nylander <po@danielnylander.se>\n" -"Language-Team: Swedish <sv@li.org>\n" +"Language-Team: Swedish <tp-sv@listor.tp-sv.se>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -19,13 +19,13 @@ msgstr "" #: boot-installer.xml:4 #, no-c-format msgid "Booting the Installation System" -msgstr "" +msgstr "Starta upp installationssystemet" #. Tag: title #: boot-installer.xml:9 #, no-c-format msgid "Booting the Installer on &arch-title;" -msgstr "" +msgstr "Starta upp installeraren pÃ¥ &arch-title;" #. Tag: title #: boot-installer.xml:20 @@ -36,95 +36,55 @@ msgstr "" #. Tag: para #: boot-installer.xml:21 #, no-c-format -msgid "" -"Console firmware is stored in a flash ROM and started when an Alpha system " -"is powered up or reset. There are two different console specifications used " -"on Alpha systems, and hence two classes of console firmware available:" +msgid "Console firmware is stored in a flash ROM and started when an Alpha system is powered up or reset. There are two different console specifications used on Alpha systems, and hence two classes of console firmware available:" msgstr "" #. Tag: para #: boot-installer.xml:31 #, no-c-format -msgid "" -"<emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem " -"specification, which provides an operating environment for OpenVMS, Tru64 " -"UNIX, and Linux operating systems." +msgid "<emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem specification, which provides an operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems." msgstr "" #. Tag: para #: boot-installer.xml:38 #, no-c-format -msgid "" -"<emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the " -"Advanced RISC Computing (ARC) specification, which provides an operating " -"environment for Windows NT." +msgid "<emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the Advanced RISC Computing (ARC) specification, which provides an operating environment for Windows NT." msgstr "" #. Tag: para #: boot-installer.xml:47 #, no-c-format -msgid "" -"From the user's perspective, the most important difference between SRM and " -"ARC is that the choice of console constrains the possible disk-partitioning " -"scheme for the hard disk which you wish to boot off of." +msgid "From the user's perspective, the most important difference between SRM and ARC is that the choice of console constrains the possible disk-partitioning scheme for the hard disk which you wish to boot off of." msgstr "" #. Tag: para #: boot-installer.xml:54 #, no-c-format -msgid "" -"ARC requires that you use an MS-DOS partition table (as created by " -"<command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition " -"tables are the <quote>native</quote> partition format when booting from ARC. " -"In fact, since AlphaBIOS contains a disk partitioning utility, you may " -"prefer to partition your disks from the firmware menus before installing " -"Linux." +msgid "ARC requires that you use an MS-DOS partition table (as created by <command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition tables are the <quote>native</quote> partition format when booting from ARC. In fact, since AlphaBIOS contains a disk partitioning utility, you may prefer to partition your disks from the firmware menus before installing Linux." msgstr "" #. Tag: para #: boot-installer.xml:63 #, no-c-format -msgid "" -"Conversely, SRM is <emphasis>incompatible</emphasis><footnote> <para> " -"Specifically, the bootsector format required by the Console Subsystem " -"Specification conflicts with the placement of the DOS partition table. </" -"para> </footnote> with MS-DOS partition tables. Since Tru64 Unix uses the " -"BSD disklabel format, this is the <quote>native</quote> partition format for " -"SRM installations." +msgid "Conversely, SRM is <emphasis>incompatible</emphasis><footnote> <para> Specifically, the bootsector format required by the Console Subsystem Specification conflicts with the placement of the DOS partition table. </para> </footnote> with MS-DOS partition tables. Since Tru64 Unix uses the BSD disklabel format, this is the <quote>native</quote> partition format for SRM installations." msgstr "" #. Tag: para #: boot-installer.xml:76 #, no-c-format -msgid "" -"GNU/Linux is the only operating system on Alpha that can be booted from both " -"console types, but &debian; &release; only supports booting on SRM-based " -"systems. If you have an Alpha for which no version of SRM is available, if " -"you will be dual-booting the system with Windows NT, or if your boot device " -"requires ARC console support for BIOS initialization, you will not be able " -"to use the &debian; &release; installer. You can still run &debian; " -"&release; on such systems by using other install media; for instance, you " -"can install Debian woody with MILO and upgrade." +msgid "GNU/Linux is the only operating system on Alpha that can be booted from both console types, but &debian; &release; only supports booting on SRM-based systems. If you have an Alpha for which no version of SRM is available, if you will be dual-booting the system with Windows NT, or if your boot device requires ARC console support for BIOS initialization, you will not be able to use the &debian; &release; installer. You can still run &debian; &release; on such systems by using other install media; for instance, you can install Debian woody with MILO and upgrade." msgstr "" #. Tag: para #: boot-installer.xml:87 #, no-c-format -msgid "" -"Because <command>MILO</command> is not available for any of the Alpha " -"systems currently in production (as of February 2000), and because it is no " -"longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM " -"firmware on your older Alpha, it is recommended that you use SRM when " -"possible." +msgid "Because <command>MILO</command> is not available for any of the Alpha systems currently in production (as of February 2000), and because it is no longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM firmware on your older Alpha, it is recommended that you use SRM when possible." msgstr "" #. Tag: para #: boot-installer.xml:95 #, no-c-format -msgid "" -"The following table summarizes available and supported system type/console " -"combinations (see <xref linkend=\"alpha-cpus\"/> for the system type names). " -"The word <quote>ARC</quote> below denotes any of the ARC-compliant consoles." +msgid "The following table summarizes available and supported system type/console combinations (see <xref linkend=\"alpha-cpus\"/> for the system type names). The word <quote>ARC</quote> below denotes any of the ARC-compliant consoles." msgstr "" #. Tag: entry @@ -146,11 +106,20 @@ msgid "alcor" msgstr "alcor" #. Tag: entry -#: boot-installer.xml:115 boot-installer.xml:118 boot-installer.xml:124 -#: boot-installer.xml:130 boot-installer.xml:133 boot-installer.xml:136 -#: boot-installer.xml:139 boot-installer.xml:145 boot-installer.xml:148 -#: boot-installer.xml:151 boot-installer.xml:160 boot-installer.xml:169 -#: boot-installer.xml:184 boot-installer.xml:187 +#: boot-installer.xml:115 +#: boot-installer.xml:118 +#: boot-installer.xml:124 +#: boot-installer.xml:130 +#: boot-installer.xml:133 +#: boot-installer.xml:136 +#: boot-installer.xml:139 +#: boot-installer.xml:145 +#: boot-installer.xml:148 +#: boot-installer.xml:151 +#: boot-installer.xml:160 +#: boot-installer.xml:169 +#: boot-installer.xml:184 +#: boot-installer.xml:187 #, no-c-format msgid "ARC or SRM" msgstr "ARC eller SRM" @@ -168,9 +137,15 @@ msgid "book1" msgstr "book1" #. Tag: entry -#: boot-installer.xml:121 boot-installer.xml:127 boot-installer.xml:142 -#: boot-installer.xml:154 boot-installer.xml:163 boot-installer.xml:166 -#: boot-installer.xml:172 boot-installer.xml:178 boot-installer.xml:181 +#: boot-installer.xml:121 +#: boot-installer.xml:127 +#: boot-installer.xml:142 +#: boot-installer.xml:154 +#: boot-installer.xml:163 +#: boot-installer.xml:166 +#: boot-installer.xml:172 +#: boot-installer.xml:178 +#: boot-installer.xml:181 #, no-c-format msgid "SRM only" msgstr "SRM endast" @@ -290,7 +265,9 @@ msgid "ruffian" msgstr "ruffian" #. Tag: entry -#: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193 +#: boot-installer.xml:175 +#: boot-installer.xml:190 +#: boot-installer.xml:193 #, no-c-format msgid "ARC only" msgstr "ARC endast" @@ -334,165 +311,110 @@ msgstr "<entry>xlt</entry>" #. Tag: para #: boot-installer.xml:200 #, no-c-format -msgid "" -"Generally, none of these consoles can boot Linux directly, so the assistance " -"of an intermediary bootloader is required. For the SRM console, " -"<command>aboot</command>, a small, platform-independent bootloader, is used. " -"See the (unfortunately outdated) <ulink url=\"&url-srm-howto;\">SRM HOWTO</" -"ulink> for more information on <command>aboot</command>." +msgid "Generally, none of these consoles can boot Linux directly, so the assistance of an intermediary bootloader is required. For the SRM console, <command>aboot</command>, a small, platform-independent bootloader, is used. See the (unfortunately outdated) <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</command>." msgstr "" #. Tag: para #: boot-installer.xml:209 #, no-c-format -msgid "" -"The following paragraphs are from the woody install manual, and are included " -"here for reference; they may be useful to someone at a later date when " -"Debian supports MILO-based installs again." +msgid "The following paragraphs are from the woody install manual, and are included here for reference; they may be useful to someone at a later date when Debian supports MILO-based installs again." msgstr "" #. Tag: para #: boot-installer.xml:215 #, no-c-format -msgid "" -"Generally, none of these consoles can boot Linux directly, so the assistance " -"of an intermediary bootloader is required. There are two mainstream Linux " -"loaders: <command>MILO</command> and <command>aboot</command>." +msgid "Generally, none of these consoles can boot Linux directly, so the assistance of an intermediary bootloader is required. There are two mainstream Linux loaders: <command>MILO</command> and <command>aboot</command>." msgstr "" #. Tag: para #: boot-installer.xml:221 #, no-c-format -msgid "" -"<command>MILO</command> is itself a console, which replaces ARC or SRM in " -"memory. <command>MILO</command> can be booted from both ARC and SRM and is " -"the only way to bootstrap Linux from the ARC console. <command>MILO</" -"command> is platform-specific (a different <command>MILO</command> is needed " -"for each system type) and exist only for those systems, for which ARC " -"support is shown in the table above. See also the (unfortunately outdated) " -"<ulink url=\"&url-milo-howto;\">MILO HOWTO</ulink>." +msgid "<command>MILO</command> is itself a console, which replaces ARC or SRM in memory. <command>MILO</command> can be booted from both ARC and SRM and is the only way to bootstrap Linux from the ARC console. <command>MILO</command> is platform-specific (a different <command>MILO</command> is needed for each system type) and exist only for those systems, for which ARC support is shown in the table above. See also the (unfortunately outdated) <ulink url=\"&url-milo-howto;\">MILO HOWTO</ulink>." msgstr "" #. Tag: para #: boot-installer.xml:231 #, no-c-format -msgid "" -"<command>aboot</command> is a small, platform-independent bootloader, which " -"runs from SRM only. See the (also unfortunately outdated) <ulink url=\"&url-" -"srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</" -"command>." +msgid "<command>aboot</command> is a small, platform-independent bootloader, which runs from SRM only. See the (also unfortunately outdated) <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</command>." msgstr "" #. Tag: para #: boot-installer.xml:238 #, no-c-format msgid "" -"Thus, three scenarios are generally possible, depending on the system's " -"console firmware and whether or not <command>MILO</command> is available: " -"<informalexample><screen>\n" +"Thus, three scenarios are generally possible, depending on the system's console firmware and whether or not <command>MILO</command> is available: <informalexample><screen>\n" "SRM -> aboot\n" "SRM -> MILO\n" "ARC -> MILO\n" -"</screen></informalexample> Because <command>MILO</command> is not available " -"for any of the Alpha systems currently in production (as of February 2000), " -"and because it is no longer necessary to buy an OpenVMS or Tru64 Unix " -"license to have SRM firmware on your older Alpha, it is recommended that you " -"use SRM and <command>aboot</command> on new installations of GNU/Linux, " -"unless you wish to dual-boot with Windows NT." +"</screen></informalexample> Because <command>MILO</command> is not available for any of the Alpha systems currently in production (as of February 2000), and because it is no longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM firmware on your older Alpha, it is recommended that you use SRM and <command>aboot</command> on new installations of GNU/Linux, unless you wish to dual-boot with Windows NT." msgstr "" #. Tag: para #: boot-installer.xml:253 #, no-c-format -msgid "" -"The majority of AlphaServers and all current server and workstation products " -"contain both SRM and AlphaBIOS in their firmware. For <quote>half-flash</" -"quote> machines such as the various evaluation boards, it is possible to " -"switch from one version to another by reflashing the firmware. Also, once " -"SRM is installed, it is possible to run ARC/AlphaBIOS from a floppy disk " -"(using the <command>arc</command> command). For the reasons mentioned above, " -"we recommend switching to SRM before installing &debian;." +msgid "The majority of AlphaServers and all current server and workstation products contain both SRM and AlphaBIOS in their firmware. For <quote>half-flash</quote> machines such as the various evaluation boards, it is possible to switch from one version to another by reflashing the firmware. Also, once SRM is installed, it is possible to run ARC/AlphaBIOS from a floppy disk (using the <command>arc</command> command). For the reasons mentioned above, we recommend switching to SRM before installing &debian;." msgstr "" #. Tag: para #: boot-installer.xml:264 #, no-c-format -msgid "" -"As on other architectures, you should install the newest available revision " -"of the firmware<footnote> <para> Except on Jensen, where Linux is not " -"supported on firmware versions newer than 1.7 — see <ulink url=\"&url-" -"jensen-howto;\"></ulink> for more information. </para> </footnote> before " -"installing &debian;. For Alpha, firmware updates can be obtained from <ulink " -"url=\"&url-alpha-firmware;\">Alpha Firmware Updates</ulink>." +msgid "As on other architectures, you should install the newest available revision of the firmware<footnote> <para> Except on Jensen, where Linux is not supported on firmware versions newer than 1.7 — see <ulink url=\"&url-jensen-howto;\"></ulink> for more information. </para> </footnote> before installing &debian;. For Alpha, firmware updates can be obtained from <ulink url=\"&url-alpha-firmware;\">Alpha Firmware Updates</ulink>." msgstr "" #. Tag: title -#: boot-installer.xml:283 boot-installer.xml:892 boot-installer.xml:1384 -#: boot-installer.xml:1889 boot-installer.xml:1971 boot-installer.xml:2311 +#: boot-installer.xml:283 +#: boot-installer.xml:892 +#: boot-installer.xml:1384 +#: boot-installer.xml:1889 +#: boot-installer.xml:1971 +#: boot-installer.xml:2311 #: boot-installer.xml:2407 #, no-c-format msgid "Booting with TFTP" -msgstr "" +msgstr "Uppstart via TFTP" #. Tag: para #: boot-installer.xml:284 #, no-c-format msgid "" -"In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput> " -"prefix, and will be listed in the output of the <userinput>show dev</" -"userinput> command, like this (edited slightly): <informalexample><screen>\n" +"In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput> prefix, and will be listed in the output of the <userinput>show dev</userinput> command, like this (edited slightly): <informalexample><screen>\n" ">>> show dev\n" "ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65\n" "ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54\n" "ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0\n" -"</screen></informalexample> You first need to set the boot protocol: " -"<informalexample><screen>\n" +"</screen></informalexample> You first need to set the boot protocol: <informalexample><screen>\n" ">>> set ewa0_protocol bootp\n" -"</screen></informalexample> Then check the medium type is correct: " -"<informalexample><screen>\n" +"</screen></informalexample> Then check the medium type is correct: <informalexample><screen>\n" ">>> set ewa0_mode <replaceable>mode</replaceable>\n" -"</screen></informalexample> You can get a listing of valid modes with " -"<userinput>>>>set ewa0_mode</userinput>." +"</screen></informalexample> You can get a listing of valid modes with <userinput>>>>set ewa0_mode</userinput>." msgstr "" #. Tag: para #: boot-installer.xml:302 #, no-c-format msgid "" -"Then, to boot from the first Ethernet interface, you would type: " -"<informalexample><screen>\n" +"Then, to boot from the first Ethernet interface, you would type: <informalexample><screen>\n" ">>> boot ewa0 -flags \"\"\n" -"</screen></informalexample> This will boot using the default kernel " -"parameters as included in the netboot image." +"</screen></informalexample> This will boot using the default kernel parameters as included in the netboot image." msgstr "" #. Tag: para #: boot-installer.xml:311 #, no-c-format -msgid "" -"If you wish to use a serial console, you <emphasis>must</emphasis> pass the " -"<userinput>console=</userinput> parameter to the kernel. This can be done " -"using the <userinput>-flags</userinput> argument to the SRM <userinput>boot</" -"userinput> command. The serial ports are named the same as their " -"corresponding files in <userinput>/dev</userinput>. Also, when specifying " -"additional kernel parameters, you must repeat certain default options that " -"are needed by the &d-i; images. For example, to boot from <userinput>ewa0</" -"userinput> and use a console on the first serial port, you would type:" +msgid "If you wish to use a serial console, you <emphasis>must</emphasis> pass the <userinput>console=</userinput> parameter to the kernel. This can be done using the <userinput>-flags</userinput> argument to the SRM <userinput>boot</userinput> command. The serial ports are named the same as their corresponding files in <userinput>/dev</userinput>. Also, when specifying additional kernel parameters, you must repeat certain default options that are needed by the &d-i; images. For example, to boot from <userinput>ewa0</userinput> and use a console on the first serial port, you would type:" msgstr "" #. Tag: screen #: boot-installer.xml:323 #, no-c-format -msgid "" -">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -"console=ttyS0"" +msgid ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0"" msgstr "" #. Tag: title #: boot-installer.xml:328 #, no-c-format msgid "Booting from CD-ROM with the SRM Console" -msgstr "" +msgstr "Uppstart frÃ¥n cd-rom med SRM-konsoll" #. Tag: para #: boot-installer.xml:329 @@ -500,8 +422,7 @@ msgstr "" msgid "" "Type <informalexample><screen>\n" ">>> boot xxxx -flags 0\n" -"</screen></informalexample> where <replaceable>xxxx</replaceable> is your CD-" -"ROM drive in SRM notation." +"</screen></informalexample> where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation." msgstr "" #. Tag: title @@ -513,61 +434,39 @@ msgstr "" #. Tag: para #: boot-installer.xml:342 #, no-c-format -msgid "" -"To boot a CD-ROM from the ARC console, find your sub-architecture code name " -"(see <xref linkend=\"alpha-cpus\"/>), then enter <filename>\\milo\\linload." -"exe</filename> as the boot loader and <filename>\\milo" -"\\<replaceable>subarch</replaceable></filename> (where <replaceable>subarch</" -"replaceable> is the proper subarchitecture name) as the OS Path in the `OS " -"Selection Setup' menu. Ruffians make an exception: You need to use <filename>" -"\\milo\\ldmilo.exe</filename> as boot loader." +msgid "To boot a CD-ROM from the ARC console, find your sub-architecture code name (see <xref linkend=\"alpha-cpus\"/>), then enter <filename>\\milo\\linload.exe</filename> as the boot loader and <filename>\\milo\\<replaceable>subarch</replaceable></filename> (where <replaceable>subarch</replaceable> is the proper subarchitecture name) as the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: You need to use <filename>\\milo\\ldmilo.exe</filename> as boot loader." msgstr "" #. Tag: title #: boot-installer.xml:358 #, no-c-format msgid "Booting from Floppies with the SRM Console" -msgstr "" +msgstr "Uppstart frÃ¥n startdisketter med SRM-konsoll" #. Tag: para #: boot-installer.xml:359 #, no-c-format msgid "" -"At the SRM prompt (<prompt>>>></prompt>), issue the following " -"command: <informalexample><screen>\n" +"At the SRM prompt (<prompt>>>></prompt>), issue the following command: <informalexample><screen>\n" ">>> boot dva0 -flags 0\n" -"</screen></informalexample> possibly replacing <filename>dva0</filename> " -"with the actual device name. Usually, <filename>dva0</filename> is the " -"floppy; type <informalexample><screen>\n" +"</screen></informalexample> possibly replacing <filename>dva0</filename> with the actual device name. Usually, <filename>dva0</filename> is the floppy; type <informalexample><screen>\n" ">>> show dev\n" -"</screen></informalexample> to see the list of devices (e.g., if you want to " -"boot from a CD). Note that if you are booting via MILO, <command>-flags</" -"command> argument is ignored, so you can just type <command>boot dva0</" -"command>. If everything works OK, you will eventually see the Linux kernel " -"boot." +"</screen></informalexample> to see the list of devices (e.g., if you want to boot from a CD). Note that if you are booting via MILO, <command>-flags</command> argument is ignored, so you can just type <command>boot dva0</command>. If everything works OK, you will eventually see the Linux kernel boot." msgstr "" #. Tag: para #: boot-installer.xml:376 #, no-c-format msgid "" -"If you want to specify kernel parameters when booting via <command>aboot</" -"command>, use the following command: <informalexample><screen>\n" -">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -"load_ramdisk=1 arguments\"\n" -"</screen></informalexample> (typed on one line), substituting, if necessary, " -"the actual SRM boot device name for <filename>dva0</filename>, the Linux " -"boot device name for <filename>fd0</filename>, and the desired kernel " -"parameters for <filename>arguments</filename>." +"If you want to specify kernel parameters when booting via <command>aboot</command>, use the following command: <informalexample><screen>\n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 load_ramdisk=1 arguments\"\n" +"</screen></informalexample> (typed on one line), substituting, if necessary, the actual SRM boot device name for <filename>dva0</filename>, the Linux boot device name for <filename>fd0</filename>, and the desired kernel parameters for <filename>arguments</filename>." msgstr "" #. Tag: para #: boot-installer.xml:388 #, no-c-format -msgid "" -"If you want to specify kernel parameters when booting via <command>MILO</" -"command>, you will have to interrupt bootstrap once you get into MILO. See " -"<xref linkend=\"booting-from-milo\"/>." +msgid "If you want to specify kernel parameters when booting via <command>MILO</command>, you will have to interrupt bootstrap once you get into MILO. See <xref linkend=\"booting-from-milo\"/>." msgstr "" #. Tag: title @@ -579,131 +478,114 @@ msgstr "" #. Tag: para #: boot-installer.xml:400 #, no-c-format -msgid "" -"In the OS Selection menu, set <command>linload.exe</command> as the boot " -"loader, and <command>milo</command> as the OS Path. Bootstrap using the " -"newly created entry." +msgid "In the OS Selection menu, set <command>linload.exe</command> as the boot loader, and <command>milo</command> as the OS Path. Bootstrap using the newly created entry." msgstr "" #. Tag: title #: boot-installer.xml:409 #, no-c-format msgid "Booting with MILO" -msgstr "" +msgstr "Uppstart med MILO" #. Tag: para #: boot-installer.xml:410 #, no-c-format -msgid "" -"MILO contained on the bootstrap media is configured to proceed straight to " -"Linux automatically. Should you wish to intervene, all you need is to press " -"space during MILO countdown." +msgid "MILO contained on the bootstrap media is configured to proceed straight to Linux automatically. Should you wish to intervene, all you need is to press space during MILO countdown." msgstr "" #. Tag: para #: boot-installer.xml:416 #, no-c-format msgid "" -"If you want to specify all the bits explicitly (for example, to supply " -"additional parameters), you can use a command like this: " -"<informalexample><screen>\n" +"If you want to specify all the bits explicitly (for example, to supply additional parameters), you can use a command like this: <informalexample><screen>\n" "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->\n" -"</screen></informalexample> If you are booting from something other than a " -"floppy, substitute <filename>fd0</filename> in the above example with the " -"appropriate device name in Linux notation. The <command>help</command> " -"command would give you a brief MILO command reference." +"</screen></informalexample> If you are booting from something other than a floppy, substitute <filename>fd0</filename> in the above example with the appropriate device name in Linux notation. The <command>help</command> command would give you a brief MILO command reference." msgstr "" #. Tag: title #: boot-installer.xml:435 #, no-c-format msgid "Booting from TFTP" -msgstr "" +msgstr "Uppstart frÃ¥n TFTP" #. Tag: para -#: boot-installer.xml:441 boot-installer.xml:898 boot-installer.xml:1402 -#: boot-installer.xml:1895 boot-installer.xml:2317 boot-installer.xml:2413 +#: boot-installer.xml:441 +#: boot-installer.xml:898 +#: boot-installer.xml:1402 +#: boot-installer.xml:1895 +#: boot-installer.xml:2317 +#: boot-installer.xml:2413 #, no-c-format -msgid "" -"Booting from the network requires that you have a network connection and a " -"TFTP network boot server (DHCP, RARP, or BOOTP)." +msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)." msgstr "" #. Tag: para -#: boot-installer.xml:446 boot-installer.xml:903 boot-installer.xml:1407 -#: boot-installer.xml:1900 boot-installer.xml:2322 boot-installer.xml:2418 +#: boot-installer.xml:446 +#: boot-installer.xml:903 +#: boot-installer.xml:1407 +#: boot-installer.xml:1900 +#: boot-installer.xml:2322 +#: boot-installer.xml:2418 #, no-c-format -msgid "" -"Older systems such as the 715 might require the use of an RBOOT server " -"instead of a BOOTP server." +msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server." msgstr "" #. Tag: para -#: boot-installer.xml:451 boot-installer.xml:908 boot-installer.xml:1412 -#: boot-installer.xml:1905 boot-installer.xml:2327 boot-installer.xml:2423 +#: boot-installer.xml:451 +#: boot-installer.xml:908 +#: boot-installer.xml:1412 +#: boot-installer.xml:1905 +#: boot-installer.xml:2327 +#: boot-installer.xml:2423 #, no-c-format -msgid "" -"The installation method to support network booting is described in <xref " -"linkend=\"install-tftp\"/>." +msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>." msgstr "" #. Tag: title #: boot-installer.xml:459 #, no-c-format msgid "Booting from TFTP on NetWinder" -msgstr "" +msgstr "Uppstart frÃ¥n TFTP pÃ¥ NetWinder" #. Tag: para #: boot-installer.xml:461 #, no-c-format -msgid "" -"NetWinders have two network interfaces: The 10Mbps NE2000-compatible card is " -"<filename>eth0</filename> and the 100Mbps Tulip card is <filename>eth1</" -"filename>." +msgid "NetWinders have two network interfaces: The 10Mbps NE2000-compatible card is <filename>eth0</filename> and the 100Mbps Tulip card is <filename>eth1</filename>." msgstr "" #. Tag: para #: boot-installer.xml:467 #, no-c-format -msgid "" -"You need NeTTrom 2.2.1 or later to boot the installation system. NeTTrom " -"2.3.3 is recommended: get these files from <ulink url=\"ftp://ftp.netwinder." -"org/pub/netwinder/firmware/\"></ulink>:" +msgid "You need NeTTrom 2.2.1 or later to boot the installation system. NeTTrom 2.3.3 is recommended: get these files from <ulink url=\"ftp://ftp.netwinder.org/pub/netwinder/firmware/\"></ulink>:" msgstr "" #. Tag: filename #: boot-installer.xml:476 #, no-c-format msgid "nettrom-2.3-3.armv4l.rpm" -msgstr "" +msgstr "nettrom-2.3-3.armv4l.rpm" #. Tag: filename #: boot-installer.xml:481 #, no-c-format msgid "nettrom-2.3.3.bin" -msgstr "" +msgstr "nettrom-2.3.3.bin" #. Tag: filename #: boot-installer.xml:486 #, no-c-format msgid "nettrom-2.3.3.bin.md5sum" -msgstr "" +msgstr "nettrom-2.3.3.bin.md5sum" #. Tag: para #: boot-installer.xml:491 #, no-c-format msgid "" -"After rebooting and interrupting the boot process during the countdown, you " -"must first configure the network either with a static address: " -"<informalexample><screen>\n" +"After rebooting and interrupting the boot process during the countdown, you must first configure the network either with a static address: <informalexample><screen>\n" " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" -"</screen></informalexample> where 24 is the number of set bits in the " -"netmask, or a dynamic address: <informalexample><screen>\n" +"</screen></informalexample> where 24 is the number of set bits in the netmask, or a dynamic address: <informalexample><screen>\n" " NeTTrom command-> boot diskless\n" -"</screen></informalexample> You may also need to configure the " -"<userinput>route1</userinput> settings if the TFTP server is not on the " -"local subnet. The rest of the config is pretty standard (the save-all step " -"is optional): <informalexample><screen>\n" +"</screen></informalexample> You may also need to configure the <userinput>route1</userinput> settings if the TFTP server is not on the local subnet. The rest of the config is pretty standard (the save-all step is optional): <informalexample><screen>\n" " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" " NeTTrom command-> setenv kerntftpfile boot.img\n" " NeTTrom command-> save-all\n" @@ -711,147 +593,117 @@ msgid "" " NeTTrom command-> setenv kernconfig tftp\n" " NeTTrom command-> setenv rootdev /dev/ram\n" " NeTTrom command-> setenv cmdappend root=/dev/ram\n" -"</screen></informalexample> Only the last four of these interfere with " -"normal disk booting, so it is safe to issue <command>save-all</command> " -"right before them, which will store the network settings in case you need to " -"boot from the network again. If you want to use the serial console to " -"install your NetWinder, you also need the following setting: " -"<informalexample><screen>\n" -" NeTTrom command-> setenv cmdappend root=/dev/ram " -"console=ttyS0,115200\n" -"</screen></informalexample> Use the <command>printenv</command> command to " -"review your environment settings. Finally, if your <envar>cmdappend</envar> " -"NeTTrom variable has the <option>noinitrd</option> option, you must remove " -"it so the downloaded kernel can boot with its attached ramdisk." +"</screen></informalexample> Only the last four of these interfere with normal disk booting, so it is safe to issue <command>save-all</command> right before them, which will store the network settings in case you need to boot from the network again. If you want to use the serial console to install your NetWinder, you also need the following setting: <informalexample><screen>\n" +" NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200\n" +"</screen></informalexample> Use the <command>printenv</command> command to review your environment settings. Finally, if your <envar>cmdappend</envar> NeTTrom variable has the <option>noinitrd</option> option, you must remove it so the downloaded kernel can boot with its attached ramdisk." msgstr "" #. Tag: title #: boot-installer.xml:527 #, no-c-format msgid "Booting from TFTP on CATS" -msgstr "" +msgstr "Uppstart frÃ¥n TFTP pÃ¥ CATS" #. Tag: para #: boot-installer.xml:529 #, no-c-format -msgid "" -"On CATS machines, use <command>boot de0:</command> or similar at the Cyclone " -"prompt." +msgid "On CATS machines, use <command>boot de0:</command> or similar at the Cyclone prompt." msgstr "" #. Tag: title #: boot-installer.xml:540 #, no-c-format msgid "Booting from CD-ROM" -msgstr "" +msgstr "Uppstart frÃ¥n cd-rom" #. Tag: para -#: boot-installer.xml:546 boot-installer.xml:599 boot-installer.xml:1021 -#: boot-installer.xml:1852 boot-installer.xml:2099 boot-installer.xml:2453 +#: boot-installer.xml:546 +#: boot-installer.xml:599 +#: boot-installer.xml:1021 +#: boot-installer.xml:1852 +#: boot-installer.xml:2099 +#: boot-installer.xml:2453 #, no-c-format -msgid "" -"The easiest route for most people will be to use a set of Debian CDs. If you " -"have a CD set, and if your machine supports booting directly off the CD, " -"great! Simply <phrase arch=\"i386\"> configure your system for booting off a " -"CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert " -"your CD, reboot, and proceed to the next chapter." +msgid "The easiest route for most people will be to use a set of Debian CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply <phrase arch=\"i386\"> configure your system for booting off a CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert your CD, reboot, and proceed to the next chapter." msgstr "" #. Tag: para -#: boot-installer.xml:557 boot-installer.xml:610 boot-installer.xml:1032 -#: boot-installer.xml:1863 boot-installer.xml:2110 boot-installer.xml:2464 +#: boot-installer.xml:557 +#: boot-installer.xml:610 +#: boot-installer.xml:1032 +#: boot-installer.xml:1863 +#: boot-installer.xml:2110 +#: boot-installer.xml:2464 #, no-c-format -msgid "" -"Note that certain CD drives may require special drivers, and thus be " -"inaccessible in the early installation stages. If it turns out the standard " -"way of booting off a CD doesn't work for your hardware, revisit this chapter " -"and read about alternate kernels and installation methods which may work for " -"you." +msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you." msgstr "" #. Tag: para -#: boot-installer.xml:565 boot-installer.xml:618 boot-installer.xml:1040 -#: boot-installer.xml:1871 boot-installer.xml:2118 boot-installer.xml:2472 +#: boot-installer.xml:565 +#: boot-installer.xml:618 +#: boot-installer.xml:1040 +#: boot-installer.xml:1871 +#: boot-installer.xml:2118 +#: boot-installer.xml:2472 #, no-c-format -msgid "" -"Even if you cannot boot from CD-ROM, you can probably install the Debian " -"system components and any packages you want from CD-ROM. Simply boot using a " -"different media, such as floppies. When it's time to install the operating " -"system, base system, and any additional packages, point the installation " -"system at the CD-ROM drive." +msgid "Even if you cannot boot from CD-ROM, you can probably install the Debian system components and any packages you want from CD-ROM. Simply boot using a different media, such as floppies. When it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive." msgstr "" #. Tag: para -#: boot-installer.xml:573 boot-installer.xml:626 boot-installer.xml:1048 -#: boot-installer.xml:1879 boot-installer.xml:2126 boot-installer.xml:2480 +#: boot-installer.xml:573 +#: boot-installer.xml:626 +#: boot-installer.xml:1048 +#: boot-installer.xml:1879 +#: boot-installer.xml:2126 +#: boot-installer.xml:2480 #, no-c-format -msgid "" -"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." +msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." msgstr "" #. Tag: para #: boot-installer.xml:580 #, no-c-format -msgid "" -"To boot a CD-ROM from the Cyclone console prompt, use the command " -"<command>boot cd0:cats.bin</command>" +msgid "To boot a CD-ROM from the Cyclone console prompt, use the command <command>boot cd0:cats.bin</command>" msgstr "" #. Tag: title -#: boot-installer.xml:593 boot-installer.xml:1015 boot-installer.xml:1840 -#: boot-installer.xml:2093 boot-installer.xml:2447 +#: boot-installer.xml:593 +#: boot-installer.xml:1015 +#: boot-installer.xml:1840 +#: boot-installer.xml:2093 +#: boot-installer.xml:2447 #, no-c-format msgid "Booting from a CD-ROM" -msgstr "" +msgstr "Uppstart frÃ¥n en cd-rom" #. Tag: title #: boot-installer.xml:731 #, no-c-format -msgid "" -"Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" +msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para #: boot-installer.xml:734 #, no-c-format -msgid "" -"To boot the installer from hard disk, you must first download and place the " -"needed files as described in <xref linkend=\"boot-drive-files\"/>." +msgid "To boot the installer from hard disk, you must first download and place the needed files as described in <xref linkend=\"boot-drive-files\"/>." msgstr "" #. Tag: para #: boot-installer.xml:739 #, no-c-format -msgid "" -"If you intend to use the hard drive only for booting and then download " -"everything over the network, you should download the <filename>netboot/" -"debian-installer/i386/initrd.gz</filename> file and its corresponding " -"kernel. This will allow you to repartition the hard disk from which you boot " -"the installer, although you should do so with care." +msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/i386/initrd.gz</filename> file and its corresponding kernel. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care." msgstr "" #. Tag: para #: boot-installer.xml:747 #, no-c-format -msgid "" -"Alternatively, if you intend to keep an existing partition on the hard drive " -"unchanged during the install, you can download the <filename>hd-media/initrd." -"gz</filename> file and its kernel, as well as copy a CD iso to the drive " -"(make sure the file is named ending in <literal>.iso</literal>). The " -"installer can then boot from the drive and install from the CD image, " -"without needing the network." +msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD image, without needing the network." msgstr "" #. Tag: para #: boot-installer.xml:756 #, no-c-format -msgid "" -"For <command>LILO</command>, you will need to configure two essential things " -"in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to " -"load the <filename>initrd.gz</filename> installer at boot time; </para></" -"listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use " -"a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is " -"a <filename>/etc/lilo.conf</filename> example:" +msgid "For <command>LILO</command>, you will need to configure two essential things in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to load the <filename>initrd.gz</filename> installer at boot time; </para></listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is a <filename>/etc/lilo.conf</filename> example:" msgstr "" #. Tag: screen @@ -862,149 +714,100 @@ msgid "" " label=newinstall\n" " initrd=/boot/newinstall/initrd.gz\n" " root=/dev/ram0\n" -" append=\"<phrase condition=\"sarge\">devfs=mount,dall </" -"phrase>ramdisk_size=12000\"" +" append=\"<phrase condition=\"sarge\">devfs=mount,dall </phrase>ramdisk_size=12000\"" msgstr "" #. Tag: para #: boot-installer.xml:777 #, no-c-format -msgid "" -"For more details, refer to the <citerefentry><refentrytitle>initrd</" -"refentrytitle> <manvolnum>4</manvolnum></citerefentry> and " -"<citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</" -"manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and " -"reboot." +msgid "For more details, refer to the <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> and <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and reboot." msgstr "" #. Tag: para #: boot-installer.xml:786 #, no-c-format msgid "" -"The procedure for <command>GRUB</command> is quite similar. Locate your " -"<filename>menu.lst</filename> in the <filename>/boot/grub/</filename> " -"directory (sometimes in the <filename>/boot/boot/grub/</filename>), add the " -"following lines: <informalexample><screen>\n" +"The procedure for <command>GRUB</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (sometimes in the <filename>/boot/boot/grub/</filename>), add the following lines: <informalexample><screen>\n" "title New Install\n" "kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n" "initrd (hd0,0)/boot/newinstall/initrd.gz\n" -"</screen></informalexample> and reboot. <phrase condition=\"sarge\">If the " -"boot fails, you can try adding <userinput>devfs=mount,dall</userinput> to " -"the <quote>kernel</quote> line. </phrase>" +"</screen></informalexample> and reboot. <phrase condition=\"sarge\">If the boot fails, you can try adding <userinput>devfs=mount,dall</userinput> to the <quote>kernel</quote> line. </phrase>" msgstr "" #. Tag: para #: boot-installer.xml:799 #, no-c-format -msgid "" -"Note that the value of the <userinput>ramdisk_size</userinput> may need to " -"be adjusted for the size of the initrd image. From here on, there should be " -"no difference between <command>GRUB</command> or <command>LILO</command>." +msgid "Note that the value of the <userinput>ramdisk_size</userinput> may need to be adjusted for the size of the initrd image. From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>." msgstr "" #. Tag: title #: boot-installer.xml:810 #, no-c-format msgid "Booting from USB Memory Stick" -msgstr "" +msgstr "Uppstart frÃ¥n USB-minne" #. Tag: para #: boot-installer.xml:811 #, no-c-format -msgid "" -"Let's assume you have prepared everything from <xref linkend=\"boot-dev-" -"select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB " -"stick into some free USB connector and reboot the computer. The system " -"should boot up, and you should be presented with the <prompt>boot:</prompt> " -"prompt. Here you can enter optional boot arguments, or just hit &enterkey;." +msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;." msgstr "" #. Tag: para #: boot-installer.xml:820 #, no-c-format -msgid "" -"In case your computer doesn't support booting from USB memory devices, you " -"can still use a single floppy to do the initial boot and then switch to USB. " -"Boot your system as described in <xref linkend=\"floppy-boot\"/>; the kernel " -"on the boot floppy should detect your USB stick automatically. When it asks " -"for the root floppy, simply press &enterkey;. You should see &d-i; starting." +msgid "In case your computer doesn't support booting from USB memory devices, you can still use a single floppy to do the initial boot and then switch to USB. Boot your system as described in <xref linkend=\"floppy-boot\"/>; the kernel on the boot floppy should detect your USB stick automatically. When it asks for the root floppy, simply press &enterkey;. You should see &d-i; starting." msgstr "" #. Tag: title -#: boot-installer.xml:833 boot-installer.xml:1952 boot-installer.xml:2353 +#: boot-installer.xml:833 +#: boot-installer.xml:1952 +#: boot-installer.xml:2353 #: boot-installer.xml:2501 #, no-c-format msgid "Booting from Floppies" -msgstr "" +msgstr "Uppstart frÃ¥n startdisketter" #. Tag: para -#: boot-installer.xml:834 boot-installer.xml:2361 +#: boot-installer.xml:834 +#: boot-installer.xml:2361 #, no-c-format -msgid "" -"You will have already downloaded the floppy images you needed and created " -"floppies from the images in <xref linkend=\"create-floppy\"/>." +msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>." msgstr "" #. Tag: para #: boot-installer.xml:841 #, no-c-format -msgid "" -"To boot from the installer boot floppy, place it in the primary floppy " -"drive, shut down the system as you normally would, then turn it back on." +msgid "To boot from the installer boot floppy, place it in the primary floppy drive, shut down the system as you normally would, then turn it back on." msgstr "" #. Tag: para #: boot-installer.xml:847 #, no-c-format -msgid "" -"For installing from an LS-120 drive (ATAPI version) with a set of floppies, " -"you need to specify the virtual location for the floppy device. This is done " -"with the <emphasis>root=</emphasis> boot argument, giving the device that " -"the ide-floppy driver maps the device to. For example, if your LS-120 drive " -"is connected as the first IDE device (master) on the second cable, you enter " -"<userinput>linux root=/dev/hdc</userinput> at the boot prompt. Installation " -"from LS-120 is only supported by 2.4 and later kernels." +msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>linux root=/dev/hdc</userinput> at the boot prompt. Installation from LS-120 is only supported by 2.4 and later kernels." msgstr "" #. Tag: para #: boot-installer.xml:858 #, no-c-format -msgid "" -"Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</" -"keycap> <keycap>Delete</keycap></keycombo> does not properly reset the " -"machine, so a <quote>hard</quote> reboot is recommended. If you are " -"installing from an existing operating system (e.g., from a DOS box) you " -"don't have a choice. Otherwise, please do a hard reboot when booting." +msgid "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not properly reset the machine, so a <quote>hard</quote> reboot is recommended. If you are installing from an existing operating system (e.g., from a DOS box) you don't have a choice. Otherwise, please do a hard reboot when booting." msgstr "" #. Tag: para #: boot-installer.xml:867 #, no-c-format -msgid "" -"The floppy disk will be accessed, and you should then see a screen that " -"introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt." +msgid "The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt." msgstr "" #. Tag: para #: boot-installer.xml:873 #, no-c-format -msgid "" -"Once you press &enterkey;, you should see the message " -"<computeroutput>Loading...</computeroutput>, followed by " -"<computeroutput>Uncompressing Linux...</computeroutput>, and then a " -"screenfull or so of information about the hardware in your system. More " -"information on this phase of the boot process can be found below in <xref " -"linkend=\"kernel-msgs\"/>." +msgid "Once you press &enterkey;, you should see the message <computeroutput>Loading...</computeroutput>, followed by <computeroutput>Uncompressing Linux...</computeroutput>, and then a screenfull or so of information about the hardware in your system. More information on this phase of the boot process can be found below in <xref linkend=\"kernel-msgs\"/>." msgstr "" #. Tag: para #: boot-installer.xml:882 #, no-c-format -msgid "" -"After booting from the boot floppy, the root floppy is requested. Insert the " -"root floppy and press &enterkey;, and the contents are loaded into memory. " -"The installer program <command>debian-installer</command> is automatically " -"launched." +msgid "After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched." msgstr "" #. Tag: para @@ -1022,11 +825,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:923 #, no-c-format -msgid "" -"It could be that your Network Interface Card or Motherboard provides PXE " -"boot functionality. This is a <trademark class=\"trade\">Intel</trademark> " -"re-implementation of TFTP boot. If so you may be able to configure your BIOS " -"to boot from the network." +msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel</trademark> re-implementation of TFTP boot. If so you may be able to configure your BIOS to boot from the network." msgstr "" #. Tag: title @@ -1038,31 +837,25 @@ msgstr "" #. Tag: para #: boot-installer.xml:935 #, no-c-format -msgid "" -"It could be that your Network Interface Card provides TFTP boot " -"functionality." +msgid "It could be that your Network Interface Card provides TFTP boot functionality." msgstr "" #. Tag: para #: boot-installer.xml:940 #, no-c-format -msgid "" -"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. " -"Please refer to this document." +msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document." msgstr "" #. Tag: title #: boot-installer.xml:948 #, no-c-format msgid "Etherboot" -msgstr "" +msgstr "Etherboot" #. Tag: para #: boot-installer.xml:949 #, no-c-format -msgid "" -"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> " -"provides bootdiskettes and even bootroms that do a TFTPboot." +msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" #. Tag: title @@ -1075,143 +868,69 @@ msgstr "" #: boot-installer.xml:959 #, no-c-format msgid "" -"When the installer boots, you should be presented with a friendly graphical " -"screen showing the Debian logo and the boot prompt: " -"<informalexample><screen>\n" +"When the installer boots, you should be presented with a friendly graphical screen showing the Debian logo and the boot prompt: <informalexample><screen>\n" "Press F1 for help, or ENTER to boot:\n" -"</screen></informalexample> At the boot prompt you can either just press " -"&enterkey; to boot the installer with default options or enter a specific " -"boot method and, optionally, boot parameters." +"</screen></informalexample> At the boot prompt you can either just press &enterkey; to boot the installer with default options or enter a specific boot method and, optionally, boot parameters." msgstr "" #. Tag: para #: boot-installer.xml:971 #, no-c-format -msgid "" -"Information on available boot methods and on boot parameters which might be " -"useful can be found by pressing <keycap>F2</keycap> through <phrase " -"condition=\"sarge\"><keycap>F7</keycap></phrase><phrase condition=\"etch" -"\"><keycap>F8</keycap></phrase>. If you add any parameters to the boot " -"command line, be sure to type the boot method (the default is " -"<userinput>linux</userinput>) and a space before the first parameter (e.g., " -"<userinput>linux debconf/priority=medium</userinput>)." +msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing <keycap>F2</keycap> through <phrase condition=\"sarge\"><keycap>F7</keycap></phrase><phrase condition=\"etch\"><keycap>F8</keycap></phrase>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>linux</userinput>) and a space before the first parameter (e.g., <userinput>linux debconf/priority=medium</userinput>)." msgstr "" #. Tag: para #: boot-installer.xml:981 #, no-c-format -msgid "" -"If you are installing the system via a remote management device that " -"provides a text interface to the VGA console, you may not be able to see the " -"initial graphical splash screen upon booting the installer; you may even not " -"see the boot prompt. Examples of these devices include the text console of " -"Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's " -"<quote>Integrated Remote Assistant</quote> (IRA). You can blindly press " -"F1<footnote> <para> In some cases these devices will require special escape " -"sequences to enact this keypress, for example the IRA uses <keycombo> " -"<keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</" -"keycap>. </para> </footnote> to bypass this screen and view the help text. " -"Once you are past the splash screen and at the help text your keystrokes " -"will be echoed at the prompt as expected. To prevent the installer from " -"using the framebuffer for the rest of the installation, you will also want " -"to add <userinput>debian-installer/framebuffer=false</userinput> to the boot " -"prompt, as described in the help text." +msgid "If you are installing the system via a remote management device that provides a text interface to the VGA console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot prompt. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA). You can blindly press F1<footnote> <para> In some cases these devices will require special escape sequences to enact this keypress, for example the IRA uses <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</keycap>. </para> </footnote> to bypass this screen and view the help text. Once you are past the splash screen and at the help text your keystrokes will be echoed at the prompt as expected. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>debian-installer/framebuffer=false</userinput> to the boot prompt, as described in the help text." msgstr "" #. Tag: title #: boot-installer.xml:1056 #, no-c-format msgid "CD Contents" -msgstr "" +msgstr "Cd-innehÃ¥ll" #. Tag: para #: boot-installer.xml:1058 #, no-c-format -msgid "" -"There are three basic variations of Debian Install CDs. The " -"<emphasis>Business Card</emphasis> CD has a minimal installation that will " -"fit on the small form factor CD media. It requires a network connection in " -"order to install the rest of the base installation and make a usable system. " -"The <emphasis>Network Install</emphasis> CD has all of the packages for a " -"base install but requires a network connection to a Debian mirror site in " -"order to install the extra packages one would want for a complete system . " -"The set of Debian CDs can install a complete system from the wide range of " -"packages without needing access to the network." +msgid "There are three basic variations of Debian Install CDs. The <emphasis>Business Card</emphasis> CD has a minimal installation that will fit on the small form factor CD media. It requires a network connection in order to install the rest of the base installation and make a usable system. The <emphasis>Network Install</emphasis> CD has all of the packages for a base install but requires a network connection to a Debian mirror site in order to install the extra packages one would want for a complete system . The set of Debian CDs can install a complete system from the wide range of packages without needing access to the network." msgstr "" #. Tag: para #: boot-installer.xml:1074 #, no-c-format -msgid "" -"The IA-64 architecture uses the next generation Extensible Firmware " -"Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows " -"little about the boot device other than the partition table and Master Boot " -"Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted " -"disk partitions. This simplifies the often arcane process of starting a " -"system. The system boot loader and the EFI firmware that supports it have a " -"full filesystem to store the files necessary for booting the machine. This " -"means that the system disk on an IA-64 system has an additional disk " -"partition dedicated to EFI instead of the simple MBR or boot block on more " -"conventional systems." +msgid "The IA-64 architecture uses the next generation Extensible Firmware Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows little about the boot device other than the partition table and Master Boot Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted disk partitions. This simplifies the often arcane process of starting a system. The system boot loader and the EFI firmware that supports it have a full filesystem to store the files necessary for booting the machine. This means that the system disk on an IA-64 system has an additional disk partition dedicated to EFI instead of the simple MBR or boot block on more conventional systems." msgstr "" #. Tag: para #: boot-installer.xml:1090 #, no-c-format -msgid "" -"The Debian Installer CD contains a small EFI partition where the " -"<command>ELILO</command> bootloader, its configuration file, the installer's " -"kernel, and initial filesystem (initrd) are located. The running system also " -"contains an EFI partition where the necessary files for booting the system " -"reside. These files are readable from the EFI Shell as described below." +msgid "The Debian Installer CD contains a small EFI partition where the <command>ELILO</command> bootloader, its configuration file, the installer's kernel, and initial filesystem (initrd) are located. The running system also contains an EFI partition where the necessary files for booting the system reside. These files are readable from the EFI Shell as described below." msgstr "" #. Tag: para #: boot-installer.xml:1099 #, no-c-format -msgid "" -"Most of the details of how <command>ELILO</command> actually loads and " -"starts a system are transparent to the system installer. However, the " -"installer must set up an EFI partition prior to installing the base system. " -"Otherwise, the installation of <command>ELILO</command> will fail, rendering " -"the system un-bootable. The EFI partition is allocated and formatted in the " -"partitioning step of the installation prior to loading any packages on the " -"system disk. The partitioning task also verifies that a suitable EFI " -"partition is present before allowing the installation to proceed." +msgid "Most of the details of how <command>ELILO</command> actually loads and starts a system are transparent to the system installer. However, the installer must set up an EFI partition prior to installing the base system. Otherwise, the installation of <command>ELILO</command> will fail, rendering the system un-bootable. The EFI partition is allocated and formatted in the partitioning step of the installation prior to loading any packages on the system disk. The partitioning task also verifies that a suitable EFI partition is present before allowing the installation to proceed." msgstr "" #. Tag: para #: boot-installer.xml:1111 #, no-c-format -msgid "" -"The EFI Boot Manager is presented as the last step of the firmware " -"initialization. It displays a menu list from which the user can select an " -"option. Depending on the model of system and what other software has been " -"loaded on the system, this menu may be different from one system to another. " -"There should be at least two menu items displayed, <command>Boot Option " -"Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. " -"Using the first option is preferred, however, if that option is not " -"available or the CD for some reason does not boot with it, use the second " -"option." +msgid "The EFI Boot Manager is presented as the last step of the firmware initialization. It displays a menu list from which the user can select an option. Depending on the model of system and what other software has been loaded on the system, this menu may be different from one system to another. There should be at least two menu items displayed, <command>Boot Option Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. Using the first option is preferred, however, if that option is not available or the CD for some reason does not boot with it, use the second option." msgstr "" #. Tag: title #: boot-installer.xml:1130 #, no-c-format msgid "IMPORTANT" -msgstr "" +msgstr "VIKTIGT" #. Tag: para #: boot-installer.xml:1131 #, no-c-format -msgid "" -"The EFI Boot Manager will select a default boot action, typically the first " -"menu choice, within a pre-set number of seconds. This is indicated by a " -"countdown at the bottom of the screen. Once the timer expires and the " -"systems starts the default action, you may have to reboot the machine in " -"order to continue the installation. If the default action is the EFI Shell, " -"you can return to the Boot Manager by running <command>exit</command> at the " -"shell prompt." +msgid "The EFI Boot Manager will select a default boot action, typically the first menu choice, within a pre-set number of seconds. This is indicated by a countdown at the bottom of the screen. Once the timer expires and the systems starts the default action, you may have to reboot the machine in order to continue the installation. If the default action is the EFI Shell, you can return to the Boot Manager by running <command>exit</command> at the shell prompt." msgstr "" #. Tag: title @@ -1223,62 +942,37 @@ msgstr "" #. Tag: para #: boot-installer.xml:1150 #, no-c-format -msgid "" -"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " -"display the EFI Boot Manager page and menu after it completes its system " -"initialization." +msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes its system initialization." msgstr "" #. Tag: para #: boot-installer.xml:1156 #, no-c-format -msgid "" -"Select <command>Boot Maintenance Menu</command> from the menu with the arrow " -"keys and press <command>ENTER</command>. This will display a new menu." +msgid "Select <command>Boot Maintenance Menu</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a new menu." msgstr "" #. Tag: para #: boot-installer.xml:1162 #, no-c-format -msgid "" -"Select <command>Boot From a File</command> from the menu with the arrow keys " -"and press <command>ENTER</command>. This will display a list of devices " -"probed by the firmware. You should see two menu lines containing either the " -"label <command>Debian Inst [Acpi ...</command> or <command>Removable Media " -"Boot</command>. If you examine the rest of the menu line, you will notice " -"that the device and controller information should be the same." +msgid "Select <command>Boot From a File</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a list of devices probed by the firmware. You should see two menu lines containing either the label <command>Debian Inst [Acpi ...</command> or <command>Removable Media Boot</command>. If you examine the rest of the menu line, you will notice that the device and controller information should be the same." msgstr "" #. Tag: para #: boot-installer.xml:1173 #, no-c-format -msgid "" -"You can choose either of the entries that refer to the CD/DVD drive. Select " -"your choice with the arrow keys and press <command>ENTER</command>. If you " -"choose <command>Removable Media Boot</command> the machine will immediately " -"start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</" -"command> instead, it will display a directory listing of the bootable " -"portion of the CD, requiring you to proceed to the next (additional) step." +msgid "You can choose either of the entries that refer to the CD/DVD drive. Select your choice with the arrow keys and press <command>ENTER</command>. If you choose <command>Removable Media Boot</command> the machine will immediately start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</command> instead, it will display a directory listing of the bootable portion of the CD, requiring you to proceed to the next (additional) step." msgstr "" #. Tag: para #: boot-installer.xml:1184 #, no-c-format -msgid "" -"You will only need this step if you chose <command>Debian Inst [Acpi ...</" -"command>. The directory listing will also show <command>[Treat like " -"Removable Media Boot]</command> on the next to the last line. Select this " -"line with the arrow keys and press <command>ENTER</command>. This will start " -"the boot load sequence." +msgid "You will only need this step if you chose <command>Debian Inst [Acpi ...</command>. The directory listing will also show <command>[Treat like Removable Media Boot]</command> on the next to the last line. Select this line with the arrow keys and press <command>ENTER</command>. This will start the boot load sequence." msgstr "" #. Tag: para #: boot-installer.xml:1196 #, no-c-format -msgid "" -"These steps start the Debian boot loader which will display a menu page for " -"you to select a boot kernel and options. Proceed to selecting the boot " -"kernel and options." +msgid "These steps start the Debian boot loader which will display a menu page for you to select a boot kernel and options. Proceed to selecting the boot kernel and options." msgstr "" #. Tag: title @@ -1290,135 +984,79 @@ msgstr "" #. Tag: para #: boot-installer.xml:1207 #, no-c-format -msgid "" -"If, for some reason, option 1 is not successful, reboot the machine and when " -"the EFI Boot Manager screen appears there should be one option called " -"<command>EFI Shell [Built-in]</command>. Boot the Debian Installer CD with " -"the following steps:" +msgid "If, for some reason, option 1 is not successful, reboot the machine and when the EFI Boot Manager screen appears there should be one option called <command>EFI Shell [Built-in]</command>. Boot the Debian Installer CD with the following steps:" msgstr "" #. Tag: para #: boot-installer.xml:1218 #, no-c-format -msgid "" -"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " -"display the EFI Boot Manager page and menu after it completes system " -"initialization." +msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes system initialization." msgstr "" #. Tag: para #: boot-installer.xml:1224 #, no-c-format -msgid "" -"Select <command>EFI Shell</command> from the menu with the arrow keys and " -"press <command>ENTER</command>. The EFI Shell will scan all of the bootable " -"devices and display them to the console before displaying its command " -"prompt. The recognized bootable partitions on devices will show a device " -"name of <filename>fs<replaceable>n</replaceable>:</filename>. All other " -"recognized partitions will be named <filename>blk<replaceable>n</" -"replaceable>:</filename>. If you inserted the CD just before entering the " -"shell, this may take a few extra seconds as it initializes the CD drive." +msgid "Select <command>EFI Shell</command> from the menu with the arrow keys and press <command>ENTER</command>. The EFI Shell will scan all of the bootable devices and display them to the console before displaying its command prompt. The recognized bootable partitions on devices will show a device name of <filename>fs<replaceable>n</replaceable>:</filename>. All other recognized partitions will be named <filename>blk<replaceable>n</replaceable>:</filename>. If you inserted the CD just before entering the shell, this may take a few extra seconds as it initializes the CD drive." msgstr "" #. Tag: para #: boot-installer.xml:1238 #, no-c-format -msgid "" -"Examine the output from the shell looking for the CDROM drive. It is most " -"likely the <filename>fs0:</filename> device although other devices with " -"bootable partitions will also show up as <filename>fs<replaceable>n</" -"replaceable></filename>." +msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the <filename>fs0:</filename> device although other devices with bootable partitions will also show up as <filename>fs<replaceable>n</replaceable></filename>." msgstr "" #. Tag: para #: boot-installer.xml:1245 #, no-c-format -msgid "" -"Enter <command>fs<replaceable>n</replaceable>:</command> and press " -"<command>ENTER</command> to select that device where <replaceable>n</" -"replaceable> is the partition number for the CDROM. The shell will now " -"display the partition number as its prompt." +msgid "Enter <command>fs<replaceable>n</replaceable>:</command> and press <command>ENTER</command> to select that device where <replaceable>n</replaceable> is the partition number for the CDROM. The shell will now display the partition number as its prompt." msgstr "" #. Tag: para #: boot-installer.xml:1252 #, no-c-format -msgid "" -"Enter <command>elilo</command> and press <command>ENTER</command>. This will " -"start the boot load sequence." +msgid "Enter <command>elilo</command> and press <command>ENTER</command>. This will start the boot load sequence." msgstr "" #. Tag: para #: boot-installer.xml:1259 #, no-c-format -msgid "" -"As with option 1, these steps start the Debian boot loader which will " -"display a menu page for you to select a boot kernel and options. You can " -"also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</" -"command> command at the shell prompt. Proceed to selecting the boot kernel " -"and options." +msgid "As with option 1, these steps start the Debian boot loader which will display a menu page for you to select a boot kernel and options. You can also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</command> command at the shell prompt. Proceed to selecting the boot kernel and options." msgstr "" #. Tag: title #: boot-installer.xml:1273 #, no-c-format msgid "Installing using a Serial Console" -msgstr "" +msgstr "Installation med en seriellkonsoll" #. Tag: para #: boot-installer.xml:1275 #, no-c-format -msgid "" -"You may choose to perform an install using a monitor and keyboard or using a " -"serial connection. To use a monitor/keyboard setup, select an option " -"containing the string [VGA console]. To install over a serial connection, " -"choose an option containing the string [<replaceable>BAUD</replaceable> baud " -"serial console], where <replaceable>BAUD</replaceable> is the speed of your " -"serial console. Menu items for the most typical baud rate settings on the " -"ttyS0 device are preconfigured." +msgid "You may choose to perform an install using a monitor and keyboard or using a serial connection. To use a monitor/keyboard setup, select an option containing the string [VGA console]. To install over a serial connection, choose an option containing the string [<replaceable>BAUD</replaceable> baud serial console], where <replaceable>BAUD</replaceable> is the speed of your serial console. Menu items for the most typical baud rate settings on the ttyS0 device are preconfigured." msgstr "" #. Tag: para #: boot-installer.xml:1286 #, no-c-format -msgid "" -"In most circumstances, you will want the installer to use the same baud rate " -"as your connection to the EFI console. If you aren't sure what this setting " -"is, you can obtain it using the command <command>baud</command> at the EFI " -"shell." +msgid "In most circumstances, you will want the installer to use the same baud rate as your connection to the EFI console. If you aren't sure what this setting is, you can obtain it using the command <command>baud</command> at the EFI shell." msgstr "" #. Tag: para #: boot-installer.xml:1293 #, no-c-format -msgid "" -"If there is not an option available that is configured for the serial device " -"or baud rate you would like to use, you may override the console setting for " -"one of the existing menu options. For example, to use a 57600 baud console " -"over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into " -"the <classname>Boot:</classname> text window." +msgid "If there is not an option available that is configured for the serial device or baud rate you would like to use, you may override the console setting for one of the existing menu options. For example, to use a 57600 baud console over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into the <classname>Boot:</classname> text window." msgstr "" #. Tag: para #: boot-installer.xml:1304 #, no-c-format -msgid "" -"Most IA-64 boxes ship with a default console setting of 9600 baud. This " -"setting is rather slow, and the normal installation process will take a " -"significant time to draw each screen. You should consider either increasing " -"the baud rate used for performing the installation, or performing a Text " -"Mode installation. See the <classname>Params</classname> help menu for " -"instructions on starting the installer in Text Mode." +msgid "Most IA-64 boxes ship with a default console setting of 9600 baud. This setting is rather slow, and the normal installation process will take a significant time to draw each screen. You should consider either increasing the baud rate used for performing the installation, or performing a Text Mode installation. See the <classname>Params</classname> help menu for instructions on starting the installer in Text Mode." msgstr "" #. Tag: para #: boot-installer.xml:1313 #, no-c-format -msgid "" -"If you select the wrong console type, you will be able to select the kernel " -"and enter parameters but both the display and your input will go dead as " -"soon as the kernel starts, requiring you to reboot before you can begin the " -"installation." +msgid "If you select the wrong console type, you will be able to select the kernel and enter parameters but both the display and your input will go dead as soon as the kernel starts, requiring you to reboot before you can begin the installation." msgstr "" #. Tag: title @@ -1430,117 +1068,74 @@ msgstr "" #. Tag: para #: boot-installer.xml:1324 #, no-c-format -msgid "" -"The boot loader will display a form with a menu list and a text window with " -"a <classname>Boot:</classname> prompt. The arrow keys select an item from " -"the menu and any text typed at the keyboard will appear in the text window. " -"There are also help screens which can be displayed by pressing the " -"appropriate function key. The <classname>General</classname> help screen " -"explains the menu choices and the <classname>Params</classname> screen " -"explains the common command line options." +msgid "The boot loader will display a form with a menu list and a text window with a <classname>Boot:</classname> prompt. The arrow keys select an item from the menu and any text typed at the keyboard will appear in the text window. There are also help screens which can be displayed by pressing the appropriate function key. The <classname>General</classname> help screen explains the menu choices and the <classname>Params</classname> screen explains the common command line options." msgstr "" #. Tag: para #: boot-installer.xml:1336 #, no-c-format -msgid "" -"Consult the <classname>General</classname> help screen for the description " -"of the kernels and install modes most appropriate for your installation. You " -"should also consult <xref linkend=\"boot-parms\"/> below for any additional " -"parameters that you may want to set in the <classname>Boot:</classname> text " -"window. The kernel version you choose selects the kernel version that will " -"be used for both the installation process and the installed system. If you " -"encounter kernel problems with the installation, you may also have those " -"same problems with the system you install. The following two steps will " -"select and start the install:" +msgid "Consult the <classname>General</classname> help screen for the description of the kernels and install modes most appropriate for your installation. You should also consult <xref linkend=\"boot-parms\"/> below for any additional parameters that you may want to set in the <classname>Boot:</classname> text window. The kernel version you choose selects the kernel version that will be used for both the installation process and the installed system. If you encounter kernel problems with the installation, you may also have those same problems with the system you install. The following two steps will select and start the install:" msgstr "" #. Tag: para #: boot-installer.xml:1354 #, no-c-format -msgid "" -"Select the kernel version and installation mode most appropriate to your " -"needs with the arrow keys." +msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys." msgstr "" #. Tag: para #: boot-installer.xml:1359 #, no-c-format -msgid "" -"Enter any boot parameters by typing at the keyboard. The text will be " -"displayed directly in the text window. This is where kernel parameters (such " -"as serial console settings) are specified." +msgid "Enter any boot parameters by typing at the keyboard. The text will be displayed directly in the text window. This is where kernel parameters (such as serial console settings) are specified." msgstr "" #. Tag: para #: boot-installer.xml:1366 #, no-c-format -msgid "" -"Press <command>ENTER</command>. This will load and start the kernel. The " -"kernel will display its usual initialization messages followed by the first " -"screen of the Debian Installer." +msgid "Press <command>ENTER</command>. This will load and start the kernel. The kernel will display its usual initialization messages followed by the first screen of the Debian Installer." msgstr "" #. Tag: para #: boot-installer.xml:1375 #, no-c-format -msgid "" -"Proceed to the next chapter to continue the installation where you will set " -"up the language locale, network, and disk partitions." +msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions." msgstr "" #. Tag: para #: boot-installer.xml:1386 #, no-c-format -msgid "" -"Booting an IA64 system from the network is similar to a CD boot. The only " -"difference is how the installation kernel is loaded. The EFI Boot Manager " -"can load and start programs from a server on the network. Once the " -"installation kernel is loaded and starts, the system install will proceed " -"thru the same steps as the CD install with the exception that the packages " -"of the base install will be loaded from the network rather than the CD drive." +msgid "Booting an IA64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed thru the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive." msgstr "" #. Tag: para #: boot-installer.xml:1420 #, no-c-format -msgid "" -"Network booting an ia64 system requires two architecture-specific actions. " -"On the boot server, DHCP and TFTP must be configured to deliver " -"<command>elilo</command>. On the client a new boot option must be defined in " -"the EFI boot manager to enable loading over a network." +msgid "Network booting an ia64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver <command>elilo</command>. On the client a new boot option must be defined in the EFI boot manager to enable loading over a network." msgstr "" #. Tag: title #: boot-installer.xml:1431 #, no-c-format msgid "Configuring the Server" -msgstr "" +msgstr "Konfiguration av servern" #. Tag: para #: boot-installer.xml:1432 #, no-c-format msgid "" -"A suitable TFTP entry for network booting an ia64 system looks something " -"like this: <informalexample><screen>\n" +"A suitable TFTP entry for network booting an ia64 system looks something like this: <informalexample><screen>\n" "host mcmuffin {\n" " hardware ethernet 00:30:6e:1e:0e:83;\n" " fixed-address 10.0.0.21;\n" " filename \"debian-installer/ia64/elilo.efi\";\n" "}\n" -"</screen></informalexample> Note that the goal is to get <command>elilo.efi</" -"command> running on the client." +"</screen></informalexample> Note that the goal is to get <command>elilo.efi</command> running on the client." msgstr "" #. Tag: para #: boot-installer.xml:1442 #, no-c-format -msgid "" -"Extract the <filename>netboot.tar.gz</filename> file into the directory used " -"as the root for your tftp server. Typical tftp root directories include " -"<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This " -"will create a <filename>debian-installer</filename> directory tree " -"containing the boot files for an IA-64 system." +msgid "Extract the <filename>netboot.tar.gz</filename> file into the directory used as the root for your tftp server. Typical tftp root directories include <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This will create a <filename>debian-installer</filename> directory tree containing the boot files for an IA-64 system." msgstr "" #. Tag: screen @@ -1558,422 +1153,274 @@ msgstr "" #. Tag: para #: boot-installer.xml:1452 #, no-c-format -msgid "" -"The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</" -"filename> file that should work for most configurations. However, should you " -"need to make changes to this file, you can find it in the <filename>debian-" -"installer/ia64/</filename> directory. It is possible to have different " -"config files for different clients by naming them using the client's IP " -"address in hex with the suffix <filename>.conf</filename> instead of " -"<filename>elilo.conf</filename>. See documentation provided in the " -"<classname>elilo</classname> package for details." +msgid "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</filename> file that should work for most configurations. However, should you need to make changes to this file, you can find it in the <filename>debian-installer/ia64/</filename> directory. It is possible to have different config files for different clients by naming them using the client's IP address in hex with the suffix <filename>.conf</filename> instead of <filename>elilo.conf</filename>. See documentation provided in the <classname>elilo</classname> package for details." msgstr "" #. Tag: title #: boot-installer.xml:1469 #, no-c-format msgid "Configuring the Client" -msgstr "" +msgstr "Konfiguration av klienten" #. Tag: para #: boot-installer.xml:1470 #, no-c-format -msgid "" -"To configure the client to support TFTP booting, start by booting to EFI and " -"entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> " -"<listitem><para> Add a boot option. </para></listitem> <listitem><para> You " -"should see one or more lines with the text <guimenuitem>Load File [Acpi" -"()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose " -"the one containing the MAC address of the interface from which you'll be " -"booting. Use the arrow keys to highlight your choice, then press enter. </" -"para></listitem> <listitem><para> Name the entry <userinput>Netboot</" -"userinput> or something similar, save, and exit back to the boot options " -"menu. </para></listitem> </itemizedlist> You should see the new boot option " -"you just created, and selecting it should initiate a DHCP query, leading to " -"a TFTP load of <filename>elilo.efi</filename> from the server." +msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> <listitem><para> Add a boot option. </para></listitem> <listitem><para> You should see one or more lines with the text <guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose the one containing the MAC address of the interface from which you'll be booting. Use the arrow keys to highlight your choice, then press enter. </para></listitem> <listitem><para> Name the entry <userinput>Netboot</userinput> or something similar, save, and exit back to the boot options menu. </para></listitem> </itemizedlist> You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of <filename>elilo.efi</filename> from the server." msgstr "" #. Tag: para #: boot-installer.xml:1502 #, no-c-format -msgid "" -"The boot loader will display its prompt after it has downloaded and " -"processed its configuration file. At this point, the installation proceeds " -"with the same steps as a CD install. Select a boot option as in above and " -"when the kernel has completed installing itself from the network, it will " -"start the Debian Installer." +msgid "The boot loader will display its prompt after it has downloaded and processed its configuration file. At this point, the installation proceeds with the same steps as a CD install. Select a boot option as in above and when the kernel has completed installing itself from the network, it will start the Debian Installer." msgstr "" #. Tag: para #: boot-installer.xml:1511 #, no-c-format -msgid "" -"Proceed to the next chapter to continue the installation where you will set " -"up the language locale, network, and the disk partitions." +msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and the disk partitions." msgstr "" #. Tag: title #: boot-installer.xml:1524 #, no-c-format msgid "Choosing an Installation Method" -msgstr "" +msgstr "Välja en installationsmetod" #. Tag: para #: boot-installer.xml:1526 #, no-c-format -msgid "" -"Some &arch-title; subarchs have the option of booting using either a 2.4.x " -"or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux " -"kernel. The installer should also require less memory when using a 2.4.x " -"linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses " -"tmpfs." +msgid "Some &arch-title; subarchs have the option of booting using either a 2.4.x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux kernel. The installer should also require less memory when using a 2.4.x linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses tmpfs." msgstr "" #. Tag: para #: boot-installer.xml:1534 #, no-c-format -msgid "" -"If you are using a 2.2.x linux kernel, then you need to use the " -"&ramdisksize; kernel parameter." +msgid "If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; kernel parameter." msgstr "" #. Tag: para #: boot-installer.xml:1541 #, no-c-format -msgid "" -"Also, if you are using a 2.2.x linux kernel, then you must make sure you are " -"using a ramdisk built to accommodate it, see the <ulink url=\"&disturl;/main/" -"installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink>. In " -"general, this means you need to use the initrd22.gz ramdisk from the " -"respective directory." +msgid "Also, if you are using a 2.2.x linux kernel, then you must make sure you are using a ramdisk built to accommodate it, see the <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink>. In general, this means you need to use the initrd22.gz ramdisk from the respective directory." msgstr "" #. Tag: para #: boot-installer.xml:1549 #, no-c-format -msgid "" -"Make sure <userinput>root=/dev/ram</userinput> is one of your kernel " -"parameters." +msgid "Make sure <userinput>root=/dev/ram</userinput> is one of your kernel parameters." msgstr "" #. Tag: para #: boot-installer.xml:1554 #, no-c-format -msgid "" -"If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's " -"&arch-title; debian-installer FAQ</ulink>." +msgid "If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's &arch-title; debian-installer FAQ</ulink>." msgstr "" #. Tag: title #: boot-installer.xml:1571 #, no-c-format msgid "Amiga" -msgstr "" +msgstr "Amiga" #. Tag: para #: boot-installer.xml:1572 #, no-c-format -msgid "" -"The only method of installation available to amiga is the hard drive (see " -"<xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not " -"bootable.</emphasis>" +msgid "The only method of installation available to amiga is the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" #. Tag: para #: boot-installer.xml:1578 #, no-c-format -msgid "" -"Amiga does not currently work with bogl, so if you are seeing bogl errors, " -"you need to include the kernel parameter <userinput>debian-installer/" -"framebuffer=false</userinput>." +msgid "Amiga does not currently work with bogl, so if you are seeing bogl errors, you need to include the kernel parameter <userinput>debian-installer/framebuffer=false</userinput>." msgstr "" #. Tag: title #: boot-installer.xml:1587 #, no-c-format msgid "Atari" -msgstr "" +msgstr "Atari" #. Tag: para #: boot-installer.xml:1588 #, no-c-format -msgid "" -"The installer for atari may be started from either the hard drive (see <xref " -"linkend=\"m68k-boot-hd\"/>) or from floppies (see <xref linkend=\"boot-from-" -"floppies\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" +msgid "The installer for atari may be started from either the hard drive (see <xref linkend=\"m68k-boot-hd\"/>) or from floppies (see <xref linkend=\"boot-from-floppies\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" #. Tag: para #: boot-installer.xml:1595 #, no-c-format -msgid "" -"Atari does not currently work with bogl, so if you are seeing bogl errors, " -"you need to include the kernel parameter <userinput>debian-installer/" -"framebuffer=false</userinput>." +msgid "Atari does not currently work with bogl, so if you are seeing bogl errors, you need to include the kernel parameter <userinput>debian-installer/framebuffer=false</userinput>." msgstr "" #. Tag: title #: boot-installer.xml:1604 #, no-c-format msgid "BVME6000" -msgstr "" +msgstr "BVME6000" #. Tag: para #: boot-installer.xml:1605 #, no-c-format -msgid "" -"The installer for BVME6000 may be started from a cdrom (see <xref linkend=" -"\"m68k-boot-cdrom\"/>), floppies (see <xref linkend=\"boot-from-floppies\"/" -">), or the net (see <xref linkend=\"boot-tftp\"/>)." +msgid "The installer for BVME6000 may be started from a cdrom (see <xref linkend=\"m68k-boot-cdrom\"/>), floppies (see <xref linkend=\"boot-from-floppies\"/>), or the net (see <xref linkend=\"boot-tftp\"/>)." msgstr "" #. Tag: title #: boot-installer.xml:1615 #, no-c-format msgid "Macintosh" -msgstr "" +msgstr "Macintosh" #. Tag: para #: boot-installer.xml:1616 #, no-c-format -msgid "" -"The only method of installation available to mac is from the hard drive (see " -"<xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not " -"bootable.</emphasis> Macs do not have a working 2.4.x kernel." +msgid "The only method of installation available to mac is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis> Macs do not have a working 2.4.x kernel." msgstr "" #. Tag: para #: boot-installer.xml:1623 #, no-c-format -msgid "" -"If your hardware uses a 53c9x-based scsi bus, then you may need to include " -"the kernel parameter <userinput>mac53c9x=1,0</userinput>. Hardware with two " -"such scsi buses, such as the Quadra 950, will need <userinput>mac53c9x=2,0</" -"userinput> instead. Alternatively, the parameter can be specified as " -"<userinput>mac53c9x=-1,0</userinput> which will leave autodetection on, but " -"which will disable SCSI disconnects. Note that specifying this parameter is " -"only necessary if you have more than one hard disk; otherwise, the system " -"will run faster if you do not specify it." +msgid "If your hardware uses a 53c9x-based scsi bus, then you may need to include the kernel parameter <userinput>mac53c9x=1,0</userinput>. Hardware with two such scsi buses, such as the Quadra 950, will need <userinput>mac53c9x=2,0</userinput> instead. Alternatively, the parameter can be specified as <userinput>mac53c9x=-1,0</userinput> which will leave autodetection on, but which will disable SCSI disconnects. Note that specifying this parameter is only necessary if you have more than one hard disk; otherwise, the system will run faster if you do not specify it." msgstr "" #. Tag: title #: boot-installer.xml:1638 #, no-c-format msgid "MVME147 and MVME16x" -msgstr "" +msgstr "MVME147 och MVME16x" #. Tag: para #: boot-installer.xml:1639 #, no-c-format -msgid "" -"The installer for MVME147 and MVME16x may be started from either floppies " -"(see <xref linkend=\"boot-from-floppies\"/>) or the net (see <xref linkend=" -"\"boot-tftp\"/>). <emphasis>In other words the cdrom is not bootable.</" -"emphasis>" +msgid "The installer for MVME147 and MVME16x may be started from either floppies (see <xref linkend=\"boot-from-floppies\"/>) or the net (see <xref linkend=\"boot-tftp\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" #. Tag: title #: boot-installer.xml:1649 #, no-c-format msgid "Q40/Q60" -msgstr "" +msgstr "Q40/Q60" #. Tag: para #: boot-installer.xml:1650 #, no-c-format -msgid "" -"The only method of installation available to Q40/Q60 is from the hard drive " -"(see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom " -"is not bootable.</emphasis>" +msgid "The only method of installation available to Q40/Q60 is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" msgstr "" #. Tag: title #: boot-installer.xml:1661 #, no-c-format msgid "Booting from a Hard Disk" -msgstr "" +msgstr "Starta upp frÃ¥n en hÃ¥rddisk" #. Tag: para -#: boot-installer.xml:1667 boot-installer.xml:2172 +#: boot-installer.xml:1667 +#: boot-installer.xml:2172 #, no-c-format -msgid "" -"Booting from an existing operating system is often a convenient option; for " -"some systems it is the only supported method of installation." +msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation." msgstr "" #. Tag: para -#: boot-installer.xml:1673 boot-installer.xml:2178 +#: boot-installer.xml:1673 +#: boot-installer.xml:2178 #, no-c-format -msgid "" -"To boot the installer from hard disk, you will have already completed " -"downloading and placing the needed files in <xref linkend=\"boot-drive-files" -"\"/>." +msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files in <xref linkend=\"boot-drive-files\"/>." msgstr "" #. Tag: para #: boot-installer.xml:1682 #, no-c-format -msgid "" -"At least six different ramdisks may be used to boot from the hard drive, " -"three different types each with and without support for a 2.2.x linux kernel " -"(see <ulink url=\"&disturl;/main/installer-&architecture;/current/images/" -"MANIFEST\">MANIFEST</ulink> for details)." +msgid "At least six different ramdisks may be used to boot from the hard drive, three different types each with and without support for a 2.2.x linux kernel (see <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink> for details)." msgstr "" #. Tag: para #: boot-installer.xml:1690 #, no-c-format -msgid "" -"The three different types of ramdisks are <filename>cdrom</filename>, " -"<filename>hd-media</filename>, and <filename>nativehd</filename>. These " -"ramdisks differ only in their source for installation packages. The " -"<filename>cdrom</filename> ramdisk uses a cdrom to get debian-installer " -"packages. The <filename>hd-media</filename> ramdisk uses an iso image file " -"of a cdrom currently residing on a hard disk. Finally, the " -"<filename>nativehd</filename> ramdisk uses the net to install packages." +msgid "The three different types of ramdisks are <filename>cdrom</filename>, <filename>hd-media</filename>, and <filename>nativehd</filename>. These ramdisks differ only in their source for installation packages. The <filename>cdrom</filename> ramdisk uses a cdrom to get debian-installer packages. The <filename>hd-media</filename> ramdisk uses an iso image file of a cdrom currently residing on a hard disk. Finally, the <filename>nativehd</filename> ramdisk uses the net to install packages." msgstr "" #. Tag: title #: boot-installer.xml:1711 #, no-c-format msgid "Booting from AmigaOS" -msgstr "" +msgstr "Starta upp frÃ¥n AmigaOS" #. Tag: para #: boot-installer.xml:1712 #, no-c-format -msgid "" -"In the <command>Workbench</command>, start the Linux installation process by " -"double-clicking on the <guiicon>StartInstall</guiicon> icon in the " -"<filename>debian</filename> directory." +msgid "In the <command>Workbench</command>, start the Linux installation process by double-clicking on the <guiicon>StartInstall</guiicon> icon in the <filename>debian</filename> directory." msgstr "" #. Tag: para #: boot-installer.xml:1718 #, no-c-format -msgid "" -"You may have to press the &enterkey; key twice after the Amiga installer " -"program has output some debugging information into a window. After this, the " -"screen will go grey, there will be a few seconds' delay. Next, a black " -"screen with white text should come up, displaying all kinds of kernel " -"debugging information. These messages may scroll by too fast for you to " -"read, but that's OK. After a couple of seconds, the installation program " -"should start automatically, so you can continue down at <xref linkend=\"d-i-" -"intro\"/>." +msgid "You may have to press the &enterkey; key twice after the Amiga installer program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue down at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: title #: boot-installer.xml:1733 #, no-c-format msgid "Booting from Atari TOS" -msgstr "" +msgstr "Starta upp frÃ¥n Atari TOS" #. Tag: para #: boot-installer.xml:1734 #, no-c-format -msgid "" -"At the GEM desktop, start the Linux installation process by double-clicking " -"on the <guiicon>bootstra.prg</guiicon> icon in the <filename>debian</" -"filename> directory and clicking <guibutton>Ok</guibutton> at the program " -"options dialog box." +msgid "At the GEM desktop, start the Linux installation process by double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the <filename>debian</filename> directory and clicking <guibutton>Ok</guibutton> at the program options dialog box." msgstr "" #. Tag: para #: boot-installer.xml:1741 #, no-c-format -msgid "" -"You may have to press the &enterkey; key after the Atari bootstrap program " -"has output some debugging information into a window. After this, the screen " -"will go grey, there will be a few seconds' delay. Next, a black screen with " -"white text should come up, displaying all kinds of kernel debugging " -"information. These messages may scroll by too fast for you to read, but " -"that's OK. After a couple of seconds, the installation program should start " -"automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." +msgid "You may have to press the &enterkey; key after the Atari bootstrap program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: title #: boot-installer.xml:1756 #, no-c-format msgid "Booting from MacOS" -msgstr "" +msgstr "Starta upp frÃ¥n MacOS" #. Tag: para #: boot-installer.xml:1757 #, no-c-format -msgid "" -"You must retain the original Mac system and boot from it. It is " -"<emphasis>essential</emphasis> that, when booting MacOS in preparation for " -"booting the Penguin linux loader, you hold the <keycap>shift</keycap> key " -"down to prevent extensions from loading. If you don't use MacOS except for " -"loading linux, you can accomplish the same thing by removing all extensions " -"and control panels from the Mac's System Folder. Otherwise extensions may be " -"left running and cause random problems with the running linux kernel." +msgid "You must retain the original Mac system and boot from it. It is <emphasis>essential</emphasis> that, when booting MacOS in preparation for booting the Penguin linux loader, you hold the <keycap>shift</keycap> key down to prevent extensions from loading. If you don't use MacOS except for loading linux, you can accomplish the same thing by removing all extensions and control panels from the Mac's System Folder. Otherwise extensions may be left running and cause random problems with the running linux kernel." msgstr "" #. Tag: para #: boot-installer.xml:1768 #, no-c-format -msgid "" -"Macs require the <command>Penguin</command> bootloader. If you do not have " -"the tools to handle a <command>Stuffit</command> archive, &penguin19.hfs; is " -"an hfs disk image with <command>Penguin</command> unpacked. <xref linkend=" -"\"create-floppy\"/> describes how to copy this image to a floppy." +msgid "Macs require the <command>Penguin</command> bootloader. If you do not have the tools to handle a <command>Stuffit</command> archive, &penguin19.hfs; is an hfs disk image with <command>Penguin</command> unpacked. <xref linkend=\"create-floppy\"/> describes how to copy this image to a floppy." msgstr "" #. Tag: para #: boot-installer.xml:1777 #, no-c-format -msgid "" -"At the MacOS desktop, start the Linux installation process by double-" -"clicking on the <guiicon>Penguin Prefs</guiicon> icon in the " -"<filename>Penguin</filename> directory. The <command>Penguin</command> " -"booter will start up. Go to the <guimenuitem>Settings</guimenuitem> item in " -"the <guimenu>File</guimenu> menu, click the <guilabel>Kernel</guilabel> tab. " -"Select the kernel (<filename>vmlinuz</filename>) and ramdisk " -"(<filename>initrd.gz</filename>) images in the <filename>install</filename> " -"directory by clicking on the corresponding buttons in the upper right " -"corner, and navigating the file select dialogs to locate the files." +msgid "At the MacOS desktop, start the Linux installation process by double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in the <filename>Penguin</filename> directory. The <command>Penguin</command> booter will start up. Go to the <guimenuitem>Settings</guimenuitem> item in the <guimenu>File</guimenu> menu, click the <guilabel>Kernel</guilabel> tab. Select the kernel (<filename>vmlinuz</filename>) and ramdisk (<filename>initrd.gz</filename>) images in the <filename>install</filename> directory by clicking on the corresponding buttons in the upper right corner, and navigating the file select dialogs to locate the files." msgstr "" #. Tag: para #: boot-installer.xml:1792 #, no-c-format -msgid "" -"To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -> " -"<guimenuitem>Settings...</guimenuitem>, then switch to the " -"<guilabel>Options</guilabel> tab. Boot parameters may be typed in to the " -"text entry area. If you will always want to use these settings, select " -"<guimenu>File</guimenu> -> <guimenuitem>Save Settings as Default</" -"guimenuitem>." +msgid "To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -> <guimenuitem>Settings...</guimenuitem>, then switch to the <guilabel>Options</guilabel> tab. Boot parameters may be typed in to the text entry area. If you will always want to use these settings, select <guimenu>File</guimenu> -> <guimenuitem>Save Settings as Default</guimenuitem>." msgstr "" #. Tag: para #: boot-installer.xml:1801 #, no-c-format -msgid "" -"Close the <guilabel>Settings</guilabel> dialog, save the settings and start " -"the bootstrap using the <guimenuitem>Boot Now</guimenuitem> item in the " -"<guimenu>File</guimenu> menu." +msgid "Close the <guilabel>Settings</guilabel> dialog, save the settings and start the bootstrap using the <guimenuitem>Boot Now</guimenuitem> item in the <guimenu>File</guimenu> menu." msgstr "" #. Tag: para #: boot-installer.xml:1808 #, no-c-format -msgid "" -"The <command>Penguin</command> booter will output some debugging information " -"into a window. After this, the screen will go grey, there will be a few " -"seconds' delay. Next, a black screen with white text should come up, " -"displaying all kinds of kernel debugging information. These messages may " -"scroll by too fast for you to read, but that's OK. After a couple of " -"seconds, the installation program should start automatically, so you can " -"continue below at <xref linkend=\"d-i-intro\"/>." +msgid "The <command>Penguin</command> booter will output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: title #: boot-installer.xml:1823 #, no-c-format msgid "Booting from Q40/Q60" -msgstr "" +msgstr "Starta upp frÃ¥n Q40/Q60" #. Tag: para #: boot-installer.xml:1825 @@ -1984,27 +1431,19 @@ msgstr "" #. Tag: para #: boot-installer.xml:1829 #, no-c-format -msgid "" -"The installation program should start automatically, so you can continue " -"below at <xref linkend=\"d-i-intro\"/>." +msgid "The installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." msgstr "" #. Tag: para #: boot-installer.xml:1841 #, no-c-format -msgid "" -"Currently, the only &arch-title; subarchitecture that supports CD-ROM " -"booting is the BVME6000." +msgid "Currently, the only &arch-title; subarchitecture that supports CD-ROM booting is the BVME6000." msgstr "" #. Tag: para #: boot-installer.xml:1913 #, no-c-format -msgid "" -"After booting the VMEbus systems you will be presented with the LILO " -"<prompt>Boot:</prompt> prompt. At that prompt enter one of the following to " -"boot Linux and begin installation proper of the Debian software using vt102 " -"terminal emulation:" +msgid "After booting the VMEbus systems you will be presented with the LILO <prompt>Boot:</prompt> prompt. At that prompt enter one of the following to boot Linux and begin installation proper of the Debian software using vt102 terminal emulation:" msgstr "" #. Tag: para @@ -2028,29 +1467,24 @@ msgstr "" #. Tag: para #: boot-installer.xml:1941 #, no-c-format -msgid "" -"You may additionally append the string <screen>TERM=vt100</screen> to use " -"vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>." +msgid "You may additionally append the string <screen>TERM=vt100</screen> to use vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>." msgstr "" #. Tag: para #: boot-installer.xml:1953 #, no-c-format -msgid "" -"For most &arch-title; architectures, booting from a local filesystem is the " -"recommended method." +msgid "For most &arch-title; architectures, booting from a local filesystem is the recommended method." msgstr "" #. Tag: para #: boot-installer.xml:1958 #, no-c-format -msgid "" -"Booting from the boot floppy is supported only for Atari and VME (with a " -"SCSI floppy drive on VME) at this time." +msgid "Booting from the boot floppy is supported only for Atari and VME (with a SCSI floppy drive on VME) at this time." msgstr "" #. Tag: title -#: boot-installer.xml:1974 boot-installer.xml:2021 +#: boot-installer.xml:1974 +#: boot-installer.xml:2021 #, no-c-format msgid "SGI Indys TFTP Booting" msgstr "" @@ -2061,16 +1495,14 @@ msgstr "" msgid "" "After entering the command monitor use <informalexample><screen>\n" "bootp():\n" -"</screen></informalexample> on SGI Indys to boot linux and to begin " -"installation of the Debian Software. In order to make this work you may have " -"to unset the <envar>netaddr</envar> environment variable. Type " -"<informalexample><screen>\n" +"</screen></informalexample> on SGI Indys to boot linux and to begin installation of the Debian Software. In order to make this work you may have to unset the <envar>netaddr</envar> environment variable. Type <informalexample><screen>\n" "unsetenv netaddr\n" "</screen></informalexample> in the command monitor to do this." msgstr "" #. Tag: title -#: boot-installer.xml:1994 boot-installer.xml:2043 +#: boot-installer.xml:1994 +#: boot-installer.xml:2043 #, no-c-format msgid "Broadcom BCM91250A TFTP Booting" msgstr "" @@ -2079,83 +1511,63 @@ msgstr "" #: boot-installer.xml:1995 #, no-c-format msgid "" -"On the Broadcom BCM91250A evaluation board, you have to load the SiByl boot " -"loader via TFTP which will then load and start the Debian installer. In most " -"cases, you will first obtain an IP address via DHCP but it is also possible " -"to configure a static address. In order to use DHCP, you can enter the " -"following command on the CFE prompt: <informalexample><screen>\n" +"On the Broadcom BCM91250A evaluation board, you have to load the SiByl boot loader via TFTP which will then load and start the Debian installer. In most cases, you will first obtain an IP address via DHCP but it is also possible to configure a static address. In order to use DHCP, you can enter the following command on the CFE prompt: <informalexample><screen>\n" "ifconfig eth0 -auto\n" -"</screen></informalexample> Once you have obtained an IP address, you can " -"load SiByl with the following command: <informalexample><screen>\n" +"</screen></informalexample> Once you have obtained an IP address, you can load SiByl with the following command: <informalexample><screen>\n" "boot 192.168.1.1:/boot/sibyl\n" -"</screen></informalexample> You need to substitute the IP address listed in " -"this example with either the name or the IP address of your TFTP server. " -"Once you issue this command, the installer will be loaded automatically." +"</screen></informalexample> You need to substitute the IP address listed in this example with either the name or the IP address of your TFTP server. Once you issue this command, the installer will be loaded automatically." msgstr "" #. Tag: title -#: boot-installer.xml:2018 boot-installer.xml:2552 +#: boot-installer.xml:2018 +#: boot-installer.xml:2552 #, no-c-format msgid "Boot Parameters" -msgstr "" +msgstr "Uppstartsparametrar" #. Tag: para #: boot-installer.xml:2022 #, no-c-format -msgid "" -"On SGI Indys you can append boot parameters to the <command>bootp():</" -"command> command in the command monitor." +msgid "On SGI Indys you can append boot parameters to the <command>bootp():</command> command in the command monitor." msgstr "" #. Tag: para #: boot-installer.xml:2027 #, no-c-format msgid "" -"Following the <command>bootp():</command> command you can give the path and " -"name of the file to boot if you did not give an explicit name via your bootp/" -"dhcp server. Example: <informalexample><screen>\n" +"Following the <command>bootp():</command> command you can give the path and name of the file to boot if you did not give an explicit name via your bootp/dhcp server. Example: <informalexample><screen>\n" "bootp():/boot/tftpboot.img\n" -"</screen></informalexample> Further kernel parameters can be passed via " -"<command>append</command>:" +"</screen></informalexample> Further kernel parameters can be passed via <command>append</command>:" msgstr "" #. Tag: screen #: boot-installer.xml:2037 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" -msgstr "" +msgstr "bootp(): append=\"root=/dev/sda1\"" #. Tag: para #: boot-installer.xml:2044 #, no-c-format -msgid "" -"You cannot pass any boot parameters directly from the CFE prompt. Instead, " -"you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP " -"server and add your parameters to the <replaceable>extra_args</replaceable> " -"variable." +msgid "You cannot pass any boot parameters directly from the CFE prompt. Instead, you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP server and add your parameters to the <replaceable>extra_args</replaceable> variable." msgstr "" #. Tag: title #: boot-installer.xml:2061 #, no-c-format msgid "s390 Limitations" -msgstr "" +msgstr "Begränsningar för s390" #. Tag: para #: boot-installer.xml:2062 #, no-c-format -msgid "" -"In order to run the installation system a working network setup and ssh " -"session is needed on S/390." +msgid "In order to run the installation system a working network setup and ssh session is needed on S/390." msgstr "" #. Tag: para #: boot-installer.xml:2067 #, no-c-format -msgid "" -"The booting process starts with a network setup that prompts you for several " -"network parameters. If the setup is successful, you will login to the system " -"by starting a ssh session which will launch the standard installation system." +msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting a ssh session which will launch the standard installation system." msgstr "" #. Tag: title @@ -2167,44 +1579,25 @@ msgstr "" #. Tag: para #: boot-installer.xml:2079 #, no-c-format -msgid "" -"On S/390 you can append boot parameters in the parm file. This file can " -"either be in ASCII or EBCDIC format. Please read <ulink url=\"&url-s390-" -"devices;\">Device Drivers and Installation Commands</ulink> for more " -"information about S/390-specific boot parameters." +msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. Please read <ulink url=\"&url-s390-devices;\">Device Drivers and Installation Commands</ulink> for more information about S/390-specific boot parameters." msgstr "" #. Tag: para #: boot-installer.xml:2133 #, no-c-format -msgid "" -"Currently, the only &arch-title; subarchitectures that support CD-ROM " -"booting are PReP and New World PowerMacs. On PowerMacs, hold the <keycap>c</" -"keycap> key, or else the combination of <keycap>Command</keycap>, " -"<keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> " -"keys together while booting to boot from the CD-ROM." +msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the CD-ROM." msgstr "" #. Tag: para #: boot-installer.xml:2142 #, no-c-format -msgid "" -"OldWorld PowerMacs will not boot a Debian CD, because OldWorld computers " -"relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-" -"software version of this driver is not available. All OldWorld systems have " -"floppy drives, so use the floppy drive to launch the installer, and then " -"point the installer to the CD for the needed files." +msgid "OldWorld PowerMacs will not boot a Debian CD, because OldWorld computers relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-software version of this driver is not available. All OldWorld systems have floppy drives, so use the floppy drive to launch the installer, and then point the installer to the CD for the needed files." msgstr "" #. Tag: para #: boot-installer.xml:2151 #, no-c-format -msgid "" -"If your system doesn't boot directly from CD-ROM, you can still use the CD-" -"ROM to install the system. On NewWorlds, you can also use an OpenFirmware " -"command to boot from the CD-ROM manually. Follow the instructions in <xref " -"linkend=\"boot-newworld\"/> for booting from the hard disk, except use the " -"path to <command>yaboot</command> on the CD at the OF prompt, such as" +msgid "If your system doesn't boot directly from CD-ROM, you can still use the CD-ROM to install the system. On NewWorlds, you can also use an OpenFirmware command to boot from the CD-ROM manually. Follow the instructions in <xref linkend=\"boot-newworld\"/> for booting from the hard disk, except use the path to <command>yaboot</command> on the CD at the OF prompt, such as" msgstr "" #. Tag: screen @@ -2217,19 +1610,19 @@ msgstr "" #: boot-installer.xml:2166 #, no-c-format msgid "Booting from Hard Disk" -msgstr "" +msgstr "Starta upp frÃ¥n hÃ¥rddisk" #. Tag: title #: boot-installer.xml:2187 #, no-c-format msgid "Booting CHRP from OpenFirmware" -msgstr "" +msgstr "Starta upp CHRP frÃ¥n OpenFirmware" #. Tag: emphasis #: boot-installer.xml:2191 #, no-c-format msgid "Not yet written." -msgstr "" +msgstr "Ännu inte skriven." #. Tag: title #: boot-installer.xml:2196 @@ -2240,15 +1633,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2197 #, no-c-format -msgid "" -"If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to " -"boot into the installation system. Double click the <guiicon>BootX</guiicon> " -"application icon. Click on the <guibutton>Options</guibutton> button and " -"select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the " -"chance to select the <filename>ramdisk.image.gz</filename> file. You may " -"need to select the <guilabel>No Video Driver</guilabel> checkbox, depending " -"on your hardware. Then click the <guibutton>Linux</guibutton> button to shut " -"down MacOS and launch the installer." +msgid "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to boot into the installation system. Double click the <guiicon>BootX</guiicon> application icon. Click on the <guibutton>Options</guibutton> button and select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the chance to select the <filename>ramdisk.image.gz</filename> file. You may need to select the <guilabel>No Video Driver</guilabel> checkbox, depending on your hardware. Then click the <guibutton>Linux</guibutton> button to shut down MacOS and launch the installer." msgstr "" #. Tag: title @@ -2261,34 +1646,18 @@ msgstr "" #: boot-installer.xml:2216 #, no-c-format msgid "" -"You will have already placed the <filename>vmlinux</filename>, " -"<filename>initrd.gz</filename>, <filename>yaboot</filename>, and " -"<filename>yaboot.conf</filename> files at the root level of your HFS " -"partition in <xref linkend=\"files-newworld\"/>. Restart the computer, and " -"immediately (during the chime) hold down the <keycap>Option</keycap>, " -"<keycap>Command (cloverleaf/Apple)</keycap>, <keycap>o</keycap>, and " -"<keycap>f</keycap> keys all together. After a few seconds you will be " -"presented with the Open Firmware prompt. At the prompt, type " -"<informalexample><screen>\n" +"You will have already placed the <filename>vmlinux</filename>, <filename>initrd.gz</filename>, <filename>yaboot</filename>, and <filename>yaboot.conf</filename> files at the root level of your HFS partition in <xref linkend=\"files-newworld\"/>. Restart the computer, and immediately (during the chime) hold down the <keycap>Option</keycap>, <keycap>Command (cloverleaf/Apple)</keycap>, <keycap>o</keycap>, and <keycap>f</keycap> keys all together. After a few seconds you will be presented with the Open Firmware prompt. At the prompt, type <informalexample><screen>\n" "0 > boot hd:<replaceable>x</replaceable>,yaboot\n" -"</screen></informalexample> replacing <replaceable>x</replaceable> with the " -"partition number of the HFS partition where the kernel and yaboot files were " -"placed, followed by a &enterkey;. On some machines, you may need to use " -"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few " -"more seconds you will see a yaboot prompt <informalexample><screen>\n" +"</screen></informalexample> replacing <replaceable>x</replaceable> with the partition number of the HFS partition where the kernel and yaboot files were placed, followed by a &enterkey;. On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few more seconds you will see a yaboot prompt <informalexample><screen>\n" "boot:\n" -"</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type " -"either <userinput>install</userinput> or <userinput>install video=ofonly</" -"userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> " -"argument is for maximum compatibility; you can try it if <userinput>install</" -"userinput> doesn't work. The Debian installation program should start." +"</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type either <userinput>install</userinput> or <userinput>install video=ofonly</userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> argument is for maximum compatibility; you can try it if <userinput>install</userinput> doesn't work. The Debian installation program should start." msgstr "" #. Tag: title #: boot-installer.xml:2251 #, no-c-format msgid "Booting from USB memory stick" -msgstr "" +msgstr "Starta upp frÃ¥n USB-minne" #. Tag: para #: boot-installer.xml:2252 @@ -2299,62 +1668,34 @@ msgstr "" #. Tag: para #: boot-installer.xml:2258 #, no-c-format -msgid "" -"Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/" -">. To boot a Macintosh system from a USB stick, you will need to use the " -"Open Firmware prompt, since Open Firmware does not search USB storage " -"devices by default. To get to the prompt, hold down " -"<keycombo><keycap>Command</keycap> <keycap>Option</keycap> <keycap>o</" -"keycap> <keycap>f</keycap></keycombo> all together while booting (see <xref " -"linkend=\"invoking-openfirmware\"/>)." +msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. To get to the prompt, hold down <keycombo><keycap>Command</keycap> <keycap>Option</keycap> <keycap>o</keycap> <keycap>f</keycap></keycombo> all together while booting (see <xref linkend=\"invoking-openfirmware\"/>)." msgstr "" #. Tag: para #: boot-installer.xml:2270 #, no-c-format -msgid "" -"You will need to work out where the USB storage device appears in the device " -"tree, since at the moment <command>ofpath</command> cannot work that out " -"automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</" -"userinput> at the Open Firmware prompt to get a list of all known devices " -"and device aliases. On the author's system with various types of USB stick, " -"paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</" -"filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and " -"<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work." +msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment <command>ofpath</command> cannot work that out automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</userinput> at the Open Firmware prompt to get a list of all known devices and device aliases. On the author's system with various types of USB stick, paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work." msgstr "" #. Tag: para #: boot-installer.xml:2282 #, no-c-format msgid "" -"Having worked out the device path, use a command like this to boot the " -"installer: <informalexample><screen>\n" -"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:" -"tbxi\n" -"</screen></informalexample> The <replaceable>2</replaceable> matches the " -"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image " -"earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open " -"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. " -"<command>yaboot</command>) in the directory previously blessed with " -"<command>hattrib -b</command>." +"Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n" +"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:tbxi\n" +"</screen></informalexample> The <replaceable>2</replaceable> matches the Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. <command>yaboot</command>) in the directory previously blessed with <command>hattrib -b</command>." msgstr "" #. Tag: para #: boot-installer.xml:2296 #, no-c-format -msgid "" -"The system should now boot up, and you should be presented with the " -"<prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, " -"or just hit &enterkey;." +msgid "The system should now boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;." msgstr "" #. Tag: para #: boot-installer.xml:2302 #, no-c-format -msgid "" -"This boot method is new, and may be difficult to get to work on some " -"NewWorld systems. If you have problems, please file an installation report, " -"as explained in <xref linkend=\"submit-bug\"/>." +msgid "This boot method is new, and may be difficult to get to work on some NewWorld systems. If you have problems, please file an installation report, as explained in <xref linkend=\"submit-bug\"/>." msgstr "" #. Tag: para @@ -2366,51 +1707,31 @@ msgstr "" #. Tag: para #: boot-installer.xml:2339 #, no-c-format -msgid "" -"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " -"monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command " -"<command>boot enet:0</command>. PReP and CHRP boxes may have different ways " -"of addressing the network. On a PReP machine, you should try <userinput>boot " -"<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>," -"<replaceable>client_ipaddr</replaceable></userinput>." +msgid "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <command>boot enet:0</command>. PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try <userinput>boot <replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>." msgstr "" #. Tag: para #: boot-installer.xml:2354 #, no-c-format -msgid "" -"Booting from floppies is supported for &arch-title;, although it is " -"generally only applicable for OldWorld systems. NewWorld systems are not " -"equipped with floppy drives, and attached USB floppy drives are not " -"supported for booting." +msgid "Booting from floppies is supported for &arch-title;, although it is generally only applicable for OldWorld systems. NewWorld systems are not equipped with floppy drives, and attached USB floppy drives are not supported for booting." msgstr "" #. Tag: para #: boot-installer.xml:2366 #, no-c-format -msgid "" -"To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it " -"in floppy drive after shutting the system down, and before pressing the " -"power-on button." +msgid "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button." msgstr "" #. Tag: para #: boot-installer.xml:2372 #, no-c-format -msgid "" -"For those not familiar with Macintosh floppy operations: a floppy placed in " -"the machine prior to boot will be the first priority for the system to boot " -"from. A floppy without a valid boot system will be ejected, and the machine " -"will then check for bootable hard disk partitions." +msgid "For those not familiar with Macintosh floppy operations: a floppy placed in the machine prior to boot will be the first priority for the system to boot from. A floppy without a valid boot system will be ejected, and the machine will then check for bootable hard disk partitions." msgstr "" #. Tag: para #: boot-installer.xml:2379 #, no-c-format -msgid "" -"After booting, the <filename>root.bin</filename> floppy is requested. Insert " -"the root floppy and press &enterkey;. The installer program is automatically " -"launched after the root system has been loaded into memory." +msgid "After booting, the <filename>root.bin</filename> floppy is requested. Insert the root floppy and press &enterkey;. The installer program is automatically launched after the root system has been loaded into memory." msgstr "" #. Tag: title @@ -2422,37 +1743,19 @@ msgstr "" #. Tag: para #: boot-installer.xml:2391 #, no-c-format -msgid "" -"Many older Apple monitors used a 640x480 67Hz mode. If your video appears " -"skewed on an older Apple monitor, try appending the boot argument " -"<userinput>video=atyfb:vmode:6</userinput> , which will select that mode for " -"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to " -"<userinput>video=aty128fb:vmode:6</userinput> ." +msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ." msgstr "" #. Tag: para #: boot-installer.xml:2431 #, no-c-format -msgid "" -"On machines with OpenBoot, simply enter the boot monitor on the machine " -"which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use " -"the command <userinput>boot net</userinput> to boot from a TFTP and RARP " -"server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:" -"dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. Some older " -"OpenBoot revisions require using the device name, such as <userinput>boot le" -"()</userinput>; these probably don't support BOOTP nor DHCP." +msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. Some older OpenBoot revisions require using the device name, such as <userinput>boot le()</userinput>; these probably don't support BOOTP nor DHCP." msgstr "" #. Tag: para #: boot-installer.xml:2487 #, no-c-format -msgid "" -"Most OpenBoot versions support the <userinput>boot cdrom</userinput> command " -"which is simply an alias to boot from the SCSI device on ID 6 (or the " -"secondary master for IDE based systems). You may have to use the actual " -"device name for older OpenBoot versions that don't support this special " -"command. Note that some problems have been reported on Sun4m (e.g., Sparc " -"10s and Sparc 20s) systems booting from CD-ROM." +msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems). You may have to use the actual device name for older OpenBoot versions that don't support this special command. Note that some problems have been reported on Sun4m (e.g., Sparc 10s and Sparc 20s) systems booting from CD-ROM." msgstr "" #. Tag: para @@ -2461,34 +1764,23 @@ msgstr "" msgid "" "To boot from floppy on a Sparc, use <informalexample><screen>\n" "Stop-A -> OpenBoot: \"boot floppy\"\n" -"</screen></informalexample> Be warned that the newer Sun4u (ultra) " -"architecture does not support floppy booting. A typical error message is " -"<computeroutput>Bad magic number in disk label - Can't open disk label " -"package</computeroutput>. Furthermore, a number of Sun4c models (such as the " -"IPX) do not support the compressed images found on the disks, so also are " -"not supported." +"</screen></informalexample> Be warned that the newer Sun4u (ultra) architecture does not support floppy booting. A typical error message is <computeroutput>Bad magic number in disk label - Can't open disk label package</computeroutput>. Furthermore, a number of Sun4c models (such as the IPX) do not support the compressed images found on the disks, so also are not supported." msgstr "" #. Tag: para #: boot-installer.xml:2514 #, no-c-format -msgid "" -"Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from " -"booting (instead of not supporting booting at all). The appropriate OBP " -"update can be downloaded as product ID 106121 from <ulink url=\"http://" -"sunsolve.sun.com\"></ulink>." +msgid "Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from booting (instead of not supporting booting at all). The appropriate OBP update can be downloaded as product ID 106121 from <ulink url=\"http://sunsolve.sun.com\"></ulink>." msgstr "" #. Tag: para #: boot-installer.xml:2521 #, no-c-format msgid "" -"If you are booting from the floppy, and you see messages such as " -"<informalexample><screen>\n" +"If you are booting from the floppy, and you see messages such as <informalexample><screen>\n" "Fatal error: Cannot read partition\n" "Illegal or malformed device name\n" -"</screen></informalexample> then it is possible that floppy booting is " -"simply not supported on your machine." +"</screen></informalexample> then it is possible that floppy booting is simply not supported on your machine." msgstr "" #. Tag: title @@ -2500,43 +1792,25 @@ msgstr "" #. Tag: para #: boot-installer.xml:2534 #, no-c-format -msgid "" -"If you cannot boot because you get messages about a problem with " -"<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which " -"holds configuration information for you firmware, has run out. See the " -"<ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more " -"information." +msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information." msgstr "" #. Tag: para #: boot-installer.xml:2553 #, no-c-format -msgid "" -"Boot parameters are Linux kernel parameters which are generally used to make " -"sure that peripherals are dealt with properly. For the most part, the kernel " -"can auto-detect information about your peripherals. However, in some cases " -"you'll have to help the kernel a bit." +msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit." msgstr "" #. Tag: para #: boot-installer.xml:2560 #, no-c-format -msgid "" -"If this is the first time you're booting the system, try the default boot " -"parameters (i.e., don't try setting parameters) and see if it works " -"correctly. It probably will. If not, you can reboot later and look for any " -"special parameters that inform the system about your hardware." +msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware." msgstr "" #. Tag: para #: boot-installer.xml:2567 #, no-c-format -msgid "" -"Information on many boot parameters can be found in the <ulink url=\"http://" -"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, " -"including tips for obscure hardware. This section contains only a sketch of " -"the most salient parameters. Some common gotchas are included below in <xref " -"linkend=\"boot-troubleshooting\"/>." +msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>." msgstr "" #. Tag: para @@ -2544,39 +1818,20 @@ msgstr "" #, no-c-format msgid "" "When the kernel boots, a message <informalexample><screen>\n" -"Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k " -"available\n" -"</screen></informalexample> should be emitted early in the process. " -"<replaceable>total</replaceable> should match the total amount of RAM, in " -"kilobytes. If this doesn't match the actual amount of RAM you have " -"installed, you need to use the <userinput>mem=<replaceable>ram</" -"replaceable></userinput> parameter, where <replaceable>ram</replaceable> is " -"set to the amount of memory, suffixed with <quote>k</quote> for kilobytes, " -"or <quote>m</quote> for megabytes. For example, both <userinput>mem=65536k</" -"userinput> and <userinput>mem=64m</userinput> mean 64MB of RAM." +"Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k available\n" +"</screen></informalexample> should be emitted early in the process. <replaceable>total</replaceable> should match the total amount of RAM, in kilobytes. If this doesn't match the actual amount of RAM you have installed, you need to use the <userinput>mem=<replaceable>ram</replaceable></userinput> parameter, where <replaceable>ram</replaceable> is set to the amount of memory, suffixed with <quote>k</quote> for kilobytes, or <quote>m</quote> for megabytes. For example, both <userinput>mem=65536k</userinput> and <userinput>mem=64m</userinput> mean 64MB of RAM." msgstr "" #. Tag: para #: boot-installer.xml:2592 #, no-c-format -msgid "" -"If you are booting with a serial console, generally the kernel will " -"autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</" -"phrase>. If you have a videocard (framebuffer) and a keyboard also attached " -"to the computer which you wish to boot via serial console, you may have to " -"pass the <userinput>console=<replaceable>device</replaceable></userinput> " -"argument to the kernel, where <replaceable>device</replaceable> is your " -"serial device, which is usually something like <filename>ttyS0</filename>." +msgid "If you are booting with a serial console, generally the kernel will autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</phrase>. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>." msgstr "" #. Tag: para #: boot-installer.xml:2605 #, no-c-format -msgid "" -"For &arch-title; the serial devices are <filename>ttya</filename> or " -"<filename>ttyb</filename>. Alternatively, set the <envar>input-device</" -"envar> and <envar>output-device</envar> OpenPROM variables to " -"<filename>ttya</filename>." +msgid "For &arch-title; the serial devices are <filename>ttya</filename> or <filename>ttyb</filename>. Alternatively, set the <envar>input-device</envar> and <envar>output-device</envar> OpenPROM variables to <filename>ttya</filename>." msgstr "" #. Tag: title @@ -2588,14 +1843,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2617 #, no-c-format -msgid "" -"The installation system recognizes a few additional boot " -"parameters<footnote> <para> Note that the kernel accepts a maximum of 8 " -"command line options and 8 environment options (including any options added " -"by default for the installer). If these numbers are exceeded, 2.4 kernels " -"will drop any excess options and 2.6 kernels will panic. <phrase condition=" -"\"etch\">With kernel 2.6.9 or newer, you can use 32 command line options and " -"32 environment options.</phrase> </para> </footnote> which may be useful." +msgid "The installation system recognizes a few additional boot parameters<footnote> <para> Note that the kernel accepts a maximum of 8 command line options and 8 environment options (including any options added by default for the installer). If these numbers are exceeded, 2.4 kernels will drop any excess options and 2.6 kernels will panic. <phrase condition=\"etch\">With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options.</phrase> </para> </footnote> which may be useful." msgstr "" #. Tag: term @@ -2613,24 +1861,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:2643 #, no-c-format -msgid "" -"The default installation uses <userinput>debconf/priority=high</userinput>. " -"This means that both high and critical priority messages are shown, but " -"medium and low priority messages are skipped. If problems are encountered, " -"the installer adjusts the priority as needed." +msgid "The default installation uses <userinput>debconf/priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed." msgstr "" #. Tag: para #: boot-installer.xml:2650 #, no-c-format -msgid "" -"If you add <userinput>debconf/priority=medium</userinput> as boot parameter, " -"you will be shown the installation menu and gain more control over the " -"installation. When <userinput>debconf/priority=low</userinput> is used, all " -"messages are shown (this is equivalent to the <emphasis>expert</emphasis> " -"boot method). With <userinput>debconf/priority=critical</userinput>, the " -"installation system will display only critical messages and try to do the " -"right thing without fuss." +msgid "If you add <userinput>debconf/priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>debconf/priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>debconf/priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss." msgstr "" #. Tag: term @@ -2642,24 +1879,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2665 #, no-c-format -msgid "" -"This boot parameter controls the type of user interface used for the " -"installer. The current possible parameter settings are: <itemizedlist> " -"<listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></" -"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</" -"userinput></para> </listitem><listitem> " -"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </" -"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=slang</userinput></" -"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=ncurses</" -"userinput></para> </listitem><listitem> " -"<para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> </" -"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> " -"</listitem><listitem> <para><userinput>DEBIAN_FRONTEND=corba</userinput></" -"para> </listitem> </itemizedlist> The default front end is " -"<userinput>DEBIAN_FRONTEND=newt</userinput>. " -"<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial " -"console installs. Generally only the <userinput>newt</userinput> frontend is " -"available on default install media, so this is not very useful right now." +msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=slang</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=ncurses</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=corba</userinput></para> </listitem> </itemizedlist> The default front end is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally only the <userinput>newt</userinput> frontend is available on default install media, so this is not very useful right now." msgstr "" #. Tag: term @@ -2671,11 +1891,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2702 #, no-c-format -msgid "" -"Setting this boot parameter to 2 will cause the installer's boot process to " -"be verbosely logged. Setting it to 3 makes debug shells available at " -"strategic points in the boot process. (Exit the shells to continue the boot " -"process.)" +msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)" msgstr "" #. Tag: userinput @@ -2723,9 +1939,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2727 #, no-c-format -msgid "" -"Shells are run at various points in the boot process to allow detailed " -"debugging. Exit the shell to continue the boot." +msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot." msgstr "" #. Tag: term @@ -2737,19 +1951,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:2742 #, no-c-format -msgid "" -"The value of the parameter is the path to the device to load the Debian " -"installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</" -"userinput>" +msgid "The value of the parameter is the path to the device to load the Debian installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>" msgstr "" #. Tag: para #: boot-installer.xml:2748 #, no-c-format -msgid "" -"The boot floppy, which normally scans all floppies and USB storage devices " -"it can to find the root floppy, can be overridden by this parameter to only " -"look at the one device." +msgid "The boot floppy, which normally scans all floppies and USB storage devices it can to find the root floppy, can be overridden by this parameter to only look at the one device." msgstr "" #. Tag: term @@ -2761,22 +1969,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:2759 #, no-c-format -msgid "" -"Some architectures use the kernel framebuffer to offer installation in a " -"number of languages. If framebuffer causes a problem on your system you can " -"disable the feature by the parameter <userinput>debian-installer/" -"framebuffer=false</userinput>. Problem symptoms are error messages about " -"bterm or bogl, a blank screen, or a freeze within a few minutes after " -"starting the install." +msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature by the parameter <userinput>debian-installer/framebuffer=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install." msgstr "" #. Tag: para #: boot-installer.xml:2768 #, no-c-format -msgid "" -"The <userinput>video=vga16:off</userinput> argument may also be used to " -"disable the framebuffer. Such problems have been reported on a Dell Inspiron " -"with Mobile Radeon card." +msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card." msgstr "" #. Tag: para @@ -2794,13 +1993,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2782 #, no-c-format -msgid "" -"Because of display problems on some systems, framebuffer support is " -"<emphasis>disabled by default</emphasis> for &arch-title;. This can result " -"in ugly display on systems that do properly support the framebuffer, like " -"those with ATI graphical cards. If you see display problems in the " -"installer, you can try booting with parameter <userinput>debian-installer/" -"framebuffer=true</userinput>." +msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput>." msgstr "" #. Tag: term @@ -2812,9 +2005,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2796 #, no-c-format -msgid "" -"Set to <userinput>false</userinput> to prevent probing for USB on boot, if " -"that causes problems." +msgid "Set to <userinput>false</userinput> to prevent probing for USB on boot, if that causes problems." msgstr "" #. Tag: term @@ -2826,21 +2017,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:2806 #, no-c-format -msgid "" -"By default, the &d-i; automatically probes for network configuration via " -"DHCP. If the probe succeeds, you won't have a chance to review and change " -"the obtained settings. You can get to the manual network setup only in case " -"the DHCP probe fails." +msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails." msgstr "" #. Tag: para #: boot-installer.xml:2813 #, no-c-format -msgid "" -"If you have a DHCP server on your local network, but want to avoid it " -"because e.g. it gives wrong answers, you can use the parameter " -"<userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the " -"network with DHCP and to enter the information manually." +msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually." msgstr "" #. Tag: term @@ -2852,9 +2035,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2825 #, no-c-format -msgid "" -"Set to <userinput>false</userinput> to prevent starting PCMCIA services, if " -"that causes problems. Some laptops are well known for this misbehavior." +msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." msgstr "" #. Tag: term @@ -2866,9 +2047,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2836 #, no-c-format -msgid "" -"Specify the url to a preconfiguration file to download and use in automating " -"the install. See <xref linkend=\"automatic-install\"/>." +msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term @@ -2880,9 +2059,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2846 #, no-c-format -msgid "" -"Specify the path to a preconfiguration file to load to automating the " -"install. See <xref linkend=\"automatic-install\"/>." +msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>." msgstr "" #. Tag: term @@ -2894,22 +2071,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:2856 #, no-c-format -msgid "" -"By default, before rebooting, &d-i; automatically ejects the optical media " -"used during the installation. This can be unnecessary if the system does not " -"automatically boot off the CD. In some cases it may even be undesirable, for " -"example if the optical drive cannot reinsert the media itself and the user " -"is not there to do it manually. Many slot loading, slim-line, and caddy " -"style drives cannot reload media automatically." +msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically." msgstr "" #. Tag: para #: boot-installer.xml:2865 #, no-c-format -msgid "" -"Set to <userinput>false</userinput> to disable automatic ejection, and be " -"aware that you may need to ensure that the system does not automatically " -"boot from the optical drive after the initial installation." +msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation." msgstr "" #. Tag: term @@ -2933,9 +2101,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:2886 #, no-c-format -msgid "" -"Set to <userinput>true</userinput> to enter rescue mode rather than " -"performing a normal installation. See <xref linkend=\"rescue\"/>." +msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." msgstr "" #. Tag: title @@ -2953,51 +2119,31 @@ msgstr "" #. Tag: para #: boot-installer.xml:2911 #, no-c-format -msgid "" -"The biggest problem for people using floppy disks to install Debian seems to " -"be floppy disk reliability." +msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." msgstr "" #. Tag: para #: boot-installer.xml:2916 #, no-c-format -msgid "" -"The boot floppy is the floppy with the worst problems, because it is read by " -"the hardware directly, before Linux boots. Often, the hardware doesn't read " -"as reliably as the Linux floppy disk driver, and may just stop without " -"printing an error message if it reads incorrect data. There can also be " -"failures in the Driver Floppies most of which indicate themselves with a " -"flood of messages about disk I/O errors." +msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the Driver Floppies most of which indicate themselves with a flood of messages about disk I/O errors." msgstr "" #. Tag: para #: boot-installer.xml:2925 #, no-c-format -msgid "" -"If you are having the installation stall at a particular floppy, the first " -"thing you should do is re-download the floppy disk image and write it to a " -"<emphasis>different</emphasis> floppy. Simply reformatting the old floppy " -"may not be sufficient, even if it appears that the floppy was reformatted " -"and written with no errors. It is sometimes useful to try writing the floppy " -"on a different system." +msgid "If you are having the installation stall at a particular floppy, the first thing you should do is re-download the floppy disk image and write it to a <emphasis>different</emphasis> floppy. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system." msgstr "" #. Tag: para #: boot-installer.xml:2935 #, no-c-format -msgid "" -"One user reports he had to write the images to floppy <emphasis>three</" -"emphasis> times before one worked, and then everything was fine with the " -"third floppy." +msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy." msgstr "" #. Tag: para #: boot-installer.xml:2941 #, no-c-format -msgid "" -"Other users have reported that simply rebooting a few times with the same " -"floppy in the floppy drive can lead to a successful boot. This is all due to " -"buggy hardware or firmware floppy drivers." +msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers." msgstr "" #. Tag: title @@ -3009,39 +2155,25 @@ msgstr "" #. Tag: para #: boot-installer.xml:2952 #, no-c-format -msgid "" -"If you have problems and the kernel hangs during the boot process, doesn't " -"recognize peripherals you actually have, or drives are not recognized " -"properly, the first thing to check is the boot parameters, as discussed in " -"<xref linkend=\"boot-parms\"/>." +msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>." msgstr "" #. Tag: para #: boot-installer.xml:2959 #, no-c-format -msgid "" -"If you are booting with your own kernel instead of the one supplied with the " -"installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your " -"kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>." +msgid "If you are booting with your own kernel instead of the one supplied with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>." msgstr "" #. Tag: para #: boot-installer.xml:2966 #, no-c-format -msgid "" -"Often, problems can be solved by removing add-ons and peripherals, and then " -"trying booting again. <phrase arch=\"i386\">Internal modems, sound cards, " -"and Plug-n-Play devices can be especially problematic.</phrase>" +msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"i386\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" msgstr "" #. Tag: para #: boot-installer.xml:2972 #, no-c-format -msgid "" -"If you have a large amount of memory installed in your machine, more than " -"512M, and the installer hangs when booting the kernel, you may need to " -"include a boot argument to limit the amount of memory the kernel sees, such " -"as <userinput>mem=512m</userinput>." +msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>." msgstr "" #. Tag: title @@ -3053,55 +2185,31 @@ msgstr "" #. Tag: para #: boot-installer.xml:2984 #, no-c-format -msgid "" -"There are some common installation problems that can be solved or avoided by " -"passing certain boot parameters to the installer." +msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." msgstr "" #. Tag: para #: boot-installer.xml:2989 #, no-c-format -msgid "" -"Some systems have floppies with <quote>inverted DCLs</quote>. If you receive " -"errors reading from the floppy, even when you know the floppy is good, try " -"the parameter <userinput>floppy=thinkpad</userinput>." +msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>." msgstr "" #. Tag: para #: boot-installer.xml:2995 #, no-c-format -msgid "" -"On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk " -"drivers), the IDE drive may not be properly recognized. Again, try it first " -"without the parameters and see if the IDE drive is recognized properly. If " -"not, determine your drive geometry (cylinders, heads, and sectors), and use " -"the parameter <userinput>hd=<replaceable>cylinders</replaceable>," -"<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></" -"userinput>." +msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>." msgstr "" #. Tag: para #: boot-installer.xml:3004 #, no-c-format -msgid "" -"If you have a very old machine, and the kernel hangs after saying " -"<computeroutput>Checking 'hlt' instruction...</computeroutput>, then you " -"should try the <userinput>no-hlt</userinput> boot argument, which disables " -"this test." +msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test." msgstr "" #. Tag: para #: boot-installer.xml:3011 #, no-c-format -msgid "" -"If your screen begins to show a weird picture while the kernel boots, eg. " -"pure white, pure black or colored pixel garbage, your system may contain a " -"problematic video card which does not switch to the framebuffer mode " -"properly. Then you can use the boot parameter <userinput>debian-installer/" -"framebuffer=false</userinput> or <userinput>video=vga16:off</userinput> to " -"disable the framebuffer console. Only the English language will be available " -"during the installation due to limited console features. See <xref linkend=" -"\"boot-parms\"/> for details." +msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>debian-installer/framebuffer=false</userinput> or <userinput>video=vga16:off</userinput> to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" #. Tag: title @@ -3113,28 +2221,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:3027 #, no-c-format -msgid "" -"Some laptop models produced by Dell are known to crash when PCMCIA device " -"detection tries to access some hardware addresses. Other laptops may display " -"similar problems. If you experience such a problem and you don't need PCMCIA " -"support during the installation, you can disable PCMCIA using the " -"<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can " -"then configure PCMCIA after the installation is completed and exclude the " -"resource range causing the problems." +msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems." msgstr "" #. Tag: para #: boot-installer.xml:3037 #, no-c-format -msgid "" -"Alternatively, you can boot the installer in expert mode. You will then be " -"asked to enter the resource range options your hardware needs. For example, " -"if you have one of the Dell laptops mentioned above, you should enter " -"<userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list " -"of some common resource range options in the <ulink url=\"http://pcmcia-cs." -"sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource " -"settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the " -"commas, if any, when you enter this value in the installer." +msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer." msgstr "" #. Tag: title @@ -3146,14 +2239,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:3055 #, no-c-format -msgid "" -"The kernel normally tries to install USB modules and the USB keyboard driver " -"in order to support some non-standard USB keyboards. However, there are some " -"broken USB systems where the driver hangs on loading. A possible workaround " -"may be disabling the USB controller in your mainboard BIOS setup. Another " -"option is passing the <userinput>debian-installer/probe/usb=false</" -"userinput> parameter at the boot prompt, which will prevent the modules from " -"being loaded." +msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter at the boot prompt, which will prevent the modules from being loaded." msgstr "" #. Tag: title @@ -3165,22 +2251,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:3071 #, no-c-format -msgid "" -"During the boot sequence, you may see many messages in the form " -"<computeroutput>can't find <replaceable>something</replaceable> </" -"computeroutput>, or <computeroutput> <replaceable>something</replaceable> " -"not present</computeroutput>, <computeroutput>can't initialize " -"<replaceable>something</replaceable> </computeroutput>, or even " -"<computeroutput>this driver release depends on <replaceable>something</" -"replaceable> </computeroutput>. Most of these messages are harmless. You see " -"them because the kernel for the installation system is built to run on " -"computers with many different peripheral devices. Obviously, no one computer " -"will have every possible peripheral device, so the operating system may emit " -"a few complaints while it looks for peripherals you don't own. You may also " -"see the system pause for a while. This happens when it is waiting for a " -"device to respond, and that device is not present on your system. If you " -"find the time it takes to boot the system unacceptably long, you can create " -"a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." +msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable> </computeroutput>, or <computeroutput> <replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable> </computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable> </computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." msgstr "" #. Tag: title @@ -3192,24 +2263,13 @@ msgstr "" #. Tag: para #: boot-installer.xml:3097 #, no-c-format -msgid "" -"If you get through the initial boot phase but cannot complete the install, " -"the bug reporter menu choice may be helpful. <phrase condition=\"sarge\"> It " -"copies system error logs and configuration information to a user-supplied " -"floppy. </phrase> <phrase condition=\"etch\"> It lets you store system error " -"logs and configuration information from the installer to a floppy, or " -"download them in a web browser. </phrase> This information may provide clues " -"as to what went wrong and how to fix it. If you are submitting a bug report " -"you may want to attach this information to the bug report." +msgid "If you get through the initial boot phase but cannot complete the install, the bug reporter menu choice may be helpful. <phrase condition=\"sarge\"> It copies system error logs and configuration information to a user-supplied floppy. </phrase> <phrase condition=\"etch\"> It lets you store system error logs and configuration information from the installer to a floppy, or download them in a web browser. </phrase> This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report you may want to attach this information to the bug report." msgstr "" #. Tag: para #: boot-installer.xml:3114 #, no-c-format -msgid "" -"Other pertinent installation messages may be found in <filename>/var/log/</" -"filename> during the installation, and <filename>/var/log/debian-installer/</" -"filename> after the computer has been booted into the installed system." +msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/debian-installer/</filename> after the computer has been booted into the installed system." msgstr "" #. Tag: title @@ -3221,31 +2281,20 @@ msgstr "" #. Tag: para #: boot-installer.xml:3126 #, no-c-format -msgid "" -"If you still have problems, please submit an installation report. We also " -"encourage installation reports to be sent even if the installation is " -"successful, so that we can get as much information as possible on the " -"largest number of hardware configurations." +msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations." msgstr "" #. Tag: para #: boot-installer.xml:3133 #, no-c-format -msgid "" -"If you have a working Debian system, the esiest way to send an installation " -"report is to install the installation-report and reportbug packages " -"(<command>apt-get install installation-report reportbug</command>) and run " -"the command <command>reportbug installation-report</command>." +msgid "If you have a working Debian system, the esiest way to send an installation report is to install the installation-report and reportbug packages (<command>apt-get install installation-report reportbug</command>) and run the command <command>reportbug installation-report</command>." msgstr "" #. Tag: para #: boot-installer.xml:3140 #, no-c-format msgid "" -"Please use this template when filling out installation reports, and file the " -"report as a bug report against the <classname>installation-reports</" -"classname> pseudo package, by sending it to <email>submit@bugs.debian.org</" -"email>. <informalexample><screen>\n" +"Please use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n" "Package: installation-reports\n" "\n" "Boot method: <How did you boot the installer? CD? floppy? network?>\n" @@ -3279,8 +2328,6 @@ msgid "" "\n" "<Description of the install, in prose, and any thoughts, comments\n" " and ideas you had during the initial install.>\n" -"</screen></informalexample> In the bug report, describe what the problem is, " -"including the last visible kernel messages in the event of a kernel hang. " -"Describe the steps that you did which brought the system into the problem " -"state." +"</screen></informalexample> In the bug report, describe what the problem is, including the last visible kernel messages in the event of a kernel hang. Describe the steps that you did which brought the system into the problem state." msgstr "" + diff --git a/po/sv/install-methods.po b/po/sv/install-methods.po index d2cd23974..32aa48594 100755 --- a/po/sv/install-methods.po +++ b/po/sv/install-methods.po @@ -4,206 +4,141 @@ # msgid "" msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" +"Project-Id-Version: install-methods\n" "POT-Creation-Date: 2001-02-09 01:25+0100\n" -"PO-Revision-Date: 2005-11-16 22:45+0100\n" +"PO-Revision-Date: 2005-11-20 22:25+0100\n" "Last-Translator: Daniel Nylander <po@danielnylander.se>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" +"Language-Team: Swedish <tp-sv@listor.tp-sv.se>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: sv\n" +"X-Poedit-Country: sv\n" #. Tag: title #: install-methods.xml:5 -#, fuzzy, no-c-format +#, no-c-format msgid "Obtaining System Installation Media" -msgstr "Installationsfel för grundsystemet" +msgstr "FÃ¥ tag pÃ¥ installationsmedia" #. Tag: title #: install-methods.xml:12 -#, fuzzy, no-c-format +#, no-c-format msgid "Official &debian; CD-ROM Sets" -msgstr "Inte en giltig cd-skiva för Debian" +msgstr "Officiella &debian; cd-rom-uppsättningar" #. 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 #: install-methods.xml:83 #, no-c-format msgid "Downloading Files from Debian Mirrors" -msgstr "" +msgstr "Ladda ner filer frÃ¥n Debian-speglar" #. 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 #: install-methods.xml:99 #, no-c-format msgid "Where to Find Installation Images" -msgstr "" +msgstr "Var man finner installationsavbildningar" #. 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> — 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> — 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 +#, no-c-format msgid "Alpha Installation Files" -msgstr "/tmp - temporära filer" +msgstr "Installationsfiler för Alpha" #. 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 +#, no-c-format msgid "RiscPC Installation Files" -msgstr "/tmp - temporära filer" +msgstr "Installationsfiler för RiscPC" #. 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 +#, no-c-format msgid "NetWinder Installation Files" -msgstr "/tmp - temporära filer" +msgstr "Installationsfiler för NetWinder" #. 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 +#, no-c-format msgid "CATS Installation Files" -msgstr "/tmp - temporära filer" +msgstr "Installationsfiler för CATS" #. 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 @@ -215,54 +150,37 @@ 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 #: install-methods.xml:250 -#, fuzzy, no-c-format +#, no-c-format msgid "Creating an IPL tape" -msgstr "Skapar enhetsfiler..." +msgstr "Skapa ett IPL-band" #. 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 #: install-methods.xml:276 #, no-c-format msgid "Creating Floppies from Disk Images" -msgstr "" +msgstr "Skapa startdisketter frÃ¥n diskettavbildningar" #. 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 @@ -280,335 +198,214 @@ 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 #: install-methods.xml:316 #, no-c-format msgid "Writing Disk Images From a Linux or Unix System" -msgstr "" +msgstr "Skriva diskettavbildning frÃ¥n ett Linux eller Unix-system" #. Tag: para #: 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 #: install-methods.xml:380 #, no-c-format msgid "Writing Disk Images From DOS, Windows, or OS/2" -msgstr "" +msgstr "Skriva diskettavbildning frÃ¥n DOS, Windows eller OS/2" #. 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 #: install-methods.xml:414 #, no-c-format msgid "Writing Disk Images on Atari Systems" -msgstr "" +msgstr "Skriva diskettavbildning pÃ¥ Atari-system" #. 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 #: install-methods.xml:426 #, no-c-format msgid "Writing Disk Images on Macintosh Systems" -msgstr "" +msgstr "Skriva diskettavbildning pÃ¥ Macintosh-system" #. 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 #: install-methods.xml:445 #, no-c-format msgid "Writing Disk Images From MacOS" -msgstr "" +msgstr "Skriva diskettavbildning frÃ¥n MacOS" #. 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 #: install-methods.xml:468 #, no-c-format msgid "Writing Disk Images with <command>Disk Copy</command>" -msgstr "" +msgstr "Skriva diskettavbildning med <command>Disk Copy</command>" #. 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 #: install-methods.xml:523 #, no-c-format msgid "Writing Disk Images with <command>suntar</command>" -msgstr "" +msgstr "Skriva diskettavbildning med <command>suntar</command>" #. 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 #: install-methods.xml:573 #, no-c-format msgid "Preparing Files for USB Memory Stick Booting" -msgstr "" +msgstr "Förbereda filer för uppstart med USB-minne" #. 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 @@ -620,56 +417,37 @@ msgstr "" #. Tag: para #: 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:" +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:" msgstr "" #. Tag: screen #: install-methods.xml:601 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sda</replaceable>" -msgstr "" +msgstr "# zcat boot.img.gz > /dev/<replaceable>sda</replaceable>" #. Tag: para #: 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:" +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:" msgstr "" #. Tag: screen #: install-methods.xml:612 #, no-c-format msgid "# zcat boot.img.gz > /dev/<replaceable>sda2</replaceable>" -msgstr "" +msgstr "# zcat boot.img.gz > /dev/<replaceable>sda2</replaceable>" #. Tag: para #: install-methods.xml:615 #, no-c-format -msgid "" -"Using this method will destroy anything already on the device. Make sure " -"that you use the correct device name for your USB stick." +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." +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 @@ -681,190 +459,131 @@ msgstr "" #. Tag: para #: 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:650 install-methods.xml:746 +#: install-methods.xml:650 +#: install-methods.xml:746 #, no-c-format msgid "USB stick partitioning on &arch-title;" -msgstr "" +msgstr "Partitionering av USB-minne pÃ¥ &arch-title;" #. Tag: para #: 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: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: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: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: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: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/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>" +"</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: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: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: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: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:794 #, no-c-format msgid "<filename>vmlinux</filename> (kernel binary)" -msgstr "" +msgstr "<filename>vmlinux</filename> (kärn-binär)" #. Tag: para #: install-methods.xml:799 #, no-c-format msgid "<filename>initrd.gz</filename> (initial ramdisk image)" -msgstr "" +msgstr "<filename>initrd.gz</filename> (initiell ramdisk-avbild)" #. Tag: para #: install-methods.xml:804 -#, fuzzy, no-c-format +#, no-c-format msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" -msgstr "Skapandet av huvudkonfigurationsfilen för yaboot misslyckades." +msgstr "<filename>yaboot.conf</filename> (yaboots konfigurationsfil)" #. Tag: para #: install-methods.xml:809 #, no-c-format msgid "<filename>boot.msg</filename> (optional boot message)" -msgstr "" +msgstr "<filename>boot.msg</filename> (valfritt uppstartsmeddelande)" #. Tag: para #: install-methods.xml:814 -#, fuzzy, no-c-format +#, no-c-format msgid "Optional kernel modules" -msgstr "Moduler som ska laddas:" +msgstr "Valfria kärnmoduler" #. Tag: para #: 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" @@ -876,89 +595,67 @@ 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:836 -#, fuzzy, no-c-format +#, no-c-format msgid "Adding an ISO image" -msgstr "Hittade ingen installations-ISO-avbild" +msgstr "Lägga till en ISO-avbild" #. Tag: para #: 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: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: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:862 #, no-c-format msgid "Booting the USB stick" -msgstr "" +msgstr "Starta upp pÃ¥ USB-minne" #. Tag: para #: 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:870 #, no-c-format msgid "# install-mbr /dev/<replaceable>sda</replaceable>" -msgstr "" +msgstr "# install-mbr /dev/<replaceable>sda</replaceable>" #. Tag: title #: install-methods.xml:882 #, no-c-format msgid "Preparing Files for Hard Disk Booting" -msgstr "" +msgstr "Förbereda filer för uppstart med hÃ¥rddisk" #. Tag: para #: 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: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 @@ -970,77 +667,55 @@ msgstr "" #. Tag: para #: 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: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: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: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: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: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:941 #, no-c-format msgid "<filename>vmlinuz</filename> (kernel binary)" -msgstr "" +msgstr "<filename>vmlinuz</filename> (kärn-binär)" #. Tag: para #: install-methods.xml:946 #, no-c-format msgid "<filename>initrd.gz</filename> (ramdisk image)" -msgstr "" +msgstr "<filename>initrd.gz</filename> (ramdisk-avbild)" #. Tag: para #: 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 @@ -1052,33 +727,13 @@ msgstr "" #. Tag: para #: 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: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 @@ -1090,37 +745,26 @@ msgstr "" #. Tag: para #: 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: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:1019 #, no-c-format msgid "vmlinux" -msgstr "" +msgstr "vmlinux" #. Tag: filename #: install-methods.xml:1024 #, no-c-format msgid "initrd.gz" -msgstr "" +msgstr "initrd.gz" #. Tag: filename #: install-methods.xml:1029 @@ -1137,12 +781,7 @@ msgstr "yaboot.conf" #. Tag: para #: 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 @@ -1160,117 +799,68 @@ msgstr "" #. Tag: para #: 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: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: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: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: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: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: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: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:1146 -#, fuzzy, no-c-format +#, no-c-format msgid "Setting up RARP server" -msgstr "Klar med partitionen" +msgstr "Konfigurering av RARP-server" #. Tag: para #: 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: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" @@ -1280,66 +870,40 @@ 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: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: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:1202 -#, fuzzy, no-c-format +#, no-c-format msgid "Setting up BOOTP server" -msgstr "Klar med partitionen" +msgstr "Konfigurering av BOOTP-server" #. Tag: para #: 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: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" @@ -1347,43 +911,26 @@ 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: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:1265 -#, fuzzy, no-c-format +#, no-c-format msgid "Setting up a DHCP server" -msgstr "Klar med partitionen" +msgstr "Konfigurering av DHCP-server" #. Tag: para #: 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" @@ -1403,28 +950,19 @@ 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: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: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 @@ -1437,8 +975,7 @@ msgstr "" #: 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" @@ -1466,62 +1003,39 @@ 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:1313 -#, fuzzy, no-c-format +#, no-c-format msgid "Enabling the TFTP Server" -msgstr "Diskussionsgruppsserver" +msgstr "Aktivering av TFTP-server" #. Tag: para #: 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: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: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 > /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\" > /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 @@ -1533,76 +1047,43 @@ msgstr "" #. Tag: para #: 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: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: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: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:1401 -#, fuzzy, no-c-format +#, no-c-format msgid "DECstation TFTP Images" -msgstr "Visa knappbilder" +msgstr "Avbilder för DECstation TFTP" #. Tag: para #: 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: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 @@ -1614,43 +1095,19 @@ msgstr "" #. Tag: para #: 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:1463 -#, fuzzy, no-c-format +#, no-c-format msgid "Alpha TFTP Booting" -msgstr "Alfavärde för markeringsrutan" +msgstr "Uppstart för Alpha via TFTP" #. Tag: para #: 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 @@ -1663,28 +1120,16 @@ msgstr "" #: 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: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 @@ -1696,20 +1141,13 @@ msgstr "" #. Tag: para #: 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: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 @@ -1721,11 +1159,7 @@ msgstr "" #. Tag: para #: 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 @@ -1737,9 +1171,7 @@ msgstr "" #. Tag: para #: 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 @@ -1751,12 +1183,7 @@ msgstr "Automatisk installation" #. Tag: para #: 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 @@ -1768,93 +1195,53 @@ msgstr "" #. Tag: para #: 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: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: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: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 > <replaceable>file</replaceable>\n" "$ debconf-get-selections >> <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: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: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: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: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 @@ -1866,11 +1253,7 @@ msgstr "" #. Tag: para #: 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 @@ -1880,3 +1263,4 @@ msgid "" "d-i foo/bar string value\n" "d-i foo/bar seen false" msgstr "" + diff --git a/po/sv/preparing.po b/po/sv/preparing.po index c5064bc06..05befebc0 100755 --- a/po/sv/preparing.po +++ b/po/sv/preparing.po @@ -4,20 +4,22 @@ # msgid "" msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" +"Project-Id-Version: installation guide 20051025 preparing\n" "POT-Creation-Date: 2001-02-09 01:25+0100\n" -"PO-Revision-Date: 2005-11-16 22:43+0100\n" +"PO-Revision-Date: 2005-11-20 10:54+0100\n" "Last-Translator: Daniel Nylander <po@danielnylander.se>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" +"Language-Team: Swedish <tp-sv@listor.tp-sv.se>\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" +"X-Poedit-Language: sv\n" +"X-Poedit-Country: sv\n" #. Tag: title #: preparing.xml:5 -#, fuzzy, no-c-format +#, no-c-format msgid "Before Installing &debian;" -msgstr "Installation av &debian; &release för &architecture;" +msgstr "Före installation av &debian;" #. Tag: para #: preparing.xml:6 @@ -27,9 +29,9 @@ msgstr "" #. Tag: title #: preparing.xml:19 -#, fuzzy, no-c-format +#, no-c-format msgid "Overview of the Installation Process" -msgstr "Uppdatering pågår..." +msgstr "Översikt för installationsprocessen" #. Tag: para #: preparing.xml:20 @@ -87,15 +89,15 @@ msgstr "" #. Tag: para #: preparing.xml:85 -#, fuzzy, no-c-format +#, no-c-format msgid "Boot the installation system." -msgstr "Installation av grundsystemet" +msgstr "Starta upp installationssystemet." #. Tag: para #: preparing.xml:90 -#, fuzzy, no-c-format +#, no-c-format msgid "Select installation language." -msgstr "Välj katalogens språk" +msgstr "Välj sprÃ¥k för installationen." #. Tag: para #: preparing.xml:95 @@ -105,9 +107,9 @@ msgstr "" #. Tag: para #: preparing.xml:101 -#, fuzzy, no-c-format +#, no-c-format msgid "Configure one network interface." -msgstr "Konfigurera nätverket automatiskt med DHCP?" +msgstr "Konfigurera ett nätverkssgränssnitt" #. Tag: para #: preparing.xml:106 @@ -208,21 +210,21 @@ msgstr "" #. Tag: title #: preparing.xml:249 -#, fuzzy, no-c-format +#, no-c-format msgid "Information You Will Need" -msgstr "Du behöver ange en address" +msgstr "Information du behöver" #. Tag: title #: preparing.xml:252 -#, fuzzy, no-c-format +#, no-c-format msgid "Documentation" -msgstr "Documentation författare" +msgstr "Dokumentation" #. Tag: title #: preparing.xml:255 -#, fuzzy, no-c-format +#, no-c-format msgid "Installation Manual" -msgstr "manuell sökning" +msgstr "Installationsmanual" #. Tag: para #: preparing.xml:257 @@ -232,9 +234,9 @@ msgstr "" #. Tag: itemizedlist #: preparing.xml:263 -#, fuzzy, no-c-format +#, no-c-format msgid "&list-install-manual-files;" -msgstr "Visa filer som lista" +msgstr "&list-install-manual-files;" #. Tag: para #: preparing.xml:269 @@ -250,9 +252,9 @@ msgstr "" #. Tag: title #: preparing.xml:290 -#, fuzzy, no-c-format +#, no-c-format msgid "Hardware documentation" -msgstr "Documentation författare" +msgstr "HÃ¥rdvarudokumentation" #. Tag: para #: preparing.xml:291 @@ -268,15 +270,15 @@ msgstr "" #. Tag: ulink #: preparing.xml:308 -#, fuzzy, no-c-format +#, no-c-format msgid "Linux/m68k FAQ" -msgstr "Linux Standard Base" +msgstr "Linux/m68k FAQ" #. Tag: ulink #: preparing.xml:314 -#, fuzzy, no-c-format +#, no-c-format msgid "Linux/Alpha FAQ" -msgstr "Alfavärde för markeringsrutan" +msgstr "Linux/Alpha FAQ" #. Tag: ulink #: preparing.xml:320 @@ -286,9 +288,9 @@ msgstr "" #. Tag: ulink #: preparing.xml:326 -#, fuzzy, no-c-format +#, no-c-format msgid "Linux/Mips website" -msgstr "Linux Standard Base" +msgstr "Linux/Mips webbplats" #. Tag: title #: preparing.xml:335 @@ -394,33 +396,33 @@ msgstr "" #. Tag: entry #: preparing.xml:451 -#, fuzzy, no-c-format +#, no-c-format msgid "Hardware" -msgstr "Maskinvarustöd" +msgstr "HÃ¥rdvara" #. Tag: entry #: preparing.xml:451 -#, fuzzy, no-c-format +#, no-c-format msgid "Information You Might Need" -msgstr "Du behöver ange en address" +msgstr "Information du kanske behöver" #. Tag: entry #: preparing.xml:457 -#, fuzzy, no-c-format +#, no-c-format msgid "Hard Drives" -msgstr "Partitionera hårddiskar automatiskt" +msgstr "hÃ¥rddiskar" #. Tag: entry #: preparing.xml:458 -#, fuzzy, no-c-format +#, no-c-format msgid "How many you have." -msgstr "Är du vilsen?" +msgstr "Hur mÃ¥nga du har." #. Tag: entry #: preparing.xml:460 -#, fuzzy, no-c-format +#, no-c-format msgid "Their order on the system." -msgstr "Inga funktionspaket hittades på det här systemet.\n" +msgstr "Deras ordning i systemet." #. Tag: entry #: preparing.xml:462 @@ -431,15 +433,15 @@ msgstr "" #. Tag: entry #: preparing.xml:464 #: preparing.xml:516 -#, fuzzy, no-c-format +#, no-c-format msgid "Available free space." -msgstr "Oanvändbart ledigt utrymme" +msgstr "Tillgängligt ledigt utrymme." #. Tag: entry #: preparing.xml:465 -#, fuzzy, no-c-format +#, no-c-format msgid "Partitions." -msgstr "Partitioner formatteras" +msgstr "Partitioner." #. Tag: entry #: preparing.xml:467 @@ -449,52 +451,52 @@ msgstr "" #. Tag: entry #: preparing.xml:471 -#, fuzzy, no-c-format +#, no-c-format msgid "Monitor" -msgstr "Monitor input" +msgstr "Skärm" #. Tag: entry #: preparing.xml:472 #: preparing.xml:492 #: preparing.xml:498 #: preparing.xml:504 -#, fuzzy, no-c-format +#, no-c-format msgid "Model and manufacturer." -msgstr "Datum och tid" +msgstr "Modell och tillverkare." #. Tag: entry #: preparing.xml:474 -#, fuzzy, no-c-format +#, no-c-format msgid "Resolutions supported." -msgstr "Understödda enheter" +msgstr "Upplösningar som stöds." #. Tag: entry #: preparing.xml:475 -#, fuzzy, no-c-format +#, no-c-format msgid "Horizontal refresh rate." -msgstr "Standard samplingsrekvens:" +msgstr "" #. Tag: entry #: preparing.xml:476 -#, fuzzy, no-c-format +#, no-c-format msgid "Vertical refresh rate." -msgstr "Standard samplingsrekvens:" +msgstr "" #. Tag: entry #: preparing.xml:478 #, no-c-format msgid "Color depth (number of colors) supported." -msgstr "" +msgstr "Färgdjup (antal färger) som stöds." #. Tag: entry #: preparing.xml:480 -#, fuzzy, no-c-format +#, no-c-format msgid "Screen size." -msgstr "Ogiltig storlek" +msgstr "Skärmstorlek." #. Tag: entry #: preparing.xml:483 -#, fuzzy, no-c-format +#, no-c-format msgid "Mouse" msgstr "Mus" @@ -502,63 +504,63 @@ msgstr "Mus" #: preparing.xml:484 #, no-c-format msgid "Type: serial, PS/2, or USB." -msgstr "" +msgstr "Typ: seriell, PS/2 eller USB." #. Tag: entry #: preparing.xml:486 -#, fuzzy, no-c-format +#, no-c-format msgid "Port." -msgstr "Port:" +msgstr "Port." #. Tag: entry #: preparing.xml:487 #, no-c-format msgid "Manufacturer." -msgstr "" +msgstr "Tillverkare." #. Tag: entry #: preparing.xml:488 -#, fuzzy, no-c-format +#, no-c-format msgid "Number of buttons." -msgstr "Meddelandeknappar" +msgstr "Antal knappar." #. Tag: entry #: preparing.xml:491 #: preparing.xml:519 -#, fuzzy, no-c-format +#, no-c-format msgid "Network" -msgstr "Nätverk" +msgstr "Nätverk" #. Tag: entry #: preparing.xml:494 #: preparing.xml:520 -#, fuzzy, no-c-format +#, no-c-format msgid "Type of adapter." -msgstr "Tangentbordstyp:" +msgstr "Typ av adapter." #. Tag: entry #: preparing.xml:497 -#, fuzzy, no-c-format +#, no-c-format msgid "Printer" msgstr "Skrivare" #. Tag: entry #: preparing.xml:500 -#, fuzzy, no-c-format +#, no-c-format msgid "Printing resolutions supported." -msgstr "Följande kodningssystem stöds:" +msgstr "Utskriftsupplösningar som stöds." #. Tag: entry #: preparing.xml:503 -#, fuzzy, no-c-format +#, no-c-format msgid "Video Card" -msgstr "Smartkort" +msgstr "Grafikkort" #. Tag: entry #: preparing.xml:506 -#, fuzzy, no-c-format +#, no-c-format msgid "Video RAM available." -msgstr "(beskrivning saknas)" +msgstr "Tillgängligt videominne." #. Tag: entry #: preparing.xml:508 @@ -570,19 +572,19 @@ msgstr "" #: preparing.xml:513 #, no-c-format msgid "DASD" -msgstr "" +msgstr "DASD" #. Tag: entry #: preparing.xml:514 -#, fuzzy, no-c-format +#, no-c-format msgid "Device number(s)." -msgstr "Spår nummer:" +msgstr "Enhetsnummer." #. Tag: entry #: preparing.xml:522 -#, fuzzy, no-c-format +#, no-c-format msgid "Device numbers." -msgstr "RAID%s-enhet nr. %s" +msgstr "Enhetsnummer." #. Tag: entry #: preparing.xml:523 @@ -592,9 +594,9 @@ msgstr "" #. Tag: title #: preparing.xml:531 -#, fuzzy, no-c-format +#, no-c-format msgid "Hardware Compatibility" -msgstr "Maskinvarustöd" +msgstr "HÃ¥rdvarukompatibilitet" #. Tag: para #: preparing.xml:533 @@ -652,9 +654,9 @@ msgstr "" #. Tag: title #: preparing.xml:590 -#, fuzzy, no-c-format +#, no-c-format msgid "Network Settings" -msgstr "Nätverksinställningar" +msgstr "Nätverksinställningar" #. Tag: para #: preparing.xml:592 @@ -670,15 +672,15 @@ msgstr "" #. Tag: para #: preparing.xml:604 -#, fuzzy, no-c-format +#, no-c-format msgid "Your domain name." -msgstr "Ledarnamn" +msgstr "Ditt domännamn." #. Tag: para #: preparing.xml:609 -#, fuzzy, no-c-format +#, no-c-format msgid "Your computer's IP address." -msgstr "ange IP-address (0..9, vänster, höger)" +msgstr "Din dators IP-address." #. Tag: para #: preparing.xml:614 @@ -712,9 +714,9 @@ msgstr "" #. Tag: para #: preparing.xml:645 -#, fuzzy, no-c-format +#, no-c-format msgid "ESSID of your wireless network." -msgstr "Trådlös ESSID för ${iface}" +msgstr "ESSID för ditt trÃ¥dlösa nätverk." #. Tag: para #: preparing.xml:650 @@ -766,27 +768,27 @@ msgstr "" #. Tag: entry #: preparing.xml:703 -#, fuzzy, no-c-format +#, no-c-format msgid "Install Type" -msgstr "Tangentbordstyp:" +msgstr "Installationstyp" #. Tag: entry #: preparing.xml:703 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>RAM</entry>" -msgstr "Byt namn på post" +msgstr "<entry>RAM</entry>" #. Tag: entry #: preparing.xml:703 #, no-c-format msgid "Hard Drive" -msgstr "hårddisk" +msgstr "hÃ¥rddisk" #. Tag: entry #: preparing.xml:709 -#, fuzzy, no-c-format +#, no-c-format msgid "No desktop" -msgstr "Bulgarisk skrivbordsmiljö" +msgstr "Ingen skrivbordsmiljö" #. Tag: entry #: preparing.xml:710 @@ -798,13 +800,13 @@ msgstr "24 megabyte" #: preparing.xml:711 #, no-c-format msgid "450 megabytes" -msgstr "" +msgstr "450 megabyte" #. Tag: entry #: preparing.xml:713 -#, fuzzy, no-c-format +#, no-c-format msgid "With Desktop" -msgstr "Bulgarisk skrivbordsmiljö" +msgstr "Med skrivbordsmiljö" #. Tag: entry #: preparing.xml:714 @@ -816,19 +818,19 @@ msgstr "64 megabyte" #: preparing.xml:715 #, no-c-format msgid "1 gigabyte" -msgstr "" +msgstr "1 gigabyte" #. Tag: entry #: preparing.xml:717 -#, fuzzy, no-c-format +#, no-c-format msgid "Server" -msgstr "Server:" +msgstr "Server" #. Tag: entry #: preparing.xml:718 -#, fuzzy, no-c-format +#, no-c-format msgid "128 megabytes" -msgstr "128-QAM" +msgstr "128 megabyte" #. Tag: entry #: preparing.xml:719 @@ -868,9 +870,9 @@ msgstr "" #. Tag: term #: preparing.xml:758 -#, fuzzy, no-c-format +#, no-c-format msgid "Work Console" -msgstr "Felkonsoll" +msgstr "Arbetskonsoll" #. Tag: para #: preparing.xml:759 @@ -1066,9 +1068,9 @@ msgstr "" #. Tag: title #: preparing.xml:1049 -#, fuzzy, no-c-format +#, no-c-format msgid "Partitioning in Windows NT" -msgstr "Windows NT %lu.%lu (bygge %lu" +msgstr "Partitionering i Windows NT" #. Tag: para #: preparing.xml:1051 @@ -1150,9 +1152,9 @@ msgstr "" #. Tag: title #: preparing.xml:1174 -#, fuzzy, no-c-format +#, no-c-format msgid "Partitioning for DOS" -msgstr "Val: \"%c\" för hjälp> " +msgstr "Partitionering för DOS" #. Tag: para #: preparing.xml:1176 @@ -1170,13 +1172,13 @@ msgstr "" #: preparing.xml:1190 #, no-c-format msgid "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4" -msgstr "" +msgstr "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4" #. Tag: title #: preparing.xml:1201 -#, fuzzy, no-c-format +#, no-c-format msgid "Partitioning in AmigaOS" -msgstr "IPv6-in-IPv4" +msgstr "Partitionering i AmigaOS" #. Tag: para #: preparing.xml:1202 @@ -1246,9 +1248,9 @@ msgstr "" #. Tag: title #: preparing.xml:1302 -#, fuzzy, no-c-format +#, no-c-format msgid "Partitioning in MacOS" -msgstr "IPv6-in-IPv4" +msgstr "Partitionering i MacOS" #. Tag: para #: preparing.xml:1303 @@ -1264,9 +1266,9 @@ msgstr "" #. Tag: title #: preparing.xml:1330 -#, fuzzy, no-c-format +#, no-c-format msgid "Partitioning from SunOS" -msgstr "Frekvens (Hz): från" +msgstr "Partitionering frÃ¥n SunOS" #. Tag: para #: preparing.xml:1332 @@ -1294,9 +1296,9 @@ msgstr "" #. Tag: title #: preparing.xml:1376 -#, fuzzy, no-c-format +#, no-c-format msgid "MacOS/OSX Partitioning" -msgstr "Fortsätt partitionering?" +msgstr "MacOS/OSX-partitionering" #. Tag: para #: preparing.xml:1378 @@ -1356,7 +1358,7 @@ msgstr "" #: preparing.xml:1467 #, no-c-format msgid "AMI BIOS" -msgstr "" +msgstr "AMI BIOS" #. Tag: para #: preparing.xml:1468 @@ -1368,7 +1370,7 @@ msgstr "" #: preparing.xml:1476 #, no-c-format msgid "Award BIOS" -msgstr "" +msgstr "Award BIOS" #. Tag: para #: preparing.xml:1477 @@ -1380,7 +1382,7 @@ msgstr "" #: preparing.xml:1486 #, no-c-format msgid "DTK BIOS" -msgstr "" +msgstr "DTK BIOS" #. Tag: para #: preparing.xml:1487 @@ -1390,9 +1392,9 @@ msgstr "" #. Tag: term #: preparing.xml:1494 -#, fuzzy, no-c-format +#, no-c-format msgid "IBM PS/2 BIOS" -msgstr "PS kvadrat (Euklidisk punkt)" +msgstr "IBM PS/2 BIOS" #. Tag: para #: preparing.xml:1495 @@ -1404,7 +1406,7 @@ msgstr "" #: preparing.xml:1509 #, no-c-format msgid "Phoenix BIOS" -msgstr "" +msgstr "Phoenix BIOS" #. Tag: para #: preparing.xml:1510 @@ -1427,9 +1429,9 @@ msgstr "" #. Tag: title #: preparing.xml:1542 #: preparing.xml:1885 -#, fuzzy, no-c-format +#, no-c-format msgid "Boot Device Selection" -msgstr "Fastställer startenhet för GRUB..." +msgstr "Val av uppstartsenhet" #. Tag: para #: preparing.xml:1544 @@ -1483,7 +1485,7 @@ msgstr "" #: preparing.xml:1599 #, no-c-format msgid "C is the hard drive, and A is the floppy drive." -msgstr "" +msgstr "C är hÃ¥rddisken och A är diskettenheten." #. Tag: para #: preparing.xml:1605 @@ -1541,15 +1543,15 @@ msgstr "" #. Tag: title #: preparing.xml:1671 -#, fuzzy, no-c-format +#, no-c-format msgid "Miscellaneous BIOS Settings" -msgstr "Blandade ljudinställningar och moduler" +msgstr "Blandade BIOS-inställningar" #. Tag: title #: preparing.xml:1673 -#, fuzzy, no-c-format +#, no-c-format msgid "CD-ROM Settings" -msgstr "CD-ROM saknas" +msgstr "Cd-rom-inställningar" #. Tag: para #: preparing.xml:1674 @@ -1571,9 +1573,9 @@ msgstr "" #. Tag: title #: preparing.xml:1695 -#, fuzzy, no-c-format +#, no-c-format msgid "Virus Protection" -msgstr "okänd krypteringsalgoritm\n" +msgstr "Virusskydd" #. Tag: para #: preparing.xml:1696 @@ -1583,9 +1585,9 @@ msgstr "" #. Tag: title #: preparing.xml:1717 -#, fuzzy, no-c-format +#, no-c-format msgid "Shadow RAM" -msgstr "Pilskugga" +msgstr "Shadow RAM" #. Tag: para #: preparing.xml:1718 @@ -1595,9 +1597,9 @@ msgstr "" #. Tag: title #: preparing.xml:1735 -#, fuzzy, no-c-format +#, no-c-format msgid "Memory Hole" -msgstr "Hålförhållande" +msgstr "" #. Tag: para #: preparing.xml:1736 @@ -1613,9 +1615,9 @@ msgstr "" #. Tag: title #: preparing.xml:1758 -#, fuzzy, no-c-format +#, no-c-format msgid "Advanced Power Management" -msgstr "Stadsförvaltning" +msgstr "" #. Tag: para #: preparing.xml:1759 @@ -1637,9 +1639,9 @@ msgstr "" #. Tag: title #: preparing.xml:1802 -#, fuzzy, no-c-format +#, no-c-format msgid "Invoking OpenFirmware" -msgstr "vid OpenFirmware-prompten." +msgstr "" #. Tag: para #: preparing.xml:1803 @@ -1721,15 +1723,15 @@ msgstr "" #. Tag: screen #: preparing.xml:1939 -#, fuzzy, no-c-format +#, no-c-format msgid "eeprom boot-device=disk1:1" -msgstr "Fastställer startenhet för GRUB..." +msgstr "eeprom boot-device=disk1:1" #. Tag: title #: preparing.xml:1949 -#, fuzzy, no-c-format +#, no-c-format msgid "BIOS Setup" -msgstr "Installation av hårddisk..." +msgstr "" #. Tag: para #: preparing.xml:1950 @@ -1781,9 +1783,9 @@ msgstr "" #. Tag: title #: preparing.xml:2028 -#, fuzzy, no-c-format +#, no-c-format msgid "Setting up an installation server" -msgstr "Klar med partitionen" +msgstr "Ställa in en installationsserver" #. Tag: para #: preparing.xml:2030 @@ -1841,9 +1843,9 @@ msgstr "" #. Tag: title #: preparing.xml:2105 -#, fuzzy, no-c-format +#, no-c-format msgid "The Turbo Switch" -msgstr "Uncommitted omkopplare:" +msgstr "Turbo-knappen" #. Tag: para #: preparing.xml:2106 @@ -1855,7 +1857,7 @@ msgstr "" #: preparing.xml:2119 #, no-c-format msgid "Cyrix CPUs and Floppy Disk Errors" -msgstr "" +msgstr "Cyrix CPU:er och diskettfel" #. Tag: para #: preparing.xml:2120 @@ -1871,9 +1873,9 @@ msgstr "" #. Tag: title #: preparing.xml:2138 -#, fuzzy, no-c-format +#, no-c-format msgid "Peripheral Hardware Settings" -msgstr "Sparar inställningar för nätverket ..." +msgstr "" #. Tag: para #: preparing.xml:2139 @@ -1891,7 +1893,7 @@ msgstr "" #: preparing.xml:2157 #, no-c-format msgid "USB BIOS support and keyboards" -msgstr "" +msgstr "USB BIOS-stöd och tangentbord" #. Tag: para #: preparing.xml:2158 @@ -1903,7 +1905,7 @@ msgstr "" #: preparing.xml:2171 #, no-c-format msgid "More than 64 MB RAM" -msgstr "" +msgstr "Mer än 64 MB RAM" #. Tag: para #: preparing.xml:2172 diff --git a/po/sv/random-bits.po b/po/sv/random-bits.po index b3f920791..bb2bff54a 100755 --- a/po/sv/random-bits.po +++ b/po/sv/random-bits.po @@ -4,54 +4,45 @@ # msgid "" msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" +"Project-Id-Version: random-bits\n" "POT-Creation-Date: 2001-02-09 01:25+0100\n" -"PO-Revision-Date: 2005-11-16 22:42+0100\n" +"PO-Revision-Date: 2005-11-21 00:17+0100\n" "Last-Translator: Daniel Nylander <po@danielnylander.se>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" +"Language-Team: Swedish <tp-sv@listor.tp-sv.se>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: sv\n" +"X-Poedit-Country: sv\n" #. Tag: title #: random-bits.xml:4 -#, fuzzy, no-c-format +#, no-c-format msgid "Random Bits" -msgstr "_Packa bitar" +msgstr "Blandade delar" #. Tag: title #: random-bits.xml:11 -#, fuzzy, no-c-format +#, no-c-format msgid "Preconfiguration File Example" -msgstr "Misslyckades med att hämta förkonfigurationsfilen" +msgstr "Exempel pÃ¥ förkonfigurationsfil" #. 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 @@ -95,8 +86,7 @@ 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" @@ -175,8 +165,7 @@ 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" @@ -219,13 +208,11 @@ 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" @@ -276,8 +263,7 @@ 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" @@ -395,8 +381,7 @@ 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" @@ -423,11 +408,9 @@ 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" @@ -458,8 +441,7 @@ 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" @@ -483,8 +465,7 @@ 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" @@ -574,8 +555,7 @@ msgid "" "# 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" @@ -612,13 +592,11 @@ 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" @@ -673,8 +651,7 @@ 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" @@ -776,8 +753,7 @@ 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" @@ -819,52 +795,45 @@ msgstr "" #. Tag: title #: random-bits.xml:62 -#, fuzzy, no-c-format +#, no-c-format msgid "Linux Devices" -msgstr "Inmatningsenheter" +msgstr "Linux-enheter" #. 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 #: random-bits.xml:78 -#, fuzzy, no-c-format +#, no-c-format msgid "<filename>fd0</filename>" -msgstr "Ogiltigt filnamn: %s" +msgstr "<filename>fd0</filename>" #. Tag: entry #: random-bits.xml:79 -#, fuzzy, no-c-format +#, no-c-format msgid "First Floppy Drive" -msgstr "Mata in en formaterad diskett i diskettstationen" +msgstr "Första diskettenheten" #. Tag: filename #: random-bits.xml:81 -#, fuzzy, no-c-format +#, no-c-format msgid "<filename>fd1</filename>" -msgstr "Ogiltigt filnamn: %s" +msgstr "<filename>fd1</filename>" #. Tag: entry #: random-bits.xml:82 -#, fuzzy, no-c-format +#, no-c-format msgid "Second Floppy Drive" -msgstr "Mata in en formaterad diskett i diskettstationen" +msgstr "Andra diskettenheten" #. Tag: filename #: random-bits.xml:88 -#, fuzzy, no-c-format +#, no-c-format msgid "<filename>hda</filename>" -msgstr "Ogiltigt filnamn: %s" +msgstr "<filename>hda</filename>" #. Tag: entry #: random-bits.xml:89 @@ -874,9 +843,9 @@ msgstr "" #. Tag: filename #: random-bits.xml:91 -#, fuzzy, no-c-format +#, no-c-format msgid "<filename>hdb</filename>" -msgstr "Ogiltigt filnamn: %s" +msgstr "<filename>hdb</filename>" #. Tag: entry #: random-bits.xml:92 @@ -886,9 +855,9 @@ msgstr "" #. Tag: filename #: random-bits.xml:94 -#, fuzzy, no-c-format +#, no-c-format msgid "<filename>hdc</filename>" -msgstr "Ogiltigt filnamn: %s" +msgstr "<filename>hdc</filename>" #. Tag: entry #: random-bits.xml:95 @@ -898,9 +867,9 @@ msgstr "" #. Tag: filename #: random-bits.xml:97 -#, fuzzy, no-c-format +#, no-c-format msgid "<filename>hdd</filename>" -msgstr "Ogiltigt filnamn: %s" +msgstr "<filename>hdd</filename>" #. Tag: entry #: random-bits.xml:98 @@ -916,9 +885,9 @@ msgstr "" #. Tag: entry #: random-bits.xml:101 -#, fuzzy, no-c-format +#, no-c-format msgid "First partition of the first IDE hard disk" -msgstr "Hittade ingen rotpartition pÃ¥ den första disken" +msgstr "Första partitionen pÃ¥ första IDE-hÃ¥rddisken" #. Tag: filename #: random-bits.xml:103 @@ -934,9 +903,9 @@ msgstr "" #. Tag: filename #: random-bits.xml:110 -#, fuzzy, no-c-format +#, no-c-format msgid "<filename>sda</filename>" -msgstr "Ogiltigt filnamn: %s" +msgstr "<filename>sda</filename>" #. Tag: entry #: random-bits.xml:111 @@ -946,9 +915,9 @@ msgstr "" #. Tag: filename #: random-bits.xml:113 -#, fuzzy, no-c-format +#, no-c-format msgid "<filename>sdb</filename>" -msgstr "Ogiltigt filnamn: %s" +msgstr "<filename>sdb</filename>" #. Tag: entry #: random-bits.xml:114 @@ -958,9 +927,9 @@ msgstr "" #. Tag: filename #: random-bits.xml:116 -#, fuzzy, no-c-format +#, no-c-format msgid "<filename>sdc</filename>" -msgstr "Ogiltigt filnamn: %s" +msgstr "<filename>sdc</filename>" #. Tag: entry #: random-bits.xml:117 @@ -972,19 +941,19 @@ msgstr "" #: random-bits.xml:119 #, no-c-format msgid "sda1" -msgstr "" +msgstr "sda1" #. Tag: entry #: random-bits.xml:120 -#, fuzzy, no-c-format +#, no-c-format msgid "First partition of the first SCSI hard disk" -msgstr "Hittade ingen rotpartition pÃ¥ den första disken" +msgstr "Första partitionen pÃ¥ första SCSI-hÃ¥rddisken" #. Tag: filename #: random-bits.xml:122 #, no-c-format msgid "sdd10" -msgstr "" +msgstr "sdd10" #. Tag: entry #: random-bits.xml:123 @@ -994,69 +963,69 @@ msgstr "" #. Tag: filename #: random-bits.xml:129 -#, fuzzy, no-c-format +#, no-c-format msgid "<filename>sr0</filename>" -msgstr "Ogiltigt filnamn: %s" +msgstr "<filename>sr0</filename>" #. Tag: entry #: random-bits.xml:130 #, no-c-format msgid "SCSI CD-ROM with the lowest SCSI ID" -msgstr "" +msgstr "SCSI cd-rom med lägsta SCSI ID" #. Tag: filename #: random-bits.xml:132 -#, fuzzy, no-c-format +#, no-c-format msgid "<filename>sr1</filename>" -msgstr "Ogiltigt filnamn: %s" +msgstr "<filename>sr1</filename>" #. Tag: entry #: random-bits.xml:133 #, no-c-format msgid "SCSI CD-ROM with the next higher SCSI ID" -msgstr "" +msgstr "SCSI cd-rom med nästa högre SCSI ID" #. Tag: filename #: random-bits.xml:139 #, no-c-format msgid "ttyS0" -msgstr "" +msgstr "ttyS0" #. Tag: entry #: random-bits.xml:140 #, no-c-format msgid "Serial port 0, COM1 under MS-DOS" -msgstr "" +msgstr "Seriellport 0, COM1 under MS-DOS" #. Tag: filename #: random-bits.xml:142 #, no-c-format msgid "ttyS1" -msgstr "" +msgstr "ttyS1" #. Tag: entry #: random-bits.xml:143 #, no-c-format msgid "Serial port 1, COM2 under MS-DOS" -msgstr "" +msgstr "Seriellport 1, COM2 under MS-DOS" #. Tag: filename #: random-bits.xml:145 #, no-c-format msgid "psaux" -msgstr "" +msgstr "psaux" #. Tag: entry #: random-bits.xml:146 -#, fuzzy, no-c-format +#, no-c-format msgid "PS/2 mouse device" -msgstr "Skapar enhetsfiler..." +msgstr "PS/2-musenhet" #. Tag: filename #: random-bits.xml:148 #, no-c-format msgid "gpmdata" -msgstr "" +msgstr "gpmdata" #. Tag: entry #: random-bits.xml:149 @@ -1068,7 +1037,7 @@ msgstr "" #: random-bits.xml:155 #, no-c-format msgid "cdrom" -msgstr "" +msgstr "cdrom" #. Tag: entry #: random-bits.xml:156 @@ -1078,9 +1047,9 @@ msgstr "" #. Tag: filename #: random-bits.xml:158 -#, fuzzy, no-c-format +#, no-c-format msgid "mouse" -msgstr "Mus" +msgstr "mus" #. Tag: entry #: random-bits.xml:159 @@ -1092,7 +1061,7 @@ msgstr "" #: random-bits.xml:165 #, no-c-format msgid "null" -msgstr "" +msgstr "null" #. Tag: entry #: random-bits.xml:166 @@ -1102,9 +1071,9 @@ msgstr "" #. Tag: filename #: random-bits.xml:168 -#, fuzzy, no-c-format +#, no-c-format msgid "zero" -msgstr "Placera vid &noll" +msgstr "noll" #. Tag: entry #: random-bits.xml:169 @@ -1114,68 +1083,46 @@ msgstr "" #. Tag: title #: random-bits.xml:176 -#, fuzzy, no-c-format +#, no-c-format msgid "Setting Up Your Mouse" -msgstr "Klar med partitionen" +msgstr "Konfigurera din mus" #. Tag: para #: 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 => /dev/psaux => gpm => /dev/gpmdata -> /dev/mouse => " -"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 => /dev/psaux => gpm => /dev/gpmdata -> /dev/mouse => 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 @@ -1194,56 +1141,45 @@ msgstr "" #. Tag: title #: random-bits.xml:228 -#, fuzzy, no-c-format +#, no-c-format msgid "Disk Space Needed for Tasks" -msgstr "Drivrutinen som behövs för din diskettstation:" +msgstr "Diskplats som behövs för uppgifter" #. 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 #: random-bits.xml:265 -#, fuzzy, no-c-format +#, no-c-format msgid "Task" -msgstr "^Funktionsinfo" +msgstr "Uppgift" #. Tag: entry #: random-bits.xml:266 -#, fuzzy, no-c-format +#, no-c-format msgid "Installed size (MB)" -msgstr "För stor storlek" +msgstr "Installerad storlek (MB)" #. Tag: entry #: random-bits.xml:267 -#, fuzzy, no-c-format +#, no-c-format msgid "Download size (MB)" -msgstr "För stor storlek" +msgstr "Nedladdningsstorlek (MB)" #. Tag: entry #: random-bits.xml:268 @@ -1253,256 +1189,227 @@ msgstr "" #. Tag: entry #: random-bits.xml:274 -#, fuzzy, no-c-format +#, no-c-format msgid "Desktop" -msgstr "Skrivbord" +msgstr "Skrivbordsmiljö" #. Tag: entry #: random-bits.xml:275 #, no-c-format msgid "1392" -msgstr "" +msgstr "1392" #. Tag: entry #: random-bits.xml:276 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>460</entry>" -msgstr "Byt namn pÃ¥ post" +msgstr "<entry>460</entry>" #. Tag: entry #: random-bits.xml:277 #, no-c-format msgid "1852" -msgstr "" +msgstr "1852" #. Tag: entry #: random-bits.xml:281 -#, fuzzy, no-c-format +#, no-c-format msgid "Web server" msgstr "Webbserver" #. Tag: entry #: random-bits.xml:282 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>36</entry>" -msgstr "Byt namn pÃ¥ post" +msgstr "<entry>36</entry>" #. Tag: entry #: random-bits.xml:283 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>12</entry>" -msgstr "IngÃ¥ng 12" +msgstr "<entry>12</entry>" #. Tag: entry #: random-bits.xml:284 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>48</entry>" -msgstr "Byt namn pÃ¥ post" +msgstr "<entry>48</entry>" #. Tag: entry #: random-bits.xml:288 -#, fuzzy, no-c-format +#, no-c-format msgid "Print server" msgstr "Utskriftsserver" #. Tag: entry #: random-bits.xml:289 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>168</entry>" -msgstr "Byt namn pÃ¥ post" +msgstr "<entry>168</entry>" #. Tag: entry #: random-bits.xml:290 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>58</entry>" -msgstr "Byt namn pÃ¥ post" +msgstr "<entry>58</entry>" #. Tag: entry #: random-bits.xml:291 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>226</entry>" -msgstr "Byt namn pÃ¥ post" +msgstr "<entry>226</entry>" #. Tag: entry #: random-bits.xml:295 -#, fuzzy, no-c-format +#, no-c-format msgid "DNS server" msgstr "DNS-server" #. Tag: entry #: random-bits.xml:296 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>2</entry>" -msgstr "post" +msgstr "<entry>2</entry>" #. Tag: entry #: random-bits.xml:297 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>1</entry>" -msgstr "post" +msgstr "<entry>1</entry>" #. Tag: entry -#: random-bits.xml:298 random-bits.xml:311 -#, fuzzy, no-c-format +#: random-bits.xml:298 +#: random-bits.xml:311 +#, no-c-format msgid "<entry>3</entry>" -msgstr "post" +msgstr "<entry>3</entry>" #. Tag: entry #: random-bits.xml:302 -#, fuzzy, no-c-format +#, no-c-format msgid "File server" msgstr "Filserver" #. Tag: entry #: random-bits.xml:303 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>47</entry>" -msgstr "Byt namn pÃ¥ post" +msgstr "<entry>47</entry>" #. Tag: entry #: random-bits.xml:304 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>24</entry>" -msgstr "Byt namn pÃ¥ post" +msgstr "<entry>24</entry>" #. Tag: entry #: random-bits.xml:305 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>71</entry>" -msgstr "Byt namn pÃ¥ post" +msgstr "<entry>71</entry>" #. Tag: entry #: random-bits.xml:309 -#, fuzzy, no-c-format +#, no-c-format msgid "Mail server" msgstr "E-postserver" #. Tag: entry #: random-bits.xml:310 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>10</entry>" -msgstr "IngÃ¥ng 10" +msgstr "<entry>10</entry>" #. Tag: entry #: random-bits.xml:312 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>13</entry>" -msgstr "IngÃ¥ng 13" +msgstr "<entry>13</entry>" #. Tag: entry #: random-bits.xml:316 -#, fuzzy, no-c-format +#, no-c-format msgid "SQL database" msgstr "SQL-databas" #. Tag: entry #: random-bits.xml:317 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>66</entry>" -msgstr "Byt namn pÃ¥ post" +msgstr "<entry>66</entry>" #. Tag: entry #: random-bits.xml:318 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>21</entry>" -msgstr "Byt namn pÃ¥ post" +msgstr "<entry>21</entry>" #. Tag: entry #: random-bits.xml:319 -#, fuzzy, no-c-format +#, no-c-format msgid "<entry>87</entry>" -msgstr "Byt namn pÃ¥ post" +msgstr "<entry>87</entry>" #. 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 #: random-bits.xml:347 #, no-c-format msgid "Installing &debian; from a Unix/Linux System" -msgstr "" +msgstr "Installera &debian; frÃ¥n ett Unix/Linux-system" #. 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 +#, no-c-format msgid "Getting Started" -msgstr "Spel pÃ¥börjat." +msgstr "" #. 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 @@ -1512,57 +1419,41 @@ msgid "" "# mkdir /mnt/debinst\n" "# mount /dev/hda6 /mnt/debinst" msgstr "" +"# mkdir /mnt/debinst\n" +"# mount /dev/hda6 /mnt/debinst" #. 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 +#, no-c-format msgid "Install <command>debootstrap</command>" -msgstr "Kommandosträngen är tom" +msgstr "Installera <command>debootstrap</command>" #. 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 @@ -1573,54 +1464,38 @@ msgid "" "# cd /\n" "# zcat /full-path-to-work/work/data.tar.gz | tar xv" msgstr "" +"# ar -x debootstrap_0.X.X_arch.deb\n" +"# cd /\n" +"# zcat /full-path-to-work/work/data.tar.gz | tar xv" #. 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 +#, no-c-format msgid "Run <command>debootstrap</command>" -msgstr "Misslyckades att köra förinställt kommando" +msgstr "Kör <command>debootstrap</command>" #. 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 @@ -1630,42 +1505,40 @@ msgid "" "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n" " /mnt/debinst http://http.us.debian.org/debian" msgstr "" +"# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n" +" /mnt/debinst http://http.us.debian.org/debian" #. Tag: title #: random-bits.xml:500 -#, fuzzy, no-c-format +#, no-c-format msgid "Configure The Base System" -msgstr "Konfigurera grundsystemet innan omstart" +msgstr "Konfigurera grundsystemet" #. 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 #: random-bits.xml:506 #, no-c-format msgid "# LANG= chroot /mnt/debinst /bin/bash" -msgstr "" +msgstr "# LANG= chroot /mnt/debinst /bin/bash" #. Tag: title #: random-bits.xml:511 -#, fuzzy, no-c-format +#, no-c-format msgid "Mount Partitions" -msgstr "Konfigurera och montera partitioner" +msgstr "Montera partitioner" #. Tag: para #: 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" @@ -1682,36 +1555,28 @@ 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 #: random-bits.xml:532 -#, fuzzy, no-c-format +#, no-c-format msgid "# mount -t proc proc /proc" -msgstr "Monteringspunkt:" +msgstr "# mount -t proc proc /proc" #. 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 #: random-bits.xml:540 -#, fuzzy, no-c-format +#, no-c-format msgid "# mount -t proc proc /mnt/debinst/proc" -msgstr "Misslyckades att montera /target/proc" +msgstr "# mount -t proc proc /mnt/debinst/proc" #. Tag: title #: random-bits.xml:546 @@ -1721,40 +1586,35 @@ msgstr "Konfigurera tangentbordet" #. Tag: para #: random-bits.xml:547 -#, fuzzy, no-c-format +#, no-c-format msgid "To configure your keyboard:" -msgstr "Det finns inget tangentbord att konfigurera" +msgstr "För att konfigurera ditt tangentbord:" #. Tag: screen #: random-bits.xml:551 #, no-c-format msgid "# dpkg-reconfigure console-data" -msgstr "" +msgstr "# dpkg-reconfigure console-data" #. 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 #: random-bits.xml:562 -#, fuzzy, no-c-format +#, no-c-format msgid "Configure Networking" -msgstr "Konfigurera tangentbordet" +msgstr "Konfigurera nätverket" #. Tag: para #: 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" @@ -1780,76 +1640,62 @@ 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 > /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 #: random-bits.xml:599 #, no-c-format msgid "Configure Timezone, Users, and APT" -msgstr "" +msgstr "Konfigurera tidszon, användare och APT" #. 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 #: random-bits.xml:605 #, no-c-format msgid "# /usr/sbin/base-config new" -msgstr "" +msgstr "# /usr/sbin/base-config new" #. Tag: title #: random-bits.xml:611 -#, fuzzy, no-c-format +#, no-c-format msgid "Configure Locales" -msgstr "Konfigurera tangentbordet" +msgstr "Konfigurera lokalanpassning" #. Tag: para #: 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 +#, no-c-format msgid "Install a Kernel" -msgstr "Kärna som ska installeras:" +msgstr "Installera en kärna" #. 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 "" @@ -1857,38 +1703,25 @@ msgstr "" #. Tag: screen #: random-bits.xml:638 #, no-c-format -msgid "" -"# apt-get install kernel-image-<replaceable>2.X.X-arch-etc</replaceable>" -msgstr "" +msgid "# apt-get install kernel-image-<replaceable>2.X.X-arch-etc</replaceable>" +msgstr "# apt-get install kernel-image-<replaceable>2.X.X-arch-etc</replaceable>" #. Tag: title #: random-bits.xml:644 -#, fuzzy, no-c-format +#, no-c-format msgid "Set up the Boot Loader" -msgstr "/boot - startladdarens statiska filer" +msgstr "" #. 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 @@ -1913,21 +1746,14 @@ 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" @@ -1936,8 +1762,7 @@ 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 @@ -1949,55 +1774,37 @@ 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 #: random-bits.xml:730 #, no-c-format msgid "Requirements" -msgstr "" +msgstr "Krav" #. 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 @@ -2009,32 +1816,25 @@ 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 +#, no-c-format msgid "Setting up source" -msgstr "Ställer in OpenFirmware" +msgstr "" #. 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 @@ -2046,64 +1846,52 @@ 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 "" #. Tag: title #: random-bits.xml:774 -#, fuzzy, no-c-format +#, no-c-format msgid "Installing target" -msgstr "M_Ã¥larbetslista:" +msgstr "" #. 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 #: random-bits.xml:787 -#, fuzzy, no-c-format +#, no-c-format msgid "Load installer components" -msgstr "Installationskomponenter som ska laddas:" +msgstr "Läs in Installationskomponenter" #. 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 +#, no-c-format msgid "Detect network hardware" -msgstr "Identifiera nätverksmaskinvara" +msgstr "Identifiera nätverkshÃ¥rdvara" #. 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 @@ -2115,18 +1903,13 @@ 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 @@ -2150,22 +1933,18 @@ 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 "" + |