.\" This file was generated with po4a. Translate the source file.
.\"
.\"*******************************************************************
-.TH LIVE\-BOOT conf 24.08.2012 3.0~b2\-1 "Debian Live Project"
+.TH LIVE\-BOOT conf 2012\-04\-09 3.0~a27\-1 "Debian Live Project"
.SH NAME
\fBlive\-persistence.conf\fP \- Configuration file for persistence media in
.SH DESCRIPTION
If live\-boot probes a persistence volume with the label (or GPT name, or
-file name, but from now on we will just say "label") "persistence", that
+file name, but from now on we will just say "label") "custom\-ov", that
volume's persistence is fully customizable through the
\fBlive\-persistence.conf\fP file stored on the root of its file system. Any
such labeled volume must have such a file, or it will be ignored.
.PP
-The format of \fBlive\-persistence.conf\fP allows empty lines and lines starting
+The format of \fBlive\-persistence.conf\fP allow empty lines and lines starting
with a "#" (used for comments), both which will be ignored. A so called
"custom mount" has the format:
.PP
.PP
For each custom mount \fIDIR\fP must be an absolute path that cannot contain
white spaces or the special . and .. path components, and cannot be /live
-(or any of its sub\-directories). Once activated all changes (file deletion,
-creation and modification) to \fIDIR\fP on the live file system are stored
-persistently into a path equivalent to \fIDIR\fP on the persistence media,
-called the source directory. The default way to achieve persistence is to
-simply bind\-mount the corresponding source directory to \fIDIR\fP, but this can
-be changed through the use of \fIOPTION\fPs.
+(or any of its sub\-directories), or / (for the latter, use "full\-ov"
+persistence instead). Once activated all changes (file deletion, creation
+and modification) to \fIDIR\fP on the live file system are stored persistently
+into a path equivalent to \fIDIR\fP on the persistence media, called the source
+directory. The default way to achieve persistence is to simply bind\-mount
+the corresponding source directory to \fIDIR\fP, but this can be changed
+through the use of \fIOPTION\fPs.
.PP
All custom mounts will be done in an order so that no two custom mounts can
"hide" each other. For instance, if we have the two \fIDIR\fP:s /a and /a/b it
options in a coma\-separated list:
.IP \fBsource\fP=\fIPATH\fP 4
When given, store the persistence changes into \fIPATH\fP on the persistence
-media. \fIPATH\fP must be a relative path (with respect to the persistence
-media root) that cannot contain white spaces or the special . or .. path
-components, with the exception that it can be just . which means the
-persistence media root. This option is mostly relevant if you want to nest
-custom mounts, which otherwise would cause errors, or if you want to make
-the whole media root available (similar to the now deprecated \fBhome\-rw\fP
-type of persistence).
+media. \fIPATH\fP must be a relative path (w.r.t. the persistence media root)
+that cannot contain white spaces or the special . or .. path components,
+with the exception that it can be just . which means the persistence media
+root. This option is mostly relevant if you want to nest custom mounts,
+which otherwise would cause errors, or if you want to make the whole media
+root available (similar to the now deprecated \fBhome\-rw\fP type of
+persistence).
.PP
The following options are mutually exclusive (only the last given one will
be in effect):
<\fIdebian\-live@lists.debian.org\fP>.
.SH AUTHOR
-live\-persistence.conf was written by anonym <\fIanonym@lavabit.com\fP>
-for the Debian project.
+live.persist was written by anonym <\fIanonym@lavabit.com\fP> for the
+Debian project.
projects / live-boot-grml.git / blobdiff