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
|
#
# 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.
#
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm 1.7.0-2\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: 2004-10-31 00:32+0900\n"
"Last-Translator: Hideki Yamane <henrich@samba.gr.jp>\n"
"Language-Team: Japanese <debian-japanese@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=EUC-JP\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: note
#. Description
#: ../mdadm.templates:1001
msgid "Initialise the superblock if you reuse hard disks"
msgstr "�ϡ��ɥǥ�����������Ѥ������ superblock ���������Ƥ�������"
#. 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 ""
"�ٹ�! �����Υ��ȡ���ˤ�äưۤʤ� RAID ���쥤��Ǥ� md superblock ���ݻ�"
"���Ƥ���ϡ��ɥǥ�������ȤäƤ����硢��ư��ư��ǽ��ͭ���ˤ������� "
"superblock ���Ǿ���뤳�Ȥ���ɬ�ספǤ���"
#. Type: note
#. Description
#: ../mdadm.templates:1003
#, fuzzy
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 ""
"�����Ԥ��ˤϡ�RAID �ǥХ�����ưŪ�˵�ư������ superblock ���Ǿ��"
"�ޤ� (mdadm --zero-superblock /dev/xxx)�� �����ơ���ư��ư��ǽ��ͭ���ˤ��뤿"
"��ˤ� 'dpkg-reconfigure mdadm' ���ޥ�ɤ����ѤǤ��ޤ���"
#. 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 "RAID �ǥХ�����ưŪ�˵�ư���ޤ���?"
#. 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 "RAID �ƻ�ǡ�����ư���ޤ���?"
#. 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 "�ǡ��������Τ������밸��:"
#. 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 ""
"RAID ���쥤�Υ��ơ��������Ѳ��������˥�����Τ�������桼���Υ�륢��"
"�쥹�����Ϥ��Ƥ���������"
#~ 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 ""
#~ "RAID �ǥХ�������ưŪ�˵�ư����褦�ˤ���ȡ������ƥ൯ư�������Ƥ� RAID "
#~ "�ǥХ��������Ф��졢��ưŪ�˹�������ޤ������Υ��ץ����� md �ɥ饤�Ф���"
#~ "���塼��Ȥ��ƥ���ѥ��뤵��Ƥ�����Τߤ����Ѥ��ޤ��������ͥ���Ȥ߹���"
#~ "�ǥ���ѥ��뤷�Ƥ�����硢�����ƥ൯ư���˥����ͥ�ˤ�äƼ�ư��ư���¹Ԥ�"
#~ "���Τǡ����Υ��ץ����Ǥ�����ϤǤ��ޤ���"
#~ 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 ""
#~ "RAID �ƻ�ǡ����ư��Ƥ����硢RAID ���쥤��°���Ƥ���ǥ��������ξ�"
#~ "���뤫���餫����ͳ���Ѳ������ݤ˥������Τ������ޤ���"
|
