1 # SOME DESCRIPTIVE TITLE
2 # Copyright (C) YEAR Free Software Foundation, Inc.
3 # This file is distributed under the same license as the live-boot package.
4 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
9 "Project-Id-Version: live-boot 5.0~a5-1\n"
10 "POT-Creation-Date: 2015-08-23 10:55+0200\n"
11 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
12 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
13 "Language-Team: LANGUAGE <LL@li.org>\n"
16 "Content-Type: text/plain; charset=CHARSET\n"
17 "Content-Transfer-Encoding: 8bit\n"
20 #: en/live-boot.7:1 en/persistence.conf.5:1
26 #: en/live-boot.7:1 en/persistence.conf.5:1
32 #: en/live-boot.7:1 en/persistence.conf.5:1
38 #: en/live-boot.7:1 en/persistence.conf.5:1
40 msgid "Live Systems Project"
44 #: en/live-boot.7:3 en/persistence.conf.5:3
50 #: en/live-boot.7:6 en/persistence.conf.5:7
56 #: en/live-boot.7:28 en/persistence.conf.5:57
62 #: en/live-boot.7:154 en/persistence.conf.5:190
68 #: en/live-boot.7:158 en/persistence.conf.5:194
69 msgid "I<live-build>(7)"
73 #: en/live-boot.7:160 en/persistence.conf.5:196
74 msgid "I<live-config>(7)"
78 #: en/live-boot.7:162 en/persistence.conf.5:198
79 msgid "I<live-tools>(7)"
83 #: en/live-boot.7:163 en/persistence.conf.5:199
89 #: en/live-boot.7:165 en/persistence.conf.5:201
91 "More information about live-boot and the Live Systems project can be found "
92 "on the homepage at E<lt>I<http://live-systems.org/>E<gt> and in the manual "
93 "at E<lt>I<http://live-systems.org/manual/>E<gt>."
97 #: en/live-boot.7:166 en/persistence.conf.5:202
103 #: en/live-boot.7:168 en/persistence.conf.5:204
105 "Bugs can be reported by submitting a bugreport for the live-boot package in "
106 "the Bug Tracking System at E<lt>I<http://bugs.debian.org/>E<gt> or by "
107 "writing a mail to the Live Systems mailing list at E<lt>I<debian-live@lists."
112 #: en/live-boot.7:169 en/persistence.conf.5:205
118 #: en/live-boot.7:170 en/persistence.conf.5:206
120 "live-boot was written by Daniel Baumann E<lt>I<mail@daniel-baumann.ch>E<gt>."
124 #: en/persistence.conf.5:6
126 "B<persistence.conf> - Configuration file for persistence media in live-boot"
130 #: en/persistence.conf.5:13
132 "If live-boot probes a persistence volume with the label (or GPT name, or "
133 "file name, but from now on we will just say \"label\") \"persistence\", that "
134 "volume's persistence is fully customizable through the B<persistence.conf> "
135 "file stored on the root of its file system. Any such labeled volume must "
136 "have such a file, or it will be ignored."
140 #: en/persistence.conf.5:17
142 "The format of B<persistence.conf> allows empty lines and lines starting with "
143 "a \"#\" (used for comments), both which will be ignored. A so called "
144 "\"custom mount\" has the format:"
148 #: en/persistence.conf.5:20
149 msgid "I<DIR> [I<OPTION>]..."
153 #: en/persistence.conf.5:24
155 "which roughly translates to \"make I<DIR> persistence in the way described "
156 "by the list of I<OPTION>s\"."
160 #: en/persistence.conf.5:35
162 "For each custom mount I<DIR> must be an absolute path that cannot contain "
163 "white spaces or the special . and .. path components, and cannot be /live "
164 "(or any of its sub-directories). Once activated all changes (file deletion, "
165 "creation and modification) to I<DIR> on the live file system are stored "
166 "persistently into a path equivalent to I<DIR> on the persistence media, "
167 "called the source directory. The default way to achieve persistence is to "
168 "simply bind-mount the corresponding source directory to I<DIR>, but this can "
169 "be changed through the use of I<OPTION>s."
173 #: en/persistence.conf.5:48
175 "All custom mounts will be done in an order so that no two custom mounts can "
176 "\"hide\" each other. For instance, if we have the two I<DIR>:s /a and /a/b "
177 "it would always be the case that /a is mounted first, then /a/b. This "
178 "remains true no matter how the lines in B<persistence.conf> are ordered, or "
179 "if several B<persistence.conf> files on different persistence media are used "
180 "at the same time. However, it is forbidden for custom mounts to have their "
181 "source directory inside the source directory of another custom mount, so the "
182 "source directories that are auto-created by live-boot does not support "
183 "\"nested\" mounts like /a and /a/b on the same media. In this case you must "
184 "use the B<source> option (see below) to make sure that they are stored in "
185 "different source directories."
189 #: en/persistence.conf.5:56
191 "When a source directory doesn't exist on the persistence media for a certain "
192 "custom mount, it will be created automatically, and permissions and "
193 "ownership will be optimistically set according to I<DIR>. It will also be "
194 "bootstrapped by copying the contents of the I<DIR> into its source directory "
195 "on the persistence media. The bootstrapping will not happen when the B<link> "
196 "or B<union> options are used (see below)."
200 #: en/persistence.conf.5:60
202 "Custom mounts defined in B<persistence.conf> accept the following options in "
203 "a comma-separated list:"
207 #: en/persistence.conf.5:60
209 msgid "B<source>=I<PATH>"
213 #: en/persistence.conf.5:69
215 "When given, store the persistence changes into I<PATH> on the persistence "
216 "media. I<PATH> must be a relative path (with respect to the persistence "
217 "media root) that cannot contain white spaces or the special . or .. path "
218 "components, with the exception that it can be just . which means the "
219 "persistence media root. This option is mostly relevant if you want to nest "
220 "custom mounts, which otherwise would cause errors, or if you want to make "
221 "the whole media root available (similar to the now deprecated B<home-rw> "
222 "type of persistence)."
226 #: en/persistence.conf.5:72
228 "The following options are mutually exclusive (only the last given one will "
233 #: en/persistence.conf.5:72
239 #: en/persistence.conf.5:74
240 msgid "Bind-mount the source directory to I<DIR>. This is the default."
244 #: en/persistence.conf.5:74
250 #: en/persistence.conf.5:83
252 "Create the directory structure of the source directory on the persistence "
253 "media in I<DIR> and create symbolic links from the corresponding place in "
254 "I<DIR> to each file in the source directory. Existing files or directories "
255 "with the same name as any link will be overwritten. Note that deleting the "
256 "links in I<DIR> will only remove the link, not the corresponding file in the "
257 "source; removed links will reappear after a reboot. To permanently add or "
258 "delete a file one must do so directly in the source directory."
262 #: en/persistence.conf.5:91
264 "Effectively B<link> will make only files already in the source directory "
265 "persistent, not any other files in I<DIR>. These files must be manually "
266 "added to the source directory to make use of this option, and they will "
267 "appear in I<DIR> in addition to files already there. This option is useful "
268 "when only certain files need to be persistent, not the whole directory "
269 "they're in, e.g. some configuration files in a user's home directory."
273 #: en/persistence.conf.5:91
279 #: en/persistence.conf.5:100
281 "Save the rw branch of a union on the persistence media, so only the changes "
282 "are stored persistently. This can potentially reduce disk usage compared to "
283 "bind-mounts, and will not hide files added to the read-only media. One "
284 "caveat is that the union will use I<DIR> from the image's read-only file "
285 "system, not the real file system root, so files created after boot (e.g. by "
286 "live-config) will not appear in the union. This option will use the union "
287 "file system specified by live-boot's B<union> boot parameter."
291 #: en/persistence.conf.5:101
297 #: en/persistence.conf.5:102
299 msgid "B</live/persistence>"
303 #: en/persistence.conf.5:108
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:109
318 #: en/persistence.conf.5:114
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:114 en/persistence.conf.5:128
331 #: en/persistence.conf.5:117
332 msgid "/home/user1 link,source=config-files/user1"
336 #: en/persistence.conf.5:117 en/persistence.conf.5:132
342 #: en/persistence.conf.5:120
343 msgid "/home/user2 link,source=config-files/user2"
347 #: en/persistence.conf.5:120 en/persistence.conf.5:136
353 #: en/persistence.conf.5:123
358 #: en/persistence.conf.5:123 en/persistence.conf.5:139
364 #: en/persistence.conf.5:126
369 #: en/persistence.conf.5:128
370 msgid "The corresponding source directories are:"
374 #: en/persistence.conf.5:132
376 "I<VOL>/config-files/user1 (but it would be I<VOL>/home/user1 without the "
381 #: en/persistence.conf.5:136
383 "I<VOL>/config-files/user2 (but it would be I<VOL>/home/user2 without the "
388 #: en/persistence.conf.5:139
393 #: en/persistence.conf.5:142
398 #: en/persistence.conf.5:145
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:150
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:150
420 #: en/persistence.conf.5:153
421 msgid "I<VOL>/config-files/user1/.emacs"
425 #: en/persistence.conf.5:153
431 #: en/persistence.conf.5:156
432 msgid "I<VOL>/config-files/user2/.bashrc"
436 #: en/persistence.conf.5:156
442 #: en/persistence.conf.5:159
443 msgid "I<VOL>/config-files/user2/.ssh/config"
447 #: en/persistence.conf.5:161
448 msgid "Then the following links and directories will be created:"
452 #: en/persistence.conf.5:161 en/persistence.conf.5:164
453 #: en/persistence.conf.5:170
459 #: en/persistence.conf.5:164
460 msgid "/home/user1/.emacs -E<gt> I<VOL>/config-files/user1/.emacs (from a)"
464 #: en/persistence.conf.5:167
465 msgid "/home/user2/.bashrc -E<gt> I<VOL>/config-files/user2/.bashrc (from b)"
469 #: en/persistence.conf.5:167
475 #: en/persistence.conf.5:170
476 msgid "/homea/user2/.ssh (from c)"
480 #: en/persistence.conf.5:174
482 "/home/user2/.ssh/config -E<gt> I<VOL>/config-files/user2/.ssh/config (from c)"
486 #: en/persistence.conf.5:180
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:189
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:192
509 msgid "I<live-boot>(7)"