summaryrefslogtreecommitdiff
path: root/debian/po/sv.po
blob: 89eb7d801f27b69a9dc624c2403badd35bee4436 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
# Translators, if you are not familiar with the PO format, gettext
# documentation is worth reading, especially sections dedicated to
# this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
# Some information specific to po-debconf are available at
# /usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
# Developers do not need to manually edit POT or PO files.
# , fuzzy
#
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm 1.12.0-1\n"
"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n"
"POT-Creation-Date: 2006-09-13 10:30+0200\n"
"PO-Revision-Date: 2006-06-29 22:06+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"
"Content-Type: text/plain; charset=iso-8859-1\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: string
#. Description
#: ../mdadm.templates:1001
#, fuzzy
msgid "MD arrays needed for the root filesystem:"
msgstr "RAID-kedjor som beh?vs f?r rotfilsystemet:"

#. Type: string
#. Description
#: ../mdadm.templates:1001
msgid "${msg}"
msgstr ""

#. Type: string
#. Description
#: ../mdadm.templates:1001
#, fuzzy
msgid ""
"Please enter a space-separated list of devices, 'all', or 'none'. You may "
"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"."
msgstr ""
"Ange en blankstegsseparerad lista p? enheter, eller \"all\". Du kan utesluta "
"den inledande \"/dev\" och bara ange t.ex. \"md0 md1\"."

#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid "for internal use - only the long description is needed."
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:2001
#, fuzzy
msgid ""
"If your system has its root filesystem on an MD array (RAID), it needs to be "
"started early during the boot sequence. If your root filesystem is on a "
"logical volume (LVM), which is on MD, all constituent arrays need to be "
"started."
msgstr ""
"Om ditt system har sitt rotfilsystem p? en RAID-volym beh?ver den startas "
"upp tidigt i uppstartssekvensen. Om ditt rotfilsystem finns p? en logisk "
"volym (LVM), vilket ?r p? RAID beh?ver alla best?ende kedjor att startas."

#. Type: text
#. Description
#: ../mdadm.templates:2001
#, fuzzy
msgid ""
"If you know exactly which arrays are needed to bring up the root filesystem, "
"and you want to postpone starting all other arrays to a later point in the "
"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to "
"simply start all available arrays."
msgstr ""
"Om du vet exakt vilka kedjor som beh?vs f?r att ta upp rotfilsystemet, ange "
"dem h?r. Alternativt, ange \"all\" f?r att helt enkelt starta alla tillg?"
"ngliga kedjor. Om du inte beh?ver eller vill starta n?gra kedjor f?r "
"rotfilsystemet, l?mna svaret blankt h?r (eller ange \"none\")."

#. Type: text
#. Description
#: ../mdadm.templates:2001
msgid ""
"If you do not need or want to start any arrays for the root filesystem, "
"leave the answer blank (or enter 'none'). This may be the case if you are "
"using kernel autostart or do not need any arrays to boot."
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:3001
msgid "An error occurred: device node does not exist"
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:4001
msgid "An error occurred: not a block device"
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:5001
msgid "An error occurred: not an MD array"
msgstr ""

#. Type: text
#. Description
#: ../mdadm.templates:6001
msgid "An error occurred: array not listed in mdadm.conf file"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid "Proceed with starting arrays not listed in mdadm.conf?"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid ""
"The array you have specified (${array}) is not listed in the configuration "
"file ${config}. Therefore it cannot be started during boot, unless you "
"correct the configuration file and recreate the initial ramdisk."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid ""
"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend "
"to continue."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:7001
msgid ""
"This warning is only relevant if you need arrays to be started from the "
"initial ramdisk to be able to boot. If you use kernel autostarting, or do "
"not need any arrays to be started as early as the initial ramdisk is loaded, "
"you can simply continue. Alternatively, choose not to continue and enter "
"'none' when prompted which arrays to start from the initial ramdisk."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:8001
#, fuzzy
msgid "Do you want to start MD arrays automatically?"
msgstr "Vill du starta RAID-enheter automatiskt?"

#. Type: boolean
#. Description
#: ../mdadm.templates:8001
#, fuzzy
msgid ""
"Once the base system has come up, mdadm can start all MD arrays (RAIDs) "
"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless "
"you have compiled multi-device (MD) support into the kernel and marked all "
"partitions part of MD arrays with type 0xfd (as those and only those will be "
"started automatically by the kernel), this is probably what you want."
msgstr ""
"N?r grundsystemet har kommit upp kan mdadm starta alla RAID-enheter som den "
"kan hitta och som inte har startats. S?vida du har byggt in RAID-st?d i k?"
"rnan (vilket inneb?r att alla RAID-kedjor startas upp automatiskt), detta ?r "
"antagligen n?got du vill g?ra."

#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid ""
"If your kernel supports it (>> 2.6.14), mdadm can periodically check the "
"redundancy of your MD arrays (RAIDs). This may be a resource-intensive "
"process, depending on your setup, but it could help prevent rare cases of "
"data loss. Note that this is a read-only check unless errors are found; if "
"errors are found, mdadm will try to correct them, which may result in write "
"access to the media."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:9001
msgid ""
"The default, if turned on, is to run the checks on the first Sunday of every "
"month at 01:06 o'clock."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:10001
#, fuzzy
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Vil du starta RAID-?vervakningsdemonen?"

#. Type: boolean
#. Description
#: ../mdadm.templates:10001
#, fuzzy
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure). You probably want to enable it."
msgstr ""
"RAID-?vervakningsdemonen skickar e-postnotifieringar f?r viktiga RAID-h?"
"ndelser (s?som ett diskfel). Du vill antagligen aktivera denna funktion."

#. Type: string
#. Description
#: ../mdadm.templates:11001
msgid "Recipient for email notifications:"
msgstr "Mottagare f?r e-postnotifieringar:"

#. Type: string
#. Description
#: ../mdadm.templates:11001
#, fuzzy
msgid ""
"Please enter the email address of the user who should get the email "
"notification for important MD events."
msgstr ""
"Ange e-postadressen till den anv?ndare som ska ta emot e-postnotifieringar f?"
"r dessa viktiga RAID-h?ndelser."

#~ msgid "Initialise the superblock if you reuse hard disks"
#~ msgstr "Initiera superblocket om du ?teranv?nder h?rddiskar"

#~ msgid ""
#~ "WARNING! If you are using hard disks which have RAID superblocks from "
#~ "earlier installations in different RAID arrays, you MUST zero each "
#~ "superblock *before* activating the autostart feature."
#~ msgstr ""
#~ "VARNING! Om du anv?nder h?rddiskar som har RAID-superblock fr?n tidigare "
#~ "installationer i andra RAID-kedjor M?STE du nollst?lla superblocket "
#~ "*innan* du aktiverar autostartfunktionen."

#~ msgid ""
#~ "To do this, do not start the RAID devices automatically. First, zero the "
#~ "superblock (mdadm --zero-superblock /dev/mdX). Next, use `dpkg-"
#~ "reconfigure mdadm` to reactivate the autostart feature."
#~ msgstr ""
#~ "F?r att g?ra detta, starta inte RAID-enheterna automatiskt. Nollst?ll f?"
#~ "rst superblocket (mdadm --zero-superblock /dev/mdX), anv?nd sedan \"dpkg-"
#~ "reconfigure mdadm\" f?r att ?teraktivera autostartfunktionen."

#~ msgid ""
#~ "You have the option to start all other arrays (those not needed for the "
#~ "root filesystem) later in the boot sequence. Doing so will give you "
#~ "greater control over the arrays with the mdadm configuration file. "
#~ "Starting all arrays at boot-time may be safer though."
#~ msgstr ""
#~ "Du har alternativet att starta alla andra kedjor (de som inte beh?vs f?r "
#~ "rotfilsystemet) senare i uppstartssekvensen. Att g?ra det ger dig st?rre "
#~ "kontroll ?ver kedjorna med mdadms konfigurationsfil. Starta alla kedjor "
#~ "vid uppstart kan dock vara s?krare."

#~ msgid ""
#~ "If RAID devices are started automatically, all RAID devices are "
#~ "discovered and assembled automatically at system startup. This option "
#~ "should only be used if the md driver is compiled as a module. If it is "
#~ "compiled into your kernel, the automatic startup will be performed at "
#~ "boot time by the kernel and therefore you should not choose this option."
#~ msgstr ""
#~ "Om RAID-enheter startas automatiskt kommer alla RAID-enheter att uppt?"
#~ "ckas och s?ttas ihop automatiskt vid systemets uppstart. Denna funktion b?"
#~ "r bara anv?ndas om md-drivaren ?r byggd som en modul. Om den ?r inbyggd i "
#~ "din k?rna kommer den automatiska uppstarten att g?ras av k?rnan vid "
#~ "systemets uppstart och d?rf?r b?r du inte v?lja denna funktion h?r."

#~ msgid ""
#~ "When the RAID monitor daemon runs, email notifications are sent when a "
#~ "disk belonging to a RAID array fails or changes its status for some "
#~ "reason."
#~ msgstr ""
#~ "N?r RAID-?vervakningsdaemonen k?r kommer e-postnotifieringar att skickas "
#~ "n?r en disk som tillh?r en RAID-array fallerar eller ?ndrar status av n?"
#~ "gon anledning."