summaryrefslogtreecommitdiff
path: root/debian/po/nl.po
blob: 1a9914a6db6be2bb7696b299e39db0e7e045e584 (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
# translation of mdadm_2.5.2-2.po to Dutch
# translation of mdadm_nl.po to Dutch
#
#    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.
# Frans Pop <aragorn@tiscali.nl>, 2005, 2006.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm_2.5.2-2\n"
"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n"
"POT-Creation-Date: 2006-08-21 00:28+0100\n"
"PO-Revision-Date: 2006-07-05 17:30+0200\n"
"Last-Translator: Frans Pop <aragorn@tiscali.nl>\n"
"Language-Team: Dutch <debian-l10n-dutch@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.9.1\n"

#. Type: string
#. Description
#: ../mdadm.templates:1001
#, fuzzy
msgid "MD arrays needed for the root filesystem:"
msgstr "Voor het basisbestandssysteem benodigde RAID-reeksen:"

#. 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 ""
"Geef de apparaatbestanden (gescheiden met spaties) of 'all' in. U kunt "
"volstaan met het ingeven van bijvoorbeeld \"md0 md1\" (en dus '/dev/...' "
"weglaten)."

#. Type: text
#. Description
#: ../mdadm.templates:2001
#, fuzzy
msgid ""
"If your system has its root filesystem on a MD volume, 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 ""
"Als het basisbestandssysteem van uw systeem zich op een RAID-volume bevindt, "
"dient dit vroeg in de opstartcyclus geactiveerd te worden. Als uw "
"basisbestandssysteem zich op een logisch volume (LVM) op RAID bevindt, "
"dienen alle betrokken reeksen geactiveerd te worden."

#. 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. If you do not need or want to start any "
"arrays for the root filesystem, leave the answer blank (or enter 'none')."
msgstr ""
"Als u exact weet welke reeksen nodig zijn om het basisbestandssysteem te "
"activeren, geef deze dan hier in. Als alternatief kunt u 'all' opgeven wat "
"als resultaat heeft dat alle reeksen geactiveerd zullen worden. Als u geen "
"reeksen hoeft of wenst te activeren voor het basisbestandssysteem, laat dan "
"het antwoord leeg (of geef 'none' in)."

#. 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 a 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:8001
#, fuzzy
msgid "Do you want to start MD devices automatically?"
msgstr "RAID-apparaten automatisch starten?"

#. Type: boolean
#. Description
#: ../mdadm.templates:8001
#, fuzzy
msgid ""
"Once the base system has come up, mdadm can start all MD devices specified "
"in /etc/mdadm/mdadm.conf, which have not yet been started. Unless you have "
"compiled MD support into the kernel (in which case all MD arrays with "
"partitions of type 0xfd (and only those) are started automatically anyway), "
"this is probably what you want."
msgstr ""
"Nadat het basissysteem eenmaal is opgestart, kan mdadm zorg dragen voor het "
"activeren van alle RAID-apparaten die nog niet zijn gestart. "
"Normaalgesproken zal u deze optie willen selecteren, eventueel tenzij uw "
"kernel is gecompileerd met niet-modulaire RAID-ondersteuning (in dat geval "
"worden alle RAID-reeksen sowieso automatisch gestart)."

#. 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 devices. 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 "Wilt u de achtergronddienst voor de RAID-monitor starten?"

#. Type: boolean
#. Description
#: ../mdadm.templates:10001
#, fuzzy
msgid ""
"The MD monitor daemon sends email notifications in response to important MD "
"events (such as a disk failure). You probably want to enable it."
msgstr ""
"De achtergronddienst voor de RAID-monitor stuurt per mail berichten bij "
"belangrijke gebeurtenissen die betrekking hebben op RAID (zoals een falende "
"harde schijf). Aangeraden wordt deze in te schakelen."

#. Type: string
#. Description
#: ../mdadm.templates:11001
msgid "Recipient for email notifications:"
msgstr "Adres voor mailberichten:"

#. Type: string
#. Description
#: ../mdadm.templates:11001
#, fuzzy
msgid ""
"Please enter the email address of the user who should get the email "
"notification for these important MD events."
msgstr ""
"Geef het mailadres in van de gebruiker die een mailbericht dient te "
"ontvangen voor belangrijke gebeurtenissen met betrekking tot RAID."

#~ msgid "Initialise the superblock if you reuse hard disks"
#~ msgstr "Superblok initialiseren als u harde schijven hergebruikt?"

#~ 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 ""
#~ "Waarschuwing! Als u harde schijven gebruikt die een RAID-superblok "
#~ "bevatten van een eerdere installatie in een andere RAID-reeks, dan MOET u "
#~ "het superblok overschrijven met nullen vóórdat u de \"autostart\"-optie "
#~ "activeert."

#~ 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 ""
#~ "U kunt dit doen door RAID-apparaten nu niet automatisch te laten starten. "
#~ "Overschrijf eerst het superblok met nullen ('mdadm --zero-superblock /dev/"
#~ "mdX'). Gebruik daarna 'dpkg-reconfigure mdadm' om de \"autostart\"-optie "
#~ "te activeren."

#~ 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 ""
#~ "U heeft de optie om alle andere reeksen (die niet benodigd zijn voor het "
#~ "basisbestandssysteem) later in de opstartcyclus te activeren. Dit geeft u "
#~ "meer controle over de reeksen met het mdadm configuratiebestand. Het is "
#~ "echter mogelijk veiliger om alle reeksen tijdens het opstarten van het "
#~ "systeem te activeren."