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 VERSION\n"
10 "POT-Creation-Date: 2012-04-05 08:11+0300\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/live-snapshot.1:1 en/live.persist.5:1
26 #: en/live-boot.7:1 en/live-snapshot.1:1 en/live.persist.5:1
32 #: en/live-boot.7:1 en/live-snapshot.1:1 en/live.persist.5:1
38 #: en/live-boot.7:1 en/live-snapshot.1:1 en/live.persist.5:1
40 msgid "Debian Live Project"
44 #: en/live-boot.7:3 en/live-snapshot.1:3 en/live.persist.5:3
50 #: en/live-boot.7:6 en/live-snapshot.1:17 en/live.persist.5:7
56 #: en/live-boot.7:28 en/live-snapshot.1:20 en/live.persist.5:57
62 #: en/live-boot.7:162 en/live-snapshot.1:54 en/live.persist.5:191
68 #: en/live-boot.7:168 en/live-snapshot.1:58 en/live.persist.5:195
69 msgid "I<live-build>(7)"
73 #: en/live-boot.7:170 en/live-snapshot.1:60 en/live.persist.5:197
74 msgid "I<live-config>(7)"
78 #: en/live-boot.7:172 en/live-snapshot.1:62 en/live.persist.5:199
79 msgid "I<live-tools>(7)"
83 #: en/live-boot.7:173 en/live-snapshot.1:63 en/live.persist.5:200
89 #: en/live-boot.7:175 en/live-snapshot.1:65 en/live.persist.5:204
91 "More information about live-boot and the Debian Live project can be found on "
92 "the homepage at E<lt>I<http://live.debian.net/>E<gt> and in the manual at "
93 "E<lt>I<http://live.debian.net/manual/>E<gt>."
97 #: en/live-boot.7:176 en/live-snapshot.1:66 en/live.persist.5:205
103 #: en/live-boot.7:178 en/live-snapshot.1:68 en/live.persist.5:210
105 "Bugs can be reported by submitting a bugreport for the live-boot package in "
106 "the Debian Bug Tracking System at E<lt>I<http://bugs.debian.org/>E<gt> or by "
107 "writing a mail to the Debian Live mailing list at E<lt>I<debian-live@lists."
112 #: en/live-boot.7:179 en/live-snapshot.1:69 en/live.persist.5:211
118 #: en/live.persist.5:6
119 msgid "B<live.persist> - Configuration file for persistent media in live-boot"
123 #: en/live.persist.5:13
125 "If live-boot probes a persistent volume with the label (or GPT name, or file "
126 "name, but from now on we will just say \"label\") \"custom-ov\", that "
127 "volume's persistence is fully customizable through the B<live.persist> file "
128 "stored on the root of its file system. Any such labeled volume must have "
129 "such a file, or it will be ignored."
133 #: en/live.persist.5:17
135 "The format of B<live.persist> allow empty lines and lines starting with a \"#"
136 "\" (used for comments), both which will be ignored. A so called \"custom "
137 "mount\" has the format:"
141 #: en/live.persist.5:20
142 msgid "I<DIR> [I<OPTION>]..."
146 #: en/live.persist.5:24
148 "which roughly translates to \"make I<DIR> persistent in the way described by "
149 "the list of I<OPTION>s\"."
153 #: en/live.persist.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), or / (for the latter, use \"full-ov\" "
158 "persistence instead). Once activated all changes (file deletion, creation "
159 "and modification) to I<DIR> on the live file system are stored persistently "
160 "into a path equivalent to I<DIR> on the persistent media, called the source "
161 "directory. The default way to achieve persistence is to simply bind-mount "
162 "the corresponding source directory to I<DIR>, but this can be changed "
163 "through the use of I<OPTION>s."
167 #: en/live.persist.5:48
169 "All custom mounts will be done in an order so that no two custom mounts can "
170 "\"hide\" each other. For instance, if we have the two I<DIR>:s /a and /a/b "
171 "it would always be the case that /a is mounted first, then /a/b. This "
172 "remains true no matter how the lines in B<live.persist> are ordered, or if "
173 "several B<live.persist> files on different persistent media are used at the "
174 "same time. However, it is forbidden for custom mounts to have their source "
175 "directory inside the source directory of another custom mount, so the source "
176 "directories that are auto-created by live-boot does not support \"nested\" "
177 "mounts like /a and /a/b on the same media. In this case you must use the "
178 "B<source> option (see below) to make sure that they are stored in different "
179 "source directories."
183 #: en/live.persist.5:56
185 "When a source directory doesn't exist on the persistent media for a certain "
186 "custom mount, it will be created automatically, and permissions and "
187 "ownership will be optimistically set according to I<DIR>. It will also be "
188 "bootstrapped by copying the contents of the I<DIR> into its source directory "
189 "on the persistent media. The bootstrapping will not happen when the "
190 "B<linkfiles> or B<union> options are used (see below)."
194 #: en/live.persist.5:60
196 "Custom mounts defined in B<live.persist> accept the following options in a "
197 "coma-separated list:"
201 #: en/live.persist.5:60
203 msgid "B<source>=I<PATH>"
207 #: en/live.persist.5:69
209 "When given, store the persistent changes into I<PATH> on the persistent "
210 "media. I<PATH> must be a relative path (w.r.t. the persistent media root) "
211 "that cannot contain white spaces or the special . or .. path components, "
212 "with the exception that it can be just . which means the persistent media "
213 "root. This option is mostly relevant if you want to nest custom mounts, "
214 "which otherwise would cause errors, or if you want to make the whole media "
215 "root available (similar to the now deprecated B<home-rw> type of "
220 #: en/live.persist.5:72
222 "The following options are mutually exclusive (only the last given one will "
227 #: en/live.persist.5:72
233 #: en/live.persist.5:74
234 msgid "Bind-mount the source directory to I<DIR>. This is the default."
238 #: en/live.persist.5:74
244 #: en/live.persist.5:83
246 "Create the directory structure of the source directory on the persistent "
247 "media in I<DIR> and create symbolic links from the corresponding place in "
248 "I<DIR> to each file in the source directory. Existing files or directories "
249 "with the same name as any link will be overwritten. Note that deleting the "
250 "links in I<DIR> will only remove the link, not the corresponding file in the "
251 "source; removed links will reappear after a reboot. To permanently add or "
252 "delete a file one must do so directly in the source directory."
256 #: en/live.persist.5:91
258 "Effectively B<linkfiles> will make only files already in the source "
259 "directory persistent, not any other files in I<DIR>. These files must be "
260 "manually added to the source directory to make use of this option, and they "
261 "will appear in I<DIR> in addition to files already there. This option is "
262 "useful when only certain files need to be persistent, not the whole "
263 "directory they're in, e.g. some configuration files in a user's home "
268 #: en/live.persist.5:91
274 #: en/live.persist.5:101
276 "Save the rw branch of a union on the persistent media, so only the changes "
277 "are stored persistently. This can potentially reduce disk usage compared to "
278 "bind-mounts, and will not hide files added to the read-only media. One "
279 "caveat is that the union will use I<DIR> from the image's read-only file "
280 "system, not the real file system root, so files created after boot (e.g. by "
281 "live-config) will not appear in the union. This option will use the union "
282 "file system specified by live-boot's B<union> boot parameter, but is not "
283 "supported with B<union=unionmount>."
287 #: en/live.persist.5:102
293 #: en/live.persist.5:103
295 msgid "B</live/persistent>"
299 #: en/live.persist.5:109
301 "All persistent volumes will be mounted here (in a directory corresponding to "
302 "the device name). The B<live.persist> file can easily be edited through this "
303 "mount, as well as any source directories (which is especially practical for "
304 "custom mounts using the B<linkfiles> option)."
308 #: en/live.persist.5:110
314 #: en/live.persist.5:115
316 "Let's say we have a persistent volume I<VOL> with the a B<live.persist> file "
317 "containing the following four lines (numbered for ease of reference):"
321 #: en/live.persist.5:115 en/live.persist.5:129
327 #: en/live.persist.5:118
328 msgid "/home/user1 linkfiles,source=config-files/user1"
332 #: en/live.persist.5:118 en/live.persist.5:133
338 #: en/live.persist.5:121
339 msgid "/home/user2 linkfiles,source=config-files/user2"
343 #: en/live.persist.5:121 en/live.persist.5:137
349 #: en/live.persist.5:124
354 #: en/live.persist.5:124 en/live.persist.5:140
360 #: en/live.persist.5:127
365 #: en/live.persist.5:129
366 msgid "The corresponding source directories are:"
370 #: en/live.persist.5:133
372 "I<VOL>/config-files/user1 (but it would be I<VOL>/home/user1 without the "
377 #: en/live.persist.5:137
379 "I<VOL>/config-files/user2 (but it would be I<VOL>/home/user2 without the "
384 #: en/live.persist.5:140
389 #: en/live.persist.5:143
394 #: en/live.persist.5:146
396 "It was necessary to set the B<source> options for 1 and 2, since they "
397 "otherwise would become nested with 3's source, which is illegal."
401 #: en/live.persist.5:151
403 "Line 3 will be taken care of before line 1 and 2 in order to prevent custom "
404 "mounts 1 and 2 from being hidden by 3. When line 3 is handled, I<VOL>/home "
405 "is simply bind-mounted on /home. To illustrate what happens for lines 1 and "
406 "2, let's say that the following files exist:"
410 #: en/live.persist.5:151
416 #: en/live.persist.5:154
417 msgid "I<VOL>/config-files/user1/.emacs"
421 #: en/live.persist.5:154
427 #: en/live.persist.5:157
428 msgid "I<VOL>/config-files/user2/.bashrc"
432 #: en/live.persist.5:157
438 #: en/live.persist.5:160
439 msgid "I<VOL>/config-files/user2/.ssh/config"
443 #: en/live.persist.5:162
444 msgid "Then the following links and directories will be created:"
448 #: en/live.persist.5:162 en/live.persist.5:165 en/live.persist.5:171
454 #: en/live.persist.5:165
455 msgid "/home/user1/.emacs -E<gt> I<VOL>/config-files/user1/.emacs (from a)"
459 #: en/live.persist.5:168
460 msgid "/home/user2/.bashrc -E<gt> I<VOL>/config-files/user2/.bashrc (from b)"
464 #: en/live.persist.5:168
470 #: en/live.persist.5:171
471 msgid "/homea/user2/.ssh (from c)"
475 #: en/live.persist.5:175
477 "/home/user2/.ssh/config -E<gt> I<VOL>/config-files/user2/.ssh/config (from c)"
481 #: en/live.persist.5:181
483 "One could argue, though, that lines 1 and 2 in the example B<live.persist> "
484 "file above are unnecessary since line 3 already would make all of /home "
485 "persistent. The B<linkfiles> option is intended for situations where you "
486 "don't want a complete directory to be persistent, only certain files in it "
487 "or its sub-directories."
491 #: en/live.persist.5:190
493 "Line 4 can be mounted at any time since its I<DIR> (and source directory) is "
494 "completely disjoint from all the other custom mounts. When mounted, I<VOL>/"
495 "usr will be the rw branch due to the B<union> option, and will only contain "
496 "the difference compared to the underlying read-only file system. Hence "
497 "packages could be installed into /usr with great space-wise efficiency "
498 "compared to bind-mounts, since in the latter case all of /usr would have to "
499 "be copied into I<VOL>/usr during the initial bootstrap."
503 #: en/live.persist.5:193
504 msgid "I<live-boot>(7)"
508 #: en/live.persist.5:213
510 "live.persist was written by anonym E<lt>I<anonym@lavabit.com>E<gt> for the "