diff options
Diffstat (limited to 'debian/po/templates.pot')
-rw-r--r-- | debian/po/templates.pot | 176 |
1 files changed, 176 insertions, 0 deletions
diff --git a/debian/po/templates.pot b/debian/po/templates.pot new file mode 100644 index 00000000..beb000aa --- /dev/null +++ b/debian/po/templates.pot @@ -0,0 +1,176 @@ +# 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: mdadm\n" +"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n" +"POT-Creation-Date: 2012-05-22 00:50+0100\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" +"Language: \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=CHARSET\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: string +#. Description +#: ../mdadm.templates:2001 +msgid "MD arrays needed for the root file system:" +msgstr "" + +#. Type: string +#. Description +#: ../mdadm.templates:2001 +msgid "" +"Please enter 'all', 'none', or a space-separated list of devices such as " +"'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)." +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "for internal use - only the long description is needed." +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "" +"If the system's root file system is located on an MD array (RAID), it needs " +"to be started early during the boot sequence. If it is located on a logical " +"volume (LVM), which is on MD, all constituent arrays need to be started." +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "" +"If you know exactly which arrays are needed to bring up the root file " +"system, 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 "" + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "" +"If you do not need or want to start any arrays for the root file system, " +"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:4001 +msgid "An error occurred: device node does not exist" +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not a block device" +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: not an MD array" +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:7001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Start arrays not listed in mdadm.conf?" +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "" +"The specified array (${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:8001 +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:10001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "" +"If the kernel supports it (versions greater than 2.6.14), mdadm can " +"periodically check the redundancy of MD arrays (RAIDs). This may be a " +"resource-intensive process, depending on the local 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:10001 +msgid "" +"The default, if turned on, is to check on the first Sunday of every month at " +"01:06." +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:11001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:11001 +msgid "" +"The MD (RAID) monitor daemon sends email notifications in response to " +"important MD events (such as a disk failure)." +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:11001 +msgid "Enabling this option is recommended." +msgstr "" + +#. Type: string +#. Description +#: ../mdadm.templates:12001 +msgid "Recipient for email notifications:" +msgstr "" + +#. Type: string +#. Description +#: ../mdadm.templates:12001 +msgid "" +"Please enter the email address of the user who should get the email " +"notifications for important MD events." +msgstr "" |