.\" This file was generated with po4a. Translate the source file.
.\"
.\"*******************************************************************
-.TH LIVE\-BOOT 7 2012\-04\-08 3.0~a26\-1 "Debian Live Project"
+.TH LIVE\-BOOT 7 2012\-04\-09 3.0~a26\-1 "Debian Live Project"
.SH NAME
\fBlive\-boot\fP \- System Boot Scripts
.\" This file was generated with po4a. Translate the source file.
.\"
.\"*******************************************************************
-.TH LIVE\-BOOT conf 2012\-04\-08 3.0~a26\-1 "Debian Live Project"
+.TH LIVE\-BOOT conf 2012\-04\-09 3.0~a26\-1 "Debian Live Project"
.SH NAME
\fBlive\-persistence.conf\fP \- Configuration file for persistence media in
custom mount, it will be created automatically, and permissions and
ownership will be optimistically set according to \fIDIR\fP. It will also be
bootstrapped by copying the contents of the \fIDIR\fP into its source directory
-on the persistence media. The bootstrapping will not happen when the
-\fBlinkfiles\fP or \fBunion\fP options are used (see below).
+on the persistence media. The bootstrapping will not happen when the \fBlink\fP
+or \fBunion\fP options are used (see below).
.SH OPTIONS
Custom mounts defined in \fBlive\-persistence.conf\fP accept the following
be in effect):
.IP \fBbind\fP 4
Bind\-mount the source directory to \fIDIR\fP. This is the default.
-.IP \fBlinkfiles\fP 4
+.IP \fBlink\fP 4
Create the directory structure of the source directory on the persistence
media in \fIDIR\fP and create symbolic links from the corresponding place in
\fIDIR\fP to each file in the source directory. Existing files or directories
source; removed links will reappear after a reboot. To permanently add or
delete a file one must do so directly in the source directory.
.IP
-Effectively \fBlinkfiles\fP will make only files already in the source
-directory persistent, not any other files in \fIDIR\fP. These files must be
-manually added to the source directory to make use of this option, and they
-will appear in \fIDIR\fP in addition to files already there. This option is
-useful when only certain files need to be persistent, not the whole
-directory they're in, e.g. some configuration files in a user's home
-directory.
+Effectively \fBlink\fP will make only files already in the source directory
+persistent, not any other files in \fIDIR\fP. These files must be manually
+added to the source directory to make use of this option, and they will
+appear in \fIDIR\fP in addition to files already there. This option is useful
+when only certain files need to be persistent, not the whole directory
+they're in, e.g. some configuration files in a user's home directory.
.IP \fBunion\fP 4
Save the rw branch of a union on the persistence media, so only the changes
are stored persistently. This can potentially reduce disk usage compared to
All persistence volumes will be mounted here (in a directory corresponding
to the device name). The \fBlive\-persistence.conf\fP file can easily be edited
through this mount, as well as any source directories (which is especially
-practical for custom mounts using the \fBlinkfiles\fP option).
+practical for custom mounts using the \fBlink\fP option).
.SH EXAMPLES
for ease of reference):
.TP 7
1.
-/home/user1 linkfiles,source=config\-files/user1
+/home/user1 link,source=config\-files/user1
.TP
2.
-/home/user2 linkfiles,source=config\-files/user2
+/home/user2 link,source=config\-files/user2
.TP
3.
/home
.PP
One could argue, though, that lines 1 and 2 in the example
\fBlive\-persistence.conf\fP file above are unnecessary since line 3 already
-would make all of /home persistent. The \fBlinkfiles\fP option is intended for
+would make all of /home persistent. The \fBlink\fP option is intended for
situations where you don't want a complete directory to be persistent, only
certain files in it or its sub\-directories.
.PP
.\" This file was generated with po4a. Translate the source file.
.\"
.\"*******************************************************************
-.TH LIVE\-BOOT 1 2012\-04\-08 3.0~a26\-1 "Debian Live Project"
+.TH LIVE\-BOOT 1 2012\-04\-09 3.0~a26\-1 "Debian Live Project"
.SH NAME
\fBlive\-snapshot\fP \- simple script to ease persistence usage
-.TH LIVE\-BOOT 7 2012\-04\-08 3.0~a26-1 "Debian Live Project"
+.TH LIVE\-BOOT 7 2012\-04\-09 3.0~a26-1 "Debian Live Project"
.SH NAME
\fBlive\-boot\fR \- System Boot Scripts
-.TH LIVE\-BOOT conf 2012\-04\-08 3.0~a26-1 "Debian Live Project"
+.TH LIVE\-BOOT conf 2012\-04\-09 3.0~a26-1 "Debian Live Project"
.SH NAME
\fBlive-persistence.conf\fR \- Configuration file for persistence media in
permissions and ownership will be optimistically set according to
\fIDIR\fR. It will also be bootstrapped by copying the contents of the
\fIDIR\fR into its source directory on the persistence media. The
-bootstrapping will not happen when the \fBlinkfiles\fR or \fBunion\fR
+bootstrapping will not happen when the \fBlink\fR or \fBunion\fR
options are used (see below).
.SH OPTIONS
will be in effect):
.IP "\fBbind\fR" 4
Bind-mount the source directory to \fIDIR\fR. This is the default.
-.IP "\fBlinkfiles\fR" 4
+.IP "\fBlink\fR" 4
Create the directory structure of the source directory on the
persistence media in \fIDIR\fR and create symbolic links from the
corresponding place in \fIDIR\fR to each file in the source directory.
links will reappear after a reboot. To permanently add or delete a
file one must do so directly in the source directory.
.IP
-Effectively \fBlinkfiles\fR will make only files already in the source
+Effectively \fBlink\fR will make only files already in the source
directory persistent, not any other files in \fIDIR\fR. These files
must be manually added to the source directory to make use of this
option, and they will appear in \fIDIR\fR in addition to files already
corresponding to the device name). The \fBlive-persistence.conf\fR file can
easily be edited through this mount, as well as any source directories
(which is especially practical for custom mounts using the
-\fBlinkfiles\fR option).
+\fBlink\fR option).
.SH EXAMPLES
for ease of reference):
.TP 7
1.
-/home/user1 linkfiles,source=config-files/user1
+/home/user1 link,source=config-files/user1
.TP
2.
-/home/user2 linkfiles,source=config-files/user2
+/home/user2 link,source=config-files/user2
.TP
3.
/home
.PP
One could argue, though, that lines 1 and 2 in the example
\fBlive-persistence.conf\fR file above are unnecessary since line 3 already
-would make all of /home persistent. The \fBlinkfiles\fR option is
+would make all of /home persistent. The \fBlink\fR option is
intended for situations where you don't want a complete directory to
be persistent, only certain files in it or its sub-directories.
.PP
-.TH LIVE\-BOOT 1 2012\-04\-08 3.0~a26-1 "Debian Live Project"
+.TH LIVE\-BOOT 1 2012\-04\-09 3.0~a26-1 "Debian Live Project"
.SH NAME
\fBlive\-snapshot\fR \- simple script to ease persistence usage
msgid ""
msgstr ""
"Project-Id-Version: live-boot VERSION\n"
-"POT-Creation-Date: 2012-04-08 22:48+0300\n"
+"POT-Creation-Date: 2012-04-09 15:13+0300\n"
"PO-Revision-Date: 2012-04-08 22:48+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
#. type: TH
#: en/live-boot.7:1 en/live-persistence.conf.5:1 en/live-snapshot.1:1
#, no-wrap
-msgid "2012-04-08"
+msgid "2012-04-09"
msgstr ""
#. type: TH
msgid ""
msgstr ""
"Project-Id-Version: live-boot VERSION\n"
-"POT-Creation-Date: 2012-04-08 22:48+0300\n"
+"POT-Creation-Date: 2012-04-09 15:13+0300\n"
"PO-Revision-Date: 2012-04-08 22:48+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
#. type: TH
#: en/live-boot.7:1 en/live-persistence.conf.5:1 en/live-snapshot.1:1
#, no-wrap
-msgid "2012-04-08"
+msgid "2012-04-09"
msgstr ""
#. type: TH
"custom mount, it will be created automatically, and permissions and "
"ownership will be optimistically set according to I<DIR>. It will also be "
"bootstrapped by copying the contents of the I<DIR> into its source directory "
-"on the persistence media. The bootstrapping will not happen when the "
-"B<linkfiles> or B<union> options are used (see below)."
+"on the persistence media. The bootstrapping will not happen when the B<link> "
+"or B<union> options are used (see below)."
msgstr ""
#. type: Plain text
#. type: IP
#: en/live-persistence.conf.5:74
#, no-wrap
-msgid "B<linkfiles>"
+msgid "B<link>"
msgstr ""
#. type: Plain text
#. type: Plain text
#: en/live-persistence.conf.5:91
msgid ""
-"Effectively B<linkfiles> will make only files already in the source "
-"directory persistent, not any other files in I<DIR>. These files must be "
-"manually added to the source directory to make use of this option, and they "
-"will appear in I<DIR> in addition to files already there. This option is "
-"useful when only certain files need to be persistent, not the whole "
-"directory they're in, e.g. some configuration files in a user's home "
-"directory."
+"Effectively B<link> will make only files already in the source directory "
+"persistent, not any other files in I<DIR>. These files must be manually "
+"added to the source directory to make use of this option, and they will "
+"appear in I<DIR> in addition to files already there. This option is useful "
+"when only certain files need to be persistent, not the whole directory "
+"they're in, e.g. some configuration files in a user's home directory."
msgstr ""
#. type: IP
"All persistence volumes will be mounted here (in a directory corresponding "
"to the device name). The B<live-persistence.conf> file can easily be edited "
"through this mount, as well as any source directories (which is especially "
-"practical for custom mounts using the B<linkfiles> option)."
+"practical for custom mounts using the B<link> option)."
msgstr ""
#. type: SH
#. type: Plain text
#: en/live-persistence.conf.5:118
-msgid "/home/user1 linkfiles,source=config-files/user1"
+msgid "/home/user1 link,source=config-files/user1"
msgstr ""
#. type: TP
#. type: Plain text
#: en/live-persistence.conf.5:121
-msgid "/home/user2 linkfiles,source=config-files/user2"
+msgid "/home/user2 link,source=config-files/user2"
msgstr ""
#. type: TP
msgid ""
"One could argue, though, that lines 1 and 2 in the example B<live-"
"persistence.conf> file above are unnecessary since line 3 already would make "
-"all of /home persistent. The B<linkfiles> option is intended for situations "
-"where you don't want a complete directory to be persistent, only certain "
-"files in it or its sub-directories."
+"all of /home persistent. The B<link> option is intended for situations where "
+"you don't want a complete directory to be persistent, only certain files in "
+"it or its sub-directories."
msgstr ""
#. type: Plain text
msgid ""
msgstr ""
"Project-Id-Version: live-boot VERSION\n"
-"POT-Creation-Date: 2012-04-08 22:48+0300\n"
+"POT-Creation-Date: 2012-04-09 15:13+0300\n"
"PO-Revision-Date: 2012-04-08 22:48+0300\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
#. type: TH
#: en/live-boot.7:1 en/live-persistence.conf.5:1 en/live-snapshot.1:1
#, no-wrap
-msgid "2012-04-08"
+msgid "2012-04-09"
msgstr ""
#. type: TH
msgid ""
msgstr ""
"Project-Id-Version: live-boot VERSION\n"
-"POT-Creation-Date: 2012-04-08 22:48+0300\n"
+"POT-Creation-Date: 2012-04-09 15:13+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"
#. type: TH
#: en/live-boot.7:1 en/live-persistence.conf.5:1 en/live-snapshot.1:1
#, no-wrap
-msgid "2012-04-08"
+msgid "2012-04-09"
msgstr ""
#. type: TH
msgid ""
msgstr ""
"Project-Id-Version: live-boot VERSION\n"
-"POT-Creation-Date: 2012-04-08 22:48+0300\n"
+"POT-Creation-Date: 2012-04-09 15:13+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"
#. type: TH
#: en/live-boot.7:1 en/live-persistence.conf.5:1 en/live-snapshot.1:1
#, no-wrap
-msgid "2012-04-08"
+msgid "2012-04-09"
msgstr ""
#. type: TH
"custom mount, it will be created automatically, and permissions and "
"ownership will be optimistically set according to I<DIR>. It will also be "
"bootstrapped by copying the contents of the I<DIR> into its source directory "
-"on the persistence media. The bootstrapping will not happen when the "
-"B<linkfiles> or B<union> options are used (see below)."
+"on the persistence media. The bootstrapping will not happen when the B<link> "
+"or B<union> options are used (see below)."
msgstr ""
#. type: Plain text
#. type: IP
#: en/live-persistence.conf.5:74
#, no-wrap
-msgid "B<linkfiles>"
+msgid "B<link>"
msgstr ""
#. type: Plain text
#. type: Plain text
#: en/live-persistence.conf.5:91
msgid ""
-"Effectively B<linkfiles> will make only files already in the source "
-"directory persistent, not any other files in I<DIR>. These files must be "
-"manually added to the source directory to make use of this option, and they "
-"will appear in I<DIR> in addition to files already there. This option is "
-"useful when only certain files need to be persistent, not the whole "
-"directory they're in, e.g. some configuration files in a user's home "
-"directory."
+"Effectively B<link> will make only files already in the source directory "
+"persistent, not any other files in I<DIR>. These files must be manually "
+"added to the source directory to make use of this option, and they will "
+"appear in I<DIR> in addition to files already there. This option is useful "
+"when only certain files need to be persistent, not the whole directory "
+"they're in, e.g. some configuration files in a user's home directory."
msgstr ""
#. type: IP
"All persistence volumes will be mounted here (in a directory corresponding "
"to the device name). The B<live-persistence.conf> file can easily be edited "
"through this mount, as well as any source directories (which is especially "
-"practical for custom mounts using the B<linkfiles> option)."
+"practical for custom mounts using the B<link> option)."
msgstr ""
#. type: SH
#. type: Plain text
#: en/live-persistence.conf.5:118
-msgid "/home/user1 linkfiles,source=config-files/user1"
+msgid "/home/user1 link,source=config-files/user1"
msgstr ""
#. type: TP
#. type: Plain text
#: en/live-persistence.conf.5:121
-msgid "/home/user2 linkfiles,source=config-files/user2"
+msgid "/home/user2 link,source=config-files/user2"
msgstr ""
#. type: TP
msgid ""
"One could argue, though, that lines 1 and 2 in the example B<live-"
"persistence.conf> file above are unnecessary since line 3 already would make "
-"all of /home persistent. The B<linkfiles> option is intended for situations "
-"where you don't want a complete directory to be persistent, only certain "
-"files in it or its sub-directories."
+"all of /home persistent. The B<link> option is intended for situations where "
+"you don't want a complete directory to be persistent, only certain files in "
+"it or its sub-directories."
msgstr ""
#. type: Plain text
msgid ""
msgstr ""
"Project-Id-Version: live-boot VERSION\n"
-"POT-Creation-Date: 2012-04-08 22:48+0300\n"
+"POT-Creation-Date: 2012-04-09 15:13+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"
#. type: TH
#: en/live-boot.7:1 en/live-persistence.conf.5:1 en/live-snapshot.1:1
#, no-wrap
-msgid "2012-04-08"
+msgid "2012-04-09"
msgstr ""
#. type: TH
fi
local opt_source=""
- local opt_linkfiles=""
+ local opt_link=""
for opt in $(echo ${options} | tr ',' ' ');
do
case "${opt}" in
source=*)
opt_source=${opt#source=}
;;
- linkfiles)
- opt_linkfiles="yes"
+ link)
+ opt_link="yes"
;;
union|bind)
;;
local full_source="$(trim_path ${backing}/${source})"
local full_dest="$(trim_path ${rootmnt}/${dir})"
- if [ -n "${opt_linkfiles}" ]
+ if [ -n "${opt_link}" ]
then
echo "${device} ${full_source} ${full_dest} ${options}" >> ${links}
else
while read device source dest options # < ${custom_mounts}
do
local opt_bind="yes"
- local opt_linkfiles=""
+ local opt_link=""
local opt_union=""
for opt in $(echo ${options} | tr ',' ' ');
do
case "${opt}" in
bind)
opt_bind="yes"
- unset opt_linkfiles opt_union
+ unset opt_link opt_union
;;
- linkfiles)
- opt_linkfiles="yes"
+ link)
+ opt_link="yes"
unset opt_bind opt_union
;;
union)
opt_union="yes"
- unset opt_bind opt_linkfiles
+ unset opt_bind opt_link
;;
esac
done
if [ -n "${PERSISTENCE_READONLY}" ]
then
continue
- elif [ -n "${opt_union}" ] || [ -n "${opt_linkfiles}" ]
+ elif [ -n "${opt_union}" ] || [ -n "${opt_link}" ]
then
# unions and don't need to be bootstrapped
- # linkfiles dirs can't be bootstrapped in a sensible way
+ # link dirs can't be bootstrapped in a sensible way
mkdir -p "${source}"
chown_ref "${dest}" "${source}"
chmod_ref "${dest}" "${source}"
# XXX: If CONFIG_AUFS_ROBR is added to the Debian kernel we can
# ignore the loop below and set rofs_dest_backing=$dest
local rofs_dest_backing=""
- if [ -n "${opt_linkfiles}"]
+ if [ -n "${opt_link}"]
then
for d in ${rootmnt}/live/rofs/*
do
done
fi
- if [ -n "${opt_linkfiles}" ] && [ -z "${PERSISTENCE_READONLY}" ]
+ if [ -n "${opt_link}" ] && [ -z "${PERSISTENCE_READONLY}" ]
then
link_files ${source} ${dest} ${rootmnt}
- elif [ -n "${opt_linkfiles}" ] && [ -n "${PERSISTENCE_READONLY}" ]
+ elif [ -n "${opt_link}" ] && [ -n "${PERSISTENCE_READONLY}" ]
then
mkdir -p ${rootmnt}/live/persistence
local links_source=$(mktemp -d ${rootmnt}/live/persistence/links-source-XXXXXX)
# post boot
local cow_dir="/live/overlay/${dest}"
fi
- if [ -e "${cow_dir}" ] && [ -z "${opt_linkfiles}" ]
+ if [ -e "${cow_dir}" ] && [ -z "${opt_link}" ]
then
# If an earlier custom mount has files here
# it will "block" the current mount's files