From 89adeb3c4d91d12062e6fca8a00978eea52fe67f Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Thu, 27 Sep 2012 11:02:41 +0200 Subject: Switching to final name for the persistence configuration file 'persistence.conf' in line with boot parameter. --- manpages/de/live-boot.de.7 | 8 +- manpages/de/live-persistence.conf.de.5 | 209 ---------- manpages/de/persistence.conf.de.5 | 207 ++++++++++ manpages/en/live-boot.7 | 8 +- manpages/en/live-persistence.conf.5 | 213 ---------- manpages/en/persistence.conf.5 | 213 ++++++++++ manpages/es/live-boot.es.7 | 10 +- manpages/es/live-persistence.conf.es.5 | 225 ----------- manpages/es/persistence.conf.es.5 | 225 +++++++++++ manpages/po/de/live-boot.7.po | 46 +-- manpages/po/de/live-persistence.conf.5.po | 513 ------------------------ manpages/po/de/persistence.conf.5.po | 511 ++++++++++++++++++++++++ manpages/po/es/live-boot.7.po | 56 +-- manpages/po/es/live-persistence.conf.5.po | 640 ------------------------------ manpages/po/es/persistence.conf.5.po | 638 +++++++++++++++++++++++++++++ manpages/po4a.cfg | 2 +- manpages/pot/live-boot.7.pot | 44 +- manpages/pot/live-persistence.conf.5.pot | 514 ------------------------ manpages/pot/persistence.conf.5.pot | 512 ++++++++++++++++++++++++ 19 files changed, 2393 insertions(+), 2401 deletions(-) delete mode 100644 manpages/de/live-persistence.conf.de.5 create mode 100644 manpages/de/persistence.conf.de.5 delete mode 100644 manpages/en/live-persistence.conf.5 create mode 100644 manpages/en/persistence.conf.5 delete mode 100644 manpages/es/live-persistence.conf.es.5 create mode 100644 manpages/es/persistence.conf.es.5 delete mode 100644 manpages/po/de/live-persistence.conf.5.po create mode 100644 manpages/po/de/persistence.conf.5.po delete mode 100644 manpages/po/es/live-persistence.conf.5.po create mode 100644 manpages/po/es/persistence.conf.5.po delete mode 100644 manpages/pot/live-persistence.conf.5.pot create mode 100644 manpages/pot/persistence.conf.5.pot (limited to 'manpages') diff --git a/manpages/de/live-boot.de.7 b/manpages/de/live-boot.de.7 index d2b0e5f..0c77340 100644 --- a/manpages/de/live-boot.de.7 +++ b/manpages/de/live-boot.de.7 @@ -3,7 +3,7 @@ .\" This file was generated with po4a. Translate the source file. .\" .\"******************************************************************* -.TH LIVE\-BOOT 7 26.09.2012 3.0~b3\-1 "Debian Live Project" +.TH LIVE\-BOOT 7 27.09.2012 3.0~b3\-1 "Debian Live Project" .SH NAME \fBlive\-boot\fP \- System Boot Scripts @@ -180,7 +180,7 @@ This parameter enables usage of local swap partitions. 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\fP(5)). Overlay image files have extensions which +(see \fIpersistence.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 @@ -263,10 +263,10 @@ loaded in alphanumeric order. .IP \fB/etc/live/boot/*\fP 4 .IP \fBlive/boot.conf\fP 4 .IP \fBlive/boot/*\fP 4 -.IP \fBlive\-persistence.conf\fP 4 +.IP \fBpersistence.conf\fP 4 .SH "SEE ALSO" -\fIlive\-persistence.conf\fP(5) +\fIpersistence.conf\fP(5) .PP \fIlive\-build\fP(7) .PP diff --git a/manpages/de/live-persistence.conf.de.5 b/manpages/de/live-persistence.conf.de.5 deleted file mode 100644 index f160b4e..0000000 --- a/manpages/de/live-persistence.conf.de.5 +++ /dev/null @@ -1,209 +0,0 @@ -.\"******************************************************************* -.\" -.\" This file was generated with po4a. Translate the source file. -.\" -.\"******************************************************************* -.TH LIVE\-BOOT conf 26.09.2012 3.0~b3\-1 "Debian Live Project" - -.SH NAME -\fBlive\-persistence.conf\fP \- Configuration file for persistence media in -live\-boot - -.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 -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 -with a "#" (used for comments), both which will be ignored. A so called -"custom mount" has the format: -.PP -.RS -\fIDIR\fP [\fIOPTION\fP]... -.RE -.PP -which roughly translates to "make \fIDIR\fP persistence in the way described by -the list of \fIOPTION\fPs". -.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. -.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 -would always be the case that /a is mounted first, then /a/b. This remains -true no matter how the lines in \fBlive\-persistence.conf\fP are ordered, or if -several \fBlive\-persistence.conf\fP files on different persistence media are -used at the same time. However, it is forbidden for custom mounts to have -their source directory inside the source directory of another custom mount, -so the source directories that are auto\-created by live\-boot does not -support "nested" mounts like /a and /a/b on the same media. In this case you -must use the \fBsource\fP option (see below) to make sure that they are stored -in different source directories. -.PP -When a source directory doesn't exist on the persistence media for a certain -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 \fBlink\fP -or \fBunion\fP options are used (see below). - -.SH OPTIONS -Custom mounts defined in \fBlive\-persistence.conf\fP accept the following -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). -.PP -The following options are mutually exclusive (only the last given one will -be in effect): -.IP \fBbind\fP 4 -Bind\-mount the source directory to \fIDIR\fP. This is the default. -.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 -with the same name as any link will be overwritten. Note that deleting the -links in \fIDIR\fP will only remove the link, not the corresponding file in the -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 \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 -bind\-mounts, and will not hide files added to the read\-only media. One -caveat is that the union will use \fIDIR\fP from the image's read\-only file -system, not the real file system root, so files created after boot (e.g. by -live\-config) will not appear in the union. This option will use the union -file system specified by live\-boot's \fBunion\fP boot parameter, but is not -supported with \fBunion=unionmount\fP. - -.SH DIRECTORIES -.IP \fB/live/persistence\fP 4 -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 \fBlink\fP option). - -.SH EXAMPLES - -Let's say we have a persistence volume \fIVOL\fP with the a -\fBlive\-persistence.conf\fP file containing the following four lines (numbered -for ease of reference): -.TP 7 -1. -/home/user1 link,source=config\-files/user1 -.TP -2. -/home/user2 link,source=config\-files/user2 -.TP -3. -/home -.TP -4. -/usr union -.PP -The corresponding source directories are: -.TP 7 -1. -\fIVOL\fP/config\-files/user1 (but it would be \fIVOL\fP/home/user1 without the -\fBsource\fP option) -.TP -2. -\fIVOL\fP/config\-files/user2 (but it would be \fIVOL\fP/home/user2 without the -\fBsource\fP option) -.TP -3. -\fIVOL\fP/home -.TP -4. -\fIVOL\fP/usr -.PP -It was necessary to set the \fBsource\fP options for 1 and 2, since they -otherwise would become nested with 3's source, which is invalid. -.PP -Line 3 will be taken care of before line 1 and 2 in order to prevent custom -mounts 1 and 2 from being hidden by 3. When line 3 is handled, \fIVOL\fP/home -is simply bind\-mounted on /home. To illustrate what happens for lines 1 and -2, let's say that the following files exist: -.TP 7 -a. -\fIVOL\fP/config\-files/user1/.emacs -.TP -b. -\fIVOL\fP/config\-files/user2/.bashrc -.TP -c. -\fIVOL\fP/config\-files/user2/.ssh/config -.PP -Then the following links and directories will be created: -.TP 7 -Link: -/home/user1/.emacs \-> \fIVOL\fP/config\-files/user1/.emacs (from a) -.TP -Link: -/home/user2/.bashrc \-> \fIVOL\fP/config\-files/user2/.bashrc (from b) -.TP -Dir: -/homea/user2/.ssh (from c) -.TP -Link: -/home/user2/.ssh/config \-> \fIVOL\fP/config\-files/user2/.ssh/config (from -c) -.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 \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 -Line 4 can be mounted at any time since its \fIDIR\fP (and source directory) is -completely disjoint from all the other custom mounts. When mounted, -\fIVOL\fP/usr will be the rw branch due to the \fBunion\fP option, and will only -contain the difference compared to the underlying read\-only file -system. Hence packages could be installed into /usr with great space\-wise -efficiency compared to bind\-mounts, since in the latter case all of /usr -would have to be copied into \fIVOL\fP/usr during the initial bootstrap. - -.SH "SEE ALSO" -\fIlive\-boot\fP(7) -.PP -\fIlive\-build\fP(7) -.PP -\fIlive\-config\fP(7) -.PP -\fIlive\-tools\fP(7) - -.SH HOMEPAGE -More information about live\-boot and the Debian Live project can be found on -the homepage at <\fIhttp://live.debian.net/\fP> and in the manual at -<\fIhttp://live.debian.net/manual/\fP>. - -.SH BUGS -Bugs can be reported by submitting a bugreport for the live\-boot package in -the Debian Bug Tracking System at <\fIhttp://bugs.debian.org/\fP> or by -writing a mail to the Debian Live mailing list at -<\fIdebian\-live@lists.debian.org\fP>. - -.SH AUTHOR -live\-persistence.conf was written by anonym <\fIanonym@lavabit.com\fP> -for the Debian project. diff --git a/manpages/de/persistence.conf.de.5 b/manpages/de/persistence.conf.de.5 new file mode 100644 index 0000000..18e6b4f --- /dev/null +++ b/manpages/de/persistence.conf.de.5 @@ -0,0 +1,207 @@ +.\"******************************************************************* +.\" +.\" This file was generated with po4a. Translate the source file. +.\" +.\"******************************************************************* +.TH LIVE\-BOOT conf 27.09.2012 3.0~b3\-1 "Debian Live Project" + +.SH NAME +\fBpersistence.conf\fP \- Configuration file for persistence media in live\-boot + +.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 +volume's persistence is fully customizable through the \fBpersistence.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 \fBpersistence.conf\fP allows empty lines and lines starting with +a "#" (used for comments), both which will be ignored. A so called "custom +mount" has the format: +.PP +.RS +\fIDIR\fP [\fIOPTION\fP]... +.RE +.PP +which roughly translates to "make \fIDIR\fP persistence in the way described by +the list of \fIOPTION\fPs". +.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. +.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 +would always be the case that /a is mounted first, then /a/b. This remains +true no matter how the lines in \fBpersistence.conf\fP are ordered, or if +several \fBpersistence.conf\fP files on different persistence media are used at +the same time. However, it is forbidden for custom mounts to have their +source directory inside the source directory of another custom mount, so the +source directories that are auto\-created by live\-boot does not support +"nested" mounts like /a and /a/b on the same media. In this case you must +use the \fBsource\fP option (see below) to make sure that they are stored in +different source directories. +.PP +When a source directory doesn't exist on the persistence media for a certain +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 \fBlink\fP +or \fBunion\fP options are used (see below). + +.SH OPTIONS +Custom mounts defined in \fBpersistence.conf\fP accept the following 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). +.PP +The following options are mutually exclusive (only the last given one will +be in effect): +.IP \fBbind\fP 4 +Bind\-mount the source directory to \fIDIR\fP. This is the default. +.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 +with the same name as any link will be overwritten. Note that deleting the +links in \fIDIR\fP will only remove the link, not the corresponding file in the +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 \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 +bind\-mounts, and will not hide files added to the read\-only media. One +caveat is that the union will use \fIDIR\fP from the image's read\-only file +system, not the real file system root, so files created after boot (e.g. by +live\-config) will not appear in the union. This option will use the union +file system specified by live\-boot's \fBunion\fP boot parameter, but is not +supported with \fBunion=unionmount\fP. + +.SH DIRECTORIES +.IP \fB/live/persistence\fP 4 +All persistence volumes will be mounted here (in a directory corresponding +to the device name). The \fBpersistence.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 \fBlink\fP option). + +.SH EXAMPLES + +Let's say we have a persistence volume \fIVOL\fP with the a \fBpersistence.conf\fP +file containing the following four lines (numbered for ease of reference): +.TP 7 +1. +/home/user1 link,source=config\-files/user1 +.TP +2. +/home/user2 link,source=config\-files/user2 +.TP +3. +/home +.TP +4. +/usr union +.PP +The corresponding source directories are: +.TP 7 +1. +\fIVOL\fP/config\-files/user1 (but it would be \fIVOL\fP/home/user1 without the +\fBsource\fP option) +.TP +2. +\fIVOL\fP/config\-files/user2 (but it would be \fIVOL\fP/home/user2 without the +\fBsource\fP option) +.TP +3. +\fIVOL\fP/home +.TP +4. +\fIVOL\fP/usr +.PP +It was necessary to set the \fBsource\fP options for 1 and 2, since they +otherwise would become nested with 3's source, which is invalid. +.PP +Line 3 will be taken care of before line 1 and 2 in order to prevent custom +mounts 1 and 2 from being hidden by 3. When line 3 is handled, \fIVOL\fP/home +is simply bind\-mounted on /home. To illustrate what happens for lines 1 and +2, let's say that the following files exist: +.TP 7 +a. +\fIVOL\fP/config\-files/user1/.emacs +.TP +b. +\fIVOL\fP/config\-files/user2/.bashrc +.TP +c. +\fIVOL\fP/config\-files/user2/.ssh/config +.PP +Then the following links and directories will be created: +.TP 7 +Link: +/home/user1/.emacs \-> \fIVOL\fP/config\-files/user1/.emacs (from a) +.TP +Link: +/home/user2/.bashrc \-> \fIVOL\fP/config\-files/user2/.bashrc (from b) +.TP +Dir: +/homea/user2/.ssh (from c) +.TP +Link: +/home/user2/.ssh/config \-> \fIVOL\fP/config\-files/user2/.ssh/config (from +c) +.PP +One could argue, though, that lines 1 and 2 in the example +\fBpersistence.conf\fP file above are unnecessary since line 3 already 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 +Line 4 can be mounted at any time since its \fIDIR\fP (and source directory) is +completely disjoint from all the other custom mounts. When mounted, +\fIVOL\fP/usr will be the rw branch due to the \fBunion\fP option, and will only +contain the difference compared to the underlying read\-only file +system. Hence packages could be installed into /usr with great space\-wise +efficiency compared to bind\-mounts, since in the latter case all of /usr +would have to be copied into \fIVOL\fP/usr during the initial bootstrap. + +.SH "SEE ALSO" +\fIlive\-boot\fP(7) +.PP +\fIlive\-build\fP(7) +.PP +\fIlive\-config\fP(7) +.PP +\fIlive\-tools\fP(7) + +.SH HOMEPAGE +More information about live\-boot and the Debian Live project can be found on +the homepage at <\fIhttp://live.debian.net/\fP> and in the manual at +<\fIhttp://live.debian.net/manual/\fP>. + +.SH BUGS +Bugs can be reported by submitting a bugreport for the live\-boot package in +the Debian Bug Tracking System at <\fIhttp://bugs.debian.org/\fP> or by +writing a mail to the Debian Live mailing list at +<\fIdebian\-live@lists.debian.org\fP>. + +.SH AUTHOR +persistence.conf was written by anonym <\fIanonym@lavabit.com\fP> for +the Debian project. diff --git a/manpages/en/live-boot.7 b/manpages/en/live-boot.7 index 8fd08a4..8871abb 100644 --- a/manpages/en/live-boot.7 +++ b/manpages/en/live-boot.7 @@ -1,4 +1,4 @@ -.TH LIVE\-BOOT 7 2012\-09\-26 3.0~b3-1 "Debian Live Project" +.TH LIVE\-BOOT 7 2012\-09\-27 3.0~b3-1 "Debian Live Project" .SH NAME \fBlive\-boot\fR \- System Boot Scripts @@ -109,7 +109,7 @@ This parameters allows to set a custom ramdisk size (it's the '\-o size' option .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 "persistence" (see \fIlive-persistence.conf\fR(5)). Overlay image files have extensions which determines their filesystem, e.g. "persistence.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 \fIpersistence.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 @@ -151,10 +151,10 @@ This optional file (inside the live media) contains a list of white\-space or ca .IP "\fB/etc/live/boot/*\fR" 4 .IP "\fBlive/boot.conf\fR" 4 .IP "\fBlive/boot/*\fR" 4 -.IP "\fBlive-persistence.conf\fR" 4 +.IP "\fBpersistence.conf\fR" 4 .SH SEE ALSO -\fIlive-persistence.conf\fR(5) +\fIpersistence.conf\fR(5) .PP \fIlive\-build\fR(7) .PP diff --git a/manpages/en/live-persistence.conf.5 b/manpages/en/live-persistence.conf.5 deleted file mode 100644 index 92fa09f..0000000 --- a/manpages/en/live-persistence.conf.5 +++ /dev/null @@ -1,213 +0,0 @@ -.TH LIVE\-BOOT conf 2012\-09\-26 3.0~b3-1 "Debian Live Project" - -.SH NAME -\fBlive-persistence.conf\fR \- Configuration file for persistence media in -live\-boot - -.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 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 -The format of \fBlive-persistence.conf\fR allows empty lines and lines starting -with a "#" (used for comments), both which will be ignored. A so -called "custom mount" has the format: -.PP -.RS -\fIDIR\fR [\fIOPTION\fR]... -.RE -.PP -which roughly translates to "make \fIDIR\fR persistence in the way -described by the list of \fIOPTION\fRs". -.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). -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 -achieve persistence is to simply bind-mount the corresponding source -directory to \fIDIR\fR, but this can be changed through the use of -\fIOPTION\fRs. -.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\fR:s /a and /a/b it would always be the case that /a is mounted -first, then /a/b. This remains true no matter how the lines in -\fBlive-persistence.conf\fR are ordered, or if several \fBlive-persistence.conf\fR files -on different persistence media are used at the same time. However, it -is forbidden for custom mounts to have their source directory inside -the source directory of another custom mount, so the source -directories that are auto-created by live-boot does not support -"nested" mounts like /a and /a/b on the same media. In this case you -must use the \fBsource\fR option (see below) to make sure that they -are stored in different source directories. -.PP -When a source directory doesn't exist on the persistence media for a -certain custom mount, it will be created automatically, and -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 \fBlink\fR or \fBunion\fR -options are used (see below). - -.SH OPTIONS -Custom mounts defined in \fBlive-persistence.conf\fR accept the following -options in a coma-separated list: -.IP "\fBsource\fR=\fIPATH\fR" 4 -When given, store the persistence changes into \fIPATH\fR on the -persistence media. \fIPATH\fR 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\fR type of persistence). -.PP -The following options are mutually exclusive (only the last given one -will be in effect): -.IP "\fBbind\fR" 4 -Bind-mount the source directory to \fIDIR\fR. This is the default. -.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. -Existing files or directories with the same name as any link will be -overwritten. Note that deleting the links in \fIDIR\fR will only -remove the link, not the corresponding file in the 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 \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 -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\fR" 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 bind-mounts, and will not hide files added to the -read-only media. One caveat is that the union will use \fIDIR\fR from -the image's read-only file system, not the real file system root, so -files created after boot (e.g. by live-config) will not appear in the -union. This option will use the union file system specified by -live-boot's \fBunion\fR boot parameter, but is not supported with -\fBunion=unionmount\fR. - -.SH DIRECTORIES -.IP "\fB/live/persistence\fR" 4 -All persistence volumes will be mounted here (in a directory -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 -\fBlink\fR option). - -.SH EXAMPLES - -Let's say we have a persistence volume \fIVOL\fR with the a -\fBlive-persistence.conf\fR file containing the following four lines (numbered -for ease of reference): -.TP 7 -1. -/home/user1 link,source=config-files/user1 -.TP -2. -/home/user2 link,source=config-files/user2 -.TP -3. -/home -.TP -4. -/usr union -.PP -The corresponding source directories are: -.TP 7 -1. -\fIVOL\fR/config-files/user1 (but it would be \fIVOL\fR/home/user1 -without the \fBsource\fR option) -.TP -2. -\fIVOL\fR/config-files/user2 (but it would be \fIVOL\fR/home/user2 -without the \fBsource\fR option) -.TP -3. -\fIVOL\fR/home -.TP -4. -\fIVOL\fR/usr -.PP -It was necessary to set the \fBsource\fR options for 1 and 2, since -they otherwise would become nested with 3's source, which is invalid. -.PP -Line 3 will be taken care of before line 1 and 2 in order to prevent -custom mounts 1 and 2 from being hidden by 3. When line 3 is handled, -\fIVOL\fR/home is simply bind-mounted on /home. To illustrate what -happens for lines 1 and 2, let's say that the following files exist: -.TP 7 -a. -\fIVOL\fR/config-files/user1/.emacs -.TP -b. -\fIVOL\fR/config-files/user2/.bashrc -.TP -c. -\fIVOL\fR/config-files/user2/.ssh/config -.PP -Then the following links and directories will be created: -.TP 7 -Link: -/home/user1/.emacs -> \fIVOL\fR/config-files/user1/.emacs (from a) -.TP -Link: -/home/user2/.bashrc -> \fIVOL\fR/config-files/user2/.bashrc (from b) -.TP -Dir: -/homea/user2/.ssh (from c) -.TP -Link: -/home/user2/.ssh/config -> \fIVOL\fR/config-files/user2/.ssh/config -(from c) -.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 \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 -Line 4 can be mounted at any time since its \fIDIR\fR (and source -directory) is completely disjoint from all the other custom -mounts. When mounted, \fIVOL\fR/usr will be the rw branch due to the -\fBunion\fR option, and will only contain the difference compared to -the underlying read-only file system. Hence packages could be -installed into /usr with great space-wise efficiency compared to -bind-mounts, since in the latter case all of /usr would have to be -copied into \fIVOL\fR/usr during the initial bootstrap. - -.SH SEE ALSO -\fIlive\-boot\fR(7) -.PP -\fIlive\-build\fR(7) -.PP -\fIlive\-config\fR(7) -.PP -\fIlive\-tools\fR(7) - -.SH HOMEPAGE -More information about live\-boot and the Debian Live project can be -found on the homepage at <\fIhttp://live.debian.net/\fR> and in the -manual at <\fIhttp://live.debian.net/manual/\fR>. - -.SH BUGS -Bugs can be reported by submitting a bugreport for the live\-boot -package in the Debian Bug Tracking System at -<\fIhttp://bugs.debian.org/\fR> or by writing a mail to the Debian -Live mailing list at <\fIdebian-live@lists.debian.org\fR>. - -.SH AUTHOR -live\-persistence.conf was written by anonym <\fIanonym@lavabit.com\fR> for the -Debian project. diff --git a/manpages/en/persistence.conf.5 b/manpages/en/persistence.conf.5 new file mode 100644 index 0000000..cb5503b --- /dev/null +++ b/manpages/en/persistence.conf.5 @@ -0,0 +1,213 @@ +.TH LIVE\-BOOT conf 2012\-09\-27 3.0~b3-1 "Debian Live Project" + +.SH NAME +\fBpersistence.conf\fR \- Configuration file for persistence media in +live\-boot + +.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 volume's persistence is fully customizable through the +\fBpersistence.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 +The format of \fBpersistence.conf\fR allows empty lines and lines starting +with a "#" (used for comments), both which will be ignored. A so +called "custom mount" has the format: +.PP +.RS +\fIDIR\fR [\fIOPTION\fR]... +.RE +.PP +which roughly translates to "make \fIDIR\fR persistence in the way +described by the list of \fIOPTION\fRs". +.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). +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 +achieve persistence is to simply bind-mount the corresponding source +directory to \fIDIR\fR, but this can be changed through the use of +\fIOPTION\fRs. +.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\fR:s /a and /a/b it would always be the case that /a is mounted +first, then /a/b. This remains true no matter how the lines in +\fBpersistence.conf\fR are ordered, or if several \fBpersistence.conf\fR files +on different persistence media are used at the same time. However, it +is forbidden for custom mounts to have their source directory inside +the source directory of another custom mount, so the source +directories that are auto-created by live-boot does not support +"nested" mounts like /a and /a/b on the same media. In this case you +must use the \fBsource\fR option (see below) to make sure that they +are stored in different source directories. +.PP +When a source directory doesn't exist on the persistence media for a +certain custom mount, it will be created automatically, and +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 \fBlink\fR or \fBunion\fR +options are used (see below). + +.SH OPTIONS +Custom mounts defined in \fBpersistence.conf\fR accept the following +options in a coma-separated list: +.IP "\fBsource\fR=\fIPATH\fR" 4 +When given, store the persistence changes into \fIPATH\fR on the +persistence media. \fIPATH\fR 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\fR type of persistence). +.PP +The following options are mutually exclusive (only the last given one +will be in effect): +.IP "\fBbind\fR" 4 +Bind-mount the source directory to \fIDIR\fR. This is the default. +.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. +Existing files or directories with the same name as any link will be +overwritten. Note that deleting the links in \fIDIR\fR will only +remove the link, not the corresponding file in the 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 \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 +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\fR" 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 bind-mounts, and will not hide files added to the +read-only media. One caveat is that the union will use \fIDIR\fR from +the image's read-only file system, not the real file system root, so +files created after boot (e.g. by live-config) will not appear in the +union. This option will use the union file system specified by +live-boot's \fBunion\fR boot parameter, but is not supported with +\fBunion=unionmount\fR. + +.SH DIRECTORIES +.IP "\fB/live/persistence\fR" 4 +All persistence volumes will be mounted here (in a directory +corresponding to the device name). The \fBpersistence.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 +\fBlink\fR option). + +.SH EXAMPLES + +Let's say we have a persistence volume \fIVOL\fR with the a +\fBpersistence.conf\fR file containing the following four lines (numbered +for ease of reference): +.TP 7 +1. +/home/user1 link,source=config-files/user1 +.TP +2. +/home/user2 link,source=config-files/user2 +.TP +3. +/home +.TP +4. +/usr union +.PP +The corresponding source directories are: +.TP 7 +1. +\fIVOL\fR/config-files/user1 (but it would be \fIVOL\fR/home/user1 +without the \fBsource\fR option) +.TP +2. +\fIVOL\fR/config-files/user2 (but it would be \fIVOL\fR/home/user2 +without the \fBsource\fR option) +.TP +3. +\fIVOL\fR/home +.TP +4. +\fIVOL\fR/usr +.PP +It was necessary to set the \fBsource\fR options for 1 and 2, since +they otherwise would become nested with 3's source, which is invalid. +.PP +Line 3 will be taken care of before line 1 and 2 in order to prevent +custom mounts 1 and 2 from being hidden by 3. When line 3 is handled, +\fIVOL\fR/home is simply bind-mounted on /home. To illustrate what +happens for lines 1 and 2, let's say that the following files exist: +.TP 7 +a. +\fIVOL\fR/config-files/user1/.emacs +.TP +b. +\fIVOL\fR/config-files/user2/.bashrc +.TP +c. +\fIVOL\fR/config-files/user2/.ssh/config +.PP +Then the following links and directories will be created: +.TP 7 +Link: +/home/user1/.emacs -> \fIVOL\fR/config-files/user1/.emacs (from a) +.TP +Link: +/home/user2/.bashrc -> \fIVOL\fR/config-files/user2/.bashrc (from b) +.TP +Dir: +/homea/user2/.ssh (from c) +.TP +Link: +/home/user2/.ssh/config -> \fIVOL\fR/config-files/user2/.ssh/config +(from c) +.PP +One could argue, though, that lines 1 and 2 in the example +\fBpersistence.conf\fR file above are unnecessary since line 3 already +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 +Line 4 can be mounted at any time since its \fIDIR\fR (and source +directory) is completely disjoint from all the other custom +mounts. When mounted, \fIVOL\fR/usr will be the rw branch due to the +\fBunion\fR option, and will only contain the difference compared to +the underlying read-only file system. Hence packages could be +installed into /usr with great space-wise efficiency compared to +bind-mounts, since in the latter case all of /usr would have to be +copied into \fIVOL\fR/usr during the initial bootstrap. + +.SH SEE ALSO +\fIlive\-boot\fR(7) +.PP +\fIlive\-build\fR(7) +.PP +\fIlive\-config\fR(7) +.PP +\fIlive\-tools\fR(7) + +.SH HOMEPAGE +More information about live\-boot and the Debian Live project can be +found on the homepage at <\fIhttp://live.debian.net/\fR> and in the +manual at <\fIhttp://live.debian.net/manual/\fR>. + +.SH BUGS +Bugs can be reported by submitting a bugreport for the live\-boot +package in the Debian Bug Tracking System at +<\fIhttp://bugs.debian.org/\fR> or by writing a mail to the Debian +Live mailing list at <\fIdebian-live@lists.debian.org\fR>. + +.SH AUTHOR +persistence.conf was written by anonym <\fIanonym@lavabit.com\fR> for the +Debian project. diff --git a/manpages/es/live-boot.es.7 b/manpages/es/live-boot.es.7 index ce14d4d..b35d1a5 100644 --- a/manpages/es/live-boot.es.7 +++ b/manpages/es/live-boot.es.7 @@ -3,7 +3,7 @@ .\" This file was generated with po4a. Translate the source file. .\" .\"******************************************************************* -.TH LIVE\-BOOT 7 26.09.2012 3.0~b3\-1 "Proyecto Debian Live" +.TH LIVE\-BOOT 7 27.09.2012 3.0~b3\-1 "Proyecto Debian Live" .SH NOMBRE \fBlive\-boot\fP \- Scripts de Arranque del Sistema @@ -191,8 +191,8 @@ live\-boot buscará dispositivos con "persistence". Estos pueden ser particiones (con el nombre GPT correcto), sistemas de ficheros (con la etiqueta correcta) o ficheros imagen (con el nombre de fichero correcto). Los overlays tienen la etiqueta/nombre "persistence" (ver -\fIlive\-persistence.conf\fP(5)). Los ficheros imagen overlay tienen extensiones -que determinan su sistema de ficheros, por ejemplo, "persistence.ext4". +\fIpersistence.conf\fP(5)). Los ficheros imagen overlay tienen extensiones que +determinan su sistema de ficheros, por ejemplo, "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 @@ -282,10 +282,10 @@ alfanumérico. .IP \fB/etc/live/boot/*\fP 4 .IP \fBlive/boot.conf\fP 4 .IP \fBlive/boot.d/*\fP 4 -.IP \fBlive\-persistence.conf\fP 4 +.IP \fBpersistence.conf\fP 4 .SH "VER ADEMÁS" -\fIlive\-persistence.conf\fP(5) +\fIpersistence.conf\fP(5) .PP \fIlive\-build\fP(7) .PP diff --git a/manpages/es/live-persistence.conf.es.5 b/manpages/es/live-persistence.conf.es.5 deleted file mode 100644 index 757363e..0000000 --- a/manpages/es/live-persistence.conf.es.5 +++ /dev/null @@ -1,225 +0,0 @@ -.\"******************************************************************* -.\" -.\" This file was generated with po4a. Translate the source file. -.\" -.\"******************************************************************* -.TH LIVE\-BOOT conf 26.09.2012 3.0~b3\-1 "Proyecto Debian Live" - -.SH NOMBRE -\fBlive\-persistence.conf\fP \- Fichero para configurar medios de almacenamiento -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") "persistence", 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 esa -etiqueta debe tener uno de esos ficheros, o si no será ignorado. -.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 -ignorados. Un "montaje personalizado" tiene el formato: -.PP -.RS -\fIDIR\fP [\fIOPTION\fP]... -.RE -.PP -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 /. 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. -.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 -tenemos los dos \fIDIR\fP:s /a y /a/b siempre /a será montado en primer lugar, -después /a/b. Esto siempre es así sin importar el orden en que aparezcan las -líneas en \fBlive\-persistence.conf\fP o incluso si se usan varios ficheros -\fBlive\-persistence.conf\fP en medios persistentes distintos al mismo -tiempo. Sin embargo, no está permitido que un montaje personalizado tenga su -directorio de origen en el interior del directorio de origen de otro montaje -personalizado, ya que los directorios de origen que live\-boot crea -automáticamente no tienen soporte para montajes "anidados" como /a y /a/b en -el mismo medio. En este caso se debe usar la opción \fBsource\fP (ver debajo) -para asegurarse de que se almacenan en directorios de origen diferentes. -.PP -Cuando un directorio de origen no existe en los medios con persistencia para -un montaje personalizado en particular, se creará automáticamente, y los -permisos y sus propietarios se establecen de forma óptima de acuerdo a -\fIDIR\fP. También se realiza una preinstalación (bootstrap N. del T.) copiando -los contenidos de \fIDIR\fP en su directorio de origen en el medio con -persistencia. La preinstalación no se realiza cuando se utilizan las -opciones \fBlink\fP o \fBunion\fP (ver debajo). - -.SH OPCIONES -Los montajes personalizados definidos en \fBlive\-persistence.conf\fP aceptan -las siguientes opciones en una lista separada por comas: -.IP \fBsource\fP=\fIPATH\fP 4 -Cuando se especifica, se guardan los cambios persistentes en \fIPATH\fP en los -medios con persistencia. \fIPATH\fP debe ser una ruta relativa (respecto a la -raíz del medio persistente) que no puede contener espacios en blanco o los -componentes especiales . o .. con la excepción de que puede ser simplemente -\&. lo que significa la raíz del medio persistente. Esta opción es relevante -si se desea anidar montajes personalizados, lo que de otro modo produciría -errores, o si se desea hacer que toda la raíz del medio esté disponible (de -forma similar al ahora obsoleto tipo de persistencia \fBhome\-rw\fP) -.PP -Las siguientes opciones son mutuamente exclusivas (únicamente la última -tendrá efecto): -.IP \fBbind\fP 4 -Montar de forma enlazada el directorio de origen a \fIDIR\fP. Esto es así por -defecto. -.IP \fBlink\fP 4 -Crea la estructura de directorios del directorio de origen en el medio -persistente en \fIDIR\fP y crea los enlaces simbólicos desde el lugar -correspondiente en \fIDIR\fP a cada fichero en el directorio de origen. Si los -directorios o ficheros contienen el mismo nombre, al igual que cualquier -otro enlace, serán sobrescritos. Tener en cuenta que los enlaces en \fIDIR\fP -sólo eliminan el enlace, no el fichero correspondiente en el directorio; los -enlaces eliminados reaparecerán tras reiniciar. Para añadir o eliminar un -fichero de forma permanente se debe hacer directamente en el directorio de -origen. -.IP -\fBlink\fP tan sólo hará persistentes los ficheros que ya se encuentran en el -directorio de origen, y no cualquier otro fichero en \fIDIR\fP. Estos ficheros -deben ser añadidos manualmente en el directorio de origen pare utilizar esta -opción y ellos aparecerán en \fIDIR\fP además de los ficheros que ya se -encuentran allí. Esta opción es útil cuando sólo es necesario hacer -persistentes ciertos ficheros y no todo el directorio en el que se -encuentran, por ejemplo, algunos ficheros de configuración en el directorio -home de un usuario. -.IP \fBunion\fP 4 -Guardar la rama rw de una unión en un medio persistente, de modo que los -cambios son guardados de forma persistente. Potencialmente esto puede -reducir el uso del disco comparado con los montajes enlazados, y no -esconderá los ficheros añadidos a los medios de sólo lectura. Un buen truco -es que la unión utilizará el \fIDIR\fP del sistema de ficheros de sólo lectura -de la imagen y no de la raíz del sistema de ficheros real, por eso los -ficheros que se crean después del arranque (por ejemplo live\-config) no -aparecerán en la unión. Esta opción utilizará el sistema de ficheros unión -especificado por el parámetro de arranque \fBunion\fP de live\-boot pero no -tiene soporte si se utiliza \fBunion=unionmount\fP. - -.SH DIRECTORIOS -.IP \fB/live/persistence\fP 4 -Aquí se montarán todos los volumenes persistentes (en un directorio que -corresponda con el nombre del dispositivo). El fichero -\fBlive\-persistence.conf\fP se puede editar fácilmente a través de este -montaje, así como cualquier directorio de origen (esto resulta especialmente -práctico para los montajes personalizados usando la opción \fBlink\fP). - -.SH EJEMPLOS - -Si tenemos un volumen con persistencia \fIVOL\fP con un fichero -\fBlive\-persistence.conf\fP que contiene las cuatro lineas siguientes -(numeradas para una mejor referencia): -.TP 7 -1. -/home/user1 link,source=config\-files/user1 -.TP -2. -/home/user2 link,source=config\-files/user2 -.TP -3. -/home -.TP -4. -/usr union -.PP -Los directorios de origen correspondientes son: -.TP 7 -1. -\fIVOL\fP/config\-files/user1 (pero sería \fIVOL\fP/home/user1 sin la opción -\fBsource\fP) -.TP -2. -\fIVOL\fP/config\-files/user2 (pero sería \fIVOL\fP/home/user2 sin la opción -\fBsource\fP) -.TP -3. -\fIVOL\fP/home -.TP -4. -\fIVOL\fP/usr -.PP -Era necesario establecer las opciones \fBsource\fP para 1 y 2, ya que de otro -modo resultarían anidados con el origen de 3, lo cual no es válido. -.PP -La línea 3 será tenida en cuenta antes que las líneas 1 y 3 para evitar que -los montajes personalizados 1 y 2 resulten escondidos por 3. Cuando se -procesa la línea 3, \fIVOL\fP/home es simplemente montado en unión a -/home. Para ilustrar lo que sucede con las líneas 1 y 2, digamos que los -siguientes ficheros existen: -.TP 7 -a. -\fIVOL\fP/config\-files/user1/.emacs -.TP -b. -\fIVOL\fP/config\-files/user2/.bashrc -.TP -c. -\fIVOL\fP/config\-files/user2/.ssh/config -.PP -Entonces se crearán los siguientes enlaces y directorios: -.TP 7 -Enlace: -/home/user1/.emacs \-> \fIVOL\fP/config\-files/user1/.emacs (de a) -.TP -Enlace: -/home/user2/.bashrc \-> \fIVOL\fP/config\-files/user2/.bashrc (de b) -.TP -Directorio: -/homea/user2/.ssh (de c) -.TP -Enlace: -/home/user2/.ssh/config \-> \fIVOL\fP/config\-files/user2/.ssh/config (de c) -.PP -Se podría decir, sin embargo, que las líneas 1 y 2 en el fichero de ejemplo -\fBlive\-persistence.conf\fP anterior son innecesarias ya que la línea 3 ya -crearía el directorio /home persistente. La opción \fBlink\fP se utiliza en -situaciones en las que no se desea guardar de forma persistente un -directorio completo, sino únicamente algunos ficheros o subdirectorios -incluidos en él. -.PP -La línea 4 se puede montar en cualquier momento ya que su \fIDIR\fP (y su -directorio de origen) es completamente independiente de todos los otros -montajes personalizados. Cuando se monta, \fIVOL\fP/usr será la rama rw debido -a la opción \fBunion\fP y tan sólo contendrá la diferencia en comparación con -el sistema de ficheros subyacente de sólo lectura. Por eso los paquetes -pueden ser instalados en /usr con gran eficiencia de espacio comparado con -los montajes enlazados, ya que en este último caso el contenido de /usr -tendría que ser copiado en \fIVOL\fP/usr durante la preinstalación inicial. - -.SH "VER ADEMÁS" -\fIlive\-boot\fP(7) -.PP -\fIlive\-build\fP(7) -.PP -\fIlive\-config\fP(7) -.PP -\fIlive\-tools\fP(7) - -.SH "PÁGINA WEB" -Se puede encontrar más información acerca de live\-boot y el proyecto Debian -Live en la página web <\fIhttp://live.debian.net/\fP> y en el manual en -<\fIhttp://live.debian.net/manual/\fP>. - -.SH ERRORES -Se puede notificar los fallos enviando un informe de errores sobre el -paquete live\-boot en el Debian Bug Tracking System en -<\fIhttp://bugs.debian.org/\fP> o escribiendo un mensaje a la lista de -correo de Debian Live a la dirección -<\fIdebian\-live@lists.debian.org\fP>. - -.SH AUTOR -live\-persistence.conf fue escrito por anonym <\fIanonym@lavabit.com\fP> -para el proyecto Debian. diff --git a/manpages/es/persistence.conf.es.5 b/manpages/es/persistence.conf.es.5 new file mode 100644 index 0000000..52cd84f --- /dev/null +++ b/manpages/es/persistence.conf.es.5 @@ -0,0 +1,225 @@ +.\"******************************************************************* +.\" +.\" This file was generated with po4a. Translate the source file. +.\" +.\"******************************************************************* +.TH LIVE\-BOOT conf 27.09.2012 3.0~b3\-1 "Proyecto Debian Live" + +.SH NOMBRE +\fBpersistence.conf\fP \- Fichero para configurar medios de almacenamiento 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") "persistence", la persistencia de ese volumen es +completamente personalizable a través del fichero \fBpersistence.conf\fP +almacenado en la raíz de su sistema de ficheros. Cualquier volumen esa +etiqueta debe tener uno de esos ficheros, o si no será ignorado. +.PP +El formato de \fBpersistence.conf\fP permite añadir líneas vacias o líneas que +comiencen por "#" (usado para los comentarios), ambos serán ignorados. Un +"montaje personalizado" tiene el formato: +.PP +.RS +\fIDIR\fP [\fIOPTION\fP]... +.RE +.PP +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 /. 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. +.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 +tenemos los dos \fIDIR\fP:s /a y /a/b siempre /a será montado en primer lugar, +después /a/b. Esto siempre es así sin importar el orden en que aparezcan las +líneas en \fBpersistence.conf\fP o incluso si se usan varios ficheros +\fBpersistence.conf\fP en medios persistentes distintos al mismo tiempo. Sin +embargo, no está permitido que un montaje personalizado tenga su directorio +de origen en el interior del directorio de origen de otro montaje +personalizado, ya que los directorios de origen que live\-boot crea +automáticamente no tienen soporte para montajes "anidados" como /a y /a/b en +el mismo medio. En este caso se debe usar la opción \fBsource\fP (ver debajo) +para asegurarse de que se almacenan en directorios de origen diferentes. +.PP +Cuando un directorio de origen no existe en los medios con persistencia para +un montaje personalizado en particular, se creará automáticamente, y los +permisos y sus propietarios se establecen de forma óptima de acuerdo a +\fIDIR\fP. También se realiza una preinstalación (bootstrap N. del T.) copiando +los contenidos de \fIDIR\fP en su directorio de origen en el medio con +persistencia. La preinstalación no se realiza cuando se utilizan las +opciones \fBlink\fP o \fBunion\fP (ver debajo). + +.SH OPCIONES +Los montajes personalizados definidos en \fBpersistence.conf\fP aceptan las +siguientes opciones en una lista separada por comas: +.IP \fBsource\fP=\fIPATH\fP 4 +Cuando se especifica, se guardan los cambios persistentes en \fIPATH\fP en los +medios con persistencia. \fIPATH\fP debe ser una ruta relativa (respecto a la +raíz del medio persistente) que no puede contener espacios en blanco o los +componentes especiales . o .. con la excepción de que puede ser simplemente +\&. lo que significa la raíz del medio persistente. Esta opción es relevante +si se desea anidar montajes personalizados, lo que de otro modo produciría +errores, o si se desea hacer que toda la raíz del medio esté disponible (de +forma similar al ahora obsoleto tipo de persistencia \fBhome\-rw\fP) +.PP +Las siguientes opciones son mutuamente exclusivas (únicamente la última +tendrá efecto): +.IP \fBbind\fP 4 +Montar de forma enlazada el directorio de origen a \fIDIR\fP. Esto es así por +defecto. +.IP \fBlink\fP 4 +Crea la estructura de directorios del directorio de origen en el medio +persistente en \fIDIR\fP y crea los enlaces simbólicos desde el lugar +correspondiente en \fIDIR\fP a cada fichero en el directorio de origen. Si los +directorios o ficheros contienen el mismo nombre, al igual que cualquier +otro enlace, serán sobrescritos. Tener en cuenta que los enlaces en \fIDIR\fP +sólo eliminan el enlace, no el fichero correspondiente en el directorio; los +enlaces eliminados reaparecerán tras reiniciar. Para añadir o eliminar un +fichero de forma permanente se debe hacer directamente en el directorio de +origen. +.IP +\fBlink\fP tan sólo hará persistentes los ficheros que ya se encuentran en el +directorio de origen, y no cualquier otro fichero en \fIDIR\fP. Estos ficheros +deben ser añadidos manualmente en el directorio de origen pare utilizar esta +opción y ellos aparecerán en \fIDIR\fP además de los ficheros que ya se +encuentran allí. Esta opción es útil cuando sólo es necesario hacer +persistentes ciertos ficheros y no todo el directorio en el que se +encuentran, por ejemplo, algunos ficheros de configuración en el directorio +home de un usuario. +.IP \fBunion\fP 4 +Guardar la rama rw de una unión en un medio persistente, de modo que los +cambios son guardados de forma persistente. Potencialmente esto puede +reducir el uso del disco comparado con los montajes enlazados, y no +esconderá los ficheros añadidos a los medios de sólo lectura. Un buen truco +es que la unión utilizará el \fIDIR\fP del sistema de ficheros de sólo lectura +de la imagen y no de la raíz del sistema de ficheros real, por eso los +ficheros que se crean después del arranque (por ejemplo live\-config) no +aparecerán en la unión. Esta opción utilizará el sistema de ficheros unión +especificado por el parámetro de arranque \fBunion\fP de live\-boot pero no +tiene soporte si se utiliza \fBunion=unionmount\fP. + +.SH DIRECTORIOS +.IP \fB/live/persistence\fP 4 +Aquí se montarán todos los volumenes persistentes (en un directorio que +corresponda con el nombre del dispositivo). El fichero \fBpersistence.conf\fP +se puede editar fácilmente a través de este montaje, así como cualquier +directorio de origen (esto resulta especialmente práctico para los montajes +personalizados usando la opción \fBlink\fP). + +.SH EJEMPLOS + +Si tenemos un volumen con persistencia \fIVOL\fP con un fichero +\fBpersistence.conf\fPque contiene las cuatro lineas siguientes (numeradas para +una mejor referencia): +.TP 7 +1. +/home/user1 link,source=config\-files/user1 +.TP +2. +/home/user2 link,source=config\-files/user2 +.TP +3. +/home +.TP +4. +/usr union +.PP +Los directorios de origen correspondientes son: +.TP 7 +1. +\fIVOL\fP/config\-files/user1 (pero sería \fIVOL\fP/home/user1 sin la opción +\fBsource\fP) +.TP +2. +\fIVOL\fP/config\-files/user2 (pero sería \fIVOL\fP/home/user2 sin la opción +\fBsource\fP) +.TP +3. +\fIVOL\fP/home +.TP +4. +\fIVOL\fP/usr +.PP +Era necesario establecer las opciones \fBsource\fP para 1 y 2, ya que de otro +modo resultarían anidados con el origen de 3, lo cual no es válido. +.PP +La línea 3 será tenida en cuenta antes que las líneas 1 y 3 para evitar que +los montajes personalizados 1 y 2 resulten escondidos por 3. Cuando se +procesa la línea 3, \fIVOL\fP/home es simplemente montado en unión a +/home. Para ilustrar lo que sucede con las líneas 1 y 2, digamos que los +siguientes ficheros existen: +.TP 7 +a. +\fIVOL\fP/config\-files/user1/.emacs +.TP +b. +\fIVOL\fP/config\-files/user2/.bashrc +.TP +c. +\fIVOL\fP/config\-files/user2/.ssh/config +.PP +Entonces se crearán los siguientes enlaces y directorios: +.TP 7 +Enlace: +/home/user1/.emacs \-> \fIVOL\fP/config\-files/user1/.emacs (de a) +.TP +Enlace: +/home/user2/.bashrc \-> \fIVOL\fP/config\-files/user2/.bashrc (de b) +.TP +Directorio: +/homea/user2/.ssh (de c) +.TP +Enlace: +/home/user2/.ssh/config \-> \fIVOL\fP/config\-files/user2/.ssh/config (de c) +.PP +Se podría decir, sin embargo, que las líneas 1 y 2 en el fichero de ejemplo +\fBpersistence.conf\fP anterior son innecesarias ya que la línea 3 ya crearía +el directorio /home persistente. La opción \fBlink\fP se utiliza en +situaciones en las que no se desea guardar de forma persistente un +directorio completo, sino únicamente algunos ficheros o subdirectorios +incluidos en él. +.PP +La línea 4 se puede montar en cualquier momento ya que su \fIDIR\fP (y su +directorio de origen) es completamente independiente de todos los otros +montajes personalizados. Cuando se monta, \fIVOL\fP/usr será la rama rw debido +a la opción \fBunion\fP y tan sólo contendrá la diferencia en comparación con +el sistema de ficheros subyacente de sólo lectura. Por eso los paquetes +pueden ser instalados en /usr con gran eficiencia de espacio comparado con +los montajes enlazados, ya que en este último caso el contenido de /usr +tendría que ser copiado en \fIVOL\fP/usr durante la preinstalación inicial. + +.SH "VER ADEMÁS" +\fIlive\-boot\fP(7) +.PP +\fIlive\-build\fP(7) +.PP +\fIlive\-config\fP(7) +.PP +\fIlive\-tools\fP(7) + +.SH "PÁGINA WEB" +Se puede encontrar más información acerca de live\-boot y el proyecto Debian +Live en la página web <\fIhttp://live.debian.net/\fP> y en el manual en +<\fIhttp://live.debian.net/manual/\fP>. + +.SH ERRORES +Se puede notificar los fallos enviando un informe de errores sobre el +paquete live\-boot en el Debian Bug Tracking System en +<\fIhttp://bugs.debian.org/\fP> o escribiendo un mensaje a la lista de +correo de Debian Live a la dirección +<\fIdebian\-live@lists.debian.org\fP>. + +.SH AUTOR +persistence.conf fue escrito por anonym <\fIanonym@lavabit.com\fP> para +el proyecto Debian. diff --git a/manpages/po/de/live-boot.7.po b/manpages/po/de/live-boot.7.po index 0369a03..837a24b 100644 --- a/manpages/po/de/live-boot.7.po +++ b/manpages/po/de/live-boot.7.po @@ -5,7 +5,7 @@ msgid "" msgstr "" "Project-Id-Version: live-boot 3.0~b3-1\n" -"POT-Creation-Date: 2012-09-26 14:38+0300\n" +"POT-Creation-Date: 2012-09-27 10:58+0300\n" "PO-Revision-Date: 2012-04-08 22:48+0300\n" "Last-Translator: Daniel Baumann \n" "Language-Team: none\n" @@ -16,31 +16,31 @@ msgstr "" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #. type: TH -#: en/live-boot.7:1 en/live-persistence.conf.5:1 +#: en/live-boot.7:1 en/persistence.conf.5:1 #, no-wrap msgid "LIVE-BOOT" msgstr "" #. type: TH -#: en/live-boot.7:1 en/live-persistence.conf.5:1 +#: en/live-boot.7:1 en/persistence.conf.5:1 #, no-wrap -msgid "2012-09-26" -msgstr "26.09.2012" +msgid "2012-09-27" +msgstr "27.09.2012" #. type: TH -#: en/live-boot.7:1 en/live-persistence.conf.5:1 +#: en/live-boot.7:1 en/persistence.conf.5:1 #, no-wrap msgid "3.0~b3-1" msgstr "3.0~b3-1" #. type: TH -#: en/live-boot.7:1 en/live-persistence.conf.5:1 +#: en/live-boot.7:1 en/persistence.conf.5:1 #, no-wrap msgid "Debian Live Project" msgstr "" #. type: SH -#: en/live-boot.7:3 en/live-persistence.conf.5:3 +#: en/live-boot.7:3 en/persistence.conf.5:3 #, no-wrap msgid "NAME" msgstr "" @@ -51,7 +51,7 @@ msgid "B - System Boot Scripts" msgstr "" #. type: SH -#: en/live-boot.7:6 en/live-persistence.conf.5:7 +#: en/live-boot.7:6 en/persistence.conf.5:7 #, no-wrap msgid "DESCRIPTION" msgstr "" @@ -137,7 +137,7 @@ msgid "" msgstr "" #. type: SH -#: en/live-boot.7:28 en/live-persistence.conf.5:57 +#: en/live-boot.7:28 en/persistence.conf.5:57 #, no-wrap msgid "OPTIONS" msgstr "" @@ -573,8 +573,8 @@ 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 \"persistence" -"\" (see I(5)). Overlay image files have extensions " -"which determines their filesystem, e.g. \"persistence.ext4\"." +"\" (see I(5)). Overlay image files have extensions which " +"determines their filesystem, e.g. \"persistence.ext4\"." msgstr "" #. type: IP @@ -839,43 +839,43 @@ msgstr "" #. type: IP #: en/live-boot.7:154 #, no-wrap -msgid "B" +msgid "B" msgstr "" #. type: SH -#: en/live-boot.7:156 en/live-persistence.conf.5:191 +#: en/live-boot.7:156 en/persistence.conf.5:191 #, no-wrap msgid "SEE ALSO" msgstr "" #. type: Plain text #: en/live-boot.7:158 -msgid "I(5)" +msgid "I(5)" msgstr "" #. type: Plain text -#: en/live-boot.7:160 en/live-persistence.conf.5:195 +#: en/live-boot.7:160 en/persistence.conf.5:195 msgid "I(7)" msgstr "" #. type: Plain text -#: en/live-boot.7:162 en/live-persistence.conf.5:197 +#: en/live-boot.7:162 en/persistence.conf.5:197 msgid "I(7)" msgstr "" #. type: Plain text -#: en/live-boot.7:164 en/live-persistence.conf.5:199 +#: en/live-boot.7:164 en/persistence.conf.5:199 msgid "I(7)" msgstr "" #. type: SH -#: en/live-boot.7:165 en/live-persistence.conf.5:200 +#: en/live-boot.7:165 en/persistence.conf.5:200 #, no-wrap msgid "HOMEPAGE" msgstr "" #. type: Plain text -#: en/live-boot.7:167 en/live-persistence.conf.5:204 +#: en/live-boot.7:167 en/persistence.conf.5:204 msgid "" "More information about live-boot and the Debian Live project can be found on " "the homepage at EIE and in the manual at " @@ -883,13 +883,13 @@ msgid "" msgstr "" #. type: SH -#: en/live-boot.7:168 en/live-persistence.conf.5:205 +#: en/live-boot.7:168 en/persistence.conf.5:205 #, no-wrap msgid "BUGS" msgstr "" #. type: Plain text -#: en/live-boot.7:170 en/live-persistence.conf.5:210 +#: en/live-boot.7:170 en/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 EIE or by " @@ -898,7 +898,7 @@ msgid "" msgstr "" #. type: SH -#: en/live-boot.7:171 en/live-persistence.conf.5:211 +#: en/live-boot.7:171 en/persistence.conf.5:211 #, no-wrap msgid "AUTHOR" msgstr "" diff --git a/manpages/po/de/live-persistence.conf.5.po b/manpages/po/de/live-persistence.conf.5.po deleted file mode 100644 index 539eede..0000000 --- a/manpages/po/de/live-persistence.conf.5.po +++ /dev/null @@ -1,513 +0,0 @@ -# German translations for live-boot package -# Copyright (C) 2006-2012 Daniel Baumann -# This file is distributed under the same license as the live-boot package. -# -msgid "" -msgstr "" -"Project-Id-Version: live-boot 3.0~b3-1\n" -"POT-Creation-Date: 2012-09-26 14:38+0300\n" -"PO-Revision-Date: 2012-04-08 22:48+0300\n" -"Last-Translator: Daniel Baumann \n" -"Language-Team: none\n" -"Language: de\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=ASCII\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=(n != 1);\n" - -#. type: TH -#: en/live-boot.7:1 en/live-persistence.conf.5:1 -#, no-wrap -msgid "LIVE-BOOT" -msgstr "" - -#. type: TH -#: en/live-boot.7:1 en/live-persistence.conf.5:1 -#, no-wrap -msgid "2012-09-26" -msgstr "26.09.2012" - -#. type: TH -#: en/live-boot.7:1 en/live-persistence.conf.5:1 -#, no-wrap -msgid "3.0~b3-1" -msgstr "3.0~b3-1" - -#. type: TH -#: en/live-boot.7:1 en/live-persistence.conf.5:1 -#, no-wrap -msgid "Debian Live Project" -msgstr "" - -#. type: SH -#: en/live-boot.7:3 en/live-persistence.conf.5:3 -#, no-wrap -msgid "NAME" -msgstr "" - -#. type: SH -#: en/live-boot.7:6 en/live-persistence.conf.5:7 -#, no-wrap -msgid "DESCRIPTION" -msgstr "" - -#. type: SH -#: en/live-boot.7:28 en/live-persistence.conf.5:57 -#, no-wrap -msgid "OPTIONS" -msgstr "" - -#. type: SH -#: en/live-boot.7:156 en/live-persistence.conf.5:191 -#, no-wrap -msgid "SEE ALSO" -msgstr "" - -#. type: Plain text -#: en/live-boot.7:160 en/live-persistence.conf.5:195 -msgid "I(7)" -msgstr "" - -#. type: Plain text -#: en/live-boot.7:162 en/live-persistence.conf.5:197 -msgid "I(7)" -msgstr "" - -#. type: Plain text -#: en/live-boot.7:164 en/live-persistence.conf.5:199 -msgid "I(7)" -msgstr "" - -#. type: SH -#: en/live-boot.7:165 en/live-persistence.conf.5:200 -#, no-wrap -msgid "HOMEPAGE" -msgstr "" - -#. type: Plain text -#: 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 EIE and in the manual at " -"EIE." -msgstr "" - -#. type: SH -#: en/live-boot.7:168 en/live-persistence.conf.5:205 -#, no-wrap -msgid "BUGS" -msgstr "" - -#. type: Plain text -#: 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 EIE or by " -"writing a mail to the Debian Live mailing list at EIE." -msgstr "" - -#. type: SH -#: en/live-boot.7:171 en/live-persistence.conf.5:211 -#, no-wrap -msgid "AUTHOR" -msgstr "" - -#. type: Plain text -#: en/live-persistence.conf.5:6 -msgid "" -"B - Configuration file for persistence media in live-" -"boot" -msgstr "" - -#. type: Plain text -#: 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\") \"persistence\", that " -"volume's persistence is fully customizable through the B file stored on the root of its file system. Any such labeled volume " -"must have such a file, or it will be ignored." -msgstr "" - -#. type: Plain text -#: en/live-persistence.conf.5:17 -msgid "" -"The format of B allows empty lines and lines starting " -"with a \"#\" (used for comments), both which will be ignored. A so called " -"\"custom mount\" has the format:" -msgstr "" - -#. type: Plain text -#: en/live-persistence.conf.5:20 -msgid "I [I