1 # German translations for live-boot package
2 # Copyright (C) 2006-2014 Daniel Baumann <mail@daniel-baumann.ch>
3 # This file is distributed under the same license as the live-boot package.
7 "Project-Id-Version: live-boot 4.0.0-1\n"
8 "POT-Creation-Date: 2014-08-27 19:52+0200\n"
9 "PO-Revision-Date: 2013-11-10 20:10+0900\n"
10 "Last-Translator: Carlos Zuferri <chals@altorricon.com>\n"
11 "Language-Team: none\n"
14 "Content-Type: text/plain; charset=ASCII\n"
15 "Content-Transfer-Encoding: 8bit\n"
16 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
19 #: en/live-boot.7:1 en/persistence.conf.5:1
25 #: en/live-boot.7:1 en/persistence.conf.5:1
31 #: en/live-boot.7:1 en/persistence.conf.5:1
37 #: en/live-boot.7:1 en/persistence.conf.5:1
39 msgid "Live Systems Project"
43 #: en/live-boot.7:3 en/persistence.conf.5:3
49 #: en/live-boot.7:6 en/persistence.conf.5:7
55 #: en/live-boot.7:28 en/persistence.conf.5:57
61 #: en/live-boot.7:154 en/persistence.conf.5:191
67 #: en/live-boot.7:158 en/persistence.conf.5:195
68 msgid "I<live-build>(7)"
72 #: en/live-boot.7:160 en/persistence.conf.5:197
73 msgid "I<live-config>(7)"
77 #: en/live-boot.7:162 en/persistence.conf.5:199
78 msgid "I<live-tools>(7)"
82 #: en/live-boot.7:163 en/persistence.conf.5:200
88 #: en/live-boot.7:165 en/persistence.conf.5:202
90 "More information about live-boot and the Live Systems project can be found "
91 "on the homepage at E<lt>I<http://live-systems.org/>E<gt> and in the manual "
92 "at E<lt>I<http://live-systems.org/manual/>E<gt>."
96 #: en/live-boot.7:166 en/persistence.conf.5:203
102 #: en/live-boot.7:168 en/persistence.conf.5:205
104 "Bugs can be reported by submitting a bugreport for the live-boot package in "
105 "the Bug Tracking System at E<lt>I<http://bugs.debian.org/>E<gt> or by "
106 "writing a mail to the Live Systems mailing list at E<lt>I<debian-live@lists."
111 #: en/live-boot.7:169 en/persistence.conf.5:206
117 #: en/live-boot.7:170 en/persistence.conf.5:207
119 "live-boot was written by Daniel Baumann E<lt>I<mail@daniel-baumann.ch>E<gt>."
123 #: en/persistence.conf.5:6
125 "B<persistence.conf> - Configuration file for persistence media in live-boot"
129 #: en/persistence.conf.5:13
131 "If live-boot probes a persistence volume with the label (or GPT name, or "
132 "file name, but from now on we will just say \"label\") \"persistence\", that "
133 "volume's persistence is fully customizable through the B<persistence.conf> "
134 "file stored on the root of its file system. Any such labeled volume must "
135 "have such a file, or it will be ignored."
139 #: en/persistence.conf.5:17
141 "The format of B<persistence.conf> allows empty lines and lines starting with "
142 "a \"#\" (used for comments), both which will be ignored. A so called "
143 "\"custom mount\" has the format:"
147 #: en/persistence.conf.5:20
148 msgid "I<DIR> [I<OPTION>]..."
152 #: en/persistence.conf.5:24
154 "which roughly translates to \"make I<DIR> persistence in the way described "
155 "by the list of I<OPTION>s\"."
159 #: en/persistence.conf.5:35
161 "For each custom mount I<DIR> must be an absolute path that cannot contain "
162 "white spaces or the special . and .. path components, and cannot be /live "
163 "(or any of its sub-directories). Once activated all changes (file deletion, "
164 "creation and modification) to I<DIR> on the live file system are stored "
165 "persistently into a path equivalent to I<DIR> on the persistence media, "
166 "called the source directory. The default way to achieve persistence is to "
167 "simply bind-mount the corresponding source directory to I<DIR>, but this can "
168 "be changed through the use of I<OPTION>s."
172 #: en/persistence.conf.5:48
174 "All custom mounts will be done in an order so that no two custom mounts can "
175 "\"hide\" each other. For instance, if we have the two I<DIR>:s /a and /a/b "
176 "it would always be the case that /a is mounted first, then /a/b. This "
177 "remains true no matter how the lines in B<persistence.conf> are ordered, or "
178 "if several B<persistence.conf> files on different persistence media are used "
179 "at the same time. However, it is forbidden for custom mounts to have their "
180 "source directory inside the source directory of another custom mount, so the "
181 "source directories that are auto-created by live-boot does not support "
182 "\"nested\" mounts like /a and /a/b on the same media. In this case you must "
183 "use the B<source> option (see below) to make sure that they are stored in "
184 "different source directories."
188 #: en/persistence.conf.5:56
190 "When a source directory doesn't exist on the persistence media for a certain "
191 "custom mount, it will be created automatically, and permissions and "
192 "ownership will be optimistically set according to I<DIR>. It will also be "
193 "bootstrapped by copying the contents of the I<DIR> into its source directory "
194 "on the persistence media. The bootstrapping will not happen when the B<link> "
195 "or B<union> options are used (see below)."
199 #: en/persistence.conf.5:60
201 "Custom mounts defined in B<persistence.conf> accept the following options in "
202 "a comma-separated list:"
206 #: en/persistence.conf.5:60
208 msgid "B<source>=I<PATH>"
212 #: en/persistence.conf.5:69
214 "When given, store the persistence changes into I<PATH> on the persistence "
215 "media. I<PATH> must be a relative path (with respect to the persistence "
216 "media root) that cannot contain white spaces or the special . or .. path "
217 "components, with the exception that it can be just . which means the "
218 "persistence media root. This option is mostly relevant if you want to nest "
219 "custom mounts, which otherwise would cause errors, or if you want to make "
220 "the whole media root available (similar to the now deprecated B<home-rw> "
221 "type of persistence)."
225 #: en/persistence.conf.5:72
227 "The following options are mutually exclusive (only the last given one will "
232 #: en/persistence.conf.5:72
238 #: en/persistence.conf.5:74
239 msgid "Bind-mount the source directory to I<DIR>. This is the default."
243 #: en/persistence.conf.5:74
249 #: en/persistence.conf.5:83
251 "Create the directory structure of the source directory on the persistence "
252 "media in I<DIR> and create symbolic links from the corresponding place in "
253 "I<DIR> to each file in the source directory. Existing files or directories "
254 "with the same name as any link will be overwritten. Note that deleting the "
255 "links in I<DIR> will only remove the link, not the corresponding file in the "
256 "source; removed links will reappear after a reboot. To permanently add or "
257 "delete a file one must do so directly in the source directory."
261 #: en/persistence.conf.5:91
263 "Effectively B<link> will make only files already in the source directory "
264 "persistent, not any other files in I<DIR>. These files must be manually "
265 "added to the source directory to make use of this option, and they will "
266 "appear in I<DIR> in addition to files already there. This option is useful "
267 "when only certain files need to be persistent, not the whole directory "
268 "they're in, e.g. some configuration files in a user's home directory."
272 #: en/persistence.conf.5:91
278 #: en/persistence.conf.5:101
280 "Save the rw branch of a union on the persistence media, so only the changes "
281 "are stored persistently. This can potentially reduce disk usage compared to "
282 "bind-mounts, and will not hide files added to the read-only media. One "
283 "caveat is that the union will use I<DIR> from the image's read-only file "
284 "system, not the real file system root, so files created after boot (e.g. by "
285 "live-config) will not appear in the union. This option will use the union "
286 "file system specified by live-boot's B<union> boot parameter, but is not "
287 "supported with B<union=unionmount>."
291 #: en/persistence.conf.5:102
297 #: en/persistence.conf.5:103
299 msgid "B</live/persistence>"
303 #: en/persistence.conf.5:109
305 "All persistence volumes will be mounted here (in a directory corresponding "
306 "to the device name). The B<persistence.conf> file can easily be edited "
307 "through this mount, as well as any source directories (which is especially "
308 "practical for custom mounts using the B<link> option)."
312 #: en/persistence.conf.5:110
318 #: en/persistence.conf.5:115
320 "Let's say we have a persistence volume I<VOL> with the a B<persistence.conf> "
321 "file containing the following four lines (numbered for ease of reference):"
325 #: en/persistence.conf.5:115 en/persistence.conf.5:129
331 #: en/persistence.conf.5:118
332 msgid "/home/user1 link,source=config-files/user1"
336 #: en/persistence.conf.5:118 en/persistence.conf.5:133
342 #: en/persistence.conf.5:121
343 msgid "/home/user2 link,source=config-files/user2"
347 #: en/persistence.conf.5:121 en/persistence.conf.5:137
353 #: en/persistence.conf.5:124
358 #: en/persistence.conf.5:124 en/persistence.conf.5:140
364 #: en/persistence.conf.5:127
369 #: en/persistence.conf.5:129
370 msgid "The corresponding source directories are:"
374 #: en/persistence.conf.5:133
376 "I<VOL>/config-files/user1 (but it would be I<VOL>/home/user1 without the "
381 #: en/persistence.conf.5:137
383 "I<VOL>/config-files/user2 (but it would be I<VOL>/home/user2 without the "
388 #: en/persistence.conf.5:140
393 #: en/persistence.conf.5:143
398 #: en/persistence.conf.5:146
400 "It was necessary to set the B<source> options for 1 and 2, since they "
401 "otherwise would become nested with 3's source, which is invalid."
405 #: en/persistence.conf.5:151
407 "Line 3 will be taken care of before line 1 and 2 in order to prevent custom "
408 "mounts 1 and 2 from being hidden by 3. When line 3 is handled, I<VOL>/home "
409 "is simply bind-mounted on /home. To illustrate what happens for lines 1 and "
410 "2, let's say that the following files exist:"
414 #: en/persistence.conf.5:151
420 #: en/persistence.conf.5:154
421 msgid "I<VOL>/config-files/user1/.emacs"
425 #: en/persistence.conf.5:154
431 #: en/persistence.conf.5:157
432 msgid "I<VOL>/config-files/user2/.bashrc"
436 #: en/persistence.conf.5:157
442 #: en/persistence.conf.5:160
443 msgid "I<VOL>/config-files/user2/.ssh/config"
447 #: en/persistence.conf.5:162
448 msgid "Then the following links and directories will be created:"
452 #: en/persistence.conf.5:162 en/persistence.conf.5:165
453 #: en/persistence.conf.5:171
459 #: en/persistence.conf.5:165
460 msgid "/home/user1/.emacs -E<gt> I<VOL>/config-files/user1/.emacs (from a)"
464 #: en/persistence.conf.5:168
465 msgid "/home/user2/.bashrc -E<gt> I<VOL>/config-files/user2/.bashrc (from b)"
469 #: en/persistence.conf.5:168
475 #: en/persistence.conf.5:171
476 msgid "/homea/user2/.ssh (from c)"
480 #: en/persistence.conf.5:175
482 "/home/user2/.ssh/config -E<gt> I<VOL>/config-files/user2/.ssh/config (from c)"
486 #: en/persistence.conf.5:181
488 "One could argue, though, that lines 1 and 2 in the example B<persistence."
489 "conf> file above are unnecessary since line 3 already would make all of /"
490 "home persistent. The B<link> option is intended for situations where you "
491 "don't want a complete directory to be persistent, only certain files in it "
492 "or its sub-directories."
496 #: en/persistence.conf.5:190
498 "Line 4 can be mounted at any time since its I<DIR> (and source directory) is "
499 "completely disjoint from all the other custom mounts. When mounted, I<VOL>/"
500 "usr will be the rw branch due to the B<union> option, and will only contain "
501 "the difference compared to the underlying read-only file system. Hence "
502 "packages could be installed into /usr with great space-wise efficiency "
503 "compared to bind-mounts, since in the latter case all of /usr would have to "
504 "be copied into I<VOL>/usr during the initial bootstrap."
508 #: en/persistence.conf.5:193
509 msgid "I<live-boot>(7)"