diff options
| author | Daniel Nylander <debian@danielnylander.se> | 2006-03-11 09:52:49 +0000 |
|---|---|---|
| committer | Daniel Nylander <debian@danielnylander.se> | 2006-03-11 09:52:49 +0000 |
| commit | 2eb89b4ac77e607a6fd14b8f545c2a84d490867d (patch) | |
| tree | 01688880d27147f30c033d13df1dc82317aaf69d /po/sv | |
| parent | a21381fa35781905b80be6ce65a93a5fb51435aa (diff) | |
| download | installation-guide-2eb89b4ac77e607a6fd14b8f545c2a84d490867d.zip | |
more updates
Diffstat (limited to 'po/sv')
| -rw-r--r-- | po/sv/boot-installer.po | 2540 | ||||
| -rw-r--r-- | po/sv/preparing.po | 4 |
2 files changed, 524 insertions, 2020 deletions
diff --git a/po/sv/boot-installer.po b/po/sv/boot-installer.po index 6b189fa32..734d51897 100644 --- a/po/sv/boot-installer.po +++ b/po/sv/boot-installer.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: installation-guide 20051025 boot-installer\n" "POT-Creation-Date: 2006-03-08 01:02+0000\n" -"PO-Revision-Date: 2006-03-05 09:59+0100\n" +"PO-Revision-Date: 2006-03-11 10:54+0100\n" "Last-Translator: Daniel Nylander <po@danielnylander.se>\n" "Language-Team: Swedish <tp-sv@listor.tp-sv.se>\n" "MIME-Version: 1.0\n" @@ -34,133 +34,56 @@ msgstr "Konsollfirmware för Alpha" #. 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:" -msgstr "" -"Konsollfirmware lagras i ett flash-rom och startas när ett Alpha-system slås " -"på eller startas om. Det finns två olika konsollspecifikationer som används " -"på Alpha-system och därför finns två klasser av konsollfirmware tillgängliga:" +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 "Konsollfirmware lagras i ett flash-rom och startas när ett Alpha-system slås på eller startas om. Det finns två olika konsollspecifikationer som används på Alpha-system och därför finns två klasser av konsollfirmware tillgängliga:" #. 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." -msgstr "" -"<emphasis>SRM-konsoll</emphasis>, baserad på specifikationen Alpha Console " -"Subsystem, som tillhandahåller ett operativmiljö för operativsystemen " -"OpenVMS, Tru64 UNIX och Linux." +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 "<emphasis>SRM-konsoll</emphasis>, baserad på specifikationen Alpha Console Subsystem, som tillhandahåller ett operativmiljö för operativsystemen OpenVMS, Tru64 UNIX och Linux." #. 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." -msgstr "" -"<emphasis>ARC, AlphaBIOS eller ARCSBIOS-konsoll</emphasis>, baserad på " -"specifikationen Advanced RISC Computing (ARC), som tillhandahåller en " -"operativmiljö för 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 "<emphasis>ARC, AlphaBIOS eller ARCSBIOS-konsoll</emphasis>, baserad på specifikationen Advanced RISC Computing (ARC), som tillhandahåller en operativmiljö för Windows NT." #. 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." -msgstr "" -"Från användarens perspektiv är den mest viktiga skillnaden mellan SRM och " -"ARC den att valet av konsoll begränsar det möjliga diskpartitionsschemat för " -"hårddisken som du önskar starta upp från." +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 "Från användarens perspektiv är den mest viktiga skillnaden mellan SRM och ARC den att valet av konsoll begränsar det möjliga diskpartitionsschemat för hårddisken som du önskar starta upp från." #. 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." -msgstr "" -"ARC kräver att du använder en MS-DOS-partitionstabell (som skapas av " -"<command>cfdisk</command>) för uppstartsdisken. Därför är MS-DOS-" -"partitionstabeller det <quote>ursprungliga</quote> partitionsformatet vid " -"uppstarter från ARC. Faktum är att eftersom AlphaBIOS innehåller ett " -"diskpartitioneringsverktyg kanske du föredrar att partitionera dina diskar " -"från firmwaremenyerna före installation av 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 "ARC kräver att du använder en MS-DOS-partitionstabell (som skapas av <command>cfdisk</command>) för uppstartsdisken. Därför är MS-DOS-partitionstabeller det <quote>ursprungliga</quote> partitionsformatet vid uppstarter från ARC. Faktum är att eftersom AlphaBIOS innehåller ett diskpartitioneringsverktyg kanske du föredrar att partitionera dina diskar från firmwaremenyerna före installation av Linux." #. 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." -msgstr "" -"Motsatt är SRM <emphasis>inkompatibel</emphasis><footnote> <para> Specifikt " -"är formatet på uppstartssektorn som krävs av Console Subsystem Specification " -"i konflikt med placeringen av DOS-partitionstabellen. </para> </footnote> " -"med MS-DOS-partitionstabeller. Eftersom Tru64 Unix använder formatet för BSD-" -"disketiketter, är det här det ursprungliga (<quote>native</quote>) " -"partitionsformatet för SRM-installationer." +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 "Motsatt är SRM <emphasis>inkompatibel</emphasis><footnote> <para> Specifikt är formatet på uppstartssektorn som krävs av Console Subsystem Specification i konflikt med placeringen av DOS-partitionstabellen. </para> </footnote> med MS-DOS-partitionstabeller. Eftersom Tru64 Unix använder formatet för BSD-disketiketter, är det här det ursprungliga (<quote>native</quote>) partitionsformatet för SRM-installationer." #. 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." -msgstr "" -"GNU/Linux är det enda operativsystemet på Alpha som kan startas upp från " -"båda konsolltyperna, men &debian; &release; har endast stöd för uppstart på " -"SRM-baserade system. Om du har en Alpha som det inte finns någon SRM-version " -"tillgänglig för, om du vill använda dubbel-uppstart tillsammans med Windows " -"NT, eller om din uppstartsenhet kräver stöd för ARC-konsoll för initiering " -"av BIOS kommer du inte kunna använda installeraren för &debian; &release;. " -"Du kan fortfarande köra &debian; &release; på sådana system genom att " -"använda andra installationsmedia, till exempel kan du installera Debian " -"woody med MILO och uppgradera." +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 "GNU/Linux är det enda operativsystemet på Alpha som kan startas upp från båda konsolltyperna, men &debian; &release; har endast stöd för uppstart på SRM-baserade system. Om du har en Alpha som det inte finns någon SRM-version tillgänglig för, om du vill använda dubbel-uppstart tillsammans med Windows NT, eller om din uppstartsenhet kräver stöd för ARC-konsoll för initiering av BIOS kommer du inte kunna använda installeraren för &debian; &release;. Du kan fortfarande köra &debian; &release; på sådana system genom att använda andra installationsmedia, till exempel kan du installera Debian woody med MILO och uppgradera." #. 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." -msgstr "" -"Följande tabell sammanställer tillgängliga och systemtyper/" -"konsollkombinationer som stöds (se <xref linkend=\"alpha-cpus\"/> för namnen " -"på systemtyperna). Ordet <quote>ARC</quote> nedan below indikerar någon av " -"de ARC-godkända konsollerna." +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 "Följande tabell sammanställer tillgängliga och systemtyper/konsollkombinationer som stöds (se <xref linkend=\"alpha-cpus\"/> för namnen på systemtyperna). Ordet <quote>ARC</quote> nedan below indikerar någon av de ARC-godkända konsollerna." #. Tag: entry #: boot-installer.xml:107 @@ -181,11 +104,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" @@ -203,9 +135,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 "Endast SRM" @@ -325,7 +263,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 "Endast ARC" @@ -369,111 +309,65 @@ 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." -msgstr "" -"Följande paragrafer kommer från installationsmanualen för woody och " -"inkluderas här som referens: de kan vara användbara för någon vid ett senare " -"datum när Debian har stöd för MILO-baserade installationer igen." +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 "Följande paragrafer kommer från installationsmanualen för woody och inkluderas här som referens: de kan vara användbara för någon vid ett senare datum när Debian har stöd för MILO-baserade installationer igen." #. 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>." -msgstr "" -"Som på andra arkitekturer, bör du installera de senaste tillgängliga " -"revisionen av firmware<footnote> <para> Utom på Jensen, där Linux inte stöds " -"på firmware-versioner senareän 1.7 — se <ulink url=\"&url-jensen-howto;" -"\"></ulink> för mer information. </para> </footnote> före installation av " -"&debian;. För Alpha, uppdateringar av firmware kan hämtas från <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 "Som på andra arkitekturer, bör du installera de senaste tillgängliga revisionen av firmware<footnote> <para> Utom på Jensen, där Linux inte stöds på firmware-versioner senareän 1.7 — se <ulink url=\"&url-jensen-howto;\"></ulink> för mer information. </para> </footnote> före installation av &debian;. För Alpha, uppdateringar av firmware kan hämtas från <ulink url=\"&url-alpha-firmware;\">Alpha Firmware Updates</ulink>." #. Tag: title -#: boot-installer.xml:283 boot-installer.xml:1007 boot-installer.xml:1498 -#: boot-installer.xml:1993 boot-installer.xml:2075 boot-installer.xml:2164 -#: boot-installer.xml:2508 boot-installer.xml:2604 +#: boot-installer.xml:283 +#: boot-installer.xml:1007 +#: boot-installer.xml:1498 +#: boot-installer.xml:1993 +#: boot-installer.xml:2075 +#: boot-installer.xml:2164 +#: boot-installer.xml:2508 +#: boot-installer.xml:2604 #, no-c-format msgid "Booting with TFTP" msgstr "Uppstart via TFTP" @@ -482,62 +376,41 @@ msgstr "Uppstart via TFTP" #: 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 "" -"Sedan, för att starta upp från det första Ethernet-gränssnittet, kan du " -"skriva: <informalexample><screen>\n" +"Sedan, för att starta upp från det första Ethernet-gränssnittet, kan du skriva: <informalexample><screen>\n" ">>> boot ewa0 -flags \"\"\n" -"</screen></informalexample> Det här kommer att starta upp med de " -"kärnparametrar som är standard och som inkluderats i netboot-avbilden." +"</screen></informalexample> Det här kommer att starta upp med de kärnparametrar som är standard och som inkluderats i netboot-avbilden." #. 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"" -msgstr "" -">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -"console=ttyS0"" +msgid ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0"" +msgstr ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0"" #. Tag: title #: boot-installer.xml:328 @@ -551,13 +424,11 @@ msgstr "Uppstart från cd-rom med SRM-konsoll" 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 "" "Ange <informalexample><screen>\n" ">>> boot xxxx -flags 0\n" -"</screen></informalexample> där <replaceable>xxxx</replaceable> är din cd-" -"rom-enhet i SRM-notation." +"</screen></informalexample> där <replaceable>xxxx</replaceable> är din cd-rom-enhet i SRM-notation." #. Tag: title #: boot-installer.xml:341 @@ -568,14 +439,7 @@ msgstr "Uppstart från cd-rom med ARC eller AlphaBIOS-konsoll" #. 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 @@ -588,54 +452,30 @@ msgstr "Uppstart från startdisketter med SRM-konsoll" #: 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>." -msgstr "" -"Om du vill ange kärnparametrar vid uppstart med <command>aboot</command>, " -"använd följande kommando: <informalexample><screen>\n" -">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -"load_ramdisk=1 arguments\"\n" -"</screen></informalexample> (angivet på en rad), som ersätter, om " -"nödvändigt, det faktiska namnet på uppstartsenheten i SRM för " -"<filename>dva0</filename>, namnet för uppstartsenheten för Linux för " -"<filename>fd0</filename>, och de önskade kärnparametrarna för " -"<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 "" +"Om du vill ange kärnparametrar vid uppstart med <command>aboot</command>, använd följande kommando: <informalexample><screen>\n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 load_ramdisk=1 arguments\"\n" +"</screen></informalexample> (angivet på en rad), som ersätter, om nödvändigt, det faktiska namnet på uppstartsenheten i SRM för <filename>dva0</filename>, namnet för uppstartsenheten för Linux för <filename>fd0</filename>, och de önskade kärnparametrarna för <filename>arguments</filename>." #. 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\"/>." -msgstr "" -"Om du vill ange kärnparametrar vid uppstart med <command>MILO</command>, " -"måste du avbryta bootstrap när du kommit in i MILO. Se <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 "Om du vill ange kärnparametrar vid uppstart med <command>MILO</command>, måste du avbryta bootstrap när du kommit in i MILO. Se <xref linkend=\"booting-from-milo\"/>." #. Tag: title #: boot-installer.xml:398 @@ -646,10 +486,7 @@ msgstr "Uppstart från startdisketter med ARC eller AlphaBIOS-konsoll" #. 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 @@ -661,24 +498,16 @@ 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 @@ -688,105 +517,81 @@ msgid "Booting from TFTP" msgstr "Uppstart från TFTP" #. Tag: para -#: boot-installer.xml:441 boot-installer.xml:1013 boot-installer.xml:1516 -#: boot-installer.xml:1999 boot-installer.xml:2514 boot-installer.xml:2610 +#: boot-installer.xml:441 +#: boot-installer.xml:1013 +#: boot-installer.xml:1516 +#: boot-installer.xml:1999 +#: boot-installer.xml:2514 +#: boot-installer.xml:2610 #, 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)." -msgstr "" -"Uppstart från nätverket kräver att du har en nätverksanslutning och en TFTP-" -"server konfigurerad för uppstarter (DHCP, RARP eller BOOTP)." +msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)." +msgstr "Uppstart från nätverket kräver att du har en nätverksanslutning och en TFTP-server konfigurerad för uppstarter (DHCP, RARP eller BOOTP)." #. Tag: para -#: boot-installer.xml:446 boot-installer.xml:1018 boot-installer.xml:1521 -#: boot-installer.xml:2004 boot-installer.xml:2519 boot-installer.xml:2615 +#: boot-installer.xml:446 +#: boot-installer.xml:1018 +#: boot-installer.xml:1521 +#: boot-installer.xml:2004 +#: boot-installer.xml:2519 +#: boot-installer.xml:2615 #, no-c-format -msgid "" -"Older systems such as the 715 might require the use of an RBOOT server " -"instead of a BOOTP server." -msgstr "" +msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server." +msgstr "Äldre system såsom 715 kan kräva att en RBOOT-server används istället för en BOOTP-server." #. Tag: para -#: boot-installer.xml:451 boot-installer.xml:1023 boot-installer.xml:1526 -#: boot-installer.xml:2009 boot-installer.xml:2524 boot-installer.xml:2620 +#: boot-installer.xml:451 +#: boot-installer.xml:1023 +#: boot-installer.xml:1526 +#: boot-installer.xml:2009 +#: boot-installer.xml:2524 +#: boot-installer.xml:2620 #, no-c-format -msgid "" -"The installation method to support network booting is described in <xref " -"linkend=\"install-tftp\"/>." -msgstr "" -"Installationsmetoden som har stöd för nätverksuppstart finns beskriven i " -"<xref linkend=\"install-tftp\"/>." +msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>." +msgstr "Installationsmetoden som har stöd för nätverksuppstart finns beskriven i <xref linkend=\"install-tftp\"/>." #. Tag: title #: boot-installer.xml:459 -#, fuzzy, no-c-format +#, no-c-format msgid "Booting from TFTP on Netwinder" -msgstr "Uppstart från TFTP på NetWinder" +msgstr "Starta upp NetWinder via TFTP" #. Tag: para #: boot-installer.xml:460 #, no-c-format -msgid "" -"Netwinders have two network interfaces: A 10Mbps NE2000-compatible card " -"(which is generally referred to as <literal>eth0</literal>) and a 100Mbps " -"Tulip card. There may be problems loading the image via TFTP using the " -"100Mbps card so it is recommended that you use the 10Mbps interfaced (the " -"one labeled with <literal>10 Base-T</literal>)." +msgid "Netwinders have two network interfaces: A 10Mbps NE2000-compatible card (which is generally referred to as <literal>eth0</literal>) and a 100Mbps Tulip card. There may be problems loading the image via TFTP using the 100Mbps card so it is recommended that you use the 10Mbps interfaced (the one labeled with <literal>10 Base-T</literal>)." msgstr "" #. Tag: para #: boot-installer.xml:469 #, no-c-format -msgid "" -"You need NeTTrom 2.2.1 or later to boot the installation system, and version " -"2.3.3 is recommended. Unfortunately, firmware files are currently not " -"available for download because of license issues. If this situation changes, " -"you may find new images at <ulink url=\"http//www.netwinder.org/\"></ulink>." +msgid "You need NeTTrom 2.2.1 or later to boot the installation system, and version 2.3.3 is recommended. Unfortunately, firmware files are currently not available for download because of license issues. If this situation changes, you may find new images at <ulink url=\"http//www.netwinder.org/\"></ulink>." msgstr "" #. Tag: para #: boot-installer.xml:477 #, no-c-format msgid "" -"When you boot your Netwinder you have to interrupt the boot process during " -"the countdown. This allows you to set a number of firmware settings needed " -"in order to boot the installer. First of all, start by loading the default " -"settings: <informalexample><screen>\n" +"When you boot your Netwinder you have to interrupt the boot process during the countdown. This allows you to set a number of firmware settings needed in order to boot the installer. First of all, start by loading the default settings: <informalexample><screen>\n" " NeTTrom command-> load-defaults\n" -"</screen></informalexample> Furthermore, you must configure the network, " -"either with a static address: <informalexample><screen>\n" +"</screen></informalexample> Furthermore, you must configure the network, either with a static address: <informalexample><screen>\n" " NeTTrom command-> setenv netconfig_eth0 flash\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-> setenv netconfig_eth0 dhcp\n" -"</screen></informalexample> You may also need to configure the " -"<userinput>route1</userinput> settings if the TFTP server is not on the " -"local subnet. Following these settings, you have to specify the TFTP server " -"and the location of the image. You can then store your settings to flash. " -"<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. Following these settings, you have to specify the TFTP server and the location of the image. You can then store your settings to flash. <informalexample><screen>\n" " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" " NeTTrom command-> setenv kerntftpfile boot.img\n" " NeTTrom command-> save-all\n" -"</screen></informalexample> Now you have to tell the firmware that the TFTP " -"image should be booted: <informalexample><screen>\n" +"</screen></informalexample> Now you have to tell the firmware that the TFTP image should be booted: <informalexample><screen>\n" " NeTTrom command-> setenv kernconfig tftp\n" " NeTTrom command-> setenv rootdev /dev/ram\n" -"</screen></informalexample> If you use a serial console to install your " -"Netwinder, you need to add the following setting: <informalexample><screen>\n" -" NeTTrom command-> setenv cmdappend root=/dev/ram " -"console=ttyS0,115200\n" -"</screen></informalexample> Alternatively, for installations using a " -"keyboard and monitor you have to set: <informalexample><screen>\n" +"</screen></informalexample> If you use a serial console to install your Netwinder, you need to add the following setting: <informalexample><screen>\n" +" NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200\n" +"</screen></informalexample> Alternatively, for installations using a keyboard and monitor you have to set: <informalexample><screen>\n" " NeTTrom command-> setenv cmdappend root=/dev/ram\n" -"</screen></informalexample> You can use the <command>printenv</command> " -"command to review your environment settings. After you have verified that " -"the settings are correct, you can load the image: <informalexample><screen>\n" +"</screen></informalexample> You can use the <command>printenv</command> command to review your environment settings. After you have verified that the settings are correct, you can load the image: <informalexample><screen>\n" " NeTTrom command-> boot\n" -"</screen></informalexample> In case you run into any problems, a <ulink url=" -"\"http://www.netwinder.org/howto/Firmware-HOWTO.html\">detailed HOWTO</" -"ulink> is available." +"</screen></informalexample> In case you run into any problems, a <ulink url=\"http://www.netwinder.org/howto/Firmware-HOWTO.html\">detailed HOWTO</ulink> is available." msgstr "" #. Tag: title @@ -798,10 +603,8 @@ msgstr "Uppstart från TFTP på CATS" #. Tag: para #: boot-installer.xml:530 #, no-c-format -msgid "" -"On CATS machines, use <command>boot de0:</command> or similar at the Cyclone " -"prompt." -msgstr "" +msgid "On CATS machines, use <command>boot de0:</command> or similar at the Cyclone prompt." +msgstr "På CATS-maskiner, använd <command>boot de0:</command> eller liknande på Cyclone-prompten." #. Tag: title #: boot-installer.xml:540 @@ -810,182 +613,133 @@ msgid "Booting from CD-ROM" msgstr "Uppstart från cd-rom" #. Tag: para -#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1135 -#: boot-installer.xml:1956 boot-installer.xml:2296 boot-installer.xml:2650 +#: boot-installer.xml:546 +#: boot-installer.xml:716 +#: boot-installer.xml:1135 +#: boot-installer.xml:1956 +#: boot-installer.xml:2296 +#: boot-installer.xml:2650 #, 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." -msgstr "" -"Den enklaste vägen för de flesta personer är att använda en uppsättning " -"Debian-cd-skivor. Om du har en cd-uppsättning och om din maskin har stöd för " -"att starta upp direkt från cd, bra! Bara att <phrase arch=\"i386\"> " -"konfigurera ditt system för att starta upp från en cd som beskrivs i <xref " -"linkend=\"boot-dev-select\"/>, </phrase> mata in din cd, starta om och " -"fortsätt till nästa kapitel." +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 "Den enklaste vägen för de flesta personer är att använda en uppsättning Debian-cd-skivor. Om du har en cd-uppsättning och om din maskin har stöd för att starta upp direkt från cd, bra! Bara att <phrase arch=\"i386\"> konfigurera ditt system för att starta upp från en cd som beskrivs i <xref linkend=\"boot-dev-select\"/>, </phrase> mata in din cd, starta om och fortsätt till nästa kapitel." #. Tag: para -#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1146 -#: boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661 +#: boot-installer.xml:557 +#: boot-installer.xml:727 +#: boot-installer.xml:1146 +#: boot-installer.xml:1967 +#: boot-installer.xml:2307 +#: boot-installer.xml:2661 #, 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." -msgstr "" -"Notera att vissa cd-enheter kan kräver speciella drivrutiner och kan därför " -"vara otillgängliga i de tidiga stegen av installationen. Om det visar sig " -"att det vanliga sättet att starta upp från en cd inte fungerar på din " -"hårdvara, besök det här kapitlet igen och läs om alternativa kärnor och " -"installationsmetoder som kan fungera för dig." +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 "Notera att vissa cd-enheter kan kräver speciella drivrutiner och kan därför vara otillgängliga i de tidiga stegen av installationen. Om det visar sig att det vanliga sättet att starta upp från en cd inte fungerar på din hårdvara, besök det här kapitlet igen och läs om alternativa kärnor och installationsmetoder som kan fungera för dig." #. Tag: para -#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1154 -#: boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669 +#: boot-installer.xml:565 +#: boot-installer.xml:735 +#: boot-installer.xml:1154 +#: boot-installer.xml:1975 +#: boot-installer.xml:2315 +#: boot-installer.xml:2669 #, 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." -msgstr "" -"Även om du inte kan starta upp från cd-rom kan du antagligen installera " -"Debians systemkomponenter och de paket du vill från cd-rom. Starta helt " -"enkelt upp på ett annat media, såsom disketter. När det är dags att " -"installera operativsystemet, grundsystemet och eventuellt andra paket, peka " -"installationssystemet till cd-rom-enheten." +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 "Även om du inte kan starta upp från cd-rom kan du antagligen installera Debians systemkomponenter och de paket du vill från cd-rom. Starta helt enkelt upp på ett annat media, såsom disketter. När det är dags att installera operativsystemet, grundsystemet och eventuellt andra paket, peka installationssystemet till cd-rom-enheten." #. Tag: para -#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1162 -#: boot-installer.xml:1983 boot-installer.xml:2323 boot-installer.xml:2677 +#: boot-installer.xml:573 +#: boot-installer.xml:743 +#: boot-installer.xml:1162 +#: boot-installer.xml:1983 +#: boot-installer.xml:2323 +#: boot-installer.xml:2677 #, no-c-format -msgid "" -"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." -msgstr "" -"Om du har problem att starta upp, se <xref linkend=\"boot-troubleshooting\"/" -">." +msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." +msgstr "Om du har problem att starta upp, se <xref linkend=\"boot-troubleshooting\"/>." #. 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>" -msgstr "" +msgid "To boot a CD-ROM from the Cyclone console prompt, use the command <command>boot cd0:cats.bin</command>" +msgstr "För att starta upp en cd-rom från Cyclones konsollprompt, använd kommandot <command>boot cd0:cats.bin</command>" #. Tag: title #: boot-installer.xml:589 -#, fuzzy, no-c-format +#, no-c-format msgid "Booting from Firmware" -msgstr "Starta upp CHRP från OpenFirmware" +msgstr "Starta upp från firmware" #. Tag: para #: boot-installer.xml:595 #, no-c-format -msgid "" -"There is an increasing number of consumer devices that directly boot from a " -"flash chip on the device. The installer can be written to flash so it will " -"automatically start when you reboot your machines." -msgstr "" +msgid "There is an increasing number of consumer devices that directly boot from a flash chip on the device. The installer can be written to flash so it will automatically start when you reboot your machines." +msgstr "Det finns ett ökande antal konsumentenheter som startar upp direkt från ett flashchip på enheten. Installeraren kan skrivas till flash så att den automatiskt startar upp när du startar om dina maskiner." #. Tag: para #: boot-installer.xml:601 #, no-c-format -msgid "" -"In many cases, changing the firmware of an embedded device voids your " -"warranty. Sometimes you are also not able to recover your device if there " -"are problems during the flashing process. Therefore, please take care and " -"follow the steps precisely." -msgstr "" +msgid "In many cases, changing the firmware of an embedded device voids your warranty. Sometimes you are also not able to recover your device if there are problems during the flashing process. Therefore, please take care and follow the steps precisely." +msgstr "I många fall gäller inte din garanti när firmware i inbäddade enheter ändras. Ibland kan du inte heller återhämta din enhet om det inträffar problem under flashningsprocessen. Var därför försiktig och följ stegen noga." #. Tag: title #: boot-installer.xml:612 -#, fuzzy, no-c-format +#, no-c-format msgid "Booting the NSLU2" -msgstr "Uppstart med MILO" +msgstr "Starta upp NSLU2" #. Tag: para #: boot-installer.xml:613 #, no-c-format msgid "There are three ways how to put the installer firmware into flash:" -msgstr "" +msgstr "Det finns tre sätt hur man lägger in installerarens firmware i flash-minnet:" #. Tag: title #: boot-installer.xml:619 #, no-c-format msgid "Using the NSLU2 web interface" -msgstr "" +msgstr "Använda webbgränssnittet i NSLU2" #. Tag: para #: boot-installer.xml:620 #, no-c-format -msgid "" -"Go to the administration section and choose the menu item <literal>Upgrade</" -"literal>. You can then browse your disk for the installer image you have " -"previously downloaded. Then press the <literal>Start Upgrade</literal> " -"button, confirm, wait for a few minutes and confirm again. The system will " -"then boot straight into the installer." -msgstr "" +msgid "Go to the administration section and choose the menu item <literal>Upgrade</literal>. You can then browse your disk for the installer image you have previously downloaded. Then press the <literal>Start Upgrade</literal> button, confirm, wait for a few minutes and confirm again. The system will then boot straight into the installer." +msgstr "Gå till administrationssektionen och välj menyposten <literal>Upgrade</literal>. Du kan sedan bläddra på din disk efter installationsavbilden du tidigare hämtade ner. Tryck sedan på knappen <literal>Start Upgrade</literal>, bekräfta, vänta ett par minuter och bekräfta igen. Systemet kommer sedan att starta upp direkt in i installeraren." #. Tag: title #: boot-installer.xml:631 #, no-c-format msgid "Via the network using Linux/Unix" -msgstr "" +msgstr "Via nätverket med Linux/Unix" #. Tag: para #: boot-installer.xml:632 #, no-c-format msgid "" -"You can use <command>upslug2</command> from any Linux or Unix machine to " -"upgrade the machine via the network. This software is packaged for Debian. " -"First, you have to put your NSLU2 in upgrade mode: <orderedlist> " -"<listitem><para> Disconnect any disks and/or devices from the USB ports. </" -"para></listitem> <listitem><para> Power off the NSLU2 </para></listitem> " -"<listitem><para> Press and hold the reset button (accessible through the " -"small hole on the back just above the power input). </para></listitem> " -"<listitem><para> Press and release the power button to power on the NSLU2. </" -"para></listitem> <listitem><para> Wait for 10 seconds watching the ready/" -"status LED. After 10 seconds it will change from amber to red. Immediately " -"release the reset button. </para></listitem> <listitem><para> The NSLU2 " -"ready/status LED will flash alternately red/green (there is a 1 second delay " -"before the first green). The NSLU2 is now in upgrade mode. </para></" -"listitem> </orderedlist> See the <ulink url=\"http://www.nslu2-linux.org/" -"wiki/OpenSlug/UsingTheBinary\">NSLU2-Linux pages</ulink> if you have " -"problems with this. Once your NSLU2 is in upgrade mode, you can flash the " -"new image: <informalexample><screen>\n" +"You can use <command>upslug2</command> from any Linux or Unix machine to upgrade the machine via the network. This software is packaged for Debian. First, you have to put your NSLU2 in upgrade mode: <orderedlist> <listitem><para> Disconnect any disks and/or devices from the USB ports. </para></listitem> <listitem><para> Power off the NSLU2 </para></listitem> <listitem><para> Press and hold the reset button (accessible through the small hole on the back just above the power input). </para></listitem> <listitem><para> Press and release the power button to power on the NSLU2. </para></listitem> <listitem><para> Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset button. </para></listitem> <listitem><para> The NSLU2 ready/status LED will flash alternately red/green (there is a 1 second delay before the first green). The NSLU2 is now in upgrade mode. </para></listitem> </orderedlist> See the <ulink url=\"http://www.nslu2-linux.org/wiki/OpenSlug/UsingTheBinary\">NSLU2-Linux pages</ulink> if you have problems with this. Once your NSLU2 is in upgrade mode, you can flash the new image: <informalexample><screen>\n" "sudo upslug2 -i di-nslu2.bin\n" -"</screen></informalexample> Note that the tool also shows the MAC address of " -"your NSLU2, which may come in handy to configure your DHCP server. After the " -"whole image has been written and verified, the system will automatically " -"reboot. Make sure you connect your USB disk again now, otherwise the " -"installer won't be able to find it." +"</screen></informalexample> Note that the tool also shows the MAC address of your NSLU2, which may come in handy to configure your DHCP server. After the whole image has been written and verified, the system will automatically reboot. Make sure you connect your USB disk again now, otherwise the installer won't be able to find it." msgstr "" +"Du kan använda <command>upslug2</command> från valfri Linux- eller Unix-maskin för att uppgradera maskinen via nätverket. Den här programvaran är paketerad för Debian. Först måste du försätta din NSLU2 i uppgraderingsläge: <orderedlist> <listitem><para> Koppla loss alla diskar och/eller enheter från USB-portarna. </para></listitem> <listitem><para> Stäng av din NSLU2 </para></listitem> <listitem><para> Tryck och håll nere omstartsknappen (tillgänglig genom ett litet hål på baksidan ovanför strömanslutningen). </para></listitem> <listitem><para> Tryck och släpp strömknappen för att starta upp NSLU2. </para></listitem> <listitem><para> Vänta 10 sekunder och se på ready-/status-lampan. Efter 10 sekunder kommer en att ändra färg från orange till röd. Släpp omedelbart omstartsknappen. </para></listitem> <listitem><para> Lampan på NSLU2 för ready/status kommer att blinka rött och grönt (det är en sekunds fördröjning före den första gröna). NSLU2 är nu i uppgraderingsläge. </para></listitem> </orderedlist> Se <ulink url=\"http://www.nslu2-linux.org/wiki/OpenSlug/UsingTheBinary\">NSLU2-Linux-sidor</ulink> om du har problem med det här. När din NSLU2 är i uppgraderingsläge, kan du lägga in den nya flashavbilden: <informalexample><screen>\n" +"sudo upslug2 -i di-nslu2.bin\n" +"</screen></informalexample> Notera att verktyget även visar MAC-adressen på din NSLU2, vilket kan vara användbart för att konfigurera din DHCP-server. Efter att hela avbilden har skrivits och validerats kommer systemet att automatiskt starta om. Se till att du ansluter din USB-disk igen nu, annars kommer installeraren inte att kunna hitta den." #. Tag: title #: boot-installer.xml:693 #, no-c-format msgid "Via the network using Windows" -msgstr "" +msgstr "Via nätverket med Windows" #. Tag: para #: boot-installer.xml:694 #, no-c-format -msgid "" -"There is <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmware/" -"all_router_utility.zip\">a tool</ulink> for Windows to upgrade the firmware " -"via the network." -msgstr "" +msgid "There is <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmware/all_router_utility.zip\">a tool</ulink> for Windows to upgrade the firmware via the network." +msgstr "Det finns <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmware/all_router_utility.zip\">ett verktyg</ulink> för Windows för att uppgradera firmware via nätverket." #. Tag: title -#: boot-installer.xml:710 boot-installer.xml:1129 boot-installer.xml:1944 -#: boot-installer.xml:2290 boot-installer.xml:2644 +#: boot-installer.xml:710 +#: boot-installer.xml:1129 +#: boot-installer.xml:1944 +#: boot-installer.xml:2290 +#: boot-installer.xml:2644 #, no-c-format msgid "Booting from a CD-ROM" msgstr "Uppstart från en cd-rom" @@ -993,73 +747,32 @@ msgstr "Uppstart från en cd-rom" #. Tag: title #: boot-installer.xml:848 #, no-c-format -msgid "" -"Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" -msgstr "" -"Uppstart från Linux med <command>LILO</command> eller <command>GRUB</command>" +msgid "Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" +msgstr "Uppstart från Linux med <command>LILO</command> eller <command>GRUB</command>" #. Tag: para #: boot-installer.xml:851 #, 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\"/>." -msgstr "" -"För att starta upp installeraren från hårddisk måste du första hämta och " -"placera de nödvändiga filerna som beskrivs i <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 "För att starta upp installeraren från hårddisk måste du första hämta och placera de nödvändiga filerna som beskrivs i <xref linkend=\"boot-drive-files\"/>." #. Tag: para #: boot-installer.xml:856 #, 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." -msgstr "" -"Om du bara tänkte använda hårddisken för att starta upp och sedan hämta allt " -"över nätverket, bör du hämta filen <filename>netboot/debian-installer/i386/" -"initrd.gz</filename> och dess korresponderande kärna. Den låter dig " -"partionera om hårddisken från vilken du startar upp installeraren, fastän du " -"bör göra det med försiktighet." +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 "Om du bara tänkte använda hårddisken för att starta upp och sedan hämta allt över nätverket, bör du hämta filen <filename>netboot/debian-installer/i386/initrd.gz</filename> och dess korresponderande kärna. Den låter dig partionera om hårddisken från vilken du startar upp installeraren, fastän du bör göra det med försiktighet." #. Tag: para #: boot-installer.xml:864 #, 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." -msgstr "" -"Alternativt, om du tänker behålla en existerande partition på hårddisken i " -"oförändrat skick under installationen, kan du hämta filen <filename>hd-media/" -"initrd.gz</filename> och dess kärna, såväl som en kopia av en cd-avbild till " -"enheten (se till att filens namn slutar på <literal>.iso</literal>). " -"Installeraren kan sedan starta upp från enheten och installera från cd-" -"avbilden, utan behov av nätverk." +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 "Alternativt, om du tänker behålla en existerande partition på hårddisken i oförändrat skick under installationen, kan du hämta filen <filename>hd-media/initrd.gz</filename> och dess kärna, såväl som en kopia av en cd-avbild till enheten (se till att filens namn slutar på <literal>.iso</literal>). Installeraren kan sedan starta upp från enheten och installera från cd-avbilden, utan behov av nätverk." #. Tag: para #: boot-installer.xml:873 #, 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:" -msgstr "" -"För <command>LILO</command>, behöver du konfigurera två viktiga saker i " -"<filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> för att " -"läsa in <filename>initrd.gz</filename> installeraren vid uppstart; </para></" -"listitem> <listitem><para> få kärnan <filename>vmlinuz</filename> att " -"använda en RAM-disk som sin rotpartition. </para></listitem> </itemizedlist> " -"Här är ett exempel på en <filename>/etc/lilo.conf</filename>:" +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 "För <command>LILO</command>, behöver du konfigurera två viktiga saker i <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> för att läsa in <filename>initrd.gz</filename> installeraren vid uppstart; </para></listitem> <listitem><para> få kärnan <filename>vmlinuz</filename> att använda en RAM-disk som sin rotpartition. </para></listitem> </itemizedlist> Här är ett exempel på en <filename>/etc/lilo.conf</filename>:" #. Tag: screen #: boot-installer.xml:894 @@ -1080,36 +793,20 @@ msgstr "" #. Tag: para #: boot-installer.xml:894 #, 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." -msgstr "" -"För fler detaljer, referera till manualsidorna " -"<citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</" -"manvolnum></citerefentry> och <citerefentry><refentrytitle>lilo.conf</" -"refentrytitle> <manvolnum>5</manvolnum></citerefentry>. Kör nu " -"<userinput>lilo</userinput> och starta om." +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 "För fler detaljer, referera till manualsidorna <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> och <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry>. Kör nu <userinput>lilo</userinput> och starta om." #. Tag: para #: boot-installer.xml:903 #, 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." msgstr "" -"Proceduren för <command>GRUB</command> är ganska lik. Leta upp din " -"<filename>menu.lst</filename> i katalogen <filename>/boot/grub/</filename> " -"(ibland finns den i <filename>/boot/boot/grub/</filename>), lägg till " -"följande rader: <informalexample><screen>\n" +"Proceduren för <command>GRUB</command> är ganska lik. Leta upp din <filename>menu.lst</filename> i katalogen <filename>/boot/grub/</filename> (ibland finns den i <filename>/boot/boot/grub/</filename>), lägg till följande rader: <informalexample><screen>\n" "title Ny installation\n" "kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n" "initrd (hd0,0)/boot/newinstall/initrd.gz\n" @@ -1118,14 +815,8 @@ msgstr "" #. Tag: para #: boot-installer.xml:914 #, 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>." -msgstr "" -"Notera att värden för <userinput>ramdisk_size</userinput> kan behöva " -"justeras efter initrd-avbildens storlek. Från och med nu bör det inte vara " -"några skillnader mellan <command>GRUB</command> och <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 "Notera att värden för <userinput>ramdisk_size</userinput> kan behöva justeras efter initrd-avbildens storlek. Från och med nu bör det inte vara några skillnader mellan <command>GRUB</command> och <command>LILO</command>." #. Tag: title #: boot-installer.xml:925 @@ -1136,139 +827,66 @@ msgstr "Uppstart från USB-minne" #. Tag: para #: boot-installer.xml:926 #, 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;." -msgstr "" -"Låt oss anta att du har förberett allt från <xref linkend=\"boot-dev-select" -"\"/> och <xref linkend=\"boot-usb-files\"/>. Anslut ditt USB-minne i någon " -"ledig USB-kontakt och starta om datorn. Systemet bör starta upp och du bör " -"se prompten <prompt>boot:</prompt>. Här kan du ange ytterligare " -"uppstartsargument eller bara trycka &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 "Låt oss anta att du har förberett allt från <xref linkend=\"boot-dev-select\"/> och <xref linkend=\"boot-usb-files\"/>. Anslut ditt USB-minne i någon ledig USB-kontakt och starta om datorn. Systemet bör starta upp och du bör se prompten <prompt>boot:</prompt>. Här kan du ange ytterligare uppstartsargument eller bara trycka &enterkey;." #. Tag: para #: boot-installer.xml:935 #, 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." -msgstr "" -"I fall att din dator inte har stöd för uppstart från USB-minnesenheter kan " -"du fortfarande använda en enda diskett för att göra den initiala uppstarten " -"och sedan byta till USB. Starta upp ditt system som beskrivs i <xref linkend=" -"\"floppy-boot\"/>; kärnan på startdisketten ska automatiskt identifiera ditt " -"USB-minne. När den frågar efter rotdisketten, tryck bara &enterkey;. Du bör " -"nu se &d-i; starta." +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 "I fall att din dator inte har stöd för uppstart från USB-minnesenheter kan du fortfarande använda en enda diskett för att göra den initiala uppstarten och sedan byta till USB. Starta upp ditt system som beskrivs i <xref linkend=\"floppy-boot\"/>; kärnan på startdisketten ska automatiskt identifiera ditt USB-minne. När den frågar efter rotdisketten, tryck bara &enterkey;. Du bör nu se &d-i; starta." #. Tag: title -#: boot-installer.xml:948 boot-installer.xml:2056 boot-installer.xml:2550 +#: boot-installer.xml:948 +#: boot-installer.xml:2056 +#: boot-installer.xml:2550 #: boot-installer.xml:2698 #, no-c-format msgid "Booting from Floppies" msgstr "Uppstart från startdisketter" #. Tag: para -#: boot-installer.xml:949 boot-installer.xml:2558 +#: boot-installer.xml:949 +#: boot-installer.xml:2558 #, 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\"/>." -msgstr "" -"Du ska redan ha hämtat diskettavbilderna du behövde och skapat disketterna " -"från avbilderna i <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 "Du ska redan ha hämtat diskettavbilderna du behövde och skapat disketterna från avbilderna i <xref linkend=\"create-floppy\"/>." #. Tag: para #: boot-installer.xml:956 #, 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." -msgstr "" -"För att starta upp från installerarens startdiskett, placera den i primära " -"diskettenheten, stäng ner systemet som vanligt och starta upp det igen." +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 "För att starta upp från installerarens startdiskett, placera den i primära diskettenheten, stäng ner systemet som vanligt och starta upp det igen." #. Tag: para #: boot-installer.xml:962 #, 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." -msgstr "" -"För att installera från en LS-120-enhet (ATAPI-versionen) med en uppsättning " -"disketter, behöver du ange den virtuella platsen för diskettenheten. Det här " -"gör man med uppstartargumentet <emphasis>root=</emphasis>, som anger enheten " -"som drivrutinen kan mappa enheten till. Till exempel, om din LS-120-enhet är " -"ansluten som första IDE-enhet (master) på andra kabeln, anger du " -"<userinput>linux root=/dev/hdc</userinput> vid uppstartsprompten. " -"Installation från LS-120 stöds endast av kärnor i 2.4-serien och senare." +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 "För att installera från en LS-120-enhet (ATAPI-versionen) med en uppsättning disketter, behöver du ange den virtuella platsen för diskettenheten. Det här gör man med uppstartargumentet <emphasis>root=</emphasis>, som anger enheten som drivrutinen kan mappa enheten till. Till exempel, om din LS-120-enhet är ansluten som första IDE-enhet (master) på andra kabeln, anger du <userinput>linux root=/dev/hdc</userinput> vid uppstartsprompten. Installation från LS-120 stöds endast av kärnor i 2.4-serien och senare." #. Tag: para #: boot-installer.xml:973 #, 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." -msgstr "" -"Notera att på vissa maskiner, <keycombo><keycap>Control</keycap> " -"<keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> återställer inte " -"korrekt maskinen, så en <quote>hård</quote> omstart rekommenderas. Om du " -"installerar från ett existerande operativsystem (exempelvis från en DOS-" -"burk) har du inget val. Om inte, vänligen gör en hård omstart vid uppstart." +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 "Notera att på vissa maskiner, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> återställer inte korrekt maskinen, så en <quote>hård</quote> omstart rekommenderas. Om du installerar från ett existerande operativsystem (exempelvis från en DOS-burk) har du inget val. Om inte, vänligen gör en hård omstart vid uppstart." #. Tag: para #: boot-installer.xml:982 #, 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." -msgstr "" -"Disketten kommer att läsas från och du bör sedan se en skärm som " -"introducerar startdisketten och slutar med prompten <prompt>boot:</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 "Disketten kommer att läsas från och du bör sedan se en skärm som introducerar startdisketten och slutar med prompten <prompt>boot:</prompt>." #. Tag: para #: boot-installer.xml:988 #, 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\"/>." -msgstr "" -"När du trycker &enterkey;, bör du se meddelandet <computeroutput>Loading...</" -"computeroutput>, följt av <computeroutput>Uncompressing Linux...</" -"computeroutput>, och sedan en skärm full av information om hårdvaran i ditt " -"system. Mer information angående den här fasen i uppstartsprocessen kan " -"hittas under i <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 "När du trycker &enterkey;, bör du se meddelandet <computeroutput>Loading...</computeroutput>, följt av <computeroutput>Uncompressing Linux...</computeroutput>, och sedan en skärm full av information om hårdvaran i ditt system. Mer information angående den här fasen i uppstartsprocessen kan hittas under i <xref linkend=\"kernel-msgs\"/>." #. Tag: para #: boot-installer.xml:997 #, 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." -msgstr "" -"Efter uppstart från startdisketten kommer rotdisketten att efterfrågas. Mata " -"in rotdisketten och tryck &enterkey;, och dess innehåll kommer att läsas in " -"i minnet. Installeringsprogrammet <command>debian-installer</command> " -"startas automatiskt." +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 "Efter uppstart från startdisketten kommer rotdisketten att efterfrågas. Mata in rotdisketten och tryck &enterkey;, och dess innehåll kommer att läsas in i minnet. Installeringsprogrammet <command>debian-installer</command> startas automatiskt." #. Tag: para #: boot-installer.xml:1031 @@ -1285,16 +903,8 @@ msgstr "Nätverkskort eller moderkort med stöd för PXE" #. Tag: para #: boot-installer.xml:1038 #, 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." -msgstr "" -"Det kan vara så att ditt nätverkskort eller moderkort erbjuder " -"funktionalitet för uppstart via PXE. Det är en åter-implementation av TFTP-" -"uppstart från <trademark class=\"trade\">Intel</trademark>. Om så är fallet " -"kan du konfigurera ditt BIOS att starta upp från nätverket." +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 "Det kan vara så att ditt nätverkskort eller moderkort erbjuder funktionalitet för uppstart via PXE. Det är en åter-implementation av TFTP-uppstart från <trademark class=\"trade\">Intel</trademark>. Om så är fallet kan du konfigurera ditt BIOS att starta upp från nätverket." #. Tag: title #: boot-installer.xml:1049 @@ -1305,22 +915,14 @@ msgstr "Nätverkskort med Network BootROM" #. Tag: para #: boot-installer.xml:1050 #, no-c-format -msgid "" -"It could be that your Network Interface Card provides TFTP boot " -"functionality." -msgstr "" -"Det kan vara så att ditt nätverkskort erbjuder funktionalitet för att starta " -"upp via TFTP." +msgid "It could be that your Network Interface Card provides TFTP boot functionality." +msgstr "Det kan vara så att ditt nätverkskort erbjuder funktionalitet för att starta upp via TFTP." #. Tag: para #: boot-installer.xml:1055 #, no-c-format -msgid "" -"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. " -"Please refer to this document." -msgstr "" -"Låt oss (<email>&email-debian-boot-list;</email>) veta hur du gjorde det. " -"Vänligen referera till det här dokumentet." +msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document." +msgstr "Låt oss (<email>&email-debian-boot-list;</email>) veta hur du gjorde det. Vänligen referera till det här dokumentet." #. Tag: title #: boot-installer.xml:1063 @@ -1331,12 +933,8 @@ msgstr "Etherboot" #. Tag: para #: boot-installer.xml:1064 #, no-c-format -msgid "" -"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> " -"provides bootdiskettes and even bootroms that do a TFTPboot." -msgstr "" -"<ulink url=\"http://www.etherboot.org\">Etherboot-projektet</ulink> erbjuder " -"startdisketter och även ROM-filer som kan göra uppstarter via TFTP." +msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot." +msgstr "<ulink url=\"http://www.etherboot.org\">Etherboot-projektet</ulink> erbjuder startdisketter och även ROM-filer som kan göra uppstarter via TFTP." #. Tag: title #: boot-installer.xml:1073 @@ -1348,75 +946,25 @@ msgstr "Uppstartsprompten" #: boot-installer.xml:1074 #, 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 "" -"När installeraren startar upp bör du presenteras med en snäll grafisk skärm " -"som visar Debians logotyp och en uppstartsprompt: <informalexample><screen>\n" +"När installeraren startar upp bör du presenteras med en snäll grafisk skärm som visar Debians logotyp och en uppstartsprompt: <informalexample><screen>\n" "Press F1 for help, or ENTER to boot:\n" -"</screen></informalexample> Vid uppstartsprompten kan du antingen bara " -"trycka &enterkey; för att starta upp installeraren med standardalternativ " -"eller ange en specifik uppstartsmetod och, valfritt, uppstartsparametrar." +"</screen></informalexample> Vid uppstartsprompten kan du antingen bara trycka &enterkey; för att starta upp installeraren med standardalternativ eller ange en specifik uppstartsmetod och, valfritt, uppstartsparametrar." #. Tag: para #: boot-installer.xml:1086 #, 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 <keycap>F8</" -"keycap>. 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 "" -"Information om tillgängliga uppstartsmetoder och om uppstartsparametrar som " -"kan vara användbara kan hittas genom att trycka <keycap>F2</keycap> till " -"<keycap>F8</keycap>. Om du lägger till några parametrar till kommandoraden, " -"tänk på att ange uppstartsmetoden (standard är <userinput>linux</userinput>) " -"och ett blanksteg före den första parametern (exempelvis <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 <keycap>F8</keycap>. 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 "Information om tillgängliga uppstartsmetoder och om uppstartsparametrar som kan vara användbara kan hittas genom att trycka <keycap>F2</keycap> till <keycap>F8</keycap>. Om du lägger till några parametrar till kommandoraden, tänk på att ange uppstartsmetoden (standard är <userinput>linux</userinput>) och ett blanksteg före den första parametern (exempelvis <userinput>linux debconf/priority=medium</userinput>)." #. Tag: para #: boot-installer.xml:1095 #, 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." -msgstr "" -"Om du installerar systemet via en fjärrhanteringsenhet som tillhandahåller " -"ett textgränssnitt till VGA-konsollen, kan du inte se den initiala grafiska " -"uppstartsskärmen under uppstarten av installeraren; du kanske inte heller " -"kan se uppstartsprompten. Exempel på de här enheterna inkluderar " -"textkonsollen för Compaqs <quote>integrated Lights Out</quote> (iLO) och HP:" -"s <quote>Integrated Remote Assistant</quote> (IRA). Du kan helt blint trycka " -"F1<footnote> <para> I vissa fall kräver de här enheterna en speciell " -"tangentsekvens för att göra den här tangenttryckningen, till exempel " -"använder IRA <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>," -" <keycap>1</keycap>. </para> </footnote> för att komma förbi den här " -"skärmen och visa hjälptexten. När du har kommit förbi uppstartsskärmen och " -"är vid hjälptexten kommer dina tangenttryckning att ekas vid prompten som " -"förväntat. För att förhindra att installeraren använder grafikkortet i " -"resten av installationen, kan du också lägga till <userinput>debian-" -"installer/framebuffer=false</userinput> till uppstartsprompten, som beskrivs " -"i hjälptexten." +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 "Om du installerar systemet via en fjärrhanteringsenhet som tillhandahåller ett textgränssnitt till VGA-konsollen, kan du inte se den initiala grafiska uppstartsskärmen under uppstarten av installeraren; du kanske inte heller kan se uppstartsprompten. Exempel på de här enheterna inkluderar textkonsollen för Compaqs <quote>integrated Lights Out</quote> (iLO) och HP:s <quote>Integrated Remote Assistant</quote> (IRA). Du kan helt blint trycka F1<footnote> <para> I vissa fall kräver de här enheterna en speciell tangentsekvens för att göra den här tangenttryckningen, till exempel använder IRA <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</keycap>. </para> </footnote> för att komma förbi den här skärmen och visa hjälptexten. När du har kommit förbi uppstartsskärmen och är vid hjälptexten kommer dina tangenttryckning att ekas vid prompten som förväntat. För att förhindra att installeraren använder grafikkortet i resten av installationen, kan du också lägga till <userinput>debian-installer/framebuffer=false</userinput> till uppstartsprompten, som beskrivs i hjälptexten." #. Tag: title #: boot-installer.xml:1170 @@ -1427,72 +975,31 @@ msgstr "Cd-innehåll" #. Tag: para #: boot-installer.xml:1172 #, 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." -msgstr "" +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 "Det finns tre enkla variationer av Debians installationsskivor. Cd-skivan <emphasis>Visitkort</emphasis> innehåller en minimal installation som passar på ett minimalt cd-media. Den kräver en nätverksanslutning för att installera resten av grundinstallationen och skapa ett användbart system. Cd-skivan <emphasis>Nätinstallation</emphasis> har alla paket för en grundinstallation men kräver en nätverksanslutningen till en Debian-spegel för att installera de extra paket som man vill ha för ett komplett system. Uppsättningen av Debian-cd-skivor kan installera ett komplett system från en mängd olika paket utan behov av tillgång till nätverket." #. Tag: para #: boot-installer.xml:1188 #, 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:1204 #, 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:1213 #, 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:1225 #, 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 @@ -1504,14 +1011,7 @@ msgstr "VIKTIGT" #. Tag: para #: boot-installer.xml:1245 #, 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 @@ -1523,62 +1023,37 @@ msgstr "Alternativ 1: Starta upp från Boot Option Maintenance Menu" #. Tag: para #: boot-installer.xml:1264 #, 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:1270 #, 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:1276 #, 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:1287 #, 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:1298 #, 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:1310 #, 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 @@ -1590,80 +1065,43 @@ msgstr "Alternativ 2: Starta upp från EFI-skalet" #. Tag: para #: boot-installer.xml:1321 #, 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:1332 #, 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." -msgstr "" -"Mata in cd-skivan i dvd/cd-enheten och starta om maskinen. Firmware kommer " -"att visa EFI Boot Manager-sidan och menyn efter den färdigställer " -"systeminitieringen." +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 "Mata in cd-skivan i dvd/cd-enheten och starta om maskinen. Firmware kommer att visa EFI Boot Manager-sidan och menyn efter den färdigställer systeminitieringen." #. Tag: para #: boot-installer.xml:1338 #, 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:1352 #, 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>." -msgstr "" -"Undersök utskriften från skalet som letar efter cd-rom-enheten. Det är " -"antagligen enheten <filename>fs0:</filename> även om andra enheter med " -"startbara partitioner också kommer att visas som <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 "Undersök utskriften från skalet som letar efter cd-rom-enheten. Det är antagligen enheten <filename>fs0:</filename> även om andra enheter med startbara partitioner också kommer att visas som <filename>fs<replaceable>n</replaceable></filename>." #. Tag: para #: boot-installer.xml:1359 #, 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:1366 #, 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:1373 #, 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 @@ -1675,61 +1113,32 @@ msgstr "Installation med en seriellkonsoll" #. Tag: para #: boot-installer.xml:1389 #, 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:1400 #, 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:1407 #, 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:1418 #, 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:1427 #, 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." -msgstr "" -"Om du väljer fel konsolltyp kommer du kunna välja kärna och ange parametrar " -"men både skärmen och din inmatning kommer att försvinna så snart som kärnan " -"startat och kräver att du startar om före du kan påbörjar installationen." +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 "Om du väljer fel konsolltyp kommer du kunna välja kärna och ange parametrar men både skärmen och din inmatning kommer att försvinna så snart som kärnan startat och kräver att du startar om före du kan påbörjar installationen." #. Tag: title #: boot-installer.xml:1436 @@ -1740,92 +1149,49 @@ msgstr "Välj uppstartskärna och inställningar" #. Tag: para #: boot-installer.xml:1438 #, 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:1450 #, 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:1468 #, no-c-format -msgid "" -"Select the kernel version and installation mode most appropriate to your " -"needs with the arrow keys." -msgstr "" -"Välj kärnversionen och installationsläget som är mest lämplig för dina behov " -"med piltangenterna." +msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys." +msgstr "Välj kärnversionen och installationsläget som är mest lämplig för dina behov med piltangenterna." #. Tag: para #: boot-installer.xml:1473 #, 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:1480 #, 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." -msgstr "" -"Tryck <command>ENTER</command>. Det kommer att läsa in och starta kärnan. " -"Kärnan kommer att visa dess vanliga initieringsmeddelanden följt av första " -"skärmen av 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 "Tryck <command>ENTER</command>. Det kommer att läsa in och starta kärnan. Kärnan kommer att visa dess vanliga initieringsmeddelanden följt av första skärmen av Debian Installer." #. Tag: para #: boot-installer.xml:1489 #, 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." -msgstr "" -"Fortsätt till nästa kapitel för att fortsätta installationen där du kommer " -"att ställa in språkanpassning, nätverk och diskpartitioner." +msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions." +msgstr "Fortsätt till nästa kapitel för att fortsätta installationen där du kommer att ställa in språkanpassning, nätverk och diskpartitioner." #. Tag: para #: boot-installer.xml:1500 #, 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:1534 #, 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 @@ -1838,35 +1204,26 @@ msgstr "Konfiguration av servern" #: boot-installer.xml:1546 #, 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 "" -"En lämplig TFTP-post för att starta upp via nätverket på ett ia64-system ser " -"ut ungefär som den här: <informalexample><screen>\n" +"En lämplig TFTP-post för att starta upp via nätverket på ett ia64-system ser ut ungefär som den här: <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> Notera att målet är att få <command>elilo.efi</" -"command> att köra på klienten." +"</screen></informalexample> Notera att målet är att få <command>elilo.efi</command> att köra på klienten." #. Tag: para #: boot-installer.xml:1556 #, 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 @@ -1890,15 +1247,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:1566 #, 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 @@ -1910,41 +1259,20 @@ msgstr "Konfiguration av klienten" #. Tag: para #: boot-installer.xml:1584 #, 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:1616 #, 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:1625 #, 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." -msgstr "" -"Fortsätt till nästa kapitel för att fortsätta installationen där du kommer " -"att ställa in språkanpassning, nätverk och diskpartitionerna." +msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and the disk partitions." +msgstr "Fortsätt till nästa kapitel för att fortsätta installationen där du kommer att ställa in språkanpassning, nätverk och diskpartitionerna." #. Tag: title #: boot-installer.xml:1638 @@ -1955,43 +1283,26 @@ msgstr "Välja en installationsmetod" #. Tag: para #: boot-installer.xml:1640 #, 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:1648 #, no-c-format -msgid "" -"If you are using a 2.2.x linux kernel, then you need to use the " -"&ramdisksize; kernel parameter." -msgstr "" -"Om du använder en Linux-kärna med version 2.2.x, behöver du använda " -"kärnparametern &ramdisksize;." +msgid "If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; kernel parameter." +msgstr "Om du använder en Linux-kärna med version 2.2.x, behöver du använda kärnparametern &ramdisksize;." #. Tag: para #: boot-installer.xml:1653 #, no-c-format -msgid "" -"Make sure <userinput>root=/dev/ram</userinput> is one of your kernel " -"parameters." -msgstr "" -"Se till att <userinput>root=/dev/ram</userinput> är en av dina " -"kärnparametrar." +msgid "Make sure <userinput>root=/dev/ram</userinput> is one of your kernel parameters." +msgstr "Se till att <userinput>root=/dev/ram</userinput> är en av dina kärnparametrar." #. Tag: para #: boot-installer.xml:1658 #, no-c-format -msgid "" -"If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's " -"&arch-title; debian-installer FAQ</ulink>." -msgstr "" -"Om du får problem, ta en titt i <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 "Om du får problem, ta en titt i <ulink url=\"&url-m68k-cts-faq;\">cts's &arch-title; debian-installer FAQ</ulink>." #. Tag: title #: boot-installer.xml:1675 @@ -2002,26 +1313,14 @@ msgstr "Amiga" #. Tag: para #: boot-installer.xml:1676 #, 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>" -msgstr "" -"Den enda installationsmetoden tillgänglig för amiga är via hårddisken (se " -"<xref linkend=\"m68k-boot-hd\"/>). <emphasis>Med andra ord, cd-skivan är " -"inte startbar.</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 "Den enda installationsmetoden tillgänglig för amiga är via hårddisken (se <xref linkend=\"m68k-boot-hd\"/>). <emphasis>Med andra ord, cd-skivan är inte startbar.</emphasis>" #. Tag: para #: boot-installer.xml:1682 #, 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>." -msgstr "" -"Amiga fungerar för tillfället inte med bogl, så om du ser fel från bogl " -"behöver du inkludera kärnparametern <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 "Amiga fungerar för tillfället inte med bogl, så om du ser fel från bogl behöver du inkludera kärnparametern <userinput>debian-installer/framebuffer=false</userinput>." #. Tag: title #: boot-installer.xml:1691 @@ -2032,27 +1331,14 @@ msgstr "Atari" #. Tag: para #: boot-installer.xml:1692 #, 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>" -msgstr "" -"Installeraren för atari kan startas från antingen hårddisken (se <xref " -"linkend=\"m68k-boot-hd\"/>) eller från disketter (se <xref linkend=\"boot-" -"from-floppies\"/>). <emphasis>Med andra ord, cd-skivan är inte startbar.</" -"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 "Installeraren för atari kan startas från antingen hårddisken (se <xref linkend=\"m68k-boot-hd\"/>) eller från disketter (se <xref linkend=\"boot-from-floppies\"/>). <emphasis>Med andra ord, cd-skivan är inte startbar.</emphasis>" #. Tag: para #: boot-installer.xml:1699 #, 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>." -msgstr "" -"Atari fungerar för närvarande inte med bogl så om du ser fel från bogl " -"behöver du inkludera kärnparametern <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 "Atari fungerar för närvarande inte med bogl så om du ser fel från bogl behöver du inkludera kärnparametern <userinput>debian-installer/framebuffer=false</userinput>." #. Tag: title #: boot-installer.xml:1708 @@ -2063,10 +1349,7 @@ msgstr "BVME6000" #. Tag: para #: boot-installer.xml:1709 #, 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 @@ -2078,27 +1361,13 @@ msgstr "Macintosh" #. Tag: para #: boot-installer.xml:1720 #, 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." -msgstr "" -"Den enda installationsmetoden som är tillgänglig för mac är från hårddisken " -"(se <xref linkend=\"m68k-boot-hd\"/>). <emphasis>Med andra ord, cd-skivan är " -"inte startbar.</emphasis> Mac har ingen fungerande 2.4.x-kärna." +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 "Den enda installationsmetoden som är tillgänglig för mac är från hårddisken (se <xref linkend=\"m68k-boot-hd\"/>). <emphasis>Med andra ord, cd-skivan är inte startbar.</emphasis> Mac har ingen fungerande 2.4.x-kärna." #. Tag: para #: boot-installer.xml:1727 #, 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 @@ -2110,11 +1379,7 @@ msgstr "MVME147 och MVME16x" #. Tag: para #: boot-installer.xml:1743 #, 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 @@ -2126,14 +1391,8 @@ msgstr "Q40/Q60" #. Tag: para #: boot-installer.xml:1754 #, 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>" -msgstr "" -"Den enda installationsmetoden som är tillgänglig för Q40/Q60 är från " -"hårddisken (se <xref linkend=\"m68k-boot-hd\"/>). <emphasis>Med andra ord, " -"cd-skivan är inte startbar.</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 "Den enda installationsmetoden som är tillgänglig för Q40/Q60 är från hårddisken (se <xref linkend=\"m68k-boot-hd\"/>). <emphasis>Med andra ord, cd-skivan är inte startbar.</emphasis>" #. Tag: title #: boot-installer.xml:1765 @@ -2142,51 +1401,29 @@ msgid "Booting from a Hard Disk" msgstr "Starta upp från en hårddisk" #. Tag: para -#: boot-installer.xml:1771 boot-installer.xml:2369 +#: boot-installer.xml:1771 +#: boot-installer.xml:2369 #, 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." -msgstr "" -"Uppstart från ett existerande operativsystem är ofta ett bekvämt alternativ, " -"för vissa system är det den enda installationsmetoden som stöds." +msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation." +msgstr "Uppstart från ett existerande operativsystem är ofta ett bekvämt alternativ, för vissa system är det den enda installationsmetoden som stöds." #. Tag: para -#: boot-installer.xml:1777 boot-installer.xml:2375 +#: boot-installer.xml:1777 +#: boot-installer.xml:2375 #, 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" -"\"/>." -msgstr "" -"För att starta upp installeraren från hårddisk måste du redan ha hämtat och " -"placerat de filer som behövs i <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 "För att starta upp installeraren från hårddisk måste du redan ha hämtat och placerat de filer som behövs i <xref linkend=\"boot-drive-files\"/>." #. Tag: para #: boot-installer.xml:1786 #, 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)." -msgstr "" -"Åtminstone sex olika ramdiskar kan användas för att starta upp från " -"hårddisken, tre olika typer vardera med och utan stöd för en Linuxkärna " -"version 2.2.x (se <ulink url=\"&disturl;/main/installer-&architecture;/" -"current/images/MANIFEST\">MANIFEST</ulink> för detaljer)." +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 "Åtminstone sex olika ramdiskar kan användas för att starta upp från hårddisken, tre olika typer vardera med och utan stöd för en Linuxkärna version 2.2.x (se <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink> för detaljer)." #. Tag: para #: boot-installer.xml:1794 #, 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 @@ -2198,24 +1435,13 @@ msgstr "Starta upp från AmigaOS" #. Tag: para #: boot-installer.xml:1816 #, 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." -msgstr "" +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 "I <command>Workbench</command>, start Linux-installationsprocessen genom att dubbelklicka på ikonen <guiicon>StartInstall</guiicon> i katalogen <filename>debian</filename>." #. Tag: para #: boot-installer.xml:1822 #, 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 @@ -2227,28 +1453,13 @@ msgstr "Starta upp från Atari TOS" #. Tag: para #: boot-installer.xml:1838 #, 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." -msgstr "" -"I skrivbordsmiljön GEM, starta Linux-installationsprocessen genom att " -"dubbelklicka på ikonen <guiicon>bootstra.prg</guiicon> i katalogen " -"<filename>debian</filename> och klicka <guibutton>Ok</guibutton> i " -"programmets inställningsruta." +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 "I skrivbordsmiljön GEM, starta Linux-installationsprocessen genom att dubbelklicka på ikonen <guiicon>bootstra.prg</guiicon> i katalogen <filename>debian</filename> och klicka <guibutton>Ok</guibutton> i programmets inställningsruta." #. Tag: para #: boot-installer.xml:1845 #, 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 @@ -2260,73 +1471,37 @@ msgstr "Starta upp från MacOS" #. Tag: para #: boot-installer.xml:1861 #, 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:1872 #, 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:1881 #, 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:1896 #, 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:1905 #, 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:1912 #, 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 @@ -2344,37 +1519,26 @@ msgstr "FIXME" #. Tag: para #: boot-installer.xml:1933 #, 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:1945 #, no-c-format -msgid "" -"Currently, the only &arch-title; subarchitecture that supports CD-ROM " -"booting is the BVME6000." -msgstr "" -"För närvarande, den enda underarkitekturen av &arch-title; som har stöd för " -"uppstart via cd-rom är BVME6000." +msgid "Currently, the only &arch-title; subarchitecture that supports CD-ROM booting is the BVME6000." +msgstr "För närvarande, den enda underarkitekturen av &arch-title; som har stöd för uppstart via cd-rom är BVME6000." #. Tag: para #: boot-installer.xml:2017 #, 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 #: boot-installer.xml:2028 #, no-c-format msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000" -msgstr "" -"ange <screen>i6000 &enterkey;</screen> för att installera en BVME4000/6000" +msgstr "ange <screen>i6000 &enterkey;</screen> för att installera en BVME4000/6000" #. Tag: para #: boot-installer.xml:2033 @@ -2386,37 +1550,29 @@ msgstr "ange <screen>i162 &enterkey;</screen> för att installera en MVME162" #: boot-installer.xml:2038 #, no-c-format msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167" -msgstr "" -"ange <screen>i167 &enterkey;</screen> för att installera en MVME166/167" +msgstr "ange <screen>i167 &enterkey;</screen> för att installera en MVME166/167" #. Tag: para #: boot-installer.xml:2045 #, 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>." -msgstr "" +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 "Du kan även lägga till strängen <screen>TERM=vt100</screen> för att använda terminalemuleringen vt100, exempelvis <screen>i6000 TERM=vt100 &enterkey;</screen>." #. Tag: para #: boot-installer.xml:2057 #, 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:2062 #, 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." -msgstr "" -"Uppstart från startdisketten stöds endast på Atari och VME (med en SCSI-" -"diskettenhet på VME) för tillfället." +msgid "Booting from the boot floppy is supported only for Atari and VME (with a SCSI floppy drive on VME) at this time." +msgstr "Uppstart från startdisketten stöds endast på Atari och VME (med en SCSI-diskettenhet på VME) för tillfället." #. Tag: title -#: boot-installer.xml:2078 boot-installer.xml:2125 +#: boot-installer.xml:2078 +#: boot-installer.xml:2125 #, no-c-format msgid "SGI Indys TFTP Booting" msgstr "Uppstart för SGI Indy via TFTP" @@ -2427,41 +1583,36 @@ msgstr "Uppstart för SGI Indy via TFTP" 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:2098 boot-installer.xml:2147 boot-installer.xml:2202 +#: boot-installer.xml:2098 +#: boot-installer.xml:2147 +#: boot-installer.xml:2202 #: boot-installer.xml:2241 #, no-c-format msgid "Broadcom BCM91250A TFTP Booting" msgstr "Uppstart för Broadcom BCM91250A via TFTP" #. Tag: para -#: boot-installer.xml:2099 boot-installer.xml:2203 +#: boot-installer.xml:2099 +#: boot-installer.xml:2203 #, 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:2122 boot-installer.xml:2226 boot-installer.xml:2749 +#: boot-installer.xml:2122 +#: boot-installer.xml:2226 +#: boot-installer.xml:2749 #, no-c-format msgid "Boot Parameters" msgstr "Uppstartsparametrar" @@ -2469,21 +1620,16 @@ msgstr "Uppstartsparametrar" #. Tag: para #: boot-installer.xml:2126 #, 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:2131 #, 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 @@ -2493,61 +1639,41 @@ msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "bootp(): append=\"root=/dev/sda1\"" #. Tag: para -#: boot-installer.xml:2148 boot-installer.xml:2242 +#: boot-installer.xml:2148 +#: boot-installer.xml:2242 #, 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:2167 boot-installer.xml:2229 -#, fuzzy, no-c-format +#: boot-installer.xml:2167 +#: boot-installer.xml:2229 +#, no-c-format msgid "Cobalt TFTP Booting" -msgstr "Uppstart för SGI Indy via TFTP" +msgstr "Starta upp Cobalt via TFTP" #. Tag: para #: boot-installer.xml:2168 #, no-c-format -msgid "" -"Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to " -"install an NFS server and put the installer files in <filename>/nfsroot</" -"filename>. When you boot your Cobalt, you have to press the left and the " -"right cursor buttons at the same time and the machine will boot via the " -"network from NFS. It will then display several options on the display. There " -"are the following two installation methods:" +msgid "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to install an NFS server and put the installer files in <filename>/nfsroot</filename>. When you boot your Cobalt, you have to press the left and the right cursor buttons at the same time and the machine will boot via the network from NFS. It will then display several options on the display. There are the following two installation methods:" msgstr "" #. Tag: para #: boot-installer.xml:2178 #, no-c-format -msgid "" -"Via SSH (default): In this case, the installer will configure the network " -"via DHCP and start an SSH server. It will then display a random password and " -"other login information (such as the IP address) on the Cobalt LCD. When you " -"connect to the machine with an SSH client you can start with the " -"installation." +msgid "Via SSH (default): In this case, the installer will configure the network via DHCP and start an SSH server. It will then display a random password and other login information (such as the IP address) on the Cobalt LCD. When you connect to the machine with an SSH client you can start with the installation." msgstr "" #. Tag: para #: boot-installer.xml:2187 #, no-c-format -msgid "" -"Via serial console: Using a null modem cable, you can connect to the serial " -"port of your Cobalt machine (using 115200 bps) and perform the installation " -"this way. This option is not available on Qube 2700 (Qube1) machines since " -"they have no serial port." +msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way. This option is not available on Qube 2700 (Qube1) machines since they have no serial port." msgstr "" #. Tag: para #: boot-installer.xml:2230 #, no-c-format -msgid "" -"You cannot pass any boot parameters directly. Instead, you have to edit the " -"<filename>/nfsroot/default.colo</filename> file on the NFS server and add " -"your parameters to the <replaceable>args</replaceable> variable." +msgid "You cannot pass any boot parameters directly. Instead, you have to edit the <filename>/nfsroot/default.colo</filename> file on the NFS server and add your parameters to the <replaceable>args</replaceable> variable." msgstr "" #. Tag: title @@ -2559,20 +1685,13 @@ msgstr "Begränsningar för s390" #. Tag: para #: boot-installer.xml:2259 #, no-c-format -msgid "" -"In order to run the installation system a working network setup and ssh " -"session is needed on S/390." -msgstr "" -"För att kunna köra installationssystemet på S/390 behövs en fungerande " -"nätverkskonfiguration och en ssh-session." +msgid "In order to run the installation system a working network setup and ssh session is needed on S/390." +msgstr "För att kunna köra installationssystemet på S/390 behövs en fungerande nätverkskonfiguration och en ssh-session." #. Tag: para #: boot-installer.xml:2264 #, 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 @@ -2584,44 +1703,25 @@ msgstr "Uppstartsparametrar för s390" #. Tag: para #: boot-installer.xml:2276 #, 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:2330 #, 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:2339 #, 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:2348 #, 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 @@ -2657,15 +1757,7 @@ msgstr "Starta upp OldWorld PowerMac från MacOS" #. Tag: para #: boot-installer.xml:2394 #, 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 @@ -2678,27 +1770,11 @@ msgstr "Starta upp NewWorld Mac från OpenFirmware" #: boot-installer.xml:2413 #, 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 @@ -2711,67 +1787,39 @@ msgstr "Starta upp från USB-minne" #: boot-installer.xml:2449 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." -msgstr "" +msgstr "För närvarande är NewWorld PowerMac-system kända att ha stöd för uppstart via USB." #. Tag: para #: boot-installer.xml:2455 #, 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:2467 #, 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:2479 #, 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:2493 #, 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:2499 #, 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 @@ -2783,51 +1831,31 @@ msgstr "" #. Tag: para #: boot-installer.xml:2536 #, 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:2551 #, 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:2563 #, 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:2569 #, 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:2576 #, 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 @@ -2839,37 +1867,19 @@ msgstr "Uppstartsparametrar för PowerPC" #. Tag: para #: boot-installer.xml:2588 #, 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:2628 #, 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:2684 #, 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 @@ -2878,34 +1888,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:2711 #, 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>." -msgstr "" +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 "Ett flertal Sparc (exempelvis Ultra 10) har ett OBP-fel som förhindrar dem från att starta upp (istället för att inte stöda uppstart alls). Den lämpliga uppdateringen för OBP kan hämtas som produkt-id 106121 från <ulink url=\"http://sunsolve.sun.com\"></ulink>." #. Tag: para #: boot-installer.xml:2718 #, 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 @@ -2917,120 +1916,50 @@ msgstr "IDPROM-meddelanden" #. Tag: para #: boot-installer.xml:2731 #, 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:2750 #, 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." -msgstr "" -"Uppstartsparametrar är parametrar för Linux-kärnan som generellt sett " -"används för att se till att kringutrustning hanteras korrekt. För det mesta " -"kan kärnan automatiskt identifiera information om din kringutrustning. Dock, " -"i vissa fall, behöver du hjälpa kärnan en bit på vägen." +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 "Uppstartsparametrar är parametrar för Linux-kärnan som generellt sett används för att se till att kringutrustning hanteras korrekt. För det mesta kan kärnan automatiskt identifiera information om din kringutrustning. Dock, i vissa fall, behöver du hjälpa kärnan en bit på vägen." #. Tag: para #: boot-installer.xml:2757 #, 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." -msgstr "" -"Om det här är första gången du startar upp systemet kan du prova de " -"uppstartsparametrar som är standard (alltså, ställ inte in några parametrar) " -"och se om det fungerar korrekt. Det kommer säkert att göra det. Om inte, kan " -"du starta om senare och leta efter några speciella parametrar som informerar " -"systemet om din hårdvara." +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 "Om det här är första gången du startar upp systemet kan du prova de uppstartsparametrar som är standard (alltså, ställ inte in några parametrar) och se om det fungerar korrekt. Det kommer säkert att göra det. Om inte, kan du starta om senare och leta efter några speciella parametrar som informerar systemet om din hårdvara." #. Tag: para #: boot-installer.xml:2764 #, 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\"/>." -msgstr "" -"Information om många uppstartsparametrar kan hittas i <ulink url=\"http://" -"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, " -"inklusive tips för obskyr hårdvara. Den här sektion innehåller endast en del " -"av de mest vanliga parametrarna. Vissa vanliga problem finns beskrivna i " -"<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 "Information om många uppstartsparametrar kan hittas i <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, inklusive tips för obskyr hårdvara. Den här sektion innehåller endast en del av de mest vanliga parametrarna. Vissa vanliga problem finns beskrivna i <xref linkend=\"boot-troubleshooting\"/>." #. Tag: para #: boot-installer.xml:2773 #, 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 "" "När kärnan startar upp bör meddelandet<informalexample><screen>\n" -"Memory:<replaceable>tillgängligt</replaceable>k/<replaceable>totalt</" -"replaceable>k available\n" -"</screen></informalexample> visas tidigt i processen. <replaceable>totalt</" -"replaceable> bör stämma med totalt RAM-minne i kilobyte. Om det inte stämmer " -"med den faktiska mängden RAM-minne du har installerad behöver du använda " -"parametern <userinput>mem=<replaceable>ram</replaceable></userinput>, där " -"<replaceable>ram</replaceable> är inställd till mängden minne och ändelsen " -"<quote>k</quote> för kilobyte eller <quote>m</quote> för megabyte. Till " -"exempel, både <userinput>mem=65536k</userinput> och <userinput>mem=64m</" -"userinput> betyder 64MB RAM-minne." +"Memory:<replaceable>tillgängligt</replaceable>k/<replaceable>totalt</replaceable>k available\n" +"</screen></informalexample> visas tidigt i processen. <replaceable>totalt</replaceable> bör stämma med totalt RAM-minne i kilobyte. Om det inte stämmer med den faktiska mängden RAM-minne du har installerad behöver du använda parametern <userinput>mem=<replaceable>ram</replaceable></userinput>, där <replaceable>ram</replaceable> är inställd till mängden minne och ändelsen <quote>k</quote> för kilobyte eller <quote>m</quote> för megabyte. Till exempel, både <userinput>mem=65536k</userinput> och <userinput>mem=64m</userinput> betyder 64MB RAM-minne." #. Tag: para #: boot-installer.xml:2789 #, 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>." -msgstr "" -"Om du startar upp på en seriekonsoll kommer generellt sett kärnan att " -"autodetektera det<phrase arch=\"mipsel\"> (dock inte på DECstation)</" -"phrase>. Om du har ett grafikkort (framebuffer) och ett tangentbord anslutet " -"till datorn som du önskar starta upp via seriekonsoll, kan du skicka med " -"följande argument <userinput>console=<replaceable>enhet</replaceable></" -"userinput> till kärnan, där <replaceable>enhet</replaceable> är din " -"serieenhet, som vanligtvis är något liknande <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 "Om du startar upp på en seriekonsoll kommer generellt sett kärnan att autodetektera det<phrase arch=\"mipsel\"> (dock inte på DECstation)</phrase>. Om du har ett grafikkort (framebuffer) och ett tangentbord anslutet till datorn som du önskar starta upp via seriekonsoll, kan du skicka med följande argument <userinput>console=<replaceable>enhet</replaceable></userinput> till kärnan, där <replaceable>enhet</replaceable> är din serieenhet, som vanligtvis är något liknande <filename>ttyS0</filename>." #. Tag: para #: boot-installer.xml:2802 #, 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>." -msgstr "" -"För &arch-title; heter serieenheterna <filename>ttya</filename> eller " -"<filename>ttyb</filename>. Alternativt, ställ in OpenPROM-variablerna " -"<envar>input-device</envar> och <envar>output-device</envar> till " -"<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 "För &arch-title; heter serieenheterna <filename>ttya</filename> eller <filename>ttyb</filename>. Alternativt, ställ in OpenPROM-variablerna <envar>input-device</envar> och <envar>output-device</envar> till <filename>ttya</filename>." #. Tag: title #: boot-installer.xml:2813 @@ -3041,22 +1970,8 @@ msgstr "Parametrar för Debian Installer" #. Tag: para #: boot-installer.xml:2814 #, 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. With kernel 2.6.9 " -"or newer, you can use 32 command line options and 32 environment options. </" -"para> </footnote> which may be useful." -msgstr "" -"Installationssystemet känner igen ytterligare ett antal " -"uppstartsparametrar<footnote> <para> Notera att kärnan accepterar maximalt 8 " -"kommandoradsflaggor och 8 miljöflaggor (inklusive de flaggor som läggs till " -"som standard för installeraren). Om de här siffrorna överstigs kommer 2.4-" -"kärnor att förkasta de flaggor som överstiger gränsen och 2.6-kärnor får " -"panik. Med kärnan 2.6.9 eller senare kan du använda 32 kommandoradsflaggor " -"eller 32 miljöflaggor. </para> </footnote> som kan vara användbara." +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. With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options. </para> </footnote> which may be useful." +msgstr "Installationssystemet känner igen ytterligare ett antal uppstartsparametrar<footnote> <para> Notera att kärnan accepterar maximalt 8 kommandoradsflaggor och 8 miljöflaggor (inklusive de flaggor som läggs till som standard för installeraren). Om de här siffrorna överstigs kommer 2.4-kärnor att förkasta de flaggor som överstiger gränsen och 2.6-kärnor får panik. Med kärnan 2.6.9 eller senare kan du använda 32 kommandoradsflaggor eller 32 miljöflaggor. </para> </footnote> som kan vara användbara." #. Tag: term #: boot-installer.xml:2834 @@ -3068,42 +1983,19 @@ msgstr "debconf/priority" #: boot-installer.xml:2835 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." -msgstr "" -"Den här parametern ställer in så att meddelanden med lägst prioritet visas." +msgstr "Den här parametern ställer in så att meddelanden med lägst prioritet visas." #. Tag: para #: boot-installer.xml:2839 #, 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." -msgstr "" -"Standardinstallationen använder <userinput>debconf/priority=high</" -"userinput>. Det betyder att både meddelanden med prioriteterna hög och " -"kritisk visas, men meddelanden med prioriteterna medium och låg hoppas över. " -"Om problem påträffas justerar installeraren prioriteten efter behov." +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 "Standardinstallationen använder <userinput>debconf/priority=high</userinput>. Det betyder att både meddelanden med prioriteterna hög och kritisk visas, men meddelanden med prioriteterna medium och låg hoppas över. Om problem påträffas justerar installeraren prioriteten efter behov." #. Tag: para #: boot-installer.xml:2846 #, 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." -msgstr "" -"Om du lägger till <userinput>debconf/priority=medium</userinput> som " -"uppstartsparameter kommer du att få se installationsmenyn och få mer " -"kontroll över installationen. När <userinput>debconf/priority=low</" -"userinput> används kommer alla meddelanden visas (det här är likvärdigt med " -"uppstartsmetoden <emphasis>expert</emphasis>). Med <userinput>debconf/" -"priority=critical</userinput> kommer installationssystemet endast att visa " -"kritiska meddelanden och försöka göra det rätta utan att krånga till det." +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 "Om du lägger till <userinput>debconf/priority=medium</userinput> som uppstartsparameter kommer du att få se installationsmenyn och få mer kontroll över installationen. När <userinput>debconf/priority=low</userinput> används kommer alla meddelanden visas (det här är likvärdigt med uppstartsmetoden <emphasis>expert</emphasis>). Med <userinput>debconf/priority=critical</userinput> kommer installationssystemet endast att visa kritiska meddelanden och försöka göra det rätta utan att krånga till det." #. Tag: term #: boot-installer.xml:2860 @@ -3114,43 +2006,8 @@ msgstr "DEBIAN_FRONTEND" #. Tag: para #: boot-installer.xml:2861 #, 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." -msgstr "" -"Den här uppstartsparametern kontrollerar den typ av användargränssnitt som " -"används för installeraren. De för närvarande möjliga parametervärdena är: " -"<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> Standardgränssnitt är " -"<userinput>DEBIAN_FRONTEND=newt</userinput>. " -"<userinput>DEBIAN_FRONTEND=text</userinput> kan föredras för installationer " -"via seriekonsoll. Generellt sett är endast gränssnittet <userinput>newt</" -"userinput> tillgängligt på standardinstallationsmedia så den här parametern " -"är inte så användbar just nu." +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 "Den här uppstartsparametern kontrollerar den typ av användargränssnitt som används för installeraren. De för närvarande möjliga parametervärdena är: <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> Standardgränssnitt är <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> kan föredras för installationer via seriekonsoll. Generellt sett är endast gränssnittet <userinput>newt</userinput> tillgängligt på standardinstallationsmedia så den här parametern är inte så användbar just nu." #. Tag: term #: boot-installer.xml:2897 @@ -3161,16 +2018,8 @@ msgstr "BOOT_DEBUG" #. Tag: para #: boot-installer.xml:2898 #, 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.)" -msgstr "" -"Ställ in den här uppstartsparametern till 2 innebär att installerarens " -"uppstartsprocess kommer att loggas på ett informativt sätt. Ställ in den " -"till 3 och felsökningsloggar blir tillgängliga på strategiska punkter i " -"uppstartsprocessen. (Avsluta skalen för att fortsätta uppstartsprocessen.)" +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 "Ställ in den här uppstartsparametern till 2 innebär att installerarens uppstartsprocess kommer att loggas på ett informativt sätt. Ställ in den till 3 och felsökningsloggar blir tillgängliga på strategiska punkter i uppstartsprocessen. (Avsluta skalen för att fortsätta uppstartsprocessen.)" #. Tag: userinput #: boot-installer.xml:2907 @@ -3217,12 +2066,8 @@ msgstr "BOOT_DEBUG=3" #. Tag: para #: boot-installer.xml:2923 #, 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." -msgstr "" -"Skal kommer att köras på olika punkter i uppstartsprocessen för detaljerad " -"felsökning. Avsluta skalet för att fortsätta uppstarten." +msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot." +msgstr "Skal kommer att köras på olika punkter i uppstartsprocessen för detaljerad felsökning. Avsluta skalet för att fortsätta uppstarten." #. Tag: term #: boot-installer.xml:2937 @@ -3233,26 +2078,14 @@ msgstr "INSTALL_MEDIA_DEV" #. Tag: para #: boot-installer.xml:2938 #, 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>" -msgstr "" -"Värdet för parametern är sökvägen till enheten som Debian Installer ska " -"läsas in från. Till exempel, <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 "Värdet för parametern är sökvägen till enheten som Debian Installer ska läsas in från. Till exempel, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>" #. Tag: para #: boot-installer.xml:2944 #, 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." -msgstr "" -"Startdisketten, som normalt sett söker av alla disketter och USB-" -"lagringsenheter den kan hitta efter rotdisketten, kan åsidosättas av den här " -"parametern för att endast söka på en enhet." +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 "Startdisketten, som normalt sett söker av alla disketter och USB-lagringsenheter den kan hitta efter rotdisketten, kan åsidosättas av den här parametern för att endast söka på en enhet." #. Tag: term #: boot-installer.xml:2954 @@ -3264,32 +2097,14 @@ msgstr "debian-installer/framebuffer" #. Tag: para #: boot-installer.xml:2955 #, 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." -msgstr "" -"Vissa arkitekturer använder kärnans framebuffer för att erbjuda en " -"installation på ett antal olika språk. Om framebuffer orsakar ett problem på " -"ditt system kan du inaktivera funktionen genom parametern <userinput>debian-" -"installer/framebuffer=false</userinput>. Symptom på problemet är " -"felmeddelanden om bterm eller bogl, en blank skärm, eller en frysning inom " -"ett par minuter efter påbörjad installation." +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 "Vissa arkitekturer använder kärnans framebuffer för att erbjuda en installation på ett antal olika språk. Om framebuffer orsakar ett problem på ditt system kan du inaktivera funktionen genom parametern <userinput>debian-installer/framebuffer=false</userinput>. Symptom på problemet är felmeddelanden om bterm eller bogl, en blank skärm, eller en frysning inom ett par minuter efter påbörjad installation." #. Tag: para #: boot-installer.xml:2964 #, 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." -msgstr "" -"Argumentet <userinput>video=vga16:off</userinput> kan också användas för att " -"inaktivera grafikkortet. Sådana program har rapporterats på en Dell Inspiron " -"med Mobile Radeon-kort." +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 "Argumentet <userinput>video=vga16:off</userinput> kan också användas för att inaktivera grafikkortet. Sådana program har rapporterats på en Dell Inspiron med Mobile Radeon-kort." #. Tag: para #: boot-installer.xml:2970 @@ -3306,20 +2121,8 @@ msgstr "Liknande problem har blivit rapporterats för hppa." #. Tag: para #: boot-installer.xml:2978 #, 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>." -msgstr "" -"På grund av skärmproblem på vissa system, stöd för framebuffer är " -"<emphasis>inaktiverad som standard</emphasis> för &arch-title;. Det kan " -"resultera i en ful skärm på system som korrekt sett har stöd för " -"framebuffer, såsom de med ATI-grafikkort. Om du ser skärmproblem i " -"installeraren kan du prova att starta upp med parametern <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 "På grund av skärmproblem på vissa system, stöd för framebuffer är <emphasis>inaktiverad som standard</emphasis> för &arch-title;. Det kan resultera i en ful skärm på system som korrekt sett har stöd för framebuffer, såsom de med ATI-grafikkort. Om du ser skärmproblem i installeraren kan du prova att starta upp med parametern <userinput>debian-installer/framebuffer=true</userinput>." #. Tag: term #: boot-installer.xml:2991 @@ -3330,12 +2133,8 @@ msgstr "debian-installer/probe/usb" #. Tag: para #: boot-installer.xml:2992 #, no-c-format -msgid "" -"Set to <userinput>false</userinput> to prevent probing for USB on boot, if " -"that causes problems." -msgstr "" -"Ställ in till <userinput>false</userinput> för att förhindra sökning efter " -"USB vid uppstart, om det orsakar problem." +msgid "Set to <userinput>false</userinput> to prevent probing for USB on boot, if that causes problems." +msgstr "Ställ in till <userinput>false</userinput> för att förhindra sökning efter USB vid uppstart, om det orsakar problem." #. Tag: term #: boot-installer.xml:3001 @@ -3346,30 +2145,14 @@ msgstr "netcfg/disable_dhcp" #. Tag: para #: boot-installer.xml:3002 #, 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." -msgstr "" -"Som standard söker &d-i; automatiskt efter nätverkskonfiguration via DHCP. " -"Om sökningen lyckas, har du ingen chans att granska och ändra de mottagna " -"inställningarna. Du kan komma åt de manuellt inställningarna endast om DHCP-" -"sökningen misslyckas." +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 "Som standard söker &d-i; automatiskt efter nätverkskonfiguration via DHCP. Om sökningen lyckas, har du ingen chans att granska och ändra de mottagna inställningarna. Du kan komma åt de manuellt inställningarna endast om DHCP-sökningen misslyckas." #. Tag: para #: boot-installer.xml:3009 #, 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." -msgstr "" -"Om du har en DHCP-server på ditt lokala nätverk men du vill undvika den på " -"grund av att den, exempelvis ger fel svar, kan du använda parametern " -"<userinput>netcfg/disable_dhcp=true</userinput> för att förhindra att " -"nätverket konfigureras med DHCP och att informationen matas in manuellt." +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 "Om du har en DHCP-server på ditt lokala nätverk men du vill undvika den på grund av att den, exempelvis ger fel svar, kan du använda parametern <userinput>netcfg/disable_dhcp=true</userinput> för att förhindra att nätverket konfigureras med DHCP och att informationen matas in manuellt." #. Tag: term #: boot-installer.xml:3020 @@ -3380,13 +2163,8 @@ msgstr "hw-detect/start_pcmcia" #. Tag: para #: boot-installer.xml:3021 #, 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." -msgstr "" -"Ställ in till <userinput>false</userinput> för att förhindra att PCMCIA-" -"tjänster startas, om det orsakar problem. Vissa bärbara datorer är kända för " -"det här problemet." +msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." +msgstr "Ställ in till <userinput>false</userinput> för att förhindra att PCMCIA-tjänster startas, om det orsakar problem. Vissa bärbara datorer är kända för det här problemet." #. Tag: term #: boot-installer.xml:3031 @@ -3397,12 +2175,8 @@ msgstr "preseed/url" #. Tag: para #: boot-installer.xml:3032 #, no-c-format -msgid "" -"Specify the url to a preconfiguration file to download and use in automating " -"the install. See <xref linkend=\"automatic-install\"/>." -msgstr "" -"Ange en url till en förkonfigurationsfil att hämta och använda för att " -"automatisera installationen. Se <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 "Ange en url till en förkonfigurationsfil att hämta och använda för att automatisera installationen. Se <xref linkend=\"automatic-install\"/>." #. Tag: term #: boot-installer.xml:3041 @@ -3413,12 +2187,8 @@ msgstr "preseed/file" #. Tag: para #: boot-installer.xml:3042 #, no-c-format -msgid "" -"Specify the path to a preconfiguration file to load to automating the " -"install. See <xref linkend=\"automatic-install\"/>." -msgstr "" -"Ange sökvägen till en förkonfigurationsfil att läsa in för att automatisera " -"installationen. Se <xref linkend=\"automatic-install\"/>." +msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>." +msgstr "Ange sökvägen till en förkonfigurationsfil att läsa in för att automatisera installationen. Se <xref linkend=\"automatic-install\"/>." #. Tag: term #: boot-installer.xml:3051 @@ -3429,32 +2199,14 @@ msgstr "cdrom-detect/eject" #. Tag: para #: boot-installer.xml:3052 #, 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." -msgstr "" -"Som standard, före omstart, matar &d-i; automatiskt ut det optiska mediat " -"som användes under installationen. Det kan vara onödigt om systemet inte " -"startar upp automatiskt på cd. I vissa fall kan det inte vara önskvärt, till " -"exempel om den optiska enheten inte kan mata in mediat själv om användaren " -"inte finns där för att göra det manuellt. Många cd-läsare kan inte mata in " -"media automatiskt." +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 "Som standard, före omstart, matar &d-i; automatiskt ut det optiska mediat som användes under installationen. Det kan vara onödigt om systemet inte startar upp automatiskt på cd. I vissa fall kan det inte vara önskvärt, till exempel om den optiska enheten inte kan mata in mediat själv om användaren inte finns där för att göra det manuellt. Många cd-läsare kan inte mata in media automatiskt." #. Tag: para #: boot-installer.xml:3061 #, 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." -msgstr "" -"Ställ in till <userinput>false</userinput> för att inaktivera automatisk " -"utmatning och tänk på att du kan behöva se till att systemet inte startar " -"upp automatiskt från den optiska enheten efter den initiala installationen." +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 "Ställ in till <userinput>false</userinput> för att inaktivera automatisk utmatning och tänk på att du kan behöva se till att systemet inte startar upp automatiskt från den optiska enheten efter den initiala installationen." #. Tag: term #: boot-installer.xml:3072 @@ -3466,8 +2218,7 @@ msgstr "ramdisk_size" #: boot-installer.xml:3073 #, no-c-format msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." -msgstr "" -"Om du använder en 2.2.x-kärna, kan du behöva att ställa in &ramdisksize;." +msgstr "Om du använder en 2.2.x-kärna, kan du behöva att ställa in &ramdisksize;." #. Tag: term #: boot-installer.xml:3081 @@ -3478,13 +2229,8 @@ msgstr "rescue/enable" #. Tag: para #: boot-installer.xml:3082 #, no-c-format -msgid "" -"Set to <userinput>true</userinput> to enter rescue mode rather than " -"performing a normal installation. See <xref linkend=\"rescue\"/>." -msgstr "" -"Ställ in till <userinput>true</userinput> för att gå in i räddningsläget " -"istället för att genomföra en normal installation. Se <xref linkend=\"rescue" -"\"/>." +msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." +msgstr "Ställ in till <userinput>true</userinput> för att gå in i räddningsläget istället för att genomföra en normal installation. Se <xref linkend=\"rescue\"/>." #. Tag: title #: boot-installer.xml:3100 @@ -3501,72 +2247,32 @@ msgstr "Tillförlitlighet för disketter" #. Tag: para #: boot-installer.xml:3107 #, no-c-format -msgid "" -"The biggest problem for people using floppy disks to install Debian seems to " -"be floppy disk reliability." -msgstr "" -"Det största problemet för personer som använder disketter för att installera " -"Debian verkar vara pålitligheten för disketterna." +msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." +msgstr "Det största problemet för personer som använder disketter för att installera Debian verkar vara pålitligheten för disketterna." #. Tag: para #: boot-installer.xml:3112 #, 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." -msgstr "" -"Startdisketten är den diskett med värsta problemen på grund av att den läses " -"av hårdvaran direkt, före Linux startar upp. Ofta läser hårdvaran inte så " -"tillförlitligt som Linux egna drivrutin för diskettenheten och kan bara " -"stoppa upp utan att skriva ut något felmeddelande om den läser felaktig " -"data. Det kan också bli fel i drivrutinsdisketterna som visar sig som massor " -"av meddelanden om disk in/ut-fel." +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 "Startdisketten är den diskett med värsta problemen på grund av att den läses av hårdvaran direkt, före Linux startar upp. Ofta läser hårdvaran inte så tillförlitligt som Linux egna drivrutin för diskettenheten och kan bara stoppa upp utan att skriva ut något felmeddelande om den läser felaktig data. Det kan också bli fel i drivrutinsdisketterna som visar sig som massor av meddelanden om disk in/ut-fel." #. Tag: para #: boot-installer.xml:3121 #, 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." -msgstr "" -"Om du får installationen att stanna upp på en speciell diskett, första saken " -"du bör göra är att hämta ned diskettavbilden igen och skriva den till en " -"<emphasis>annan</emphasis> diskett. Bara omformatering av gamla disketten " -"kanske inte räcker, även om det verkar som om disketten blev omformaterad " -"och skriven utan fel. Det är användbart ibland att prova skriva disketten på " -"ett annat 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 "Om du får installationen att stanna upp på en speciell diskett, första saken du bör göra är att hämta ned diskettavbilden igen och skriva den till en <emphasis>annan</emphasis> diskett. Bara omformatering av gamla disketten kanske inte räcker, även om det verkar som om disketten blev omformaterad och skriven utan fel. Det är användbart ibland att prova skriva disketten på ett annat system." #. Tag: para #: boot-installer.xml:3131 #, 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." -msgstr "" -"En användare rapporterar att han måste skriva avbilderna till disketten " -"<emphasis>tre</emphasis> gånger före en fungerade och sedan var allt bra med " -"den tredje disketten." +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 "En användare rapporterar att han måste skriva avbilderna till disketten <emphasis>tre</emphasis> gånger före en fungerade och sedan var allt bra med den tredje disketten." #. Tag: para #: boot-installer.xml:3137 #, 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." -msgstr "" -"Andra användare har rapporterat att helt enkelt starta om ett par gånger med " -"samma diskett i diskettenheten kan leda till en lyckad uppstart. Det är på " -"grund av felaktig hårdvara eller drivrutinen för diskettenheten i firmware." +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 "Andra användare har rapporterat att helt enkelt starta om ett par gånger med samma diskett i diskettenheten kan leda till en lyckad uppstart. Det är på grund av felaktig hårdvara eller drivrutinen för diskettenheten i firmware." #. Tag: title #: boot-installer.xml:3146 @@ -3577,54 +2283,26 @@ msgstr "Uppstartskonfiguration" #. Tag: para #: boot-installer.xml:3148 #, 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\"/>." -msgstr "" -"Om du har problem och kärnan hänger sig under uppstartsprocessen, inte " -"känner igen kringutrustning som du faktiskt har, eller enheter som inte " -"korrekt känns igen är uppstartsparametrarna den första saken att " -"kontrollera, det diskuteras i <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 "Om du har problem och kärnan hänger sig under uppstartsprocessen, inte känner igen kringutrustning som du faktiskt har, eller enheter som inte korrekt känns igen är uppstartsparametrarna den första saken att kontrollera, det diskuteras i <xref linkend=\"boot-parms\"/>." #. Tag: para #: boot-installer.xml:3155 #, 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>." -msgstr "" -"Om du startar upp med din egna kärna istället för den som skickas med " -"installeraren, se till att <userinput>CONFIG_DEVFS</userinput> är inställd i " -"din kärna. Installeraren kräver <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 "Om du startar upp med din egna kärna istället för den som skickas med installeraren, se till att <userinput>CONFIG_DEVFS</userinput> är inställd i din kärna. Installeraren kräver <userinput>CONFIG_DEVFS</userinput>." #. Tag: para #: boot-installer.xml:3162 #, 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>" -msgstr "" -"Ofta kan problemen lösas genom att ta bort tillägg och kringutrustning och " -"sedan försöka starta upp igen. <phrase arch=\"i386\">Interna modem, ljudkort " -"och enheter med Plug-n-Play kan vara speciellt problematiska.</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 "Ofta kan problemen lösas genom att ta bort tillägg och kringutrustning och sedan försöka starta upp igen. <phrase arch=\"i386\">Interna modem, ljudkort och enheter med Plug-n-Play kan vara speciellt problematiska.</phrase>" #. Tag: para #: boot-installer.xml:3168 #, 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>." -msgstr "" -"Om du har en stor mängd minne installerad i din maskin, mer än 512MB, och " -"installeraren hänger sig när kärnan startar upp, kan du behöva att inkludera " -"ett uppstartsargument för att begränsa mängden minne som kärnan ser, såsom " -"<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 "Om du har en stor mängd minne installerad i din maskin, mer än 512MB, och installeraren hänger sig när kärnan startar upp, kan du behöva att inkludera ett uppstartsargument för att begränsa mängden minne som kärnan ser, såsom <userinput>mem=512m</userinput>." #. Tag: title #: boot-installer.xml:3179 @@ -3635,80 +2313,32 @@ msgstr "Vanliga installationsproblem på &arch-title;" #. Tag: para #: boot-installer.xml:3180 #, no-c-format -msgid "" -"There are some common installation problems that can be solved or avoided by " -"passing certain boot parameters to the installer." -msgstr "" -"Det finns några vanliga installationsproblem som kan lösas eller undvikas " -"genom att skicka med vissa uppstartsparametrar till installeraren." +msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." +msgstr "Det finns några vanliga installationsproblem som kan lösas eller undvikas genom att skicka med vissa uppstartsparametrar till installeraren." #. Tag: para #: boot-installer.xml:3185 #, 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>." -msgstr "" -"Vissa system har disketter med <quote>omvänd DCL</quote>. Om du upptäcker " -"fel vid inläsning från disketten även om disketten är bra, prova med " -"parametern <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 "Vissa system har disketter med <quote>omvänd DCL</quote>. Om du upptäcker fel vid inläsning från disketten även om disketten är bra, prova med parametern <userinput>floppy=thinkpad</userinput>." #. Tag: para #: boot-installer.xml:3191 #, 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>." -msgstr "" -"På vissa system, såsom IBM PS/1 eller ValuePoint (som har ST-506-" -"hårddiskar), kanske IDE-disken inte kan identifieras korrekt. Igen, prova " -"den först utan parametrar och se om IDE-disken identifieras korrekt. Om " -"inte, ta reda på geometrin för din hårddisk (cylindrar, huvuden och " -"sektorer), och använd parametern <userinput>hd=<replaceable>cylindrar</" -"replaceable>,<replaceable>huvuden</replaceable>,<replaceable>sektorer</" -"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 "På vissa system, såsom IBM PS/1 eller ValuePoint (som har ST-506-hårddiskar), kanske IDE-disken inte kan identifieras korrekt. Igen, prova den först utan parametrar och se om IDE-disken identifieras korrekt. Om inte, ta reda på geometrin för din hårddisk (cylindrar, huvuden och sektorer), och använd parametern <userinput>hd=<replaceable>cylindrar</replaceable>,<replaceable>huvuden</replaceable>,<replaceable>sektorer</replaceable></userinput>." #. Tag: para #: boot-installer.xml:3200 #, 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." -msgstr "" -"Om du har en mycket gammal maskin, och kärnan hänger sig efter den sagt " -"<computeroutput>Checking 'hlt' instruction...</computeroutput>, så ska du " -"prova uppstartsargumentet <userinput>no-hlt</userinput>, som inaktiverar det " -"här testet." +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 "Om du har en mycket gammal maskin, och kärnan hänger sig efter den sagt <computeroutput>Checking 'hlt' instruction...</computeroutput>, så ska du prova uppstartsargumentet <userinput>no-hlt</userinput>, som inaktiverar det här testet." #. Tag: para #: boot-installer.xml:3207 #, 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." -msgstr "" -"Om din skärm börjar visa en konstig bild vid uppstart av kärnan, exempelvis " -"vitt, svart eller färgat pixelskräp, kan ditt system innehålla ett " -"problematiskt grafikkort som inte kan byta till framebuffer-läget korrekt. " -"Då kan du använda uppstartsparametern <userinput>debian-installer/" -"framebuffer=false</userinput> eller <userinput>video=vga16:off</userinput> " -"för att inaktivera framebuffer-konsollen. Endast det engelska språket kommer " -"att vara tillgängligt under installationen på grund av begränsade " -"konsollfunktioner. Se <xref linkend=\"boot-parms\"/> för detaljer." +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 "Om din skärm börjar visa en konstig bild vid uppstart av kärnan, exempelvis vitt, svart eller färgat pixelskräp, kan ditt system innehålla ett problematiskt grafikkort som inte kan byta till framebuffer-läget korrekt. Då kan du använda uppstartsparametern <userinput>debian-installer/framebuffer=false</userinput> eller <userinput>video=vga16:off</userinput> för att inaktivera framebuffer-konsollen. Endast det engelska språket kommer att vara tillgängligt under installationen på grund av begränsade konsollfunktioner. Se <xref linkend=\"boot-parms\"/> för detaljer." #. Tag: title #: boot-installer.xml:3222 @@ -3719,45 +2349,14 @@ msgstr "Systemet fryser under konfigurationsfasen för PCMCIA" #. Tag: para #: boot-installer.xml:3223 #, 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." -msgstr "" -"Vissa modeller av bärbara datorer producerade av Dell är kända att krascha " -"när identifiering av PCMCIA-enheter försöker komma åt vissa " -"hårdvaruadresser. Andra bärbara kan visa liknande problem. Om du upplever " -"sådana problem och du inte behöver PCMCIA-stöd under installationen kan du " -"inaktivera PCMCIA med uppstartsparametern <userinput>hw-detect/" -"start_pcmcia=false</userinput>. Du kan då konfigurera PCMCIA efter " -"installationen är genomförd och exkludera resursintervallet som orsakar " -"problemen." +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 "Vissa modeller av bärbara datorer producerade av Dell är kända att krascha när identifiering av PCMCIA-enheter försöker komma åt vissa hårdvaruadresser. Andra bärbara kan visa liknande problem. Om du upplever sådana problem och du inte behöver PCMCIA-stöd under installationen kan du inaktivera PCMCIA med uppstartsparametern <userinput>hw-detect/start_pcmcia=false</userinput>. Du kan då konfigurera PCMCIA efter installationen är genomförd och exkludera resursintervallet som orsakar problemen." #. Tag: para #: boot-installer.xml:3233 #, 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." -msgstr "" -"Alternativt kan du starta upp installeraren i expert-läget. Du kommer då att " -"bli frågad att ange inställningar för resursintervall som din hårdvara " -"behöver. Till exempel, om du har en av Dells bärbara datorer som nämndes " -"ovan, bör du ange <userinput>exclude port 0x800-0x8ff</userinput> här. Det " -"finns också en lista på några vanliga resursintervall i <ulink url=\"http://" -"pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System " -"resource settings section of the PCMCIA HOWTO</ulink>. Notera att du måste " -"ta bort eventuella kommatecken när du anger det här värdet i installeraren." +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 "Alternativt kan du starta upp installeraren i expert-läget. Du kommer då att bli frågad att ange inställningar för resursintervall som din hårdvara behöver. Till exempel, om du har en av Dells bärbara datorer som nämndes ovan, bör du ange <userinput>exclude port 0x800-0x8ff</userinput> här. Det finns också en lista på några vanliga resursintervall i <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Notera att du måste ta bort eventuella kommatecken när du anger det här värdet i installeraren." #. Tag: title #: boot-installer.xml:3250 @@ -3768,23 +2367,8 @@ msgstr "Systemet fryser vid inläsning av USB-moduler" #. Tag: para #: boot-installer.xml:3251 #, 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." -msgstr "" -"Kärnan försöker normalt sett att installera USB-moduler och drivrutinen för " -"USB-tangentbord för att ge stöd för icke-standardiserade USB-tangentbord. " -"Dock, det finns några trasiga USB-system där drivrutinen hänger sig vid " -"inläsning. Ett möjligt sätt att komma runt problemet är att inaktivera USB-" -"kontrollern i BIOS-inställningen på ditt moderkort. Ett annat alternativ är " -"att skicka med parametern <userinput>debian-installer/probe/usb=false</" -"userinput> vid uppstartsprompten, som kommer att förhindra att modulerna " -"läses in." +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 "Kärnan försöker normalt sett att installera USB-moduler och drivrutinen för USB-tangentbord för att ge stöd för icke-standardiserade USB-tangentbord. Dock, det finns några trasiga USB-system där drivrutinen hänger sig vid inläsning. Ett möjligt sätt att komma runt problemet är att inaktivera USB-kontrollern i BIOS-inställningen på ditt moderkort. Ett annat alternativ är att skicka med parametern <userinput>debian-installer/probe/usb=false</userinput> vid uppstartsprompten, som kommer att förhindra att modulerna läses in." #. Tag: title #: boot-installer.xml:3265 @@ -3795,39 +2379,8 @@ msgstr "Tolkning av kärnans uppstartsmeddelanden" #. Tag: para #: boot-installer.xml:3267 #, 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\"/>)." -msgstr "" -"Under uppstartssekvensen kan du se många meddelanden i formen " -"<computeroutput>can't find <replaceable>something</replaceable> </" -"computeroutput>, eller <computeroutput> <replaceable>something</replaceable> " -"not present</computeroutput>, <computeroutput>can't initialize " -"<replaceable>something</replaceable> </computeroutput>, eller till och med " -"<computeroutput>this driver release depends on <replaceable>något</" -"replaceable> </computeroutput>. De flesta av de här meddelandena är " -"harmlösa. Du ser dem för att kärnan för installationssystemet är byggd för " -"att köras på datorer med många olika kringutrustningsenheter. Så klart, " -"ingen dator kommer att ha alla möjliga kringutrustningsenheter, så " -"operativsystemet kan klaga en hel del när den letar efter kringutrustning " -"som du inte har. Du kan också se att systemet pausar en stund. Det händer " -"när det väntar på att en enhet ska svara, och den enheten finns inte på " -"ditt system. Om du tycker att tiden det tar att starta upp systemet är på " -"tok för lång, kan du skapa en anpassad kärna senare (se <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 "Under uppstartssekvensen kan du se många meddelanden i formen <computeroutput>can't find <replaceable>something</replaceable> </computeroutput>, eller <computeroutput> <replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable> </computeroutput>, eller till och med <computeroutput>this driver release depends on <replaceable>något</replaceable> </computeroutput>. De flesta av de här meddelandena är harmlösa. Du ser dem för att kärnan för installationssystemet är byggd för att köras på datorer med många olika kringutrustningsenheter. Så klart, ingen dator kommer att ha alla möjliga kringutrustningsenheter, så operativsystemet kan klaga en hel del när den letar efter kringutrustning som du inte har. Du kan också se att systemet pausar en stund. Det händer när det väntar på att en enhet ska svara, och den enheten finns inte på ditt system. Om du tycker att tiden det tar att starta upp systemet är på tok för lång, kan du skapa en anpassad kärna senare (se <xref linkend=\"kernel-baking\"/>)." #. Tag: title #: boot-installer.xml:3292 @@ -3838,33 +2391,14 @@ msgstr "Felrapporterare" #. Tag: para #: boot-installer.xml:3293 #, 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. It lets you store system error " -"logs and configuration information from the installer to a floppy, or " -"download them in a web browser. 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 "" -"Om du kommer igenom den initiala uppstartsfasen men inte kan färdigställa " -"installationen, kan menyvalet för felrapportering vara till hjälp. Den låter " -"dig lagra felloggar från systemet och information om konfigurationen från " -"installeraren till en diskett, eller hämta dem i en webbläsare. Den " -"informationen kan innehålla ledtrådar till vad som gick fel och hur man " -"löser det. Om du skickar in en felrapport kan du bifoga den här " -"informationen i felrapporten." +msgid "If you get through the initial boot phase but cannot complete the install, the bug reporter menu choice may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them in a web browser. 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 "Om du kommer igenom den initiala uppstartsfasen men inte kan färdigställa installationen, kan menyvalet för felrapportering vara till hjälp. Den låter dig lagra felloggar från systemet och information om konfigurationen från installeraren till en diskett, eller hämta dem i en webbläsare. Den informationen kan innehålla ledtrådar till vad som gick fel och hur man löser det. Om du skickar in en felrapport kan du bifoga den här informationen i felrapporten." #. Tag: para #: boot-installer.xml:3304 #, no-c-format -msgid "" -"Other pertinent installation messages may be found in <filename>/var/log/</" -"filename> during the installation, and <filename>/var/log/installer/</" -"filename> after the computer has been booted into the installed system." -msgstr "" -"Andra relevanta installationsmeddelanden kan hittas i <filename>/var/log/</" -"filename> under installationen, och <filename>/var/log/installer/</filename> " -"efter datorn har startats om till det nyligen installerade systemet." +msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system." +msgstr "Andra relevanta installationsmeddelanden kan hittas i <filename>/var/log/</filename> under installationen, och <filename>/var/log/installer/</filename> efter datorn har startats om till det nyligen installerade systemet." #. Tag: title #: boot-installer.xml:3315 @@ -3875,39 +2409,20 @@ msgstr "Skicka installationsrapporter" #. Tag: para #: boot-installer.xml:3316 #, 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." -msgstr "" -"Om du fortfarande har problem, skicka in en installationsrapport. Vi " -"uppmuntrar att installationsrapporter skickas in även om installationen " -"lyckats, så att vi kan få så mycket information som möjligt på flest antal " -"olika hårdvarukonfigurationer." +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 "Om du fortfarande har problem, skicka in en installationsrapport. Vi uppmuntrar att installationsrapporter skickas in även om installationen lyckats, så att vi kan få så mycket information som möjligt på flest antal olika hårdvarukonfigurationer." #. Tag: para #: boot-installer.xml:3323 #, no-c-format -msgid "" -"If you have a working Debian system, the easiest 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 "" -"Om du har ett fungerande Debian-system är det enklaste sättet att skicka in " -"en installationsrapport att installera paketen installation-report och " -"reportbug (<command>apt-get install installation-report reportbug</command>) " -"och kör kommandot <command>reportbug installation-report</command>." +msgid "If you have a working Debian system, the easiest 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 "Om du har ett fungerande Debian-system är det enklaste sättet att skicka in en installationsrapport att installera paketen installation-report och reportbug (<command>apt-get install installation-report reportbug</command>) och kör kommandot <command>reportbug installation-report</command>." #. Tag: para #: boot-installer.xml:3330 #, 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" @@ -3941,19 +2456,12 @@ 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." -msgstr "" -"Använd den här mallen när du fyller i installationsrapporter och skicka " -"sedan rapporten som en felrapport mot pseudopaketet <classname>installation-" -"reports</classname>, genom att skicka det till <email>submit@bugs.debian." -"org</email> (skriv på engelska). <informalexample><screen>\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." +msgstr "" +"Använd den här mallen när du fyller i installationsrapporter och skicka sedan rapporten som en felrapport mot pseudopaketet <classname>installation-reports</classname>, genom att skicka det till <email>submit@bugs.debian.org</email> (skriv på engelska). <informalexample><screen>\n" "Package: installation-reports\n" "\n" -"Boot method: <Hur startade du upp installeraren? Cd? Diskett? Nätverk?" -">\n" +"Boot method: <Hur startade du upp installeraren? Cd? Diskett? Nätverk?>\n" "Image version: <Fyll i datum och var du fick tag på avbilden>\n" "Date: <Datum och tid för installationen>\n" "\n" @@ -3982,18 +2490,14 @@ msgstr "" "\n" "Comments/Problems:\n" "\n" -"<Beskrivning av installationen, i prosa och eventuella tankar, " -"kommentarer\n" +"<Beskrivning av installationen, i prosa och eventuella tankar, kommentarer\n" " och idéer du hade under installationen.>\n" -"</screen></informalexample> Beskriv i felrapporten vad problemet är, " -"inklusive de sista meddelandena från kärnan om problemet var att kärnan " -"hängde sig. Beskriv de steg du tog som slutade i att systemet fick problem." +"</screen></informalexample> Beskriv i felrapporten vad problemet är, inklusive de sista meddelandena från kärnan om problemet var att kärnan hängde sig. Beskriv de steg du tog som slutade i att systemet fick problem." #~ msgid "nettrom-2.3-3.armv4l.rpm" #~ msgstr "nettrom-2.3-3.armv4l.rpm" - #~ msgid "nettrom-2.3.3.bin" #~ msgstr "nettrom-2.3.3.bin" - #~ msgid "nettrom-2.3.3.bin.md5sum" #~ msgstr "nettrom-2.3.3.bin.md5sum" + diff --git a/po/sv/preparing.po b/po/sv/preparing.po index e85a414ae..cef510395 100644 --- a/po/sv/preparing.po +++ b/po/sv/preparing.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: installation guide 20051025 preparing\n" "POT-Creation-Date: 2006-03-02 09:59+0000\n" -"PO-Revision-Date: 2006-03-04 10:36+0100\n" +"PO-Revision-Date: 2006-03-11 10:24+0100\n" "Last-Translator: Daniel Nylander <po@danielnylander.se>\n" "Language-Team: Swedish <tp-sv@listor.tp-sv.se>\n" "MIME-Version: 1.0\n" @@ -1038,7 +1038,7 @@ msgstr "Partitionering i Tru64 UNIX" #: preparing.xml:982 #, no-c-format msgid "Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly known as OSF/1, uses the partitioning scheme similar to the BSD <quote>disk label</quote>, which allows for up to eight partitions per disk drive. The partitions are numbered <quote>1</quote> through to <quote>8</quote> in Linux and <quote>lettered</quote> <quote>a</quote> through to <quote>h</quote> in UNIX. Linux kernels 2.2 and higher always correspond <quote>1</quote> to <quote>a</quote>, <quote>2</quote> to <quote>b</quote> and so on. For example, <filename>rz0e</filename> in Tru64 UNIX would most likely be called <filename>sda5</filename> in Linux." -msgstr "" +msgstr "Tru64 UNIX, tidigare känd som Digital UNIX, som i sin tur är känd som OSF/1, använder ett partitioneringsschema liknande BSD <quote>disketikett</quote>, vilken tillåter upp till åtta partitioner per disk. Partitionerna numreras från <quote>1</quote> till <quote>8</quote> i Linux och <quote>bokstäverna</quote> <quote>a</quote> till <quote>h</quote> i UNIX. Linux 2.2-kärnor och högre korresponderar alltid <quote>1</quote> till <quote>a</quote>, <quote>2</quote> till <quote>b</quote> och så vidare. Till exempel, <filename>rz0e</filename> i Tru64 UNIX skulle sannolikt kallas för <filename>sda5</filename> i Linux." #. Tag: para #: preparing.xml:994 |