diff options
author | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-07-08 22:24:52 +0000 |
---|---|---|
committer | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-07-08 22:24:52 +0000 |
commit | 724cca90e642a6bfbdd212dbf9b838187b27267e (patch) | |
tree | b852ad629769e0c9738f7170eb9c861f4be25bec /debian/po/nl.po | |
parent | c1aba7fa922cc2762f4044efb5fb574981a71703 (diff) |
Load newtrunk into mdadm/trunk.
Diffstat (limited to 'debian/po/nl.po')
-rw-r--r-- | debian/po/nl.po | 208 |
1 files changed, 208 insertions, 0 deletions
diff --git a/debian/po/nl.po b/debian/po/nl.po new file mode 100644 index 00000000..10512196 --- /dev/null +++ b/debian/po/nl.po @@ -0,0 +1,208 @@ +# 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. +# +msgid "" +msgstr "" +"Project-Id-Version: mdadm_nl\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-07-07 17:30+0200\n" +"PO-Revision-Date: 2005-09-19 19:00+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: note +#. Description +#: ../mdadm.templates:1001 +msgid "Initialise the superblock if you reuse hard disks" +msgstr "Superblok initialiseren als u harde schijven hergebruikt" + +#. Type: note +#. Description +#: ../mdadm.templates:1002 +#, fuzzy +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 md-superblok bevatten " +"van een eerdere installatie in een andere RAID-reeks, dan MOET u het " +"superblok overschrijven met nullen voordat u de \"autostart\"-optie " +"activeert." + +#. Type: note +#. Description +#: ../mdadm.templates:1003 +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." + +#. Type: note +#. Description +#: ../mdadm.templates:1004 +msgid "" +"If you manage your RAIDs otherwise (e.g. EVMS), either disable autostart, or " +"ensure that /etc/mdadm/mdadm.conf only lists those arrays you want to start " +"by mdadm." +msgstr "" + +#. Type: string +#. Description +#: ../mdadm.templates:2001 +msgid "RAID arrays needed for the root filesystem:" +msgstr "" + +#. Type: string +#. Description +#: ../mdadm.templates:2002 +msgid "" +"If your system has its root filesystem on a RAID volume, it needs to be " +"started early during the boot sequence. If your root filesystem is on a " +"logical volume (LVM), which is on RAID, all constituent arrays need to be " +"started." +msgstr "" + +#. Type: string +#. Description +#: ../mdadm.templates:2003 +msgid "" +"If you know exactly which arrays are needed to bring up the root filesystem, " +"enter them 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 "" + +#. Type: string +#. Description +#: ../mdadm.templates:2004 +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 "" + +#. Type: string +#. Description +#: ../mdadm.templates:2005 +msgid "" +"Please enter a space-separated list of devices, or 'all'. You may omit the " +"leading '/dev/' and just enter e.g. \"md0 md1\"." +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:3001 +#, fuzzy +msgid "Do you want to start RAID devices automatically?" +msgstr "Wilt u de RAID-apparaten automatisch starten?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:3002 +msgid "" +"Once the base system has come up, mdadm can start all RAID devices specified " +"in /etc/mdadm/mdadm.conf, which have not yet been started. Unless you have " +"compiled RAID support into the kernel (in which case all RAID arrays with " +"partitions of type 0xfd (and only those) are started automatically anyway), " +"this is probably what you want." +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:4001 +msgid "Should mdadm run monthly parity checks of the RAID arrays?" +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:4002 +msgid "" +"If your kernel supports it (>> 2.6.14), mdadm can periodically check the " +"parity of your RAID devices. This may be a resource-intensive process, " +"depending on your setup, but it could help prevent rare cases of data loss." +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:4003 +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:5001 +#, fuzzy +msgid "Do you want to start the RAID monitoring daemon?" +msgstr "Wilt u de achtergronddienst voor de RAID-monitor starten?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:5002 +msgid "" +"The RAID monitor daemon sends email notifications in response to important " +"RAID events (such as a disk failure). You probably want to enable it." +msgstr "" + +#. Type: string +#. Description +#: ../mdadm.templates:6001 +#, fuzzy +msgid "Recipient for email notifications:" +msgstr "Adres voor mailberichten van achtergronddienst:" + +#. Type: string +#. Description +#: ../mdadm.templates:6002 +#, fuzzy +msgid "" +"Please enter the email address of the user who should get the email " +"notification for these important RAID events." +msgstr "" +"Geef het mailadres in van de gebruiker die een mailbericht dient te " +"ontvangen als de status van een RAID-reeks wijzigt." + +#~ 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 "" +#~ "Als RAID-apparaten automatisch worden gestart, worden alle RAID-apparaten " +#~ "tijdens het opstarten van het systeem automatisch gedetecteerd en " +#~ "samengesteld. Deze optie dient alleen te worden gebruikt als het md-" +#~ "stuurprogramma als module is gecompileerd. Als het stuurprogramma in de " +#~ "kernel is gecompileerd, wordt de automatische detectie verzorgd door de " +#~ "kernel en dient deze optie dus niet te worden geselecteerd." + +#~ 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 "" +#~ "Als de achtergronddienst voor de RAID-monitor actief is, worden " +#~ "mailberichten gestuurd als een harde schijf die deel uitmaakt van een " +#~ "RAID-reeks het begeeft of de status ervan wijzigt." |