1 # German translations for live-boot package
2 # Copyright (C) 2006-2012 Daniel Baumann <daniel@debian.org>
3 # This file is distributed under the same license as the live-boot package.
7 "Project-Id-Version: live-boot 3.0~b6-1\n"
8 "POT-Creation-Date: 2012-10-02 10:38+0300\n"
9 "PO-Revision-Date: 2012-04-08 22:48+0300\n"
10 "Last-Translator: Daniel Baumann <daniel@debian.org>\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 "Debian Live 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:156 en/persistence.conf.5:191
67 #: en/live-boot.7:160 en/persistence.conf.5:195
68 msgid "I<live-build>(7)"
72 #: en/live-boot.7:162 en/persistence.conf.5:197
73 msgid "I<live-config>(7)"
77 #: en/live-boot.7:164 en/persistence.conf.5:199
78 msgid "I<live-tools>(7)"
82 #: en/live-boot.7:165 en/persistence.conf.5:200
88 #: en/live-boot.7:167 en/persistence.conf.5:204
90 "More information about live-boot and the Debian Live project can be found on "
91 "the homepage at E<lt>I<http://live.debian.net/>E<gt> and in the manual at "
92 "E<lt>I<http://live.debian.net/manual/>E<gt>."
96 #: en/live-boot.7:168 en/persistence.conf.5:205
102 #: en/live-boot.7:170 en/persistence.conf.5:210
104 "Bugs can be reported by submitting a bugreport for the live-boot package in "
105 "the Debian Bug Tracking System at E<lt>I<http://bugs.debian.org/>E<gt> or by "
106 "writing a mail to the Debian Live mailing list at E<lt>I<debian-live@lists."
111 #: en/live-boot.7:171 en/persistence.conf.5:211
117 #: en/persistence.conf.5:6
119 "B<persistence.conf> - Configuration file for persistence media in live-boot"
123 #: en/persistence.conf.5:13
125 "If live-boot probes a persistence volume with the label (or GPT name, or "
126 "file name, but from now on we will just say \"label\") \"persistence\", that "
127 "volume's persistence is fully customizable through the B<persistence.conf> "
128 "file stored on the root of its file system. Any such labeled volume must "
129 "have such a file, or it will be ignored."
133 #: en/persistence.conf.5:17
135 "The format of B<persistence.conf> allows empty lines and lines starting with "
136 "a \"#\" (used for comments), both which will be ignored. A so called "
137 "\"custom mount\" has the format:"
141 #: en/persistence.conf.5:20
142 msgid "I<DIR> [I<OPTION>]..."
146 #: en/persistence.conf.5:24
148 "which roughly translates to \"make I<DIR> persistence in the way described "
149 "by the list of I<OPTION>s\"."
153 #: en/persistence.conf.5:35
155 "For each custom mount I<DIR> must be an absolute path that cannot contain "
156 "white spaces or the special . and .. path components, and cannot be /live "
157 "(or any of its sub-directories). Once activated all changes (file deletion, "
158 "creation and modification) to I<DIR> on the live file system are stored "
159 "persistently into a path equivalent to I<DIR> on the persistence media, "
160 "called the source directory. The default way to achieve persistence is to "
161 "simply bind-mount the corresponding source directory to I<DIR>, but this can "
162 "be changed through the use of I<OPTION>s."
166 #: en/persistence.conf.5:48
168 "All custom mounts will be done in an order so that no two custom mounts can "
169 "\"hide\" each other. For instance, if we have the two I<DIR>:s /a and /a/b "
170 "it would always be the case that /a is mounted first, then /a/b. This "
171 "remains true no matter how the lines in B<persistence.conf> are ordered, or "
172 "if several B<persistence.conf> files on different persistence media are used "
173 "at the same time. However, it is forbidden for custom mounts to have their "
174 "source directory inside the source directory of another custom mount, so the "
175 "source directories that are auto-created by live-boot does not support "
176 "\"nested\" mounts like /a and /a/b on the same media. In this case you must "
177 "use the B<source> option (see below) to make sure that they are stored in "
178 "different source directories."
182 #: en/persistence.conf.5:56
184 "When a source directory doesn't exist on the persistence media for a certain "
185 "custom mount, it will be created automatically, and permissions and "
186 "ownership will be optimistically set according to I<DIR>. It will also be "
187 "bootstrapped by copying the contents of the I<DIR> into its source directory "
188 "on the persistence media. The bootstrapping will not happen when the B<link> "
189 "or B<union> options are used (see below)."
193 #: en/persistence.conf.5:60
195 "Custom mounts defined in B<persistence.conf> accept the following options in "
196 "a coma-separated list:"
200 #: en/persistence.conf.5:60
202 msgid "B<source>=I<PATH>"
206 #: en/persistence.conf.5:69
208 "When given, store the persistence changes into I<PATH> on the persistence "
209 "media. I<PATH> must be a relative path (with respect to the persistence "
210 "media root) that cannot contain white spaces or the special . or .. path "
211 "components, with the exception that it can be just . which means the "
212 "persistence media root. This option is mostly relevant if you want to nest "
213 "custom mounts, which otherwise would cause errors, or if you want to make "
214 "the whole media root available (similar to the now deprecated B<home-rw> "
215 "type of persistence)."
219 #: en/persistence.conf.5:72
221 "The following options are mutually exclusive (only the last given one will "
226 #: en/persistence.conf.5:72
232 #: en/persistence.conf.5:74
233 msgid "Bind-mount the source directory to I<DIR>. This is the default."
237 #: en/persistence.conf.5:74
243 #: en/persistence.conf.5:83
245 "Create the directory structure of the source directory on the persistence "
246 "media in I<DIR> and create symbolic links from the corresponding place in "
247 "I<DIR> to each file in the source directory. Existing files or directories "
248 "with the same name as any link will be overwritten. Note that deleting the "
249 "links in I<DIR> will only remove the link, not the corresponding file in the "
250 "source; removed links will reappear after a reboot. To permanently add or "
251 "delete a file one must do so directly in the source directory."
255 #: en/persistence.conf.5:91
257 "Effectively B<link> will make only files already in the source directory "
258 "persistent, not any other files in I<DIR>. These files must be manually "
259 "added to the source directory to make use of this option, and they will "
260 "appear in I<DIR> in addition to files already there. This option is useful "
261 "when only certain files need to be persistent, not the whole directory "
262 "they're in, e.g. some configuration files in a user's home directory."
266 #: en/persistence.conf.5:91
272 #: en/persistence.conf.5:101
274 "Save the rw branch of a union on the persistence media, so only the changes "
275 "are stored persistently. This can potentially reduce disk usage compared to "
276 "bind-mounts, and will not hide files added to the read-only media. One "
277 "caveat is that the union will use I<DIR> from the image's read-only file "
278 "system, not the real file system root, so files created after boot (e.g. by "
279 "live-config) will not appear in the union. This option will use the union "
280 "file system specified by live-boot's B<union> boot parameter, but is not "
281 "supported with B<union=unionmount>."
285 #: en/persistence.conf.5:102
291 #: en/persistence.conf.5:103
293 msgid "B</live/persistence>"
297 #: en/persistence.conf.5:109
299 "All persistence volumes will be mounted here (in a directory corresponding "
300 "to the device name). The B<persistence.conf> file can easily be edited "
301 "through this mount, as well as any source directories (which is especially "
302 "practical for custom mounts using the B<link> option)."
306 #: en/persistence.conf.5:110
312 #: en/persistence.conf.5:115
314 "Let's say we have a persistence volume I<VOL> with the a B<persistence.conf> "
315 "file containing the following four lines (numbered for ease of reference):"
319 #: en/persistence.conf.5:115 en/persistence.conf.5:129
325 #: en/persistence.conf.5:118
326 msgid "/home/user1 link,source=config-files/user1"
330 #: en/persistence.conf.5:118 en/persistence.conf.5:133
336 #: en/persistence.conf.5:121
337 msgid "/home/user2 link,source=config-files/user2"
341 #: en/persistence.conf.5:121 en/persistence.conf.5:137
347 #: en/persistence.conf.5:124
352 #: en/persistence.conf.5:124 en/persistence.conf.5:140
358 #: en/persistence.conf.5:127
363 #: en/persistence.conf.5:129
364 msgid "The corresponding source directories are:"
368 #: en/persistence.conf.5:133
370 "I<VOL>/config-files/user1 (but it would be I<VOL>/home/user1 without the "
375 #: en/persistence.conf.5:137
377 "I<VOL>/config-files/user2 (but it would be I<VOL>/home/user2 without the "
382 #: en/persistence.conf.5:140
387 #: en/persistence.conf.5:143
392 #: en/persistence.conf.5:146
394 "It was necessary to set the B<source> options for 1 and 2, since they "
395 "otherwise would become nested with 3's source, which is invalid."
399 #: en/persistence.conf.5:151
401 "Line 3 will be taken care of before line 1 and 2 in order to prevent custom "
402 "mounts 1 and 2 from being hidden by 3. When line 3 is handled, I<VOL>/home "
403 "is simply bind-mounted on /home. To illustrate what happens for lines 1 and "
404 "2, let's say that the following files exist:"
408 #: en/persistence.conf.5:151
414 #: en/persistence.conf.5:154
415 msgid "I<VOL>/config-files/user1/.emacs"
419 #: en/persistence.conf.5:154
425 #: en/persistence.conf.5:157
426 msgid "I<VOL>/config-files/user2/.bashrc"
430 #: en/persistence.conf.5:157
436 #: en/persistence.conf.5:160
437 msgid "I<VOL>/config-files/user2/.ssh/config"
441 #: en/persistence.conf.5:162
442 msgid "Then the following links and directories will be created:"
446 #: en/persistence.conf.5:162 en/persistence.conf.5:165
447 #: en/persistence.conf.5:171
453 #: en/persistence.conf.5:165
454 msgid "/home/user1/.emacs -E<gt> I<VOL>/config-files/user1/.emacs (from a)"
458 #: en/persistence.conf.5:168
459 msgid "/home/user2/.bashrc -E<gt> I<VOL>/config-files/user2/.bashrc (from b)"
463 #: en/persistence.conf.5:168
469 #: en/persistence.conf.5:171
470 msgid "/homea/user2/.ssh (from c)"
474 #: en/persistence.conf.5:175
476 "/home/user2/.ssh/config -E<gt> I<VOL>/config-files/user2/.ssh/config (from c)"
480 #: en/persistence.conf.5:181
482 "One could argue, though, that lines 1 and 2 in the example B<persistence."
483 "conf> file above are unnecessary since line 3 already would make all of /"
484 "home persistent. The B<link> option is intended for situations where you "
485 "don't want a complete directory to be persistent, only certain files in it "
486 "or its sub-directories."
490 #: en/persistence.conf.5:190
492 "Line 4 can be mounted at any time since its I<DIR> (and source directory) is "
493 "completely disjoint from all the other custom mounts. When mounted, I<VOL>/"
494 "usr will be the rw branch due to the B<union> option, and will only contain "
495 "the difference compared to the underlying read-only file system. Hence "
496 "packages could be installed into /usr with great space-wise efficiency "
497 "compared to bind-mounts, since in the latter case all of /usr would have to "
498 "be copied into I<VOL>/usr during the initial bootstrap."
502 #: en/persistence.conf.5:193
503 msgid "I<live-boot>(7)"
507 #: en/persistence.conf.5:213
509 "persistence.conf was written by anonym E<lt>I<anonym@lavabit.com>E<gt> for "
510 "the Debian project."