.IP \fBpersistence\fP 4
live\-boot will probe devices for persistence media. These can be partitions
(with the correct GPT name), filesystems (with the correct label) or image
-files (with the correct file name). Overlays are labeled/named either
-"full\-ov", which will be mounted on /, or "custom\-ov", which can be
-completely customized (see \fIlive\-persistence.conf\fP(5)). The order these are
-handled are: full\-ov, custom\-ov. Overlay image files have extensions which
-determines their filesystem, e.g. "custom\-ov.ext4".
+files (with the correct file name). Overlays are labeled/named "persistence"
+(see \fIlive\-persistence.conf\fP(5)). Overlay image files have extensions which
+determines their filesystem, e.g. "persistence.ext4".
.IP "\fBpersistence\-encryption\fP=\fITYPE1\fP,\fITYPE2\fP ... \fITYPEn\fP" 4
This option determines which types of encryption that we allow to be used
when probing devices for persistence media. If "none" is in the list, we
.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") "custom\-ov", that
+file name, but from now on we will just say "label") "persistence", 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
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), 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.
+(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.
.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
.IP "\fBswapon\fR" 4
This parameter enables usage of local swap partitions.
.IP "\fBpersistence\fR" 4
-live\-boot will probe devices for persistence media. These can be partitions (with the correct GPT name), filesystems (with the correct label) or image files (with the correct file name). Overlays are labeled/named either "full\-ov", which will be mounted on /, or "custom\-ov", which can be completely customized (see \fIlive-persistence.conf\fR(5)). The order these are handled are: full\-ov, custom\-ov. Overlay image files have extensions which determines their filesystem, e.g. "custom\-ov.ext4".
+live\-boot will probe devices for persistence media. These can be partitions (with the correct GPT name), filesystems (with the correct label) or image files (with the correct file name). Overlays are labeled/named "persistence" (see \fIlive-persistence.conf\fR(5)). Overlay image files have extensions which determines their filesystem, e.g. "persistence.ext4".
.IP "\fBpersistence\-encryption\fR=\fITYPE1\fR,\fITYPE2\fR ... \fITYPEn\fR" 4
This option determines which types of encryption that we allow to be used when probing devices for persistence media. If "none" is in the list, we allow unencrypted media; if "luks" is in the list, we allow LUKS\-encrypted media. Whenever a device containing encrypted media is probed the user will be prompted for the passphrase. The default value is "none".
.IP "\fBpersistence\-media\fR={\fIremovable\fR|\fIremovable\-usb\fR}" 4
.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") "custom\-ov",
+or file name, but from now on we will just say "label") "persistence",
that volume's persistence is fully customizable through the
\fBlive-persistence.conf\fR file stored on the root of its file system. Any such
labeled volume must have such a file, or it will be ignored.
.PP
For each custom mount \fIDIR\fR 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), or / (for the latter,
-use "full-ov" persistence instead). Once activated all changes (file
+cannot be /live (or any of its sub-directories).
+Once activated all changes (file
deletion, creation and modification) to \fIDIR\fR on the live file
system are stored persistently into a path equivalent to \fIDIR\fR on
the persistence media, called the source directory. The default way to
.IP \fBpersistence\fP 4
live\-boot will probe devices for persistence media. These can be partitions
(with the correct GPT name), filesystems (with the correct label) or image
-files (with the correct file name). Overlays are labeled/named either
-"full\-ov", which will be mounted on /, or "custom\-ov", which can be
-completely customized (see \fIlive\-persistence.conf\fP(5)). The order these are
-handled are: full\-ov, custom\-ov. Overlay image files have extensions which
-determines their filesystem, e.g. "custom\-ov.ext4".
+files (with the correct file name). Overlays are labeled/named "persistence"
+(see \fIlive\-persistence.conf\fP(5)). Overlay image files have extensions which
+determines their filesystem, e.g. "persistence.ext4".
.IP "\fBpersistence\-encryption\fP=\fITYPE1\fP,\fITYPE2\fP ... \fITYPEn\fP" 4
Esta opción determina qué tipo de cifrado se usa cuando se prueban los
dispositivos de los medios con persistencia. Si se especifica "none" en la
con persistencia en live\-boot
.SH DESCRIPCIÓN
-Si live\-boot prueba un volumen persistente con la etiqueta (o nombre GPT, o
-nombre de fichero, aunque a partir de este momento nos referiremos a él como
-simplemente "etiqueta") "custom\-ov", la persistencia de ese volumen es
-completamente personalizable a través del fichero \fBlive\-persistence.conf\fP
-almacenado en la raíz de su sistema de ficheros. Cualquier volumen con una
-de esas etiquetas debe tener uno de esos ficheros, o si no será ignorado.
+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
+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
El formato de \fBlive\-persistence.conf\fP permite añadir líneas vacias o líneas
que comiencen por "#" (usado para los comentarios), ambos serán
lo que se traduce como "hacer \fIDIR\fP persistente en la forma descrita en la
lista de \fIOPTION\fPs".
.PP
-Para cada uno de los montajes personalizados \fIDIR\fP debe ser una ruta
-absoluta que no puede contener espacios en blanco ni los componentes
-especiales . y .. además no puede ser /live (o ninguno de sus
-sub\-directorios) ni / (para este último utilizar persistencia
-"full\-ov"). Una vez activados todos los cambios (creación, modificación y
-borrado de ficheros) en \fIDIR\fP en el sistema de ficheros en vivo, son
-guardados de forma persistente en una ruta equivalente a \fIDIR\fP en el medio
-persistente, llamado el directorio de origen. La manera de conseguir la
-persistencia por defecto es simplemente hacer un montaje enlazado
-(bind\-mount N.del T.) del directorio de origen al \fIDIR\fP, aunque esto se
-puede cambiar utilizando las opciones \fIOPTION\fPs.
+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.
.PP
Todos los montajes personalizados serán montados en orden de tal manera que
dos montajes personalizados no se "escondan" uno al otro. Por ejemplo, si
msgid ""
msgstr ""
"Project-Id-Version: live-boot 3.0~a31-1\n"
-"POT-Creation-Date: 2012-06-06 18:40+0300\n"
+"POT-Creation-Date: 2012-06-06 18:54+0300\n"
"PO-Revision-Date: 2012-04-08 22:48+0300\n"
"Last-Translator: Daniel Baumann <daniel@debian.org>\n"
"Language-Team: none\n"
msgid ""
"live-boot will probe devices for persistence media. These can be partitions "
"(with the correct GPT name), filesystems (with the correct label) or image "
-"files (with the correct file name). Overlays are labeled/named either \"full-"
-"ov\", which will be mounted on /, or \"custom-ov\", which can be completely "
-"customized (see I<live-persistence.conf>(5)). The order these are handled "
-"are: full-ov, custom-ov. Overlay image files have extensions which "
-"determines their filesystem, e.g. \"custom-ov.ext4\"."
+"files (with the correct file name). Overlays are labeled/named \"persistence"
+"\" (see I<live-persistence.conf>(5)). Overlay image files have extensions "
+"which determines their filesystem, e.g. \"persistence.ext4\"."
msgstr ""
#. type: IP
msgid ""
msgstr ""
"Project-Id-Version: live-boot 3.0~a31-1\n"
-"POT-Creation-Date: 2012-06-06 18:26+0300\n"
+"POT-Creation-Date: 2012-06-06 18:55+0300\n"
"PO-Revision-Date: 2012-04-08 22:48+0300\n"
"Last-Translator: Daniel Baumann <daniel@debian.org>\n"
"Language-Team: none\n"
msgstr ""
#. type: SH
-#: en/live-boot.7:160 en/live-persistence.conf.5:191
+#: en/live-boot.7:156 en/live-persistence.conf.5:191
#, no-wrap
msgid "SEE ALSO"
msgstr ""
#. type: Plain text
-#: en/live-boot.7:164 en/live-persistence.conf.5:195
+#: en/live-boot.7:160 en/live-persistence.conf.5:195
msgid "I<live-build>(7)"
msgstr ""
#. type: Plain text
-#: en/live-boot.7:166 en/live-persistence.conf.5:197
+#: en/live-boot.7:162 en/live-persistence.conf.5:197
msgid "I<live-config>(7)"
msgstr ""
#. type: Plain text
-#: en/live-boot.7:168 en/live-persistence.conf.5:199
+#: en/live-boot.7:164 en/live-persistence.conf.5:199
msgid "I<live-tools>(7)"
msgstr ""
#. type: SH
-#: en/live-boot.7:169 en/live-persistence.conf.5:200
+#: en/live-boot.7:165 en/live-persistence.conf.5:200
#, no-wrap
msgid "HOMEPAGE"
msgstr ""
#. type: Plain text
-#: en/live-boot.7:171 en/live-persistence.conf.5:204
+#: en/live-boot.7:167 en/live-persistence.conf.5:204
msgid ""
"More information about live-boot and the Debian Live project can be found on "
"the homepage at E<lt>I<http://live.debian.net/>E<gt> and in the manual at "
msgstr ""
#. type: SH
-#: en/live-boot.7:172 en/live-persistence.conf.5:205
+#: en/live-boot.7:168 en/live-persistence.conf.5:205
#, no-wrap
msgid "BUGS"
msgstr ""
#. type: Plain text
-#: en/live-boot.7:174 en/live-persistence.conf.5:210
+#: en/live-boot.7:170 en/live-persistence.conf.5:210
msgid ""
"Bugs can be reported by submitting a bugreport for the live-boot package in "
"the Debian Bug Tracking System at E<lt>I<http://bugs.debian.org/>E<gt> or by "
msgstr ""
#. type: SH
-#: en/live-boot.7:175 en/live-persistence.conf.5:211
+#: en/live-boot.7:171 en/live-persistence.conf.5:211
#, no-wrap
msgid "AUTHOR"
msgstr ""
#: en/live-persistence.conf.5:13
msgid ""
"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\") \"custom-ov\", that "
+"file name, but from now on we will just say \"label\") \"persistence\", that "
"volume's persistence is fully customizable through the B<live-persistence."
"conf> file stored on the root of its file system. Any such labeled volume "
"must have such a file, or it will be ignored."
msgid ""
"For each custom mount I<DIR> 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), or / (for the latter, use \"full-ov\" "
-"persistence instead). Once activated all changes (file deletion, creation "
-"and modification) to I<DIR> on the live file system are stored persistently "
-"into a path equivalent to I<DIR> on the persistence media, called the source "
-"directory. The default way to achieve persistence is to simply bind-mount "
-"the corresponding source directory to I<DIR>, but this can be changed "
-"through the use of I<OPTION>s."
+"(or any of its sub-directories). Once activated all changes (file deletion, "
+"creation and modification) to I<DIR> on the live file system are stored "
+"persistently into a path equivalent to I<DIR> on the persistence media, "
+"called the source directory. The default way to achieve persistence is to "
+"simply bind-mount the corresponding source directory to I<DIR>, but this can "
+"be changed through the use of I<OPTION>s."
msgstr ""
#. type: Plain text
msgid ""
msgstr ""
"Project-Id-Version: live-boot 3.0~a31-1\n"
-"POT-Creation-Date: 2012-06-06 18:40+0300\n"
+"POT-Creation-Date: 2012-06-06 18:54+0300\n"
"PO-Revision-Date: 2012-05-13 18:30+0100\n"
"Last-Translator: Carlos Zuferri «chals» <chals@altorricon.com>\n"
"Language-Team: none\n"
msgid ""
"live-boot will probe devices for persistence media. These can be partitions "
"(with the correct GPT name), filesystems (with the correct label) or image "
-"files (with the correct file name). Overlays are labeled/named either \"full-"
-"ov\", which will be mounted on /, or \"custom-ov\", which can be completely "
-"customized (see I<live-persistence.conf>(5)). The order these are handled "
-"are: full-ov, custom-ov. Overlay image files have extensions which "
-"determines their filesystem, e.g. \"custom-ov.ext4\"."
+"files (with the correct file name). Overlays are labeled/named \"persistence"
+"\" (see I<live-persistence.conf>(5)). Overlay image files have extensions "
+"which determines their filesystem, e.g. \"persistence.ext4\"."
msgstr ""
"live-boot buscará dispositivos con \"persistence\". Estos pueden ser "
"particiones (con el nombre GPT correcto), sistemas de ficheros (con la "
msgid ""
msgstr ""
"Project-Id-Version: live-boot 3.0~a31-1\n"
-"POT-Creation-Date: 2012-06-06 18:26+0300\n"
+"POT-Creation-Date: 2012-06-06 18:55+0300\n"
"PO-Revision-Date: \n"
"Last-Translator: Carlos Zuferri «chals» <chals@altorricon.com>\n"
"Language-Team: none\n"
msgstr "OPCIONES"
#. type: SH
-#: en/live-boot.7:160 en/live-persistence.conf.5:191
+#: en/live-boot.7:156 en/live-persistence.conf.5:191
#, no-wrap
msgid "SEE ALSO"
msgstr "VER ADEMÁS"
#. type: Plain text
-#: en/live-boot.7:164 en/live-persistence.conf.5:195
+#: en/live-boot.7:160 en/live-persistence.conf.5:195
msgid "I<live-build>(7)"
msgstr "I<live-build>(7)"
#. type: Plain text
-#: en/live-boot.7:166 en/live-persistence.conf.5:197
+#: en/live-boot.7:162 en/live-persistence.conf.5:197
msgid "I<live-config>(7)"
msgstr "I<live-config>(7)"
#. type: Plain text
-#: en/live-boot.7:168 en/live-persistence.conf.5:199
+#: en/live-boot.7:164 en/live-persistence.conf.5:199
msgid "I<live-tools>(7)"
msgstr "I<live-tools>(7)"
#. type: SH
-#: en/live-boot.7:169 en/live-persistence.conf.5:200
+#: en/live-boot.7:165 en/live-persistence.conf.5:200
#, no-wrap
msgid "HOMEPAGE"
msgstr "PÁGINA WEB"
#. type: Plain text
-#: en/live-boot.7:171 en/live-persistence.conf.5:204
+#: en/live-boot.7:167 en/live-persistence.conf.5:204
msgid ""
"More information about live-boot and the Debian Live project can be found on "
"the homepage at E<lt>I<http://live.debian.net/>E<gt> and in the manual at "
"E<lt>I<http://live.debian.net/manual/>E<gt>."
#. type: SH
-#: en/live-boot.7:172 en/live-persistence.conf.5:205
+#: en/live-boot.7:168 en/live-persistence.conf.5:205
#, no-wrap
msgid "BUGS"
msgstr "ERRORES"
#. type: Plain text
-#: en/live-boot.7:174 en/live-persistence.conf.5:210
+#: en/live-boot.7:170 en/live-persistence.conf.5:210
msgid ""
"Bugs can be reported by submitting a bugreport for the live-boot package in "
"the Debian Bug Tracking System at E<lt>I<http://bugs.debian.org/>E<gt> or by "
"Live a la dirección E<lt>I<debian-live@lists.debian.org>E<gt>."
#. type: SH
-#: en/live-boot.7:175 en/live-persistence.conf.5:211
+#: en/live-boot.7:171 en/live-persistence.conf.5:211
#, no-wrap
msgid "AUTHOR"
msgstr "AUTOR"
#. type: Plain text
#: en/live-persistence.conf.5:13
+#, fuzzy
+#| msgid ""
+#| "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\") \"custom-ov\", "
+#| "that volume's persistence is fully customizable through the B<live-"
+#| "persistence.conf> file stored on the root of its file system. Any such "
+#| "labeled volume must have such a file, or it will be ignored."
msgid ""
"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\") \"custom-ov\", that "
+"file name, but from now on we will just say \"label\") \"persistence\", that "
"volume's persistence is fully customizable through the B<live-persistence."
"conf> file stored on the root of its file system. Any such labeled volume "
"must have such a file, or it will be ignored."
#. type: Plain text
#: en/live-persistence.conf.5:35
+#, fuzzy
+#| msgid ""
+#| "For each custom mount I<DIR> 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), or / (for the latter, use \"full-ov\" "
+#| "persistence instead). Once activated all changes (file deletion, creation "
+#| "and modification) to I<DIR> on the live file system are stored "
+#| "persistently into a path equivalent to I<DIR> on the persistence media, "
+#| "called the source directory. The default way to achieve persistence is to "
+#| "simply bind-mount the corresponding source directory to I<DIR>, but this "
+#| "can be changed through the use of I<OPTION>s."
msgid ""
"For each custom mount I<DIR> 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), or / (for the latter, use \"full-ov\" "
-"persistence instead). Once activated all changes (file deletion, creation "
-"and modification) to I<DIR> on the live file system are stored persistently "
-"into a path equivalent to I<DIR> on the persistence media, called the source "
-"directory. The default way to achieve persistence is to simply bind-mount "
-"the corresponding source directory to I<DIR>, but this can be changed "
-"through the use of I<OPTION>s."
+"(or any of its sub-directories). Once activated all changes (file deletion, "
+"creation and modification) to I<DIR> on the live file system are stored "
+"persistently into a path equivalent to I<DIR> on the persistence media, "
+"called the source directory. The default way to achieve persistence is to "
+"simply bind-mount the corresponding source directory to I<DIR>, but this can "
+"be changed through the use of I<OPTION>s."
msgstr ""
"Para cada uno de los montajes personalizados I<DIR> debe ser una ruta "
"absoluta que no puede contener espacios en blanco ni los componentes "
msgid ""
msgstr ""
"Project-Id-Version: live-boot VERSION\n"
-"POT-Creation-Date: 2012-06-06 18:40+0300\n"
+"POT-Creation-Date: 2012-06-06 18:54+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgid ""
"live-boot will probe devices for persistence media. These can be partitions "
"(with the correct GPT name), filesystems (with the correct label) or image "
-"files (with the correct file name). Overlays are labeled/named either \"full-"
-"ov\", which will be mounted on /, or \"custom-ov\", which can be completely "
-"customized (see I<live-persistence.conf>(5)). The order these are handled "
-"are: full-ov, custom-ov. Overlay image files have extensions which "
-"determines their filesystem, e.g. \"custom-ov.ext4\"."
+"files (with the correct file name). Overlays are labeled/named \"persistence"
+"\" (see I<live-persistence.conf>(5)). Overlay image files have extensions "
+"which determines their filesystem, e.g. \"persistence.ext4\"."
msgstr ""
#. type: IP
msgid ""
msgstr ""
"Project-Id-Version: live-boot VERSION\n"
-"POT-Creation-Date: 2012-06-06 18:26+0300\n"
+"POT-Creation-Date: 2012-06-06 18:55+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
msgstr ""
#. type: SH
-#: en/live-boot.7:160 en/live-persistence.conf.5:191
+#: en/live-boot.7:156 en/live-persistence.conf.5:191
#, no-wrap
msgid "SEE ALSO"
msgstr ""
#. type: Plain text
-#: en/live-boot.7:164 en/live-persistence.conf.5:195
+#: en/live-boot.7:160 en/live-persistence.conf.5:195
msgid "I<live-build>(7)"
msgstr ""
#. type: Plain text
-#: en/live-boot.7:166 en/live-persistence.conf.5:197
+#: en/live-boot.7:162 en/live-persistence.conf.5:197
msgid "I<live-config>(7)"
msgstr ""
#. type: Plain text
-#: en/live-boot.7:168 en/live-persistence.conf.5:199
+#: en/live-boot.7:164 en/live-persistence.conf.5:199
msgid "I<live-tools>(7)"
msgstr ""
#. type: SH
-#: en/live-boot.7:169 en/live-persistence.conf.5:200
+#: en/live-boot.7:165 en/live-persistence.conf.5:200
#, no-wrap
msgid "HOMEPAGE"
msgstr ""
#. type: Plain text
-#: en/live-boot.7:171 en/live-persistence.conf.5:204
+#: en/live-boot.7:167 en/live-persistence.conf.5:204
msgid ""
"More information about live-boot and the Debian Live project can be found on "
"the homepage at E<lt>I<http://live.debian.net/>E<gt> and in the manual at "
msgstr ""
#. type: SH
-#: en/live-boot.7:172 en/live-persistence.conf.5:205
+#: en/live-boot.7:168 en/live-persistence.conf.5:205
#, no-wrap
msgid "BUGS"
msgstr ""
#. type: Plain text
-#: en/live-boot.7:174 en/live-persistence.conf.5:210
+#: en/live-boot.7:170 en/live-persistence.conf.5:210
msgid ""
"Bugs can be reported by submitting a bugreport for the live-boot package in "
"the Debian Bug Tracking System at E<lt>I<http://bugs.debian.org/>E<gt> or by "
msgstr ""
#. type: SH
-#: en/live-boot.7:175 en/live-persistence.conf.5:211
+#: en/live-boot.7:171 en/live-persistence.conf.5:211
#, no-wrap
msgid "AUTHOR"
msgstr ""
#: en/live-persistence.conf.5:13
msgid ""
"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\") \"custom-ov\", that "
+"file name, but from now on we will just say \"label\") \"persistence\", that "
"volume's persistence is fully customizable through the B<live-persistence."
"conf> file stored on the root of its file system. Any such labeled volume "
"must have such a file, or it will be ignored."
msgid ""
"For each custom mount I<DIR> 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), or / (for the latter, use \"full-ov\" "
-"persistence instead). Once activated all changes (file deletion, creation "
-"and modification) to I<DIR> on the live file system are stored persistently "
-"into a path equivalent to I<DIR> on the persistence media, called the source "
-"directory. The default way to achieve persistence is to simply bind-mount "
-"the corresponding source directory to I<DIR>, but this can be changed "
-"through the use of I<OPTION>s."
+"(or any of its sub-directories). Once activated all changes (file deletion, "
+"creation and modification) to I<DIR> on the live file system are stored "
+"persistently into a path equivalent to I<DIR> on the persistence media, "
+"called the source directory. The default way to achieve persistence is to "
+"simply bind-mount the corresponding source directory to I<DIR>, but this can "
+"be changed through the use of I<OPTION>s."
msgstr ""
#. type: Plain text
old_root_overlay_label="live-rw"
old_home_overlay_label="home-rw"
-custom_overlay_label="custom-ov"
+custom_overlay_label="persistence"
persistence_list="live-persistence.conf"
if [ ! -f /live.vars ]