[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

mdadm 4.1-6: Please update debconf PO translation for the package mdadm



Hi,

You were so kind and translated debconf questions for mdadm in the
past. Some questions have changed. Would you please update your
translation? 

Please submit the updated file as bug against mdadm, preferably
before:

    Tue, 13 Oct 2020 05:09:36 -0700.

Thanks so much!   

Kind regards
Felix Lechner

# Danish translation mdadm.
# Copyright (C) 2011 mdadm & nedenstående oversættere.
# This file is distributed under the same license as the mdadm package.
# Joe Hansen <joedalton2@yahoo.dk>, 2011.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2011-04-03 17:30+01:00\n"
"Last-Translator: Joe Hansen <joedalton2@yahoo.dk>\n"
"Language-Team: Danish <debian-l10n-danish@lists.debian.org> \n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr "Skal mdadm køre månedlig redundanskontrol af MD arrays?"

#. Type: boolean
#. Description
#: ../mdadm.templates:2001
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 ""
"Hvis kernen understøtter det (versioner større end 2.6.14), kan mdadm "
"periodisk kontrollere redundansen på MD arrays (RAID'er). Det kan være en "
"ressourcekrævende proces, afhængig af den lokale opsætning, men det kan "
"hjælpe med at forhindre at du i sjældne tilfælde får datatab. Bemærk at "
"dette er en skrivebeskyttet kontrol med mindre at der findes fejl; hvis der "
"registreres fejl vil mdadm forsøge at rette dem, hvilket kan medføre "
"skriveadgang til mediet."

#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"Standarden - hvis aktiveret - er at kontrollere på den første søndag i hver "
"måned klokken 01:06."

#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""

#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Ønsker du at starte MD-overvågningsdæmonen?"

#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"MD-overvågningsdæmonem (RAID) sender e-post-påmindelser udløst af vigtige MD-"
"hændelser (såsom en diskfejl)."

#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Aktivering af denne indstilling anbefales."

#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Modtager af e-post-påmindelser:"

#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Indtast venligst e-post-adressen på brugeren, som skal modtage e-post-"
"påmindelser for vigtige MD-hændelser."

#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "MD arrays krævet for rodfilsystemet:"

#~ 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 ""
#~ "Indtast venligst »all«, »none« eller en mellemrumsadskilt liste af "
#~ "enheder såsom »md0 md1« eller »md/1 md/d0« (det foranstillede »/dev/« kan "
#~ "udelades)."

#~ msgid "for internal use - only the long description is needed."
#~ msgstr "for intern brug - kun den lange beskrivelse er krævet."

#~ 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 ""
#~ "Hvis systemets rodfilsystem er placeret på en MD-array (RAID), skal det "
#~ "startes tidligt under opstartssekvensen. Hvis den er placeret på en "
#~ "logisk diskenhed (LVM), som er på MD, skal alle indgående arrays startes."

#~ 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 ""
#~ "Hvis du ved præcis hvilke arrays som er krævet, for at få rodfilsystemet "
#~ "op, og du ønsker at udsætte start af alle andre arrays til et senere "
#~ "tidspunkt i opstartssekvensen, så indtast her de arrays som skal startes. "
#~ "Alternativt kan du indtaste »all« for at starte alle tilgængelige arrays."

#~ 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 ""
#~ "Hvis du ikke har brug for eller ønsker at starte nogen arrays for "
#~ "rodfilsystemet, så efterlad svaret tomt (eller indtast »none«). Dette kan "
#~ "være tilfældet, hvis du bruger automatisk start af kernen eller ikke skal "
#~ "bruge arrays til at starte op med."

#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Der opstod en fejl: Enhedsknude findes ikke"

#~ msgid "An error occurred: not a block device"
#~ msgstr "Der opstod en fejl: Ikke en blokenhed"

#~ msgid "An error occurred: not an MD array"
#~ msgstr "Der opstod en fejl: Ikke en MD array"

#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr "Der opstod en fejl: Array er ikke anført i mdadm.conf-filen"

#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "Start arrays er ikke anført i mdadm.conf?"

#~ 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 ""
#~ "Den angivne array (${array}) er ikke anført i konfigurationsfilen "
#~ "(${config}). Den kan derfor ikke startes under opstarten, med mindre du "
#~ "retter i konfigurationsfilen og gendanner den oprindleige ramdisk."

#~ 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 ""
#~ "Denne advarsel er kun relevant hvis du skal have arrays til at blive "
#~ "startet fra den oprindelige ramdisk for at kunne starte op. Hvis du "
#~ "bruger den automatiske opstart i kernen, eller ikke skal bruge at arrays "
#~ "startes så tidligt som den oprindelige ramdisk indlæses, så kan du bare "
#~ "fortsætte. Alternativt så vælg at fortsætte og indtaste »none« når du "
#~ "bliver spurgt om hvilke arrays, der skal startes fra den oprindelige "
#~ "ramdisk."

Reply to: