1 # German translations for live-boot package
2 # Copyright (C) 2006-2013 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~a13-1\n"
8 "POT-Creation-Date: 2013-05-27 16:45+0300\n"
9 "PO-Revision-Date: 2013-04-13 16:48+0100\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
30 #: en/live-boot.7:1 en/persistence.conf.5:1
35 #: en/live-boot.7:1 en/persistence.conf.5:1
37 msgid "Live Systems Project"
41 #: en/live-boot.7:3 en/persistence.conf.5:3
47 #: en/live-boot.7:6 en/persistence.conf.5:7
53 #: en/live-boot.7:28 en/persistence.conf.5:57
59 #: en/live-boot.7:154 en/persistence.conf.5:191
65 #: en/live-boot.7:158 en/persistence.conf.5:195
66 msgid "I<live-build>(7)"
70 #: en/live-boot.7:160 en/persistence.conf.5:197
71 msgid "I<live-config>(7)"
75 #: en/live-boot.7:162 en/persistence.conf.5:199
76 msgid "I<live-tools>(7)"
80 #: en/live-boot.7:163 en/persistence.conf.5:200
86 #: en/live-boot.7:165 en/persistence.conf.5:202
88 "More information about live-boot and the Live Systems project can be found "
89 "on the homepage at E<lt>I<http://live-systems.org/>E<gt> and in the manual "
90 "at E<lt>I<http://live-systems.org/manual/>E<gt>."
94 #: en/live-boot.7:166 en/persistence.conf.5:203
100 #: en/live-boot.7:168 en/persistence.conf.5:205
102 "Bugs can be reported by submitting a bugreport for the live-boot package in "
103 "the Bug Tracking System at E<lt>I<http://bugs.debian.org/>E<gt> or by "
104 "writing a mail to the Live Systems mailing list at E<lt>I<debian-live@lists."
109 #: en/live-boot.7:169 en/persistence.conf.5:206
115 #: en/live-boot.7:170 en/persistence.conf.5:207
117 "live-boot was written by Daniel Baumann E<lt>I<mail@daniel-baumann.ch>E<gt>."
121 #: en/persistence.conf.5:6
123 "B<persistence.conf> - Configuration file for persistence media in live-boot"
127 #: en/persistence.conf.5:13
129 "If live-boot probes a persistence volume with the label (or GPT name, or "
130 "file name, but from now on we will just say \"label\") \"persistence\", that "
131 "volume's persistence is fully customizable through the B<persistence.conf> "
132 "file stored on the root of its file system. Any such labeled volume must "
133 "have such a file, or it will be ignored."
137 #: en/persistence.conf.5:17
139 "The format of B<persistence.conf> allows empty lines and lines starting with "
140 "a \"#\" (used for comments), both which will be ignored. A so called "
141 "\"custom mount\" has the format:"
145 #: en/persistence.conf.5:20
146 msgid "I<DIR> [I<OPTION>]..."
150 #: en/persistence.conf.5:24
152 "which roughly translates to \"make I<DIR> persistence in the way described "
153 "by the list of I<OPTION>s\"."
157 #: en/persistence.conf.5:35
159 "For each custom mount I<DIR> must be an absolute path that cannot contain "
160 "white spaces or the special . and .. path components, and cannot be /live "
161 "(or any of its sub-directories). Once activated all changes (file deletion, "
162 "creation and modification) to I<DIR> on the live file system are stored "
163 "persistently into a path equivalent to I<DIR> on the persistence media, "
164 "called the source directory. The default way to achieve persistence is to "
165 "simply bind-mount the corresponding source directory to I<DIR>, but this can "
166 "be changed through the use of I<OPTION>s."
170 #: en/persistence.conf.5:48
172 "All custom mounts will be done in an order so that no two custom mounts can "
173 "\"hide\" each other. For instance, if we have the two I<DIR>:s /a and /a/b "
174 "it would always be the case that /a is mounted first, then /a/b. This "
175 "remains true no matter how the lines in B<persistence.conf> are ordered, or "
176 "if several B<persistence.conf> files on different persistence media are used "
177 "at the same time. However, it is forbidden for custom mounts to have their "
178 "source directory inside the source directory of another custom mount, so the "
179 "source directories that are auto-created by live-boot does not support "
180 "\"nested\" mounts like /a and /a/b on the same media. In this case you must "
181 "use the B<source> option (see below) to make sure that they are stored in "
182 "different source directories."
186 #: en/persistence.conf.5:56
188 "When a source directory doesn't exist on the persistence media for a certain "
189 "custom mount, it will be created automatically, and permissions and "
190 "ownership will be optimistically set according to I<DIR>. It will also be "
191 "bootstrapped by copying the contents of the I<DIR> into its source directory "
192 "on the persistence media. The bootstrapping will not happen when the B<link> "
193 "or B<union> options are used (see below)."
197 #: en/persistence.conf.5:60
199 "Custom mounts defined in B<persistence.conf> accept the following options in "
200 "a coma-separated list:"
204 #: en/persistence.conf.5:60
206 msgid "B<source>=I<PATH>"
210 #: en/persistence.conf.5:69
212 "When given, store the persistence changes into I<PATH> on the persistence "
213 "media. I<PATH> must be a relative path (with respect to the persistence "
214 "media root) that cannot contain white spaces or the special . or .. path "
215 "components, with the exception that it can be just . which means the "
216 "persistence media root. This option is mostly relevant if you want to nest "
217 "custom mounts, which otherwise would cause errors, or if you want to make "
218 "the whole media root available (similar to the now deprecated B<home-rw> "
219 "type of persistence)."
223 #: en/persistence.conf.5:72
225 "The following options are mutually exclusive (only the last given one will "
230 #: en/persistence.conf.5:72
236 #: en/persistence.conf.5:74
237 msgid "Bind-mount the source directory to I<DIR>. This is the default."
241 #: en/persistence.conf.5:74
247 #: en/persistence.conf.5:83
249 "Create the directory structure of the source directory on the persistence "
250 "media in I<DIR> and create symbolic links from the corresponding place in "
251 "I<DIR> to each file in the source directory. Existing files or directories "
252 "with the same name as any link will be overwritten. Note that deleting the "
253 "links in I<DIR> will only remove the link, not the corresponding file in the "
254 "source; removed links will reappear after a reboot. To permanently add or "
255 "delete a file one must do so directly in the source directory."
259 #: en/persistence.conf.5:91
261 "Effectively B<link> will make only files already in the source directory "
262 "persistent, not any other files in I<DIR>. These files must be manually "
263 "added to the source directory to make use of this option, and they will "
264 "appear in I<DIR> in addition to files already there. This option is useful "
265 "when only certain files need to be persistent, not the whole directory "
266 "they're in, e.g. some configuration files in a user's home directory."
270 #: en/persistence.conf.5:91
276 #: en/persistence.conf.5:101
278 "Save the rw branch of a union on the persistence media, so only the changes "
279 "are stored persistently. This can potentially reduce disk usage compared to "
280 "bind-mounts, and will not hide files added to the read-only media. One "
281 "caveat is that the union will use I<DIR> from the image's read-only file "
282 "system, not the real file system root, so files created after boot (e.g. by "
283 "live-config) will not appear in the union. This option will use the union "
284 "file system specified by live-boot's B<union> boot parameter, but is not "
285 "supported with B<union=unionmount>."
289 #: en/persistence.conf.5:102
295 #: en/persistence.conf.5:103
297 msgid "B</live/persistence>"
301 #: en/persistence.conf.5:109
303 "All persistence volumes will be mounted here (in a directory corresponding "
304 "to the device name). The B<persistence.conf> file can easily be edited "
305 "through this mount, as well as any source directories (which is especially "
306 "practical for custom mounts using the B<link> option)."
310 #: en/persistence.conf.5:110
316 #: en/persistence.conf.5:115
318 "Let's say we have a persistence volume I<VOL> with the a B<persistence.conf> "
319 "file containing the following four lines (numbered for ease of reference):"
323 #: en/persistence.conf.5:115 en/persistence.conf.5:129
329 #: en/persistence.conf.5:118
330 msgid "/home/user1 link,source=config-files/user1"
334 #: en/persistence.conf.5:118 en/persistence.conf.5:133
340 #: en/persistence.conf.5:121
341 msgid "/home/user2 link,source=config-files/user2"
345 #: en/persistence.conf.5:121 en/persistence.conf.5:137
351 #: en/persistence.conf.5:124
356 #: en/persistence.conf.5:124 en/persistence.conf.5:140
362 #: en/persistence.conf.5:127
367 #: en/persistence.conf.5:129
368 msgid "The corresponding source directories are:"
372 #: en/persistence.conf.5:133
374 "I<VOL>/config-files/user1 (but it would be I<VOL>/home/user1 without the "
379 #: en/persistence.conf.5:137
381 "I<VOL>/config-files/user2 (but it would be I<VOL>/home/user2 without the "
386 #: en/persistence.conf.5:140
391 #: en/persistence.conf.5:143
396 #: en/persistence.conf.5:146
398 "It was necessary to set the B<source> options for 1 and 2, since they "
399 "otherwise would become nested with 3's source, which is invalid."
403 #: en/persistence.conf.5:151
405 "Line 3 will be taken care of before line 1 and 2 in order to prevent custom "
406 "mounts 1 and 2 from being hidden by 3. When line 3 is handled, I<VOL>/home "
407 "is simply bind-mounted on /home. To illustrate what happens for lines 1 and "
408 "2, let's say that the following files exist:"
412 #: en/persistence.conf.5:151
418 #: en/persistence.conf.5:154
419 msgid "I<VOL>/config-files/user1/.emacs"
423 #: en/persistence.conf.5:154
429 #: en/persistence.conf.5:157
430 msgid "I<VOL>/config-files/user2/.bashrc"
434 #: en/persistence.conf.5:157
440 #: en/persistence.conf.5:160
441 msgid "I<VOL>/config-files/user2/.ssh/config"
445 #: en/persistence.conf.5:162
446 msgid "Then the following links and directories will be created:"
450 #: en/persistence.conf.5:162 en/persistence.conf.5:165
451 #: en/persistence.conf.5:171
457 #: en/persistence.conf.5:165
458 msgid "/home/user1/.emacs -E<gt> I<VOL>/config-files/user1/.emacs (from a)"
462 #: en/persistence.conf.5:168
463 msgid "/home/user2/.bashrc -E<gt> I<VOL>/config-files/user2/.bashrc (from b)"
467 #: en/persistence.conf.5:168
473 #: en/persistence.conf.5:171
474 msgid "/homea/user2/.ssh (from c)"
478 #: en/persistence.conf.5:175
480 "/home/user2/.ssh/config -E<gt> I<VOL>/config-files/user2/.ssh/config (from c)"
484 #: en/persistence.conf.5:181
486 "One could argue, though, that lines 1 and 2 in the example B<persistence."
487 "conf> file above are unnecessary since line 3 already would make all of /"
488 "home persistent. The B<link> option is intended for situations where you "
489 "don't want a complete directory to be persistent, only certain files in it "
490 "or its sub-directories."
494 #: en/persistence.conf.5:190
496 "Line 4 can be mounted at any time since its I<DIR> (and source directory) is "
497 "completely disjoint from all the other custom mounts. When mounted, I<VOL>/"
498 "usr will be the rw branch due to the B<union> option, and will only contain "
499 "the difference compared to the underlying read-only file system. Hence "
500 "packages could be installed into /usr with great space-wise efficiency "
501 "compared to bind-mounts, since in the latter case all of /usr would have to "
502 "be copied into I<VOL>/usr during the initial bootstrap."
506 #: en/persistence.conf.5:193
507 msgid "I<live-boot>(7)"