diff options
Diffstat (limited to 'debian/po/templates.pot')
-rw-r--r-- | debian/po/templates.pot | 162 |
1 files changed, 162 insertions, 0 deletions
diff --git a/debian/po/templates.pot b/debian/po/templates.pot new file mode 100644 index 00000000..e9d5d10d --- /dev/null +++ b/debian/po/templates.pot @@ -0,0 +1,162 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER +# This file is distributed under the same license as the PACKAGE package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\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: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=CHARSET\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: note +#. Description +#: ../mdadm.templates:1001 +msgid "Initialise the superblock if you reuse hard disks" +msgstr "" + +#. Type: note +#. Description +#: ../mdadm.templates:1002 +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 "" + +#. 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 "" + +#. 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 +msgid "Do you want to start RAID devices automatically?" +msgstr "" + +#. 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 +msgid "Do you want to start the RAID monitoring daemon?" +msgstr "" + +#. 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 +msgid "Recipient for email notifications:" +msgstr "" + +#. Type: string +#. Description +#: ../mdadm.templates:6002 +msgid "" +"Please enter the email address of the user who should get the email " +"notification for these important RAID events." +msgstr "" |